Study guide
Manage Data Transformation and Data Preparation
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 Data Transformation and Data Preparation
Key Takeaways Explain This Topic AI
CPMAI Phase 3 Data Preparation is routinely the largest single block of effort on an AI project and the phase most consistently under-estimated when the schedule is written.
Cleaning choices are business rulings in disguise: whether a blank means zero or unknown, and whether an outlier is an error or the fraud you are hunting, are SME decisions that must be recorded rather than defaulted by an analyst.
The exact transformations used in training must run identically in production; scaling constants, imputation defaults, and category vocabularies are learned artifacts that ship and version with the model, and train/serve skew is a leading production failure.
Synthetic data can rebalance a rare class or protect privacy in development, but it cannot create information that was never observed, and a model validated only on synthetic data is not validated.
A transformation applied by hand and left undocumented is a defect even when the model performs well, because the prepared dataset can no longer be regenerated, audited, or retrained.
Last updated: August 2026
Phase 3 Is Where the Project Actually Spends Its Time
CPMAI Phase 3, Data Preparation , converts the raw data you accepted at the Domain III data-sufficiency gate into a dataset a model can actually be trained on. It is routinely the largest single block of effort on an artificial intelligence (AI) project, and it is the phase most consistently under-estimated when the schedule is drawn up. PMI publishes no figure for how much of a project it should consume, and the widely quoted percentages come from surveys of how data scientists spend their week rather than from project accounting, so plan it from your own phase estimates and record the actual against them at closeout. Schedules that budget Phase 3 as a short technical step are the ones that slip.
ECO Domain IV, Task 4 does not ask you to write the transformations. It asks you to manage them: to ensure the decisions buried inside them are made by the right people, recorded, and reproducible. Nearly every trap in this task is a technically competent transformation applied by the wrong authority or left undocumented.
Cleaning and Preprocessing: Business Decisions in Disguise
A data engineer cleaning a claims table makes rulings that look technical and are not.
Missing values. A blank field can mean "not applicable", "not captured by this channel", or a genuine zero. Each meaning implies a different treatment — drop the row, impute a value, or add an explicit "unknown" indicator. Only a subject-matter expert (SME) knows which applies, and the wrong choice quietly teaches the model something false.
Outliers. Removing extreme values steadies some model families. But in fraud detection, anomaly monitoring, or equipment-failure prediction, the outliers are the target class. "Remove or keep" is a business ruling about what the model exists to find.
Duplicates and entity resolution. When two customer records match imperfectly, someone must decide which is the system of record and how conflicting fields are merged. That is a data-governance decision, not a scripting preference.
Your job is to force each ruling to be explicit rather than defaulted by whoever happened to open the notebook. Every ruling gets a named decider and a written entry in the data preparation log — the document that answers the auditor or the puzzled business owner two years later.
Feature Engineering: Where Domain Knowledge Enters the Model
Feature engineering turns raw fields into the signals a model learns from: transactions in the last 24 hours, days since last service, the ratio of claim amount to policy limit, whether a shipment crossed a weekend. This is the single point in the lifecycle where human expertise is deliberately injected, so convene the SME sessions yourself and insist features are defined in business language before they are coded.
Ask one question of every proposed feature: will this value be available, with the same meaning, at the moment of prediction? A field that is only populated after the outcome is known produces a spectacular model and a worthless one. (The formal check for that belongs to the readiness gate in the next section.)
Feature selection is a management trade-off, not a purity exercise. Each retained feature buys marginal signal and creates a permanent liability: an upstream source to monitor, a data contract with another team, another way the pipeline breaks at 3 a.m. Ask what a feature costs to maintain for three years, not just what it adds to a validation score.
Normalization, Standardization, and the Production Rule
Some model families compute distances or gradients across features, so a field measured in millions swamps one measured in single digits unless the values are rescaled. Normalization (compressing to a fixed range) and standardization (recentring around a common mean and spread) remove that artifact. Tree-based models are largely indifferent; distance-based and neural models are not. That is the whole depth a manager needs: the model family determines whether scaling is required .
The operational rule matters far more than the mathematics. The exact same transformations must run in production as in training. Scaling constants, imputation defaults, and the vocabulary of known categories are learned artifacts : fitted on training data, then versioned and shipped alongside the model rather than recomputed from whatever arrives at serving time. When production recomputes them, identical inputs are transformed differently than in training, scores drift for no visible reason, and the team chases a phantom modeling problem. This mismatch — train/serve skew — is a leading cause of AI systems that evaluate beautifully and underperform on day one.
Augmentation and Synthetic Data: Use and Limits
Data augmentation creates additional training examples from existing ones; synthetic data generation creates artificial records that imitate the statistical structure of real ones. Both have legitimate uses:
Rare-class balancing — a fraud rate of 0.3 percent gives an algorithm almost nothing to learn from, so the minority class is amplified in training.
Privacy-preserving development data — engineers build and test against synthetic records rather than real patient or customer data.
Rarely observed conditions — augmented images of a defect type that appears twice a year.
The limits are absolute and the exam tests them. Synthetic data cannot create information that was never observed. A generator trained on a population that barely contains self-employed applicants cannot invent what they really look like; it reproduces and amplifies whatever bias the seed data carried, and can collapse onto a narrow band of repeated patterns. Two rules follow. Augmentation and balancing apply to the training split only , never to validation or test. And a model validated only on synthetic data is not validated — final evaluation runs on real, observed records at the real event rate. Synthetic data also inherits the privacy classification of its seed.
Reproducibility and Documentation
Transformations live in versioned pipeline code , not in an analyst's notebook or a spreadsheet. The test is blunt: given the same raw extract, can the pipeline be re-run today and produce the same prepared dataset? If not, you cannot investigate a production incident, retrain on a comparable basis, or answer an auditor. Pin a dataset version identifier to every model version, keep the decision log of SME rulings with it, and require that any correction — however small — be implemented in the pipeline rather than applied by hand.
Transformation decision Business question behind it Who decides Production implication
Missing-value handling Does a blank mean zero, not applicable, or not captured? Data SME with the process owner; PM records the ruling The imputation default is a shipped artifact and must be applied identically at serving time
Outlier treatment Is an extreme value an error, or the event we are trying to detect? Risk or fraud SME Removing outliers can delete exactly the class the model must predict
Duplicate and entity resolution Which record is the system of record when two customers match? Data governance or data owner Serving must resolve identity by the same rule or one entity is scored twice
Feature construction Which signals does an expert actually use to make this call today? SME plus data scientist; PM convenes Each feature becomes a permanent upstream dependency to monitor
Feature selection and pruning Is the marginal accuracy worth maintaining this feed for three years? PM with product owner and data engineering Fewer features mean a smaller integration surface and cheaper monitoring
Normalization and standardization Which model family are we using, and is it sensitive to scale? Data science lead; PM records as configuration Scaling constants ship and version with the model, never recomputed live
Categorical encoding What should happen when an unseen category arrives in production? Data scientist with the SME Needs a defined fallback for unknown values or the endpoint fails
Class balancing and augmentation Is this class rare in reality, or rare only in our sample? SME with data science Training split only; the decision threshold must be recalibrated to real prevalence
Synthetic data generation Are we closing a privacy gap, or inventing evidence we never collected? Privacy or legal with data science Final evaluation must still run on real observed records
Regenerability, Not Performance, Is the Acceptance Test
A transformation applied by hand and undocumented is a defect, even when the model performs well . Performance is not the acceptance criterion for Phase 3 work; regenerability is. When a scenario tells you an analyst corrected records in a spreadsheet, fixed a join manually, or tuned a threshold "just for this run", the correct managerial response is to have the change reimplemented in the versioned pipeline and the dataset regenerated — not to log a risk and move on.