CMII (Configuration Management II)

CMII is the configuration-management methodology and certification developed by Vincent Watts and the Institute of Configuration Management (ICM), widely cited in CIMdata material as a vendor-neutral framework for closed-loop change. Where ISO 10007 and EIA-649 give guidelines, CMII gives an opinionated, prescriptive process model centered on getting the requirements clear, complete, and consistent before changes are released — and tightly integrating change control with the document and product structure.

Core principles (paraphrased from the ICM model)

• Clarity, completeness, consistency of requirements as a precondition for release.
• Closed-loop change — every change tracks back to a discrepancy in requirements or in the as-released configuration.
• Single change form instead of separate ECR/ECO/ECN proliferation; status drives the workflow.
• Fast-track changes for low-risk changes; full review for risk-bearing changes.
• Effectivity (see effectivity) and baselining as first-class concepts.
• Training and certification — CMII practitioners are formally certified.

Position vs ISO 10007

ISO 10007 defines what configuration management is. CMII defines how to do it — a process design plus role definitions plus tooling expectations. They are complementary; many regulated programs cite both.

Relationships (see sidebar)

• Normative for ECO, ECN, ECR, Change Control Board, Classification Schema, and the PLM Data Model.

Steward

Institute of Configuration Management (ICM); not an ISO standard but cross-referenced in CIMdata, NDIA, and aerospace/defense contracts.