What is the difference between a BOM and a parts list?

A parts list says what a thing contains. A bill of materials says what it contains in what quantity, in what relationship, under what conditions and at what revision. Those extra clauses exist because real questions cannot be answered without them.

What is a phantom assembly?

An assembly that exists in engineering and not in the world — a fastener kit is the usual example. It is convenient to reference as one line, never purchased as a kit, and exploded into its components when manufacturing consumes them on the line.

Why do reference designators matter?

Because their count should equal the quantity, and when it does not, one of the two is wrong. It is a cheap check that is almost never automated, which is how boards get built with three of a component that has four places on the layout.

What is the difference between EBOM and MBOM?

The engineering bill describes what the product is; the manufacturing bill describes how a specific plant builds it. They diverge over phantoms, packaging and consumables, regional substitutions and assembly sequence — all legitimate, all lost if you run only one.

What does effectivity mean?

The window in which a BOM line applies — a date range, a unit-number range, or a plant. It is how a bill holds both the old and the new component as correct answers during the weeks between a change being approved and taking effect.

What is a floating child reference?

A line naming the part rather than an exact revision, letting a policy decide which revision applies: latest released, effective at a date, or pinned at parent release. A pinned reference never moves. The mistake is not knowing which kind a line uses.

What a bill of materials actually is

A parts list is not a bill of materials

A parts list says what a thing contains. A bill of materials says what a thing contains, in what quantity, in what relationship, under what conditions, at what revision. The extra clauses are not bureaucracy; each one exists because a real question could not be answered without it.

The clearest way to see the difference is to ask a bill of materials a question it cannot answer as a list. “What did unit 1420 contain when it shipped in March?” A list has one answer, which is whatever the list says now. A bill of materials has the right answer, which is what was effective for that unit on that date.

That is the whole subject. Everything below is a mechanism for holding more than one true answer at a time without a person arbitrating between them.

Structure: levels, not rows

A BOM is a tree, not a table. A product contains sub-assemblies, which contain parts, which may themselves be assemblies. The nesting matters because it describes how the thing is built and because change propagates along it.

Single-level shows what one assembly directly contains. Multi-level or indented expands the whole tree. Flat or summarised collapses everything to a total per part, which is what purchasing wants — a screw appearing four times in a housing used twice is eight screws, and the flat view is the only one that says so.

A phantom is an assembly that exists in engineering and not in the world. A fastener kit is the common example: convenient to reference as one line, never bought as a kit, and exploded into its components when manufacturing consumes it. Phantoms are why the engineering and manufacturing structures legitimately differ.

Parent — the assembly a line belongs to.
Child — the part or assembly the line references.
Line — the relationship itself, with quantity and conditions on it. This is the object that matters, and the one most tools under-model.
Level — depth in the tree. Level 0 is the product; a fastener three levels down still affects it.

Quantity is harder than it looks

Most quantities are integers and most of the difficulty comes from the ones that are not.

Fractional quantities appear whenever a part is consumed by measure: 1.4 metres of cable, 12 grams of adhesive, 0.25 of a sheet. The unit of measure is part of the quantity, and a system that stores the number without the unit produces errors that are wrong by a factor rather than by an item — which is the kind that survives review.

As-required covers consumables where the quantity genuinely is not fixed: solder, flux, thread-locker. Recording zero is wrong and recording a guess is worse; a distinct as-required value is the honest option.

Scrap and yield are the difference between what is consumed and what ends up in the product. A component with a 2% expected loss needs 102 issued per 100 built, and where that factor lives — engineering quantity or manufacturing quantity — is a real modelling decision.

Reference designators name where each instance goes: R1, R2, R3, R4. Their count should equal the quantity, and when it does not, one of the two is wrong. That check is cheap and almost never automated, which is why boards get built with three of a four-place component.

The four conditions

This is the part that separates a bill of materials from a list, and it is where most tools stop.

Effectivity — the window in which a line applies. Usually a date range, sometimes a unit-number range for serialised products, sometimes a plant. A change approved in August to take effect on 1 October means both the old and new component are correct answers, for different questions, for six weeks.

Options and variants — which configuration a line belongs to. A product shipping in 120 V and 240 V has both power supplies in the structure, and exactly one of them in any given build.

Revision policy — what a line means when it names a part without naming a revision. A pinned reference points at an exact revision forever. A floating reference lets policy decide: latest released, the revision effective on the date asked about, or the one pinned when the parent released. Both are legitimate; not knowing which a line uses is not.

Plant scope — which site a line applies to. The same product built in two places often differs by a label, a carton, or a locally sourced component.

Supply all four and the structure resolves to exactly one answer. Supply none and it has many, all of them defensible, which is why two people reading the same BOM reach different conclusions and both are right.

EBOM and MBOM are different documents

The engineering bill describes what the product is: the design, as engineering owns it. The manufacturing bill describes how a particular plant builds it.

They diverge for four reasons, all legitimate. Phantoms explode into their components. Manufacturing-only parts appear — cartons, labels, thread-locker, desiccant, protective film, none of which are in the design and all of which are consumed. Plants substitute regional parts. And structure gets reorganised around assembly sequence rather than function.

Teams that run one bill for both purposes usually discover the problem when an engineer restructures an assembly and the packaging silently disappears. Teams that run two without a trace between them discover it when a design change reaches engineering's bill and nothing else.

How to tell whether yours is under control

Four questions, none of which need software to ask.

Can you answer what a specific unit shipped with, without reconstructing it from work orders? Reconstruction tells you what was consumed, not what was specified, and if a substitution was recorded as the original it is confidently wrong.

Does a change take effect on a date, or on approval? If those are the same event, every phased cutover is a manual reconciliation and stock gets stranded.

Does anyone keep a private spreadsheet? Not as a failing — as a signal. A spreadsheet beside the system is a list of things the system makes hard, and it is usually the most accurate document in the building.

Do two reports about the same product ever disagree? A cost rollup and a where-used that return different line sets means each is computing conditions its own way, and there is no way to tell which is right.