File Reuse and Rejuvenation
File Reuse and Rejuvenation
(OP)
Is there a limit to the reuse of files?
We have been reusing files as the starting point for new designs since around 2005. At each reuse, changes are incorporated to take advantage of the latest NX functionality. As you may imagine, these files now have expression P values in the 10-30K+ range. All along we have used part clean up and manually ensured that the files are kept as streamlined as possible.
Lately we have begun seeing very odd issues arise of which there is no good rational to explain. Internally we are discussing defining and implementing a ‘file rejuvenation’ process. I would like to hear what others have to say on this topic.
Does Siemens have a suggestion as to known limitations and best approach to rejuvenate files?
Currently running NX7.5 going to NX9 4th quarter
We have been reusing files as the starting point for new designs since around 2005. At each reuse, changes are incorporated to take advantage of the latest NX functionality. As you may imagine, these files now have expression P values in the 10-30K+ range. All along we have used part clean up and manually ensured that the files are kept as streamlined as possible.
Lately we have begun seeing very odd issues arise of which there is no good rational to explain. Internally we are discussing defining and implementing a ‘file rejuvenation’ process. I would like to hear what others have to say on this topic.
Does Siemens have a suggestion as to known limitations and best approach to rejuvenate files?
Currently running NX7.5 going to NX9 4th quarter





RE: File Reuse and Rejuvenation
www.nxjournaling.com
RE: File Reuse and Rejuvenation
You are not alone in this. I had a user come complain that he had to always change the decimal places on angular dimensions to zero places. I opened a new file, created a sketch, extruded it, then opened a new drawing. My angular dimensions came in with zero decimal places since the company defaults had been set that way 3 years ago. He was using an old file to start a new file from.
In the long run, you save no time by modifying an existing file over starting a new one.
"Wildfires are dangerous, hard to control, and economically catastrophic."
Ben Loosli
RE: File Reuse and Rejuvenation
File -> Export -> Part...
...and select the bodies of interest and Export (Paste) them into a NEW clean file. Now the only issue here would be that all of the expressions moved with your bodies/features, their names would be 'hashed' to make sure that they're unique, but there are ways of cleaning that up as well (I've got a GRIP program which will convert the unique expressions back to their original names).
John R. Baker, P.E.
Product 'Evangelist'
Product Engineering Software
Siemens PLM Software Inc.
Industry Sector
Cypress, CA
Siemens PLM:
UG/NX Museum:
To an Engineer, the glass is twice as big as it needs to be.
RE: File Reuse and Rejuvenation
Based on my work in CheckMate checker development it seems that NX holds on to a lot of "background" data such as geometry and other things off on layers outside of user access. Part clean-up doesn't seem to clean all of this.
Between the file>>export option and the Copy>>Cut>>Paste option does anyone have experience as to which results in a cleaner result.
Thanks for all the replies! It is always good to gain the experiences of others.
RE: File Reuse and Rejuvenation
John R. Baker, P.E.
Product 'Evangelist'
Product Engineering Software
Siemens PLM Software Inc.
Industry Sector
Cypress, CA
Siemens PLM:
UG/NX Museum:
To an Engineer, the glass is twice as big as it needs to be.