Plan During Architecture Phase End-of-life planning begins during the system’s design phase (Phase 3), not when the moment of decommission arrives. The AISDP documents the end-of-life process from the outset, including trigger criteria, deployer notification templates, data lifecycle closure procedures, and post-decommission obligations. The plan is refined as the system matures. See for detailed treatment. Key outputs
- Design-phase planning requirement
- AISDP documentation from outset
- Refinement through system maturity
Seven Workstreams Summary WS1: Deployer transition (notification, API deprecation, embedded system support). WS2: Technical shutdown (staged endpoint deactivation, model archival, credential revocation). WS3: Data lifecycle closure (per-category retention/deletion, GDPR reconciliation). WS4: Downstream decision monitoring (historical output impact). WS5: Documentation finalisation (final AISDP version). WS6: Archival (ten-year immutable storage). WS7: Regulatory notifications (EU database, deployers, competent authority). See for detailed treatment. Key outputs
- Seven workstreams with cross-references
- Parallel execution for mandated withdrawals
- Sequential execution for planned retirements
Post-Decommission Obligations Summary Five continuing obligations: ten-year document retention with annual accessibility verification, GDPR data subject rights response capability, post-withdrawal serious incident reporting, historical PMM data analysis capability, and downstream decision monitoring where historical outputs continue affecting individuals. Named owners and expiry dates documented in the post-decommission monitoring schedule. Key outputs
- Five continuing obligations
- Named owners and expiry dates
- Annual review by AI Governance Lead