> 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.md).

# Deployment guidelines

Use Gallagher best practices to design, implement, and maintain Command Centre systems.

***

## Introduction

This article sets out Gallagher’s best practice guidelines for designing, installing, and maintaining a Gallagher Command Centre system and its hardware. Following them helps a system run reliably, stay secure and supportable, and meet both the manufacturer’s recommendations and any legal or regulatory requirements.

### Who this article is for

* Integrators and channel partners who design and install Gallagher systems.
* Customer IT teams responsible for the servers, network and databases that Command Centre runs on.
* System administrators who operate and maintain Command Centre day to day.
* Gallagher Professional Services.

### How to read this article

The guidelines use the following terms to show how strongly each one applies:

<table><thead><tr><th width="227">Term</th><th>Meaning</th></tr></thead><tbody><tr><td>Must / required</td><td>A requirement. Not following it risks system failure, data loss or a security weakness.</td></tr><tr><td>Recommended / should</td><td>Gallagher’s best practice, based on what has proven to work in the field. It cannot be guaranteed for every site, so any departure should be a deliberate, documented decision.</td></tr><tr><td>Consider / may</td><td>Optional; whether it applies depends on the site’s requirements.</td></tr></tbody></table>

Where a local standard, regulation or customer security requirement is stricter than these guidelines, the stricter requirement applies.

## Compatibility

The information in this article is provided in a generic format that is compatible with different deployments of Command Centre and its hardware.

This article is designed to be version-agnostic. Where a recommendation depends on a particular Command Centre or controller version, that version is stated alongside it. This is a live article that is updated periodically. Check that you are using the latest edition, and refer to the release notes for the version in use.

When designing or investigating a Command Centre system, check the [Compatibility matrix](https://help.security.gallagher.com/knowledge-hub/deployment-resources/engineering-and-design-reference/compatibility-matrix.md). It covers operating systems, SQL versions, supported hardware, and software features across all versions.

Gallagher Security can provide professional services to assist sites. Contact your local Gallagher representative to learn more.

## Article structure

This guidance is organized by system area:

<table><thead><tr><th width="243">Area</th><th>Guidance</th></tr></thead><tbody><tr><td><a data-mention href="https://help.security.gallagher.com/knowledge-hub/deployment-resources/engineering-and-design-reference/deployment-guidelines/infrastructure-and-it.md">Infrastructure and IT</a></td><td>Network, servers, SQL Server, workstations, and integrations</td></tr><tr><td><a data-mention href="https://help.security.gallagher.com/knowledge-hub/deployment-resources/engineering-and-design-reference/deployment-guidelines/hardware.md">Hardware</a></td><td>Controllers, power, wiring, readers, and field devices</td></tr><tr><td><a data-mention href="https://help.security.gallagher.com/knowledge-hub/deployment-resources/engineering-and-design-reference/deployment-guidelines/software.md">Software</a></td><td>Configuration, databases, backups, and operational security</td></tr><tr><td><a data-mention href="https://help.security.gallagher.com/knowledge-hub/deployment-resources/engineering-and-design-reference/deployment-guidelines/maintenance.md">Maintenance</a></td><td>Upgrades, physical checks, and operational monitoring</td></tr><tr><td><a data-mention href="https://help.security.gallagher.com/knowledge-hub/deployment-resources/engineering-and-design-reference/deployment-guidelines/best-practice-checklist.md">Deployment checklist</a></td><td>Commissioning and review checks across all areas</td></tr></tbody></table>

## Technical resources

This article provides references to key technical resources, including links where possible. Version-specific documentation and utilities are provided with the Command Centre Software installation files. We recommend using them.

### Key resources

Gallagher Security provides key resources to assist with the use of a site’s Command Centre system. We recommend using them.

1. [Gallagher Security Compatibility Matrix](https://media.gallagher.com/asset/97e522a3-f16b-4e3d-ba13-b8e8248f1028/CC-Compatibility-Matrix.xlsx)\
   A resource detailing hardware and software compatibility between different versions.
2. [Gallagher Command Centre Commissioning Report](https://media.gallagher.com/m/13bd1b59c1caf8ae/original/Command-Centre-Commissioning-Report-Template.pdf)\
   A template that can be used when commissioning a Command Centre site.
3. [Gallagher Command Centre Maintenance Schedule](https://media.gallagher.com/m/2632d3b28e2ef495/original/Command-Centre-Maintenance-Schedule-Template.pdf)\
   A template that can be used when performing maintenance on a Command Centre site.


---

# 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.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.
