An expanding service zone can have enough water at its sources and still leave customers with low pressure or irregular supply. The gap exists because a supply total says nothing about whether the distribution system can move that water to each area at the time and pressure required. For a growing utility, the useful capacity figure is deliverable demand under credible operating conditions, checked against what crews and operators see in the street.

Source supply and deliverable capacity

A source-capacity check answers how much water is available. A distribution-capacity check asks how much reaches customers, at workable pressure, when they need it. The difference matters in zones that receive water on a schedule: adequate volume over a day does not establish adequate flow during a shorter supply window.

In Adhewada Zone 5, Bhavnagar, rising population and demand prompted an assessment of a zone-wise, time-based system. The existing system had low pressure, irregular supply, and water loss. Its assessment examined distribution patterns, pressure, flow, and supply timing rather than treating source availability as the whole capacity question.

For a utility planning an extension, that distinction changes the first decision. Before sizing new supply against projected demand, identify the delivery areas and operating periods already under strain. Otherwise, additional water may enter a system that still cannot deliver it where demand is growing.

Why pressure changes the capacity answer

The choice between demand-driven and pressure-driven analysis can change what a capacity result appears to mean.

In a demand-driven calculation, each junction is assigned its specified demand, even if the calculated pressure is inadequate. EPANET’s network model explains that this approach can imply full delivery at negative pressure. That result is a hydraulic warning, not evidence that customers received the requested water.

In a pressure-driven calculation, delivered demand decreases as pressure falls and can reach zero below a specified minimum-pressure threshold. The difference between specified and delivered demand becomes an estimate of unmet demand. For a pressure-deficient zone, that is the more useful capacity answer: it shows where the service obligation exceeds what the system can deliver under the modeled conditions.

Pressure thresholds need to match the decision at hand. If the assumed minimum and required pressures do not reflect the service you intend to provide, a precise-looking unmet-demand total can still support the wrong investment.

Operating conditions and future demand scenarios

A capacity result is tied to the operating condition that produced it. EPANET can simulate flows and pressures over time, including pump and tank operation. That makes it possible to test whether a zone that performs adequately in one period falls short as storage levels, pump schedules, or demand change.

Build scenario simulation around decisions the utility actually faces. Compare current operation with a constrained supply period, then test planned growth and plausible changes in demand. In a scheduled system like Adhewada’s, the supply window belongs in those scenarios; an average-day total alone would conceal its effect on delivery.

Future demand should be treated as a range, not a single forecast that decides an asset purchase. Research on real-life distribution design considers different demand scenarios, while work on climate change and asset deterioration compares demand-driven and pressure-driven assessments. For a utility, the practical question is which proposed upgrade still works when both demand and operating assumptions move.

Choosing a hydraulic modeling platform for capacity work

Start platform selection with the hydraulic question and the physical system. The U.S. Environmental Protection Agency offers EPANET as free, public-domain software for simulating flow, pressure, and water quality in pressurized distribution systems. It has no fixed network-size limit, so an assumed node limit is a poor reason to rule it out.

Scope matters more than a software label. EPANET assumes that pipes remain full; partially filled pipe flow lies outside that scope. A large model also needs defensible network data, demands, controls, and pressure assumptions. Unlimited size does not make an unverified model useful.

Commercial water network modeling software is another option where it fits the team’s workflow. The Adhewada researchers used WaterGEMS for simulation, analysis, and optimization, and Bentley identifies OpenFlows Water as water distribution modeling software. Ask prospective platform providers to demonstrate the operating scenarios, pressure-driven calculations, result inspection, and model calibration your capacity decision requires. Physics-based simulation earns its place when those outputs change an infrastructure decision, not when a product list looks comprehensive.

Field observations and trustworthy model results

A simulated shortfall can guide spending only if the network representation and observed operation support it. The Adhewada assessment used data collected from the Bhavnagar Municipal Corporation, created a network layout, and examined pipe and junction reports. That is a useful pattern: connect field information to inspectable hydraulic results before recommending changes.

Use this checklist before relying on a capacity finding:

• Match the condition. Compare observed pressures, flows, and supply times with the same operating period in the model.
• Inspect the network. Check the layout, junction demands, pipe properties, and operating controls where the result drives a proposed investment.
• Review the calculation. Resolve warnings before interpreting low-pressure areas; disconnected networks or failed convergence can make EPANET results unusable or inaccurate.
• Trace the decision. Record which observation and scenario support the proposed pipe, pump, storage, or operational change.

When observed pressure and simulated pressure disagree, model calibration comes before design approval. The mismatch may point to an incorrect operating assumption or an issue in the field that the model does not yet represent.

Investigating low pressure and suspected water loss

Low field pressure alongside an adequate modeled capacity result is a reason to investigate, not to accept either answer unquestioned. Recheck supply timing, pump and tank operation, network connections, and demand assumptions against the observed period. The Adhewada case considered water loss alongside pressure, flow, and irregular supply, showing why these observations belong in the same operational investigation.

Water network leakage detection can then help prioritize where crews look. ASCE describes a near-real-time, pressure-based approach that automates sensor selection and retraining decisions and uses a cumulative sum chart designed for noisy data. The reported changes reduced manual tuning and false alarms under realistic operating conditions. That makes pressure monitoring useful for flagging suspicious behavior, but an alert does not identify an excavation point or prove that leakage caused every pressure discrepancy.

From a suspected leak to a field location

Pressure evidence can narrow the search area; locating the leak is a different job. SebaKMT explains that effective acoustic correlation depends on knowing the pipeline route accurately. In its described field sequence, a correlator indicates a suspected point, which a crew checks with a ground microphone before excavation.

The pipe-location method also has to suit the pipe material, site conditions, and access. If records leave the route uncertain, resolving that uncertainty is part of leak investigation, not an optional preliminary. A capacity model may tell you where lost water could matter most; field verification tells you where to dig.

Make the capacity decision on delivered service

Source supply is one input to a capacity decision. The stronger basis is delivered demand across relevant pressures, supply periods, and growth scenarios, supported by field observations and a calculation that runs without unresolved warnings. If street pressure remains low while the model looks adequate, revisit its delivery assumptions and investigate water loss separately.

For the next planned expansion, bring operators’ pressure and supply records into a pressure-driven scenario assessment before committing to new capacity. That gives the planning team a clearer choice between changing operation, investigating a field fault, and building infrastructure.

Related Articles

• Heat network hydraulic modeling: how to cut project delivery time
• Thermal network simulation: how to detect and locate pressure anomalies
• How consultants use digital twins to win district heating projects
• What is district heating used for in urban energy planning?
• Hydraulic modelling and digital twins: real-time insights for district heating