What AE-N-E-B Is
AE-N-E-B (Alarm and Event-Notification External-B) is the BACnet Interoperability Building Block (BIBB) for a device that originates an event notification through an Event Enrollment object watching a property on a different device. “External” is the operative word, paired against AE-N-I-B, which covers the same origination role for a device alarming on its own objects.
A device claiming AE-N-E-B hosts the Event Enrollment object, evaluates the algorithm against the remote property it references, and dispatches the notification the same way an intrinsic object would: through a Notification Class recipient list.
What It Requires
AE-N-E-B does not require the hosting device to run any particular algorithm; it requires the Event Enrollment object’s Object_Property_Reference to resolve, its Event_Type and Event_Parameters to apply one of the standard algorithms to that referenced value, and the resulting notification to route through a Notification Class the same way an intrinsic object’s would.
| Piece | What it does |
|---|---|
Object_Property_Reference | Names the device, object, and property being watched, which can be on any device on the network |
| The event algorithm | Evaluates the referenced value against Event_Parameters and drives Event_State on the Event Enrollment object, not on the monitored object |
Notification_Class | Names the class that carries the recipient list for this alarm |
Where You Meet It in the Field
A gateway exposing Modbus meter readings as Analog Input objects with no intrinsic-reporting properties is a common case: an Event Enrollment object elsewhere on the network watches the meter’s Present_Value and applies OutOfRange to it, since the gateway itself never will. It is also how a supervisory controller centralizes alarm logic instead of relying on every downstream device to alarm correctly on its own, or how you alarm a value on a legacy device that predates intrinsic reporting altogether.
What Chipkin Provides
Event Enrollment is modeled in the CAS BACnet Stack, and coverage tracks the algorithms the stack implements rather than being fully general. Talk to us about the specific algorithm and remote property you need to watch.
[!NOTE] AE-N-E-B says nothing about which algorithm the Event Enrollment object runs. Confirm the specific algorithm against the algorithm reference before assuming a device claiming AE-N-E-B can watch for the condition you need.
Related Pages
- BACnet Intrinsic Event Notification
- BACnet Intrinsic Event Algorithms
- AE-N-I-B: Alarm and Event-Notification Internal-B
- AE-N-A: Alarm and Event-Notification-A
- AE-ACK-A: AcknowledgeAlarm Initiate
- AE-ACK-B: AcknowledgeAlarm Execute
- BACnet Event Enrollment Object
- BACnet ConfirmedEventNotification Service
- BACnet