Project with Sub-Projects?

Project with Sub-Projects?

nucleusgmbh
Enthusiast Enthusiast
978 Views
4 Replies
Message 1 of 5

Project with Sub-Projects?

nucleusgmbh
Enthusiast
Enthusiast

Hi guys,

 

first of all: we are using IV 2016 with vault.

 

Our company is constructing special-machines. Every machine is different but uses same components.

Some example:

 

Project a)

Cutter-Unit with several sub-folder, assemblies and part

 

Project b)

Complete machine where one part of it is the cutter-unit

 

Project c)

Complete different machine which also includes the cutter-unit

 

Earlyer we used only one Project with several sub-folders. This had a massive problem:

We couldn't prevent that someone, somewhere referenced a part from a different project. If someone modifies this part now because he doesn't know it is referenced from a different machine, he "destroys" the other project as it does not represent the real status again.

 

Thats why we changed our structure and use one project (ipj) for each machine now.

But what is the best way to use sub-assemblys now? Is there a function I don't know to use sub-projects?

From software-development I know something called sub-modules (git).

 

CU

mts

 

 

 

0 Likes
979 Views
4 Replies
Replies (4)
Message 2 of 5

mcgyvr
Consultant
Consultant

The key for your company problem is that each project files are totally independant of other projects files.. single projects as you have switched to now solves your problem.. assuming each project points to a new folder and ALL files including subassemblies are stored inside that folder.

 

Subassemblies are no different than any other assembly or any other part files.. 

 

Of course you also said.. "each machine is different but uses the same components"... well now it really doesn't use the same components

You might still call it "bracket1" but bracket1 could be modified for each project and is no longer the same.. so its not the same component (by my definition anyways)

 

Sounds like what you may have done instead of indivudual projects is use library locations to essentially "read only" on your common parts that will never change..



-------------------------------------------------------------------------------------------
Inventor 2023 - Dell Precision 5570

Did you find this reply helpful ? If so please use the Accept Solution button below.
Maybe buy me a beer through Venmo @mcgyvr1269
0 Likes
Message 3 of 5

PaulMunford
Community Manager
Community Manager
I think that projects are a red herring here. It sounds like you need to sort out revision/version control. Libraries would be a good place to start. Do you use Vault?


Customer Adoption Specialist: Autodesk Informed Design
Help | Learn | Forum | Blog | Ideas | Sample content | Linkedin 

Message 4 of 5

nucleusgmbh
Enthusiast
Enthusiast

Yes, we use vault.

The problem I have with libraries is that I don't know how to parts in it.

0 Likes
Message 5 of 5

mcgyvr
Consultant
Consultant

@nucleusgmbh wrote:

Yes, we use vault.

The problem I have with libraries is that I don't know how to parts in it.


You simply include the location of the "read only" parts under the libraries folder of your project.

 

Then you can create another project that allows you to modify those files if needed...

 

http://help.autodesk.com/view/INVNTOR/2016/ENU/?guid=GUID-3C72B1C2-72BC-4CD4-A2F4-66228DC2DB73



-------------------------------------------------------------------------------------------
Inventor 2023 - Dell Precision 5570

Did you find this reply helpful ? If so please use the Accept Solution button below.
Maybe buy me a beer through Venmo @mcgyvr1269