Configuring Parametric Part Variations Using a Master Model

[sj_kohlmann]

Objective
We’re exploring a solution to efficiently configure our base models. Many of our parts come in multiple variations, sometimes exceeding 60 per part. Each model is driven by several parameters that define these variations.

All part and assembly files are fully parametric and modeled from the origin using work geometry. Adjusting parameters does not cause conflicts or break the models.

What We’re Looking For
Our goal is to maintain a single master part file ("mother model") and generate all 60+ variations into a library, similar to how Autodesk’s Content Center operates. This approach allows us to manage revisions centrally and avoid duplicating effort across multiple files.

Our Question
What would be your recommended approach to set this up?
Can this be achieved using iLogic, iPart, or iAssembly? Or would you suggest a third-party configurator like DriveWorks (for SOLIDWORKS)?

Important constraints:

• We want to avoid file replication or manual copying.
• Variants should be generated and stored in a reusable library folder.

[johnsonshiue]

Hi! I believe you want to use Inventor Model States (all wrapped in one file) or iPart/iAssembly (one factory file and member files).

For the former, after you authorize the Model State members, you will need to elaborate the members manually or programmatically so that the members persist.

For the latter, you will need to use Generate Files command to generate each member files individually.

Many thanks!

[sj_kohlmann]

Model states are in theory the best way (I think). But model states causes performance issues as our models are too large.
I try to understand the difference with iParts as they generate a unique part model for each configuration. Do you know if these files can be saved to a library and re-used?

"you will need to use Generate Files command to generate each member" - does this stay associative after generating each model state individually? 

Secondly, do you have an advise on 3rd party configurators?

[johnsonshiue]

Hi! Yes, iPart and iAssembly member files can be generated and stored in a library folder for reuse purpose. That is the exact design intent they were built initially.

Another option is to leverage Inventor iLogic rule. You may configure the model however you like. When you are done configuring, you may use iLogic Design Copy to spawn the dataset. I am not aware of any 3rd party configurator for Inventor.

Many thanks!

[IgorMir]

iPart children can be generated in bulk.

---

@johnsonshiue wrote:

For the latter, you will need to use Generate Files command to generate each member files individually.

Many thanks!

---

[SharkDesign]

Is this method of any use to you?

https://youtu.be/8qu7jwK9M6k?si=nr20QKxlkpi1jXLI

[sj_kohlmann]

Thank you for the link, this can be very usefull.
We have thought about it but with 15K components with 1000 unique parts this will be too tricky. I thought about having iLogic push variables top-down at sub-assy level as most parts share the same parameters. But when the parts changes (parameter Length=100 to 200), the file should become a unique file. If it changes back to Length = 100, then it should be the previous file. We need a library of files in which it looks and replaces.
Thanks again.

[sj_kohlmann]

Is there documentation or videos you can share about iPart and library folder reuse?
Also for the iLogic rule with design copy and re-using data if it is previously generated. 

[SharkDesign]

Yeah, ideally you need to make a full copy of a design and then use this iLogic code. I did write a full code that would store new parts in certain places and pull in existing parts from Vault if there already was one, but I can't post it here and it was VERY complicated. 

[sj_kohlmann]

I understand it is very complicated as it is very custom to your situation. I am used to 3rd party software to manage most of these complicated things (reading full codes) with an understandable interface. I was expecting the same for Inventor and hoped for more advise.

I am also still interested in iParts if it will be suitable to our needs