Configuration Management

AS9100-aligned knowledge and project tool for identifying configuration items, establishing baselines, controlling change, defining effectivity, maintaining configuration status and verifying the as-built product.

Configuration Management in simple terms
The key question: “Exactly what is this product, what requirements apply to it, what changes have been incorporated, and can we prove it?”

Configuration Management (CM) keeps the authorised product definition and the real product aligned throughout its life. It connects requirements, drawings, BOMs, software, materials, manufacturing instructions, special processes, inspection, test, approved changes, concessions and the as-built record.

1. PlanScope, roles, rules and tools
2. IdentifyConfiguration items and baselines
3. Control ChangeAssess, approve and implement
4. Account for StatusKnow what applies and what is embodied
5. AuditVerify records and product agree

Document control is not the same as configuration management

Document control can tell you that Drawing 12345 is at Revision F. CM should allow you to determine which revision, BOM, software, process specifications, approved changes and deviations apply to a particular serial number or lot — and whether the physical product agrees with that record.

Baselines

Complex programmes may use a functional baseline (what the product must do), an allocated baseline (how requirements are allocated to configuration items) and a product baseline (the detailed definition used to build, verify, deliver and support the product). The exact baseline structure should be appropriate to the organisation, product and contract.

AS9100 alignment

AS9100 clause 8.1.2 is the central CM requirement. CM also interacts with documented information, design and development changes, external-provider controls, production, identification and traceability, release, nonconforming outputs and first article inspection. This app is guidance and a project aid; customer, regulatory and contractual requirements always take precedence.

Example: controlled electronics assembly change
A simple example of why effectivity and status accounting matter.
Assembly P/N 456789 changes from Rev B to Rev C because of a PCB change. There are completed units, WIP, supplier stock and units in qualification. The change is impact-assessed, approved, supporting documents are updated and Rev C is made effective from S/N 000121. The CM record preserves which earlier serial numbers remain Rev B and which changes, concessions or rework each unit contains.
Project Definition & Configuration Management Plan
Baseline Definition
Configuration Element Library
Select relevant elements to build the project baseline. The app contains a built-in library and can also load the CSV from https://sp-i.org/files/cm.csv when hosted there.
UseIDCategoryElementDescriptionCM ActivityReference
Project Configuration Items
Add product-specific identifiers, revisions, owners and baseline status.
CI IDCategoryConfiguration Item / DocumentPart / Doc No.Revision / VersionOwnerBaselineStatusNotes
Configuration Change Register
A robust change should have a reason, impact assessment, approval, implementation point and verification.
Change IDTitle / DescriptionReasonAffected CIsImpact AssessmentApproval / CCBEffectivityStatusVerification / Evidence
Change ProposedECR / problem / improvement
Impact AssessmentEngineering, quality, operations, supply chain, safety, cost
AuthoriseChange authority / CCB / customer
ImplementUpdate definition and set effectivity
Verify & AccountConfirm embodiment and update status
Configuration Status Accounting
Status accounting is the ability to report the current and historical configuration: approved baselines, change status, effectivity, deviations and what has actually been incorporated.
0Configuration items
0Changes
0Open changes
0%Assurance complete
Product / Serial Configuration Trace
Serial / LotPart NumberBaseline / RevSoftware / FirmwareEmbodied ChangesConcessions / DeviationsFAI / VerificationAs-Built Status
CM Assurance Checklist
Use this as a project health check or supplier audit aid. Evidence should be objective and product-specific.
Audit technique
Pick a real serial number or lot and walk the chain: contract/PO → requirements → drawing/model → BOM → manufacturing plan → work instructions/programmes → special processes → inspection/test → approved changes → deviations/concessions → FAI → CofC/release → as-built configuration. Ask: Can you demonstrate that this product represents the authorised configuration at the point it was manufactured and delivered?
Project Review & Output
Important use note
This tool supports configuration-management planning, education and record-building. It does not reproduce proprietary AS9100 or ISO standard text and does not itself demonstrate compliance. Apply the organisation's approved QMS, contractual requirements, customer-specific requirements and regulatory obligations.