The bill of materials is usually a second draft of a decision the engineer already made
A Tekla model already knows every part, every profile, every quantity, the structural engineer made those decisions once, inside the model. What happens next, at most steel fabricators, is someone re-types that same information into a spreadsheet or an MES so the shop floor has a bill of materials to work from. Every re-entry is a chance for a typo, a missed revision, or a part count that doesn't match what the model actually says by the time it reaches the shop floor. If you already use PowerFab, we compared the two in SteelFlow MES vs Tekla PowerFab.
Where the gap actually shows up
- Revisions lag. The engineer updates the model; the spreadsheet BOM doesn't get the memo until someone remembers to re-export and re-type it.
- Transcription errors compound. A profile size or quantity typo doesn't get caught until a part doesn't fit or material runs short mid-production.
- There's no single source of truth, when the model and the BOM disagree, nobody's sure which one is actually current without checking both by hand.
What a direct Tekla → BOM pipeline changes
SteelFlow's Tekla plugin pulls the model straight into a structured bill of materials, no manual re-entry step exists to introduce drift in the first place. A model revision produces an updated BOM as a mechanical consequence of updating the model, not a separate task someone has to remember to do.
Why this matters more than it sounds
This isn't a convenience feature, it removes an entire category of error at the source instead of catching it downstream with better inspection. The BOM production teams work from and the model engineers actually designed stop being two documents that can silently disagree.
Frequently asked questions
Why is retyping a Tekla BOM a problem for steel fabricators?
Every manual re-entry is a chance for a typo, a missed revision or a part count that no longer matches the model. Revisions lag because the spreadsheet only updates when someone re-exports and retypes it, errors surface when a part doesn't fit or material runs short, and nobody is sure which document is current.
How does a direct Tekla to BOM import work in SteelFlow MES?
SteelFlow's Tekla plugin pulls the model straight into a structured bill of materials, so there is no manual re-entry step at all. When the engineer revises the model, an updated BOM follows as a consequence of that change, instead of being a separate task someone has to remember to do.
Why does a model-linked BOM matter beyond saving time?
It removes a whole category of error at the source instead of catching it later with more inspection. The BOM the shop works from and the model the engineers designed stop being two documents that can silently disagree, and it becomes the starting point for part-level traceability and the data a steel Digital Product Passport is expected to carry.
A BOM that stays tied to the model is also the starting point for the data a Digital Product Passport for steel is expected to carry.
Once the BOM is in, the next step is putting the marks on the steel itself; we covered that in piece-mark barcode tracking from cutting to dispatch.
If your shop already runs an ERP and you are wondering where a model-linked BOM fits, we compared the two in what an MES adds when you already have an ERP.
