How Enterprises Choose Smart Meters and Submetering for Multi-Site Monitoring

Choosing smart meters for a multi-site enterprise is not a device decision — it is a measurement architecture decision. The meters you pick, where you place them, and how they communicate determine whether you get one usable energy picture across branches or a pile of disconnected readings.

What metering levels does a multi-site enterprise actually need?

Most enterprises need two levels: a main-incomer meter at every site to establish the total consumption picture, and submeters only on the loads that actually drive cost — HVAC plant, production equipment, kitchens, data rooms, or tenant areas.

The utility's own meter belongs to the utility. It tells you what you owe, usually monthly, and you rarely get interval data from it in a form you control. A private check meter on your main incomer, just downstream of the utility point, gives you your own interval data, lets you verify utility invoices, and creates a comparable baseline across every branch.

Submetering is where budgets are won or lost. The working rule: meter what you intend to manage. A submeter per floor makes sense in an office tower where floors map to departments or tenants. A submeter per asset makes sense for a chiller plant you plan to optimize. A submeter on everything makes sense nowhere — each point adds hardware, installation, commissioning, and a data stream someone must maintain.

Should you choose wired (Modbus/M-Bus) or wireless (LoRaWAN/cellular) communication?

Choose wired Modbus or M-Bus when meters cluster in electrical rooms you control and cable routes exist; choose LoRaWAN or cellular when points are scattered across a large site, or across many small branches where cabling would cost more than the meters themselves.

Most estates end up hybrid: Modbus chains inside switchrooms, LoRaWAN for scattered points, cellular for branches with no usable network. What matters is that every option reports into one platform.

Which accuracy class do you need — billing or monitoring?

If money changes hands on the reading — tenant billing, cost allocation with contractual weight, reconciliation against the utility — specify Class 0.5S under IEC 62053-22; for internal monitoring and load analysis, Class 1 under IEC 62053-21 is usually sufficient and noticeably cheaper.

The "S" classes are defined to hold their accuracy at low load through current transformers, which is exactly where cheaper meters drift. Remember the chain: a Class 0.5S meter measuring through a Class 3 CT delivers Class 3 performance in practice, so specify meter and CT accuracy together. For multifunction panel meters, IEC 61557-12 is the reference standard vendors should quote.

When do you need CT-operated meters instead of direct-connected?

Direct-connected meters suit small final circuits — commonly up to around 100 A per manufacturer application guidance; above that, main incomers and large feeders are metered through current transformers (CTs).

For retrofit projects, split-core CTs clip around existing cables without a shutdown, which matters in branches that cannot lose power for an afternoon. Solid-core CTs are cheaper and slightly more accurate but require disconnecting conductors. Whichever you choose, record the CT ratio for every point at commissioning — a wrong or unrecorded ratio silently corrupts every reading that follows.

What data interval is worth collecting?

Fifteen-minute interval data is the practical default: it matches how utilities compute demand, and it is granular enough to reveal base load, startup spikes, and after-hours waste.

Monthly totals hide almost everything actionable. One-minute data, at the other extreme, multiplies storage and communication load — and exceeds what a LoRaWAN link can carry for many registers — so reserve it for temporary diagnostics on specific assets. Decide the register list deliberately too: kWh, kW demand, per-phase currents and voltages, and power factor cover most needs; harmonics and waveform capture are specialist additions, not defaults.

What integration questions should you ask vendors?

Ask how the data leaves the meter and who owns it once it has: open protocol or proprietary head-end, export formats, and what happens to your history if you change software later.

A short checklist for vendor meetings:

• Which open protocols does the meter speak natively (Modbus, M-Bus, LoRaWAN), and is a gateway required?
• Can we export our full interval history at any time, in a documented format?
• How are default passwords handled and firmware updates delivered over the meter's life?
• Does the meter buffer readings locally when communications drop, and for how long?
• What commissioning documentation is delivered — register maps, CT ratios, point naming?
• Are enclosures and electronics rated for our ambient temperatures, especially outdoor installations in Gulf conditions?

How should you sequence a rollout across branches?

Put a main-incomer meter in every branch first, then submeter deeply at your two or three most expensive sites, and only then write the standard package you roll out everywhere else.

Phase one buys comparability: a league table of branches per square meter or per unit of output, which by itself directs attention to the outliers. Phase two, at the pilot sites, teaches you which submeters earned their cost and which were noise. Phase three turns that lesson into a repeatable template — a fixed register list, a naming convention, a CT-ratio record sheet, and one communication design per branch type — so branch twenty commissions as cleanly as branch four. If ISO 50001 certification is on your roadmap, this staged measurement plan maps directly onto what the standard expects from an energy data collection plan.

How does ENTEK help?

Rolling metering out across many branches is as much a procurement challenge as a technical one: the same specification must reach several suppliers, offers must be comparable line by line, and deliveries must be tracked per site. ENTEK lets enterprises send one clear quotation request to verified suppliers, compare the offers that come back against the same specification, and manage the resulting orders across all branches from a single view — so a phased metering program stays consistent from the pilot sites to the last branch.