<!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>Rules</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">Rules</div>
      <hr noshade="true">
      <p align="left"><img align="bottom" src="graphics/rules.gif"></p>
      <p class="para_topic"><b class="uiTerm">Rules</b> checks a Piping and Instrumentation Diagram against a specified set of rules. If a violation is detected, its place is marked and message gives you the reason behind the violation. You can suppress the message dialog box at any time.
      </p>
      <p class="para_topic">The details for checking the rules are defined by means of User_Preferences in the Routing Logical Application View file by specifying the following:</p>
      <ol type="1" start="1">
         <li>
            <p class="para_item">Name of an attribute (for example, MEMBER_NAME), the absence of which denotes a component as being universal.</p>
         </li>
         <li>
            <p class="para_item">A constant prefix in the names of one or more attributes holding the nominal sizes of a component or the one holding the nominal sizes of a stock (for example, DN for DN1, DN2, and so on).</p>
         </li>
         <li>
            <p class="para_item">A constant prefix in the names of ports (for example, C for C1, C2, and so on).</p>
         </li>
         <li>
            <p class="para_item">Names of attributes for which all members of a run must have the same value.</p>
         </li>
         <li>
            <p class="para_item">Names of attributes for which certain components with the same type of counter (see <a class="links" href="javascript:void(0)" onclick="top.openFile('routingtools/counter.html');return(false);">Counter</a>) must have the same value.
            </p>
         </li>
         <li>
            <p class="para_item">Some information about the size of the violation marker.</p>
         </li>
      </ol>
      <p class="para_topic">Routing Logical allows you to choose a rule and start the check. You can:</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 numbers refer to the preferences in the list above.</p>
               </div>
            </td>
         </tr>
      </table>
      <ul>
         <li>
            <p class="para_item">Check for components and stock that do not belong to a run and do not represent the start or end of a run.</p>
         </li>
         <li>
            <p class="para_item">Check for components that belong to the same run and have different values for certain attributes (4).</p>
         </li>
         <li>
            <p class="para_item">Check for components that belong to the same type of counter (see <a class="links" href="javascript:void(0)" onclick="top.openFile('routingtools/counter.html');return(false);">Counter</a>) and do not have unique values in the respective counter attributes If (5) is given, the values in the counter attributes must be unique only in combination with the values of attributes given by (5).
            </p>
         </li>
         <li>
            <p class="para_item">Check for ports, the names of which start with a certain string (3), followed by a number and which do not connect to a stock and check for stocks that do not connect to a port, the name of which starts with a certain string (3), followed by a number.</p>
         </li>
         <li>
            <p class="para_item">Check connected ports with mismatching nominal sizes (name nominal size attribute given by a certain string (5), followed by a number).</p>
         </li>
         <li>
            <p class="para_item">Check for labels (see <a class="links" href="javascript:void(0)" onclick="top.openFile('routingtools/label.html');return(false);">Label</a>) that refer to attributes which no longer exist. No violation marker is created and a default value is placed in the label instead).
            </p>
         </li>
         <li>
            <p class="para_item">Check for auxiliary attributes that are no longer referenced by labels (see <a class="links" href="javascript:void(0)" onclick="top.openFile('routingtools/label.html');return(false);">Label</a>) and remove them.
            </p>
         </li>
      </ul>
      <div class="figure">
         <p align="center"><img align="bottom" src="graphics/rlo.gif"></p>
      </div>
      <div class="title_figure">Rule violation marker example</div>
      <p class="para_topic">The <b class="uiTerm">Rules</b> feature can be accessed in Routing Logical under <b class="uiTerm">Analysis&rarr;Design Rules&rarr;Routing Logical</b>.
      </p>
   </body>
</html>