Not a generic IoT dashboard with smart-meter branding.
smoc.cloud wasn't built by people who simply understand smart metering protocols. It was built by people who have written and implemented them. That first-hand knowledge of DLMS/COSEM, CIM and MultiSpeak is engineered into the platform. smoc.cloud understands the devices, objects, events, relationships and operational context behind the data, turning information from across the complete device estate into actionable intelligence. Fewer tools. Faster diagnosis. Fewer surprises. Better operational decisions. And evidence you can confidently put in front of a regulator.
Vendor-agnostic, unified operations
One platform integrates across the entire smart metering stack — HES, MDMS, billing, GIS, ADMS and cellular connectivity — ingesting real DLMS/COSEM, CIM and MultiSpeak traffic from multiple vendors at once. Adding a new MDMS or billing vendor is a connector, not a platform rewrite.
Real visibility, not vanity metrics
Read-success and online-percentage KPIs are computed from actual device-reporting data — never static or seeded numbers — backed by a configurable KPI catalogue, live SLA dashboards, escalation policies, breach tracking and a complete audit log. When the regulator asks, the evidence already exists.
True multi-tenant isolation
Every table holding tenant data is protected by row-level security enforced at the database layer, not just in application logic — so one tenant's data genuinely cannot surface in another's queries, even if a route has a bug. Severity rules, KPI thresholds and roles are configured per tenant on one platform.
Granular, auditable access control
A permission catalogue of 90+ distinct keys — not just admin/viewer — lets a tenant define exactly who can view a connector, who can acknowledge an exception and who can issue a command that changes something in the field. Consequential actions like remote disconnect and MDMS commission/decommission are deliberately separated from routine ones.
Field-to-office continuity
Job dispatch, ticketing and escalation live in the same platform as connector and device data: alerts become triage cases, cases become field jobs, firmware findings become campaigns. Operators stop jumping between a monitoring tool and a separate work-order system.
Global-ready out of the box
The UI supports 35 languages, including right-to-left, with tenant-level language restrictions — built for utilities and integrators operating across multiple countries, regions and regulatory regimes.
Security built in, not bolted on
Secrets are managed through a dedicated vault with fail-closed behaviour — the system refuses to start rather than run with a required secret missing. Credentials are encrypted at rest, and every write against tenant data passes the same RLS and permission gate.
Built for scale and reliability
The architecture accounts for Kafka-based ingestion, connection-pool safety around outbound vendor calls, and a migration and RLS test discipline that catches tenant-isolation regressions before they ship.
Fewer truck rolls, caught before they're needed
Per-device read-success and connector-health are computed continuously, so degraded meters surface on the estate heatmap and in alerts on day one — not three billing cycles later. Each field visit costs tens of pounds in technician, vehicle and scheduling overhead, so catching read failures early across a large fleet is one of the most directly quantifiable ROI levers a metering operations platform offers.
Utilities, integrators and vendors.
Three kinds of organisation run smoc.cloud — for three different reasons.
Electricity, gas, water and heat utilities replacing one-tool-per-utility with a single operations platform they can prove compliance from.
Integrators who need an operations layer above the hardware and head-ends they deploy — configurable per client, isolated per tenant.
Vendors who want their devices and head-ends operated well alongside everyone else's, through standard DLMS, CIM and MultiSpeak interfaces.
Every system in the stack, normalised into one operational picture.
Data arrives from the head-end systems, bearer management platforms, MDMS, ADMS, GIS, SIEM and billing systems already in your estate. smoc.cloud normalises all of it into a single overview, lets operations act on that overview, and records every action as evidence.
From vendor exports to one operations platform.
A staged route that starts with the head-ends you already run and ends with compliance you can prove from live data.
Connect the head-ends you already run
Normalise devices, registers and events
Run operations from one screen
Prove compliance from live data
ROI calculator
Model the annual field cost your estate can avoid with remote fault resolution.
See your estate in smoc.cloud.
A demo walks through your utility types, your vendors and your compliance obligations — not a generic slide deck.