Corrective Actions (Alert-To-Action Bindings)
When a certain error occurs, it often requires one specific remedy. For example, when available memory on a device becomes low, its internal database must be downloaded or purged. This is always the case – it’s never another action, such as turning the device off or running a servo.
Because of it being so predictable, it can be automated. Any system action that is available in the user interface may be automatically launched in response to an alert.
If no operators are on duty or system functions are in standalone mode, the corrective action launched is “non-interactive” (also called "automatic" or "headless"). There are also “interactive” corrective actions which require operator input in real-time.
Some interactive corrective actions:
Some automatic corrective actions: