Technical focus · KOMEC GLOBAL

Hydraulic modelling for water networks.

A water-network model connects physical assets, operating rules and demand to pressure, flow and storage behaviour. Its value depends on how well that evidence answers a defined engineering question.

Professional context: Raef Kobeissi · CEng FIMechE
  1. 01

    Establish

    Network data, demands and operating conditions.

  2. 02

    Check

    Topology, field evidence and model behaviour.

  3. 03

    Stress-test

    Peak demand, outages and future scenarios.

  4. 04

    Interpret

    Constraints, confidence and investment implications.

Method sequence, not project data or measured performance.

01 · Purpose

Start with the decision, not the model size.

Hydraulic modelling can examine supply capacity, pressure constraints, pumping and storage operation, trunk-main reinforcement and network resilience. The brief should identify the decision, the relevant operating period and the acceptance criteria before detailed scenarios are built.

A strategic capacity assessment and a detailed operational investigation need different evidence. An explicit model boundary prevents a network-wide result from being interpreted as proof of local asset performance.

02 · Evidence

Make the inputs and calibration traceable.

Useful inputs include asset connectivity, pipe diameters and lengths, elevations, pump curves, valve settings, reservoir levels and time-varying demand. Asset records should be reconciled with known operations: a wrong valve status can matter more than a finely adjusted roughness coefficient.

Compare calculated pressures, flows and tank levels with suitable field observations. Record sensor locations, time alignment, operating conditions and measurement uncertainty. Avoid compensating for a structural error by adjusting an unrelated parameter.

Calibration describes agreement with the observations used to adjust the model. A separate operating period or independent dataset can test whether that agreement holds beyond the calibration conditions. Where evidence is limited, state the resulting restriction on use.

03 · Scenarios

Show what changes, and how performance is judged.

Compare scenarios against an explicit baseline. Keep demand assumptions, operating controls and infrastructure changes separate so that the cause of an improvement remains visible.

Example assessment framework — no project values
ScenarioQuestionUseful output and unit
Peak demandWhere is pressure or capacity limiting?Pressure head (m); flow (L/s); velocity (m/s)
Asset outageCan alternative routes maintain supply?Unmet demand (L/s); duration (h); storage level (m)
Future growthWhen does reinforcement become necessary?Demand (ML/d); headloss (m); capacity margin (L/s)
Operating changeWhat changes in pumping and storage?Energy (kWh/d); tank level (m); pump duty (L/s and m)

Scroll the table sideways to read all 3 columns.

Acceptance limits are scheme-specific; the units above are not universal pass/fail thresholds. State whether flow is instantaneous or averaged over a period and whether head is pressure head or hydraulic grade relative to a datum.

04 · Interpretation

Separate a model result from a decision.

Low-pressure scenarios require care. A demand-driven calculation assumes specified demand is delivered; pressure-dependent demand can represent reduced delivery as pressure falls. A converged solution alone does not establish that the physical system can deliver the required service.

Test influential uncertainties such as demand distribution, roughness, pump characteristics and operating controls. Report which conclusions remain stable, which need better evidence and whether an option depends on a particular operating intervention.

A useful handover includes a versioned model, data and assumption register, calibration evidence, scenario definitions and a concise statement of constraints. Technical peer review provides a separate challenge to the interpretation before it supports a consequential decision.

Common questions

Choosing the right level of modelling.

How is hydraulic network modelling different from CFD?

Network modelling represents how connected pipes, pumps and storage assets interact across a system. CFD resolves spatial flow behaviour within a defined domain, such as a tank or chamber. The methods can complement each other, but neither substitutes automatically for the other.

Does a good calibration prove every future scenario?

No. Confidence is strongest within the conditions supported by evidence. A materially different demand, topology or operating regime may need additional measurements, sensitivity testing or a revised model representation.

Technical references

These references support the methods discussed; they do not imply endorsement of KOMEC GLOBAL or certification of a particular model.

  • US EPA · EPANET

    Water-distribution network modelling capabilities and links to the official user manual.

Professional contact

Let’s connect.

For a professional conversation about water infrastructure, modelling methods or technical collaboration.