> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/products/cc-software/configure/interface-options/facility-management-interfaces/bacnet-overview.md).

# BACnet - overview

Integrate BACnet-compatible building devices with Command Centre alarm management.

Command Centre is capable of bi-directional communication with BACnet-compatible devices and objects. Gallagher's **BACnet Protocol Interface** allows specified **Controller 6000s to act as BACnet clients**, to both read and write BACnet Object values.

* **Inbound communication.** Command Centre can monitor BACnet objects for state changes and raise alarms accordingly.
* **Outbound communication.** Command Centre allows BACnet objects to change state in response to events.

**Versions supported:** Command Centre **v8.10 through v9.40**.

## Use case

The major benefits to a site implementing the BACnet Protocol Interface are:

* Command Centre can be the central repository for all site alarms. It can monitor boiler, chiller, and air conditioning failures, maintenance alarms, and similar.
* Events received are processed by Command Centre, so they get the full event and alarm management capability of the system alongside other site alarms. That includes reporting, notifications, URL Tile, operator notes, and escalations.
* Access driven environment control translates to energy efficiency and potential cost savings. Site managers can ensure that only people with the correct access rights activate services such as lighting and air conditioning on a valid card badge, that people use the correct services (cleaners may require less lighting than other users), and that services shut down when no movement is detected.

Many sites already run a building management system as a stand-alone system for managing services. Integrating it with Command Centre provides the energy savings above, plus a centralized alarm and event management system so stakeholders are aware of alarms as they are raised.

> 🧭 **Where to start**
>
> * **Planning the install?** → [BACnet - Basic Setup Requirements](/knowledge-hub/products/cc-software/configure/interface-options/facility-management-interfaces/bacnet-overview/bacnet-basic-setup-requirements.md)
> * **Checking what BACnet will not do?** → [BACnet - Limitations](/knowledge-hub/products/cc-software/configure/interface-options/facility-management-interfaces/bacnet-overview/bacnet-limitations.md)

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>BACnet - Basic Setup Requirements</strong></td><td></td><td></td><td><a href="/knowledge-hub/products/cc-software/configure/interface-options/facility-management-interfaces/bacnet-overview/bacnet-basic-setup-requirements.md">BACnet - basic setup requirements</a></td></tr><tr><td><strong>BACnet - Limitations</strong></td><td></td><td></td><td><a href="/knowledge-hub/products/cc-software/configure/interface-options/facility-management-interfaces/bacnet-overview/bacnet-limitations.md">BACnet - limitations</a></td></tr></tbody></table>

**Documentation:** BACnet Protocol Interface Feature Overview v5. Release Note BACnet, published for each version from v8.10 through v9.40. Release Note BACnet PICS, published for each version from v8.10 through v9.40.

***

🔗 **Related**

* [Facility Management Interfaces](/knowledge-hub/products/cc-software/configure/interface-options/facility-management-interfaces.md). The other building and server-to-server interfaces: Booking Interface, Cardholder Count Outputs, Cardholder Sync, and Event Sync.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/products/cc-software/configure/interface-options/facility-management-interfaces/bacnet-overview.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
