Building a Utility IoT Strategy Beyond Connectivity
Connectivity is only the first layer. Success requires data, applications, operations and governance working together.
Most utility IoT initiatives can point to a connectivity achievement — meters, sensors, or field devices that now report in. Far fewer can point to a decision that was made, or a cost avoided, because of what that connectivity delivered.
That gap isn't a connectivity problem. It's a strategy problem. Connectivity is the layer that gets funded first, because it's visible, procurable and easy to specify in an RFP. The layers above it — turning a stream of readings into trustworthy data, turning data into applications people actually use, embedding those applications into daily operations, and governing the whole thing as it grows — are harder to specify, easier to underfund, and where most of the real value actually lives.
This briefing sets out the full stack a utility IoT strategy needs, where most programmes stall, and the risks of treating connectivity as the finish line rather than the starting point.
Six layers, one strategy
Connectivity is layer two of six. Everything that actually creates value sits above it.
Figure 1. Devices and connectivity are necessary, but they're the foundation, not the strategy. Data, applications, operations and governance are where value is actually created.
Where most programmes stop
The pattern is consistent across utilities and across IoT verticals, not just metering: near-universal success getting devices connected, then a steep drop-off at every layer above it, because each successive layer requires a different kind of investment — organisational, not just technical.
Figure 2. The drop happens exactly where the required investment shifts from technical to organisational — data quality ownership, workflow redesign, and governance across multiple device types.
What a partial strategy costs the estate
An estate connected without a data or application layer behind it produces volume without insight — more readings, more events, more raw feeds, none of it translated into a decision anyone actually makes differently. Grid-modernisation ambitions in particular depend on layers most connectivity-only programmes never reach: DERMS and voltage-optimisation applications need governed, quality-assured data flowing into operational workflows, not a connectivity achievement sitting in a project closeout report.
It also compounds across device types. A utility that builds a metering-only IoT capability, then separately builds a DER-monitoring capability, then separately again a grid-sensor capability, ends up with three disconnected data and governance models where one, done deliberately, would have served all three.
What's missing above connectivity
Unowned data quality
Raw device data arrives, but no one is accountable for validating, normalising or trusting it before it reaches an application.
Applications with no decision attached
Dashboards and analytics exist, but nothing in the operating model changes as a result of what they show.
Workflows never redesigned
Field and control-room processes built for a pre-IoT world absorb new alerts as noise rather than as new inputs to act on.
Governance built per device type
Metering, DER and grid-sensor IoT each get separate ownership and security models instead of one coherent policy.
No single accountable owner
IoT strategy spans IT, OT and engineering; without a named owner across all three, each layer optimises locally.
Standards fragmentation
Each device category adopts its own protocols and data models, recreating the integration burden discussed elsewhere in this series.
Building the full stack deliberately
Budget every layer, not just connectivity
Fund data, application, operations and governance work explicitly in the original business case, not as a later phase.
Name an accountable owner across IT, OT and engineering
Someone needs authority over the whole stack, not just the layer their department already controls.
Design one governance model for multiple device types
Build data and security governance to extend across metering, DER and grid sensors from the outset.
Attach every new data feed to a specific decision
Before building a dashboard, define what operational or customer decision it's meant to change.
Redesign the workflow, not just the tool
Update field and control-room processes deliberately so new alerts and insights get acted on, not absorbed as noise.
Connectivity answers "can the device talk to us?" It doesn't answer "does that change what we do?" A utility IoT strategy that stops at connectivity has built the easiest layer and left the valuable ones unbuilt. Treated as a full stack from the start, the same investment turns a connected estate into an operational capability.
How a read moves across the estate
HOVER OR TAP A STAGE TO EXPAND TECHNICAL SPECS
The full stack, not the first layer
Connectivity is the layer utilities procure first and think about most, because it's the most visible gap. But an IoT strategy that stops there produces a connected estate with no operating model to use it.
Data governance, application architecture, operations integration and security each need their own owner and roadmap, or the connectivity investment sits underused. The strategy is the stack, not the bearer.
- 01
- 02
- 03Clean Energy for All Europeans — European Commission
- 04
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.