All resources
Blog · 5 Nov 2026 · 5 min read · smoc.cloud team

Three protocols and two dashboards is not visibility

When 40,000 meters go dark overnight, the real risk is not the outage. It is how long it takes to see it across disconnected tools.

The typical setup

Most utility operations teams run some version of the same stack: one tool for protocol ingestion, another for field service and a spreadsheet holding the rest together.

It works on a quiet day. It breaks when something big happens.

When 40,000 meters go dark

Picture an overnight event that takes tens of thousands of meters offline. Someone has to log in to three systems, export data, line up timestamps and work out whether it is a network fault, a head-end issue or a firmware problem.

That delay is the real risk. Not the outage itself, but the time it takes to see it happening.

What one operations view changes

  • One login instead of several vendor consoles
  • One timeline that orders events from meters, networks and head-end systems
  • One picture of the estate, whether you run under 100k meters or over 1M
  • Faster root cause, because correlated events point to the shared cause

Visibility is not the number of dashboards you have. It is how quickly you can answer: what is actually happening right now?

See your whole estate

smoc.cloud brings ingestion through to field management into one operations view. Request a demo to see your whole estate, not just the parts your current tools can reach.

How smoc.cloud helps

When an estate runs on several protocols and vendor consoles, outages hide in the gaps between them. smoc.cloud brings every vendor, network and head-end into one operational view.

  1. Spot it

    See the whole estate at once

    Meters from every vendor and protocol appear on one live view, so 40,000 meters going dark is visible in minutes, not after the morning reports.

  2. Find the root cause

    Find the common cause across tools

    Events from different head-ends and networks are correlated, so a dropout spanning two systems is traced to one shared cause instead of being investigated twice.

  3. Fix it

    Coordinate one response

    One incident, one owner and one timeline replace parallel investigations, with status shared across operations, network and field teams.

What this means for you

Mixed PLC, RF mesh and cellular networks are where blind spots hide. One timeline across them cuts the time to locate network-wide events.

DNOs: how smoc.cloud helps
The Metering Operations Brief

One email a month with new articles, whitepapers and field notes on running smart metering estates. Unsubscribe at any time.

Join the conversation on LinkedIn

Open on LinkedIn
Nov 18, 2026

Customers never see your head-end. They see their bill. A commissioning that stalls. A meter that quietly stops reading. A register that drifts. None of it reaches the customer straight away. Weeks later it arrives as an estimated bill and a call to the contact centre. Our new whitepaper follows five moments that shape the customer experience, from installation to support, and shows where operations decide whether each one goes right. Which stage generates most of your metering complaints? #CustomerExperience #SmartMetering #Utilities

Nov 18, 2026

Two meters. Both fully DLMS/COSEM compliant. Different object lists, different event codes for the same power failure, different load profile settings. Compliance gives you a common language. It doesn't give you a common vocabulary. That's the gap the DLMS UA Generic Companion Profile closes: standard objects and behaviours that every model implements the same way. Fewer custom integrations, faster onboarding of new models, less lock-in. Our new whitepaper explains what it means for the metering business, not just the engineers. #DLMS #SmartMetering #Standards

Nov 17, 2026

If you're a utility lead, your IT and compliance teams will ask about security before you ever get to features. They should. Metering platforms touch critical infrastructure and customer data. A good demo answers the hard questions early: how the platform is secured, how it handles compliance, how it fits protocols you already run. What's the first question your IT team asks about a new platform? #UtilityOperations #SmartMetering #CyberSecurity

next_step

See your estate in smoc.cloud.

A demo walks through your utility types, your vendors and your compliance obligations — not a generic slide deck.