What B-ACSD 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-ACSD (BACnet Access Control Security Display) is a security operator display, defined in Annex L of ANSI/ASHRAE 135-2024 (clause L.3.3). It monitors and controls access-control devices, supports a minimal level of configuration such as setting threat levels, and receives and handles access events, targeted at security personnel who watch and operate the physical access-control system.
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-ACSD is an operator-side (client) profile: it initiates reads and writes against other devices, and it receives access-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-ACSD is the security-monitoring display rather than an administration workstation.
- Guard-station displays. A console where security staff watch doors, acknowledge access events, and set threat levels.
- Lobby security consoles. A display paired with a head end (the central BMS server) that presents access-object data and event logs.
- Monitoring panels. A station that shows access-control status and handles events without enrolling users or configuring the object set.
Required Services
The table below is the service set required by the B-ACSD 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-ACV-A | Yes | Yes |
| Data sharing | ReadPropertyMultiple | DS-RPM-A | Yes | - |
| Data sharing | WriteProperty | DS-WP-A, DS-ACM-A | Yes | - |
| Data sharing | WritePropertyMultiple | DS-WPM-A | Yes | - |
| Alarm and event management | ConfirmedEventNotification | AE-N-A, AE-AC-A, AE-ACAVN-A | - | Yes |
| Alarm and event management | UnconfirmedEventNotification | AE-N-A, AE-AC-A, AE-ACAVN-A | - | Yes |
| Alarm and event management | AcknowledgeAlarm | AE-ACK-A, AE-AC-A | Yes | - |
| Alarm and event management | GetEventInformation | AE-AS-A | Yes | - |
| Alarm and event management | GetAlarmSummary | AE-AS-A | Yes | - |
| Alarm and event management | ReadRange (event-log view) | AE-ELV-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 | - |
| Device and network management | TimeSynchronization | DM-MTS-A | Yes | - |
| Device and network management | UTCTimeSynchronization | DM-MTS-A | Yes | - |
The view and modify BIBBs add no wire service beyond the rows above. DS-ACV-A (Access Control View) and DS-ACM-A (Access Control Modify) read and write access-object properties; AE-ACVM-A adjusts access-event parameters; SCHED-VM-A views and modifies schedules and calendars. Each is carried by the ReadProperty and WriteProperty rows above. B-ACSD has no object-creation, backup-and-restore, or audit-reporting requirement, which is what separates it from the access-control workstations.
Related Profiles
| Profile | How it differs from B-ACSD |
|---|---|
| B-ACWS | Access Control Workstation: a step up. Adds user enrollment, object creation, and backup and restore |
| B-AACWS | Advanced Access Control Workstation: the full interface. Adds site-object configuration and audit reporting |
| B-ACC | Access Control Controller: the device side. It generates the access events a B-ACSD displays and handles |
What Chipkin Provides
B-ACSD 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-ACSD operator interface.