What B-LSAP Is
A BACnet device profile is a standardized capability level: a checklist of things a device must be able to do before it can wear the label. B-LSAP (BACnet Life Safety Annunciator Panel) is a life-safety operator interface for the indication of life-safety events and status, defined in Annex L of ANSI/ASHRAE 135-2024 (clause L.2.3). It is used for monitoring and event handling of a life-safety system, targeted at the daily operator who needs to see status and handle events.
The checklist items are BACnet Interoperability Building Blocks (BIBBs), each a named unit of capability such as “can send a read request” (DS-RP-A). B-LSAP is an operator-side (client) profile: it initiates reads and silence and reset operations against other devices, and it receives event notifications rather than generating them. A device documents its profile claim in its PICS (Protocol Implementation Conformance Statement); to verify a claim, ask for the PICS and check the profile line.
Where It’s Used
B-LSAP is the fixed indicator panel rather than a full workstation.
- Life-safety annunciator panels. A wall panel in a lobby or control room that lights up and displays Life Safety Point and Life Safety Zone status and lets an operator acknowledge, silence, and reset events.
- Guard-station indicators. A simple panel paired with a head end (the central BMS server) that shows life-safety events without configuration capability.
- Remote indication points. A display that presents life-safety object data and handles event acknowledgment at a satellite location.
Required Services
The table below is the service set required by the B-LSAP BIBBs. Initiates means the device sends the request or notification; Executes means the device receives and acts on it (responding, for confirmed services). BIBB codes encode the same split: a -A BIBB is the initiating side, a -B BIBB the executing side. A - means the profile does not require that direction; a device may still support it.
| Capability area | Service | Required by BIBB | Initiates | Executes |
|---|---|---|---|---|
| Data sharing | ReadProperty | DS-RP-A, DS-RP-B, DS-LSV-A | Yes | Yes |
| Data sharing | WriteProperty | DS-WP-A | Yes | - |
| Alarm and event management | ConfirmedEventNotification | AE-N-A, AE-LSVN-A | - | Yes |
| Alarm and event management | UnconfirmedEventNotification | AE-N-A, AE-LSVN-A | - | Yes |
| Alarm and event management | LifeSafetyOperation | AE-LS-A | Yes | - |
| Alarm and event management | AcknowledgeAlarm | AE-ACK-A, AE-LS-A | Yes | - |
| Device and network management | Who-Is | DM-DDB-A, DM-DDB-B | Yes | Yes |
| Device and network management | I-Am | DM-DDB-A, DM-DDB-B | Yes | Yes |
| Device and network management | Who-Has | DM-DOB-B | - | Yes |
| Device and network management | I-Have | DM-DOB-B | Yes | - |
The DS-LSV-A (Life Safety View) BIBB presents life-safety object values and folds onto the ReadProperty row, so the profile adds no new wire service beyond it. B-LSAP has no scheduling, trending, alarm-summarization, or configuration requirement, which is what separates it from the life-safety workstations.
Related Profiles
| Profile | How it differs from B-LSAP |
|---|---|
| B-LSWS | Life Safety Workstation: a step up. Adds scheduling, trending, alarm summarization, and backup and restore |
| B-ALSWS | Advanced Life Safety Workstation: the full interface. Adds object creation, event-log modification, and audit reporting |
| B-LSC | Life Safety Controller: the device side. It generates the notifications a B-LSAP annunciates and executes the silence and reset operations it sends |
What Chipkin Provides
B-LSAP is an operator-side profile: its initiating and notification-receiving behavior is implemented in Chipkin’s BACnet test tooling rather than the shipping device stack, which targets the server-side profiles. Talk to us about building or integrating a B-LSAP operator interface.