> 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/server-properties/alarm-flooding.md).

# Alarm Flooding

### Introduction

Alarm Flooding occurs when the same alarm is generated numerous times and fills up the Alarm Viewer window. Alarms qualify as "Flood Alarms" when the following conditions apply:

* There exists a previous alarm which has the following identical fields:
  * Priority
  * Source
  * Event Type
  * In the case of Card alarms, the card details (card number, facility code) must also be matched
* The alarm occurs within a specified number of seconds after the previous alarm. Where the number of seconds is the "tolerance" for the priority at which the alarm occurred.
* The previous alarm has not been acknowledged.

This procedure allows you to specify time periods during which Command Centre will summarise multiple occurrences of the same alarm. Operators require the "Edit Site" operator privilege to perform this procedure.

### Procedure

1. Open the **Command Centre Server Properties** window. [How?](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/opening-the-server-properties-window.md)
2. Click the **Alarm Flooding** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-4f5b28659c9a5c28ace1b9ba30e54c34e5af8827%2Falmfloodtab.png?alt=media)
3. Enter times (in seconds) in the **Tolerance** column for the Alarm Priorities required. If you set the tolerance time to 0, alarm flooding will not operate for that priority of alarm.

   The **Tolerance** time is the period of time allowed between repeated alarms to constitute an Alarm Flood. Repeated alarms that occur outside of the tolerance time will constitute new alarms, whereas unprocessed repeated alarms inside the tolerance time will become part of an Alarm Flood.
4. Enter times (in minutes) in the **Forget Interval** column for the Alarm Priorities required.

   The purpose of the **Forget Interval** time is to remind operators that an alarm is still occurring, therefore if a new occurrence of an alarm occurs after the **Forget Flood Interval** time specified, the alarm (flood) is moved to the top of it's priority in the Alarm Viewer window.

   **For example:**

   If the Forget Flood Interval is set to 10 minutes, and an alarm occurs at 2:00pm and keeps reoccurring, the first occurrence of the alarm after 2:10pm will move the alarm flood to the top of it's priority in the Alarm Viewer window.
5. Select the appropriate option from the **Multi-breaks** drop-down lists, for the Alarm Priorities required.

   <table><thead><tr><th width="96">Option</th><th>Description</th></tr></thead><tbody><tr><td>Enabled</td><td>Each alarm activation and restoral is transmitted. This is the default behaviour.</td></tr><tr><td>Latched</td><td>Only the first activation of an alarm from any one source is transmitted and the restoral is sent according to the Action Plan's Deactivate rule. If the Alarm Zone changes from its known state to any other state, then multi-breaking will be reset.</td></tr><tr><td>Unlatched</td><td>When Unlatched is selected, the <strong>Threshold</strong> field becomes enabled. This setting allows the number of alarms whose activation and restoral is transmitted to be changed from 1 only to a nominated number up to 10 before multi-breaking is reset. Multi-breaking will also be reset on expiry of the confirmation time if ‘Enable confirmed alarms’ is selected on the <strong>Standards</strong> tab.<br>If the <strong>Threshold</strong> is set to '1', only the first alarm activation and restoral is transmitted. If the Alarm Zone changes from its known state to any other state, or the alarm is acknowledged, then multi-breaking will be reset.</td></tr></tbody></table>
6. 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

The selected Tolerances and Forget Flood Intervals have been configured.


---

# 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/server-properties/alarm-flooding.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.
