What is a Bill of Materials (BOM)?

What a Bill of Materials actually is

A Bill of Materials (BOM) is the structured list of everything that goes into a manufactured product — every raw material, component and sub-assembly, with the quantity-per and any scrap or yield allowance at each level. It is the engineering answer to one question: what is this product made of? Everything the shop floor does downstream starts from it. Explode a work order against its BOM and you know exactly what to reserve, requisition and issue; roll the BOM up and you know what the product costs in material; reverse it and you know every product a component touches.

A BOM is not a stores register and not a purchase list — it is a definition. It says that one finished good is built from, say, two of one sub-assembly and three kilograms of a raw material, and it holds that relationship independently of any one order. That is what makes it reusable: author it once, revise it under control, and every work order for that part explodes the same bill. In Fast Production Software the BOM header lives in one table and its material lines in another, so a single bill can carry hundreds of child lines and still be released, versioned and costed as one object.

Anatomy of a BOM line

Each line of a BOM is a relationship between a parent item and one child item. A well-formed BOM line carries at least these fields:

• Child item — the component, raw material or sub-assembly consumed.
• Quantity-per — how many units of the child go into one unit of the parent, in the child's unit of measure.
• Scrap / yield allowance — the extra material to requisition because some is lost in process, so the issued quantity reflects reality, not the theoretical minimum.
• Level / position — where the line sits in the indented structure, so a multi-level explosion knows what feeds what.
• Make-or-buy — whether the child is manufactured in-house (and therefore has its own BOM) or purchased.

Those fields are what let a system do arithmetic on a bill. Multiply quantity-per by the order quantity, add the scrap allowance, and you have the requisition. Roll the child costs up the levels and you have the material cost. Miss the scrap allowance and every issue comes up short; miss the make-or-buy flag and a purchased part gets treated as manufactured, or vice versa.

Single-level vs multi-level BOM

The single most important distinction in BOMs is depth.

In a single-level BOM, a finished good simply lists a sub-assembly as one line. In a multi-level BOM, that sub-assembly is a manufactured item in its own right — it has its own bill, its own route, its own semi-finished-goods transfer. This matters on the floor: an assembly manufacturer makes and books the sub-assembly (as SFG) before the final build, so the structure has to carry every level or the intermediate stock never gets tracked. A structural explosion is what lets each level be manufactured, costed and traced independently.

Master, structural and order-specific BOMs

A serious system holds a BOM in more than one form, because a make-to-order job cannot be allowed to corrupt the standard definition.

The order-specific bill is what a fabrication or job shop lives on — every order differs slightly, so the bill is carried against the customer order (OA) rather than forced into the master. Fast Production keeps the two eras distinct: a master bill authored and released once, and an order BOM built against a specific order, so a one-off change to a job never silently edits the standard the rest of the floor is building against.

BOM vs Bill of Resources

The BOM has a twin that is easy to confuse with it: the Bill of Resources (BOR). Where the BOM lists what a product is made of, the Bill of Resources lists what it takes to make it — the machines, labour, tools and operations each level consumes.

The two are released together and, taken as a pair, define a manufacturable part: the BOM feeds material issue and WIP, the BOR feeds the process route and work centers. Get both and a work order can be exploded for material and scheduled onto machines from one released definition. This pairing is also the foundation of BOM costing: material roll-up from the BOM lines, resource cost from the BOR and operation times.

Where-used and BOM-level reporting

A BOM explosion runs top-down: from a parent to its children. The where-used report runs the other way — from a component to every parent that consumes it. It answers which products use this part?, and it is indispensable the moment anything about a component changes.

Suppose a supplier discontinues a fastener, or a raw-material grade is superseded. Before you can act you need to know every BOM and every open work order that fastener sits in — otherwise you fix one product and break three others. Where-used analysis, together with BOM-level (indented) and item-wise BOM reporting, is how a plant sees the full blast radius of a change before it makes it. It is also the natural input to an engineering change notice: the ECN team runs where-used to scope the change, then revises every affected bill under control.

Release control and engineering change

The most under-appreciated thing about a BOM is that it has a status. A bill is authored and revised in draft, but production must never build against a definition that is still moving. Release control promotes a BOM from draft to a released status, at which point — and only then — a work order can explode against it. In Fast Production the bill and its process list are released together, so the floor gets a material definition and a route in one controlled step.

After release, nothing changes silently. Anything that must be revised goes through an engineering change (ECN): the change is raised, approved and released, the revised bill becomes the active definition, and superseded revisions stay traceable. That discipline is what lets an automotive or engineered-part maker answer an audit question — which revision of the bill built this lot? — years after the fact. A BOM without release control and change history is a document; a BOM with them is a controlled engineering record.

How Fast Production Software holds the BOM

Fast Production Software, built by Improsys in Pune on the shared Fast Suite platform, implements every form of BOM described above as real, exercised modules:

Because it runs on the shared platform, the same BOM feeds Fast Planning / MRP upstream and shares its stock ledger with Fast Inventory and Quality downstream — the manufacturing core behind real deployments such as Nikhtish Engineering and Solidus Hi-Tech, where the BOM tables run to tens of thousands of live lines.

Frequently asked questions