Can't currently map Max HL/1000. This would be more efficient/useful in some cases than mapping Max HL (feet). If your model has many segments, it is possible that very high head loss areas will not be flagged if only the HL is available.

InfoWater can use the option to "Export simulation results for external application" to export selected results to DBF files. It would be nice to have this work for InfoSurge.

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

Allow changes made in a parent scenario to push through and update all child scenarios unless that link is broken in the child scenario(s).

This goes along with the improvement suggestion titled "Data Sets" by Kathryn Carreira. The Scenario and Data Sets organization needs to be improved in InfoWater Pro as other software already excels in this area. Right now if something changes in one scenario it has to be manually updated in all child scenarios, this becomes exponentially time consuming with larges model and multiple scenarios.

When the design pressure exceeds the static pressure at a particular node, that node will be excluded from a design fireflow model run. The output table should include a banner at the top listing the excluded nodes, as these can make a big difference in available flows and can easily be overlooked. Currently, this event is only described in the .RPT file (shown as "Summary of Excluded Search Nodes: due to static pressure < design pressure").

It would be very helpful if, for any data set that is created by creating a clone of another data set, you could keep track of that. Perhaps a visually branched system of data sets to see if any of the sets were created based on another set. That is how WaterGEMS shows their data sets (aka alternatives). Or some other way of keeping track of which data sets were cloned, with options for recording when it was cloned and a more in-depth description/reasoning.

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.

Currently, if the flow direction through the pipe is opposite to the direction of the pipe drawn it shows as a negative flow value. So if the flow goes both direction during the run, smaller positive value shows as the maximum flow and larger negative value shows as the minimum flow. This is wrong.

Please add the ability to import demand scaling using CSV file on WS PRO

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.

We have 20,000-pipe InfoSurge licenses. We frequently have operational models larger than that, where we want to perform Surge modeling. Even if we deactivate portions of the network, InfoSurge still counts the total number of features. This wastes time deleting features to make a new model that is then possibly diverging from the original.

Currently, the available built-in fireflow options in WS Pro run for individual nodes/hydrants as if no hydrant in the system is open. Adding the ability to run multiple hydrants that are opened simultaneously will be very useful.

The Live Data Adapter can be a powerful tool for calibrating models, but is difficult to set up. Many times, you don't have permission to connect to the SCADA historian database. Right now, it only supports ClearSCADA, PI, SQL Server, and Oracle, formats which require familiarity with these databases. If the tool could connect to Excel, CSV, or Access DB files, it would be more flexible and useful to all users.

Alternatively, update the "Real-Time Data Connection" feature (Command Center>Edit) to allow for gap analysis.

For long section picks on model runs showing the hydraulic gradients etc. it would be useful when carrying out scenario work to be able to display more than one set of run results - currently have to export to excel.

ICM got the capability of the scenario modelling within the single network. H2Omap also had the same capability. Any possibility of having the same capability in WS pro?

Assets with controls (Pumps, PRVs etc.) should have multiple control options.

So Control 1 could be a control regime applicable to model calibration.

Control 2 could be control relevant to a General Applications model,

Controls 3, 4, 5 etc could be used for modelling specific scenarios for analyses.

A tick box would enable (and disable) which control is used in the model run.

LIDAR data is now typically stored in a .tif format as opposed to .asc, and so it would be useful to be able to create a ground model in Infoworks WS Pro using .tif data.

The current DemandWatch Pro doesn't have any functionality to set national holidays, even though water consumption should change on holidays greatly. Some national holidays are different yearly, so it will be great if we can define national holidays in some ways in DemandWatch Pro.