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.

01 Detail

Trigger, action plan, and escalation criteria.

optimization_metric lighting medium essential tier AI: yes

Related metric: schedule_compliance
Trigger: actual_state != scheduled_state beyond boundary tolerance (sustained)
Value drivers: Energy savings
Preconditions: Schedule configured and mapped to the circuit/space; circuit on/off state sampled every 1-5 min.
Human role: Secondary — investigates local control when auto-revert does not hold or the pattern recurs.
Action plan: (1) Confirm the schedule is current and correctly mapped to the space (not a stale template). (2) Auto-revert the circuit to its scheduled state and clear the manual override where controls allow — lighting is commandable. (3) If auto-revert does not hold, treat it as a local control fault (manual switch, stuck contactor, photocell drift, unsynced time clock) and scope a maintenance check. (4) Flag the circuit for pattern review if the event recurs.
Escalation: (1) The same space shows low compliance across many sites -> the template schedule is wrong for that space type; refresh it centrally rather than dispatching. (2) Low compliance at one site only -> a local control issue; scope a maintenance check (switch, contactor, photocell, time clock). (3) Auto-revert blocked by local controls -> notify site ops; a manual reset is required.
Prevention: (1) Schedule sync routine whenever store hours or corporate policy change — propagate to every affected space in the same cycle. (2) Exclude or widen tolerance on photocell-controlled spaces (exterior, parking) until ambient-light integration ships, so daylight-driven switching is not flagged as non-compliance.