Storm Sewer & Flood Modeling
Welcome to the Innovyze Stormwater, Sewer, and Flood modeling feedback page.
298 results found
-
Include a new conduit type for tile drains
Add a new conduit type to model tile drains or underdrains. These are common in agricultural fields and certain stormwater control structures. Currently, its difficult to model these since you can't account for the time it takes to infiltrate from the surface to the drain based on its depth.
2 votes -
Use PDM Soil moisture deficit variable to trigger RTC
Just like you can set thresholds or target values for level or flow in an RC I would like to be able to use the Soil moisture deficit variable from PDM subcatchment to regulate structures or variable pumps. This could be useful to somewhat reproduce the behavior of water users such as pond fishermen or irrigating farmers.
5 votes -
Sediment depth variable for Storage nodes
It appears that amounts of sediment are carried along when water is overflowing over the banks of the river: part of the sediment from sediment fractions SF1 and SF2 leaves the river and goes to the Storage Areas during flooding. Although this is taken into account in the sediment balance, there is no variable being saved for the Storage Node in order to know how much sediment may accumulate in that storage area, nor can it be exported or visualized. Could you add the quality variable "sediment depth" present for the river sections also for the storage node (you don't…
3 votes -
Update French rainfall to include multiple durations
Ability to add more than 1 duration per return period in a single rainfall object.
There are 3 sets of parameters for durations 6 < t < 60, 60 < t < 360 and 360 < t < 24hr.
It would be useful to be able to add these parameters for each return period and then select a number of durations.
6 votes -
Ability to use variables in range RTC rules
For RTC range rules, we want to be able to use variables instead of constant values for the minimum and maximum values.
10 votes -
Simplify the Ground Water Model
Simplify the InfoWorks Ground Water model Or GIM by using only the Ground layer instead of two layers Soil and Ground.
Don’t use the soil store component of the GIM.
Innovyze, please simplify the conceptual design of the GIM by reducing it to one layer.
1 vote -
Order ARR19 Box and Whisker plots by duration
The box and whisker plot outputs order alphabetically. It would be useful if it ordered based on rainfall event duration instead.
4 votes -
Graph sum of multiple objects instead of each selected object
While looking at multiple drainage areas in a basin (in my example), results can become hard to read; it would be nice if you could graph multiple objects and have the option to see the summation of the selection instead of each individual item.
2 votes -
Compare WWG and TWG files
A tool to compare different WWG files and TWG files and report on the differences, similar to the Compare functionality for Networks.
1 voteThanks for the idea!
-
I would like improvements for ICM with SWMM engine
add ICM SWMM functionalities that are already available in ICM with regular engine
- Area take off
- Population data
- CN/Runoff coeff. lookup
-Create dummy boundaries15 votes -
Enable RTK parameters to use rain gauge boundaries
Enable RTK parameters to use rain gauge boundaries with the SWMM5 engine
2 votes -
section view of ground model and 2d mesh
It would be very usefull to be able to generate a section view of both a ground model and a generated 2d mesh. At the moment this is only possible in a flood section after a simulation.
So it should be not too difficult to move this possibility also to a network before simulating.
3 votes -
Export statistical template results automatically as part of the manifest.
Particularly CSO spill statistics - enabling models to be run maybe weekly with historical data, the statistics exported - spill nr, duration and particularly predicted volume. This data can then be analysed in tools outside of ICMLive. This data would significantly enhance the understanding of CSO spills by adding volume to the normal Event Duration Monitoring
7 votes -
As a user i want to see 'failed' simulations within the Results Management Window rather than 'completed' status
When a sim completes as status Incomplete the sim icon changes to red and the Job control window states sim status Incomplete. However, in the Results Management window the sim status is ‘Complete’!
For consistency and user friendliness; Please can you fix to reflect the status Incomplete? This change will make re-running sims so much easier and save end users not having to delve into IDs to work out which sim need investigation.
3 votes -
As a user I want to be able to adjust dry weather flow diurnal profiles easily to account for day light savings
Diurnal wastewater and tradewaste profiles shift over the course of the year due to day light saving time adjustments. I would like to see ICM include the ability to phase shift the diurnal patterns to account for DLS. I believe this adjustment would be best placed in the "monthly calibration" tab where in addition to the scaling "factor' there is also a time adjustment factor
1 vote -
Need additional Timestep function for "Between episodes" of "Simulation runoff only"
It needs creating a new Timestep function in ICM Run window that allows setting up timestep for "Simulation runoff only" for the "Between episodes" separately with "Timestep (s)" in Run window. This new function saves a lot of running time when the model can simulate the runoff only with larger time step using the "Episode Collection"
2 votes -
Scenario assigned 'official' ID numbers within software
I would like for scenario names to be prefixed with a built-in ID number, in the same way that model commits have official version numbers, and wastewater and trade waste profiles have ID numbers. ICM clearly tracks ID numbers behind the scenes, since it is able to keep the scenarios in the same order (rather than sorting them alphabetically or similar).
When specifying exactly which 'model' was used to produce a set of simulation results, it is necessary to specify network ID, version ID and scenario ID - so it would be helpful to be able to just point to…
1 vote -
compatibility with WMTS servers
Compatibility with WMTS servers for the GIS layer control would be very urgent. Right now a lot of data is only to project from WMTS servers.
1 vote -
Commit history for scenarios
Commit history for scenarios
Show an extra column in the commit history window to indicate how many scenarios exist in this version of the network. Ideally, there would be a button or column through which you can see the names of the scenarios for this network version.10 votes -
Add Data Sets to InfoWorks
Add Data Sets to InfoWorks as one can do in InfoSWMM. Helpful when clients want to model alternatives scenarios and make last minute changes.
2 votes
- Don't see your idea?