> 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/action-plans/creating-a-new-action-plan.md).

# Creating a new Action Plan

### Introduction

When creating a new Action Plan you perform the following steps:

* Within the **Action Plan** List Window, create a new Action Plan.
* Define the 'course of action' for each of the Alarm Zone States, (i.e. specify relays to be deactivated when an alarm is not active, and set the Escalation details).

Operators require the "Edit Alarm Configuration" operator privilege to perform this procedure, and must be in the same or parent Division of the Action Plan.

**Notes:**

* If the Action Plan is to operate an [Output](https://help.security.gallagher.com/knowledge-hub/configuration-client/glossary-of-terms.md#output), camera and/or macro, ensure these items are already configured.
* The alarm behaviour can be configured specifically for the types of events in Command Centre, (i.e. Command Centre events and Controller events), therefore you need only configure the property pages relevant for a particular event type, as indicated in Step 5.

***

### Configuration

To configure a new Action Plan, perform the following procedures in Gallagher Configuration Client:

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).

   **Note:** The next four tabs will reflect the Alarm Zone States in use in your Command Centre system, (i.e. as configured on the **Alarm Zone States** tab of the Server Properties).

   Each of these tabs will be named according to the user-configurable names of the four Alarm Zone States. For example, the **Armed** and **Disarmed** tabs will display as **Set** and **Unset** if you changed these in the Alarm Zone States tab of the Server Properties. Refer to [Alarm Zone States](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/alarm-zone-states.md) for further detail.

   The type of Action Plan you are creating, (i.e. for what type of event), determines which tabs need configuring, as follows:

   <table><thead><tr><th width="186">If...</th><th>then configure the...</th></tr></thead><tbody><tr><td>Controller,</td><td><strong>Armed</strong> (or <strong>Set</strong>) tab, <strong>Disarmed</strong> (or <strong>Unset</strong>) tab and <strong>Escalation</strong> tab.</td></tr><tr><td>Command Centre,</td><td><strong>Command Centre</strong> tab.</td></tr></tbody></table>
4. Click each tab as appropriate and configure the Action Plan properties:

<details>

<summary>Armed (or Set) tab</summary>

1. Click the **Armed** (or **Set** ) tab.

   These settings define the responses when the item's Alarm Zone is armed.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-8949a033147dc5cb2892c93efcb1e8e461f03092%2Ftab_armed.png?alt=media)
2. Specify the priority of events or alarms generated, from the **Alarm Priority** drop-down list.

   When an event occurs and it has this associated Alarm Zone state, the response will be of this priority.

   **Note:** The drop-down list will be populated with alarm priority names configured for the overall Command Centre system.
3. The Alarm Dialler field relates to Contact ID. If required, click within the Alarm Dialler field to display the available options, and from the list select the appropriate **Alarm Dialler** for Contact ID.

   See [External Alarm Monitoring](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/external-alarm-monitoring.md) for an explanation of what Contact ID is, and for instructions on configuring Contact ID.
4. Drag and drop the outputs that are required to activate into the **Output** grid.

   **Note:** If the Alarm Priority is set to "Not an Event" or "Message Only", the output(s) will not be activated.
5. Drag and drop the DVR Cameras (Cardax or third-party), Macros and/or External System Items to be triggered into the **Cameras, Macros, and External System Items** grid.

   **Note:** When the Action Plan is executed:

   * The footage recorded by the cameras in this grid at the time of the event/alarm is associated with the event/alarm. As a result, when viewing an event/alarm in Command Centre client, a camera tile can show footage taken by these cameras at the time which the alarm occurred.
   * The string(s) on the **Trigger -- Events** tab of the cameras and External System Items in this grid are sent to those devices’ third-party systems.
   * Note that when Macros in this grid are run, they will not run a bulk change if triggered from an Action Plan.
6. Select the appropriate option from the **Deactivate** drop-down list.

   There are three options available, and your selection will determine when outputs (that are activated when an alarm occurs), are deactivated. The options are:

   * when an alarm is acknowledged,
   * when an alarm is acknowledged **or** becomes inactive,
   * when an alarm is acknowledged **and** becomes inactive.
7. By checking the **Keep alarm and relays active when alarm zone unset** checkbox this will ensure that outputs (defined on this Action Plan tab) that are active when the Alarm Zone changes state, will remain active after the state change (provided the alarm has not been acknowledged).
8. Tick the appropriate checkbox for the ‘course of action’ for an escalated event or alarm. **Escalation Rules** are as follows:

   <table><thead><tr><th width="222">Rule</th><th>Description</th></tr></thead><tbody><tr><td>Escalate if not acknowledged for:</td><td>The alarm will escalate if it is not acknowledged within the specified time.</td></tr><tr><td>Escalate if in active state for:</td><td>The event or alarm will escalate if it remains active for the specified time.</td></tr><tr><td>Escalate if two events from the same point within:</td><td>The event or alarm will escalate immediately if an event from the same point and event group occurred within the previous time specified.</td></tr><tr><td>Escalate if two events from different points in same zone within:</td><td>The event or alarm will escalate immediately if an event from another point in the point's alarm zone with the same event group occurred within the previous time specified.<br><strong>Warning:</strong> Any points generating events in the same group can contribute to this rule, including outputs. To avoid unintentional escalation, outputs should not be assigned an alarm zone or be assigned an alarm zone where this escalation rule is not used.</td></tr><tr><td>Escalate if zone contains:</td><td>The event or alarm will escalate immediately if the alarm stack already contains the specified number of unacknowledged alarms from points in the Alarm Zone.</td></tr></tbody></table>

   **Note:**

   Escalation will only work if the Inputs in an Alarm Zone are on the same Controller, and the Alarm Zone is not spanned.
9. Click **Apply** to save your changes.

</details>

<details>

<summary>Disarmed (or Unset) tab</summary>

1. Click the **Disarmed** (or **Unset)** tab.

   These settings define the responses when the item's Alarm Zone is disarmed.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-746198f6a6edd1b32e3a5506aa9f15ccd168548f%2Factionplan_disarmedtab.png?alt=media)
2. Specify the priority of events or alarms generated, from the **Alarm Priority** drop-down list.

   When an event occurs and it has this associated Alarm Zone state, the response will be of this priority.

   **Note:** The drop-down list will be populated with alarm priority names configured for the overall Command Centre system.
3. The Alarm Dialler field relates to Contact ID. If required, click within the Alarm Dialler field to display the available options, and from the list select the appropriate **Alarm Dialler** for Contact ID.

   See [External Alarm Monitoring](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/external-alarm-monitoring.md) for an explanation of what Contact ID is, and for instructions on configuring Contact ID.
4. Drag and drop the outputs that are required to activate into the **Output** grid.

   **Note:** If the Alarm Priority is set to "Not an Event" or "Message Only", the output(s) will not be activated.
5. Drag and drop the DVR Cameras (Cardax or third-party), Macros and/or External System Items to be triggered into the **Cameras, Macros, and External System Items** grid.

   Note: When the Action Plan is executed:

   * The footage recorded by the cameras in this grid at the time of the event/alarm is associated with the event/alarm. As a result, when viewing an event/alarm in Command Centre client, a camera tile can show footage taken by these cameras at the time which the alarm occurred.
   * The string(s) on the **Trigger -- Events** tab of the cameras and External System Items in this grid are sent to those devices’ third-party systems.
   * The Macros in this grid are run. Note that Macros that run a bulk change will not occur from an Action Plan.
6. Select the appropriate option from the **Deactivate** drop-down list.

   There are three options available, and your selection will determine when outputs (that are activated when an alarm occurs), are deactivated. The options are:

   * when an alarm is acknowledged,
   * when an alarm is acknowledged **or** becomes inactive,
   * when an alarm is acknowledged **and** becomes inactive.
7. By checking the **Keep alarm and relays active when alarm zone unset** checkbox this will ensure that outputs (defined on this Action Plan tab) that are active when the Alarm Zone changes state, will remain active after the state change (provided the alarm has not been acknowledged).
8. Tick the appropriate checkbox for the ‘course of action’ for an escalated event or alarm. **Escalation Rules** are as follows:

   <table><thead><tr><th width="222">Rule</th><th>Description</th></tr></thead><tbody><tr><td>Escalate if not acknowledged for:</td><td>The alarm will escalate if it is not acknowledged within the specified time.</td></tr><tr><td>Escalate if in active state for:</td><td>The event or alarm will escalate if it remains active for the specified time.</td></tr><tr><td>Escalate if two events from the same point within:</td><td>The event or alarm will escalate immediately if an event from the same point and event group occurred within the previous time specified.</td></tr><tr><td>Escalate if two events from different points in same zone within:</td><td>The event or alarm will escalate immediately if an event from another point in the point's alarm zone with the same event group occurred within the previous time specified.<br><strong>Warning:</strong> Any points generating events in the same group can contribute to this rule, including outputs. To avoid unintentional escalation, outputs should not be assigned an alarm zone or be assigned an alarm zone where this escalation rule is not used.</td></tr><tr><td>Escalate if zone contains:</td><td>The event or alarm will escalate immediately if the alarm stack already contains the specified number of unacknowledged alarms from points in the Alarm Zone.</td></tr></tbody></table>

   **Note:**

   Escalation will only work if the Inputs in an Alarm Zone are on the same Controller, and the Alarm Zone is not spanned.
9. Click **Apply** to save your changes.
10. Repeat these steps (b-i) for the next two tabs also, (i.e. **User 1** and **User 2** tabs, unless these have been renamed in the Server Properties).

</details>

<details>

<summary>Escalation tab</summary>

1. Click the **Escalation** tab.

   These settings define the 'course of action' for an escalated event or alarm. The only difference between this tab and the other Alarm Zone State tabs is that the escalation options are not available as the event or alarm has already been escalated.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-be297e73953428e541e28b9f9231fbbfa3492a6f%2Ftab_esc.png?alt=media)
2. Select the appropriate Escalation **Alarm Priority**.

   Escalation will occur if this setting has a higher priority than the "Alarm Priority" setting within the Alarm Zone tabs.

   **Note:**

   All events and alarms that escalate to the escalated priority will:

   * also appear in the **Escalated Alarm Viewer**, and
   * display as “Escalated” in the Alarm Details.
3. The Alarm Dialler field relates to Contact ID. If required, click within the Alarm Dialler field to display the available options and from the list select the appropriate **Alarm Dialler** for Contact ID.

   See [External Alarm Monitoring](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/external-alarm-monitoring.md) for an explanation of what Contact ID is, and for instructions on configuring Contact ID.

   **Note:**

   Alarms will be sent as many times as an Alarm Dialler appears on an Action Plan for the various priorities involved in an escalation. **For example:**

   If a "Forced Door" alarm uses a very high priority Action Plan with an Alarm Dialler attached, it will escalate to a critical priority that also has the Alarm Dialler attached. The "Forced Door" alarm Contact ID message will then be sent twice, (i.e. once for each priority).
4. When the event is escalated to a higher priority, you can set outputs to operate by dragging and dropping those required into the **Outputs** grid.
5. Drag and drop the DVR Cameras (Gallagher or third-party), Macros and/or External System Items to be triggered into the **Cameras, Macros, and External System Items** grid.

   **Note:** When the Action plan is executed:

   * The footage recorded by the cameras in this grid at the time of the event/alarm is associated with the event/alarm. As a result, when viewing an event/alarm in Command Centre client, a camera tile can show footage taken by these cameras at the time which the alarm occurred.
   * The string(s) on the **Trigger -- Events** tab of the cameras and External System Items in this grid are sent to those devices’ third-party systems.
   * The Macros in this grid are run. Note that Macros that run a bulk change will not occur from an Action Plan.

</details>

<details>

<summary>Command Centre tab</summary>

1. Click the **Command Centre** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f9b2270e5d43ffc3c4dc9c479e7c9e8201da87f7%2Ftab_commandcentre.png?alt=media)
2. Specify the priority of events or alarms generated, from the **Alarm Priority** drop-down list.

   When an event occurs the response will be of this priority.

   **Note:**

   The drop-down list will be populated with alarm priority names configured for the overall Command Centre system.
3. Drag and drop the macro(s) to be triggered if this Action Plan causes an alarm to be generated, into the **Macros** grid.

   **Note:** Macros that run a bulk change will not occur from an Action Plan.

</details>

5. Click the **Custom Fields** tab if you want to add and assign a custom field value to this Action Plan.

   For further details regarding the **Custom Fields** tab, see [Custom Fields](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/custom-fields.md).
6. 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).
7. Click **OK** to exit and save your changes.

   Click **Cancel** to exit without saving your changes.

   Click **Apply** to save your changes and stay in this window.

### Result

A new Action Plan is created.

When an event is generated - that is linked to this Action Plan, those cameras and outputs will activate and an alarm message is displayed to the operator - with the set priority. If the alarm is not acknowledged it will escalate in priority.

**Note:** All macros that run from an Action Plan should be tested to ensure they do not cause a loop to occur. If a loop is triggered, either delete the macro from the Action Plan or set the Alarm Priority to 'Not an Event'.

***

### Deleting Action Plans

Refer to [Deleting items](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/deleting-items.md) for the procedure on how to delete an Action Plan.


---

# 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/action-plans/creating-a-new-action-plan.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.
