Product(s): | WaterSight |
Area: | Documentation |
A new pipe break event can be triggered from the Operational Response page. The goal is to easily simulate and show the impacts on the service levels throughout the network caused by a pipe break event.
Steps
Valves to be closed are automatically calculated and represent the nearest valves that will isolate the smallest portion of the network. Checking or unchecking a valve in the right side table (or by directly clicking with the right button of the cursor above the valve and select "Toggle Operable") will trigger a new re-compute and suggest other valves (the nearest ones) to be closed. This is useful as sometimes the nearest valves may be inoperable due to failure or other reasons. In case the user pretends specifically to define the valves or pipes that should be closed, please consider instead running a valves operation event.
Results above are calculated based only on geospatial and pipe connectivity analysis. The user can enable the hydraulic model engine to identify low pressure customers that may exist due to that event or to assess the impact on other hydraulic variables such as flow and pressure. Please see here for more information on how to simulate steady state and extended period model runs.
Note: If you experience a problem with network outage segmentation and you use a check valve on the pipe next to a reservoir, try placing the check valve on the next-downstream pipe (rather than on the pipe directly adjacent to the reservoir). We are working toward improvements of the handling of this situation.
Results
For more detailed explanation on the results, including the description of the results displayed on the right side panel, please click here.
See more
OpenFlows WaterSight TechNotes and FAQ's
WaterSight Learning Resources Guide