From a static network drawing to a system that can be tested.
A GIS-integrated hydraulic model connects surveyed network reality with engineering assumptions. It allows planners and operators to examine how pressure, demand, flow, storage, controls and water quality may behave—before deciding where intervention is required.
END-TO-END WORKFLOW
One continuous engineering chain.
Each stage preserves the evidence, assumptions and topology required by the next.
01
Field survey
Ground-truth network alignments, assets, elevations and observed operating conditions.
Clean topology, connect assets and prepare an engineering-ready spatial network.
04
Hydraulic model
Assign demands, levels, roughness, controls, patterns and operating assumptions.
05
EPANET simulation
Run DDA or PDA and extended-period scenarios through the model engine.
06
Diagnostics
Map pressure, flow, velocity, head loss, storage cycles and warning locations.
07
Decision support
Compare improvement scenarios before recommending physical or operational action.
INTERACTIVE MODEL VIEW
See the network change by result layer and time.
Select a simulation output, then move through the supply cycle. This public visual uses anonymised demonstration data while showing the actual analysis logic.
CURRENT LAYERPressure
View node pressure distribution and time variation across the supply cycle.
HYDRAULIC MODEL / DEMONSTRATION
Normal rangeReviewWarning
SIMULATION TIME08:00
m
MODEL FOUNDATION
Reliable simulation starts with structured evidence.
INPUT LAYER
Demand basis
Census and projected population, design year, growth rate, LPCD, institutional demand and minor-loss assumptions.
Supply windows, pump curves, valve status and settings, source head, reservoir and tank levels.
INPUT LAYER
Validation evidence
Field observations, known operating behaviour and measured values used for ground-truthing and model review.
ANALYSIS & DIAGNOSTICS
Move from results to locations that need attention.
Every output remains connected to the map, model element, simulation time and operating assumption.
01
Pressure & demand
Node pressure maps, time variation, critical nodes, low-pressure zones and DDA/PDA comparison.
02
Pipe performance
Flow, direction, velocity, head loss and head-loss gradient for every modelled pipe.
03
Storage & operations
Reservoir or tank level cycles, pump and valve scenarios, supply-hour and time-step testing.
04
Issue location
Searchable warnings for excessive head loss, zero or low velocity, low pressure and low chlorine.
SCENARIO TESTING
Compare options before changing the physical system.
Test demand methods, supply schedules, pump operation, valve settings, storage adequacy and network improvements. Re-run the model to understand the effect of each proposed change.
Supply-hour and time-step scenariosPump, valve and tank operating casesDemand growth and zonal allocationImprovement option re-simulation
PRESSURE-DRIVEN ANALYSIS
Relate delivered demand to available pressure.
Useful for examining service under pressure-deficient conditions and identifying demand that may not be fully delivered.
Analysis method selected according to project purpose and available evidence.
ENGINEERING DELIVERABLES
Outputs that remain useful beyond a single simulation.
01Simulation-ready EPANET model files
02Structured GIS network database
03Pressure, flow, velocity and head-loss maps
0424-hour node, pipe and storage results
05Searchable result tables and CSV exports
06Scenario comparison and improvement options
07Technical reports and engineering drawings
08Model assumptions, warnings and run history
CONNECTED DELIVERABLE
Model + map + evidence + recommendation
The result is an auditable engineering package—not an isolated graphic or a black-box calculation.
Model recommendations are advisory and human-reviewed. Data completeness, field validation, model fidelity, convergence, mass balance, reproducibility and operational safety are considered before any action is approved.
FROM NETWORK DATA TO ACTION
Make water-supply performance visible before intervention begins.
