Questions about this article, topic, or product? Click here.

WaterSight - Active Events

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

Active Events Table

Overview

The Active Events table lists all events (one event by row) that are automatically generated by the software (based on some user defined alert triggers configured in the administration) or manually added by the user, and are active (this include the following status: field work, new, open, under investigation), ordered by date (this means that most recent events will appear first). Events that were closed by the user are not displayed by default but can be found by directly filtering "Closed" under the status column.

The generated alerts can be triggered using the sensor pattern as reference, or can be based on absolute sensor values defined by the user. All trigger configurations are defined by the user at the alerts administration page. For some tips how to configure bursts alerts, please see this article. If you want to know more about pipe break event workflow in WaterSight, click here.

Important note: Once the anomalies represented by those events are finished (or in case they are false positives), the user should make sure he updates the status to Closed (or deletes), so that the Active Event List will be always showing the most recent alerts that are still Active. For more information about events management workflow. please click here.

The active events table lists by default all events that are open and that require user attention, ordered by date, this means that most recent events will appear first. Closed events will not be displaying by default in the table, but the user can use the status column filter to search for those specific events. In the list there is also a mini-graph view that allows the user to easily and quickly identify and understand each event.

Events detail

For a detailed view of a specific event (listed in a row), click on the edit button located under the Action column (last column).

Adding new manual event

It is also possible to manually add an event, by clicking in the "Add" button just above the alerts list. This is particular useful to track events that are happening or occurred in the network, but were not automatically detected by the software.

In a more easy way, the user can also directly add manual events directly from the sensor or zone graphs (accessible thought the Network Monitoring pages), by clicking on the create event button located on the top of the graphs.

Figure 1 - Add a manual event directly from the graph by clicking in the "Created Event button" located on the top of the sensor or zone graphs.

When clicking on the button, a pop-up dialog will appear for the user to insert more information about the event. Please note that the start and end date of the event by default will automatically match the time period defined in the big graph window, however the user can change. For a more efficient workflow, the user can adjust the start and end date of the graph itself (by moving the time range slider below) before clicking in the "create event" button. Once the event is created, it will be automatically highlighted in the graph with a purple pyramid icon and will also be available in the Active Events table.

Tip: Directly clicking in the purple event icon will immediately redirect the user to that specific alert detail page.

Deleting events

Manual or automatically generated events can be deleted from the application by selecting the desired rows (events) and clicking in the delete button located on the top of the table or located in each row.

Search events

It is possible to search events:

by ID: click on the filter icon inside the ID/Name column and type the ID of the event
by Name:click on the filter icon inside the ID/Name column and type the ID of the event
by Origin: select an origin, from a dropdown option field located above the table on the right.

Figure 2 - Search by ID or Name

Figure 3 - Search by Origin

CSV Export

The user can download the list of alerts and all the respective details to CSV for further analysis.

ID/Name Column

ID: Automatic ID generated by the system and that is unique. Can not be changed.

Name: For automatically generated events, the name corresponds to the name of the trigger defined by the user in the Admin >> Alerts. The trigger name can only be changed in the Admin >> Alerts page. For manual added events, corresponds to the name of the event defined by the user when adding/creating the event and it can be changed directly in the active events properties panel located on the right.

Status

Click on the symbol located on the right of the Status to see all filter options.

By default the list of alerts is showing all alerts that are active and that require user attention. This includes the alerts with the following status: New, Under Investigation, Field Work and Open (all status except Closed). Once an alert is closed, it will be hidden from the default view list, and the user will need to check the “Closed” status from the status table available and located on the right side. The user can also search for specific alerts in the list based on one or more selected status.

Symptom

This easily identifies the reason why automatic alerts were generated. The symptom is identified based on the user admin configurations defined in the alerts configuration page:

For alert types "Pattern" and "Absolute":

If an alert was triggered based on a flow time series, high: symptom will be flow increase,
If an alert was triggered based on a flow time series, low: symptom will be flow decrease,
If an alert was triggered based on a level time series, high: symptom will be level increase,
If an alert was triggered based on a level time series, low: symptom will be level decrease,
If an alert was triggered based on a pressure time series, high: symptom will be pressure increase,
If an alert was triggered based on a pressure time series, low: symptom will be pressure decrease,
The exact same logic applies to all other type of measurements used in WaterSight;

For alert types "No Data" and "Flat Reading":

If an alert was triggered based on the type "No Data": symptom will be No Data,
If an alert was triggered based on the type "Flat Reading": symptom will be Flat Reading

For more information, see below, under Event Properties section.

Origin/Extreme Value

Origin: Sensor or zone or large customer which the time series that generated the alert belongs to. For more information about the difference between triggering alerts for zones vs sensors, please click here.

Extreme value: Maximum or minimum value registered by the sensor/zone (depending if alert type is high or low). This value is automatically calculated by the software for automatically generated alerts. For manually added alerts, this field must be manually completed. For pattern based alarms (please see alerts configuration page for more detail), this corresponds to the burst (or event) flow, and it is given by the maximum difference obtained between the sensor real value and the pattern. For absolute based alarms (please see alerts configuration page for more detail), this corresponds to the maximum absolute value registered by the sensor (within the period of the event).


Figure 4. Máx value registered by the event, for a pattern based alert.	Figure 5. Máx value registered by the event, for a absolute based alert

End date: end date of the event. For pattern based alerts (please see alerts configuration page for more detail) it is when the event returns to the pattern. For absolute based alerts (please see alerts configuration page for more detail) it is when real values are below (for high type) or above (for low type) the absolute numerical value defined by the user in the alerts configuration. In case the event is still out of the patterns or still above or below the absolute threshold value defined, then it will appear "In progress".

Note - importance of associating or comparing large customers flows with zones flow, to improve response to zone alerts. Whenever a zone alert is automatically generated by the solution, and in case that zone includes large customers with smart meter data, please make sure to always compare zone flow with the large customer flow to discard potential consumptions. Another option is to create a new zone and include, in the zone balance, the large customers as outflow of the area. In this case, whenever a zone alert is generated, the customer consumption is already discarded (please make sure the original zone with the large customer included is also kept, so we can correctly track the water balance components for the zone).

Graph

Mini-graph view of the event.

Actions

Map: will directly jump to the map page.

Edit: will directly jump to the event details page.

Delete: will delete the event.

Event Properties panel - Event Detail

Changes to the event (changing name, status, category, making comments, etc) are made through the right side panel. For that the user needs to first select in the Active Events table the row (event) he wants to edit.

ID: same as described above

Name: same as described above

Origin: same as described above

Status: status of the event. The user should update status according with the respective events workflow:

New: by default all events are generated with this status;
Under Investigation: change to this status if it is required further investigation, before deciding if the event should be opened or closed or removed;
Open: change to this status to acknowledge this alert. Also a preliminary analysis should already have been made to filter possible false positives;
Field work: change to this status if the user is confident that the alert can represent any anomaly in the network and there are already some people in the field looking for the anomaly;
Closed: the event should only be close whenever the conditions that triggered the alarm went back to normal, and when a cause was identified. If it was not possible to identify a cause, please close the event and categorize it as unknow. If the alert is also considered a false positive, the user can directly move from step 1 to 5.

The user has the option to filter the events that appear on the list. By default the list is always showing all alerts/events that are in progress (this means all alerts that are not closed).

Category: whenever an alert is generated, the category is always set to unknown, expect if the alert type (configured in the Alerts Administration page) was set to "No Data" or "Flat Reading". In these two last cases, the default category of the event generated is Meter Failure.

After the cause of the event was identified, the user must select the most appropriate field defined in WaterSigth: Unknown, Meter Failure, Burst, Leak, Flow Increase, Maintenance Work, Zone Change, Holiday. Maintenance work includes all operational works developed in the network (flushing, opening/closing valves, etc). Zone Change refers to a temporary or permanent change of the zone layout (by opening/closing valves).

Symptom: same as described above.

Start date: the date the event started (and not the date the alert was triggered). As illustrated in figure below, the alert is generated when the trigger configurations defined by the user in the alerts configuration page are met, however the real event can already have started some hours earlier.

Figure 1. Difference between event start date and date the alert was triggered, for a pattern based alert.

End Date: end date of the event, for which the alert was triggered. For pattern based alerts (please see alerts configuration page for more detail) it is when the event returns to the pattern. For high type alerts this means below percentile 80th (values are color coded with a black circle). For low type alerts this means above percentile 20th (values are color coded with a black circle). For absolute based alerts (please see alerts configuration page for more detail) it is when real values are below (for high type) or above (for low type) the absolute numerical value defined by the user.

Figure 2. Start date and End Date for a pattern based alarm.

Duration: the duration of the event is automatically calculated by the software using the Start Date and End Date (for automatically generated alerts). For manually added alerts, this field must be manually completed.

Figure 3. Duration of the event.

Max.Value (or extreme value): same as described above, in the Active Events table section.

Lost Volume: Volume lost in anomalies and other events (like bursts, leaks, flushing, fire usage, etc). This volume is automatically calculated by the software for automatically generated alerts, and only for alerts that were generated based on a flow time-series using pattern high as a criteria (please see alerts configuration page for more detail).

The volume is automatically calculated by integrating the difference between real flow and expected flow (the pattern) along time, for the all duration of the event.

Figure 5. Identification of the lost volume.

Exclude From Patterns: The user has the ability to control if an event should be considered for the pattern and forecasts calculations of the sensor or if should be ignored. 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. In these cases the option "Remove From Patterns" should be checked .

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.

Please note that if an anomalous (extraordinary) event has occurred and the "Exclude From Pattern" option is unchecked (or either because the user did not categorize the event or because he wrongly override the defaults), those values related to the anomalous events will be considered for the future patterns calculations and forecasts, and with this "polluting" the patterns. For more information please take a look at this article.

Comments: The user can update the event with some relevant comments (for example the type of burst, location, and other relevant information for the utility).

Event Properties panel - Trigger Detail

Displays the information related with the configurations of the trigger that generated the alert. Those configurations are defined in the Alerts administration page.

Trigger name: name defined by the user for the trigger that generated the event. Trigger name is defined in the Alerts administration page.

Type: defines the method that is used to evaluate the alert criteria. The user can define 4 different types of alerts: Pattern, Absolute, No Data and Flat Reading. More information in the Alerts administration page.

High/Low: the user picks High or Low to indicate if the trigger is a high or low alarm. More information in the Alerts administration page.

Time Series: the user defines the real time series where all trigger configurations will be assessed. Available options are the 15 minutes time series, the daily minimum series and the daily average series. More information in the Alerts administration page.

Pattern History: this option is only available for pattern based alerts. The user can choose the time period that will be used to serve as reference to generate the alerts. More information in the Alerts administration page.

Value/Threshold: the user defined value from which an alarm can be automatically generated. More information in the Alerts administration page.

Minimum Duration: it defines the minimum number of consecutive outliers needed to generate the alarm. More information in the Alerts administration page.