WaterSight - Pipe Break Results

Product(s): WaterSight
Version(s): 10.00.
Area: Documentation

Map view

Map automatically zoomed to the location of the event, highlighting all customers affected by the pipe break event, as well as pipes affected and valves to close.

Customers are represented with the following colors:

  • Red customers: customers with no pressure (no supply) connected to the isolated pipe
  • Purple customers: customers with no pressure (no supply) connected to the pipes downstream the isolated pipe
  • Yellow customers: customers with low pressure due to the event

Pipes are represented with the following colores:

  • Isolated pipes (between valves) at red
  • Downstream affected pipes (with no service) with purple color

User can click in any element in the map to see the results for a specific element. Graph result will only be available if the event simulation run is Extended Period type, please see below for more information.

Using the map controls, the user can also analyze several hydraulic parameters, such as pressure, flow, velocities, etc.

Map Controls

Layers: Use the layers option located on the top of the map to enable or disable additional geospatial information as well as the 3D context. Any GIS information that is uploaded in WaterSight (through shapefile upload in the GIS administration page) will be here displayed.

Model Element Visibility: The user can control the elements that are shown on the map, such as:

  • Pipes -  enable or disable pipes elements on the map view and which variables to see (diameter, flow, headloss, headloss gradient, velocity). Default is on. 
  • Junctions - enable or disable nodes elements on the map view, which variables to see  (elevation, demand, hydraulic grade line, pressure). Default is on. 
  • Tanks - enable or disable tanks elements on the map view. Default is on. 
  • Reservoirs - enable or disable reservoirs elements on the map view. Default is on. 
  • Pumps - enable or disable pumps elements on the map view. Default is on. 
  • Control Valves - enable or disable PRV and FCV elements on the map view, and which status to see. Default is on. 
  • Isolation Valves - enable or disable isolation valves (TVC, GPV and Isolation valves elements) on the map view, and which status to see. Default is off.
  • Customers - enable or disable customers elements on the map view. Default is off. 
  • Laterals -  enable or disable laterals elements on the map view. Default is off. 
  • Flow Animation - allows the user to easily understand flow direction, through particles simulation. 

Model Symbology

  • Preset Map Configurations - controls the all model symbology and display: 
    • Default - Pipes Flow and Junctions Pressure are selected. Styles configurations can be configured by the user in the Administration, under Numerical Models. 
    • Low Pressures - Only Junctions with low pressures are displayed in the map. Styles configurations can be configured by the user in the Administration, under Numerical Models. 
    • High Pressure - Only Junctions with high pressures are displayed in the map. Styles configurations can be configured by the user in the Administration, under Numerical Models.
    • Transmission Main - Only Pipes flow is displayed. Styles configurations can be configured by the user in the Administration, under Numerical Models.
    • SCADA Elements - All sensors are displayed in the map
    • Custom - Different model views can be configured and become easily accessible to operators. The user can select which variable to see for pipes and junctions. Styles configurations can be configured by the user in the Administration, under Numerical Models. More information here.
  • Elements Outline - if enabled, all network elements are outlined in the map by a white contour line
  • Pipes - allows the user to select which styles configuration to see in the map. Several styles configuration are automatically available by default such as: diameter, headloss gradient, flow, velocity, age and concentration. The user can change the defaults or add more. Styles configurations can be configured by the user in the Administration, under Numerical Models. 
  • Junctions - allows the user to select which styles configuration to see in the map. Several styles configuration are automatically available by default such as: age, concentration, elevation, HGL, pressure, Low pressure. The user can change the defaults or add more. Styles configurations can be configured by the user in the Administration, under Numerical Models. 
  • Control Valves - choose the control valves to display on the map: all, active, inactive or closed. 

Side-by side view:

Side-by-side view will only be available for emergency events that were created in the last 7 days. If side-by-side view option is on, it will be possible to easily compare the baseline scenario (with no event) with the event scenario. User can click in any element in the map to see the results for a specific element and compare pre and post event conditions. Graph result will only be available if the event simulation run is Extended Period type, please see below for more information.

Summary

Statistics about the simulated pipe break event:

  • Number of critical Customers affected
  • Total number of Customers affected, including zero pressure and low pressure
  • Number of Valve to be closed
Critical customers affected are those that have zero or low pressure during the simulated event. The information about critical customers need to be previously provided by the user and filled in the configuration template used to import customers information, in the digital twin administration. 
The rule to highlight low pressure customers is the following:
  • All customers which were above the minimum pressure threshold before the event and end up by being below the minimum pressure threshold after the event  AND/OR
  • All customers that were already below the minimum pressure but had a pressure decrease greater than 15% with the event
The minimum pressure threshold is defined in the digital twin settings, under the service expectations tab.
Examples: Low pressure threshold: 50psi
Case 1: Without event 70, With event 60 -> do NOT highlight (good conditions)
Case 2: Without event 70, With event 40 -> highlight (it passed the threshold)
Case 3: Without event 51, With event 49 -> highlight (it passed the threshold)
Case 4: Without event 49, With event 48 -> do NOT highlight (it was already low and variation less then 15%)
Case 5: Without event 49, With event 35 ->  do highlight (it was already low but a variation greater then 15%)
 

Valves to close

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

Simulate

Opens a dialog to run the steady state or extended period simulation with the some user defined settings. 

Isolation type of run

If the user does not press the simulation button, all the results displayed are just considering the isolation of the pipe, and all customers affected are identified only based on geospatial and pipe connectivity analysis. This means that affected customers will be those that end up without any supply. In that case, above the simulate button, it will be displayed Isolation as simulation type.

Steady state run

Besides the geospatial and pipe connectivity analysis, the hydraulic model engine will also run in order to identify customers located nearby that although still have supply, may experience a significant decrease in pressure. Steady state means that the period analyzed corresponds only to the exact instant when pipe was closed, that is defined by the user. In that case, above the simulate button, it will be displayed Steady state as simulation type.

Extended period run

Besides the geospatial and pipe connectivity analysis, the hydraulic model engine will also run in order to identify customers located nearby that although still have supply, may experience a significant decrease in pressure. Extended period means that the period analyzed comprises a specific duration (and not an instant) defined by the user. In that case, above the simulate button, it will be displayed Extended Period as simulation type. There are two types of extend period runs:

  • No isolation: this is the default option and only considers the leakage without any isolation of the pipe

  • With isolation: if toggled on, this means that the event can include a period with leakage (before closing the pipe) and then the period when the pipe was closed in order to repair the leak.

Extended period run dialog

Leakage flow: pipe break flow in the units defined for the digital twin.

Leakage start time: the start of the leakage.

Isolate: by default off, allows to specify details when and how long isolation occurs within in simulation time range.

Calculation Start date: the start date for the model run

Calculation End date: the end date for the model run

Affected List of Customers

Summary of all affected customers (Billing ID and address). Click in the Full Screen button to have a complete view (in a tabular format) of all customers affected, with more detailed information

Click in the download CSV button to export the list of all Affected Customers to a CSV file. 

See also

OpenFlows WaterSight TechNotes and FAQ's

Recommended
Related