NX Part Numbers in Teamcenter

[Dave K]

I'm curious on companies using NX and Teamcenter, that do NOT use the Teamcenter created ID number (aka DB_Part_No).

Company history is the use of a "smart" part number, which tells the user the car type, year, and general location the part is used. Most in the company wish to maintain this ability, and our smart number will not go away, it will be used in the Part Name, at the very least.

Siemens has pushed the use of the Teamcenter created ID number, as the preferred, or best practice.

My interest is in companies that do not use the Teamcenter created ID number, and what drawbacks, or caveats they have experienced?

-Dave

NX 9, Teamcenter 10

 

[petulf]

How do you generate these part numbers? are they too complex to handle via a naming rule attached to the item id? Is there another system that generates them for you? Are they internal only or used by the customer?

We used to use significant item id´s but when moving over to TC/NX we changed to using non-significant id´s and moved the part classification information from the part number to attributes on the item and item revision. We did this to simplify our teamcenter deployment and store the information in a more human readable way, but the cost is that we have had to spend more time on formatting the data sent downstream.

 

[Dave K]

We have an excel spreadsheet, that the designer logs the part number and description.

Example:
X15-01-123

X is the car type
15 is the year
01 is the car section
123 is unique

We are also creating attributes for each of the sections. X15-01-123 is marked on the part, and is used as the drawing number.

Our big caveat right now, is since we are migrating from Solidworks to NX, it is possible to import the same part, multiple times. Naming rules dictate we must use the auto assigned number in TC, so we put our smart part number in the part name. Thus duplicates are possible. Duplicate use of the smart part number are possible for new parts, if two users happen to name parts with X15-01-123, before one or the other saves the spreadsheet.

Culturally I don't see the smart part number going away, but we have to address the potential for duplicates, and the easiest route I see right now, to is have the user enter DB_Part_No manually. I'm just wondering what can go wrong, as it is not Siemens preferred method.

-Dave

NX 9, Teamcenter 10

 

[NutAce]

At our company we have mixed naming rules...
We have the posibility to have the autogenerated fixed DB_Part_NO (following our auto Naming Rule "PAA@######" ) which users get when they select the "Assign" button.
And we also have a "Free hand" number with a partialy fixed naming rule like ###.###.###.### which can only contain numbers. This must be Unique or Teamcenter won't accept it (site setting).

So your desired part number rule is very well possible with Teamcenter checking for Duplicates.

Ronald van den Broek
Application Specialist
Winterthur Gas & Diesel Ltd
NX8.5.3 / TC9.1.2
HPZ420 Intel(R) Xeon(R) CPU E5-1620 0 @ 3.60GHz, 32 Gb Win7 64B
Nvidea Quadro4000 2048MB DDR5
HP EliteBook 8570W Intel(R) Core(TM) I7-3740QM CPU @ 2.70GHz, 16Gb Win7 64B

 

[Dave K]

We should be able to allow both the TC autogenerated, and user assigned variants too, then. We do have another facility that wants to use the autogenerated, but they produce fewer parts.

-Dave

NX 9, Teamcenter 10