MES ERP Integration: Shop Floor Data Into Your ERP
When the shop floor reports to one system and finance plans in another, work orders close late and costs are guesses. Vascoh builds the integration layer that moves production events between your MES, machines and ERP.
of manufacturers still collect data manually, and 44% report at least a doubling of the data they collect compared with two years earlier.
Source: Manufacturing Leadership Council, Seventy Percent of Manufacturers Still Enter Data Manually (2024)of manufacturers name high cost as a top barrier to AI, followed by technical expertise gaps (35%) and resistance to change (35%).
Source: Deloitte, AI in Manufacturing 2026of manufacturers use AI/ML at the facility or network level, and another 23% are piloting it.
Source: Deloitte, 2025 Smart Manufacturing and Operations SurveyWhat is MES ERP integration?
It is the exchange of data between the system that runs production and the system that runs the business. The ERP sends released work orders, routings, BOMs and item data down. The MES or shop floor system sends back production confirmations, scrap, labor hours, machine status and material consumption.
The ISA-95 standard describes these layers and the information that crosses between them. Many integrations use its object models, or the B2MML XML schemas, as a common vocabulary even when the actual transport is a REST call or a database table.
- Down to the floor: work orders, routings, BOMs, item masters, customer orders
- Up to the ERP: quantity completed, scrap, labor and machine time, lot and serial numbers
- Quality: inspection results and nonconformance records tied to the work order
Why is shop floor ERP integration usually manual?
The Manufacturing Leadership Council survey found 70% of manufacturers still collect data manually. A supervisor writes counts on a traveler, and an office clerk keys them into the ERP at the end of the shift. The costing then runs on yesterday's numbers.
Integration removes that keying step. The data gets captured once, at the machine or the operator station, and posts to the ERP as a production confirmation with the correct work order, operation and quantity.
An example of the cost: a work order for 500 pieces finishes on Tuesday but the traveler reaches the office on Wednesday. Purchasing sees the material as still committed, shipping cannot quote a firm date and the cost variance report is a day behind. Multiply that across dozens of orders and the office is always correcting yesterday.
What are the common ways to connect them?
The right method depends on what each side supports. Machines speak OPC UA, MTConnect or Modbus. MES products expose REST or database interfaces. ERPs expose REST, SOAP, OData or import tables.
Vascoh typically builds a middle service that receives events, validates them against open work orders, queues them, and posts to the ERP with retries. A queue matters because ERPs have downtime windows and API limits, and production does not stop for either.
Security applies on the plant network too. Machine-level protocols such as OPC UA support certificates and encryption, and the edge gateway should be the only device crossing from the operations network to the business network.
- OPC UA or MTConnect from machines to an edge gateway
- Message queue between the shop floor and the ERP
- Idempotent posting so a retry never double-counts a completion
- Dead-letter queue for events that fail validation, with an alert
What breaks in MES to ERP integrations?
Backflushing mismatches are the most common: the ERP consumes materials on a rule that no longer matches how the floor works. Unit of measure conversion errors come next, followed by operations reported out of sequence and rework that the ERP routing cannot represent.
Deloitte lists technical expertise gaps (35%) among the top barriers to AI in manufacturing, and integration skills fall in the same bucket. Document the mapping rules and keep tests for them so the next ERP upgrade does not silently change behavior.
Test with ugly cases: an operator reports against a closed work order, a scan arrives twice, the network drops for ten minutes mid-shift. Each of these should produce a clear, recoverable outcome instead of a corrupted record. Replaying a day of real events into a test ERP before go-live finds most of these problems cheaply.
Do you need a full MES to integrate the shop floor?
No. A plant can capture production events from tablets at stations, barcode scans or machine signals and post them straight to the ERP through a lightweight service. A full MES makes sense when you need electronic work instructions, genealogy and detailed scheduling. Many plants need less, and a simpler build costs less to run.
Start with the events that hurt most, usually production quantity and scrap. Labor and machine time can follow once the first flow is stable and trusted by the people on the floor.
How a project runs
From first call to working system.
Map the data flows
List each event the floor generates, the ERP transaction it should create and the fields that must match.
Build the integration service
Vascoh builds the capture layer, the queue and the ERP connector with validation, retries and monitoring.
Run in parallel
Floor and office both record for a trial period. You compare counts, fix mapping gaps, then retire the manual step.
Questions
Common questions
What is MES ERP integration?
It is the two-way exchange between a manufacturing execution system and an ERP: work orders and routings flow to the floor, and production counts, scrap, labor and material use flow back.
How do you integrate shop floor data with an ERP?
Capture events at the source (operator stations, scanners or machines), validate them against open work orders, queue them and post them to the ERP API with retry logic.
What standards are used in MES integration?
ISA-95 defines the layers and information models, B2MML is its XML expression, and OPC UA and MTConnect are common for machine connectivity.
Can I integrate without replacing my ERP?
Yes. A middle service can adapt the events to whatever interface your ERP offers, whether REST, SOAP, import tables or file drops.
What is the biggest risk in MES ERP integration?
Mismatched rules for material backflush, units of measure and operation sequence. Documenting mappings and testing them against real work orders catches most of these.
Related
Related problems.
Manufacturing Software Integration: ERP, MES, EDI and Accounting
A typical plant runs an ERP, an accounting package, a quality system, spreadsheets and customer portals that do not talk to each other.
AI Production Scheduling for Small and Mid-Size Plants
A planner rebuilding the schedule in Excel every morning is the bottleneck nobody put on the capacity chart.
ERP Integration Services That Connect the Rest of Your Stack
An ERP is meant to be the system of record, but orders, inventory and shipping data still arrive by spreadsheet and email.
Manufacturing Software Development Company for Plants Under 500 People
Your ERP covers 80% of the plant, and the other 20% runs on spreadsheets, whiteboards and email.
Middleware Development: One Layer Between All Your Systems
When every system talks to every other system, a single change breaks three integrations.
More in Manufacturing.
Contact
Tell us what needs to talk to what.
Describe the systems and the manual work, and we will tell you what is realistic to build and what is not.