Barcode Technology

Barcode History

Barcode Label Paper

Barcode Printer

Barcode Application

Inventory Management

AI Barcode QRCode

Barcode Scanner

Barcode Software

Barcode Software B

Barcode Software C

Barcode Software D

Barcode Software E

New Technology A

New Technology B

Robot Technology

Barcode Types

Barcode Types B

Barcode Types C

Barcode Types D

Barcode Types E

Barcode Types F

Electronic Technology

Psychology at Work

Barcode Technology and Barcode Software Related   <<< Back to Directory <<<

How ERP Systems Drive the Mechanical Manufacturing Industry (P2)

Chapter 2: From Blueprint to BOM - The Product Structure

2.1 The Invisible Skeleton of Every Machine

Every physical product in mechanical manufacturing - from a simple cast-iron bracket to a multi-stage industrial gearbox - has an invisible skeleton. That skeleton is not made of steel or aluminum. It is made of information. Specifically, it is a structured list that answers three deceptively simple questions:

1. What parts go into this product

2. How many of each part

3. How do those parts relate to each other

This list is called the Bill of Materials (BOM) . In non-technical language, a BOM is a recipe. But in the world of ERP systems and mechanical manufacturing, a BOM is far more powerful than a kitchen recipe. It is the single source of truth for engineering, purchasing, production, quality, and even finance. Without an accurate BOM, a factory cannot order the right materials, cannot schedule the right operations, cannot cost the product correctly, and cannot deliver on time.

This chapter explains what a BOM really is, why it sits at the heart of every ERP system, and how mechanical manufacturers must structure it to avoid costly errors.

2.2 The Simple Idea That Becomes Complex

At first glance, a BOM seems trivial. For a simple product like a steel shaft, the BOM might be:

| Item | Quantity | Unit |

||-||

| 4140 steel round bar, 50mm diameter x 300mm | 1 | piece |

| Protective oil coating | 0.01 | liter |

| Packaging cardboard tube | 1 | piece |

That is a single-level BOM. It shows only the finished product and its immediate components. For a product with five parts, a single-level BOM might be sufficient. But mechanical manufacturing rarely stays that simple.

Consider a hydraulic cylinder assembly. It contains:

- A cylinder barrel (machined from steel tube)

- A piston rod (machined from solid bar)

- A piston head (machined from cast iron)

- Seals (bought from a supplier)

- End caps (machined from steel plate)

- Various screws and retaining rings

Each of those machined parts *itself* requires raw materials and possibly sub-assembly operations. The cylinder barrel might require a welded mounting bracket, which itself is fabricated from a steel plate and a boss. The piston rod might require chrome plating done by an outside subcontractor.

This nested structure forces us to think in multiple levels. A single-level BOM is insufficient. What we need is a multi-level BOM that shows the entire product tree.

2.3 The Product Tree - Visualizing the BOM

An ERP system stores the BOM as a hierarchical structure, often called a product tree or indented BOM. Each level of the tree represents a step in assembly or manufacturing. The root (top level) is the finished, sellable product. Below it are subassemblies. Below those are components. At the lowest level are raw materials or purchased items.

Let us build a concrete example: a simple pneumatic cylinder assembly (part number CYL-100).

Level 0: Finished Assembly

- CYL-100: Pneumatic cylinder, 100mm stroke

Level 1: Direct children of CYL-100

- BODY-100: Cylinder body (machined, requires raw tube)

- PISTON-100: Piston assembly (subassembly)

- ENDCAP-100: End cap (machined)

- SEAL-KIT: Purchased seal kit

- SCREW-M5x20: 4 pieces, purchased

Level 2: Components of PISTON-100 (subassembly)

- ROD-100: Piston rod (machined)

- PISTON-HEAD-100: Piston head (machined)

- NUT-M10: 1 piece, purchased

Level 3: Raw materials for machined parts

- For BODY-100: Aluminum tube, 80mm OD x 60mm ID x 150mm long

- For ENDCAP-100: Aluminum plate, 10mm thick x 120mm square (rough size)

- For ROD-100: 4140 steel bar, 20mm diameter x 200mm long

- For PISTON-HEAD-100: Aluminum bar, 60mm diameter x 30mm long

In an ERP system, this tree is not just a picture. It is a set of linked database records. When an engineer changes the PISTON-HEAD material from aluminum to steel, the ERP instantly recalculates the cost, weight, and procurement requirements for the entire CYL-100 assembly.

2.4 Engineering BOM vs. Manufacturing BOM - A Critical Distinction

One of the most common and costly mistakes in mechanical manufacturing is confusing the Engineering BOM (EBOM) with the Manufacturing BOM (MBOM) . They are related but not identical.

Engineering BOM (EBOM): Created by design engineers in CAD (Computer-Aided Design) systems. The EBOM reflects the product *as designed*. It is function-oriented. It shows every part that makes the product work, exactly as it appears on the exploded-view drawing. The EBOM typically lists the piston rod as a single line item.

Manufacturing BOM (MBOM): Created by manufacturing engineers and production planners. The MBOM reflects the product *as built*. It is process-oriented. It includes not only the same components but also:

- Manufacturing aids (e.g., fixture plates, cutting tools that are consumed)

- Packaging materials (e.g., anti-rust paper, wooden crates)

- Intermediate states (e.g., 'piston rod, after turning but before grinding')

- Subcontract operations (e.g., 'heat treatment - external supplier')

- Consumables (e.g., coolant, cutting oil - sometimes allocated per batch)

In many mechanical factories, the EBOM and MBOM live in different systems - the EBOM in CAD, the MBOM in spreadsheets or legacy systems. When a design changes, someone must manually update the MBOM. Human error is almost inevitable. A missing or incorrect MBOM leads to purchasing the wrong steel grade, ordering incorrect quantities, or skipping an inspection step.

A modern ERP system for mechanical manufacturing bridges this gap in two ways:

1. It can import the EBOM directly from CAD files (via integration tools).

2. It provides a workspace to convert the EBOM into an MBOM by adding manufacturing-specific data, while maintaining a link to the original design.

The golden rule: One change, one update. If the engineering team changes the piston diameter from 20mm to 22mm, that single change in CAD should, through the ERP integration, automatically flag the MBOM for review and update. No separate manual data entry.

2.5 BOM Types: Single-Level, Indented, Modular, and Phantom

Beyond the EBOM/MBOM distinction, ERP systems support several BOM structures for different manufacturing scenarios. Mechanical manufacturers encounter all of them.

Single-level BOM: Lists only the immediate children of an assembly. Suitable for very simple products or for high-level cost estimation. Rarely sufficient for production planning.

Indented (multi-level) BOM: Shows the full hierarchy with indentation to indicate levels. This is the standard for ERP systems. It allows material requirements planning (MRP) to explode the entire product tree and calculate requirements at every level.

Modular (or configurable) BOM: Used when a product family has many variants. For example, a gearbox manufacturer might offer the same basic housing with three different gear ratios, two different input shaft lengths, and an optional cooling fan. A modular BOM contains all possible components, with rules that select the correct subset when a customer order is placed. This is also called a 150% BOM - because no single product uses more than 50% of the listed items, but the BOM contains 150% of what any one variant needs. The ERP system applies configuration rules to generate a specific, flattened BOM for each order.

Phantom BOM: A special technique for items that are never stocked as inventory. Instead, they are immediately consumed into the next level of assembly. For example, a small welded bracket might be produced and then immediately attached to a larger frame in the same work center. By marking the bracket as a phantom in the ERP, the system plans the production of the bracket but does not create an inventory record for it. This reduces unnecessary stock-keeping units (SKUs) and simplifies the planner's view.

Planning BOM: A simplified BOM used for forecasting and aggregate planning. It groups similar components (e.g., 'assorted M6 screws') rather than listing every individual part number. Planning BOMs are converted into detailed BOMs when firm orders arrive.

2.6 Where BOMs Go Wrong - Real Disasters

Theory is clean. Reality is messy. Let us examine three real-world failure modes of BOM management in mechanical manufacturing.

Case 1: The Missing Substitution Rule

A pump manufacturer listed a specific stainless steel grade (316) for a housing. The purchasing agent could buy the cheaper 304 grade if approved by engineering, but the ERP had no place to store that substitution rule. A new buyer ordered 316 at double the price. The cost overrun on that one order wiped out the profit for the entire quarter.

What the ERP should have done: The BOM item should have had an approved substitute field, with priority rules. When inventory of 316 was low, the system would suggest 304 as an alternative and route the substitution request to engineering for quick approval.

Case 2: The Phantom That Wasn't

A valve manufacturer created a separate part number for a small bushing that was always made in the same operation as the valve seat and immediately assembled. The ERP treated the bushing as a normal inventory item. The planners had to create separate work orders, move inventory, and count the bushing in year-end physical inventory - all for an item that never sat on a shelf. Thousands of hours were wasted over five years.

What the ERP should have done: The bushing should have been modeled as a phantom or even just a note on the valve seat routing. A proper BOM review by manufacturing engineers would have caught this.

Case 3: The Uncontrolled CAD Export

A heavy equipment manufacturer allowed any designer to export a BOM from CAD directly into the ERP without a formal change process. One junior designer accidentally set the quantity of hydraulic hoses from 1 to 10. The ERP created purchase requisitions for 10 times the needed hoses. The factory received 900 hoses instead of 90. Storage space overflowed, and cash was tied up for months.

What the ERP should have done: The integration should have been gated by an engineering change order (ECO) workflow. Any BOM change must be approved by a senior engineer and a planner before it updates the live MBOM.

2.7 The Role of the BOM in Material Requirements Planning (MRP)

The BOM is not just a static list. It is a dynamic input to the ERP's most powerful engine: Material Requirements Planning (MRP) . MRP takes three things:

1. A master production schedule (what finished products are needed, and when)

2. The BOM (what components make each finished product)

3. Inventory status (what is already on hand or on order)

MRP then performs an operation called BOM explosion. Starting at the top level, it multiplies the required quantity of the finished product by the BOM quantities, subtracts existing inventory, and generates planned orders for components at each level.

Let us walk through a small explosion example. Suppose we need 10 units of CYL-100 (the pneumatic cylinder from section 2.3). The BOM tells us:

- Each CYL-100 needs 1 BODY-100 --> need 10

- Each CYL-100 needs 1 PISTON-100 --> need 10

- Each PISTON-100 needs 1 ROD-100 --> need 10

- Each ROD-100 needs 1 piece of 4140 steel bar --> need 10

If the ERP already has 3 ROD-100 in inventory, the net requirement becomes 7 ROD-100, which translates to 7 steel bars. This simple multiplication repeats for thousands of parts across hundreds of finished products. A human cannot do it reliably. An ERP can do it in seconds.

Without an accurate BOM, MRP becomes garbage-in, garbage-out. A single missing component in the BOM means that component will never be ordered, and production will stop when it is missing.

2.8 BOM Accuracy - The Single Most Important Metric

In ERP implementation, there is a well-known saying: 'BOM accuracy is not a goal; it is a prerequisite.' What level of accuracy is acceptableFor mechanical manufacturing, best-in-class plants achieve 99% or higher BOM accuracy. How is accuracy measuredBy randomly selecting a BOM, going to the factory floor, and physically verifying that every listed component exists in the right quantity, and that no unlisted component is used.

A 95% BOM accuracy might sound good, but it means that one in twenty products has an error. In a factory producing 500 different assemblies, that is 25 assemblies with wrong BOMs - enough to cause multiple daily shortages.

How do factories achieve high BOM accuracy

1. Disciplined engineering change process - No change without an ECO number.

2. Regular BOM audits - Random checks by a cross-functional team.

3. Closed-loop feedback - When a machinist notices a discrepancy (e.g., the BOM calls for a 50mm screw but a 55mm screw fits better), there is a simple digital form to flag the issue to engineering.

4. Integration with CAD - Eliminate manual re-entry.

2.9 The BOM Lifecycle in ERP

A BOM in a mechanical ERP system is not static. It passes through several stages from creation to retirement.

| Stage | Description | Typical Actions |

|-|-||

| Preliminary | Engineering is still exploring options | No procurement or production allowed |

| Released to prototype | BOM is stable enough to build prototypes | Small-scale material orders, special work order type |

| Released to production | Fully approved for regular manufacturing | MRP can generate purchase requisitions and work orders |

| Hold/blocked | A problem has been found; do not use | Investigation by engineering; procurement suspended |

| Phased-out | Product is discontinued | No new work orders; service parts may remain |

| Archive | No longer active in production | Historical cost analysis only |

Each transition requires approval, often recorded as an ECO. The ERP maintains a full revision history. If a part made in 2022 used BOM revision B, and revision C changed the seal type, the ERP can still report historical costs correctly.

2.10 BOMs and Costing - Where Every Penny Starts

A mechanical product's cost is not a mystery. It is the sum of:

- Material cost (from BOM, using current purchase prices or standard costs)

- Labor cost (from routing times multiplied by labor rates)

- Machine cost (from routing times multiplied by machine hour rates)

- Overhead (allocated based on formulas)

The BOM directly feeds the material cost. If the BOM says a gearbox uses 2 kg of bronze, and bronze costs $10/kg, the material cost is $20. If the BOM incorrectly says 1 kg, the ERP will show an optimistic $10 material cost, but the factory will buy and use 2 kg, bleeding $10 per unit in hidden loss.

Modern ERP systems support standard costing with variances. The standard material cost is calculated from the BOM and standard prices. When production reports actual usage, the ERP compares actual vs. standard. A large negative variance (actual > standard) often points to a BOM error - either wrong quantity in the BOM or excessive scrap on the shop floor.

2.11 Practical Advice for Mechanical Manufacturers

If you are implementing or improving an ERP system in a mechanical factory, focus on these BOM principles:

1. One BOM owner per product - Typically a manufacturing engineer. No drive-by edits from sales or finance.

2. Use phantom BOMs aggressively - For items that are never stocked, save the SKU.

3. Never bypass the ECO process - Even for 'small' changes. Small changes aggregate into big errors.

4. Train everyone who touches the BOM - Designers, planners, buyers, and even machinists who report discrepancies.

5. Start with a pilot family - Clean up BOMs for one product family (e.g., all small cylinders) before rolling out to all products.

6. Measure BOM accuracy weekly - And post the results in the factory. Visibility drives improvement.

2.12 Summary: The BOM as the Heart of ERP

Return to our original image. A BOM is far more than a list. It is the structural skeleton of every product. The ERP system reads that skeleton to order materials, schedule machines, assign labor, calculate costs, and invoice customers. When the BOM is accurate, the ERP can perform its magic: transforming a chaotic collection of raw steel, cutting tools, and machinist hours into a finished product delivered on time and at the right cost.

When the BOM is wrong, nothing else matters. The best scheduling algorithms, the fastest CNC machines, and the most motivated workers cannot compensate for the fact that the factory ordered aluminum instead of steel, or 50 screws instead of 500.

In the next chapter, we will look at how the ERP uses the BOM (together with inventory data) to keep the factory fed with materials - a discipline called inventory management. But always remember: inventory management begins and ends with the BOM. No BOM, no plan. No plan, no product.

Key takeaways from Chapter 2 (expanded):

1. The BOM is a hierarchical list of all components, raw materials, and subassemblies in a product.

2. Multi-level (indented) BOMs are essential for mechanical manufacturing.

3. Engineering BOM (as designed) and Manufacturing BOM (as built) must be linked but can differ.

4. Modular, phantom, and planning BOMs solve specific manufacturing scenarios.

5. BOM errors directly cause material shortages, excess costs, and late deliveries.

6. BOM accuracy of 99%+ is achievable with disciplined processes and ERP integration.

7. The BOM feeds MRP, costing, purchasing, and shop floor execution - it is the single most important data structure in the ERP system.

 

EasierSoft Barcode Label Design & Bulk Printing Software

---- Use Excel Data to Batch Print Barcodes on Label Sheets or Roll Labels  

---- How to use this barcode software

Download:  Free Barcode Software + Barcode Label Designer

Download Free Barcode Software at Softonic

     Download at CNET

Once you obtain a GS1/UPC/EAN barcode, or other barcode type and QR code, you can use our free software to batch print barcode labels onto Roll label paper using a professional label printer, or to batch print barcodes onto Avery 5160 label sheets using a regular laser or inkjet printer. Our software has free and paid versions.

The free version fully meets your needs for batch printing GS1/UPC/EAN barcodes. The paid version can import data from Excel and databases to batch print barcode labels with different values.

How to Start

Input Data

Import Excel Data

Print Barcode

Barcode Format

Label Designer

All Screen Shot

Export Barcode Image

Save Template

Output Word Excel

How to Use & FAQ:

Print bulk barcodes quickly

Print barcodes to Avery 5160 label

How to bulk Barcode Printing

Sample - Avery 5162 (2x7) Label Sheet

Example: Print barcodes to 5*3cm roll

Example: Print barcodes to 5161 label

Example: Print barcodes to 5162 label

Example: Print barcodes to 5163 label

Example: Print barcodes to 5164 label

Example: Print portrait orientation 5164

Example: Print barcodes to 5167 label

Example: Print barcodes to 5168 label

Example: Print portrait orientation 5168

Example: Print barcodes to 5169 label

Example: Print barcodes to 5660 label

Example: Print barcodes to 5661 label

Example: Print barcodes to 5662 label

Example: Print barcodes to 5663 label

Example: Print barcodes to 5664 label

Example: Print portrait orientation 5664

Example: Print barcodes to 5873 label

Example: Print barcodes to 5874 label

Two ways to import Excel data

Import Excel Data - Pro Edition

Import Excel Data - Std Edition

Import Data from Excel - Detail

Load Data From Excel File

Data Editing Table

Copy Data From Excel

Four ways to input barcode data

Add ASCII Key E

Input Multiple Lines of Text for Barcodes

Generates Sequential Serial Numbers

Import or copy data from Excel sheets

Special sequence number generation

Std Details: Simple Input Form

Std Details: Multiple Line Text Input

Details: Sequence Barcode Generator

Examples: Sequence Barcode Generator

Import Data From Excel Spreadsheet

Barcode Data Correspondence Diagram

Data Editor

Editing a Single Row Data in Form

Batch Editing Multiple Rows of Data

Batch Data Editing - Example 2

Design & print complex barcode labels

Configuring Text Elements on Label

Configuring Barcode Elements on Label

Configuring Image Elements on Label

Setting Line Elements on Label

Highlights

Excel integration: Import data directly from Excel to generate and print barcodes in bulk.

Label designer: Create complex labels with multiple barcodes, text, logos, and shapes.

Batch printing: Print thousands of barcodes at once using standard inkjet/laser printers or professional barcode printers.


Flexible editions:

Standard Edition: Simple batch printing with Excel data.

Professional Edition: Adds command-line automation for workflow integration.

Label Designer Edition: Advanced design features for complex labels.


Why Choose Our Barcode Solutions?

Cost-effective: Free online generator and permanent free desktop version available.

Easy to use: No technical expertise required—just input data and print.

Versatile: Supports nearly all 1D and 2D barcode types, including QR codes.

Trusted: Recommended by CNET and widely downloaded by users worldwide.


Suitable Use Cases

Small businesses and startups needing quick barcode labels for products.

Retailers and online sellers managing inventory with batch barcode printing.

Manufacturers requiring sequential or custom barcode labels for packaging.

Educational and testing environments where barcodes are used for tracking.

 

 

CONTACT

cs@easiersoft.com

If you have any question, please feel free to email us.

 

https://free-barcode.com

 

<<< Back to Directory <<<     Barcode Generator     Barcode Freeware     Privacy Policy