Know What Your Facility Actually Spends on Power: A Field Guide to Monitoring, Submetering, and Cost Visibility

Facility power monitoring is the continuous measurement, attribution, and analysis of electrical consumption, by circuit, process, tenant, or piece of equipment, using revenue-grade or monitoring-grade meters integrated through open protocols. It exposes the cost categories that the utility bill bundles together (energy, demand, ratchet, power factor, time-of-use), enables submetering for tenant and process cost allocation, and turns electricity from a backward-looking expense into a forward-looking operational lever. The utility bill alone is not monitoring: it is a billing artifact that arrives weeks late, aggregated across everything the building did.

Ask a CFO what their facility spends on power and they can quote the monthly bill within a few thousand dollars. Ask which floor, process, tenant, or piece of equipment is driving that number, and the answer usually starts with "we think." For most facilities, the utility bill is the only authoritative source of truth about power, and it is the wrong one. It is too late, too aggregate, and structured for billing rather than for decisions.

Power is one of the largest controllable operating costs in any mission-critical facility, and one of the least understood. Most owners and operators have visibility only at the meter the utility uses for billing, which arrives weeks late, aggregated across everything the building did, and structured to make the utility easy to audit rather than to make the facility easy to run. The result is a recurring expense the size of a payroll line with the operational visibility of a phone bill.

This guide breaks down what real facility power monitoring should do for you: the cost categories the utility bill hides, the difference between metering and monitoring, the signal quality that determines whether your data is decision-grade, how submetering enables true cost allocation across tenants and processes, and where a platform like ControlCom Connect turns all of it into operational insight instead of another dashboard.

Why the utility bill is the wrong source of truth

The utility bill is a billing artifact. It tells you what the utility is going to charge you, after the fact, against rate schedules that bundle three or four distinct cost mechanisms into one total. By the time the bill arrives, the decisions that drove that month are gone. The peak demand interval already happened, the power factor penalty was already incurred, and the time-of-use schedule already counted what you ran during the expensive window.

Worse, almost no utility bill resolves cost below the building meter. A campus with three buildings on a single utility account sees one number. A hospital with a surgical suite, a data center, a cafeteria, and a chiller plant on the same service sees one number. The most expensive consumer in the building is invisible to the people paying for it.

The cost categories monitoring should expose

Commercial and industrial electricity rates are layered. Five distinct mechanisms typically contribute to the bill, and good monitoring breaks each one out separately because each one responds to different operational levers.

• Energy charges (kWh): what most operators think of as "the bill." Driven by total consumption. Reducible by efficiency improvements and load-shifting.
• Demand charges (kW): a per-month fee based on the highest fifteen-minute or thirty-minute average load the facility hit during the billing period. Often thirty to fifty percent of the total bill for industrial accounts. Reducible by peak-shaving, sequencing, and demand-response.
• Demand ratchets: a clause in many utility tariffs that says your billed demand for the next 11 months cannot drop below a percentage (often 75 to 90 percent) of your annual peak. One bad 30-minute window in August can inflate the next year of bills.
• Power factor penalties: a surcharge when reactive power consumption pushes power factor below the utility threshold (commonly 0.90 to 0.95). Mitigable by capacitor banks, active filtering, and load-side correction.
• Time-of-use and seasonal rates: per-kWh prices that vary by hour of day and month of year, often by a factor of two or three. Loads that can shift even partially out of peak windows pay back fast.

When monitoring exposes these five separately, every conversation about reducing power spend stops being about "use less electricity" and starts being about specific levers with measurable returns. That distinction is the entire point of the system.

Signal quality: not all metering is decision-grade

Monitoring is only as good as the data underneath it. Two facilities with identical dashboards can be operating on data that is off by ten percent and updating once an hour versus data that is accurate to a fraction of a percent and updating every second. The difference matters when you are deciding whether to run a chiller, dispatch a peaker, or accept a demand-response signal.

• ANSI C12.20 (Class 0.2 and 0.5): the US revenue-grade meter standard. Required for billable submetering and utility-grade installations.
• IEC 61557-12: the international classification for power monitoring devices, useful for separating monitoring-grade from utility-grade equipment.
• CT and PT accuracy class: the current and voltage transformers feeding the meter set the ceiling for accuracy. A 0.2-class meter on a 1.0-class CT is a 1.0-class measurement.
• Sampling rate and data resolution: revenue billing needs 15-minute averages. Power quality and demand-response need second-level or sub-second sampling.
• Time synchronization: meters across a facility must agree on time to within milliseconds for events to correlate and for demand calculations to align with the utility window.
• Communications reliability: a meter that disappears from the network for four hours has a four-hour hole in your operational picture, regardless of how accurate it was during the rest of the day.

Submetering and cost allocation

Submetering is the practice of installing meters downstream of the utility meter to attribute consumption to specific circuits, tenants, processes, or pieces of equipment. It is the only way to answer the questions that matter most: "what does the data center cost us, separate from the rest of the building?" and "is this tenant paying their fair share?"

• Tenant submetering: revenue-grade meters on tenant feeders, with rates that match the lease agreement. Eliminates disputes and turns common-area energy from a fixed overhead into an allocated cost.
• Process submetering: meters on individual production lines, chillers, compressors, or pumps. Exposes the cost per unit of output and makes energy intensity a managed metric.
• Departmental allocation: hospital or campus environments where surgical suites, imaging, food service, and central plant should each see their own consumption and cost.
• Sustainability reporting: submetering provides the granular data ESG and ISO 50001 energy management systems require, by source and by use.
• Demand-response participation: utility programs that pay for verified curtailment require auditable, revenue-grade measurement of what was shed.

Submetering pays for itself fastest in facilities with multiple cost centers, regulated cost allocation requirements, or eligible demand-response programs. For a hospital, a multi-tenant industrial park, or a critical-process facility, it is usually the highest-ROI piece of the monitoring stack.

What a useful monitoring platform should do

There are dozens of monitoring platforms on the market. Most of them produce a dashboard. The useful ones produce decisions. A short list of what to look for, and what to be suspicious of:

• Real-time visibility, not yesterday's data: if the platform cannot show you what is happening right now, it cannot help you avoid the next demand peak.
• Baselines and anomaly detection: a chart of consumption is not a tool until something flags when it deviates from normal. Static thresholds are weak; learned baselines that adapt to schedule, occupancy, and season are strong.
• Cost translation, not just kilowatt-hours: every consumption metric should translate to dollars under the tariff that actually applies. "We used 12 percent more energy" is interesting; "we paid an extra $4,300 this month, and here is why" is actionable.
• Multi-site comparison: for organizations with more than one facility, the ability to benchmark sites against each other reveals operational variance and best practices that single-site dashboards cannot.
• Open data, not a walled garden: the platform should expose its data through standard APIs, support export to historians and BI tools, and never be the only place your data lives.
• Integration with the protection and control system: monitoring that is bolted on as a separate parallel system misses half the story. Monitoring that lives next to the relays, meters, and controls sees alarms in context.
• Cybersecurity posture: this is OT data flowing over IP networks. Segmentation, authentication, audit logs, and patch management should all have answers.

Standards and frameworks worth knowing

A few standards and frameworks come up consistently when monitoring scope is being defined. Familiarity with them helps separate substantive proposals from marketing.

• ISO 50001: the international standard for energy management systems. Defines the policy, planning, measurement, and review cycle that turns monitoring data into managed performance.
• ASHRAE Standard 90.1 and Guideline 14: energy efficiency for buildings and measurement and verification of savings. The basis for proving that an efficiency project actually delivered.
• IEEE 1459: definitions for measurement of electric power quantities under non-sinusoidal, unbalanced, or transient conditions. The standard that determines whether your power monitor actually measures what it claims to in real-world conditions.
• NIST handbook 44: legal metrology for utility-grade measurement, the underlying basis for ANSI C12 in the US.
• IEC 61850: the substation automation standard that increasingly extends into monitoring through device-level data models and reporting services.

Where ControlCom Connect fits

ControlCom Connect is the ControlCom Technologies Engineering remote monitoring and analytics platform, and it sits above the protection and control layer rather than inside it. The integrated control system runs the facility. ControlCom Connect collects from the meters, relays, breakers, and thermal sensors continuously, attributes consumption to circuits and processes, translates kilowatt-hours into dollars under the right tariff, and surfaces deviations before they become demand peaks, ratchet events, or unplanned outages.

• Continuous visibility into electrical and thermal health of every breaker, panel, and switchgear bus the platform is monitoring
• Cost translation against the actual utility tariff, including time-of-use, demand, ratchet, and power factor mechanisms
• Submetering rollup across tenants, processes, and cost centers for accurate allocation and chargeback
• Alerting on demand approaching the monthly peak, on power factor drifting toward the penalty threshold, on thermal trends that predict component failure
• Open data through APIs and standard protocols, so the data is available to historians, BI tools, and any future platform we are not part of
• Designed as visibility, not as a dependency: the facility runs the same whether the platform is reachable or not

The reason that distinction matters is that monitoring should never become a single point of failure. The control system holds the safety and reliability of the facility. The monitoring platform holds the visibility. Coupling them creates risk. Separating them, while still integrating the data, is the architecture ControlCom Technologies Engineering delivers.

Common questions

How we approach monitoring projects

ControlCom Technologies Engineering starts with the operational decisions the facility wants to make and works backward to the measurement scope. A facility chasing demand-charge reductions has a different metering plan than one driven by tenant allocation or by sustainability reporting. The first deliverable is a measurement and verification plan that ties every monitoring point to a decision and a dollar value, before any meter is installed.

Every system ControlCom delivers is vendor-neutral by design, built on revenue-grade and monitoring-grade meters that match the accuracy class to the decision, integrated through open protocols, and exposed through ControlCom Connect for the analytics and alerting that turn the data into operational levers. The facility owner should never feel that their data lives somewhere only ControlCom can reach.

Key takeaways

• Facility power monitoring is continuous measurement, attribution, and analysis of electrical consumption; metering is the underlying measurement, and monitoring is the decision-making layer built on top of it.
• Commercial and industrial electricity bills typically combine five distinct cost mechanisms, energy (kWh), demand (kW), demand ratchets, power factor penalties, and time-of-use rates, each of which responds to a different operational lever.
• Demand charges often account for 30 to 50 percent of an industrial facility's total electricity bill (typical US commercial and industrial tariff structures, NIST Handbook 44 reference billing categories).
• Revenue-grade metering is defined by ANSI C12.20 (Class 0.2 and 0.5 in the US); monitoring-grade equipment is classified by IEC 61557-12.
• ISO 50001 is the international standard for energy management systems, defining the policy, planning, measurement, and review cycle that turns monitoring data into managed performance.