Understand Bill of Materials (BOM) Types

Bill of Materials (BOM) form the bedrock of Deliverables Management, establishing the structure of materials in an understood hierarchy. Deliverables Management utilizes different types of BOMs, defined here:

• EBOM – Engineering Bill of Material (available in Engineering and E3D)

  • Focuses on design intent to describe how the final product should be built in alignment with technical drawings or CAD files. EBOMs are essential for ensuring that design parameters are followed throughout manufacturing. EBOMs represent the design database in Dabacon.

  • Innovator user cannot delete these BOM structures

  • Hierarchy information derives from: EBOM\Site\Zone

• FBOM – Fabrication Bill of Materials (only available for the marine environment in E3D, otherwise it is an MBOM)

  • Outlines all components, sub-assemblies, and raw materials needed for manufacturing. It offers extra information such as production instructions, machine settings, and tool requirements. FBOMs are essential for converting the concept into a workable plan for production.

  • Represents the Manufacturing database in Dabacon.

  • Both EBOM and FBOM are BOM structures created in the Unified Engineering and replicated in Innovator

  • Innovator user cannot delete these BOM structures

  • Hierarchy information derives from: FBOM\MANPKG\XXXX

• MBOM – Manufacture Bill of Materials (available in E3D)

  • This is a detailed blueprint that lists all components, sub-assemblies, raw materials, and processes required to build a shippable product. The MBOM is production-centric, providing assembly, inventory management, and procurement instructions.

  • Innovator user cannot delete these BOM structures

  • Hierarchy information derives from: MBOM\WKPKWL\CWAREA\WKPACK

• PBOM – Purpose specific BOM (available in Innovator)

  • PBOM provides the ability to achieve a goal. Example purposes include: maximum weight collection, same sizes like the same width of pipe, same material, and more.

  • Innovator user can delete the PBOM

  • Changes (on hierarchy) done in the Purpose specific BOMs are not reflected in other BOMs