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?

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.

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.

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.

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?

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.

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

As part of a ruby script, I would like to add a specific layer list to a network to enable a Spatial SQL to be run. This script needs to be run on all our networks as part of a regular update. We have 1100 models which would require an extensive manual activity.

There is an existing method "WSOpenNetwork.openmolayer_list" but this i sonly available internally to Innovyze. Could you please make it available to all?

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.

I would like to be able to see the worst case across multiple simulations (highest water levels) along the 1d network when reviewing results. Essentially being able to visualize statistical report results in a long section.

It would be handy if the Geoplan centred on the selected link when selecting a long section. It seems every time select a long-section the windows split into two halves, one for the geoplan, the other for the long-section. As a result the link I just selected is seldom visible in the geoplan frame, meaning I have to manually re-center the geoplan before I can carry on selecting links for the long section.

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

We'd like to have model results as an input in the TVD connectors. An example is where we have observed flows that we would like to use at a tributary and then switch to catchment flows when the observations run out. We know this can be done using a set up of sluices and dummy objects but it would be a lot more elegant to simply have the subcatchment as Input B. I'm sure there are plenty of other examples of where using model results as an input would be useful.

This is important to assist troubleshooting issues related with TSDB performance during implementation and maintenance of TSDBs. The log should include the exact queries produced by their streams when data is updated.

It would add value to ICM if users could export the Maximum Flood Contours as Elevations in the same way that we can for Depth. This would be particularly useful as currently Depth is the only property that be be exported as an ASCII Grid file.

It appears that the contour intervals used in the export is taken from the "Flood" theme. Perhaps under "Map Type" there could be options to add "Flood Elevation - Filled/Show Layers/Transparent/etc" and hence with a Flood Elevation map type chosen the Max Flood Contours could be exported as elevations.

Beside an upstanding vertical orrifice, it would be practical to be able to implement horizontal 'bottom holes' from one node to an underlaying node. e.g when a ditch can drain to an underlying conduit by means of a bottom opening. This might be a more straight forward implementation then the weir circumference workround method which is now often used. if possible both circular and rectangular.

At present, ICM river cross sections can only be exported to dwg one by one. It would be helpful to be able to export all the modelled cross sections in a single operation (eg via data export centre)