Why utility integration is 70% SAP and 30% everything else
For E-On Delgaz Grid we connected SAP IS-U, smart metering, GIS, OMS and ADMS on one service bus — 25 sub-projects, 95+ XSLT transformation templates, canonical models synchronized across every operational system. The surprising part wasn't the scale. It was the nomenclatures.
The landscape
SAP IS-U at the core. A Head-End System for smart metering readings. A separate AMR for gas. ADMS for distribution management. OMS for outages. GIS for infrastructure. DMS, MDM, CPT, customer portal. Each with its own vendor, release cycle, data model. Not one big system — an ecosystem.
The dominant pattern
Scheduled task → fetch from HES → transform → enqueue in JMS → consume via SAP BAPI/RFC. Repeated with variations across dozens of flows. JMS with DLQ for messages that can't reach SAP during upgrades. None of this is exotic. All of it has to be right.
The canonical model for nomenclatures
Equipment types, locations, plants, work centers, cost centers, classes. One definition between SAP and the operational systems. Not SAP plus an alias in GIS plus another in OMS. One master, controlled propagation. We are talking about tens of thousands of records, not dozens.
The outage flow
Field event → OMS web event → GIS correlation (which streets, which transformers, which customers affected) → customer portal notification. Everything under a correlation ID. When someone asks "how many customers were affected between hour X and Y?", there is an instant answer — not a weekly report.
Regulatory reporting
Periodic exports to ANRE and other regulators. Automatic retry when the destination is unavailable. Fault handler per flow — one error doesn't stop the rest. Auditable per record, not per file.
Operational realities
JMS with DLQ for messages that can't be delivered to SAP during upgrades. Each flow with its own retry, back-off, dead-letter behaviour. When SAP returns, the queue drains in order. When it doesn't return in time, the operator knows exactly what has accumulated.
What gets underestimated
Nomenclature synchronization takes more effort than the business flows. Because an error here corrupts every downstream report — financial, operational, regulatory. Nomenclature consistency is the invisible work that keeps everything else standing.