<!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>Engagement value definition</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_topic4" id="xps10_pagetitle">Engagement value definition</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('routingtools/parts_overview.html');return(false);">Parts 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('routingtools/parts_toolbar.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('routingtools/parts_quality.html');return(false);">Related Topics</a></p>
            </td>
         </tr>
      </table><br><p class="para_topic">Routing looks in several places for the value to use for engagement, in the following order:</p>
      <ol type="1" start="1">
         <li>
            <p class="para_item">An ENGAGE characteristic defined on the port in the routing assembly work part (port occurrence).</p>
         </li>
         <li>
            <p class="para_item">An ENGAGE characteristic found on the port within the piece part component (port prototype).</p>
         </li>
         <li>
            <p class="para_item">An ENGAGE characteristic defined on the occurrence of the piece part in the routing assembly work part (component occurrence).</p>
         </li>
         <li>
            <p class="para_item">An ENGAGE characteristic defined as a part attribute within the piece part.</p>
         </li>
         <li>
            <p class="para_item">The engagement value defined on the port in the piece part via the <b class="uiTerm">Qualify Part</b> dialog box (which may be zero).
            </p>
         </li>
      </ol>
      <p class="para_topic"><em>Some notes of interest:</em></p>
      <ul>
         <li>
            <p class="para_item">The engagement value can be defined via a standard modeling expression and therefore may use the full power of expression definition, for example, if ... then ... else, to define an appropriate value.</p>
         </li>
         <li>
            <p class="para_item">If you define an ENGAGE characteristic for the port, you may define it as a REFERENCE. This means that the value of the ENGAGE characteristic is the name of a characteristic attached to the part (via the part table). For example, you can define a port characteristic ENGAGE that is of type REFERENCE that has a value ENGAGE_1. When Routing needs to get the value of the port ENGAGE, it will look up the value of the part's ENGAGE_1 value and use that.</p>
         </li>
         <li>
            <p class="para_item">The use of the ENGAGE characteristics to override the port defined value may be disabled. If the environment variable UGII_ROUTING_SKIP_ENGAGE_CHARX is defined to be TRUE, the system does not search for port engage characteristics. This can significantly improve the performance of the <b class="uiTerm">Place Part</b> operations.
            </p>
         </li>
      </ul>
   </body>
</html>