Types of BOM: Engineering, Manufacturing and Service

Engineering, manufacturing and service BOMs describe a product for different tasks; single-level and multi-level describe how its component structure is organised. A manufacturing BOM can be multi-level, so these labels should not be treated as mutually exclusive types.

Agree the task and owner of each view before choosing software fields. Design needs to specify the product, production needs to make it, and service needs to identify the parts and instructions relevant to maintaining the installed product.

Compare BOM views through one product

Consider an illustrative electrical enclosure made from a shell, cover and fasteners. It is a teaching example, not an engineering specification. The teams may need different arrangements of the same controlled product information.

PTC's EBOM, MBOM and SBOM explanation describes these different purposes. A factory's exact fields and transformation rules depend on its product and systems. Do not assume every engineering component is separately serviceable or that every service kit is a production subassembly.

Separate purpose from product depth

A single-level BOM shows the immediate components of a parent item. A multi-level BOM also represents the contents of subassemblies. ERPNext's BOM documentation provides a reference for nested structures.

If the enclosure contains a stocked mounting assembly, its immediate BOM may list that assembly as one item. Expanding the assembly exposes the bracket and fastener requirements beneath it. Planning must then account for usable subassembly stock before deciding how much underlying material to make or buy.

Other labels describe another dimension of the record. A configurable or variant BOM concerns permitted product options. A costed BOM concerns the cost basis applied to components and operations. Define option rules and costing assumptions explicitly rather than treating these labels as a complete design.

Keep a controlled link between views

Give each component a stable identity and preserve the revision that applied to a particular order or installed product. A renamed description is a weak substitute for a controlled relationship. Record who approves a change and how it reaches the teams using another view.

Test the software with a specific change

Bring one product with a subassembly, an approved revision and a service part to the demo. Ask how each view is represented, which relationships are maintained and what requires manual review. Introduce a change while an order is open and trace the effect on its material and instructions.

This guide does not establish that Optiwise automatically converts or synchronises EBOM, MBOM and SBOM views. Review your requirements against the proposed production configuration and document any gap. Use the BOM creation template when the immediate task is preparing component lines, quantities and units.

Questions from manufacturing teams

Can a manufacturing BOM be multi-level?

Yes. Manufacturing describes the purpose of the BOM, while multi-level describes a structure containing nested subassemblies. Both labels can apply to the same record.

Is a service BOM identical to a spare-parts list?

A service BOM may organise serviceable parts, kits and applicability for an installed product. Define the approved service task and compatible versions rather than assuming every design component is a spare.

Should engineering changes automatically update open production orders?

The change needs an approved effective rule and a decision about open work and existing stock. Preserve the earlier instruction and explicitly communicate which orders use the new revision.