3
views, one BOM
Three bills of materials pretending to be one
« Aligning the engineering and production BOMs forces pointless drawing updates that overload the engineering office. »One structure, three views. Each discipline reads what it needs.
Use case · Engineering · Project management
Keep one BOM from design to production, with mass and cost computed.
On the V-model · Left branch: design to implementationKoddex holds one engineering BOM per series or customer, linked to your CAD and ERP rather than copied from them. Revisions, variants and quantities sit in one tree, and mass and cost totals are computed automatically.
15 min
to assemble a complex product structure, instead of 2 to 3 days in Excel
1 day
for a change impact analysis, instead of 2 weeks of meetings and spreadsheets
Measured at our reference customer after a year in use. Your first scope measures them on your own programme.
Watch it in 60 seconds
BOM management · Koddex
01
Three BOMs that never stay in sync
3
sites
Three sites, three continents, one machine
« If it is complicated, people simply do not do it. »One workspace the three sites write into, not three that export.
0
tools
A hundred and twenty engineers, no technical data tool
« We have no technical data management tool at all. Searching and proving compliance are both hard. »Structure first, then the search works because the data has shape.
One BOM from design to the line
Engineering, manufacturing and as-delivered views read the same items, so a revision made in design reaches the line without being re-entered.
Totals you no longer rebuild
Mass, cost and margins are computed on the BOM tree, so changing a part updates every assembly and variant that uses it.
Where-used in one click
Every part knows the assemblies, variants and customers that use it, so a supplier change is answered before the meeting, not during it.
02
A BOM the whole team reads from
01
Totals computed from the components
Quantities, unit mass and unit cost roll up from each component to the top assembly, so there is no spreadsheet copy of the BOM to keep in sync.
02
Change one part, every variant recomputes
Variants share their common parts, so a change to one part updates every variant that uses it and shows the difference.
03
Each system keeps the data it masters
CAD keeps the geometry and the ERP keeps price and stock, while Koddex links both to the BOM instead of importing copies that go out of date.
03
Assign the task to the AI mechanical engineer.
It picks up the task in Koddex, works on your product data, comments on what it found and hands you the result to approve.
AI mechanical engineer
▸Check the gripper assembly against its mass budget after rev C.
- Reads the parts, requirements and tests
- Follows the links, within your rights
- Proposes it on a branch for you to sign
2 sub-assemblies exceed their budget, by 40 g and 115 g. The 115 g comes from the supplier B bracket, and two lighter alternatives are already qualified in variant V2. I drafted the change request on a branch for your review.
Every agent action logged · scoped to the user's permissions
Discover more use cases
Frequently asked questions
See all questionsAny attribute reachable through the links: values on the same item, values on children or parents, and values on items linked through a relation. That is what makes recursive roll-ups across a BOM possible.
No. A spreadsheet formula points at a cell address. A Computed formula points at a typed attribute on a typed entity, so moving or renaming things never silently breaks the calculation.
No. Koddex sits with your CAD, PLM and ERP, not instead of them. It links what is already there on one graph and computes the effects of a change, and it connects to PLM, QMS, ERP and MES platforms through its API.
The first use case is typically live within 48 hours, and full onboarding takes about three weeks, led by a dedicated Customer Success Manager.
Exclusively in the European Union, in the AWS Europe (Ireland) region. No customer data leaves the European Economic Area without your prior written agreement.
A 20-min demo. Your first use case live in 1 month.
Bring one assembly and its variants. In the demo, we change a part in a BOM like yours and show the effect on every variant.
0-5 min
you describe the product and the change
5-15 min
we show the use case in Koddex on a product like yours
15-20 min
you leave with a plan for your first use case, live within a month