BOM management in PLM: Why a “connected BOM” beats a BOM in Excel and subsequent data entry in ERP

A BOM (Bill of Materials) is more than a list of parts. It is the product’s “DNA” – and errors in the BOM are often the starting point for incorrect purchases, production stoppages, quality nonconformances and costly changes. Yet in many companies, BOMs are still managed in spreadsheets, emails, local PDM folders – or “in the heads” of key personnel. The result is a BOM that is disconnected from CAD, documentation, changes, quality and ERP.

A connected BOM in PLM gives you a single controlled product structure with revision control, traceability and a controlled flow to ERP/MES – making changes, variants and quality part of the normal process, rather than a firefighting exercise afterwards.

What does “connected BOM” mean?

By “connected”, we mean that the BOM does not exist as a static document, but is linked to:

• CAD structures (eBOM) – links between models/drawings and BOM line items
• Documentation – specifications, certificates, data sheets, assembly instructions
• Changes (ECR/ECO/ECN) – change history at part and structure level
• Quality – NCR/CAPA/SCAR are linked to specific components and revisions
• ERP/MES – approved structures and master data flow downstream in a controlled manner

In short: the BOM becomes not just “what we think we are building”, but “what we have actually approved for manufacture”.

Typical symptoms of weak BOM management (and why it happens)

If you recognise several of these, your BOM is probably “disconnected”:

1. Different BOM versions in circulation: “I have the latest one… I think.”

2. ERP becomes the source of truth for the engineering structure (even though engineering actually owns the definition)

3. Extensive manual data entry: copying/pasting between CAD, Excel and ERP

4. Changes take too long: because the impact and affected parts are unclear

5. Quality nonconformances recur: because lessons learned and root causes are not linked to the correct revision/configuration

This often happens because the business has grown faster than its methods: what worked when you had 20 parts does not work well when you have 20,000.

What do you gain from managing your BOM in PLM?

1) A consistent product structure and better decisions

When the BOM is structured and revision-controlled, it becomes easier to answer:

• Which products are affected by a change?
• Which deliveries contain a given component?
• Which revision was current when the nonconformance occurred?

2) Faster changes with less risk

PLM lets you manage changes as a process:

• propose → assess → approve → implement → verify

Updating the BOM becomes part of the change, rather than a “task someone has to remember”.

3) Better interaction with ERP/MES

ERP excels at planning, inventory, costing and purchasing. PLM is best at product definition, documentation, revision and change management. Giving these systems clear roles and integrating them reduces duplicate work and data conflicts.

Best practice: How to succeed

Here is a robust minimum setup for BOM management in PLM:

A) Define ownership

• Engineering owns the product definition (eBOM, technical attributes, revisions)
• Supply chain/production owns planning and operational data (lead time, inventory, purchasing parameters)

B) Standardise attributes and rules

Typical BOM attributes you should standardise:

• part number, description, unit, quantity, material, mass
• “make/buy”, criticality, approved alternatives
• compliance fields (RoHS/REACH/conflict minerals) as needed

C) Establish “release” as a gate

The BOM must not flow to ERP until:

• the structure has been validated
• the required documents are included
• the revision and effectivity rules are correct

Common pitfalls

• “We put the BOM in PLM, but still make changes in ERP” → two sources of truth
• No variant management → a proliferation of copies
• BOM without document links → documentation becomes an afterthought
• Too little focus on users → the tool is perceived as “control” rather than “flow”

Summary

A connected BOM in PLM gives you control over the product structure, changes and traceability – and makes it possible to scale without losing control. You reduce errors, save time and improve collaboration between engineering, production and purchasing.

Next step: Start with one product family, build a simple BOM standard and establish a “release-to-ERP” flow. You can then expand to include variants, effectivity dates and mBOM.