Total active energy the site draws, by interval and billing period, trended against the site's own history and reconciled to the utility bill. The base signal for spend — surfaces consumption creep and meter-vs-bill mismatches before they show up as a higher invoice.
Total active energy the site draws (kWh), by interval and billing period, trended against the site's own history and reconciled to the utility bill. It is the base spend signal for the account — the meter telemetry on one side, the invoice on the other.
The calculation method depends on the data available for each client and site. The core signal is active energy (kWh) from the main service meter, summed per interval (typically 15-minute or hourly) into a daily and monthly total.
Energy Intelligence reads the meter — it does not command it. The metric works from two sources and two sources only: the meter telemetry and the utility bill. Metered kWh is reconciled against the billed kWh each cycle; a divergence beyond tolerance points to a CT-ratio or multiplier error, a billing mistake worth recovering, or a metering gap.
Each period is trended against the site's own baseline — same day-of-week, same month — never against an invented cross-customer benchmark. V1 does not weather- or occupancy-normalize, so a step-change or an elevated overnight floor is flagged for a walkthrough, not auto-attributed to a cause.
The off-hours floor — consumption while the store is closed — is computed as the overnight minimum draw and is the single richest no-capex savings target, because anything burning at 3am with the doors locked is, by definition, waste. The exact thresholds depend on the site's hours, area, equipment mix, and tariff.
| Range | Classification | Interpretation |
|---|---|---|
| At or below the site's own baseline | Expected | Consumption tracks the store's historical profile for the same day-of-week / month; meter reconciles to the bill |
| 5 – 15% above baseline (sustained) | Consumption creep — monitor | A drift worth a walkthrough: a load left on, a propped door, a schedule that slipped, or early equipment degradation |
| Greater than 15% above baseline (no known change) | Step-change — flag for walkthrough | A discrete jump with no merchandising or hours change; scope a site walkthrough before it shows up as a higher invoice |
| Off-hours floor above the expected overnight minimum | Off-hours waste — highest savings target | Energy burned while the store should be idle: lighting/signage timeclock, HVAC night setback, or a case stuck in continuous run |
| Above the client-defined consumption ceiling | Threshold breach — client-defined cap exceeded | Consumption is over the absolute kWh ceiling the client set (a budgeted or contracted cap), independent of baseline drift; confirm the breach and walk the cause with the site |
| Metered kWh vs billed kWh diverges beyond tolerance | Meter-vs-bill mismatch — reconcile | Possible CT-ratio / multiplier error or billing mistake; open a billing-recovery review with the customer |
Reference ranges only — calibrate per client based on operating hours, store area, equipment mix, and tariff before activating compliance reporting. A 24/7 convenience store and a bank branch that closes at 2pm have entirely different expected profiles and off-hours floors.
There is no universal compliance percentage for consumption — the target is defined per client. A common framing is the share of sites whose period consumption and off-hours floor stay within the agreed band around their own baseline (a reference starting point of 85% of sites in-band), reviewed and agreed with each client before activating reporting.
The table below shows how moving Energy consumption 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 Energy consumption moves this lever |
|---|---|---|
| Energy savings | Direct, primary | Consumption is the base signal for spend. Catching consumption creep and an elevated off-hours floor — the load left on overnight, the timeclock that slipped, the case stuck in continuous run — is the most direct no-capex lever to cut the energy bill. Reconciling metered kWh to the invoice also recovers billing and CT-ratio errors. Anchored in 7-Eleven outcomes ($5M energy savings); per-site magnitude is expected (pending validation). |
| Avoided truck rolls | Indirect, leading indicator | A consumption step-change with no operational explanation is often equipment failing into continuous run. Flagging it for a scoped walkthrough — rather than waiting for a comfort or product-loss complaint — turns what would have been an emergency dispatch into a planned, correctly-scoped visit. Where the site is sub-metered, the residual draw is attributed to the exact circuit before anyone is sent out. |
| Sustainability | Direct | Every kWh removed from the off-hours floor or from consumption creep is a direct CO2e reduction. Because the off-hours floor is the richest savings target, it is also the cleanest sustainability lever — cutting energy the store was never using productively in the first place. |
The table below summarizes the alarms that fire directly from Energy consumption. 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-hours consumption above floor | Closed/unoccupied-hours consumption sits above the store's expected overnight floor — energy burned while the site should be idle. | Medium | Essential | Hybrid | Energy savings · Sustainability | Open SOP → |
| Consumption step-change | Daily or monthly consumption steps up against the site's own trailing baseline with no known operational change. | Medium | Essential | Hybrid | Energy savings · Avoided truck rolls | Open SOP → |
| Consumption above defined threshold | Period or interval consumption exceeds a client-defined absolute ceiling (a budgeted or contracted kWh cap), independent of the site's own baseline drift — the customer's own line in the sand for 'too much energy'. | Medium | Essential | Hybrid | Energy savings · Sustainability | Open SOP → |
More alarms in development (single-source, meter + bill): baseload-ratio drift watch and a meter-vs-bill reconciliation alarm. Submetering and power-quality alarms (per-circuit step-change, service-voltage out-of-band, power-factor penalty) are the Optimized differentiator and require submetering / power-quality metering. Composite, multi-signal attribution that combines consumption with weather and occupancy context will appear in a future release.
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.
Every consumption finding rests on two sources: the meter telemetry and the utility bill. If metered kWh and billed kWh diverge beyond tolerance, treat the data as suspect before treating any alarm as real — the cause may be a CT-ratio or multiplier error, a billing mistake worth recovering, or a metering gap. Reconcile first; do not report the site against its consumption band, and do not scope a walkthrough on a number the bill contradicts.
V1 trends consumption against the site's own baseline and does not normalize for weather or occupancy. So a hot-weather month or a sales event will read as elevated consumption. Where several sites in the same region move together in the same period, present it as expected context in the MBR rather than a finding — and scope a walkthrough for the genuinely site-specific anomalies. This is a portfolio reading, not a single SOP.
Energy Intelligence reads the meter; it does not switch loads. Where a consumption pattern points to a demand or schedule fix, Keedian recommends it and — where the customer also runs Keedian on HVAC, Lighting, or Refrigeration — executes it through that product (night setback, staggered start-up, timeclock correction). On a meter-only account the output is a guided recommendation for the site, not a remote command.
When the off-hours floor survives the end-of-day checklist for two or more months, the site is a candidate for a controls retrofit — a timeclock, a smart thermostat, or a contactor fix — which is a capital conversation, not a per-SOP operational fix. Document the floor trend and the no-capex steps already tried, then present it to the client in the MBR with the expected payback. CapEx decisions are entirely on the client's side.
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.