ARENA / RANGER | USER GUIDE |
Email address.
•Acknowledged by station
ARENA that acknowledged the alarm
•Item Name
Alarm source (datapoint) that has caused the alarm.
–Shows ´System` when the alarm is a system alarm
–Shows the datapoint name for point alarms
•Item Value: value/status of the datapoint when the alarm has occurred.
–Shows N/A when the alarm is a system alarm that does not provide an item value.
–Shows the value and engineering unit of the datapoint when the alarm was raised for analog points
–Show the status text of the datapoint when the alarm was raised for digital points
•Alarm severity
Critical or Uncritical. For system alarms, this is always ´critical`
•Alarm class
System or Application (for point related alarms)
•Datapoint
Datapoint that caused the alarm
•Acknowledged
•Shows whether the alarm is acknowledged (Yes) or not (No)
•Alarm Direction
Shows whether the alarm was coming (occurred) or going (cleared).
•Plant
Name of plant where the alarm occurred.
•Segment
Name of segment where the alarm occurred.
•Station
Name of station where the alarm occurred.
•System
Name of system where the alarm occurred.
Alarm Indication in Tree Any new alarm, regardless from which site it comes, is indicated by a red triangle at the tree item (site, controller, plant) that causes the alarm.
In the global alarm list, alarms can be:
•filtered
•printed
•deleted
•acknowledged
•uploaded
Alarm List Views Alarms can be displayed in 2 different ways:
•Detailled View
Coming and going alarms are displayed separately and can be acknowledged individually. The content of the list and the sort order of the list content can be configured.
•Summary View
Coming and going alarms are displayed in one line. An alarm is regarded as acknowledged, if both, coming and going alarm, have been acknowledged. If an alarm is acknowledged, both alarms (coming and going) are acknowledged. The sort order of the list content can be configured.
74 |
