How digital twins are reshaping resilience planning for water utilities

A pipe break can send utility operators to supervisory control and data acquisition (SCADA) readings, engineers to a hydraulic model, and field crews to a geographic information system (GIS) map. Each view may be useful, yet none gives the team the same picture on its own. An operational digital twin connects simulated behavior with operating and location data, so staff can investigate pressure, water-quality, and leakage concerns before choosing a response. The starting decision is which behavior the model must simulate and which connections will keep it useful when conditions change.

The Simulation Foundation Behind an Operational View

A hydraulic model gives the twin its physics-based view of the water distribution system. The U.S. Environmental Protection Agency’s EPANET 2.2 performs extended-period simulations of hydraulic and water-quality behavior in drinking-water systems. That makes it a relevant foundation when engineers need to see how conditions develop over time, not merely inspect a network drawing.

The choice of water network modeling software should follow the decision it must support. WaterGEMS and WaterCAD, for example, include water age, tracing, and constituent analysis for water-quality work. For design work tied closely to mapped inputs, ESurvey’s application can place an imported topographic file behind a network drawing and overlay a georeferenced image in its CAD window. Those capabilities answer different questions; a useful procurement brief names the simulations and mapped inputs the utility actually needs.

How Operating Data Becomes a Connected Twin

A simulation becomes operationally useful when staff can relate its network behavior to current readings and asset locations. Before its digital-twin project, Orange City Water had data distributed across SCADA, GIS, hydraulic models, and customer-information platforms. In Nagpur, a utility used OpenFlows WaterSight to bring SCADA, GIS, and hydraulic-modeling data into one platform for a real-time view of distribution performance.

That connection changes the operator’s task. Instead of reconciling separate screens before investigating an event, the team has a common view for monitoring conditions and making operating decisions. The integration work still matters: readings need to correspond to the right modeled locations, and the mapped network must reflect the system crews encounter.

Nashville Metro Water Services faced a related split. Engineers worked with modeling data, operators with SCADA, and maintenance teams with computerized maintenance management system (CMMS) records. Keeping those datasets apart made recurring causes of water-quality, leak, and pressure complaints harder to identify. For a utility planning a twin, that is a reason to specify the questions teams must answer together before selecting an interface.

What the Model Shows Between Sensors

Sensors report conditions where they are installed; water distribution simulation helps staff assess what may be happening between them. Nashville partnered with Xylem Vue on a twin for real-time drinking-water decisions. Its connected application displays water age, pressure, and source at network nodes, including a view of operating conditions in areas without sensors.

That view is useful for directing investigation, not for turning every modeled node into a measurement. Xylem reports that the Nashville twin helped staff find unexpectedly high water age in a particular storage tank. On a system with more than 3,000 miles of water mains, narrowing attention to a specific asset is a practical result. Operators can then check the relevant operating history and decide what action the condition warrants.

From a Leakage Signal to a Located Pipe

Water network leakage detection has two distinct jobs: flagging a possible loss and locating it well enough for field action. A discrepancy between water entering a zone and water reaching users can raise suspicion, as Spatial-Eye describes. Nashville’s twin can also draw staff attention to distribution anomalies before they become disruptions or complaints, according to Xylem. Neither signal identifies an excavation point.

For a suspected leak, the investigation can proceed in this order:

  1. Check the anomaly and its location. Compare the operating signal with the affected zone and the mapped pipe route before dispatching location work.
  2. Confirm the pipe route. Effective acoustic correlation depends on an accurately located pipe, according to SebaKMT. Choose a location method that fits the pipe material, surroundings, and access.
  3. Narrow and verify the point. Use a correlator to identify a suspected position, then a ground microphone to check it, following the field sequence SebaKMT describes.

The twin can make the search more focused. The crew’s measurements still determine where a repair belongs.

Scenario Simulation for Disruption Planning

Once operating data and the hydraulic model describe the same system, engineers can test responses before committing crews and equipment. In Nagpur, the connected twin supports hydraulic simulations for pump failures and pipe breaks. That is a direct resilience-planning use: assess the consequences of an interruption and compare possible operating responses while there is still time to choose.

The scenario should match the decision. A pipe-break exercise may ask which parts of the distribution system face pressure changes under proposed responses; a pump-failure exercise may test how an alternative operating arrangement behaves. Xylem’s drinking-water application is another example of real-time scenario simulation, while the EPA presents its Water Network Tool for Resilience for natural-disaster preparation. The useful output is a response the utility can evaluate against its operating constraints, not simply a simulation run.

Connecting Hydraulic Decisions to Pipe Replacement Priorities

Operational decisions and capital decisions use some of the same network information, but they have different horizons. DC Water’s GIS modernization began in 2024 with a move from ArcMap to ArcGIS Pro. Its GIS database also connects to asset management and field applications, so the migration has to preserve the links staff use beyond the map.

DC Water had used separate software for water, sewer, and asset-risk modeling. According to Aquanuity, exchanging data between those platforms and the ArcGIS inventory required data pipelines and staff effort, with opportunities for transfer errors. DC Water consequently reevaluated its asset-management and water-distribution-system modeling software during the GIS migration. For another utility, the lesson is to map those exchanges before changing platforms; a hydraulic model cannot improve replacement decisions if asset identities or updates lose their way between systems.

Where Asset Risk and Hydraulic Insight Meet

DC Water already identifies and prioritizes pipe-replacement projects by risk, according to Aquanuity. With approximately 1,300 miles of active mains and an average main age of around 80 years, prioritization has an evident purpose. A modeled consequence of losing a pipe could add useful context to that risk assessment, but it does not replace the asset judgment.

Aquanuity presents a fully integrated hydraulic-and-asset model as a future direction for DC Water, not a capability already in operation. The immediate decision is more concrete: preserve the GIS-to-asset and field connections that current priorities depend on, then define how hydraulic results should enter the next planning workflow.

A practical starting point for resilience planning

For a utility weighing an operational twin, the first scope should name a decision staff struggle to make with disconnected views. Define the hydraulic and water-quality behavior needed to support it, connect the relevant SCADA and GIS data, and test whether the resulting view directs a real investigation or disruption scenario. That keeps modeled conditions, field-verified leaks, and risk-based replacement priorities in their proper roles while giving each team a better basis for its next decision.

Related Articles

© Fluidit 2026