Intrinsic alarming is fully compliant with the BACnet standard specifications and should only be used when integrating with BACnet devices. Intrinsic alarming allows you to configure the detection of alarm conditions and the generation of event messages based on attributes (properties) within an object that is compliant with the standard BACnet objects, such as the High/Low alarm limits for analog objects and the alarm state for binary objects. The Notification Class Object routes the event message.
By default, objects do not have intrinsic alarming; however, you can add intrinsic alarming to an object by setting its Intrinsic Alarming Defined attribute to True. Also, you can add intrinsic alarming when you create an object, or you can add intrinsic alarming to an existing object. You can remove intrinsic alarming from an existing object by changing its Intrinsic Alarming Defined attribute to False. The Intrinsic Alarming Defined attribute is located under the BACnet heading in the Insert Object wizard and in the object’s Focus view, which is accessible when you select the Advanced option for the display. When you set the Intrinsic Alarming Defined attribute to True, the BACnet Alarm tab appears the next time you view the object. The default alarming settings (for example, high and low limits) are used until you change the settings on the BACnet Alarm tab. When you set the Intrinsic Alarming Defined attribute to False, all intrinsic alarm settings configured through the BACnet Alarm tab are discarded and the alarming settings return to their default values. For more information on configuring intrinsic alarming in an object, see Configuring Metasys/BACnet Integration Alarming.
Intrinsic alarming is only available for your Metasys system if you set the BACnet Site attribute to True in the Site object. See the Site Object for information on configuring the BACnet Site attribute.
To view the BACnet intrinsic alarming attributes of existing Metasys objects after they have been configured, view the object and click the BACnet Alarm tab. You can add alarm extensions to objects supporting intrinsic alarming.
The following Metasys objects are compliant with the standard BACnet objects and support BACnet intrinsic alarming:
After configuring one or more objects with intrinsic alarming, you must configure at least one Notification Class object to define the routing of event messages to BACnet device destinations. Then, you must reference the desired Notification Class object from the objects with intrinsic alarming. If you want the Notification Class object to route the event messages created by the objects with intrinsic alarming to the Metasys Alarm and Event Management feature, set the Notification Class object’s Route to Metasys attribute to true.
In addition, you can add object to objects with intrinsic alarming if you want to route event messages to both BACnet device destinations and Metasys DDAs. For more information on DDAs, see Event Message Routing, Filtering, and Destinations.
The Enable Alarms and Disable Alarms commands for objects using intrinsic alarming edit the Event Enable flags under Alarm State to prevent alarms.
You can configure intrinsic alarming online at the Site Management Portal (SMP) UI or offline in the SCT. Intrinsic alarms for objects in an FAC can be defined using CCT or SMP, but not SCT. If defined with SMP, you must specify if the intrinsic alarm is to Use Remote Alarming as defined in the object's Focus tab. If true, the intrinsic alarm parameters are stored in the FAC. If false, the parameters are stored in the Engine.
For details on the attributes appearing on the BACnet Alarms tab, see BACnet Alarm Tab in the Object and Feature Tabs section.