ERP should send only the production and business context the digital work instruction system needs to present the correct approved instruction for a specific job. In most regulated plants, ERP should not be treated as the source of detailed work instruction content, engineering definition, inspection characteristics, or training evidence unless it has been formally designed, governed, and validated for that role.
Common ERP-to-work-instruction data
The exact interface depends on how ERP, MES, PLM, QMS, and document control are divided at the site. Common ERP-sourced data includes:
- Production order, work order, or shop order identifier.
- Order status, priority, quantity, due date, and planned start date.
- Part number, item number, description, and unit of measure.
- Part revision, if ERP is the controlled source or a synchronized consumer of the controlled revision.
- Lot, batch, or serial number requirements.
- Customer, program, contract, or configuration identifiers where they affect execution.
- Routing, operation number, work center, and sequence references, if ERP owns or publishes the routing.
- BOM, material allocation, kit, or component references where ERP is the source of planning and material control.
- Planner, production line, site, or WIP location information when needed for filtering or dispatch.
- Hold, rework, or order exception indicators, if ERP is part of that control process.
This data is usually used to identify the job, select the right instruction set, and place the operator in the correct operation context. It should not be copied broadly just because it exists in ERP.
Data that usually should not originate in ERP
Detailed work instruction content usually belongs in a controlled instruction, MES, or document management process. Engineering definition normally comes from PLM or an engineering document control system. Quality events and nonconformance workflows often belong in QMS or MES. Training status may come from an LMS or training record system.
ERP may reference these records, but referencing is different from being the system of record. In regulated environments, uncontrolled duplication creates revision and traceability risk.
The critical issue is version alignment
The interface must make it clear how the ERP order, part revision, routing operation, instruction revision, and engineering effectivity relate to each other. A work instruction system can only present the correct instruction if those relationships are defined and maintained.
Common failure modes include a released ERP order pointing to an obsolete instruction, a PLM revision not synchronized to ERP, a routing operation renamed without updating the instruction mapping, or a rework order that does not follow the standard production path. These are governance problems as much as integration problems.
Brownfield integration reality
In many plants, ERP was implemented long before digital work instructions. Routing data may be incomplete, part revisions may be handled differently across sites, and legacy MES or paper travelers may still carry execution logic. A full replacement of ERP, MES, PLM, and QMS just to support work instructions is usually unrealistic because of validation cost, qualification burden, downtime risk, integration debt, traceability obligations, and long equipment lifecycles.
A safer pattern is usually to define a narrow, controlled interface: ERP sends the order context; PLM or document control governs technical content; MES or the work instruction system captures execution evidence; QMS handles nonconformance and disposition where required. The exact boundary should be documented, tested, and change-controlled.
Practical controls to include
- Clear system-of-record rules for part, revision, routing, BOM, and instruction version.
- Validation of order-to-instruction mapping before production use.
- Exception handling for missing revisions, inactive instructions, engineering changes, holds, and rework.
- Audit trails for interface transactions and manual overrides.
- Access controls for customer, defense, export-controlled, or proprietary technical data.
- Monitoring for failed, delayed, or duplicate ERP messages.
If those controls are weak, the integration can still move data, but it may not reliably prevent operators from seeing the wrong instruction or working to the wrong configuration.