cancel
Showing results for 
Search instead for 
Did you mean: 

Part Revision Handling

Creator
Creator

Hi,

 

I'm not sure where to place this question but I hope this is right..

 

A quick summery of the situation,

 

Until recently so did my company both the engineering and the manufacturing of all our products but they have now sold all the manufacturing to a subcontractor. All the manufacturing personnel including me did get further employment at the new subcontractor. This means that instead of only make our own parts so will we now be a job shop that will make parts to multiple customers.

Before did we use Teamcenter to manage all our data and the part revision. Our new company has decided that we don´t need any type of PDM-system (I don´t agree with them), so we will run NX in native and need some way to handle the different revision of the parts we gets from our customers.
-------------

 

If I get a part from a customer that has the filename “12345_A” and then make a cam-setup that has the “12345_A” added as a component so does everything work fine until I receive revision “B” from the customer. The part that I now need to use will have the filename “12345_B” but my cam-setup will still point to “12345_A”.
This is dangerous because I now can work on the wrong component in the cam-setup if I forgot to replace the component to the new “12345_B”.
I could instead delete or move the old part revision so NX will not find it when I open the cam-setup but I now need to point to the new part revision manually.

I have found something in NX that is called “Part Name Versions” that could be a great solution on my problem, but how will that work then I receives files from multiple customers that has different revision system? Sometimes with letters another with numbers and so on.

So my question to you guys that run NX in native and special you that receive files from multiple customers, how do you handle part revision? Do you have any tips for me?

I guess that my problem has been solved multiple times before but I can't seem to find a good solution.

 

I'm sorry for the long text but I hope you have the time to read it and give me some help.

Thanks!

3 REPLIES

Re: Part Revision Handling

Genius
Genius

Please see link below if it helps.

 

http://nxway.blogspot.co.uk/2009/06/using-revisions-in-native-nx.html

 

As far as data from different customers, you could setup different folders for each customer, then managing each project in sub folders with all revisions with that project.

 

 

BR
Mak
TC10/NX 9

Re: Part Revision Handling

Esteemed Contributor
Esteemed Contributor

You could handle this by using multiple UGII_SITE_DIR locations, so each customer has its separate site folder with its customer defaults.

Stefan Pendl, Systemmanager CAx, HAIDLMAIR GmbH
Production: NX10.0.3, VERICUT 8.0, FBM, MRL 3.1.4 | TcUA 10.1 MP7 Patch 0 (10.1.7.0) | TcVis 10.1
Development: VB.NET, Tcl/Tk    Testing: NX11.0 EAP, NX12.0 EAP

How to Get the Most from Your Signature in the Community

Re: Part Revision Handling

Legend
Legend

I do the following


Customer Name Abrev_ Their Part Number _ Their Rev_ My Revision _ Version 1

 

So

TST_1001_A_01-01

 

Then if I make a revision to the file for my own CAM purposes

TST_1001_A_02-01

 

 

I've been using this system for a while now and never had any issues.

 

If you have made TST_1001_A_01-01

You will have TST_1001_A_01-01_setup_1.prt

 

Then they order TST_1001_B_01-01 you copy the setup file and rename TST_1001_B_01-01_setup_1.prt and make the appropriate changes.

 

Then something comes up and you want to do an internal change for your own reason

TST_1001_B_02-01

TST_1001_B_02-01_setup_1.prt

 

NX11.0.1

Learn online





Solution Information