BACnet_NOC

The Notification Class object type (WinCC OA datapoint type) defines a standardized object that represents and contains information required for the distribution of event notifications within BACnet systems. Notification Classes are useful for event-initiating objects that have identical needs in terms of how their notifications should be handled, what the destination(s) for their notifications should be, and how they should be acknowledged.

A notification class defines how event notifications will 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 destination devices or processes should receive notifications.

The purpose of prioritization is to provide a means of ensuring 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.

The purpose of acknowledgment is to provide assurance that a notification has been acted upon by some other agent, rather than simply having been received correctly by another device. In most cases, acknowledgments come from human operators.

TO-OFFNORMAL, 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 destinations or to different destinations based on the time of day or day of week. Notification Classes may specify a list of destinations, each of which is qualified by time, day of week, and type of handling. A destination specifies a set of days of the week (Monday through Sunday) during which the destination is considered viable by the Notification Class object. In addition, each destination has a FromTime and ToTime, which specify a window, on those days of the week, during which the destination is viable. If an event that uses a Notification Class object occurs and the day is one of the days of the week that is valid for a given destination and the time is within the window specified in the destination, then the destination shall be sent a notification. Destinations may be further qualified, as applicable, by any combination of the three event transitions TO-OFFNORMAL, TO-FAULT, or TONORMAL.

The destination also defines the recipient device to receive the notification and a process within the device. Processes are identified by numeric handles that are only meaningful to the destination device. The administration of these handles is a local matter. The recipient device may be specified by either its unique Device Object_Identifier or its BACnetAddress. In the latter case, a specific node address, a multicast address, or a broadcast address may be used. The destination further specifies whether the notification will be sent using a confirmed or unconfirmed event notification.

Datapoint Type Name

BACnet_NOC

(Object/)Datapoint Type Structure

Faceplate

Tabs

The "Properties 1" shows the general property values of the object.

In the "Properties 2" tab the recipient for the notification class can be specified.

Click on the "+ IP" button, if for the recipient specification an IP address is given.

Click on the "+ DEV" button, if for the recipient specification a device number is given.

Recipient specification over an IP address:

Recipient specification over a device number:

For more information on tabs see Tabs.

Available Symbol Types

Name	Usage	$ Parameter	Symbol
NOC	Object for the time-related assignment of alarm end event messages.	DP