Production planning with BOMs in an ERP
By Graeon.ai · Updated
Production planning in an ERP starts from the bill of materials (BOM): the ERP takes what customers have ordered, subtracts finished stock already on hand, adds the safety stock you want to keep, and tells you what to make and what material it needs. The plan is then broken into daily plans and, where needed, route cards that follow each batch through its stages.
What a BOM does in the ERP
A bill of materials lists what goes into one unit of a product: raw materials, bought-out parts, packing material and sub-assemblies, each with a quantity. Once the BOM is in the ERP, a production entry can take the right material out of stock and put the finished goods in, without anyone keying two separate stock entries.
A multi-level BOM goes one step further. A finished product uses sub-assemblies, and each sub-assembly has its own BOM. Planning then works level by level: to make the product you need the sub-assemblies, and to make those you need the raw material. Many plants also make in two stages, such as a bulk batch that is later packed into finished packs, and the BOM has to show both.
How netting works
Netting is the arithmetic a planner does on paper every morning. For each product, it compares demand with supply and keeps a cushion.
- Demand: open sales orders and customer schedules
- Less: finished stock already in the warehouse, and work already in progress
- Plus: the safety stock you have decided to hold for that product
- Result: the quantity to produce, which the BOM turns into the material you need
- Then: compare that material with stores, so purchase knows what to buy before the line stops
Daily plans, monthly plans and route cards
A rolling monthly plan shows the load ahead and is revised as orders come in. The daily plan is what the shift supervisor actually works to: which product, how much, on which line or machine. Machine shift logs then record what was really made, so the next plan starts from fact rather than from memory.
A route card travels with a batch or job through its stages, such as cutting, machining, finishing and inspection. Each stage signs off what it passed, sends back what needs rework and records scrap with a reason. That gives you work in progress by stage, not just a total at the end of the day.
Common mistakes
- BOMs that are never updated after a design or recipe change, so stock drifts from reality
- Planning against gross orders without subtracting stock, which builds up finished goods
- No safety stock for fast movers, so one late truck stops a line
- Recording production only at the end of the shift, so the plan is a day behind
- Treating scrap as a stock adjustment instead of recording it at the stage, with a reason
Getting started, step by step
- Put your BOMs in first, starting with the products that make most of your volume
- Record production entries against those BOMs, so stock moves on its own
- Add process stages to the BOM, so you can see where each batch is
- Set safety stock for the products where running out hurts most
- Only then switch on netting and daily plans, once the stock figures can be trusted
How Graeon ERP handles it
In Graeon ERP, BOMs and production entries post material out and finished goods in. Two-stage production is supported: a bulk batch, then packing into finished packs. Each BOM can carry process stages, so you see which step a batch is at, and production and packing entries can come from the shop-floor phone, reaching the ERP within minutes.
Deeper planning is available, switched on per company: multi-level BOMs with options and routing, a Production Action Plan that nets stock, orders and safety stock, daily plans, customer schedules, a rolling monthly plan and machine shift logs. Route cards with stage-by-stage sign-off, send back and scrap with reasons are also available, switched on per company.