Roster Selection Hierarchy
The system will select which active Roster to call for an alarm by matching its Area property to the source of the alarm. The following rules are applied to make that match. Note that rules for Alarm Area Filtering and Tag Area Filtering take precedence - operators are not called for an alarm that occurs in an area for which they are not authorized.
Whenever a device driver is referred to in these rules, it means the driver tag configured in the I/O tag. If that is a Polling Driver tag or a DriverMUX tag, then that is examined to the exclusion of other driver tags in the communication chain.
In general, Roster tags should use the area, Default, unless you intend to send different sets of alarms to different operators.
This rule applies only to I/O tags, status tags, control tags and the Data Flow Pulse Input. For Selector Switches, and legacy input tags and output tags, the area of the device driver is not checked when working through the roster hierarchy. Refer to the following table:
Support for the area property "GeneralAlarm" was removed in version 11.1.
I/O Type | Driver's Area Checked | Driver's Area Not Checked |
---|---|---|
I/O and Calculation | ✓ | |
Analog Control | ✓ | |
Analog Status | ✓ | |
Digital Control | ✓ | |
Digital Status |
✓ |
|
Data Flow Pulse Input |
✓ |
|
Pump Status |
✓ |
|
Selector Switch |
✓ |
|
String I/O |
✓ |
|
Analog Output |
✓ |
|
Analog Input |
✓ |
|
Digital Input |
✓ |
|
Digital Output |
✓ |
The rules are slightly different for alarms built into tags other than Alarm, and those for tags of type, Alarm.
Alarms built into I/O tags:
Alarm tags: