コンテンツへスキップ

What Is a BOM? E-BOM, M-BOM, Sales BOM and Service BOM Explained

The bill of materials (BOM) sits at the center of a manufacturer’s core data. Yet when people say “the BOM,” engineering, manufacturing, sales and service are each looking at the same product from a completely different angle. This introductory guide walks through five BOM types — D-BOM (design BOM), E-BOM (engineering BOM), M-BOM (manufacturing BOM), sales BOM and service BOM — and then covers variant configuration for products whose structure changes by order, and the “two-tier M-BOM model” that works well for companies producing at multiple sites.

What you will learn

  • The basic structure of a BOM, and why each function ends up needing its own
  • How D-BOM, E-BOM, M-BOM, sales BOM and service BOM differ
  • What actually happens when an E-BOM is turned into an M-BOM
  • Managing the M-BOM in two tiers: a common M-BOM plus site-specific M-BOMs
  • How variant configuration (the 150% BOM) relates to each BOM
  • Where to start with BOM governance, and the most common mistakes

1. What a BOM is

A BOM describes which items — and how many of each — make up a given item, whether that is a finished product, a unit or a part. The simplest way to picture it is as parent–child relationships with quantities, stacked into a hierarchy.

Element Meaning Example
Parent item The item being built Industrial pump (finished product)
Child item An item that goes into the parent Motor unit, casing, bolts
Quantity How many children per one parent 8 bolts
Level Depth in the hierarchy Product → unit → part → raw material
Validity / change number When the structure is effective from and to From June 1, the bolt switches to a new part number after an engineering change

A BOM never stands alone; it always pairs with the item (material) master. The item master says what an item is — description, unit, procurement type, cost — while the BOM says how items connect. If the item numbering scheme is inconsistent, no amount of care in building BOMs will make them connect across departments. That is why BOM projects so often turn into item-numbering projects.

2. Why there is more than one BOM

For the same product, each function needs to know something different:

  • Engineering wants to know which functions are realized by which parts
  • Manufacturing wants to know what is assembled, where, and in what order
  • Sales wants to know what is sold to the customer, and in which combinations
  • Service wants to know what is replaced or repaired at the customer site

Trying to serve all of these with a single BOM produces data that is awkward for everyone. The basic approach is therefore to separate BOMs by purpose — and then connect them correctly.

3. The five BOMs

We will go through the five BOMs in the order of the product lifecycle. Terminology varies between companies and industries; this article uses the following definitions.

3-1. D-BOM (design BOM)

The D-BOM reflects the structure designers build in CAD. Because mechanical, electrical and software engineers each work in their own tools, the D-BOM normally exists separately for each design discipline.

  • It follows the CAD assembly structure and ignores manufacturing considerations
  • It contains parts still under study, including parts that have no part number yet
  • It is the designer’s working unit and changes frequently

3-2. E-BOM (engineering BOM)

The E-BOM integrates the discipline-level D-BOMs into the released technical structure of the product. It is engineering’s official answer to the question: “This product consists of these functional modules and these released part numbers.”

  • Mechanical, electrical and software are integrated into one product structure
  • Managed with released part numbers, drawing numbers and revisions
  • Updated only through approved engineering changes (ECR/ECO)
  • Typically mastered in a PLM system

Separating the D-BOM from the E-BOM keeps “the designer’s work in progress” apart from “technical information the company has released.” A simple rule — downstream manufacturing and procurement may only reference the E-BOM — prevents purchasing mistakes caused by unreleased data.

3-3. M-BOM (manufacturing BOM)

The M-BOM describes how the product is built. Even for the same product, its structure differs from the E-BOM.

Added or changed in the M-BOM (not in the E-BOM) Example
Intermediate items that match the process “Painted casing,” “pre-assembled motor unit”
Consumables needed in production Adhesive, grease, labels, packaging
Phantom items A functional grouping in design that is not stocked and is assembled directly into the next level
Procurement type / make-or-buy This unit is bought complete from a subcontractor
Link to operations Which part is consumed at which operation (tied to the routing)

Because the M-BOM drives MRP, production orders and product costing, it is generally mastered in the ERP system.

3-4. Sales BOM

The sales BOM describes the structure in terms of what is sold to the customer, and how.

  • Sets and kits (main unit + accessories + manual sold as one item)
  • Options (parts or services that can be added to the standard configuration)
  • Things sold together but not manufactured, such as software licenses and maintenance contracts

The sales BOM defines the units for order entry, shipping and billing. “What we sell” and “what we build” often do not line up — for example, finished units are built one at a time but shipped as a kit. Absorbing that gap in the sales BOM keeps the M-BOM from being distorted for commercial reasons.

3-5. Service BOM

The service BOM is the structure used to maintain and repair products after they ship.

  • Built around replaceable units — the modules swapped as a whole in the field
  • Holds service part numbers, interchangeability and substitute parts
  • Parts must keep being supplied for the service life, even after series production ends
  • May hold, for each delivered unit (serial number), the structure actually installed and its replacement history

The production structure and the service structure drift apart over time. An engineering change may switch a part in new production, but the units already shipped still contain the old part. Knowing which structure is in which delivered unit is the core of the service BOM.

3-6. The five BOMs compared

D-BOM E-BOM M-BOM Sales BOM Service BOM
Question it answers How is it being designed? What is it made of? How is it built? What do we sell? What do we replace or repair?
Main users Designers Engineering, quality Production planning, shop floor, procurement, costing Sales, order management, shipping Field service, maintenance
Structural unit CAD assembly Function / module Operation / intermediate item Sales item / set Replaceable unit
Rate of change Very high Per engineering change Engineering + manufacturing changes Per product planning cycle Continues after shipment
Typical system CAD / PDM PLM ERP ERP (sales) / CRM Service management / ERP

4. How the BOMs connect

The five BOMs are not built independently; information flows from upstream to downstream.

D-BOM → (integrate) → E-BOM → (transform) → M-BOM
E-BOM → (commercialize) → Sales BOM
E-BOM / M-BOM → (restructure for service) → Service BOM

The key point is that going from E-BOM to M-BOM is a transformation, not a copy. Intermediate items are added, phantoms are set, consumables are included, and the structure is rearranged to match the process. If nobody owns this transformation, or the rules are unclear, you see problems like these:

  • An engineering change reaches the E-BOM but not the M-BOM
  • Manufacturing edits the M-BOM on its own, and the link back to the E-BOM is lost
  • People reconcile the two by hand every time to work out which one is right

That is why the backbone of BOM management is being able to trace where each E-BOM item ended up in the M-BOM, and having a reliable path for engineering changes to flow from E-BOM to M-BOM.

5. The two-tier M-BOM model (common M-BOM + site-specific M-BOMs)

For companies with multiple plants at home and abroad building the same product, how the M-BOM is held becomes a major issue.

5-1. What happens when each site builds its own M-BOM

If each plant receives the E-BOM and builds its own M-BOM, things work at first. Each plant has different equipment, processes and suppliers, so building an M-BOM that suits the site is natural. Over time, though, the following problems surface:

  • Every engineering change has to be applied separately at every plant, leading to missed or late updates
  • Nobody can see how far the plants’ structures are the same and where they differ
  • Each new site starts its M-BOM from scratch
  • Headquarters cannot compare or roll up cost and requirements across sites, because the structural assumptions are not aligned

5-2. The idea behind the two tiers

One approach is to split the M-BOM into two tiers:

Tier What it holds Owner
Upper: common M-BOM (master M-BOM, global M-BOM) The standard manufacturing structure that does not change no matter where the product is built. The mapping to the E-BOM is done here, once. Standard intermediate items are also defined here. Corporate manufacturing engineering / BOM management
Lower: site-specific M-BOM Only the differences specific to that site: how operations are split, make-or-buy differences, substitution with locally sourced parts, alternates, site-specific packaging. Each plant’s manufacturing engineering

The key is that a site-specific M-BOM does not copy the common M-BOM and rewrite it; it references the common M-BOM and holds only the differences.

5-3. What the two tiers buy you

  • Engineering changes are applied in one place. E-BOM changes go into the common M-BOM first and are then rolled out to each site; a site only checks whether its own differences are affected
  • Differences between sites become visible. Because they are held explicitly, you can explain why one plant is different
  • New sites ramp up faster. Start from the common M-BOM and define only that site’s differences
  • Company-wide comparison is easier. With the common part aligned, cost and labor differences between sites can be analyzed as structural differences

5-4. Decisions to make up front

  • How much is common. Make the common tier too thick and sites lose flexibility; too thin and the two tiers are pointless. A rule of thumb: anything affecting quality or performance is common; anything about how it is built is site-level
  • Types and granularity of differences. Define in advance which kinds of difference a site may hold — substitution, addition, deletion, quantity change
  • Authority. Sites must not edit the common M-BOM directly. Changes to the common part go to headquarters as change requests
  • Approval and rollout flow. Engineering change in the E-BOM → update of the common M-BOM → impact check at each site → cut-over on an aligned effective date, with a named owner for each step

5-5. How it looks in systems

The two-tier model is often realized as a division of roles between PLM and ERP — for example, the common M-BOM is held in PLM, and M-BOMs with site-specific differences applied are passed to each plant’s ERP. In SAP S/4HANA, a BOM can be created without a plant and then allocated to several plants, or each plant can hold its own BOM; how the common and site-specific parts are represented has to be designed together with the PLM side. Which approach fits depends on the number of sites, how much they differ, and how often engineering changes occur.

6. Variant configuration and the BOM

6-1. The combinatorial explosion

For products whose structure depends on the customer’s order (configure-to-order, assemble-to-order and so on), building a BOM for every combination of options quickly becomes unmanageable. Three motor ratings × two materials × four control panels × with or without accessories already gives 48 combinations. Real products often reach thousands or tens of thousands.

6-2. The 150% BOM (super BOM)

The answer is to hold one BOM containing every part that could be selected, and to pull out only the parts needed for the specification chosen at order time. Because it contains every option — more than the 100% actually used — it is called a “150% BOM” or “super BOM.”

Element Role Example
Characteristic What the customer chooses Motor rating, material, control panel type
Characteristic value The available choices 5.5 kW / 7.5 kW / 11 kW
Constraint Rule excluding invalid combinations The 11 kW motor is only available in stainless steel
Selection condition Rule deciding which parts to take from the BOM If rating = 7.5 kW, use motor part B
Calculation rule Derives quantities or dimensions from the specification Pipe length = installation dimension − 200 mm

6-3. Which BOM it acts on

Variant configuration spans several BOMs:

  • On the sales side, it controls which combinations a customer may choose and which must not be sold — the specification check at quotation and order entry
  • On the M-BOM side, it pulls the parts needed to build the chosen specification and feeds MRP and production orders
  • On the E-BOM side, it presupposes that the product is designed in modules. Adding variant configuration later to a product that is not modular makes the rules too complex to maintain

In SAP, this is realized with configurable materials, a super BOM, characteristics and classes, and object dependencies (constraints, selection conditions, procedures). See SAP Variant Configuration (VC): Configurable Product Management for details.

6-4. Where it tends to go wrong in operation

  • Nobody is clearly responsible for maintaining the rules, so they depend on one or two individuals
  • The BOM changed with an engineering change, but the selection conditions and constraints were not updated
  • Sales sells a combination that manufacturing cannot build, because sales-side constraints and M-BOM selection conditions have drifted apart

7. Where to start with BOM governance

A lot needs to be decided before any system goes in. As a starting point, use this order:

  1. Settle the item numbering scheme and who owns the item master. If each department uses its own part numbers, the BOMs cannot be connected
  2. Decide which system is the master for which BOM. For example: E-BOM in PLM, M-BOM in ERP, sales BOM in sales management, service BOM in service management — one master each
  3. Define the E-BOM-to-M-BOM transformation rules. How intermediate items are cut, how phantoms are used, how consumables are handled
  4. Define the engineering change flow. Change numbers, effective dates, treatment of old-part inventory, notification downstream
  5. Layer on multi-site rollout (the two-tier model) and variant configuration afterwards. Introduced before the basic flow is stable, they only add complexity

8. Common mistakes

  • Using the E-BOM directly for production. Without intermediate items and consumables, MRP and costing do not add up
  • Hand-building an M-BOM at every site. Engineering changes get missed, and differences between sites cannot be explained
  • Staying on spreadsheets. Versions, effective dates and change history cannot be traced
  • Skipping the sales BOM and bending the M-BOM for sales. Kits and accessories distort the M-BOM
  • Using the production BOM as the service BOM. The structure of shipped units is unknown, and the wrong service parts get ordered

Summary

A BOM is not “one correct parts list” but “a mechanism for correctly connecting several parts lists that serve different purposes.” Release the design with the D-BOM and E-BOM, make the E-BOM-to-M-BOM transformation explicit, and absorb commercial and service needs in the sales and service BOMs. On top of that, add the two-tier common/site-specific M-BOM if you build at multiple sites, and variant configuration if the structure changes by order.

Talk to us about BOM governance and PLM/ERP integration

For questions on E-BOM/M-BOM mapping, consolidating M-BOMs across sites, or designing variant configuration, please reach out via our contact page.