Configuration Management Checklist
Quality & Inspection Standards
PRODUCTS CENTER
Get Custom Quote
PRODUCTS CENTER
Configuration Management Checklist
Configuration management is the discipline of maintaining consistency between a product's physical attributes, its functional characteristics, and its documented requirements throughout the product lifecycle. Under GJB9001C, configuration management is not merely a best practice — it is a mandatory requirement that ensures product integrity, change traceability, and mission success.
For PCB manufacturers serving military and aerospace programs, configuration management means that every design revision, every process change, and every material substitution is formally identified, controlled, accounted for, and audited. GJB 3206B-2022 establishes the technical state management framework with four core activities: configuration identification, configuration control, configuration status accounting, and configuration verification and audit.This checklist transforms these requirements into actionable verification items for PCB manufacturing operations.
Engineering Summary
- GJB9001C Clause 8.3.2(o) requires implementation of technical state management measures and compilation of technical state file lists.
- GJB 3206B-2022 establishes the four-activity framework: configuration identification, configuration control, configuration status accounting, and configuration verification and audit.
- Configuration baselines (functional, allocated, product) must be established and maintained throughout the product lifecycle.
- Design changes must comply with technical state management requirements per GJB 3206B.
- Configuration status accounting records must document the evolution of technical states and enable full traceability.
1. Why Configuration Management Matters in Military PCB Manufacturing
In military and aerospace applications, the consequences of configuration errors are severe — from mission failure to loss of life. Configuration management ensures that every PCB delivered to the warfighter is built to the correct design, with the correct materials, using the correct processes.
| Configuration Management Benefit | Why It Matters |
|---|---|
| Design Integrity | Ensures that the product matches the approved design documentation — document-to-document consistency, document-to-product consistency. |
| Change Traceability | Every change to the product or its documentation is recorded, reviewed, approved, and traceable. |
| Interchangeability | Configuration management ensures that products with the same configuration are form, fit, and function interchangeable. |
| Regulatory Compliance | GJB9001C and military contracts mandate configuration management. Non-compliance results in rejected shipments and program delays. |
| Product Supportability | Accurate configuration records enable effective sustainment, repair, and upgrade over the product's service life. |
KEY INSIGHT:
Configuration management is the backbone of quality assurance in military manufacturing. A product that meets all performance requirements can still be rejected if configuration records are incomplete or inconsistent.
2. GJB9001C Configuration Management Requirements
2.1 Clause 8.3.2 — Design and Development Planning
Clause 8.3.2 establishes the planning requirements for design and development, including specific configuration management obligations:
- 8.3.2(o): Implement measures for technical state management and compile a technical state file list.
- 8.3.2(p): Apply product optimization design and professional engineering techniques including general quality characteristics design and human factors engineering.
- 8.3.2(s): Identify and propose support resources required for product delivery.
- 8.3.2(x): For products using digital design and manufacturing, establish process control requirements for information transfer, data conversion, and technical state management.
2.2 Clause 8.3.6 — Design and Development Changes
Clause 8.3.6 requires that design changes comply with technical state management requirements:
- Design changes shall comply with technical state management requirements.
- Software changes shall comply with software configuration management requirements.
- Organizations shall track the implementation of design changes.
- Important design changes shall undergo systematic analysis and verification, and shall be approved through prescribed procedures.
- Documented information shall be retained for: design changes, review results, change authorization, and measures taken to prevent adverse effects.
2.3 GJB 3206B-2022 — Technical State Management Framework
GJB 3206B-2022 establishes the comprehensive framework for technical state management, superseding GJB 3206A-2010. The standard defines four core activities:
| Activity | Description | PCB Implementation |
|---|---|---|
| Configuration Identification | Determine configuration items and required technical state documents; identify configuration items and documents; establish and maintain baselines | PCB part numbers, revision schemes, baseline documentation packages |
| Configuration Control | Control change applications, deviation permits, and concessions through Argument, evaluation, coordination, approval, and implementation | ECR/ECO/ECN processes for PCB changes |
| Configuration Status Accounting | Record and report technical state control status; maintain traceability of technical state evolution | Revision histories, configuration status reports |
| Configuration Verification and Audit | Verify product conformance to technical state documentation; conduct functional and physical configuration audits | First Article Inspection, configuration audits |
CRITICAL REQUIREMENT:
GJB 3206B requires that "The physical weapons and equipment match the corresponding documents exactly." — the physical product must maintain consistency with its documentation, and documentation must maintain internal consistency.
3. Configuration Management Framework — Core Concepts
3.1 Configuration Items
A configuration item is a part of a product that requires configuration management. Configuration items typically include components that have significant impact on product performance, functionality, or reliability.
For PCB manufacturing, configuration items typically include:
- PCB Bare Board: Gerber files, fabrication drawing, stackup specification
- PCB Assembly: Assembly drawing, bill of materials, component placement files
- Test Fixtures: Test specifications, test procedures, acceptance criteria
- Process Documentation: Work instructions, process control documents, setup sheets
3.2 Configuration Baselines
A configuration baseline is the formally approved technical state of a product at a specific point in time. Baselines provide the reference point for subsequent design, production, test, and sustainment activities.
| Baseline Type | Description | PCB Example |
|---|---|---|
| Functional Baseline | Established at the conclusion of requirements definition — defines functional characteristics | PCB performance requirements, electrical specifications |
| Allocated Baseline | Established at the conclusion of design allocation — defines allocated requirements for configuration items | Layer stackup, material specifications, design rules |
| Product Baseline | Established at the conclusion of production — defines as-built product configuration | Released Gerber files, fabrication drawings, BOM |
3.3 Configuration Status Accounting
Configuration status accounting is the activity of formally recording and reporting the technical state control status throughout the product lifecycle. It ensures that technical state evolution is fully traceable.
Key records include:
- Technical state file approval records
- Configuration item identification records
- Baseline establishment records
- Change application and approval records
- Version upgrade records
- Deviation permit and concession records
- Configuration audit records
4. Configuration Identification for PCB Manufacturing
Configuration identification is the foundation of configuration management. It involves determining configuration items, establishing technical state documentation, and applying unique identifiers.
4.1 Product Structure
Product structure describes the hierarchical composition of a product, showing the relationships and quantities of its constituent elements.
For PCB manufacturing, the product structure typically includes:
- Level 0: Finished PCB Assembly
- Level 1: Bare PCB, Components, Solder, Solder Mask
- Level 2: Laminate, Prepreg, Copper Foil (for bare PCB); Individual Components (for assembly)
- Level 3: Raw materials (glass fabric, resin, copper)
4.2 Configuration Item Identification
Each configuration item and its associated documents must be assigned a unique identifier following a consistent naming convention.
- Part Number: Unique identifier for each PCB configuration (e.g., PCB-12345-001)
- Document Number: Unique identifier for each technical document (e.g., FAB-12345-001)
- Revision Identifier: Indicates the current revision (e.g., Rev A, V1.0)
- Serial Number: Unique identifier for individual units (for component-level traceability)
5. Configuration Control for PCB Manufacturing
Configuration control ensures that changes to the product or its documentation are properly identified, evaluated, approved, and implemented.
5.1 Change Classification
Changes should be classified based on their impact:
- Class I (Major): Changes affecting form, fit, function, or interchangeability — require customer approval
- Class II (Minor): Changes that do not affect form, fit, or function — internal approval
- Emergency Changes: Changes required to address urgent issues — expedited approval process
5.2 Change Control Process
The change control process follows a structured workflow:
- Change Initiation: Change need identified — Engineering Change Request (ECR) created
- Change Evaluation: Impact assessment, cross-functional review, risk analysis
- Change Approval: Formal approval by authorized personnel — Engineering Change Order (ECO) issued
- Change Implementation: Documentation updated, production process revised
- Change Verification: Verification that change was implemented correctly
- Change Closure: Records updated — Engineering Change Notice (ECN) issued
6. Complete Configuration Management Checklist for PCB Manufacturers
Use this comprehensive checklist to assess and improve your configuration management system against GJB9001C and GJB 3206B requirements.
| # | Check Item | Reference | Status | Evidence |
|---|---|---|---|---|
| Section A: Configuration Management Planning | ||||
| A1 | Configuration management plan is established and documented | GJB 3206B | ☐ | |
| A2 | Configuration management roles and responsibilities are defined | GJB 3206B | ☐ | |
| A3 | Technical state management measures are implemented per 8.3.2(o) | 8.3.2(o) | ☐ | |
| A4 | Technical state file list is compiled and maintained | 8.3.2(o) | ☐ | |
| Section B: Configuration Identification | ||||
| B1 | Configuration items are identified and documented | GJB 3206B | ☐ | |
| B2 | Product structure is established | GJB 3206B | ☐ | |
| B3 | Unique identifiers are assigned to all configuration items and documents | GJB 3206B | ☐ | |
| B4 | Technical state documents are identified for each configuration item | GJB 3206B | ☐ | |
| B5 | Document identification includes title, date, author, and revision | GJB 3206B | ☐ | |
| Section C: Configuration Baselines | ||||
| C1 | Functional baseline is established and documented | GJB 3206B | ☐ | |
| C2 | Allocated baseline is established and documented | GJB 3206B | ☐ | |
| C3 | Product baseline is established and documented | GJB 3206B | ☐ | |
| C4 | Baseline documentation is formally approved and released | GJB 3206B | ☐ | |
| C5 | Baseline changes are controlled through formal change process | GJB 3206B | ☐ | |
| Section D: Configuration Control | ||||
| D1 | Change control procedure is documented and implemented | GJB 3206B | ☐ | |
| D2 | Change classification (Class I/II/Emergency) is defined | GJB 3206B | ☐ | |
| D3 | Engineering Change Requests (ECRs) are used to initiate changes | 8.3.6 | ☐ | |
| D4 | Change impact assessments are performed and documented | 8.3.6 | ☐ | |
| D5 | Changes are approved by authorized personnel before implementation | 8.3.6 | ☐ | |
| D6 | Design changes comply with technical state management requirements | 8.3.6 | ☐ | |
| D7 | Software changes comply with software configuration management requirements | 8.3.6 | ☐ | |
| D8 | Change implementation is tracked and verified | 8.3.6 | ☐ | |
| D9 | Deviation permit and concession procedures are defined | GJB 3206B | ☐ | |
| Section E: Configuration Status Accounting | ||||
| E1 | Configuration status accounting procedure is established | GJB 3206B | ☐ | |
| E2 | Technical state file approval records are maintained | GJB 3206B | ☐ | |
| E3 | Change application and approval records are maintained | GJB 3206B | ☐ | |
| E4 | Version upgrade records are maintained | GJB 3206B | ☐ | |
| E5 | Configuration status reports are generated and distributed | GJB 3206B | ☐ | |
| E6 | Records are archived and protected per requirements | GJB 3206B | ☐ | |
| Section F: Configuration Verification and Audit | ||||
| F1 | Configuration verification procedure is established | GJB 3206B | ☐ | |
| F2 | Configuration consistency checks are performed | GJB 3206B | ☐ | |
| F3 | Functional configuration audits are conducted | GJB 3206B | ☐ | |
| F4 | Physical configuration audits are conducted | GJB 3206B | ☐ | |
| F5 | Audit findings are documented and corrective actions are tracked | GJB 3206B | ☐ | |
| Section G: PCB-Specific Configuration Items | ||||
| G1 | Gerber files are under configuration control with unique revisions | 8.3.6 | ☐ | |
| G2 | Fabrication drawings are under configuration control | 8.3.6 | ☐ | |
| G3 | Assembly drawings are under configuration control | 8.3.6 | ☐ | |
| G4 | Bill of Materials (BOM) is under configuration control | 8.3.6 | ☐ | |
| G5 | Stackup specifications are under configuration control | 8.3.6 | ☐ | |
| G6 | Test specifications are under configuration control | 8.3.6 | ☐ | |
| G7 | Process documents are under configuration control | 8.3.6 | ☐ | |
| Section H: Documented Information Requirements | ||||
| H1 | Design and development change records are maintained | 8.3.6 | ☐ | |
| H2 | Change review results are documented | 8.3.6 | ☐ | |
| H3 | Change authorization records are documented | 8.3.6 | ☐ | |
| H4 | Measures to prevent adverse effects are documented | 8.3.6 | ☐ | |
| H5 | Configuration management records are retained per requirements | 7.5.3 | ☐ | |
7. Configuration Management for Digital Design and Manufacturing
GJB9001C Clause 8.3.2(x) requires that for products using digital design and manufacturing, organizations establish process control requirements for information transfer, data conversion, and technical state management.
| Digital CM Area | Requirement | PCB Implementation |
|---|---|---|
| Information Transfer | Establish controls for digital information transfer between systems and stakeholders | Controlled file transfer protocols, data exchange formats |
| Data Conversion | Control data conversion processes to ensure integrity | Gerber to ODB++ conversion verification, format validation |
| Technical State Management | Apply configuration management to digital design artifacts | Version control for CAD files, revision management for digital data |
8. Audit Preparation Checklist
| # | Audit Check Item | What Auditors Verify | Status |
|---|---|---|---|
| 1 | Configuration management plan is documented and implemented | CM plan document, implementation evidence | ☐ |
| 2 | Configuration items are identified and documented | CI list, identification records | ☐ |
| 3 | Configuration baselines are established and documented | Baseline documentation, approval records | ☐ |
| 4 | Change control procedure is implemented | ECR/ECO/ECN records, approval signatures | ☐ |
| 5 | Design changes comply with technical state management requirements | Change records, GJB 3206B compliance evidence | ☐ |
| 6 | Configuration status accounting records are maintained | Status reports, revision histories, change logs | ☐ |
| 7 | Configuration audits have been conducted | Audit reports, findings, corrective actions | ☐ |
| 8 | Documented information is retained as required | Record retention policy, accessible records | ☐ |
| 9 | PCB documentation (Gerber, drawings, BOM) is under configuration control | Document revisions, change records, consistency checks | ☐ |
| 10 | Digital design and manufacturing configuration controls are implemented | Data transfer controls, conversion verification, version control | ☐ |
9. Common Audit Findings and How to Avoid Them
| Finding | Why It Happens | How to Avoid |
|---|---|---|
| "No configuration management plan" | CM requirements not formally documented | Develop and maintain a configuration management plan |
| "Configuration items not identified" | No systematic CI selection process | Establish CI selection criteria and maintain CI list |
| "No configuration baselines" | Baselines not formally established or documented | Establish functional, allocated, and product baselines |
| "Changes not controlled" | Changes made without formal approval | Implement ECR/ECO/ECN process; enforce approval before change |
| "No configuration status accounting" | Technical state not recorded or reported | Implement status accounting per GJB 3206B requirements |
| "Design changes not compliant with GJB 3206B" | Changes made without technical state management consideration | Ensure all design changes follow GJB 3206B requirements |
| "No configuration audits" | Audits not planned or conducted | Plan and conduct functional and physical configuration audits |
| "Documentation not coordinated" | Gerber revised but drawings not updated | Perform cross-document coordination checks before releasing revisions |
10. Frequently Asked Questions
What is configuration management under GJB9001C?
Configuration management is the discipline of maintaining consistency between a product's physical attributes, its functional characteristics, and its documented requirements. GJB9001C requires implementation of technical state management measures per Clause 8.3.2(o) and compliance with GJB 3206B.
What are the four activities of configuration management under GJB 3206B?
The four core activities are: configuration identification, configuration control, configuration status accounting, and configuration verification and audit.
What are configuration baselines?
Configuration baselines are formally approved technical states at specific points in time. The three baseline types are: functional baseline, allocated baseline, and product baseline.
What is the difference between Class I and Class II changes?
Class I (major) changes affect form, fit, function, or interchangeability and require customer approval. Class II (minor) changes do not affect form, fit, or function and can be approved internally.
What documents must be under configuration control for PCB manufacturing?
All technical documents must be under configuration control: Gerber files, fabrication drawings, assembly drawings, BOMs, stackup specifications, test specifications, and process documents.
What is configuration status accounting?
Configuration status accounting is the activity of formally recording and reporting the technical state control status throughout the product lifecycle. It ensures that technical state evolution is fully traceable.
How does GJB9001C Clause 8.3.6 relate to configuration management?
Clause 8.3.6 requires that design changes comply with technical state management requirements (GJB 3206B) and that software changes comply with software configuration management requirements.
Related Standards & Topics
PCB Manufacturing for Military and Aerospace Programs
UltroNiu Electronics Group provides PCB and PCBA manufacturing services with full GJB9001C-compliant configuration management. Contact our engineering team to discuss your program's configuration management requirements.
Request Engineering ReviewReferences: GJB9001C-2017 Clauses 8.3.2, 8.3.6; GJB 3206B-2022 Technical State Management; GJB 5235-2004 Military Software Configuration Management. Configuration management framework sourced from GJB 3206B-2022 implementation guidance. Configuration baseline concepts sourced from GJB 3206B-2022. Courtesy of UltroNiu Engineering Knowledge Center.
Get Custom Quote
PRODUCTS CENTER
World-class PCB & PCBA manufacturer focused on high-frequency and high-reliability boards for defense, aerospace, automotive and industrial electronics.
You can unsubscribe at any time with a single click.
Copyright © 2025 UltroNiu Electronics Group All Rights reserved.
Sorry, there is currently no content in the current column
You can check other sections
Business License