Water Distribution

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Push Changes From Parent to Child(ren) Scenarios

    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.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Operational Modeling  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Data Exchange  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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…

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Operational Modeling  ·  Flag idea as inappropriate…  ·  Admin →
  4. Further "Set Area Codes" functionality - InfoWorks WS Pro

    2 feature requests for consideration, both relating to the “set area codes” functionality in InfoWorks WS Pro:
    1. The ability to save the “set area code” configuration, whether that be in a model tree group or as a cfg file, so that you don’t have to reset all preferences every time you open the tool
    2. A “pause area code identification” button so that you can make multiple changes to assets without having to wait for the area codes to recalculate after every minor change (and without having to close the set area code window to prevent the recalculation, which…

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Productivity  ·  Flag idea as inappropriate…  ·  Admin →
  5. 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.

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    RECEIVED  ·  0 comments  ·  Productivity  ·  Flag idea as inappropriate…  ·  Admin →
  6. Make InfoWater windows and dialog boxes resizable

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

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    RECEIVED  ·  2 comments  ·  Productivity  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    RECEIVED  ·  0 comments  ·  Productivity  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Productivity  ·  Flag idea as inappropriate…  ·  Admin →
  9. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  10. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Productivity  ·  Flag idea as inappropriate…  ·  Admin →
  11. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    RECEIVED  ·  1 comment  ·  Operational Modeling  ·  Flag idea as inappropriate…  ·  Admin →
  13. 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.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Engine  ·  Flag idea as inappropriate…  ·  Admin →
  14. Max or Min Flow values should not depend on the pipe direction. i.e. the value being positive or negative depend on the pipe direction

    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.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    RECEIVED  ·  0 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  15. Import demand scaling using CSV file on WS PRO

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

    9 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    RECEIVED  ·  0 comments  ·  Productivity  ·  Flag idea as inappropriate…  ·  Admin →
  16. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    RECEIVED  ·  0 comments  ·  Productivity  ·  Flag idea as inappropriate…  ·  Admin →
  17. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    RECEIVED  ·  0 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  18. 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.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    RECEIVED  ·  0 comments  ·  Operational Modeling  ·  Flag idea as inappropriate…  ·  Admin →
  19. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data Exchange  ·  Flag idea as inappropriate…  ·  Admin →
  20. display multiple scenario results on long section picks

    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.

    9 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    ON ROADMAP  ·  0 comments  ·  Operational Modeling  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5
  • Don't see your idea?

Feedback and Knowledge Base