CALCULATE
Establish the measured engineering contextReview logger/pull-down behaviour and refrigeration performance relationships before deciding what the fault is.
Open product step →Run a clearly labelled synthetic cold-storage case through the real HVACR Studio workflow. The POC starts with a freezer room that is not reaching setpoint, then moves through measured context, guided diagnosis, corrective action, retest, documentation and Project continuity.
Demo-data boundary: the values below are synthetic exhibition data, not a customer Project or engineering acceptance record. The troubleshooting engine and public routes are the real product.
At the stall, follow this sequence instead of opening unrelated calculators. Free value comes first; Project context is introduced only when the visitor wants persistent equipment history and controlled reporting.
Review logger/pull-down behaviour and refrigeration performance relationships before deciding what the fault is.
Open product step →The free POC works without login. Move into a Cold Room Project only when equipment identity, history and traceability are needed.
Open product step →Launch the real Basic Issue Finder with the synthetic REFCOLD observation and readings already loaded.
Start this step →Use the same troubleshooting session to record the corrective action instead of treating a suggested cause as completed work.
Open product step →The free flow can create a shareable troubleshooting card; Project mode adds controlled equipment/service reporting and history.
Open product step →Recent free sessions remain on the device; Professional Projects preserve equipment, evidence, actions, retest and reports for future work.
Open product step →“Freezer Room 01 is set to -18 °C but is around -12 °C. What should the engineer check first?”
Use logger/pull-down review and refrigeration diagnostics to establish evidence before diagnosis.
The POC opens Cold Room → room not reaching temperature with the synthetic observation and readings already entered.
For the hero demonstration, confirm the observed airflow/frost clue, then continue through infiltration, refrigeration evidence, load and sensor/setpoint checks.
Demonstrate that suggested causes are not treated as completed work. Enter only the action actually performed and then record the new condition.
Show the free share card, then explain how Professional keeps the same job connected to equipment, evidence, Actions, retest and controlled reports.
Use the first scenario for the full booth story. The other two let a refrigeration visitor immediately choose a familiar problem without changing the product architecture.
Room setpoint is -18 °C, but the observed room condition is about -12 °C and pull-down is slow.
Presenter cue: Use the guided checks to test airflow/icing, infiltration, refrigeration-side evidence, load and sensor/setpoint context instead of jumping straight to refrigerant charge.
Frost returns quickly after defrost and airflow across the evaporator is becoming uneven.
Presenter cue: Walk through defrost sequence, infiltration, fan/airflow and drainage evidence. Keep the result as a ranked troubleshooting trail, not an automatic root-cause declaration.
The condensing/discharge condition is higher than intended and heat rejection needs structured checking.
Presenter cue: Check heat-rejection surface, condenser fan/airflow, entering condition and qualified refrigerant-side evidence without inferring charge from one snapshot.
HVACR Studio should not claim that one temperature, pressure or visual clue proves refrigerant charge, leakage, restriction, compressor condition, food/product release or compliance. The demo is strongest when it shows how observations, checks, action and retest remain separate and traceable.