Consumption step-change.

Daily or monthly consumption steps up against the site's own trailing baseline with no known operational change.

01 Detail

Trigger, action plan, and escalation criteria.

optimization_metric energy medium essential tier AI: hybrid

Related metric: energy_consumption
Trigger: period_kwh vs trailing_baseline up > threshold (no known change)
Value drivers: Energy savings Avoided truck rolls
Preconditions: Trailing consumption baseline per site; bill for reconciliation.
Human role: Validates the anomaly and scopes the walkthrough.
Action plan: (1) Flag the step-change vs the site's same-day-of-week / same-month baseline (un-normalized — flag, don't auto-attribute). (2) Walkthrough scope: a propped door, a load left on, a newly-added load, or equipment failed into continuous run. (3) Reconcile metered kWh against the bill — a divergence can be a CT-ratio/multiplier or billing error worth recovering. (4) Guide the site to the controllable cause; dispatch only if equipment is implicated.
Escalation: (1) No controllable cause + a rising compressor signature → scheduled equipment visit before product/comfort loss. (2) Meter-vs-bill divergence beyond tolerance → open a billing-recovery review with the customer.
Prevention: (1) Monthly baseline refresh when a site changes hours, area, or equipment. (2) Standing meter-vs-bill reconciliation each billing cycle.