Where should routing execution be recorded?

Routing execution should be recorded in the controlled execution record for the job, usually an MES, electronic traveler, or electronic device history record system. The record should show what operation was performed, by whom, when, against which routing revision, using which materials, equipment, tools, inspections, and approvals. In regulated manufacturing, it is not enough to record only that an ERP operation was closed unless that ERP process also captures the required execution evidence and audit trail.

The practical distinction is simple: PLM usually owns the engineering definition, ERP usually owns planning and order control, and MES or the digital traveler usually owns shop-floor execution. The execution record is where the plant proves what actually happened, not just what was planned.

What commonly belongs in the execution record

The routing execution record commonly includes:

• operation start, pause, completion, and rework status;
• operator, inspector, or approver identity;
• date and time stamps, including any electronic signatures where required;
• routing, work instruction, drawing, or specification revision used at the time of work;
• material lots, serial numbers, batch numbers, and component consumption;
• equipment, fixture, tool, and calibration references where relevant;
• inspection results, measured values, attachments, and pass/fail decisions;
• nonconformances, deviations, concessions, or MRB dispositions linked to the affected operation;
• audit trail entries for changes, corrections, and late entries.

Why ERP alone is often not enough

ERP systems often handle order release, routing masters, labor reporting, inventory movement, and cost collection. Those are important, but they do not always provide adequate operation-level traceability, controlled work instruction display, inspection capture, electronic signature controls, or audit trails. Some ERP deployments can be configured to do more, but that depends on the implementation, validation scope, and shop-floor usability.

If operators complete work in a separate traveler, spreadsheet, paper packet, or machine interface and someone later summarizes the result in ERP, the ERP transaction is not the full execution record. It is a downstream business transaction unless it is explicitly validated and controlled as the execution system of record.

Where PLM and QMS fit

PLM should generally hold product definition, engineering routing intent, bills of material, drawings, specifications, and approved revisions. It should not normally be the place where production operators record each execution step unless the site has deliberately implemented and validated it for that purpose.

QMS systems typically manage nonconformances, CAPA, deviations, audit findings, and quality workflows. They may hold part of the quality record, but they should be linked back to the affected job, serial number, lot, and routing operation. A nonconformance record that cannot be tied to the execution step where it occurred creates traceability problems.

Brownfield reality

Many plants do not have a clean single-system model. A routing may originate in PLM, be planned in ERP, be executed in MES, have inspection data in a quality system, and have equipment status in a maintenance or calibration system. That can work, but only if ownership, integration, revision control, and audit trails are clear.

Full replacement is often unrealistic in regulated brownfield environments. Qualification burden, validation cost, downtime risk, integration complexity, traceability obligations, and long equipment lifecycles usually make coexistence more practical than replacement. The important control is not system purity. It is knowing which system is authoritative for each part of the record and preventing uncontrolled duplicates.

Failure modes to avoid

• Recording completion in ERP while inspection evidence remains in paper files or local spreadsheets.
• Allowing operators to use an obsolete routing or work instruction revision.
• Storing deviations outside the job record without a controlled link to the affected operation.
• Re-keying execution data between systems without reconciliation or audit trail.
• Treating scanned paper as equivalent to structured execution data when searchability, genealogy, or exception handling is required.
• Assuming the system timestamp is sufficient without operator identity, revision context, and change history.

The safest general answer is that routing execution belongs in the validated execution layer: MES, digital traveler, eDHR, or an equivalent controlled system. ERP, PLM, QMS, and maintenance systems should exchange or reference that data as needed, but the site should not leave execution evidence scattered across uncontrolled records.