<!DOCTYPE html
  PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

<!--
Copyright (c) 2006 UGS Corp.

All Rights Reserved.

This software and related documentation are proprietary to UGS Corp.
-->
<html>
   <head>
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <title>Teamcenter Classification set-up</title>
      <script language="javaScript">
        abridged="false";
        displayConditions=new Array();
      </script>
      <link type="text/css" href="../css/main_styles.css" rel="stylesheet">
   </head>
   <body class="bodydocs" onload="top.pageLoader()" bgcolor="#FFFFFF">
      <div class="title_topic2" id="xps10_pagetitle">Teamcenter Classification set-up</div>
      <hr noshade="true">
      <table cellspacing="4" align="center">
         <tr valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td">Overview</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td"><a class="links" href="javascript:void(0)" onclick="top.openFile('routingadmin/team_views.html');return(false);">Options</a></p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td"><a class="links" href="javascript:void(0)" onclick="top.openFile('routingadmin/team_admin.html');return(false);">Related Topics</a></p>
            </td>
         </tr>
      </table><br><p class="para_topic">Routing contains functionality for specifying a placement item through <b class="uiTerm">Teamcenter Classification</b> (an add-on to Teamcenter versions 8, 9 or 10). This topic describes how to set up Routing to work with <b class="uiTerm">Classification</b> to select parts. Familiarity with <b class="uiTerm">Classification</b> is assumed.
      </p>
      <div class="title_division">Hierarchy</div>
      <p class="para_division">The routing stock and fitting items should be separated from the other classification data. To do this, simply create a group at the <b class="uiTerm">Classification Root</b> node.
      </p>
      <p class="para_division">The <b class="uiTerm">Disciplines</b> structure, defined in the Routing APV file, allows for the creation of specialized sub-applications. These sub-applications can be general (for example piping), or specific (high pressure tubing). <b class="uiTerm">Disciplines</b> have the ability of specifying the root nodes for stocks and fittings. If the Routing Classification data is organized around the disciplines, placement of parts and assignment of stocks is greatly improved.
      </p>
      <p class="para_division">In Routing the administrator can specify a <b class="uiTerm">Discipline</b> called <em>High Pressure Tubing</em>. Part of the definition of the Discipline would specify that the Start_Stock_Node is <em>High Pressure Tubing Stock</em> and that the Start_FItting_Node is <em>High Pressure Tubing Fittings</em>. When in the Routing application the nodes above the start nodes are not displayed for that discipline.
      </p>
      <div class="title_division">Attributes</div>
      <p class="para_division">All attributes specified in <b class="uiTerm">Classification</b> for an item are applied to the item when it is placed. So any attributes that are used for design rule checking, bill of materials, and so on, should be specified in <b class="uiTerm">Classification</b>.
      </p>
      <p class="para_division">When specifying Classification attributes there are several things to keep in mind. Routing only uses the <b class="uiTerm">Name</b> and <b class="uiTerm">Format</b> dynamic input boxes. The <b class="uiTerm">Format</b> dynamic input box used is dependant on the units of the class, Format 1 is used for metric classes and Format 2 is used for inch classes. No unit conversions are performed by Routing during attribute assignments.
      </p>
      <p class="para_division">Real, integer, and string classification attributes are converted to their corresponding NX attribute types. LOV classification attributes are converted to string NX attributes. Arrays of attributes and date attributes are not supported.</p>
      <p class="para_division">There are several attributes that the Routing application uses for specific purposes. Some of these attributes are generated on-the-fly during retrieval of classification data.</p>
      <table bgcolor="#F0F0F0" border="" cellpadding="2" cellspacing="4" width="95%" align="center">
         <colgroup span="1">
            <col span="1" width="99*">
            <col span="1" width="100*">
            <col span="1" width="100*">
         </colgroup>
         <tbody>
            <tr bgcolor="#C0C0C0">
               <td colspan="1" rowspan="1">
                  <p class="para_td"><b class="uiTerm">Attribute Name</b></p>
               </td>
               <td colspan="1" rowspan="1">
                  <p class="para_td"><b class="uiTerm">Description</b></p>
               </td>
               <td colspan="1" rowspan="1">
                  <p class="para_td"><b class="uiTerm">Notes</b></p>
               </td>
            </tr>
            <tr>
               <td colspan="1" rowspan="1">
                  <p class="para_td"><code>PART_NAME</code></p>
               </td>
               <td colspan="1" rowspan="1">
                  <p class="para_td">Specifies the name of a part. This attribute is used to load the part for either <b class="uiTerm">Stock Assignment</b> or <b class="uiTerm">Place Part</b>. For part family parts, the Part Name is the template part.
                  </p>
               </td>
               <td colspan="1" rowspan="1">
                  <p class="para_td">The Routing Classification retrieval program automatically adds this attribute. The generated PART_NAME is the <b class="uiTerm">Item Name</b>. <em>DO NOT ADD</em> this attribute in <b class="uiTerm">Classification</b>.
                  </p>
               </td>
            </tr>
            <tr>
               <td colspan="1" rowspan="1">
                  <p class="para_td"><code>MEMBER_NAME</code></p>
               </td>
               <td colspan="1" rowspan="1">
                  <p class="para_td">The name of a part family member part. The entry must have a corresponding PART_NAME attribute that specifies the template part for this member.</p>
               </td>
               <td colspan="1" rowspan="1">
                  <p class="para_td">The Routing <b class="uiTerm">Classification</b> retrieval program automatically adds this attribute as well. The generated MEMBER_NAME is the Item ID. <em>DO NOT ADD</em> this attribute to <b class="uiTerm">Classification</b>.
                  </p>
               </td>
            </tr>
            <tr>
               <td colspan="1" rowspan="1">
                  <p class="para_td"><code>PART_NUMBER</code></p>
               </td>
               <td colspan="1" rowspan="1" valign="top">
                  <p class="para_td">Specifies an identifier for the type of part. The PART_NUMBER is used to differentiate parts and is very similar to the Item ID in Teamcenter . However. a single part file can have multiple entries in the part table data with different PART_NUMBER attributes. This allows for the reuse of parts in cases where the geometry is the same but other data (such as MATERIAL) are the only variant.</p>
               </td>
               <td colspan="1" rowspan="1">
                  <p class="para_td">The PART_NUMBER attribute can be specified in <b class="uiTerm">Classification</b>. If it is not specified as a <b class="uiTerm">Classification</b> attribute, it is automatically added by the retrieval program and it's value is always the Item ID.
                  </p>
               </td>
            </tr>
            <tr>
               <td colspan="1" rowspan="1">
                  <p class="para_td"><code>SYMBOL_PART_NAME</code></p>
               </td>
               <td colspan="1" rowspan="1">
                  <p class="para_td">Specifies the name of the part to use for representation of the part in the Routing <b class="uiTerm">Logical</b> application. When placing parts in the Routing <b class="uiTerm">Logical</b> application the SYMBOL_PART_NAME part is placed instead of the Item.
                  </p>
               </td>
               <td colspan="1" rowspan="1">
                  <p class="para_td">This is a new attribute for NX 2 Ship. It is recommended that the customer add this for all parts that might be used in the Routing <b class="uiTerm">Logical</b> application.
                  </p>
               </td>
            </tr>
            <tr>
               <td colspan="1" rowspan="1">
                  <p class="para_td"><code>WEIGHT</code></p>
               </td>
               <td colspan="1" rowspan="1">
                  <p class="para_td">Specifies the unit weight for stock. This is used during stock assignment to automatically assign a density to the stock body for an accurate mass calculation. The default unit weight for stock qualified in a metric part is kilograms/meter, and pounds/foot for inch parts.</p>
               </td>
               <td colspan="1" rowspan="1">
                  <p class="para_td">Applying this column for stocks is highly recommended that you apply this column fir sticks if using the <b class="uiTerm">Mass Calculation</b> functionality in NX.
                  </p>
               </td>
            </tr>
            <tr>
               <td colspan="1" rowspan="1">
                  <p class="para_td"><code>WEIGHT_UNITS</code></p>
               </td>
               <td colspan="1" rowspan="1">
                  <p class="para_td">Specifies the units of the WEIGHT column. Valid values are:</p>
                  <p class="para_td">KG&ndash;METERS</p>
                  <p class="para_td">GM&ndash;CMS</p>
                  <p class="para_td">LB&ndash;FOOT</p>
                  <p class="para_td">LB&ndash;INCHES</p>
               </td>
               <td colspan="1" rowspan="1">
                  <p class="para_td">This attribute is optional. The KEY&ndash;LOV feature would be very useful for this attribute type.</p>
               </td>
            </tr>
            <tr>
               <td colspan="1" rowspan="1">
                  <p class="para_td"><code>ELBOW_ANG</code></p>
               </td>
               <td colspan="1" rowspan="1">
                  <p class="para_td">Elbow angle value. Used by the <b class="uiTerm">Auto&ndash;Elbow</b> placement routing during <b class="uiTerm">Create Path</b> and by the <b class="uiTerm">Cut Elbow</b> functionality.
                  </p>
               </td>
               <td colspan="1" rowspan="1">
                  <p class="para_td">The column is required for the proper use of elbows. Adding this column to all classes that specify elbows is highly recommended.</p>
               </td>
            </tr>
         </tbody>
      </table><br><p class="para_division">All attributes in your classification for stock should be made mandatory so that they will have valid values when applied in the Routing program.</p>
   </body>
</html>