DLMS/COSEM and IEC CIM: how the two standards fit together
Two layers of interoperability
DLMS/COSEM standardises the data inside the meter, using OBIS identifiers for every value and event.
IEC CIM standardises how enterprise systems such as MDMS, HES and work management exchange information.
Why operations needs both
An operations layer reads vendor-specific events, normalises them using DLMS/COSEM semantics, and publishes them to the rest of the utility using CIM messages. That is what removes the per-vendor integration tax.
How smoc.cloud helps
DLMS/COSEM tells you what a meter holds and IEC CIM tells systems how to exchange it. smoc.cloud bridges the two, so data keeps its meaning from the meter to the enterprise.
- Spot it
Catch mapping and data issues
smoc.cloud checks that OBIS objects arriving from meters map cleanly to CIM messages, and flags missing, malformed or mismatched values.
- Find the root cause
Trace a bad value to its origin
When a downstream system receives the wrong data, lineage through the information model shows whether the cause is the meter profile, the head-end or the integration mapping.
- Fix it
Standard interfaces, fewer custom fixes
A single information model with standard CIM and MultiSpeak interfaces removes one-off point-to-point mappings that break with every new meter type.
IEC 61968-9 messages let your operations layer talk to MDMS, outage and work management systems in one predictable way, which keeps network events and meter events on the same page.
DNOs: how smoc.cloud helpsOne email a month with new articles, whitepapers and field notes on running smart metering estates. Unsubscribe at any time.











