<!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>Routing Electrical 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_topic2" id="xps10_pagetitle">Routing Electrical 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/preferences_elec_wiring_preference.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_wire_connect_list.html');return(false);">Related Topics</a></p>
            </td>
         </tr>
      </table><br><p class="para_topic">The Routing Electrical program allows you to quickly define assemblies placed around and through other NX assemblies. These subassemblies typically define the systems that provide power or signals, deliver fluids, dispose of waste, provide structural support, or enable general access to the devices in the assembly. For example, within an aircraft engine pipes and tubes are routed from the fuel tanks to various injection points around the engine or, within an automobile, wiring is required to supply power to the electric windows (and many other things, as well).</p>
      <p class="para_topic">Routing provides the tools to define the paths through the assembly, to assign stock (such as pipes and tubes) to these paths, and to place standard parts (such as tees and elbows) to connect the various pieces of stock in the overall assembly.</p>
      <p class="para_topic">Routing also provides various editing functions to modify an existing routing assembly by moving or editing the paths and moving or removing the standard parts. You can extend the base functionality provided by Routing into different areas to create process specific applications in order to provide industry specific knowledge, support and automation. For the Routing Electrical application, Routing supplies the interface to work with a connection list to define wire connectivity and a component list to identify the components for wires connection.</p>
      <div class="title_division">System organization</div>
      <p class="para_division">Routing is a common foundation that is the prerequisite for all Routing applications. The current process specific routing applications are Routing Mechanical and Routing Electrical. You can purchase these standard applications separately and customized to meet a specific user's needs, or customers may develop their own routing applications using either Routing module. This Help system documents the base capabilities, which are available to both Routing applications. To access the applications, choose <b class="uiTerm">Applications&rarr;Routing Electrical</b>. Each of the applications has its own Help system.
      </p>
      <div class="title_division">System dependencies</div>
      <p class="para_division">Routing depends on NX and Assemblies. Other NX modules are required to perform specific operations such as the creation of drawings and clearance analysis.</p>
      <div class="title_division">Running with Teamcenter Integration</div>
      <p class="para_division">Routing will run with Teamcenter Integration. You must import all part library parts into the database. Other routing files (application view, part library view, rlist configuration file, and so on) may be imported into the Teamcenter database as well. See <a class="links" href="javascript:void(0)" onclick="top.popUpPage('routingadmin/index.html?goto=routingadmin/manage_team.html&vars=-aux,-home','linkInter','menubar=yes,status=yes,resizable=yes,toolbar=yes,scrollbars=yes,location=no,directories=no');return(false);">Managing Routing administrative files from Teamcenter</a> in for more information.
      </p>
      <p class="para_division">The Routing <b class="uiTerm">Bill of Materials</b> may be set up to generate items in a Teamcenter <b class="uiTerm">BOM View</b> for stock. For more information on setting this up refer to <a class="links" href="javascript:void(0)" onclick="top.popUpPage('routingadmin/index.html?goto=routingadmin/title_page.html&vars=-aux,-home','linkInter','menubar=yes,status=yes,resizable=yes,toolbar=yes,scrollbars=yes,location=no,directories=no');return(false);">Routing Systems</a>: Configuration Guide &ndash; Part Table Files, which explains the characteristic DB_PART_NO.
      </p><a class="endOfDocLinks" href="introduction_elec_ntro_pltforms.html">Platforms</a><br></body>
</html>
