{"id":84,"date":"2022-05-13T13:52:02","date_gmt":"2022-05-13T13:52:02","guid":{"rendered":"https:\/\/thebacnetinstitute.org\/history\/"},"modified":"2022-08-02T12:18:56","modified_gmt":"2022-08-02T12:18:56","slug":"history","status":"publish","type":"page","link":"https:\/\/thebacnetinstitute.org\/history\/","title":{"rendered":"History"},"content":{"rendered":"\n
BACnet (Building Automation and Con\u00adtrol Network)<\/strong> was created in response to the realization that the building industry needed a cost-effective way to integrate different systems from diverse vendors into one coherent automation and control system. This required a level of data communications interoperability that did not exist, so in June of 1987, members of the industry came together at the ASHRAE Annual Meeting in Nashville, Tennessee to talk about a solution. This was the first meeting of what eventually became the BACnet Committee<\/a>.<\/p>\n\n\n\n Developing a detailed, comprehensive standard was a large technical task, but in 1995, ANSI\/ASHRAE Standard 135 was published and BACnet was officially launched. The next year ASHRAE Standing Standard Project Committee 135 (SSPC 135) was formed to interpret, maintain, and extend the standard. In 2003, BACnet achieved the status of an International Organization for Standardization standard (ISO 16484-5). That same year, BACnet’s companion standard, ANSI\/ASHRAE Standard 135.1, Method of Test for Conformance to BACnet<\/em>, was published in the United States and soon joined the BACnet protocol itself internationally as ISO 16484-6.<\/p>\n\n\n\n