Simulation results from runs can be viewed in the Baseline map view of the IWLive Pro.
There are four types of runs for which simulation results can be viewed:
- Projection Run - scheduled in the IWLive Pro Administrator and automatically created by the IWLive Pro Server, the projection run is used to forecast potential problems in the network.
- Incident Run - created in the IWLive Pro Operator from a projection run, the incident run is used to create a copy of a projection run, which can then be used to further assess forecast problems
- Response Run - created in the
IWLive Pro Operator from an incident run, or another response run, the Response Run is used to assess solutions to network problems
Additionally, projection runs, incident runs and response runs can be optimised using BalanceNet.
Simulation results are viewed in the Baseline Page in the Operator and are selected for viewing from the Run Manager. Incident and Response runs are also created in the Run Manager.
- Triggered Projection Run - automatically created by the IWLive Pro Server whenever the condition of an alarm is met (alarm ON).
Projection Runs
Projection run simulations are carried out automatically according to the schedule set up by the IWLive Pro Administrator. A projection run cannot be altered by the Operator.
Note: Projection runs will not load automatically when you have an Incident run or Response run open. To load, click the Projection run.
Under normal circumstances projection runs cannot be created by the Operator as they are automatically scheduled. However ad hoc projection runs may be generated by the Operator via the Request Projection Window.
The purpose of the projection run is to predict potential problems or events in the network, such as low reservoir level or critical pressures.
Simulation results of each projection run are assessed. If an event occurred during the simulation, a warning is displayed in the Map view on the Headlines Page in the Operator by colouring the zone representing the network. Warnings can be assigned different colours according to level of importance.
Results of the projection run can be viewed in the Baseline page in the Operator. Incident runs and response runs can be created by the Operator in order to assess solutions to the problem.
Incident Runs
An Incident Run can be created from a Projection Run via the Run Manager.
The incident run, when created, is an exact copy of the projection run from which it was created.
The purpose of the incident run is to capture the status of the network at the time of the projection run for further assessment of forecast problems. See Editing Object Fields for Incident and Response Runs for details on how to edit object data for incident runs.
The incident run can be updated from current live data (telemetry and switch updates).
Response Runs
A Response Run can be created from an Incident Run or another Response Run via the Run Manager.
- A response run created from an incident run is an exact copy of the incident run.
- A response run created from another response run, inherits all fields from the original response run, but is considered to be a child of the parent incident run.
The purpose of the response run is to assess possible solutions to the problems originally identified by the projection run from which the parent incident run was created. Control data in a response run can be edited and a simulation carried out to assess the efficacy of the control changes. For example valves can be closed to isolate a burst, and the simulation re-run to assess the effects of the valve closure. See Editing Object Fields for Incident and Response Runs for details on how to edit object data for response runs.
Response runs cannot be directly updated from live data, but can be updated from the parent incident run that may have been updated from live data.
Important note about BalanceNet Runs
A BalanceNet Run is a run performed in InfoWorks WS Pro that has been optimised using the BalanceNet functionality. BalanceNet is an ultrafast optimiser allowing water utilities to improve the efficiency of their distribution systems and ensuring more reliable operations at maximum cost savings. Thanks to BalanceNet, the best possible pumping schedules get produced with minimum effort, reduced labour requirements and significant cost savings.
Please refer to the BalanceNet Runs and Simulations help topic for more information.
Triggered Projection Runs
Projection runs can be triggered in IWLive Pro Operator Client. Run triggering relies on alarms being set up in InfoWorks WS Pro or IWLive Pro Operator Client Administrator, in the Trigger Feeds page of the Baseline object. Alarms are conditions that can be used to alert the user about interesting occurrences in the data coming from external sources (e.g. SCADA), such as a value being below or above a certain fixed level. When the alarm condition is true (alarm ON), projection runs are triggered in IWLive Pro Operator Client at a frequency specified in the Minimum triggered run repetition (min) field of the Trigger Feeds page of the Baseline.
In IWLive Pro Operator Client Administrator server configuration takes place in the IWLive Pro Server dialog. In particular the running of projection runs from alarms can be enabled and the alarm scan interval can be set there.
In the Run Manager Window, the word Alarm is appended to the run name for triggered projection runs. The Alarm Run Reason grid which is accessible from this window displays the reason why that run was triggered.
IWLive Pro still supports one run at a time for each baseline. If a projection run is already running when a projection run is triggered by an alarm the triggered run will only start after the existing projection run is finished. Also. if the run repetition is set to 1 minute but the projection runs take 15 minutes to run, a new triggered run will only be started once every 15 minutes.