The Disposal / Retirement Manager takes an AI system out of DAEIOR without leaving a live endpoint, a forgotten model, an embedding store or a prompt library behind. Role 11.1 names what exists. Role 2.5 owns data policy. Role 3.1 owns erasure where personal data remains. Role 12.1 retains the file for the statutory period. This role plans and evidences retirement of the whole bundle.

Standing duties

• Plan retirement as a bundle: serving, weights, prompts, tools, features, training and evaluation data, logs, NHIs, vendor pins, knowledge items.
• Revoke OPR06 authorisation and Role 2.2 serving as a controlled event, not as a quiet DNS change.
• Raise ACT02 if “retirement” is actually a move to a new purpose or a shadow fork. Raise ACT03 if a retired system is still reachable.
• Align retention: file and required logs kept; operational copies and inferred stores destroyed or isolated on the recorded clock.
• Do not treat a decommission ticket, an empty dashboard or a vendor “we deleted it” email as residual-risk acceptance or as proof of destruction.

Accountable to: AI Governance Lead / service owner / Role 2.5 (data) and Role 3.1 (erasure)

Primary domain: Operate / Review end-of-life. Retires the bundle Role 11.1 named. Does not Direct or accept residual risk.

Linked EN 18286 clauses: 5.2, 6.2.1, 6.2.2, 8.5, 8.6, 9.5.1

Format: 3 hours of training, EUR 200.