The share of valid temperature readings in the period that fall inside each asset's configured operating band. It is the earliest signal that a case or chamber is drifting toward product loss. Bands are set per asset and product category — there is no universal cooler or freezer threshold — and chambers and display cases roll up separately, refrigerated and frozen. Current temperature and period compliance are kept distinct: a case can read in-band right now and still have spent the afternoon out of band.
The percentage of valid temperature readings during the evaluated period that fall within the configured operating band for each refrigeration asset. It is a product-protection signal about whether an asset is holding the temperature its product category requires, distinct from the asset's instantaneous reading — a case can be in-band at the moment it is read and still have spent hours out of band earlier in the day.
Per asset, compliance over the period is count(valid readings in band) / count(valid readings) × 100. The band is configured per asset and product category; no universal cooler or freezer threshold is hard-coded into the metric.
Invalid, missing, stale, or explicitly suppressed sensor intervals are excluded from both the numerator and the denominator — a communications gap or a suppressed maintenance window is not scored as compliant and not scored as a breach.
Rollups are kept separate by asset type and product category: chambers (walk-in coolers and freezers) and display cases (refrigerated and frozen) each roll up on their own, so a strong chamber score cannot mask a drifting case line, and refrigerated and frozen bands are never averaged together.
Open multideck cases may participate in temperature compliance even where they have no door telemetry — compliance is a temperature measurement and does not depend on a door sensor.
| Range | Classification | Interpretation |
|---|---|---|
| Compliance ≥ 99% of valid readings in band | Expected — protecting product | The asset holds its configured band; product in that case or chamber is at the temperature its category requires. |
| Compliance 95 – 99%, or short repeated excursions | Drifting — monitor | The asset leaves its band often enough to shorten shelf life or approach a product-safety limit; scope the asset before an excursion becomes a loss. |
| Compliance below 95%, or a sustained out-of-band period | Out of band — investigate | The asset is regularly outside the temperature its product requires; correlate with door activity and peer assets and work the excursion before product is lost. |
Reference bands only. The operating band, the compliance floor, and the persistence window are configured per asset and product category before reporting — a frozen chamber, a refrigerated display case, and a prepared-food case each hold different targets, and none of them is a universal catalog constant.
The per-asset target is to hold the configured band for the great majority of valid readings, with the exact floor agreed per asset and product category. The metric reports against each asset's own configured band, not against a single fleet-wide temperature.
The table below shows how moving Refrigeration Temperature Compliance 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 Compliance moves this lever |
|---|---|---|
| Product loss prevention | Direct, primary | Refrigeration is grocery's highest product-loss-risk asset class — at Chedraui, refrigeration-related product loss reached roughly $5M a year. Temperature compliance is the earliest fleet-wide signal that a case or chamber is drifting toward that loss, turning a spoiled-product write-off into a scoped intervention while the product is still good. |
| Customer experience | Indirect | Product held in its band stays available, safe, fresh, and at the serving temperature customers expect. Catching drift before it reaches the shelf protects product availability and quality — an indirect commercial outcome, not a direct sales-uplift claim. |
| Energy savings | Indirect, leading indicator | An asset that struggles to hold its band while the store is otherwise normal is often working harder than it should — a door-seal, load, or airflow issue. Surfacing the compliance drift points to the inefficient asset; the energy magnitude is expected (pending validation). |
The table below summarizes the alarms that fire directly from Refrigeration Temperature Compliance. 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 |
|---|---|---|---|---|---|---|
| High temperature excursion | A refrigeration asset holds above its configured upper band for longer than its configured persistence window — a product-risk excursion that must be validated, triaged, and, where safety may be affected, met with a product-check recommendation. | High | Essential | Hybrid | Product loss prevention · Customer experience · Avoided truck rolls | Open SOP → |
| Low temperature excursion | A refrigeration asset holds below its configured lower band for longer than its configured persistence window. The SOP distinguishes excessive cooling or control failure, freezing risk for refrigerated product, normal freezer behavior inside its own band, and invalid or drifting sensor readings. | Medium | Essential | Hybrid | Product loss prevention · Energy savings · Avoided truck rolls | Open SOP → |
More alarms in development (single-metric): a slow-drift watch that flags an asset trending toward its band edge before it breaches, and a category-level pattern alert for a case line drifting together across a site. Composite alarms that combine temperature compliance with door exposure and recovery to separate a load event from a mechanical fault 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 temperature reading can be wrong before it is out of band — a failed or drifting probe, a stale feed, or a reading taken during a suppressed maintenance window. Confirm sensor health and exclude invalid, missing, stale, or suppressed intervals before reporting an asset as out of compliance, so a data-quality fault is not worked as a product-risk excursion.
The operating band, the compliance floor, and the persistence window depend on the asset and what it holds — a frozen chamber, a refrigerated multideck, and a prepared-food case are different targets. Confirm the band and category mapping for each asset before activating compliance reporting, so an asset is not scored against a band that does not fit its product.
A sustained excursion above the safe limit for the product category is a food-safety exposure, not only an efficiency reading. Recommend a product check to the store when a high excursion crosses the category's safety threshold for its persistence window, and record the outcome. The safety limits and persistence windows are configuration inputs agreed per category, not universal catalog constants.
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.