Could we have a 'Node level affects groundwater infiltration' for the soil store please?
This simulation parameter was introduced to InfoWorks ICM recently to limit infiltration from the ground store to the model. Could this be extended to limit flows from the soil store as well?
As often when are using models for design purposes, infiltration can become excessive in design events compared to verification. Therefore we have to manually reduce soil store inflow, often requiring new limiting discharge orifices and nodes at each subcatchment with GI applied. Thanks

As part of our ICM Live system we use the Siltation module. While this creates a dynamic siltation on each pipe, there isn't an easy way to manage it. Once a pipe is cleaned we need to stop the live model and potentially apply all the dynamic silt levels to the conduits as if they were observed and restart the siltation module form scratch. We need a better way. Could we have a job created for PPM (as in InfoAsset) that would reset the dynamic value on specific pipes. This could be linked to InfoAsset?

Many software suites allow the option to zoom in on both y and x axes on their graphs. However, ICM only allows zooming on the x-axis which often takes away the ability to see trends for lower or higher conditions. I am aware that it is possible to change the y-axis range in properties, but that is not desired since it requires changing the range numerous times as you pan through the data. This is a major caveat which sometimes changes our choice of modeling software, especially for systems which require heavy calibration and data visualization.

Similar to the ARR and NOAA 14 storm generators, build one that could utilize Environment Canada data with common distribution types.

When pruning, subcatchment drainage manholes are reassigned to the first modeled downstream manhole. However, when pruning subcatchments that drain to single or multiple links, ICM gives incorrect results in some cases and doesn't work at all in other cases, which then causes validation errors after pruning. I submitted this as a bug since it gives incorrect results, but Innovyze asked me to submit is as a "feature request". So please vote for this so it can be fixed and work correctly.

It would help if your recently used flags were promoted to the top of the flags list.

For example, I am updating flags for some manhole surveys (flagged "SM"). Alphabetically, SM is close to the bottom of the list which means I have to scroll to find the flag. For each manhole, I am probably updating 10-15 flags each time so removing the scroll element of the flag update would save some time and frustration.

For the moment we can only 'branch' an earlier version from the commit history interface or 'copy' this earlier version.
- the branch can't be disconnected from the 'mother' network
- the copy looses the commit history
It would be nice to deliver a .icmt file that contains only the earlier version of a network we are working on including the commit history and detached from the original network, so no branch.

Users would like to use SWMM5 Buildup Washoff in ICM Networks AND the SWMM5 treatment equations at a node or link in the ICM St Venant solution.

ICM SWMM networks have both options but for the purposes of using the powerful routing solution in ICM - It would be good to have at least a treatment feature at node/link even as a simple percentage pollutant removal LID/SuDS do have this simple BMP water quality removal.

Currently ICM isn't equipped with the tools to calculate the slope from an underlying ground model or 2D zone so this will need to be determined outside of the program. Can you include the ability for the program to calculate an average catchment slope based on the 2D mesh data or ground model within each sub catchment as an option if this has not been done outside of ICM?

Applying pipe blockage is a standard required in Australia and the functionality in ICM to do this is not user friendly (using blockage links). A simple % pipe blockage in the conduit properties should really be an option. This is particular the case for cross drainage and also orifice and pipes leaving detention basins (where a pit isnt used)

I would like to display the 2D results (depth, elevation, velocity) at each individual GRID cell using labels.
This is currently available in XPSWMM, so I would like the same functionality in InfoWorks ICM as I would rather not have to export the data to GIS.

I want to be able to break my events into daily values. Currently this would require setting up 7 separate templates each with the unique day set under the 'Time Window' button. I want a tick option added that will allow me to do this within the single template.

Provide way to rename Pages on Observed vs Predicted Graphs to Flow Monitor/ Depth Monitor nos. If there are considerable nos of FM/ DMs, an individual has to go through page nos to find out which FM is checked/verified. Facility to rename the pages to relevant FM/DM would help quick viewing of graphs.

It would be a great feature to call the 'Total storage calculation' function from a ruby script and write the output into a csv-file.

If it is not possible to call the build-In function from ruby, it would also help to call the 'storage calculation function' from InfoWorks ICM UI for a set of nodes (maybe from a selection list) and write the output directly to csv-file(s).

II would like to be able to change order of scenarios (after Base). So be able to move up scenarios or down scenarios in the drop down list. I often have to delete scenarios or created amended versions of copied scenarios and this often results in a pretty messed up list of scenarios

I would like to be able to analyse a number of simulations in terms of the worst flood depth per 2D mesh element. An integrated tool (along the lines of the already existing worst case grid output) would avoid the need to mess around in external GIS.

Developp this tool would help the customer to analyze their calibration and justify the used coefficients.