Schematic 3D Integrator User Guide

How to Configure Build Rules : Configuration File Section by Section : Example Rule Group for SCVALV
This next example illustrates a Rule Group for schematic valves. The Source Type shown below restricts this Rule Group to being applied where the source object is of type SCVALV.
Figure 6:22.
This Rule Group has a number of nested Rule Groups. The first has a Condition that applies when the source object has a valid SPRE, denoted by being not equal to Nulref.
Here is the Condition:
This Rule Group has a Create Action that specifies the type of object to be created during a Build operation, in this case based on the attribute GTYPE of the source object.
One of the accompanying Assign Actions copies the attribute SPRE from the source object.
Figure 6:25.
The second nested Rule Group has a Condition that applies it when the source object does not have a valid SPRE, denoted by being equal to Nulref.
Here is the Condition:
This Rule Group has a further nested Rule Group that defines it as applying to source objects with particular GTYPE values.
This Rule Group also has a Create Action that specifies the type of object to be created during a Build operation, again based on the attribute GTYPE of the source object.
Figure 6:28.
The Create Action has a Selector which will be used during a Build operation to select the object from the pipe specification. It will also be compared with a severity level of warning. Each Selector has a Question and Answer. This Selector takes the STYPE from the source object’s SCSTYP attribute.
Figure 6:29.
This is accompanied by a Report Action that will output an error message in the Compare report if the flow direction is reversed.
A Report Action is used when the check required includes an expression based on 3D data, whereas an Assign Rule compares the whole value of a 3D attribute to an expression based on schematic data. The following example uses a Report Action to check a substring of a pipe name. In this example the PIPE name follows the convention Size-Fluid-Area-LineNumber and the SCPLIN name follows the convention Unit-Size-Fluid-Spec-LineNumber. To compare the Fluid requires a Report Action with Condition:
An appropriate Mismatch Report would be ‘Fluid code does not match’. If the condition evaluates false, then this message will be output in the report. Note that there is no output if it evaluates true.

1974 to current year. AVEVA Solutions Limited and its subsidiaries. All rights reserved.
AVEVA Logo