# 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](https://docs.buildings.ability.abb/collection/english-v14/documentation/alarms-rules-and-escalations/rules)

*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/alarms-rules-and-escalations/alarms)

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](https://docs.buildings.ability.abb/collection/english-v14/documentation/alarms-rules-and-escalations/escalations)

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)

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