An operational digital twin for water assets is a live 3D replica of a treatment works, pumping station or storage site, built from CAD and fed with SCADA and sensor data so operators and asset managers can see condition, test what-if scenarios and spot anomalies. iUNI's digital twin service, from the Wartens group's digital twin and XR company, builds these at 1:1 scale from CAD, integrates them with SCADA, PLC and ERP systems, and typically takes 12 to 24 weeks.
This article is about the operational twin specifically: the one that runs alongside a live asset for years. If you are still deciding whether a twin is worth it at all, start with our broader guide to digital twins for water treatment.
Why AMP8 makes an operational digital twin for water worth costing
Ofwat approved 拢104 billion of water company spending for April 2025 to March 2030, 77% more than AMP7, according to Causeway's AMP8 summary. The same source names skills as the biggest delivery challenge. More assets, more monitoring obligations and fewer experienced operators to watch them is the situation where a shared, visual view of asset condition starts to pay.
The operational twin does not replace SCADA. SCADA is for running the plant now. The twin is for understanding it: where an asset is degrading, how a works would cope with a pump out of service, and what an operator new to the site needs to see to understand it quickly.
What an operational twin is, and what it is not
The UK's Gemini Principles, published through the Centre for Digital Built Britain, are a useful test for any twin proposal:
All digital twins must have clear purpose, must be trustworthy and must function effectively.
- It is a live replica fed by measurements, with a web 3D viewer, dashboards, anomaly detection and what-if simulation.
- It is not a hydraulic network model. Network modelling tools remain the right place for pressure and flow studies; the twin can display their results.
- It is not a control system. It should read from SCADA and the historian, never write setpoints back to the plant.
What iUNI delivers
| Deliverable | What it gives a water operator |
|---|---|
| Digital twin platform with 3D viewer | 1:1 model of the asset in a browser, no software to install |
| IoT integration layer | Live values from SCADA, historian and sensors mapped to equipment |
| Analytics and reporting dashboard | Trends, anomaly flags and reports per asset |
| VR/AR visualisation module | Walk-throughs for training and maintenance planning |
iUNI lists predictive maintenance and anomaly detection, what-if scenario simulation and integration with SCADA, PLC and ERP among the features. iUNI publishes price ranges on its pricing page; scope drives where a project lands within them.
Connecting the twin to SCADA and telemetry
The integration is where water projects succeed or stall. Most UK water companies already collect the data a twin needs: telemetry from outstations, SCADA at the works and a historian. The twin should take data from those systems, not from new connections into the control network.
- Read from the historian or a SCADA gateway, typically over OPC UA, across a one-way or tightly firewalled path that your OT security team approves.
- Leave telemetry as it is. Outstation protocols to the regional control centre do not change for the twin.
- Map tags to equipment. Every pump, valve and instrument in the model gets the tags that describe it. Inconsistent tag naming across sites is the single biggest cost driver here.
- Define data quality rules. A stale or out-of-range value must look stale in the twin, not like a real reading.
Three water use cases that justify the effort
Pumping station performance. Show run hours, starts, current and wet well level per pump, then run what-if scenarios for a pump out of service ahead of a storm. Storm tanks and overflows. Combine level, spill and event duration monitoring data with the 3D layout so investigators can see an event in context; our article on event duration monitoring covers the data chain. Treatment process anomalies. Flag a blower or dosing pump drifting away from its normal pattern before it alarms on SCADA.
Digital Twin for the Water Industry
Siemens Knowledge Hub
This video is hosted on YouTube. Playing it loads content from Google, which may set cookies.
Watch on YouTubeHow the 12 to 24 week build usually runs
Weeks one to four cover survey, CAD and drawing collection, data source review and agreement on the first use case. The model build and tag mapping follow, then integration with the historian or SCADA gateway, dashboard and analytics set-up, and acceptance with operators using real events. A single pumping station sits at the short end; a full treatment works with several process streams sits at the long end.
Because Wartens are automation engineers first, the twin is built by people who read PLC programs and SCADA databases for a living. The same model can later support virtual commissioning of a control upgrade; see our digital twins and virtual commissioning service. Control upgrades themselves run through our water and wastewater controls engineering.
Next step
Pick one asset and one decision you want to improve. Send us the drawings and a tag list through the contact page and we will come back with a written scope, timeline and price.
