AssetWolf has a range of tools for detecting alarm situations and handling them.
As a user you can define triggers — conditions for an alarm to be raised — and you can determine which asset type (or types) each trigger applies to.
Wherever a field, or calculated field, has a numeric value, you can set a working range, and levels that are too high, too low, or warning levels. For example here, for a temperature range:
AssetWolf can perform calculations whenever data arrives, running scripts written in Phi on that data to perform calculations that you define.
Calculations can be simple or can consider many factors. You can set up a custom trigger condition by doing:
if ( # some condition ) { fireTrigger (triggerCodeName, "explanation") }
You may wish to trigger an alarm when a device goes off-line for too long.
For example, if a device is meant to communicate every 15 minutes, you may wish to raise an alarm if it hasn't connected for over two hours:
You can define a procedure that is followed when an alarm is triggered. This can include:
An alarm event, once triggered, has a range of severity levels. These handle situations when:
So for example, if you're monitoring perishable goods in a refrigerator, and a high temperature alarm occurs, you may need to check the goods.
In this way, AssetWolf has a range of configurable options for handling alarms.