Glossary

Product genealogy

Product genealogy is the as-built record linking a product to its materials, components, lots, processes, and quality history.

Data Integration, Security and Trust Data Integrity, Version Control and Audit Trails Traceability and Genealogy

Product genealogy is the structured record of how a product was actually made, including the materials, components, lots, serial numbers, process steps, equipment, inspections, and quality events linked to it. It describes the as-built or as-manufactured history of a unit, batch, or lot.

In manufacturing systems, product genealogy is commonly used for traceability, containment analysis, quality investigations, recall scoping, and digital thread data models. It may include parent-child relationships between assemblies and subassemblies, material consumption records, split and merge events, rework history, timestamps, operator or station records, and inspection results.

Product genealogy should not be confused with a bill of materials or routing. A bill of materials defines the intended product structure, and a routing defines the planned sequence of operations. Product genealogy records what actually happened during production. It is also narrower than traceability as a general capability, because traceability includes the systems, procedures, and data controls used to follow products and materials across the lifecycle.

Serial number traceability supports back-to-birth records by giving each unit a persistent identifier that can be linked to material, process, inspection, configuration, nonconformance, and shipment records. It does not create a complete history by itself; the underlying data, integrations, and change controls must be reliable.

Why is configuration management so critical to product safety?

Configuration management is critical to product safety because safety depends on the exact approved combination of design, software, materials, process parameters, and service changes actually used in the field. When that baseline is unclear or uncontrolled, plants can build, inspect, ship, or repair against the wrong revision and lose traceability needed to assess risk, contain defects, and manage change.

How long must NCR records be retained in aerospace programs?

There is no single aerospace-wide retention period for NCR records. Retention is usually driven by the strictest applicable requirement: customer contract, purchase order flowdown, regulatory obligation, QMS procedure, and program-specific quality clauses. Some records may need to be kept for many years or longer for critical parts.

How can digital systems reduce errors in manual lot tracking spreadsheets?

Digital systems can reduce lot tracking errors, but not by automation alone. The main gains come from controlled data entry, barcode scanning, system-enforced genealogy, version control, and audit trails tied to ERP, MES, QMS, and receiving records. Results depend on master data quality, process discipline, integration reliability, and validation in the actual plant environment.

Related Glossary