> 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-hardware/controllers/controller-7000-and-7000-sdc/configure/controller-7000-time.md). # Configure controller time Configure Controller 7000 time synchronization, UTC offsets, time zones, and event timestamps. #### Where does a controller get its time from? Gallagher controllers get their time from the Command Centre server they are configured to connect to. This configuration also applies to Controller 7000 SDC. #### How does a controller distribute time 1. The **CC server** must have its time, timezone, and region correctly configured. 2. The server calculates **UTC time** and sends it to the controller. 3. The controller applies its **UTC offset** (configured in CC on the controller's Setup tab) to determine local time. 4. The controller uses this local time for all timed events (schedules, access groups, alarm zones, and so on). ![Controller time — UTC offset display on web page](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-40d50b2c5ed0d376df666e1b878b6b4a5feca1cc%2FSECHUB-C7000-TIME-01-controller-time-utc-offset.png?alt=media) **Example log timestamp format from the controller:** ``` 2026-04-23T12:58:12.972+12:00 ``` The format is: `Date T Time UTC-offset`. ![Server UTC time and controller time comparison](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-d1a4e067cd4fa02b1daeb05301733664aa1afe8c%2FSECHUB-C7000-TIME-03-server-utc-and-controller-time.png?alt=media) The image above shows the server time (NZ timezone, bottom left), the UTC time (13:00), and the controller's web page confirming it reads 13:00 with a +12:00 offset, meaning the controller's local time is 01:00 the next day in NZ. *** #### How is a controller's timezone configured? The controller's timezone is set independently of the server's timezone in **Configuration Client** under the controller's **Setup** tab. ![Controller timezone configuration in CC](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-7cb7d2a8bb789dc2038edae27ab269c0c3591db0%2FSECHUB-C7000-TIME-02-controller-timezone-config.png?alt=media) Key points: * The controller **can be set to a completely different timezone** to the server. * All time-related actions on the controller (schedules, access rules, alarm triggers) are performed relative to the controller's **configured locale**, not the server's timezone. * The controller can also be configured to use its own **local calendar**. See the Calendars configuration in Command Centre for details. *** ## Events and reports * Events occurring on the controller are returned to the CC server and recorded in the `CCFTEvent` database for later retrieval. * Reports generated for these events display the time the event occurred, **based on the workstation's timezone**, not the controller's timezone or the server's timezone. > **Troubleshooting:** If event timestamps appear incorrect in reports, confirm: > > 1. The server timezone is correctly configured. > 2. The controller UTC offset is correctly set in the controller's Setup tab. > 3. The workstation generating the report has the correct timezone set in Windows. All three affect what timestamps are displayed. *** 🔗 **Related** * [Bringing Online and Networking](/knowledge-hub/products/cc-hardware/controllers/controller-7000-and-7000-sdc/configure/controller-7000-bringing-online-and-ne.md). The controller's Setup tab, where the UTC offset is configured. * [Controller 7000](broken://pages/873trKCrdhjXzfqYdsdU). Variants, specifications, and accessories. --- # 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-hardware/controllers/controller-7000-and-7000-sdc/configure/controller-7000-time.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.