Event List

The Event List window displays all the detected events with each one on a separate row. This window is your main starting point for dealing with events. For instructions, see the step-by-step section.

When opened, Event List displays in the main work area of the user interface. When it is closed, depending on the Client Profile Event List may be either entirely hidden or collapsed to a vertical bar down the left side of the screen.

The display of Event List is limited to 10000 event lines; if such limit is exceeded, the status bar of Event List will indicate the display limit and the total number of events detected (for example, 10000 of 50000).

Event List Workspace

1

Summary bar

Contains a set of event lamps that provide an overview of the events in the system. For more details, see Event Lamps and Summary Bar.

2

Event Detail bar

In some configurations, prominently displays an event that requires immediate attention across the top of the screen.

3

Title bar

Depending on what you select, the title bar of the Event List window shows:

  • Event List if no event is selected in the list.
  • Event location if a single event is selected in the list.
  • Number of events being processed, if multiple events are selected in the list.
  • Details of the applied filter, if a filter is applied to the events, and no event is being processed.

It also contains some icons to open/close the Contextual pane (6), and depending on the Client Profile, lock the layout and restore down the window.

4

Event button

Graphic indicator of an event in the system. For more details, see the reference section.

5

Event descriptor

Contains the event button, event details and event-handling commands for the event currently being processed. For more details, see the reference section.

6

Contextual pane

Hidden by default. When open, it provides additional information, actions, and resources about the object that issued the event. The following tabs are available:

  • Operation/Extended Operation: Lets you inspect all the properties of the event source, and view and execute any commands/actions available for that object. If you selected multiple events, these tabs display only the properties common to all the events, properties having different values are marked with an asterisk.
  • Detailed Log tab: Lets you view a detailed log of the currently selected event.

A contextual menu becomes available when you right-click the Event List column headers and provides you with options to customize the columns that display in Event List, and to print out the whole list of events.

Events in Distributed Systems

In distributed systems, to view the total number of events for an individual system, check—in the Extended Operation tab—the Event Count property of its Main Server.

Incomplete Alarm Information in the Event List

In some alarm situations, the operator will see only partial information about an alarm on the event list. For example, the event list might show that the alarm has returned to normal without a corresponding off-normal alarm entry, or the operator might see repeated alarm events without an explanation of whether the system returned to normal in between each alarm. In cases where the event list contains what appears to be an incomplete sequence of alarm events, be sure to check the full event log contained within the history database (see “Operating Reference -> Alarms –> Activity Log and Event Log” for more on accessing the event log). Depending on the specific alarm logic of an event, the event log will contain a more complete picture of the of the transitions before, after and during an alarm than the summary information contained in the event list window.

Driver Generated Events

Driver generated events, for example, may create an unusual pattern in the alarm list. A driver generated event means that an object has transitioned from one alarm state to another, without returning to a normal state first. When this happens, the driver generates the missing “to-normal” state (all alarm states must have a corresponding normal state). A driver generated event can occur when a device fails to send the additional state or if the workstation was down for a period of time and missed the event.