Utility systems integration, starting at the meter
We work on the interfaces between head-end systems, meter data management, outage management and billing — where utility data most often goes wrong, and where it is hardest to see that it has.
- HES & MDM
- OMS & ADMS
- CIS and billing interfaces
- Event-driven integration
- Kafka, MuleSoft, Azure Integration Services
What we do
AMI & Meter Data Integration
Head-end to downstream: interval and register data, event streams, validation and reconciliation across meter types and vendors.
ESB Integration
Governed, observable integrations for mission-critical flows between CIS, OMS, AMI and customer channels.
Solutions Design & Architecture
Current-state mapping, target architectures and phased roadmaps for utility operations.
Cloud Integration
Secure connectivity and event streaming between on-premise OT/IT systems and cloud platforms.
DevOps & Platform
Automated delivery pipelines, infrastructure as code, and standardized environments.
Support & Continuous Improvement
Ongoing support scoped to the engagement — runbooks, monitoring and iterative improvement.
The problems live between the systems
A corrected reading is re-sent from the head-end. It carries the same meter, the same timestamp, a different value. Downstream, a straightforward de-duplication rule treats it as a repeat and discards it. The correction never arrives, nothing reports an error, and the original figure stands.
Failures of this kind are ordinary, quiet and expensive. They are rarely defects in any one system. They live in the assumptions each system makes about the others.
More patterns like this
How we work
- Assess. Current-state mapping across CIS, OMS, AMI and SCADA interfaces, and where the assumptions between them break.
- Design. Target architecture, integration patterns, security and governance.
- Implement. Iterative delivery with automated testing and observability.
- Support. Runbooks, documentation and continuous improvement.