Structural Modeling Best Practices: Common Mistakes That Compound Through a Project
November 7, 2026
No Comments
Autodesk Inventor and Vault are sold as separate products, but for manufacturing design teams, they’re really meant to be understood as one connected system — Inventor builds the model and assembly structure, and Vault is what actually keeps that structure’s data trustworthy as more people and more design changes touch it over time. This matters more in mechanical and manufacturing design than in almost any other CAD discipline, because a manufacturing assembly’s complexity — hundreds of parts, each with real purchasing, fabrication, and assembly implications — makes “just use a shared folder” fail faster and more expensively than it does in simpler design work.
A single Inventor assembly for even a moderately complex manufactured product can reference dozens or hundreds of individual part files, each potentially reused across multiple assemblies, each with its own revision history, and each eventually needing to map to a real purchasing or fabrication line item. A generic shared folder can technically hold all of these files, but it has no concept of “this part is used in three different assemblies” or “this component is purchased, not fabricated, so don’t count it twice in the BOM.” That structural blindness is exactly where manufacturing teams get burned — not by losing files, but by the BOM derived from those files being quietly wrong.
Inside an Inventor assembly, each component carries a status setting that Vault uses to decide how that component behaves in the item BOM:
| Component Status | What It Means | BOM Treatment |
|---|---|---|
| Normal | A standard, fabricated or assembled part | Appears as its own BOM line item |
| Purchased | Bought as a finished component, not fabricated in-house | Counted as a single BOM line item regardless of whether it’s a part or sub-assembly |
| Phantom | A component used for modeling/positioning purposes only, not a real discrete manufactured item | Excluded from the item BOM entirely |
| Reference | Shown for visual/positioning reference, not actually part of the build | Excluded from the item BOM entirely |
| Inseparable | Treated as permanently joined to its parent (e.g., a welded sub-assembly) | Rolled into the parent item rather than listed separately |
Getting these statuses right at the modeling stage is what determines whether your Vault-generated BOM actually matches reality. A common, costly mistake: leaving fastener or bracket sub-assemblies marked as Normal when they should be Phantom or Inseparable, which inflates the BOM with line items that don’t correspond to anything a buyer or fabricator should be ordering or building separately.
A BOM in Vault isn’t a separate document you maintain by hand alongside your model — it’s generated directly from the assembly structure each time a file carrying a BOM is assigned an “item” inside Vault. This is the real payoff of CAD-integrated PDM over generic file management: change the assembly structure in Inventor, check it in, and the BOM reflects that structural change automatically, rather than requiring someone to manually update a spreadsheet that can silently drift out of sync with the actual design.
This automatic generation is also exactly why component status discipline matters so much. The BOM is only as accurate as the status settings feeding it — Vault isn’t guessing at what should count as a line item, it’s mechanically applying the rules your component statuses define.
For most manufacturing teams, the Vault-generated BOM isn’t the final destination — it needs to reach an ERP, MRP, or PLM system where purchasing, production planning, and costing actually happen. Autodesk’s own Vault Data APIs exist specifically to support this kind of connection, and a number of third-party tools focus specifically on automating that transfer so nobody is manually re-typing BOM data into a separate system.
It’s worth being realistic about what these integrations typically offer: several well-known connector tools handle a one-way transfer — design and BOM data moving from Inventor/Vault into the ERP system, not bidirectional synchronization back into the CAD environment. If your team needs genuine two-way synchronization between engineering and ERP, that’s a more involved integration conversation worth having directly with whoever administers your ERP system, rather than assuming any connector handles it by default.
Autodesk’s own answer for teams that want a more integrated PLM layer specifically is Vault PLM, which pairs Vault Professional with Fusion Manage and includes a connector intended to automate syncing items and BOMs between the two. Whether that’s the right fit over a lighter third-party ERP connector depends heavily on your existing ERP investment and how deeply you want engineering and business systems tied together — this is genuinely a case where the right answer varies by company, not a one-size-fits-all recommendation.
Once a BOM accurately reflects your assembly structure and component statuses, it becomes the practical basis for costing — rolling up purchased component prices, estimated fabrication costs, and quantities into a real per-unit or per-project cost figure. This is often where ERP integration earns its keep most visibly for a manufacturing business: a BOM that’s wrong because of sloppy component status settings doesn’t just cause a production headache, it produces a wrong cost estimate that can genuinely affect a quote or a margin decision. Getting the BOM fundamentals right earlier in this guide isn’t purely an engineering-tidiness concern — it has a direct line to commercial decisions made from that same data downstream.
One underused feature worth knowing about: Vault includes a thin web client that lets people view design data, BOMs, and change orders using only a browser and their Vault login — no Inventor seat required. This matters more than it might sound for manufacturing teams specifically, because purchasing staff, production planners, and managers who need to see a current BOM or check a change order’s status usually shouldn’t need a full CAD license just to look at data that Inventor users are already maintaining.
Even with a correctly generated BOM and correctly set component statuses, one practical gap remains common: making sure the revision shown on a drawing’s title block or revision table actually matches the item revision Vault is tracking internally. Because drawings and models are separate files that happen to reference each other, a disciplined check-in habit on the model doesn’t automatically guarantee the drawing’s visible revision table was updated to match. Building a habit of confirming drawing revision callouts against the actual item revision at each release — rather than assuming they’re automatically synchronized — closes a gap that otherwise shows up as exactly the kind of “the drawing says B but the model is on C” confusion PDM is meant to prevent in the first place.
Many manufacturing organizations eventually end up maintaining two related but distinct views of the same product: an Engineering BOM (EBOM), which reflects how the designer actually structured the assembly in Inventor, and a Manufacturing BOM (MBOM), which reflects how the product is actually built and sequenced on the shop floor — sometimes with different groupings, added process steps like sub-assembly stages, or consumables that never appear in the design model at all (adhesives, paint, packaging). Vault’s item BOM, generated directly from your Inventor structure, is fundamentally an EBOM. Whether you need a separate, explicitly maintained MBOM — and whether that lives inside Vault/ERP integration or as a distinct process in your ERP system — depends on how different your actual build sequence is from your design structure. Smaller manufacturing operations with a build process that closely mirrors the design structure can often get by treating the EBOM as close enough to the MBOM; more complex production environments usually can’t, and conflating the two without realizing it is a quiet but real source of production-planning confusion.
Designers under deadline pressure often leave every component on its default status rather than deliberately setting Purchased, Phantom, or Inseparable where appropriate. The BOM that comes out the other end then needs manual cleanup every time, which defeats much of the automation’s purpose.
As covered above, several common integration tools are explicitly one-way. Teams that assume changes in the ERP system will flow back into Vault automatically, without confirming that specific capability, can end up with engineering and business data quietly diverging.
If non-CAD staff still rely on someone exporting a spreadsheet for them manually instead of using Vault’s own web client for current BOM data, you’re reintroducing exactly the kind of manual, error-prone step that CAD-integrated PDM is meant to eliminate.
Manufacturing assemblies are typically full of standard hardware — bolts, nuts, washers, bearings — pulled from Inventor’s content center rather than modeled from scratch. These standard parts interact with the BOM slightly differently than custom-designed components. Because they’re usually purchased rather than fabricated, teams generally set them to Purchased status, and because the same exact fastener often appears dozens of times across a single assembly, getting the quantity rollup right in the BOM matters more here than almost anywhere else — a BOM that lists each identical bolt as a separate line instead of correctly rolling up the quantity makes purchasing and costing meaningfully harder to work with. Confirming your content center parts carry consistent, correct status settings before an assembly goes to item assignment is a worthwhile habit, since inconsistent fastener handling is a common, avoidable source of BOM cleanup work.
Real manufacturing products are rarely a single flat list of parts — they’re typically assemblies of sub-assemblies, sometimes several levels deep. Vault’s item BOM can represent this nested structure, which matters because a flat BOM (every single part listed at one level, regardless of which sub-assembly it belongs to) and an indented, multi-level BOM (reflecting the actual build structure) serve genuinely different audiences. Purchasing teams often want a flattened view to see total part quantities across the whole product; production planners often want the indented, multi-level view that matches how the product actually gets built in stages. Vault’s BOM views can typically support both, but it’s worth confirming with your own vault administrator which view different teams are actually looking at day to day, since confusion between the two is a realistic source of miscommunication between engineering, purchasing, and the shop floor.
Component status rules, BOM generation behavior, and ERP connection points are the kind of detail that’s genuinely hard to get right from documentation alone — they only really click once you’ve set them up on a real assembly and watched the BOM respond (or fail to respond correctly) to your choices. Orbit Training Centre Dubai’s Autodesk Vault / PLM course works through exactly this: real Inventor assemblies, real component status decisions, and the practical BOM and data-management workflow manufacturing teams actually need, rather than treating Vault as an abstract concept disconnected from your CAD work.
They remain part of the Inventor assembly model itself for geometry and positioning purposes, but Autodesk’s documentation is specific that they don’t appear in Vault Professional’s item BOM once an assembly is assigned an item — their role is purely structural/visual inside the CAD file, not as a counted BOM line.
Both appear as BOM line items, but a Purchased component is always counted as a single line regardless of whether it’s technically a simple part or a more complex sub-assembly — because from a procurement standpoint, you’re buying it as one finished unit, not building or costing its internal structure separately.
Yes — Vault’s Data APIs are built to support external connections generally, and a number of third-party tools specifically target common ERP/MRP systems. The right choice depends on which ERP system you already run and whether you need one-way or two-way data flow, which is worth confirming directly with the specific connector vendor rather than assuming.
No. Plain file-level check-in/check-out works without item assignment. Items specifically come into play when you need Vault’s BOM, engineering change order, and more structured lifecycle management features — which is typically the case for real manufacturing assemblies, but not necessarily for every supporting file in a project.
No. Vault PLM is a separate bundle that pairs Vault Professional with Autodesk’s Fusion Manage product specifically for deeper PLM-style item and BOM synchronization. Vault Professional alone already includes solid BOM and change management capability for many manufacturing teams — whether you need the additional PLM layer depends on how much broader product-lifecycle functionality your team genuinely requires beyond engineering data management.