BACnet Access Point Object

The BACnet Access Point object (Clause 12.31) authenticates and authorizes a credential at a door or gate, with its ACCESS_EVENT reporting and properties.

What the Access Point Object Is

The Access Point object, defined in Clause 12.31 of ANSI/ASHRAE 135-2024, is how a BACnet device represents the authentication and authorization process at an access-controlled point such as a door, gate, or turnstile. It is directional: it controls access in one direction only, so a door controlled in both directions is modeled by two Access Point objects.

Authentication verifies who is presenting a credential (card, PIN, biometric, or a multi-factor combination). Authorization then decides whether that credential may enter, checking authorization mode, occupancy limits, external verification, and threat level. When both pass, the Access Point commands its Access Door to unlock at a configured priority. Every request produces one or more access events; these are stateless (NORMAL to NORMAL transitions only) and, for intrinsic reporting, use the ACCESS_EVENT algorithm for both alarm events and transaction events, delivered through the event notification services.

Where You’ll See It

  • Card readers and turnstiles. Each controlled direction through a reader-guarded opening is one Access Point object that consumes factors from a Credential Data Input and grants or denies entry.
  • Access controllers. Panels carrying the b-acc and b-aacc access-control profiles host Access Point objects that arbitrate authentication and drive Access Door objects.
  • Anti-passback and occupancy. An Access Point references the Access Zone it leads into and out of, so entry and exit update zone occupancy and enforce passback rules.

Required Properties

Clause 12.31 requires every Access Point object to provide these properties. Datatypes are the spec’s names: Unsigned is an integer, BOOLEAN a true/false flag, and the BACnet-prefixed types are structured values defined by the standard. The Access Point has no Present_Value; the authentication and authorization result is reported through the access-event properties.

PropertyDatatypeWhat it holds
Object_IdentifierBACnetObjectIdentifierThe object’s type and instance number, unique within the device
Object_NameCharacterStringThe human-readable point name, unique within the device
Object_TypeBACnetObjectTypeAlways access-point for this object
Status_FlagsBACnetStatusFlagsFour health flags: in-alarm, fault, overridden, out-of-service
Event_StateBACnetEventStateThe object’s current event state (normal, off-normal, or fault)
ReliabilityBACnetReliabilityNames the reason whenever the fault flag is set
Out_Of_ServiceBOOLEANWhen true, the object stops performing authentication and authorization
Authentication_StatusBACnetAuthenticationStatusWhere the object is in the authentication sequence
Active_Authentication_PolicyUnsignedWhich configured authentication policy is currently in effect
Number_Of_Authentication_PoliciesUnsignedHow many authentication policies this point defines
Authorization_ModeBACnetAuthorizationModeHow authorization is being enforced right now
Access_EventBACnetAccessEventThe most recent access event generated at this point
Access_Event_TagUnsignedGroups the events belonging to one access transaction
Access_Event_TimeBACnetTimeStampWhen the most recent access event occurred
Access_Event_CredentialBACnetDeviceObjectReferenceThe credential involved in the most recent access event
Access_DoorsBACnetARRAY[N] of BACnetDeviceObjectReferenceThe Access Door objects this point commands
Priority_For_WritingUnsignedThe priority at which this point commands its doors
Property_ListBACnetARRAY[N] of BACnetPropertyIdentifierThe list of properties this instance actually implements

Optional Properties

The properties integrators meet most are the authentication-policy group (Authentication_Policy_List, Authentication_Policy_Names), the lockout and failed-attempt controls, and the zone references (Zone_To, Zone_From) that tie the point to occupancy tracking. The intrinsic-reporting group generally appears or is absent as a set. Audit_Level and Auditable_Operations are the audit-logging controls added in 135-2024.

PropertyDatatypeGroup
DescriptionCharacterStringGeneral
Authentication_Policy_ListBACnetARRAY[N] of BACnetAuthenticationPolicyAccess model
Authentication_Policy_NamesBACnetARRAY[N] of CharacterStringAccess model
Verification_TimeUnsignedAccess model
LockoutBOOLEANAccess model
Lockout_Relinquish_TimeUnsignedAccess model
Failed_AttemptsUnsignedAccess model
Failed_Attempt_EventsBACnetLIST of BACnetAccessEventAccess model
Max_Failed_AttemptsUnsignedAccess model
Failed_Attempts_TimeUnsignedAccess model
Threat_LevelBACnetAccessThreatLevelAccess model
Occupancy_Upper_Limit_EnforcedBOOLEANAccess model
Occupancy_Lower_Limit_EnforcedBOOLEANAccess model
Occupancy_Count_AdjustBOOLEANAccess model
Accompaniment_TimeUnsignedAccess model
Access_Event_Authentication_FactorBACnetAuthenticationFactorAccess model
Muster_PointBOOLEANAccess model
Zone_ToBACnetDeviceObjectReferenceAccess model
Zone_FromBACnetDeviceObjectReferenceAccess model
Notification_ClassUnsignedIntrinsic reporting
Transaction_Notification_ClassUnsignedIntrinsic reporting
Access_Alarm_EventsBACnetLIST of BACnetAccessEventIntrinsic reporting
Access_Transaction_EventsBACnetLIST of BACnetAccessEventIntrinsic reporting
Event_EnableBACnetEventTransitionBitsIntrinsic reporting
Acked_TransitionsBACnetEventTransitionBitsIntrinsic reporting
Notify_TypeBACnetNotifyTypeIntrinsic reporting
Event_Time_StampsBACnetARRAY[3] of BACnetTimeStampIntrinsic reporting
Event_Message_TextsBACnetARRAY[3] of CharacterStringIntrinsic reporting
Event_Message_Texts_ConfigBACnetARRAY[3] of CharacterStringIntrinsic reporting
Event_Detection_EnableBOOLEANIntrinsic reporting
Event_Algorithm_Inhibit_RefBACnetObjectPropertyReferenceIntrinsic reporting
Event_Algorithm_InhibitBOOLEANIntrinsic reporting
Reliability_Evaluation_InhibitBOOLEANFault detection
Audit_LevelBACnetAuditLevelAuditing
Auditable_OperationsBACnetAuditOperationFlagsAuditing
TagsBACnetARRAY[N] of BACnetNameValueTagging and profile
Profile_LocationCharacterStringTagging and profile
Profile_NameCharacterStringTagging and profile
  • Access Door: the physical door this point commands to unlock on a successful grant.
  • Credential Data Input: the reader that supplies the authentication factors this point consumes.
  • Access Zone: the secured area whose entry and exit points are Access Point objects.
  • Access Credential: the credential whose rights this point evaluates during authorization.

What Chipkin Provides

The Access Point object, including its authentication-policy model and ACCESS_EVENT intrinsic reporting, is a first-class object type in the CAS BACnet Stack. Talk to us about modeling your device’s points.