How a bill of materials supports production control

What the BOM defines

The BOM identifies required components and quantities for a parent item. Effective implementations also address units, effective status, revision, expected loss, alternatives, and the relationship to operations.

BOM and routing

The BOM describes material while the routing describes work. Operations, sequence, setup, run time, work center, labor, and machine rates allow the system to connect capacity and resource cost with component demand.

From definition to execution

A production order should reference an approved definition, plan materials and operations, record actual issues and completions, capture scrap or substitutions, and receive the finished item with a traceable cost.

Governance and testing

Define who may create, review, approve, revise, and retire BOMs. Test quantity precision, unit conversion, partial builds, component shortages, reversals, and cost rollups before relying on automated planning.

Questions to bring to discovery

• Which users and decisions depend on this workflow?
• Where does information originate, and which system owns it?
• Which exceptions, corrections, and approvals must be supported?
• How will the organization measure a successful result?

Bill of material types describe different decisions

An engineering BOM reflects product design. A manufacturing BOM reflects how the organization builds the product, including production-relevant components, packaging, intermediate assemblies, and operations. A sales or configurable BOM may describe the customer-selected configuration, while a service BOM supports maintenance after delivery. One organization may not need every type, but it must define which structure is authoritative at each handoff.

Moving an engineering structure into ERP without review can create planning problems. Design assemblies do not always match stocked or manufactured subassemblies. Manufacturing may require consumables, yield factors, substitute rules, or packaging that are absent from the drawing. The conversion process needs an owner and approval rather than an informal copy.

How the bill of materials management process works

1. Define items and units. Every component and parent requires a stable identifier, status, stocking unit, and conversion rule.
2. Create the structure. Add component quantities, levels, scrap factors, issue method, substitutes, and effectivity.
3. Connect the routing. Identify operations and work centres that consume material, labour, machine time, or subcontracted service.
4. Review and approve. Validate completeness, manufacturability, availability, cost, quality, and the intended effective date.
5. Release to planning and production. MRP and production orders use the approved version, not an uncontrolled draft.
6. Measure actual results. Compare planned material, time, output, scrap, and cost with the order’s activity.
7. Control change. Preserve history, assess affected orders and inventory, and approve the next revision.

What BOM management software should control

• Single-level and multi-level product structures with where-used inquiry.
• Draft, approved, obsolete, and effective revision states.
• Component units, quantities, rounding, yield, scrap, and substitutes.
• Routings, work centres, setup, run time, resources, and subcontracting.
• Make, buy, stock, and phantom or intermediate assembly decisions.
• Material, labour, resource, subcontracting, and overhead cost rollups.
• Permissions for creation, engineering review, production approval, and emergency change.
• Links to documents, quality instructions, production orders, inventory, purchasing, and accounting.

A spreadsheet can describe a small structure, but it becomes difficult to answer which revision was built, where a changed component is used, whether open orders need action, and how the change affects supply and cost. A BOM module in ERP keeps product definition connected to execution.

Control revisions without rewriting production history

A revision should have a reason, owner, approval, and effective condition. Depending on the business, effectivity may be a date, serial range, lot, customer configuration, or explicit production release. Existing orders may remain on the prior revision, adopt the new one, or require individual review. The decision must be visible.

When a component changes, use where-used analysis to identify parents, open production, purchase commitments, service obligations, quality documents, and remaining inventory. Decide whether old stock can be consumed, reworked, returned, segregated, or written off. This is why BOM change control belongs beside inventory and costing rather than in an isolated engineering file.

Connect expected cost with actual production

A cost rollup estimates the material, labour, machine, subcontracting, and overhead required by the approved BOM and routing. A production order records what actually happened. Variance may come from purchase price, substitution, extra consumption, scrap, yield, longer run time, a different resource, or an overhead rule.

Do not respond to every variance by changing the BOM. First determine whether the order was exceptional or whether the standard is no longer representative. Keep the calculation inputs and effective date so finance and operations can explain margin changes and reproduce the expected cost.

Test a BOM module with a difficult product

Use a multi-level assembly containing purchased and manufactured components, two units of measure, a substitute, scrap, a subcontracted operation, and a quality check. Approve one revision, release production, then introduce a component change while an order is open. The demonstration should show planning, issue, time, scrap, partial completion, finished receipt, cost, and inventory impact.

Acceptance evidence should answer which revision the order used, how required quantity was calculated, whether shortages are traceable, who approved the change, what value entered finished inventory, and how the result reaches accounting. This scenario tests the bill of material module in ERP more effectively than creating a simple component list.

How Simor ERP supports BOM and production control

Simor ERP connects BOMs, routings, work centres, production orders, work orders, material consumption, time logs, quality checks, scrap, subcontracting, cost rollups, inventory, and accounting. The product foundation can be reviewed live using a representative manufacturing scenario.

Simor Soft can adapt fields, statuses, approval rules, reports, documents, labels, integrations, shop-floor steps, and cost logic when the manufacturer has a justified requirement. This makes it possible to preserve product-definition control while fitting the operating model rather than forcing every plant into one generic sequence.

Handle variants, substitutes, and temporary deviations

Product families may share a common structure while size, colour, voltage, packaging, customer option, or region changes selected components. Decide whether the ERP will use separate BOMs, a configurable structure, option rules, or a controlled copy. The choice affects planning volume, revision effort, cost comparison, and the risk that one variant is updated while another is missed.

Approved substitutes need scope and priority. A substitute may be valid only for a site, supplier, customer, date range, or shortage. Record whether planning may select it automatically or a supervisor must approve its use on the production order. Temporary deviation should not silently change the master BOM. Preserve the reason, affected orders, quantity, approver, quality impact, and actual cost.

Connect BOM ownership across engineering, planning, production, and finance

Engineering may define design intent, but planning needs lead times and make-or-buy decisions, production needs executable operations, quality needs instructions and tolerances, purchasing needs approved components, and finance needs reproducible cost. Assign ownership for each field and create a review path that brings these perspectives together before release.

Segregation of duties may prevent the same user from creating and approving a high-impact revision. Emergency changes need an expedited path with later review. Reports should expose draft revisions, changes awaiting approval, obsolete components still on open orders, cost rollups that failed, and production using an unexpected version. These queues turn governance into daily work rather than a policy document.

Prepare BOM data for migration or implementation

Before loading structures, standardize item identifiers, units, parent-child relationships, quantities, revision codes, effectivity, make-or-buy status, and routing references. Detect loops, missing components, duplicate lines, impossible units, zero quantities, inactive parts, and parents without an approved version. Decide how drawings, specifications, and quality documents will remain linked.

Reconcile more than the number of BOM records. Compare component counts by parent, extended quantities for representative builds, where-used results, rolled cost, and material demand from a sample production plan. Then release a production order from migrated data and verify issue, completion, variance, and accounting. A structurally valid import is not sufficient if the resulting order cannot be executed correctly.

Measures that reveal BOM quality

Useful measures include production orders with unplanned material, component shortages caused by master-data errors, scrap variance, revision-related rework, cost-rollup exceptions, obsolete components on active structures, engineering-change lead time, and orders released with an unapproved or unexpected version. Define the source and owner for each measure.

Interpret the measures together. A faster change process is not an improvement if errors and rework rise. A lower material variance may hide frequent manual BOM edits. Review a sample of exceptions and connect the result to training, approval, source data, configuration, or product design before deciding on corrective action.

Related guides and solutions

How Simor Soft can help

Simor Soft can assess the current process, configure or customize Simor ERP and our other product foundations, build a dedicated application, connect existing systems, migrate data, and support the solution after launch for decisions about How a bill of materials supports production control. The recommended path depends on operational value, risk, timeline, and long-term ownership.