Model State - Inventor 2022

Model State - Inventor 2022

admaiora
Mentor Mentor
12,767 Views
61 Replies
Message 1 of 62

Model State - Inventor 2022

admaiora
Mentor
Mentor

No question this time... Just wow!

So many things unlocked with Model States!

 

Thanks @ChrisMitchell01 and to the dev team.

Great stuff!

Admaiora
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.

_____________________________________________________________________________
12,768 Views
61 Replies
Replies (61)
Message 61 of 62

admaiora
Mentor
Mentor

Hi,

 

after some years I see that:

-companies that doesn't use PDMs or use at a basic level love Model States

-companies with complex PDMs/high use doesn't prefer to use Model States, they have always a lots a of problems to manage that kind of files/data

 

A third , creative, category use Model states only for 1 model states just to use excel formulas to generate advanced metadatas (part number, description, etc) at a next level (much better compared to classic >exoprt parameters> =<paremeter>x etc etc

Admaiora
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.

_____________________________________________________________________________
0 Likes
Message 62 of 62

bike_josh
Enthusiast
Enthusiast

Model states are a great tool to replace iParts and iAssemblies but the big limitation I see is with assemblies. I think a pretty typical use of an iAssembly or assembly with model states would be to create a model where you can easily select configurations. For instance, a bike may have the option for hydraulic disk brakes or mechanical, cable-actuated derailleurs or electric, a dropper seat post or a fixed, etc. iAssemblies can handle this very well with keys and can create a tabulated BOM in a drawing that shows what's included in each configuration. However, iAssemblies are slow, frequently and easily get out of date, and require a separate file to be saved for each configuration. Models state driven assemblies, on the other hand, are very fast, unlikely to loose reference between states, and only required a single file. However, they can't be controlled with keys so you'll have to select the correct configuration from 10s or 100s of rows and there's currently no way to automatically create tabulated BOMs in a drawing. Each configuration would have to have its own BOM listed in the drawing or you'd have to manually create a BOM using the generic table tool.

 

There's an active idea to bring the tabulated BOM functionality to model states. Please vote for it here: https://forums.autodesk.com/t5/inventor-ideas/model-state-support-tabulated-parts-list/idi-p/1068619...