Percentage of time actual space temperature was within the expected range during evaluated hours. Measures whether the physical outcome is achieved — independent of how the thermostat is configured.
The percentage of time during the analysis period that the actual space temperature was within the expected range for that zone, equipment, and time of day. Unlike setpoint compliance — which measures whether the system is configured correctly — temperature compliance measures whether the physical result is being achieved.
An important distinction: A site can have perfect setpoint compliance and still fail temperature compliance if the equipment cannot maintain the target temperature. Conversely, a site can have poor setpoint compliance but still achieve acceptable temperatures if the equipment overcompensates. Both metrics are needed to get a complete picture. Correct setpoints with poor temperature compliance is the clearest signal of an equipment or capacity issue.
The general approach is to evaluate each interval against the expected temperature range for that zone and time window. Intervals within the defined range are counted as compliant.
Temperature compliance = compliant intervals / evaluated intervals × 100
The denominator is evaluated intervals, not total intervals. Hours outside the defined compliance window are excluded from the calculation entirely.
Not all hours need to be evaluated. The compliance window must be defined per zone and per schedule before the metric is activated. Common examples: a customer-facing retail space may only require compliance during business hours; a 24h operation may require compliance at all hours but with a different range overnight; a storage area may have a wider acceptable range or no compliance requirement. This definition must be documented and agreed upon with the client.
The following are reference ranges only and must be reviewed and validated with each client before being used as compliance targets.
| Zone type | Mode | Reference range (°F) |
|---|---|---|
| Customer-facing retail | Cooling (standard hours) | 68 – 76°F |
| Customer-facing retail | Cooling (high-traffic hours) | 66 – 74°F (1–2°F lower justified by elevated metabolic load) |
| Customer-facing retail | Heating | 68 – 72°F |
| Storage / back-of-house | Any | 60 – 80°F (wider range; setback more aggressive overnight) |
| Office spaces | Cooling | 70 – 76°F (ASHRAE 55) |
| Office spaces | Heating | 68 – 72°F |
Reference ranges only. Calibrate per client, zone type, climate zone, and operational agreement. Portfolio compliance target (default: 85% of sites compliant) to be agreed with each client.
Above-range and below-range deviations have different operational meanings and urgency levels.
Cooling mode: comfort failure — space warmer than expected. Also implies the equipment is working harder than needed → efficiency impact. Highest urgency during business hours.
Heating mode: overconsumption — space warmer than necessary → energy waste.
Cooling mode: overconsumption — equipment cooling more than needed → energy waste and potential comfort issue (too cold).
Heating mode: comfort failure — space colder than expected → occupant dissatisfaction.
Temperature Compliance is one of the four HVAC optimization metrics Keedian tracks. The table below shows how moving this metric impacts each of the four customer value drivers the product is designed to improve. These are the same four levers expressed on every HVAC product page as Expected Outcomes — the metric pages explain the mechanism; the product pages express the magnitude.
| Value driver | Impact strength | How Temperature Compliance moves this lever |
|---|---|---|
| Energy savings | Indirect | Temperature Compliance is the outcome of equipment + controls + setpoint configuration; it is not a direct energy lever on its own. Healthy compliance does create headroom to optimize setpoints and schedules more aggressively for energy without risking comfort. |
| Avoided truck rolls | Direct, strong | Temperature non-compliance is the primary signal that drives comfort complaints and, with them, reactive dispatch. Catching compliance dips before customers complain enables proactive remediation. The compliance trend is also the critical triage input that separates a real comfort failure from a false alarm — avoiding unnecessary truck rolls in both directions. |
| Asset lifespan | Indirect | Non-compliance is the symptom of equipment struggling, not a direct lifespan driver. Acting on compliance protects against the underlying issues (refrigerant, coils, fans, capacity), so it indirectly extends life; the direct lifespan levers are Runtime and Cooling DeltaT. |
| Customer experience | Direct, primary | Temperature Compliance is the CX metric for HVAC. Comfort means temperature in the expected range during occupied hours; this metric measures it directly. It is both the leading indicator (drops precede complaints) and the lagging confirmation of every other lever's success. |
The table below summarizes the principal alarms that fire directly from Temperature Compliance. Each row links to the full operational detail (trigger, preconditions, action plan, human role, linked SOPs) in the SOPs catalog. These are single-metric alarms only — composite FDD that combines multiple metrics with control state and weather context will appear in a future release.
| Alarm | Description | Severity | Tier | AI executes? | Value drivers | SOP |
|---|---|---|---|---|---|---|
| Severe temperature deviation | Space temperature is far outside the expected band — an active comfort failure is in progress. | Urgent | Essential | Hybrid | Customer experience · Avoided truck rolls | Open SOP → |
| Sustained temperature out-of-range | Space temperature has been outside the expected band for longer than the noise / startup tolerance window. | High | Optimized | Hybrid | Customer experience · Avoided truck rolls | Open SOP → |
Roadmap: rolling site-compliance KPI (% of time in compliance over a daily/weekly window) — currently surfaced as a dashboard metric rather than an alarm. Composite alarms in development (multi-metric FDD): capacity vs load mismatch, comfort masked by override (correlation with Setpoint Compliance), early-warning comfort risk (DeltaT degradation predicting future Temperature Compliance dips).
The action plan for each alarm lives on its own SOP page in the SOPs catalog — with the diagnostic steps, human role, value drivers, and escalation criteria specific to that alarm. The list below maps each temperature-derived alarm to its SOP; this page keeps only the cross-alarm items that don't belong to a single SOP (definition errors, sensor placement, capital decisions).
If the configured compliance window or expected range doesn't reflect the site's actual operational hours, traffic patterns, or zone type, every alarm derived from this metric is unreliable. Correct the zone configuration, recalculate affected periods if possible, and document the correction. Validate any change with the client before applying.
If a sensor sits near a supply diffuser or in an unrepresentative location, it will consistently read lower (or higher) than the actual space temperature, biasing every alarm against the site. Escalate internally to the technical team. Do not report the site as non-compliant until the issue is confirmed or ruled out.
If site changes have permanently increased heat gain (expansion, layout change, kitchen install), the current HVAC capacity may no longer be sufficient — this is a capital-expenditure conversation, not a per-SOP operational fix. Document the timeline and any known site changes. Present findings to the client in the MBR with comparison to baseline thermal load.
Per-alarm escalation criteria live in the Escalation block of each SOP in the SOPs catalog. The patterns below are metric-level — they are read from the portfolio view, not from any single alarm firing, and don't belong to a single SOP.
Escalation criteria and communication protocols should be defined as part of the operational agreement with each client. The guidelines below are a general reference and should be adapted to the specific terms, SLAs, and relationship dynamics in place for each account.
Percentage of time actual space temperature was within the expected range during evaluated hours. Measures whether the physical result is achieved, independent of how the thermostat is configured. Correct setpoints with poor temperature compliance is the clearest signal of an equipment or capacity issue. Above-range events during business hours are the highest-urgency scenario. Reviewed monthly in MBR.
SOPs linked to this metric will be documented here. Each SOP will describe the step-by-step operational procedure for a specific scenario identified in the Alarms and Actions sections above.