Intelligent BOM Unified Management Solution Design

I. BOM Multi-View Concept

1.1 EBOM (Engineering BOM)

• Creator: Design Department
• Focus: Product functional design, assembly logic relationships
• Structure: Organized by function/assembly relationship
• Data Source: The starting point for all downstream BOMs

1.2 PBOM (Process BOM)

• Creator: Process Design Department
• Focus: Processing routes, assembly sequences
• Core Actions: Break down (refine EBOM rough parts) + Combine parts (group standard parts) + Supplement process information

1.3 MBOM (Manufacturing BOM)

• Creator: Production Manufacturing Department
• Focus: Shop floor execution, manufacturing sequence
• Core Actions: Reorganize by workstation + Supplement execution information (material picking/packaging, line-side storage, distribution method)

II. Implementation Architecture in SCSAI agent

2.1 Existing Data Model

Product (产品)
  └── Model (型号/变型)
        └── Part (零部件)
              ├── Part BOM (BOM关系)
              │     ├── source_id → 父件 Part
              │     ├── related_id → 子件 Part
              │     ├── quantity (数量)
              │     ├── sort_order (排序)
              │     └── reference_designator (位号)
              └── classification (区分 Component/Assembly)

2.2 Component vs Assembly

| 类型 | 说明 | BOM中的角色 | 生命周期 |

|------|------|------------|---------|

| Assembly | Consists of multiple sub-components | Parent item (has children) | Depends on all child items reaching Released |

| Component | The smallest indivisible manufacturing/procurement unit | Leaf node (no children) | Independently reaches Released |

| Phantom | Logically assembled but not physically assembled | Parent item but expanded through | No inventory, deleted in MBOM |

2.3 Multi-View Implementation Plan

#### Option A: Based on classification field (Recommended, minimal changes)

Distinguish view source in the Part's classification:

• EBOM_Assembly / EBOM_Component: Engineering view
• MBOM_Assembly / MBOM_Component: Manufacturing view
• PBOM_Assembly / PBOM_Component: Process view

The front end queries the corresponding classification's Part BOM relationships through the BOM view selector.

#### Option B: Based on Independent Relationship Types

Create three types of Relationships:

• Part BOM EBOM: Engineering BOM relationship
• Part BOM PBOM: Process BOM relationship
• Part BOM MBOM: Manufacturing BOM relationship

Each view maintains its structure independently, linked via "interchangeable part" mapping.

III. Front-End Implementation Plan

3.1 BOM View Switching

[EBOM视图] [PBOM视图] [MBOM视图] [全部视图]

3.2 Multi-Level Tree Expansion (Lazy Loading)

1. Initial load: Only load the top-level BOM list.
2. Click to expand: Load the direct child components of that node.
3. Child component expansion: Recursively load to any depth.
4. Expand/Collapse All: Control the globalExpand state.

3.3 Key Query AML

<!-- 查询 Part 的 BOM 子件（支持任意层级） -->
<AML>
  <Item type="Part BOM" action="get" 
        select="id,related_id(id,name,item_number,major_rev,state,classification,cost,weight,make_buy,unit),quantity,sort_order" 
        maxRecords="200">
    <source_id condition="eq">{partId}</source_id>
  </Item>
</AML>

<!-- 查询所有顶层 BOM（不是任何 BOM 的子件） -->
<AML>
  <Item type="Part" action="get" select="id,name,item_number,..." maxRecords="1000">
    <Relationships>
      <Item type="Part BOM" action="get" select="id">
        <source_id>
          <Item type="Part" action="get" select="id"/>
        </source_id>
      </Item>
    </Relationships>
  </Item>
</AML>

IV. Product → Model → Part Hierarchy Relationship

产品 (Product)
  ├── 型号A (Model)
  │     ├── 零部件1 (Part - Assembly)
  │     │     ├── 子零件1.1 (Part - Component)
  │     │     └── 子零件1.2 (Part - Component)
  │     └── 零部件2 (Part - Component)
  └── 型号B (Model)
        └── ...

• Product: Top-level product, manages product families.
• Model: Product variant, linked to specific Parts (via part_number).
• Part: The core entity of the BOM, forming assembly trees of any depth through Part BOM relationships.

V. Change Management (ECR/ECN)

• ECR (Engineering Change Request): Proposes a change requirement.
• ECN (Engineering Change Notice): Approves and implements the change.
• Change Propagation: Upstream EBOM changes → automatic alerts for downstream PBOM/MBOM synchronization.

VI. Reference Materials

• PTC Windchill: Product Structure Management PSE module, supports multi-view editing and rule-based auto-generation.
• Siemens Teamcenter: Variant configuration + BOM transformation rule scripts.
• SAP: Super BOM + Dependencies + Engineering Change Number controls versioning.
• SCSAI agent: The ItemType + Relationship system inherently supports multi-view.