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.

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.

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.

Change the default colour of the background from white to other colours to help the user interface and improve the user experience.

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

Add option in WS Pro so that control status of objects is controlled by the flow solution in the current time step, not the previous time step. The way WS Pro currently works, with the control based on the previous TS often results in pump on/off status being incorrect and sometimes pump cycling on/off. It also breaks the fundamental steady state assumption of the solution.

I suppose this would require running iterations of each time step until the control solution/status converged, or something, but should be possible.

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

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.

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.

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.

As far as I can tell this is an EPANET bug, but say your tank levels are set to minimum 4 and maximum 20. If you have a stage/volume curve that goes below 4, your tank will supply water forever from a level of 4 feet.

in WS Pro