> 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/cc-software/reference/server-bespoke-minimum-specification.md). # Server - bespoke minimum specification Gather site requirements for a bespoke Command Centre server specification. > 📋 **Prerequisites:** Read [Server - Minimum Specification](/knowledge-hub/products/cc-software/reference/minimum-specifications.md) first. Every site is unique, and it is extremely rare for two sites to be the same, so a one-size-fits-all guide is difficult. For sites that are larger than the standard tiers or have unusual requirements, our Gallagher representatives can assist with recommendations by assessing requirements and usage. Examples of the information collected is below: *** ## Storage requirement questions * Doors on site (including Gallagher and 3rd-party doors, e.g. Aperio) * Door access events per day (average) * External items connected to Command Centre (systems such as CCTV) * External event rate sent to Command Centre per day, average (systems such as CCTV) * Storage retention time required on the SQL database, in days (assuming events are archived to a networked drive) * Is the SQL instance on another machine? ## Future expansion resilience questions * Expected door growth rate over the next 5 years or so * Whether the site expects to start or increase REST usage in the next 5 years * Whether the site is looking to add other features or integrations in the next 5 years ## Server specification questions * Active workstation connections (including Visitor Management, Mobile Command Centre) * Number of cardholders * Number of controllers * Number of REST connections * The type of REST connections typically run (POST or GET) * The longest-running REST query time (minutes) * Number of regularly running reports * Time the longest-running report takes to complete (minutes) * Number of regularly run EDIs * How often the EDIs are run *** 🔗 **Related** * [Server - Minimum Specification](/knowledge-hub/products/cc-software/reference/minimum-specifications.md). The standard Small / Medium / Large / Extra Large tiers. --- # 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/cc-software/reference/server-bespoke-minimum-specification.md?ask=&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.