Software for the operators who keep the grid, the plant and the pipeline running
Energy & Utilities Software Development
An energy or utility operator runs some of the oldest control systems and some of the newest meters in any industry, and rarely trusts the data between them. This practice builds the grid, asset, field and metering software behind that operator. The asset record agrees with the map, the crew captures the job on site, and interval data reaches billing intact.
01Start from the network, not the software
Name where the record breaks first.
Energy buyers describe a break rather than a product. An asset the EAM, the GIS and the crew each describe differently points one way. A permit written up after the shift, or historian data nobody will let out of the control network, points elsewhere. Naming the break settles the route before a platform is chosen.
Work orders, network geometry and inspection findings describe the same pole, valve or transformer differently.Integration keeps the EAM, GIS and mobile records in step, and the data practice builds the governed asset register they all read from.
Inspections, switching steps and permits are written up after the crew returns, if the paper survives the shift.A field application captures the job where it happens and holds it until the network returns, and custom development covers the permit and scheduling logic no vendor product has.
Smart meters deliver readings the settlement and billing stack was never built to take.Data engineering lands, validates and estimates interval data at scale, and custom development rebuilds the billing and settlement steps that choke on it.
SCADA and historian data stays locked behind the OT boundary because nobody trusts the path out.IoT engineering builds the authenticated, one-way path from historian to cloud, and security engineering designs the zones and conduits it crosses.
Asset & Work Management Integration
EAM, CMMS and GIS kept in agreement about every asset and work order.
Field Operations & Inspection Apps
Switching, inspection and permit-to-work captured by the crew, offline until the signal returns.
Metering & Billing Data Platforms
AMI, MDM, settlement and interval data engineered into one governed pipeline.
OT/IT Integration & Monitoring
SCADA and historian data brought to the cloud across a boundary designed to IEC 62443.
02The boundary as a design input
Built for the control network, the crew and the regulator.
Utility software fails at the edges an office system never meets. A reading must cross from the OT network without opening a path back, and a crew must record a switching step in a basement with no coverage. A regulator will ask for that record years later. The delivery process settles those conditions as architecture before the first screen is designed.
Map what the regulator and the dispatcher will ask for
Which asset, outage and metering records must exist, and who signs them off, is settled first, so the data model produces them rather than reconstructs them.
The record before the interfaceDesign the data path out, never a path back in
Historian and SCADA data crosses to the cloud through zones and conduits designed to IEC 62443, with nothing on the IT side able to write towards the control network.
Architecture that respects the OT boundaryValidate underground, in the yard and on the tower
Field applications are tested in the places coverage disappears, because a switching step recorded late is a safety event, not a data-quality issue.
Tested where the crew actually worksShip outside storm season, with rollback rehearsed
Changes to outage, metering and dispatch systems land in agreed windows behind a staged rollout, so a bad release never coincides with a peak-demand event.
A release the network can absorb
03Services for energy and utility operators, with the standards behind each
Find the utility service you came for, and the standard it must speak.
An operator searches for a named system: an EAM integration, a field-service app, a meter data platform. This ledger sets each beside the deliverable behind it, the standards and integrations it must honour, and the practice that owns the work. The four standards beneath govern how substation, asset and market data is modelled, exchanged and protected.
| What you need | What we build | Standards and integrations | Where it lives |
|---|---|---|---|
| Asset management integration | EAM, CMMS and GIS connected so every asset, work order and inspection reads from one governed record | IBM Maximo and SAP PM APIs, Esri ArcGIS Utility Network, CIM (IEC 61968) asset models | System Integration |
| Field service and inspection | Offline-first crew application for inspections, switching, permit-to-work and defect capture at the point of work | Offline sync with conflict resolution, GPS and photo capture, permit-to-work records, WCAG 2.2 | Mobile App Development |
| Metering and billing data | AMI and MDM pipelines that land, validate and estimate interval data before settlement and billing consume it | AMI head-end APIs, VEE rules, settlement and market-message formats, MDM integration | Data Engineering |
| Outage and grid operations data | Outage, switching and network-state data unified from SCADA, OMS and ADMS into one operational record | IEC 61850 and IEC 60870-5-104 context, CIM (IEC 61970) network models, OMS and ADMS APIs | Data Integration |
| Renewables and DER monitoring | Telemetry from wind, solar, storage and distributed resources brought into one monitoring and forecasting platform | OPC UA, AVEVA PI historians, MQTT, IEC 61850 context, inverter and SCADA vendor APIs | IoT Development |
| Legacy modernisation of operator systems | Ageing billing, outage and asset systems changed in reversible stages without a service interruption | Strangler migration, CIM-aligned data models, IEC 62443 zoning kept intact through every wave | Legacy Modernization |
IEC 61850 and IEC 60870
The substation automation and telecontrol standards behind protection, control and SCADA communication. Integration work reads their data models as context, so operational data arrives with its meaning rather than as raw points.
OPC UA and AVEVA PI historians
The vendor-neutral protocol and the historian most operators already run. Pipelines read equipment and process data through them, with authentication and encryption in the path, rather than asking a plant to change how it stores telemetry.
CIM (IEC 61968 and IEC 61970)
The Common Information Model for utility asset, network and market data exchange. Asset registers and integration contracts are drawn against its classes, so EAM, GIS and operations systems share one vocabulary.
IEC 62443 and NERC CIP context
The industrial security series defines the zones, conduits and levels every OT-to-IT path here is designed to. For US operators subject to NERC CIP, the architecture supports the compliance programme; certification remains the operator's own.
04Evidence and proof
Networks and sites that kept their record.
Energy proof has to hold up in a regulatory audit and a storm restoration, not in a demo. These previews show the standard while the two referenceable projects are written up for client approval.
Explore case studies
Every substation reporting into one asset record without a control-network change.
A distribution utility held asset data in an EAM, a GIS and a set of crew spreadsheets that never agreed. An integration layer built against CIM models gave planning, operations and the field one governed register, with the OT boundary left untouched.
- Asset systems in agreement
- Every substation, one feed
- Control-network changes required
- None
Wind and solar telemetry brought into one monitoring platform the operations team trusts.
A renewables operator watched each site through its own vendor portal and reconciled output by hand. Historian and inverter data was landed through OPC UA and MQTT into one governed platform, so forecasting and availability reporting ran from a single feed.
- Sites monitored from one platform
- All, one feed
- Manual output reconciliation
- Retired
They asked about the OT boundary before they asked about the dashboard. Nobody else did.
Sample · pending client approval
05Four doors into energy and utilities engineering
Enter through the practice that fits the break.
Energy work usually begins at one of four doors. Connect the asset systems that disagree, put a working application in the crew's hands, make metering and operations data trustworthy, or apply AI where the data can support it. Every door runs through the same boundary-first delivery discipline and the same proof standard.
- System Integration
Connect the asset and work systems
EAM, CMMS and GIS integrated through documented interfaces so one governed record serves the office, the map and the crew.
- Mobile App Development
Put the record in the crew's hands
Field-operations and inspection applications that capture switching, permits and defects on site and sync when coverage returns.
- Data & Analytics
Make metering and operations data trustworthy
AMI, historian and outage data engineered into governed pipelines that billing, dispatch and the regulator can rely on.
- AI & Automation
Apply AI to load, outage and inspection data
Load forecasting, outage prediction and inspection-image analysis built with evaluation evidence before any recommendation reaches a control room.
06Straight answers
Asked before a grid technology budget is set.
01Do you integrate with our EAM, CMMS and GIS?
Yes, through the published interfaces of platforms such as IBM Maximo, SAP PM and Esri ArcGIS Utility Network. Replacing a working asset system is rarely the answer; keeping it in agreement with the map and the crew usually is.
02Can field applications work inside a substation with no coverage?
That is the starting assumption. Crew applications hold every inspection, switching step and permit locally, then synchronise when coverage returns and resolve conflicts deliberately. A basement or a rural line loses signal far more often than any test environment does.
03How do you move SCADA and historian data to the cloud safely?
Through a path designed to IEC 62443 zones and conduits, reading OPC UA or AVEVA PI on the OT side and carrying data outward only. Nothing on the IT side can write towards the control network, and the design is reviewed with the operator's security team before a line of code.
04When is an ETRM or energy-management product the better route?
When the need is trading, position management, market risk or packaged building and site energy management. Those are mature product categories, and buying one is usually the right call. This practice builds the operator systems around them, and will say so plainly when a product fits better.
05Do you handle AMI and meter data management?
Yes, from the head-end feed through validation, estimation and editing to the settlement and billing steps that consume interval data. Existing MDM platforms are integrated rather than replaced, and the pipeline is built to keep the billing stack from choking on the volume.
06How is this different from manufacturing or construction software?
This practice serves the operators who run generation, networks, retail energy, oil and gas operations and water. Plant and production systems are served by the Manufacturing practice, and contractors building infrastructure by the Construction practice, each engineered for a different buyer and operating reality.
07Can you support our NERC CIP or other compliance programme?
The architecture is designed so that the operator's compliance programme can be evidenced: segmentation, access control, logging and change records are built in rather than retrofitted. Certification and attestation remain the operator's own; no compliance status is claimed on their behalf.
08How is energy and utilities software work priced?
Against the integration, field and OT surface uncovered during scoping, not a flat industry rate. An EAM integration and an offline-first crew application carry different engineering risk, so the estimate follows the actual work rather than an average.