Configuration Status Accounting
Quality & Inspection Standards
PRODUCTS CENTER
Get Custom Quote
PRODUCTS CENTER
Configuration Status Accounting Under GJB9001C
Configuration status accounting — referred to in Chinese military standards as "Technical Status Record" — is the formal activity of recording and reporting the technical state control status throughout the product lifecycle. GJB9001C Clause 8.1(i) requires organizations to "implement configuration identification, control, accounting, and audit" in accordance with GJB 3206. Configuration status accounting is the mechanism that ensures every change, every baseline, and every configuration item is documented, traceable, and reportable.
For PCB manufacturers, configuration status accounting means systematically recording and reporting the technical state of every PCB product throughout its lifecycle — from initial design through production, fielding, and sustainment. Without rigorous configuration status accounting, organizations cannot answer three fundamental questions: What is the current state of the product? Are changes controlled? Can historical states be traced?This guide provides a complete implementation roadmap covering the definition, standard requirements, work content, record and report types, PCB-specific applications, and audit preparation for configuration status accounting.
Engineering Summary
- Configuration status accounting is one of the four core activities of technical state management: identification, control, accounting, and audit.
- GJB9001C Clause 8.1(i) requires organizations to implement configuration status accounting per GJB 3206.
- Technical state accounting includes four work activities: recording, analysis and evaluation, reporting, and archiving and protection of configuration status information.
- GJB 3206B Appendix G specifies 10 categories of information to be recorded; Appendix H specifies 8 types of reports.
- For PCB manufacturers, status accounting covers Gerber revisions, BOM changes, material substitutions, process changes, and baseline updates.
- Key outputs include configuration item lists, baseline file lists, change control reports, and configuration status accounting reports.
1. What Auditors Check — A Quick Overview
| Audit Focus | What External Auditors Verify | Expected Evidence |
|---|---|---|
| Configuration Status Records | Are technical state records maintained for all configuration items? | Configuration item lists, baseline file lists, revision histories |
| Change Recording | Are all changes recorded with traceability to approval? | ECR/ECO/ECN records, change approval records, version upgrade records |
| Status Reporting | Are configuration status reports generated and submitted as required? | Configuration status reports, technical state control reports, customer reports |
| Traceability | Can the current technical state be traced back through all changes? | Complete revision histories, change logs, configuration status accounting databases |
| Analysis and Evaluation | Is configuration status information analyzed to identify trends and improvement opportunities? | Analysis reports, trend data, management review inputs |
| Archiving and Protection | Are configuration status records properly archived and protected? | Archived records, storage systems, access controls, retention schedules |
KEY INSIGHT:
Configuration status accounting answers three fundamental questions: What is the current state of the product? Are changes controlled? Can historical states be traced? Auditors will verify that all three questions can be answered with documented evidence.
2. Standard Requirements for Configuration Status Accounting
2.1 GJB9001C — The Foundational Requirement
GJB9001C-2017 Clause 8.1(i) establishes the foundational requirement for configuration status accounting: "In accordance with GJB 3206, determine technical state baselines and their technical state items, prepare a technical state management plan, and implement technical state identification, control, accounting, and audit".
This requirement makes configuration status accounting mandatory for all organizations in the military supply chain. It is not optional — it is a non-negotiable element of GJB9001C compliance.
2.2 GJB 3206B — The Technical State Management Framework
GJB 3206B-2022 is the definitive standard governing technical state management for weapons and equipment and their supporting products. Technical state management consists of four core activities:
- Technical State Identification — Determining technical state items and their required documentation
- Technical State Control — Controlling changes to technical state baselines
- Technical State Accounting — Recording and reporting the technical state control status
- Technical State Verification and Audit — Verifying product conformity to technical state documentation
Configuration status accounting is the "record and report" function that ensures the technical state evolution is fully traceable and transparent. It is the mechanism that provides visibility into what has changed, when it changed, who approved it, and what the current state is.
2.3 The "Three Questions" Principle
Configuration status accounting is designed to answer three fundamental questions about the product:
- Question 1: Is the current state of the product clear and documented?
- Question 2: Are state changes controlled and traceable?
- Question 3: Can historical states be traced and reconstructed?
If an organization cannot answer all three questions with documented evidence, its configuration status accounting system is inadequate.
3. Configuration Status Accounting — Definition and Purpose
3.1 Definition
Configuration status accounting — "Technical Status Record" in Chinese — is defined as the activity of recording and reporting configuration status information throughout the product lifecycle to describe the technical state of the product.
It is "the formal recording and reporting of established technical state documentation, proposed change status, and the implementation status of approved changes". This includes recording configuration items, configuration baselines, engineering changes, deviations, waivers, and their corresponding content.
3.2 Purpose
The purpose of configuration status accounting is to:
- Ensure traceability — Every change to the product's technical state is recorded and traceable
- Provide visibility — All stakeholders have visibility into the current technical state
- Support decision-making — Accurate status information enables informed decisions about changes
- Enable audits — Complete records support configuration audits and external assessments
- Facilitate sustainment — Historical records support long-term product support and maintenance
- Demonstrate compliance — Records provide evidence of compliance with GJB9001C and GJB 3206B requirements
3.3 Relationship to Other Configuration Management Activities
Configuration status accounting is the "memory" of the configuration management system:
- Configuration Identification defines what to track — status accounting tracks it
- Configuration Control manages changes — status accounting records them
- Configuration Audit verifies conformity — status accounting provides the baseline for verification
4. Configuration Status Accounting Work Content — The Four Activities
Under GJB 3206B, configuration status accounting consists of four primary work activities:
4.1 Recording of Configuration Status Information
The first activity is the systematic recording of configuration status information throughout the product lifecycle. This includes:
- Technical state file approval records
- Borrowing and copying records for technical state documents
- Change application reports
- Change approval records
- Version upgrade records
- Nonconformance review records
- Deviation and waiver records
For PCB manufacturers, recording includes tracking every revision of Gerber files, fabrication drawings, assembly drawings, BOMs, stackup specifications, and test specifications.
4.2 Analysis and Evaluation
GJB 3206B expanded the scope of configuration status accounting to include analysis and evaluation of configuration status information. This involves:
- Analyzing configuration status data to identify trends
- Evaluating the effectiveness of change control processes
- Identifying areas for improvement in configuration management
- Assessing configuration management performance
- Providing inputs to management reviews
For PCB manufacturers, analysis might include tracking change frequency by product type, identifying recurring change drivers (e.g., component obsolescence, customer requirement changes), and evaluating the effectiveness of the change control process.
4.3 Reporting
Reporting is the formal communication of configuration status information to stakeholders. Reports include:
- Configuration item lists
- Configuration baseline file lists
- Configuration status description reports
- Configuration control reports
- Configuration consistency check reports
- Configuration audit reports
- Configuration status accounting reports
- Configuration management self-assessment reports
Reports are typically submitted at major milestones (design reviews, qualification reviews, production readiness reviews) and as required by contract or technical state management plan.
4.4 Archiving and Protection
Configuration status information must be archived and protected to ensure long-term accessibility and integrity. This includes:
- Establishing retention periods for configuration status records
- Ensuring records remain readable and accessible throughout the retention period
- Protecting records against loss, damage, or unauthorized access
- Maintaining configuration status accounting databases or systems
- Ensuring records are available for audits and future reference
For PCB manufacturers, this means retaining complete configuration records for the full product lifecycle — which for military programs can be 20-30+ years.
5. Configuration Status Accounting Records and Reports
GJB 3206B provides specific guidance on what must be recorded and reported through two appendices:
5.1 Appendix G — Information to Be Recorded (10 Categories)
Appendix G specifies 10 categories of information that must be recorded:
| Category | Description | PCB Example |
|---|---|---|
| G.1 | Configuration item identification | PCB assembly, PCB bare board, software |
| G.2 | Configuration baseline documents | Functional, allocated, product baseline documentation |
| G.3 | Change requests and approvals | ECR/ECO/ECN records |
| G.4 | Change implementation status | Revision history, implementation records |
| G.5 | Deviation and waiver records | Deviation permits, concession records |
| G.6 | Configuration audit results | FAI reports, configuration audit reports |
| G.7 | Configuration status at milestones | PDR, CDR, production release status |
| G.8 | Interface control status | Interface control document revisions |
| G.9 | Software configuration status | Software version, firmware revision |
| G.10 | Other configuration status information | Obsolescence status, lifecycle information |
5.2 Appendix H — Required Reports (8 Types)
Appendix H specifies 8 types of reports that must be generated:
| Report Type | Description | PCB Application |
|---|---|---|
| H.1 | Configuration Item List | List all PCB configuration items with their identifiers |
| H.2 | Configuration Baseline File List | List all documents in functional, allocated, product baselines |
| H.3 | Configuration Status Description Report | Describe overall technical state of the PCB |
| H.4 | Configuration Control Report | Report all changes made during the reporting period |
| H.5 | Configuration Consistency Check Report | Verify consistency between documentation and product |
| H.6 | Configuration Audit Report | Report results of configuration audits |
| H.7 | Configuration Status Accounting Report | Comprehensive status summary and assessment |
| H.8 | Configuration Management Self-Assessment Report | Self-assessment of configuration management system |
PRACTICAL NOTE:
Appendix H is informative (non-mandatory). Organizations may tailor reports based on product complexity and contract requirements. However, the underlying information must still be recorded and available for audit.
6. PCB Configuration Status Accounting Scenarios — Practical Examples
6.1 PCB Configuration Item List
| CI Identifier | Description | Baseline | Current Revision | Status |
|---|---|---|---|---|
| PCB-001 | PCB Bare Board | Product Baseline | V2.1 | Released |
| PCB-001-ASSY | PCB Assembly | Product Baseline | V2.1 | Released |
| PCB-001-SW | Firmware | Product Baseline | V3.0 | Released |
| PCB-STACKUP-001 | Stackup Specification | Allocated Baseline | V1.2 | Released |
6.2 PCB Baseline File List
| Baseline Type | Document | Document Number | Revision | Approval Date |
|---|---|---|---|---|
| Functional | Customer Specification | CUST-SPEC-001 | Rev C | 2026-01-15 |
| Allocated | Stackup Specification | PCB-STACKUP-001 | V1.2 | 2026-03-20 |
| Product | Fabrication Drawing | PCB-FAB-001 | V2.1 | 2026-06-10 |
| Product | Gerber Files | PCB-GERBER-001 | V2.1 | 2026-06-10 |
| Product | Bill of Materials | PCB-BOM-001 | V2.0 | 2026-06-10 |
6.3 PCB Change Control Report
| ECR/ECN | Change Description | Impact | Approval Date | Implementation Status |
|---|---|---|---|---|
| ECR-2026-045 | Trace width adjustment 0.127mm → 0.150mm | Minor | 2026-03-20 | Implemented |
| ECR-2026-089 | Material substitution FR4 → High-frequency | Major (Class I) | 2026-06-10 | In Progress |
| ECR-2026-102 | Capacitor substitution (EOL) | Major (Class I) | 2026-07-15 | Approved |
7. Key Control Points in PCB Configuration Status Accounting
7.1 Configuration Item Identification
- Clearly identify all configuration items (CIs) in the PCB product structure
- Assign unique identifiers to each CI
- Document the relationship between CIs and their baselines
- Maintain a current configuration item list
7.2 Revision and Change Tracking
- Record every revision of every technical state document
- Link each revision to its ECR/ECO/ECN approval record
- Maintain complete revision histories for all documents
- Ensure change implementation status is tracked and recorded
7.3 Baseline Status Recording
- Record the approval and release of each baseline (functional, allocated, product)
- Document the composition of each baseline (which documents at which revisions)
- Record baseline changes and updates
- Maintain a baseline file list
7.4 Status Reporting
- Generate configuration status reports at major milestones
- Include configuration status in design review packages
- Report changes and their status to stakeholders
- Submit required reports to customers per contract requirements
7.5 Configuration Status Accounting System
- Implement a configuration status accounting database or system
- Ensure the system captures all required information
- Enable query and reporting capabilities
- Provide access controls and audit trails
- Ensure long-term data preservation
7.6 The "Three Documents" of Status Accounting
In Chinese military practice, configuration status accounting is often implemented through "three documents":
- Deviation Document (Deviation sheet / Technical Notice): Records temporary deviations from technical state documentation
- Change Document (Change Order): Records permanent changes to technical state documentation
- Query Document (Questioning Form): Records questions or challenges to technical state documentation
8. Audit Preparation Checklist for PCB Manufacturers
| # | Check Item | Clause | Status | Notes |
|---|---|---|---|---|
| Recording | ||||
| 1 | Configuration item list is maintained and current | GJB 3206B | ☐ | |
| 2 | Baseline file list is maintained and current | GJB 3206B | ☐ | |
| 3 | All changes are recorded with approval traceability | 8.3.6 | ☐ | |
| 4 | Deviation and waiver records are maintained | GJB 3206B | ☐ | |
| Analysis and Evaluation | ||||
| 5 | Configuration status information is analyzed for trends | GJB 3206B | ☐ | |
| 6 | Analysis results are used for process improvement | GJB 3206B | ☐ | |
| Reporting | ||||
| 7 | Configuration status reports are generated as required | GJB 3206B | ☐ | |
| 8 | Reports are submitted to customers per contract | 8.1(i) | ☐ | |
| Archiving and Protection | ||||
| 9 | Configuration status records are properly archived | GJB 3206B | ☐ | |
| 10 | Records are protected against loss and unauthorized access | 7.5.3 | ☐ | |
| 11 | Retention periods are defined and followed | 7.5.3 | ☐ | |
| Traceability | ||||
| 12 | Current technical state can be traced through all changes | GJB 3206B | ☐ | |
| 13 | Configuration status accounting records support audit traceability | GJB 3206B | ☐ | |
9. Common Audit Findings and How to Avoid Them
| Finding | Why It Happens | How to Avoid |
|---|---|---|
| "No configuration item list" | CIs not systematically identified and documented | Create and maintain a current configuration item list for all products |
| "Changes not recorded in status accounting" | Changes made but not entered into the status accounting system | Link change approval to status accounting update; make it a mandatory step |
| "No baseline file list" | Baseline composition not documented | Document every baseline with its constituent documents and revisions |
| "Reports not generated or submitted" | Reporting requirements not understood or ignored | Define reporting requirements in technical state management plan; assign responsibility |
| "No analysis of status information" | Status accounting seen as administrative rather than analytical | Incorporate analysis into status accounting process; use data for improvement |
| "Records not archived or protected" | No systematic archiving process | Implement document management system with archiving and retention capabilities |
| "Cannot trace current state to historical changes" | Incomplete revision history or change records | Maintain complete revision histories; link all changes to approvals |
10. Frequently Asked Questions
What is configuration status accounting?
Configuration status accounting — "技术状态记实" — is the activity of recording and reporting configuration status information throughout the product lifecycle to describe the technical state of the product. It is one of the four core activities of technical state management.
What are the four work activities of configuration status accounting?
The four activities are: recording of configuration status information, analysis and evaluation, reporting, and archiving and protection.
What must be recorded in configuration status accounting?
GJB 3206B Appendix G specifies 10 categories including: configuration item identification, baseline documents, change requests and approvals, change implementation status, deviation and waiver records, and configuration audit results.
What reports are required for configuration status accounting?
GJB 3206B Appendix H specifies 8 types of reports: configuration item list, baseline file list, status description report, control report, consistency check report, audit report, status accounting report, and self-assessment report.
What are the "three documents" of configuration status accounting?
In Chinese military practice, the "three documents" are: deviation document (technical notice), change document, and query document.
How does configuration status accounting differ from revision control?
Revision control is the mechanism for tracking document versions. Configuration status accounting is the broader activity of recording and reporting all technical state information — including baselines, changes, deviations, and audit results — to provide complete traceability of the product's technical state.
What is the purpose of analysis in configuration status accounting?
GJB 3206B expanded status accounting to include analysis and evaluation of configuration status information to identify trends, evaluate change control effectiveness, and identify areas for improvement.
How long must configuration status records be retained?
For military programs, configuration status records must be retained for the full product lifecycle — which can be 20-30+ years. Specific retention periods should be defined in the technical state management plan and comply with contract requirements.
Related Standards & Topics
PCB Manufacturing for Military and Aerospace Programs
UltroNiu Electronics Group provides PCB and PCBA manufacturing services under GJB9001C-compliant configuration status accounting. Contact our engineering team for program-specific configuration management and status reporting requirements.
Request Engineering ReviewReferences: GJB9001C-2017 Clause 8.1(i) (Central Military Commission Equipment Development Department); GJB 3206B-2022 Technical State Management; GJB 3206A-2010 Technical State Management. Technical state management four-activity framework sourced from GJB 3206B-2022. Configuration status accounting definition and work content sourced from GJB 3206B-2022. Appendix G and Appendix H recording and reporting requirements sourced from GJB 3206B-2022 implementation guidance. "Three documents" practice sourced from industry implementation of technical state accounting. PCB configuration status accounting practices based on industry best practices for military and aerospace PCB manufacturing. 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.
WhatsApp：8618823711371
Email：info@ultroniu.com
Message
Phone：+86 188 2371 1371
Tel：+86-0755-28788896