Meaning
A formally approved specification of a product’s hardware and software components at a specific point in time establishes a foundation for future development and release control. Engineers establish a configuration baseline to ensure all teams work with identical schematics, bill of materials, and firmware revisions. This reference point guarantees that subsequent modifications can be tracked and evaluated against a known operational state.
Reference Specification
System integrators build their testing protocols around the documented state of the assembly as defined by the master files. When a product enters mass production, the current configuration baseline dictates the exact part numbers and firmware versions loaded onto the assembly line. This lock prevents unauthorized component substitutions by the contract manufacturer.
Change Management
Modifications to the locked design files require a formal engineering change proposal before any revision to the assembly is permitted. Sourcing and engineering teams analyze the impact of any proposed change against the current configuration baseline to evaluate compatibility and regulatory impact. When a change is approved, a new baseline is created, and the old one is archived to maintain design history.
This structured progression ensures that firmware and hardware revisions remain synchronized throughout the product lifecycle.
Audit Procedure
Verification audits compare the physical units rolling off the line against the approved documentation. If the bill of materials differs from the configuration baseline, the quality team halts production to resolve the discrepancy.