<!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>Guiding principles</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">Guiding principles</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/en_level_overview.html');return(false);">Overview</a></p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td">How To</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td"><a class="links" href="javascript:void(0)" onclick="top.openFile('routingadmin/en_level_practices.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/en_level_partdir.html');return(false);">Related Topics</a></p>
            </td>
         </tr>
      </table><br><p class="para_topic">The goals developed for the best practices for maintaining entry-level part libraries are:</p>
      <ul>
         <li>
            <p class="para_item">Minimize the number of NX part files that are required to populate a part library. Since each NX part family member generates a different part file, this means minimizing the number of family members.</p>
         </li>
         <li>
            <p class="para_item">Minimize the amount of information duplicated in the Part Tables and the NX part families.</p>
         </li>
         <li>
            <p class="para_item">Simplify the coordination of the information in the Part Tables and the associated NX part families.</p>
         </li>
         <li>
            <p class="para_item">Provide tools for maintaining individual Part Tables.</p>
         </li>
      </ul>
      <p class="para_topic">The foundations of best practices for the guiding principles are:</p>
      <ul>
         <li>
            <p class="para_item">Part Tables contain the master data for an entry-level part library. To add or change a NX part family member the associated Part Table should be changed first and then use update_fam_from_ptb to update the part family based on the master data in the Part Table.</p>
         </li>
         <li>
            <p class="para_item">To minimize the number of parts required to populate a part library, create different part family members only if there are geometric differences between the family members. Part specifications in a Part Table should reference the same NX part or part family member if the specified parts are geometrically the same. Other differences, such as material type, record as attributes on each specific occurrences of the part. This means that a NX part family table should only contain columns for a unique member name and the expressions that you use to drive the shape of the part.</p>
         </li>
         <li>
            <p class="para_item">You can maintain Part Tables with the NX spreadsheet by using ptb2ss and ss2ptb. Alternatively, the part tables may be edited directly using a text editor.</p>
         </li>
      </ul>
   </body>
</html>