Create a Rule

Procedure

1. Click on RULES [A]

   ▷ The rule overview opens

2. Click on [B]

   ▷ The Add Rules [C] window opens ◈ Alternatively, you can also click on one of the fields [B1]. In this case, the rule is created directly in the corresponding asset. The [D] field does not need to be filled out then.

3. Configure the rule

   ◈ See ↗ Details for more information on the individual options

4. Click on Confirm [M] to save the rule

Details

Element	Title	Details
[C]	"Add Rule" menu	In this menu, the rule is configured
[D]	Rule configuration	Configure a rule
[E]	Automatically create tickets	This function will be available soon.
[F]	Asset	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 out.
[G]	Type	Select the alarm type. Available options: Standard: An alarm is created when an asset attribute meets a certain condition. ↗ Asset Status: an alarm is created when the asset has been inactive for a certain time.
[H]	Attribute	Select the attribute for which the rule applies
[I]	Condition	In this field and in field [I1], you determine which condition must be met for an alarm to be triggered.
[I1]	Limit value	Here you enter the limit value.
[J]	Activate aggregation	Activate this switch if the rule should be based on aggregated values. This makes further aggregation options visible.
[J1]	Aggregation mode	Select how the values within the selected raster should be aggregated. Options include Average, Min, Max, Sum.
[J2]	Aggregation raster	Defines the time raster on which the aggregation is based (e.g., 15 minutes, 1 hour, 1 day). This raster determines the evaluation depth of the rule.
[K]	Priority	Select the priority that an alarm triggered by this rule should have
[L]	Acknowledgment	If you activate this option: An alarm triggered by this rule is ↗ subject to acknowledgment.
[M]	Tags	Give the rule one or more tags
[N]	"Alarm comes" message	This message is displayed when the alarm is triggered
[N1]	Standard	Use the message preset by Eliona. The value is displayed under [M3]
[N1]	Custom	You can define your own message. The variables available to you can be found -> here
[N2]	Preview	Preview of the "alarm comes" message
[O]	"Alarm goes" message	This message is displayed when the alarm goes away
[O]	"Alarm goes" message: Standard	Use the message preset by Eliona. The value is displayed under [L3]
[NO]	"Alarm goes" message: Custom	Create your own "alarm goes" message
[O]	"Alarm goes" input field	Displays the "alarm goes" message. If "Custom" [L3] is activated: The custom message can be entered in this field
[P]	Add rule	Save inputs and create rule

Acknowledgment Obligation

You can activate the "Acknowledgment Obligation" option for rules. The acknowledgment obligation has the following effects:

As explained in the ↗ Introduction, an alarm is triggered when the conditions of a rule are met. The acknowledgment obligation regulates what happens when the conditions of a rule are NO longer met.

Example

A rule is created that triggers an alarm as soon as the temperature rises above 25 °C. The acknowledgment obligation regulates what happens when the temperature drops below 25 °C again.

Behavior of Alarms Without Acknowledgment Obligation

When the conditions for the alarm are no longer met, the alarm disappears from the ↗ Alarm Overview on its own.

The disappeared alarm is displayed in the ↗ Alarm History.

Behavior of Alarms With Acknowledgment Obligation

Even if the conditions for the alarm are no longer met, the alarm remains in the ↗ Alarm Overview.

For an alarm with an acknowledgment obligation to be removed from the Alarm Overview, the alarm must be acknowledged.

See also: ↗ Alarms Subject to Acknowledgment and Dismissed Alarms.

This explains how alarms can be acknowledged.