Events Lists provide an audit trail of activity on your system. Events that are recorded in an Events List include those that relate to alarm activity. Alarm-related entries are displayed using the appropriate Severity color (see The Color of Entries in a List other than the Alarms List in the Geo SCADA Expert Guide to Lists). In each case, the entry’s Source indicates the Group, Group Instance, or item with which the event is associated.
Alarm-related activities that are recorded in the Event Journal (Events List) include:
- Alarm raised—Logged to indicate the occurrence of an unacknowledged uncleared alarm. Along with other information, the entry indicates the cause of the alarm and the item with which the alarm is associated (see Understand Events Lists in the Geo SCADA Expert Guide to Lists).
The entry is appended with the text (Suppressed Consequential) or (Suppressed Maintenance) should the alarm be suppressed. Suppressed alarms are not shown on alarm displays, such as Alarms Lists and the Alarm Banner, but do appear on other displays (see Alarm Suppression).
- Alarm <original alarm message> unsuppressed—Logged due to a suppressed alarm becoming unsuppressed. An alarm becomes unsuppressed should the abnormal condition that caused the alarm still exist, but the ‘parent’ alarm that caused the suppression clears.
- Alarm <original alarm message> redirected to <name of redirection action>—Logged due to an alarm being redirected using an Alarm Redirection Action (see the Geo SCADA Expert Guide to Alarm Redirection).
- Alarm <original alarm message> priority changed from <old severity level> to <new severity level>—Logged due to an alarm being redirected using a Change Priority alarm redirection action (see Change Priority Action in the Geo SCADA Expert Guide to Alarm Redirection).
- Alarm <original alarm message>, responsibility assigned to <User, User Group, or ViewX workstation>—Logged to indicate the name of the User, User Group, or ViewX workstation(s) with the ability to acknowledge this particular alarm. This type of entry indicates that either:
- The alarm has been redirected using a Set Responsibility Action alarm redirection action (see Set Responsibility Action in the Geo SCADA Expert Guide to Alarm Redirection)
or:
- The ability to acknowledge the alarm has been restricted by either the SetAlarmResponsibleUser, or SetAlarmResponsibleWorkstation methods. Both of these methods are associated with the CAlarmObject and CGroup database tables. For more information, see the database Schema.
- Alarm redirections matching group <redirection group> canceled—Logged due to the CancelRedirections method being used to cancel any alarm redirections that are associated with a particular Redirection Group. In addition to this entry, entries are also logged for each individual Alarm Redirection Action that was canceled due to the CancelRedirections method being triggered. For more information, see CancelRedirections and RestartRedirections Methods in the Geo SCADA Expert Guide to Alarm Redirection.
- Alarm <original alarm message>, alarm redirection <name of redirection action> canceled—Logged due to the CancelRedirections method being used to cancel alarm redirections. One event message is logged per canceled Alarm Redirection Action.
- Alarm redirections matching group <redirection group> restarted—Logged due to the RestartRedirections method being used to restart any previously canceled alarm redirections that are associated with a particular Redirection Group. In addition to this entry, entries are also logged for each individual Alarm Redirection Action that was restarted due to the RestartRedirections method being triggered. For more information, see CancelRedirections and RestartRedirections Methods in the Geo SCADA Expert Guide to Alarm Redirection.
- Alarm <original alarm message>, alarm redirection <name of redirection action> restarted—Logged due to the RestartRedirections method being used to restart previously canceled alarm redirections. One event message is logged per restarted Alarm Redirection Action.
- Alarm <original alarm message>, responsibility assignment removed—Logged due to either:
- A Set Responsibility Action alarm redirection being revoked. This will typically be due to a further Set Responsibility Action being triggered, to remove the restriction set by a previous Set Responsibility Action.
or:
- The ClearAlarmResponsibility method being used to remove the restriction on which User, User Group, or ViewX workstation(s) had the ability to acknowledge the original alarm. The ClearAlarmResponsibility method is associated with the CAlarmObject and CGroup database tables. For more information, see the database Schema.
- Alarm <original alarm message> acknowledged—Logged due to an existing alarm being acknowledged. The User column indicates the user that acknowledged the alarm. This might be a user that is logged onto the system, or a built-in internal ‘user’, such as a Logic program (see Understand Events Lists in the Geo SCADA Expert Guide to Lists).
The entry is appended with a comment if it was logged due to an Acknowledge with Comment action.
- Alarm <original alarm message> unacknowledged—Logged due to a previously acknowledged alarm being unacknowledged. The User column indicates the user that unacknowledged the alarm.
The entry is appended with a comment if it was logged due to an Unacknowledge with Comment action.
- Alarms disabled—Logged due to the Disable Alarms action being used to disable (hide) alarms on a particular item or group of items.
- Alarms enabled—Logged due to the Enable Alarms action being used to enable (register) alarms on a particular item or group of items.
- Alarm <original alarm message> removed—Logged due to an acknowledged alarm being removed. The User column indicates the user that removed the alarm.
The entry is appended with a comment if it was logged due to a Remove with Comment action.
- Alarm cleared—Logged due to an existing uncleared alarm clearing. An alarm clears once the abnormal condition that raised the alarm no longer exists.
The entry is appended with the text (Suppressed Consequential) or (Suppressed Maintenance) if the alarm cleared while it was suppressed (see Alarm Suppression).
Further Information
Alarm Redirections and Redirection Actions: see the Geo SCADA Expert Guide to Alarm Redirection.
Events and Events Lists: see the Geo SCADA Expert Guide to Lists.