Schematic Model Manager User Guide
Pre-configuration : Mapping Set-Up : Attribute Mapping
Attribute Mapping
Attribute Mappings should be configured before loading data as any subsequent changes to the mappings will mean that previously imported data must be re-imported in order for the new mappings to be applied to it. Attribute mappings are crucial to the page matching process and must be correctly configured in order for diagrams to be matched and merged.
If default UDAs are being used, then all of the core attributes from the source data should already be populated, but system-specific attributes stored within the GenericAttributes elements in the import files will not be present. To configure attribute mappings see View/Edit Attribute Mappings.
Note:
The rest of this section is relevant if source data is imported from files in the 3.2.0 format of the ISO 15926 schema. It is not relevant if data is imported from version 3.3.3 files or later.
The source data may use system-specific attributes in order to specify how segments are connected across diagrams. If the source data has been generated using AVEVA P&ID and the Schematic Model Manager default attribute mappings relating to the SCOPCI and SCOPCO schematic database elements have not been amended, then no additional cross-page connectivity related attribute mappings will be required. Pre-configured Attribute mappings for matching page connections are provided with the application.
However, if the source data was generated from an alternative gateway or tool, cross-page connectivity attribute mapping may need to be configured in order to ensure that cross-page connectivity is maintained. To do this:
1.
Find the values of the AttributeName attributes on the CrossPageConnection XML elements in the source data file.
2.
Open the source data file in a tool capable of displaying XML files (the contents of the source file will not need to be edited). Find the values of the AttributeName attributes on the CrossPageConnection XML elements.
The following example shows the CrossPageConnection element in a data source generated by AVEVA P&ID:
In this example the AttributeName attribute of the CrossPageConnection XML element is "PipeId".
3.
Ensure that the Schematic Model Manager source dictionary has been populated from a file or files which match the source data structure that will be used to load P&IDs into the project (see Configure the Source Data Dictionary).
4.
Using the attribute mapping tool, create an attribute mapping which operates on the SCOPCI and SCOPCO schematic database elements. The default attribute mapping may be used on these elements when the Schematic Model Manager is installed as a basis for your custom attribute mapping.
5.
The UDA :Pmgdfltmatch has been defined for storing diagram connection attribute values where only one attribute is used for the connection. Set the database attribute value of the attribute mapping to :Pmgdfltmatch:
6.
The correct source data attribute must now be mapped to the UDA :Pmgdfltmatch, to ensure that page matching occurs.
To do this, click the ellipsis option to the right of the attribute mapping's Source Attribute field. This will open the XPath expression builder:
7.
Navigate to the attribute used in the source data file to store cross-page connectivity matching values.
The source data attribute PipeId is used in the AVEVA Schematic Model Manager Gateway. The example above shows this source attribute and its associated mapping in the Source Dictionary window of the Schematic Model Manager XPath Expression Builder.
8.
A mapping from this source data file attribute to the UDA :Pmgdfltmatch has now been created.
If cross page connectivity in the source data files is represented using more than one attribute, then it will be necessary to create additional UDAs against the SCOPCI and SCOPCO schematic database elements, and to then create additional attribute mappings to ensure that these are populated during an import.
1974 to current year. AVEVA Solutions Limited and its subsidiaries. All rights reserved.
AVEVA Logo