Yes. Part genealogy can usually be implemented without replacing existing ERP and PLM systems. In regulated manufacturing, that is often the more realistic approach because ERP and PLM replacement carries qualification burden, validation cost, downtime risk, integration complexity, and long asset lifecycle constraints. The practical pattern is to add or improve an execution and traceability layer, often MES or a connected quality/execution system, that uses ERP and PLM data while capturing the as-built record on the shop floor.
The important distinction is that ERP, PLM, MES, and QMS do not usually own the same truth. PLM typically manages design intent, engineering structure, documents, and revision control. ERP typically manages demand, orders, inventory, purchasing, costing, and planning. MES or an execution system is usually where serial numbers, lot consumption, operations performed, operator actions, equipment use, inspection results, deviations, rework, and signoffs are captured at production depth.
What has to be integrated
Part genealogy depends on reliable links between planned, designed, and executed data. The minimum integration scope usually includes:
- Part numbers, revisions, and effectivity from PLM or controlled engineering sources.
- Work orders, production orders, inventory lots, and material transactions from ERP.
- Routings, operations, work instructions, and inspection requirements from MES, PLM, ERP, or a controlled hybrid model.
- Serial, lot, batch, and component consumption records captured during execution.
- Nonconformance, MRB, rework, concession, and disposition records from QMS or MES.
- Supplier lot and certificate references where purchased material traceability is required.
The architecture is site-specific. Some plants use ERP as the system of record for orders and inventory, PLM for released engineering data, MES for execution, and QMS for nonconformance and CAPA. Others have legacy MES functions embedded in ERP or paper-based travelers that must be digitized gradually. The right design depends on current system ownership, validation status, data quality, and how much traceability is required by program, customer, product risk, or regulation.
Where implementations fail
Genealogy projects fail when they assume that integration alone creates traceability. It does not. The data model must define how a physical part, serial number, lot, operation, revision, material issue, inspection result, and nonconformance relate to each other. If those identifiers are inconsistent across ERP, PLM, MES, and QMS, the genealogy will be incomplete or misleading.
Common failure modes include uncontrolled part revision changes, duplicate item masters, weak lot controls, manual backflushing, late transaction entry, paper travelers that are not reconciled, missing supplier lot links, and rework paths that are not captured with enough detail. Integration latency can also matter. A genealogy record built from overnight batch updates may be acceptable for some reporting use cases, but not for real-time containment or release decisions.
Another risk is overcustomizing the integration to match today’s process exceptions. In brownfield plants, exceptions are real, but hard-coding every workaround can create a brittle system that is difficult to validate and maintain. A better approach is usually to define controlled exception workflows with audit trails, approvals, and clear data ownership.
What should not be assumed
Implementing part genealogy does not automatically make records compliant, audit-ready, or acceptable to a customer or regulator. The system must be validated for its intended use where required, governed under change control, and supported by procedures that define how operators, quality, engineering, planning, and IT use the data.
It also should not be assumed that ERP or PLM can capture complete as-built genealogy by themselves. Some ERP systems can record serial and lot transactions, and some PLM systems can manage configured product structures, but shop-floor genealogy often requires operation-level capture, time sequencing, inspection evidence, nonconformance linkage, and operator or equipment context that sits closer to MES and QMS.
Practical answer
Replacing ERP or PLM is usually not necessary, and in many regulated brownfield environments it is not realistic. The better question is whether the existing systems can provide stable master data, revision control, order context, and inventory transactions, and whether an execution layer can capture the missing as-built evidence with validated interfaces and controlled workflows.
If the current ERP and PLM data is inconsistent, genealogy can still be implemented, but the first phase may need to focus on master data cleanup, identifier strategy, interface mapping, and process discipline. Without that foundation, the result may look digital while still depending on manual reconciliation and local knowledge.