The operating problem
The ERP shows that a batch order is complete. At the line, part of the batch was diverted to rework after an interruption. The lab has released one lot, another is on hold, and the warehouse is expecting the original quantity. An on-time production dashboard can be green while the dispatch team is preparing stock it cannot ship. At a multi-line plant this is also a planning problem: the next shift may schedule material that exists only in the ERP.
- Source recordsERP order, bill of material and approved revision
- ProcessingMES execution, actual consumption and line events
- Decision ownerQuality disposition and supervisor exception review
- Operational outputReleased lot and supported ERP/WMS posting
Implementation approach
Agree a production contract with planning, operations, quality and warehouse teams. Define what planned, started, physically produced, quarantined, released and received mean at this plant. Map the ERP order and operation to the MES run, material lot, equipment and warehouse receipt. Read approved events from the operations layer through the plant’s supported integration gateway. Keep machine control with the PLC and SCADA teams and business posting with the ERP.
Systems found on real plant floors
Siemens documents an Australian MotorOne installation with Mescada where SIMATIC PCS neo and Opcenter MES connect process control to the ERP. AVEVA describes Borg Manufacturing integrating enterprise orders and plant execution in its Australian manufacturing operations. Those installations show that the ERP-to-operations boundary is a real integration problem. The proposed design starts by identifying the MES, historian, PLC/SCADA and ERP already supported at the buyer’s site.
Rollout across lines and sites
Select one product family with a changeover, rework and a real quality hold. Run the event model alongside manual closeout. Confirm tag meaning and count direction with the line engineer, then validate each accounting posting with finance. Promote a reusable event contract to a second line only after documenting local equipment names, unit conversions and plant-specific quality rules.
Exceptions and operating controls
Handle split lots, merged rework, unit conversions, a lab hold arriving after packing and a late line event after shift close. Use source identifiers and a persistent posting ledger so recovery from an interface outage cannot post yield twice. An unresolved physical count stays visible to the shift supervisor; a feed coming back online cannot release a quality hold.
Illustrative operating scenario
A filling line stops during changeover. The operator records partially filled product for rework while the packaging counter includes everything that passed its sensor. Quality releases only the conforming lot. The shift supervisor sees the gap against the production order; the warehouse receives only released pallets. The rework stays linked when it is consumed on a later shift.
Acceptance test and handover
Establish the baseline from the last completed production period: compare run completions, pack counts, rework, scrap and stock the warehouse could actually release. Separate recording delays from physical yield loss. Compare product families and shift patterns before attributing a change to the integration.
Rehearse disconnecting the business interface while local production continues. Replay buffered events into a test ERP, verify yield and stock once, then reverse a deliberately mistaken disposition through the authorised workflow. The plant receives mappings, event ownership, interface monitoring, a cutover sequence, a back-out procedure and the evidence package for the next site.
Siemens and Mescada · MotorOne tank farm automation and Opcenter MES