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

Overview

The user has the ability to control if an event should be considered for the pattern and forecasts calculations of the sensor/zone or if should be ignored. The pattern is represented in the graph of each sensor/zone by a grey band and corresponds to the expected behaviour of the sensor/zone. For more information about patterns, go for example to the Sensor Overview help page.

Figure 1- The pattern confidence bands are represented with a grey color while real values (sampled in 15 minutes time step or hourly or daily) are represented with a black line and colored dots.

Generally all alerts that represent anomalous or extraordinary events (such as bursts, leaks, fires, tank overflows, temporary zone changes and meter failures) should not be considered for the pattern calculations and forecasts of the respective sensor, as those events will not repeat in a periodically basis or represent wrong function of the meter.

Figure 2 - Burst alert example. Real values (at red) outside the pattern confidence bands.

Creating Manual Events to exclude specific periods

The user can manually "Add" events in order to to assure that specific periods are not considered for the patterns calculations. Steps are below:

Access the sensor or zone graph detail and zoom to the period that should be ignored
Add a manual event for that period by clicking in the button above the graph, and define the event category as meter failure. You should also close the event (so it will not get displayed in the active event list and in the map) and make some comments. See image below. After the meter failure event is created it will be highlighted in the sensor graph with a red cross symbol. The user can create multiple meter failure events if there are different time periods he wants to ignore.

By doing this, patterns do not become "polluted" by anomalous events or data failures, even if no alerts are triggered/configured and are being automatically generated by the solution.


Flat Reading event. Exclude from Pattern option NOT checked.	Flat Reading event. Exclude from Pattern option checked.

Also note that periods with events classified as meter failure will also be ignored for the water balances calculations. More information about this here, under the section "Ignoring Specific Periods for the System Input Volume Calculation".

Using Automatic generated Events to exclude specific periods

Events can be automatically generated by the solution based on alert triggers defined by the user in the alerts administration (Admin >> Alerts). By default the alerts types configured as No Data or Flat Reading will automatically generate events that will have the option "Exclude From Patterns" enabled (this means that meter failure periods are automatically not considered for the pattern calculation). All other alerts type (pattern and absolute) will generate events that will have the option "Exclude From Patterns" disabled by default (meaning that those periods will be considered for future pattern calculation). However, once an event is generated by the application and correctly categorized, this option will be automatically updated:

if categorized by the user as meter failure, burst, leak or maintenance work the option "Exclude From Pattern" is automatically enabled/Checked meaning that those periods will NOT be considered for future pattern calculation
if categorized by the user as unknown or zone change the option "Exclude From Pattern" is kept disabled meaning that those periods will be considered for future pattern calculation.

The user has always the option to override these defaults by manually changing these settings in the Event Properties table, in the Active Events page, by checking or unchecking the Exclude From patterns option, as shown in figure below.

Figure 3 - Manually change "Exclude from Patterns" option.

Note that in case an alert is generated and represents a new operational condition of the network, or something that will tend to repeat in the future at similar hours, that period should be considered for the future pattern calculations, avoiding that in the future new alerts are generated due to the same and already identified reason (and avoiding generation of false positives). Some examples of this can include for example: i) permanent zone changes, ii) when entering in the summer period - where flows can increase significantly - or in the winter period - where flows can decrease significantly , iii) any event in the network that will tend to repeat in the future at similar hours.

WaterSight - Assuring Cleaned Patterns

Overview

Creating Manual Events to exclude specific periods

Using Automatic generated Events to exclude specific periods

See Also