SMaaS vs Utility-Owned AMI: Which Model Creates More Value?
Comparing capital investment, operational responsibility, scalability and risk between ownership and service models.
"Which model creates more value?" is really the wrong first question. Ownership and service don't make the same underlying costs and risks cheaper or more expensive — they distribute those same costs, risks and control differently across time, and across two organisations instead of one.
A utility that owns its AMI estate carries the capital, the technology risk and the operational workload — and keeps full control over every decision along the way. A utility using SMaaS trades a share of that control for a provider absorbing a share of the capital, the technology risk and the day-to-day operations. Whether that trade creates more value depends entirely on what the utility already has, and what it's trying to become.
This briefing compares the two models across four dimensions most business cases skip past too quickly: capital investment, operational responsibility, scalability and risk.
Front-loaded vs level
The most visible difference is also the most misleading one if it's the only thing compared. Utility-owned AMI concentrates spend up front — meters, network infrastructure and system integration are largely capital expenditure, financed and depreciated over the asset's life, with a further capital spike typically arriving mid-life for a technology refresh. SMaaS converts that same capability into a recurring operating cost, level or close to it from the first month, with the provider financing the underlying assets.
Figure 1. Illustrative shape, not a forecast for any specific programme — the pattern is consistent: ownership front-loads cost and spikes again at refresh; SMaaS levels it into a recurring fee.
Level opex is easier to plan around and doesn't compete with other capital projects for approval — but it rarely removes the total cost, it relocates it, and usually adds the provider's margin and financing cost into the ongoing fee. The comparison that matters isn't "which is cheaper" in isolation; it's which cost profile better matches the utility's financing position, regulatory allowance structure and appetite for a large up-front commitment.
Who runs the estate day to day
Capital structure gets the attention in board papers; operational responsibility is where the difference actually shows up in day-to-day work. The two models don't just redistribute cost — they redistribute headcount, expertise and daily decision-making across very different categories of activity.
Figure 2. Billing and regulatory compliance stay predominantly with the utility in both models. Everything closer to the network and the field tends to move furthest toward the provider under SMaaS.
That pattern also tracks where specialist technical expertise — RF planning, module firmware, field logistics at scale — is hardest for a utility to build and retain in-house, which is often the real driver behind an SMaaS decision, more than the headline cost comparison.
Growing, shrinking and changing shape
Ownership ties the pace of estate growth to internal capital-approval cycles and procurement lead times. Adding capacity, absorbing an acquired territory, or responding to a policy-driven acceleration — a faster EV rollout, a new low-carbon heating mandate — means competing for budget and running a new deployment programme each time. SMaaS is usually structured to flex with contracted volume, letting a utility scale up or down inside an existing commercial relationship rather than launching a new capital project every time the estate's shape changes.
That elasticity cuts both ways, though. A utility that later wants to bring metering back in-house — after a merger, a change in regulatory strategy, or simply reaching a scale where ownership becomes more economical — finds that unwinding a SMaaS contract and migrating a live, multi-year estate is its own significant undertaking, not a simple off-switch. Scalability under SMaaS is real, but it's scalability within the relationship, not scalability out of it.
Where it actually sits
Risk is the dimension both models claim to handle well, and the one worth the closest look — because it doesn't disappear under either model, it just finds a different owner.
Notice what doesn't move: regulatory accountability for metering accuracy and data protection stays with the utility under both models, because in most jurisdictions the utility — not its service provider — is the regulated entity. Any SMaaS evaluation that treats compliance risk as fully outsourced is evaluating the wrong thing.
So which creates more value?
Value depends on fit, not on a universal winner. Four questions tend to point toward one model or the other:
Capital position
Ownership tends to suit utilities with ready capital access and stable regulatory allowance for capex; SMaaS tends to suit utilities where capital is constrained or better deployed elsewhere.
Operational capability
Ownership suits utilities with — or building — strong internal network-operations and field-logistics capability; SMaaS suits utilities that would otherwise build that capability from scratch for one programme.
Growth trajectory
Ownership suits a stable, well-forecast estate; SMaaS suits an estate expecting significant, uncertain or fast-changing growth.
Risk appetite
Ownership keeps control and risk together; SMaaS separates them — value depends on whether the utility would rather manage the risk directly or manage the provider that's managing it.
Neither model is inherently more valuable — they're two different bets on where control, capital and risk should sit over the life of an AMI programme. The utilities that get the most value from either choice are the ones that made it deliberately, against their own capital position, operational capability and growth trajectory — not the ones that treated it as a procurement formality decided by price per meter.
How a read moves across the estate
HOVER OR TAP A STAGE TO EXPAND TECHNICAL SPECS
Matching the model to the utility
Ownership and service aren't better or worse; they fit different utilities. A large utility with an established asset-management capability, cheap capital and a long asset horizon often captures more value owning. A smaller utility, or one whose core competence is customer service rather than field operations, often does better buying the outcome.
The wrong choice isn't a model — it's a model mismatched to the utility's actual capability and balance sheet.
- 01
- 02
- 03
- 04Energy Industry Practice — Energy UK
Chris Gales
Chris Gales leads CEHG. He converts complex technical and commercial choices into clear decisions and dependable outcomes for utilities running connected device estates at scale.
He writes these field notes from the practice — on bearer migration, smart metering architecture, procurement and operations — to help estates start counting down early.