Smart Utility Metering: Why Systems Stop Being Read
Most metering projects fail after handover, not during it. The four decisions that matter more than the brand, and the clauses that stop vendor lock-in.
A smart meter that nobody reads is an expensive ordinary meter.
That is the outcome on a surprising number of projects. The hardware is installed, the specification is met, the handover is signed — and eighteen months later the data goes nowhere, nobody has been trained to act on it, and the building is billed the way it always was.
The failure is almost never the meter. It is everything the meter was supposed to connect to.
What actually makes a metering project work?
Deciding, before anything is bought, what decision the data is meant to change. Sub-metering for tenant billing, energy management for cost reduction and leak detection for water losses are three different projects with three different specifications. A system designed for one rarely serves another well.
This sounds obvious and is routinely skipped, because metering is usually specified as a product line in a schedule rather than as an outcome. The consequence shows up later: meters placed where they are easy to install rather than where the boundary of responsibility actually sits, a communication path that works in the lab and not through three concrete floors, and data arriving in a format nobody’s billing system can ingest. Every one of those is decided at specification stage and expensive to fix afterwards. Start from the question who will look at this, how often, and what will they do differently because of it — and the technical choices mostly answer themselves.
The four decisions that matter more than the brand
| Decision | What goes wrong when it is made late |
|---|---|
| Where the boundaries are | Meters end up measuring a mix of tenants and common areas, so no bill can be defended |
| How data gets out | Wired, wireless or mixed. Signal through structure is a site question, not a datasheet question |
| Where data lands | If it cannot enter the billing or BMS system in a usable format, it is not information |
| Who owns it after handover | Unowned systems drift. Batteries die, a gateway is unplugged, nobody notices for a year |
The fourth is the one that decides whether the system still works in year three, and it is the one least likely to appear in a tender document.
Specifying a meter without locking yourself in
The practical risk in metering is not a bad meter. It is a closed system: hardware that only talks to one vendor’s software, on one vendor’s licence, at one vendor’s renewal price.
A few clauses protect you, and they cost nothing to include at tender:
- Open, documented communication protocols, so another integrator can read the fleet later
- Raw data export in a standard format, available to the owner without a licence condition
- Named accuracy class and the standard it is measured to, not an unreferenced percentage
- Calibration and verification arrangements — including what happens when a meter is disputed
- Spares and replacement availability, with a stated period
- Who holds the credentials to the gateway and the platform after handover
That last clause has resolved more disputes than every technical specification combined. A building that cannot log into its own metering system does not own it.
Water metering is not electrical metering
They get bundled in specifications and they behave differently.
Water sub-metering is usually justified by two things — fair allocation between tenants, and finding losses. The second is where the value hides. A continuous small flow at 3 a.m. across a whole building is a leak signature that no monthly reading will ever reveal, and it is often paying for itself before the tenant billing does.
That has a design consequence: for leak detection you need interval data, not monthly totals, and you need somebody who looks at it. A water metering system delivering monthly figures to an inbox is doing the allocation job and none of the loss job.
Accuracy class: the number that decides whether a bill holds up
When a tenant disputes a reading, the argument is not settled by the brand on the meter. It is settled by the accuracy class it was certified to, and by whether that class was ever written into the specification.
For AC electricity meters the structure is worth knowing, because it is simple once someone lays it out. Since the 2020 revision, the general requirements and test methods sit in one place — IEC 62052-11 — and the class-specific requirements sit in the parts alongside it. IEC 62053-21 covers static meters for active energy in classes 0,5, 1 and 2. IEC 62053-22 covers transformer-operated static meters in the tighter classes 0,1 S, 0,2 S and 0,5 S, for networks up to 1 000 V AC at 50 or 60 Hz.
The practical translation:
| Where it sits | Typical class | Why |
|---|---|---|
| Apartment or small tenant unit | Class 1 or 2 | Directly connected, modest consumption, cost sensitive |
| Commercial tenant, large load | Class 0,5 or 0,5 S | The money per percentage point of error is real |
| Incomer, bulk supply, revenue boundary | Class 0,2 S | Transformer-operated; a fraction of a percent is a large sum |
The mistake that costs the most is specifying one class across a whole estate to keep procurement simple. An over-specified apartment meter wastes money quietly. An under-specified incomer creates a discrepancy between what the utility bills the building and what the building bills its tenants — and that gap does not close by itself. It becomes somebody’s loss every month.
Ask for the class, the standard it was certified against, and the test report. A datasheet that states a class without naming the standard is stating a marketing position.
Source: IEC 62053-22:2020. Standards are revised; confirm the current edition applicable in your market.
R160 and Q3: what a water meter datasheet is really telling you
Water meter datasheets look opaque until you know that two numbers carry almost all the meaning.
Q3 is the permanent flow rate — the highest flow the meter is built to handle continuously. R is the ratio between Q3 and Q1, the minimum flow at which the meter must still measure within its permitted error. So R is a range, not a quality badge: R = Q3 ÷ Q1.
Work one through. On a meter with Q3 of 4 m³/h and an R of 160, the minimum flow is 4 ÷ 160 = 0,025 m³/h — about 25 litres an hour. Below that, the meter is not obliged to be accurate. Take the same Q3 with R80, and the minimum doubles to 50 litres an hour.
That difference is where estates quietly lose water. A slow leak, a dripping cistern, a tap that never quite closes — these are low-flow events. A meter with a narrow range registers a proportion of them as nothing at all. The water leaves the system and never appears on anyone’s bill, which is exactly the gap that shows up later as unaccounted-for water.
The error limits themselves are banded by flow zone rather than being a single figure. In the upper zone, between Q2 and Q4, Class 1 permits ±1% and Class 2 permits ±2%. In the lower zone, between Q1 and Q2, the permitted error widens to ±3% and ±5% respectively. A meter is therefore allowed to be least accurate exactly where leakage lives.
If your reason for metering is leak detection rather than billing, the R value matters more than the accuracy class. Specify the range first.
Flow definitions and error bands per ISO 4064-1 and OIML R 49-1. Confirm the edition and the class permitted by your local metrology authority before ordering.
Interoperability: the clause that decides if you can ever change supplier
The most expensive thing in a metering system is not the meters. It is being unable to replace them.
An estate that buys a proprietary system discovers the position three or four years later, when a batch fails, or the head-end software licence is renewed on new terms, or the supplier exits the market. At that point the meters are fine and the estate still has no options, because nothing else speaks the protocol.
The protection is a specification clause, written before purchase, requiring an open and documented data model and communication protocol — the IEC 62056 series, known as DLMS/COSEM, is the reference point in electricity metering. It does not guarantee that two vendors’ meters behave identically. It does mean the data model is public, so a second vendor can be integrated without the first one’s cooperation.
Three questions settle it before you order:
- Which protocol and profile, exactly? Named in the contract, not described as “open standard” in a brochure.
- Who owns the data, and in what format can you export it? If the answer is a report rather than a file, you do not own it in any useful sense.
- What happens to the head-end software if the relationship ends? Licence terms, data export, and whether the system keeps working.
None of these are technical questions. They are commercial ones, and they are much cheaper to ask before the order than after.
What we will tell you not to buy
If the building has no one who will own the data — no facilities manager, no billing process, no agreed routine — then a full smart metering deployment will not deliver what the business case promised, and we will say so rather than ship it.
In that situation the better answer is usually smaller: meter the boundaries that actually get billed, get the data into one place someone already opens, and expand once the routine exists. A partial system in use beats a complete system nobody reads.
Questions buyers ask
What accuracy class do we need?
It depends on whether readings will be used for billing, for internal management, or for statutory purposes — and the requirement is set by the rules of your market. Confirm the applicable standard for your jurisdiction and specify to it; do not accept a bare percentage.
Wired or wireless?
A site question. Wireless saves installation cost and is affected by structure, distance and interference. Wired is more predictable and more disruptive to retrofit. On most real buildings the answer is a mix, decided by survey.
Can we integrate with our existing BMS?
Usually, if the protocols are open and documented. Ask for the integration method in writing at tender stage rather than discovering it at commissioning.
What happens when a tenant disputes a reading?
Whatever your contract says — which is why the verification and calibration route should be written down before the first bill is issued, not after the first argument.
What should we send for a quotation?
Single-line diagrams or service layouts, the number and type of points, what the data is for, and what system it must reach. Those four give you a real number instead of an indicative one.
Where to go next
Tell us what the data is meant to change — billing, losses, consumption — and send the service layout. We will come back with a specification built around that outcome, and say plainly where a smaller system would serve you better.
Request a quotation, or read about what we supply and how we handle quality and documentation.