GUIDE

How is a BOM extracted from a drawing package?

A BOM can arrive as a genuinely tabular file, embedded in a drawing's parts list, or spread across a multi-sheet assembly with balloons pointing to a separate table. Extraction means normalising whichever shape it arrived in, then cross-checking that every balloon on a drawing has a matching line and every line is actually called out somewhere.

Key facts

Category
Reading the documents
Applies to
Sheet metal and fabrication
Cross-check
Every balloon matched to a line, every line called out
Last verified
August 28, 2026

What forms does a BOM actually arrive in?

Sometimes a genuinely tabular file, an Excel or CSV sheet with columns already labelled. Sometimes a table embedded in a drawing's title block or a dedicated parts-list sheet. Sometimes there is no single table at all: an assembly drawing carries item-number balloons that only make sense once matched against a separate parts list on another sheet.

How does a tabular source get normalised?

By mapping whatever headers the customer used, QTY, Item No, P/N, Description, Material, or any variant of them, onto one consistent schema, and cleaning up the row-level noise that comes with real spreadsheets: quantities entered as text, merged header cells, and subtotal rows that are not real line items.

How does a drawing-embedded parts list get reconciled?

The table structure is extracted from the sheet itself, then every item-number balloon shown on the drawing view is checked against the parts list rows: a balloon with no matching line, or a line never called out on any view, is a real inconsistency a person needs to see, not a formatting quirk to ignore. On a multi-sheet assembly, sub-assembly BOMs are rolled up into the top-level count, with quantities multiplied by how many times that sub-assembly is used higher up, and the same purchased part appearing under slightly different descriptions across sheets is reconciled to one line.

What happens when a revised BOM arrives?

It is compared against the last version quoted rather than re-keyed from nothing: added lines, removed lines and quantity changes come back as a diff, so the person reviewing the revision sees exactly what moved instead of re-checking every row from scratch.

Frequently asked questions

customiser