Rule Evaluation Order for Pipe Ancillary Rule Sets

The order of rules in a rule set is significant, as the first one to return a result is used. This means that rules that appear later in the list may not be evaluated in some cases. See the following example for more insight into how rule order and rule set IDs are used to narrow down ancillary selection.

Example

Rule set /MDS-RULES-RLSET provides three examples of rules that return rule set IDs:

1. Rule MDS-RULES-RLSET-SYSTEM/R1 uses a pipe naming convention to make a selection based on specific criteria, such as system, or any other project-defined attributes embedded in the pipe name:

   

2. Rule MDS-RULES-RLSET-PIPE-SPEC/R1 uses pipe specification to make a selection:

   

3. Rule MDS-RULES-RLSET-DESIGN-AREA/R1 uses design area (in this case the zone) to make a selection:

   

In each case, if the rule is evaluated as true, the resulting rule set ID is used to narrow down the rules used for ancillary selection.