Skip to main content
Integrar IoT
Power MonitoringSubmeteringRevenue GradeTenant Billing

Power Monitoring Submetering: Revenue-Grade Accuracy

October 15, 2025 · Marcus Chen

When a building owner sends a tenant a monthly bill for energy, that number had better survive scrutiny. Utilities enforce the accuracy of their own billing meters to ANSI C12.20 accuracy classes and recalibrate them on fixed schedules, but the submeter used to reallocate that cost to tenants is governed by nothing until a dispute lands on someone’s desk. Revenue-grade submetering is the discipline of treating every tenant, cost-center, and department boundary as if it were the utility meter at the property line—because, economically, it is.

Revenue-Grade versus Monitoring-Grade

The term “revenue grade” describes the meter’s accuracy class, not its price tag. In North America, ANSI C12.20 defines Class 0.2 and Class 0.5 meters, meaning the measured energy is accurate to within 0.2 or 0.5 percent of the true value. Utility billing meters are almost always Class 0.2. Monitoring-only meters—the kind used for trend spotting—are typically Class 1.0 or looser and drift more over time. That difference matters when small percentage errors are multiplied across large bills and many tenants.

Revenue-grade also implies more than the metrology chip inside the meter. It implies:

  • Instrument transformer rating. Current transformers (CTs) are specified with an accuracy class and a burden rating. A Class 0.5 meter paired with an unrated or overburdened CT is not revenue-grade no matter what the meter face says.
  • Verification process. Calibration records, test dates, and traceable standards for both the meter and its CTs.
  • Data integrity. Sealed, tamper-evident hardware and timestamped interval data that can survive an audit years later.

Why Buildings Submeter at All

The core business case is simple: cost allocation requires a defensible measurement. Where a lease is “gross with escalation,” the owner wants to track each tenant’s consumption to bill energy at cost. Where leases are triple-net, the building must allocate common-area energy fairly. Without submeters, owners fall back on square-footage proration, which is fair to nobody: a 5,000-square-foot server room can draw more power in a month than a 15,000-square-foot office floor, and proration silently taxes the office tenant while subsidizing the server room.

Submetering also unlocks performance insight that proration hides:

  • Benchmarking by space type. kWh per square foot for office, lab, retail, and data zones becomes a comparable metric rather than an anonymous blend.
  • Demand attribution. Interval data shows which tenant drove the building’s peak—and therefore which share of the demand charge they should carry.
  • Operational leakage. A tenant leaving a suite at full HVAC over the weekend is visible in their interval pattern and addressable under the lease’s energy rules.

Billing Methodology Is the Real Decision

The hardest part of a submetering project is not installing meters; it is deciding what the tenants will actually be billed for. A typical building uses a cascading model:

Cost component Basis How it is measured
Tenant consumption kWh and peak kW on their meter Direct interval reading
Common-area energy Owner’s estimate or pro rata Shared across tenants, usually by area or headcount
Demand charges Coincident peak The building’s monthly peak, split by each tenant’s usage during that window
Fixed grid costs Pass-through Divided by metered usage share

The subtlety is the coincident peak. If the utility bills a single demand charge for the building, and every tenant runs equipment at 4 p.m., allocating demand by each tenant’s own maximum does not reflect reality—the building’s peak is a shared event. Professional practice is to use coincidence factors: each tenant’s kW during the building’s actual 15-minute peak window, which requires interval data from the utility meter aligned in time with the tenant meters.

A Three-Building Case in Numbers

A 200,000-square-foot office building with 12 tenants spends $180,000 a year on electricity, including $45,000 of demand charges. Under square-footage proration, tenant A, occupying 12,000 square feet (6 percent of the building), pays 6 percent of every cost line. Once interval submetering reveals that tenant A runs a 24/7 colocation rack area consuming 11 percent of kWh and 14 percent of coincident demand, their true bill is roughly $11,400 higher per year—and the other tenants stop subsidizing it. That reallocation recovers the meter project cost in the first billing cycle, and it gives tenant A an incentive to negotiate the demand-limitation clause they never knew they needed.

Choosing and Deploying Meters

The evaluation criteria that separate a good submetering deployment from a liability:

  • Accuracy class and the CT chain. Verify that the whole chain—meter, CTs, and wiring—meets the class you will cite in a dispute.
  • Interval recording. Meters should log at least 15-minute intervals locally, buffering through communication outages rather than losing data.
  • Timestamping. All meters, and the billing system, must run on synchronized time. A 15-minute demand interval is meaningless if the meters disagree by three minutes.
  • Remote reading. Submeters are worth little if reading them requires a clipboard. Verify the communication path—Modbus RTU on the branch panel, BACnet MS/TP in the BAS, or MQTT/HTTP to the platform—actually reaches every meter.
  • Audit trail. Billing-grade data must be immutable once posted. Any adjustment process should be logged, not silently edited.

Making Billing Defensible

Even the best meters fail an audit if the process is weak. Three practices keep tenant bills defensible:

  1. Fixed closing schedule. Define the billing month boundary precisely and close meter reads at the same instant across the portfolio.
  2. Documented exception handling. Meter outages happen; the billing policy must state the estimation method used when a tenant’s meter is offline—typically proration from the prior period—and apply it uniformly.
  3. Periodic recalibration. Revenue meters drift. A documented recalibration cycle, typically every three to five years and aligned with the CT class, keeps the Class 0.2 claim honest.

Conclusion

Submetering is an accounting problem as much as an instrumentation problem. When the meter chain is revenue-grade, the time base is synchronized, and the allocation policy is explicit, tenant billing stops being a source of friction and becomes a transparent operating number. Done well, it pays for itself in the first reconciliation, improves leasing trust, and gives the owner the per-space data needed to negotiate better demand and utility contracts.

Integrar IoT’s energy platform collects interval data from revenue-grade meters over Modbus, BACnet, MQTT, OPC UA, and DNP3, aligns timestamps across meters and the utility, and produces the allocation reports that keep submetering billing both fair and auditable.

Related: