An Integrated BOM refers to a BOM architecture in which different BOM forms share a common core hierarchy through unified underlying data architecture design. All critical BOM data is carried on the core hierarchy, ensuring seamless data connectivity and consistency across different BOM types.

SuperBOM is a BOM organization model relative to single-product BOM. A single-product BOM is created for a specific individual product, whereas a SuperBOM organizes multiple related products (on the same platform or within the same product family) into a single BOM structure and distinguishes the usage of parts across different products through configuration conditions.

• SuperBOM aligns with platform-based and product-family development strategies. If products are developed based on platforms and families, organizing product data using a single-product BOM model contradicts this business model.
• The SuperBOM provides a concrete implementation foundation for modularization.
• The SuperBOM significantly reduces the total number of BOMs within the enterprise.
• The SuperBOM avoids the need to synchronize the same part change across multiple BOMs.

BOM flattening is a widely adopted best practice in manufacturing. Its fundamental objective is to make the BOM serve all business domains rather than a single functional domain.
A flattened BOM improves cross-domain data connectivity, accelerates change propagation, significantly reduces data redundancy in configurable SuperBOMs, and eliminates “change bubbling” issues.

The value of EarlyBOM lies in enabling early involvement of cost management, early procurement, and project management in the product development process. To support meaningful participation by these business functions, the BOM must reflect manufacturing depth — down to the supplier-level part hierarchy. If the BOM only provides system or subsystem frameworks, these functions cannot perform substantive work.

EarlyBOM and EBOM serve essentially the same business functions and stakeholders. The difference lies only in BOM maturity at different product development stages.
EarlyBOM is used in early development stages and does not require formal engineering change control. Once the product enters the engineering-controlled stage, the BOM transitions into EBOM, where all changes must be governed through formal engineering change management.
Therefore, we recommend that EarlyBOM and EBOM share the same organizational structure as two stages of the same BOM. This ensures continuity for downstream application departments.

MBOM is built based on EBOM and is created for different manufacturing plants to fully reflect process and logistics differences between plants.
MBOM management covers key manufacturing information such as process routings and workstations, as well as auxiliary materials, raw materials, assemblies, and other related data.

SBOM is built based on EBOM. SBOM management covers service parts such as dismantled assemblies, in-house spare parts, repair kits, and other service items (e.g., primer-coated parts, e-coated parts).