Study guide
Manage the AI Solution Transition Plan
PMI Certified Professional in Managing AI PMI-CPMAI
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: PMI-CPMAI Exam Foundations & the CPMAI Methodology
The PMI-CPMAI Exam: Format, Eligibility, Fees & Scoring The CPMAI Methodology: Six Phases and Data-Centric Iteration CPMAI vs Waterfall, Agile, and CRISP-DM
2 Chapter 2: AI and Machine Learning Fundamentals for CPMAI
The Seven Patterns of AI Supervised, Unsupervised & Reinforcement Learning Why AI Projects Fail: Value, Data Readiness & Right-Sizing
3 Chapter 3: Domain I — Support Responsible and Trustworthy AI Efforts (15%)
Oversee the Privacy and Security Plan Manage AI/ML Transparency in Data and Algorithm Selection Conduct Bias Checks on Model, Data, and Algorithm Monitor Regulatory and Policy Compliance Manage Accountability Documentation and the Audit Trail
4 Chapter 4: Domain II — Identify Business Needs and Solutions, Part 1 (26%)
Identify the Problem to Be Solved Evaluate Initial AI Feasibility Conduct Security, Safety, and Ethics Risk Assessments Develop the AI Project Scope Statement Determine Return on Investment
5 Chapter 5: Domain II — Identify Business Needs and Solutions, Part 2
Manage Adoption and Integration Risks Draft the AI Solution Define Success Criteria and KPIs Support Business Case Creation Identify Project Resources: People, Hardware, and Contractors
6 Chapter 6: Domain III — Identify Data Needs, Part 1 (26%)
Define the Required Data Identify Data Subject-Matter Experts Identify Data Sources and Locations Coordinate the AI Workspace and Infrastructure Gather the Required Data
7 Chapter 7: Domain III — Identify Data Needs, Part 2
Check Data Privacy, Compliance, and Access Oversee Data Evaluation Determine If the Data Meets Solution Needs: The Phase 2 Go/No-Go Convey Data Understanding to Leadership
8 Chapter 8: Domain IV — Manage AI Model Development and Evaluation (16%)
Oversee AI/ML Model Technique and Algorithm Selection Oversee Model QA/QC and Configuration Management Manage AI/ML Model Training Manage Data Transformation and Data Preparation Verify Data Quality for the Data Preparation Go/No-Go Verify the Model Is Ready for Operationalization
9 Chapter 9: Domain V — Operationalize AI Solution, Part 1 (17%)
Manage Creation of the AI Solution Deployment Plan Manage the AI Solution Deployment Oversee Model Governance in Production Oversee AI Solution Metrics and Performance Monitoring
10 Chapter 10: Domain V — Operationalize AI Solution, Part 2
Prepare the Final Report and Lessons Learned Manage the AI Solution Transition Plan Oversee the AI Solution Contingency Plan
Manage the AI Solution Transition Plan
Key Takeaways Explain This Topic AI
AI handover differs from software handover on four counts: the system degrades with no code change, it needs periodic retraining, judging output quality requires judgment rather than uptime checks, and it carries bias-monitoring, audit-trail and model-review obligations.
Plan the transition as an overlap period spanning at least one full retraining cycle, not a cutover date, and define exit criteria the operations team must demonstrate before the project team leaves.
Knowledge transfer content is fixed: the model card with known limitations, the runbook, the retraining trigger and approval procedure, the escalation path, and the named remaining data SMEs.
Ongoing maintenance — inference compute, monitoring, evaluation-set labeling, retraining and SME review — is a permanent operating cost that needs both an owner and a funding line.
The project is not closable while any operational responsibility is unassigned, and "the data science team will keep an eye on it" is not an operating model because it has no rota, threshold, budget, or accountability.
Last updated: August 2026
What Operations Is Actually Being Asked to Take On
ECO Domain V, Task 6 hands a live artificial intelligence (AI) solution to a team that did not build it. Whether that handover holds is decided by one question, and it is not whether documentation was delivered — it usually was. It is whether four specific responsibilities have a name against each of them, because a standard support function will not pick any of them up by default:
Watching for decay that nothing announces. No code changes, no deployment, and accuracy still falls as the world drifts away from the training data. No alert fires unless somebody built one.
Running periodic retraining , which is a recurring project activity — triggered, approved and promoted — rather than a patch cycle.
Exercising judgment about output quality. Someone has to be able to tell a plausible-but-wrong output from a correct one. A green uptime dashboard says nothing about whether the predictions are still sensible.
Carrying standing obligations — periodic bias monitoring, an audit trail of decisions, scheduled model review, and the ability to explain an individual decision to a customer or regulator.
A support team that is excellent at conventional incident management can hold all four of these responsibilities and still let a model quietly decay, because nothing in their normal toolkit alerts on it.
Plan an Overlap, Not a Date
Transition plans fail when they name a cutover date and nothing else. Plan an overlap period in which operations runs the system and the project team is available at declining intensity. Size the overlap so that it spans at least one full retraining cycle and, ideally, one real incident — you want operations executing the procedures with the project team watching, rather than reading about them.
Then define exit criteria for the project team . The transition is complete only when:
Every operational responsibility has a named accountable owner.
Operations has executed a retraining and a rollback at least once, observed.
Monitoring dashboards and alert thresholds are live and routed to a real on-call rota.
The model card, runbook, and escalation path are published where support staff can find them.
A funding line exists in the operating budget for compute, monitoring, labeling, and SME review time.
The first scheduled model review and bias review are booked in the calendar.
Until those are satisfied you have a date, not a handover.
What Actually Gets Transferred
Knowledge transfer to production support is a defined content set, not a meeting:
The model card and known limitations — intended use, populations or segments where performance is weak, the confidence range, what the model must not be used for, and the bias-check results with the date they were run.
The runbook — normal operating metrics, alert thresholds and what each alert means, first-response steps, the rollback procedure, and contacts.
The retraining procedure — the trigger (calendar, drift threshold, or performance floor), where training data comes from, who approves a retrained candidate, and how it is promoted to production.
The escalation path — who to call, who decides, and who is authorized to take the model offline.
The remaining data subject matter experts (SMEs) — named people who know what the fields actually mean. This is the most routinely lost artifact on the list, because SMEs return to their day jobs and nobody records who they were.
Maintenance Is a Permanent Operating Cost
Ongoing maintenance procedures cost money every year: inference compute, monitoring and drift tooling, periodic labeling to refresh evaluation sets, retraining compute and the SME review that accompanies it, and human-in-the-loop reviewers if the design uses them. This is an operating expense with no end date. Assigning the work without the budget produces a handover that fails within two quarters, so each responsibility below needs both an owner and a funding line.
Who Owns What After Handover
Operational responsibility Who owns it after handover What they need to be able to do What goes wrong if unassigned
Model performance monitoring Operations or MLOps on-call, under an accountable service owner Read drift and accuracy dashboards, know the thresholds, distinguish real degradation from seasonal variation Decay goes unnoticed until a business user complains months later
Data pipeline health The data engineering team that owns the upstream sources Detect a stalled feed, a schema change, or a silent rise in nulls before it reaches the model The model serves confident predictions on stale or malformed input
Retraining decisions The accountable business or service owner, advised by data science Decide when the trigger has fired, approve the candidate model, authorize promotion The model runs indefinitely on its original training data
Incident response The existing incident-management function, extended with AI severity criteria Classify AI incidents, invoke the fallback, execute rollback A silently wrong model is not treated as an incident because nothing is down
Bias and compliance review Risk or compliance, with a named reviewer and a fixed cadence Re-run subgroup checks, maintain the audit trail, answer explanation requests The obligation lapses and the first evidence of a problem arrives from outside
Business-outcome tracking The process owner who signed the business case Track the KPI against baseline and report at an agreed cadence Nobody can say whether the solution still earns its operating cost
Documentation and Training for Two Audiences
Support staff need the runbook, model card, escalation and retraining procedures, plus hands-on rehearsal during the overlap. End users need something completely different: what the output means, how much confidence to place in it, when and how to override it, how to report a bad output, and the fact that behavior will change after each retrain. Under-training end users produces either blanket over-trust or silent abandonment — and abandonment shows up directly in the adoption number you reported in the final report.
The Exam Behavior to Remember
The project is not closable while any operational responsibility is unassigned . When a scenario offers you a clean cutover with one owner missing, holding closure until that owner exists is the correct answer. And "the data science team will keep an eye on it" is not an operating model: there is no rota, no threshold, no budget, and no accountability, and the arrangement evaporates the moment that data scientist changes teams.