From Theory to the Street: Implementation of a Digital Twin and Master Map for Hydraulic Operation.

Question

I want to share with you part of the experience and the technical architecture behind the Master Map and the Digital Twin of Hydraulic Infrastructure that we have implemented nationwide in our country, Panama. Many times we see models or web viewers that remain on paper or fail in the field due to latency issues or broken data routes.

The real challenge of engineering is not uploading a file to the cloud, but making that information useful for those who make critical decisions: The Engineers and the operational crews in the field.

The Technical Challenge: Connectivity and Geospatial Rigor.

To manage a network that ranges from main adduction lines to distribution networks, the design of the geographic database must be impeccable. In our project, we prioritized topological continuity and metadata cleanliness, focusing strictly on the functional attributes of hydraulic engineering: pressures, diameters, valves, and operational status of components.

Bridging the Gap between Office and Field.

The key to the success of this Digital Twin has been real-time integration through mobile workflows linked to systems like Open Smart. The operational cycle starts from receiving citizen complaints through the 311 line. The damage is immediately tracked in the system, marked in red to alert about the active incident.

When our crews arrive at the site, they carry out the repair and update the node in the field.

Not only is the job closure reported and multimedia evidence of the excavation attached, but data on replacement materials used is also entered. This transforms the Feature Layer into a living historical record, serving as an automated tool for technical audit processes and inventory control directly from the map.

Operational Results.

The impact of optimizing the map architecture translates into real use. An optimized Master Map records intensive traffic peaks precisely during field operation hours. Seeing the view counter rise significantly within minutes confirms that technicians are using the map on their devices to resolve incidents instantly.

This methodological and technical approach is the same one we will soon present at the Esri User Conference 2026 in San Diego, California, where we will detail this national case study.

I would like to open the debate with you:

1-How do you manage entity layer latency when your crews operate in areas with limited cellular coverage? I look forward to reading your comments!

OsvaldoDiaz · Answer

​Hi Robert and everyone,
​Thank you so much for the encouraging words! It is an honor to have the water utilities community looking forward to this work.
​I wanted to share an important update regarding my participation. Due to sudden institutional budgetary and administrative constraints here in Panama, I will not be able to travel physically to San Diego.
​However, "giving up" is simply not an option for me. I have officially registered as a virtual attendee, and our Master Map has been successfully submitted to the Digital Map Gallery (Submission ID: 42234), verified as Authoritative by the system.
​I am particularly excited to share how we resolved the historical tracking of our infrastructure. Instead of bloating the geometric asset layers, we implemented a strict "separation of concerns" strategy using 1:N relational database architectures. Every asset (hydrants, valves, meters) acts as a parent entity connected to independent, specialized inspection and maintenance tables. This ensures that every event, pressure record, and operational change is preserved in its own independent lifecycle record without compromising the core spatial data.

​Although I won't be standing next to a physical poster, I will be fully active online throughout the entire week, ready to discuss this relational data model and exchange technical insights with fellow water utility engineers.
​I would deeply appreciate the support, feedback, and votes of this amazing community once the Digital Map Gallery opens next week. Let's show the global strength of robust water data engineering!
​See you all online,

​Ing. Osvaldo Díaz
National GIS Content Administrator, IDAAN Panama

OsvaldoDiaz · Answer

Hi Robert,

Thank you for the architectural insight. You are absolutely right about the importance of separating historical maintenance from the GIS feature lifecycle.

That is precisely why my current setup implements a ´separation of concerns´ strategy.

By using 1:M relationships and dedicated inspection tables (e.g., Hydrant Maintenance Inspection, System Valve Inspection), the historical data resides independently of the geometric asset. This ensures that even if an asset is retired or modified in the Utility Network, the audit trail and pressure history remain intact.

Regarding the Survey123 integration, it acts as the data entry point that populates these related tables, effectively maintaining that decoupling while ensuring real-time data integrity.

Best regards,

Osvaldo´´

RobertKrisher · Answer

The requirements you have listed are common requirements for utility data in an enterprise GIS, and are not impacted one way or the other by the ArcGIS Utility network.

Take care when designing considering your options for solving these requirements. As an example, hydrant inspection/maintenance history (including pressure tests) are usually stored in a separate asset management system so that it remains even after the asset has been retired or abandoned. Because features in the GIS are often deleted when retired, or moved to separate layers when abandoned, you should consider how you will handle the history if you decide to implement a solution that does not include an asset management system.