Key Takeaways
- Invest in as-built capture at the point of manufacture — retrospective reconstruction is expensive and incomplete
- Genealogy data must travel with the product when it changes hands — to service contractors, repair depots, and end customers
- A recall scope that requires physical inspection of every unit because genealogy data is absent costs orders of magnitude more than a recall bounded by traceable serial numbers
- As-maintained records are as important as as-built records for high-service-interval products — the service history is part of the product's identity
Short Answer
Product genealogy is the complete lifecycle record of a specific physical unit — what components went into it, which manufacturing lot they came from, which engineering revisions were in effect when it was built, what field modifications were made, and what service has been performed. It answers the question every quality engineer dreads hearing after a field failure: "exactly what was in that unit, and when did it change?"
- Product genealogy tracks individual unit history, not just the designed configuration — it records what actually happened to a specific serial number
- The as-built record captures the configuration at manufacture; the as-maintained record captures every subsequent change and service event
- Genealogy data is the foundation for recall scope determination — without it, manufacturers must recall entire populations rather than affected units
- Warranty claim processing depends on genealogy — without knowing a unit's build history, it is impossible to distinguish in-warranty failures from out-of-warranty ones
- Traceability to raw material lots and supplier batches is the deepest level of genealogy and is mandatory in food, pharma, and aerospace
What is Product Genealogy?
Product genealogy is the complete lifecycle history of a specific physical unit — not the designed product, but this serial number, this unit, the one on the floor of a repair depot or at a customer site or under investigation after a field failure. It records what components went into it, which engineering revision was in effect when each component was installed, which production lot the materials came from, what deviations from the design specification were authorized, what modifications were made after manufacture, and what service has been performed throughout the unit's operational life.
The distinction between product genealogy and product configuration is important. Configuration management answers "what should this product be?" — the approved BOM, the drawings, the specifications. Product genealogy answers "what is this unit actually?" — the as-built record, which may differ from the as-designed configuration due to effectivity windows, authorized substitutions, or deviation approvals, and the as-maintained record, which captures every subsequent change. For complex, long-lived products, these two answers diverge over time, and the divergence is the genealogy.
In regulated industries, maintaining complete product genealogy is a legal requirement. FAA requires airlines and MROs to maintain airworthiness records for the life of the aircraft — including every component replacement, repair, and service bulletin compliance event. FDA requires medical device manufacturers to maintain device history records (DHRs) that trace every device unit to its manufacturing records. Automotive manufacturers are increasingly required to maintain traceability through multiple tiers of the supply chain. In these contexts, product genealogy is not a quality initiative; it is the baseline obligation.
Why Product Genealogy Matters in PLM
The economic argument for product genealogy concentrates in three areas: recall management, warranty processing, and field failure investigation.
Recall management is the most visible. When a safety issue is identified — a component batch with a latent defect, a manufacturing process that produced out-of-tolerance parts for a specific build window — the scope question is paramount. A manufacturer with complete genealogy data can identify exactly which serial numbers received the affected component from the affected lot. A manufacturer without genealogy data must recall every unit of the model year, or the production run, or the entire model line. The cost difference between a bounded recall and an unbounded one can be an order of magnitude. The 2014 Takata airbag recall — which eventually covered hundreds of millions of vehicles globally — illustrates what happens when supply chain traceability data is insufficient to bound scope.
Warranty processing requires genealogy data to be defensible. A unit returned under warranty with a failed component may or may not be covered, depending on when the component was installed, which supplier lot it came from, and whether the failure mode matches the warranty conditions. Without a traceable as-built and as-maintained record, warranty decisions are guesswork — the manufacturer either pays claims it could legitimately deny or denies claims it should pay, both of which create risk.
Common Use Cases
- Recall scope determination: Manufacturers use lot traceability records in the as-built genealogy to identify exactly which serial numbers received components from a flagged supplier lot, bounding the recall to affected units and avoiding costly over-recall of unaffected inventory.
- Aviation MRO compliance: Aircraft operators and MRO facilities maintain as-maintained records for every airframe and component, tracking time-since-new, cycles-since-overhaul, and service bulletin compliance status — a regulatory requirement for continued airworthiness under FAA and EASA regulations.
- Field failure root cause investigation: Engineers use product genealogy to identify patterns in field failures — whether failures cluster around a specific build date, a specific component revision, or a specific manufacturing shift — enabling targeted corrective action rather than blanket design changes.
Related Concepts
- What is MBOM? — the manufacturing bill of materials from which as-built records are derived during production
- What is Supply Chain Traceability? — the upstream discipline of tracking components and materials back through the supply chain to their origin
- What is Digital Thread? — the data architecture that connects genealogy records across design, manufacturing, and service systems
Frequently Asked Questions
What is the difference between as-designed, as-built, and as-maintained?
As-designed is the engineering intent — the approved BOM and drawings that define how the product should be built. As-built is the actual configuration of a specific unit as it left the factory — which may differ from as-designed due to authorized deviations, component substitutions, or build-date effectivity differences. As-maintained is the running record of everything that has happened to that unit since it left the factory — field modifications, component replacements, repairs, and service events. All three layers together constitute the product genealogy of an individual unit.
How does product genealogy support recall management?
When a field failure or safety issue is identified, the first question is scope: which units are affected? Without genealogy data, the answer is "all units of this model" — which may mean hundreds of thousands of units when only a few thousand are actually at risk. With genealogy data, the investigation can trace back to the specific component lot, manufacturing batch, or build-date window and identify exactly which serial numbers received the affected component. This can reduce recall scope by 90% or more, saving enormous cost and avoiding unnecessary customer disruption.
What PLM data records constitute product genealogy?
Product genealogy draws from several PLM and manufacturing data sources: the as-built BOM (actual components used, at actual revision levels), shop traveler records (which operations were performed, by whom, with what tooling, on which date), inspection and test records (actual measured values, not just pass/fail), deviation and waiver records (authorized departures from the design specification), and as-maintained records from service and MRO systems. The PLM system is the backbone, but genealogy often requires integration with MES, ERP, and field service management systems to be complete.
Want to listen instead of read? 56 DemystifyingPLM articles are available as audio.
Browse audio →Looking up PLM terminology? Browse the canonical reference.
PLM Glossary →Cite this article
Finocchiaro, Michael. “What is Product Genealogy?.” DemystifyingPLM, May 16, 2026, https://www.demystifyingplm.com/what-is-product-genealogy
PLM industry analyst · 35+ years at IBM, HP, PTC, Dassault Systèmes
Firsthand knowledge of the evolution from early 3D modeling kernels to today's cloud-native platforms and agentic AI — the history, strategy, and future of PLM.