|
Product(s): |
OpenFlowsTM WaterSightTM |
|
Version(s): |
Various |
|
Area: |
Help and Documentation |
Overview
Events can be automatically generated by WaterSight based on user predefined alert triggers (configured in the administration). Once generated events are both listed under the active events table or displayed in the map.
Too many false events?
Users that are monitoring and analysing events might conclude that the platform is generating too many events, in most cases false positives. Despite the alert trigger conditions are met, it can be clearly concluded that those events just represent normal consumption deviations. If that is the case, the admin user should access the administration section and update the alert triggers in order to prevent similar events to be generated in the future. Usually this means either increase the threshold or the minimum duration, or both. Something that can be of great help is the trigger preview functionality, where the admin user can test and preview the alert triggers changes before enabling them.
Flat Reading events - false events or too many?
A particular case can occur with flat reading events. The goal of flat reading events is to detect when the sensor stops to measure correctly, by marking always the same value (figure below).
Figure 1 - Flat Reading measurement
After the user has configured those type of alerts in the administration, it might happen that in particular cases false flat reading alerts are being generated (when it shouldn't) or too many flat reading events. If that is the case, the admin user should change the threshold value (or variance) that is defined in the administration alerts page (figure 2). WaterSight already assumes default values, and those should only be changed in case flat reading events are not being properly generated. User should consider the following:
- in case flat reading events are not being generated at all (and they should), this means that the threshold variance is too low and the user should increase the value. Please check trigger preview before saving final changes.
- in case flat reading events are being generated in excess (too many) this means that the defined threshold variance is too high and the user should decrease the value. Please check trigger preview before saving final changes.
- for duplicated flat reading events (cases where it should generate just one instead of multiple events), most likely that the flat reading event is finishing too early (once it finds a different value), in that case the user should increase the threshold value just a bit so that the first event does not finish before it should. Please check trigger preview before saving final changes.
Figure 2 - Updating flat reading threshold
See Also