Meridian's CIO wants the AI roadmap folded into the airline's broader digital-transformation initiative rather than run as a side project. From a CPMAI standpoint, what is the strongest justification for connecting AI initiatives to the digital-transformation program?
Select an answer to reveal the explanation.
Short Explanation
AI projects are hungry for clean, accessible, modern data — which is exactly what a digital-transformation program is supposed to deliver. Running them separately means the AI team keeps tripping over the same legacy-systems problem the transformation program was funded to fix.
Full Explanation
CPMAI explicitly connects AI initiatives to digital transformation because they share the same foundation: modern data infrastructure, integrated systems, and streamlined processes. Meridian's legacy operations systems (noted in the intake as predating any of today's AI work) are exactly the kind of constraint digital transformation is meant to resolve, and an AI project that ignores that dependency risks stalling on unusable or fragmented data — a direct CPMAI failure mode. The 'should be kept fully separate' distractor contradicts this shared-dependency logic and would strand the AI project without the infrastructure it needs. The 'branding exercise' distractor trivializes a real technical and organizational dependency into cosmetics, which is not how CPMAI frames the relationship. The 'GDPR-preparation' distractor conflates digital transformation with a narrow legal-compliance purpose; GDPR readiness may be one beneficiary of better data governance, but it is not why digital transformation and AI initiatives are linked in CPMAI's framing. Aligning the two programs also gives the AI PM leverage to request the same executive sponsorship and budget prioritization the transformation program already has.