Showing results for 
Search instead for 
Did you mean: 

tailor the generic classification capability in Teamcenter to my specific part-families

Siemens Creator Siemens Creator
Siemens Creator

Procedure question:

How do I tailor the generic classification capability in Teamcenter to my specific part-family business processes?


I have a customer from the past that has a procedure question, I am not a classification guy and have a question for part families and classification in TeamCenter…



               Customer has very complex part-families in Native, they can be nested 3 to 7 deep… (not recommended) but it is what it is


               They also have spreadsheets for the part-families that can be of 5 sheets , the main sheet that Nx uses but they have other sheets that drive this main sheet for arrangements due to not using TeamCenter

It was the way the company choose to mimic ‘data management’ as crewed as it may be…


Now they are using TeamCenter functionality hence Classification …


  • What would the proper process be to migrate the part families from Native into TeamCenter

                                             Do you just bulk dump the Nx part files into TeamCenter and regenerate using spreadsheet ?


  • What is the process to us classification for the part families ?
  • Is there documentation for classification and Nx part-family migration?



You can control how the callout values in the NX Parts List are synchronized with the Teamcenter database.

Synchronize Callouts

By default, the NX callout values are synchronized with the Structure Manager Find No. (previously called sequence numbers). You can change this by specifying a value for the Callout Management customer default (see Teamcenter Integration Customer Defaults for additional information). The value that you specify is the title of an NX attribute.

This attribute title must be one that is synchronized with Teamcenter (i.e., with a note type defined in the Teamcenter database whose type matches the title). If there is no note type defined that matches the title, then an error message displays the first time Teamcenter Integration needs to use the value of this default.

The attribute specified by your default never actually exists in the NX data structure. When you create an attribute with that title, the setting of the attribute is intercepted. Instead of the usual action, the attribute CALLOUT is created or edited, and you enter its value. The corresponding note type in the Teamcenter structure is synchronized with the attribute titled CALLOUT. This is because NX requires the attribute CALLOUT to be present for use with callouts on drawings.

If you have specified an attribute other than DB_SEQUENCE_NO to be the callout attribute, then the Find No. in Structure Manager and the attribute DB_SEQUENCE_NO on NX components is synchronized. This means that when you load an assembly and the structure is updated from Teamcenter, attributes with this title appear on components and can be used in the parts list.


The DB_SEQUENCE_NO attribute is entered in the Callout: Attribute Title field on the Teamcenter Integration for NX→User Attributes, All tab in the Customer Defaults dialog.

The figure below shows the mapping, by illustrating two drawings of the same assembly together with the corresponding BOM in Teamcenter. In Case 1, the callouts have been synchronized with the Find Nos. in Structure Manager. In Case 2, the callouts have been synchronized with the note DRAW_No in Structure Manager.

Be aware that in each case the attribute title CALLOUT corresponds to the required value in Structure Manager: in the first case with the Find No. field, and in the second case with the DRAW_NO note type.

Case 1:


Teamcenter Structure Manager


Structure Manager Find No.

Callout Management


Case 2:


Teamcenter Structure Manager



Callout Management



Structure Manager Find No.

Also be aware that in each case the attribute not used for the callout is held separately and its value corresponds to the appropriate Structure Manager value (DRAW_NO in the second case with note type DRAW_NO, and DB_SEQUENCE_NO in the first case with the Find No.).

Re: tailor the generic classification capability in Teamcenter to my specific part-families

Solution Partner Phenom Solution Partner Phenom
Solution Partner Phenom
I can answer a couple of your questions but not all of them...
- Part Families cannot have multiple generations. They must be single level (nesting not allowed).
- You would migrate the "parent" and then regenerate the children in Teamcenter.
- Arrangements are handled differently in Tc (special relationship) so their spreadsheet process probably won't work.

Do not bulk import until the existing FOP (family of parts) have been cleaned up. You can get into trouble very quickly. What can take hours to import can take weeks or months to delete so be careful and deliberate.

Randy Ellsworth, Teamcenter Architect, Applied CAx, LLC
NX 11 | SW 2016 | Creo 4 | TcUA 11.4
Evaluating: AW 3.4