WaterSight - Assuring Cleaned Patterns

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 behavior 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) should not be considered for the pattern calculations and forecasts of the respective sensor, as those events will not repeat in a periodically basis. 

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

On the other hand, 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.

By default the alerts types configured as No Data or Flat Reading (configured in the alerts administration) 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 (meaning that those periods will be considered for future pattern calculation) as starting point. However, once an event is correctly categorized, this option will be automatically updated:

  • if categorized 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 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.

However, it is important also to refer that the user does not need to wait for an alert to be generated in order to get "cleaner" patterns. The user can  manually "Add" alerts directly form the Active Events table (clicking the button   ), define the period in which something unusual as occurred in the network, and then selecting the option  "Exclude From Patterns" from the events list.  By doing this patterns do not become "polluted" by anomalous events or data failures, even if no alerts are triggered/configured. 

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

For more information about WaterSight, please go to OpenFlows WaterSight TechNotes and FAQ's.

Recommended
Related