BACnet Life Safety Point Object

The BACnet Life Safety Point object (Clause 12.15) models a fire or life-safety device by mode and state, with its CHANGE_OF_LIFE_SAFETY alarm.

What the Life Safety Point Object Is

The Life Safety Point object, defined in Clause 12.15 of ANSI/ASHRAE 135-2024, is how a BACnet device represents an initiating or indicating device in a fire, life-safety, or security application: a smoke detector, pull station, siren, or supervised output. Its condition is described by two things together, a mode and a state. Present_Value is the current life-safety state, and Mode sets the operating mode that governs how the object’s internal logic evaluates that state.

Unlike an analog or binary point, a Life Safety Point carries life-safety-specific behavior: it can be silenced, it reports the operation expected of an operator through Operation_Expected, and it responds to the LifeSafetyOperation service for silence and reset. Life Safety Point objects that support intrinsic reporting apply the CHANGE_OF_LIFE_SAFETY event algorithm and deliver alarms through the event notification services.

Where You’ll See It

  • Fire devices. Automatic fire detectors, pull stations, sirens, and supervised printers on a fire panel each map to a Life Safety Point object.
  • Life-safety controllers. Devices carrying the B-LSC Life Safety Controller profile host Life Safety Point objects and roll them up into Life Safety Zone objects.
  • Silence and reset. An operator silences a sounder or resets a detector through the LifeSafetyOperation service, and Silenced reports the result.

Required Properties

Clause 12.15 requires every Life Safety 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.

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 life-safety-point for this object
Present_ValueBACnetLifeSafetyStateThe current life-safety state (quiet, alarm, fault, and similar). Read-only
Tracking_ValueBACnetLifeSafetyStateThe state the object is tracking toward, used during transitions
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, Present_Value is decoupled from the physical device for testing
ModeBACnetLifeSafetyModeThe operating mode that governs the object’s internal logic. Writable
Accepted_ModesBACnetLIST of BACnetLifeSafetyModeThe modes this object will accept
SilencedBACnetSilencedStateWhether and how the object has been silenced
Operation_ExpectedBACnetLifeSafetyOperationThe operator action the object is expecting next
Property_ListBACnetARRAY[N] of BACnetPropertyIdentifierThe list of properties this instance actually implements

Optional Properties

The properties integrators meet most are the life-safety group (Life_Safety_Alarm_Values, Alarm_Values, Fault_Values, Maintenance_Required) and the direct-reading fields (Direct_Reading, Units) for detectors that report an analog level. 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
Device_TypeCharacterStringGeneral
Life_Safety_Alarm_ValuesBACnetLIST of BACnetLifeSafetyStateIntrinsic reporting
Alarm_ValuesBACnetLIST of BACnetLifeSafetyStateIntrinsic reporting
Fault_ValuesBACnetLIST of BACnetLifeSafetyStateFault detection
Time_DelayUnsignedIntrinsic reporting
Notification_ClassUnsignedIntrinsic 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
Time_Delay_NormalUnsignedIntrinsic reporting
Reliability_Evaluation_InhibitBOOLEANFault detection
Maintenance_RequiredBACnetMaintenanceLife safety
SettingUnsignedLife safety
Direct_ReadingREALLife safety
UnitsBACnetEngineeringUnitsLife safety
Member_OfBACnetLIST of BACnetDeviceObjectReferenceLife safety
Floor_NumberUnsigned8Life safety
Value_SourceBACnetValueSourceCommanding
Audit_LevelBACnetAuditLevelAuditing
Auditable_OperationsBACnetAuditOperationFlagsAuditing
TagsBACnetARRAY[N] of BACnetNameValueTagging and profile
Profile_LocationCharacterStringTagging and profile
Profile_NameCharacterStringTagging and profile
  • Life Safety Zone: the object that groups Life Safety Points and other zones into a single monitored area.
  • Binary Input: the general-purpose two-state input, when a contact needs no life-safety mode and state model.

What Chipkin Provides

The Life Safety Point object, including its mode-and-state model and CHANGE_OF_LIFE_SAFETY intrinsic reporting, is a first-class object type in the CAS BACnet Stack. Talk to us about modeling your device’s points.