CAIM study materials
CAIM study resources

CAIM key terms

CAIM · Get comfortable with the vocabulary.

AI governance framework

A documented system of roles, policies, decision rights, and controls that directs how an organization selects, builds, deploys, and retires AI systems, and how it evidences accountability to stakeholders.

Related: Model risk tiering, AI policy
AI strategy alignment

The practice of tying AI initiatives to explicit enterprise goals, operating model choices, and measurable outcomes so that investment decisions trace back to business priorities rather than to technology enthusiasm.

Related: Value hypothesis, AI use case portfolio
AI policy

A written set of mandatory rules stating which AI uses are permitted, prohibited, or require approval, who may approve them, and what evidence must be retained to demonstrate compliance.

Related: AI governance framework, Acceptable use policy
Model risk tiering

Classification of AI systems into risk levels based on potential harm, autonomy, data sensitivity, and regulatory exposure, which then determines the depth of testing, documentation, and oversight each system receives.

Related: Model risk management, Human oversight
AI use case portfolio

The managed inventory of candidate and active AI initiatives, ranked by expected value, feasibility, risk, and dependencies, used to sequence funding and staffing decisions across the organization.

Related: Value hypothesis, AI strategy alignment
Value hypothesis

A testable statement linking a proposed AI capability to a specific business outcome, a baseline metric, an expected magnitude of change, and the timeframe in which that change should be observable.

Related: Business case, Benefits realization
Business case

The structured justification for an AI investment covering costs, expected benefits, assumptions, risks, alternatives considered, and the decision criteria used to fund or reject the initiative.

Related: Total cost of ownership, Value hypothesis
Total cost of ownership (TCO)

The full lifecycle cost of an AI solution, including data preparation, compute, integration, licensing, monitoring, retraining, support staff, and eventual decommissioning, not just initial build spend.

Related: Business case, Run cost versus change cost
Benefits realization

The discipline of measuring whether an AI initiative delivered the outcomes promised in its business case, comparing actual metrics against baselines and triggering corrective action when gaps persist.

Related: Value hypothesis, KPI instrumentation
Run cost versus change cost

The separation of ongoing operating expense for a live AI system from one-time investment to build or substantially modify it, which clarifies budget ownership and reveals the true cost of scaling.

Related: Total cost of ownership (TCO)
Data quality dimensions

The measurable attributes of data fitness for use, typically completeness, accuracy, consistency, timeliness, uniqueness, and validity, each assessed against thresholds defined by the consuming AI use case.

Related: Data lineage, Training-serving skew
Data lineage

A recorded trace of where data originated, how it was transformed, and where it flowed, enabling impact analysis, root-cause investigation, and defensible answers when regulators or auditors ask about model inputs.

Related: Feature store, Data quality dimensions
Feature store

A shared platform component that computes, stores, and serves model input variables consistently to both training pipelines and live inference, reducing duplicated logic and inconsistency between phases.

Related: Training-serving skew, MLOps
Training-serving skew

A degradation in production performance caused by differences between how input data was prepared during model training and how it is prepared or arrives during live inference, including schema, timing, or transformation drift.

Related: Feature store, Data drift
Data drift

Change over time in the statistical distribution of production input data relative to the data a model learned from, which can silently erode accuracy even when the underlying relationship has not changed.

Related: Concept drift, Model monitoring
Concept drift

Change over time in the true relationship between model inputs and the target outcome, meaning the patterns a model learned no longer describe the world it is now asked to predict.

Related: Data drift, Model retraining trigger
MLOps

The set of engineering practices, automation, and platform tooling that moves models from experimentation into reliable production operation, covering versioning, testing, deployment, monitoring, and retraining.

Related: CI/CD for models, Model registry
Model registry

A catalog that records each model version with its training data references, parameters, evaluation results, approvals, and deployment status, providing the audit trail for what is running and why.

Related: MLOps, Model documentation
CI/CD for models

Automated pipelines that test, validate, package, and release model or prompt changes through controlled environments, so that updates pass the same quality and approval gates as software code.

Related: MLOps, Shadow deployment
Shadow deployment

A release pattern in which a new model runs alongside the incumbent on live traffic without affecting decisions, allowing performance comparison under real conditions before any cutover.

Related: Canary release, Champion-challenger testing
Canary release

A staged rollout that exposes a small, monitored fraction of live traffic to a new model version, expanding exposure only if error, latency, and quality metrics stay within agreed thresholds.

Related: Shadow deployment, Rollback plan
Champion-challenger testing

A continuous evaluation method where the current production model is compared against one or more candidate models on the same live or replayed traffic using predefined success metrics.

Related: Shadow deployment, Model retraining trigger
Model retraining trigger

A defined condition, such as drift exceeding a threshold, accuracy falling below a floor, or a scheduled interval elapsing, that automatically initiates review and possible retraining of a production model.

Related: Concept drift, Model monitoring
Model monitoring

Continuous collection and review of production signals such as input distributions, prediction distributions, accuracy where labels exist, latency, and error rates to detect degradation and incidents.

Related: Data drift, Observability
Observability

The degree to which an AI system's internal state can be inferred from its emitted logs, metrics, and traces, enabling teams to diagnose failures and explain behavior without reproducing them offline.

Related: Model monitoring, Incident response
Human oversight

Deliberate human involvement in an AI system's decisions or outputs, ranging from review of individual cases to monitoring aggregate behavior, calibrated to the risk and reversibility of harm.

Related: Human in the loop, Model risk tiering
Human in the loop

A design in which a person must review and approve an AI recommendation before any consequential action is taken, retaining human authority over the outcome in the workflow.

Related: Human oversight, Automation bias
Automation bias

The human tendency to accept automated recommendations uncritically, which can make nominal human review meaningless unless reviewers receive conflicting evidence, training, and authority to overrule.

Related: Human in the loop
Bias testing

Systematic evaluation of model behavior across demographic and other protected groups to detect disparate error rates, representation gaps, or outcome disparities before and after deployment.

Related: Fairness metric, Model documentation
Fairness metric

A quantified criterion for comparing model outcomes across groups, such as equal error rates, demographic parity, or calibration by group, chosen with awareness that some definitions conflict mathematically.

Related: Bias testing
Explainability

The ability to give accurate, understandable reasons for a specific AI output or for the model's overall behavior, at a level of detail appropriate to the audience and the decision's stakes.

Related: Model documentation, Human oversight
Model documentation

A structured record of a model's purpose, intended use, training data, evaluation results, known limitations, and owners, kept current so reviewers and auditors can assess fitness without reverse engineering.

Related: Model registry, Explainability
Risk-based regulation

A regulatory approach that imposes obligations proportional to the likelihood and severity of harm a system can cause, with stricter requirements for higher-risk uses and lighter ones for minimal-risk uses.

Related: Model risk tiering, AI policy
Data protection impact assessment

A structured pre-deployment review of how an AI system processes personal data, identifying privacy risks, legal bases, retention limits, and mitigations, usually required before high-risk processing begins.

Related: Purpose limitation, AI policy
Purpose limitation

The privacy principle that personal data collected for one stated purpose may not be repurposed for unrelated uses, such as training a model, without a compatible legal basis and appropriate transparency.

Related: Data protection impact assessment
AI literacy program

Structured training that gives staff at different roles the understanding of AI capabilities, limitations, risks, and obligations they need to use or oversee these systems responsibly.

Related: Center of excellence, Role-based enablement
Center of excellence

A central team that sets standards, provides reusable assets and expertise, and coaches distributed business teams, balancing consistency in practice against local speed of delivery.

Related: AI literacy program, Federated operating model
Federated operating model

An organizational design in which a central group owns shared platforms and guardrails while business units own their own AI use cases, products, and outcome accountability.

Related: Center of excellence, AI governance framework
Role-based enablement

Learning and support tailored to what a specific job function must do with AI, distinguishing executives, developers, risk reviewers, and frontline users rather than delivering one generic curriculum.

Related: AI literacy program
Change management

The structured work of preparing people for an AI-enabled process change through communication, involvement, training, and reinforcement so that adoption persists after launch.

Related: Adoption metric, Role-based enablement
Adoption metric

A measure of whether intended users actually use an AI capability in the intended way, such as active usage, override rate, or workflow coverage, distinct from model accuracy.

Related: Benefits realization, Change management
KPI instrumentation

The deliberate embedding of measurement into an AI workflow so that baseline and post-deployment values of business metrics are captured automatically and can be attributed to the intervention.

Related: Benefits realization, Adoption metric
Incident response

A documented process for detecting, triaging, containing, communicating, and learning from AI failures or harmful outputs, including defined severity levels, owners, and escalation paths.

Related: Rollback plan, Observability
Rollback plan

A pre-tested procedure for reverting a model, prompt, or configuration to a known-good version quickly when production behavior breaches acceptable thresholds.

Related: Canary release, Incident response
AI acceptable use policy

Rules that specify permitted tools, data types, and behaviors for employees using AI, including prohibitions on entering confidential information into unapproved external services.

Related: AI policy, Shadow AI
Shadow AI

Use of AI tools or models by employees without organizational approval or visibility, creating unmanaged data exposure, inconsistent outputs, and gaps in the governance record.

Related: AI acceptable use policy, AI governance framework