The time an asset takes to return to its configured band after a known disturbance — a prolonged door opening, a controller-exposed defrost, or another recognized load event. Measured against the asset's own baseline and comparable asset types, a recovery that slows or fails is a leading indicator that the asset is losing its ability to hold temperature — weeks before that degradation becomes product loss. It narrows and prioritizes investigation; it is not a definitive compressor, refrigerant, coil, or airflow diagnosis.
The time a refrigeration asset requires to return to its configured operating band after a known disturbance, such as a prolonged door opening, a defrost event exposed by an existing controller, or another recognized load event. It is a predictive, leading-indicator signal about an asset's ability to recover its temperature — distinct from Temperature Compliance, which measures whether the asset is in band, not how well it bounces back.
Recovery is measured only over intervals following a valid, identified disturbance — the metric does not require defrost telemetry to work, and it does not attempt a recovery calculation when no disturbance can be recognized, so an ordinary in-band period is never scored as a recovery event.
For each recovery event the metric tracks recovery duration (time back to band), recovery slope (how steeply the asset pulls the temperature down), failed recovery (the asset does not return within the approved maximum window), and degradation over time (recovery getting slower across repeated events).
Recovery is compared against the asset's own baseline and comparable asset types — a walk-in freezer and a refrigerated multideck recover on different curves, so the metric benchmarks like against like rather than against a single fleet number.
The metric is a leading indicator that narrows investigation and prioritizes intervention. A degrading recovery curve is consistent with several causes; the metric does not present itself as a definitive compressor, refrigerant, coil, or airflow diagnosis, and any dispatch correlates temperature, door, controller, runtime, and peer-asset evidence first.
| Range | Classification | Interpretation |
|---|---|---|
| Recovery duration and slope near the asset's approved baseline | Expected — recovering normally | The asset returns to band after a disturbance the way it always has; no action. |
| Recovery materially slower than the asset's baseline for repeated events | Recovery degrading — monitor | The asset is losing its ability to recover; prioritize investigation and correlate other evidence before the degradation becomes an excursion. |
| Asset fails to return to band within the approved maximum recovery window | Failed recovery — investigate | The asset cannot recover after the disturbance; correlate temperature, door, controller, runtime, and peer-asset evidence and work it before product is at risk. |
Reference behavior only, expressed relative to each asset's own approved baseline and comparable asset types — not fixed absolute minutes. The maximum recovery window, the degradation margin, and what counts as a valid disturbance are configured per asset and product category before reporting.
There is no universal recovery time — an acceptable recovery curve depends on the asset type, its product category, and the disturbance. The target is the asset's own approved baseline; the metric reports slowing or failed recovery against that baseline and against comparable asset types, not against a fixed minute count.
The table below shows how moving Refrigeration Temperature Recovery impacts each customer value driver the product is designed to improve — the metric page explains the mechanism; the product pages express the magnitude.
| Value driver | Impact strength | How Refrigeration Temperature Recovery moves this lever |
|---|---|---|
| Product loss prevention | Direct, primary | An asset whose recovery is slowing is on its way to holding temperature poorly under load — the condition that produces spoiled product. Catching the degrading recovery curve weeks before it becomes a sustained excursion turns a future write-off into a planned intervention, protecting the product-loss exposure Chedraui carried at roughly $5M a year. |
| Avoided truck rolls | Direct | Because recovery narrows the investigation and correlates door, controller, runtime, and peer-asset evidence before a dispatch, it prioritizes the assets that genuinely need a visit and gives the technician a scoped starting point — reducing unnecessary or incorrectly scoped dispatches. Chedraui saw roughly 50% faster work-order handling on the same operating model; the recovery-specific magnitude here is expected (pending validation). |
| Asset lifespan | Indirect, leading indicator | A recovery curve that degrades steadily is an early signature of an asset working its way toward a fault. Flagging it as a scoped item lets the customer plan a repair or replacement before the asset fails outright, extending its useful life. The metric prioritizes intervention; it does not by itself diagnose the mechanical cause. |
The table below summarizes the alarms that fire directly from Refrigeration Temperature Recovery. Each row links to the full operational detail (trigger, preconditions, action plan, human role, escalation, prevention) in the SOPs catalog.
| Alarm | Description | Severity | Tier | AI executes? | Value drivers | SOP |
|---|---|---|---|---|---|---|
| Slow temperature recovery | An asset's recovery time or recovery slope degrades materially against its approved baseline for repeated events after a recognized disturbance. A leading indicator worked with correlated evidence — not a definitive mechanical diagnosis — to prioritize intervention before degradation becomes product loss. | Medium | Optimized | Hybrid | Product loss prevention · Avoided truck rolls · Asset lifespan | Open SOP → |
| Failed temperature recovery | An asset does not return to its configured band within the approved maximum recovery window after a recognized disturbance. Worked with correlated temperature, door, controller, runtime, and peer-asset evidence before recommending dispatch, and treated as a product-risk event when temperature is already out of band. | High | Optimized | Hybrid | Product loss prevention · Avoided truck rolls · Customer experience | Open SOP → |
More alarms in development (single-metric): a recovery-degradation trend that ranks assets by how fast their recovery curve is slowing, and a disturbance-classifier refinement that separates defrost recovery from door-load recovery. Composite alarms that combine recovery with temperature compliance and door exposure to attribute a degrading curve to a specific disturbance will appear in a future release.
The action plan for each alarm lives on its own SOP page in the SOPs catalog — with the diagnostic steps, human role, value drivers, escalation, and prevention specific to that alarm. The list below maps each alarm to its SOP.
A slowing or failed recovery is a leading indicator, not a diagnosis. Before recommending a dispatch, correlate the available temperature, door, controller, runtime, and peer-asset evidence — a long recovery that followed a prolonged door opening or a defrost is expected, while a degrading recovery with no disturbance explanation is the genuine signal. Do not assert a compressor, refrigerant, coil, or airflow cause the metric cannot confirm.
Recovery is only meaningful after a recognized disturbance and against a valid baseline. Confirm the disturbance is real (a prolonged door opening, a controller-exposed defrost, another recognized load event) and that the asset's baseline and comparable-asset benchmark are configured before scoring recovery, so an ordinary in-band period or an unconfigured asset does not produce a false recovery finding.
When an asset's recovery degrades against baseline for repeated events, originate a ticket ahead of a sustained excursion rather than waiting for a temperature breach. Prioritize the asset for intervention using the cross-site and cross-asset benchmark, and scope the ticket with the correlated evidence so the field visit is targeted.
Per-alarm escalation criteria live in the Escalation block of each SOP in the SOPs catalog. The patterns below are metric-level — read from the portfolio view, not from any single alarm firing.