topic Re: Project structure and data management with skeleton design in Inventor Forum

Project structure and data management with skeleton design

louis.siguier — Thu, 12 Oct 2023 11:16:14 GMT

Hello,

I am a relatively new user of Inventor (1year) and currently the first and only in my company right after my graduation. I learned CAO with Catia and Solidworks during my degree but i'm self-taught with inventor.

I know this topic as been asked a lot of times but there's as many solutions as there is projects ... For what i saw there is plenty of different strategy and i don't know wich i should apply. I think i also have some issues with how i work using context and skeleton design.

For confidentiality i will use the exemple of a car as my project.

So my company want a new car, but first they had to design a dashboard to upgrade old car model's and to put in the new one. Then they started to design a new engine wich will be used in the new car and future ones. To finish design the car using the previous assemblies and new parts.

I started the CAO using skeleton strategy, one big for the car, and two smaller linked to the first for the dashboard and the engine.

So my workspace as all files in the « car project » folder but then i had to do a V2 for the engine, how do i deal with the skeleton for the V2 ?

In the V2 there will be new parts but also V1 parts that are not modified. If i use design copy and create a skeleton_V2 + a engine_V2.iam and later have to change parts_V1 in the V2, this parts will be linked to the skeleton_V1 no ?

So i was thinking of this solutions :

- 1 big project CAR in wich there is the project dashboard and the project engine

(If there is a new version i just create a project_engine_V2 for example ?)

- Or a big project CAR with folder for each sub assembly but then if there's new version i can't keep them inside because i will have the parts twice some times

Are they adapted or there is other solutions ?

I may have misunderstand some Inventor features and hope my problem is clear

Thank you in advance to the people who will read and respond to my questions.

Re: Project structure and data management with skeleton design

Gabriel_Watson — Thu, 26 Oct 2023 16:44:04 GMT

You don't need to duplicate parts, if you save all reusable (non-project specific) parts and subcomponents under a library sort of folder (does not have to be an explicit library), and project-customized parts within the project folders. Keep in mind that you should still use a single IPJ/Inventor Project File for all projects if possible, to make the most out of such arrangement.

Depending on how you make components based on the skeleton, you could break the links to the original skeleton reference. Adaptivity and live-referencing are powerful but only as useful as the amount of changes in parametric sizing you have. Once you establish the "CAR" product size and configuration (which typical/standard parts, including Content Center, are used to build it), you should not rely on skeleton files any longer, and perhaps leverage iLogic forms and other ways to set up a whole assembly parametrically.
The only useful way I see for keeping a skeleton-driven design over time in standardized products (not products/projects that are entirely unique) is if you are using frame generator, tube and pipe, or iParts/iAssemblies guided by the skeleton. Those may help pre-pick the sizes, but you should be building a library of components to be consumed.

Re: Project structure and data management with skeleton design

Frederick_Law — Thu, 26 Oct 2023 17:26:16 GMT

You can have general skeletons (car overall, engine compartment with mounting points and wall) to locate components and detail skeletons (engine specific: V6, L4, L4 Turbo).

You'll need to develop your own process.

I was mainly in custom machine. So every machine has it's own Master Skeleton.

I did use Design Copy to make similar machines but they're not linked.

I did a few CNC fixtures with linked Master but it get confusing fast and you can't split the projects. They're forever linked together.

Re: Project structure and data management with skeleton design

louis.siguier — Fri, 27 Oct 2023 09:23:18 GMT

Thank you for your reply !

When you used Design Copy for new similar machines, it means that in both folder you could have the same file twice ? (For example a protection panel that was the same in both machine) or as soon as you have twice the same, you save into a librairy ?

Using skeleton i was once taught to use a "Design" folder and a "Valided" folder. The design is where i work and as soon the design is valided i move it to the "Valided" folder and i'm not supppose to modify, its mainly used to make drawing etc (It was with catia and as @Gabriel_Watson said we had to broke the links)

But breaking link wont work for me i think, because my company strategy force me to be able to modify V1 while designing V2 etc 😕

Re: Project structure and data management with skeleton design

Frederick_Law — Fri, 27 Oct 2023 13:38:58 GMT

Design Copy in Vault allow renaming and reusing files.

I worked mostly with custom machinery. We don't keep track of or stock "same" machine parts.

So yes, the same part will be copied with a new name.

Library part or hardware will not be copied. ie nuts and bolts, Festo components etc.

I had one project with 11 versions before we decided which one to use with same Master Sketch.

You can try to split up the skeleton for V1, V2.

Depends on if you need to maintain V1.