Step 1: Prepare CAD properties
Automation needs consistent data. Agree on a mandatory property set for every part: part number, description, material, unit, type (make / buy / phantom) and supplier code where relevant. Update templates and clean up existing files.
Step 2: Extract the BOM
Read the assembly structure through the CAD API, including quantities, sub-assemblies, virtual components and exclusions such as reference parts. Decide whether ERP needs a multi-level structure or a flat list.
Step 3: Map and transform
| Rule | Example |
|---|---|
| Skip items | Exclude reference and envelope parts |
| Flatten | Phantom weldments pass children to parent |
| Raw material | Sheet part → sheet material + area |
| Units | Profiles in metres, fasteners in pieces |
| Lookups | CAD material "S355" → ERP material code "RM-0355" |
Step 4: Compare with ERP
Before writing, compare the new BOM with the current ERP BOM. Show engineers a clear list of additions, deletions and quantity changes, and which items do not yet exist in ERP.
+ 100-2311 Gusset plate qty 4 (new item)
~ 100-2302 Base plate qty 1 → 2
- 900-0012 M10 hex bolt removedStep 5: Validate and write
Validate mandatory fields, then create items and BOMs through the ERP API or a supported import interface. Record ERP responses and write item numbers back to CAD if required.
Step 6: Pilot and go live
- Run in parallel with the manual process for a few weeks.
- Compare results and fix mapping rules.
- Train engineers on error messages and fixes.
- Switch off manual entry.
The comparison step is what builds trust: engineers see exactly what will change before ERP is touched.
BOM to ERP with ENGIMANDI
Read automating BOM generation and CAD to ERP integration: how it works, or see our CAD integration services.