Keedian operations · Standard procedure

Abnormal post-defrost behavior.

After a verified defrost and past its configured suppression window, the case does not settle back into its band as expected. Defrost Performance flags the abnormal post-defrost behavior; the recovery curve itself is owned by Temperature Recovery, which this alarm correlates to rather than duplicates.

01 Detail

Trigger, action plan, and escalation criteria.

optimization_metric refrigeration medium managed tier AI: hybrid

Related metric: refrigeration_defrost_cycle_performance
Trigger: case fails to settle into band after a verified defrost and past the configured suppression window (correlated with temperature recovery)
Value drivers: Product loss prevention Energy savings Asset lifespan
Preconditions: A verified defrost event with start/end evidence; configured Delay-After-Defrost suppression window; case temperature feed and refrigeration_temperature_recovery available for correlation.
Human role: Secondary review after AI validation; primary when a dispatch is required.
Action plan: (1) Confirm a verified defrost occurred and the suppression window has closed before evaluating. (2) Correlate with refrigeration_temperature_recovery — do not recompute the recovery curve here; use it to judge whether recovery is abnormal. (3) Distinguish a defrost-execution cause (owned here) from a broader recovery/hardware cause (owned by Temperature Recovery). (4) Route to the appropriate follow-up: a defrost-timing correction remotely, or a dispatch where recovery points to hardware.
Escalation: (1) Abnormal recovery that keeps the case out of band → escalate on the temperature-recovery path as a product-risk excursion. (2) Repeated abnormal recoveries tied to defrost on the same case → controls/hardware review candidate.
Prevention: (1) Commission the suppression window per case so post-defrost evaluation starts at the right moment. (2) Keep defrost and recovery correlated per case to separate a defrost-execution cause from a recovery cause.