Commissioned Research
Top 10 Best Water System Design Software of 2026

GITNUXSOFTWARE REVIEW

Construction & Infrastructure

Top 10 Best Water System Design Software of 2026

Water system design software roundup comparing KYPipe, PCSWMM, and HydroCAD for engineers, with tradeoffs for pipe, runoff, and drainage modeling.

21 min readUpdated Editorially scoped research
How we ranked these tools
01Editorial Scope

Vendors set the topic, but our editors set the inclusion criteria and the evaluation framework before research starts.

02Source Research

Search agents gather the source set and the review record, including transcriptions of video reviews and podcasts.

Read our full methodology →

Framework: Features 40% · Ease 30% · Value 30%

Gitnux may earn a commission through links on this page. This does not influence our reviews. Editorial policy

Water system design software tools translate hydraulic and hydrologic requirements into models that teams can size, simulate, and document for permitting and design signoff. This comparison helps technical evaluators weigh schema and GIS data workflows, model fidelity for pipe networks and drainage, and integration paths that affect iteration speed and audit-ready outputs.

KYPipe is the best pick for engineers who iterate water network designs from GIS because its model-first editing keeps topology creation and export-ready deliverables in one workflow, while PCSWMM is the better fit for SWMM-centered stormwater and wastewater cycles since its SWMM-compatible run and connectivity management makes repeatable hydraulic checks easier.

Editor’s top 3 picks

Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.

Editor pick
1

KYPipe

Model-first editing with GIS-driven network creation and export-ready deliverables in one workflow.

Best for: Fits when engineers iterate network design using GIS inputs, then need consistent exports for hydraulic checks and drafting.

2

PCSWMM

Editor pick

SWMM-focused modeling and run management with UI tools that keep network connectivity consistent across iterations.

Best for: Fits when engineers need SWMM-aligned modeling and reliable output review for storm and hydraulic design cycles.

3

HydroCAD

Editor pick

Integrated fire flow adequacy checks with dedicated design report outputs across multiple demand scenarios.

Best for: Fits when hydraulic modeling needs repeatable scenario runs and CAD deliverables with EPANET exchange.

Comparison Table

1
KYPipeBest overall
SMB
9.4/10
Overall
2
vertical specialist
8.7/10
Overall
3
8.6/10
Overall
4
enterprise
8.3/10
Overall
5
8.0/10
Overall
6
vertical specialist
7.9/10
Overall
7
7.4/10
Overall
8
7.1/10
Overall
9
vertical specialist
6.9/10
Overall
10
enterprise
6.5/10
Overall
#1

KYPipe

SMB

Developer of PIPE2000 software for water distribution system modeling and analysis.

9.4/10
Overall
Features9.4/10
Ease of Use9.3/10
Value9.5/10
Standout feature

Model-first editing with GIS-driven network creation and export-ready deliverables in one workflow.

KYPipe organizes water network data around graph-like connectivity so that edits to pipes, junctions, and appurtenances propagate through the model state. The workflow supports importing GIS features for network skeletonization, applying pipe properties such as material or roughness inputs, and running hydraulic checks that feed design decisions. KYPipe’s export options support handoff to drafting environments like AutoCAD via DWG generation, which helps teams keep geometry and attributes aligned.

A key tradeoff is that the most specialized analysis tasks tend to depend on how well the workflow matches the chosen simulator path, so deep customization may be limited compared with tools that expose every simulation parameter directly. KYPipe fits best when teams need fast iteration on network topology, demand assumptions, and pressure outcomes, then produce consistent deliverables for review cycles.

Pros
  • +Web workflow for editing network topology and properties in one place
  • +GIS import supports building a usable model foundation from spatial data
  • +Export paths help maintain geometry plus attributes for drafting handoffs
  • +Repeatable configuration supports consistent design iteration across scenarios
Cons
  • –Advanced simulation parameter exposure is narrower than in specialist desktop tools
  • –Topology cleanup after GIS import can take manual passes for complex cases
  • –Large models may feel slower during interactive editing and validation
Use scenarios
  • Municipal engineering teams

    Iterate pressure outcomes after design edits

    Faster design review cycles

  • Consulting engineers

    Generate DWG deliverables from models

    Less drafting rework

Show 2 more scenarios
  • Water modeling specialists

    Calibrate pipe roughness inputs

    More consistent calibration runs

    Apply and adjust pipe property inputs while keeping network connectivity and attribute mapping consistent.

  • Engineering managers

    Standardize scenario configurations

    Lower variance across analysts

    Reuse configuration patterns so scenario variants keep assumptions aligned across a team workflow.

Best for: Fits when engineers iterate network design using GIS inputs, then need consistent exports for hydraulic checks and drafting.

#2

PCSWMM

vertical specialist

SWMM-based stormwater and wastewater modeling platform with GIS integration.

8.7/10
Overall
Features8.7/10
Ease of Use8.7/10
Value8.7/10
Standout feature

SWMM-focused modeling and run management with UI tools that keep network connectivity consistent across iterations.

PCSWMM pairs a WAT and water distribution workflow with a focused graphical interface for building and running storm and hydraulic network models. It supports model execution through the same SWMM engine logic that many engineers already use, so file-based exchange and repeatable runs map cleanly to established practices.

Import and editing tools target real-world geometry and network data, including layout and connectivity validation before simulation. Output handling supports the typical questions around flows, heads, and system behavior across steady-state vs extended-period schedules.

Pros
  • +Direct SWMM-compatible modeling workflow for repeatable hydraulic runs
  • +Editing tools make pipe, pump, and node connectivity changes easy to audit
  • +Simulation outputs align with common design checks and troubleshooting
  • +Supports both steady-state style checks and extended-period behavior
Cons
  • –Hydraulic model construction depends on disciplined network topology definition
  • –Automation and API surface are limited compared with workflow-scriptable toolchains
  • –Advanced GIS conditioning requires extra pre-processing outside the app
  • –Calibration iteration can be slower for large multi-zone networks
Use scenarios
  • Civil pipe designers

    Check buried pipe capacity and reinforcement

    Repeatable pipe documentation

  • Utility modelers

    Update network geometry and roughness inputs

    Operational review-ready model

Show 2 more scenarios
  • Stormwater design teams

    Compare detention storage and routing outcomes

    Downstream flow comparison

    Evaluates detention behavior and hydrograph routing across alternative boundary conditions for stormwater plans.

  • Hydraulic calibration specialists

    Tune parameters against time-series observations

    Better observed match

    Compares modeled results to field observations and adjusts parameters for wet-weather or operational studies.

Best for: Fits when engineers need SWMM-aligned modeling and reliable output review for storm and hydraulic design cycles.

#3

HydroCAD

SMB

Stormwater modeling software for detention pond and drainage system design.

8.6/10
Overall
Features8.6/10
Ease of Use8.6/10
Value8.6/10
Standout feature

Integrated fire flow adequacy checks with dedicated design report outputs across multiple demand scenarios.

HydroCAD runs water conveyance and distribution hydraulic modeling from a detailed component network of pipes, valves, pumps, and storage. It focuses on engineering workflows for pressure and headloss calculations, including peak demand and fire flow adequacy checks.

The software supports EPANET compatibility for exchanging network models, while its reporting and scenario management are geared toward iterative design reviews. AutoCAD DWG export helps transfer layouts and model context into deliverable CAD documents.

Pros
  • +Strong scenario-based design iteration for pressures, flows, and fire flow targets
  • +Flexible network component modeling supports valves, pumps, reservoirs, and storage
  • +EPANET compatibility supports network model exchange with other hydraulic workflows
  • +AutoCAD DWG export supports layout handoff to deliverable CAD drawings
Cons
  • –GIS import needs careful preprocessing before topology validation and assignment
  • –Transient and extended-period analysis depth can lag teams focused on time-varying operations
Use scenarios
  • Civil engineering consultants

    Produce drainage review calculation packages

    Structured design review outputs

  • Stormwater and civil engineers

    Size detention pond stage and discharge

    Documented detention behavior

Show 2 more scenarios
  • Land development engineering teams

    Model subdivision drainage during layout iterations

    Iteration-ready drainage sizing

    Simulates site catchments, pipes, junctions, and storage to generate sizing results for land development.

  • Site drainage engineers

    Analyze stormwater pipe networks under surcharge

    Hydraulic checks for sizing

    Evaluates pipes, junctions, inlets, surcharge conditions, and hydraulic grade lines for design storms.

Best for: Fits when hydraulic modeling needs repeatable scenario runs and CAD deliverables with EPANET exchange.

#4

Deltares

enterprise

Research institute providing WANDA and SOBEK software for water system analysis.

8.3/10
Overall
Features8.3/10
Ease of Use8.3/10
Value8.3/10
Standout feature

Calibration-driven network iteration with tight control over hydraulic parameters during validation runs.

Deltares is used to build and validate network models where pipe roughness calibration, valve behavior, and demand allocation choices materially change computed headloss and pressures. The workflow supports GIS imports for building skeletons and aligning network geometry to terrain, then iterating scenarios through model calibration and network checks. Hydraulic modeling output can feed downstream decisions like pressure zone delineation and fire flow adequacy assessments. The primary fit signal is engineering control over modeling assumptions and repeatable scenario runs.

Pros
  • +Strong engineering workflow for calibration and scenario validation
  • +GIS-aligned network preparation supports terrain-aware modeling
  • +Detailed control over hydraulic assumptions for network performance studies
  • +Repeatable multi-scenario analysis supports model comparison
Cons
  • –Automation surface leans on workflow standardization and file interchange
  • –Collaboration governance like granular RBAC and audit log is not its focus
  • –Extended setup effort for data conditioning and network cleanup
  • –Deep integration with design CAD often requires pipeline glue
Use scenarios
  • Water utility network engineers

    Pressure and demand scenario comparison

    More defensible operating decisions

  • Consulting modelers

    GIS-to-hydraulic model production

    Faster model preparation cycles

Show 2 more scenarios
  • Program managers for capital works

    Fire flow adequacy studies

    Clearer mitigation options

    Run scenario evaluations that assess hydraulic capacity and system response for critical fire flow cases.

  • Academic and research teams

    Hydraulic analysis workflow reproducibility

    More reproducible findings

    Maintain controlled modeling assumptions across experiments with consistent inputs and scenario definitions.

Best for: Fits when engineering teams need calibrated hydraulic models and repeatable scenario validation with GIS-aligned data.

#5

Pipe Flow Software

SMB

Developer of Pipe Flow Expert for pipe network pressure drop and flow calculations.

8.0/10
Overall
Features8.0/10
Ease of Use8.0/10
Value8.0/10
Standout feature

Calibration-focused adjustments let teams iteratively align observed behavior with modeled headloss and flow results within scenario sets.

Pipe Flow Software is designed around iterative network studies where pipe roughness calibration, demand-driven or pressure-driven behavior, and multiple simulation scenarios need to be compared consistently. The interface supports building and editing network elements, running hydraulic analysis, and reviewing pressures, flows, and system performance indicators across steady-state and extended-period cases. Integration support is geared toward reusing existing network geometry and attribute sources rather than redrawing everything inside the model.

Pros
  • +Strong scenario comparisons across steady-state and extended-period studies
  • +Practical calibration workflow tied to headloss and flow outcomes
  • +CAD and GIS data exchange supports reuse of existing network geometry
  • +Engineering outputs cover pressure, flow, and fire flow evaluation tasks
Cons
  • –Limited emphasis on API automation for model provisioning and batch runs
  • –Complex model edits can feel slower than CAD-first workflows
  • –Some integrations depend on correct data preparation before import
Use scenarios
  • Municipal engineering analysts

    Calibrate roughness and validate operations

    Better match to field conditions

  • Water utility design teams

    Fire flow adequacy checks

    Identified adequacy gaps

Show 1 more scenario
  • GIS-CAD coordination teams

    Reuse assets across tools

    Reduced redraw effort

    Import topology and attributes from GIS and export results back to CAD-style deliverables.

Best for: Fits when teams need repeatable network scenarios with calibration feedback and clear engineering outputs.

#6

MagiCAD

vertical specialist

BIM and CAD software for MEP design including plumbing and water systems.

7.9/10
Overall
Features7.9/10
Ease of Use7.9/10
Value7.9/10
Standout feature

CAD-linked network data authoring that preserves element attributes during analysis input generation.

MagiCAD targets water system design work that centers on CAD-based modeling and hydraulic calculation handoff. It supports building a network layout in a familiar drawing workflow, then generating analysis-ready datasets for water distribution network analysis and related steady-state studies.

Pros
  • +CAD-native editing keeps network topology aligned with drawings
  • +Repeatable export steps reduce re-entry when model geometry changes
  • +Supports common water distribution network analysis workflows
  • +Element-level controls make pipe attributes easier to keep consistent
Cons
  • –Advanced analysis automation depends on external modeling and data exchange
  • –Extensibility and API surface are not evident for custom hydraulic pipelines
  • –Complex multi-scenario studies can require extra model management
  • –GIS-heavy workflows can need preprocessing before network import
Use scenarios
  • HVAC and sheet-metal designers

    Run pressure-loss sizing across duct branches

    Repeatable sizing outputs

  • MEP coordination teams

    Revise layouts without breaking documentation

    Fewer disconnected updates

Show 2 more scenarios
  • Fire protection designers

    Design sprinkler layouts with calculation-linked iteration

    Coordinated sprinkler plans

    Places sprinkler heads and connected piping while keeping calculation-linked iterations coordinated across revisions.

  • Plumbing engineers and contractors

    Generate shop drawings and schedules

    Consistent construction documentation

    Models water supply and sanitary drainage systems and generates plans, isometrics, risers, and schedules for construction.

Best for: Fits when engineers need CAD-first network modeling and repeatable export-to-analysis workflows for steady-state studies.

#7

Fluidit

SMB

Provider of Fluidit Water and Fluidit Sewer for network data management and hydraulic modeling.

7.4/10
Overall
Features7.4/10
Ease of Use7.4/10
Value7.4/10
Standout feature

EPANET analysis is tied to a model editor workflow so engineers can adjust attributes and re-run scenarios without leaving the modeling loop.

Fluidit focuses on water system hydraulic modeling workflows with a built model editor for network geometry, connectivity, and attributes. It supports EPANET-based analysis so engineers can run headloss and demand-driven scenarios in the same modeling environment.

Pros
  • +EPANET-compatible analysis execution from a dedicated network model
  • +GIS-assisted import reduces manual node and pipe re-creation effort
  • +Scenario reruns support repeatable calibration and what-if comparisons
  • +Attribute-centric editing for pipes, junctions, and controls
Cons
  • –Less direct workflow coverage for Civil 3D drafting to hydraulic transfer
  • –Limited visibility into advanced validation tooling for topology issues
  • –Automation depth depends on export-and-reimport patterns
  • –Transient and extended-period workflows require careful model setup discipline
Use scenarios
  • Water engineers

    Model geometry and connectivity in editor

    Faster model creation

  • GIS-assisted design teams

    Move network designs between GIS and analysis

    Reduced data rework

Show 1 more scenario
  • Operations-focused modelers

    Rerun scenario configurations consistently

    Consistent rerun results

    Emphasizes configuration and scenario reruns so engineers can evaluate changes without rebuilding one-off cases.

Best for: Fits when teams need consistent EPANET-driven network analysis with GIS-assisted model setup and scenario reruns.

#8

h2x Engineering

SMB

Cloud-based plumbing and water system design software for building services.

7.1/10
Overall
Features7.1/10
Ease of Use7.0/10
Value7.2/10
Standout feature

Configuration-driven network study templates that keep model inputs consistent across revisions and drawing deliverable updates.

h2x Engineering targets water system design workflows that need tight coupling between hydraulic modeling inputs and engineering drawing deliverables. Core capabilities center on water distribution network analysis support, including EPANET compatibility for modeling and results review.

Pros
  • +Supports EPANET-compatible modeling workflows for distribution analysis
  • +Emphasizes configuration reuse across recurring network studies
  • +Integrates modeling inputs from CAD and GIS source data
  • +Produces engineering outputs aligned with drawing-centric review cycles
Cons
  • –Less automation depth than code-first pipelines for batch scenario runs
  • –Topology validation and QA tooling are narrower than some engineering toolchains
  • –API and extensibility surface is limited compared with scriptable ecosystems
  • –Demand allocation and pressure zone workflows can require manual setup discipline
Use scenarios
  • Water utility model engineers

    Run EPANET workflows with drawdown-ready outputs

    Consistent study outputs

  • GIS-to-model integration teams

    Transform GIS and CAD data into simulations

    Rerun without rebuild

Show 1 more scenario
  • Extended-period study teams

    Parameterize steady-state and EP simulations

    Repeatable scenario testing

    Uses configuration-driven modeling controls to support both steady-state and extended-period scenarios reliably.

Best for: Fits when teams need repeatable hydraulic studies tied to CAD and GIS workflows without building custom automation.

#9

Carlson Civil

vertical specialist

Civil design suite with storm sewer and hydrology tools for land development.

6.9/10
Overall
Features6.9/10
Ease of Use6.9/10
Value6.9/10
Standout feature

CAD-centric utility network editing that keeps geometry and attributes synchronized for analysis-ready export.

Carlson Civil is a civil design workflow tool used to build water distribution models from CAD and GIS inputs, then prepare network data for hydraulic analysis. The software focuses on maintaining GIS-aligned geometry and attributes while supporting utilities-specific drafting and model cleanup before export.

Pros
  • +CAD-first network editing for pipes, nodes, and attributes
  • +Attribute-driven model cleanup workflows for connectivity accuracy
  • +Repeatable project setup for large network revisions
  • +Interoperability support for EPANET-style analysis preparation
Cons
  • –Hydraulic analysis depth depends on external modeling execution
  • –Automation and API surface for provisioning appears limited versus code-first integrations
  • –Limited native support for network-level GIS topology validation
  • –Extended-period modeling work requires careful pre-export data hygiene
Use scenarios
  • Utility CAD drafters

    Prepare GIS-aligned water distribution inputs

    Analysis-ready network data

  • Survey-to-design teams

    Transfer measured geometry into design models

    Less geometry reconstruction

Show 2 more scenarios
  • Civil consultants for RV sites

    Plan utilities and grading for recreational parks

    Coordinated site deliverables

    Supports CAD-based layout and utility routing with civil drafting tools to produce coordinated site documentation.

  • Environmental utility consultants

    Produce coordinated utility and septic site plans

    Coordinated utility drawings

    Creates site plans with grading, surfaces, and utility routing components for utility-focused projects.

Best for: Fits when water teams already run Civil 3D-style drafting workflows and need dependable network data prep for external hydraulic runs.

#10

Innovyze

enterprise

Provider of water distribution and wastewater modeling software including InfoWater and InfoSWMM.

6.5/10
Overall
Features6.5/10
Ease of Use6.5/10
Value6.5/10
Standout feature

Topology validation workflows that check connectivity and isolation before simulation runs, reducing downstream troubleshooting.

Innovyze targets water system design and hydraulic modeling workflows with a GIS-first approach and engineering-grade network tools. Core capabilities include demand and pressure analysis tied to model geometry, plus model checking for network topology consistency before running simulations.

Pros
  • +GIS-linked network building reduces manual coordinate cleanup
  • +Topology validation catches connectivity and isolation issues before runs
  • +EPANET workflows support teams mixing modeling engines
  • +Automation-friendly modeling patterns for phased design revisions
Cons
  • –Advanced setup requires discipline across layers, zones, and attributes
  • –Civil 3D interchange often needs format-specific QA for layers and properties
  • –Extended-period studies take more tuning than simple steady-state cases
  • –Large models can feel slower when iterating many scenarios
Use scenarios
  • GIS-centered water modelers

    Check topology before running simulations

    Fewer model errors

  • Water pressure analysis teams

    Analyze demand and pressure tied to geometry

    Clear performance assessment

Show 1 more scenario
  • Civil 3D and GIS pipeline teams

    Automate model exchange across tools

    Less repetitive modeling

    Uses scripting hooks and model-management features to reduce repeat modeling work across project phases using common exchange formats.

Best for: Fits when GIS-based water network teams need repeatable hydraulic scenarios and engine flexibility.

Conclusion

After evaluating 10 water system design software, KYPipe stands out as our overall top pick — it scored highest across our combined criteria of features, ease of use, and value, which is why it sits at #1 in the rankings above.

Our Top Pick
KYPipe

Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.

Frequently Asked Questions About Water System Design Software

How does EPANET compatibility differ across HydroCAD, Fluidit, and h2x Engineering for day-to-day workflow?
HydroCAD supports EPANET compatibility with EPANET-aligned model exchange plus scenario and reporting for iterative design reviews. Fluidit ties EPANET-based analysis to a built model editor so engineers can rerun demand-driven scenarios after changing attributes. h2x Engineering uses EPANET-compatible modeling support inside configuration-driven study templates that keep demand and asset parameterization consistent across CAD and GIS revisions.
Which toolset is better for calibration-driven model iteration when observed data must match headloss and flow results?
Deltares is built around calibration-driven network iteration with tight control over hydraulic parameters during validation runs. Pipe Flow Software focuses on calibration feedback inside scenario management so headloss and flow alignment is preserved across repeated studies. Innovyze also supports engineering-grade model checking, but its emphasis lands more on topology validation than calibration parameter workflows.
How should teams choose between KYPipe and MagiCAD when the primary authoring surface is GIS-first versus CAD-first?
KYPipe uses a web workflow that drives model setup from GIS-linked inputs, then produces export-ready outputs for hydraulic checks and drafting. MagiCAD centers on CAD-based network layout and generates analysis-ready datasets while preserving CAD element attributes for water distribution network analysis. Teams that start with Civil 3D-style drawing edits usually find MagiCAD fits the editing loop better, while GIS-led teams typically benefit from KYPipe’s model-centric pipeline.
When model assembly errors show up as disconnected nodes or bad connectivity, which workflow catches issues before simulation runs?
Innovyze provides topology validation steps that check connectivity and isolation before running simulations. h2x Engineering uses configuration-driven modeling controls designed to keep demand and asset parameterization consistent across revisions, which reduces repeated input mistakes. Deltares supports network topology validation as part of engineering-grade data preparation used in GIS-to-network modeling pipelines.
Where does PCSWMM fit versus PCSWMM-style SWMM-aligned workflows, and what breaks if a project needs EPANET-native exchange?
PCSWMM runs storm and hydraulic network models using SWMM engine logic, so the workflow and output expectations match SWMM modeling practice. Fluidit and HydroCAD target EPANET-based analysis, so EPANET-native exchange and reruns are more natural there than a SWMM-first UI loop. If a project workflow requires EPANET-aligned model interchange in multiple phases, PCSWMM can force file-based conversion work that complicates repeatable study governance.
How do scenario management and rerun mechanics compare across Pipe Flow Software, HydroCAD, and Fluidit?
Pipe Flow Software organizes repeatable design studies through model assembly, scenario management, and result review in a scenario set workflow. HydroCAD emphasizes iterative scenario runs with design report outputs that support pressure and headloss calculations plus fire flow adequacy checks. Fluidit emphasizes repeatable configuration and scenario reruns by keeping the EPANET analysis tied to the model editor so attribute edits propagate into reruns.
What is the tradeoff between open CAD export control in MagiCAD and topology-calibration control in Deltares for steady-state versus extended-period studies?
MagiCAD preserves CAD element attributes during analysis input generation, which reduces manual re-entry when steady-state deliverables must track drawing edits. Deltares prioritizes calibration-driven control and supports multi-scenario simulations across steady-state and extended-period behavior, which helps when model realism depends on parameter alignment. The tradeoff is that CAD-linked authoring speed in MagiCAD can conflict with the deeper calibration iteration loop required in Deltares for extended-period fidelity.
How do teams migrate data models when starting from GIS layers and moving into hydraulic modeling inputs in Innovyze, Carlson Civil, and Deltares?
Innovyze supports GIS-first model checking and demand and pressure analysis tied to model geometry, which helps maintain alignment from GIS inputs into hydraulic runs. Carlson Civil focuses on GIS- and CAD-aligned geometry and attributes while preparing network data for hydraulic analysis exports. Deltares supports GIS-to-network modeling pipelines and includes data preparation steps used with geospatial inputs and terrain-aware constraints.
How do admin controls and security differ in practice for enterprise governance across these water modeling platforms?
None of the listed tools expose admin controls details in a way that can be compared purely by capability description here, but enterprise governance typically depends on RBAC scope, audit log coverage, and provisioning model. Deltares and Innovyze emphasize engineering-grade workflows and automation hooks, which affects how controlled changes are tracked across scenario iterations. KYPipe’s web workflow changes the governance surface because approvals and input edits concentrate in the web model environment rather than only in desktop model authoring.

Tools reviewed

Primary sources checked during evaluation.

Referenced in the comparison table and product reviews above.

How to Choose the Right Water System Design Software

We separate water system design software by how far it goes beyond drawing: model import/export and automation surface determine whether teams can keep hydraulic networks consistent across updates. The most noticeable differences usually show up in EPANET compatibility, API/automation, and RBAC with audit logging.

EPANET file and solver compatibility

Why it matters

When EPANET compatibility is strong, you can reuse prior models and avoid silent interpretation differences that break design assumptions. Weak compatibility forces rework and makes comparisons across revisions harder.

How to check

In the demo, load a sample network and confirm it runs to the same expected results after saving and reloading. Then ask the team to show what happens to key sections like junctions, pipes, and controls when you round-trip a file.

Data model mapping for network objects

Why it matters

Water networks live or die by data model mapping accuracy. If object attributes and units don’t map predictably, you’ll chase discrepancies instead of design decisions.

How to check

Ask for a sample model with non-default units or custom fields and import it. Verify that labels and parameters stay attached to the same network objects after editing and exporting.

API and automation for batch runs

Why it matters

API and automation matter when you run many scenarios or coordinate with other workflows. Without a clear automation surface, teams rely on manual clicks and lose reproducibility.

How to check

Ask what automation options exist: a scriptable interface, a job API, or a batch-run workflow. Request a simple scenario generation demo (e.g., change boundary conditions across a set) and show where outputs land.

Audit logs and change traceability

Why it matters

Audit logs and change traceability let teams answer “what changed and why” when designs diverge. This reduces review time and prevents accidental overwrites during iterative edits.

How to check

Create a small change (e.g., modify a pipe attribute) and check whether the system records who, what, and when. Then try reverting or comparing before/after states during the demo.

RBAC with review workflows

Why it matters

RBAC with review workflows keeps model edits controlled when multiple roles touch the same network. It also clarifies who can publish design outputs.

How to check

In the demo, request role examples such as viewer, editor, and reviewer. Show how permissions affect editing and whether a publish or lock step exists before results are shared.

Result outputs and report reproducibility

Why it matters

Result outputs and report reproducibility determine whether reviewers can trust what they see. When outputs don’t match across exports or re-runs, sign-off becomes subjective.

How to check

Run the same case twice: once immediately and once after saving/reloading. Compare result tables and plots, then export a report and verify key numbers match.

Red flags

  • Imports run but key parameters shift after round-trip saving
  • Automation exists only as manual export steps with no job interface
  • Audit trails show timestamps but not clear before/after model details

Fit by situation

  • If your workflow starts from existing EPANET models, prioritize EPANET file and solver compatibility.
  • If you run many scenarios and need repeatability, prioritize API and automation for batch runs.
  • If multiple people edit the same network before sign-off, prioritize RBAC with review workflows.
Commissioned Research

Funding and competing interests

This study was co-funded by several of the vendors assessed in it. No single vendor funded it. Funders could propose the market studied.

They had no role in selecting vendors, setting or weighting criteria, analysing data or drawing conclusions, and they received the same factual-accuracy check as every other vendor assessed.

Market definition, inclusion rules and criteria weights were fixed by an editor before research began and did not change afterwards. Editorial process →

Keep exploring

FOR SOFTWARE VENDORS

Not on this list? Let’s fix that.

Our best-of pages are how many teams discover and compare tools in this space. If you think your product belongs in this lineup, we’d like to hear from you—we’ll walk you through fit and what an editorial entry looks like.

Apply for a Listing

WHAT THIS INCLUDES

  • Where buyers compare

    Readers come to these pages to shortlist software—your product shows up in that moment, not in a random sidebar.

  • Editorial write-up

    We describe your product in our own words and check the facts before anything goes live.

  • On-page brand presence

    You appear in the roundup the same way as other tools we cover: name, positioning, and a clear next step for readers who want to learn more.

  • Kept up to date

    We refresh lists on a regular rhythm so the category page stays useful as products and pricing change.