3D model update from previous rev to new rev in Teamcenter and NX manager

[CAD Application Support]

Hi All,

scenario :
If we have a component and it goes from rev 01 to 02 to 03. 03 is latest rev that Iam making for for an upcoming build in a couple of months. Now rev 02 was used in an ongoing build and there were some issues found that needs cad update. So I open rev 02 and make cad updates and save it. Now when I load rev 03, is there any way via script or something we can prompt the user that previous rev of the model has been updated since rev 03 was last modified, do you want to update the rev 03 model for the latest changes from rev 02, if yes, then program goes and updates the current model of rev 03 in the current user session. I see there would be a scenario where it may totally break the current 3D model, in which case, the feature update should stop on encountering the failure .

is this achievable in the context of Teamcenter and NXmanager?

 

[cowski]

In TC, once a part has been released, no one can make changes to it anymore. It is possible for an admin to "un-release" a part so that changes can be made, but this is bad practice. In your scenario, if rev 2 is released and rev 3 is not (it is still a work in progress), the changes would have to be made to rev 3.

www.nxjournaling.com

 

[CAD Application Support]

Hi Cowski,

The problem here is that TC is being used as ERP system here , so up reving the component during the ongoing build is not possible. Yes we do have rework workflow that gives designer ability to open the 3D ,make changes and save them. Iam curious if there is any script or anyways in which when I open rev 03, NX would prompt me that rev 02 has been modified and do I want to import those changes by doing model compare on the fly to highlight the changes ..

 

[cowski]

To answer your question directly, I know of no way to merge the changes of 2 separate file revisions.

Based on your short description of the process, your company needs to get a better handle on configuration management. Otherwise the problems are only going to get worse (and more expensive to fix).

www.nxjournaling.com

 

[Toost]

The only solution I see , if this happens frequently , is that you wave link the 02 into 03 as the starting block. Then add new stuff to 03.
One can fiddle by copying the actual NX partfile from revision to revision , but then you would loose all modifications done in 03.

Regards,
Tomas

Never try to teach a pig to sing. I wastes your time and it annoys the pig.