Notification Class Manager - Honeywell Centraline FALCON User Manual

Table of Contents

FALCON

About Notification Class

Object Types

EN2Z-0962GE51 R0715

The notification class manager in CARE is used for adapting the alarming to the EBI

central and 3

party BACnet clients according to the requirements.

This is done by creating, editing and deleting notification class objects. Notification

class objects will be assigned to datapoints in order to enable alarming for

datapoints.

Notification class objects represent and contain information required for the

distribution of event notifications within a BACnet system.

Notification Classes are useful for event-initiating objects that have identical needs

in terms of how their notifications should be handled, what the recipient(s) for their

notifications should be, and how they should be acknowledged.

A notification class defines how event notifications shall be prioritized in their

handling according to TO-OFFNORMAL, TO-FAULT, and TO-NORMAL events;

whether these categories of events require acknowledgment (nearly always by a

human operator); and what recipient devices (e.g. Excel Web HTML Interface, EBI)

or processes should receive notifications.

The purpose of prioritization is to provide a means to ensure that alarms or event

notifications with critical time considerations are not unnecessarily delayed. The

possible range of priorities is 0 - 255. A lower number indicates a higher priority.

Priorities may be assigned to TO OFF-NORMAL, TO FAULT, and TO NORMAL

events individually within a notification class.

In CARE, the alarms/event notifications are prioritized by default as follows:

Event / Alarm Category

Urgent (range 0...84)

High (range 85...169)

Low (range 170...250)

NOTE: The CARE ranges slightly differ from the event / alarm priority ranges

defined in the BACnet standard which affects the associated network

priority (see "Alarm and Event Priority Classification" section below).

The transitions have the following denotation:

Back To-Normal

The alarm is going to normal state, that is, the value of the datapoint remains under

the high limit, or exceeds the low limit.

To Off-Normal

The alarm reaches off-normal state, that is, the datapoint value exceeds the high

limit, or remains under the low limit.

To Fault

The alarm originates in a fault such as sensor break, etc. See "Point Flag

Indications" for details.

The purpose of acknowledgment is to provide assurance that a notification has been

acted upon by some other agent, rather than merely having been received correctly

by another device. In most cases, acknowledgments come from human operators.

TO OFF-NORMAL, TO FAULT, and TO NORMAL events may, or may not, require

individual acknowledgment within a notification class.

It is often necessary for event notifications to be sent to multiple recipients or to

different recipients based on the time of day or day of week. Notification Classes

may specify a list of recipients, each of which is qualified by time, day of week, and

type of handling. A recipient is specified by a set of days of the week (Monday

through Sunday) during which the recipient is considered viable by the Notification

110