Glossary · Evidence, assurance and traceability
Lifecycle claim
In assurance and systems engineering, a lifecycle claim is a claim that must remain valid through operation, maintenance, updates, and modifications, not only at release. It needs evidence that is kept current over time.
- Systems engineering
- Verification
In one sentence
A lifecycle claim must stay true through operation, maintenance, updates and modifications, so its evidence has to be kept current.
Example
“The emergency stop of the conveyor line meets PL d” is a lifecycle claim: it depends on yearly proof tests, correct spare parts and a controlled process for every PLC program update.
How it applies
- Evidence: Identify for each lifecycle claim what can invalidate it: wear, drift, software updates, modifications, changed use. Plan evidence that is renewed accordingly, such as periodic verification records.
- Integrated systems: Updates to one subsystem can invalidate claims about another. Link claims to the configuration items they depend on.
- Change control: Every change should be checked against the lifecycle claims it touches as part of change control.
- Technical documentation: The user often carries part of the burden, through maintenance and tests. The safety lifecycle activities that the user must perform belong in the information for use.
Lifecycle claim vs. release claim
A release claim describes the state at delivery. A lifecycle claim is a promise about the whole service life and is only credible with maintenance, monitoring and change control behind it.