Productization
Energy

Energy Per-circuit power & current

Real power and current of an individual circuit — an RTU, the refrigeration rack, the lighting panel — captured by a submeter. Turns the meter into a per-asset view: it attributes energy by end use and provides the baseline every equipment-health signal compares against.

01 Metric Definition

What it measures and how it is calculated

What it measures

The real power (kW) and current (A) drawn by an individual circuit — an RTU, the refrigeration rack, the lighting panel — captured by a submeter at the panel during the analysis period. It turns the whole-building meter into a per-asset view: it attributes energy by end use and provides the baseline every equipment-health signal compares against.

How it is calculated

The calculation depends on the metering installed at each site. At Optimized, a submeter on the individual circuit reports real power and current directly — this per-circuit metering is the differentiator that makes per-asset attribution possible; the whole-building meter alone cannot separate one RTU from the rack.

Per-circuit power is read directly from the submeter; current is the RMS measurement on the same circuit. From the steady running power and current, a healthy baseline is established per circuit at commissioning (and re-established after a service visit or an equipment change), and every later reading is compared against that circuit's own baseline rather than against another site.

Attribution works from two sources only — the per-circuit telemetry and the utility bill. There is no weather or occupancy normalization in V1: a step-change against baseline is flagged for a walkthrough, not auto-attributed to ambient conditions. The exact thresholds and baselining logic vary by client depending on the equipment class, the metering point, and the integration.

Reference thresholds

RangeClassificationInterpretation
Within ± baseline bandExpectedCircuit power and current tracking its own healthy baseline at like-for-like operating conditions
Step-change vs baseline (no known change)Flag — scope a walkthroughConsumption or run-fraction stepped up with no merchandising or load change; attribute to the exact circuit before product or comfort loss
Rising-current signature on the stepDegradation — book serviceA circuit pulling more amps to do the same work; the earliest electrical sign of fouling, charge loss, or wear — schedule a visit, not an emergency dispatch
Circuit drawing during scheduled off-hoursSchedule / contactor faultA load running when it should be off — a timeclock, control, or contactor problem to correct on site

Reference examples only. Baselines and step-change thresholds are calibrated per client and per circuit based on equipment class, metering point, and operating hours before any alarm is activated. No customer benchmark is implied by these ranges.

Portfolio compliance target

There is no single portfolio compliance target for this metric — it is an attribution baseline, not a pass/fail KPI. The agreed target is the set of circuits submetered per site and the per-circuit baselines kept current; define both with each client at commissioning.

02 Impact

How this metric moves the customer value drivers

The table below shows how moving Per-circuit power & current impacts each customer value driver the product is designed to improve — the metric page explains the mechanism; the product pages express the magnitude.

Value driverImpact strengthHow Per-circuit power & current moves this lever
Energy savingsDirect, primaryPer-circuit power is what turns a whole-building anomaly into an exact end use. Attributing kWh to the RTU, the rack, or the lighting panel is the only way to know which load to act on — and where the customer also runs Keedian on HVAC, Lighting, or Refrigeration, that attribution is what lets the connected product act on the right circuit. Energy Intelligence reads the meter; it does not command the load.
Avoided truck rollsDirect, strongA per-circuit step-change is attributed to the exact circuit before it becomes a complaint, so an emergency dispatch becomes a scheduled visit with the right scope already known. The same attribution separates a real circuit fault from a metering artifact or a utility-side issue — avoiding the truck roll that diagnoses nothing.
Asset lifespanIndirect, leading indicatorPer-circuit current is the baseline every equipment-health signal compares against — short-cycling and cycling frequency both read off this circuit. Catching the step-change or the rising-current signature weeks early lets the customer correct the root cause (fouling, charge loss, a schedule fault) before the equipment is damaged.
03 Detection

How it surfaces and when it is reviewed

How it surfaces

Alarm
Can be configured to fire when a submetered circuit's consumption or run-fraction steps up against its own baseline with no known merchandising or load change.
Equipment
Per-circuit power and current shown against baseline in the Site Dashboard per-circuit table, with the deviating circuit identified by end use (RTU, rack, lighting panel).
Site
The affected circuit flagged in the Energy Detail or Top/Worst Performers tab, with the attributed end use and the meter-vs-bill reconciliation alongside.
Portfolio
Circuits running off-schedule or trending against baseline rolled up across sites in the Executive Summary dashboard for the monthly review.

Review cadence

Monthly
Reviewed during MBR using the per-circuit trend and the meter-vs-bill reconciliation for the billing cycle.
Weekly
Operations team reviews circuits trending against baseline and any off-hours draw on the worst-performers list.
Real-time
Alert triggered for a per-circuit step-change or off-hours draw where configured.
04 Alarms

Principal alarms derived from this metric

The table below summarizes the alarms that fire directly from Per-circuit power & current. Each row links to the full operational detail (trigger, preconditions, action plan, human role, escalation, prevention) in the SOPs catalog.

AlarmDescriptionSeverityTierAI executes?Value driversSOP
Per-circuit consumption step-change A sub-metered circuit's consumption or run-fraction steps change with no merchandising or load change. High Optimized Hybrid Avoided truck rolls · Asset lifespan · Energy savings Open SOP →
More alarms in development

More alarms in development (single-metric): off-hours circuit draw as a standalone alarm. The equipment-health signals that compare against this per-circuit baseline — short-cycling, service-voltage and power-factor power-quality alarms — are documented on their own metric pages. Composite FDD that combines per-circuit current with control state will appear in a future release.

05 Actions

What to do based on the alarm

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.

Per-circuit consumption step-change

Attribute the step to the exact circuit, scope the equipment check, and convert an emergency truck roll into a scheduled visit — the full diagnostic sequence, human role, and escalation criteria live on the SOP page.

Responsible
Keedian operations team
Urgency
See SOP
Client approval
See SOP

Submetering integrity or attribution issue suspected (metric-level — not a single alarm)

If a circuit's power or current looks implausible, or the per-circuit readings don't sum toward the whole-building meter, treat the attribution as unreliable before acting on any alarm. A CT clamp on the wrong circuit, a reversed CT, or a wrong CT ratio biases every signal that compares against this baseline. Escalate internally to the technical team, exclude the affected circuit from the period, and confirm the metering point before reporting anything to the client.

Responsible
Keedian technical team
Urgency
High — bad attribution corrupts every equipment-health signal that reads off this circuit
Client approval
No for investigation — Yes if a CT has to be re-clamped on site

Meter-versus-bill divergence (metric-level — billing recovery)

Reconcile attributed circuit energy and total metered kWh against the utility bill each cycle. A divergence beyond tolerance can be a CT-ratio or multiplier error or a billing mistake worth recovering — present the finding to the customer rather than absorbing it as a circuit fault. This is a portfolio-level reconciliation, not a per-circuit dispatch.

Responsible
Keedian account manager (communication) + operations team (data)
Urgency
Medium — a recoverable cost, surfaced at the billing cycle
Client approval
Yes — billing-recovery action is the customer's to pursue with the utility

Baseline calibration after an equipment or merchandising change (metric-level)

When a circuit's equipment is serviced or replaced, or merchandising changes the load, the old baseline no longer holds and a step-change against it is expected behavior, not a fault. Re-baseline the affected circuit and note the change so it is not reported as an anomaly. This keeps every downstream equipment-health signal honest.

Responsible
Keedian operations team
Urgency
Low — routine baseline hygiene
Client approval
No
06 Escalation

When and how to escalate

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.

Portfolio-level patterns — typically communicated in the MBR
  • Several sites showing the same per-circuit drift on the same equipment class — a fleet pattern worth a corporate maintenance or specification review
  • Recurring meter-vs-bill divergence across sites — open a standing billing-recovery review with the customer rather than handling it case by case
  • Circuits repeatedly drawing during scheduled off-hours across multiple sites — a controls or timeclock-retrofit candidate to flag for the customer
Cross-alarm urgency — typically requires out-of-cycle communication
  • A per-circuit step-change co-occurring with a rising-current signature on a refrigeration or RTU circuit — degradation in progress; book service before product or comfort loss, do not wait for the next MBR
  • A submetering-integrity issue affecting per-circuit attribution across the portfolio — pause the affected reporting until the CTs are confirmed
  • Any per-circuit finding with direct financial impact for the customer — a recoverable billing error or a circuit approaching a capacity limit that blocks a planned equipment addition
07 Prevention

Controls to avoid recurring issues

Configuration controls

  • Submeter the circuits that matter at commissioning — the RTUs, the refrigeration rack, the lighting panel — and record which CT reads which end use so attribution is unambiguous
  • Establish a healthy per-circuit baseline at commissioning and after every service visit, and re-baseline whenever the equipment or merchandising on a circuit changes
  • Document the circuit and breaker rating on file so current readings can be checked against the continuous-load limit

Monitoring controls

  • Configure automated alerts for a per-circuit step-change against baseline and for any draw during scheduled off-hours
  • Reconcile attributed circuit energy and total metered kWh against the utility bill every billing cycle to catch CT-ratio, multiplier, or billing errors early
  • Watch the per-circuit current trend as the baseline for the equipment-health signals — short-cycling and cycling frequency both read off this circuit

Reporting controls

  • Include the per-circuit attribution and the meter-vs-bill reconciliation in every MBR
  • Flag circuits trending against baseline for two consecutive periods before they become an escalation item
  • Maintain a log of circuits with recurring anomalies to surface systemic patterns across the portfolio and separate a real fault from a stale baseline