> 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-schindler-action-plans.md).

# Configuring Schindler Action Plans

A Schindler Action Plan is required to associate the dummy door (yet to be created) with the External System Item (terminal). An Action Plan is required for each terminal in the building.

1. Click **Configure** from the menu bar, then **Action Plans**.

   The **Action Plan** List Window opens (in [grid view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/grid-view.md)).
2. **Right click** and select **New\...Action Plan**.

   By default the **General** tab displays.
3. Complete the fields as required.

   For further detail see [General tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/general-tab.md).
4. Click the **Armed** (or **Set** ) tab.

   These settings define the responses when the item is linked with the Armed Alarm Zone.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-20655ebc3dc356ce08833908a0f954d56701abef%2Fschindler_terminalactionplan.png?alt=media)
5. Select **Not an Event** from the Alarm Priority drop-down list.

   **Note:** Ensure the Action Plan has an Alarm Priority that is set to 'Not an Event' otherwise you will get a lot of unnecessary events about access through the door. For debugging during the installation it may be useful to configure the priority to 'Message Only'.
6. Drag and drop the External System Item (terminal) to be triggered into the **Cameras, Macros and External System Items** grid, (e.g. Terminal 14).
7. Click the **Disarmed** tab and repeat steps 5-6. These settings define the responses when the item triggering the Action Plan is in the disarmed state.
8. Repeat steps 5-6 for the next two tabs also, (i.e. **User 1** and **User 2** tabs).
9. Click the **Notes** tab if you want to add a note(s) about this Action Plan.

   For further details regarding the **Notes** tab, see [Notes](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/notes.md).
10. Click **OK** to exit and save your changes.
11. Repeat this procedure to create an Action Plan for each terminal in the building.


---

# 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-schindler-action-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.
