Bills of material that stay true after the third revision.
Multi-level structures, controlled revisions, engineering change orders and where-used lookups, so a design change reaches production instead of an inbox.
A bill of material is the most referenced record in a factory and usually the least governed. It decides what gets bought, what gets issued, what a product costs and what the customer is quoted. And in a large number of units it lives in a spreadsheet that has been copied, edited and emailed enough times that nobody is certain which file is current.
The cost of that is not abstract. It is material purchased against an old revision, an assembly built with a superseded part, a quotation priced from a structure that changed two months ago. Each one is discovered late, and each one is expensive in a way that is hard to attribute back to its cause.
BOM management software is not a prettier parts list; it is a governed one. Managing the BOM as a controlled record instead of a document fixes the class of problem rather than the instance. There is one current revision. Changing it is an event with an author and a date. Anything that consumed the old one — an open work order, a pending purchase order, a live quotation — is findable, because the structure knows what uses it.
What you get
Multi-level structures
Assemblies containing sub-assemblies that have bills of their own, expanded to raw material whenever the full requirement is what you need.
Controlled revisions
One current version, with the previous ones kept, so what a job was built against is still answerable a year later.
Engineering change orders
A design change raised, reviewed and released as an event, rather than a new file appearing on a shared drive.
Where-used lookups
Every assembly a component appears in, which is the question you need answered the moment a part is superseded or a supplier stops making it.
Costing from the structure
Material cost rolled up through the levels, so a change in a raw material rate reaches the finished product's cost without anybody recalculating.
Feeds planning directly
The same structure that describes the product drives the material requirement when a work order is released.
The where-used question
Most BOM work runs top-down: what goes into this product. The question that actually costs money runs the other way — which products contain this component. It comes up when a supplier discontinues a part, when a batch is found defective, when a price moves sharply, or when an engineering change touches something shared across several assemblies.
Answered from a spreadsheet, it is a search across files and a hope that none were missed. Answered from a structured BOM, it is a lookup, and the list it returns is the list of everything that has to be reviewed. The difference decides whether a component problem is contained or discovered one assembly at a time.
Why engineering changes need to be events
A design change that arrives as a revised drawing on email has no mechanism behind it. Whether purchase saw it, whether the open work orders were reviewed, whether the existing stock of the old part is usable or scrap — all of that depends on somebody thinking to ask.
Raising the change as an engineering change order gives it the mechanism. The change has an owner, a reason and an effective point, and the things it affects are visible because the structure knows them. Production keeps building to the old revision until the change is released, which is usually the correct answer and almost never what happens when the change arrives as a file.
Costing that follows the structure
When the BOM is structured, product cost is a roll-up rather than an estimate: material at each level, aggregated upward. That makes rate changes traceable — a casting that went up eleven percent shows its effect on every finished product containing it — and it makes quotation a calculation instead of a judgement call about how much the last price should move.
Questions people ask.
What is BOM management software?
It holds the bill of material as a structured, versioned record rather than a document: multi-level assemblies, one current revision with history behind it, and the links that let you ask which products a given component is used in.
Does it support multi-level bills of material?
Yes. An assembly can contain sub-assemblies that carry their own bills, and the whole structure can be exploded to raw material when a work order needs the full requirement.
How are engineering changes handled?
As an engineering change order — a change with an owner, a reason and a release point, so production continues to the current revision until the new one is released and everything the change affects can be reviewed first.
Can we see which products use a particular component?
Yes. A where-used lookup returns every assembly containing the component, which is the list you need when a part is superseded, discontinued or found defective.
Does the BOM drive purchasing and production?
Yes. The same structure produces the material requirement when a work order is released, and the shortage that requirement reveals is what purchase works from.
Related parts of the system
Tell us what you make.
The useful version of a demo uses your own item list and last month's orders, not ours.
Get in touch