ERP/MES Integration for Coil Packing Lines: Questions to Ask
An automatic coil packing line can move a coil without ERP or MES integration. What it cannot do reliably is release the coil, apply the correct label, and record the correct packaging result when the data source is unclear.
This guide helps automation, IT/OT, quality, and project teams define the integration boundary before the line is specified.
| Data-flow table column | What it defines |
|---|---|
| Field | Coil ID, weight, packaging recipe, label data, quality state, shipment record |
| Source of truth | ERP, MES, scale, operator, or quality system |
| Owner | The system or person allowed to correct the field |
| Failure behavior | Buffer, manual route, reject, hold, or safe stop |
| Audit | How a correction is recorded and traced |
Start with the release decision
List the data a coil needs before it can leave the line: coil identifier, order or heat/batch information where relevant, measured weight, packaging rule, label data, quality state, and shipment record.
For each field, identify the source of truth and the system or person that may correct it. The line should not invent a value when the source is unavailable.
The image shows an ERP system visual. It represents the enterprise-level source of order, recipe, and shipment data that the packing line must consume without inventing its own values.
Map the handoffs, not just the machines
Draw the points where data is read, written, or confirmed: coil arrival, identification, weighing, recipe selection, wrapping, strapping, labeling, inspection, stacking, and discharge.
The integration boundary should match the physical boundary. A coil should not be physically released past a point that its record has not passed.
The image shows a smart steel coil packaging system with ERP integration. The value of the integration comes from the fields, timing, and failure behavior across this boundary, not from the connection itself.
Ask the right interface questions
Before comparing vendors, ask these questions:
- Which system owns the coil identifier and order record?
- Which fields does the line consume, and which fields does it produce?
- What happens when the ERP/MES service is unavailable?
- What happens when a label cannot be verified?
- Who may correct a weight, recipe, or quality state?
- What acknowledgement proves the record was accepted?
- How are corrections audited?
The answers often reveal that the difficult part is not the connector but the business rule.
Avoid protocol-first language
It is common to ask for “MES integration” or “ERP integration” as if those words define a scope. A useful request describes the fields, timing, failure behavior, and audit trail. The protocol or middleware choice should follow the requirements, not the other way around.
ISA-95 can provide a technology-neutral reference for separating enterprise and manufacturing-control functions, but it does not select a protocol or prove compatibility between a customer’s systems.
The image shows a person checking the control system for a packing line. This is where interface questions become practical: the line must show the operator what data is missing, who can correct it, and what happens next.
Design for unavailable systems
Every integration has a failure state. Define a project-approved buffer or manual route for when the source system is slow, unavailable, or returns an incomplete record. The fallback should be traceable and should not allow a coil to bypass its required quality or label check.
If the fallback is not defined before installation, operators will create one under pressure.
Include data in acceptance tests
FAT and SAT should test not only normal coil flow but also missing fields, label mismatch, weight discrepancy, recipe change, and system outage. The acceptance criteria should state what evidence proves the record followed the coil correctly.
A practical next step
Create a data-flow table with the field, source of truth, owner, correction route, failure behavior, and audit requirement. Bring IT/OT, quality, production, and the supplier together to review it before the line scope is fixed.
The image shows a working discussion in an office-like setting. That is the right format for the integration review: IT/OT, quality, production, and the supplier agree on the data-flow table before the automatic coil packing line scope is frozen.
Watch an automatic horizontal steel coil strapping line in operation:
