The name of the equipment associated with the analog alarm. Select a name from the drop-down list of existing equipment definitions, or enter a name.

There is a limit of 254 characters across the Equipment and Item Name fields, including any separating periods (.).

The name of the alarm tag. The name needs to be unique to the cluster and adhere to tag name syntax rules.

If your project includes a large number of tags, a naming convention can be helpful when searching and debugging tags (see Using structured tag names).

A meaningful description of the alarm, for example, a name that includes the physical device associated with the alarm. The name is used when details of the alarm are displayed on the screen or logged to a device. This field does not support variable data.

The name of the cluster that runs the alarm. This field needs to be defined if your project has more than one cluster.

You can leave this field blank in a multi-cluster system if cluster replication is enabled (see the parameter [General]ClusterReplication).

The alarm category to which the alarm is assigned, defined as either a category number or a label (see Categorize Alarms).

If not specified, the category defaults to category 0.

An analog variable tag, expression or base value that determines if a deviation alarmTriggered when the value of a variable deviates from a setpoint by a specified amount. The alarm remains active until the value of the variable falls (or rises) to the value of the deadband. is to be triggered. This property is optional. If a setpoint is not specified, it will default to 0 (zero).
Note: If set to an analog variable tag, it needs to be a different tag to the Variable Tag property of the alarm.

Delay period for High High Alarms. Alarm will activate if its triggering condition is met for the duration of the delay period (see Using Alarm Delay).

If no value is set, the high high alarm will be activated as soon as the tag exceeds the high high value.

Note: The delay period needs to be entered in the format HH:MM:SS (hours:minutes:seconds). The value needs to be between 0 seconds (00:00:00) and 24 hours (24:00:00).

The delay period for high alarms. Alarm will activate if its triggering condition is met for the duration of this period. If no value is set, the high alarm will be activated as soon as the tag exceeds the high value.

Note: The delay period needs to be entered in the format HH:MM:SS (hours:minutes:seconds). The value needs to be between 0 seconds (00:00:00) and 24 hours (24:00:00).

When a tag value increases from high to high high within the high delay period, the delay timer is reset. The high high alarm is only activated if the value remains in the high high range for the delay period.

When the value increases from high to high high after the high delay period has expired, a high alarm is activated and then the delay period for the high high alarm begins.

If the tag value exceeds the high high value and then falls below it before the high high delay period expires, at the time it falls, the high alarm is triggered immediately.

It has an ON time of when the tag value exceeded the high high value. These points also apply to tag values traveling between Low and Low Low ranges.

The delay period for Low Alarms. The alarm will only activate if its triggering condition is met for the duration of this period. This property is optional. If no value is set, the Low Alarm is activated as soon as the tag drops below the Low value.

Note: The delay period needs to be entered in the format HH:MM:SS (Hours:Minutes:Seconds). The value needs to be between 0 seconds (00:00:00) and 24 hours (24:00:00).

The delay period for Low Low Alarms. The alarm will only activate if its triggering condition is met for the duration of this period. If no value is set, the Low Low Alarm is activated as soon as the tag drops below the Low Low value.

Note: The delay period needs to be entered in the format HH:MM:SS (Hours:Minutes:Seconds). The value needs to be between 0 seconds (00:00:00) and 24 hours (24:00:00).

The analog variable (tag) or expression that triggers the alarm.

The value used as the triggering condition for a Deviation Alarm. A Deviation Alarm is activated when the value of the Variable Tag remains outside the deviation range (determined by the Setpoint) for the duration of the Deviation Delay period. This property is optional. If a deviation is not specified, no Deviation Alarm is activated.

The delay period for Deviation Alarms. The alarm will only activate if its triggering condition is met for the duration of this period. If no value is set, the Deviation Alarm is activated as soon as the Variable Tag falls outside the deviation range.

Note: The delay period needs to be entered in the format HH:MM:SS (Hours:Minutes:Seconds). The value needs to be between 0 seconds (00:00:00) and 24 hours (24:00:00).

By dividing this value by the alarm period, the "maximum rate" at which the value of the variable tag can change is determined. At each Scan Time, the value of the tag is checked. If its rate of change is greater than the maximum rate, a Rate of Change Alarm is triggered.

For example, to verify that a tank does not fill too quickly, you might configure a rate of change alarm, using a Rate of 300 liters, an [Alarm]Period of 60 seconds, and an [Alarm]ScanTime of 1 second. This means that the maximum allowable rate of change for the tank level is 5 l/sec (300 liters / 60 seconds). The actual rate of change at each ScanTime is calculated. That is, every second, it checks the current level of the tank and compares it to the level recorded a second earlier. If the actual rate of change is, say, 8 l/sec, a Rate of Change Alarm is triggered immediately.

The variable tags deadband % needs to be less than the alarms rate divided by the engineering scale of the variable tag. Otherwise, the rate of change alarm will only go off when the change in the variable tag exceeds the deadband value. If no value is set, no Rate of Change Alarm is activated.

Value the Variable Tag needs to return to before the Alarm becomes inactive.

The display format of the value (of the variable) when it is displayed on a graphics page, written to a file or passed to a function (that expects a string). If a format is not specified, the format defaults to the format specified for Variable tag.

The name of the graphics page that displays when the AlarmHelp() function is called by a user-defined command. If not specified no action occurs when the AlarmHelp() function is called.

Value used as the triggering condition for a high high alarm. If the value of the variable tag exceeds this value for the duration of the high high delay period the alarm will be triggered. The active alarm will have an ON time of when the tag exceeded the high high value. Because a high alarm needs to precede a high high alarm, when the high high alarm is triggered it replaces the high alarm.

To display more than one state on the alarm page at the same time, configure a separate alarm for each state. (Each alarm would monitor the same tag.)

The value used as the triggering condition for a high alarm. The high alarm becomes active when the value of the variable tag exceeds this value for the duration of the high delay period. The active alarm has an ON time of when the tag exceeded the high value.

The value used as the triggering condition for a Low Alarm. Alarm becomes active when the value of the Variable Tag drops below this value and remains there for the duration of the Low Delay period. The active alarm has an ON time of when the tag fell below the Low value.

A read/write property that indicates whether the alarm will be paged. When the value is 1 (TRUE) the alarm will be paged. The default value is 0 (FALSE). This property can be read using alarm tag browsing and read or modified when tag properties are enabled using the tag name "myCluster.myAlarm.paging".

Area the alarm belongs to. If an operator does not have access to an area, the alarm is not visible on the alarm display. For example, if you enter Area 1 here, operator need to have access to Area 1 (plus any necessary privileges) to acknowledge or disable this alarm.

The area and privilege fields defined here needs to be designed to work in conjunction. A privilege defined on a button (say) will ignore the alarm defined area.

Privilege necessary by an operator to acknowledge or disable the alarm.

If you assign an acknowledgment privilege to an alarm, you should also check the privilege that is also assigned to the command(s) that acknowledge the alarm. If you assign a different privilege to the commands, an operator needs to have both privileges to acknowledge the command. More importantly, the area defined here may be ignored.