Product(s): | WaterSight |
Version(s): | 10.00. |
Area: | Documentation |
The operational event page goal is to assess and demonstrate the impact of operational events (such as pipe breaks, fire events and pump shutdowns) to service levels, including the details of the customers affected (with no water and low pressures).
Please update minimum admissible pressure defined in the digital twin settings, under the service expectations tab, so that low pressure customers can be correctly identified.
Opens a drop down menu to select the events to create.
Workflow | Description |
Pipe Break | Select a pipe from the map and simulate the impact of a pipe break to service levels |
Fire Event | Select a fire node from the map and simulate the impact of the additional flow required to service levels |
Pump Shutdown | Select a pump to shutdown from the map and simulate the impact to service levels |
Valve Operations | Select valves to open or close from the map and simulate the impact to service levels |
Once an event is created, the user will automatically be redirected to a map to set the location of the event. The operational event is automatically saved in the Operational Events table (below the New event button) after a location for the event is defined.
User defined name assigned to the event. This field can be changed in the event editor page. To accede the event editor page, click on the map icon located on the right side of the table (last column).
The type of event selected from the "New Event" drop down button, that was used to create the record. This field is automatically populated and can't be changed.
Time when the event record was created by the user. This field is automatically populated and can't be changed.
The email of the user that created the event record. This field is automatically populated and can't be changed.
Indicates the status of the event simulation. This field is automatically populated and updated and can't be changed.
Status | Type | Description |
Preparing | All | Model computation about to start |
Isolating | Pipe break | Topological analysis in progress to determine affected customers (no hydraulic model computation required) |
Isolated | Pipe break | Results from topological analysis are available (no hydraulic model computation required) |
In Progress | All | Model computation in progress |
Succeeded | All | Model computation completed successfully; results are available for review |
Failed | All | Model computation failed; results are unavailable |
Customers that in the baseline scenario (with no event) had pressure and during the event scenario end up with no pressure, during at least one time step of the all simulation period.
Customers with low pressure:
- All customers that in the baseline scenario (with no event) were above the minimum pressure threshold (defined in the administration, under the service expectations tab) and during the event scenario end up with no pressure, during at least one time step of the all simulation period
- All customers that were already below the minimum pressure in the baseline scenario (no event) but had a pressure decrease greater than 15% with the event, during at least one time step of the all simulation period
Number of critical customers with zero pressure 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.
Inconsistent Results for Affected Customers
Service Expectation - Minimum pressure
OpenFlows WaterSight TechNotes and FAQ's
WaterSight Learning Resources Guide