# Create a rule

## Procedure

<figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/wQxG5bYcWUAuGfcYrYGY/A5F985CD-E74B-4172-8E96-10432F822958.png" alt=""><figcaption></figcaption></figure>

1. Click on **RULES \[A]**\
   ▷ The rule overview opens
2. Click on **\[B]**\
   ▷ The window **Add rules \[C]** opens\
   ◈ Alternatively, you can also click one of the fields **\[B1]** clic&#x6B;**.** In this case, the rule is created directly in the corresponding asset. The field **\[D]** then no longer needs to be filled out
3. Configure the rule\
   ◈ See [↗ Details](#details) for more information on the individual options
4. Click on **Confirm \[M]**, to save the rule

## Details

<figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/U7xV8a3qJLIfAnSUpdnY/Regeln%20Rules.png" alt=""><figcaption></figcaption></figure>

<table data-full-width="true"><thead><tr><th width="92">Element</th><th width="323">Title</th><th>Details</th></tr></thead><tbody><tr><td><strong>[C]</strong></td><td>Menu "Add Rule"</td><td>In this menu, the rule is configured</td></tr><tr><td><strong>[D]</strong></td><td>Rule configuration</td><td>Configure a rule</td></tr><tr><td><strong>[E]</strong></td><td>Create tickets automatically</td><td>This feature will be available soon.</td></tr><tr><td><strong>[F]</strong></td><td>asset</td><td>Select the asset for which the rule should apply. If you created the rule via one of the fields [B1], this field is already filled in.</td></tr><tr><td><strong>[G]</strong></td><td>Type</td><td><p>Select the alarm type. The following are available:</p><ul><li>Standard: An alarm is created when an asset attribute meets a certain condition. </li><li><a href="../../assets/asset-status-active-inactive-unmonitored-assets">↗ Asset status</a>: an alarm is created when the asset is inactive for a certain period of time.</li></ul></td></tr><tr><td><strong>[H]</strong></td><td>Attribute</td><td>Select the attribute for which the rule applies</td></tr><tr><td><strong>[I]</strong></td><td>Condition</td><td>In this field as well as in field [I1], you determine which condition must be met in order to trigger an alarm.</td></tr><tr><td><strong>[I1]</strong></td><td>Threshold</td><td>Enter the threshold here.</td></tr><tr><td><strong>[J]</strong></td><td>Enable aggregation</td><td>Enable this switch if the rule should be based on <strong>aggregated values</strong> . This will reveal additional aggregation options.</td></tr><tr><td><strong>[J1]</strong></td><td>Aggregation mode</td><td>Choose how the values within the selected grid should be aggregated. Examples include <em>Average</em>, <em>Min</em>, <em>Max</em>, <em>Sum</em>.</td></tr><tr><td><strong>[J2]</strong></td><td>Aggregation grid</td><td>Defines the time grid on which the aggregation is based (e.g. <em>15 minutes</em>, <em>1 hour</em>, <em>1 day</em>). This grid determines the evaluation depth of the rule.</td></tr><tr><td><strong>[K]</strong></td><td>Priority</td><td>Select the priority that an alarm triggered by this rule should have</td></tr><tr><td><strong>[L]</strong></td><td>Acknowledgement</td><td>If you enable this option: An alarm triggered by this rule is <a href="#quittierungspflicht">↗ acknowledgement required</a>.</td></tr><tr><td><strong>[M]</strong></td><td>Tags</td><td>Assign one or more tags to the rule</td></tr><tr><td><strong>[N]</strong></td><td>"Alarm comes" message</td><td>This message is displayed when the alarm is triggered</td></tr><tr><td><strong>[N1]</strong></td><td>Standard</td><td>Use the preconfigured message from Eliona. The value is displayed under [M3]</td></tr><tr><td><strong>[N1]</strong></td><td>Custom</td><td>You can define your own message. You can find out which variables are available there <a href="../../../academy/twig-templating-in-eliona">-> here</a></td></tr><tr><td><strong>[N2]</strong></td><td>Preview</td><td>Preview of the alarm-comes message</td></tr><tr><td><strong>[O]</strong></td><td>"Alarm goes" message</td><td>This message is displayed when the alarm clears</td></tr><tr><td><strong>[O]</strong></td><td>"Alarm goes" message: Standard</td><td>Use the preconfigured message from Eliona. The value is displayed under [L3]</td></tr><tr><td><strong>[NO]</strong></td><td>Alarm goes" message: Custom</td><td>Create a custom "alarm goes" message</td></tr><tr><td><strong>[O]</strong></td><td>"Alarm goes" input field</td><td>Displays the "alarm goes" message. If "Custom" [L3] is enabled: the custom message can be entered in this field</td></tr><tr><td><strong>[P]</strong></td><td>Add rule</td><td>Save entries and create rule</td></tr></tbody></table>

## Acknowledgement requirement

You can enable the "acknowledgement required" option for rules. The acknowledgement requirement has the following effects:

As explained in the [↗ ](https://docs.buildings.ability.abb/collection/english-v14/documentation/alarms-rules-and-escalations)[Introduction](https://docs.buildings.ability.abb/collection/english-v14/documentation/alarms-rules-and-escalations) an alarm is triggered when the conditions of a rule are met. The acknowledgement requirement regulates what happens when the conditions of a rule are NO LONGER met.

{% hint style="info" %}
**Example**&#x20;

A rule is created that triggers an alarm as soon as the temperature rises above 25 °C. The acknowledgement requirement regulates what happens when the temperature drops below 25 °C again.
{% endhint %}

### Behavior of alarms *Without* Acknowledgement requirement

If the conditions for the alarm are no longer met, the alarm disappears on its own from the [↗ alarm overview](https://docs.buildings.ability.abb/collection/english-v14/documentation/alarms#die-alarm-uebersicht).&#x20;

The disappeared alarm is in the[ ↗ alarm history ](https://docs.buildings.ability.abb/collection/english-v14/documentation/alarms#alarm-historie)displayed.

### Behavior of alarms *With* Acknowledgement requirement

Even if the conditions for the alarm are no longer met, the alarm remains in the  [↗ alarm overview](https://docs.buildings.ability.abb/collection/english-v14/documentation/alarms#die-alarm-uebersicht). &#x20;

For an alarm with acknowledgement requirement to be removed from the alarm overview, the alarm must be acknowledged.

{% hint style="info" %}
See also: [↗ Acknowledgement-required and clearing alarms](https://docs.buildings.ability.abb/collection/english-v14/documentation/alarms-rules-and-escalations/alarms/acknowledgement-required-and-self-clearing-alarms).

There it is explained how alarms can be acknowledged.
{% endhint %}


---

# 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/english-v14/documentation/alarms-rules-and-escalations/rules/create-a-rule.md?ask=<question>
```

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.