Ideas

Showing 12 of 1370

Provide Velocity Constraint in Multi-Fireflow

Provide the ability to limit velocity for the multi-fireflow run option. Presently only the Fireflow run option offers a max velocity constraint capability; the Multi-Fireflow run option does not have a max velocity feature.

Guest 11 months ago in InfoWater Pro / Engine 0 Under consideration

2 VOTE

Steady state simulations for different times or for average demand

Steady state simulations are useful for 1) evaluating an initial or simplified version of a model (for example with average demands) or 2) evaluating a specific condition (like maximum demand, etc.) without much complexity. If your model is alread...

Felipe Hernandez 4 months ago in InfoWater Pro / Engine 0 Gathering support

3 VOTE

InfoSurge velocity results

Please add pipeline velocities to the results for surge simulations. This really helps when designing surge tanks and connecting pipelines.

Guest 8 months ago in InfoWater Pro / Engine 1 For Review

4 VOTE

Add the ability to drain subcatchments to the grate of a gully

When importing models from XPSWMM to ICM, my subcatchments drain directly to the node where an inlet capture curve is applied to limit flow to the 1d system. I would like to replicate this behavior easily in ICM when nodes are connected to the 2D ...

Sophia Buchanan almost 2 years ago in InfoWorks ICM / Inlets 0 Gathering support

3 VOTE

Enforce velocity constraint on all pipes during Fireflow

InfoWater Pro offers the ability to constrain Fire flow at hydrants so that the max velocity in pipes doesn't exceed a specified threshold. Currently the only option is to enforce this on "Connected Pipes", assuming that the last pipe reaching the...

Nathan Gerdts over 1 year ago in InfoWater Pro / Engine 1 Gathering support

3 VOTE

modeling surge check valves

I’m also wondering if you all are considering adding more options on how to model check valves.

Guest about 2 years ago in InfoWater Pro / Engine 1 Gathering support

2 VOTE

Drain nodes connected to 2d domain representing road gullies to 1D pipe network without digitised connection

Often datasets of road gullies are only in point format and lack details on the connections to the surface water sewer network. A function to allow 1D nodes representing road gullies (which are are connected to the 2D domain with a head discharge ...

Guest over 1 year ago in InfoWorks ICM / Inlets 0 Gathering support

1 VOTE

Hydrant Design Flow vs Available Flow!

I don't like the new update, which makes the available flow subject to a velocity constraint. In the previous version, the pressure constraint was on the hydrant flowing, while the design flow would consider the network pressure and pipes. They sh...

Guest 11 months ago in InfoWater Pro / Engine 0 For Review

3 VOTE

Include an "excluded search nodes" warning in fireflow output table

When the design pressure exceeds the static pressure at a particular node, that node will be excluded from a design fireflow model run. The output table should include a banner at the top listing the excluded nodes, as these can make a big differe...

Guest over 4 years ago in InfoWater Pro / Engine 0 In progress

3 VOTE

inlet riser option for tank

Have an option to specify an Inlet Riser Pipe for the tank element. This would hold the fill head at a constant, set at the riser pipe elevation, but allow the tank discharge head vary with the tank level.

Guest almost 5 years ago in InfoWater Pro / Engine 0 Gathering support

Please enter your email address

FILTER BY CATEGORY