BACnet Credential Data Input Object

The BACnet Credential Data Input object (Clause 12.36) is a card, PIN, or biometric reader that captures authentication factors, with property tables.

What the Credential Data Input Object Is

The Credential Data Input object, defined in Clause 12.36 of ANSI/ASHRAE 135-2024, is how a BACnet device represents a physical reader that captures authentication factors: a card reader, keypad, or biometric reader. An authentication factor is the unique digital identifier a credential presents, and Present_Value holds the most recently read factor.

A reader that supports several factor formats that are not interchangeable is modeled as several Credential Data Input objects, one per function (for example, a combined card-and-biometric reader). A reader whose formats are interchangeable, such as one that reads multiple Wiegand formats, is modeled as a single object. Credential Data Input objects may optionally support intrinsic reporting, but only to report fault conditions: they perform the first stage of reliability evaluation and apply no off-normal event algorithm. The Access Point object consumes the factors this object captures.

Where You’ll See It

  • Readers at a door. Each card reader, keypad, or biometric reader wired to an access controller is a Credential Data Input object.
  • Multi-technology readers. A reader that captures both a card and a fingerprint is two Credential Data Input objects, one per factor.
  • Fault reporting. A tamper or communications fault on the reader surfaces through Reliability and the fault-reporting properties.

Required Properties

Clause 12.36 requires every Credential Data Input 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.

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 credential-data-input for this object
Present_ValueBACnetAuthenticationFactorThe most recently read authentication factor
Status_FlagsBACnetStatusFlagsFour health flags: in-alarm, fault, overridden, out-of-service
ReliabilityBACnetReliabilityNames the reason whenever the fault flag is set
Out_Of_ServiceBOOLEANWhen true, Present_Value is decoupled from the physical reader for testing
Supported_FormatsBACnetARRAY[N] of BACnetAuthenticationFactorFormatThe authentication-factor formats this reader can capture
Update_TimeBACnetTimeStampWhen Present_Value was last updated
Property_ListBACnetARRAY[N] of BACnetPropertyIdentifierThe list of properties this instance actually implements

Optional Properties

The properties integrators meet most are Supported_Format_Classes and the fault-reporting group. The intrinsic-reporting group here supports fault conditions only, since this object applies no off-normal event algorithm. Audit_Level and Auditable_Operations are the audit-logging controls added in 135-2024.

PropertyDatatypeGroup
DescriptionCharacterStringGeneral
Supported_Format_ClassesBACnetARRAY[N] of UnsignedAccess model
Event_Detection_EnableBOOLEANIntrinsic reporting
Notification_ClassUnsignedIntrinsic reporting
Event_EnableBACnetEventTransitionBitsIntrinsic reporting
Event_StateBACnetEventStateIntrinsic 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
Reliability_Evaluation_InhibitBOOLEANFault detection
Audit_LevelBACnetAuditLevelAuditing
Auditable_OperationsBACnetAuditOperationFlagsAuditing
TagsBACnetARRAY[N] of BACnetNameValueTagging and profile
Profile_LocationCharacterStringTagging and profile
Profile_NameCharacterStringTagging and profile
  • Access Point: the object that consumes the factors this reader captures and performs authentication.
  • Access Credential: the credential whose stored factors are matched against a captured factor.
  • Access Door: the door the access point unlocks after a successful read.

What Chipkin Provides

The Credential Data Input object, including its authentication-factor capture and format model, is a first-class object type in the CAS BACnet Stack. Talk to us about modeling your device’s points.