The percentage of time each lighting circuit's on/off state matched the agreed schedule for its space. The primary discipline indicator for lighting — unlike HVAC, where comfort can excuse non-compliance, lighting run against schedule is almost always pure waste.
The percentage of time each lighting circuit's on/off state matched the agreed schedule for its space, averaged across the spaces in scope for the period. At portfolio level the metric reframes as the percentage of sites whose schedule compliance meets the per-site threshold. It is the primary discipline indicator for lighting: lights left on overnight, exterior lights running mid-day, or parking lights on during daylight are each a schedule violation. Unlike HVAC, where comfort can partially excuse non-compliance, lighting non-compliance is almost always pure waste.
The metric is the share of sampled intervals where the circuit's actual on/off state matched its scheduled state, with a short boundary tolerance (a few minutes, configurable) so a circuit turning off slightly late is not flagged.
compliance_circuit = matching intervals / total intervals × 100.
compliance_space = average across the circuits in that space.
compliance_site = average across spaces after the in-scope filter is applied.
The metric only exists where a schedule is configured and mapped to the circuit or space. Circuits with no schedule are excluded from the average — they are not counted as non-compliant.
| Range | Classification | Interpretation |
|---|---|---|
| ≥ 90% per circuit | Compliant | Circuit tracks its schedule within tolerance; no action required. Include in MBR trend. |
| 75 – 90% per circuit | Watch zone | Flag for monitoring; investigate if sustained over two consecutive periods. Often an early sign of schedule drift or a stale template. |
| < 75% per circuit | Non-compliant | Diagnose per the action guide: auto-revert first, then decide template fix vs local control fault. |
Reference thresholds only — examples to calibrate per client, site, space, and circuit. Targets are configurable: a common starting point is ≥ 90% per circuit at site level and ≥ 85% of stores compliant at portfolio level, to be agreed with each client. Photocell-controlled spaces (exterior, parking) are a special case — their state is driven by ambient light, not the clock; until ambient-light integration ships, exclude them or give them a wide-tolerance schedule.
The target percentage of stores compliant (reference: 85% of stores, with ≥ 90% per circuit at site level) should be defined and agreed with each client. These defaults are starting points only and are configurable per client, site, space, and circuit.
The table below shows how moving Schedule 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 Schedule Compliance moves this lever |
|---|---|---|
| Energy savings | Direct, primary | Off-schedule lighting is energy spent with no operational benefit — sales lighting on after close, exterior or parking lights on at mid-day, a zone left lit overnight. Because lighting non-compliance is almost always pure waste, restoring schedule compliance is the most direct lever to cut lighting kWh. Lighting is commandable, so the platform reverts the circuit to its scheduled state automatically rather than waiting for a site visit. |
| Sustainability | Indirect | Eliminated off-schedule run-hours convert directly into avoided energy, and avoided energy converts into lower CO2e. Schedule Compliance is the cleanest evidence that the lighting reductions are real and sustained — useful when a client reports against an emissions or efficiency commitment. |
The table below summarizes the alarms that fire directly from Schedule 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 |
|---|---|---|---|---|---|---|
| Off-schedule lighting | A lighting circuit's on/off state is against its agreed schedule — exterior or parking lights on at mid-day, sales lighting on after close, or a zone dark during operating hours. | Medium | Essential | Yes | Energy savings | Open SOP → |
Single alarm today: Off-schedule lighting (auto-revert first, then template fix vs local control fault). Roadmap (single-metric): schedule-drift trend per space type. Composite alarms in development (multi-metric): photocell/ambient-light integration so exterior and parking spaces are scored on \"on when ambient < X lux\" instead of being excluded.
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.
Before dispatching anyone, separate the two failure modes. If the SAME space type is below target across MANY sites, the template schedule is wrong for that space — for example a store open until 23:00 with lighting scheduled to 22:00. Fix the schedule centrally and propagate it to every affected space; do not dispatch a technician to each site. If compliance is low at ONE site only, treat it as a local control fault (manual switch left on, photocell drift, an unsynchronized time clock, a stuck contactor) and scope a maintenance check. Reading the portfolio view first prevents a template error from being mistaken for dozens of independent field problems.
Exterior and parking lighting is driven by ambient light, not the clock, so a clock-based schedule will flag normal daylight switching as non-compliance. Until ambient-light integration ships, exclude these spaces from the compliance average or give them a wide-tolerance schedule, and label them clearly so they are not read as failures in the MBR. When integration is available, the schedule for these spaces should encode "on when ambient < X lux" rather than a fixed time.
If compliance values look implausible — a circuit with no schedule mapped being counted as non-compliant, or a gap in the on/off sampling read as off-schedule — escalate internally before treating any alarm as real. Confirm the circuit has a schedule configured and mapped (unmapped circuits are excluded by design, not flagged). Do not report the affected site as non-compliant in the MBR until the gap is resolved; document the period affected so it can be excluded or recalculated.
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.