- Related metric
runtime- Trigger
runtime_hours_per_day > expected_range_max (sustained)- Value drivers
-
Energy savings
Asset lifespan
- Preconditions
- Site schedule + expected runtime range for the site profile.
- Human role
- Secondary review after AI; Primary when a dispatch is required.
- Action plan
-
(1) Check the current setpoint against the corporate policy — if overridden, auto-revert.
(2) Cross-check the schedule (is runtime concentrated within the operating window?).
(3) Cross-check Temperature Compliance — if the unit is struggling to hold setpoint, this is a capacity issue, not behavioral.
(4) If no controllable cause is found, schedule a diagnostic visit scoped to filter, refrigerant, or coil cleaning.
- Escalation
-
(1) Override pattern recurs at the same site → flag for client conversation at the MBR (staff training or policy gap suspected).
(2) Capacity-driven excessive runtime confirmed via Cooling ΔT trend → dispatch within SLA with diagnostic scope.
(3) Excessive runtime co-occurs with a Temperature Compliance failure → comfort risk; out-of-cycle notification to client ops.
(4) Pattern persists for 2+ consecutive months without a resolution path → escalate to client facilities lead.
- Prevention
-
(1) Annual diagnostic visit cadence for sites in the upper half of the expected runtime range — catch filter, refrigerant, and coil issues before they become capacity-driven excessive runtime.
(2) Override-pattern monitoring per site at monthly cadence — reinforce setpoint policy with store managers before the override becomes habitual.
(3) Capacity baseline refresh when a site adds square footage, equipment, or extended hours — outdated baselines drive false-positive runtime alarms.