> 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/external-systems/schindlerid/the-call-manager-interface-plugin/configuring-secure-free-floors/configuring-a-site-plan-for-secure-free-floors.md).

# Configuring a Site Plan for Secure/Free Floors

Drag the External System Item (floor) onto a Site Plan beside the Virtual Output. When placed on the Site Plan side by side, it is easily seen whether the Free/Secure action succeeded or whether it needs to be repeated.

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

If all goes fine, the status of the virtual output will match the status of the External System Item (floor).

If a user overrides a Virtual Output at the moment when the Schindler simulated terminal is still processing the previous request (and therefore the latter one is thrown away), the status of the External System Item (floor) reflects the last successful change, therefore differs from the External System Item (terminal) status, and this way informs the operator that he/she should repeat the action.

**Note:** In the example above, the Output Icon Set has been applied to the External System Items (floors). This enables you to view the status of a floor easily, when the External System Item (floor) is added to the Site Plan. Refer to the topic [Creating a new Icon Set](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/icon-sets/creating-a-new-icon-set.md) for further details.


---

# 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/external-systems/schindlerid/the-call-manager-interface-plugin/configuring-secure-free-floors/configuring-a-site-plan-for-secure-free-floors.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.
