> 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-monitoring/alarm-input-test-modes/configuring-alarm-zones-for-test-modes.md).

# Configuring Alarm Zones for Test Modes

### Introduction

This procedure describes how to configure each Alarm Zone that requires testing.

### Procedure

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

   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** on the appropriate Alarm Zone and select **Properties**.
3. Click the **Testing** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-39477d7699d7a44b2e11a2cf9d6d80fba8daa923%2Falarmzone_testingtab.png?alt=media)
4. In the **Test mode time-out** field, enter the number of minutes required to complete the test.

   (Default = 15 minutes. Configurable from 1 to 60 minutes.)

   In the example above, the test will timeout after 15 minutes.

   The time left will be displayed as a countdown on the terminal. An audible warning will sound with one minute to go and the staff member will be given the opportunity to extend the testing time.

   When the test is extended, the time to complete the test will revert back to the original time period configured. The test can be extended multiple times.
5. Check the **This zone may be tested during disarming** checkbox.
6. In the **Maximum test postponement** field, enter the maximum number of days that can pass before a mandatory test is required.

   (Default = 7 days. Configurable from 1 to 30 days.)

   In the example above, after 7 days the test is no longer optional.
7. Does the Alarm Zone contain vibration devices?

   If **yes**, go to Step 8.

   If **no**, go to Step 11.
8. Drag and drop Drag and drop the vibration devices (outputs) you require to trigger during the pre-arm timeout period into the grid.

   **Note:** These outputs must be set to pulse when triggered.
9. Click the **Alarm Warnings** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-02869a96d65d74d82fddfe3f09d651e3463ef90a%2Falarmzone_alarmwarningstab.png?alt=media)
10. In the **Pre-Arm Timeout** field, enter an appropriate period that you want Controllers to ignore alarms for, (i.e. 0-60 seconds).

    **Note:** The pre-arm timeout period will need to allow enough time for the vibration devices to settle before any alarms are raised. A pre-arm timeout value of approximately 10 seconds is suggested.
11. Click the **OK** button to exit and save your changes.
12. Repeat this procedure for each Alarm Zone that requires testing.


---

# 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-monitoring/alarm-input-test-modes/configuring-alarm-zones-for-test-modes.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.
