iParts / iAssemblies (Inventor)
Family-table-driven configurations — one part file representing a family of variants via an embedded factory table.
🔗 Related Concepts
Deepen your understanding with these related topics:
Definition
An iPart is an .ipt with an embedded factory table. Each row defines parameter values, feature suppression, and iProperties for one member of the family. iAssemblies do the same at the assembly level. When inserted into an assembly, the user picks the member from a dialog.
Why it matters
iParts replace hundreds of nearly-identical files with one parent file containing a table. Fasteners, brackets, pulleys, gears commonly ship as iParts.
Common pitfalls
- iPart members with feature combinations that can't be modelled — open-as-member produces errors.
- Forgetting to publish iPart members to content centre — limits reuse.
- Long iPart tables (1000+ members) — slow Inventor on insert.
Table-driven part and assembly families
An iPart turns one part into a factory: an embedded table where each row is a member with its own dimensions, feature suppression, iProperties, and file name. iAssemblies do the same for assemblies, additionally controlling component inclusion. Placing an iPart prompts for the member row and generates the corresponding concrete file.
Authoring clean factories
Rename parameters before building the table so columns are legible, mark key columns as keys to drive the placement dialog, and keep member counts sane — very large tables are better served by Content Center or iLogic. Use custom (versus standard) member behaviour when each placement must be an independently-numbered file.
References
Primary and vendor documentation used while writing this page (external links, not republished):
Inventor Ecosystem Context
This concept is a core structural element of the Inventor drafting and engineering environment developed by Autodesk. Autodesk's Windows-native parametric MCAD — strong on large mechanical assemblies, sheet metal, frame generator, and integration with Autodesk Vault and Revit.
Relevant Inventor FAQs
❓ What's the difference between Inventor and Fusion 360?
Inventor is Windows-only desktop, file-based, deep MCAD with Vault integration. Fusion 360 is cross-platform (Win/Mac), cloud-data, broader scope (CAM, electronics, generative design), simpler assemblies. Inventor for established mechanical engineering teams; Fusion 360 for makers, small teams, integrated CAM workflows.
❓ Can Inventor open SOLIDWORKS files?
Indirectly. Inventor doesn't natively read .sldprt/.sldasm; export from SOLIDWORKS to STEP or Parasolid, then open in Inventor. Features import as static geometry without parametric history.
❓ What's in the Product Design & Manufacturing Collection?
Inventor, AutoCAD, AutoCAD Mechanical, Inventor Nastran (FEA), Inventor Tolerance Analysis, Factory Design Utilities, Inventor CAM, Vault Basic, ReCap Pro, and Fusion 360 (selected modules). Most production Inventor users are on PDMC rather than standalone Inventor.
⚡ Concept Self-Test
Test your understanding of this concept to lock in your memory. Completing this quiz will automatically sync to your career learning progress.
🎓 Recommended Practice Lessons
Step-by-step practical exercises and certification-aligned paths chosen by our editors to master this concept:
Autodesk Inventor 2025 | Basics For Beginners | Step-by-Step
🌳 Semantic Crossroads & Navigation Pathways
Trunk-Branch-Leaf ModelExplore cross-referenced learning lanes. Connect this specific method back to macro CAD coordinate foundations, parent software environments, and sibling parameters in our shared taxonomy map.
Global Foundations
Core glossary, interactive graph, and domain-wide concept index.
Ecosystem Integration
Parent design environments and platforms implementing this method natively.
Active Context & Neighbors
Current active term and close sibling concepts: