Glossary · Change, versions and configuration
Rollback capability
In systems engineering, rollback capability is the ability to return to a previous valid system, configuration, documentation and evidence state after a change. A rollback is only complete when all four states match again.
- Systems engineering
- Functional safety
- Technical documentation
In one sentence
Rollback capability means returning to a previous valid state of system, configuration, documentation and evidence, not only reinstalling old software.
Example
After a failed PLC update on a packaging line, maintenance restores the previous program, parameter set and HMI texts from the configuration baseline and reinstates the matching operating instructions.
How it applies
- Integrated systems: A rollback target must be a known configuration baseline. Rolling back one component alone can break version compatibility with its peers.
- Machine safety: Safety parameters and safety program versions are part of the rollback. After rolling back, confirm that safety functions are in the verified state, for example with a functional check.
- Technical documentation: Manuals, HMI texts and warning labels have to match the restored version. Keep previous documentation versions retrievable.
- Cybersecurity: Rollback can reintroduce known vulnerabilities. Patch management should define when a rollback is acceptable and for how long.
Rollback vs. recovery
Recovery behavior brings a running system back to normal operation after a fault. A rollback reverses a change and returns to an earlier approved state.