Glossary · Fault behavior and system states
Recovery behavior
Also known as: recovery
In systems engineering, recovery behavior is the defined behavior for restoring operation after a fault, stop or degraded condition, including the checks, resets and resynchronization needed before normal operation resumes.
- Functional safety
- Integrated systems
In one sentence
Recovery behavior defines how a system returns to operation after a fault, stop or degraded mode, without unexpected startup or lost state.
Example
After an emergency stop in a robot cell, the operator acknowledges the fault, performs a manual reset outside the cell, and the robot resumes only after a new start command.
How it applies
- Machine safety: Resetting a safety function must not by itself restart the machine; a separate, deliberate start command is needed. Manual reset and restart prevention are the design measures here, and unexpected startup is the hazard to avoid.
- Integrated systems: Before operation resumes, resynchronize states between systems, discard or re-validate buffered commands and confirm positions. Define recovery as transitions in the state model.
- Technical documentation: Recovery procedures are among the most frequently used instructions. Write them as step-by-step tasks that include the required checks.
Recovery behavior vs. reset
A reset acknowledges a fault or a stopped safety function. Recovery behavior is the whole defined path back to operation, of which the reset is one step.