structure and equipment to work in more people

[Mould Rimbamba]

Hello everyone, I just signed up
just to ask you a dilemma....

work in a company that produces molds and until yesterday everyone made their own mold without "breaking" others if not for harvests at the table. We still work in catia v5r19, we haven't gone to 20 yet even if the dealer is now a year that gave us the cds.

Where is the matter?

from today we have to develop the mold in two.. maybe even in three and we have placed the problem of how to open the project files at the same time: We all work on a server.

we have the classic structure with a catproduct that is the axieme of the mold under which there are a catproduct for the jet, a catproduct for the fixed part, a catproduct for the mobile part, a catproduct for the castle and a catproduct for every wagon or movement that you want.
inside the catproduct there are obviously all catparts with the classic catpart adapter or skeleton or as everyone calls it.

so that everyone can open any of these "under assemblies" catproduct and work quietly without incurring any contextual error or having strange errors then, when the "project helmet" opens the assemblies and updates all the mold there is any particular attention to follow?
I don't want to get to the bottom and eventually load the whole project and discover missed links various errors and throw there too much time.

Thank you in advance.. .

 

[ferrezio]

the problem will always be the common parts, because sooner or later someone will come to mind to change an existing part that maybe is using you too, so the direct answer to the question is that if you all work on a single server and behind there is the normal system (pdm) that controls what you write, you will risk at best the exponential replication of the projects because no one wants its work to be touched and not want to touch the work of others,

as it described the structure of the model correctly worked, but you should evaluate the strutting of the trees you create, both parts and assemblies, if you create links between files, if you use published, if you have libraries etc...).

the only notice I can give you, pay attention to how you codify the models, how you manage the progress states of the implementations of the changes, how you archive the standard parts (viteries, colorings, mold plates etc.), and if you change the common parts you start a procedure that will keep everyone informed of the change:

Hi.