# Smart Logic

BuildingPro Suites has a powerful system to register events, report them, and forward them to the appropriate specialists for clarification.

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

***

## Terminology

To understand how alarms, rules, etc., are handled in BuildingPro Suites, it is necessary to familiarize yourself with the terminology used.

### [-> Rules](https://docs.buildings.ability.abb/collection/platform/alarms-rules-and-escalations/rules)

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

Based on *rules*, you can configure in detail when an alarm should be triggered.

### [-> Alarms](https://docs.buildings.ability.abb/collection/platform/alert-center/alarms)

An *alarm* in BuildingPro Suites is any message about a non-standard condition. Whenever BuildingPro Suites detects a deviation from a rule, BuildingPro Suites creates an alarm.

An *alarm* is not automatically a sign of immediate danger. Even in a harmless case, e.g., an overflowing trash can, BuildingPro Suites creates an *alarm*—provided there is a corresponding *rule*.

To distinguish how urgent *alarms* are, *alarms* are sorted by priorities.

### [-> Escalations](https://docs.buildings.ability.abb/collection/platform/platform-core/alert-and-escalation/escalations)

When an *alarm* is issued, selected users can be notified automatically and via various channels, e.g., by email or SMS. This functionality is called *escalation*.

### [-> Tickets & Tasks](https://docs.buildings.ability.abb/collection/platform/service-desk)

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

*Tickets* can be divided into individual work packages. These work packages are *tasks*.