> For the complete documentation index, see [llms.txt](https://docs.buildings.ability.abb/collection/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildings.ability.abb/collection/english-v14/documentation/alarms-rules-and-escalations/escalations/group-escalations.md).

# Group escalations

## Overview

If many alarms are triggered within a short period of time, this can lead to a flood of notifications. To avoid this, alarms can be combined within an escalation. In this process, several incoming alarms are consolidated into a single escalation message, depending on individually defined conditions. In addition, certain alarm tags can be excluded from the combination, so that these continue to be escalated individually.

### Procedure

<div data-full-width="true"><figure><img src="/files/0241e26fb4dc5ca8923c18c98a8e67b6cdc7655c" alt=""><figcaption></figcaption></figure></div>

1. Click on *Engineering* **\[A]**
2. Click on *escalation* **\[B]**

   ▷ The overview of the escalation configurations opens.
3. Click on **\[D]**\
   ▷ The window opens *Combining alarms* **\[D1]**.
4. Activate the switch **\[D2]**, to activate the combining of alarms.
5. Enter under **\[D3]** the period in seconds within which the alarms must occur in order to be combined.
6. Enter under **\[D4]** the minimum number of alarms that must occur within the defined period for them to be combined.
7. Select under **\[D5]** the alarm tags that should be excluded from the combination (e.g. *High Prio*).
8. Click on **Save** **\[D6]**, to apply the changes.

### Example

**Conditions:**

* Period: **10 seconds**
* Minimum number: **5 alarms**

**Scenario 1:**\
Within 8 seconds, 5 alarms are triggered without excluded tags → **The alarms are combined** and sent as a single escalation message.

**Scenario 2:**\
Within 10 seconds, 4 alarms are triggered → **No combination**, 4 separate escalation messages are sent.

**Scenario 3:**\
Within 10 seconds, 7 alarms are triggered, 2 of them with the tag *High Prio* (excluded) → The 5 remaining alarms are combined, the 2 *High Prio*-alarms are escalated individually.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.buildings.ability.abb/collection/english-v14/documentation/alarms-rules-and-escalations/escalations/group-escalations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.