Product Genealogy Systems Selection Guide
Compare genealogy routes using actual lot/serial resolution, capture events, relationships, system ownership, exceptions and known-history trace results.
Compare product-genealogy routes using the same input/output identities, transformation events and trace questions. Test whether each option can explain a known split, combination, return, substitution and rework history at the identity level actually captured.
Start with the identifier and relationship rules and review the capture-to-trace sequence. Include missing, duplicate, late and offline events, corrections and record ownership. Do not infer serial-level certainty from batch-only input evidence.
Compare options in the conditions where they must work — Product Genealogy Systems
Plan product genealogy systems around your identifiers, substrates, production events, system interfaces, exceptions and verification records. Discuss a practical data-flow approach with Oxford Traceability. A useful shortlist should show how every option copes with identifier and data rules for component-to-product genealogy records and exception, rework and duplicate handling.
Discuss your application
Ask every supplier the same questions
| Decision | What to ask | What to check |
|---|---|---|
| Identity and relationship definition | Where are lot identities sufficient and where is a true individual serial captured? | Identifier/source definitions, input/output relationships and limits on the precision of trace claims. |
| Mark, label, tag or read evidence | Can the intended identifier be captured on the actual substrate and operating route? | Identified samples, readability checks and separate checks that the data and product association are correct. |
| Capture point and production conditions | Which real event establishes consumption or assembly, and what happens during movement, change and interruption? | Station/order/output association, quantities/units, returns and actual operating exceptions. |
| System and record ownership | Which source owns each identifier, event, relationship and correction? | Mapped handovers, identifiers, acknowledgement/reconciliation responsibilities and incomplete states. |
| Exception, substitution and rework rules | How are missing, duplicate, late or offline events and changed composition represented? | Known exception histories, actual fitted identities, preserved previous state and authorised correction decisions. |
| Trace and reconciliation evidence | Do backward and forward results explain the same known history? | Expected/observed outputs for splits, combinations, returns and rework, with unresolved events and identity-resolution limits visible. |
Include simpler approaches to component-to-product genealogy records in your shortlist
| Approach | Often suitable when | Watch for |
|---|---|---|
| Defined component-to-product genealogy route | The required lot/serial relationships and capture events can be identified and tested. | Use actual consumption and assembly evidence; a planned bill of materials or readable code alone is insufficient. |
| Label-Based Identification where Direct Marking Is Unsuitable | The agreed item/material identity is carried on a label appropriate to the actual substrate and operating route. | Trial physical readability, correct data and product association over the stated use conditions. A label or scan does not establish actual consumption or complete genealogy. |
| Direct-Part Marking where Lifecycle and Substrate Justify It | The agreed identity must be associated with the actual part under the stated substrate and lifecycle conditions. | Trial the proposed mark/read method and its identity association. Preserve the same input/output, exception and reconciliation rules; readable marking alone is not a complete product history. |
Pause before choosing when…
- Only perfect or hand-selected examples of production identification using component-to-product genealogy records are available.
- No one has defined how verification, retention and reconciliation evidence will be evaluated.
- The normal range for identifier and data rules for component-to-product genealogy records is described only as “usually fine” but has not been bounded.
- Your operator, cleaning, maintenance or recovery access has not been considered.
- Quoted performance depends on another machine or data source that is not included.