Enterprise-grade Configuration Management Plan aligned to SAE/EIA-649C, SAE/EIA-649-1, and MIL-HDBK-61B
CMP-001-2026
Rev C
2026-03-25
UNCLASSIFIED
APPROVED
CM Authority
Product Lifecycle Management System
Digital Engineering & Configuration Intelligence Platform
Prepared in accordance with:
SAE/EIA-649C • SAE/EIA-649-1 • MIL-HDBK-61B
Document Number
CMP-001-2026
Revision
C
Date
25 March 2026
| Rev | Date | Author | Description | Approved By |
|---|---|---|---|---|
| C | 2026-03-25 | CM Authority | Major revision - SAE/EIA-649C alignment | Program Manager |
| B | 2025-11-15 | CM Manager | Added digital thread requirements | Program Manager |
| A | 2025-06-01 | CM Manager | Initial release | Program Manager |
Prepared By
Configuration Management Authority
Signature / Date
Electronically Signed - 2026-03-25
Approved By
Program Manager
Signature / Date
Electronically Signed - 2026-03-25
This Configuration Management Plan (CMP) establishes the comprehensive framework, policies, processes, and procedures for implementing and maintaining configuration management across the BaseLinx PLM platform and all associated configuration items throughout the system lifecycle. This plan is designed to ensure product integrity, traceability, and control from concept through disposal.
The purpose of this CMP is to:
"Configuration management is a process for establishing and maintaining consistency of a product's performance, functional, and physical attributes with its requirements, design, and operational information throughout its life."
This CMP applies to all configuration items managed within or interfacing with the BaseLinx PLM platform, including:
This Configuration Management Plan is authorized by the Program Manager and is binding upon all organizational elements, contractors, subcontractors, and suppliers involved in the design, development, production, test, and sustainment of products managed within the BaseLinx PLM platform.
| Organization | Full CMP | Change Control | Status Accounting | Audit Support |
|---|---|---|---|---|
| Prime Contractor | ● | ● | ● | ● |
| Subcontractors (Critical) | ● | ● | ● | ● |
| Suppliers (Tier 1) | ◐ | ● | ● | ◐ |
| Suppliers (Tier 2+) | ○ | ◐ | ◐ | ○ |
The primary industry standard for configuration management, defining the five core CM functions and establishing the framework for planning, identifying, controlling, status accounting, and verifying configuration throughout the product lifecycle.
Supplemental requirements specific to defense contracts, addressing government interface requirements, Class I/II change classifications, Configuration Control Board operations, and contractual CM deliverables.
Department of Defense handbook providing detailed implementation guidance for configuration management throughout the acquisition lifecycle, including milestone alignment, technical reviews, and baseline management.
| CM Function | SAE/EIA-649C | SAE/EIA-649-1 | MIL-HDBK-61B | CMP Section |
|---|---|---|---|---|
| CM Planning | Section 4 | Section 3 | Chapter 3 | Section 3 |
| Configuration Identification | Section 5 | Section 4 | Chapter 4 | Section 5 |
| Configuration Control | Section 6 | Section 5 | Chapter 5 | Section 6 |
| Status Accounting | Section 7 | Section 6 | Chapter 6 | Section 7 |
| Verification & Audit | Section 8 | Section 7 | Chapter 7 | Section 8 |
It is the policy of this organization that all products, systems, and services shall be developed, produced, and sustained under a disciplined configuration management program that ensures product integrity, supports informed decision-making, and maintains the digital thread from requirements through verification.
This policy mandates that:
Ensure products conform to requirements and design intent throughout their lifecycle
Maintain complete trace from requirements through design, build, test, and operation
Provide accurate, timely visibility of configuration status to all stakeholders
Prevent unauthorized changes and ensure changes are properly evaluated and approved
Ensure compliance with contractual, regulatory, and organizational requirements
Enable reproduction of any product configuration at any point in its lifecycle
The BaseLinx PLM platform serves as the authoritative operational environment for configuration management. This system provides comprehensive capabilities for managing the complete product lifecycle from requirements through sustainment, including:
| Application | Purpose | Data Flow | Integration Type |
|---|---|---|---|
| CAD Systems (CATIA, NX, SOLIDWORKS) | Design data, drawings, models | Bi-directional | Native API |
| ERP (SAP, Oracle) | Part master, BOMs, inventory | Bi-directional | Web Services |
| Requirements (DOORS, Jama) | Requirements, traceability | Bi-directional | OSLC/REST |
| ALM/DevOps (Jira, GitHub) | Issues, code, builds | Bi-directional | REST API |
Per SAE/EIA-649C and MIL-HDBK-61B, the following baselines are established and maintained within the BaseLinx PLM platform. Each baseline represents a formally approved set of configuration documentation at a specific point in the product lifecycle.
System-level functional requirements
CI-level performance specs
Detailed design & TDP
As-fielded configuration
| Baseline | Establishment Point | Content | Change Authority |
|---|---|---|---|
| Functional Baseline (FBL) | System Requirements Review (SRR) | System Performance Specification (Type A) | Government/Customer CCB |
| Allocated Baseline (ABL) | Preliminary Design Review (PDR) | Development Specifications (Type B) | Government/Customer CCB |
| Product Baseline (PBL) | Critical Design Review (CDR) / FCA/PCA | Product Specifications (Type C), TDP | Contractor CCB (Class II) / Govt (Class I) |
| Operational Baseline (OBL) | Initial Operational Capability (IOC) | As-Fielded Configuration | Sustaining CCB |
Configuration Items (CIs) are selected based on the criteria defined in SAE/EIA-649C Section 5.2. The following factors determine CI selection:
| Attribute | Description | Required | Example |
|---|---|---|---|
| Part Number | Unique identifier per naming convention | AVN-5500-001 | |
| Revision | Current revision level | C | |
| Title/Name | Descriptive name | Avionics Bay Assembly | |
| CI Type | Classification of configuration item | HWCI | |
| Lifecycle State | Current state in workflow | Released | |
| Owner | Responsible engineer/organization | Avionics IPT | |
| Classification | Security/export classification | ITAR Controlled | |
| Baseline | Associated configuration baseline | Optional | PBL Rev 3 |
| Effectivity | Serial/lot applicability | Optional | S/N 001-050 |
Configuration control ensures that changes to baselined configuration items are properly identified, documented, evaluated, approved, implemented, and verified. The change management process within BaseLinx PLM follows the workflow defined below.
Originator submits change request with justification
Engineering evaluates technical, schedule, cost impacts
Determine Class I (Major) or Class II (Minor)
Configuration Control Board evaluates and approves
Approved change is released for implementation
Change is incorporated into design/production
Verify change implementation is complete and correct
ECO closed, baseline updated
Per SAE/EIA-649-1 and MIL-HDBK-61B, changes are classified based on their impact on form, fit, function, interchangeability, safety, reliability, or contractual requirements.
A change that affects one or more of the following baseline attributes:
A change that does NOT affect any of the following:
Program Manager or designated representative. Has final approval authority.
| Change Type | Cost Impact | Schedule Impact | Approval Authority |
|---|---|---|---|
| Class I - Any Impact | Any | Any | Government/Customer CCB |
| Class II - High Impact | > $100K | > 30 days | Program CCB |
| Class II - Medium Impact | $10K - $100K | 7 - 30 days | IPT CCB |
| Class II - Low Impact | < $10K | < 7 days | CM Manager |
Configuration Status Accounting (CSA) provides the means to record, track, and report the status of configuration items and changes throughout the lifecycle. The BaseLinx PLM platform maintains comprehensive status accounting records including:
| Report | Description | Frequency |
|---|---|---|
| Configuration Item List | Complete listing of all CIs with current status | Weekly |
| Change Status Report | All open/pending changes with status | Weekly |
| Baseline Status Report | Current baseline content and changes | Monthly |
| Variance Report | Active deviations and waivers | Monthly |
Configuration verification ensures that configuration items conform to their documented requirements and that the configuration documentation accurately represents the physical configuration. BaseLinx PLM supports the following verification activities:
The FCA verifies that the actual performance of a CI meets the requirements stated in its functional and allocated configuration documentation. Per MIL-HDBK-61B:
The PCA verifies that the CI as built conforms to the product baseline documentation. Per MIL-HDBK-61B:
| Activity | PM | CM Mgr | Chief Engr | QA | Mfg | CCB |
|---|---|---|---|---|---|---|
| ECR Initiation | I | C | R | I | C | I |
| Impact Analysis | I | C | A/R | C | C | I |
| Change Classification | I | R | A | C | I | I |
| CCB Review | I | R | C | C | C | A |
| ECO Approval | I | R | C | C | I | A |
| Implementation | I | C | A | C | R | I |
| Verification | I | C | C | A/R | C | I |
| Baseline Update | I | A/R | C | I | I | I |
An agreed-upon description of the attributes of a product at a point in time.
An aggregation of hardware, software, or both that is designated for configuration management.
A process for establishing and maintaining consistency of a product's performance with its requirements.
END OF DOCUMENT
Configuration Management Plan • CMP-001-2026 Rev C • BaseLinx PLM
This document is controlled. Verify currency before use.