> 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/alarme-regeln-und-eskalationen/eskalationen/allgemeinen-kalender-erstellen.md).

# Create general calendar

## Overview

*General calendar* serve as the basis for when alarms are escalated.

We recommend, *General calendar* to make it as generous as possible. Often a *General Calendar* is created for an entire year.

By leaving out days, you can use the General Calendar to determine when alarms should NOT be escalated, e.g. on public holidays. Keep in mind that you can have multiple General Calendars and can select multiple General Calendars for each escalation.<br>

## Create calendar

<div data-full-width="true"><figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/rUIt0W0p8gNhshVzGmgX/Eskalation%20(1).png" alt=""><figcaption></figcaption></figure></div>

1. Click on **Engineering \[A]**
2. Click on **Escalation \[B]**
3. **Click on \[C]**

   ▷ The calendar view opens.
4. Click on **\[D]**\
   ▷ The window opens **\[D1]**
5. Give the calendar a name **\[D2]**
6. Click on **\[D3]**, to create new dates in the calendar
7. Activate the switch **\[D4]**
8. Select under **\[D5]** the start date
9. Select under **\[D6]** the end date
10. Optional: Click again on **\[D3]** to create additional entries.\
    ◈ By leaving out dates between the entries, you can disable escalations for a certain period, e.g. for public holidays.
11. Click on **Save** **\[D7]**


---

# 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/english-v14/documentation/alarme-regeln-und-eskalationen/eskalationen/allgemeinen-kalender-erstellen.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.