Working with External Data - 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.2
Spoolgen Version
9.2

The Get External Data (GED) function enables you to set the attributes or properties of the pipelines and components in a Piping Object Data (POD) file by using data contained in spreadsheets or databases. The following example shows a line list in Excel format. The line list contains a range of data to output on the isometric drawing:

LINE-REF

PROJECT

AREA

PID FROM

PID TO

PAINT CODE

SG-T1

RM100

DISTILLATION

300-020

300-033

P12

SG-T2

RM100

DISTILLATION

300-021

300-034

P15

SG-T3

RM100

COOLING WATER

300-022

300-035

P20

SG-T3

RM100

DISTILLATION

300-023

300-036

P25

Using the GED function, you can do the following:

  • Establish a connection to the external data source, such as the spreadsheet used in this example.

  • Specify how to link the information in the external data source to the POD file. Using the example line list, you can use the PIPELINE-REFERENCE attribute in the POD file to find the row in the spreadsheet to use. For example, you can find the row in which the LINE-REF column contains a matching value.

  • Specify the mapping of the data in the spreadsheet to the attributes in the POD file. Using the same line list example, you can map the values in the PROJECT column ito the PROJECT-IDENTIFIER attribute in the POD file.

After you have populated the attributes, you can use standard Isogen features to plot the values on the drawings or output them to a report.

Debugging

GEDDebug is a diagnostic tool that collects information each time that you run the GED function. The generation of GEDDebug information is controlled by a registry entry. After you define the registry setting, the software creates a sub-folder in your local Temp folder (%Temp%) called GedDebug in which to store GED processing results.

For assistance in modifying the registry settings, contact customer support.

An example of the full folder hierarchy is shown below. Processing results are organized in a collection of subfolders within the GedDebug folder that identify the job, the name of which corresponds to the pipeline key (1), and the date and time of the GED run (2).

At the start of the GED process, a copy of each data source referenced in the .xml configuration file and a copy of the original .pod file is placed in the Before folder. When the GED process finishes, an additional copy of each data source is placed in the After folder, along with a copy of the subsequent .pod file.

  • Results of each GED process are written to a .log file and stored in the folder that identifies the pipeline job.

  • The software creates an additional log file called GEDBatchLog.log in the GedDebug folder. This log file provides cumulative details of all of the GED processes.

  • If the pipeline key is ALL, the name of the subfolder that identifies the job corresponds to the first pipeline in the POD instead of the pipeline key.

What do you want to do?