> 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/best-practice-checklist.md).

# Deployment checklist

Verify Command Centre infrastructure, hardware, software, and maintenance requirements during commissioning and reviews.

Use this checklist when commissioning a site and at regular reviews. Use the linked guidance for details on each group of checks.

Use it alongside the [Gallagher Command Centre Commissioning Report](https://media.gallagher.com/m/13bd1b59c1caf8ae/original/Command-Centre-Commissioning-Report-Template.pdf), which records the commissioning details for the site.

### [Infrastructure and IT](https://help.security.gallagher.com/knowledge-hub/deployment-resources/engineering-and-design-reference/deployment-guidelines/infrastructure-and-it.md)

* [ ] [Compatibility matrix](https://help.security.gallagher.com/knowledge-hub/deployment-resources/engineering-and-design-reference/compatibility-matrix.md) checked for the operating system, SQL Server and hardware versions in use
* [ ] Dedicated VLAN for controllers where the site has many; wireless used only as a backup path
* [ ] Firewall ports opened as described in [Network ports and protocols](https://help.security.gallagher.com/knowledge-hub/deployment-resources/engineering-and-design-reference/network-ports-and-protocols.md)
* [ ] Remote controllers addressed by DHCP or manually; OneLink configured where used
* [ ] Server meets the minimum specifications; sustained CPU, memory, and disk utilization below 75%
* [ ] Operating system patched as per the site’s policies
* [ ] Separate install/upgrade account (sysadmin) and dedicated service account (db\_owner); a separate, limited account for housekeeping
* [ ] Command Centre services monitored, where the site has a monitoring system
* [ ] Minidump type set to level 1 and Trace logging off for normal operation
* [ ] Virtual machines: no long-lived snapshots, fixed memory, thick-provisioned disks and reserved CPU
* [ ] SQL instance dedicated to Command Centre; latency to the server under 1 ms
* [ ] SQL Server edition suits the site; SQL Express limits understood if used
* [ ] Hardening guides reviewed and applied
* [ ] Workstation deployment method chosen (ClickOnce or MSI)
* [ ] Operators log on to workstations with standard Windows accounts
* [ ] Integration versions confirmed compatible with the Command Centre version
* [ ] Each REST client has its own API key, a least-privilege REST operator and a pinned client certificate

### [Hardware](https://help.security.gallagher.com/knowledge-hub/deployment-resources/engineering-and-design-reference/deployment-guidelines/hardware.md)

* [ ] Local regional requirements identified and met
* [ ] Gallagher or approved power supplies used; at least 12 Vdc at device terminals at peak load
* [ ] Door locks on their own dedicated, fused power cable
* [ ] Cabling tidy and labelled, with at least 300 mm (12 in) between LV and ELV cabling
* [ ] HBUS runs daisy-chained, or star-wired through an HBUS 8 Port Hub or HBUS module; no longer than 500 metres (1,640 ft) end to end; end devices terminated
* [ ] Readers at least 200 mm (8 in) apart and away from metal surfaces
* [ ] Device limits checked against each installation note
* [ ] Tampers in use, and optical tampers initialised with the cabinet closed

### [Software](https://help.security.gallagher.com/knowledge-hub/deployment-resources/engineering-and-design-reference/deployment-guidelines/software.md)

* [ ] Latest supported Command Centre version installed
* [ ] CCFT Service Manager set to run on startup
* [ ] Database Recovery Code exported and stored securely, away from the server
* [ ] Naming convention agreed and applied
* [ ] Divisions designed before configuration begins
* [ ] Scheduled backups to a location off the server; interim backups after significant changes; a test restore completed
* [ ] RPO and RTO agreed with the customer, and a DR plan documented
* [ ] Archiving configured
* [ ] Calendars and Day Categories set up
* [ ] DESFire EV3 or higher cards used; SSK exported and stored securely; unused card technologies disabled
* [ ] Operator groups follow least privilege; each operator has their own login
* [ ] Access Group lineage planned
* [ ] All components of a door hosted on the same controller

### [Maintenance](https://help.security.gallagher.com/knowledge-hub/deployment-resources/engineering-and-design-reference/deployment-guidelines/maintenance.md)

* [ ] Upgrade process uses an isolated test environment
* [ ] Maintenance schedule agreed with the customer
* [ ] Active alarms processed promptly; no controllers configured but offline; long reports staggered

## Sign-off

|              |   |
| ------------ | - |
| Site         |   |
| Completed by |   |
| Date         |   |
| Notes        |   |


---

# 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/best-practice-checklist.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.
