Manufacturing engineering sits at the crossroads. Engineering hands off, and you turn that data into something the shop floor, the laser cutter, the saw and purchasing can actually work with. When something goes wrong upstream, it ends up on your desk. And usually only at the moment it really costs time: a bill of materials that does not match the assembly, a model full of leftover geometry, or a PDF with a revision number that has already gone to the supplier.
The heart of the problem is almost never poor craftsmanship. It is messy data. Getting clean data into production is exactly the link where things go wrong: between engineering's Inventor model and the production documents that hit the floor. In this article we walk through the most common downstream errors, and show how Model Cleaner, the iProperty Menu, BOM Export and Batch Publish catch them at the source: in the model, not on the purchase order.
What goes wrong when engineering delivers messy data
Nobody deliberately hands off a messy model. But under time pressure, things get left behind. A sketch that is no longer used. A suppressed feature that was once a variant. A material code typed in by hand that differs by just one character from what purchasing has in the ERP. Each one small on its own. Together they are the reason your workday is full of checking instead of preparing.
A few situations you will probably recognize:
- The bill of materials does not match the model. A part appears twice, or a quantity in the parts list has been overwritten by hand and no longer matches what is actually in the assembly. The shop floor orders too little, or far too much.
- iProperties are half filled in or inconsistent. One part has a tidy description, the other is still called "Part1". The material is sometimes in the physical properties of the model, sometimes only typed into the title block of the drawing, and the two contradict each other.
- Models are heavy and slow. Leftover surfaces, stray sketches and floating work planes make an assembly slow to open and cause the export to trip over geometry that does not belong. A DXF that suddenly contains an extra contour, a STEP the supplier does not trust.
- Production documents are assembled by hand. Someone exports a PDF, a DWG, a DXF for the laser cutter and a STEP for the supplier, one part at a time. One forgotten file or one outdated revision, and the wrong version ends up on the floor.
The common thread: an error that starts upstream gets more expensive downstream. A wrong material code takes engineering ten seconds to correct. That same error slipping through manufacturing engineering and reaching purchasing costs a wrong order, a wait on material that does not arrive, and a phone call to the supplier you would rather not have made. That is why you want to catch errors as close to the source as possible. The further an error rolls down the chain, the more it costs to undo.
Start at the source: clean models with Model Cleaner
Before you export anything at all, the model itself needs to be in order. Leftover geometry is treacherous: you do not always see it in the graphics window, but it is there in the browser and it comes along in your export. Surfaces that once served as construction geometry, sketches with no function, work planes that are no longer attached to anything: they make the model heavy and the result unpredictable.
Model Cleaner removes that leftover geometry and tidies up the browser. You notice the difference straight away in practice. A lighter model opens faster. A cleaned-up browser is readable for the next person who opens the file, who does not first have to mentally set aside ten suppressed features and nameless sketches to understand how the part is built. And an export no longer trips over geometry that does not belong. For manufacturing engineering that means fewer surprises at the moment you need a DXF for the laser cutter or a STEP for the supplier.
The beauty of it is that cleaning up does not have to wait until it lands on your desk. If engineering runs Model Cleaner before they wrap up, you receive a clean model. And if something did get left behind, you do it yourself in a few clicks, instead of manually combing through the entire browser looking for what does not belong.
One source of truth for metadata: the iProperty Menu
Material, description, item number, supplier, weight: that metadata determines whether the rest of the chain can work. The problem is that iProperties in Inventor end up scattered and inconsistently filled in. One engineer fills them in neatly, another leaves fields empty, and a third types a material code that deviates slightly from the standard. Manufacturing engineering then gets to straighten that out, part by part.
The iProperty Menu tackles this with one configurable data card per document type. Instead of hunting for the same fields across different tabs and dialogs, you get the same clear card for each document type. You see at a glance what is filled in and what is missing. And because the card is configurable, you define which fields matter: for your company, your ERP, your production. A part, an assembly and a drawing each have their own relevant fields; you no longer need to keep them in your head, they are laid out ready for you.
Why this matters so much downstream: the iProperties are the source the bill of materials and the production documents both draw from. If the material is correct in the iProperty, then it is correct in the BOM Export to Excel, then it is correct on the PDF in the title block, then it is correct on the order. Right once at the source, and it is right everywhere. Wrong once at the source, and you correct the same error in four places, and if you miss one, a wrong value runs all the way through into production.
Through the Dashboard you can take this a step further and connect the tools to your ERP and other software. Then the metadata flows not only neatly through Inventor, but also to the systems behind it, without anyone retyping item numbers and without a typo lodging itself between the model and the ERP.
One data card per document type, metadata that is correct everywhere and a model that goes into production clean: see for yourself how much follow-up work that saves.
Try 30 days freeBills of materials that are correct: BOM Export to a fixed template
The bill of materials is the document where most downstream errors come together. Purchasing orders from it, the shop floor works with it, estimating calculates with it. If the bill of materials does not come one-to-one out of the model but has been updated by hand along the way, that is exactly where you introduce the risk.
BOM Export pulls the bill of materials straight out of Inventor into Excel, in a fixed template. That "fixed template" is more important than it sounds. It means every bill of materials looks the same: the same columns, the same order, the same fields. Purchasing does not have to search for where the item number is, because it is always in the same place. Estimating can rely on the quantities coming from the model and not from someone's memory.
The difference from copying by hand is fundamental. With retyping or cut-and-paste, errors creep in: a line skipped, a quantity copied wrong, an old version reused because nobody remembered which one was current. An export from the model takes what is actually in the assembly. If engineering changes something, you export again and you have the current bill of materials, no detective work to figure out which version is now the right one.
Run the numbers with an example. Suppose you have ten assemblies per project, and that neatly reworking a manual bill of materials costs you on average a quarter of an hour each. That is two and a half hours per project, purely on getting bills of materials right. With an export to a fixed template, the vast majority of that work falls away. This is an assumption, not a measurement, but you will recognize the order of magnitude, and it adds up with every project.
From clean model to production: Batch Publish
Once the model is clean, the metadata is correct and the bill of materials comes from the model, the last step is delivering the production documents. This is traditionally the moment where handwork and haste come together: a PDF, a DWG, a DXF for the laser cutter, a STEP for the supplier, one part at a time. Lots of clicks, lots of chance of a forgotten file or an outdated revision tagging along anyway.
Batch Publish produces all production documents in one step: PDF, DWG, DXF and STEP at the same time, and it works together with Vault. The proof is in the numbers we are happy to put on the table: 1 click instead of 12 steps, and 48 PDFs in 6 seconds. For manufacturing engineering that means not just time savings, but above all reliability. One action delivers a complete, consistent set of documents, no hand-assembled folder where half of it lags a revision behind and you have to work out afterward what is actually in it.
Companies like Little Giant Europe, Van Egten, Banzo and Mannen van Staal work with Thundercad to make exactly this step predictable: publish once, and the whole set is ready.
The chain in one overview
Four tools, four moments in the chain. Here is how each step intervenes on an error that would otherwise only surface downstream:
| Step | Tool | Error you prevent |
|---|---|---|
| Clean model | Model Cleaner | Slow assemblies and exports that trip over leftover geometry |
| Correct metadata | iProperty Menu | Empty or inconsistent iProperties that flow downstream into BOM, PDF and ERP |
| Correct bill of materials | BOM Export | Quantities and item numbers that deviate from the model |
| Complete document set | Batch Publish | Forgotten files and outdated revisions on the floor |
It is no coincidence that the order from top to bottom is also the order in your workflow. Exporting a bill of materials from a model with wrong iProperties gives you a tidy layout with wrong content. Publishing before you have cleaned up takes the mess along into production. The gain arises precisely because each step rests on a clean previous step.
Make clean data an agreement, not a coincidence
The biggest gain is not in any single tool, but in establishing a way of working where clean data is the standard instead of the exception. Agree on what "handing off" means: a cleaned-up model, a filled-in data card, a bill of materials that comes from the model. The moment that is the norm, your role shifts from checking-and-correcting to actually preparing.
That is the difference clean data into production makes. Not spectacular, but structural: fewer phone calls, fewer wrong orders, fewer versions getting mixed up. And a workday that is about the work itself, not about straightening out someone else's haste. If you want to go deeper into the individual parts, take a look in the knowledge base or see what else Thundercad automates in Inventor.
Frequently asked questions
Who should run Model Cleaner: engineering or manufacturing engineering?
The best place is at the source: if engineering runs Model Cleaner before they wrap up, you receive a clean model and have nothing left to tidy up. But you can also do it yourself if something did get left behind. It takes a few clicks instead of combing through the browser by hand. In practice an agreement works best: cleaning up is part of "done".
Why is a fixed template for the bill of materials so important?
Because the people after you, purchasing, estimating, the shop floor, can rely on everything always being in the same place. No searching for where the item number is, no doubt about the column order. BOM Export pulls the bill of materials straight out of Inventor into Excel in that fixed template, so the content comes from the model and the form is the same every time.
What do I need to use Thundercad?
Windows 10 or 11, Autodesk Inventor 2025 or newer and an active Autodesk account. Thundercad works together with Autodesk Vault and can be connected to your ERP through the Dashboard. You can try it free for 30 days without a credit card. After that the price is EUR 30 per user per month, or EUR 300 per user per year (two months free), excluding VAT.