<!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>Disciplines</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_topic3" id="xps10_pagetitle">Disciplines</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('routingadmin/view_overview.html');return(false);">Overview</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/view_example.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/view_descrip.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('routingadmin/xml_key.html');return(false);">Related Topics</a></p>
            </td>
         </tr>
      </table><br><p class="para_topic">A discipline tailors Routing for a particular design task. You may have one discipline for piping and one for tubing, or you could have several different disciplines just for piping. The active discipline determines many things, but most importantly it determines the parts available to the user and a set of specifications. You may define as many diciplines in the APV as needed.</p>
      <p class="para_topic">A discipline contains other groups within it. Specification groups must appear within a discipline. Other groups may appear within or outside of a discipline. Sections defined within a discipline override those outside a discipline. Since you chose the active discipline, the order in which disciplines appear in the APV file serves only to define the order in which they appear for choosing (the order being the order in which they appear in the APV). If the system defines one or more disciplines in the APV, the first <b class="uiTerm">Discipline</b> defined is the default and the first <b class="uiTerm">Specification</b> defined within that <b class="uiTerm">Discipline IDs</b> the default specification.
      </p>
      <div class="title_division">Use of Disciplines </div>
      <p class="para_division">The idea of the <b class="uiTerm">Discipline</b> section is that each discipline (piping, tubing, raceway, HVAC, etc.) needs very different settings than the others. This is particularly true of characteristics, callbacks and plug-ins. Even within the same discipline, different settings are desirable (design of a high pressure piping system is very different than a gravity fed drainage system, for example). The <b class="uiTerm">Discipline </b> section of the APV provides the means to manage these differences.
      </p>
   </body>
</html>