Productization
← Back to SOPs catalog
Keedian operations · Standard procedure

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.

01 Detail

Trigger, action plan, and escalation criteria.

optimization_metric refrigeration medium optimized tier AI: hybrid
Related metric
refrigeration_temperature_recovery
Trigger
recovery_duration > baseline_recovery + degradation_margin (or recovery_slope < baseline_slope), repeated events after a valid disturbance
Value drivers
Product loss prevention Avoided truck rolls Asset lifespan
Preconditions
A valid disturbance can be identified (prolonged door opening, controller-exposed defrost, or another recognized load event); the asset's recovery baseline and comparable-asset benchmark are configured; temperature, door, controller, and runtime feeds validated.
Human role
Primary for the intervention decision and dispatch scoping; secondary review after AI on evidence correlation.
Action plan
(1) Confirm a valid disturbance and a configured baseline — recovery is scored only after a recognized disturbance and against the asset's own baseline and comparable asset types. (2) Confirm the degradation is real and repeated, not a single long recovery that followed an unusually large disturbance. (3) Correlate the evidence before calling it a fault — temperature, door, controller, runtime, and peer-asset data; a long recovery explained by a prolonged door opening or defrost is expected. (4) Do not assert a compressor, refrigerant, coil, or airflow cause the metric cannot confirm — the recovery curve narrows investigation, it does not diagnose. (5) Originate a predictive ticket ahead of a sustained excursion when recovery degrades against baseline for repeated events, prioritized by the cross-asset benchmark. (6) Scope any dispatch with the correlated evidence so the field visit starts targeted; capture closure evidence with root cause.
Escalation
(1) Recovery degradation co-occurs with a sustained temperature-compliance breach on the same asset → treat as a product-risk event in progress, not a leading indicator; escalate out of cycle. (2) An asset's recovery degrades steadily across multiple months → maintenance or replacement candidate, prioritized by the cross-asset benchmark at the MBR. (3) An asset type recovers more slowly across several sites → systemic load, layout, or maintenance-cadence issue worth a portfolio review. (4) A disturbance-detection or baseline fault makes recovery unreliable across many assets → pause recovery reporting until the configuration is reconciled.
Prevention
(1) Configure what counts as a valid disturbance, the degradation margin, and each asset's baseline and comparable-asset benchmark before activating the metric. (2) Trend recovery next to temperature compliance and door exposure so a recovery finding is read alongside its likely disturbance. (3) Maintain a per-asset recovery log so a slow degradation is visible over months before it becomes product loss.