Two kinds of IT that must learn to talk to each other
IT expertise for energy and utilities (water, wastewater, waste, heating networks) covers ground that few other industries know: the coexistence of two kinds of IT. On one side, business IT: billing, subscriber relations, finance, human resources. On the other, industrial IT: controllers, installation supervision, remote network management, sensors.
These two worlds have neither the same pace nor the same priorities. A business system is updated often and tolerates a short interruption. A controller that runs a pumping station or an electrical substation stays in service for many years, and stopping it has physical consequences.
Yet value comes from bringing them together. It is by combining field measurements with operational and customer data that you detect a leak, anticipate a failure or adjust a round. The central issue of the industry is therefore one of information system architecture: moving data from the installation to the business side without opening an attack path in the other direction.
IT expertise for energy and utilities: typical workstreams
An operational data platform. Sensor measurements, smart meter readings, intervention histories, weather data: the sources are numerous, heterogeneous and voluminous. Bringing them together in a governed data platform is the prerequisite for almost every other project.
Knowledge of the asset base. Pipes, substations, plants, vehicles: an operator manages its assets over long periods. A reliable register, linked to mapping and maintenance, underpins renewal decisions. A predictive maintenance model trained on an inaccurate inventory predicts nothing useful.
Equipping field teams. Intervention scheduling, mobile applications usable without a network, reporting from the worksite. These tools are only worth anything if they are adopted by technicians whose job is not data entry.
Keeping digital services running. When an application becomes indispensable to operations, its availability is measured and managed. SRE and observability practices then apply to the software surrounding the industrial tooling.
Reporting to local authorities. An operator that runs a service on behalf of a local authority owes it indicators that comply with its contract. Producing them by hand, contract by contract, takes time that operations do not have. Making them reliable at source is a data project in its own right.
NIS2 and GDPR: the framework to build in from the design stage
Directive (EU) 2022/2555, known as the NIS2 directive, covers in particular energy, drinking water and wastewater (Annex I) as well as waste management (Annex II). It distinguishes essential entities from important entities. Its Article 21 requires them to take cybersecurity risk management measures, including incident handling, business continuity and supply chain security. Its Article 23 organises the reporting of significant incidents. Its Article 20 commits management bodies, which approve these measures and oversee their implementation.
As a directive, its obligations apply through national law. The measures it describes correspond, in all cases, to practices that a network operator has every interest in mastering.
Regulation (EU) 2016/679 (GDPR) concerns the industry more than is commonly thought. Consumption data linked to an identifiable subscriber is personal data, and a fine-grained measurement can reveal lifestyle habits. The principles of Article 5 (specified purpose, data minimisation, limited retention period) and data protection by design under Article 25 translate into concrete decisions: which measurement interval to collect, at what level to aggregate, how long to retain.
Running a project when the service cannot stop
Service continuity imposes its discipline on the project.
- You do not experiment in production. A change affecting the industrial tooling is validated on a test bench or a pilot site, with a rollback that has been prepared and rehearsed.
- Intervention windows belong to operations. The project schedule is negotiated with those who run the service, not the other way round.
- Equipment outlives software. A new solution must coexist with older controllers and protocols. The project plans for this coexistence instead of assuming a uniform installed base.
- Deployment happens in waves. Sites, contracts and regions do not have the same maturity. A PMO that tracks progress site by site prevents a successful pilot from going nowhere.
Our involvement, from framing to operations
We work in four stages: frame, prove, industrialise, operate. Framing brings together IT teams, automation engineers and operators from the outset, because a project decided without any one of the three fails in the field. Proof is obtained on a real site or scope, with real data. Industrialisation deals with what the pilot left aside: security, monitoring, recovery after an incident. Operations rely on your teams, to whom our consultants pass on their practices.
Security runs through all four stages. We approach it through cyber resilience: knowing what must keep running in the event of an incident, and in what order the rest restarts. To discuss it based on your situation, write to us.