- ERP (Enterprise Resource Planning): Creates the business plan—what to make, how much, and when.
- Salesforce Manufacturing Cloud: Orchestrates the commercial forecasting, unifying customer demand with ERP supply data.
- MES (Manufacturing Execution System): Receives the manufacturing order and converts it into controlled shop-floor instructions.
- Operators & Equipment: Perform the physical manufacturing steps.
- Execution & Recording: MES guides the work, enforces rules, and builds a comprehensive manufacturing history based on actual yield, not just plans.
- Feedback Loop: MES sends the business-relevant actuals back to the ERP and Salesforce ecosystems for real-time inventory and customer updates.
Salesforce says: "The customer needs this order, here is the demand forecast."
ERP says: "Understood. We need to manufacture this specific product to fulfill it."
MES says: "I will translate that request into controlled, step-by-step manufacturing work."
The operator and equipment say: "We are doing the physical work on the floor."
MES says: "I am recording exactly what happened, step by step."
ERP says: "I will use these actual results to update inventory, costing, and future planning."
The Complete System Architecture Map
SALESFORCE MANUFACTURING CLOUD (Demand & Forecasting) | +-- Commercial Demand + Service Insights v ERP (Business Plan) | +-- Product + Quantity + Order + Batch + Master Data v MES (Execution & Control) | +-- Dispatch + Guide + Check + Record v OPERATOR + EQUIPMENT (Physical Manufacturing) | +-- Actual materials consumed + yield + time + quality checks v MES (Data Collection) | +-- Formats actuals into Electronic Batch Records (EBR) v ERP & SALESFORCE (Reconciliation) | +-- Update Inventory & Costing (ERP) +-- Update Order Status & Customer Visibility (Salesforce)
Imagine a pharmaceutical company needs 100,000 tablets of a 500 mg product.
- ERP generates the order: Product: 500 mg tablet | Batch: B10025 | Target: 100,000 tablets. ERP attaches the Bill of Materials (BOM) and scheduled dates.
- ERP sends the order to MES: The system prepares B10025 for execution by validating recipes, materials, and equipment readiness.
- Execution: Operators run the machines. MES records actual lots used, timestamps, and process checks.
- The Reality Check: The plan asked for 100,000 tablets, but after quality checks and material loss, the actual yield is 98,700 tablets.
- The Feedback: MES sends the actual 98,700 output back to ERP. ERP updates financial ledgers and inventory accurately, rather than blindly assuming 100,000 tablets were made.
The Step-by-Step Concept
Step 1: Planning (Salesforce & ERP)Modern manufacturing begins before the ERP. Salesforce Manufacturing Cloud captures customer run-rate business, sales agreements, and forecasts. It feeds this demand into the ERP. The ERP manages the business side of manufacturing: creating the production order, determining required batches (like B10025), and mapping out the necessary raw materials.
MES requires a reliable data feed to begin execution. ERP sends a structured payload containing the order number, material IDs, target quantities, planned dates, and associated BOMs. The exact API or middleware (like MuleSoft) ensures MES has trusted information to prepare the work.
Step 3: Execution Readiness (MES)Receiving an order doesn't trigger immediate physical work. MES validates readiness:
- Is the correct recipe approved and active?
- Are required materials physically present and out of quality-hold status?
- Are operators certified for this specific machine?
MES routes the job to the correct work center. It guides the operator through the process flow:
Dispense Materials -> Blend -> Compress Tablets -> Coat -> Inspect -> Package
At each step, MES enforces rules, requires barcode scans, and prevents progression if conditions aren't met.
Step 5: Physical Work & Control (PLC / SCADA)MES does not physically mix powders. Operators and machines do. While MES handles the manufacturing context, lower-level control systems like Programmable Logic Controllers (PLCs) or SCADA control the actual hardware.
Step 6: Capturing the TruthMES records reality, creating the Electronic Batch Record (EBR). It logs exact material consumption, precise equipment used, electronic signatures, exception events, and final acceptable yield.
Step 7: Closing the Loop (MES back to ERP/Salesforce)ERP and Salesforce do not need to know which operator pressed a button at 2:04 PM. They need business metrics. MES aggregates the data and sends back the final production count, scrap totals, and material consumption. ERP calculates exact costs, while Salesforce updates the customer on order fulfillment status.
System Ownership Breakdown
A robust architecture relies on single sources of truth.
- Commercial Demand & Forecasts: Owned by Salesforce Manufacturing Cloud.
- Business Production Orders: Owned by ERP (e.g., SAP, Oracle).
- Detailed Execution History: Owned by MES.
- Physical Machine Control: Owned by PLC / SCADA.
- Enterprise Costing & Inventory: Owned by ERP.
Do not say: "ERP sends the order to MES, and MES sends it to the machine."
This is far too simplistic. A strong technical answer separates the layers:
ERP = Business Plan
MES = Manufacturing Execution, Guidance, & Evidence
PLC / SCADA = Hardware/Process Control
Operator = Physical Work
Always conclude by explaining the feedback loop of actual data returning to the ERP.
Downtime Scenarios & Disagreements
What if ERP goes down?If an order is already downloaded to MES, the shop floor can usually continue executing cached orders based on approved downtime procedures. However, new orders cannot be initiated, and completions will queue until ERP is restored. Once ERP is back, reconciliation scripts must run to sync inventory.
What if MES goes down?In highly regulated environments (like pharmaceuticals), if MES goes down, physical manufacturing typically halts. You cannot legally proceed without controlled electronic guidance and evidence capture. Sites must rely on rigorous, pre-approved paper fallback procedures—never improvisation.
What if ERP and MES Disagree?If ERP expects 100,000 units but MES registers an approved change order for 120,000 units, the system architecture must dictate the system of record. Generally, MES holds the actual truth of the floor, and ERP must adjust to reflect the documented reality, rather than forcing the shop floor to match a theoretical plan.
- Rule: Planning, execution, machine control, and evidence recording must have strict boundaries and controlled handoffs.
- Gain: Total visibility. You get a single connected pipeline from customer demand (Salesforce) to business planning (ERP) to shop-floor truth (MES).
- Price: Requires flawless middleware integration (e.g., MuleSoft), strict master-data governance, and established downtime protocols.
- Limits: MES cannot fix broken ERP master data, and ERP cannot magically recreate lost shop-floor batch records.
Key Points Summary
- Data defines the modern factory: Planning (ERP) is inherently a forecast; execution (MES) is the immutable reality.
- Integration is mandatory: Disconnected systems lead to manual data entry, latency, and compliance risks. Modern stacks utilize APIs to keep Salesforce, ERP, and MES in constant synchronization.
- Exceptions must be managed: System architectures must account for hardware failures, network downtime, and yield discrepancies without losing data integrity.
Core Q&A: Test Your Knowledge
1. What is ERP's main role in this end-to-end flow?
ERP acts as the business planner. It determines what product to make, the quantity required, the bill of materials needed, and the timeline, based on commercial demand.
2. What is MES's main role?
MES takes the ERP's plan and turns it into controlled, step-by-step execution. It guides operators, enforces business rules, and records exactly what happens on the shop floor.
3. Who performs the physical manufacturing work?
The human operators and the physical manufacturing equipment.
4. What is the difference between MES and PLC/SCADA?
MES handles the context and the manufacturing record (e.g., verifying materials, logging signatures). PLC/SCADA handles the direct physical control of the hardware (e.g., controlling valve pressure, motor speeds).
5. Why does MES record actual values instead of only planned values?
Because plans rarely match reality perfectly. Scrap, machine errors, and material variations happen. Businesses need actual values to ensure accurate inventory, precise financial costing, and regulatory compliance.
6. Give three examples of actual data MES can record for B10025.
The exact lot numbers of raw materials consumed, the specific user who approved the blending step, and the exact timestamp when the batch finished.
7. What kinds of information can MES send back to ERP?
Total acceptable yield, total scrap, exact material consumption, and order completion confirmations.
8. What should be defined if ERP goes down while a batch is already running?
A formal downtime procedure must dictate if MES can continue running cached orders and how the systems will queue and process updates once connectivity is restored.
9. Why is reconciliation important after an interface failure?
Without reconciliation, ERP might miss a production run, leading to ghost inventory, delayed customer shipments, and inaccurate financial ledgers.
10. Explain the complete B10025 flow in less than one minute.
Salesforce captures customer demand. ERP creates a plan to make 100,000 tablets and sends it to MES. MES guides the operator and machines to build the product. During execution, some material is scrapped, resulting in 98,700 good tablets. MES records this reality and sends the actual numbers back to ERP and Salesforce to update inventory and customer records.