Stage capital upgrades and plan long-term network growth

Model projected demands across 5-, 10-, and 20-year horizons. Group proposed assets into modular change sets, stage capital works across multi-year cycles, and re-sequence projects without breaking scenario trees.

Long-term capital planning on a reliable scenario foundation

Master plans and Capital Improvement Plans (CIP) dictate where hundreds of millions in infrastructure investments are committed over multi-decade horizons. Sizing trunk mains, siting reservoirs, and staging booster stations requires modeling future development and rising demands to ensure reliable pressure and fire protection for years to come.

In traditional software, long-term scenario management is notoriously brittle. Branching deep scenario trees often corrupts parent-child relationships, while duplicating network models creates fragmented file sets that quickly fall out of sync. epanet-js uses an inheritance-based staging architecture: future capital works are grouped into modular change sets that can be re-sequenced, advanced, or deferred across planning horizons without destabilizing downstream models.

Draw proposed assets once, activate across stages

Lay out planned transmission lines, storage tanks, and pump stations directly on the network map and set them out of service. Proposed assets remain part of the project's spatial fabric without impacting current baseline runs.

When configuring staged scenarios, simply activate the specific assets scheduled for that horizon. The same drawn assets serve every scenario combination, eliminating duplicate geometry and ensuring pipe properties remain consistent across all evaluated alternatives.

Inherit growth across 5-, 10-, and 20-year horizons

Structure your capital plan into clear operational milestones—such as Year 5, Year 10, and Year 20. Each horizon inherits the infrastructure upgrades and base demands of the preceding stage, accurately mirroring how a distribution network expands in the field.

Simulate any stage independently to verify minimum pressure compliance, peak-hour velocities, and available fire flow under projected future loads.

Re-sequence capital works without unpicking the model

Capital schedules change as development timelines shift, budgets adjust, or grant funding is secured. In epanet-js, every proposed improvement project is an isolated change set rather than a hardcoded model branch.

If a pump station upgrade slips from Year 5 to Year 10, simply move that change set to the later milestone. Downstream scenarios inherit the updated timing automatically, with zero redrawing, missing connections, or file reconciliations.

Build a well-justified, evidence-backed capital program

With modular change sets and on-demand scenario runs, planning shifts from static guess-and-check to systematic optimization: identifying the exact sequencing and infrastructure sizing needed to maintain regulatory pressures and fire flows with minimal upfront capital.

The result is a transparent, staged investment program supported by clear hydraulic evidence—ready for technical reviews, council presentations, and rate-case filings.

Planning capabilities in epanet-js

Model long-term horizons

Simulate how distribution networks perform years ahead as population shifts, developments connect, and demand patterns evolve.

Test growth and demand scenarios

Apply localized growth forecasts to identify exactly when and where transmission lines or storage reach capacity limits.

Stage capital upgrades

Lay out reinforcements across 5-, 10-, and 20-year horizons and re-sequence projects between stages without redrawing network geometry.

Support capital improvement plans (CIP)

Compare competing project sequences and capital timing to construct an evidence-backed, prioritized investment schedule.

Put your capital plan to the test

Stage your future infrastructure, adjust project sequences, and evaluate long-term performance across competing capital pathways.

Built on the same model as your daily operations

Long-term planning should not be locked in an isolated model that gathers dust between five-year master planning cycles. In epanet-js, long-term staging and short-term operational analysis share the exact same network model and calibration data. The same foundation you use for operational modeling and model calibration supports your 20-year master plan.

Explore related modeling solutions

Planning connects directly to the rest of your modeling pipeline.

Frequently asked questions

Frequently asked questions about long-horizon staging and capital planning.

What is a scenario in epanet-js?
A scenario is a structured branch of your baseline network that captures demand variations, proposed assets, and operational status changes without duplicating the underlying model file. In planning workflows, scenarios stack into successive stages (such as Year 5, Year 10, and Year 20) to reflect cumulative infrastructure growth over time. Read our scenarios architecture RFC for design details.
How does multi-year staging work?
You lay out proposed infrastructure directly on the map and mark it as out-of-service. Each horizon scenario then activates the specific assets planned for that timeframe alongside that stage's projected demands. Each stage inherits the infrastructure of the stage before it, ensuring the network evolves realistically from one planning phase to the next.
Can I adjust a project's timeline (e.g., from Year 5 to Year 10)?
Yes. Every capital improvement is encapsulated as a discrete, modular change set. If a trunk main or booster upgrade is deferred from Year 5 to Year 10, you simply reassign that change set to the later stage. Downstream scenarios automatically update, keeping network connectivity consistent without requiring manual re-edits.
How do I compare alternative investment pathways?
Because change sets are modular, you can branch scenarios to compare competing engineering strategies—such as constructing a new storage reservoir versus upsizing an existing transmission main. You can evaluate pressure compliance, fire flow capacity, and capital timing across multiple pathways side by side.
How does this support master planning and capital programming?
A master plan or Capital Improvement Plan (CIP) requires rigorous hydraulic justification. The staged scenarios, sequencing evaluations, and capacity checks run in epanet-js provide the verifiable data—pressures, velocities, and available fire flows under projected loads—that substantiate your capital recommendations.

Model your entire planning horizon in one project

Build an actionable, staged capital program behind your next master plan. Launch epanet-js free, or schedule a technical walk-through with our team.