> 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/product-advisories/current-advisories/gbus-obsolescence-statement-march-2023.md).

# GBUS obsolescence

Plan GBUS replacement before upgrading Command Centre beyond version 9.0.

**Command Centre v9.0 is the last version with support for GBUS devices.** Customers must replace GBUS devices with **HBUS** devices to upgrade past v9.0.

HBUS was released in **2012** for improved speed, data protection, and automated scalability. GBUS was released 20 years earlier, in **2003**.

In **2018** GBUS devices were placed into runout status. Gallagher is no longer able to supply GBUS devices. Customers continuing on this legacy technology risk being unable to obtain replacements on failure or system change. Supporting GBUS costs development time with every Command Centre release.

## Benefits of upgrading GBUS to HBUS

* Improved cyber security with device authentication, improved encryption, and DESFire key rolling
* Support for Mobile Credentials
* Faster speeds
* Reduced install labour through device self-discovery
* More devices per controller
* Over-the-wire device firmware updates
* Support for star-wired and daisy-chained architectures across the full range of readers, door modules and I/O expanders

## GBUS obsolescence timeline

| Year | Event                                                 |
| ---- | ----------------------------------------------------- |
| 2003 | GBUS introduced as the communication protocol         |
| 2012 | HBUS introduced to replace GBUS                       |
| 2015 | GBUS placed into legacy status                        |
| 2018 | GBUS placed into runout status                        |
| 2023 | Announcement that v9.0 is the last supporting version |

See the [GBUS Obsolescence FAQ flyer](https://media.gallagher.com/m/6c91d3c7d6288704/original/GBUS-Obsolescence-FAQ-Flyer.pdf).

{% file src="/files/BfBWM2ErB3vF1EFM2Vs8" %}
Gallagher GBUS Obsolescence Statement
{% endfile %}

***

🔗 **Related**

* [Product Advisories](/knowledge-hub/products/product-advisories.md). The full register of obsolescence, security, and deprecation notices.


---

# 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/product-advisories/current-advisories/gbus-obsolescence-statement-march-2023.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.