managing multiple revisions
managing multiple revisions
(OP)
NX 7.5 with teamcenter 8.3
Something seems to be wrong with the way we handle managing multiple revisions of an assembly.
Example:
Assembly "newassembly.01" consists of the files
file1.01
file2.01
file3.01
this assembly has been put in production, so we release it in TC, which is supposed to fix the entire assembly
now, we review this assembly and make newassembly.02
where file1.01 gets a new revision: file1.02
so newassembly.02 consists of
file1.02
file2.01
file3.01
now, however, when we open newassembly.01, file1 also has revision 02, in stead of revision 01.
It seems like, when you fix(release) an assembly, it does NOT fix the revisions of each file inside that assembly.
Is there a way to fix this?
Something seems to be wrong with the way we handle managing multiple revisions of an assembly.
Example:
Assembly "newassembly.01" consists of the files
file1.01
file2.01
file3.01
this assembly has been put in production, so we release it in TC, which is supposed to fix the entire assembly
now, we review this assembly and make newassembly.02
where file1.01 gets a new revision: file1.02
so newassembly.02 consists of
file1.02
file2.01
file3.01
now, however, when we open newassembly.01, file1 also has revision 02, in stead of revision 01.
It seems like, when you fix(release) an assembly, it does NOT fix the revisions of each file inside that assembly.
Is there a way to fix this?





RE: managing multiple revisions
Try load newassembly01 with the load as saved option, then it will take file1.01. Keep in mind to switch it off afterwards.
Best regards,
Michaël.
NX7.5.4.4 + TC Unified 8.3
RE: managing multiple revisions
However, I'm surprised that that's the way it has to be done.
In my opinion, the revision of a part should also be fixed when the assembly is fixed. It sounds more logical. Because changing the revision of an underlying part in an assembly, changes that assembly, so it would also need a new revision.
Or is this not how it works?
RE: managing multiple revisions
However, there is another workaround - if you load the earlier assembly revision into PSE, change the rev rule to Precise and then click the Open in NX button, that will load up the assembly as it was when it was last saved.
HTH,
JH
JHTH
NX 7.0.1.7 + TC 2007
RE: managing multiple revisions
Load options are great, but you need to understand how they work to make them work in your environment. You should also get a good understanding of versioning rules and how TC applies them.
"Wildfires are dangerous, hard to control, and economically catastrophic."
Ben Loosli
RE: managing multiple revisions
I do not know what this bow viewer/editor is, or how to open or load a file in it. Could you elaborate a bit more please?
(my teamcenter help doesn't seem to work, so no help there either...)
RE: managing multiple revisions
can anyone else tell me what it's called?
JHTH
NX 7.0.1.7 + TC 2007
RE: managing multiple revisions
this would only work if you knew which version you needed. Not if you want to open an assembly to find out which version you need in that specific version of the assembly.
@JHTH: this opens the structure manager.
there is a column there called "rules configured by"
for most of the items it says "precise", for the ones that have the wrong revision it says "working()". I suppose thats what I have to change? How can I do this?
RE: managing multiple revisions
Should've read the help first (and click preview)
RE: managing multiple revisions
Click the top level assembly and apply the rev rule to that, see where that gets you to.
Jon
JHTH
NX 7.0.1.7 + TC 2007
RE: managing multiple revisions
NX 7.5
Teamcenter 8
RE: managing multiple revisions
In engineering, you may want to always load the latest components of an assembly to see what chnages have been made to the components.
In manufacturing or the assembly line, you will want to load the assembly exactly as it was saved and released. If engineering is working on a change, you do not want the latest changes.
It takes some work to get the proper load options for each set of users in a company. I was an admin contractor for a large NX user but they had no corporate support, just a user who had been taught the basics. I studied what they were doing and recommended some changes to the load options and immediately had a bunch of users complaining that there assemblies were loading wrong components. Had to develop a short training session to show them what the changes were and how they affected what parts were loaded in session.
"Wildfires are dangerous, hard to control, and economically catastrophic."
Ben Loosli
RE: managing multiple revisions
Anyway, when I put the load option to 'precise only', some of the parts won't load at all. When I try to load them manually I get the following error:
any ideas?
NX 7.5
Teamcenter 8
RE: managing multiple revisions
It seems to be much harder to have NX with TC work in the simple way that I-Deas did.
Regards
Jurgen
RE: managing multiple revisions
This is exactly what I want. Can you give me any more tips on how to achieve this?
NX 7.5
Teamcenter 8
RE: managing multiple revisions
However, As Saved in native NX, still may not give you exactly what you want becasue of the way NX handles directory searches and loading. It is also dependent on how you have your search paths set and where your files are located. If you keep all files in one directory, you will have problems. Released files should be moved to a Release folder. TC should have rules about loading Released files before WIP files, etc.
"Wildfires are dangerous, hard to control, and economically catastrophic."
Ben Loosli