Notes on BIBB’s are provided here: http://www.chipkin.com/articles/bacnet-bibbs
|
AE-ACK-A |
Alarm and Event Notification – Acknowledgement |
|
Alarm and Event Management |
|
A client sends an acknowledgement after receiving an Alarm or Event notification that requires one. |
|
AE-ACK-B |
Alarm and Event Notification – Acknowledgement |
|
Alarm and Event Management |
|
A server processes an alarm or event notification |
|
AE-ASUM-A |
Alarm and Event – Alarm Summary |
|
Alarm and Event Management |
|
A client polls for a summary |
|
AE-ASUM-B |
Alarm and Event – Alarm Summary |
|
Alarm and Event Management |
|
Server sends an alarm summary |
|
AE-ESUM-A |
Alarm and Event – Enrolment Summary |
|
Alarm and Event Management |
|
Client wants a summary of event initiating objects. Selection criteria may be specified in the request. |
|
GetEnrollmentSummary |
No |
Yes |
|
AE-ESUM-B |
Alarm and Event – Enrolment Summary |
|
Alarm and Event Management |
|
Server sends a list of selected objects that are event initiating. Selectionis based on the requesting criteria. |
|
GetEnrollmentSummary |
Yes |
No |
|
AE-INFO-A |
Alarm and Event – Information |
|
Alarm and Event Management |
|
The GetEventInformation service is used by a client BACnet-user to obtain a summary of all “active event states”. The term |
|
“active event states” refers to all event-initiating objects that |
|
(a) have an Event_State property whose value is not equal to NORMAL, or |
|
(b) have an Acked_Transitions property, which has at least one of the bits (TO-OFFNORMAL, TO-FAULT, TONORMAL) |
|
GetEventInformation |
Yes |
No |
|
AE-INFO-B |
Alarm and Event – Information |
|
Alarm and Event Management |
|
Server sends a summary of all active event states |
|
“active event states” refers to all event-initiating objects that |
|
(a) have an Event_State property whose value is not equal to NORMAL, or |
|
(b) have an Acked_Transitions property, which has at least one of the bits (TO-OFFNORMAL, TO-FAULT, TONORMAL) |
|
GetEventInformation |
No |
Yes |
|
AE-LS-A |
Alarm and Event – Life Saftey |
|
Alarm and Event Management |
|
A client devices as a life saftety device is able to process and acknowldege notifications it receives about life safty events. The Client |
|
sends a reset, silence or unsilence message. Is intended for fire and life safety systems. |
|
LifeSafetyOperation |
Yes |
No |
|
AE-LS-B |
Alarm and Event – Life Saftey |
|
Alarm and Event Management |
|
A device as a server and as a life saftey device sends notifications about life safety events. Server performs the reset or silence |
|
LifeSafetyOperation |
No |
Yes |
| AE-N-A |
Alarm and Event Notification |
|
Alarm and Event Management |
|
A Client can process notifications about alarms and other events from any standard or proprietary eventgenerating |
|
object of any standard or proprietary event type. |
|
UnConfirmedEventNotification |
No |
Yes |
|
ConfirmedEventNotification |
No |
Yes |
|
AE-N-E-B |
Alarm and Event Notification – External Device |
|
Alarm and Event Management |
|
Server device sends notifications about alarms and other events in another device. At least one event enrolment object mustbe |
|
supported and DS_RP-A and AE-N-I-B must be supported. If the notifications require acknowldgement then the server must be capable |
|
of processing the acknowledgdments by supporting AE-ACK-B |
|
object of any standard or proprietary event type. |
|
AE-N-I-B |
Alarm and Event Notification – Internal |
|
Alarm and Event Management |
|
Server device sends notifications about alarms and other events. The server must support Intrinsic or Algorihmic reporting. If the |
|
notifications require acknowldgement then the server must be capable of processing the acknowledgdments by supporting AE-ACK-B |
|
object of any standard or proprietary event type. |
|
ConfirmedEventNotification |
Yes |
No |
|
UnconfirmedEventNotification |
Yes |
No |
|
Client can subscribe for COV notification and can process the notifications from the remote device.Support for subscriptions of a |
|
limited lifetime is required, and support for subscriptions of indefinite lifetime is optional. This service has two important differences |
|
from the SubscriveCOVProperty service. Firstly, there is a limited set of properties (For the most part, Present_Value and Status_Flags) |
|
it may subscribe to and secondly the COVIncrement is not part of the subscription – the notifications are based on how the server is |
|
UnconfirmedCOVNotification |
No |
Yes |
|
ConfirmedCOVNotification |
No |
Yes |
|
Server can accept subscriptions and send COV notifications to the remote device. Requires support for a minimum of five concurrent |
|
subscriptions. Support for |
|
subscriptions of a limited lifetime is required, and support for subscriptions of indefinite lifetime is optional. |
|
ConfirmedCOVNotification |
Yes |
No |
|
UnconfirmedCOVNotification |
Yes |
No |
|
DS-COVP-A |
Change of Value – Property |
|
Client can subscribe for COV notification of one/more properties of a single object and can process the notifications from the remote |
|
device.Support for subscriptions of a limited lifetime is required, and support for subscriptions of indefinite lifetime is optional. This |
|
service allows the COVIncrement to be specified and range of subscribable properties is larger than DS-COV-A |
|
ConfirmedCOVNotification |
No |
Yes |
|
UnconfirmedCOVNotification |
No |
Yes |
|
DS-COVP-B |
Change of Value – Property |
|
Server can accept subscriptions and send COV notifications Requires support for a minimum of five concurrent subscriptions. Support |
|
for subscriptions of a limited lifetime is required, and support for subscriptions of indefinite lifetime is optional. |
|
ConfirmedCOVNotification |
Yes |
No |
|
UnconfirmedCOVNotification |
Yes |
No |
|
DS-COVU-A |
Unsolicited COV |
|
Client can process unsolicited COV messages from a Server. |
|
UnconfirmedCOVNotification |
No |
Yes |
|
DS-COVU-B |
Unsolicited COV |
|
Server can send unsolicited COV messages to a remote client. |
|
UnconfirmedCOVNotification |
Yes |
No |
|
Client Polls for Data from remote device |
|
DS-RPC-A |
Read Property Conditional |
|
Client polls for data from one/more properties from one/more objects. Selection is based on criteria specified. |
|
ReadPropertyConditional |
Yes |
No |
|
DS-RPC-B |
Read Property Conditional |
|
Server responds conditionally sending selected properties from selected objects based on conditional criteria. |
|
ReadPropertyConditional |
Yes |
No |
|
DS-RPM-A |
Read Property Multiple |
|
Client Polls for Data from remote device |
|
ReadPropertyMultiple |
Yes |
No |
|
DS-RPM-B |
Read Property Multiple |
|
ReadPropertyMultiple |
No |
Yes |
|
Client sets the value of a property of a single object in the server device. |
|
Server allows a value to be changed by a remote client. |
|
DS-WPM-A |
Write Property Multiple |
|
Client sets the value of a one/more properties of a single object in the server device. This is different from ReadPropertyMultiple which |
|
can process properties more than one object. |
|
WritePropertyMutiple |
Yes |
No |
|
DS-WPM-B |
Write Property Multiple |
|
Server allows the values of one/more properties to be set by a remote client. |
|
WritePropertyMutiple |
No |
Yes |
|
DM-BR-A |
Backup and Restore |
|
Client reads the files that contain the configuration of the B device and writes those files to the B device should it |
|
need to be restored to its previously backed-up state. |
|
ReinitializeDevice |
Yes |
No |
|
DM-BR-B |
Backup and Restore |
|
Server sends it’s cofiguration to a remote client and allows a remote device to restore it by accepting a configuration and allowing a |
|
ReinitializeDevice |
No |
Yes |
|
DM-DCC-A |
Commication Control |
|
The DeviceCommunicationControl service is used by a client BACnet-user to instruct a remote device to stop initiating and |
|
optionally stop responding to all APDUs (except DeviceCommunicationControl or, if supported, ReinitializeDevice) on the |
|
communication network or internetwork for a specified duration of time. This service is primarily used by a human operator |
|
DeviceCommunicationControl |
Yes |
No |
|
DM-DCC-B |
Commication Control |
|
The controlled device responds to the request. |
|
DeviceCommunicationControl |
No |
Yes |
|
DM-DDB-A |
Dynamic Device Binding |
|
A client can send discovery messages as well as process discovery anouncements send by other devices |
|
DM-DDB-B |
Dynamic Device Binding |
|
A server can process discovery requests and can accounce itself. |
|
DM-DOB-B |
Dynamic Object Binding |
|
Client polls to see which devices contain an object specified by Name or Object Identifier |
|
DM-LM-A |
List Manipulation |
|
Many BACnet object types have properties that are lists of a particular datatype. The Client can add and remove list |
|
elements in properties of objects in the Server |
|
DM-LM-B |
List Manipulation |
|
The Server device removes/add the items the client requested to be changed in the list |
|
DM-OCD-A |
Object Creation and Deletion |
|
A client requests a server device to create / delete an object. Only applies to the Object Types supported on the server. Check the server |
|
device PICS statememnt as it shoud contain a list of the types which can be dynamicallly manipulated. |
|
DM-OCD-B |
Object Creation and Deletion |
|
A server device processes the request to add / delete objects on the fly. |
|
Client sends non-BACNet data to a remote device. |
|
ConfirmedPrivateTransfer |
Yes |
No |
|
UnconfirmedPrivateTransfer |
Yes |
No |
|
The Recipient of the non-BACNet data, processes the data. |
|
UnconfirmedPrivateTransfer |
No |
Yes |
|
ConfirmedPrivateTransfer |
No |
Yes |
|
When devices restart they can send notifications of this event. Support for this BIBB means the device can process these notifications |
|
UnconfirmedCOVNotification |
No |
Yes |
|
When a device restarts it can send notifications of this event. |
|
UnconfirmedCOVNotification |
Yes |
No |
|
Client requests a device to reinitialize |
|
ReinitializeDevice |
Yes |
No |
|
Server device performs the reinitialization |
|
ReinitializeDevice |
No |
Yes |
|
Client sends text data to a remote device. The device must support at least one of the services. |
|
UnconfirmedTextMessage |
Yes |
No |
|
ConfirmedTextMessage |
Yes |
No |
|
The Recipient of the Text data, processes the data. |
|
UnconfirmedTextMessage |
No |
Yes |
|
ConfirmedTextMessage |
No |
Yes |
|
DM-TS-A |
Time Synch – Local Time |
|
Client sends a time synch message. The TimeSynchronization service is used by a requesting BACnet-user to notify a remote device of |
|
the correct current time. |
|
This service may be broadcast, multicast, or addressed to a single recipient. Its purpose is to notify recipients of the correct |
|
current time so that devices may synchronize their internal clocks with one another. |
|
TimeSynchronization |
Yes |
No |
|
DM-TS-B |
Time Synch – Local Time |
|
The server device applies the time synch. Its device object must support the Local_Time and Local_Date properties. |
|
TimeSynchronization |
No |
Yes |
|
DM-UTC-A |
Time Synch – Coordinated Universal Time |
|
Client sends a time synch message. The TimeSynchronization service is used by a requesting BACnet-user to notify a remote device of |
|
the correct current time. |
|
This service may be broadcast, multicast, or addressed to a single recipient. Its purpose is to notify recipients of the correct |
|
current time so that devices may synchronize their internal clocks with one another. |
|
UTCTimeSynchronization |
Yes |
No |
|
DM-UTC-B |
Time Synch – Coordinated Universal Time |
|
The server device applies the time synch. Its device object must support the Local_Time , Local_Date, UTC_Offset …properties. |
|
UTCTimeSynchronization |
No |
Yes |
|
A client opens and conducts a Virtual Terminal session with a remote device. |
|
A server devices allows a Virtual Terminal sessions to be opended and exchanges data with the remote client. |
|
NM-CE-A |
Connection Establishment |
|
A device sends a command to a half-router to establish/terminate connections |
|
Establish-Connection-To-Network |
Yes |
No |
|
Disconnect-Connection-To-Network |
Yes |
No |
|
NM-CE-B |
Connection Establishment |
|
A half-router processes commands to establish/terminate connections |
|
Disconnect-Connection-To-Network |
No |
Yes |
|
Establish-Connection-To-Network |
No |
Yes |
| NM-RC-A |
Router Configuration |
|
Client sends messages to configure or query a router or half-router |
|
Initialize-Routing-Table-Ack |
No |
Yes |
|
Initialize-Routing-Table |
Yes |
No |
|
Who-Is-Router-To-Network |
Yes |
No |
|
I-Am-Router-To-Network |
No |
Yes |
|
I-Could-Be-Router-To-Network |
No |
Yes |
|
NM-RC-B |
Router Configuration |
|
A router or half-router acts on configuration commands or responds to queries about the configuration. |
|
Who-Is-Router-To-Network |
Yes |
Yes |
|
Initialize-Routing-Table |
No |
Yes |
|
Initialize-Routing-Table-Ack |
Yes |
No |
|
I-Am-Router-To-Network |
Yes |
Yes |
|
A client manipulates schedules and calandars in a server device. To do this the client musts support these two BIBBs DS-RP-A and DS- |
|
SCHED-E-B |
Scheduling-External |
|
Allows time and date scheduling of specific objects in other devices. To support SCHED-E-B the device must also required to support |
| SCHED-I-B |
Scheduling-Internal |
|
A device as a server has objects and properties that can be scheduled by date and time. The device supports at least one calandar and |
|
one schedule object (must support at least 6 entries per day). This device must also support DM-TS-B and/or DM-UTC-B to claim support |
|
T-ATR-A |
Automated Trend Retrieval |
|
A device as a client can respond to notifications that a trend log is ready and reads the new data from the server. |
|
ConfirmedEventNotification |
No |
Yes |
|
T-ATR-B |
Automated Trend Retrieval |
|
When a trend log has aquired a preset number of records the device (as a server) sends notification to a client device. |
|
ConfirmedEventNotification |
Yes |
No |
|
T-VMT-A |
Viewing and Modifying Trends |
|
A client can display Trend Data obtained from the server device and can maipulate parameters in the remote server device that control |
|
T-VMT-E-B |
Viewing and Modifying Trends External |
|
The device as a server can collect trend log data from an external device and store these records internally. The device must also |
|
support T-VMT-I-B and DS-RP-A. |
|
T-VMT-I-B |
Viewing and Modifying Trends Internal |
|
The device as a server can collect trend log data records and store them internally. Support for at least one Trend Log Object is provided. |