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

# Alarms, rules and escalations

Eliona has a powerful system for recording, reporting, and forwarding events to the relevant specialists for clarification.

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

## Terminology

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

### [-> Rules](/collection/english-v14/documentation/alarms-rules-and-escalations/rules.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](/collection/english-v14/documentation/alarms-rules-and-escalations/alarms.md)

A *Alarm* In Eliona, an alarm is any notification 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* are, *Alarms* they are sorted by priority.

### [-> escalations](/collection/english-v14/documentation/alarms-rules-and-escalations/escalations.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](/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 broken down 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 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.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.