...
Sv translation | |||||||||
---|---|---|---|---|---|---|---|---|---|
| |||||||||
Message rules define, if and when messages are generated. In this article, we'll be talking about the creation of new message rules in QUDE with the help of two examples.
1st example: simple message rules without conditionsFor this example, we create a message rule that generates a new message whenever the outdoor temperature of your facility is 0°C (32°F) or below. The freezing point is relevant for various situations and the structure of the evaluation rule can be used as a template for many other simple calculations. Step-by-step instruction
2nd example: the annual limitvalueof refilled refrigerant has been exceededWe create a message rule to informs us that notifies you when the annual limit value of refilled refrigerant has been exceeded. The limit value is the equivalent to of the expected amount of refrigerant that should be refilled every year. An excess of this value usually means, that there is indicates a problem, for example like such as a leak. For this calculation rule, we 'll be using use the following logic: The property "Filling quantity" (refrigerant_quantity) describes the filling quantity of the tanktank's holding capacity. 20% of it are equivalent to the usual annual refilling quantity that we'll use as a limit value. That's why we divide this value the refrigerant quantity by 5. In order to get the annual refilling quantity, we have to choose the function "Sum" and time period "1y" (1 year) for the chosen data point in the list. With the help of the message rule above, a message is generated once the annual refill quantity is more than 20% of the tank's capacity. Step-by-step instruction
3rd example: the ventilation system is switched on outside of opening hoursFor the second example, we would like to generate a calculation rule, whenever the ventilation system is switched on, even though the matching store is closed. This calculation rule can help finding faults in the system. The data point or the activity status can also be switched with various other similar data points, if you would like to analyse other time-dependent values. For this calculation rule, we'll be using the following logic: When using conditions with a further outcome, you define a condition and two possible outcomes that can be calculated. In the case of message rules, this setup is often used to either create a message rule, or not. The constants "true" and "false" express this logic. A "true" result will generate a message rule, whilst "false" won't create one. The condition consists of two components: the activity status and the opening hours. The condition for opening hours is defined in the schedule brick. We use the time outside the opening hours as a condition by setting the schedule brick to "is not active" ("active" would mean during the opening hours). The second condition verifies the activity status of the ventilation system. The activity status is a boolean data point and therefore only has two values: "true", which means that the system is switched on, and "false", which indicates a switched off system. The relational operator veryfies, if the system is switched on by equating the value of the data point with the boolean constant "true". The system is switched on whenever the values are equal. The brick for boolean operators defines with "and" that both conditions have to be "true" to generate a message rule. Step-by-step instruction
|