Study guide
Identify Data Sources and Locations
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
Identify Data Sources and Locations
Key Takeaways Explain This Topic AI
Domain III, Task 3 produces a concrete artifact — a data source inventory recording, for every required data element, its system, owner, approver, access method, permitted use, access lead time and risks.
Distinguish the system of record from downstream copies: warehouse tables are shaped by transformation rules and often keep only current state, so corrections and deletions that a model needs no longer exist.
External and third-party data must clear four gates — cost over the model's operational life, licensing and permitted use confirmed in writing, refresh and schema guarantees, and the risk of depending on a feed you do not control.
History-depth requirements set in Task 1 routinely force excavation of legacy systems and cold archives, where the questions are whether the format is still readable, whether expertise survives, and whether retention has already deleted it.
Access approval for a regulated source can take weeks and sits on the critical path — surface access lead time as a schedule risk with a date, and start the longest approvals on day one of Data Understanding.
Last updated: August 2026
The Deliverable Is an Inventory
Task 3 has a physical output. A data source inventory lists, for every data element in your requirements, where it lives, who owns it, how you get it, what it costs, what you are permitted to do with it, and how long access takes. It is the bridge between Task 1 (what you need) and the later task of actually gathering data, and it is the document that converts 'the data is around somewhere' into a plan a sponsor can fund.
Internal Systems: System of Record Versus Downstream Copy
Map the internal estate first, in categories:
Operational databases — the transactional systems where data is authored: billing, CRM, ERP, electronic health records, ticketing.
Data warehouses and marts — modeled, cleaned, business-defined; convenient, but the transformation may already have destroyed what you need.
Data lakes and lakehouses — raw and high-volume, with variable documentation.
SaaS platforms — marketing automation, HR, support tooling; reachable only through an API with rate limits and export restrictions.
Event and application logs — clickstream, telemetry, audit trails; often the only record of what a user did rather than what the system concluded.
The distinction that matters most is system of record versus downstream copy . The system of record is where a value is authored and corrected. A warehouse table is a copy, shaped by transformation rules, refresh lags and filters someone chose years ago for a reporting purpose. Copies are usually easier to access and are often perfectly adequate — but you must know which you are using and ask what the transformation dropped. Corrections and deletions are the classic casualty: warehouses frequently keep only current state, so the record of what a value was at decision time, which point-in-time correctness demands, has already been overwritten.
External and Third-Party Data
Weather, credit, firmographics, geospatial, market prices, benchmark panels and industry datasets can supply signal your organization cannot generate. Four questions decide whether a feed is usable:
Cost — per record, per seat, per call, or annual license, and whether that cost recurs for the operational life of the model rather than only during the project.
Licensing and permitted use. This is the gate project managers skip. A license that permits internal analysis may forbid training a model, redistributing derived outputs, or embedding results in a commercial product. Get permitted use confirmed in writing by procurement and legal before the data enters the pipeline.
Refresh and continuity guarantees — what the agreement promises about refresh cadence, schema stability, historical restatement and notice of change.
Control. A model whose most important feature comes from a vendor feed inherits that vendor's pricing power, outage risk and right to discontinue. Ask now what happens to the model if the feed stops, and record the answer as a risk; it reappears in Domain V contingency planning.
Cloud and Distributed Repositories
Modern data is rarely in one place: object storage buckets, regional databases, subsidiary systems and partner platforms. Establish two things for each — where the data physically sits, and what may cross a border. Data residency rules, whether national law or contractual commitment, may prohibit copying data out of a region, which can force training to happen where the data lives rather than where the platform team would prefer. Egress charges and network paths turn a 'free' internal dataset into a real line item. Multi-entity organizations regularly discover that the same customer table exists in five regions with five schemas and five owners, and that consolidating it is a project in its own right.
Legacy Systems and Archives
The history-depth requirement set in Task 1 is what usually forces this excavation. Deep history lives in the least accessible places: decommissioned mainframe extracts, tape or cold-storage archives, a vendor system nobody has logged into since the migration, fixed-width flat files with no schema. Establish three things. Can anyone still read the format and restore it? Does documentation or living expertise survive — this is where the SMEs from Task 2 matter most? And has retention policy already deleted what you need, which is common and non-negotiable. Recovering three years of pre-migration history is a work package with a cost, a duration and an owner, not a footnote in a status report.
Ownership, Permissions and Lead Time
For every source, document the owner (accountable for the data), the steward (defines and maintains it), the approver (grants access), the classification (public, internal, confidential, regulated), the approved purpose , and the typical approval duration . That last field is what the exam cares about. Approval for a regulated source can take weeks — privacy review, security review, contract amendment, environment provisioning — and it sits on your critical path whether or not you tracked it. Surface access lead time as a schedule risk with a real date, and start the longest approvals on day one of Data Understanding. Detailed privacy clearance is a separate Domain III task; here you are establishing that a path exists and how long it takes.
Data Source Inventory Template
Data element Source and type Owner / approver Access method Permitted use Access lead time Recorded risk
Monthly usage by account Billing platform — internal, system of record Billing operations director / IT security Nightly extract to project workspace Internal analytics, already approved ~2 weeks Only 13 months retained online; older history sits in archive
Support ticket narratives Support SaaS platform — external, free text Head of support / vendor administrator Rate-limited API export Internal analytics; contains personal data, privacy review required 4–6 weeks Personal data in free text creates a redaction work package
Regional weather history Third-party provider — licensed feed Procurement / vendor account manager Licensed API, annual fee License must be confirmed to cover model training 6+ weeks including contracting Recurring cost for the model's life; discontinuation risk
Keep the inventory alive through the phase. It becomes the input to data gathering, the evidence behind the data-sufficiency go/no-go, and the reference the operations team needs at handover.
The Trap: Existence Is Not Availability
The exam repeatedly punishes the assumption that because data exists somewhere, the project can use it. Between existence and use sit ownership, classification, consent and permitted purpose, technical readability, retention limits, residency rules, cost and an approval queue. Treat a source as unavailable until you have a named approver, a stated purpose and a realistic date. And when a source turns out to be genuinely unusable, that is a Data Understanding finding to escalate — feeding back into scope, the business case or the solution design — not a problem to route around by quietly substituting a convenient dataset nobody has assessed.