How to use File Versioning?

[4mranch1]

We are using NX3.0 native.

Our current part numbering system:
222123_- Where the dash represents the revision level.
560123_A Where the A represents the revision level

With the above data as an example how do I fill in the 5 blocks under File/Utilities/Customer Defaults/Assemblies/Site Standards/Part Name Versions

Gary Ashby
Designer

 

[JohnRBaker]

When you are in the Customer Defaults at the section you've indicated, go to Help -> On Context and it will bring up the section of the documentation that will provide an explanation of the how to format these fields and will include examples.


John R. Baker, P.E.
Product 'Evangelist'
UGS NX Product Line
SIEMENS PLM Software
Cypress, CA

http://www.siemens.com/ugs

http://www.plmworld.org/museum/

 

[4mranch1]

Thanks John. I came across the use of pushing 'F1' while the Customer Default window. The document you referd to opened and I am currently attempting to understand it. This is what I have come with so far:

Full Part File Name Format: ([0-9\-]+_)(\[0-9]+)
Version Independent Section Of The File Name: \1
Part File Name Match: ([0-9\-]+_)
Version Section Of Part File Name Match: \1
Numeric

Our part numbering set-up is as follows:

222123_- Where the "-" is our revision level.
222123_1 "1" would be the next revision. (2,3,4,...)
222123-12_- Where "-1" is a sub component at revision "-"
222123-12_1 "1" would be the next revision. (2,3,4,...)

The first set of 6 numbers is our base part number.
"_" is just used as a divider between the base number and the revision level.
"-" followed by our revision number/s after the base number.

Gary Ashby
Designer

 

[hudson888]

Gary,

Your original post seemed like you wanted to use _A as the version, your second post seems to be using a similar system but numeric.

This should work, but after setting the values you may have to save your new defaults and re-start UG. Look in your Load Options for the Load latest tick box to be available, it is greyed out when versioning is not set. Before you tick it on set up your search directories and check using verify directories whether the system is recognizing the versioning rules correctly.

You may also find that there are files with naming conflicts on your system. For example you would understand that 560123_1.prt was a legitimate name, but if you have other files with similar names that you didn't realize may be recognized as versions either because you need to fine tune your definition or because somebody used a similar name like 123_01, (it could be a suppliers part number or a junk file just similar enough to be recognized by the computer).

If you just wish to support legacy data using an alphabetic revision system then you'll want to stick with the above. If on the other hand you are undertaking to set up a new system then I would recommend the military version type as it is more powerful and flexible.

Best Regards

Hudson

 

[4mranch1]

Hudson,

Thanks for your informative review of what I have done so far. Yes my original post was using letters as the revision scheme, and we will end up going in that direction. For right now, and on this particular project, the powers at large want to go with the numeric revision. My plan is to set the defaults for now and then when the revision type changes, reset the defualts.

I will try and convince my higher ups of the need for the Military style revisioning and hopefully change their minds.

Gary Ashby
Designer