OpenFlows | Water Infrastructure - WaterSight - Previous Simulations

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

Results from every automatic run of the model in WaterSight are saved in this page and can be downloaded by the user for further analysis using WaterGEMS or WaterCAD. Each row of the table lists one complete run of the model. The respective model with the results can be downloaded by clicking in the icon button located on the left of each Model Domain. The frequency at which each model run is saved depends on the run frequency defined in the Numerical Models configuration page.

Model Domain

Automatic name generated by the software once a hydraulic model is uploaded through the Numerical Models configuration page.

Type

Model input format. For now it is only possible to upload WaterGEMS models.

Start Date

Corresponds to the time the model was computed.

End Date

The time for which a new model run will be calculated. This depends on the run frequency defined in the Numerical Models configuration page.

RunTime (min)

The time it took for a complete hydraulic model run.

Status

Shows if the model was computed with success or not. If green the model computed successfully. If orange warning symbol, the model run with success but with some warnings. If red, there was an error and it was not possible to run the model, therefore the latest model results will not be available in WaterSight.

Message

Warnings and error messages are displayed in the Message column.

More detailed information and messages for each model run can be found by downloading and opening the logs file:

Figure 1 - Log file example for a specific model run

Common Error Messages

Note that if the hydraulic model runs fail, the operational response simulation will also fail (for the same period).

A summary of the potential errors is listed under the "Messages" column in the Previous simulation page, as described above. For more detailed message errors the user should download the model run which had problems and download the simulation and log files (this log file can also be downloaded from the operational response simulation page in case the operational model runs - pipe break, fire event, pump shutdown, valve operations - are failing).

Inside of the downloaded zip file open the UNS file extension and look for an extensive detail of all possible errors and warnings, example below.

Failed to obtain zone pattern

A very common error is related with a failure obtaining the zone pattern:

Error: PrepareAdditionalConditions - Failed to obtain zone pattern of zone North

This situation happens when the automatic zone demand adjustment option is enabled for that zone (configured in the Administration >> Numerical Modelling >> Configuration) but there are no flow patterns available for that specific zone.

Troubleshoot steps - check if there is zone flow pattern available:

1 - Go to Network Monitoring >> Graphs

2 - Select the Zone Overview Dashboard, by clicking in the zone button located on the top right of the page

3 - Click in the zone graph you want to analyse (in the title). This will enter in the zone graph detail.

4 - In the zone graph detail change the pattern option to last month, and the time series to 15 min, and check if pattern (grey band) gets displayed or not in the graph for the period that fails (or if it is a flat line). If the pattern last month is not displayed or is a flat line, than it will not be also possible to use it for the hydraulic model run and the model run will fail in case it is using this zone to adjust the demands. This might happen due to one of the reasons below:

There is no zone data for the last week or more, as one of the sensors that belongs to the zone balance just failed and does not have data anymore. If that is the case, you can go to Admin >> Zones >> edit the zone and select the gap filling option Yes. The pattern should be recalculated for the zone using estimated data, and the model should run again.
There is flow data for each sensor, but there is at least one event associated with one of the sensors or zone that extend for a large period with the option "Exclude from pattern" set to yes. If that is the case, just go to the event and disable the option "Exclude from Pattern" or delete the event. For more information about excluding events from patterns click here.

5 - If none of the solutions mention in point 4 above fix the issue, the user can always go to Administration >> Numerical Modelling >> Configuration, edit the existent model by clicking in the row, and in the right side panel remove the zone that is failing from the Adjustment zones option, as shown below. After saving, wait for the next model run (based on the run frequency defined) and check that there are no more errors in the Previous Simulation tab.

Execution Failed - Invalid Tank operating range

If the model fails with the message Invalid Tank operating range, this means that value assumed by the hydraulic model for the tank operation is below the minimum or above the maximum. Example of the error message below:

In case you are using real tank levels to override tank model boundary conditions (in case you have in the WaterGEMS uploaded model the sensor level defined as SCADA element and mapped to the tank model element), most likely that one of the sensor level values (real value) registered at least one value that is outside the max and min tank operating condition defined in WaterGEMS uploaded model.

For example in example below, the Scovill Tank was configured in the uploaded WaterGEMS model to have a minimum level of 89 ft and maximum of 115 ft.

And if we look into the Scovil tank levels in WaterSight, we can see that the sensor goes several times to more than 115 ft:

As this model element is associated with a SCADA element in the model, the real time measurements (more than 115 ft in some cases) are being input into the model and this is making the model to fail (as it only allows max level of 115 ft).

Possible solutions:

Adjust the minimum and max levels defined in the WaterGEMS to be consistent to what is being displayed by the sensors, and upload the new model again in Admin >> Numerical models;
If the sensor is temporarily malfunctioning, you can temporarily mark those sensor as as offline in WaterSight (in Admin >> sensors). Once marked as offline, that sensor will stop to reive data and will be discarded for the model simulation. After few hours the new hydraulic model runs will not use the measurements from that specific sensor to override model results. Once the sensor has good data again, return to the administration and remove the offline status, so it can start again to be used by the hydraulic model. More information can be found here - Unassigning sensor from model element.
If the sensor chronically have some wrong measurements frequently (each day or each week), you can create a derived signal in the WaterGEMS model to exclude those bad measurements, reupload the new model again and add the derived signal to the Admin sensor list. More information about adding derived signals, here.
In case you don't have any sensor levels mapped to the tank model elements in WaterGEMS, then the initial tank level value configured in the WaterGEMS model that was uploaded in WaterSight should be wrong (initial level needs to be > than min level and < max level).

WaterSight - Previous Simulations