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.

As a use the ability to 'schedule' statistical reports would be extremely useful. currently if i'm generating a spill report on several overflows for a 10yr TSR series this can take several hours. The process effectively locks the software and prevents any other operation from been undertaken. This is highly inefficient and costly especially when optioneering if several iterations are needed. Shorter TSR's can be run in this case however even a year with several CSO's can take 20-30mins.

Options such as 'Reintegrate' & Duplicate'

We would like to see the water levels at the bridge linear structures as it is important for us to be able to see the water levels with respect to the bridge openings and decks.

Currently, the User URL option for the "View Online" menu in Innovyze ICM only allows for the output of longitude and latitude coordinates. Our GIS system is built on the BNG projection and therefore uses X/Y coordinates in its URL. Can you enable X/Y coordinates to be used in the User URL generated by ICM?

InfoSWMM provides Pipe/Conduit summary report with values for Max flow divided by "Full Flow". Here the "full flow" is based on Manning's equation for when the pipe is full. However as a sewer utility, we're not allowed to fill pipes. We must keep pipes below 80% full as a constant benchmark.
We'd prefer all our reports are compared against 0.8d/D instead of Full Flow.

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.

Please include weirs and orifices in the ARR Ensemble Statistics summary. Currently, only conduits or natural channels are included.

With the large amounts of data generated it would be beneficial if a supported configuration would be to have a WDS installed on a server but pointing at databases (and solves etc) over the network on a remote storage system (such as NAS). This would make the whole solution far more scalable as the need arose.

Creating or amending ICMTs is slow, especially if they contain ground models. Even deleting or creating new 'folder' items in ICMTs is slow. Speeding this process up would increase productivity.

A better copy function between networks might be usefull: e.g. Also copy the 'link head discharge' or 'conduit shape geometry' tables when copying a link from one network to an other. Or at least a popup allowing you to select which lists to copy or not.

Can we please have net/effective rainfall as a result?

When applying direct rainfall onto 2D zones traditional roughness values do not typically apply, especially where the depths of water on the mesh element are very small. Often the workaround is to apply much higher roughness values in order to 'slow the flow'. It would be helpful to have a depth varying roughness that could be phased out as the water depth increases. This would put ICM in line with how TUFLOW and Flood Modeller Pro deal with the problem.

We all make mistakes!

I have a model that has masses of roughness polygons. invariably some of these overlap. I also have overlapping roughness zones where I have 'donut' features. My life would be SO much easier if meshing didn't fail when the roughness zones overlap. Can we p[ease have the restriction on these relaxed? If we have to specify a priority then that would be acceptable. It doesn't seem to be a problem with HEC-RAS or TUFLOW.... :-)

As an organisation we would like to export the data exposed in show details view in order to assist with reporting in relation disc storage/ utilisation i.e. ID associated with Model Group.
We store all our DAP models within a single Db so collecting manually is time consuming

In ICM I can sample elevations from ground model to cross section line and use that for river reaches, but sometimes I just want to use simple Channel links or maybe I'm using the SWMM engine which doesn't have rivers.

I want to pull the channel shape profile from a cross section line on the map to quickly configure simple 1D storm systems.