ERP vs. MES vs. PLC: Why Manufacturing Needs the Execution Layer

💬 In plain words: An Enterprise Resource Planning (ERP) system knows the business plan (e.g., "We need 100,000 tablets"). However, the ERP isn't standing next to the operator, ensuring each step is done correctly. While machines physically make the product, they don't understand the business context. A Manufacturing Execution System (MES) fills this gap. It turns high-level business goals into strictly controlled, step-by-step physical actions on the shop floor.

Key Points

• ERP handles the plan: It decides what to make, how much to make, and when it needs to be finished.
• The Shop Floor does the work: Operators and machines (PLCs/SCADA) execute the physical manufacturing process.
• MES is the middleman: It sits between the ERP and the machines, translating the business plan into a controlled execution process.
• Real-time verification: MES actively checks materials, lot numbers, equipment statuses, and operator credentials while work is happening.
• Accurate record-keeping: MES records what actually happened during production, not just what was planned.

The Architecture Map

To understand how these systems work together, visualize the flow of data from the top floor to the shop floor:

ERP / SAP / Salesforce Manufacturing Cloud
"What should we make?"
        |
        v
MES (Manufacturing Execution System)
"How do we execute it correctly and safely?"
        |
        v
SHOP FLOOR (Operators + Equipment + PLC/SCADA)
"Do the physical work."
        |
        v
MES
"Record exactly what actually happened."

Understanding the Gaps: ERP vs. MES vs. Shop Floor

What ERP Is Good At

ERPs are built for enterprise planning and broad business transactions. They keep departments aligned by answering high-level questions.

• Managing production demand and creating manufacturing orders.
• Tracking material planning, purchasing, and overall inventory levels.
• Calculating business costs and handling financial data.
• Storing planned production dates and target quantities.

What the Shop Floor Is Good At

The shop floor is the realm of physical reality. Operators and lower-level control systems (PLC and SCADA) run the actual hardware.

• Starting and stopping heavy equipment.
• Controlling motors, pumps, valves, and packaging lines.
• Monitoring real-time physical values like temperature, speed, pressure, and weight.

What MES Adds to the Equation

While the shop floor can execute physical tasks, it lacks business context. While the ERP has business context, it cannot guide an operator's hands in real-time. MES bridges this gap.

• Receives the order from the ERP and loads the approved recipe or instructions.
• Guides operators step-by-step through the process.
• Verifies that the correct, approved materials are being used.
• Validates operator identities and their training authorizations.
• Captures exact quantities used and automatically records process exceptions.

📌 Real-Life Example: Follow Batch B10025

The ERP Level: Creates demand for Batch B10025. It specifies a 500mg tablet, a planned quantity of 100,000 units, the required bill of materials (BOM), and the target deadline.

The MES Level: When production starts, the MES asks the critical execution questions: Is this batch approved for release? Did the operator scan the exact right material? Is this equipment clean and available? What step comes next? It forces compliance at every micro-step.

⚠ INTERVIEW TRAP & COMMON PITFALL

Never say: "An MES is just a smaller ERP for the factory."

They have completely different jobs. ERP manages enterprise-wide planning and finances. MES manages minute-by-minute manufacturing execution and strict regulatory record-keeping. Similarly, never claim that MES replaces PLC/SCADA systems. Real-time physical machine control always belongs to the shop-floor layer.

System Failures and Disagreements

What happens if the MES goes down?

Because an MES sits directly in the critical path of manufacturing, downtime is a major architectural concern. A facility must have predefined rules for an MES outage:

• Can an active batch safely continue?
• Are we allowed to start a new batch?
• What is the approved manual (paper-based) fallback procedure?
• How will records be reconciled once the MES is back online?

What if the ERP goes down, but the MES is running?

If Batch B10025 was already transferred and released to the MES, the shop floor can usually continue executing the batch. However, new orders won't arrive, and finished goods inventory updates will be queued until the ERP comes back online. Modern architectures rely on robust retry mechanisms to sync this data later.

What if the ERP and MES disagree?

Imagine the ERP says the planned quantity is 100,000 tablets, but the MES records actual production of 120,000. Systems should never silently overwrite each other. Good architecture dictates that you identify the "Source of Truth" for that specific data point, flag the interface error, and require an authorized user to reconcile the discrepancy.

🧠 Core Memory Aid: The 4 Pillars

PLAN ➔ ERP
EXECUTE ➔ MES
CONTROL ➔ PLC / SCADA
RECORD ➔ MES

🧭 360 Card: Why MES Exists

• The Rule: Keep business planning, manufacturing execution, and machine control separated but reliably integrated.
• The Gain: Detailed, strictly controlled, error-proof execution between ERP planning and physical production.
• The Price: Increased IT complexity, requiring validation, support, interface monitoring, and robust downtime planning.
• The Limit: An MES cannot magically fix bad ERP data, poorly written recipes, or broken physical machines.

Core Q&A

Q: Why do pharmaceutical and complex manufacturers strictly require an MES between their ERP and the shop floor?

🎯 Say this first: "ERP plans what needs to be made, the shop floor performs the physical work, and the MES connects the two by strictly controlling and recording the execution to ensure regulatory compliance and quality."

While an ERP is fantastic at planning inventory and costs, it isn't designed to enforce step-by-step physical compliance. MES guarantees that the operator scans the right lot, uses the right equipment, and follows the correct sequence, generating a compliant Electronic Batch Record (EBR).

Q: If an ERP already has production orders, BOMs, and inventory tracking, why not just execute the batch directly in the ERP?

Because execution requires a fundamentally different interface and speed. The shop floor needs real-time step-by-step guidance, instant material verification, direct equipment integration, and split-second exception handling. Traditional ERPs are simply too slow and lack the granular architecture for real-time shop-floor control.

Q: Can modern cloud platforms like Salesforce Manufacturing Cloud replace an MES?

No. While modern solutions like Salesforce Manufacturing Cloud excel at unified commercial operations, sales forecasting, run-rate management, and account-based planning, they are still high-level planning and engagement tools. They rely on integrating with a dedicated MES to handle the second-by-second physical machine control and shop-floor execution.

Q: The MES goes down while Batch B10025 is halfway finished. What should the system architect do?

The architect shouldn't be making emergency decisions during an outage. A robust manufacturing facility must have a pre-approved, validated downtime procedure already in place. This includes knowing whether to halt the batch, how to switch to paper-based execution safely, and exactly how data will be backfilled once systems are restored.

Q: What is the most important concept to remember about system layers?

ERP owns the business plan. MES owns the execution and the electronic record. PLC/SCADA owns the physical machine control.