BACnet affords facility owners and managers maximum flexibility and cost-effectiveness by allowing control products made by different manufacturers to be integrated into a single, uniform system.
BACnet is designed to allow HVAC/R, lighting, life safety, access, security, power, vertical transportation and other building system control devices to interoperate.
The BACnet protocol was developed to be a consensus standard, under full public scrutiny. Today, as a national standard, it cannot be significantly changed without public review and comment.
BACnet has since also become firmly established on the international stage, where it is a European standard (CEN). It was announced at Ashrae 2003 that BACnet has become an ISO standard (ISO 16484-5).
The motivation for the BACnet standard was the widespread desire of building owners and operators for “interoperability” in building systems. Interoperability is the ability to integrate equipment associated with different building systems and/or buildings into a coherent automation and control system, regardless of manufacturer.
To accomplish this, the ASHRAE Standard Project Committee (SPC 135) solicited and received input from dozens of interested firms and individuals. The SPC reviewed all relevant national and international data communications standards and spent countless hours in debate and discussion on each element of the protocol.
After 9 years of development, the ASHRAE Standards Committee released BACnet to the industry in 1995. BACnet became a national standard upon approval by the American Standards Institute in (ANSI) shortly thereafter in December 1995.
Once the standard was published SPC 135 was disbanded and ASHRAE Standing Standards Project Committee (SSPC 135) was created in its place. SSPC 135 continues to update the BACnet standard, and its companion testing standard, to meet the evolving needs of the Building Automation industry.
Delta Controls has been raising the standard for building comfort while reducing operating expenses in commercial, retail & government buildings; manufacturing, transportation, sports and other entertainment facilities; and schools, universities and hotels for 25 years.
The extensive building automation expertise accumulated during this time allowed Delta to objectively evaluate various open protocols during the mid-90’s period, including BACnet and LON. Delta ultimately chose BACnet as the standard to be incorporated in all future products, on the strength of BACnet's universal design, functional scope and scalability, backed by it's true hardware independence with respect to handling data processing and communication.
Delta’s building automation system includes HVAC/R, Card Access and Lighting control, the world's first fully integrated BACnet system, featuring full interoperability and internet accessibility with the industry’s most extensive implementation of BACnet, native to all products through all levels of the system.
Various Delta BACnet controllers have successfully passed BTL testing and are listed on the BACnet International website under the classification of application specific controllers (the highest level of classification that BTL has tested to date). Powered by Delta’s BACnet “engine” module common to nearly all Delta controllers, Delta's advanced application controllers share the same BACnet operating software sub-set that has already been tested and approved by BTL.
Through active participation in the ASHRAE Standing Standard Project Committee 135, BACnet International and various international BACnet interest groups, Delta continues to assume an important leadership role in the ongoing development of the BACnet standard and its certification programs, as well as promoting within the industry.
BACnet International is a non-profit organization comprising manufacturers of BACnet products from various industries as well as individuals involved in systems design and implementation.
BACnet International’s mission is to encourage the successful use of BACnet in building automation systems through interoperability testing, educational programs, promotional activities and coordination with various BACnet organizations.
As one of the founding members of BACnet International, Delta has fulfilled a leadership role in BACnet International since its inception. Delta actively participates in all aspects of BACnet International and maintains a representative on the BACnet International board of directors.
The
BACnet Testing Laboratory (BTL) was formed by BACnet International to improve BACnet interoperability through extensive BACnet compliance testing at the BTL authorized test laboratory as part of a product conformance certification and listing program. Successfully tested products are listed on BACnet International’s website and are authorized to carry the BTL logo mark as proof of compliance.
With a Delta representative as co-chair for this group, Delta plays an important role in the BTL working group which is responsible for implementing the product conformance certification and listing program based upon ASHRAE Standard 135.1.
BACnet® Links
BACnet is a data communication protocol for Building Automation and Control Networks. Developed under the auspices of the American Society of Heating, Refrigerating and Air-Conditioning Engineers (ASHRAE), its purpose is to standardize communication between building automation devices and systems from different manufacturers. The protocol is supported and maintained by ASHRAE Standing Standard Project Committee 135.
BACnet affords facility owners and managers maximum flexibility and cost-effectiveness by allowing control products made by different manufacturers to be integrated into a single, uniform system. It is designed to allow HVAC/R, lighting, fire, access and security devices to interoperate. Owners can select the best technologies and services available, with the investment protection of being able to competitively expand current systems, without being “locked in” or having to replace them in the event that an original supplier loses favor. BACnet also facilitates single workstation control in campus/multi-building environments composed of a variety of different manufacturer’s control systems.
Before BACnet was developed, every manufacturer’s control equipment line was based on its own proprietary protocol. Any time equipment from different manufacturers needed to share information, custom software and hardware had to be developed and maintain at considerable time and cost.
BACnet was developed by a cross-section of industry professionals, comprising manufacturers, consulting engineers, end-users, government agencies and the academic community. It took over nine years to develop, was publicly reviewed and was adopted in 1995 as ANSI/ASHRAE Standard 135-1995.
Yes. In addition to being an American national standard (ANSI), BACnet is an established European pre-standard (CEN) and in the final stages of becoming a world standard (ISO). There are now thousands of BACnet projects installed and operating across more than eighty countries worldwide.
Interoperability is the result of different manufacturers’ devices using a common set of rules for data structure and transmission, allowing them to exchange data and execute commands.
BACnet can be implemented in any building or set of buildings, regardless of size. These systems can be very simple, with few devices, or very complex, with practically any number of devices and manufacturers.
Yes. From front-end workstations to network controllers and routers, central plant controllers, unitary controllers, actuators and sensors, BACnet is designed to be scaleable and provides a complete, cost-effective communication standard from top to bottom.
BACnet specifies six network types to accommodate different project and system requirements. These networks use widely accepted LAN standards, including Ethernet (IEEE 802.3/ISO 8802-3), ARCNET (ANSI/ATA 878.1), master slave/token passing (MS/TP, a twisted-pair RS-485 network created by BACnet), point-to-point (PTP, also created by BACnet) and LonTalk. The sixth option, BACnet/IP, was added later on to allow BACnet messages to be transported across the Internet and other IP-based wide area networks.
Native BACnet typically refers to a device that inherently represents data in BACnet format and communicates utilizing BACnet messaging. Native BACnet devices can be connected to a BACnet system without requiring a gateway device or software driver to translate to and from any proprietary protocols. Typical examples of native BACnet devices would be a native BACnet VAV application controller at the field level, and a native BACnet general system controller for central mechanical systems (e.g. air handing units) at the automation level.
Systems incorporating native BACnet devices at all levels provide facility owners and managers with superior system performance and interoperability. They are not compromised by proprietary software drivers and/or external gateways, which typically degrade system performance (throughput) and limit functional scope. Rather, BACnet messaging is utilized to communicate through all system levels, providing a consistent and seamless system-wide communications infrastructure. This also ensures owners with maximum investment protection and freedom of selection for future system expansion and upgrades, since they are not bound by the technical and commercial restrictions of proprietary drivers/gateways, as well as their potentially high maintenance costs.
It may be appropriate to specify an available gateway product for cost-effectively upgrading or expanding an existing facility with a BACnet system. The gateway bi-directionally translates the messages of the proprietary legacy system to and from the BACnet protocol, allowing them to interoperate. Another case is when integrating building systems that do not yet have native BACnet devices available (e.g. fire). Various gateways are available on the market for connecting proprietary equipment and systems to a BACnet system. Specifiers should carefully review the gateway performance specifications (including PICS) to verify that the system interoperability requirements can be met.
PICS stands for Protocol Implementation Conformance Statement. It is a detailed description for a given BACnet device stating its inherent BACnet capabilities. The level of BACnet functionality are typically scaled to suit the type of building automation device, ranging from simple intelligent peripheral devices to sophisticated operator workstations. Thus PIC statements are important for specifiers and users to ensure that the various devices will satisfy the desired interoperability requirements when designing and implementing integrated BACnet systems.
BIBB stands for BACnet Interoperability Building Block. BIBB’s represent specific individual function blocks for data exchange between interoperable devices. They are designed to be a simplifying tool for engineers to be able to write concise specifications describing the interoperability requirements of the various devices comprising a BACnet system. The various BIBB’s that have been defined to date are divided into five categories: data sharing; alarm & event management; scheduling; trending; device & network management.
A document published by the National Institute of Standards and Technology (NIST) - Internal Report 6392, GSA Guide to Specifying Interoperable Building Automation and Control Systems Using ANSI/ASHRAE Standard 135-1995, BACnet - may be particularly helpful. This report is available to the public at www.bacnet.org (located in the bibliography section).
The BACnet Interest Group – North America (BIG-NA) and the BACnet Manufacturers Association (BMA) have joined to form BACnet International - a non-profit organization of companies that design, market, and install building automation products. It includes various manufacturers of BACnet products, all of which are committed to ensuring that their BACnet products will interoperate.
BACnet International’s mandate is to encourage the successful and widespread use of BACnet in building automation and control systems through interoperability testing, educational programs, and promotional activities.
The BACnet Testing Laboratories was formed by BACnet International to perform BACnet compliance & interoperability testing of building automation products utilizing BACnet. A product-listing program identifies the products tested by BTL that have passed the necessary requirements.
Compliance testing provides assurance of interoperability between different manufacturers' products by verifying that the products correctly implement BACnet.
Listed products are authorized to display the “BTL” logo, and are presented on BACnet International's web site. This enables specifying engineers and end users to specify and purchase listed products with the assurance that these products have passed extensive BACnet interoperability testing and comply with the BACnet standard.
BACnet is the only protocol recognized as an international standard.
BACnet allows intelligent systems from various industries and manufacturers to exchange information, such as temperatures, setpoints, schedules, trend logs and alarms, and coordinate equipment operation to achieve optimum building performance. It saves facility owners/managers the costs of purchasing, engineering and maintaining custom interfaces for supervising packaged HVAC equipment (e.g. chillers), as well as integrating diverse building systems such as HVAC, lighting, fire, elevators, electrical services, etc.
BACnet empowers facility owners/managers with the flexibility of expanding and adding systems without being locked into one manufacturer. Instead, they can select the most appealing technology and services available and gain investment protection because current systems can be expanded without replacing the entire system.
The BACnet standard is independent of specific hardware platforms and supports multiple LAN technologies, including the Internet. This allows BACnet to evolve unencumbered as new technologies develop according to public demand, unlike open protocols where the underlying hardware and LAN technologies are controlled by one or few commercial enterprises.
As an ANSI/ASHRAE standard controlled by an ASHRAE standards body, BACnet cannot be changed without public review. Users have a say in any changes that may affect the protocol. Conversely, proprietary or public (open) protocols can be changed at the discretion of the creator without the customer being made aware.
