> 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.md).

# Alarms, rules and escalations

Eliona has a powerful system for registering, reporting, and forwarding incidents to the appropriate specialists for clarification.

Alarms, rules, and tickets are closely linked. Therefore, this topic is covered in a single chapter.

## Definition of terms

To understand how alarms, rules, etc. are handled in eliona, it is necessary to become familiar with the terminology used.

### [-> Rules](https://docs.buildings.ability.abb/collection/english-v14/documentation/alarme-regeln-und-eskalationen/regeln.md)

*Rules* are the conditions that must be met for an alarm to be triggered.

Using *Rules* you can configure in detail when an alarm should be triggered.

### [-> Alarms](https://docs.buildings.ability.abb/collection/english-v14/documentation/alarme-regeln-und-eskalationen/alarme.md)

A *Alarm* is in Eliona any report of an improper condition. Whenever eliona detects a deviation from a rule, eliona creates an alarm.

A *Alarm* is not automatically a sign of immediate danger. Even in a harmless case, e.g. an overflowing trash can, eliona creates an *Alarm* – provided there is a corresponding *rule* in place.

To distinguish how urgent *Alarms* they are, they are *Alarms* sorted by priority.

### [-> escalations](https://docs.buildings.ability.abb/collection/english-v14/documentation/alarme-regeln-und-eskalationen/eskalationen.md)

When a *Alarm* is issued, selected users can be notified automatically and via various channels, e.g. by email or SMS. This functionality is called *Escalation* referred to as

### [-> Tickets & Tasks](https://docs.buildings.ability.abb/collection/english-v14/documentation/tickets.md)

*Tickets* are work orders that can be sent to specialists when a *Alarm* has been issued.

*Tickets* can be subdivided into individual work packages. These work packages are *Tasks*.


---

# 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.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.
