The Ultimate Guide to Production & Process Orders in MES (With Real-World Examples)

⚡ 1-Minute Summary

• A production or process order is the official factory command to manufacture a set amount of a specific product.
• The ERP system generates the business demand, while the MES translates that demand into executable tasks on the shop floor.
• An order links the product, batch ID, volume, Bill of Materials (BOM), recipe, scheduling dates, and targeted equipment.
• Released means the order is cleared for execution. Started means physical manufacturing is underway.
• The MES captures actual real-world results and feeds material consumption and completion data back to the ERP.
• We will use Batch B10025 as our running example throughout this guide.

Topic Map

MANUFACTURING ORDER
|
+-- Business Need
|   +-- Product
|   +-- Quantity
|   +-- Due Date
|
+-- Order Definition
|   +-- Batch B10025
|   +-- BOM (Bill of Materials)
|   +-- Recipe / Routing
|   +-- Planned Line / Area
|
+-- Order Status Lifecycle
|   +-- Created
|   +-- Released
|   +-- Started
|   +-- Completed
|   +-- Closed / Confirmed
|
+-- MES Execution
    +-- Dispatch to Floor
    +-- Execute Work
    +-- Record Actuals
    +-- Return Results to ERP
  

💬 In Plain Words:

Even if a company knows it needs to sell 100,000 tablets next month, the factory floor still requires a concrete, authorized job ticket detailing exactly what to build. This job ticket is known as a production order or process order.

Think of it as the factory's official work permit: "What are we making? How much? Which batch is this? And when does it need to be done?"

Usually, the ERP system creates this request based on business needs. The MES then catches that request and breaks it down into step-by-step instructions that human operators and machines can actually execute.

📌 B10025 Example: Follow the Order

Let's say the business needs 100,000 tablets. The ERP creates a manufacturing order carrying this vital info:

• Product: 500 mg tablet
• Batch: B10025
• Target Quantity: 100,000 tablets
• Required BOM: The approved list of raw materials
• Required Recipe: The approved manufacturing steps
• Schedule: Planned production date
• Location: Planned manufacturing area/line

The ERP hands this order over to the MES. The MES now recognizes: "We have authorized work waiting for Batch B10025." It proceeds to prep the exact instructions, material checks, and compliance steps for the shop floor operators.

🎬 Real-Life Example: The Order Exists, but Production Cannot Start

Imagine the ERP creates an order for Batch B10025. It shows up in the MES, but its status is merely Created or Planned. An operator sees it and tries to hit start.

The Old/Bad Way: The MES lets the operator begin production just because the order record exists in the system.
Why this fails: The order might not be officially approved yet, or raw materials haven't cleared quality checks.

The New/Good Way: The MES strictly checks the order's status. The operator is blocked from starting until the order officially shifts to Released.
The Payoff: The factory never accidentally builds products before the planning, material staging, and quality approvals are 100% complete.

Core Concepts

What Is a Production Order?

A production order is the formal authorization to manufacture a precise quantity of a specific product. In simple terms, it dictates: "Make this item, in this exact volume, as part of this scheduled job."

For our example, Batch B10025, the order instructs the factory floor to produce 100,000 units of a 500 mg tablet.

What Is a Process Order?

If you work in process manufacturing (like pharmaceuticals, chemicals, or food and beverage), you'll often hear the term process order instead. The exact terminology fluctuates depending on the specific ERP (like SAP) and the company's operational model.

Don't get bogged down by the semantics. Whether it's a production order or a process order, the core function in the MES is identical: it is the controlled job ticket that bridges high-level planning with ground-level execution.

What Information Does an Order Carry?

• The exact product being manufactured.
• The designated batch or lot number (e.g., B10025).
• The targeted production quantity.
• Planned start and completion timestamps.
• References to the BOM (what materials to use).
• References to the Recipe or Routing (how to make it).
• The assigned production site, work center, or line.
• Priority levels for scheduling.
• Current lifecycle status (e.g., Planned, Released, Started).
• Traceability and compliance reporting references.

How BOM, Recipe, and Orders Fit Together

It's easy to mix these up. Here is how they interact cleanly:

• Production/Process Order: What work must be done? (Make 100,000 tablets for batch B10025).
• BOM (Bill of Materials): What ingredients/materials do we need? (50 kg of Active Ingredient A, plus excipients).
• Recipe / Routing: How do we physically make it? (Dispense → Blend → Compress → Coat → Package).

A Simple ERP-to-MES Flow

[ Business Demand ]
        ↓
ERP creates and manages the order
        ↓
Order generated for Batch B10025
        ↓
ERP transmits the order down to the MES
        ↓
MES validates data and prepares execution steps
        ↓
Operator starts manufacturing on the floor
        ↓
MES actively records real-world actuals (times, materials used)
        ↓
Completion and consumption data formulated
        ↓
Data sent back up to ERP and other enterprise systems
  

Understanding Order Statuses

Statuses communicate exactly where an order is in its lifecycle. While exact naming conventions vary by software, the underlying logic is universal:

• Created / Planned: The job exists in the system, but it is not yet cleared to run on the floor. (B10025 is scheduled.)
• Released: The job has passed necessary approvals and is legally allowed to move into active execution. (B10025 is ready for operators.)
• Started / In Process: Physical manufacturing has officially commenced. (Operators are currently working on B10025.)
• Completed: The planned manufacturing tasks are entirely finished. (B10025's physical steps are done.)
• Closed / Confirmed: Final business and system reviews are finalized. The order is locked. (B10025 is financially and operationally settled.)

What Does "Released" Actually Mean?

Releasing an order usually means it has successfully passed planning or QA approval gates and is fully authorized for execution. It does not mean a machine has automatically turned on. It simply means the site's business rules now permit the work to begin.

Created   = The work exists
Released  = The work is authorized
Started   = The work is physically happening
Completed = The work is physically done
  

Dispatching Work in the MES

Once an order hits Released status, the MES will "dispatch" it. Dispatching is simply the act of making the right work available at the right physical location, at the right time. For instance, B10025 might be dispatched to Tablet Press Line 2, while a different order is queued up for the Packaging area.

What MES Records During Execution

Remember this golden rule: ERP provides the plan. MES records the reality.

• Actual start and finish timestamps.
• Exact raw materials and lot numbers consumed.
• Precise quantities of materials used.
• Specific machinery and equipment utilized.
• Operator actions, logins, and electronic signatures (eBR).
• Process variables (temperatures, speeds, pressures).
• Any exceptions, alarms, or quality deviations.
• Final actual yield (how much was actually made).

Plan vs. Actual

ERP (The Plan):
"We intend to manufacture 100,000 tablets."

MES (The Actual):
"We actually yielded 98,700 acceptable tablets. 
We used these specific material lots, 
on this specific machine, 
between 08:00 and 14:30, 
with all quality checks passing."
  

The delta between the plan and the actual reality is pure gold for a business. It drives inventory accuracy, cost analysis, quality control, and factory performance metrics (OEE).

What Data Does MES Send Back to ERP?

Not every microscopic data point needs to go back to the ERP. A good integration only passes back what the business layer cares about:

• Order start and completion confirmations.
• Actual final yield quantities.
• Raw material consumption totals.
• Scrap, waste, or loss metrics.
• Newly generated batch IDs for the finished goods.
• High-level production timestamps.

Edge Case: Mid-Production Order Changes

What happens if the ERP sends B10025 to the MES for 100,000 tablets, but an hour later, the planners update the target to 120,000? The right system response depends heavily on the order's current status. If execution hasn't started, the MES can usually accept a seamless update. If the batch is already physically running on the machines, strict change-control rules kick in. The architectural design must outline exactly who owns the data, when updates are locked out, and how discrepancies are handled.

Edge Case: Duplicate ERP Messages

A robust ERP-to-MES integration must be idempotent. In plain English, idempotency means that if the MES receives the exact same order message twice (perhaps due to a network hiccup), it will not accidentally create two identical jobs. For B10025, the MES will look at the unique identifier, recognize it already has this order, and safely ignore or gracefully acknowledge the duplicate.

Edge Case: ERP-to-MES Interface Outages

Networks drop. When they do, systems shouldn't panic. Good MES design requires predefined answers to these questions:

• Can the factory continue running orders that were already downloaded?
• Can operators manually trigger an emergency order if the ERP is completely offline?
• How do stuck messages retry once the connection is restored?
• How does IT get alerted to the broken integration?
• Who handles data reconciliation once the systems are talking again?

🧠 Memory Aid

ORDER = WHAT work are we doing?
BOM = WHAT materials do we need?
RECIPE = HOW do we execute it?
MES = WHAT actually happened?

For B10025:
Order: Make 100,000 tablets.
BOM: Use these specific, approved raw ingredients.
Recipe: Follow this approved 5-step process.
MES: Record the real-world execution.

🧭 360 Card: Production & Process Orders

Rule: Never execute manufacturing work unless it has reached the explicitly approved Released status.
Gain: Creates a digital bridge between corporate business planning and controlled, compliant factory execution.
Price: Requires heavy master data alignment, robust integration architecture, strict status rules, and fast error-handling processes.
Limits: Having a valid order in the system doesn't guarantee the physical machines, materials, or operators are actually ready on the floor.
Mirror (Manual Process): Paper travelers or Excel spreadsheets. They tell operators what to do but offer zero automated control, traceability, or real-time ERP integration.
At Volume: Scaling this across thousands of lines requires highly reliable interfaces, smart queueing, duplicate prevention, and automated reconciliation.

⚠ INTERVIEW TRAP

Do not say: "As long as the order is visible on the MES screen, production can start."

Visibility does not equal authorization. An order could be visible but still flagged as Planned, On Hold, or missing critical QA data. A strong engineer always clarifies that execution requires checking the order's specific status (e.g., Released) and ensuring physical readiness.

Core Q&A

🎯 Say this first when asked about orders in an MES:
"The manufacturing order connects business planning to shop-floor reality. It dictates what product and quantity must be built, while the MES uses that order to strictly control and digitally record the actual manufacturing execution."

Q: What is the primary role of a production/process order in an MES environment?

A: The ERP creates the production demand. The order identifies the specific product, batch, target volume, timelines, and links to the required BOM and recipe. The MES catches this order, verifies it is ready for execution, dispatches it to the floor, enforces the manufacturing steps, and records the actual physical results. Finally, it sends the actual yield and material consumption data back to the ERP.

Q: ERP changes B10025 from 100,000 tablets to 120,000 after the MES has already received it. What should happen?

A: It depends on the order's current status and the site's change-control rules. If execution hasn't started, the MES usually accepts the update smoothly. If the batch is already actively running, changing the target might be locked out to prevent compliance issues. The system design must explicitly define when changes are acceptable and how they are logged.

Q: The ERP accidentally sends the B10025 order message twice. How does the MES handle this?

A: The MES must never create duplicate manufacturing jobs. The integration architecture must be duplicate-safe (idempotent). When the MES sees the repeated unique order ID, it should recognize it as a duplicate and handle it gracefully without generating a second batch on the floor.

B10025 - End-to-End View

1. Business needs 100,000 tablets
              ↓
2. ERP creates the formal order
              ↓
3. Batch ID B10025 is assigned
              ↓
4. BOM + Recipe + Quantities + Dates are linked
              ↓
5. Order is transmitted to the MES
              ↓
6. MES validates data and checks readiness
              ↓
7. Order status changes to Released
              ↓
8. Operator physically starts B10025 on the floor
              ↓
9. MES actively records all actual execution data
              ↓
10. Order is marked Completed
              ↓
11. Actual consumption & yield sent back to ERP
  

Quick Check

1. What is a production or process order?

It is the official ticket from the business telling the factory to make a specific amount of a product. Think of it as a restaurant order ticket that tells the kitchen exactly what meal to cook, how many to make, and when it needs to be ready.

2. What is the difference between an order and a batch?

An order is the request to do work (e.g., "Make 10,000 pills"). A batch is the specific, traceable physical group of materials produced together during that work. An order can create one batch, or it can be split into multiple smaller batches depending on machine capacity.

3. How does the order connect to the BOM and the recipe?

The order tells the system what to make. It acts as the master link, pulling in the BOM (the exact ingredient list) and the Recipe (the step-by-step cooking instructions) so operators and machines know exactly how to execute the job.

4. What does Released mean in plain English?

It means the green light has been given. A Released status indicates the order has passed all necessary business and quality checks, materials are ready, and the factory floor is legally and operationally authorized to start physical production.

5. What is the difference between Planned ERP data and Actual MES data?

Planned Data (ERP) is the theoretical goal: what you want to happen, the materials you expect to use, and the time it should take. Actual Data (MES) is the ground reality: exactly what was produced, the real amount of scrap, and the exact timestamps of execution.

📌 6. What kinds of actual results does the MES capture for an order like B10025?

When Batch B10025 runs, the MES captures a highly detailed digital paper trail, including:

• The exact lot numbers of raw materials consumed.
• Precise timestamps (start, pauses, finish).
• Equipment used (e.g., Mixer A vs. Mixer B).
• Operator electronic signatures (who did what).
• Final accepted quantity and any scrapped/wasted material.

7. Why does the MES need to send results back up to the ERP?

The ERP needs a reality check to run the business. By sending actual results back, the ERP can accurately deduct raw materials from inventory, calculate the true cost of the run, and inform CRM systems (like Salesforce) so the sales and logistics teams know the finished goods are ready to ship to the customer.

8. What happens if the ERP modifies an order after production has already begun?

Chaos, unless managed properly. If a machine has already started processing, the MES will typically lock the order to prevent mid-run changes that could cause compliance or safety issues. Any changes requested by the ERP at this stage usually require a manual supervisory review or must be queued for the next batch.

⚠ INTERVIEW TRAP: Question 9

Why is it critical that duplicate order messages do not trigger duplicate jobs?
Networks glitch all the time. If an ERP system times out and resends the same production order message, a poorly designed MES might create a second identical job. This leads to double-ordering, wasted raw materials, and factory confusion. The integration must be designed with idempotency—meaning the MES recognizes the unique order ID and ignores accidental repeats.

10. What must a system architect plan for regarding ERP-to-MES interface failures?

Systems will inevitably lose connection. A strong architect plans for local autonomy. The MES needs to cache downloaded orders so the factory can keep running even if the cloud or ERP connection drops. They must also build automated retry queues (store-and-forward) so that when the connection is restored, the MES can send all the saved production results back to the ERP without losing a single data point.

✓ Key Takeaway
The manufacturing order is the ultimate bridge from ERP theory to MES reality. For our Batch B10025, it seamlessly links the product, target volume, BOM, recipe, execution status, and the final real-world production results.