NX manager and part versioning

[cowski]

We are currently running NX6 native, soon to move to NX manager. Will we need to set up anything special for part versioning (revisions)?

Currently about 95% of the part numbers we assign are 'dumb' (the major exceptions being screws and wires which may have the length and/or other info encoded into the part number). To make a revision we fill out some internal paperwork, open the file, make changes, and save it. What changes do we need to make for NX manager?

Hudson, in a past thread you had mentioned using the military type versioning eg 12345.0.0.0.prt, after much searching I am unable to uncover that thread but I would like more info on that. I think it will help us now and in the future.

NX manager will be completely new to me so anyone that has experience with it please give tips, tricks, advice, caveats, etc for a new user.

Thanks!

 

[petulf]

Cowski, i think this might be the thread you are looking for.

http://www.eng-tips.com/viewthread.cfm?qid=267103&page=6

 

[cowski]

That's the thread. Some good points brought up there.
Thanks petulf!

Any and all advice is welcome, I'm not sure I know enough about it to even ask the right questions yet.

 

[hudson888]

http://www.eng-tips.com/viewthread.cfm?qid=267103

This is one such thread but it was talking around the Native file system. I'm not in the best position to advise for NX-Manager since my experience is rather with the full implementation of Teamcentre itself. As I understand it NX-Manager refers to something that could be described as a lightweight version of Teamcentre which I haven't used often enough to comment.

Best Regards

Hudson

www.jamb.com.au

Nil Desperandum illegitimi non carborundum

 

[cowski]

Ok, we have NX manager (teamcenter lite) installed and in initial testing. One possible issue that has come up is how to handle drawings (master model method). On the test we ran the drawing will always reference the most current part revision. Perhaps this is working as it should because right now I still know very little of this environment.

Let me illustrate what happens vs what I think should happen with an example. Let's say we release part 1234-05.prt (<base number>-<rev>) and create a drawing for it, 1234_dwg-01.prt. Now we rev the base part 1234-06.prt, the drawing immediately references the new part (before we rev the drawing). Now my drawing has changed before we even rev it. Perhaps that is OK, since I plan to rev the drawing as well, but now the previous revision drawing references the latest revision part. What happens if we have to pull back a rev? What will the drawing reference now?
What I think should happen is when we rev the base part, the drawing gets a rev and references the new part rev and the old drawing rev references the old part rev. If we make the change to rev both at the same time will that apply to any subassembly where the part is used? I don't see a way to discriminate between 'drawing' files and 'assembly' files; or for that matter should we? maybe we should bump the rev of an assembly whose part(s) get a rev?

If you are still reading to this point, thanks for the attention. For those running teamcenter, how do you handle the revision process, or how would you set it up if you had to do it all over?

Thanks

 

[hudson888]

Someone will correct my terminology I'm sure, but in teamcentre using the PSE revision levels of assemblies may be frozen and unfrozen to control whether the latest revisions are used. Implementation of a releasing process will ensure that released data is saved as frozen so that it never loads the latest revisions. I think what you have to do is create a new revision first and open it in NX via the PSE as unfrozen before you'll be able to perform updates loading later data.

Best Regards

Hudson

www.jamb.com.au

Nil Desperandum illegitimi non carborundum