"Native" BACnet Guide Specification

Choose this document if your client requires that their system be 100% compliant with Standard 135-2001: BACnet®–A Data Communication Protocol for Building Automation and Control Networks (ANSI Approved). This document details the information and guide specification requirements necessary for a complete operating system. “Native” BACnet means that all devices speak and understand only BACnet. The devices may be interconnected using any of the approved LAN technologies. All workstations and controllers, including unitary controllers, are native BACnet devices. No gateways shall be used for communication to controllers installed under this guide specification. Many building automation controls manufacturers are replacing their legacy protocols with native BACnet protocols.

Partially Compliant BACnet Guide Specification

Many of your clients desire the numerous benefits provided by a 100% native BACnet system; however they find themselves with existing proprietary controls. Choose this document—

• If your client requires the benefits of Standard 135-2001: BACnet®–A Data Communication Protocol for Building Automation and Control Networks (ANSI Approved) AND
• They have an existing proprietary building control system.

The main difference between native BACnet and partially compliant BACnet is that many of the field devices can be non-BACnet but still provide a degree of BACnet functionality at the front end or management level. This document details the information and guide specification requirements necessary for a complete operating system.