NETWORK SETUP
Connect your pipes. See how the flow splits.
Define a water supply, add demand points, then connect them with pipes. Start with the working example below and change only what you need.
1. Add supply and demand points
A reservoir supplies a fixed total head. A junction consumes water at its elevation. Use the same elevation datum throughout.
| Node ID | Type | Elevation / supply head (m) | Demand (L/s) | Action |
|---|
2. Connect points with pipes
Use the pipe’s inside diameter. Roughness is the absolute wall roughness for Darcy–Weisbach; 0.045 mm is a starting estimate for commercial steel. K includes fittings and other minor losses.
| Pipe ID | From | To | Length (m) | Inside Ø (mm) | Roughness (mm) | Minor-loss K | Action |
|---|
Connection preview · schematic, not to scale
Steady-state, demand-driven water calculation. Flow in L/s, lengths and heads in m, diameter and roughness in mm.
EPANET model
The file shown here is solved exactly as entered. Imported units, head-loss methods, pump curves, tanks, valves, patterns, and controls are preserved. Switching to guided tables uses the separate table model and keeps this file as a draft. Return to EPANET mode to continue editing it.
3. Solve the network
Ready.
Network results
Nodes
Links
How the network solver works
EPANET simultaneously balances flow at junctions and energy across the connected network. This is a full hydraulic network engine, including looped systems, multiple reservoirs, pumps, tanks, valves, patterns, and controls through EPANET 2.2 input files.
Choose a loop example for a steady-state calculation or the pump and tank example for an extended-period simulation. Use the guided tables for a steady pipe network, or the EPANET editor for advanced models, then solve it. Results include every hydraulic event time; use the time selector to inspect changing tank heads and flows.
Positive link flow follows its start-to-end direction. Head difference is start head minus end head; a running pump normally has a negative value. Pressure head is hydraulic head minus elevation, expressed in metres or feet of fluid. Reservoir demand is signed net inflow. Status indicates open or closed hydraulic connectivity. For valves, “Open / may regulate” does not distinguish active pressure or flow regulation; inspect the solved head and flow against the valve setting. Pump velocity is not a pipe velocity and is shown as a dash.
Water/liquid distribution hydraulics only. This does not simulate gas networks, water hammer, or water quality. EPANET’s Darcy–Weisbach correlations differ from the single-pipe calculator’s Colebrook implementation. Check the demand model, fluid properties, boundary conditions, and all reported warnings. Negative pressure under demand-driven analysis indicates a physically inadequate supply.
Engine: EPANET 2.2 via epanet-js 0.9.0, bundled locally. Runs stop after 60 seconds. Limits: 2 MB per file, 10,000 combined nodes and links, 2,000 hydraulic periods, and 500,000 result rows. Larger models should use desktop EPANET.