top of page
Search

How to Integrate ERP With Shop Floor Systems

Nov 12
9 min read

Last Updated: November 11, 2026

Quick Summary

Integrating ERP with shop floor systems means connecting the business system of record to the execution layer so work orders flow down automatically and production data flows back up. The ERP plans and the MES or shop floor layer executes, so you must pick one source of truth for each field before building anything.

  • Reconcile master data like part numbers and work centers before connecting; mismatches are the top cause of failed go-lives.

  • Pick one product family or data flow as a pilot and prove it end to end before expanding.

  • Use an edge gateway feeding an MES or shop floor layer rather than connecting PLCs directly to the ERP.

  • Segment the OT network from the corporate network and let the floor keep capturing data offline.

  • Set success criteria before go-live and test end-to-end work orders, data accuracy, error handling, and load.

Is your ERP and shop floor data still disconnected?

ContinuumPMC helps manufacturers connect systems and processes so improvements hold up.

Table of Contents

Why Connecting ERP to the Shop Floor Changes Production Visibility

Most plants already own the data they need. The problem is that it sits in two places that never talk: the ERP and the shop floor.

Your ERP knows what was ordered and billed. Your machines know what actually ran.

Connecting the two systems fixes three things at once:

  • Work orders flow down automatically to the floor, so operators stop re-keying jobs.

  • Production data flows back up to the ERP, so costing and inventory stay current.

  • Downtime and output become visible while the shift is still running, not after month-end.

The payoff is faster decisions, not just cleaner data. A supervisor who can see real machine status and work order progress catches a bottleneck in the moment, not the next morning.

ERP and MES Integration: Defining the Roles Before You Connect Anything

Before you connect a single cable, settle who does what. ERP and MES integration fails most often when the two systems are given overlapping jobs. Map the boundary first.

Where ERP Ends and MES Begins

The ERP is the business system of record: orders, purchasing, inventory valuation, job costing, and financial reporting.

The MES (manufacturing execution system) is the execution layer: production scheduling, work order dispatch, machine and labor tracking, quality data, and OEE.

Many mid-market plants run without a full MES.

Watch out: the most common mistake is letting both systems own the same work order status.

Step 1: Run a Readiness Assessment and Map Your Integration Plan

Start with an honest look at what you have. A readiness assessment tells you which systems, machines, and processes are ready to connect and which need work first; skipping it is how integrations stall halfway through.

Work through these checks in order, and name an owner for each:

  1. Inventory your systems. List every ERP module, MES or shop floor tool, PLC, sensor, and spreadsheet that will touch the integration. Record the vendor, version, and whether the system exposes an API, a database, or only a file export. This inventory becomes your integration backlog.

  2. Map your data. For each field you want to move, name the source system, the destination, the transformation required, and the business owner. A simple data-flow matrix (field, source, destination, frequency, owner) prevents the "who changed this?" arguments that derail go-lives.

  3. Reconcile master data before you connect. Part numbers, work centers, routings, units of measure, and inventory locations must match across systems. Build a cross-reference table mapping ERP IDs to MES or shop floor IDs, and decide which system is master for each record. Mismatched master data is the top cause of failed go-lives, and it is cheaper to fix in a spreadsheet than in production.

  4. Assess the floor. Note which machines can output data natively (Ethernet, OPC UA, Modbus) and which rely on paper or proprietary serial links. Flag legacy equipment that will need a protocol gateway or a manual entry step in phase one.

  5. Define the pilot scope. Pick one product family, one work center, or one data flow (for example, work order release and production confirmation) and prove it end to end before expanding. A narrow pilot surfaces data and ownership problems while the blast radius is small.

  6. Set a phased plan with exit criteria. Connect the highest-value data flows first, and write down what "done" means for each phase: which transactions must reconcile, which reports must match, and who signs off.

A common pattern is a two-to-four-week workshop with IT, operations, and finance in the room, because each group owns different master data. For a structured starting point, a complimentary labor and performance management assessment gives you a concrete read on readiness before you commit to a plan.

Watch out: teams often treat the readiness assessment as an IT exercise and skip operations and finance. The result is a technically clean integration that reconciles to the wrong work centers or cost buckets.

Step 2: Build the Shop Floor Data Integration Layer

The integration layer is the plumbing between systems. It decides how data moves, how often, and in what format. Get this right and everything downstream gets easier.

A practical build order looks like this:

  • Define the data contract. Agree on field names, units, and formats for every message.

  • Choose your transport. Most plants use APIs for system-to-system traffic and a gateway or middleware for machine data.

  • Build error handling in from day one. Every message needs a retry path and a log.

APIs, Middleware, and the Architecture Trade-Offs

There is no single right architecture. The choice depends on your systems and your tolerance for complexity. Here is how the main options compare.

Approach

Best For

Trade-Off

Direct APIs

Modern ERP and MES with clean endpoints

Tight coupling; a change on one side can break the other

Middleware / integration platform

Multiple systems and legacy tools

Adds a layer to license and maintain

Gateway at the machine edge

PLCs and sensors feeding production data

Requires edge hardware and network care

Flat-file or batch transfer

Low-volume, non-urgent data

Not real-time; higher risk of stale data

For most mid-market operations, a middleware layer earns its keep once you have more than two systems to connect, absorbing change so your ERP and shop floor software do not have to. To see how systems integration fits a broader operational plan, review the supply chain and performance improvement services.

Step 3: Handle ERP Integration With PLCs and Sensors

This is where the physical floor meets the business system, and where many projects get stuck. ERP integration with PLCs and sensors means pulling machine data into a usable stream and routing the right signals to the ERP.

Manufacturing engineer connecting Ethernet cables to a PLC cabinet on the shop floor near a data dashboard laptop.

The work breaks into clear pieces:

  • Identify the signals. Decide which machine states matter: running, idle, down, and count. Map each to a PLC tag and agree on units and timestamps before you build.

  • Choose the connection by trade-off, not by habit. OPC UA is the common choice where the PLC supports it because it carries structured data and built-in security. Modbus TCP is simpler and widely supported but has no native security model. Proprietary vendor protocols may require a gateway. Match the protocol to the machine's capability and your maintenance team's skill set.

  • Add edge processing. Normalize machine data at the edge before it hits the network: convert units, debounce signals, and aggregate counts into transactions. Edge hardware also lets you buffer data locally if the network drops.

Architecture Trade-Offs for Machine Data

There is no single right architecture. Compare the main options on latency, maintainability, and suitability:

Approach

Latency

Maintainability

Best Fit

Direct PLC-to-ERP API

Low

Low; tight coupling and fragile

Rarely appropriate; only for low-volume, simple signals

Edge gateway to MES, then ERP

Low to near-real-time

Medium; one place to change mappings

Most plants with mixed machine ages

Middleware / integration platform

Near-real-time

High; absorbs change but adds a license and a layer to monitor

Multi-system environments with legacy tools

Flat-file or batch transfer

High; stale data risk

High; simple but brittle

Low-volume, non-urgent data only

For most mid-market operations, an edge gateway feeding an MES or shop floor layer, with a middleware layer above it, earns its keep once you have more than two systems to connect.

Security and Operational Resilience

Connecting production equipment to business systems crosses the IT/OT boundary, and that boundary needs controls. Segment the OT network from the corporate network with a firewall or DMZ, and allow only the specific traffic the integration needs. Keeping production data queued through outages also helps protect workflows that combine conventional equipment with additive manufacturing, where Socal3Dprintsdesigns can be integrated without weakening the same network and recovery controls.

Legacy Equipment and Phased Migration

Older machines rarely speak modern protocols. A protocol gateway can translate serial or proprietary signals into OPC UA or Modbus, and a manual entry step can cover machines that cannot be connected in phase one.

A common mistake is sending raw machine data straight into the ERP, which is not built for high-frequency signals. If robotics and automation are part of your plan, the automation and systems integration capabilities show how PLC and sensor connectivity gets scoped.

Watch out: teams often connect the PLC directly to the corporate network to save on gateway hardware. That shortcut exposes production equipment to business-network traffic and removes the buffer that keeps the line running when the ERP is down.

Step 4: Configure Shop Floor Production Tracking and Work Order Flow

Now you make the data useful to the people running the shift. Shop floor production tracking turns raw signals into work order status, labor reporting, and inventory movement that operators and planners can act on.

Configure these flows in this order:

  1. Work order release. The ERP releases a work order; it appears on the floor automatically.

  2. Operation start and stop. Operators scan or tap to start an operation on a mobile device.

  3. Production reporting. Good and scrap counts update against the work order in near-real-time.

  4. Material and inventory tracking. Consumption posts back to the ERP as components are used.

  5. Labor reporting. Hours attach to the right job and work center.

The goal is to remove paper-based processes without adding clicks. The process and layout design services address how work actually flows on the floor so tracking fits the real routine.

Step 5: Test, Monitor, and Set Success Criteria Before Go-Live

An integration is not done when it turns on. It is done when you can prove it works and keep it working.

Build your test plan around these checks:

  • End-to-end work order test. Release a job in the ERP and confirm it completes on the floor and posts back.

  • Data accuracy check. Compare reported quantities and costs against a manual count.

  • Error handling drill. Force a failure and confirm the retry and alert paths work.

Then define success in numbers you already track: data accuracy, downtime capture rate, work order cycle time, and OEE.

Watch out: teams often skip the error-handling drill. When a real failure hits during a busy shift, an untested retry path turns a small glitch into lost production data.

Planning Your ERP and Shop Floor Integration With ContinuumPMC

Integrating ERP with shop floor systems is a people-and-process project as much as a technical one. The systems will connect.

We start with how your operation actually runs, then align people, processes, and systems so the integration holds up under real conditions.

If you are weighing an integration, or already have one that stalled, let's talk through where it stands.

A stalled integration usually traces back to a boundary nobody defined or a process nobody changed.

Frequently Asked Questions

What data should flow between ERP and the shop floor?

The minimum set is work orders out to the floor and confirmed production, scrap, labor, and material consumption back to ERP. Add machine status, downtime reasons, and quality results if you want accurate OEE and job costing. Master data matters just as much: item numbers, routings, work centers, and units of measure must match on both sides or every transaction will need manual cleanup. Map this data dictionary before you write a single integration script.

How do ERP and MES systems work together in practice?

ERP owns the commercial plan: customer orders, inventory, purchasing, and cost accounting. MES owns execution: which order runs on which machine, who is working it, and what actually happened. The integration passes released work orders down and confirmed transactions up, usually every few minutes rather than in true real time. Keeping that boundary clear stops both systems from duplicating scheduling logic and creating conflicting priorities on the floor.

Can you integrate legacy PLCs and sensors with a modern ERP?

Yes, but rarely directly. Most legacy PLCs speak protocols like Modbus or EtherNet/IP, not the APIs an ERP expects. A middleware layer or MES collects the machine signals, normalizes them, and exposes them through an API the ERP can consume. For older equipment without network capability, start with manual or barcode entry at the work center and phase in machine connectivity as hardware is replaced.

How long does an ERP and shop floor integration project take?

Timelines depend on how clean your master data is and whether middleware already exists. The biggest schedule risk is not the software, it is process decisions: who confirms a work order, how scrap gets coded, and what counts as downtime. Settle those before build starts.

 
 
 

Comments


bottom of page