Intrinsic reporting
With intrinsic reporting, the alarmable object itself assumes alarm identification and state machine for alarm handling. However, the subsequent distribution of alarm messages to alarm clients and the alarm management is no longer the responsibility of the alarm source itself, but of a Notification Class object assigned to the alarm source. The Notification Class object is both a D-MAP function block and a standard BACnet object, which contains all the information required for the distribution of alarms and system events within the system.
Algorithmic reporting
With algorithmic reporting, alarm detection and the state machine for alarm handling normally are taken over by the Event Enrollment object. In this case, alarm management also is set up in an alarm source via assigned Notification Class object.
Notification Class
Each alarm-generating object is assigned one notification class [NotifCl] only, but one notification class can be used by more than one alarm-generating object. This makes it possible to create a Notification Class object for each group of alarms (e.g., HVAC alarms, fire alarms etc.). Each alarm source in a given alarm group is assigned to the [NotifCl] for that group.
There are global and local notification class objects:
- Global notification class: One set of max. 18 global notification class objects per site. Global notification classes are replicated and thus exist on all Desigo PX of a site in identical form.
- Local notification class: On Desigo PX, local notification classes can be engineered, but are NOT replicated.
- Desigo room automation supports exclusively local notification classes.
Interface definition
The notification class function block [NotifCl] is the means by which functionality is transferred from the BACnet standard into the CFC environment.
This function block contains the instance number of the Notification Class (an integer). which must be identical to the value entered in the subordinate alarm sources. This makes it possible to create a unique reference.
The number must not be modified online.
Notification class number
There are 18 predefined global notification classes. The notification class is identified with the two independent variables AlarmFunction and AlarmClass, and referenced in the alarm source:
- AlarmFunction [Simple(1), Basic(2), Extended Alarm(3)]
- AlarmClass [UrgentAlarm (1), HighPrioAlarm (2), NormalAlarm (3), LowPrioAlarm (4), UserDefinedAlarm (5) and OffLineTrend (6)]
Formula
The notification class number is calculated as follows:
NotificationClass# := 10 * AlarmClass + AlarmFunction
This gives the following notification classes:
AlarmClass | AlarmFunction | Priority | Uses | NotificationClass# (derived) |
|---|---|---|---|---|
|
|
| Highly critical alarms, system messages, device info object |
|
UrgentAlarm | Simple | 1, 1, 5 |
| 11 |
UrgentAlarm | Basic | 1, 1, 5 |
| 12 |
UrgentAlarm | Extended | 1, 1, 5 |
| 13 |
|
|
| Critical alarms |
|
HighPrioAlarm | Simple | 2, 2, 6 |
| 21 |
HighPrioAlarm | Basic | 2, 2, 6 |
| 22 |
HighPrioAlarm | Extended | 2, 2, 6 |
| 23 |
|
|
| Normal alarms |
|
NormalAlarm | Simple | 3, 3, 7 |
| 31 |
NormalAlarm | Basic | 3, 3, 7 |
| 32 |
NormalAlarm | Extended | 3, 3, 7 |
| 33 |
|
|
| Non-critical alarms |
|
LowPrioAlarm | Simple | 4, 4, 8 |
| 41 |
LowPrioAlarm | Basic | 4, 4, 8 |
| 42 |
LowPrioAlarm | Extended | 4, 4, 8 |
| 43 |
|
|
| As project-specific alarms for special applications |
|
UserDefinedAlarm | Simple | 5, 5, 9 |
| 51 |
UserDefinedAlarm | Basic | 5, 5, 9 |
| 52 |
UserDefinedAlarm | Extended | 5, 5, 9 |
| 53 |
|
|
| Offline trends The To-Normal priority must be such that it is less than or equal to the Alarm Priority Limit of the device object (for Remote Mgmt) |
|
OffLineTrend | Simple | 2, 2, 2 |
| 61 |
OffLineTrend | Basic | 2, 2, 2 |
| 62 |
OffLineTrend | Extended | 2, 2, 2 |
| 63 |
Project-specific notification classes can be defined in addition to predefined ones. Alarm classes 7...16 are intended for this purpose. The associated calculation of a notification class number is identical to calculation of predefined notification class numbers.
Customized alarms can be engineered in Desigo PX. In this case, the value for a notification class number can be defined without restrictions.
Priority [Prio]
This defines the alarm priority on the basis of which alarm and system events are to be transmitted to the receivers. Every transition can be described individually with this BACnet property, data type ARRAY of INTEGERS [TO_OFFNORMAL; TO_FAULT; TO_NORMAL]. Priority levels can range in value from 0 to 255. The lower the value, the higher the priority. In Desigo only priorities 1 to 9 are used.
Alarmfunction [AlmFnct]
Alarm function types: Simple, Basic or Extended. [AlmFnct] is only supported by Desigo PX.
Destination list [RecpList]
The configured (permanent) alarm recipients, the week days, and the time window in which the alarm recipient is operated, are entered here. [RecpList] is equivalent to the standard BACnet property Recipient_List.
Destination list [DestLi]
This is where the configured (permanent) alarm receivers are entered, together with the days of the week and the time-window in which the alarm receiver is operated. [DestLi] is only supported by Desigo PX.
Operator units:
- Permanently connected operator units (and hence, alarm receivers) are addressed by their Device Name.
- Operator units (and hence alarm receivers) with a point-to-point connection (PTP connection) are addressed with a Remote Area Site identifier and their Device Name. For example:
- B=fff for permanent connection
- B=kkk:aa for point-to-point connection (PTP connection)
- Adjustments are required during the addressing process so that there is no conflict between the names of operator units and the plant or room management designations.
Permanent and point-to-point connections:
- For alarm receivers, the address syntax (see further below) indicates the type of connection: permanent or PTP connections.
- Desigo PX automation stations with half-routers must know the Remote Area Site designators of their remote alarm receivers to enable an PX automation station to resolve the remote alarm receiver designator.
Alarm receiver syntax:
Element | Description |
|---|---|
DeviceName | Device name. In plain text so that the user can understand it. Example: CC 01 |
DeviceIdentifier | Device Identifier. Alternative syntax for the alarm receiver of a third-party manufacturer. If the alarm receiver has a special address range or if DeviceName does not work. Example: [13456] |
RemoteAreaSiteName | Remote area site name. In plain text so that the user can understand it. Example: Chur |
NetworkNumber | Network number. Required with a third-party half router. Example: [3] |