Schematic 3D Integrator
User Guide
How to Configure Build Rules : Configuration File Section by Section : Example Rule Group for SCEQUI
The following examples illustrate some Rules under a particular Rule Group defined for schematic equipment.
|
Figure 6:12.
|
Within this Rule Group there is one Create Action. This defines the type of object to be created during a Build operation, in this case EQUI. The Variant Count is 1, which means that the Compare operation will always check for an EQUI.
|
Figure 6:13.
|
There are several Assign Actions. This one assigns a value to the attribute POS on the target object, taking that value from the POS attribute of the source object. The Build Action is set and the Compare Action is ignore. These options and their alternatives are described in more detail below.
|
Figure 6:14.
|
The Assign Action has several properties. Name is optional. Variants Count has been described above. Attribute Name is the name of the attribute to be set on the target. Attribute Value is an expression to generate the value for the target attribute, and can contain references to source. For build rules it should not contain references to target as this will be undefined at build time.
|
•
|
Assignee is the object that has the attribute whose value is being set or compared. Allowable entries are:
|
|
•
|
target - the target object in 3D, this is the usual setting
|
|
•
|
owner - the owing ZONE in 3D, described below in the example for NAME
|
|
•
|
root - the owning SITE in 3D, described below in the example for NAME
|
|
Figure 6:15.
|
|
•
|
Build Action is the action carried out during a Build operation. Allowable entries are:
|
|
•
|
set - set the value of the attribute
|
|
•
|
ignore - do not set the value of the attribute
|
|
Figure 6:16.
|
|
•
|
Compare Action is the action carried out during a Compare operation. Allowable entries are:
|
|
•
|
match - the value of the attribute must match the value generated by the rule
|
|
•
|
matchorexceed - the value of the attribute must be equal to or greater than the value generated by the rule
|
|
•
|
matchornotexceed - the value of the attribute must be equal to or less than the value generated by the rule
|
|
•
|
matchaskeyattribute - the value of the attribute will be used to find matching objects in 3D; where key attributes are defined in the rules for a particular type, all their values on a particular object must match the values generated by the rules, in order for the 3D object to be identified as a match for the source schematic object
|
|
•
|
ignore - the value of the attribute will not be compared
|
|
Figure 6:17.
|
|
•
|
Mismatch Severity determines how a mismatch is reported during a Compare operation. Allowable entries are:
|
|
•
|
critical error - the mismatch will be reported as a critical error, indicated by a red blob icon in the compare report
|
|
•
|
error - the mismatch will be reported as an error, indicated by a red dot icon in the compare report
|
|
•
|
warning - the mismatch will be reported as a warning, indicated by a yellow triangle icon in the compare report
|
|
•
|
information - the mismatch will be reported as information, indicated by a blue "i" icon in the compare report
|
|
Figure 6:18.
|
|
•
|
Mismatch Report is an optional text that will be output as a line in the compare report following the line on which the mismatch itself is reported.
|
|
Figure 6:19.
|
Another Assign Action sets the attribute NAME to be the same in 3D as on the diagram.
|
Note:
|
Name rules based on target are not well supported in Integrator as target is undefined until it is actually created. In some cases it defaults to the source object for data if the target object is not available at that point. Consider an owner rule for building a ZONE when source is SCPLIN and target is the PIPE. It would seem reasonable to set the value of the ZONE name based on the SITE name plus a prefix, e.g. ”format(‘{0}-{1}’, owner of owner of target, LNTP of source)”. But the ZONE is created before the target exists and so this rule will not give the desired result.
|
|
Figure 6:20.
|
In the same block there are two further Assign Actions for NAME. The first of these has Assignee set to owner and contains an expression to define the name of the ZONE.
|
Figure 6:21.
|
