> 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/deployment-resources/engineering-and-design-reference/product-reliability-report.md).

# Product reliability report

Five-year warranty-return rates for Gallagher product groups.

Product Reliability replaces previous Mean Time Between Failures statements.

The figures use valid warranty-return data from the last five years. This measure reflects field performance better than theoretical MTBF.

### Valid warranty returns over five years

Figures were last updated on **31 March 2025**.

| Product group               | Valid warranty returns |
| --------------------------- | ---------------------- |
| Controller 7000             | 0.05%                  |
| Controller 7000 Single Door | 0.07%                  |
| Controller 6000             | 0.98%                  |
| Controller modules          | 0.58%                  |
| I/O control equipment       | 0.22%                  |
| T Series readers            | 0.34%                  |
| Power supplies              | 0.24%                  |
| Perimeter energizers        | 0.96%                  |

### Conditions

Figures assume each product meets its published environmental specifications. Typical conditions include a **13.6 Vdc ±15%** supply.

The temperature range is **0°C to +55°C** for internal equipment. It is **−10°C to +55°C** for external equipment.

{% hint style="info" %}
All reported rates are below 1% over five years.
{% endhint %}


---

# 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/deployment-resources/engineering-and-design-reference/product-reliability-report.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.