<!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>Standard assembly structure</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">Standard assembly structure</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/logical_over.html');return(false);">Overview</a></p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td">Options</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td"><a class="links" href="javascript:void(0)" onclick="top.openFile('routingtools/electrical_scheme.html');return(false);">Related Topics</a></p>
            </td>
         </tr>
      </table><br><p class="para_topic">A Routing Logical diagram is an assembly. Each symbol is a component, manageable by standard assembly operations. Symbols are connected by routing segments, to which stock may be assigned as component stock pieces. Standard NX parts list may then be generated.</p>
      <div class="title_division">2 1/2 D diagramming</div>
      <p class="para_division">Routing Logical creates diagrams in true 3D space (NX modeling space), which allows different symbols to be placed at different Z values.&nbsp;True modeling geometry can be used as background referenced geometry (scaled if necessary) to produce a topological diagram, where symbols are located relative to the product structure.</p>
      <div class="title_division">Drawing creation</div>
      <p class="para_division">The process of creating a drawing from a <b class="uiTerm">Logical</b> diagram is the same as for an NX assembly drawing. Using the Drafting module, a view of the <b class="uiTerm">Logical Assembly</b>, typically the TOP view, is placed onto a drawing sheet. Standard drawing template and annotation tools are then available.
      </p>
      <div class="title_division">Special annotation tools</div>
      <p class="para_division">Annotation tools, beyond the standard Drafting tools, are made available to support diagram creation. One, called <b class="uiTerm">Tabular Label</b>, is delivered as a Drafting tool but was developed for diagram creation. <b class="uiTerm">Tabular Label</b> allows a label (a note with a leader) to be comprised of a table, with column or row names, with the boxes dynamically populated by the values of attributes of any modeling object. Formats may be created on-the-fly or standard formats may be saved and retrieved.
      </p>
      <p class="para_division">The other annotation tools, <b class="uiTerm">Logical Label</b> and <b class="uiTerm">Run Note</b> are Routing specific. These two tools are implemented by a Routing <b class="uiTerm">Place Part</b> callback, so they may be modified. Please see <a class="links" href="javascript:void(0)" onclick="top.popUpPage('routingadmin/index.html?goto=routingadmin/implement_callbacks.html&vars=-aux,-home','linkInter','menubar=yes,status=yes,resizable=yes,toolbar=yes,scrollbars=yes,location=no,directories=no');return(false);">Routing Systems Configuration Guide &ndash; Callbacks and Plug&ndash;ins</a> for further information.
      </p>
      <p class="para_division"><b class="uiTerm">Logical Label</b> places a label automatically after a symbol is placed, with the text of the note being populated by the value of the characteristic REFERENCE_ID assigned to the occurrence of the symbol part. The symbol is required to contain a point named NOTE_ORIGIN and a point named LEADER_ORIGIN.&nbsp;If either of these points do not exist, or the symbol does not have the characteristic REFERENCE_ID, then a note is not placed.
      </p>
      <p class="para_division"><b class="uiTerm">Run Note</b> automatically places notes along the segments belonging to a run when the run is defined. The only requirement for this functionality is that the program be properly configured.
      </p>
      <div class="title_division">Run Navigator</div>
      <p class="para_division">A new navigator provides intuitive interaction with defined runs.&nbsp;Creation, management, editing, and deletion of runs are all performed through the <b class="uiTerm">Run Navigator</b> interface. The <b class="uiTerm">Run Navigator</b> options are identical in the Routing Mechanical and Routing Logical applications. The <b class="uiTerm">Navigator</b> is similar in many respects to the <b class="uiTerm">Assembly Navigator</b>, which is familiar to most users of NX.
      </p>
      <div class="title_division">Run types</div>
      <p class="para_division">Routing Logical provides the capability of assigning line font, width, and color based on an assigned <b class="uiTerm">Run Type</b>. Custom configuration allows customers to define the types of runs available (such as Piping, Instrumentation, HVAC, and so on). As a run is defined during diagram creation, you select the <b class="uiTerm">Run Type</b>. The <b class="uiTerm">Run Type</b> has a predefined <b class="uiTerm">Line Style</b> associated to it, which immediately adjusts the line font, width, and color accordingly.
      </p>
      <div class="title_division">Run definition</div>
      <p class="para_division">A highly intelligent method of defining a run, often called a <b class="uiTerm">Pipe Line</b> in piping applications, is available for both the Routing Mechanical and the Routing Logical modules. You only need to identify the <b class="uiTerm">From Items</b> and the <b class="uiTerm">To Items</b> of the run. The system then identifies all members of the run based on the connectivity of the model. An attribute is assigned to each member item, available for any downstream applications that may require such identification.
      </p>
      <div class="title_division">Flow direction</div>
      <p class="para_division">The direction of flow in a run is ascertained from the definition of the run, being always away from a <b class="uiTerm">From Item</b> and towards a <b class="uiTerm">To Item</b>. If flow cannot be determined automatically for certain portions of a run, a user interface allows manual assignment.&nbsp;<b class="uiTerm">Flow Direction</b> arrow annotations are then easily added to a diagram.
      </p>
   </body>
</html>
