managing multiple revisions 1

[Walterke]

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?

 

[MickyV007]

This is a consequence of the assembly load options, probably you have load options, latest by alpha rev order. So you need to create a revision rule so that it will look at the release status also.
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

 

[Walterke]

Thanks for the quick reply, that does the trick.

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?

 

[JHTH]

This is one of our biggest bugbears when working with NX in Teamcenter. The assembly does actually store the last-saved revision of all the components (open the revision with the BOM viewer/editor - called PSE in TC 2007, I forget what it's called in 8.3 - and change the revision rule to Precise to see this) but it always follows the NX load options when opening assemblies, regardless of the release status.

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

 

[looslib]

Another method is to load file1.01 first, then load newassembly.01. Since file1 is already in memory, the assembly file will use that first before loking on disk for the latest version.

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

 

[Walterke]

Thanks for the help, but I'm afraid you're speaking Chinese to me.

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...)

 

[JHTH]

Expand the assembly's item revision in TC. Under it (I'm guessing a bit here as I'm not looking at TC 8.3) you should see, amongst other things, an icon that looks like a diagrammatic form of a tree structure. If so, double click it. Whatever new tab opens up is probably the 8.3 equivalent of PSE.

can anyone else tell me what it's called?

JHTH
NX 7.0.1.7 + TC 2007

 

[Walterke]

nother method is to load file1.01 first, then load newassembly.01. Since file1 is already in memory, the assembly file will use that first before loking on disk for the latest version.

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?

 

[Walterke]

Apologies for messing up my quote tags.
Should've read the help first (and click preview)

I hate computers!

 

[JHTH]

In 2007 it's under Tools > Revision Rule or the 'R' icon on the toolbar.

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

 

[Walterke]

Turns out that if you use file>save precise assembly, it seems to work. Is there a reason we should NOT do it this way?

NX 7.5
Teamcenter 8

 

[looslib]

It depends on what role you have and how you want to load your assemblies.

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

 

[Walterke]

There's only 2 people here who work with NX and we both have the same title/job, so no big problems there.

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:

warnings while opening "part"
The following warninsg were issued while loading.

[tab]"part" - No revision found through selected revision rule.

any ideas?



NX 7.5
Teamcenter 8

 

[JurgenKreisel]

Coming from I-Deas to NX/Teamcenter we still have trouble understanding the revision rules. In Ideas every time you save/checkin a part/assembly it created a new version which is akin to NX revision. If I save an assembly today (version 1) and then save it 100 times, I can still call up version 1 a year from now and it will load all the parts as they were when that version of the assembly was saved a year ago. Now I have precise mode, revision rules etc...
It seems to be much harder to have NX with TC work in the simple way that I-Deas did.

Regards
Jurgen

 

[Walterke]

you will want to load the assembly exactly as it was saved and released.

This is exactly what I want. Can you give me any more tips on how to achieve this?

NX 7.5
Teamcenter 8

 

[looslib]

Never workd with TC, so not sure how that handles it. From NX, set your load-options to As Saved.

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