Add a Double Point Status Alarm

0

State Name 0

Unknown

Yes

No

State Type 0

Alarm

1

State Name 1

Open

No

Yes

State Type 1

Event

2

State Name 2

Closed

No

Yes

State Type 2

Event

3

State Name 3

Jammed

Yes

No

State Type 3

Alarm

Equipment

The name of the equipment associated with the double point status 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 (.).

Item Name

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 defining an item name, avoid using the Reserved Words. If you use any of these, an error message will display when you compile your project.

Alarm Tag

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 Structured Tag Names.

Alarm Name

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.

Cluster Name

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).

Category

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.

Alarm Desc

A meaningful description of the alarm condition. This description is used when details of the alarm are displayed on screen or logged to a device.

This field can support variable data (by enclosing an expression in braces).

For example:

"Line Broken Alarm at Line Speed {LineSpeed1}"

See Add Variable Data to Alarm Messages.

Delay

The alarm delay period (see Use Alarm Delay).

An alarm becomes active when the state of the triggering condition remains true for the duration of the delay period.

The delay period needs to be entered in the following format:

HH:MM:SS (Hours:Minutes:Seconds).

The value needs to be between 0 seconds (00:00:00) and 24 hours (24:00:00).

Help

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 Alarm() function is called.

Comment

Any useful comment.

Variable Tag

An integer tag that represents up to eight different states in a field device.

State Name <1>

to

State Name <7>

Enter a name that describes the associated state. If an alarm or event is triggered for this state, this name will appear in the State field of the Active Alarms page and/or the SOE page.

State Type <1>

to

State Type <7>

Determines the action that occurs when the device transitions to the defined state. The options are:

• Alarm - an alarm is added to the Active Alarms page and an event is logged to the SOE page. The State Name will appear in the State field.

• Event - indicates an OFF state has occurred. An event is logged on the SOE page, even if an alarm state transition did not occur. The State Name will appear in the State field.

• None - indicates an OFF state has occurred. The State Name will appear in the State field on both the SOE and Active Alarms pages when an alarm transition occurs.

  Note: If an alarm is currently in an "Event" or "None" state, a further transition to a "None" state will not be reported.

Custom 1 to Custom 8

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

Used in a custom Cicode query function as search criteria, the custom alarm filter enables operators to identify and display a subset of active alarms.

Note:

• 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.

Paging

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".

Paging Group

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

Area

The 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

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

If you assign an acknowledgment privilege to an alarm, there is no need to assign a privilege 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.

Historize

This field enables you to automatically historize and publish the specified analog alarm in CitectHistorian.

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.

Project

The project in which the time-stamped digital alarm is configured.