<!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>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">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('routingadmin/quick_ref.html');return(false);">How To</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/app_overview.html');return(false);">Options</a></p>
            </td>
         </tr>
      </table><br><p class="para_topic">Routing programs aid the designer in areas in which stock (electrical stock such as wire, cable, shield or mechanical stock such as pipe, insulation) connect components (electrical components such as connectors, devices or mechanical components such as pumps, tanks, valves). The standard Routing applications available are Routing Electrical and Routing Mechanical. Your site may install one or both of these applications. If you install Routing Mechanical, you may choose to make use of Routing <b class="uiTerm">Logical</b> as well. Your site may create custom applications using a Routing application as the base.
      </p>
      <p class="para_topic">Routing Electrical provides functionality specific to the design of wiring and cabling, including conduit and cable trays. Routing Mechanical provides functionality specific to the design of piping, tubing, conduit, and HVAC systems. Routing <b class="uiTerm">Logical</b> provides methods to create a 2D diagram of a mechanical system.
      </p>
      <p class="para_topic">These three Routing applications share the majority of their functionality. The differences between the Routing applications are in one of the following categories: <b class="uiTerm">Part Libraries</b>, <b class="uiTerm">Design Rules</b>, and <b class="uiTerm">System Interfaces</b>. Managing these three areas constitute the role of the Routing Administrator.
      </p>
      <div class="title_division">System organization</div>
      <p class="para_division">The configuration of Routing applications begins with a file called an <b class="uiTerm">Application View File</b>, or APV file. There is always one APV file associated to the start up of a Routing application. The APV file determines many default values and settings used by Routing. As of NX 4, the APV file uses XML formatting only. Customers using the old text format APV files must migrate to the new XML formatted APV file, which offers significant enhancements.
      </p>
      <p class="para_division">The NX environment variable file, .ugii_env.dat, governs the location of Routing configuration files and folders. By default, all Routing files reside under the base NX installation directory, either in the directory named <code>UGROUTE_ELEC</code> or <code>UGROUTE_MECH</code>.
      </p>
      <div class="title_division">System dependencies</div>
      <p class="para_division">Routing depends on NX and the Assemblies. Other NX modules are required to perform specific operations such as the creation of drawings and clearance analysis.</p>
      <div class="title_division">Platforms</div>
      <p class="para_division">Routing applications run on platforms supported by NX. There are no special hardware or operating system requirements for the Routing programs.</p>
      <div class="title_division">Sample part libraries</div>
      <p class="para_division">Each Routing application comes with a set of sample part libraries. These libraries are examples to aid in the creation of production part libraries and not intended to be production capable. Both inch and metric versions of these part libraries are included in the standard installation.</p>
      <table border="0">
         <tr>
            <td valign="top" align="left"><img align="left" src="../graphics/note.gif" alt="Note" title="Note"></td>
            <td valign="bottom" align="left" width="100%">
               <div class="para_note">
                  <p class="para_note_body">The NX environment file, ugii_env, contains Routing environment variables that, by default, point to the metric versions of the part libraries. Follow the instructions included in the ugii_env file to switch from using the metric libraries to using the inch libraries.</p>
               </div>
            </td>
         </tr>
      </table>
      <div class="title_division">Running with Teamcenter Integration for NX</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.openFile('routingadmin/manage_team.html');return(false);">Managing Routing administrative files from Teamcenter</a> for more information.
      </p>
      <p class="para_division">The interface to Teamcenter enables run, spool, and stock information to be passed to Teamcenter through a PLM XML file. Refer to the specific Help topics for more information.</p>
      <p class="para_division">Support is now available for using the Teamcenter module named <b class="uiTerm">Classification</b>. This integration allows the use of the same part selection hierarchy as defined through <b class="uiTerm">Classification</b>. Refer to the specific Help topics for more information.
      </p>
   </body>
</html>