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.

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?

This would add a date_created or date_last_committed field to Scenario Objects in the WSApplication.current_network.

It could be used to delete (or archive) old scenarios.

For example, this would allow users to write a ruby script that can loop through and delete any scenarios greater than 3 years old.

It is not possible to get the information of the Job Control window with the current ICM Exchange, but it would be very useful to be able to create a dashboard using ICM Exchange to manage simulations and coordinators.

Options such as 'Reintegrate' & Duplicate'

Mike + added a function called "show data errors" in its new product in 2021, which can display objects that lack necessary field information and generate a table. This function can improve the ability of model engineers to deal with model errors more quickly. I hope ICM can add this function

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.

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

Using SQL to select gauged objects would allow their dynamic selection based on object properties, not just from a static list. This is an issue when testing scenarios if field names are added/changed. It is further compounded by selection lists becoming read-only after being used in a simulation, prompting a proliferation of duplicate selection list objects to update the list.

I am working on project which includes 50 models. where we have to give runs for different return periods and durations for each model. It is a time taking process, which unnecessarily create chances of error by creating run setup every time. is it possible to include a run set up template, which can be changed as per the user requirement and saved for the further use.?

In a workgroup setting with ICM with several simulation servers it is possible to limit a named group of simulation servers (a "group" can be just one server) for use with specific ICM model databases.

We would like to be able to limit use of a server group to specific users who will be working on many databases over a period of time. We don't want to restrict other users from running models in these databases; they can run on other servers.

Similar to how ICM lets me run a SQL query across multiple networks, I want to use SQL to summarize results in a custom way across multiple simulation results objects.

Ideally they could be joined in one table similar to the way one can query from sim.depnode and sim2.depnode when an alternate results is applied to the map. But simply running a query on each simulation in isolation would be helpful as well

Is there a matrix type tool in ICM that allows you to easily set up complicated run set ups? i.e. for this 1 Model Network, these runs with use these rainfall files, inflow files, WWG, etc are needed.

Model Name
Base Model

Rainfall Inflow WWG Tradeflows
M5-30 Inf-M5-30 WWG1 Trade1
M5-240 Inf-M5-240 WWG1 Trade1
M5-960 Inf-M5-960 WWG1 Trade1
M10-30 Inf-M10-30 WWG1 Trade1
M10-240 Inf-M10-240 WWG1 Trade1
M10-960Inf-M10-960 WWG1 Trade1

With same timesteps and 2D parameters?

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.... :-)

Would like to be able to work across multiple screens - plan view on one screen and long section/grid/graph on another.

Our team uses Python scripting extensively for data analysis and manipulation, while Ruby is foreign to us.
Please provide scripting support for Python for model manipulation and analysis.

Keyboard shortcuts can really help speed up processes and workflows in InfoWorks ICM but some of the menu options do not yet have these. Would it be possible to add the missing keyboard shortcuts, specifically for repeatable tasks such as updating objects from ground models?