An mBOM translates design intent into an executable production structure
An engineering BOM organizes the parts that define the designed product. A manufacturing BOM organizes what production must make, buy, issue, assemble, inspect, package, and trace. The mBOM can add consumables, intermediates, phantom groupings, substitutes, tooling references, effectivity, plant-specific choices, and links to routings or quality plans. Some simple products use one controlled structure, but the release decision still needs explicit ownership.
| Dimension | eBOM | mBOM | Release question |
|---|---|---|---|
| Primary purpose | Represent design intent | Represent production execution | Can the approved design be built as planned? |
| Typical owner | Engineering | Manufacturing engineering or operations | Who approves each transformation? |
| Organization | Assemblies and design relationships | Make, buy, stage, consume, and assemble | Does the structure match the production method? |
| Added control | Revision and configuration | Effectivity, plant, substitutes, routing, quality | What changes when, where, and under whose approval? |
| Downstream use | CAD, PLM, design review | Planning, purchasing, MES, costing, quality | Can consumers trace the released source? |
Treat eBOM-to-mBOM as a governed translation
The structures answer different questions. Engineering may group parts by design assembly, while production may need subassemblies, bulk material, packaging, setup items, outside processing, or plant-specific supply choices. A transfer that preserves every CAD relationship can still produce a poor manufacturing plan.
For each transformed line, retain the source item and revision, the manufacturing item, quantity and unit, make-or-buy state, operation or point of use, effectivity, substitute rule, and approval. If the transformation is manual, define the comparison and signoff. If it is automated, define validation, exceptions, and rollback.
- Use controlled item identities and units across engineering and manufacturing.
- Define whether non-modeled items belong in the mBOM, routing, work instructions, or quality plan.
- Preserve effectivity by date, order, lot, serial, plant, or configuration where required.
- Record who can add substitutes and how planning and quality constraints apply.
Do not release a BOM without production evidence
A release gate should prove that the structure is complete enough for planning and execution. Check revision, quantities, units, purchased and manufactured states, lead-time ownership, routing links, tooling, outside processing, quality requirements, drawings or instructions, and configuration rules. Missing production data should stop or condition the release rather than become an invisible planner repair.
Use a representative product to walk engineering, manufacturing engineering, planning, purchasing, quality, and production through the same structure. Ask each role what it consumes, what it changes, and how it detects an upstream revision. The handoff is ready when downstream users can trace every production decision to an approved source and exception.
BOM transfer does not prove manufacturability
A successful import only proves that data crossed a boundary. It does not prove the structure reflects the routing, plant, supply strategy, effectivity, tooling, inspection, or packaging needed to build the product.
Control effectivity before changing open work
A revision can affect quotes, purchase orders, inventory, work in process, scheduled jobs, instructions, inspection plans, service parts, and shipped-product records. Define whether the change applies to all future orders, a date, a lot, a serial range, a plant, or a named order. Do not use a simple overwrite where the business needs traceable effectivity.
Classify the change and determine which owners must approve it. A documentation correction differs from a material substitution, safety change, tolerance change, or supply-driven replacement. Preserve the reason, old and new structures, impacted work, disposition, approval, and proof that downstream systems received the intended version.
| Change control | Required evidence | Stop condition |
|---|---|---|
| Revision | Approved source and comparison | Source is not released |
| Effectivity | Date, lot, serial, order, plant, or configuration | Open work impact is unknown |
| Material | Substitute and quality approval | Supply choice violates product control |
| Downstream | Orders, inventory, instructions, quality, cost | Consumers cannot identify the active version |
Evaluate CAD, PLM, and ERP integration with real exceptions
Use the actual authoring and release stack. Test a new assembly, revision, deleted component, quantity change, unit conversion, alternate, configuration, renamed item, and rejected transfer. Confirm logs, error ownership, duplicate behavior, security, and the ability to compare source and destination after correction.
Dassault Systèmes explains eBOM as design intent and mBOM as the production view. Current DELMIAWorks and 3DEXPERIENCE integration paths must be verified for the exact release, licenses, architecture, and item-governance model. An integration demonstration is useful only when it matches the intended production control.
Use a BOM release gate with named owners
The gate records revision, effectivity, substitutes, make-or-buy state, routing, tooling, quality, downstream evidence, approval, and stop conditions.
Frequently asked questions
What is a manufacturing BOM?
A manufacturing BOM is the controlled structure of items and production information required to make, buy, issue, assemble, inspect, package, and trace a product.
What is the difference between an eBOM and an mBOM?
An eBOM represents the product as designed. An mBOM translates that design into the structure and controls required for production, including manufacturing-specific items, effectivity, supply choices, and execution links.
Can the eBOM and mBOM be the same?
Yes, simple products and operating models may use one controlled structure. The organization still needs to prove that it contains the information and ownership needed by planning, production, quality, and change control.
What should be tested in a CAD-to-ERP BOM integration?
Test new items, revisions, deletes, quantity and unit changes, alternates, configurations, duplicate prevention, rejected transfers, correction, logs, permissions, and source-to-destination reconciliation.
References and method
- Dassault Systèmes: Bill of materials, eBOM and mBOM definitions and purpose
- Dassault Systèmes ENOVIA MBOM, manufacturing BOM planning context
- Dassault Systèmes DELMIAWorks, current manufacturing ERP and MES architecture
- The tables, diagrams, selection questions, and downloadable register are Morphos 3D guidance. Verify product configuration, interfaces, validation requirements, and commercial packaging for the exact release and operating environment.
Prove the design-to-production release with one real assembly
Use the release gate to expose missing owners, effectivity rules, manufacturing additions, and downstream reconciliation before selecting an integration path.