<!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>Reference set characteristic</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">Reference set characteristic</div>
      <hr noshade="true">
      <table cellspacing="4" align="center">
         <tr valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td"><a class="links" href="javascript:void(0)" onclick="top.openFile('routingadmin/table_overview.html');return(false);">Overview</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/table_desc.html');return(false);">How To</a></p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td">Options</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td"><a class="links" href="javascript:void(0)" onclick="top.openFile('routingadmin/pt_best.html');return(false);">Related Topics</a></p>
            </td>
         </tr>
      </table><br><p class="para_topic">There is a special entry that may be included in a part table to designate the reference set to use when the part places by Routing. If a descriptor characteristic named REFERENCE_SET is defined in the part table, and a value is supplied in the row for a particular part, and the value in the row matches a predefined reference set name in the part, then the part will be loaded using the reference set in the part having the name which matches the value of this characteristic. If you do not meet any of these conditions then the part is loaded as <b class="uiTerm">Entire Part</b> (no reference set used).
      </p>
      <div class="title_division">Weight characteristic</div>
      <p class="para_division">Part Tables may contain a special characteristic called WEIGHT. For a fitting part, you can assert a mass on the occurrence of the component (see <a class="links" href="javascript:void(0)" onclick="top.popUpPage('assemblies/index.html?goto=assemblies/01topic_1.html&vars=-aux,-home','linkInter','menubar=yes,status=yes,resizable=yes,toolbar=yes,scrollbars=yes,location=no,directories=no');return(false);">Assemblies Help</a>: Weight Management) that reflects the value of the weight characteristic. For a stock part, you should assign a density to the stock body solid that reflects the weight per unit length given by the value of the weight characteristic in the part table. This holds true for both the <b class="uiTerm">Simple Style</b> display of stock and the <b class="uiTerm">Detailed Style</b> display.
      </p>
      <p class="para_division">The unit system used may be explicitly specified in the part table or implied by the units of the part. To specify the unit system, define a column named WEIGHT_UNITS and assign it a value that is one of the following:</p>
      <table bgcolor="#F0F0F0" cellpadding="2" cellspacing="4" width="95%" align="center">
         <colgroup span="1">
            <col span="1" width="43*">
            <col span="1" width="156*">
         </colgroup>
         <tr valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">KG&ndash;METERS</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">[kilogram&ndash;meters]</p>
            </td>
         </tr>
         <tr valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">GM&ndash;CMS</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">[gram centimeters]</p>
            </td>
         </tr>
         <tr valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">LB&ndash;FOOT</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">[pound foot]</p>
            </td>
         </tr>
         <tr valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">LB&ndash;INCHES</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">[pound inch]</p>
            </td>
         </tr>
      </table><br><p class="para_division">If the units system is not provided in the part table through the WEIGHT_UNITS characteristic (that is the characteristic is not defined) then the weight value is assumed to be in pound-foot for an inch part and in kilogram-meter for a millimeter part.</p>
      <p class="para_division">You can define these characteristics using the same methods as any other characteristic. The only requirement is the weight column name be WEIGHT and the units column be WEIGHT_UNITS. Since the units would probably be the same for all members of the part table, you can easily define WEIGHT_UNITS using an <b class="uiTerm">Applied Characteristic</b>. WEIGHT would be a normal column with different values for every member (for reference, weight is a column in the piping sample part table files).
      </p>
      <p class="para_division">An example of the weight units applied characteristic is as follows:</p><pre class="indent">APPLIED
			NAME			WEIGHT_UNITS
			FORMAT		LB-INCHES
END_OF_APPLIED</pre><p class="para_division">The entry on the COLUMNS for the weight characteristic would be:</p><pre class="indent">COLUMNS
		REAL/HIDE			WEIGHT
END_OF_COLUMNS</pre><p class="para_division">To measure the weight of a wiring or piping assembly, use <b class="uiTerm">Analysis&rarr;Measure Bodies</b>.
      </p>
      <div class="title_division">Minimum bend radius of wires</div>
      <p class="para_division">A new column in the wires part table (PTB) file called MIN_BEND_RADIUS can be defined to specify the minimum bend radius for each type of wire.</p>
      <p class="para_division">Once minimum bend radius has been specified, <b class="uiTerm">Design Rule Checks</b> will automatically find any point on any path that is too tight for the wires. In addition, a bundle will be constrained by the largest minimum bend radius of all the wires in the bundle.
      </p>
      <p class="para_division">An example follows:</p><pre class="indent">COLUMNS
		REAL				GAUGE
		STRING			TYPE
		REAL/HIDE		OD
		STRING/HIDE	PART_NUMBER
		STRING/HIDE	STOCK_KEY
		REAL/HIDE		MIN_BEND_RADIUS
END_OF_COLUMNS

DATA
!
!GAUGE		TYPE		OD		PART_NUMBER		STOCK_KEY		MIN_BEND_RADIUS
!
1		&rdquo;TXL&rdquo;		9.346		&rdquo;W-01&rdquo;			&rdquo;wire01&rdquo;		30.000</pre><div class="title_division">Symbol part name characteristics</div>
      <p class="para_division">For the Routing Logical program, the 3D parts are associated with a symbol part file by assigning the characteristic SYMBOL_PART_NAME. You can assign this characteristic by declaring the characteristic in the Columns and providing a value for each entry in the table or you can assign it as an <b class="uiTerm">Applied Characteristic</b>, so that all entries use the same symbol.&nbsp;You can find examples in the sample part tables provided.
      </p>
      <p class="para_division">When you select a particular part for placement and the Routing Logical program is active, the symbol part is loaded rather than the 3D part. All characteristics normally be assigned to the 3D part in the Routing Mechanical program are assigned to the symbol component in the Routing Logical work part.</p>
      <div class="title_division">Stock display characteristics</div>
      <p class="para_division">The color of a stock may be specified by including color, either in the part table columns or as an <b class="uiTerm">Applied Characteristic</b> (if all stock in the table is to have the same color). The string value of the color characteristic must match the name of a color in the session's <b class="uiTerm">Color Definition File</b> (CDF). If the stock color value does not match, the default object creation color is used. For wire stock, the color of the wire is used to display the wire when only one wire is routed along a path (including terminal wires). When more than one wire is routed, causing a bundle solid to be generated, the bundle color, defined in <b class="uiTerm">User Preferences</b>, is applied to the bundle stock solid body.
      </p>
      <p class="para_division">You can specify CGM and pattern files in the part table for the symbolic representation of stock.&nbsp;If you specify both in the part table, the order of precedence is the CGM file.&nbsp;If you only specify one, the system will use that file. The following is an example part table file showing COLOR, CGM_FILE,and PATTERN_FILE characteristics defined in Columns. Each row of the table would then provide values for these characteristics.</p><pre class="indent">COLUMNS
			STRING/HIDE			MEMBER_NAME
			REAL						DIAMETER
			REAL/HIDE				WALL_THK
			REAL/HIDE				WEIGHT
			STRING					MATERIAL

			STRING/HIDE			PART_NUMBER
			STRING/HIDE			PART_NAME
			STRING/HIDE			COLOR
			STRING/HIDE			CGM_FILE
			STRING/HIDE			PATTERN_FILE
END_OF_COLUMNS</pre><div class="title_division">Overstock part table requirements</div>
      <p class="para_division">Part tables that define overstock have two requirements. First, you must define the characteristic OVERSTOCK_TYPE and have a value of one of the four following values: <b class="uiTerm">Wrapped</b>, <b class="uiTerm">Flagged</b>, <b class="uiTerm">Sleeved</b>, or <b class="uiTerm">Fixed</b>. You can find a description of these types in <a class="links" href="javascript:void(0)" onclick="top.popUpPage('routingtools/index.html?goto=routingtools/title_page.html&vars=-aux,-home','linkInter','menubar=yes,status=yes,resizable=yes,toolbar=yes,scrollbars=yes,location=no,directories=no');return(false);">Routing Tools Help</a>: Stock.
      </p>
      <p class="para_division">The second requirement supplies values by the part tables that determine the size of the overstock. For additive overstock, which includes wrapped, flagged, and sleeved types, you must define a real valued characteristic titled THICKNESS. These types adopt the outer diameter (or cross-section if not round) of the stock the overstock is covering as the inner diameter of the overstock and adds the given thickness to determine the outer diameter (or outer cross-section if not round).</p>
      <p class="para_division">For fixed overstock (meaning it has a fixed cross-section), real values for any two of the three following characteristics must be defined: OD, ID, and THICKNESS (or synonyms of them). Given any two of these values the system will calculate the third, and assumes a round cross-section.</p>
      <p class="para_division">If a fixed cross-section overstock is not round then you must reference a part file containing the cross-section curves in the part table (see <a class="links" href="javascript:void(0)" onclick="top.popUpPage('routingtools/index.html?goto=routingtools/title_page.html&vars=-aux,-home','linkInter','menubar=yes,status=yes,resizable=yes,toolbar=yes,scrollbars=yes,location=no,directories=no');return(false);">Routing Tools</a>: Quality Part).
      </p>
      <p class="para_division">Examples of overstock part tables are found in the wiring and piping sample part tables.</p>
      <div class="title_division">DB_PART_NO characteristic</div>
      <p class="para_division">An issue exists with generating a proper Bill of Materials in Teamcenter (a BOM View) when using Routing. In <b class="uiTerm">Legacy Stock</b> mode, the stock in a routing assembly is not a component so it does not appear in the BOM view. A typical BOM View generation adds the components of an assembly, excluding stock in the case of a routing part.
      </p>
      <p class="para_division">However, as explained in the Teamcenter Integration Help topic NX to Teamcenter, an entry in the NX parts list can generate an item in the Teamcenter BOM view even if a component is not associated to that entry in the NX parts list. The requirement for this to happen is that you define a particular field for the parts list entry named DB_PART_NO, and that item is defined in Teamcenter.</p>
      <p class="para_division">This can be set up in Routing by including the characteristic DB_PART_NO in the stock part table. You must also define this field in the parts list format. Then Routing assigns this attribute to the stock as a Routing characteristic, generating the parts list using the Routing BOM function adds the stock to the parts list, and then Teamcenter adds the entry into the BOMview (provided the value of DB_PART_NO is found to be a defined item in Teamcenter).</p>
      <div class="title_division">Environment</div>
      <table bgcolor="#F0F0F0" cellpadding="2" cellspacing="4" width="95%" align="center">
         <colgroup span="1">
            <col span="1" width="70*">
            <col span="1" width="129*">
         </colgroup>
         <tr valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td"><code>UGII_EPLIB_TABLE_PATH</code></p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">Specifies the directories for Routing to find table files. Usually Part Table files are named with a .ptb suffix.</p>
            </td>
         </tr>
         <tr valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td"><code>UGII_ROUTING_PART_PATH</code></p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">Specifies the directories for Routing to find part files for the base Routing program.</p>
            </td>
         </tr>
         <tr valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td"><code>UGII_ELEC_PART_PATH</code></p>
               <p class="para_td"><code>UGII_MECH_PART_PATH</code></p>
               <p class="para_td"><code>UGII_LGCL_PART_PATH</code></p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">Specifies the directories for Routing to find part files for the respective Routing program.</p>
            </td>
         </tr>
      </table><br><p class="para_division">* The available Routing program names are Routing Mechanical, Routing Electrical, and Routing Logical.</p>
   </body>
</html>
