Alerting

On the Alerting tab in device management you can configure how the system should handle alarms.

Manage alertings

Create a new alerting by clicking Add Alerting on the left side above the sidebar or edit an existing alerting by selecting it in the sidebar.

When creating a new alerting, you must first select the type of alerting. This determines the basic behavior of the alerting and cannot be changed later. You can configure any number of alertings on one Beetle.

The available alarm types are:

WAGO MQTT Alarm

The Avelon system checks alarm conditions on the remote device at regular intervals and triggers an alarm if necessary.

Catch Unhandled Alarms

This option can be used as a temporary solution for alertings that are not caught by any of the alarm types described above. However, this is purely a safety net for testing purposes. In general, it is recommended that alarm handling be implemented using one of the other procedures described above.

Alarmed data points

Subsequently specify which data points are to be used for the alerting by dragging them from the right sidebar to the lower part of the main view. All data points assigned to the alerting are listed in the main view under Data Points. You can also assign multiple data points of the same data type simultaneously by first selecting them in the sidebar while holding down the Ctrl or Shift key.

To remove data points from an alerting, move the mouse over them and then click Remove Data Point on the right-hand side. Alarms of the data point that have already been triggered are not deleted, but new alarms are no longer triggered for this data point.

Settings

The following setting options are possible for an alerting and refer to all data points assigned to the alerting:

Name

Give the alerting a suitable name.

Alarm Chain

Select the alarm chain to be escalated in the event of an alarm to notify a stand-by service or technicians. Also see the chapter Alarm Chains.

The following options depend on the selected alarm type and are not available for all types:

Notify current alarm chain user by email when alarm is gone

With this option you can specify whether device acknowledgments should be sent by email to the recipients of the alarm message. This setting overrides the option “Notify current alarm chain user by email alarm is gone,” which can be configured in the general settings for all alertings (see Notifications).

Tickets can only be closed when alarm is gone

Restricts users to closing tickets only when they have been previously marked as “Gone” by the system, i.e. if the system received a message where the alarm condition was no longer present.

Conditional alarm suppression

Alarm suppression allows you to prevent alarms from being issued under certain conditions. Set the condition by first dragging a data point from the right sidebar to the yellow note field, then selecting the data point property to be tested from the list and configuring a value comparison, such as <LiveValue> ≥ 100.

Set data point value on user acknowledgment

This option allows an alarm on the controller to be turned off as soon as the alarm ticket is acknowledged by a user in the alarm chain. A dedicated data point is assigned to the alarm, for which you can set specific values for acknowledgment and reset. Once the alarm is acknowledged, the value of this data point will be set to the acknowledgment value and then it will be reset to the reset value after one second. Information such as the fact that a value was written, the actual acknowledgment value, system name and name of the data point will be added in the ticket history, for reference.

Enable tag for alarm messages

Activate this option and then enter any text in the Alerting Tag field. You can then use this text in the alarm message template so that it is sent to the recipient by email or SMS message as part of the alarm message in the event of an alarm. This allows several different alarm texts that depend on the alarm condition to be defined for the same data point. To learn how to use the custom tag in alarm messages, see Notifications.

WAGO MQTT Alarm

Surveillance

Activate Surveillance

Enable this option to activate the alerting. If you disable it, no alarms will be triggered.

Surveillance Mode

Present Value

The present value is used to determine the alarm state.

Upper Limit

An alarm will be triggered when the present value exceeds the upper limit.

Lower Limit

An alarm will be triggered when the present value falls below the lower limit.

Delay

If the alarm condition is met, wait for this amount of seconds before triggering an alarm. Only if the alarm condition is still present after this delay, the alarm will be triggered. This must be a multiple of the checking interval (or 0, if no delay is required).

UI State

The uiState value is used to determine the alarm state.

UI Bit Mask

An alarm will be triggered when the least significant bit of the bit mask and at least one of the selected UI states is 1.

For each selected bit in the bit mask, a separate ticket will be generated.

If a bit for which a ticket was generated is no longer set in a subsequent message, the corresponding ticket will be automatically set to “Gone” if it has not yet been closed.

If a message with the same bit is received multiple times, a new ticket will only be generated if the previously generated ticket was closed before the new message was received.

The available bits are:

2	xPhyMin	Lower measurement range exceeded
4	xPhyMax	Upper measurement range exceeded
8	xMinValue	Value is below minimum value
16	xMaxValue	Value is above maximum value
32	xCalculation	Calculation error
128	xCommunication	Communication error
512	xHandOperation	Manual operation by the user / service company