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

# Understanding Action Plans

### What is an Action Plan?

An Action Plan defines what is going to happen when an event in your security system occurs. When an event occurs the Action Plan defines the following:

* Assigns an alarm priority (e.g. message only, high priority, etc.)
* Operates the appropriate outputs, Digital Cameras and/or macros
* Escalation time

### Types of Action Plans

There are two different types of events in Command Centre, (i.e. Command Centre events and Controller events), for which the alarm behaviour can be configured via Action Plans. To configure an Action Plan for a specific type of event, use only the relevant property pages (tabs), as follows:

<table><thead><tr><th width="113.111083984375">Event Type</th><th width="210.77777099609375">Action Plan tabs to configure</th><th>Description</th></tr></thead><tbody><tr><td>Command Centre</td><td><strong>Command Centre</strong> tab</td><td>Command Centre events can be created by any part of Command Centre, (e.g. workstation, central server, communications server, etc.).<br>Command Centre is responsible for executing Action Plans for all Command Centre events. The only Action Plan behaviour supported for Command Centre events is configurable alarm priorities and automatically triggered macros. In addition, the Action Plan's 'Command Centre' configuration is always used, regardless of the state of the Alarm Zone.</td></tr><tr><td>Controller</td><td><strong>Armed</strong> (or <strong>Set</strong>) tab<br><strong>Disarmed</strong> (or <strong>Unset</strong>) tab<br><strong>User 1</strong> tab<br><strong>User 2</strong> tab<br><strong>Escalation</strong> tab</td><td>The Controller is responsible for executing Action Plans for Controller events. If the Action Plan cannot be fully handled by the Controller, (e.g. if it is configured to generate a report), then the Controller sends a message to the Command Centre to trigger the 'Command Centre' part of the Action Plan.</td></tr></tbody></table>

**Notes:**

* The **General** tab should also be configured for all event types, and the **Notes** tab if required.
* To find out what generates an event, (i.e. Command Centre or Controller), refer to the "Event/Alarm Messages" online help file via the **Help** menu bar in Command Centre.

### Which Action Plan to follow?

Every possible event that can occur within the system can be linked with an Action Plan. You link the Action Plan within the Event Response tab:

* Some events may require no action.

  For example: when an employee opens a window during working hours, no event is recorded. This event type is linked to the Action Plan "No event recorded".
* Specific events may require a specific Action Plan.

  An Action Plan is assigned to the event at the site item level.

  For example: Security lighting switches on and a message is generated when staff exit from the staff entrance.
* Events can be set to respond to default Action Plans.

  The following diagram shows the hierarchy Command Centre follows when determining which Action Plan takes priority.

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

### Escalation

If, after a preset time, the guard has not acknowledged the alarm, the alarm will automatically be escalated in priority.

**Note:** When an Alarm Zone changes state, (e.g. from *Disarmed* to *Armed*), where *Armed* uses escalation rules, the alarm will not always escalate. There are two situations where the behaviour is different, but in both cases escalation does not take place. They are:

* Where the Action Plan is set up for *Disarmed* as 'Message Only', going to *Armed* which is 'Low Priority', escalating to 'High Priority' if the input is still active after 10 seconds.
* Where the Action Plan is set up for *Disarmed* as 'Low Priority', going to *Armed* which is 'Medium Priority', escalating to 'High Priority' if the input is still active after 10 seconds.

Escalated alarms can be shown in a separate viewer from the main Alarm Viewer. For further details regarding the "Escalated Alarm Viewer" see [Alarm Viewers](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-monitoring/alarm-viewers/understanding-the-alarm-viewers.md).

### Link with Alarm Zones

The Action Plan to follow may differ depending on the state of the Alarm Zone the item is grouped with.

For example:

* During working hours, when the Alarm Zone is Unset/Disarmed, only a message is necessary.
* After hours when the Alarm Zone is Set/Armed, a high priority alarm is generated.


---

# 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/understanding-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.
