Water and utilities companies: digitalisation opportunities
Connecting drinking water, wastewater, heating, territory and other municipality or infrastructure-based utility asset, operations, field works, customer and compliance data into a single managed digital chain.
Digital maturity
medium
Skaitmenizacijos potencialas
88/100
Biggest challenge
Network, quality and customer signals insufficiently converted into incident actions
Biggest opportunity
Unified network, quality and customer impact management
The greatest value is created by the ability to quickly understand from a single signal which network asset is affected, which customers are at risk and what action will restore service.
Operating model for water and utility companies
Operations include water intake and treatment, wastewater collection and treatment, heat or other utility transmission, network maintenance, meter accounting, billing and customer service. The primary digital task is to link network topology, real-time status, field operations, quality and customer impact.
Network topology is the foundation of operational decision-making
Relationships between assets, valves, zones and customers must be sufficiently accurate for real incidents.
Quality data requires location and time context
A laboratory result must be linked to the measurement location, network regime and required action.
A customer bill begins with reliable measurement
The meter reading version, calculated quantity, correction and tariff must form a traceable chain.
Market and technology context
The EU water resilience direction encourages leakage reduction, infrastructure modernisation, smart meters and data-driven management. For utilities, this means moving from periodic measurement to an integrated network, quality, customer and field work chain.
Water resilience and climate riskLoss reduction, resource planning and infrastructure resilience are becoming strategic priorities.
Ageing networks and capital constraintsInvestment must be allocated according to actual asset risk, losses and customer impact.
Smart meters and real-time customer expectationHigher data frequency enables better control, but requires a reliable exception and communication chain.
Typical operating process
01
Resource production and treatment
Water abstraction, treatment, heat generation, equipment regimes, energy and quality are managed.
02
Transmission and distribution
Flows, pressure, temperature, network condition, losses and critical assets are monitored.
03
Metering and billing
Meter readings are collected, exceptions are checked, tariffs are applied and invoices are generated.
04
Incident and quality control
Signals, laboratory results and customer reports are linked to the network zone and impact.
05
Maintenance and field work
Crews receive the network diagram, shutdown points, materials, safety information and work priority.
06
Customer information and investment plan
Outage statuses, recovery time, complaints and asset reconstruction priorities are managed.
Digital maturity path
0
Separate network, meter and customer processes
GIS, SCADA, laboratory data, works and billing are managed separately, and incident impact is reconstructed manually.
1
Digital monitoring and basic accounting
Network status and meter readings are collected in systems, but exceptions, leakage, works and customer communication are not linked.
2
Integrated network asset and work process
Signal, GIS asset, fault, field task, completion and updated network status form a single chain.
3
Zonal network, loss and customer impact management Typical current situation
In selected network zones, GIS topology, real-time signals, meter and quality data, incidents, field works and customer impact are linked in one chain, but coverage is not yet uniform across the entire network.
4
Predictive maintenance and resource optimisation Siektina
Leak, equipment condition, energy consumption and demand patterns are used to prioritise work and investments.
5
Resilient and adaptive utility system
Grid regimes, crews, customer notifications and recovery scenarios are coordinated in real time with clear boundaries of human control.
Key finding
Water and utilities digitalisation must connect physical network topology, real-time state, quality data, customer impact and field crew actions.
The first priority is one clear network zone and a complete scenario of leakage, failure or quality incident, not a whole-city digital twin.
Related digitalisation topics
Water and heating network loss managementUtility incident managementSmart meter and billing data
Problemos
Most common digitalisation challenges
Problems arise between network topology, real-time signals, quality data, field work, meters and customer impact.
Network, quality and customer signals insufficiently converted into incident actions
Critical
SCADA alerts, laboratory results, meter anomalies and customer reports enter different work queues.
Consequences
Dispatchers manually determine the common cause and affected zone, which slows down inspection, repair and customer information.
Network leaks and unaccounted resources are detected too late
Critical
General flows, zone meters, pressure, customer consumption, fault history, ground conditions and acoustic signals are analysed separately.
Consequences
Water, heat or other resource losses continue for long periods, failures are detected late, and repair priorities are insufficiently precise.
Water and wastewater quality signals are not linked to network and customer impact
Critical
Laboratory and online measurements, network topology, flows, treatment process, complaints and incidents are kept in different solutions.
Consequences
The possible source of contamination, affected zone and necessary operational and customer communication measures are determined slowly.
The impact of emergencies and planned works on customers is determined manually
Critical
Network closure points, hydraulic or thermal topology, customer sites, work schedules and communication channels are not in one incident chain.
Consequences
Affected customers are identified late, service restoration information is announced inaccurately and incident management is prolonged.
Asset and technical data fragmented across systems
High
Water, wastewater and heating networks, pumping stations, treatment facilities, heating substations, meters, customer sites and vehicles are identified differently in GIS, SCADA, EAM, ERP and customer systems.
Consequences
Difficult to link failure, work, costs, risk and investment need to a specific physical asset.
Network and equipment maintenance often only initiated after a failure occurs
High
Maintenance decisions are often based on schedule or an incident that has already occurred, whilst actual load, condition signals, failure history and customer impact are assessed separately.
Consequences
Leaks and equipment problems are detected too late, emergency work increases and energy is used suboptimally.
Field work, network shutdowns and materials coordinated separately
High
GIS diagram, valves, safety requirements, crews, transport, materials, customer impact and proof of completion are planned in different tools.
Consequences
Unproductive callouts increase, service outages are prolonged and customers are informed inaccurately.
Meter data exceptions and invoice corrections are managed manually
High
Missing readings, unusual consumption, calculated quantities, meter replacement, tariffs, compensations and contracts pass through several systems.
Consequences
The costs of inaccurate invoices, disputes, unaccounted consumption and customer service are increasing.
Network reconstruction and capacity investments rely on fragmented data
Medium
Asset condition, losses, failure history, quality risk, demand forecasts, energy consumption and customer impact are analysed separately.
Consequences
Difficult to justify which network section or equipment should be reconstructed first and what benefit the investment will create.
Compliance, safety and environmental data are collected during reporting
Medium
Network, flow, pressure, quality, meter, laboratory, fault, customer and permit data are collected from different systems only before a report, audit or incident analysis.
Consequences
Report preparation is lengthy, data origin is difficult to trace, and non-compliance is detected too late.
Opportunities
Greatest digitalisation opportunities
Incident and loss management for a single network zoneVery high impactFor one clearly defined zone, connect GIS topology, SCADA or meter signal, loss analysis, incident priority, affected customers, mobile crew task and actual outcome.Lower water and heat losses
Quality and incident impact managementVery high impactLink laboratory and online measurements, network topology, process regimes, customer zones and communication.Faster response and public safety
Coordination of incidents, field work and customer communicationHigh impactConnect network signal, affected zone, crews, materials, proof of completion and recovery information for customers.Lower operational cost
Smart metering, billing and customer self-service platformVery high impactAutomate reading quality, anomalies, tariffs, bills, leakage alerts and customer actions.More accurate billing and customer engagement
Network condition, loss and maintenance managementVery high impactAlign asset condition, flows, pressure, failures, energy, maintenance, parts and reconstruction risk.Less downtime and better asset economics
Unified network, asset and customer data foundationVery high impactConnect GIS, SCADA, network assets, laboratories, meters, field work, customers and billing data.Reliable decisions and less data reconciliation
Quality, permit and public health controlVery high impactLink laboratory and online measurements, limit values, network zones, incidents, corrective actions and mandatory reports.Lower regulatory risk
Network capacity and reconstruction planningVery high impactCompare asset condition, losses, demand, quality risk, energy consumption and investment alternatives.More accurate capital investments
Biggest opportunity
Unified network, quality and customer impact management
The greatest opportunity is to connect the GIS network model, real-time flows and pressure, water or heat quality, meter data, leaks, asset condition, fieldwork, customer impact and billing.
Reduced water or heat losses
Shorter incident recovery
Earlier quality incident detection
More accurate billing
Better-justified network investments
Potential business impact
Resource lossesZonal balance and early anomalies help detect water or heat losses more quickly.
Energy costsPump, treatment plant and heat substation regimes are evaluated together with actual demand.
Incident durationGIS, signals, crews, materials and customer impact are visible in a single incident view.
Water and service qualityMeasurements are linked to network zone, cause, required action and customer notifications.
Billing accuracyMeter versions, tariffs, corrections and invoices are managed in a traceable manner.
Investment prioritiesAsset condition, failure history, losses and customer impact underpin the reconstruction plan.
Sprendimai
How to solve these problems
Solution directions linked to specific business area problems they address.
Problema
Network, quality and customer signals are insufficiently converted into incident actions
→
Sprendimo kryptis
Single zone incident and loss platform
Connects GIS topology, real-time signals, meters, loss balance, incident priority, affected customers, crew work and actual result.
Problema
Network leaks and unaccounted resources are identified too late
→
Sprendimo kryptis
Single zone incident and loss platform
Connects GIS topology, real-time signals, meters, loss balance, incident priority, affected customers, crew work and actual result.
Problema
Impact of emergencies and planned works on customers is determined manually
→
Sprendimo kryptis
Single zone incident and loss platform
Connects GIS topology, real-time signals, meters, loss balance, incident priority, affected customers, crew work and actual result.
Problema
Asset and technical data are fragmented across systems
→
Sprendimo kryptis
Network asset, GIS and field work system
Manages network assets, technical documentation, condition, maintenance work, network shutdowns, materials, crews and proof of completion.
Problema
Network and equipment maintenance is often initiated only when a failure occurs
→
Sprendimo kryptis
Network asset, GIS and field work system
Manages network assets, technical documentation, condition, maintenance work, network shutdowns, materials, crews and proof of completion.
Problema
Field work, network shutdowns and materials are coordinated separately
→
Sprendimo kryptis
Network asset, GIS and field work system
Manages network assets, technical documentation, condition, maintenance work, network shutdowns, materials, crews and proof of completion.
Recommended digital solutions
Solutions must connect network asset, signal, customer impact, field work, quality control and actual service restoration.
Single zone incident and loss platform
Connects GIS topology, real-time signals, meters, loss balance, incident priority, affected customers, crew work and actual result.
Network asset, GIS and field work system
Manages network assets, technical documentation, condition, maintenance work, network shutdowns, materials, crews and proof of completion.
Manages meter data quality, exceptions, corrections, invoices, notifications and customer property history.
Network reconstruction and investment platform
Connects asset condition, losses, incidents, customer impact, energy consumption, reconstruction scenarios and investment justification.
Is the organisation ready to begin?
Investment justified
Leak detection relies on cross-checking multiple systems and tables
GIS data do not always match the actual network layout
Affected customers during emergencies are determined manually
Meter exceptions generate numerous invoice corrections
Laboratory results difficult to link to network zone and action
Reikia atsargumo
There is no clear pilot network zone
Critical GIS objects have not been verified
Incident and works process is not defined
Direct control of OT equipment is expected from the first version
Recommended first version
Single network zone incident and loss process linking GIS topology, SCADA or meter signal, priority, affected customers, mobile crew task and actual outcome.
Current zone network model
Assets, valves, measurement points, customer connections and criticality.
Incidents and anomalies workflow
Signals and customer reports grouped by zone, impact and priority.
Mobile crew workspace
Network diagram, isolation points, safety information, materials and proof of completion.
Customer impact and restoration communication
Affected assets, statuses automatically identified and estimated time of restoration updated.
Kam pirmiausiaDispatcher · Network engineer · Field crew supervisor · Customer service representative · Data or loss analyst
What not to include in the first versionEntire city or regional network · Full integration of all SCADA signals · Automatic valve or equipment control · Complete replacement of billing and invoicing system
Investment priorities
Connect a single network zone's incident and loss processSelect one zone and link GIS topology, real-time signals, meters, customer sites, incident priority, mobile crew task and actual outcome.
Signal–incident–fieldworkConnect SCADA, notifications, priorities and mobile execution.
Leak and loss analyticsAlign zone balance, pressure, meters and repair results.
Quality and customer impact managementLink laboratory results, network zone, actions and communication.
Meter exceptions and investment planAutomate corrections and asset risk-based decisions.
Key implementation conditions
GIS topology must be operationally reliable
Relationships between valves, zones, connections and customer assets must be sufficiently accurate to determine incident impact.
Laboratory result must have location and time context
Sample, measurement location, network condition, threshold value and related incident must be linked.
Meter data versions must be traceable
Initial reading, calculated value, correction and final invoice must remain comparable.
Incident communication must be based on actual topology
Affected customers and estimated recovery time must be updated from the operational process, not a separate manual list.
OT and customer system integration must be minimal and secure
Customer portal must not have direct management access to critical infrastructure.
Recommended implementation sequence
01
Single network zone data audit
Select a clear water, wastewater or heating zone and verify GIS, SCADA, meters, customer objects, works and losses database.
Current zone topology
Object identifiers
Data quality gaps
Initial losses and incidents KPIs
02
Signal, object and field work integration
Connect an alert or customer notification with a network object, priority, mobile task and completion result.
Incident work queue
Mobile crew location
Object documents and valve data
Work closure evidence
03
Leak and loss management
Align zone flows, pressure, meter data, failure history and repair outcome.
Zone water or heat balance
Anomaly signals
Repair priorities
Avoided loss valuation
04
Quality and customer impact chain
Connect laboratory and online measurements, network topology, incident, affected customers and communication actions.
Quality incident process
Affected customer list
Communication scenarios
Traceable sample and action history
05
Smart meters and investment planning
Extend automation of meter exceptions, demand forecasts, asset risk and network reconstruction scenarios.
Meter data quality rules
Consumption anomalies process
Asset risk model
Investment portfolio priorities
KPIs for measuring change
Non-revenue water or heat loss percentage%
Measure network and metering efficiency.
Average leak detection timehrs or d.
Assess monitoring and analysis speed.
Average service restoration timehrs.
Measure incident management performance.
Percentage of quality incidents detected before customer complaint%
Assess early monitoring effectiveness.
Percentage of works completed on first visit%
Measure crew preparedness and network data quality.
Percentage of meter reading exceptions%
Monitor measurement and billing data reliability.
Percentage of affected customers informed on time%
Assess incident impact identification and communication.
Key risks
Digital network model does not match actual topologyIncorrect connections or valve states mislead leak and customer impact analysis.Kaip suvaldyti Start with one zone, verify critical assets on site and assign GIS data ownership.
Anomaly model confuses leakage with legitimate consumption changeUnnecessary checks are generated and staff confidence decreases.Kaip suvaldyti Use multiple signals, seasonality, customer context and measure the outcome of each alert.
Quality signal automatically triggers inappropriate actionA single measurement may be inaccurate or not reflect the entire zone.Kaip suvaldyti Base critical decisions on validated incident scenario, repeated measurement and responsible specialist review.
Smart meter project is limited to meter reading collectionData does not flow back into leakage, billing exception and customer service processes.Kaip suvaldyti Define in advance what business actions are initiated by specific meter reading signals.
First version covers the entire city networkInaccurate data and multiple integrations delay actual use.Kaip suvaldyti Start with one hydraulic or thermal zone and a full incident or loss process.
Inovacijos
More advanced digital innovations
AI, sensors and network models should help detect losses and incidents earlier, but critical quality and safety decisions are made by responsible specialists.
Market expansion3
For DI network condition, leaks and process anomalies
Highly urgent
Analyses zone flows, pressure, meters, equipment states, failures and environmental conditions.
How it is applied The signal must be linked to the network object, expected loss and a specific inspection or repair task.
What value can be created
Earlier fault detection
Reduced losses and downtime
What is needed for this to work
Contextual sensor data
Fault and works history
Model quality monitoring
Human confirmation
Medium-termCommercial solutions are available
Water or heat network digital twin
Highly urgent
The model integrates GIS topology, pipeline properties, pressure, flows, temperature, pump or heat point status and demand.
How it is applied Used for leak location, incident impact, network reconstruction, pressure or temperature optimisation and investment scenarios.
What value can be created
Faster incident impact assessment
Lower network and energy losses
What is needed for this to work
Accurate GIS
Calibrated flow and pressure data
Model validation
Medium-termApplied in practice
Robots and computer vision for network inspections
Relevant
Video, acoustic and other data help inspect pipelines, reservoirs, collectors and treatment facilities.
How it is applied The detected defect is linked to the GIS object, location, criticality and work task.
What value can be created
Greater inspection coverage
Lower safety risk for employees
What is needed for this to work
Asset geographical data
Standardised image collection
Defect taxonomy
EAM integration
Short-term perspectiveCommercial solutions are available
How it is applied Used to evaluate single-zone leakage, shutdowns, quality incidents and investment scenarios.
What value can be created
More accurate investment and maintenance planning
Faster incident impact assessment
What is needed for this to work
Reliable asset hierarchy
GIS and real-time data
Calibrated model
Version management
Long-term perspectiveApplied in practice
AI for water quality and process anomalies
Highly urgent
Models analyse laboratory, online sensor, process, flow and environmental data to detect unusual change earlier.
How it is applied Alert initiates a confirmed sampling, process verification and communication procedure, rather than an automatic final conclusion.
What value can be created
Earlier quality risk detection
Faster root cause analysis
What is needed for this to work
Calibrated sensors
Laboratory results history
Network and process context
Medium-termPilot projects
D.U.K.
Frequently asked questions
Where is it best to start digitalisation of a water or utilities company?
Most often, the best pilot is one clearly defined network zone and one process – leak, quality incident or emergency management. At this scope, it is possible to verify GIS, signals, customer connections and measure real savings.
Is it necessary to deploy smart meters to all customers immediately?
No. First, it is worth identifying which segments have frequent meter reading gaps, high losses or expensive manual reading. A pilot meter deployment must be linked to specific actions – a leak signal, billing exception or customer self-service.
How does a network digital twin differ from a GIS map?
GIS shows objects and their location, whilst an operational digital model additionally uses topology, actual states, flows, pressure, consumption and scenarios. It is worth building only when the basic network model is reliable and it is clear which decision it will improve.
How to digitalise water quality incident management?
Sample, measurement location, limit value, laboratory result, network zone, affected customers and actions taken must be in one chain. The system can help identify potential impact, but the final decision on safety measures must be made by a responsible specialist.
How to securely connect SCADA with customer and mobile systems?
Use a separate integration layer, read-only flows, the principle of least privilege and comprehensive audit history. The customer portal or mobile application should not directly control critical equipment.
How to measure return on investment?
Assess reduced water or heat losses, shorter leak detection and recovery, fewer unproductive call-outs, lower energy costs, fewer billing corrections and customer service enquiries.
Next step
Connect water supply, wastewater, heating, territorial and other municipal or infrastructure-based utilities signals, assets and actual works
An assessment of which network, quality, incident or meter data gap currently increases losses and customer risk the most.