> 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/alarm-zones/setting-up-alarm-zones.md).

# Setting up Alarm Zones

### Introduction

You need to create an Alarm Zone for each grouping of objects or entities whose states need to be armed and disarmed together.

This procedure is split into three parts, as follows:

* Creating an Alarm Zone,

  (i.e. providing the minimum information required to create a new Alarm Zone)
* Configuring an Alarm Zone,

  (i.e. linking the various components to it - Divisions, Schedules, Action Plans and Alarm Instructions are the components of an Alarm Zone).
* Initialising Alarm Zone functionality,

  (i.e. associating inputs with the Alarm Zone so they recognise any Alarm Zone state changes).

You can create a new Alarm Zone, then configure it at a later stage, once you have set up the necessary components for it.

**Note:** To maintain system integrity in the event of a communications failure, it is recommended that you have an independent Default Alarm Zone for each Controller, and that entities used in an Alarm Zone are from the same Controller, where possible. Although it is physically possible to use entities from different Controllers to build Doors or Alarm Zones, if there is a communications failure, access or intruder alarm monitoring can be compromised.

***

### Configuration

To configure an Alarm Zone, perform the following procedures in Gallagher Configuration Client:

#### Creating the Alarm Zone

1. Click **Configure** from the menu bar, then **Alarm Zones**.

   The **Alarm Zone** 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\...Alarm Zone**.

   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 **Apply** button, and the Alarm Zone is created.

   The rest of the procedure allows you to fully configure the Alarm Zone.

#### Configuring the Alarm Zone

5. Ensure the following information has already been set up:

   *Divisions*

   Refer to "[Setting up System Division](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/system-division/setting-up-system-divisions.md)".

   *Schedules*

   (if you want Alarm Zone state changes to be controlled by Schedules)

   Refer to "[Schedule](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/schedules.md)".

   *Action Plans*

   Refer to "[Creating a new Action Plan](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/action-plans/creating-a-new-action-plan.md)".

   *Alarm Instructions*

   Refer to "[Creating a new Alarm Instruction](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/alarm-instructions/creating-a-new-alarm-instruction.md)".
6. Select the appropriate Division from the drop-down list.
7. Click each tab in turn and configure the Alarm Zone properties as required:

<details>

<summary>Event Defaults tab</summary>

1. Click the **Event Defaults** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-b4ef52d91c9adc9f27ada2c8322efbeb2e20e5c6%2Feventdefaults.png?alt=media)
2. Assign the appropriate Action Plan to the desired Event type.

</details>

<details>

<summary>Alarm Instruction Defaults tab</summary>

1. Click the **Alarm Instruction Defaults** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-75f3521b1f079bc35ba2f3209d4356b69873b6a6%2Falminstdefaults.png?alt=media)
2. Assign the appropriate Alarm Instruction to the desired Event type and group.

   Once the Alarm Zone has been created and configured, it is necessary to go to the associated hardware, (e.g. PIR's), and put them in the Alarm Zone.

   **Note:** For the Alarm Zone "State Change" to activate and the "Reflect Output" to initiate, (i.e. switch on), there **must** be either an input, output, door or Controller in the Alarm Zone.

</details>

<details>

<summary>Connections tab</summary>

1. Click the **Connections** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-473c673991dce81c1027401d5b5db104388b4f98%2Falarmzone_connections.png?alt=media)
2. Select the appropriate Controller from the drop-down list, (i.e. the Controller that has the majority of site items on this Alarm Zone).

   **Note:** A Controller must be selected in order for the state of the Alarm Zone to be set.
3. The Items grid shows a "Read-only" list of all Command Centre items that are connected to or contained in the Alarm Zone, (i.e. connected via their **Event Response** property page).

   If you want to add any items to the grid, refer to [Adding multiple items to Alarm Zones](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/alarm-zones/adding-multiple-items-to-alarm-zones.md) for the procedure.

</details>

<details>

<summary>State Changes tab</summary>

1. Click the **State Changes** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-c6c6ceca6fe1c1e940122626e6ec63f20141eca6%2Fazstates.png?alt=media)
2. Click the appropriate radio button, i.e. (Manually Controlled, Schedule Controlled or Key-Switch Controlled), to indicate what controls the Alarm Zone state change.

   <table><thead><tr><th width="177">Select...</th><th>if the Alarm Zone is to...</th></tr></thead><tbody><tr><td>Manually Controlled</td><td>only have it's state changed using either a terminal, any reader or a pushbutton attached to Command Centre. It will not be affected by Schedule changes.</td></tr><tr><td>Schedule Controlled</td><td>be set and unset automatically.<br>To configure the times at which the Alarm Zone sets and unsets, assign the appropriate schedule from the <strong>Change state according to</strong> drop-down list.<br>For the <strong>Manual Unset Timeouts</strong>, enter the expiry times (range is 0-1440 minutes, i.e. max 24hrs) for each of the states that the Alarm Zone can be manually overridden via a terminal, any reader or a pushbutton, before the Alarm Zone tries to go back into the Scheduled state.<br><br><strong>Note:</strong> The Alarm Zone state change can be configured so that the length of the expiry period depends on the time of day that the manual override takes place. For example, when a manual override (unset) occurs out of hours the override expiry might be 30 minutes, whereas if the unset takes place during office hours (between 9am-5pm), the expiry period is ignored. At the end of normal office hours the alarms are again set by the schedule.<br>When the override timeout tries to go to Scheduled state it will use the exit/entry delay as usual.<br>If the manual override timeout is set to zero, this means it is disabled.<br><br><strong>Note:</strong> Schedules are configurable and can have alarms set for 24 hours or unset for 24 hours.<br>If the Alarm Zone is to be set and unset by Cardholders who have the appropriate Cardholder privileges, then the default state of the Alarm Zone should be "Set 24 hours". This is assigned by selecting a schedule from the <strong>Change state according to</strong> drop-down list that has been configured with the Alarm Zone state "Set 24 hours".<br>The Alarm Zone is then only unset by a Cardholder when badging their card at the entry reader for the zone. The Alarm Zone can then be set by a Cardholder performing a local override at a reader.</td></tr><tr><td>Key-Switch Controlled</td><td>be manually set and unset using keyswitches, (i.e. inputs).</td></tr></tbody></table>

   **Note:** New alarm zones will remain permanently disarmed until one of these modes is selected to determine their state. If it is required for an alarm zone to be permanently disarmed, then an appropriately configured schedule should be provided.
3. In the **If state change fails retry after** box, enter the appropriate time. If the alarm zone state cannot be changed for any reason, the set attempt will be repeated at intervals equal to this time. (Range is 0-10 minutes, although a setting of 0 minutes will mean the Alarm Zone will never retry after state change failure.)

   **Notes:**

   * This figure should be increased if repeated alarm zone state change failed alarms occur with details of "Network failure".
   * If this Alarm Zone is dependant on other Alarm Zones, then this figure should be as low as possible, (e.g. If this figure is set to 1, and the Controller hosting this Alarm Zone resets, then this dependant Alarm Zone will attempt to set within 1 minute).

</details>

<details>

<summary>HV/LF Mode tab</summary>

Configuration on this tab is only required if this Alarm Zone is going to be assigned to a Fence Zone associated with an F31, F32, F41, F42 or F22 Fence Controller.

**Note:** This tab will only be displayed if your site is licensed for Fence Controllers.

1. Click the **HV/LF Mode** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-1938e5145426646c444ed9c048e8099361632b51%2Fhvlfmodetab.png?alt=media)
2. Click the appropriate radio button, (i.e. Manually Controlled, Schedule Controlled or Key-Switch Controlled), to indicate what controls the HV/LF mode change.

   <table><thead><tr><th width="156">Select...</th><th>if the Alarm Zone is to...</th></tr></thead><tbody><tr><td>Manually Controlled</td><td>change between High Voltage and Low Feel using only a terminal attached to Command Centre. It will not be affected by Schedule changes.</td></tr><tr><td>Schedule Controlled</td><td>change between High Voltage and Low Feel automatically.<br>To configure the times at which the Alarm Zone changes between High Voltage and Low Feel, assign the appropriate HV/LF Schedule from the <strong>Change state according to</strong> drop-down list.<br><br><strong>Note:</strong> An HV/LF Schedule is configurable and can be set to High Voltage for 24 hours or Low Feel for 24 hours.<br>if the Alarm Zone HV/LF mode is to be changed by Cardholders who have the appropriate privileges, then the default mode of the Alarm Zone should be "High Voltage" for 24 hours.</td></tr><tr><td>Key-Switch Controlled</td><td>be manually changed between High Voltage and Low Feel using keyswitches, (i.e. inputs).</td></tr></tbody></table>

   **Note:** When a new Alarm Zone is created, the default HV/LF mode is High Voltage for 24 hours. If it is required for an Alarm Zone HV/LF mode to be Low Feel for 24 hours, then an appropriately configured schedule should be provided.

</details>

<details>

<summary>Advanced tab</summary>

1. Click the **Advanced** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-41c16f8967d98063e5af46690850ed401dd4c83c%2Faz_advanced.png?alt=media)
2. Click the appropriate radio button for the required option.

   <table><thead><tr><th width="222">If you click the...</th><th>this means that the...</th></tr></thead><tbody><tr><td><strong>Force arm</strong> radio button,</td><td>Alarm Zone will be forced to change state even if this would generate an alarm.<br><strong>IMPORTANT:</strong><br>The Alarm Zone will fail to change state if the Alarm Zone is spanned over multiple Controllers, and one or more of the Controllers goes offline.</td></tr><tr><td><strong>Isolate inputs</strong> radio button,</td><td>Inputs will stop generating alarms until the next state change. The Inputs will however still be capable of triggering other activity.<br>If an exit path is configured and a point on the exit path in alarm state, the isolation should occur at the end of the exit delay as this is when these points are Armed.<br>If an exit path is configured and a point <strong>not</strong> on the exit path in alarm state, the isolation should occur at the <strong>beginning</strong> of the exit delay as this is when these points are Armed.</td></tr><tr><td><strong>Fail to arm</strong> radio button,</td><td>Alarm Priority on the <strong>Disarmed</strong> tab of the corresponding Action Plan must be of a lower priority, (i.e. message only), for this function to work.</td></tr></tbody></table>
3. If you want to prevent the Alarm Zone from arming because of either **Unacknowledged alarms** and/or **Active alarms** in the zone, tick the checkbox(es) as appropriate.
4. Select the appropriate **Force-arm option**.

   **Note:** The **Force-arm options** control what will happen if a Force Arm is initiated at a terminal, and whether or not the relay is triggered, (i.e. the other alarm actions are still done regardless of which option is chosen). The **Force-arm options** allow for the situation where it is not desirable for a force-arm to trigger the relay, (e.g. when being force-armed from a terminal on site by a guard, the guard would not want the sirens to go off, but would want the monitoring station to know that the alarms had been armed).

   <table><thead><tr><th width="373">If an...</th><th>then the...</th></tr></thead><tbody><tr><td>exit path is configured and a point on the exit path in alarm state,</td><td>isolation should occur at the end of the exit delay as this is when these points are Armed.</td></tr><tr><td>exit path is configured and a point <strong>not</strong> on the exit path in alarm state,</td><td>isolation should occur at the <strong>beginning</strong> of the exit delay as this is when these points are Armed.</td></tr><tr><td>exit delay is configured and the Alarm Zone is force armed due to a point being in alarm state,</td><td>relays associated with the point in alarm will not be triggered.</td></tr><tr><td>exit delay is configured and a point goes into alarm state during the exit delay,</td><td>relays associated with the point in alarm <strong>will</strong> be triggered.</td></tr></tbody></table>
5. Click the appropriate **Exit Delay** radio button, so in the event of an alarm occurring that is either:

   * **not** on the exit path, and the alarm occurs during exit delay, or
   * **on** the exit path, and still in alarm at the end of exit delay, then

   at the end of the exit delay, depending on your configuration, Command Centre will check if the Alarm Zone is still able to arm.

   The **Start of exit delay** radio button is selected by default. However, if either the **EN50131 Complaince** or **SSF1014 Compliance** checkbox on the **Standards** tab of the Server Properties is checked, then the **Start and end of exit delay** radio button will be selected.
6. Indicate a **Network timeout** in seconds, and tick the **Notify restoral** checkbox if required.

   The Notify restoral behaviour applies to all points within an Alarm Zone which may enter an alarm state, (e.g. door open too long, forced door), and will cause an alarm to be raised on both the open and closed events for this Alarm Zone.

   Refer to [Notify Restoral](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-monitoring/alarm-viewers/notify-restoral.md) for further explanation.

</details>

<details>

<summary>Dependencies tab</summary>

1. Click the **Dependencies** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-1e80bdba9acb8479f5607cceb8d926d4efb952bf%2Fazdependencies.png?alt=media)
2. Drag and drop the Alarm Zones (a maximum of 20), that this Alarm Zone is to be dependent on.
3. The two checkboxes allow you to configure whether this Alarm Zone will automatically arm when all dependent zones are armed, automatically disarm when any dependent zone is disarmed, neither, or both.

   Tick or untick the option(s) as required.

</details>

<details>

<summary>Pushbuttons tab</summary>

1. Click the **Pushbuttons** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-1601d1ac10e174365ae227a3816dbeab31e29df5%2Fpushbutton.png?alt=media)
2. Drag and drop an Input to use as a pushbutton to override the Alarm Zone to it's "Armed" or "Disarmed" state for Pushbutton exits.

   Inputs should normally be wired open as the zone will change state on the transition between open and closed. If this does not suit, the input can be inverted and the alarm will change state as it goes closed to open.

   **Note:** State changes made by Inputs on this property page will be overridden by scheduled state changes.

</details>

<details>

<summary>Entry Delay tab</summary>

1. Click the **Entry Delay** tab.

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

   If you unset an Alarm Zone using a Reader or Pushbutton, and that Reader or Pushbutton is physically located inside the Alarm Zone, you need to set a **Delay Time** for "While Armed" and add a device as the Entry Point by dragging it into the **Device(s) to use as Entry Points** grid. (An Entry Point can be an Input or a Fence Zone that triggers an entry delay by opening. It does not have to be in the same zone as the zone that has the entry delay.)

   By default the **Entry Delay Time** is 0 seconds and all state checkboxes are unchecked.

   **Note:** You cannot specify an entry delay time without checking at least one state checkbox. Likewise, if you check any of the state checkboxes you must specify an entry delay time.
2. If unsetting is completed from within the Alarm Zone, a route from the entry point to the means of unsetting needs to be defined under **Device(s) to ignore when entering**. This can be achieved by either:

   * clicking the **All Devices in Zone** radio button (which is the default), OR
   * clicking the **Specific Devices in Zone** radio button and dragging the required entry route inputs (and the entry point input) into the grid.

   During entry delay, input activations from the entry route will be ignored while all other zone input activations will cause immediate alarms according to their Action Plan setup.

</details>

<details>

<summary>Exit Delay tab</summary>

1. Click the **Exit Delay** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-c769d6bfea6a287d3609891d5f65d508253c01c6%2Fazexit.png?alt=media)
2. If you set the Alarm Zone using either a Reader or a Pushbutton that is located inside the Alarm Zone, you need to configure **Delay Times** to provide enough time to exit the zone before the Inputs activate an alarm.

   Ensure the **Use exit delay** radio button is selected, and enter an appropriate delay time.

   By default the **Delay Time** is 0 seconds and all state checkboxes are unchecked.

   **Note:** You cannot specify an exit delay time without checking at least one state checkbox. Likewise, if you check any of the state checkboxes you must specify an exit delay time. See [Alarm Zone States](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/alarm-zone-states.md) for further detail.
3. If you do **not** want the exit delay to timeout, select the **Use confirmed exit** radio button. This will cause the Alarm Zone to have an exit delay that does not timeout, but only completes when one of the exit points activates.

   **Important:** With the **Use confirmed exit** mode selected, the zone will never set if one of the exit points does not activate. For this reason, this mode should never be used for zones that have an arming schedule defined, as there is no guarantee that someone else will be present at the time of auto-arming (to terminate the exit delay), and therefore the zone may not set.
4. Drag any Inputs, (e.g. Door Sensor), into the **Device(s) to use as Exit Points** box to end the Exit Delay period. This removes the need for people to wait longer than is needed to verify the Alarm Zone is set. The Exit Delay will cancel and the zone will arm when the exit point closes.

   **Note:** Inputs that have already been used as Entry Points on the **Entry Delay** tab can also be used as Exit Points on this tab. Because entry delays are triggered by 'Input Open' events and exit delays are ended by 'Input Closed' events, these cases can be distinguished.

   If an Input is used for both entry and exit delay, the Input and the Alarm Zone must co-exist on the same Controller.
5. Under **Device(s) to ignore at the time of**, configure a list of devices which will be ignored either when a request is made to arm the Alarm Zone or during the arming and while exiting from the Zone.

   If you select the **Arming and Exit Delay** option the Exit Path will be made up of any devices in the 'Ignored devices' grid plus any devices in the ‘Exit Points’ grid.

   If you select the **Arming (during Exit Delay, all devices are ignored)** option (which is the default), all devices in the Alarm Zone will be ignored during Exit Delay regardless of what has been put into the 'Ignored devices' grid.

   **Notes:**

   * Exit path configuration is supported by Controller 6000s and 7000s.
   * It is recommended you do this if your site has PIRs facing terminals, or card readers used to set alarms.
   * If you do not have the "Isolate" privilege, the arming will fail.

</details>

<details>

<summary>Delay Warnings tab</summary>

1. Click the **Delay Warnings** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-0cc691690d490a039b5df15497f5f660c50d60e3%2Fazdelay.png?alt=media)
2. Configure **Readers, Terminals** and **Outputs** as required (drag and drop).

   These items will now provide an audible indication of an entry/exit delay event.

</details>

<details>

<summary>Reflect Outputs tab</summary>

1. Click the **Reflect Outputs** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-9f35a1419049b4831429a5672400652ff43a25bb%2Fazreflect.png?alt=media)
2. Configure **Outputs** as required (drag and drop).

   Outputs turn on while in the Alarm Zone state the outputs are placed in.

</details>

<details>

<summary>Alarm Warnings tab</summary>

1. Click the **Alarm Warnings** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-09397e342279eb86652e5d5cfdfd37b2214100de%2Fazalarmwarning.png?alt=media)
2. Configure **Readers, Terminals** and **Outputs** as required (drag and drop).

   These items will now be activated during exit delay when potential alarms are present.
3. In the **Pre-arm Timeout** box, enter an appropriate period that you want Controllers to ignore alarms for, (i.e. 0-60 seconds).

   **Note:** A pre-arm timeout will need to be configured if the Alarm Zone is being used to control the state of Fence Zones. The pre-arm timeout will allow enough time for the Fence Zones to turn on and measure their output voltage before any alarms are raised. A value of approximately 5 seconds is suggested

</details>

<details>

<summary>Confirmed Alarms tab</summary>

1. Click the **Confirmed Alarms** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-9deee9fcc50241625529c48c76e4cfa1da17dc3c%2Fazconfirmedalarms.png?alt=media)
2. If you want to disable confirmed alarms, drag any devices, (e.g. Door Sensor), into the **Device(s) that disable confirmation in zone** box.

   This disabling of confirmed alarms shall apply until the zone is disarmed (or changed to some other state) and then re-armed. If entry delay expires, the zone status will show as "Zone is armed. Alarms are INHIBITED." If 'Re-enable confirmation if entry delay expires' is **not** enabled, or "Zone is armed. Entry delay expired.".
3. If you want granting access to disable the sending of confirmed alarms, check the **Access granted disables confirmation in zone** checkbox.
4. Check the **Re-enable confirmation if entry delay expires** checkbox if required. When checked, instead of confirmed alarms being inhibited, confirmed alarms will still occur after entry delay has expired.

   **Note:** Items on this page will only affect the system if "Enable Confirmed Alarms" is selected on the **Standards** page of the Server Properties. See [Standards](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/standards.md) for further detail.

</details>

8. Click the **Cameras** tab if you want to associate a DVR Camera(s) with this Alarm Zone.

   For further details see [Cameras tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/cameras-tab.md).
9. Click the **Icons** tab if you want to change the Icon Set for this Alarm Zone.

   For further details regarding the **Icons** tab, see [Icons](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/icons.md).
10. Click the **Custom Fields** tab if you want to add and assign a custom field value to this Alarm Zone.

    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).
11. Click the **Notes** tab if you want to add a note(s) about this Alarm Zone.

    For further details regarding the **Notes** tab, see [Notes](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/notes.md).
12. 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.

#### Initialising Alarm Zone functionality

Once the Alarm Zone configuration work is complete, you need to associate the inputs, (e.g. PIRs, reed switches, etc.) with the Alarm Zone so they recognise any Alarm Zone state changes.

**Note:** The Inputs need an appropriate Action Plan assigned to them. Refer to [Creating a new Action Plan](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/action-plans/creating-a-new-action-plan.md) for details.

13. Click **Configure** from the menu bar, then **Hardware**.
14. Select the appropriate input.
15. **Right click** and select **Properties**.
16. Click the **Event Response** tab, and select the Alarm Zone that the input should be associated with.

    The Access Zone(s) that the inputs are in, (i.e. physical areas that they are located), must also be associated with the Alarm Zone. The Access Zone must recognise the set and unset state of the Alarm Zone to prevent accidental cardholder entry into an Access Zone with set alarms.
17. Click **Configure** from the menu bar, then **Access Zones**.
18. Select the Access Zone the inputs are in.
19. **Right click** and select **Properties**.
20. Click the **Event Response** tab, and select the Alarm Zone that the input should be associated with.

### Result

A new Alarm Zone is configured and will operate under the command of the Alarm Zone configuration as established.

***

### Editing and Deleting Alarm Zones

Refer to [Editing items](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/editing-items.md) and [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 procedures on how to edit and delete Alarm Zones.


---

# 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/alarm-zones/setting-up-alarm-zones.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.
