For database items that can raise alarms, every situation or ‘condition’ that can raise an alarm (such as a change in point state, or an outstation losing communications) is associated with an Alarm Condition. An alarm condition identifies the particular abnormal occurrence that has triggered the alarm (for instance, a ‘Point State’ condition indicates that a change in point state has caused an alarm to be raised). For more information, see Understand Alarm Conditions and Subconditions in the ClearSCADA Guide to Alarms.
You can use one of the %ACond...% trip sequences to include details about the alarm’s alarm condition in an E-Mail or Pager action. For example, you might use the %ACondActiveTime% trip sequence to indicate the time that the alarm condition occurred.
Each alarm condition comprises at least one Alarm Subcondition. A subcondition is a particular class of alarm condition. The active subcondition provides an indication of the cause or ‘state’ of the alarm (such as an analog point’s value exceeding the High limit). An alarm condition can only have one active subcondition at any time.
You can use one of the %ASubCond...% trip sequences to include details about an alarm’s active subcondition. For example, you might use %ASubCondActiveTime% trip sequence to indicate when a point went into a presently active alarm state (such as an analog point's High High state).
For a comprehensive list of %ACond...% trip sequences that you can use with alarm redirections, see Trip Sequences Supported by Redirection Actions.