> 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/functionality-provided-by-alarm-input-test-modes.md).

# Functionality provided by Alarm Input Test Modes

The Alarm Input Test Modes feature provides the following functionality:

### Periodic Testing

Periodic Testing occurs when a staff member authorised to perform Periodic Test Mode disarms the system using a Gallagher terminal. The staff member can then choose to enter Test Mode or disarm as usual.

There is a configurable time of one to thirty days for which the test is optional. After the configurable time, the test is no longer optional.

The staff member is then required to check that all inputs configured for testing are functioning correctly. They do this by activating each input.

At any time during Test Mode it is possible for the staff member to end the test manually using the terminal. When this happens an email is sent to the manager advising that the test was aborted.

The test will need to be completed within a configurable length of time. The time left displays as a countdown on the terminal. An audible warning will sound with one minute to go and the staff member is given the opportunity to extend the testing time.

If all the inputs are successfully activated before the timeout, the terminal provides an indication that all inputs have been successfully tested. When the test completes, the system disarms and a report is sent to the alarm monitoring company and an email is sent to the manager.

If one or more inputs failed to activate before the test timeout, the test completes and the system disarms. The terminal lists all the inputs that failed the test, a report is sent to the alarm monitoring company and an email is sent to the manager for each input that failed to activate during the test.

### Manual Testing

Manual testing allows inputs to be tested without changing the state of the Alarm Zone.

A staff member or technician will be able to put areas of the system into Test Mode whilst tests are carried out. The terminal will indicate if the input is functioning correctly and no alarm will be raised during this time.

### Mask Testing

Mask Testing raises an alarm for inputs that haven't been activated within a specified period of time. The intention of this test is to identify any devices that are not working, (e.g. PIRs or door sensors).

When a configured input hasn't been activated at least once within the period of time an alarm will be raised, a message will be sent to the alarm monitoring company and an email will be sent to the manager.

### Seismic Detector Testing

Vibration devices and seismic detectors can be used to detect vibrations and/or possible attacks, (e.g. drilling or similar in a bank vault). The Controller will trigger the vibration devices that will then trigger the seismic detectors. A failed test is one where the Controller triggers the vibration devices and the seismic detectors fail to detect it. Any failed tests will raise an alarm, be reported to the alarm monitoring company and emailed to the manager.

Alarms from the seismic detectors will not be raised during testing.

### Restricted Disarming

It is possible to configure groups of staff members within the Alarm Zones they are allowed to disarm and the times they can disarm them for, (e.g. cleaners).

### Timed Disarm

It is possible to configure groups of staff members with the period of time they are allowed to disarm Alarm Zones for.

### Remote Arming and Disarming

It is possible for the system to be remotely armed or disarmed by the alarm monitoring company.

### Auto-Processing Alarms

This feature allows Command Centre to automatically process all alarms that are both inactive and acknowledged. This service can be switched On or Off as required. (By default the service is Off.)

### Multi-Break Alarms

It is possible for an input to send an alarm to the alarm monitoring company every time it transitions. When the input is sealed again, a restoral event is sent.

Alternatively, it is possible to latch alarm inputs that are sent to the alarm monitoring company. This means that only one alarm will be sent to the alarm monitoring company per input and the restoral event will not be sent until the alarm is acknowledged.


---

# 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/functionality-provided-by-alarm-input-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.
