- Value drivers
-
Customer experience
Energy savings
Avoided truck rolls
- Preconditions
- Ultrasite access for the Chedraui site; Corrigo access for WO tracking; the Chedraui OC is reachable for approval; complaint is documented in the Keedian ticket.
- Human role
- BSS (refrigeration team) diagnoses the unit in Ultrasite, calls the Chedraui OC for approval before any override, applies the timed override exactly as approved, then clears it at end-of-window.
- Action plan
-
(1) Create or update a Keedian ticket: store ID, caller name/role, areas affected, complaint (too hot / too cold); connect to the site in Ultrasite; record current zone temps and setpoints. Store staff alone is not sufficient approval.
(2) Diagnose respective units: confirm Status Online; check Outside / Space / Supply temps; check Cool1/2/3 and Heat 1/2/3 relays. Standard setpoints are 68°F heat / 72°F cool.
(3) Use the decision steps — space below heat SP with heat relays OFF → heat failure → HVAC WO in Corrigo; space above cool SP with cool relays OFF → cooling failure → HVAC WO; relays ON but space not moving toward setpoint → check Supply temp (Supply not colder than space/outside in a hot store → mechanical cooling issue → HVAC WO; Supply not warmer than space/outside in a cold store → mechanical heating issue → HVAC WO).
(4) Only consider a temporary override after mechanical / programming issues are ruled out and the store still reports comfort issues.
(5) Call the Chedraui OC; explain the diagnosis and proposed override; obtain explicit approval for new setpoints, start time, and duration; ask how high/low and how long.
(6) In Ultrasite, right-click the setpoint → Override → set the values exactly as approved (Timed type, with the approved hours).
(7) Document in both Corrigo (create a non-dispatched WO and DON'T SEND IT) and the Keedian ticket: requester, approver, what was approved, how long, how much, what changed.
(8) When the approved time expires, clear the override and return to 68°F/72°F; update both tickets; cancel the non-dispatched Corrigo WO.
- Escalation
-
(1) Unit Offline → check Corrigo for open/pending WOs for the asset; if none, create a WO for the unit and advise the MOD this is the cause (no setpoint change needed).
(2) Setpoint sensor readings look implausible (-100°F / 200°F) → suspect bad sensor → create an urgent WO for sensor replacement.
(3) Vent location is forcing comfort drift (warm air pooling at high vents during heat call) → flag to facilities; explain wait time to store.
- Author
- David Dillard
- Tools
-
Ultrasite
Corrigo
Keedian Platform
Phone (Chedraui OC)
- Roles
-
BSS — Refrigeration team
Chedraui Operations Center (approver)
Purpose
Use this SOP when Chedraui store personnel report that an area feels too hot or too cold and request an HVAC setpoint change from the standard 68°F heating / 72°F cooling settings. Distinguish true mechanical / programming issues from comfort-only requests, obtain the required Chedraui OC approval before any override, and fully document decisions in Corrigo and Keedian.
Troubleshooting
Sensor location is distorting the reading.
Cause — Space-temp sensor placed too high / too low / near ovens or freezers.
Solution. Move the sensor to a more representative location — that alone often solves the issue without replacement.
Slow warm-up despite heat call.
Cause — Vents are very high; warm air accumulates near the ceiling before reaching the space.
Solution. Long-term fix is to relocate the vents (often impractical). Explain the wait to the store; consider supplemental measures.
Reading shows -100°F or 200°F with sudden change in the logs.
Cause — Failed sensor — drives permanent heat or cool calls.
Solution. Create an urgent WO for sensor replacement; inform the store of the issue.