EBOM, MBOM and SBOM in PLM: How engineering, production and service connect

Many people say “BOM” as though it were a single thing. In practice, you often need multiple BOMs, because engineering, production and service view the product through different lenses. If these structures are not connected, you get the classic situation: engineering means one thing, production builds something else, and service has a third picture.

PLM is where these structures can be linked and managed as related sources of truth, rather than competing versions.

EBOM: Engineering BOM (what the product is)

The EBOM is typically closely linked to CAD and represents the product design:

• functional modules
• technical specifications
• material choices and requirements
• design intent

Strength: Accurate technical definition and revision control.

Weakness (on its own): It is not always optimal for production or purchasing.

MBOM: Manufacturing BOM (how the product is built)

The MBOM covers assembly, production steps and logistics:

• alternative breakdown into subassemblies
• kits/kitting
• consumables, adhesives, fasteners, process items
• substitute parts and production alternatives

Strength: Optimal for production, planning and MES (Manufacturing Execution System).

Weakness (if disconnected): Engineering changes are captured late → rework.

SBOM: Service BOM (how the product is maintained)

Service often needs a structure that:

• matches replaceable units and repair logic
• includes spare parts, kits and field modifications
• accounts for the installed base and configurations at customer sites

Strength: Enables faster and more accurate service/aftermarket operations.

Weakness (if disconnected): Incorrect parts are sent, incorrect instructions are used.

Why PLM is the “glue” between BOMs

What matters most is not that everyone sees the same structure, but that:

1. the relationships are controlled, and

2. changes propagate in a controlled manner.

In PLM, you can:

• map EBOM → MBOM (which lines/components correspond)
• manage deviations (production needs an alternative) through approval workflows
• link documentation and instructions to the correct BOM variant
• manage variants and configurations so service knows what is installed

Example: When the “same product” is not the same product

Imagine a pump:

• Engineering has modules for performance and material
• Production creates kits for efficient assembly
• Service sells spare parts kits for typical failure modes

If engineering changes an O-ring:

• The EBOM changes (new part/revision)
• The MBOM must be updated (kitting and process instructions)
• The SBOM must be updated (spare parts kits and documentation)

Without a PLM link, these become three separate tasks that often do not happen at the same time.

How to model the relationship

1) Establish the EBOM as the design master

The EBOM is often the source, but that does not mean the MBOM and SBOM are copies. They are derived structures with their own logic.

2) Use “transformation” and deviations as controlled objects

When production needs an alternative (supplier change, process choice), it should be recorded as:

• an approved substitute
• a production deviation linked to an effectivity date/serial number range
• or a formal change

3) Introduce effectivity rules

To avoid “everything always applies”, use:

• date/serial number/order as the effectivity logic

Production and service then know which configurations apply.

Summary

EBOM, MBOM and SBOM are three necessary perspectives. PLM makes them manageable, traceable and connected, so changes are coordinated and correct throughout the lifecycle.

Next step: Map one product line: what differences exist between the EBOM, MBOM and SBOM today, and where do errors/waiting times occur? This quickly provides a clear map of improvement opportunities.