While building and editing models, I want to customize easy access to tools currently burried in the Command Center (e.g. Trace Network, Join/Remove Layer tables, Clear message board, etc.).
ArcGIS Pro lets you customize toolbars, but these commands aren't yet available.

While rasters remain the best way to assign elevations throughout the model, InfoWater also supported other formats using interpolation such as contours and point elevation.
Please add these file types in InfoWater Pro.

e.g.: I want to be able to evaluate shutdwon of pumping stations in 1 one run, now I have to create a seperate run for each pumping station. A workaround I use is closing links with a GRM config, but this only shuts down links for the whole simulation.

Currently if there needs to be a global change to a dataset, the only way is to manually go through each dataset and change the element property and save. As an example, if a valve needs to be closed in multiple datasets, it would be nice to have a tool to allow that change happen to all desired datasets at one time.

This feedback also goes along with the previous posted feedback title: "Data Sets" by Kathryn Carreira and "Push Changes From Parent to Child(ren) Scenarios" by Joe Lawrence.

Many windows in InfoWater/InfoWater Pro are not resizable, making it difficult to see long values.

Currently the "Show Pipe, Pump and Valve Initial Status" under the Display Settings tab in the model Preferences window will not stay checked after you save, close, and reopen the model. Please have this option/setting maintain the last setting when the model is reopened.

Stored graphs aren't that great. Why not just make graphs persistent? This is one area where competitors blow away InfoWater and InfoWater Pro. No contest.

The option to "Export simulation results for external application" in InfoWater would be more useful if the results were exported as CSV files instead of DBF files. We regularly need to compare the results from multiple model scenarios. Microsoft PowerBI or Excel PowerQuery are great tools for importing and comparing large amounts of data and could streamline this process significantly. However, neither support importing directly from DBF files.

Allow the company that is running the software to define a standard warehouse of new assets so the modellers using it know the assets they are adding have the settings (diameters) of the actual assets or pipes that particular company uses.

Add a tools/options option so when you add new features they will be active in all scenarios, instead of getting errors 100 times for every scenario you try to run where the features were not included originally. This would be especially useful when using Intelliselection.

I use both Bentley and Innovyze water modeling software and i have noticed that the Bentley software allows you to zoom to elements from the report tables and allows you to pan, click, review properties, etc. while the report table is open. It would be really nice if Innovyze could include a zoom to feature in the report tables (similar to what is already included in the DB editor), and allow the user to pan around in the map and click on elements while the report table is open.

Would be very useful if you could either sort selection set orders or move selections up or down the list. This would make it much faster to find the selection set you want in a large list (e.g. DMA selection sets in alphabetical order)

I can calculate volume from level, but it's an extra step and requires that I copy the run results out to Excel. It's even more difficult if I have a non-circular tank. Please include tank volume in the tank results and in the "System Demand" report.

As a user I want to take advantage of multi-threaded CPUs to accelerate simulation intensive procedures (e.g. design calibration)

In InfoWorks the background colour for the GeoPlan is white - it would be beneficial to change this colour to the users choice to make particular features stand-out more clearly in the GeoPlan view

1. Allow the "Change ID" tool to rename datasets, patterns, queries, etc.
2. Make the "Change ID" window wider or resizeable to fit longer IDs.