The name of the item with which the alarm is associated.

Items form part of an equipment hierarchy. They can be used to associate tags, alarms and trends with a particular attribute of a physical piece of equipment (see Items).

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

If you leave this field blank, the last 63 characters of the Alarm Tag field will be used for the Item Name. Be aware that the Alarm Tag allows 79 characters, while Tag Item has a maximum of 63 characters. This may result in compiler errors if the combination of '<Equipment>.<TagItem>' is not unique.

Note: When entering an Item Name, there are a number of reserved words that you need to avoid. These reserved words relate to syntax that is used for tag extensions. They are:
• field
• valid
• override
• overridemode
• controlmode
• status
• v
• vt
• q
• pt
• t
If you use one of these reserved words, an error message will display when you compile your project.

Any useful comment.

The Cicode expression that triggers the alarm. Whenever the result of the expression changes to TRUE, the alarm is triggered.

A user-defined string for filtering active alarms (maximum 64 characters).

Used in a custom Cicode query function as search criteria, the custom alarm filterCustom alarm filters provide a way to filter and display active alarms. Up to eight custom filter strings can be assigned to a configured alarm. In conjunction with a user-defined query function, the custom filters enable operators to identify and display active alarms of interest. enables operators to identify and display a subset of active alarms.

Notes:

•Custom filters are visible only when the Advanced Alarms form is open in Extended mode.
• The fields are not case-sensitive and can contain 'A'..'Z', 'a'..'z', '0'..'9', and the underscore '_'.
• A custom filter cannot start with a digit.

A read only text string that indicates the paging group to which the alarm belongs. Maximum length is 80 characters. See your third-party paging system documentation for information on how to use this Paging Group string. This property can be read using alarm tag browsing or when tag properties are enabled read using the tagname "myCluster.myAlarm.paginggroup". For example, assign the value of PagingGroup to a variable:

myString = myCluster.Alarm_1.paginggroup

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

If you assign an acknowledgment privilege to an alarm, you should check the privilege that is 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.

This field enables you to automatically historizeAn object ID associated with every tag in a project that uniquely identifies the tag for use by tag-based drivers, automatically generated at compile. It is used instead of the actual address of the register (which is what most other drivers use to read from and write to I/O devices). and publish the specified digital alarm in Schneider Electric's Historian application.

If you set this field to "TRUE", the variable will be included in an automated configuration process within the Historian environment. If you set the field to "FALSE" (or leave it blank), the variable will not be included.

See Integration with Historian.

The project in which the alarm is configured.