Platform

Deep enough for the engineer. Clear enough for the board.

Ten capability areas built on one normalised estate model. Each one pairs the operational benefit with the technical proof behind it.

01estate

Device & estate management

Know exactly what is installed, where, and in what state — from commissioning through exchange, replacement and inventory — without reconciling vendor exports.

technical_proof
  • Meters, gateways and repeaters modelled as first-class devices with service-point relationships
  • Cellular and comms session history per device
  • Lifecycle states: commissioning, in service, exchange, replacement, inventory
  • Per-tenant estate segmentation
smoc · estate
devices
estate
service_points
linked
comms_sessions
24h
lifecycle
5 states
device_idtypelifecycle
MTR-E-04481Electricity · 3-phasein_service
MTR-G-11920Gasin_service
GW-0027Gatewayexchange_pending
MTR-W-30014Watercommissioning
RPT-0009Repeaterinventory
ENTITY: device · lifecycle=in_service

Illustrative UI fragment — not live product data

01 / 10
capability_stack

One estate model. Ten capability areas.

Every capability area works on the same normalised device, register and event model — so adding a vendor, a head-end or a new utility type never means rebuilding your operations platform.

Regulator-ready KPIs
One audit trail
Fewer truck rolls
device_estate
hes_layer
alerts
kpi_sla
campaigns
field_ops
network
security
commands
soc
normalised estate model
DLMS/COSEMCIMMultiSpeakOBISIEC 62056
Core advantages

Fewer integrations to run, cleaner data to bill from

smoc.cloud sits above the head-end systems you already operate, so integration work stops multiplying and data problems surface while they are still cheap to fix.

Streamlined HES integration

  • One connector per head-end system — no per-vendor tooling for your operations team.
  • DLMS/COSEM, CIM and MultiSpeak normalised into a single estate model.
  • New meter families and HES versions onboarded without rebuilding workflows.
  • Live integration health, with retries and backlogs visible per endpoint.

Better data quality

  • Missing reads, duplicates and clock drift detected at ingest, not at billing.
  • OBIS-level validation so registers mean the same thing across vendors.
  • Gap tracking to closure, with re-read commands issued from the same console.
  • Append-only audit trail behind every correction, ready for SLA evidence.
Frequently asked questions

Common questions about the platform

What programme directors and architects ask before a first conversation.

next_step

Want to see it on your vendors' traffic?

Bring the head-end systems and meter vendors you run. A demo is more useful when it is about your estate.