Water Distribution
89 results found
-
Critical Node Pressure at Design Flow
Please add a column in the Fireflow Design results that displays the "Critical Node Pressure at Design Flow". The column titled “Critical Pressure for Design Run” currently displays the input criteria as it can vary for each node. However, this is not as useful when troubleshooting or reviewing the model results. As an example, if a fire flow run is velocity limited it would be nice to know the lowest pressure node and its pressure in the critical node search domain. It may not have reached the minimum pressure if limited by the velocity constraint (i.e. how close did the…
1 vote -
Export InfoSurge results for external application
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.
5 votesIs there a specific external application you’re looking to export to?
-
Evaluate Fireflow Minimum Pressure by Zone
In the drop down menu for the Critical Node Search Range, please add the option to evaluate minimum pressure based on the same zone. Or add an option to consider multiple search areas where the user can select either the entire system and/or by zone and input the minimum pressure for both search areas.
To be frank, this is a non-issue with the Bentley software. The user sets the zone or system as the critical node search area, then sets the desired minimum pressure(s). The FF results list the limiting nodes based on the selected parameter, but will report pressures…
5 votes -
Allow InfoWater to export simulation results in CSV format instead of DBF
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.
7 votes -
WS Pro control should be based on current time step
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.
2 votes -
Persistent Graphs in InfoWater/InfoWater Pro
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.
5 votes -
Allow Customized Reports to Also Include Standard and Fireflow Results - Just Have One Result Table
Currently all model element information and results are separated between the DB Editor, Customizable Report, and Output Report/Graph. This is confusing and hard to export specific information together without having to combine it later in Excel or GIS. The main frustration is that the “Standard” or “Design Fireflow” in the Output Report/Graph results are completely separate from other information related to the model elements. As an example, it would be nice to export all fire flow results for junctions alongside any custom fields made in the DB Editor for easy referencing.
In short, instead of having three types of tables…2 votes -
Default Symbol and Map Display
Please allow the option to choose the default symbol (InfoWater Model Preferences) and Map Display symbol from the "Styles" built into ArcGIS Pro. Both ESRI and my company have custom .stylx files that house our custom symbols for points, polylines, and polygons. Having the option to chose the default style from these pre-populated styles would be fantastic. Currently, the options to change the symbol feel like it limits the modeler to changing either the color or the size.
To see where these styles live in ArcGIS Pro, head to the View tab, click on Catalog Pane, then drop down the…
1 vote -
Data Sets
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.
4 votes -
Provide a Standard Warehouse of new assets
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.
1 vote -
Change the default colour of the background from white to other colours
Change the default colour of the background from white to other colours to help the user interface and improve the user experience.
1 vote -
Include an "excluded search nodes" warning in fireflow output table
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").
2 votes -
Multi-fireflow in WS Pro
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.
5 votes -
Addition of Calendar function to DemandWatch Pro
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.
2 votes -
Multiple control options
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.
3 votes -
Create a ground model using LIDAR data in a .tif format
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.
3 votes -
New Feature is Active in All Scenarios Option (InfoWater/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.
2 votes -
Modify How InfoSurge Counts Features for Licensing
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.
2 votes -
Allow the InfoWater Pro "Live Data Adapter" to use non-live data
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.
1 vote -
Display Warnings when Tank Stage/Volume Curve Inconsistent with Levels
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.
1 vote
