how to work in multi-user environment on the same project

[Utente NX]

As suggested, I open a topic dedicated to multi-user design.
we work in environment tc.
we are in a 50-year-old designer cad.
even if we work on different product lines, we have the same rights on unreleased files.
clearly if I create a process, only those who created the process can indict it.

the problem happens on new projects.
I make an example where we are in 5 working on a new project.
the first charging the axieme becomes owner and others cannot change a comma.
Is there a mode where the axieme is loaded in read-only, as well as its components and only if it is published something become a owner?
is it possible to make a request to a colleague to release it, like a message that shows you on the screen without having to call it by phone or email?

 

[stef_design]

I don't know if it works in nx, but I'll explain how we do it in catia and proe.
example: 5 people work on the same project.
the first (administrator) opens the complete axieme with features while the other 4 in cache (without slots).
each of these 4 then opens its subgroup works and saves us.
when you want to see the general axieme with your subgroup, you charge all the features and the axieme should update.
and so on every time you change your subgroup....I collect the assembling from the virtual memory of the pc and then reload it to see the changes I made.

we have pro w4+tc2005 and we never pass for tc but we do so.
Hi.

 

[ceschi1959]

I don't know if it works in nx, but I'll explain how we do it in catia and proe.
example: 5 people work on the same project.
the first (administrator) opens the complete axieme with features while the other 4 in cache (without slots).
each of these 4 then opens its subgroup works and saves us.
when you want to see the general axieme with your subgroup, you charge all the features and the axieme should update.
and so on every time you change your subgroup....I collect the assembling from the virtual memory of the pc and then reload it to see the changes I made.

we have pro w4+tc2005 and we never pass for tc but we do so.
Hi.

just like that, changing terminology also works with nx, and also works in tc.
:finger:

 

[Utente NX]

just like that, changing terminology also works with nx, and also works in tc.
:finger:

You didn't understand the situation.
Will I make a clearer example?
stef said he doesn't work under tc, even if they do.
Are you working there?

example :
1) new project together engine and under other subgroups
2) we are all 5 designers with the same degree
3) the first who arrives in the office loads the main axieme
4) Loading or is with feature or vacuum
5) start loading a subgroup to finish yesterday's work, editing parts or adding other components.
6) I arrive and load the same together because there is a pin that I must complete
7) the complete but must also add seeger or other things
8) I can't do anything because it's in favour of my colleague who did things to us.

Now, it would be nice that I could send a direct message to my colleague's screen to request it in property.
receive the message, save and release it.

 

[stef_design]

example :
1) new project together engine and under other subgroups
2) we are all 5 designers with the same degree
3) the first who arrives in the office loads the main axieme
4) Loading or is with feature or vacuumwe put the first coming charge the axieme with features5) start loading a subgroup to finish yesterday's work, editing parts or adding other components.when it ends up saving the axieme and downloads it from the memory of the pc (i.e. it has the axieme in display mode without features)6) I arrive and load the same together because there is a pin that I must completeat this point I who had uploaded my set in display alone I load the assembling in design mode with all the features.
I should then see the changes my colleague made and I could work independently.7) the complete but must also add seeger or other things
8) I can't do anything because it's in favour of my colleague who did things to us.

this should be possible even without tc. we with proes do so. It is obvious that if the working group is small (max 3 people) the thing is feasible, + people embody in the project plus the instability of the method increases.

 

[Ryo]

we simply create a personal copy of the axieme in our home of tc, we work and save that, at finished work, we insert, or we put to those who have the rights on the "real" fife, the details or sub-axiemi that we have created

Hi.
ryo

 

[stef_design]

we simply create a personal copy of the axieme in our home of tc, we work and save that, at finished work, we insert, or we put to those who have the rights on the "real" fife, the details or sub-axiemi that we have created

Hi.
ryo

do you work only with nx or other cad along with tc?

 

[SER.CAD]

I'm sorry. Does the first person to charge the axieme become the owner of the set?

if the aid is its owner or if other rules are configured
in tc (gm style) if you put all the assembly in check in

you should work with the properties so one keeps the assembling.... and the other assemblies are the property of others
4 they change them quietly!

in this case you to see the changes you download and download the component ...

in duchies we worked like this:

the head-project was the owner of the aid and some of its components, the other projects
of other components and sub-assiems.

the head-project kept the mats of the axieme, and verifyed all encumbrance, interference etc...
if I loaded my axieme to shape my own part, or new inside or take me
of the references with wave geometry linker when I loaded the axieme it was getting me
in read only!

I was linking the surfaces or leotards I needed on my side, doing make work part, make display part
and I worked and saved!

The boss then fucked me if I was wrong. . . .

in gm that I worked a little bit' the thing was much more Moroccan the parts created within the 'ut in Italy
followed the symil-ducated rules ...but they were all proto codes, the production codes detached to detroit
on the tc server of gm if you had to work you could save them after their check-in....
and check-out....
the axieme was controlled to detroit ... and all the management of c, co, pdi entrusted to detroit to a selva
of Indian systems...

according to me for 50 people, with the method of properties as it was done in the good old desmobottega
It wasn't bad!

 

[Utente NX]

the head-project was the owner of the aid and some of its components, the other projects
of other components and sub-assiems.

the head-project kept the mats of the axieme, and verifyed all encumbrance, interference etc...
if I loaded my axieme to shape my own part, or new inside or take me
of the references with wave geometry linker when I loaded the axieme it was getting me
in read only!

I was linking the surfaces or leotards I needed on my side, doing make work part, make display part
and I worked and saved!

I like it.
but we do not have the 'wave' license.
We can do wave geometry links and so your suggestion is feasible, but the wave license what allows me to do more?

 

[ceschi1959]

I like it.
but we do not have the 'wave' license.
We can do wave geometry links and so your suggestion is feasible, but the wave license what allows me to do more?

as you see the answer or the answers you found. Of course we must be very organized and prepare a minimum of procedure. depends on the type of product, the organization of people and other aspects.
As far as the wave is concerned, I place some images I hope significant.
is a tool that allows you to manage the various links of parts and assemblies.
This license is in mach 3. But be careful because of mach 3 there are two: one nx13100 does not have it (in its place there is the pcb package) while the license nx13300 is provided.

 

[Utente NX]

thanks to all for your suggestions.

 

[Ryo]

do you work only with nx or other cad along with tc?

normally only with nx, but I have seen people who sometimes work with catia v5.... don't ask me why, the project I'm following is on nx

 

[The_Matrix]

I'm sorry. Does the first person to charge the axieme become the owner of the set?

if the aid is its owner or if other rules are configured
in tc (gm style) if you put all the assembly in check in

you should work with the properties so one keeps the assembling.... and the other assemblies are the property of others
4 they change them quietly!

in this case you to see the changes you download and download the component ...

in duchies we worked like this:

the head-project was the owner of the aid and some of its components, the other projects
of other components and sub-assiems.

the head-project kept the mats of the axieme, and verifyed all encumbrance, interference etc...
if I loaded my axieme to shape my own part, or new inside or take me
of the references with wave geometry linker when I loaded the axieme it was getting me
in read only!

I was linking the surfaces or leotards I needed on my side, doing make work part, make display part
and I worked and saved!

The boss then fucked me if I was wrong. . . .

in gm that I worked a little bit' the thing was much more Moroccan the parts created within the 'ut in Italy
followed the symil-ducated rules ...but they were all proto codes, the production codes detached to detroit
on the tc server of gm if you had to work you could save them after their check-in....
and check-out....
the axieme was controlled to detroit ... and all the management of c, co, pdi entrusted to detroit to a selva
of Indian systems...

according to me for 50 people, with the method of properties as it was done in the good old desmobottega
It wasn't bad!

Hi, guys. .
I also give you my vision, answering ser.cad.

if the study becomes a little more "extended"... so there is a larger working group that collaborates... probably we organize with assembly of study and assembly of product.
the study assembly could be done like this:mystudy (my property... we say user1)- assy1 (user ownership 2)---- comp1 (user ownership 2)
---- comp2 (user ownership 2)
---- comp3 (user ownership 2)
- assy2 (user troprie 3)
---- comp4 (user ownership 3)
---- comp5 (user ownership 3)
---- comp6 (user ownership 3)- mycomp1 (my property... (1)as said sercad, within mycomp1 you go to insert everything you need, taken from the components of your colleagues (comp2 ... comp6).
the revision rule to use, according to me is:
wrkusr (load my components in working)
any status (reload the latest release of users 2 and 3)
working (if user 2 and 3 did not release anything, I take their working... dangerous choice, but it must be left... )

The wave license for these operations doesn't need... for those who make top/down structures very structured (called in jargo archetypes or templates).
from nx7.5.3 these link controls have extended to the features of the part (with the feature browser and the new feature substitute)

if the various users (users 1, 2 and 3) are separated it is correct that their assemblies and parts remain their property. . .
if you are part of a working group then there are some methods:
- send an email (an e-mail I mean... with attached the ethem you want to have of your own property or on which you want a checkin or a change owner)
- use openscape (messanger connected with tc with which you can have a messenger style operation with the connected tc features)
with the mail or openscape your colleague receives a notice... save... release... or a change owner.

 

[ceschi1959]

Hi, guys. .
I also give you my vision, answering ser.cad.

probably we organize with assembly of study and assembly of product.

I call them control and assembly together. I don't tell you the hard work with some companies to make them understand, especially for code management. for some of them, generating a code is worse than a crash on the server.

The wave license for these operations doesn't need... for those who make top/down structures very structured (called in jargo archetypes or templates).
from nx7.5.3 these link controls have extended to the features of the part (with the feature browser and the new feature substitute)

it also allows you to make the 'selective' upgrade, and in some axioms it becomes necessary. :finger:

 

[The_Matrix]

I call them control and assembly together. I don't tell you the hard work with some companies to make them understand, especially for code management. for some of them, generating a code is worse than a crash on the server.




it also allows you to make the 'selective' upgrade, and in some axioms it becomes necessary. :finger:

coding: how do you manage the codes between control and assembly set?
wave: I once made assembly control "complexes", composed of many small parts.
Recently (with 7.5.3) I am trying to use less and put operations in the same part, using groups, feature browsers, etc... it is not bad.
then, on the wave features: sure, help... above all the possibility to make links position independent, however, unless you have the mach3 ind des, it is not worth spending...
a couple of questions:
Do you also use "product interface"? They will become more and more the means to convey geometry from one side to another.
Do you use the "general relinker" to make automatic reference changes?

 

[IPdesign]

I moved the messengers related to the brainstorming proposal in a new tread
http://www.cad3d.it/forum1/showthread.php?p=210781#post210781so this returns to its primary line

 

[stef_design]

excuse the question, as I use catia and proe, by wave what do you mean?
the possibility of relying on other geometries, namely a "copy with reference"?

 

[lostico]

excuse the question, as I use catia and proe, by wave what do you mean?
the possibility of relying on other geometries, namely a "copy with reference"?

I don't know catia and proe, but that's it.

 

[The_Matrix]

excuse the question, as I use catia and proe, by wave what do you mean?
the possibility of relying on other geometries, namely a "copy with reference"?

the copy of interpart geometry is called wave geometry linker
wave is a nx module that allows you to do many other things:
1) create independent position links
2) block regeneration in the session or permanently
3) have a map of interpart links
4) force regeneration of an assembly

 

[stef_design]

the copy of interpart geometry is called wave geometry linker
wave is a nx module that allows you to do many other things:
1) create independent position links
2) block regeneration in the session or permanently
3) have a map of interpart links
4) force regeneration of an assembly

Okay, a little dangerous, no?!? .
if the aid is managed by a few people ok, but with large assemblies managed by various competence center... help