Documentation for Axxon PSIM 2.0. Documentation for other versions of Axxon PSIM is available too.

Previous page Next page


On this page:

Purpose

The incident manager is used for processing events and generating reports (see Control and handling of events using the incident manager).

Functions

The incident manager has the following functions:

  1. Event handling according to a pre-configured script.
  2. Automatic execution of macros that are started by certain operator actions.
  3. Generation of a report on the event and operator actions.

Interface description

The incident manager interface is shown in the figure:

The incident manager interface consists of three parts:

  1. Event grouping panel (1).
    The events can be grouped by:
    1. Object.
    2. Event type.
    3. Region.
    4. No grouping—all events are displayed.
  2. Table with a list of events (2).
    The following information is displayed for each event:
    1. Indicator of the presence of the camera associated with the event .
    2. #—the column displays the indicator of event locking.
      Display of locking:
      1. Locked remotely—.
      2. Locked locally—.
    3. Event ID.
    4. Incident handler—the name of the incident handler that handles the event.
    5. Event status.
    6. Object type.
    7. Object ID.
    8. Object name.
    9. Action—description of the event.
    10. Time the event occurs.
    11. Priority.
    12. Computer—the name of the computer from which the event is received.
    13. Time (sec)—the number of seconds since the event occurred.
    14. Last comment—only the last comment entered while handling the event.
    15. All comments—all comments entered while handling the event.
    16. Additional information.
  3. Event handling interface (3).
    The event handling logic is configured based on the requirements of the configured security system (see Creating and configuring event handling logic).

To go to the report at any time, click the Interim report button (4).

The report is built on the basis of the operator's actions during event processing. The report opens automatically after completing the entire chain of actions if it is specified in the incident manager settings.

  • No labels