Glossary · Change, versions and configuration
Release decision
In systems engineering, a release decision is a controlled decision that a defined system and evidence baseline is ready for use, delivery or operation. It is taken by an authorized person or body on the basis of documented criteria.
- Verification
- Systems engineering
- Technical documentation
In one sentence
A release decision states that a defined system and evidence baseline is ready for use, delivery or operation, and records who decided on what basis.
Example
Before a robot cell is handed over, the project lead signs a release decision that references the configuration baseline, the validation report and the open-issues list.
How it applies
- Evidence: Base the decision on a named configuration baseline and a complete evidence package. Open issues and accepted deviations are listed explicitly.
- Machine safety: A release decision for operation should confirm that validation of the safety functions is complete for the released configuration.
- Technical documentation: Information for use belongs to the released baseline. Releasing a machine with outdated instructions is releasing an incomplete product.
- Compliance: An internal release decision is not a conformity assessment. It can record that the conformity steps required by applicable law have been completed, but it does not replace them.
Release decision vs. validation
Validation produces evidence that the system fits its intended use. The release decision weighs that evidence, together with open issues and documentation status, and authorizes use. Validation can be complete while release is still withheld.