Glossary · Change, versions and configuration
Configuration control
In systems engineering, configuration control is the governance of approved hardware, software, parameter, model, document and evidence configurations. It ensures that only authorized configurations are built, installed and supported.
- Systems engineering
- Functional safety
- Technical documentation
In one sentence
Configuration control keeps hardware, software, parameters, models, documents and evidence in approved, known states across the lifecycle.
Example
At a CNC machine builder, a safety parameter set can only be released to the field after the configuration board approves it and records it in the configuration baseline.
How it applies
- Scope: Include all items that can change safety-relevant behavior: hardware revisions, firmware, PLC programs, parameters, models, documents and evidence.
- Machine safety: Uncontrolled parameter changes in the field can defeat a verified safety function. Configuration control defines who may change what and how the change is recorded.
- Technical documentation: Documents are configuration items. Their versions must match the product configuration, which links configuration control to document control.
- Evidence: Each approved configuration needs a matching evidence version.
Configuration control vs. change control
Configuration control governs what the approved configurations are. Change control is the process by which a configuration is changed. Change control produces the decisions; configuration control keeps their result in a known configuration baseline.