The percentage of time circuits were actually on, averaged across the spaces in scope. Where Schedule Compliance asks whether the lights followed the rule, utilization asks how much they were actually used — most useful for spaces with no fixed schedule, where it exposes a stuck sensor or a failing circuit.
The percentage of time lighting circuits were on, averaged across the spaces in scope. At portfolio level, the percentage of sites whose utilization average falls within the expected per-space band. Utilization answers how much the lights were actually used — distinct from Schedule Compliance, which asks whether the lights followed the rule. A circuit can be fully schedule-compliant yet show low utilization because the schedule only calls for a few hours a day. The metric is most useful for spaces with no fixed schedule (parking, back of house tied to occupancy or photocell), where there is no clock to compare against.
utilization_circuit = intervals where state == ON / total intervals × 100
utilization_space = average of utilization_circuit across the circuits in the space
utilization_site = average of utilization_space across the spaces at the site
Portfolio: a site is in_band when band_low ≤ utilization_site ≤ band_high; the card shows count(sites in band) / count(sites)
Unit: %. Requires per-circuit on/off state at high frequency, and an expected utilization band defined per space
| Range | Classification | Interpretation |
|---|---|---|
| Sales floor 70–90% | Expected band (example) | Floor lit through operating hours; below band suggests a failing circuit or breaker trips, above band suggests after-hours operation |
| Parking 80–100% | Expected band (example) | Sensor- or photocell-driven; very high is normal for dusk-to-dawn, a sustained drop points to a failing circuit or clustering lamp failures |
| Back of house 40–70% | Expected band (example) | Occupancy-driven; too high signals a stuck or miscalibrated occupancy sensor, too low signals an intermittently failing circuit |
| Bathrooms 30–60% | Expected band (example) | Occupancy-driven; out-of-band high points to a stuck sensor, out-of-band low to an intermittent circuit fault |
Bands are examples only — calibrate per client, site, and space before activating compliance reporting. Utilization is a flat percentage, not per-hour compliance: a circuit running 12 h/day at the right hours and one running 12 h/day at the wrong hours score identical utilization. Only Schedule Compliance distinguishes them.
The target percentage of sites in band (reference: 85%) should be defined and agreed with each client. This default is a starting point only, and the per-space bands it is measured against are configured per client, site, and space.
The table below shows how moving Utilization 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 Utilization moves this lever |
|---|---|---|
| Energy savings | Direct | On-hours are the dominant driver of lighting kWh. A circuit running well above its expected band — a sales floor lit after close, a sensor-controlled space stuck on — is direct, recoverable energy waste. Because lighting is commandable, catching out-of-band high utilization lets Keedian revert the circuit to schedule and confirm the correction, reducing spend rather than just reporting it. |
| Avoided truck rolls | Indirect, leading indicator | Out-of-band low utilization surfaces an intermittently failing circuit, breaker trips, or clustering lamp and ballast failures before they become a dark-space complaint. Acting on the early signal lets a maintenance check be scoped and batched into a planned visit instead of an emergency dispatch, and groups failing lamps into a single relamp rather than repeat lamp-out calls. |
The table below summarizes the alarms that fire directly from Utilization. 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 |
|---|---|---|---|---|---|---|
| Utilization out of band | A lighting circuit's on-fraction falls outside the expected band for its space — too high for a sensor-controlled area, or too low for a space that should be lit. | Medium | Essential | Hybrid | Energy savings · Avoided truck rolls | Open SOP → |
Roadmap (single-metric): utilization trend degradation, low-utilization clustering tied to lamp-life burn-hour tracking. Composite alarms in development (multi-metric): utilization correlated with Schedule Compliance to separate sensor and circuit faults from schedule faults, and ambient-light integration to bring photocell-controlled spaces into band.
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.
Utilization is the primary signal for parking and back-of-house spaces driven by occupancy or photocell, where there is no schedule to check. Out-of-band high on these spaces points to a stuck occupancy sensor or miscalibrated detection — verify and recalibrate or replace the sensor, do not change a schedule that does not exist. Out-of-band low points to an intermittently failing circuit, breaker trips, or clustering lamp failures — scope a maintenance check. The per-circuit action plan lives in the Utilization out of band SOP in the SOPs catalog.
Read the failure mode from the portfolio view before acting. When the same space type is out of band across many sites, the expected band — or the template behind it — is wrong for that space type; correct it centrally rather than dispatching a technician to each site. When one site is out of band on its own, treat it as a local sensor or circuit fault and dispatch a maintenance check. Confirming this split first prevents a fleet of unnecessary truck rolls.
Exterior and parking circuits driven by a photocell follow ambient light, not the clock or a fixed occupancy pattern, so their on-fraction varies with daylight and season. Exclude these spaces from utilization compliance, or set a wide tolerance band, until ambient-light integration ships — otherwise normal dusk-to-dawn switching reads as out of band. Document any space treated this way so it is interpreted correctly in the MBR.
If per-circuit on/off values look implausible or contradict the platform-layer comms-health signal, escalate internally to the technical team before treating any out-of-band reading as real. Do not report the affected site as out of band in the MBR until the data issue is resolved. Document the suspected problem and the period affected so it can be excluded or corrected in the compliance calculation.
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.