One Computation Layer for Every Utility: Electric, Water, Gas, BTU, Steam, Compressed Air
Most facilities run separate meters and separate dashboards for each utility — and pay for it in manual reconciliation, missed cross-utility insights, and unreliable tenant invoicing. The Emergent computation layer normalizes data across all six utilities into a single time-series and a single integration target. That is what makes cross-utility insights — chiller kW/ton, compressed air $/scfm, steam-trap loss, water leak detection — actually possible.
Electric Submetering
The Panoramic Power family covers every electric measurement point: PAN-10 for branch circuits up to 63 A, PAN-12 for feeders up to 225 A, PAN-14 with external CTs from 100 A to 4000 A+, and PAN-42 for revenue-grade main service. For high-density panels we add the S7100 Branch Circuit Monitor (BCM) — up to 84 circuits in a single device. All hardware supports IECC 2021 Section C405.12 and ASHRAE 90.1 end-use submetering requirements.
See Electric SubmeteringWater Submetering
Neptune T-10 positive-displacement meters and the MTW MJ / MJ420 / MJ20S families cover residential to large commercial sizing. For non-invasive retrofits we deploy ultrasonic EES-101 and EES-201 clamp-on meters. Hot water meters are specified separately for California Title 24 and similar compliance regimes. Tenant-grade meters serve billing; process-grade meters serve cooling tower makeup, irrigation, and reuse measurement.
See Water & BTU MeteringNatural Gas Submetering
Sage Metering thermal mass flow meters and VorTek Instruments insertion vortex meters cover the full industrial range — from small process gas headers to plant main service. Both families output pulse, Modbus, and BACnet, so they integrate directly into the computation layer alongside the electric and BTU meters. Sage carries SIL-rated options for hazardous-area installations.
See Natural Gas SubmeteringBTU / Thermal Submetering
Onicon EES-301 and EES-401 ultrasonic BTU meters measure chilled-water, hot-water, and condenser-water systems with non-invasive ultrasonic flow combined with paired temperature sensors. Pre-configured packages exist for the common chiller-plant and district-energy use cases, eliminating most of the field engineering on each install.
See Water & BTU MeteringSteam Submetering
Header-level vortex and orifice meters quantify boiler output for chiller-plant heat load, central plant accounting, and process facility cost allocation. Process-level meters are deployed at sterilizers, dryers, and heat exchangers where steam is the dominant cost driver. The computation layer combines steam mass flow with condensate return data to surface steam-trap losses that otherwise stay hidden.
See Steam MeteringCompressed Air Metering
VP Instruments insertion thermal mass flow meters provide $/scfm visibility on compressed air systems. Pairing flow with the compressor's electrical kW exposes night and weekend baselines — typically 20–30% of compressor energy is leak load. The computation layer turns that gap into a prioritized leak-repair list with attributed savings.
See Compressed-Air MeteringHow the Computation Layer Unifies Six Utilities
The hardware is necessary but not sufficient. The computation layer is the software tier that turns six independent meter networks into one decision-ready data product. Four mechanics make this work:
- Edge aggregation. A Niagara JACE or Robustel gateway on-site collects every utility at its native protocol — BACnet, Modbus, pulse, LoRaWAN, REST — and buffers through outages.
- Common taxonomy. Every measurement point is mapped to a canonical tag dictionary on ingest, so "MSB-1," "MAIN-SWGR-A," and "Service Entrance" all become the same logical asset across sites.
- Normalized time-series. Timestamps are aligned to a single timezone, units are converted, gaps are flagged, and rollovers are reconciled — all before the data is exposed to consumers.
- Single integration target. The cleaned data is published once — to Niagara as virtual points, to your ERP via REST or MQTT, to ENERGY STAR Portfolio Manager, and to the tenant-billing engine.
| Dimension | Traditional siloed approach | Computation layer approach |
|---|---|---|
| Number of dashboards | One per utility (3–6) | One — across all utilities |
| Time-series alignment | Each system stamps its own time, no shared clock | Single normalized time-series across every meter |
| Tag and unit normalization | Site-by-site, manual, drifts over time | Canonical taxonomy, enforced on ingest |
| Cross-utility insights | Manual spreadsheet work, weeks behind real time | Native — chiller kW/ton, $/scfm, steam-trap loss in real time |
| Tenant billing | Separate exports, manual reconciliation | One billing run covers electricity, water, gas, and BTU |
| BMS / ERP integration | One driver per system | Single Niagara, REST, or MQTT endpoint |
For the manufacturing-specific architecture, see the real-time submetering computation layer for manufacturing plants. For the wireless hardware that feeds it, see the wireless multi-utility submetering platform.
Frequently Asked Questions
Which submetering systems monitor electricity, water, gas, and compressed air?
A complete multi-utility stack typically combines Panoramic Power wireless sensors and Branch Circuit Monitors for electricity, Neptune positive-displacement and Onicon ultrasonic meters for water and BTU, Sage Metering and VorTek thermal/vortex flow meters for natural gas and steam, and VP Instruments insertion meters for compressed air. The hardware itself is the easy part — the differentiator is the computation layer that normalizes all six streams into one time-series and one integration target.
How do you select the right meter for each utility?
Five criteria in order: required accuracy (revenue-grade vs. operational), pipe or panel constraints (intrusive vs. non-invasive), data resolution (sub-minute for demand peaks vs. 15-minute for monthly billing), output protocol (must match the integration path), and lifecycle cost including recalibration. The computation layer is protocol-agnostic so the meter choice can be optimized per measurement point without compromising the data product downstream.
Does multi-utility submetering work for tenant billing?
Yes. The computation layer applies tenant-allocation rules consistently across electricity, water, natural gas, and BTU. A single monthly billing run produces auditable invoices with backing interval data, eliminating the manual spreadsheet reconciliation that historically caused tenant disputes.
How does multi-utility submetering support sustainability reporting?
ENERGY STAR Portfolio Manager, GRESB, CDP, and SBTi all expect data across multiple utilities. The computation layer publishes normalized monthly totals to Portfolio Manager and supports Scope 1 (gas, steam) and Scope 2 (electricity) reporting with the same data foundation, including hourly-matched Scope 2 if required.
Can multi-utility submetering meet IECC 2021 and ASHRAE 90.1 end-use monitoring requirements?
Yes. Both standards require permanent end-use submetering above defined thresholds and do not specify hardware brand. The Panoramic Power PAN-12, PAN-14, PAN-42, and the S7100 BCM cover the electrical end-uses; thermal energy and gas requirements are met by EES BTU meters and Sage / VorTek gas meters. The computation layer holds the audit trail.
Get a multi-utility submetering assessment
Tell us which utilities you already meter, where the gaps are, and where the data goes today. We'll return a phased rollout plan, a hardware bill of materials, and an integration design for your BMS or ERP.
Request a Site Assessment