BACnet B-LSC Life Safety Controller Profile

B-LSC is the BACnet Life Safety Controller profile (Annex L): what it is, where it's used, and the services it requires.

What B-LSC 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-LSC (BACnet Life Safety Controller) is defined in Annex L of ANSI/ASHRAE 135-2024 (clause L.5.2) as a controller for life-safety systems: it generates life-safety event notifications and processes the silence and reset operations an operator performs on its life-safety points.

The checklist items are BACnet Interoperability Building Blocks (BIBBs), each a named unit of capability such as “generate life-safety notifications” (AE-LS-B). B-LSC is a B-role device: it answers requests and originates the alarms a supervisory system displays. A device documents its 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-LSC fits a controller managing fire and life-safety points that must annunciate to a building system.

  • Fire and smoke-control controllers. A device monitoring life-safety points and reporting alarm, supervisory, and trouble conditions to the head end (the central BMS server).
  • Life-safety annunciation. A controller whose events drive a graphic or annunciator, and which accepts operator silence and reset commands.
  • Integrated safety points. Life-safety inputs a building controller must surface as BACnet life-safety objects rather than plain binary points.

Required Services

The table below is the exhaustive service set required by the B-LSC 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 areaServiceRequired by BIBBInitiatesExecutes
Data sharingReadPropertyDS-RP-B-Yes
Data sharingReadPropertyMultipleDS-RPM-B-Yes
Data sharingWritePropertyDS-WP-B-Yes
Data sharingWritePropertyMultipleDS-WPM-B-Yes
Data sharingSubscribeCOVDS-COV-B-Yes
Data sharingConfirmedCOVNotificationDS-COV-BYes-
Data sharingUnconfirmedCOVNotificationDS-COV-BYes-
Alarm and event managementLifeSafetyOperationAE-LS-B-Yes
Alarm and event managementConfirmedEventNotificationAE-LS-BYes-
Alarm and event managementUnconfirmedEventNotificationAE-LS-BYes-
Alarm and event managementAcknowledgeAlarmAE-ACK-B-Yes
Alarm and event managementGetEventInformationAE-INFO-B-Yes
Device and network managementWho-IsDM-DDB-A, DM-DDB-BYesYes
Device and network managementI-AmDM-DDB-A, DM-DDB-BYesYes
Device and network managementWho-HasDM-DOB-B-Yes
Device and network managementI-HaveDM-DOB-BYes-
Device and network managementDeviceCommunicationControlDM-DCC-B-Yes
Device and network managementTimeSynchronization ¹DM-TS-B-Yes
Device and network managementUTCTimeSynchronization ¹DM-UTC-B-Yes
Device and network managementReinitializeDeviceDM-RD-B-Yes

The life-safety rows depend on hosted objects. The AE-LS-B requirement means the device hosts Life Safety Point and Life Safety Zone objects that originate its notifications and receive the silence and reset operations.

¹ The profile requires one of the two time-synchronization services, not both. (Protocol_Revision is a readable property of the device’s Device object.)

ProfileHow it differs from B-LSC
B-ALSCAdvanced Life Safety Controller: adds internal scheduling and an Event Log
B-BCBuilding Controller: the general controller, without the life-safety event model
B-LSAPLife Safety Annunciator Panel: the operator-side profile that displays these events

What Chipkin Provides

The CAS BACnet Stack implements the BIBB set the B-LSC profile requires, including the life-safety event model and the silence and reset operations. Talk to us about building or integrating a B-LSC device on the stack.