Alarms

Define the conditions that raise an alert in a project.

In a project’s Alarms view you define the rules that watch your data and raise an alert when something needs attention. (For the difference between an alarm rule and an active alarm, see the Alarms concept; to respond to alarms that have triggered, see the Alarm Manager.)

Conditions

An alarm watches one or more tags and triggers based on a condition. An alarm can combine several conditions, and each is one of these types — see Conditions for the full detail of each:

• Number value — compare a numeric tag against a value or another tag.
• Boolean value — watch a true/false tag for a given state.
• Bit value — watch one bit within a packed value.
• Number of changes — watch how often a tag changes over a period.
• Ping — watch whether a host on the network is reachable.
• Planar range — watch two tags as an (X, Y) point against a region.

Priority

Each alarm has a priority — Low, Medium, or High — so the most important alarms stand out and can be filtered in the Alarm Manager.

Activation and deactivation delays

To avoid alerting on brief blips, an alarm can require its condition to hold for a set time before it activates (activation delay — the duration of anomaly needed to activate), and to stay normal for a set time before it clears (deactivation delay — the duration of normal conditions needed to deactivate).

Maintenance mode

When you need to work on equipment without generating noise, maintenance mode suppresses an alarm’s notifications for all users until you turn it off.

Organizing alarms

Alarms can be arranged into folders, and assigned to categories for filtering and access control. Like tags, alarms can be imported in bulk from a file, with control over how conflicts with existing alarms are handled.