The Problem: The Bill of Materials That Was Never Right

A custom furniture workshop produced 200 unique designs per year, but their Bill of Materials (BOM) was a handwritten notebook. When a customer reordered a popular chair, the production manager guessed at the material quantities. The result: 15% material waste (too much wood ordered) and frequent delays because a critical component (like a specific hinge) was missing. Rework costs ate 8% of revenue.

How ERPNext Fixed the BOM Chaos

They implemented ERPNext’s Bill of Materials and Production Planning modules with these precise actions:

• Standardized BOM creation: Every product now has a multi-level BOM in ERPNext. For example, a dining chair includes sub-assemblies (seat frame, legs, cushion) with exact quantities and scrap rates (e.g., 5% wood waste).
• Material requirement calculation: When a sales order comes in for 50 chairs, ERPNext automatically calculates the exact quantity of each raw material needed, checks current stock, and suggests a Purchase Order for shortages.
• BOM version control: When a design changes (e.g., a new hinge type), they create a new BOM version. ERPNext ensures that only active BOMs are used in production, preventing old-spec parts from being ordered.

The Measurable Improvement

Within two months, material waste dropped from 15% to 4%. Production delays due to missing parts fell from 5 per month to 0. The rework cost vanished, and the production manager now spends his time on quality improvement instead of firefighting. The profit margin on custom orders improved by 6 percentage points.

The Problem: A Flood of Paper Receipts and Delayed Payments

A fast-growing consulting firm with 50 employees had a monthly ritual: every employee stuffed a shoebox with paper receipts, filled out a handwritten expense report, and waited 4-6 weeks for reimbursement. The finance team spent 2 full days each month manually entering data, verifying receipts, and cutting checks. Employee morale suffered, and the CFO suspected that 10% of claims were inflated or duplicated.

How ERPNext Streamlined the Expense Process

The firm deployed ERPNext’s Expense Claim module with these specific changes:

• Mobile-first submission: Employees now take a photo of each receipt with their phone and upload it directly into an ERPNext Expense Claim form. The system auto-categorizes the expense (travel, meals, office supplies).
• Policy enforcement at entry: ERPNext is configured with company expense policies (e.g., max $50 for meals, no first-class flights). If a claim exceeds the limit, it’s automatically flagged for manager approval.
• Direct integration with payroll: Approved claims are batched weekly and sent to the payroll module. Employees receive reimbursement in their next paycheck, with no manual check writing.

The Measurable Improvement

After the first cycle, the reimbursement time dropped from 30 days to 5 business days. The finance team’s processing time decreased from 2 days to 3 hours. The CFO’s audit report showed zero duplicate claims and a 12% reduction in total expense claims due to policy enforcement. Employee satisfaction scores for the reimbursement process jumped from 2.1 to 4.7 out of 5.

The Problem: Service Calls That Disappeared into a Black Hole

A regional HVAC service company had 15 technicians on the road, but no one knew where they were or what they were doing. Customers complained that service requests were lost, parts were not pre-ordered, and invoices were delayed by weeks. The service manager spent 3 hours every morning just assigning jobs from a pile of sticky notes. Revenue leakage from unbilled work was estimated at 8%.

How ERPNext Brought Order to Field Service

They implemented ERPNext’s Service Management and Project modules with these focused steps:

• Centralized service request system: Every customer call is logged as a Service Request in ERPNext. The system automatically assigns it to the nearest available technician based on their calendar and skills.
• Real-time job tracking: Technicians use a mobile app to update job status (arrived, working, completed). The manager sees a live map of all active jobs on a single dashboard.
• Auto-invoicing upon completion: When a technician marks a job as “done,” ERPNext generates an invoice based on the pre-set service contract or time spent. No more forgotten billing.

The Measurable Improvement

Within six weeks, the average response time dropped from 48 hours to 4 hours. The billing cycle shortened from 14 days to 2 days. Revenue leakage was eliminated, and the service department turned from a cost center into a profit center with a 15% margin improvement.

The Problem: The Inventory Balancing Act That Failed

A small electronics assembly plant was growing fast, but their inventory management was stuck in the past. The warehouse manager used a whiteboard to track raw material levels. Every month, they either ran out of a critical chip (stopping production for 2 days) or over-ordered resistors that sat on shelves for 6 months. The cost of emergency air freight for missing parts ate 12% of their profit margin.

How ERPNext Rebalanced the Supply Chain

They adopted ERPNext’s Inventory Planning and Reorder modules with these specific practices:

• Dynamic reorder levels: Instead of guessing, they set reorder points based on actual consumption data from the past 90 days. ERPNext automatically generates a Purchase Order when stock hits the threshold.
• Lead time tracking: For each supplier, they entered the average lead time (e.g., 14 days for chips, 30 days for custom enclosures). ERPNext now suggests order dates that ensure stock arrives just before the production run.
• Monthly ABC analysis: They run a simple ERPNext report that classifies items by value. A-items (high value, low volume) are reviewed weekly; C-items (low value, high volume) are auto-reordered monthly.

The Measurable Improvement

After three months, stockouts dropped from 3 per month to 0. The inventory turnover ratio improved from 4.2 to 6.8. The warehouse manager now spends 30 minutes a day reviewing ERPNext alerts instead of walking the aisles with a clipboard. The emergency air freight bill vanished entirely.

The Problem: Lost in Exchange Rate Confusion

A mid-sized textile exporter in Southeast Asia faced a recurring nightmare. Every month, their sales team closed deals in USD, EUR, and occasionally local currency. But when invoices were paid, the exchange rate had shifted, leaving the accounting team scrambling to manually adjust every single transaction. The result? A 3-day monthly reconciliation process, frequent disputes with customers over payment amounts, and a 5% write-off on small exchange rate differences that added up to thousands of dollars annually.

How ERPNext Transformed the Workflow

The company implemented ERPNext’s multi-currency management feature, focusing on three specific actions:

• Automatic exchange rate update: They configured ERPNext to pull daily exchange rates from a central bank API. Every sales order and invoice now locks in the rate at the moment of creation.
• Real-time gain/loss calculation: When a payment arrives in a different currency, ERPNext automatically calculates the exchange gain or loss and posts it to a dedicated GL account. No manual journal entries needed.
• Customer-specific currency profiles: Each customer’s default currency was set in their master record. The sales team no longer accidentally invoices in the wrong currency.

The Measurable Improvement

Within two months, the monthly reconciliation time dropped from 3 days to 4 hours. Write-offs due to exchange rate differences fell to near zero. The finance manager now runs a single “Currency Exchange Gain/Loss Report” every week instead of chasing spreadsheets. The sales team can confidently quote prices in any currency, knowing the system will handle the rest.

Many factory owners often ask the same questions:

Why does the workshop keep reporting material shortages when the warehouse shows enough stock?

Why is the same product profitable this month but losing money next month?

Why are production data still inconsistent even after implementing an ERP system?

In many cases, the root cause is not purchasing, nor workshop execution. It starts from the most basic yet most overlooked data source: the BOM (Bill of Materials).

Many companies treat BOM as just a material list. In reality, it is more like the construction blueprint of factory production.

Once this blueprint is wrong, purchasing, material issuing, production, warehousing, and cost accounting will all be affected.

Today, let’s go through three typical BOM mistakes that 90% of factories have experienced, using real manufacturing scenarios.

Mistake 1: BOM Is Never Updated and Production Relies on Experience

This is the most common issue.

Many factories create the BOM during the prototype or sample stage. After mass production starts, the process keeps evolving:

• Material specifications change
• Auxiliary material brands are replaced
• Packaging thickness is adjusted
• Actual scrap or loss rates increase

But the BOM itself is never updated.

As a result, purchasing still buys materials based on the old BOM, while the workshop produces according to the new process.

This leads to common problems such as:

• Some auxiliary materials are always short
• Some packaging materials keep piling up
• Actual costs never match theoretical costs

A label printing factory once faced exactly this problem.

Originally, one roll of material was expected to produce 10,000 labels. After equipment and process optimization, the stable output dropped to around 9,200 pieces, but the scrap rate in the BOM was never adjusted.

As a result, sales quotations remained too low, and the more orders they received, the more money they lost.

The final review showed that the issue was not production waste. The theoretical BOM data had simply become outdated.

Many factories are not bad at production. They are just making decisions based on expired BOM data.

Mistake 2: Semi-Finished BOM Levels Are Poorly Structured

The second very typical problem is a confusing BOM hierarchy.

For example, the normal production flow for a packaging box may look like this:

• Base paper
• Printed semi-finished product
• Laminated semi-finished product
• Die-cut semi-finished product
• Final packed product

However, many factories put all materials directly under the finished product level just to save time.

This may look convenient in the short term, but it creates serious long-term problems.

The three biggest impacts are:

First, workshops cannot issue materials accurately by process step
Second, semi-finished inventory cannot be tracked
Third, process losses cannot be analyzed separately

I once saw a color box printing factory where the lamination workshop constantly reported material shortages, while the warehouse system showed sufficient stock.

The investigation later found that the BOM had no “printed semi-finished” or “laminated semi-finished” levels at all. Everything was directly linked to the final product.

The system could only see total consumption, but it could not identify which process step was causing the issue.

From the owner’s perspective, inventory looked accurate, but profits kept shrinking.

The real issue was not execution. It was poor BOM structural design.

Mistake 3: One BOM Is Used for All Customer Orders

This problem is especially common in customized manufacturing industries, such as:

• Packaging printing
• Label printing
• OEM export manufacturing
• Creative custom products
• Digital quick printing

The same product model often has different customer requirements.

For example:

• Some customers need export packaging
• Some require instruction manuals
• Some need QR code labels
• Some need special moisture-proof materials

If the company only maintains one standard BOM, errors become unavoidable.

Common outcomes include:

• Missing materials that should have been added
• Extra materials being issued unnecessarily
• Customer-specific accessories being forgotten
• Large costing deviations

A gift box export factory once had domestic and export versions of the same product.

The export version required an English manual and moisture-proof bag, but the system only had one standard BOM.

As a result, the warehouse issued materials according to the domestic version. The missing accessories were only discovered right before shipment, causing full rework and major losses.

In many cases, the problem is not employee carelessness. It is poor BOM version management.

Why Do Many Factories Still Struggle After ERP Implementation?

Many factory owners have a common misunderstanding:

They assume that once ERP is online, production management will automatically become standardized.

In reality, ERP only amplifies existing problems faster.

If the BOM itself is wrong, the system will quickly spread the error into:

• Purchasing plans
• Production work orders
• Warehouse material issuing
• Cost accounting
• Financial profit analysis

This leads to a common situation:

The system looks advanced, but the data becomes even more chaotic.

The correct sequence should be:

First fix the BOM, then drive digital transformation.

How Can Factories Avoid These 3 Problems?

Here are three highly practical suggestions for manufacturers.

First, establish a BOM change management process
Whenever materials, processes, or loss rates change, the BOM must be updated immediately.

Second, build multi-level BOM structures
This is especially critical for printing, packaging, and assembly-based factories.

Third, maintain customer-specific BOM versions
Different customers, export standards, and accessory requirements must have separate BOM versions.

Many factories realize during post-analysis that:

Production chaos, inaccurate inventory, and distorted costing are usually not caused by poor execution.

The root cause is often that the BOM was wrong from the very beginning.

So the BOM is not just a basic master data sheet.

It is the starting point of factory profit management.

Many business owners share the same thought at some point:

“Our company is growing. Maybe it’s time to implement an ERP system.”

So they purchase software, hire an implementation partner, and form a project team. Everything looks professional and well planned.

But in reality, many ERP projects end in one of three outcomes:

The system goes live, but no one uses it.
The system goes live, but the data is unreliable.
The system goes live, but employees continue using Excel.

ERP is not just a software project. It represents a transformation in the way a company manages its operations. If the approach is wrong, companies can easily fall into common traps.

Based on real cases from many enterprises, here are five major pitfalls manufacturing companies often encounter when implementing ERP.

Pitfall 1: Unclear Objectives – “Other companies have ERP, so we should have it too”

Many ERP projects start off in the wrong direction.

A packaging company with annual revenue of 300 million decided to implement ERP after the owner heard from friends:

“Once you install ERP, management automatically becomes more standardized.”

The company immediately launched the project.

However, during the kickoff meeting, an awkward question appeared:

What exactly is ERP supposed to solve?

Sales wanted better quotation management.
Production wanted improved scheduling.
Finance wanted cost control.
The warehouse team wanted inventory accuracy.

As more requirements were added, the system became increasingly complex.

After two years, the project was still not fully implemented.

If the objective of an ERP project is unclear from the beginning, the project scope will keep expanding and eventually become uncontrollable.

The correct approach is to focus on solving a few core problems first, such as:

Unreliable delivery dates
Inaccurate inventory data
Disorganized production planning

Start by addressing the most painful problems.

Pitfall 2: Treating ERP as an IT Project

Many companies believe ERP is simply an IT responsibility.

In reality, ERP is a management project.

A machinery manufacturing company once assigned its IT manager to lead the ERP implementation.

During the project, different departments were not very cooperative.

Production said they were too busy.
Warehouse staff said they would handle it later.
Sales said they would enter data in the future.

When the system finally went live, the data was chaotic.

The essence of ERP is to standardize business processes.

For example:

How orders are created
How materials are issued
How production operations are reported
How inventory is managed

These decisions should not be made by IT alone. They are determined by management policies.

If company processes are unclear, even the best ERP system will not work effectively.

Pitfall 3: Implementing the System Before Fixing Processes

Many companies operate with processes that have evolved informally over time.

For example:

Some orders go directly to production.
Some require quotation first.
Some follow special approval procedures.

Often these rules exist only in employees’ minds.

An electronics factory discovered several issues while implementing ERP:

The same product had three different BOM versions.
The warehouse contained many temporary item codes.
Production frequently issued materials first and completed documentation later.

These issues were not addressed before the ERP system was implemented.

After the system went live, the data became even more confusing.

ERP systems tend to amplify existing problems.

If processes are chaotic, the system will simply digitize that chaos.

Pitfall 4: Ignoring Data Preparation

One of the most overlooked parts of ERP projects is data preparation.

This includes:

Item codes
BOM structures
Inventory quantities
Supplier information

A hardware manufacturing company spent only one week preparing its data before ERP implementation.

After the system went live, many problems appeared:

Inventory numbers did not match reality.
BOM structures contained errors.
Cost calculations were inaccurate.

Later the project team discovered the root causes:

Duplicate item codes
Multiple uncontrolled BOM versions
Unverified historical inventory data

ERP systems rely heavily on data accuracy.

If the data is messy, even the best system will fail.

Many successful projects spend several months preparing and cleaning data before implementation.

Pitfall 5: Insufficient Training

After ERP systems go live, a common situation appears:

The system is advanced, but employees continue using Excel.

The reason is simple:

They do not know how to use the system effectively.

An example is a printing company that provided only one training session before going live.

After returning to their daily work, most employees quickly forgot what they had learned.

Soon a strange situation developed:

The system existed, but real work continued outside the system.

Employees preferred their old methods because they were faster and more familiar.

The real success of ERP is not the launch of the system, but whether people actually use it.

Many successful companies arrange:

Role based training
Operation manuals
Post go live support

This ensures employees can truly adopt the system.

The Real Key to ERP Success

ERP is not a software project.

It is a management upgrade.

Successful ERP implementations usually share three characteristics:

The company owner actively supports and drives the project.
Business processes are clarified before system implementation.
Data preparation is taken very seriously.

When implemented properly, ERP becomes the foundation of enterprise management.

If implemented poorly, it becomes an expensive decoration.

Before launching an ERP project, every company should ask one question:

What problem are we really trying to solve?

Many factory owners share the same frustration:

They invested in ERP.
They deployed MES.
Yet production is still chaotic, inventory is inaccurate, and quality issues keep repeating.

The real reason is simple:

They bought software — but never built a system.

In mature manufacturing enterprises, these seven platforms work together like the human body:

ERP is the brain
MES is the field commander
WMS is the warehouse manager
SCM is the supply chain coordinator
PLM is the product design center
SCADA is the nervous system
QMS is the quality doctor

Let’s explain each one in plain language.

---

1. ERP — The Enterprise Brain

ERP manages the big picture.

Orders, purchasing, production planning, inventory, costs, and finance all come together here.

ERP answers three fundamental questions:

What did the customer order?
How much should we produce?
Are we making money or losing it?

Example:

A machinery factory receives an order for 100 machines.
ERP automatically breaks it into material requirements, generates purchase plans, schedules production, and calculates projected costs.

ERP decides direction — not shop-floor details.

---

2. MES — The Shop Floor Commander

MES manages execution.

ERP says “produce 100 units.”
MES decides:

Which production line goes first
Which machine runs which job
Who operates each process
How far production has progressed

MES collects real-time data on progress, labor hours, and abnormalities.

Example:

In an electronics factory, MES assigns motherboard assembly to Line A and screen installation to Line B.
If a station becomes blocked, the system alerts supervisors immediately.

ERP plans.
MES executes.

---

3. WMS — The Warehouse Manager

WMS controls materials.

Where items are stored
How much inventory remains
Which location holds finished goods
FIFO logic

Example:

An appliance factory with tens of thousands of parts uses barcode scanning through WMS to locate materials in seconds instead of relying on employee memory.

MES requests materials.
WMS delivers them.

---

4. SCM — The Supply Chain Coordinator

SCM manages the outside world.

Suppliers
Delivery schedules
Logistics status
Inventory optimization

It prevents factories from being controlled by suppliers.

Example:

When a key electronic component may be delayed, SCM issues early warnings, allowing procurement to activate backup vendors before production stops.

---

5. PLM — The Product Lifecycle Manager

PLM manages products from birth to retirement.

Drawings
BOMs
Process routes
Engineering change versions

Everything lives in PLM.

Example:

A single bolt specification changes in a automotive parts factory.
PLM synchronizes the update to ERP and MES automatically, preventing production from using outdated drawings.

Without PLM, design and manufacturing never stay aligned.

---

6. SCADA — The Machine Nervous System

SCADA connects directly to equipment.

It collects:

Temperature
Pressure
Speed
Alarm signals

This is the lowest-level source of real-world data.

Example:

When injection molding temperature exceeds limits, SCADA triggers alarms within seconds and MES halts production to avoid mass defects.

SCADA senses reality.

---

7. QMS — The Quality Doctor

QMS manages:

Incoming inspection
In-process quality checks
Final product inspection
Nonconformance tracking
Corrective actions

Example:

In a food factory, QMS traces every package back to raw material batches, production lines, and operators.

If problems occur, only affected products are recalled — not entire warehouses.

---

How the Seven Systems Truly Work Together

A typical order flows like this:

Step 1: PLM defines product structure and process routes
Step 2: ERP generates production and purchasing plans
Step 3: SCM coordinates supplier deliveries
Step 4: WMS manages material storage and feeding
Step 5: MES dispatches work orders to production
Step 6: SCADA collects real-time machine data
Step 7: QMS controls quality throughout

Finished goods enter inventory, while ERP automatically calculates cost and profit.

This is not seven separate systems.

It is one digital production pipeline.

---

Final Thought

Many companies fail because they:

Buy systems
But never integrate them

True digital transformation is not “installing ERP.”

It is connecting ERP, MES, WMS, SCM, PLM, SCADA, and QMS into one coordinated ecosystem.

When data starts flowing:

Inventory becomes accurate
Delivery becomes predictable
Quality becomes traceable
Management becomes easier

That is real manufacturing digitalization.

Why Do We Need Three Different BOMs?

In many companies, people tend to treat the Bill of Materials (BOM) as “just one list”. As a result, when design, production, and cost accounting use the same BOM, they often face problems:

• The BOM provided by R&D cannot be used directly in production;
• Even if the production BOM shows all materials are ready, the workshop still experiences shortages;
• The cost calculated by finance doesn’t match the actual expenses.

These issues often stem from a fundamental reason: using a single BOM as a “universal list”. In reality, at least three types of BOMs are needed across the product lifecycle, each solving key problems for different departments.

---

1. What is a BOM?

BOM (Bill of Materials) is a “material list” that defines the composition of a product. Whether in design, procurement, or production, everyone relies on this list. It not only tells you “what components make up the product and how many are needed”, but also “who uses it, how to use it, and for what purpose”.

---

2. The Three Types of BOMs and Their Differences

1. Engineering BOM (EBOM) — The Design Blueprint

Target Audience: R&D and design teams
Purpose: Describe what the product should be, from a functional and structural perspective.
Key Features:

• Lists all design components (parts/assemblies) hierarchically;
• Focuses on design requirements, specifications, and functions—not production processes;
• Closely linked to CAD models and drawings.

Example: An engineering BOM for a mechanical pump lists the pump body, bearings, impeller, etc., and their assembly relationships, but does not specify assembly order or manufacturing processes.

Problem it Solves: Ensures clear product design structure, consistent understanding within R&D, and provides a foundation for manufacturing and cost analysis.

---

2. Manufacturing BOM (MBOM) — Production Execution List

Target Audience: Production, process, and materials control teams
Purpose: Tell the production floor “how to make it”.
Key Features:

• Based on the engineering BOM but includes manufacturing-specific information;
• Includes assembly sequence, operations, auxiliary materials (e.g., glue, lubricants), labor hours, and inspection points;
• Supports ERP/MES systems for production scheduling, material planning (MRP), and work order issuance.

Example: For the same mechanical pump, the manufacturing BOM specifies: machine the pump body first, assemble bearings and impeller next, use sealant and lubricants during assembly, and follow the correct operation sequence.

Problem it Solves: Ensures the production floor can manufacture the product correctly according to process steps, avoiding misinterpretation of the design.

---

3. Cost BOM (CBOM) — Cost Calculation Model

Target Audience: Finance, cost analysts, pricing teams
Purpose: Calculate product cost and support pricing strategy.
Key Features:

• Flatten the engineering or manufacturing BOM and assign a cost to each item;
• Includes direct materials, labor, processing fees, transportation, losses, and overheads;
• Produces a model used for cost accounting and profit analysis.

Example: The cost BOM for an electronic device includes the prices of the screen, motherboard, etc., plus assembly labor, testing losses, and packaging costs to calculate the total unit cost.

Problem it Solves: Accurately calculates product costs, supports pricing, and prevents cost estimation errors from only looking at material prices.

---

3. How the Three BOMs Relate in the Process

From Design to Production to Costing

1. R&D produces the engineering BOM;
2. Process engineers convert the engineering BOM into the manufacturing BOM (adding operations, sequence, and auxiliary materials);
3. Finance converts the manufacturing BOM into the cost BOM by adding costs and losses;
4. The cost BOM is then used for pricing, profit analysis, and decision-making.

---

4. A Real-World Example

Scenario: A company is producing a smart watch.

1. Engineering BOM:

   • Lists case, screen, chip, sensors, strap, etc.;
   • Emphasizes functional and hierarchical design (e.g., sensors belong to the chip assembly).

2. Manufacturing BOM:

   • Based on the engineering BOM, with production steps added:
     • Step 1: Solder PCB;
     • Step 2: Test screen driver;
     • Step 3: Assemble all components;
   • Includes screws, thermal paste, screen protectors, and other auxiliary materials.

3. Cost BOM:

   • Assigns a cost to each component;
   • Adds labor costs for assembly;
   • Includes testing losses and packaging costs;
   • Produces total product cost for pricing and profit analysis.

This clear division allows R&D to focus on “correct design”, production to focus on “can it be built”, and cost teams to focus on “how much it costs”. Using a single list for all purposes leads to material shortages, assembly errors, or cost miscalculations.

---

5. Common Misconceptions and Best Practices

• Misconception 1: One BOM for all departments → causes confusion;
• Misconception 2: Treating manufacturing BOM as engineering BOM → design changes are not reflected;
• Misconception 3: Calculating cost directly from engineering BOM → ignores losses, labor, and overhead.

Best Practices:

1. Clearly separate the three BOM types in PLM/ERP;
2. Use change management to update manufacturing and cost BOMs when engineering BOM changes;
3. Assign clear responsibilities and approval workflows for different departments.

---

6. Summary: What Each BOM Solves

BOM Type	Target Audience	Core Problem Solved
Engineering BOM	R&D/Design	Defines product design
Manufacturing BOM	Production/Materials Control	Defines how to make the product
Cost BOM	Finance/Cost Analysis	Calculates product cost

Properly managing these three BOMs avoids production and cost disputes, and improves overall efficiency and profitability.

High variety, low volume, and short lead times have become the new standard in discrete manufacturing. With a large number of product variants, small batch sizes, complex routing, and frequent rush orders, scheduling easily becomes chaotic. Plans change constantly, execution struggles to follow, and production often feels like nonstop firefighting.

To solve this, we must break production planning into clear layers and connect them through three stable workflow links.

---

1. Why Is Scheduling So Difficult?

High-mix, low-volume production makes traditional experience-based scheduling ineffective:

• Orders change quickly
• Many constraints: machines, materials, and workers
• Plans often do not match real shop-floor execution

The root cause is not “poor scheduling skills,” but an unclear planning system.

---

2. Four Types of Plans: From Strategy to Execution

A complete scheduling system in discrete manufacturing consists of four layers, each solving a different problem.

---

1. Strategic Planning

This defines long-term goals, annual capacity layout, and product strategies.
It answers: “What will the company produce in the future?”

It guides:

• Long-term capacity decisions
• Product mix strategy
• Investment direction

---

2. Master Production Schedule (MPS)

MPS transforms orders and forecasts into overall production quantities and timing.

It answers: “How much do we produce in the upcoming period?”

Its key roles:

• Convert demand into capacity needs
• Set the production rhythm
• Drive procurement and material preparation

---

3. Material Requirements Planning (MRP)

MRP expands MPS into detailed material requirements:

• What materials are needed?
• How many?
• When must they arrive?

MRP ensures material readiness so production won’t stop due to shortages.

---

4. Detailed Scheduling

This is the most execution-oriented plan:

• Which machine works on which order?
• In what sequence?
• At what time?

It coordinates production at the shop-floor level and changes most frequently.

---

3. Three Links: Making Plans Truly Executable

Plans must flow through three interconnected links to work effectively.

---

1. Order → Production Link

This ensures:

• Real customer demand drives production
• MPS and scheduling follow clear priorities
• Plans match actual delivery requirements

Order changes must flow quickly into planning.

---

2. Material → Capacity Link

MRP connects material readiness with available production capacity:

• Are materials ready?
• Are machines available?
• Is manpower sufficient?

It identifies bottlenecks early to avoid unrealistic scheduling.

---

3. Plan → Execution → Feedback Link

Shop-floor variability is constant:

• Machine breakdowns
• Worker shortages
• Longer-than-expected process times
• Rush orders changing priority

Execution data must continuously feed back to MPS and scheduling, ensuring the plan stays alive and adaptable.

---

4. Key Practices for Successful Implementation

To make scheduling effective in a high-mix environment:

1. Use layered planning: Strategy → MPS → MRP → Scheduling
2. Enable real-time feedback
3. Ensure material readiness
4. Make priority rules transparent
5. Use digital tools to handle complex constraints

Scheduling is not just “calculating orders”—it is organizing the entire workflow.

---

5. Conclusion

High-mix, low-volume production is not the reason for chaos.
A poor planning system is.

By establishing four levels of planning and connecting them with three workflow links, factories can move from constant firefighting to stable, predictable production.