Configure the Get External Data configuration file - Intergraph Spoolgen - Help

Intergraph Spoolgen Help

Language
English
Product
Intergraph Spoolgen
Search by Category
Help
SmartPlant Foundation / SDx Version
10
I-Configure Version
6.0(2016)
Isogen Version
13.0(2016)
Smart Isometrics Version
7.0(2019)
Spoolgen Version
9.0(2019)

Configuring the Get External Data (GED) configuration file involves:

  • Defining specific instructions for each of the elements that are pertinent to your GED solution.

  • Defining the mapping between the data in the external data source to the attributes in the current POD file. For example, you can define mapping for only specific components, or you can create filters so that certain components are excluded from the GED solution.

  • For more information about the format and structure of the of the configuration file, see Appendix: Get External Data Configuration File.

  • For specific examples of how to configure the GED .xml configuration file, see Best Practices using GED.

  • To help you get started using the GED function, a sample external data source file, GetExternalData.xls, and a sample GED .xml configuration file, GetExternalData.xml, are delivered with the software. In a default Spoolgen installation, both files are delivered to the [Installation Drive]:\SampleIsoDir\S5Tutorial\Data\Get External Data folder. In Smart Isometrics, the two files are delivered to the [Installation Drive]:\SampleIsoDir\SPITutorial\Data\Get External Data.

How mapping works

The following example displays the pipeline attribute information for the currently opened POD file (SG-T1.POD).

To demonstrate how mapping works, review the following range of data from the example line list (in Excel format):

To import the spreadsheet data into SG-T1.POD, you must configure the PIPELINE element section of the GED configuration file to define the following:

  • The path to the external data source.

  • The SQL statement that defines the query.

  • The one-to-one mapping of the data in the spreadsheet to the appropriate pipeline attributes in the POD file.

The resulting PIPELINE element section of the GED configuration file should resemble the example below:

1 - <XLS> tag

Defines the path to the source external data. In the example above, the Excel file GetExternalData.xls is defined as the external data source.

2 - <SQL> tag

Defines the query that the software performs when the Get External Data function runs. In the example, the SQL query instructs the software to look for a value in the LINE-REF column of the external data source that matches the PIPELINE-REFERENCE attribute value in the current POD file (SG-T1.POD).

SELECT * FROM PIPELINES WHERE [LINE-REF] = '$P.PIPELINE-REFERENCE$'

When the software runs the query, it finds that the value in cell A2 of the LINE-REF column (SG-T1) matches the PIPELINE-REFERENCE in the POD file (also SG-T1). The software then applies the pipeline attributes as defined in the <EXTERNAL-MAP> tags.

3 - <EXTERNAL-MAP> tag

Specifies how the software maps the data in the spreadsheet to the attributes in the POD file. As shown in the <EXTERNAL-MAP> section of the example configuration file, Name is the POD attribute to be populated, and ExternalName is the field name in the external data source that contains the new value. The pipeline attributes in the POD file are mapped as shown in the table below:

Pipeline Attribute Name

Original Attribute Value

New Attribute Value as
Mapped to
External Data Source

PROJECT-IDENTIFIER

P-500

RM100

AREA

AR-1

Distillation

PIPELINE-TEMP

Undefined

100

PAINTING-SPEC

PNT-1

P-12

MISC-SPEC1

Undefined

300-020

MISC-SPEC2

Undefined

300-033

When the Get External Data function runs, the software updates the attribute values as specified by the GED .xml configuration file.

The structure of the remaining tags is largely identical to the <PIPELINE> tag. However, there is an optional <FILTER> tag that defines a supplementary filter to be applied at each component. The FILTER statement is always used in conjunction with the SQL element and serves to refine the results of evaluating the SQL expression. For more information about defining a <FILTER> tag, as well as detailed information about the elements that make up the configuration file, see Appendix: Get External Data Configuration File.