Software and AI for utilities and grid operators
We do utility software development for grid operators, energy suppliers, water companies and installers of heat pumps and solar panels. We connect SAP IS-U, market data and asset systems to the tools your customer service, planning and asset teams work in, and keep operational technology out of reach of anything we build.
Where the work gets stuck.
Connection requests outnumber engineers
Grid congestion means every request for a new or heavier connection needs a capacity check, a queue position and careful communication. Applications arrive incomplete and customers call repeatedly for status.
Customer questions depend on market data
Moving house, meter readings, annual bills and switching all rely on EAN codes and EDSN market messages. When messages are late or wrong, customer service cannot see why and the billing team fixes it by hand.
Asset data lives in separate worlds
Measurements sit in PI historians, work orders in Maximo or SAP, network models in GIS and inspection reports in PDFs, so condition-based maintenance stays a plan on paper.
How we improve energy and utilities.
Each one is scoped around your systems and rules, and each one keeps a person in charge of the decisions that matter.
Connection request handling
Applications are checked for completeness, enriched with EAN, address and grid data, and prepared with a draft capacity assessment for the network planner. Planners decide on the offer, and customers get status updates without calling.
Supplier customer service drafts
Questions about bills, instalments, meter readings and moving are answered with drafts that use contract, meter and market message data from SAP IS-U. Agents review replies, and payment difficulties go to a specialist team.
Outage information line
A voice agent that tells callers whether an outage is known in their postcode, the expected restore time and how to report a new one. Anyone reporting a gas smell or a dangerous situation is put through to the control room immediately.
Installer subsidy and commissioning paperwork
For heat pump and solar installers, quotes, ISDE subsidy documents, commissioning reports and grid registrations are read and checked for missing items before submission. Office staff approve each file.
Asset condition data pipeline
Historian measurements, work order history, inspection results and GIS data joined per asset, on a one-way read from OT systems. Asset managers use it to prioritise inspections and replacements.
SAP IS-U and market message integration
Monitored connections between SAP IS-U and EDSN market processes, CRM and portals, with failed or rejected messages collected in a work queue. Billing specialists resolve the cases the rules cannot.
Built around the rules.
What we design for from the first week. Your legal and compliance people keep the final word.
NIS2 and the Cyberbeveiligingswet
Electricity, gas, heat and drinking water are essential sectors under NIS2. We design for access control, logging, supply chain security and the incident reporting duties the Dutch Cyberbeveiligingswet sets.
EU AI Act for critical infrastructure
AI used as a safety component in the supply of electricity, gas, heat or water is high-risk under the AI Act. We keep our AI out of that role: it supports customer service, planning and administration, and control stays with your systems and operators.
IEC 62443 and OT separation
Data from SCADA and historians is read through one-way, segmented connections aligned with IEC 62443, and nothing we build writes to control systems.
GDPR and the Energiewet for meter data
Smart meter data is personal data, and the Energiewet sets rules for sharing energy data with consent. Our integrations check the legal basis for each data flow and log access.
Works with what you run.
If a system has an API, a database, an export or an inbox, we can build on it. These are the ones we meet most.
- SAP IS-U (S/4HANA Utilities)
- EDSN market processes
- EAN codes and the connection register
- Smart meter data (P1 and P4)
- AVEVA PI System
- IBM Maximo
- Esri ArcGIS
- Salesforce
Where to start.
Completeness checks for connection requests
Incomplete applications cost planners time and customers weeks. We start by checking and enriching new requests for one customer segment, such as small business connections, before they reach a planner.
Talk it throughWhat it includes
- Intake of application forms and attachments
- Enrichment with EAN, address and grid area data
- Missing information requests to the applicant
- Planner queue with a prepared case file
Guides.
AI vendor security questionnaire: what to ask before you buy or build
The questions to ask an AI vendor, or your own team, about data, model providers, access, logging, quality, incidents, GDPR and exit, and how to score the answers.
8 min read
AI readiness checklist: what to answer before your first agent goes live
The questions to answer before your first AI agent handles real work, from process and data to approvals, monitoring and ownership.
10 min read
Further reading.
Human-in-the-loop AI agents: design patterns for production
The patterns we use to run AI agents safely in production: approval checkpoints, confidence thresholds, tool permissions, audit trails and fallbacks.
4 min read
LLM evals: how to test AI features before every release
A practical approach to LLM evals: build a test set from real cases, combine code checks with model grading, and block releases that regress.
5 min read
Common questions.
Yes. We connect through SAP interfaces such as OData services, BAPIs and IDocs, or through your integration platform if you have one. We agree the approach with your SAP team, who stay responsible for the core system.
We never connect to control networks directly. Data from SCADA and historians comes through read-only, segmented interfaces that your OT team approves, following IEC 62443 principles.
Within the rules, yes. Access to detailed meter data needs a legal basis or customer consent, and we build consent checks and logging into every flow that uses it.
Yes. We regularly work alongside managed service providers and SAP partners. We agree interfaces, environments and responsibilities up front, and document everything for their operations team.
Security reviews and access to utility systems often take longer than the build itself. A narrow first project runs in weeks to a few months, and we plan the security steps from day one.