Alarm and Event Management Overview - Metasys - LIT-1201793 - Software Application - Site Management Portal - 12.0.50

Metasys Site Management Portal Help

Product name
Site Management Portal
Document type
User Guide
Document number
Revision date

An event is a notification of a state change of an item in the system. When a value in an FAC, Engine, or Metasys Server deviates from its normal operating condition, such as exceeding a high limit or failing to respond to a command within a specified time period, the system detects a change of state and the FAC, Engine, or Metasys Server generates an event message.

When an FAC generates an event message, it temporarily stores the event message in its Event Log. It also immediately forwards the event message to the Engine or configured Metasys Server to which it is connected. When an Engine generates an event message, it temporarily stores the message in its local event repository. When a Metasys Server generates an event message, it permanently stores the message in its event repository. You can send event messages stored in the local event repository of an Engine to the event repository of a Metasys Server for permanent storage by defining a Metasys Server event repository as the default destination. Also, you can route event messages to other destinations such as a pager or an email account. For more information, see the Event Repositories and Event Message Routing, Filtering, and Destinations sections.

For sites with Metasys for Validated Environments Installed (MVE) installed, configure the following attributes in the Site Object:

  • Annotation Include

  • Annotation Exclude

  • Annotation Alarm Priority Threshold

  • Signature Include

  • Signature Exclude

  • Signature Alarm Priority Threshold

These settings apply only to MVE sites and enable the MVE required annotations and electronic signature for event messages. You can apply these settings at the site level or down to the object level as needed. You can define the settings to require an electronic signature, an annotation, neither, or both. When both options are required and a user acknowledges or discards an event message, they are prompted to reauthenticate and enter a reason and annotation for the action. The user’s login name, date and time of signature, and the reason for signature are saved as part of the annotation. You cannot delete annotations on an MVE site.

Non-MVE sites may optionally define and use annotations; however, electronic signatures are specific to MVE sites.

See Configuring Annotation and Electronic Signature Requirements in the Site Object in MVE in the Site Management Portal User Interface section. For additional information, refer to the Metasys for Validated Environments on Site Management Portal Technical Bulletin (LIT-12011327).

The Alarms Window and Event Viewer allow you to examine and respond to event messages. The Alarms Window displays event messages one at a time in a prioritized order and allows you to respond to the newest alarm first. The Event Viewer displays all of the event messages stored in the event repository of the currently selected device. In addition, Alarm Reports allow you to query for alarm conditions in the Metasys system online and provide a list of items that are currently in an alarm condition.

Note: The current navigation view does not limit or affect the alarm notification; only the user’s permissions for managing item events can. Therefore, a user may receive an alarm for an item that does not exist in the currently displayed navigation view.

The following figure shows the flow of event messages through the Metasys system.

Figure 1. Event Message Flow

For information on how to configure and route event messages for Metasys systems integrated with BACnet devices, see Alarm and Event Management for Metasys Systems Integrated with BACnet Devices.