> 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/configuration-client/site-installation/site-plans/understanding-site-plans.md).

# Understanding Site Plans

### Introduction

Site Plans show the layout and/or relationship of devices to one another. Site Plans use (import) map images and allow graphical representations of Site Items to be placed on the map image. These Site Items can be placed on the map images as they are located in the real world and can be hardware devices, (e.g. *I/O Interfaces*), or logical entities, (e.g. [*Access Zones*](https://help.security.gallagher.com/knowledge-hub/configuration-client/glossary-of-terms.md#access-zone)). The following items can be placed on a Site Plan:

* All hardware devices
* Servers
* Access Zones
* Alarm Zones
* Doors
* Interlock Groups
* Elevator Cars and Elevator Car HLIs
* Services and Workstations
* External Systems
* Intercom Systems
* Macros
* Logic Blocks
* Links to other Site Plans

Site Items can be represented by icons or regions and are all able to convey information about their current state.

Site Items can be added, deleted, modified and viewed, depending on operator privileges.

**For example:**

Site Plans in Command Centre can be layered. An example of layered Site Plans would be to have an Overall (or Master) Site Plan representing a complete Site with links to Site Plans that represent specific areas (sections) within that Site.

Each linked Site Plan is a section of the Overall Site Plan, containing site icons for that area and/or links to other Site Plans.

When an alarm occurs:

* The guard is viewing the Overall Site Plan.
* On this plan, a Site Plan icon flashes to indicate an alarm has occurred.
* The guard right-clicks this Site Plan icon and selects 'View Site Plan with Alarm' to access the layered Site Plan.
* The layered Site Plan window opens showing further details.
* The guard can now view what the alarm is and where the alarm occurred.
* Once the appropriate action has been taken and the alarm processed, the guard can return to the Overall Site Plan.

### Site Plan List Window

The **Site Plan** List Window opens in [tree view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/tree-view.md), which is achieved via the **Lineage** tab when you set up Site Plans.

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-90fa60d715901f4563c79ddb3a9f53a8dcf3a21e%2Fsiteplanwindow.png?alt=media)

Site Plans containing items in alarm will flash on this window. If the Site Plan that has items in alarm is a child Site Plan, the parent Site Plan will flash also.

**Note:** Double-clicking on a Site Plan in alarm from here results in the Site Plan opening as long as it is a legacy Site Plan, (i.e. a Site Plan created in Configuration Client). You can then double-click the flashing icon on the Site Plan to open the Alarm Properties window for that item.

If a Site Plan was created in Command Centre Client, the following message will display when you double-click on it:

*"This site plan is edited or viewed in the Command Centre Client"*


---

# 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/configuration-client/site-installation/site-plans/understanding-site-plans.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.
