BOM Intelligence
Overview
BOM Intelligence automatically detects discrepancies between the EBOM (engineering bill of materials), the MBOM (manufacturing bill of materials) and ERP data, and turns every mismatch into a concrete action. Detected differences are colour-coded on the 3D assembly, so you can visually confirm which part differs in which source, and why.
The module does not replace enterprise PLM systems such as Windchill or Teamcenter — it takes data from them (or from uploaded CSV/Excel files), runs the reconciliation and connects the result to an action.
Key Concepts
- EBOM / MBOM / ERP — three views of the same product living in three different systems: the engineering design, the production line structure, and the purchasing/cost data.
- Issue — every discrepancy found during reconciliation; managed by a state machine:
Open → Linked to Action → In Progress → Resolved → Accepted. - Domestic content ratio — the cost-weighted share of domestic contribution:
Σ(qty × unit cost × domestic%) / Σ(qty × unit cost). Each part's domestic value goes through a resolution ladder (declared ratio → domestic/imported flag → country of origin → supplier legal name), and the rung it came from is recorded. A part with no data is not counted as zero — it is excluded from the ratio, and the ratio declares its own data coverage. - Alternative part analysis — whether a part has a domestic equivalent or alternative; fed from substitute part records.
- Data Quality Gate — on every analysis run, the EBOM/MBOM/ERP data sets are automatically scored for mandatory columns, blank part numbers, revision, unit of measure and supplier quality.
Typical Workflow
- Open BOM Intelligence from the left-hand menu.
- Add PDF, Excel/CSV, Word or web link sources to the data input area — or start a quick analysis with the demo data set.
- Run the EBOM/MBOM/ERP comparison and review the resulting issue list.
- View critical discrepancies marked directly on the part in the 3D visual inspection screen.
- Assign an action for each issue, create a task, or link it to a change request (Change Management).
- Export the results as a report or audit package.
Feature Reference
- EBOM/MBOM/ERP comparison and discrepancy detection
- Colour-coded error/discrepancy display on the 3D assembly (viewer integration)
- Issue state machine and audit trail
- Action assignment, task tracking and email notification (SMTP, with a
mailto:fallback) - Domestic content tab: cost-weighted ratio, data coverage (declared/derived/unknown), uncertainty range, target simulation and a list of domestic alternative suppliers
- Column mapping card: an audit record of which heading in your uploaded file was bound to which field
- CSV and Excel (.xlsx) upload; Turkish Excel output is supported (semicolon separator, decimal comma, heading rows above the table)
- BOM Grid: BOM extraction from a file path or from the assembly tree
- Data Quality Gate: data set quality scoring and baseline comparison
- JSON/HTML/PDF report and audit package export
How to Read the Domestic Content Ratio
The calculation is based on material cost only. The base defined by the Turkish SGM Domestic Goods Communiqué is the full production cost (direct materials + direct labour + manufacturing overhead), and the ratio is certified by a chamber-appointed expert. The figure on screen is therefore a preliminary assessment; it is not a Domestic Goods Certificate ratio — this warning is shown in the interface and in the PDF report and cannot be dismissed.
To keep the figure auditable, each analysis stores: the calculation engine version, the calculation timestamp, a row-order-independent fingerprint of the input (sha256) and the column mapping report. An auditor can re-run the same file and see exactly which column fed the number.
Parts without a domestic content column are shown as — on screen, not as 0%. These parts do not enter the denominator of the ratio; instead the "data coverage" figure drops and a single aggregated "missing domestic content data" finding is produced.
Constraints / Known Limits
- Reading native CAD files directly requires a commercial SDK or conversion infrastructure; today the conversion pipeline is at simulation/placeholder level.
- An LOD (level-of-detail) and caching layer should be added for large assemblies before production use.
- The PLM/ERP connectors (Windchill, Teamcenter, ENOVIA) are at adapter-contract level; a real live connection is a separate integration project.