> 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/historical-notices/controller-6000-extended-support-state.md).

# Controller 6000 extended support statement — April 2020

Review the 2020 Controller 6000 support-extension commitment.

**23 April 2020.** In 2017 Gallagher announced the intention to support the Controller 6000 in Command Centre until at least **1 January 2027**.

Since then Gallagher continued investing in Controller 6000 functionality, including the significant controller upgrade to the **Linux-based operating system**, and saw a continued reduction in Controller 6000 product fault returns from component and manufacturing improvements.

Gallagher announced it is **extending its intention to support the Controller 6000 to at least 1 July 2031**. Gallagher intends to support the controller in Command Centre and provide technical support until this date as a minimum. While unforeseen component obsolescence can impact product lifecycles, stating this intention provides customers reassurance on the longevity of their Controller 6000 investment.

{% file src="/files/rUyYJMx6tUlH2KfuF1a7" %}
Gallagher Controller 6000 - Support Extension Statement
{% endfile %}

***

🔗 **Related**

* [Controller 6000 - Superseded Status and Pathway to Obsolescence - March 2025](/knowledge-hub/products/product-advisories/current-advisories/controller-6000-superseded-status-and.md). The later notice that sets the end date.
* [Controller 6000](/knowledge-hub/products/cc-hardware/controllers/controller-6000.md). Setup, faults, and reference for the controller.
* [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/historical-notices/controller-6000-extended-support-state.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.