Which MES/ERP connections are common for controlling recipes and traceability?
Bidirectional interfaces between ERP (Enterprise Resource Planning) and MES (Manufacturing Execution System) are common, usually based on ISA-95 / IEC 62264 as the reference model for vertical integration between corporate IT and the manufacturing level. Here, the ERP typically plans products, quantities and schedules, while the MES handles operational execution, feedback and the capture of production data.
Typical standards and formats
- ISA-95 / IEC 62264: defines the information and functional interface between ERP and MES, including production order, product definition, material consumption and production performance.
- ISA-88 / IEC 61512: used particularly for batch and recipe-based processes, to structure the master recipe and control recipe and transfer them between the planning and execution levels.
- B2MML: an XML-based implementation of ISA-95 for the standardised exchange of order, recipe and feedback data.
- OPC UA (Open Platform Communications Unified Architecture) / IEC 62541: a platform-independent standard for communication in automation, frequently used to connect plants, machines and gateways to MES solutions.
- REST APIs, SOAP, IDoc, BAPI: common integration paths for modern or SAP-oriented ERP/MES landscapes; they are used for order transfer, status reporting and master data reconciliation.
- File-based and legacy interfaces such as CSV/XML or direct database connections: still occur in existing system landscapes, but are generally less flexible than API-based or standard-based integrations.
Common integration patterns
- Middleware- or ESB-based coupling: decouples ERP and MES and makes mapping, validation and versioning of recipe and order data easier.
- Message broker / event-based communication: used for scalable, event-driven scenarios, for example with state changes, releases or feedback.
- Direct web-service connection: suited to clearly defined transactions such as order release, recipe release or reporting batch status.
- OPC-UA-based machine connectivity via MES gateways: links machine and process data with the MES, while the ERP supplies the business target data.
Relation to recipes and traceability
- Recipe transfer: the ERP or MES provides master data and target recipes; the MES converts them into executable control recipes and passes them on to downstream systems.
- Batch traceability / genealogy: raw-material batches, process parameters, operator IDs, measured values and test results are recorded in the MES and linked to the end product to enable traceability.
- Electronic batch and production records: the MES bundles process data into a traceable production record and reports relevant results back to the ERP.
- Serialisation: in regulated industries, unique product or packaging identifiers are used to support track-&-trace requirements.
Practically relevant requirements
For a robust connection, clear data models, clean master data management, versioning of recipes and a clear separation between real-time data and transactional business data are important. Cycle times, data volumes, availability and cybersecurity also play a significant role, particularly when the machine, MES and ERP levels are integrated across several sites.
The result is that the usual architecture is a combination of a standardised information model (ISA-95/ISA-88) and a technical interface (e.g. OPC UA, REST, IDoc/BAPI or B2MML), with the MES acting as the mediating layer between ERP planning and manufacturing execution.
Industry 4.0 integration at amixon®: recipe control, data connectivity, traceability
The automation basis
amixon® mixers are supplied with a PLC control system in which mixing programmes – recipes with mixing times, rotational frequencies, dosing and temperature profiles – are stored and run reproducibly. Integration into the operator's ERP system is provided for; a barcode scanner can be integrated for real-time documentation: recipe, batch and process parameters remain linked without gaps – the basis for batch traceability and OEE evaluations.
Interfaces: project-specific to the URS rather than a catalogue promise
Every amixon® machine is a one-off built on the basis of the URS – and this applies explicitly to the automation as well: which process data (torque, temperature, moisture, pressure, run times, cycles) are recorded, and via which interface they are passed to the control system, MES or ERP, is defined and documented at project level. This produces a connection that fits the operator's existing system landscape – instead of a standard interface that is nobody's standard.
Regulated environments included
For pharmaceutical and food operations, amixon® implements the documentation requirements: assistance on request with DQ, IQ and OQ, documentation and execution in line with EU-GMP and FDA 21 CFR Part 11 – electronic records, user concepts and audit-trail requirements are taken into account in the automation concept.
Using data for availability
Recorded operating data (run times, cycles, batches) form the basis of condition-based maintenance: regular inspections and preventive maintenance secure availability, with predictive maintenance available from amixon® on request. Combined with the low maintenance requirement built into the design (mixing tool supported at the top only, low-speed operation), this produces high OEE with little monitoring effort – amixon® clarifies during project planning what scope of data makes sense for this.
Manufacturing in Paderborn as the foundation of quality
amixon® develops and manufactures exclusively at its Paderborn plant – with the greatest possible manufacturing depth and all components sourced from Germany. As a certified welding specialist company with European, Japanese and American qualifications, amixon® designs every machine as a one-off based on the operator's URS; quality control remains entirely in-house without gaps, and every specification can be verified down to component level. This manufacturing sovereignty also secures long-term supply: every component can be reproduced and re-manufactured even decades later.
Verification in the amixon® pilot plant
Before the investment comes the proof: more than 30 test units in different sizes are available at the amixon® pilot plant at the Paderborn headquarters – complemented by pilot plants in Japan, India, Thailand, China, South Korea and the USA. The trials are run with the original product, with real fill levels and batch sizes, within the intended temperature and pressure range. Mixing quality, product protection, energy input, cleanability and reproducibility in later series operation are assessed; the results are evaluated and documented together with amixon® experts – as a robust basis for the decision that rules out technical and economic risks before purchase.
Support over the life cycle
amixon® manufactures exclusively in Paderborn, holds most spare parts there in stock (further stock is held at the service locations in Japan and the USA) and provides lifelong spare parts service – complemented by maintenance, predictive maintenance on request, and modernisation and retrofitting of existing plants.