There are three types of alert types you can include in Missions or Mission templates.
Single measurement alert type is good for basic alerts. An alert is generated if any of the measurements made by the QR logger is violating the alert rule. You can create an alert for any sensor available by the logger: probe temperature, temperature, light, humidity, and shocks.
In the example below, the desired conditions are: Humidity is more than 20% and Temperature is between 2°C and 10°C. If the logger registers that humidity is 10% or temperature 15°C, an alert will be generated after the logger has been scanned.
Alert Delay triggers the alert not upon the first rule violation but only if the rule was violated continuously for a certain time. It can be set for Single measurement alerts to allow several consecutive measurements which violate the alert rule limit before generating the alert.
By setting a delay to the alert rule, you allow the alert to be triggered only after that many unacceptable measurements have been logged.
- Delay value 0 = All measurements outside the set parameters will trigger an alert
- Delay value 1 = Alert at the 2nd consecutive measurement outside the set parameters
- Delay value 3 = Alert at the 4th consecutive measurement outside the set parameters
The actual timeframe depends on both the delay setting and the measurement interval. In our example, with the delay of 5 measurements for Humidity, only the sixth consecutive measurement will trigger the alert. The measurement interval of the logger is 10 minutes, meaning that the alert will be generated if the conditions have been violated continuously for 60 minutes. For Temperature, the alert will be generated if the logger registers temperatures less than 2°C or more than 10°C continuously for 30 minutes. If the logger registers temperature 20°C only once, the alert will not occur.
The cumulative time alert type tracks the total time the rule is violated during the mission. In some cases, temperature (or any other parameter) variance is OK as long as it doesn't exceed a specific total time. You may want to use this alert rule for instance for shipments that change hands between different carriers often to make sure the product doesn't unfreeze while moving between freezers.
You can set an alert rule if a mission has lasted for longer than a set time (in minutes, hours, or days). You might want to use this setting, for instance, for temperature-sensitive shipments that are transported without temperature-controlled containers and will remain usable for a certain time despite the temperature variance. Combined with the possibility to end Missions automatically on the first scan, this alert type can provide critical information if loggers go unscanned for too long.