Pressure network modelling
Define pressure networks of junctions, tanks, reservoirs, pipes, pumps and valves, and run them through bundled EPANET.
Run pressure network scenarios on the EPANET solver as background jobs you can follow and cancel, then read pressures and flows over time at every node and link. Each run stays verifiable against the network and scenario that produced it.
Your engineers work in the desktop workbench; your agent reaches the same project through typed local tools. Items tagged In development are being built now.
Define pressure networks of junctions, tanks, reservoirs, pipes, pumps and valves, and run them through bundled EPANET.
Run saved networks and scenarios on the bundled EPANET 2.2 solver as background jobs you can follow and cancel.
Read node and link result series across the whole run period.
Check that a retained run still matches the network and scenario that produced it.
List every pressure run and job for the open project, with each run archived for later review.
Hydraulic parameters stored in scenario files separate from the solver run.
A catalogue of pressure pipes, fittings and layout rules for drawing networks in plan.
“Run the peak-hour scenario and list every node below 25 m of pressure.”
“Compare node pressures between the average-day and peak-hour scenarios.”
“Verify yesterday’s run still matches the saved network before I issue the report.”
Reserve your early-access seat. We confirm your MCP client, seat count and commercial details before access opens.
Reserve your seat ↗