It can be difficult to tell if UPC is attached to a pump without checking every time. It would be very helpful to have a way to show UPC, such as similar to live data.

When inserting a new junction in an existing pipe, InfoWater Pro interpolates the elevation data between the two existing nodes to come up with a default elevation estimate. A useful setting option would prevent this from happening, and instead default to a 0.00 elevation.

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.

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.

in WS Pro

It would be nice if the user could modify the minor loss table for pipes. Whether it be changing the minor loss values, deleting, or editing the existing values. Since we all have our own resource we typical reference for these values, it would be nice to import those values and have that database saved in Infowater to make it easy to add all bends, etc. while building a model.

Thanks!

In InfoWorks WS Pro - A way to automatically generate a system curve for a pump would be extremely useful.

It would be great to be able to change the initial tank levels without having to create a whole new tank data set or putting a duplicate tank in the current data set. That way, the initial tank level condition can be changed for any given scenario without having to worry about changes in tank geometry across all scenarios. I believe WaterGEMS allows you to do this so it would be great to see this functionality in InfoWater. Perhaps initial tank levels could be placed under the Initial Node Status controls?

There is massive interest in having a water quality model that shows pH, Nitrification, chlorine levels, age, and tracing in real time. Currently this is only possible for water age (the basic EPANET WQ does not allow for the source tracing and quality modeling we need).

Would be really nice to do these with IWLive with shorter duration Server runs (using the proceeding projection), as opposed to having to do 20 day runs in IWLive, export to InfoWater, then setup MSX there and run for another 20 days.

As a user and working within a Queensland council, Equivalent Persons (EP) are used for Local Government Infrastructure Plan (LGIP) triggers and growth planning. As the Census data is used create a demand model to define development staging horizon demands.
Currently, WSPro can handle no. of properties (l/service/day) which uses an integer but can’t handle Equivalent Persons (EP) that needs decimal formatting.
Our council believes a work-around is not suitable and creates complexity to demand allocation. WSPro should be able to handle different mechanisms for demand allocation to support all councils in Queensland and across Australia.

In WS Pro
Upstream/downstream tracing is easy for a single object.
Obtaining a single useful value (i.e. property count) is easy for multiple objects.

Combining the two is very difficult at the moment in WS Pro

I want to be able to obtain, either for all objects or a selection, the value of data x upstream or downstream.

For example: length of mains upstream, no of properties downstream

This would be a really powerful risk assessment tool but also useful for quick operational analysis.

Denver Water has a massive outage program that runs a minimum of 6 months per year. All outages are modeled. For nearly all outages, 2 valves are shut down for safety. Having the isolation trace in IWLive contain an option to trace to the 2nd valve would be really useful and make this process significantly easier!

Each simulation has a hindcast period, now and a forecast period

As a user I want to be able to model reservoir drain down and loss of supply sites during an incident showing results in the control room (mostly be used by people with no hydraulic modelling experience)