The experiences of users and implementers of BACnet have led to many constructive suggestions for improving the original standard, ANSI/ASHRAE 135-1995 and, more recently, to its successors, ANSI/ASHRAE 135-2001 and 135-2004. The files available below are in Adobe Portable Document Format (PDF). Anyone wishing to comment on public review drafts during the listed comment period can get the necessary forms and instructions on the ASHRAE Website.

• Addendum 135-2004a (This addendum is final and was approved for publication by the ASHRAE Board of Directors and by the American National Standards Institute on February 10, 2005.)
   
1. Revise Life Safety Point and Life Safety Zone objects to modify their behavior when placed out of service
 

• Addendum 135-2004b (This addendum is undergoing its fourth (45-day) public review of Independent Substantive Changes from March 21 to May 5, 2008.)
   
1. Add a new Event Log object type
2. Add a new Global Group object type
3. Add a new Trend Log Multiple object type
4. Harmonize the Trend Log object with the new Event Log and Trend Log Multiple objects
5. Define a means for a device to provide a notification that it has restarted
6. Define a means to configure a device to periodically send time synchronization messages
7. Extend the number of character sets supported
8. Enable devices other than alarm recipients to acknowledge alarms
9. Allow MS/TP BACnet Data Expecting Reply frames to be broadcast
10. Revise the Clause 5 state machines to handle slow servers
11. Add new Error Codes and specify usage
12. Add new Reliability enumeration to objects with a Reliability property

Here is the link to the First Public Review Draft of Addendum 135-2004b.
Here is the link to the Second Public Review Draft of Addendum 135-2004b that contains contains only independent substantive changes made to the first public review draft and must be reviewed with that document.
Here is the link to the Third Public Review Draft of Addendum 135-2004b that contains contains only independent substantive changes made to the second public review draft and must be reviewed with that document.


 

• Addendum 135-2004c (This addendum is final and was approved for publication by the ASHRAE Board of Directors September 29, 2006 and by the American National Standards Institute on October 2, 2006.)
   
1. Adding BACnet/WS web services interface

 

• Addendum 135-2004d (This addendum is final and was approved for publication by the ASHRAE Board of Directors June 29, 2006 and by the American National Standards Institute on June 30, 2006.)
   
1. Add a new Structured View object type
2. Allow acknowledgement of unseen TO-OFFNORMAL event notifications
3. Relax the Private Transfer and Text Message BIBB requirements
4. Exclude LIFE_SAFETY and BUFFER_READY notifications from the Alarm Notifications BIBBs
5. Establish the minimum requirements for a BACnet device with an application layer
6. Remove the requirement for the DM-DOB-A BIBB from the B-OWS and B-BC device profiles
7. Relax mandated values for APDU timeouts and retries when configurable, and change default values
8. Fix EventCount handling error in MS/TP Master Node State Machine
9. Permit routers to use a local network number in Device_Address_Binding
10. Identify conditionally writable properties
11. Specify Error returns for the AcknowledgeAlarm service


• Addendum 135-2004e (This addendum is final and was approved for publication by the ASHRAE Board of Directors March 25, 2007 and by the American National Standards Institute on March 26, 2007.)
   
1. Add a new Load Control object type
 
Here is the link to the First Public Review Draft of Addendum 135-2004e.
Here is the link to the Second Public Review Draft of Addendum 135-2004e that contains only independent substantive changes made to the first public review draft and must be reviewed with that document.
 

• Addendum 135-2004f (This addendum is final and was approved for publication by the ASHRAE Board of Directors March 25, 2007 and by the American National Standards Institute on March 26, 2007.)
   
1. Add a new Access Door object type

Here is the link to the First Public Review Draft of Addendum 135-2004f.
Here is the link to the Second Public Review Draft of Addendum 135-2004f.

 

• Addendum 135-2004g (This addendum completed its second public review on April 30, 2007. It is now available for trial implementation testing. Questions on participating in the trials should be directed to the Convener of the NS-WG.)
   
1. Updating BACnet Network Security

Here is the link to the First Public Review Draft of Addendum 135-2004g.
Here is the link to the Second Public Review Draft of Addendum 135-2004g.

 

• Addendum 135-2004h (This addendum is undergoing its second (45-day) public review of Independent Substantive Changes from March 21 to May 5, 2008.)
   
1. Change Device_Busy to Busy and apply to the Command Object type
2. Prevent overflow and underflow in Pulse_Converter object's Count property
3. Add context tags to Clause 21 production BACnetPropertyStates
4. Add new BACnetEngineering Units
5. Define COV notification service Error returns
6. Remove non-support for automatic cancellation of COV subscriptions
7. Add support for the UTF-8 character set
8. Add even and odd day support in scheduling

Here is the link to the First Public Review Draft of Addendum 135-2004h.

 

• Addendum 135-2004i (This addendum is undergoing its (slightly extended due to a clerical mis-posting of the incorrect document on the ASHRAE Website) second (45-day) public review from March 21 to May 9, 2008.)
   
1. Define new Lighting Output object type
2. Add support for breaker-tripped status to Analog and Binary Output objects
3. Add warning-blink support to Binary Output and Binary Value objects

Here is the link to the First Public Review Draft of Addendum 135-2004i.

 

• Addendum 135-2004j (This addendum is undergoing its third (45-day) public review from March 21 to May 5, 2008. The addendum defines physical access control extensions to BACnet. Although access control is part of the building automation system, in many ways it is more complex and has different constraints and requirements than typical HVAC control. In particular, there is a much greater emphasis on the security of the devices and the communications to those devices. Addendum 135-2004g provides a new BACnet security architecture to address these and other concerns.)
   
1. Add a new Access Point object type
2. Add a new Access Zone object type
3. Add a new Access User object type
4. Add a new Access Rights object type
5. Add a new Access Credential object type
6. Add a new Access Authentication Factor Input object type
7. Add a new Access ACCESS_EVENT event algorithm
8. Add a new Annex X BACnet encoding rules for authentication factor values

Here is the link to the First Public Review Draft of Addendum 135-2004j.
Here is the link to the Second Public Review Draft of Addendum 135-2004j.



• Addendum 135-2004k (Due to the posting of an incorrect version of the addendum, the first (45-day) public review dates have been changed (extended) so that the public review will now run from October 26 to December 10, 2007.) Addendum 135-2004k adds support for one "Character Encoding Form" at a time, needed for interoperability. Also incorporates the Japanese Industrial Standard Committee's change from "JIS C 6226" to "JIS X 0208."
   
1. Add support for one Character Encoding Form at a time
 

• Addendum 135-2004l (This addendum is undergoing its first (45-day) public review from September 14 to October 29, 2007.) Addendum 135-2004l adds new operator workstation profiles and BIBBs.
   
1. Add new workstation BIBBs and profiles
 

• Addendum 135-2004m (This addendum is undergoing its second (45-day) public review of Independent Substantive Changes from March 21 to May 5, 2008.) Addendum 135-2004m contains 12 independent changes to the BACnet standard, including: resolving Foreign Device registration period ambiguities, clarifying the GetEventEnrollment service's Priority Filter parameter, adding requirements to Alarm and Event BIBBs, and defining "object."
   
1. Resolve Foreign Device registration grace period and remaining time ambiguities
2. Improve Clause 5 FillWindow segment timeout constraints
3. Clarify the Priority Filter parameter in the GetEventEnrollment service request
4. Allow alarms to be re-acknowledged successfully
5. Add requirements to Alarm and Event BIBBs
6. Remove B-BC requirements for BIBBs without use cases
7. Clarify that a device may support only the ReinitializeDevice restart choices
8. Clarify DeviceCommunicationsControl and ReinitializeDevice interactions
9. Define "object"
10. Add a Deadband property to the Loop object
11. Correct the TO-FAULT conditions in the Life Safety objects' Reliability properties
12. Clarify the Trend Log's acquisition of Status_Flags

Here is the link to the First Public Review Draft of Addendum 135-2004m.

 

• Addendum 135-2004n (This addendum is undergoing its second (45-day) public review from March 21 to May 5, 2008.) Addendum 135-2004n adds support for devices with long Backup and Restore preparation times.
   
1. Add support for long Backup and Restore preparation times

Here is the link to the First Public Review Draft of Addendum 135-2004n.

 

• Addendum 135-2004o (This addendum is undergoing its first (45-day) public review from September 14 to October 29, 2007.) Addendum 135-2004o accommodates remote operator access via Annex J BACnet/IP through NAT firewalls.
   
1. Accommodate remote operator access and NAT in Annex J BACnet/IP
 

• Addendum 135-2004q (This addendum is undergoing its first (45-day) public review from March 21 to May 5, 2008.)
   
1. Allow unicast I-Ams
2. Define virtual addressing for data links with MAC addresses longer than 6 octets
3. Define the use of ZigBee as a BACnet data link layer
 

• Addendum 135-2004r (This addendum is undergoing its first (45-day) public review from March 21 to May 5, 2008.)
   
1. Clarify transitions in FLOATING_LIMIT and OUT_OF_RANGE events
2. Clarify router action when a network is marked as temporarily unreachable
3. Clarify the destination MAC used when replying to a broadcast DER frame
4. Clarify the handling of write priorities greater than 16
5. Clarify LogDatum presentation
 

• Addendum 135-2001a
  1. Add Partial Day Scheduling to the Schedule object
  2. Enable reporting of proprietary events by the Event Enrollment object
  3. Allow detailed error reporting when all ReadPropertyMultiple accesses fail
  4. Remove the Recipient property from the Event Enrollment object
  5. Add the capability to issue I-Am responses on behalf of MS/TP slave devices
  6. Add a new silenced mode to the DeviceCommunicationControl service
  7. Add 21 new engineering units
  8. Specify the behavior of a BACnetArray when its size is changed
  9. Clarify the behavior of a BACnet router when it receives an unknown network message type
   
  
• Addendum 135-2001b
  1. Remove UTC timestamps from Trend Logs and guarantee Trend Log record ordering
   
  
• Addendum 135-2001c
  1. Allow Life Safety objects to advertise supported mode
  2. Add Unsilence Options to the LifeSafetyOperation Service
  3. Specify the relationship between the Event_Type and Event_Parameter properties
  4. Add a new Accumulator Object Type
  5. Add a new Pulse Converter Object Type
  6. Standardize event notification priorities
  7. Define Abort reason when insufficient segments are available
  8. Add new Error Codes and specify usage
   
  
• Addendum 135-2001d
  1. Add clauses describing BACnet-EIB/KNX mapping

• Addendum 135-1995a
  1. Add Annex J - BACnet/IP and supporting definitions
   
  
• Addendum 135-1995b
  1. Inconsistencies are eliminated in the definitions of the Analog and Binary Value object types
  2. Any device that receives and executes UnconfirmedEventNotification service requests must support programmable process identifiers
  3. Modify each event-generating object type to contain the last timestamp for each acknowledgeable transition
  4. Modify the Notification Class object by requiring that the 'Notification Class' property be equivalent to the instance number of the Notification Class object
  5. Modify the Event Notification services to make the 'To State' parameter mandatory for notifications of type ACK_NOTIFICATION
  6. A new BACnetDeviceObjectPropertyReference production is added and its use in the Event Enrollment and Schedule object types is specified
  7. Add a Multi-state Value object type
  8. Add an Averaging object type
  9. Change all 'Process Identifier' properties and parameters to Unsigned32
  10. Change the Multi-state Input object type to correct flaws related to fault detection and reporting and achieve consistency with the proposed Multi-state Value object type
  11. Add a Protocol_Revision property to the Device object type
  12. The File object type is changed to allow truncation and partial deletion operations
  13. A new ReadRange service is added to permit reading a range of data items from a property whose datatype is a list or array of lists
  14. A new UTCTimeSynchronization service is introduced and related changes are made to properties in the Device object type
  15. Add a Trend Log object type
  16. The UnconfirmedCOVNotification service is extended to allow notifications without prior subscription as a means of distributing globally important data to a potentially large number of recipients
  17. Add eight new BACnet engineering units
   
  
• Addendum 135-1995c
  1. Add a new Life Safety Point object type that represents the characteristics of initiating and indicating devices in the fire, life safety, and security applications
  2. Add a new Life Safety Zone object type that represents the characteristics associated with an arbitrary group of BACnet Life Safety Point and Life Safety Zone objects
  3. Add functionality to the existing BACnet alarm and event features needed to support the Life Safety Point and Life Safety Zone object types
  4. Add a new LifeSafetyOperation service that provides silence and reset capabilities needed for life safety systems
  5. Add a new subclause to 19 to describe the use of existing BACnet services to provide backup and restore capability
  6. Define a new service, SubscribeCOVProperty, to allow COV notifications for arbitrary properties of an object with subscriber-specified COV increments
  7. Add Vendor ID to proprietary MS/TP frames
  8. Add a new service, GetEventInformation, that provides enough information to acknowledge alarms
   
  
• Addendum 135-1995d
  1. Replace Clause 22 with a new clause entitled "Conformance and Interoperability"
  2. Update Annex A, "Protocol Implementation Conformance Statement"
  3. Add a new Annex K entitled "BACnet Interoperability Building Blocks (BIBBs)"
  4. Add a new Annex L entitled "Descriptions and Profiles of Standardized BACnet Devices"
   
  
• Addendum 135-1995e
  1. Define the PTP connection status when the half-router can and cannot re-establish the connection
  2. Add Object Profiles and Extensions
  3. Add the capability for devices to advertise the maximum number of segments of a segmented APDU that they can receive

The need to define a set of procedures for the testing of BACnet implementations has led to the drafting of a companion standard, ANSI/ASHRAE 135.1-2003, Method of Test for Conformance to BACnet. The companion standard to ANSI/ASHRAE Standard 135 (BACnet) contains detailed tests for every feature of the BACnet protocol and provides the basis for testing and listing programs that have been established by the BACnet Manufacturers Association. The document was approved for publication by the ASHRAE Board of Directors on July 3, 2003, and by ANSI on August 6, 2003. In December 2004 Standard 135.1 was approved by ISO and CEN member countries as a Draft International Standard (ISO/DIS 16484-6). Eighteen countries voted in favor of the DIS, none against. Because this standard is subject to the Vienna Agreement between CEN and ISO (an agreement intended to reduce redundant development of standards in which both CEN and ISO countries share an interest), a further Final Draft International Standard (FDIS) vote will be taken in the near future.

• Addendum 135.1-2003a (This addendum was approved for publication on January 26, 2006 by the ASHRAE Board of Directors.)
   
1. Add Partial Day Scheduling to the Schedule object
2. Enable reporting of proprietary events by the Event Enrollment object
3. Allow detailed error reporting when all ReadPropertyMultiple accesses fail
4. Remove the Recipient property from the Event Enrollment object
5. MS/TP slave proxy tests
6. Add a new silenced mode to the DeviceCommunicationControl service
7. Addition of tests for Data Sharing BIBBs
8. Specify the behavior of a BACnetARRAY when its size is changed
9. Clarifying the behavior of a BACnet router when it receives an unknown network message type
10. Testing unsupported service request execution
11. Reading entire arrays
12. Update negative tests
 

• Addendum 135.1-2003b (This addendum is undergoing its first (45-day) public review from March 16 to April 30, 2007.)
   
1. Omit certain tests when Averaging and Command properties are fixed or not present
2. Accommodate Group objects whose members list is not changeable
3. Revise Alarm Acknowledgement tests
4. Add new Alarm Acknowledgement "offnormal" tests
5. Label conditionally-writable properties in the EPICS
6. Add new object types
 

• Addendum 135.1-2003c (This addendum is undergoing its first (45-day) public review from March 16 to April 30, 2007.)
   
1. Update references to refer to 135-2004
2. Add new object types from 135-2004
3. Omit certain tests based on Protocol_Revision
4. Exception schedule priority requirements
5. Minor corrections