The phrase “IoT in utilities” covers two distinct categories of device that have very different data paths and different destinations in the software stack. Conflating them produces a blurry picture. This article separates them and follows each data flow to its destination.
Category One: Advanced Metering Infrastructure
AMI devices, primarily electric meters from Itron and Landis+Gyr, are the largest-scale IoT deployment in the utility industry. A US investor-owned utility serving a few hundred thousand customers may have millions of interval meter reads arriving every 15 minutes. That volume cannot land directly in a CIS.
The data path works like this:
- The meter reads consumption and stores interval data locally.
- RF mesh (Itron OpenWay, Landis+Gyr Gridstream) or cellular backhaul carries reads to the AMI head-end system.
- The head-end forwards interval data to the Meter Data Management system. Oracle MDM (part of Oracle Utilities) and SAP MDG-U are the dominant platforms at large utilities; some Cayenta CIS sites use lighter MDM connectors within the Harris Computer ecosystem.
- The MDM performs Validation, Estimation, and Editing (VEE): checking for missing intervals, flagging meter tamper events, and filling short gaps with approved estimation algorithms.
- Clean, validated consumption data posts to the CIS, where SAP IS-U or Oracle CC&B picks it up to generate bills.
The MDM is the most often underestimated component in AMI rollouts. Projects that go straight from head-end to CIS without a proper MDM layer frequently struggle with billing accuracy. See our Oracle Utilities overview and SAP IS-U guide for how each platform handles the MDM integration.
Category Two: Grid Sensor and Distribution Automation Devices
Distribution automation equipment includes smart reclosers, capacitor bank controllers, line sensors, and substation IEDs (intelligent electronic devices). These do not feed the billing system. Their data destination is the SCADA/EMS layer or, increasingly, the ADMS.
GE Vernova GridOS and Schneider Electric EcoStruxure Grid both ingest this telemetry for fault detection, isolation, and restoration (FDIR) and for volt-VAR optimization. Communication protocols are predominantly DNP3 over serial or IP and IEC 61850 for modern substation automation. This data path is entirely separate from the AMI-to-MDM-to-CIS flow.
Customer outage notification is the integration point that bridges the two domains. The ADMS detects a fault and identifies affected customers using the GIS network model; it then passes outage records to the OMS. The OMS or the CIS triggers customer notifications via SMS, IVR, or a customer portal.
Water and Gas Sensor Applications
Water utilities deploy pressure and flow sensors throughout distribution networks to detect non-revenue water loss. These sensors feed supervisory control systems and, in more modern implementations, asset management platforms. The CIS still handles billing, but it receives water consumption from AMR/AMI devices using a similar head-end and MDM pattern as electric metering.
Gas distribution automation uses electronic pressure regulators and leak detection sensors whose telemetry goes to SCADA, not the CIS directly.
Predictive Maintenance: A Real Benefit With Realistic Scope
Vibration and temperature sensors on rotating equipment (pumps, compressors, transformer cooling fans) generate condition data that feeds predictive maintenance workflows. SAP PM (Plant Maintenance) and IBM Maximo are the common destinations. The value is real: catching a bearing failure before it causes an unplanned outage is straightforward to quantify. What requires caution is the assumption that every sensor feed is immediately actionable. Building the analytics layer to turn raw vibration data into a reliable maintenance trigger takes time and domain expertise.
The Integration Challenge
The diversity of protocols, head-end systems, and MDM platforms makes IoT integration in utilities one of the more complex middleware problems in industrial software. SAP IDocs, Oracle SOA-based web services, and REST APIs all appear in the same integration architecture depending on system age. Before adding new sensor sources, map the existing data flows from device to application. The question is rarely “can we collect this data?” and more often “where does it land, and who maintains the integration?” AvanSaber advises utilities on these integration architectures.