<!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>Qualify Part (Routing Electrical-specific) overview</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">Qualify Part (Routing Electrical-specific) overview</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('routingtools/wiring_ext_length_engage.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/wiring_as_example.html');return(false);">Related Topics</a></p>
            </td>
         </tr>
      </table><br><p class="para_topic"><b class="uiTerm">Qualify Part</b> is used to add information to a component part by all Routing applications. This section presents considerations specific to Routing Electrical. For general information, see <a class="links" href="javascript:void(0)" onclick="top.openFile('routingtools/parts_quality.html');return(false);">Quality Parts</a>.
      </p>
      <p class="para_topic"><b class="uiTerm">Qualify Part</b> the addition of Routing specific intelligence to a part file. This intelligence dictates how that part places into a routing assembly, how it relates to other parts in the routing assembly, and how it behaves during routing operations. <b class="uiTerm">Qualify Part</b> provides the exclusive interface for creating Routing specific objects in a part file that carry this intelligence. These objects are ports, anchors, terminals, built-in paths and cross section curves.
      </p>
      <div class="title_division">Using Qualify Part for Routing Electrical</div>
      <p class="para_division">For Routing Electrical, qualifying a part includes creating ports and assigning characteristics within the part in order to manage the electrical connectivity information as well as mechanical connectivity information.</p>
      <p class="para_division">Routing Electrical uses multiports, with virtual ports and terminal ports, to carry electrical connectivity information for the component. These ports create in <b class="uiTerm">Qualify Part</b>. A multiport allows you to define a single physical location point to represent and associate many logical connections. Establish virtual ports by associating Unique IDs to a multiport, representing logical connections. The multiport provides the physical connection location of a virtual port. A virtual port becomes a terminal port when a separate physical location point is established.
      </p>
      <p class="para_division">The logical association between the multiport and a terminal port, with the terminal Port being dependent on its multiport, remains intact and allows Routing Electrical to automate the process of creating terminal wires through <b class="uiTerm">Create Terminals</b>. Terminal ports define by reference to an instance array, both circular and rectangular. Terminal ports defined by instance arrays are useful when qualifying connectors with many pins. 
      </p>
      <p class="para_division">Below are descriptions of Routing specific objects as they relate to Routing Electrical.</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">Anchors</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">Use anchors as physical connection location points when adding the device to the assembly using the <b class="uiTerm">Place Part</b> function. You can create anchors at obvious mounting points such as the center of a connector or the corner of a mating face in order to use <b class="uiTerm">Place Part</b> to add the component to the assembly. Electrical components may be added using standard Assemblies tools, in which case you do not need anchors.
               </p>
            </td>
         </tr>
         <tr valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">Ports</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">Use ports to define a single, physical connection location points. For Routing Electrical, we recommend that standard ports be used to identify connections between devices and connectors. When routing to standard ports, you must create separate paths to each port individually to establish connectivity. For that reason, we do not recommend using standard ports to represent terminal pins.</p>
            </td>
         </tr>
         <tr valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">Multiports</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">A multiport creates to multiple logical connections using a single connection object. The multiport represents a collection of logical connections by maintaining a list of unique identifiers. You only need to create one path to establish all the logical connectivity to the unique identifiers (pins) of the component (typically a connector).</p>
            </td>
         </tr>
         <tr valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">Virtual Ports</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">If you do not define a terminal port for a unique ID included in the multiport list, then the system considers it a virtual port, since it has no physical definition. Virtual ports enable a logical connection to the component defined by the multiport without requiring a separate physical location for each connection.</p>
            </td>
         </tr>
         <tr valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">Terminal Ports</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1" valign="top">
               <p class="para_td">Terminal ports define a physical point of connection for one unique ID included in a multiport terminal list. You must define terminal ports to take advantage of the <b class="uiTerm">Create Terminals</b> feature.
               </p>
            </td>
         </tr>
      </table><br><div class="title_division">Route Part type</div>
      <p class="para_division">Electrical part types can be connector, device, or splice.</p>
   </body>
</html>