Events
- Last UpdatedNov 02, 2023
- 2 minute read
The Event Summary window provides a detailed summary of the operational activity on the AVEVA Enterprise SCADA system. Events are recorded both for Controller-initiated actions and for application-generated activities.
A record is generated in the event summary when any of the following occur:
-
The system detects a condition which will generate an alarm.
-
A significant event occurs in an application.
-
You issue commands to field devices.
-
You modify system configuration parameters.
-
You acknowledge an alarm.
Event Logging
When an event is generated, it is recorded in two locations. First, a copy is stored in the Historical database (HDB) Event table (refer to the Historical Administrator documentation). You can view the event through the Event Summary window in easy eXtended Operator Station (ezXOS), as described in the AVEVA Enterprise SCADA HMI Controller documentation. Refer also to Spool events to a file.
Second, the event message is formatted and placed in the queue for the appropriate spooler. The spooler process records the event on the appropriate log printer or in a log file. The event message takes the form of a single line of text stating the nature of the occurrence. The group to which the field device is assigned determines which spooler is used. The designated “system” spooler is used for events that do not have an appropriate group. Groups are discussed in detail in Group table.
Note: The spooler record representing the default system spooler is created upon system installation and is required for proper system functionality. As such, this record should never be deleted.
The Event database will quickly fill with data if you do not empty or purge it periodically. The archive/cleanup process performs the necessary database purging. If you store events in a log file, you should periodically delete old entries from the log file.