Configuring Metasys/BACnet Integration Alarming - Metasys - LIT-12011942 - Software Application - ODS Server - 10.1

Metasys Open Data Server Help

Product name
ODS Server
Document type
User Guide
Document number
Revision date

About this task

The BACnet Intrinsic Alarming and BACnet Event Enrollment Object Alarming routing services are fully compliant with the BACnet standard specifications and should only be used when integrating your Metasys system with BACnet devices.

You can configure intrinsic alarming online at the SMP UI or offline in the SCT. Intrinsic alarming for FAC objects can be defined with the SMP or offline with CCT.

To configure Metasys/BACnet integration alarming:


  1. Set the BACnet Site attribute to true in each Site Object representing a site that you want to use Metasys/BACnet Integration alarming.
  2. For each NAE in the site using alarming integration, configure one or more Notification Class objects for routing event messages from Event Enrollment objects and/or objects with intrinsic alarming to BACnet device destinations. Be sure you reference the BACnet devices by adding them to the Recipient List of the Notification Class object. Identify a BACnet device by using either its network address or BACnet device identifier (OID).


    • If you want to display alarm and event data from BACnet device destinations on the Metasys system Alarms Window and Event Viewer, set the Notification Class Object’s Route to Metasys attribute to true. The BACnet device must specify the NAE as a recipient for their alarms. To make the NAE an alarm recipient, configure a Notification Class object on the BACnet device. Alarms and acknowledgements from the BACnet device are incorporated into the Metasys alarming system. To route BACnet alarms from the N30 to the NAE, the N30 must be configured to use BACnet alarm routing. For information on how to configure the N30 to use BACnet alarm routing, refer to the documentation of the BACnet device you are integrating.
    • When the NAE receives an alarm from an NAE, it can be sent from the DDAs on the receiving NAE but cannot be routed again from that NAE. If the alarms need to be routed from the NAE device, they should set the Use Remote Alarming to False for objects in the FAC.
  3. Configure one or more Event Enrollment Object or objects that supports intrinsic alarming using the Object. See BACnet Intrinsic Alarming for a list of objects that support intrinsic alarming.


Note: For both types of these alarm generating objects, you must configure the Event Enrollment object’s Notification Object Reference attribute to reference the Notification Class Object created in Step 2. This reference represents the instance number of the Notification Class (value of its Object Identifier attribute). The Notification Class object and the alarming object must exist on the same device.

See BACnet Intrinsic Alarming for more information on intrinsic alarming.

See BACnet Event Enrollment Object Alarming for information on Event Enrollment alarming.

For more information on BACnet IP Integration, see the BACnet IP Integration Object and the Related Documentation table.