> 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/platform/platform-core/alert-and-escalation/escalations/configure-an-escalation.md).

# Configure an Escalation

## Overview

The "Configure Escalation" menu is divided into 5 elements.

<figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2Fu0fCYGOItbO5Z8Mq5hTU%2FGroup%20648.png?alt=media&amp;token=dd966962-8634-4ab1-b32b-ae6e4bc1ff20" alt=""><figcaption><p>Fig. 1 – The "Configure Escalation" menu in an empty state</p></figcaption></figure>

<table><thead><tr><th width="74.33333333333331"></th><th width="170"></th><th></th></tr></thead><tbody><tr><td><strong>[A]</strong></td><td>Escalation Name</td><td>Here you can adjust the name of the escalation afterward</td></tr><tr><td><strong>[B]</strong></td><td>General Calendar</td><td>Here you select the General Calendar.</td></tr><tr><td><strong>[C]</strong></td><td>Tags for Escalating</td><td>Here you specify which alarms are escalated.</td></tr><tr><td><strong>[D]</strong></td><td>Tags with Users and Destinations</td><td>Here you specify to which users an alarm is escalated.</td></tr><tr><td><strong>[E]</strong></td><td>Calendars and Schedules</td><td>Here you see details and can make further adjustments</td></tr></tbody></table>

## 1 – Add General Calendar

### 1.1 – Overview

In this step, you select **WHEN** an alarm should be escalated.

This is done by selecting 1 or more *General Calendars*. Alarms are only escalated on dates that are selected in these calendars.

The *General Calendars* are selected in **Element \[B]**. In Fig. 2, 1 General Calendar **\[B7]** has been added. The dates that have been selected in the calendar are also displayed.

{% hint style="info" %}
If no general calendar exists: Here you can learn how to [-> create a General Calendar.](https://docs.buildings.ability.abb/collection/platform/platform-core/alert-and-escalation/escalations/create-a-general-calendar.md)
{% endhint %}

After a calendar has been added, a **timeline \[E1]** appears in **Element \[E]**. Using this timeline, you can also read when the alarm is escalated. In Fig. 2, for example, a break has been inserted on November 1st. This means that no escalations would take place on November 1st.

<figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2FJ8IiX5kqWhM7MCxTINrE%2FGroup%20651.png?alt=media&amp;token=21bc8944-11f1-4a96-9b6f-7107ef627459" alt=""><figcaption><p>Fig. 2 – Selection of a General Calendar</p></figcaption></figure>

### 1.2 – Step-by-Step Guide

1. Click on **\[B1]** to add a General Calendar\
   ▷ The window **\[B2]** appears
2. In **\[B3]**, select a General Calendar\
   ▷ The selected calendar is displayed in **\[B4]**\
   ▷ In **\[B6]**, you see the validity dates for the added General Calendar
3. Optional: Select other General Calendars
4. Click on **Add \[B6]**

***

## Step 2 – Tags for Escalating

<figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2FLjtCWBCIu7XZb6IRkJyw%2FGroup%20652.png?alt=media&amp;token=bda5c1d0-17c0-4b75-b35d-2805d4df0869" alt=""><figcaption></figcaption></figure>

#### 2.1 – Overview

In this step, you determine **which** alarms are escalated.

To do this, you use [-> tags.](https://docs.buildings.ability.abb/collection/mandatory-base/platform-core/workspace-and-identity/tags.md)

As described in the [-> Alarms](https://docs.buildings.ability.abb/collection/platform/alert-center/alarms.md) chapter, every alarm is based on a [-> rule](https://docs.buildings.ability.abb/collection/platform/alarms-rules-and-escalations/rules.md). You can assign 1 or more tags to rules.

In window **\[C]**, you can specify 1 or more tags. Only alarms that were triggered via a rule that has the same tags that were also specified in window **\[C]** are escalated.

#### 2.2 – Step-by-Step

1. Click on **\[C1]** to add one or more tags for escalation
2. Added tags appear in element **\[C]**

***

## Step 3 – Tags with Users and Destinations

<figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2FQJ4Tf0k3rKZCtg5jnujU%2FGroup%20656.png?alt=media&amp;token=4391e62e-ed4d-43dd-8dbe-32fc1b6749ce" alt=""><figcaption></figcaption></figure>

### 3.1 – Overview

In this step, you choose to which users the alarm should be escalated.

Just as with alarms, you use [-> tags](https://docs.buildings.ability.abb/collection/mandatory-base/platform-core/workspace-and-identity/tags.md) for this.

In window **\[D]**, you can specify 1 or more tags. Users who have been assigned this tag are then added.

Alarms are escalated to these users.

### 3.2 – Step-by-Step

1. Click on **\[D1]**\
   ▷ The window **\[D2]** opens
2. Under **\[D3]**, select tags
3. Click on **\[D4]**\
   ▷ All users who have the selected tags appear in **Element \[D]**\
   ▷ All users who have the selected tags appear in **Element \[E]**

***

## Step 4 – Select Escalation Channel

<div data-full-width="true"><figure><img src="https://3489494878-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9GvUpaatBiReR43XFSMg%2Fuploads%2FT8p2WC1gShLa7P67EnN8%2FE42B8B62-AE5F-4C16-9B5E-CF70DFD69E93.png?alt=media&#x26;token=d087febe-95db-4cbb-8316-a05e3ad30207" alt=""><figcaption></figcaption></figure></div>

### 4.1 – Overview

In this step, you determine on which escalation channel alarms are escalated to a user.

This can be set individually for each user.

### 4.2 – Step-by-Step

1. For the user for whom you want to select the escalation channel: Click on **Edit schedule \[D6]**\
   ▷ The window **\[F]** opens\
   ▷ In the row **\[F1]**, you see all escalation channels. Unavailable escalation channels are grayed out
2. Click on the desired escalation channel
3. Make sure that the switch **\[F5]** is activated
4. Click on **Save \[FX]**
5. Click on **\[D5]** to test the escalation

***

## Step 5 – Schedules

### 5.1 – Overview

You can customize a precise schedule for each user to whom an alarm is escalated. This schedule refines the [-> General Calendar.](https://docs.buildings.ability.abb/collection/platform/platform-core/alert-and-escalation/escalations/create-a-general-calendar.md)

The schedules can be configured individually for each user and each escalation channel.

This makes it possible to notify a user, for example, both by mail and by SMS during normal working hours, but only by mail after working hours.

A separate schedule can be created for each escalation channel, or a standard schedule can be used.

This is the standard schedule for this user. This schedule ONLY APPLIES TO THIS USER!

It should not be confused with the General Calendar.

### 5.2 – Customize Standard Schedule

1. For the user for whom you want to customize the schedule: Click on **Edit schedule \[D6]**\
   ▷ The window **\[F]** opens\
   ▷ In the row **\[F1]**, the Standard Schedule tab is selected.
2. In field **\[F2]**, you can adjust the standard schedule.
3. In field **\[F3]**, you can add exceptions.
4. Click on **Save \[FX]** to apply the standard schedule.

### 5.3 – Apply Standard Schedule to an Escalation Channel

1. For the user for whom you want to apply the standard schedule: Click on **Edit schedule \[D6]**\
   ▷ The window **\[F]** opens\
   ▷ In the row **\[F1]**, you see all escalation channels. Unavailable escalation channels are grayed out
2. Click on the desired escalation channel
3. Make sure that the switch **\[F5]** is activated
4. Activate the switch **\[F4]**\
   ▷ The **\[F2]** area is grayed out\
   ▷ In the **\[F2]** area, the values you configured in [-> 5.2 Customize Standard Schedule](#id-5.2-customize-standard-schedule) appear
5. Click on **Save \[FX]**
6. Repeat this process for each escalation channel to which you want to apply the standard schedule

### 5.4 – Apply Individual Schedule for an Escalation Channel

You can use an individual schedule for each escalation channel.

1. For the user for whom you want to apply the standard schedule: Click on **Edit schedule \[D6]**\
   ▷ The window **\[F]** opens\
   ▷ In the row **\[F1]**, you see all escalation channels. Unavailable escalation channels are grayed out
2. Click on the desired escalation channel
3. Make sure that the switch **\[F5]** is activated
4. Make sure that the switch **\[F4]** is deactivated
5. In **Area \[F2]**, configure the individual schedule\
   ◈ This individual schedule only applies to the escalation channel in which it was configured!
6. Optional: Repeat the process for all desired escalation channels

***

## Step 6 – Repeated Escalations

### 6.1 – Overview

Use repeated escalations to remind a user about an alarm that is still active and has not been acknowledged. For each combination of user and escalation channel, you choose the interval and the number of additional notifications.

For example, you can repeat a user's E-mail notifications without applying the same settings to that user's SMS channel or to other users.

The required [-> notification provider](https://docs.buildings.ability.abb/collection/platform/platform-core/alert-and-escalation/escalations/notification-provider.md) and [-> user contact details](https://docs.buildings.ability.abb/collection/platform/platform-core/alert-and-escalation/escalations/configure-users-for-escalations.md) must be configured. You need permission to edit escalations to change the repeat settings.

<div data-full-width="true"><figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2Fgit-blob-b2539db7a44e050721654d650d9c3f8948f765f1%2Fv26-repeated-escalation.png?alt=media" alt="Escalation configuration with a two-minute repeat interval, four additional repetitions, and unlimited repetition switched off for an E-mail target"><figcaption><p>Fig. 6 – Repeat settings for one user and escalation channel</p></figcaption></figure></div>

| Element  | Setting               | Meaning                                                                                                                     |
| -------- | --------------------- | --------------------------------------------------------------------------------------------------------------------------- |
| **\[G]** | **Repeat every**      | Interval between repeated notifications. Choose 1, 2, 5, 10, 15, 30, or 60 minutes. **No repeat** switches repetition off.  |
| **\[H]** | **Repeat up to**      | Maximum number of additional repetitions after the initial notification. Choose 1, 2, 3, 4, 5, 10, 15, or 20 repetitions.   |
| **\[I]** | **Unlimited repeats** | Repeat without a fixed count while the alarm remains active and unacknowledged. When enabled, **Repeat up to** is disabled. |
|          | **Timehold, minutes** | The existing delay for the initial notification, measured from the alarm. This is not the repeat interval.                  |

Without a repeat interval, the count and unlimited-repetition controls are disabled. Targets without repeat settings retain their existing behavior without additional repetitions.

### 6.2 – Step-by-Step

1. Find the desired user and channel under **Users & targets**.
2. Select the interval under **Repeat every** **\[G]**.
3. Select the maximum number of additional repetitions under **Repeat up to** **\[H]**.\
   ◈ To repeat without a fixed count, enable **Unlimited repeats** **\[I]** instead.
4. Click **Save** for the target you edited.\
   ▷ The repeat settings for this target are saved.
5. Reopen the escalation to check the saved settings.

{% hint style="info" %}
In Fig. 6, **2 min** and **4 times** are selected. This means one initial notification followed by up to four additional repetitions at two-minute intervals. Repetition ends earlier if the alarm is acknowledged or is no longer active.
{% endhint %}

Choose a limited count when you want to limit the number of messages. Choose **Unlimited repeats** when reminders should continue without a fixed upper limit until a stop condition is met. Select an interval that suits your workflow.

Use **Reset all** to discard unsaved changes for the target.

### 6.3 – When Does Repetition Stop?

Further repetitions stop when:

* the alarm is acknowledged;
* the alarm is no longer active;
* the configured maximum number of additional repetitions is reached.

{% hint style="warning" %}
Changes to repeat settings apply to newly queued notifications. Notifications that are already queued retain the repeat settings with which they were queued. Switching repetition off does not retroactively stop repetitions that are already queued.
{% endhint %}

### 6.4 – Switch Off Repetition for New Notifications

1. Select **No repeat** under **Repeat every** **\[G]** for the desired target.
2. Click **Save**.\
   ▷ Newly queued notifications for this target are not repeated.

For combining notifications, see [-> Group Escalations](https://docs.buildings.ability.abb/collection/platform/platform-core/alert-and-escalation/escalations/group-escalations.md).


---

# 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://docs.buildings.ability.abb/collection/platform/platform-core/alert-and-escalation/escalations/configure-an-escalation.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.
