7.3 Configuration Management and Version Verification
Key Takeaways
- Configuration management is the technical and administrative discipline concerned with identifying, tracking, controlling, and auditing the physical and functional characteristics of project deliverables throughout their lifecycle.
- While change control governs the evaluation and decision to modify project baselines, configuration management manages the actual technical versions, documentation, and integrity of configuration items (CIs).
- The five core activities of configuration management are Configuration Planning, Configuration Identification, Configuration Control, Configuration Status Accounting (CSA), and Configuration Audit & Verification.
- A Configuration Item (CI) is any uniquely identifiable entity—hardware, software, blueprint, specification, or manual—subjected to configuration governance.
- Configuration audits consist of Functional Configuration Audits (verifying performance against specification) and Physical Configuration Audits (verifying that the physical as-built product matches design drawings).
7.3 Configuration Management and Version Verification
Definition (APM BoK7 glossary): Configuration management encompasses the technical and administrative activities concerned with the creation, maintenance, controlled change and quality control of the scope of work. A configuration is the functional and physical characteristics of a product as defined in its specification and achieved through the deployment of project management plans.
BoK7 states the payoff of a well-controlled configuration management process in two lines worth remembering: confidence that the current version of any configuration item is known, and documented traceability between versions of each configuration item.
Modern projects rarely produce simple, isolated deliverables. Whether constructing a high-speed passenger train, commissioning a biopharmaceutical cleanroom, or deploying a cloud-based enterprise resource planning (ERP) platform, project outputs are complex systems composed of hundreds or thousands of interrelated components, technical drawings, software scripts, operational manuals, and interface protocols.
If project teams fail to maintain strict version control and technical traceability over these components, catastrophic failures occur: civil contractors build from superseded blueprints, avionics technicians install outdated circuit boards, or software engineers overwrite critical code modules. Configuration Management provides the systematic technical discipline that ensures that every component is uniquely identified, changes are controlled, current states are recorded, and as-built outputs match approved specifications.
Configuration Management vs Change Control
A primary area of conceptual confusion for project practitioners is the relationship between Configuration Management and Change Control. While closely intertwined, they operate with distinct focuses and operational responsibilities.
+-----------------------------------------------------------------------------------------+
| CONFIGURATION MANAGEMENT VS CHANGE CONTROL |
+-----------------------------------------------------------------------------------------+
| CHANGE CONTROL | CONFIGURATION MANAGEMENT |
| - Focus: Decision-making governance | - Focus: Product integrity & version |
| - Evaluates: Proposed baseline changes | - Manages: Physical & digital assets |
| - Answers: 'Should we make this change?' | - Answers: 'What version is this, |
| - Driven by: Cost, schedule, business case | and does it match design?' |
| - Artifacts: Change Request, Change Log, CCB | - Artifacts: CIs, Status Accounting, |
| | Baselines, Audits (FCA / PCA) |
+-----------------------------------------------------------------------------------------+
The Symbiotic Relationship
Change control is the decision-making engine: it assesses whether a proposed modification to a baseline should be approved, rejected, or deferred based on time, cost, quality, and risk. However, change control does not physically label components, track document revisions, or audit assembly lines.
Configuration management provides the technical infrastructure and execution discipline: it identifies the specific assets affected by a change, locks down baseline files to prevent unapproved edits, records the current revision history, and performs rigorous physical inspections to verify that completed items conform to engineering drawings. In short:
- Change Control evaluates and approves the modification;
- Configuration Management identifies the items, prevents unapproved tampering, records the updated status, and verifies that the physical result matches the revised technical definition.
Comparative Analysis: Configuration Management vs Change Control
| Dimension | Configuration Management | Change Control |
|---|---|---|
| Core Purpose | Preserving technical integrity, version consistency, and deliverable traceability. | Governing and authorizing changes to agreed project performance baselines. |
| Primary Focus | The physical, digital, and functional attributes of deliverables (product scope). | The contractual baselines of scope, schedule, budget, and quality (project scope). |
| Key Question | What is the exact configuration, version, and build state of this deliverable? | Is this proposed modification justified, affordable, and approved by governance? |
| Core Activities | Planning, Identification, Control, Status Accounting, Verification Audit. | Log change request, Initial evaluation, Detailed evaluation, Recommendation, Update plans, Implement. |
| Primary Artifacts | Configuration Management Plan, CI Register, CMDB, Audit Reports (FCA / PCA). | Change Request (CR), Change Log / Register, CCB Minutes, Baselines. |
| Governing Roles | Configuration Manager, Configuration Librarian, Quality Assurance Auditors. | Project Sponsor, Change Control Board (CCB), Project Manager. |
The Five Core Activities of Configuration Management
The APM Body of Knowledge structures configuration management into five sequential, continuous activities that operate throughout the project life cycle.
+-----------------------------------------------------------------------------------------+
| 5 CORE CONFIGURATION MANAGEMENT ACTIVITIES |
+-----------------------------------------------------------------------------------------+
| 1. PLANNING --> 2. IDENTIFICATION --> 3. CONTROL |
| - Strategy & roles - Define CIs - Check-in / check-out |
| - Tools & CMDB - Unique naming - Change control linkage |
| - Baseline rules - Set Baselines - Tamper prevention |
| |
| --> 4. STATUS ACCOUNTING --> 5. AUDIT & VERIFICATION |
| - Traceability history - Functional Audit (FCA) |
| - Current state logs - Physical Audit (PCA) |
| - Reporting to PM - Conformance verification |
+-----------------------------------------------------------------------------------------+
1. Configuration Planning
The initial activity establishes the governance framework for configuration management across the project. It defines the strategy, processes, standards, and repositories documented in the Configuration Management Plan (CMP).
Key planning decisions include:
- Defining the criteria for what constitutes a Configuration Item;
- Selecting software tools and secure repositories (e.g., Configuration Management Databases [CMDB], enterprise document management systems, Git version control systems);
- Establishing roles and responsibilities, such as appointing a Configuration Manager and Configuration Librarian;
- Defining the frequency and triggers for configuration audits and baseline freeze milestones.
2. Configuration Identification
Configuration identification involves breaking down the project deliverables into discrete, uniquely identifiable components called Configuration Items (CIs), establishing their attributes, and locking initial Configuration Baselines.
Key identification activities:
- Selecting Configuration Items (CIs): Determining the appropriate level of granularity. If set too high (e.g., treating an entire locomotive as a single CI), control is ineffective; if set too low (e.g., treating every single bolt as a separate CI), administrative bureaucracy paralyzes delivery;
- Establishing Naming and Numbering Conventions: Devising unambiguous alphanumeric coding schemes that encode component family, hierarchy, and version (e.g.,
HVAC-COMP-04-v2.1); - Documenting Attributes: Recording for each CI its title, owner, technical specifications, dependencies, and interfaces with other CIs;
- Declaring Configuration Baselines: Establishing formal technical reference points (e.g., Functional Baseline at requirements freeze, Allocated Baseline at design freeze, Product Baseline at manufacture). Once baselined, a CI cannot be modified without formal change control.
3. Configuration Control
Configuration control ensures that no additions, deletions, modifications, or version revisions occur to a baselined Configuration Item without passing through the formal Change Control process.
Key control mechanisms include:
- Check-in / Check-out Mechanics: Storing baselined documents, code, or digital engineering models in secure digital vaults. When an authorized engineer needs to make an approved change, the CI is "checked out" (locking it against edits by others) and "checked back in" as a new revision level once verified;
- Enforcing Change Authorization: The Configuration Librarian will not check out a CI or accept an updated version into the repository without an approved Change Request (CR) signed by the CCB or Sponsor;
- Preventing Version Divergence: Eliminating situations where multiple engineers work on disconnected copies of the same design, ensuring the project maintains a single source of technical truth.
4. Configuration Status Accounting (CSA)
Configuration Status Accounting (CSA) is the administrative tracking and reporting function of configuration management. It records the complete lifecycle journey and real-time status of every Configuration Item.
CSA answers essential operational questions:
- What is the current approved version of this drawing, component, or code module?
- What formal Change Requests have been approved against this CI, and which have been implemented?
- Who modified this component, when did they modify it, and under what authorization?
- What predecessor versions exist, and what are their technical differences?
By maintaining an unbroken audit trail of versions and modifications, CSA provides stakeholders with complete visibility into deliverable maturity and prevents confusion across geographically dispersed delivery teams.
5. Configuration Audit and Verification
While Status Accounting records what should exist on paper or in databases, Configuration Audit and Verification provides independent physical and operational inspection to confirm that deliverables actually conform to approved specifications.
The APM recognizes two distinct, vital types of configuration audits:
A. Functional Configuration Audit (FCA)
The FCA evaluates performance and functional capability. It examines formal test data, simulation reports, and commissioning results to prove that the Configuration Item achieves all operational and performance requirements set out in its technical specification.
- Core Question: Does it perform as designed?
- Example: Testing an emergency train brake assembly in a high-speed dynamometer rig to verify that stopping distance is under 450 meters at 160 km/h in wet conditions.
B. Physical Configuration Audit (PCA)
The PCA evaluates build conformity and physical integrity. It involves physically inspecting the as-built deliverable against engineering blueprints, part lists, wiring schematics, and materials manifests to confirm that all authorized components are correctly installed and no unapproved modifications exist.
- Core Question: Is it built as designed?
- Example: Opening the train electrical cabinet and physically verifying that every circuit breaker model, cable gauge, component part number, and label matches the approved engineering assembly drawing.
Together, the FCA and PCA ensure that the customer receives a verified, compliant asset, providing the contractual foundation for formal client acceptance, warranty activation, and operational handover.
What is the primary operational objective of Configuration Status Accounting (CSA) within a project governance framework?
Before an aerospace manufacturer formally hands over a specialized satellite communications system to the client, an independent quality team conducts two audits: first, verifying flight telemetry test logs to ensure signal bandwidth meets specifications; second, opening the chassis to physically verify that every transponder part number matches the engineering schematics. How are these two audits classified?
How does Configuration Management interact with the Change Control process when a technical design change is requested on an approved mechanical component?