A utility meter is deployed once and expected to be right, connected and honest for the better part of two decades. That makes it a metrology device, a low-power radio and a security endpoint at once — all on a single cell that must outlive several phones.
DomainConnected product, utility metering
PlatformsConnected Edge
ScopeMetrology to secure long-life endpoint
Binding constraintAccurate, connected and honest for many years on one cell
DisclosureRepresentative programme; customer not named
CONTEXT
Where this started.
A smart metering endpoint measures consumption, reports it over a network, and does so unattended for many years. Once installed in the field it is rarely touched, so it has to be right the whole time, reachable the whole time, and resistant to tampering the whole time — on a battery that cannot be changed on a routine visit.
Each requirement is real. Metrology has to stay accurate over years and temperature. Communication has to reach a concentrator over a long-range, low-power bearer from awkward locations — basements, cabinets, undergrounds. Security has to protect both the reading and the endpoint, because meters touch revenue. And every microamp matters, because the battery has to last the deployment.
So the endpoint is engineered across all four: stable metrology, a low-power long-range radio, tamper and security by design, and an energy budget measured in microamp-hours against a decade-plus life.
CHALLENGES
4 problems, named.
Stated before any of them had an answer.
01
It must last the deployment
A meter that needs a battery change is a truck roll to every home; the energy budget has to stretch across many years on one cell.
02
Metrology must not drift
The reading is the product and touches revenue; accuracy has to hold over years and temperature, not just at calibration.
03
It reports from bad places
Meters sit in basements, cabinets and pits; the radio has to reach a concentrator over a long-range, low-power bearer from poor locations.
04
It is a revenue target
Because meters touch money, both the reading and the endpoint have to resist tampering and spoofing.
ARCHITECTURE
How it was built.
Reading a meter is trivial; being accurate, reachable and honest for two decades on one cell is not. The endpoint is a metrology, radio and security device at once.
CONTRIBUTION
What Faststream did.
The scope of the work, rather than a capability list.
Stable metrology — measurement that stays accurate over years and temperature, not just at the calibration point.
Low-power long-range radio — reaching a concentrator over an LPWAN bearer from basements and cabinets.
Energy budget — a microamp-hour accounting that stretches a single cell across a decade-plus deployment.
Tamper evidence — detecting and recording interference, because the meter touches revenue.
Endpoint security — protecting the reading and the device against spoofing and manipulation.
Field management — remote configuration and monitoring across a large, long-lived fleet.
WHAT WAS HARD
The parts that consumed the schedule.
Rarely the subsystem that sounds difficult.
01
Life on one cell
Stretching a single battery across the deployment is the defining constraint; every wake, every uplink is an energy decision.
02
Accuracy that lasts
Keeping metrology within tolerance over years and temperature drift, without a service visit, is harder than a bench calibration.
03
Reaching from a basement
The link budget from the worst installed locations to the concentrator sets the radio design; the easy locations are not the concern.
04
Security on revenue
Because meters touch money, the security has to be real and hold in the field for the whole life of the device.
OUTCOME
What resulted.
Lasts the deployment
Many years on a single cell, validated against a real energy budget.
Accurate for years
Metrology that holds tolerance over time and temperature.
Reaches the concentrator
A radio that reports reliably from basements and cabinets.
Honest and secure
Tamper-evident, secured metering that protects the reading and the endpoint.
Confidentiality
Customer projects are presented at property, capability, outcome and integration level. Customer names, internal architecture, confidential deliverables and commercial terms are not disclosed. Where a detail would identify a customer it is omitted rather than approximated. More is available under a non-disclosure agreement, within the limits the customer has agreed.
Why is battery life the defining constraint for a meter?
Because a smart meter is installed once and expected to run unattended for the better part of two decades, and its battery usually cannot be changed without an expensive visit to every location. That makes the energy budget the master constraint: every wake, every measurement and every uplink is an energy decision, and the whole design is shaped by the need to stretch a single cell across the entire deployment while still measuring and reporting reliably.
02
Why is metrology accuracy over time so important?
Because the reading is the product and it touches revenue. A meter that is accurate at calibration but drifts over years or with temperature produces bills that are wrong, which is unacceptable to both the utility and the customer. Keeping the measurement within tolerance across the whole deployment, unattended and without a service visit, is a harder problem than a one-time bench calibration and is central to the endpoint's design.
03
Why does a meter need security?
Because it sits at the boundary of money. Both the reading and the endpoint are targets: an attacker might try to falsify consumption, spoof the device, or tamper with the meter physically. So the endpoint is designed to detect and record tampering and to protect the integrity and authenticity of its data, and that protection has to hold in the field for the full multi-year life of the device, not just at commissioning.