Access Official Technical PDF

Share Summary:LinkedInEmail

Water network design is not simply a matter of sizing pipes for a forecast flow. New distribution infrastructure must fit the existing system, support future demand and meet the service objectives set by the relevant water service provider. For engineers, system integrators and utility decision-makers, this means connecting strategic planning, demand analysis, hydraulic modelling and asset lifecycle considerations before detailed design begins.

Start with the wider water system

A proposed development or network extension operates within a larger system of interconnected assets, operating controls and constraints. Systems planning establishes that context: it identifies boundary conditions, existing network limitations and requirements that a new connection must respect. Concept planning then helps define the scale, location and general arrangement of key infrastructure. These steps provide the basis for detailed design.

This sequence matters because the performance of a local asset can depend on conditions elsewhere in the network. A design informed only by the immediate project boundary may overlook how existing reservoirs, pumps or pressure zones affect the proposed works. Hydraulic modelling should therefore represent both existing assets and the infrastructure being considered, using the modelling detail appropriate to the project.

Design criteria also need to be applied in the right context. Standards developed for new, non-trunk distribution assets are not automatically equivalent to existing customer service levels or planning-scheme standards for trunk infrastructure. Designers should establish which requirements apply, confirm the current criteria with the relevant service provider and resolve document conflicts according to the applicable hierarchy.

Build demand projections on clear assumptions

Demand estimates shape the capacity of mains, pump stations and storage. A robust design process makes the assumptions behind those estimates visible and checks them against available system performance and historical records. Population loading is commonly expressed in equivalent persons, with non-residential estimates reflecting the land-use categories and conversion rates adopted by the relevant council.

Projections should cover the existing case and future stages at intervals that support planning across the design horizon. The CTM Water Services Design and Construction Code, for example, calls for projections at intervals of no more than five years over at least 30 years, or up to ultimate development. Major users with projected demand above 100 ML per year are to be calculated and identified separately.

Water demand is assessed using several related measures:

  • Average day demand (AD): the typical daily demand, commonly expressed per equivalent person.
  • Peak day demand (PD): demand adjusted for higher-use days, such as those associated with climatic variation.
  • Peak hour demand (PH): the short-duration demand used to assess network pressures and capacity during daily peaks.
  • Non-revenue water (NRW): water accounted for in the supply system but not represented by customer meter readings, as defined by the relevant provider.

These components should not be treated as interchangeable. In the cited code, NRW is added to the demand calculation without applying peaking factors, while customer demand uses the applicable peak factors. Where demand management is being evaluated, separating internal and external demand components can also help reveal how changes may affect future requirements. Diurnal patterns should be sourced from the water service provider rather than assumed without evidence.

Use hydraulic network modelling to test defined scenarios

Before modelling begins, the project team should state what the analysis needs to establish and how much detail is required. Model outputs should be checked against actual network behaviour where data is available. This may include flow measurements, reservoir levels, pressure logger records and input from operational staff. Calibration is important on larger projects; for smaller studies, an operational review may provide an appropriate reality check where detailed data is limited.

Different scenarios answer different design questions. A steady-state peak-hour analysis can assess whether pressures at customer boundaries meet the nominated criteria under high demand, with reservoirs at their minimum operating level and pumps or control valves set to represent the relevant operating condition. A fire-flow scenario tests the available capacity of the water mains under the specified fire demand and background-demand assumptions.

Extended period simulation is used where the question concerns how the system performs over time. For applicable bulk or reservoir-connected models, peak-day analysis can test whether reservoirs empty, whether minimum operating levels are maintained and whether the supply system can deliver at least the required peak-day volume. The model should reflect the provider’s diurnal demand pattern and the operating modes relevant to the zone.

Modelling assumptions should be reviewed rather than applied mechanically. Actual operations may differ from a default condition, particularly where a supply zone has multiple sources or operating configurations. Confirming these conditions with the service provider helps ensure the model represents a credible case.

Compare options over the asset lifecycle

The preferred design is not necessarily the option with the lowest initial construction cost. A sound assessment compares fit-for-purpose alternatives across capital costs, operations and maintenance, service outcomes and environmental impacts. It should also consider how a proposal interacts with existing asset renewal or rehabilitation programs, and whether non-asset approaches could contribute to the required outcome.

Lifecycle analysis makes these trade-offs explicit. The CTM code specifies a minimum 50-year analysis period where provider guidance is absent and identifies assumptions for discounting, cost escalation and maintenance. Those parameters are context-specific and should be verified with the relevant service provider before adoption. The assessment should document the assumptions, compare alternatives and explain why the recommended option best meets the project objectives.

Environmental considerations belong in the same decision process. The code calls for an estimate of the carbon footprint of each proposed option, using a format agreed with the service provider. Considering carbon alongside financial, operational and service factors supports a broader comparison rather than treating it as a separate afterthought.

Account for surge risks and operational realities

Steady-state and extended-period hydraulic results may not capture transient pressure events. Surge or water-hammer analysis may be needed for trunk pipelines, pumped systems and locations near actuated valves. Potential triggers include pump start or stop, power failure and valve closure. The design review should consider operating flow, system head, possible failure modes and whether pipe materials, pressure classes, thrust restraints and mitigation measures are adequate.

Depending on the system, mitigation may include air-release valves, slow-closing valves, surge tanks, pressure-reducing valves, pressure-release flanges or suitable material selection. The need for analysis and the approach to mitigation should be confirmed with the water service provider; the selection depends on the conditions of the specific system.

Make design decisions traceable

Reliable water network design depends on a connected process: establish system context, define demand assumptions, model relevant operating scenarios, compare lifecycle options and address transient risks where needed. Involving stakeholders and operations personnel throughout helps test whether proposed solutions are both technically sound and workable in practice.

For project teams, the practical outcome is a design whose assumptions and trade-offs can be reviewed by decision-makers. Clear documentation of demand, model conditions, alternatives and implementation rationale helps align new infrastructure with network needs today and the service requirements expected over time.

Access Official Technical PDF

About The Author