Are Part-revisions possible using native NX5 ? 1

[ErikvD]

Just as in Teamcenter, I would like to make part revisions by making a "save as" and rename the part.
Of course with the intention if the part is used in an assemblie it automatically updates with the "new revision name".

I'am not sure if it's possible at all ?
I've read the threads about file versioning,read the help files, played with the settings under File/Utilities/Customer Defaults/Assemblies/Site Standards/Part Name Versions but I still can't manage it.

Can anyone help me with this?

the initial partname for instance is = 012345.part (number is generated by system).
the revision partname I have I mind is 012345_01.part

 

[hudson888]

There could be two questions in one here. The first is about renaming the parts and the second is about controlling how the system recognizes those names as part revisions.

To rename using a uniform naming cypher you can use Assemblies>Cloning to affix either a prefix or a suffix to the ends of you existing part names.

To set up how the system recognizes the part revisions you need to declare part name versions in your customer defaults. The "012345" string will become your core part name, and the "01" on the end would be your version, with the underscore as your delimiter. If you aer considering using such a system then I would steer you towards using the military system of versioning such as is used for software 012345.5.03.02 where you can append any number of decimal points to represent sub releases or stages of a project development. Military is probably the most modern and flexible of the available options.

I have supplied you with the terminology used to describe what you need to do so to find out in detail should you need to you could search the forum for other posts on this topic several of which have working examples. My best advice would be to set up small test cases an experiment with how the system does these things before you use it in a wider sense, you will likely find it is neither as hard or dangerous as you may have feared.

Best Regards

Hudson

 

[DavidTolsma]

Customer defaults has a site standards section under assemblies section.

You need to define your naming convention using regular expressions. In your case you have 6 digit part number with an 'underscore' two digit number.

An example Regular expression for your site standards would be: (each line represents each section in the site standards)
([0-9]{6})(|_[0-9]{2})
\1
\1(|_[0-9]{2})
\2

Set the rule to numeric.

Another example would be:
([dD]?[0-9]{2}[a-zA-Z]?[0-9]{5,7})(|([a-zA-Z]{1,2}))

which would be for parts in this type of series:
1234567
12345678
123456789
d1234567
d12345678
d123456789

1234567_a
12345678_a
123456789_a
d1234567_a
d12345678_a
d123456789_a


Set your load options to load latest (now available since you set your site standards).

-Dave Tolsma

http://groups.google.com/group/NX_CAX/

 

[DavidTolsma]

Test this with your Assembly load options, when you add a folder to there is a verify button. This will list all the files in the folder that match and do not match.

-Dave Tolsma

http://groups.google.com/group/NX_CAX/

 

[ErikvD]

plmexchange ,Dave

Thanks a lot, This was the answer I was looking for.
i have typed in your piece of text/expressons and It worked fine.

I have considered to purchase Teamcenter mainly becauce of this issue, making part revisions.Now I'am glad I have'nt.


ErikvD
Zebra-cad 3D services
the Netherlands

 

[Dave K]

I just posted this to the official newsgroups, then found this thread...

NX 5.0.3.2

It's been...5 or 6 years since I've setup Part Versioning, so I'm a bit rusty.
I thought I had it, but something doesn't seem to be working.

here is our scenario. A part number will look like this:

PartNumber.Rev.Description.prt

The part number will be a letter, followed by 6 numbers, in rare cases, more than
6 numbers. Basically, I want what ever is in the first section, to be the "part
number", the second section the revision, and the third a nomenclature description.

V01234.a.TestPart.prt ("A" reved part)
or
N01567.o.AnotherTest.prt (o being a non-reved "o"riginal)

These are my settings:
Full Part File Name Format:
([a-z]+[0-9]\\.)(o|([a-hj-np-z]|([a-hj-np-z][a-hj-np-z])))

Version Independent Section of the Part File Name:
\1

Part File Name Match:
\1(o|([a-hj-np-z]|([a-hj-np-z][a-hj-np-z])))

Version Section of the Part File Name Match:
\2

Version Type:
Alphabetic

Any thoughts on what I messed up here?

-Dave

-Dave
Everything should be designed as simple as possible, but not simpler.

 

[DavidTolsma]

Need to find all the variations of a naming convention and list them out. Then what determines the revision, what is the starting revision, in your case an 'o'.


Part Number:

First is a letter, any letter? I'll assume any.
Then a number 6 or more in length, I'll give it a range 6 to 9
A separator of a '.' required


Revision:

First version is an 'o' or another letter 1 or 2 letters
Followed by a required '.'


Description:

I set to allow any letter up to 32 characters in length.


([a-z][0-9]{6-9}\.)(o|[a-z]{1,2}\.)([a-z]{32})
\1
\1(o|[a-z]{1,2}\.)([a-z]{32})
\2


I think this is pretty close, didn't try it out in NX to validate it.




-Dave Tolsma

http://groups.google.com/group/NX_CAX/

 

[Dave K]

Dave,

Thanks. I'll give that a try.

Yes, the first letter could be anything, it will vary, depending on the project.

Starting rev is "o", and o, i, are not used at all for revs.

I wasn't aware of, or forgot about, setting the character length.

Now, without trying it, I'm wondering what a - (dash) will do to the part number, ie V12345-2, or v12345-1_3-4. In rare cases, part numbers like that are generated.

I'll do some experimenting, and thanks again.


-Dave
Everything should be designed as simple as possible, but not simpler.

 

[DavidTolsma]

need to allow '-' as a possible value or '_'.

[a-z-_] (i think that is the correct syntax)

If you want to disallow possible letters, You would want to put in the allowable characters [abcdefghjklmnpqrstuvwxyz]. It's longer but easier to read by us.

-Dave Tolsma

http://groups.google.com/group/NX_CAX/