What AE-N-I-B Is
AE-N-I-B (Alarm and Event-Notification Internal-B) is the BACnet Interoperability Building Block (BIBB) for a device that originates event notifications from intrinsic reporting on its own objects. A device claiming AE-N-I-B evaluates an intrinsic event algorithm on the monitored object itself and dispatches ConfirmedEventNotification or UnconfirmedEventNotification to the recipients named on the Notification Class object the alarming object points at.
“Internal” is the operative word: the object being watched and the object doing the dispatching live on the same device. It is the BIBB every alarming controller claims, and it is the one intrinsic event notification is built on. Origination through an Event Enrollment object watching a property on another device is a separate claim, AE-N-E-B.
What It Requires
AE-N-I-B does not name a single service. It requires the device to run at least one event algorithm to completion: detect the condition, transition Event_State, and generate a notification honoring the transition’s entry in Event_Enable. The algorithms available are a fixed set the standard defines, and a device can claim the BIBB with any one of them implemented.
| Piece | What it does |
|---|---|
| The event algorithm | Evaluates the monitored value against its parameters and drives Event_State |
Notification_Class | Names the class that carries the recipient list for this alarming object |
Notify_Type | Marks the notification as an alarm or an event, which changes whether acknowledgment applies |
| ConfirmedEventNotification / UnconfirmedEventNotification | The service that actually carries the notification to a recipient |
Where You Meet It in the Field
Every analog or binary point that can alarm on its own is claiming AE-N-I-B. A chiller controller raising OutOfRange on a leaving-water temperature, a VAV box raising ChangeOfState on a damper-end-switch fault, a trend log raising BufferReady: all the same BIBB, different algorithms.
[!NOTE] AE-N-I-B says the device can originate an event. It says nothing about who receives it, that is AE-N-A, or about the operator acknowledging what arrives, which is AE-ACK-A at the workstation and AE-ACK-B back at the device that raised it.
What Chipkin Provides
The CAS BACnet Stack supports AE-N-I-B today: intrinsic OutOfRange on analog objects and ChangeOfState on binary and multi-state objects, dispatched through the recipient list on a Notification Class, confirmed and unconfirmed. What ships today and what the 6.x algorithm registry is targeting has the full split.