Off-schedule operation.

Trigger, action plan, and escalation criteria.

Related metric

runtime

Trigger

runtime detected outside schedule_window

Value drivers

Energy savings

Preconditions

Schedule configured and current.

Human role

Secondary — pattern review at cadence.

Action plan

(1) Validate that the schedule is up to date (not a stale corporate policy). (2) Check setpoint at the time of the event — did an override coincide? (3) Auto-revert to the schedule and disable the manual override if controls allow. (4) Flag the site for pattern review if the event recurs.

Escalation

(1) Pattern recurs > 2 events in 30 days at the same site → pattern review at the MBR; check whether the schedule is stale or a policy gap exists. (2) Auto-revert disabled by controls → notify client ops; manual reset required by site staff. (3) Off-schedule runtime concentrates in a daypart with comfort complaints → reclassify as a setpoint-policy issue, not a schedule issue. (4) Schedule out of sync across multiple sites in the same region → flag for corporate policy refresh.

Prevention

(1) Schedule sync routine whenever corporate policy changes — propagate the new schedule to all affected sites in the same cycle. (2) Override allow-list per site — define which roles can override the schedule and for how long; tighten the list when off-schedule events recur. (3) Holiday-calendar refresh at quarterly cadence — stale holiday entries are a common source of off-schedule alarms.