Schematic 3D Integrator User Guide
Schematic 3D Integrator User Guide
User Guide
AVEVA Solutions Limited
Disclaimer
1.1 AVEVA does not warrant that the use of the AVEVA software will be uninterrupted, error-free or free from
viruses.
1.2 AVEVA shall not be liable for: loss of profits; loss of business; depletion of goodwill and/or similar losses; loss of
anticipated savings; loss of goods; loss of contract; loss of use; loss or corruption of data or information; any
special, indirect, consequential or pure economic loss, costs, damages, charges or expenses which may be
suffered by the user, including any loss suffered by the user resulting from the inaccuracy or invalidity of any data
created by the AVEVA software, irrespective of whether such losses are suffered directly or indirectly, or arise in
contract, tort (including negligence) or otherwise.
1.3 AVEVA's total liability in contract, tort (including negligence), or otherwise, arising in connection with the
performance of the AVEVA software shall be limited to 100% of the licence fees paid in the year in which the user's
claim is brought.
1.4 Clauses 1.1 to 1.3 shall apply to the fullest extent permissible at law.
1.5 In the event of any conflict between the above clauses and the analogous clauses in the software licence under
which the AVEVA software was purchased, the clauses in the software licence shall take precedence.
Copyright
Copyright and all other intellectual property rights in this manual and the associated software, and every part of it
(including source code, object code, any data contained in it, the manual and any other documentation supplied
with it) belongs to, or is validly licensed by, AVEVA Solutions Limited or its subsidiaries.
All rights are reserved to AVEVA Solutions Limited and its subsidiaries. The information contained in this document
is commercially sensitive, and shall not be copied, reproduced, stored in a retrieval system, or transmitted without
the prior written permission of AVEVA Solutions Limited. Where such permission is granted, it expressly requires
that this copyright notice, and the above disclaimer, is prominently displayed at the beginning of every copy that is
made.
The manual and associated documentation may not be adapted, reproduced, or copied, in any material or
electronic form, without the prior written permission of AVEVA Solutions Limited. The user may not reverse
engineer, decompile, copy, or adapt the software. Neither the whole, nor part of the software described in this
publication may be incorporated into any third-party software, product, machine, or system without the prior written
permission of AVEVA Solutions Limited, save as permitted by law. Any such unauthorised action is strictly
prohibited, and may give rise to civil liabilities and criminal prosecution.
The AVEVA software described in this guide is to be installed and operated strictly in accordance with the terms
and conditions of the respective software licences, and in accordance with the relevant User Documentation.
Unauthorised or unlicensed use of the software is strictly prohibited.
Copyright 1974 to current year. AVEVA Solutions Limited and its subsidiaries. All rights reserved. AVEVA shall not
be liable for any breach or infringement of a third party's intellectual property rights where such breach results from
a user's modification of the AVEVA software or associated documentation.
AVEVA Solutions Limited, High Cross, Madingley Road, Cambridge, CB3 0HB, United Kingdom.
Trademark
AVEVA and Tribon are registered trademarks of AVEVA Solutions Limited or its subsidiaries. Unauthorised use of
the AVEVA or Tribon trademarks is strictly forbidden.
AVEVA product/software names are trademarks or registered trademarks of AVEVA Solutions Limited or its
subsidiaries, registered in the UK, Europe and other countries (worldwide).
The copyright, trademark rights, or other intellectual property rights in any other product or software, its name or
logo belongs to its respective owner.
Schematic 3D Integrator User Guide
Revision Sheet
Contents Page
Schematic 3D Integrator
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
Who Should Use this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
Assumptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
How the Guide is Organised . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
What the Integrator Can Do. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:2
Compare 3D Design against Schematic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:2
Build 3D Model Data from Schematic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:2
Link 3D and Schematic Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:3
Product Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:3
References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1
Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:1
Start the Integrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:1
Select Main Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:1
Open and Close a Diagram View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:2
Zoom and Pan in a Diagram View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:4
Compare a 2D and 3D Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:5
Build a 3D Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:6
Link and Unlink Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:7
Integrator Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:7
1 Introduction
This guide introduces AVEVAs Schematic 3D Integrator product. The Integrator is provided
as an Add-In to AVEVA Plant DESIGN and AVEVA Marine Outfitting. This chapter lists the
different types of user who would need to read this guide and sets out what knowledge they
will need before they start. It then explains how the Integrator is used in conjunction with
other AVEVA products.
1.1.1 Assumptions
Users have a valid Schematic license and the software has been installed.
Users of the Integrator have a basic knowledge of AVEVA DESIGN or Marine Outfitting.
Administrators have a reasonable knowledge of AVEVA Plant or Marine database structures
if they need to configure rules. A knowledge of PML is required if they need to set up batch
processes or customise the Integrator.
Integrator Controls explains how the user interface enables the Integrator tasks to be
invoked.
Integrator Functions in Detail explains the concepts behind the Integrator and describes the
main tasks in detail.
How to Configure Build Rules explains how to use the Integrator Configuration Tool.
How to use Integrator from the Command Line explains how to use Integrator functionality
from the command line.
How to Customise the Integrator describes the mechanisms available to customise the
Integrator for specific project needs.
2 References
This chapter lists other documents that provide supporting or complementary information to
this guide.
AVEVA System Requirements describes product installation and prerequisites.
Administrative users may need to refer to the following manuals:
AVEVA Diagrams User Guide
AVEVA Schematic Model Manager User Guide
AVEVA Software Customisation User Guide
AVEVA Software Customisation Reference Manual
AVEVA .NET Customisation User Guide
3 Getting Started
Getting started with the Integrator leads the inexperienced user through the steps to start
the Integrator and carry out the main tasks. It is not intended to train the user. Further
training can be supplied by AVEVA should the user require.
An AVEVA Plant or AVEVA Marine installation with some schematic data defined will be
required.
If the object is shown on only one diagram, that diagram will be opened. If it is shown on
multiple diagrams, you will be presented with a list to select from.
If you already know which diagram you want, you can open it directly from a list. From the
Integrator main bar menu select View Diagram.
The View Diagram dialogue allows you to browse for diagrams using the tree panel or
search for diagrams using the search controls.
Click on the Search button with blank text in the Search For field to get a list of all diagrams
available.
Select Diagram or Pages to see one entry per diagram or one entry per page.
Select By Diagram Name to perform a wildcard search using the name of the diagram.
Select By Content to perform a search using the name of an object such as schematic
equipment to find the diagrams it appears on.
The Diagram Viewer supports search using the following wildcards:
The Diagram page number is not included in the matching and matching is not case
sensitive.
Select the required diagram or page. If the Preview option was checked, and either a page
was selected or a single page diagram was selected, then the diagram will be displayed in
the Preview panel. Use the pan and zoom functions to inspect the diagram. Click OK to
display the diagram in the Diagram Viewer.
Figure 3:4. Zoom In, Zoom Out, and Pan Cursor Symbols
With the zoom-in or zoom-out cursor displayed, click with the left mouse button in the
diagram view. The view will be zoomed in or out centred on the position clicked. With the
pan cursor displayed, click in the view and drag the image in any direction. You can also pan
the image using the slider bars.
You can also drag out a zoom window by holding down the CTRL key and dragging out a
box with the left mouse button.
A comparison report will be displayed and the diagram and graphical views will be coloured
to reflect the results of the compare.
The Compare Report shows detailed results and marks any discrepancies. The report can
be saved from the File menu or Save Button.
Equipment built will be shown in the graphical view and listed on the Equipment Details
form. From this form you can change the equipment specification and position, and set
connection details.
Note: If you see the message Project Configuration Rules evaluation FAILED for an
SCFITT, SCVALV, SCINST or SCHVFI, check that it has a valid GTYP.
The dialogue right click menu provides options to navigate to relevant objects, and to copy
the content of the dialogue to the clipboard (e.g. so that it can be included if required in
support calls).
4 Integrator Controls
This chapter explains how to use each of the Integrator user interface controls. It explains
how to use the Main and Subtype Tables, the Schematic Viewer, and the Main Bar Menu
entries. In each case, the chapter shows how to invoke Integrator tasks from these user
interface components.
Enter the Attribute and Heading required in the new fields. Clicking Add Standard
Attributes allows the user to add all the standard attributes for the current element. The
Visible column allows the user to choose which columns to display or hide. Check the
required checkboxes to display the columns in the grid.
To add attributes of referenced elements you can use standard PML expressions such as:
NAME of DIAREF of OWNER.
To add a single element of an array attribute, use square brackets. For example, multiple
pipes can be linked to a single schematic pipeline, so to see just the first of these, use
DESLNK[1]. To see the whole array, use the attribute without any array index, e.g.
DESLNK.
The table can apply simple calculations to numerical attributes using the operators * / + - for
the operations multiply, divide, add and subtract, e.g. NUMBER * 4. You can use
parentheses ( ) to nest the expression, e.g. (LENGTH + 3.5) * BORE. Array elements and
references cannot be used in mathematical expressions.
To delete one or more columns in the Table Column Setup form, select the columns to be
deleted and click on the Delete Selected Columns button.
You can edit attribute data in the Main Table by selecting an appropriate Interaction Mode. In
Single Cell Edit, clicking on a cell places that cell in edit mode.
In Bulk Cell Edit, double clicking on a cell places that cell in edit mode. A single click on a
cell selects the cell itself, and standard Windows selection methods (left mouse click plus
Ctrl and Shift keys) select multiple groups of cells. A left mouse drag operation can also be
used to select multiple cells. In Bulk Cell Edit, Fill Down, Fill Up and Copy/Paste
operations apply to all cells currently selected.
Read only cells are shown with grey background (or the selected colour if Feedback
Colours have been changed). Cells may be read only for a variety of reasons, including
data from a read only database, an object claimed by another user, or non-editable
attributes such as Owner or Type. In Bulk Cell Edit mode, Name is read only. Following an
edit, the results (success or failure) are displayed using cell colours and tooltips. These can
be cleared by selecting Reset Cell Feedback.
4.1.6 Refresh
Selecting Main Table Menu > Refresh refreshes all cell values from the database.
4.2.2 Hide
To hide the Subtype Table select Subtype Table Menu > Hide.
4.2.4 Settings
Select Subtype Table Menu > Settings to display the Settings submenu. Select any of the
settings to enable or disable that facility.
4.3.2 Compare
Select Main Table Context Menu > Compare.
The Compare option will be available on schematic objects, and also on 3D objects that are
linked to schematic objects. For more details of the Compare operation see Integrator
Functions in Detail.
4.3.3 Build in 3D
Select Main Table Context Menu > Build then select OK when prompted to confirm.
The Build option will be available on schematic objects that are not linked to a 3D object.
When multiple objects are selected, the Build option will be available only if all the selected
objects are not linked to 3D objects.
For details of the Build operation see Integrator Functions in Detail.
4.3.5 Unlink
Select Main Table Context Menu > Unlink to unlink all objects currently linked to the
selected object.
The Unlink option will be available on objects that are already linked. When multiple objects
are selected, the Unlink option will be available only if all the selected objects are already
linked.
For more details of the Unlink operation see Integrator Functions in Detail.
Note: If you cannot see the object just added to the 3D view, use the Window menu to pop
the Integrator 3D view to the front.
The Equipment Connections form lists the nozzles and electrical connection on the
schematic equipment, and the 3D equipment. The Link columns show which connections
are linked between the schematic and 3D model. The form lists piping and HVAC nozzles
and electrical connections. It also lists connections that are direct to the equipment objects
using the ECRFA and ELCXRF reference array attributes.
To change the specification reference of a nozzle, select the nozzle in the 3D Equipment
list, then click on the Modify Specification button. This will show either the Pipework
Nozzle Specification form or the HVAC Nozzle form, as appropriate. You can also create
new nozzles or electrical connections and delete existing ones using the buttons on this
form. After making any changes, use the Refresh Lists button to update the form.
To change which 3D connection is linked to a particular schematic connection, select the
schematic connection in the Schematic Equipment list, select the 3D connection in the 3D
Equipment list, then select the Set Link button. The selected connections will be linked.
If the schematic connection is already linked to another 3D connection, the following will
occur:
The link will be removed from that connection and set on the selected connection.
That connection will be unnamed and the name will be set on the selected connection.
If that connection was auto-built in the last Build action during this session, it will be
deleted.
The Pick Connection form lists the 3D branches that have unresolved connections. When
a branch is selected in the Unresolved Branches list, Integrator does the following:
It determines the schematic branch for the selected 3D branch
It finds which schematic equipment the schematic branch is connected to
It finds their linked 3D equipment
It populates the Connections list with their nozzles.
The Connection columns show which branches are connected to which nozzles.
To change the specification reference of a nozzle, select the nozzle in the Connections list,
then click on the Modify Specification button. This will show either the Pipework Nozzle
Specification form or the HVAC Nozzle form, as appropriate. You can also create new
nozzles and delete existing ones using the buttons on this form. After making any changes,
use the Refresh Lists button to update the form.
To change which unresolved branch is connected to which nozzle, select the branch in the
Unresolved Branches list, select the nozzle in the Connections list, then select the Set
Connection button. The selected branch will be connected to the selected nozzle.
Note: Clicking on a schematic tube in the diagram will select the SCPLIN. Shift click on a
schematic tube will select the SCTUB element. This can be useful when navigating
the schematic database to investigate issues in the data, especially when there are a
number of tees in a line.
View Diagram - displays the View Diagram dialogue, and also displays a
pulldown list of recently viewed diagrams
Zoom In
Zoom Out
Always Zoom to the Table Selection - toggles the mode for auto-zoom
Remove Bookmark
The Compare, Build, Link, Unlink, Connection Details, and Pick Connections options
work in the same manner as the equivalent options for the Main Table Context Menu.
The View on Other Diagram option will be active if the selected object is available on more
than one diagram.
Note: Any highlighting of the diagram can be cleared by selecting Reset Diagram Colours
from the Integrator main bar menu.
The top section allows you to change the selection and mouseOver colours for the Diagram
Viewer. You may need to change these from the defaults if the diagram is already coloured
such that highlighting and selection are not clear. To change a colour, click on the colour box
and choose another colour from the palette.
The middle sections allow you to control where the diagram tabs appear, the number of
recent diagrams that will be remembered, and the number of tabs that can be displayed
simultaneously.
The Set CE from diagram option controls whether the current element will track the object
you click on in the diagram viewer.
These settings are per user and project and will be saved automatically between sessions.
4.8.2 Display
Select Integrator Bar Menu > Display > Main Table, Subtype Table or Diagram Viewer
to show or hide these components. Select Messages to show the Integrator Messages
dialogue which is available following a build or compare operation. Select Project
Configuration Explorer to show this component which is used to define configuration
rules, described in detail in How to Configure Build Rules.
Select Compare Colour Key to display the colours and their meanings as used in the
graphical views by a compare operation (according to the rules configuration).
4.8.8 Configurations
Select Bar Menu > Configurations to choose one of the available Configurations that have
been defined by the administrator for this project. When a Configuration is selected, its
name is included in the title of the Comparison Report.
4.8.9 View
The View options work in the same manner as the equivalent options for the Main Table
Context Options.
This is an administrative dialogue used to manage Link Worlds. Before using it, create a
separate Design Reference database in Admin, and ensure it is current on all MDBs where
linking will occur, and all users who need to link can write to it.
Note: The Manage Links dialogue is shared between Integrator and Compare/Update.
Design Reference databases can be written to by 3D, schematic and engineering
users.
The list includes all the Design and Design Reference databases available, identifying any
that contain links (links created prior to 12.1 reside in Design databases). The following
functions are available from the File menu or on a right click context menu.
Validate Output a list of links and any errors to the command line for the
selected database.
Validate All As for Validate for all databases in the list. This action will also
merge partially populated links, for example: 3D object "A" is linked
to schematic object "A" by one link and schematic object "A" is
linked to engineering object "A" by another link, as can occur when
links are created in separate extract databases.
Remove invalid Remove invalid references from links in the selected database.
references Invalid references can occur when elements are deleted and the
Link World database cannot be updated.
Caution: This operation should be used only when all of the databases holding objects
that have been linked are current on the MDB.
The Edit menu provides Cut, Copy, Paste and Delete functions to move Link Worlds
between databases. You can also drag and drop from one database to another to move or
merge a Link World.
The Line List Options can be used to compare connection information using the LLFROM
and LLTO pseudo attributes. This applies mainly to Comparing in Line List Mode. The Line
List Options are detailed in the Schematic Model Manager User Guide section 9 Line List
Configuration.
Open All Referenced Opens all diagrams relating to the report content. Each diagram
Schematics will open in a separate tab in the Diagram Viewer.
Open Opens a file browser dialogue which allows the user to open a
previously saved XML report. The report will be opened in the
Compare Report form.
Save As Opens a file browser dialogue which allows the user to save the
report as an XML dataset or as an HTML file using a stylesheet.
Stylesheets (files with extension .xsl) should be placed in the
%<proj>dflts%\modelmanagement folder.
Export Details to Opens a file browser dialogue which allows the user to export the
Excel contents of the Details tab to Excel, providing the key results of the
comparison, including the side by side matches and the error
comments, in a form that can be distributed to a wider audience.
Print Details Opens a Print dialogue which allows the user to print the contents
of the Details tab.
Copy All to 3D Copy all attribute values to 3D for all matched or linked objects
Link all matched Link all unambiguously matched objects (note this function will not
elements link matched objects if they have an In Wrong Location or a
Sequence Difference error)
Find CE in Report Focus the report on the current element (if it appears in the report)
Refresh Schematic & 3D Views Re-apply the compare rules colours to the Diagram
View and 3D View.
Set Limits Sets the 3D View limits to encompass all the 3D objects
in the report.
Significant Elements Only These two filters control which objects will be displayed
Differences and Errors Only in the Compare Report.
Highlight on Diagram These modal settings control how the Diagram View
Zoom to Diagram Selection and 3D View will respond each time an object is
Navigate to Schematic Element selected in the Compare Report. Which Navigate mode
Highlight in 3D View will be used is determined by whether the Schematic or
Zoom to 3D Selection 3D tree panel is visible in the Compare report.
Navigate to 3D Element
Show Equipment Translucent
Clear Link Selection Clear the selection of object for linking (see
Comparison Report Context Menu).
Comparison Category Details Display the current settings for the Comparison
Category used in the report (note these may have
changed since the report was made).
The first eight buttons in the Report toolbar have the following functions and are equivalent
to the View menu options.
Back
Forward
Save As
Refresh Schematic & 3D Views
Set Limits
Open All Referenced Diagrams
Significant Elements Only
Differences and Errors Only
The ninth button toggles the Summary filter. When set, only those rows corresponding to the
currently selected row in the Summary tab will be displayed (together with their owners in
the hierarchy).
The buttons in the Data panel toolbar have the following functions to control the attributes
displayed.
Differences and Errors Only
Attributes Common to 2D & 3D
Categorised
Categorised (Extended)
Alphabetic
Copy to 3D
Copy All to 3D
Refresh
Navigate Sets the object in the right click menu as the current element.
Unlink Unlinks an object. Only available when the object is already linked.
Build Builds a missing object in 3D. Only available when the object has
not been linked or matched.
Link Link an object to its match. Only available when the object has
been matched but not linked.
Select for Linking Select this object for linking - its name will be displayed in the
report status bar
Link <named Link the currently selected object to the object previously selected
objects> for linking
This chapter describes the engineering functions supported by the Integrator. It starts by
explaining the concepts embodied in the main tasks, and then details the data structures
that underpin all of the Integrator's functionality.
It explains how to build 3D model objects based on schematic objects data, describes what
happens when the Integrator creates objects in the 3D model and illustrates how rules are
used to determine exactly what data is set.
It explains how to compare 3D model data against schematic data, describes how the
Integrator compares data and how rules are applied to verify alignment or report
discrepancies.
It explains how to link 3D model data to schematic data, how to unlink if necessary, and
illustrates when these functions might be used during a project.
5.1 Concepts
Integrator provides three main functions that can be applied to data:
Compare
Build
Link
5.1.1 Compare
Integrator uses configuration rules to compare schematic and 3D objects, to verify if they
are aligned or to report any discrepancies. The comparison covers connectivity, component
sequence, and attributes data.
Connections within the 3D model should be consistent with connections within the
schematic model. This includes connection onto equipment - nozzles and electrical
connections, and connections within pipework or HVAC - head and tail references,
connection references and connection reference arrays.
Component sequence should be logically consistent between the schematic and 3D model.
Integrator will report when components such as instruments, valves, tees and reducers, are
missing or are in a different order.
Integrator will also report any missing or mismatched attribute data, using the configuration
rules to identify which attributes it should check and how they should be compared. For
example, a name may be composed from schematic attributes such as prefix, suffix and
function, and bore and specification reference must match.
Comparison Categories provide a level of control over which categories of difference are
reported against which types of objects. For example, you may choose to focus on
unmatched objects and differences in specification attributes, and to ignore other attribute
differences.
Integrator can use the results of a comparison to automatically link schematic and 3D
objects that it has found to match. It can also automatically update attributes from schematic
to 3D where it finds a difference in the data for matching or linked objects.
5.1.2 Build
Integrator can create 3D data directly from the schematic data, enabling equipment,
pipeline, HVAC and cable objects to be built automatically in 3D, populated with data from
the schematic model. This means for example that an equipment list and line list can be
propagated to the 3D model along with all their key process data, tags and inter-
connections.
Thus when schematic data is available, Integrator can provide an initial population of
corresponding objects in the 3D model. As updates occur in the schematic data, these can
be applied to the 3D data in a controlled process. Each project can control precisely which
data is transferred from schematic to 3D, what types of object are created, and which
attributes are set, using easily configured rules.
When Integrator builds an object in the 3D model, that object is automatically linked with its
corresponding schematic object.
Note: CYMLNKs also have attribute englnk referencing engineering objects, but this is not
used directly by Integrator.
Pseudo Attributes
To simplify navigation between corresponding schematic and 3D objects, Integrator
provides the pseudo attributes schlnk and deslnk directly between these two objects. The
pseudo attribute cmpsts returns the compare status description on the CYMLNK object or
on any linked schematic or design object, or on its linked ancestor. It is included by default in
the Integrator Main Table.
Cardinality
For most objects, zero or one schematic objects can be linked to zero or one 3D objects.
The exceptions are schematic pipelines which can link to zero, one or many pipes, and
schematic HVAC lines which can link to zero, one or many HVACs.
Integrator has created a separate 3D view for the compare results. This view has its own
drawlist so that results of the colour coding do not affect any other views that the user may
have defined.
Note: If you cannot see the Integrator 3D View, use the Window menu to pop it to the front.
Selecting the Details tab and then the owning schematic branch displays its detailed
compare results in the Data panel.
The source and destination connections are listed (note that the schematic branch has
a connection direct to a schematic equipment, but the pipe branch connects to a
nozzle).
Note: The missing valve marked as Not Matched, and has no values in 3D.
Selecting a row in the Summary tab will cause the report to swap to the Details tab and filter
the display to show only those rows appropriate for that selection (together with any owning
hierarchy present in the report). The Summary filter button will be automatically switched on.
Selecting Build in the valve's context menu will create the component if Integrator can
determine its list position. If not then it shows a form listing the components already present
in the 3D branch. The user must now select the position in the sequence for the valve to be
created by dragging the highlighted NEW VALVE line up or down, using the left mouse
button, and then select the OK button.
To update the value, first select the row with a left mouse click in the Data panel then right
click in the row and select Copy to 3D.
Alternatively, select the correct value from the drop-down menu provided.
If the update has been completed, the field will turn cyan.
Integrator will work through the compare report content prompting to link matched objects.
You can choose to link or skip individual objects, or click Yes to All to automatically link all
matches. On completion, the report will indicate newly linked objects in cyan and any failed
or skipped links in red. A log of the linking actions is output to the command line.
Integrator will work through the report content updating any attribute differences on linked or
matched objects. On completion, the report will indicate newly updated objects in cyan and
any failed or skipped updates in red. A log of the updating actions is output to the command
line.
From the Integrator bar menu, select Settings > Comparison Settings then check the
option to Compare Pipelines and Pipes without their member hierarchies. This will
ensure Integrator compares only the top level items (without this setting Integrator will report
all the 3D piping components as unmatched).
In order to compare the source and destination information, Integrator makes use of the line
list pseudo attributes LLFROM and LLTO. These can be configured to pick up connection
information from text attributes for the pipelines, and from connected 3D model objects for
the pipes. The Line List Options are detailed in the Schematic Model Manager User Guide
section 9 Line List Configuration. The following walks through an example configuration.
From the Integrator bar menu, select Settings > Line List Options to display the Line List
Configuration dialogue. Create an SCPLIN rule for LLFROM, setting the Prefix to take its
value from :FROM, with a comma separator, and the flag to include SCBRANCH values set
to false.
Create a similar SCPLIN rule for LLTO taking its value from :TO.
For the 3D piping, the attributes LLFROM and LLTO should be configured to hold a comma
separated list of strings derived from the connected model. Create a PIPE rule for LLFROM
and LLTO, with a comma separator, and the flag to include BRANCH values set to true.
Create a Component Rule for LLFROM and LLTO with end condition set to Valid HREF/
TREF. Add NOZZLE to the list of item types, set the expression to NAME and select
EndComponent for the expression object.
A typical means to compare pipes against pipelines is using key attributes. This allows
multiple pipes to be matched to each pipeline (refer to Matching Objects using Key
Attributes). The example below defines rules to match on LNTP and FUNC. It also defines
rules to compare LLFROM and LLTO.
From the Integrator bar menu, select Display > Project Configuration Explorer (refer to
How to Configure Build Rules for more information). Create the two SCPLIN rules to match
LNTP and FUNC as key attributes.
Note: It is not necessary to create LLENTRY configurations, but if LLENTRY returns false,
that SCPLIN or PIPE will not be compared (unless it is linked - linked items will
always be compared).
An example pipeline compared using the settings defined above shows two pipes matched
by key attributes.
Figure 5:27. Compare Report in Line List Mode showing first pipe
Note: LLFROM and LLTO are shown as matching, yet LLTO has an additional value on the
schematic side. This match is indicated as correct because the second pipe provides
the additional matching connection.
Figure 5:28. Compare Report in Line List Mode showing second pipe
The values of LLFROM and LLTO will be matched across the combination of pipes that
match each pipeline.
2. Accept Missing Element: For unmatched objects, such as a drain connection, the
corresponding elements can be accepted as missing. Integrator will still match the
object if it is added subsequently to the model.
3. Disable Matching: For objects that should not be matched ever, such as a tee for a
trunnion, whether or not Integrator has currently matched them, matching can be
disabled.
All of these actions can be reversed and the differences will then revert to being flagged up
in the comparison report. Once a number of differences have been accepted it is necessary
to redo the comparison in order to see the effects. This in turn can change which objects are
matched and thus offer more opportunities to accept differences, and so the process may
take several cycles to achieve the desired results.
This functionality requires some UDAs to have been configured by an administrator. The
definitions are included in a PML function. In Lexicon navigate to a writable database then
display the Command Line then type:
!!integratorUDAs()
Integrator stores its accepted difference information in GPSET objects. Before using the
functionality a suitable GPSET must have been selected. Refer to Accept Differences
Options.
A compare colour for Accepted Differences can be set in the configuration (refer to
Compare Colours).
Note: Before a difference on a pair of objects can be accepted, the objects must be linked.
If objects are not linked, the match may not persist in subsequent sessions as it
depends on data values and rules configuration.
If the pair of objects are matched but not linked, right click in the Details tab and select the
option to Link matched elements.
If two objects have not been matched they will be reported on different rows to each other,
and may have been matched to other objects. For example, Integrator by default will not
match an SCINST to a PCOM, but if they have been modelled that way they can be linked to
preserve the design intent. Right click in the Details tab on one of the objects, click on
Select for Linking, and then click on the required object. Then right click on the other object
and click to Link the required pair (there may be more than one choice of link candidates).
After a redo of the comparison they will be lined up in the report. The Accept Differences
option in the right click menu will then be enabled.
Hint: To find a schematic object in the report, drag and drop it from the diagram viewer or
the schematic explorer onto the report. To find a 3D object in the report, click on it in the 3D
view to make it current, then drag and drop it from the design explorer onto the report.
To accept a difference on a pair of linked objects, right click and select Accept Differences.
To accept an unmatched object, right click and select Accept missing element.
Alternatively if the object is never to be matched then select Disable matching. In the case
of a tee connection, where the connecting branch is not connected into the piping network at
its other end, the branch will also be accepted as missing, or disabled for matching. This
allows, for example, drain connections not detailed on the P&ID to be accepted in one
operation.
To reverse acceptance of a difference, right click and select Reject accepted differences.
To reverse acceptance of a missing element, right click and select Reject acceptance of
missing element.
After a number of accept or reject operations, redo the comparison to see the effect.
Integrator has a configuration option which allows an administrator to set whether accepted
differences will be ignored, i.e. reported as if the difference had not been accepted (refer to
Configurations).
Note: Integrator can build in the current SITE and ZONE if there is no rule to define the
SITE or ZONE. In order to get Integrator to build in the current ZONE, use the Main
Table Context Menu > Build. If you click in the Diagram Viewer to use its context
menu, the current element will be changed to the schematic object, and Integrator
will no longer be able to build in your intended ZONE.
Note: On build, Integrator automatically copies over the value of any attribute that appears
on both the schematic and 3D object, e.g. Description. The exact set of attributes
varies according to type. You can suppress this by creating an Assign Rule for that
type and attribute and setting its Build Action to ignore. Refer to How to Configure
Build Rules for more detail.
NOZZles are created for each schematic nozzle and ELCONNs for each schematic
electrical connection (see below how Integrator deals with nozzles and electrical
connections already defined in an equipment template).
If a specification reference has been set on the schematic equipment it will be copied to
the EQUIpment and the equipment template will be instantiated so that it has a
population of primitives. The user has an opportunity to modify the equipment
specification later in the build process.
If the schematic equipment does not have a specification reference but it does have a
description, Integrator will collect all the SPCOms and TABITEms from the equipment
specifications and selection tables, and look for a match against the descriptions of
their owners. If there is a single match this will be set as the specification reference on
the 3D equipment.
If a catalogue reference has been set on a schematic nozzle or electrical connection it
will be copied to the NOZZle or ELCONN. The user has an opportunity to modify the
specification later in the build process.
Nozzle and electrical connection references are set in accordance with the schematic
connectivity if the connecting objects exist in 3D.
If a position has been set on the schematic equipment it will be copied to the
EQUIpment. The user has an opportunity to modify the equipment position later in the
build process.
Attribute values can be set on the EQUIpment, based on attribute values on the
schematic equipment, in accordance with the rules.
The schematic and 3D objects are linked.
Although Integrator always creates nozzles and electrical connections to link to their
schematic equivalents, there may already be appropriate nozzles or electrical
connections defined in an equipment template. Integrator will check in a template for
NOZZles with matching BOREs and for ELCONNs with matching CATREFs. If a match
is found, the schematic nozzle or electrical connection will be linked to the matched
object within the template, and the auto-built NOZZle or ELCONN will be deleted. Any
attribute data, including the name, that were set on the auto-built object in accordance
with the rules, will be copied over to the selected 3D connection in the template.
The user has the opportunity to modify connection details, including changing or
swapping the links between 3D and schematic connections. If a link is moved from an
auto-built NOZZle or ELCONN in the same session that it was built, the auto-built
object will be deleted. The user can also modify the specification of the NOZZles and
ELCONNs.
Note: If you build an equipment which has no specification set, and then select an
equipment specification, the auto matching of nozzles and electrical connections will
not take place, since Integrator has already finished its build function.
Note: If you build an equipment which has a specification set, then modify the specification,
the links and any attribute data copied to the earlier template nozzles and electrical
connections will be deleted.
Some changes to schematic equipment can be propagated to 3D from the Compare Report
form. Refer to How Integrator Compares Schematic and 3D Data.
A PIPE is created in the appropriate ZONE and named in accordance with the rules.
Typically the name will be generated from a number of schematic pipeline attribute
values and can include a sequential number.
BRANches are created equivalent to the schematic branches.
Piping components are created equivalent to schematic piping instruments, valves and
fittings. Rules determine the component type. Components (including valves and
instruments) can be named if rules are defined for this.
Component specification references are copied from the schematic components where
available.
If a specification reference has not been set on the schematic component, Integrator
will try to choose the 3D component from a pipe specification using available data.
Integrator will determine the appropriate specification, generic type and bore(s). Other
selectors such as STYPE can be set by the rules. If Integrator has insufficient data to
make a single choice, it will prompt the user with the selection it is trying to make and
display the Choose form for the user to make the choice.
Connection references are set in accordance with schematic connectivity if the
connecting objects exist in 3D. This includes branch head and tail references, nozzle
connection references, component connection references and connection reference
arrays.
Attribute values can be set on the 3D pipes and components, based on attribute values
on the schematic pipelines and components, in accordance with the rules.
The schematic and 3D objects are linked.
The user has the opportunity to resolve connections where the schematic connection is
directly to schematic equipment. In 3D the connection must be to a nozzle or electrical
connection. When resolving connections the user can select an existing nozzle or
electrical connection or create a new connection.
Where a number of interconnected schematic pipelines are to be built in 3D, it is
recommended to build the main line first, before building offlegs.
Integrator can build and compare HVAC data provided that the schematic data is consistent
with the standard AVEVA HVAC application catalogue. This means that any HVAC fittings
defined on a diagram must conform to the equivalent 3D HVAC fittings that can be created
from the standard AVEVA 3D HVAC specification.
The information used by Integrator to determine the appropriate component in 3D depends
on the following attributes of the SCHVFI (schematic HVAC fitting) object:
In order for Integrator to be able to build and compare a 3D HVAC component, the
combination of this information from the SCHVFI must correspond to a component in the
standard catalogue. In particular, if there is a branch connection point, it should be P3, with
ARRIVE and LEAVE as P1 and P2 (or P2 and P1) respectively.
An example of a component that would not meet this criteria would be a rectangular, three-
way fitting with a different duct height on P3. In the standard catalogue, duct height (the
depth of the fitting) is equal across the three connection points.
For each GTYP there are one or more available SCSTYPs. To set an appropriate SCSTYP
in AVEVA Diagrams in HVAC mode, navigate to the SCHVFI by selecting it in the diagram or
schematic explorer, click on HVAC > Set SCSTYP, select an SCSTYP from the list and click
Apply.
Integrator can build user defined HVAC fittings provided that the SPREF is set on the
SCHVFI. A configuration rule should be defined in Integrator for SCHVFI elements, to copy
the SPREF if it is set on the source element.
This chapter explains how to configure the rules used by Integrator during Build and
Compare operations. It describes how to use the Integrator Configuration Explorer and
explains the different types of configuration settings.
Integrator configuration rules may be modified by Free users or by General users who are
members of team CUADMIN (the same team is used for Compare/Update configuration).
Note: If you have moved away from the default folder, use the project defaults environment
variable to get quickly to the appropriate folder. For example, in the Open File
dialogue, for the Sample project, enter %samdflts%\ModelManagement in the
Filename field and then press Enter.
To edit a section, click on its entry in the tree panel of the Configuration Explorer. Then click
in the appropriate Value field in the grid panel and edit the entry.
Real Tolerance
This is the value that will be used to compare real number attributes. Two attribute values
within this tolerance will be deemed to be equal. If no Real Tolerance value is specified the
built-in default is 0.00001.
Distance Tolerance
This is the value that will be used to compare distance attributes. Two attribute values within
this tolerance are deemed to be equal. If no Distance Tolerance value is specified the built-
in default is 0.01.
6.5.2 Dictionaries
Dictionaries may be used with the rules to define value strings against given keys. For
example the key might be the setting of an attribute, and the associated value might be
needed to perform correct build or comparison operations. In the example below a
Dictionary has been created for Disciplines.
6.5.4 Configurations
The Configurations are defined by the administrator to cover the range of uses intended
for their end users. For example, a basic setup to check for matching tagged items and pipe
specifications may be defined for early use on a project, along with a full setup to be used on
mature data. Each Configuration combines a set of Compare Colours, a Comparison
Category and a Rule Set.
To add a new Configuration, right click in the Configurations node in the explorer tree and
select Insert. Then enter a Name, an optional Description, and select the Colours, Category
and Rule Set from the drop down lists. There will always be at least a default set of Colours
and a default Category. You will need to have defined a Rule Set or imported one from
another configuration file in order to complete the selection.
Each Configuration has a number of options that can also be entered here.
Check Ignore Accepted Differences to report each difference as if it had not been
accepted.
Check Report unpositioned elements to warn when piping components have been built
but not yet positioned and orientated.
Check Strictly limit compare to selected elements to provide a faster report
(recommended). If unchecked, Integrator may take longer to complete the report and may
include additional pipelines. This can occur when matched pipes also partially match
additional pipelines.
Check Compare Lines/Pipes without member hierarchies to compare in Line List mode.
Refer to Comparing in Line List Mode for further information.
The Whole Diagram Compare options allow you to set which main types will be included in
the report for a Compare Diagram operation.
To add a new set of Compare Colours, right click in the Compare Colours node in the
explorer tree and select Insert. Then enter a Name and click in each colour cell to choose a
colour.
Each Compare State can have a Compare Colour. To change the colour for that state,
click on the colour box to the right of the state and select a colour from the browser.
The Compare States have the following meanings:
Accepted Difference The object has one or more accepted differences, e.g. it has
been accepted as missing, or an attribute difference has been
accepted, or it has had matching disabled
Connection Error The connections on the object in 3D are not consistent with the
connections on the matched schematic object, e.g. a branch is
connected to the wrong nozzle
Difference The values of one or more attributes of the object or its
members in 3D do not conform to the rules, or the sequence of
objects in 3D does not conform to the schematic sequence
Error An error with the object that can invalidate the comparison will
be noted in the Compare Report and/or the Integrator
Messages dialogue, e.g. an inconsistent connection reference,
or a missing GTYP value leading to a rules evaluation failure
Highlight This is not used for compare - it is the colour used to highlight
objects in the 3D view when selected in the Main Table or
Compare Report
Missing The object is not matched with an object on the other side, e.g.
a component on the diagram is coloured to show that there is
no matching component in 3D, or an item is missing from the
object that is coloured - typically a tube in 3D is coloured to
show where a component is missing when compared against
the matching segment on the diagram
Not Compared The objects have not been compared in the current session
OK Object data has compared correctly according to the rules
6.5.6 Categories
Comparison Categories allow certain categories of difference to be ignored so that
attention can be focused on areas of priority. You can define multiple Categories to be used
with different Configurations. For example in the early stages of a project you may want to
switch off reporting differences in most attributes, but as the data matures you want a full
comparison to be run.
When a category of difference is switched off, the differences concerned no longer appear
as comments or as red icons, and do not participate in the aggregation of differences
reported up the hierarchy (the worst case report), also the relevant rows in the Compare
Report lower Data panel are not shown.
To add a new Category, right click in the Categories node in the explorer tree and select
Insert. Then enter a Name and use the check boxes to specify which categories of
differences will be reported against which types of objects. You cannot switch off the
reporting of unmatched main type objects such as pipelines and equipment. The Key
Attributes column applies when matching by key attributes according to the rules. The
Spec Attributes column applies to specification attributes PSPE, SPRE and CATR.
Earlier versions of Integrator had Comparison Categories stored separately. To import these
into the configuration file, right click in the Categories node in the explorer tree and select
Import User Defined Categories.
6.5.7 Rules
Most of the configuration activity will be concerned with the Build and Compare rules. Rules
are organised in RuleSets and RuleGroups and use expression syntax as described below.
At any point during the Build or Compare operation there is one schematic object under
consideration. This object is referred to as the source. The corresponding design object (if
there is one) is referred to as the target. During Compare operations the target will be an
actual corresponding 3D object. During Build operations the target represents a "candidate"
for a 3D object still to be created.
Rule Types
Build and Compare rules have two basic types.
Create rules are used to create new 3D objects during Build, and to check the existence
and type of a matching object during Compare.
Assign rules are used to assign a value to an attribute during Build, and to check the setting
of an attribute on the 3D object during Compare. An Assign rule should always be preceded
by a Create rule in the same block.
Rule Sets
A Rule Set holds all the Rule Groups for a particular pairing of database types. For
example, the sample configuration has a default Rule Set for comparing Design database
content against Schematic database content.
You can add Rule Sets for other combinations of database types, e.g. schematic and
engineering, for use with Compare/Update.
Note: Compare/Update does not use the Configurations, Colours or Categories. It uses
only the Rule Sets, and will use the first Rule Set it finds appropriate to its current
source and target database types.
Rule Groups
Create and Assign rules are grouped within a Rule Group. Top level Rule Groups have a
Source Type which is the type of object for which they will be applied. Nested Rule Groups
have a logical condition that determines when the rules of the Rule Group will be applied.
When Rule Groups are nested, the inner rules are only applied if all of the conditions of the
owning Rule Groups are met.
The Rule Group name is an alphanumeric string to identify the Rule Group. It is optional
and no check is made that names are unique.
The Rule Group condition is a Boolean expression that is evaluated during Build and
Compare operations.
For Compare rules, the source and target elements can be referred to in the Rule Group
condition. These can be used to refer to attributes or UDAs on the source or target using
the "OF" syntax. For example, NAME of source refers to the NAME attribute of the
source schematic object. User defined attributes can be used in the same way, for example,
:MYATT of source. For Build rules, the target object does not exist and any reference to
it may be undefined.
An extended notation allows access to attributes on related elements - owner, previous,
next, for example, AREA of OWNER of OWNER of target.
Attribute values can be combined and compared using the full power of the expression
syntax described in detail below.
Create Rules
Create rules have a type expression that defines the 3D object type that is to be created
(during Build operations), or that is needed to match (during Compare operations). During
Build operations the object will be created at the appropriate level in the database hierarchy.
The type expression must evaluate to a legal 3D database object type. This can be an
explicit word, e.g. EQUI, or a more complex expression calculated from schematic attribute
settings. As in the Rule Group condition, the current source schematic object is referred to
as source and its attributes are identified using the "OF" syntax, for example, GTYP of
source. More powerful expressions can be created using the syntax described below.
In the situation where more than one 3D object type can be acceptable for comparison
purposes, the Create type expression uses the special Variant function. This defines a list
of all acceptable matching types, for example, Variant (TEE, OLET, FLAN). Each
argument of the Variant function is an expression as defined above. When building, the first
type listed in the Variant function will be used.
When the 3D object being created is to be selected from a specification, the questions and
answers that inform the selection process are listed in Selector rules owned by the Create
rule. Each Selector rule has a Question, e.g. STYP, and a value based on a schematic
attribute, e.g. SCSTYP of source.
Note: Quotes are not required in selector rules as Integrator will automatically include
quotes for text selectors, e.g. a rule with SCSTYP OF source operating on an
SCVALV with SCSTYP PTFE-LINED will generate Choose with STYP |PTFE-
LINED|.
Intellisense Feedback
The Configuration Explorer provides Intellisense feedback to assist with finding the
appropriate entry as you edit a rule. Full syntax available can be displayed at the start of an
entry by pressing the Alt and right arrow keys together. If a letter is entered, the available
words starting with that letter will be displayed.
The user selects a word by double clicking on that line in the drop down list.
Operators
Arithmetic expressions can be built using the usual conventions:
Operators + and - add and subtract numerical values
Operators * and / multiply and divide numerical values
Brackets () are used to group sub-expressions particularly to build nested
expressions.
Boolean expressions can be built using the following conventions:
Operators eq, ne, lt, le, gt, ge, test for equality, inequality, less than, less than or
equals, greater than, greater than or equals, and apply to a pair of numerical
expressions or a pair of alphanumeric expressions or a pair of Boolean expressions.
(The result will be unpredictable if expressions of different type are compared.)
Operators and and or test for Boolean "and" and Boolean "or" between two Boolean
expressions.
Operator not is used to negate the Boolean expression that follows it.
Attributes
Attributes can generally be included in rules using the of syntax, e.g. NAME of source, but
the dot notation can also be used, e.g. source.NAME. The dot notation is useful for array
attributes, e.g. source.BOREAR[3] < 100.
Functions
The following functions are available (minimum abbreviation shown in bold):
integer Occurs (string text, string sub) // number of occurrences of sub in text
integer Instring (string text, string sub) // Position of first occurrence of sub in text
string Substring (string text, integer start [, // substring from the start position of given
integer length]) length (or to end of text)
string Before (string text, string sub) // left part of text before given substring
string After (string text, string sub) // right part of text after given substring
string Replace (string text, string // replace all occurrences in text of substring
seek, string sub) seek with substring sub
string Trim (string text) // remove leading and trailing white space
from text
string Format (string pattern, object // substitute the values of the arguments into
arg1, ) the pattern string
string Lookup (string dictName, string key) // return the value associated with the key in
the given Dictionary
boolean Like (string pattern, string text) // test if the text conforms to the wildcard
pattern. Wild characters are:
boolean Between (object test, object // determine if the test object lies between the
lower, object upper) given lower and upper values.
boolean Inlist (object test, object // determine if the test equals one of the given
value1, ) list of values.
The Source Type here restricts this Rule Group to be applied only where the source type is
SCEQUI.
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.
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.
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
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
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
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.
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.
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.
The second has Assignee set to root and contains an expression to define the name of the
SITE.
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.
One of the accompanying Assign Actions copies the attribute SPRE from the source
object.
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.
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 objects SCSTYP attribute.
The next Rule Group has a condition that tests for a Check Valve using the SCSTYP
attribute of the SCVALV.
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:
before(after(name of target, '-'), '-') eq before(after(after(name of source, '-'), '-'), '-')
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.
This chapter explains how to use the Integrator from the command line in macros.
!!integrator.compareRuleset()
By default the Compare Report is generated to the screen. In order to send the report direct
to file the following two lines are needed to suppress the output to screen and set the
pathname:
!!integrator.setReportVisible(false)
!!integrator.setReportPath('c:\reports\rep.xml')
If the pathname of the report file has been specified as shown above, then the report can be
viewed in the Compare form using the following command (note that this command cannot
be used in non-graphics mode).
!!integrator.openReport()
The following methods have been provided to set flags to auto-link matched objects and
auto-update attributes:
!!integrator.setCompareAutoLinkMatches(!Flag is BOOLEAN)
!!integrator.setCompareAutoUpdateAttributes(!Flag is BOOLEAN)
If these are set true then the next use of the compare method will perform these functions.
Integrator link information stored on CYMLNK objects includes references to the linked
objects. It is possible during project execution for these references to become invalid when
objects are deleted. A method is provided to clean up CYMLNK objects with invalid
references.
!!Integrator.validateLinks()
Caution: This method should be used only when all of the databases holding objects that
have been linked are current on the MDB.
The following method can be used to clear the Integrator 3D graphical view drawlist:
!!integratorSupportHandler.intdrawlist().removeall()
applicable. The strings are returned as comma separated values for the category and the
total:
!!integratorSupportHandler.compareSummary() is ARRAY
The following method runs the above method internally and prints the summary to the
command line, formatted to match the summary as seen interactively:
!!integratorSupportHandler.printSummary()
Note: The command line summary methods will return values only for the last comparison
run from the command line, or for the last comparison run interactively whilst the
report is still open.
!arrayOfStrings =
!!integratorSupportHandler.acceptedDifferences()
!!integratorSupportHandler.printAllAccepted()
-- Initialise Integrator
!!integratorInit()
This chapter explains how to customise the Integrator using PML to add project specific
actions to the process.
Important: Modification of the AVEVA supplied code in the Integrator PML objects could
compromise the integrity of data managed by the Integrator, and could lead to
adverse effects on project progress. You are advised to carefully test any
modifications to these objects.
-- End of customisation
--================================================
Other methods on the IntegratorProjectHandler object should not be modified.
Index
Numerics C
2D Table . . . . . . . . . . . . . . . . . . . . . . . . 4:15 Cable . . . . . . . . . . . . . . . . . . . . . . . . . . 5:25
3D Data . . . . . . . . . . . . . . . . . . . . . 5:6, 5:22 Cardinality . . . . . . . . . . . . . . . . . . . . . . . 5:4
3D Links . . . . . . . . . . . . . . . . . . . . . . . . . 5:3 Ceil . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:13
3D Objects . . . . . . . . . . . . . . . . . . . . . . 5:26 Colour Coded . . . . . . . . . . . . . . . . . . . . . 5:6
3D Status . . . . . . . . . . . . . . . . . . . . . . . . 5:4 Colour Codes . . . . . . . . . . . . . . . . . . . . 5:13
3D Table . . . . . . . . . . . . . . . . . . . . . . . . 4:15 Column Setup . . . . . . . . . . . . . . . . . 4:3, 4:8
3D View . . . . . . . . . . . . . . . . . . . . . . . . . . 5:6 Command Line . . . . . . . . . . . . . . . . . . . . 7:1
Compare 3:5, 4:10, 4:14, 4:21, 4:30, 5:1, 5:6,
A 6:7
Compare Colour . . . . . . . . . . . . . . . . . . . 6:8
Abs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:13 Compare Colours . . . . . . . . . . . . . . . . . . 6:7
Acos . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:13 Compare Report 4:21, 4:25, 5:6, 5:10, 5:11,
After . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:14 5:12
Alog . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:13 Compare State . . . . . . . . . . . . . . . . . . . . 6:8
Alog10 . . . . . . . . . . . . . . . . . . . . . . . . . . 6:13 Compatibility . . . . . . . . . . . . . . . . . . . . . . 1:3
ARRIVE . . . . . . . . . . . . . . . . . . . . . . . . . 6:23 Concepts . . . . . . . . . . . . . . . . . . . . . . . . 5:1
Asbool . . . . . . . . . . . . . . . . . . . . . . . . . . 6:14 Configuration . . . . . . . . . . . . . . . . . . . . . 6:3
Asreal . . . . . . . . . . . . . . . . . . . . . . . . . . 6:14 Configuration File . . . . . . . . . . . . . . . . . . 6:1
Assign Action . . . . . . . . . . . . . . . 6:16, 6:18 Connection . . . . . . . . . . . . . . . . . . . . . . 4:11
Assign Actions . . . . . . . . . . . . . . 6:18, 6:20 Cos . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:13
Asst . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:14 Create . . . . . . . . . . . . . . . . . . . . . . . . . 6:11
Atan . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:13 Create Site . . . . . . . . . . . . . . . . . . . . . . . 6:4
Atant . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:13 Create Zone . . . . . . . . . . . . . . . . . . . . . . 6:4
Attribute Value . . . . . . . . . . . . . . . . . . . 5:11 Current Element . . . . . . . . . . . . . . . . . . 4:11
Customise . . . . . . . . . . . . . . . . . . . . . . . 8:1
B CYMWRL . . . . . . . . . . . . . . . . . . . . . . . . 5:5
F Occurs . . . . . . . . . . . . . . . . . . . . . . . . . 6:14
Offline Instruments . . . . . . . . . . . . . . . . 5:26
File . . . . . . . . . . . . . . . . . . . . . 4:26, 6:1, 6:2 Open . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:1
Fix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:13 Operators . . . . . . . . . . . . . . . . . . . . . . . 6:13
Format . . . . . . . . . . . . . . . . . . . . . 6:14, 6:15
Function . . . . . . . . . . . . . . . . . . . . . . . . 6:15 P
Functionality . . . . . . . . . . . . . . . . . . . . . . 8:1
Functions . . . . . . . . . . . . . . . . . . . . . . . 6:13 Pan . . . . . . . . . . . . . . . . . . . . . . . . . 3:4, 4:17
Pick Connection . . . . . . . . . . . . . . . . . . 4:13
G Pick Connections . . . . . . . . . . . . . . . . . 4:13
PML . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:1
Getting Started . . . . . . . . . . . . . . . . . . . . 3:1 Print Preview . . . . . . . . . . . . . . . . . . 4:6, 4:9
Project Defaults . . . . . . . . . . . . . . . . . . . 6:4
H Pseudo Attributes . . . . . . . . . . . . . . . . . . 5:4
L S
LEAVE . . . . . . . . . . . . . . . . . . . . . . . . . 6:23 Save . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:2
Left . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:14 Save As . . . . . . . . . . . . . . . . . . . . . . . . . 6:2
Len . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:14 Save Changes . . . . . . . . . . . . . . . . . . . . 6:2
Link . . . 3:7, 4:10, 4:14, 4:21, 5:1, 5:2, 5:26 Save Layout . . . . . . . . . . . . . . . . . . . 4:6, 4:9
Listposition . . . . . . . . . . . . . . . . . . . . . . 6:15 Save Layout As . . . . . . . . . . . . . . . . 4:6, 4:9
Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:13 SCEQUI . . . . . . . . . . . . . . . . . . . . . . . . 6:15
Log10 . . . . . . . . . . . . . . . . . . . . . . . . . . 6:13 Schematic . . . . . . . . . . . . . . . . . . . . . . . 5:2
Lookup . . . . . . . . . . . . . . . . . . . . . . . . . 6:14 Schematic Pipeline . . . . . . . . . . . . . . . . 5:24
Lower . . . . . . . . . . . . . . . . . . . . . . . . . . 6:14 SCSTYP . . . . . . . . . . . . . . . . . . . . 6:21, 6:22
SCVALV . . . . . . . . . . . . . . . . . . . . 6:19, 6:22
M Settings . . . . . . . . . . . . . . . . . . . . . . 4:4, 4:8
Show . . . . . . . . . . . . . . . . . . . . . . . 3:1, 4:19
Macro . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:4 Sin . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:13
Main Bar . . . . . . . . . . . . . . . . . . . . . . . . 4:21 Sqrt . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:13
Main Object . . . . . . . . . . . . . . . . . . . . . . 4:21 STYPE . . . . . . . . . . . . . . . . . . . . . . . . . 6:21
Subs . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:14
Subtype Table . . . . . . . . . 4:1, 4:7, 4:9, 4:14
Subtype Tables . . . . . . . . . . . . . . . . . . . . 4:7
T
Table Layouts . . . . . . . . . . . . . . . . . . . . . 8:2
Tan . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:13
Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . 4:17
Trim . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:14
U
Unlink . . . . . . . . . .3:7, 4:10, 4:21, 5:2, 5:26
Update . . . . . . . . . . . . . . . . . . . . . . . . . 4:31
Upper . . . . . . . . . . . . . . . . . . . . . . . . . . 6:14
V
View . . . . . . . . . . . . . 4:11, 4:14, 4:22, 4:28
Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . 4:18
Z
Zoom . . . . . . . . . . . . . . . . . . . . . . . 3:4, 4:17