Exploded View, Parts List and BOM: What Each One Is in Catalog Data

An exploded view is a diagram showing an assembly's parts in spatial order. A parts list is the table of part numbers keyed by position. A BOM is the structured component tree. This entry covers what each one carries, the three BOM variants, and what goes wrong when they disagree.

An exploded view is a diagram that shows an assembly’s parts pulled apart along their assembly axes, with callout numbers pointing to each component. A parts list is the table that maps each callout number to a part number, description and quantity. A BOM (bill of materials) is the full structured tree of every component in the product. The three overlap but are not the same thing.

A technician looks at an exploded view in a parts book, finds position 14, reads across to part number HY-3200, and places an order. If that parts book was published in 2019 and HY-3200 was superseded by HY-3450 in 2022, the order is wrong — and the exploded view gives no signal that anything changed. That is the central problem: the visual and the data behind it are authored separately, stored separately, and updated on different schedules.

What each one carries

Artifact	What it contains	Where it lives	Who maintains it
Exploded view	A diagram: parts shown in spatial order with callout numbers	Parts books (PDF, print), OEM service portals, aftermarket catalogs	Engineering or technical publications team; rarely updated after initial release
Parts list	A table: position number → part number, description, quantity, notes	Same parts books, ERP item records, catalog databases	Product data or catalog team; updated when part numbers change
BOM	A structured tree: parent assembly → child components, with quantities and levels	ERP (mBOM), PLM/CAD (eBOM), service documentation (sBOM)	Engineering, manufacturing or service teams depending on variant

The three BOM variants

The same product can have three different BOMs, built for three different audiences:

eBOM (engineering BOM) — the as-designed structure. It comes from CAD or PLM and represents what engineering intended the product to be. It includes every component down to the smallest fastener, organized by design hierarchy.

mBOM (manufacturing BOM) — the as-built structure. It adds manufacturing process steps, tooling, phantom assemblies (groupings that exist for production but are not a physical subassembly), and shop-floor sequencing. An mBOM may combine or split eBOM items to match how the product is actually assembled.

sBOM (service BOM) — the as-maintained structure. It lists only the parts a field technician can replace, organized by service procedure rather than design hierarchy. An sBOM drops internal components that are never serviced individually and adds consumables (lubricants, seals, filters) that are not in the eBOM at all.

BOM variant	Perspective	Typical source system	What it includes that the others may not
eBOM	As designed	PLM, CAD, PDM	Every component, including those never serviced individually
mBOM	As built	ERP production module, MES	Process steps, phantom assemblies, shop-floor sequences
sBOM	As maintained	Service manuals, aftermarket catalogs	Consumables, wear parts, service kits — items not in the original design BOM

What goes wrong when they disagree

In theory, the exploded view, the parts list and the BOM all describe the same product. In practice, they are authored in different systems, by different teams, on different schedules. The common mismatches:

Superseded part numbers. The BOM in ERP is updated when a manufacturer issues a supersession notice. The parts list in the catalog may be updated separately — or not at all. The exploded view diagram almost never changes because redrawing is expensive. Result: the diagram points to a position, the position maps to an old part number, and the BOM carries the new one.

Quantity mismatches. A parts list may show “1” for a kit that the BOM breaks into three line items. Or the sBOM lists a service kit as one orderable unit while the eBOM lists its individual contents.

Missing items. The sBOM adds consumables that were never in the eBOM. The exploded view omits parts too small to draw. The parts list carries items that exist in the catalog but were removed from the current BOM revision.

Revision drift. The exploded view was drawn for revision A of the assembly. The BOM is at revision C. Two revisions of engineering changes sit between them, and nobody reconciled the diagram.

Before and after

Before	After
Exploded view is a static image disconnected from live part data	Each callout position is linked to the current part record, with supersession chain resolved
Parts list is a flat table with no relationship to the BOM hierarchy	Parts list positions map to sBOM nodes, so a technician sees both the visual position and the component tree
Three BOMs live in three systems with no cross-reference	eBOM, mBOM and sBOM are related through shared component identities, so a change in one surfaces in the others

Where Claro fits

Claro connects the parts list to the product identity layer. When a parts-book position references a part number, Claro resolves it through the supersession chain to the current SKU and flags mismatches between the catalog record and the BOM. The result is a parts list where every position points to a live, sourced product identity — not a static number from a PDF published years ago.

Glossary

Spare Parts Data Glossary

All spare-parts data terms in one table.

Glossary

Position number and callout number

The reference numbers that link a visual part to its row in the parts list.

Guide

Parts book data model

How to structure the data behind a parts book so it stays current.

Comparison

Exploded view vs parts list vs BOM

Side-by-side: what each artifact carries, who maintains it, and where they diverge.

FAQ

What is the difference between an exploded view and a parts list?

An exploded view is a diagram that shows each component pulled apart along its assembly axis, with callout numbers pointing to each part. A parts list is the accompanying table that maps each callout number to a part number, description and quantity. The diagram shows where; the table shows what.

What are the three types of BOM?

An engineering BOM (eBOM) is the as-designed structure from PLM or CAD. A manufacturing BOM (mBOM) is the as-built structure with process steps and shop-floor sequences. A service BOM (sBOM) is the as-maintained structure listing the replaceable parts a field technician needs. The same product can have all three, and they rarely agree completely.

Why do exploded views and BOMs disagree?

Because they are authored in different systems at different times by different teams. The exploded view comes from the original parts book, often as a static image. The BOM comes from ERP or PLM. When part numbers change through supersession, one source may be updated while the other is not, creating mismatches that surface as wrong-part orders.