> 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/deployment-guidelines/maintenance.md).

# Maintenance

Maintain Command Centre systems through tested upgrades, scheduled physical checks, and operational monitoring.

Maintenance of a Gallagher Security Solution is crucial to ensure the customer’s site is kept protected from physical and cyber threats.

### Software upgrades

Gallagher recommends that upgrades are fully tested in an **isolated environment** using the site’s existing databases prior to upgrading the production environment.

Use an isolated environment so controllers, workstations, and other devices do not connect to the production site.

Identify potential issues early. This reduces or avoids site disruption.

{% hint style="warning" %}
Always verify that the install media is not marked as untrusted by Windows when performing the install/upgrade operation.
{% endhint %}

See [Command Centre server upgrade guidelines](https://help.security.gallagher.com/knowledge-hub/deployment-resources/engineering-and-design-reference/migrate-and-upgrade/command-centre-server-upgrade-guidelines.md) for upgrade planning, testing, execution, and validation.

### Physical maintenance

It is recommended that sites undergo maintenance regularly to ensure they are secure and operational. The Gallagher Command Centre Maintenance Schedule should be utilised.

### Power Supplies

Power Supplies should be checked at regular intervals for, but not limited to:

* Battery capacity
* Battery health
* Enclosure tidiness

### Door Hardware

Door Hardware should be checked at regular intervals for the following, but not limited to:

* Lock functionality
* Mounting security
* Door operation/security

[Gallagher Command Centre Maintenance Schedule](https://media.gallagher.com/m/2632d3b28e2ef495/original/Command-Centre-Maintenance-Schedule-Template.pdf)

### Operational maintenance

### Alarm Management

Active alarms in Command Centre should be kept to a minimum; they should be addressed and processed in a timely manner to avoid large numbers of alarms being queued in Command Centre. Excessive queued messages can lead to poor system performance.

### Controllers configured but not online

Controllers that are configured but not actually online will result in queued messages for those controllers. While Command Centre does cater for this, it is not recommended, as the message queue will start to become large as time moves on and more changes are made.

### Report Scheduling

Avoid scheduling reports that span vast amounts of time at the same time as other reports. This could lead to significant performance impacts if multiple long-time-span reports are run simultaneously. Staggering the reports is recommended.


---

# 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/deployment-guidelines/maintenance.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.
