# 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](/collection/platform/alarms-rules-and-escalations/rules.md) *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](/collection/platform/alert-center/alarms.md) 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](/collection/platform/platform-core/alert-and-escalation/escalations.md) 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](/collection/platform/service-desk.md) *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*. --- # Agent Instructions: 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: ``` GET https://docs.buildings.ability.abb/collection/platform/alarms-rules-and-escalations.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.