Event FAQs

The events monitor the status of a pumping station. There are three event types:

• Alarm
• Anomaly
• Incident

Browse the FAQ sections below to find out more about the different event types.

1. Go to Stations.
2. Select a station.
3. Go to Analytics.
4. Click Show events.
   A chart opens in full screen. The events show in a timeline.
5. Select an applicable time period in the upper-right corner.

A maximum of four events show. If there are more than four events in the selected time period, the first events show by default. To change which events are visible, follow these steps:

1. Click Select events.
   A list of the events that have occurred during the selected time period shows.
2. Make the selection:
   • To clear an event, click .
   • To show an event, click the event name.
3. Click Update.

The selected events show.

1. Go to Stations.
2. Select a station.
3. Go to Analytics.
4. A chart of event count shows.
5. Select an applicable time period.
   • If required, configure the chart: To see the chart in full screen, click the button.
   • For details on a column, click the column. The information goes full screen.

1. Go to Stations.
2. Select a station.
3. Go to Analytics.
4. For any chart with a time series, click the gear to open the chart settings.
5. Click the Events switch.
   The chart goes full screen. The events show below the time series.
6. Select an applicable time period and resolution in the upper-right corner.

A maximum of four events show. If there are more than four events in the selected time period, the first events show by default. To change which events are visible, follow these steps:

1. Click Select events.
2. A list of the events that have occurred during the selected time period shows.
3. Make the selection:
   • To clear an event, click .
   • To show an event, click the event name.
4. Click Update

The selected events show.

An alarm is a warning of danger that needs a user action.

Avensor shows alarm notifications from the connected devices.

• There are individual alarms for each device and station in the system
• All alarms have a default priority level for each device. It is possible to change the priority level of each alarm in the system
• It is possible to create a call list to notify users when there is an alarm
• There are several options to acknowledge an alarm
• All alarms are recorded in the alarm log

Alarm description

Priority Level: High

• The application monitors the alarm
• The alarm is saved to the log file
• Notifications are active
  • The application shows a red alarm icon
  • The application sends a message to the user

Priority Level: Medium

• The application monitors the alarm
• The alarm is saved to the log file
• Notifications are active
  • The application shows an orange alarm icon
  • The application sends a message to the user

Priority Level: Low

• The application monitors the alarm
• The alarm is saved to the log file
• Notifications are active
  • The application shows an alarm icon

Priority Level: Off

• The application does not monitor the alarm

The alarms are acknowledged through the following methods:

• In the web application
• In the mobile application
• Through an SMS

The alarm must also be acknowledged in the pump controller.

1. Go to Stations.
2. Select the station for which to change the alarm priority.
3. Go to Alarms.
4. Click the button.
5. Select the alarm.
6. Detailed information about the alarm is shown.
7. Select a priority level in the drop-down list.
8. Click the Update priority button.

The priority of the alarm is changed for the selected device and station.

1. Go to Stations.
2. Select a station.
3. Go to Settings.
4. Go to Services.
5. Disable the Alarm monitoring.

When the Alarm monitoring is disabled, the application does not monitor the alarms and send the alarm notifications for the specified time period. It is not advisable to disable the alarm monitoring for indefinitely. If this option is disabled for indefinitely, the user must manually enable it.

1. Go to Admin > Call lists.
2. Select the call list.
3. Go to the Notification schedule tab.
4. Click Edit.
5. In the setting group for the alarm notification schedule, set the Allow notifications setting to Custom.
6. Select the time zone.
7. Select the days and times that Avensor can send alarm notifications to the call list. To allow notifications for an entire day, set the time from 0:00 to 0:00.
8. Click Save.

Please see Troubleshooting: Alarms.

The alarm means that Avensor fails to communicate with the station. Either the gateway has no power, or the station does not have a connection to the mobile network.

Please see Troubleshooting: Alarms.

It means that the device is not communicating with the CCD. The communication cable might not be installed correctly, or the settings in the application or the device is not correct (wrong Modbus address or other communication link parameters).

Please see Troubleshooting: Alarms.

It is possible that the alarm is not visible in Avensor because of a filter. At the upper right in the alarm tab, it is possible to enable and disable filters. By using the filters, the user can select whether only active alarms are visible, or if both active and ceased alarms are visible.

 Check that the device is added to the station in Avensor.

If the alarm is still active, the alarm shows in Avensor when the connectivity is back.

An anomaly is a deviation from the expected value or trend, or an event that deviates significantly from the normal behavior. 

Avensor shows anomaly notifications from the connected devices.

• Anomaly types are specific for the type of station
• If any anomaly type is applicable to the station when the station is created, the anomaly detection service is enabled by default
• Anomaly types apply to different devices dependent on which data points the devices give
• For a station, it is possible to disable the following items:
  • The overall anomaly detection service
  • The detection of a specific anomaly type
• Users are notified of anomalies through in-app notifications
• The notifications can be marked as read or unread
• The notifications are automatically marked as read after 180 days

When the conditions that triggered the anomaly have not been valid for a period of time, the state of the anomaly changes to ceased. Depending on the anomaly type, the change can take a few days.

This functionality must not be used to change the anomaly status to ceased. 

1. Go to Anomalies.
2. Click the  icon.
3. The anomaly settings open.
4. Select a station.
5. For the applicable anomaly type, click the activation switch. The detection of the anomaly type is enabled or disabled for the station.

The information is applicable when these conditions are fulfilled:

• The user has permission to enable and disable the anomaly detection service
• There is minimum one anomaly type that is applicable to the station

1. Go to Stations.
2. Select a station.
3. Go to Settings.
4. Go to the Services tab.
5. Click the Anomaly detection switch.

The anomaly detection service is enabled or disabled.

The anomaly detection service cannot be enabled for one of the following reasons:

• The user does not have permission to enable the service
• There is no anomaly type that is applicable to the station

The anomalies are marked as read or unread through the following methods:

• In the web application
• In the mobile application

1. Locate the anomaly notification that is to change its read status:
   • Alternative 1: Go to Anomalies
   • Alternative 2: Go to Stations > Select a station > Anomalies
2. Click the button
3. Change the read status:
   • To mark as read, click Mark as read
   • To mark as unread, click Mark as unread
4. The anomaly notification changes read status

1. Go to Anomalies.
2. Select the anomaly.
3. Go to the Anomaly details tab. 
   The related charts show.
4. To conclude if any action is needed, examine the charts and evaluate the issue.
   For a detailed analysis, the following actions are available:
   • Adjust the visible time period by selecting the time period and the resolution of interest in the upper-right corner of the chart
   • Zoom in the chart by clicking and dragging the cursor over the area of interest

An incident is an unexpected event that may have a significant influence on the data values.

If a station has no connectivity with Avensor, a connectivity lost incident occurs. The incident shows the time period that the connection was lost. Because of system delays, the incidents can have a 30 to 60 second delay.

In the station analytics, the data and the connectivity lost incidents are collected. This layout makes it possible to correlate the data and a specific incident.

These circumstances cause a lost connectivity incident:

• Bad radio signal, because of, for example, bad antenna positioning
• Disruptions in the operator network
• Power outage
• The CCD is not connected to the correct antenna port.

For additional information, download the CCD 401 Installation, Operation and Maintenance Manual.

The connectivity lost incidents show under Station Analytics in the:

• Events chart
• Event count chart
• Data point time series

The connectivity lost incidents might be hidden because a maximum of four events shows. It is possible to change which events are visible. For more information visit the Analytics page.

Yes, the operational data is lost.

The call list is a list of users that are notified when there is an alarm. The users are notified in order of priority and with a time delay between each notified user. The priority order and time delay are configured in the application.

Users receive alarm notifications through SMS or email. If a user acknowledges the alarm, then the next user in the call list does not receive a notification. Users can set a weekly schedule to specify which days and times they receive notifications.

Multiple stations can use the same call list.

1. Go to Admin > Call lists.
2. Click the Add call list button.
3. Fill in the required text boxes.
4. Click the Save button.

The call list is created.

1. Go to Admin > Call lists.
2. Select the call list which to add the user to.
3. Click the  button.
4. Click the Add user button.
5. Click the User text box.
6. A list of users appears.
7. Select a user from the list.
8. Select the type of notification that the user receives.
9. Click the Add button.

1. Go to Stations.
2. Select the station.
3. Go to Settings.
4. Click Edit.
5. In the Customer call list field, type the name of the call list.
6. Select the call list.
7. Click the Save button.

A user that is on call receives notifications regardless of the notification schedule.

1. Go to Admin > Call lists.
2. Select the call list.
3. Go to the Notification schedule tab.
4. Click Edit.
5. In the setting group for on call users, set the Allow notifications setting to the correct alarm priority level. Users that are on call only receive notifications for alarms with the configured priority levels.
6. Click Save.
7. Go to the Priority user list tab.
8. For each user that is on call, do the following steps
   1. Click Edit.
   2. Select On call.
   3. Click Save.

The user is limited to have one phone number for each user in the call list.

1. Go to Admin > Call lists.
2. Select the call list from which to remove the user.
3. Click the  button.
4. Click the  button to remove a user.

The user is removed from the call list.