SPIsoI-Data User Guide

SmartPlant Isometrics
I-Data Integrator
User's Guide
Version 2014 (7.0)
April 2014
DISO-PE-200008D
Copyright
Copyright © 2008-2014 Intergraph® Corporation. All Rights Reserved. Intergraph is part of Hexagon.
Including software, file formats, and audiovisual displays; may be used pursuant to applicable software license agreement; contains
confidential and proprietary information of Intergraph and/or third parties which is protected by copyright law, trade secret law, and
international treaty, and may not be provided or otherwise made available without proper authorization from Intergraph Corporation.
U.S. Government Restricted Rights Legend

Use, duplication, or disclosure by the government is subject to restrictions as set forth below. For civilian agencies: This was
developed at private expense and is "restricted computer software" submitted with restricted rights in accordance with
subparagraphs (a) through (d) of the Commercial Computer Software - Restricted Rights clause at 52.227-19 of the Federal
Acquisition Regulations ("FAR") and its successors, and is unpublished and all rights are reserved under the copyright laws of the
United States. For units of the Department of Defense ("DoD"): This is "commercial computer software" as defined at DFARS
252.227-7014 and the rights of the Government are as specified at DFARS 227.7202-3.
Unpublished - rights reserved under the copyright laws of the United States.
Intergraph Corporation
300 Intergraph Way
Huntsville, AL 35813
Documentation
Documentation shall mean, whether in electronic or printed form, User's Guides, Installation Guides, Reference Guides,
Administrator's Guides, Customization Guides, Programmer's Guides, Configuration Guides and Help Guides delivered with a
particular software product.
Other Documentation
Other Documentation shall mean, whether in electronic or printed form and delivered with software or on Intergraph Smart Support,
SharePoint, or box.net, any documentation related to work processes, workflows, and best practices that is provided by Intergraph
as guidance for using a software product.
Terms of Use
a. Use of a software product and Documentation is subject to the End User License Agreement ("EULA") delivered with the
software product unless the Licensee has a valid signed license for this software product with Intergraph Corporation. If the
Licensee has a valid signed license for this software product with Intergraph Corporation, the valid signed license shall take
precedence and govern the use of this software product and Documentation. Subject to the terms contained within the
applicable license agreement, Intergraph Corporation gives Licensee permission to print a reasonable number of copies of the
Documentation as defined in the applicable license agreement and delivered with the software product for Licensee's internal,
non-commercial use. The Documentation may not be printed for resale or redistribution.
b. For use of Documentation or Other Documentation where end user does not receive a EULA or does not have a valid license
agreement with Intergraph, Intergraph grants the Licensee a non-exclusive license to use the Documentation or Other
Documentation for Licensee’s internal non-commercial use. Intergraph Corporation gives Licensee permission to print a
reasonable number of copies of Other Documentation for Licensee’s internal, non-commercial. The Other Documentation may
not be printed for resale or redistribution. This license contained in this subsection b) may be terminated at any time and for any
reason by Intergraph Corporation by giving written notice to Licensee.
Disclaimer of Warranties
Except for any express warranties as may be stated in the EULA or separate license or separate terms and conditions, Intergraph
Corporation disclaims any and all express or implied warranties including, but not limited to the implied warranties of merchantability
and fitness for a particular purpose and nothing stated in, or implied by, this document or its contents shall be considered or deemed
a modification or amendment of such disclaimer. Intergraph believes the information in this publication is accurate as of its
publication date.
The information and the software discussed in this document are subject to change without notice and are subject to applicable
technical product descriptions. Intergraph Corporation is not responsible for any error that may appear in this document.
The software, Documentation and Other Documentation discussed in this document are furnished under a license and may be used
or copied only in accordance with the terms of this license. THE USER OF THE SOFTWARE IS EXPECTED TO MAKE THE FINAL
EVALUATION AS TO THE USEFULNESS OF THE SOFTWARE IN HIS OWN ENVIRONMENT.
Intergraph is not responsible for the accuracy of delivered data including, but not limited to, catalog, reference and symbol data.
Users should verify for themselves that the data is accurate and suitable for their project work.
2 SmartPlant Isometrics
I-Data Integrator User's Guide
Limitation of Damages
IN NO EVENT WILL INTERGRAPH CORPORATION BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL INCIDENTAL,
SPECIAL, OR PUNITIVE DAMAGES, INCLUDING BUT NOT LIMITED TO, LOSS OF USE OR PRODUCTION, LOSS OF
REVENUE OR PROFIT, LOSS OF DATA, OR CLAIMS OF THIRD PARTIES, EVEN IF INTERGRAPH CORPORATION HAS BEEN
ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
UNDER NO CIRCUMSTANCES SHALL INTERGRAPH CORPORATION’S LIABILITY EXCEED THE AMOUNT THAT
INTERGRAPH CORPORATION HAS BEEN PAID BY LICENSEE UNDER THIS AGREEMENT AT THE TIME THE CLAIM IS
MADE. EXCEPT WHERE PROHIBITED BY APPLICABLE LAW, NO CLAIM, REGARDLESS OF FORM, ARISING OUT OF OR IN
CONNECTION WITH THE SUBJECT MATTER OF THIS DOCUMENT MAY BE BROUGHT BY LICENSEE MORE THAN TWO (2)
YEARS AFTER THE EVENT GIVING RISE TO THE CAUSE OF ACTION HAS OCCURRED.
IF UNDER THE LAW RULED APPLICABLE ANY PART OF THIS SECTION IS INVALID, THEN INTERGRAPH LIMITS ITS
LIABILITY TO THE MAXIMUM EXTENT ALLOWED BY SAID LAW.
Export Controls
Intergraph Corporation’s software products and any third-party Software Products obtained from Intergraph Corporation, its
subsidiaries, or distributors (including any Documentation, Other Documentation or technical data related to these products) are
subject to the export control laws and regulations of the United States. Diversion contrary to U.S. law is prohibited. These Software
Products, and the direct product thereof, must not be exported or re-exported, directly or indirectly (including via remote access)
under the following circumstances:
a. To Cuba, Iran, North Korea, Sudan, or Syria, or any national of these countries.
b. To any person or entity listed on any U.S. government denial list, including but not limited to, the U.S. Department of Commerce
Denied Persons, Entities, and Unverified Lists, http://www.bis.doc.gov/complianceandenforcement/liststocheck.htm, the U.S.
Department of Treasury Specially Designated Nationals List, http://www.treas.gov/offices/enforcement/ofac/, and the U.S.
Department of State Debarred List, http://www.pmddtc.state.gov/compliance/debar.html.
c. To any entity when Licensee knows, or has reason to know, the end use of the Software Product is related to the design,
development, production, or use of missiles, chemical, biological, or nuclear weapons, or other un-safeguarded or sensitive
nuclear uses.
d. To any entity when Licensee knows, or has reason to know, that an illegal reshipment will take place.
Any questions regarding export or re-export of these Software Products should be addressed to Intergraph Corporation’s Export
Compliance Department, Huntsville, Alabama 35894, USA.
Trademarks
Intergraph, the Intergraph logo, PDS, SmartPlant, I-Sketch, I-Tools, I-Configure, ISOGEN, CADWorx, SmartSketch, SPOOLGEN,
Sapphire, and Intergraph Smart are trademarks or registered trademarks of Intergraph Corporation or its subsidiaries in the United
States and other countries. Microsoft and Windows are registered trademarks of Microsoft Corporation. All rights reserved. Other
brands and product names are trademarks of their respective owners.
Contents
Preface .......................................................................................................................................................... 7
Documentation Set ................................................................................................................................. 7
Documentation Comments ..................................................................................................................... 8
What's New in SmartPlant Isometrics I-Data Integrator ......................................................................... 8
SmartPlant Isometrics I-Data Integrator.................................................................................................... 9

The I-Data Integrator Interface.............................................................................................................. 13
Recommended Workflow ...................................................................................................................... 14
Configure the Software ............................................................................................................................. 15

Specify the XML configuration file ......................................................................................................... 16
Configure the ISOGEN post-processor ................................................................................................ 16
Input Data ................................................................................................................................................... 19

User-Specified Text (Field Names in Output Data) .............................................................................. 20
Repeatability Return File ....................................................................................................................... 21
Bending File .......................................................................................................................................... 23
Centerline Length File ........................................................................................................................... 26
Output Data ................................................................................................................................................ 27

Output Data Formats ............................................................................................................................ 28
Automatically Generated Data .............................................................................................................. 30
Process Pipeline Files............................................................................................................................... 31

Process files interactively...................................................................................................................... 33
Process files using the command line................................................................................................... 34
View output files .................................................................................................................................... 35
View the log file ..................................................................................................................................... 36
Register the automation interface ......................................................................................................... 36
I-Data Integrator Main Window Options ................................................................................................ 37
Appendix: XML Configuration File Syntax .............................................................................................. 39

<I-DATA-INTEGRATOR-SETTINGS> Section ..................................................................................... 41
<I-DATA-INTEGRATOR-OUTPUT-OPTIONS> Section....................................................................... 43
Appendix: Basic SQL Syntax ................................................................................................................... 51
Glossary ..................................................................................................................................................... 53
Index ........................................................................................................................................................... 55
I-Data Integrator User's Guide 5
Contents
Preface
This document is a user's guide for SmartPlant Isometrics I-Data Integrator and provides
conceptual information and procedural instructions for post-processing the report files produced
by SmartPlant Isometrics, SmartPlant Spoolgen, or ISOGEN and then consolidating the data for
transfer to downstream systems. The content is identical to the online Help that is delivered as
part of the I-Data Integrator software.
Intergraph gives you permission to print as many copies of this document as you need for
non-commercial use at your company. You cannot reprint this document for resale or
redistribution outside your company.
Documentation Set
SmartPlant Isometrics documentation is available as Adobe PDF files. To access these PDF
documents, click Help > Printable Guides in the software.
The documentation set is divided into three categories:
 Installation guides contain information about installing, configuring, customizing, and
troubleshooting the product.
 User's guides provide command reference and how-to information for working in a specific
product. The content is identical to what is delivered in the online Help.
 ISOGEN guides
Installation Guides
SmartPlant Isometrics Installation Guide - Provides instructions on installing and configuring the
SmartPlant Isometrics software.
User's Guides
SmartPlant Isometrics User's Guide - Provides guidelines, procedures, and workflows for using
SmartPlant Isometrics to create isometric drawings.
SmartPlant Isometrics I-Convert User's Guide - Provides guidelines, procedures, and workflows
for converting third party plant design data into a format that is compatible with SmartPlant
Isometrics.
SmartPlant Isometrics I-Data Integrator User's Guide - Provides guidelines, procedures and
workflows for using I-Data Integrator to post-process report files.
SmartPlant Isometrics I-Tools User's Guide - Provides instructions for using I-Tools to produce
piping systems by merging IDF/PCF files from other ISOGEN-enabled products.
SmartPlant Symbol Editor User's Guide - Provides guidelines, procedures, and workflows for
using SmartPlant Symbol Editor to create custom symbol shapes to meet your drawing
annotation needs.
SmartPlant Material Editor User's Guide - Provides instructions for using SmartPlant Material
Editor to create reference data, including catalogs and materials specifications.
Preface
I-Configure User's Guide - Provides guidelines, procedures, and workflows for creating and
managing the isometric directories, projects, and styles used by other products to generate
isometric drawings and reports via ISOGEN.
ISOGEN Configuration User's Guide - Provides guidelines, procedures, and workflows for
configuring the drawing style properties that control ISOGEN isometric drawing and report
output.
ISOGEN Guides
ISOGEN Symbol Key Definitions Reference Guide - Provides information about the ISOGEN
symbol key library. This guide is from Alias, the makers of ISOGEN.
Documentation Comments
We welcome comments or suggestions about this documentation. You can send us an email at:
PPMdoc@intergraph.com.
Documentation updates for supported software versions are available from Intergraph Smart
Support (https://smartsupport.intergraph.com).
What's New in SmartPlant Isometrics I-Data Integrator

The following changes have been made to I-Data Integrator:
Version 2014 (7.0)
 There are no changes to the software in Version 2014.
SmartPlant Isometrics I-Data Integrator
SECTION 1

SmartPlant Isometrics I-Data Integrator reads many of the report files that are produced by
software that supports ISOGEN such as SmartPlant Isometrics and SmartPlant Spoolgen, and
consolidates all the data for transfer to a downstream system. Data in external spreadsheets or
databases can be accessed to supplement what is created by ISOGEN, and script files can be
executed to provide sophisticated data manipulation functions. In its simplest mode, I-Data
Integrator can transfer these report files to a database.
When multiple datasets exist in the ISOGEN data, which can happen if the same pipeline is
repeatedly run through ISOGEN, I-Data Integrator only processes the most recent dataset found
in the file. I-Data Integrator works with a project and style created by I-Configure, a SmartPlant
Spoolgen .opt file, or a PDS .def (PD_ISOGEN Definition) file.
For example, when a batch of data is processed through ISOGEN, the Material Control file can
have the structure shown below:
However, the exact format is user-defined.
reference =
pipeline1
pipespec = spec1
pipeline item_code part_no quantity description
pipeline1 ic1 1 2 flange
pipeline1 ic2 2 10 bolt
pipeline1 ic3 3 4.5M pipe
reference =
pipeline2
pipespec = spec2
pipeline2 ic3 3 3.5M pipe
pipeline2 ic4 4 2 gasket
pipeline2 ic5 5 1 valve
pipeline2
I-Data Integrator then produces two output datasets from this data, either as tables in a
Microsoft Access database or as text files. The first output dataset contains pipeline level data:
reference pipespec
pipeline1 spec1
pipeline2 spec2
The second output dataset contains component data:

pipeline1 ic3 3 4.5 pipe
pipeline2 ic3 3 3.5 pipe
pipeline2 ic4 4 2 gasket
pipeline2 ic5 5 1 valve
Data is output in one of the following formats: an Access database (.mdb), a Microsoft Excel
spreadsheet (.xls), Delimited or Fixed text file, or as an XML file.
 You can configure the delimited format as a comma delimited (.csv) for compatibility with
spreadsheets and databases, or as a tab delimited file, such as the PDS .b file.
 Fixed format files have fixed starting columns and can be used to replicate legacy output
files from a number of systems.
 Two types of XML data are supported. The first type is suitable for loading into the AES/32
application (see www.nhd.com ). The second type is an Alias-developed format.
I-Data Integrator files contain whatever data is in the ISOGEN Material Control, Welding, Spool
Information, Bending, Centerline, Repeat, or Cut List report files. This is the data that is reflected
in the I-Data Integrator output files. Furthermore, you can use information from external sources
such as databases, spreadsheets and other text files to supplement the standard ASCII
ISOGEN output report file data in order to provide one complete set of data in the format that
you require.
SmartPlant Isometrics does not automatically accumulate material. This is done by adding
queries to the configuration file or by using the reporting tools in other software products, such
as Microsoft Access.
 A template database is supplied with I-Data Integrator, which includes a number of

predefined reports that can be used to accumulate material over a project, area or pipeline
basis; however, these are intended only as a guide for helping you to develop your own.
 Although I-Data Integrator is not a material control system, the software can provide
information about the material used in a set of isometrics.
Key Features
SmartPlant Isometrics I-Data Integrator has the following key features:
 By default, the software strips out all but the most recent dataset for each pipeline
encountered.
 Interactive, command line or Automation execution. For more information, see Process
Pipeline Files (on page 31).
 Mandatory, user-configurable XML options file. The file consists of the two sections. The first
section contains user settings, including those displayed in the interface, and a few
additional settings, such as controlling the log file. The second section describes the output
options. For more information, see Appendix: XML Configuration File Syntax (on page 39).
 Data from ISOGEN can be integrated with external data, including Access databases, Excel
spreadsheets, or any ODBC compliant data source, such as an Oracle or SQL Server
database. A further option for external data is to extract a set of data from PCF, IDF or POD
files.
 You can generate new datasets from the ISOGEN data and the new external data sources
using SQL statements to manipulate them. For more information, see
<GENERATED-DATA> in <I-DATA-INTEGRATOR-OUTPUT-OPTIONS> Section (on page
43).
 ISOGEN or generated data can be further processed using scripts
 Output datasets can be re-named or suppressed. For more information, see
<OUTPUT-CONTROLS> in <I-DATA-INTEGRATOR-OUTPUT-OPTIONS> Section (on page
43).
 When using Excel output formats, you can specify the spreadsheet to write to and in which
sheet and cell to start writing the output.
 When using delimited output formats, you can specify the delimiter character, an optional
quote ( " ) character, and the file extension. For example, it is possible to output data in
Intergraph PDS Tab delimited format, such as the .b file. For more information, see
<OUTPUT-FORMATS> in <I-DATA-INTEGRATOR-OUTPUT-OPTIONS> Section (on page
43).
 You can specify the template database used by the Microsoft Access output format so that
predefined reports are automatically available in the output database.
 I-Data Integrator reads the ISOGEN Bending file and can create datasets for cut pieces,
pipe (pulled) bends, and holes. For more information, see Bending File (on page 22).
 I-Data Integrator reads the ISOGEN CenterlineLength Summary and user-defined Cut List
report files. For more information, see Centerline Length File (on page 25).
 The Repeatability Return file is read if specified in the .fls or .opt file. For more information,
see Repeatability Return File (on page 20).
 Recordsets can be split using a nominated field, for example, to split a component's
recordset by pipeline into separate output files or tables. For more information, see
<OUTPUT-CONTROLS> in <I-DATA-INTEGRATOR-OUTPUT-OPTIONS> Section (on page
43).
 Recordsets can be merged into Master/Detail outputs (delimited format only), where a
record in the Master recordset is followed by all records in the Detail recordset that meet a
user-specified criterion. For more information, see <OUTPUT-FORMATS> in
<I-DATA-INTEGRATOR-OUTPUT-OPTIONS> Section (on page 43).
 Generated recordsets are stored as queries in the temporary database.
I-Data Integrator stores/restores all your choices to the Main window each time it opens up, as
defined by the settings in the XML options file. For more information, see The I-Data Integrator
Interface (on page 12).
The I-Data Integrator Interface

Each time you open I-Data Integrator, the Main window is displayed.
Setting Processing Options

You use the options on the Main window to define the various parameters that are required for
the current post-processing event. You must define parameters for the following four types of
processing options:
 A - Configuration File
Specifies the path to the XML configuration file, which defines both the input and output
options for the structure and content of the output format data files. For more information,
see Appendix: XML Configuration File Syntax (on page 39).
 B - Input Data
Controls whether the software reads ISOGEN report files or a set of IDF/PCF/POD files for
the specified style. For more information, see Input Data (on page 19).
 C - Isometric drawing style
Specifies the drawing style to be used. You can choose between the ISOGEN style defined
within I-Configure, you can use the ISOGEN.fls or SPOOLGEN.opt files. For more
information, see I-Data Integrator Main Window Options (on page 37).
 D - Output data
Defines the output format for the data that is processed and specifies the folder location
where the output data is written. For more information, see Output Data (on page 27).
Recommended Workflow
When the same pipeline is repeatedly run through ISOGEN, the material for each run is
appended to the Material Control, Weld Summary, Spool Information and Bending files. I-Data
Integrator strips out everything but the most recent set of data for each pipeline. In other words,
each time that you run I-Data Integrator, it produces data that reflects the current state of the set
of pipelines that have been processed through SmartPlant Isometrics or SmartPlant Spoolgen.
The recommended practice is to set up a style that is used to process pipelines when they have
reached their final state. The drawings and data reports produced by this style are often the
completed deliverables from a project.
When you use SmartPlant Isometrics, there are two options for producing final issue isometric
drawings from the project:
 Single pipeline processing - Use the Generate Drawings command to process each
pipeline individually to produce drawings and data, appended to the output reports.
 Multiple pipelines processing - Use the Batch Generate Drawings command to process
a batch of pipes and generate both the drawings and output reports automatically.
For more information about SmartPlant Isometrics drawing generation, see the
SmartPlant Isometrics User's Guide, available using the Help > Printable Guides command in
the software.
You can run I-Data Integrator only once, typically at the end of the project, to produce a
consolidated and accumulated set of materials that require purchasing. Alternatively, you can
run I-Data Integrator on a daily or weekly basis as the project progresses. In the latter scenario,
automatically deleting the material files from SmartPlant Isometrics and SmartPlant Spoolgen
after running I-Data Integrator ensures that the software only collects material from the last run.
The command line execution option is typically used in this scenario because it allows you to
schedule an automated batch process to run at regular intervals to convert the current output
files.
I-Data Integrator is not a material control system. It is intended to serve as a link to such
a system.
Configure the Software

The software requires an XML configuration file to perform any kind of post-processing activity.
This configuration file contains specific instructions for how the software is to behave during
processing. By default, the software delivers a template configuration file, Default.xml, to the
[Installation Drive]:\SampleIsoDir\SPITutorial\Data\I-Data Integrator\Configuration folder during
installation. When you initially open I-Data Integrator, the software retrieves the template XML
file from the default location, loads it, and then opens the I-Data Integrator Main window. If the
software is unable to locate the Default.xml file, a message displays asking you to specify the
XML configuration file that should be used.
Because the default configuration file (Default.xml) delivered with the software only
contains the initial heading information, you will need to modify to suit your specific
post-processing requirements. For more information about the content of the configuration file,
see Appendix: XML Configuration File Syntax (on page 39).
ISOGEN Post-Processor
IDIPost.exe, a special application to be run as an ISOGEN post-processor, is delivered with
I-Data Integrator. IDIPost.exe is only available for use with Personal ISOGEN-enabled
applications, such as SmartPlant Isometrics and SmartPlant Spoolgen, and it enables the
insertion of the FILENAME field into all intrinsic recordsets.
What do you want to do?

 Specify the XML configuration file (on page 15)
 Configure the ISOGEN post-processor (on page 16)
Specify the XML configuration file

The first time that you use I-Data Integrator, the software searches for the default configuration
file called Default.xml. If the software is unable to locate this file, you are prompted to specify a
configuration file.
1. Click Yes in the message box that displays when you open the software.
The Choose XML Configuration File to Open dialog box displays.
2. Navigate to the required configuration file, and click Open.
The software loads the configuration file and opens the I-Data Integrator window.
If you are using an XML configuration that was created for a previous version of the
software, the following message displays:
To update the configuration file so that it is compatible with the current version of the software,
click Yes.
Configure the ISOGEN post-processor

1. Click Start > All Programs > SmartPlant Isometrics > I-Configure.
I-Configure opens.
2. In the Project View panel, select the appropriate isometric directory and project.
3. Under the active project, select the appropriate isometric drawing style, and then click Edit.
Alternatively, right-click the drawing style, and then click Edit.
The ISOGEN Configuration Panel opens.
4. On the Home screen, select Pre and Post Processors on the Drawing Manager panel.
The Configuration View appears.
5. In the Post-processor box, type the full path location and file name of the ISOGEN
post-processor file, Alternatively, click the browse button and navigate to the file
By default, IDIPost.exe is delivered to the C:\Program
Files\SmartPlant\Isometrics\I-Data Integrator folder during installation. Versions of Personal
ISOGEN prior 5.2.2.2 do not support spaces in the path name; consequently, you must
move IDIPost.exe to a different location in order for it to work.
6. Click to update the active style file with the new property settings.
7. Click to close the ISOGEN Configuration Panel, and then click File > Exit to close
I-Configure.
Using IDIPost.exe is only necessary if the FILENAME field is required in all intrinsic
recordsets. Unless the particular dataset requires it, there is no need to implement this feature.
See Also
Automatically Generated Data (on page 29)
SECTION 2
Input Data
SmartPlant Isometrics I-Data Integrator processes the ISOGEN output report files listed in the
table below. Output of these files is controlled in I-Configure. You set up these reports using the
ISOGEN Configuration Panel. For more information, see the ISOGEN Configuration User's
Guide, which is available using the Help > Printable Guides command in the software.
I-Configure File Property FLS Entry OPT Entry
MaterialList.SummaryFile MATERIAL-CONTROL -104
WeldList.SummaryFile WELD-SUMMARY-APPEND -125
Supplementary.SpoolInformation SPOOL-INFORMATION-FILE -154
Supplementary.BendingReport BENDING-FILE-APPEND -127
CutList.SummaryFile CUT-LIST-SUMMARY-APPEND -129
Supplementary.ReportFiles only CENTRELINE-LENGTH -109
Supplementary.RepeatFile REPEATABILITY-RETURN -117
Supplementary.ReportFiles only DRAWING-CROSS-REF-FILE -158
Supplementary.ReportFiles only SITE-ASSEMBLY-FILE-APPEND -164
In most cases, the format and content of the output file must be specified using an input file, as
shown in the following table. In the indicated cases, the ISOGEN report file is a fixed format.
Output FLS definition OPT Definition
MATERIAL CONTROL MATERIAL-LIST-DEFINITION -122
CUT-LIST-SUMMARY MATERIAL-LIST-DEFINITION -122
WELD SUMMARY WELDING-DEFINITION -120
SPOOL INFORMATION DRAWING-DEFINITION -123
DRAWING-CROSS-REF DRAWING-DEFINITION -158
SITE-ASSEMBLY-FILE-APPEND FUNCTION-DEFINITION -140
BENDING, CUTTING & HOLE

INFORMATION
Fixed format file structure output automatically by ISOGEN.
CENTRELINE-LENGTH
Input Data
REPEATABILITY RETURN
 For a description of how I-Data Integrator behaves, see Output Data (on page 27).
 Only the standard template configuration file is necessary to convert ISOGEN report data to
the required output format.
ISOGEN Input/Output File Configuration

You can configure Material Control, Welding, Cut Piece and Spool Information output report files
(in ASCII format) using I-Configure (SmartPlant Isometrics files, SmartPlant Spoolgen files) or
by editing the ISOGEN input (run-time) control files. The recommended method is to use the
ISOGEN Configuration Panel to configure the required reports.
Bending, Repeatability Return, and Centerline Length files are fixed format and can be
specified to ISOGEN only as an output report.
See Also
User-Specified Text (Field Names in Output Data) (on page 20)
Repeatability Return File (on page 20)
Bending File (on page 22)
Centerline Length File (on page 25)
User-Specified Text (Field Names in Output Data)

I-Data Integrator uses the user-specified text as the field name when processing the TitleText
lines (PRINTED-M/C-TITLES data). In the example below, the software generates a field called
Pipeline in the output data.
Pipeline 'PIPELINE-REFERENCE'
I-Data Integrator sets the field name using the attribute name of the column in the report (or the
entry in the DATA-ITEMS section of the MLD, DDF, or WDF). In the next example, the software
generates a field called PIPELINE-REFERENCE in the output data.
'PIPELINE-REFERENCE' 1 L
You can modify this behavior by placing the required field name in brackets (< >) after a
comment character (!). In the following example, the software generates fields called PipelineID
in the output data. In SmartPlant I-Configure, you set the Comment property on the column.
PRINTED-M/C-TITLES
Pipeline 'PIPELINE-REFERENCE' ! <PipelineID>
PRINTED-M/C-DATA-ITEMS
'PIPELINE-REFERENCE' 1 L ! <PipelineID>
This applies to SmartPlant Isometrics, ISOGEN, and SmartPlant Spoolgen input control
files, which are usually generated automatically by I-Configure.
See Also
Input Data (on page 19)
Input Data
Repeatability Return File

If you specify a RepeatFile in I-Configure, a Repeatabiltiy Return file in the .FLS file, or a –117
record in the SmartPlant Spoolgen .OPT file, I-Data Integrator reads the generated file,
consolidates it, and then creates two new intrinsic recordsets: Components_2 and Welds_2.
Both of these recordsets can be processed in the same way as intrinsic recordsets that are
created from the Material Control, Welding, Spool Information, or Bending files.
You must use the ASCII repeat file option. Set Option Switch 109 Position 1 to 7 Intergraph
Corporation. I-Data Integrator reads the option switch settings and does not attempt to read the
Repeatability file unless this value is set.
Components_2 Recordset
The Components_2 table contains the following fields:
Field Description
PIPELINE Pipeline reference.
DRG Drawing number.
PT-NO Part number – ISOGEN generated, 1,2,3…
Unique part number. This is the same as PT-NO if unique part numbering is
UPN not used or set to the ISOGEN generated unique part number if it is (for
example, 1.1, 1.2, 1.3, 2.1, and so on).
NS Nominal size in the current bore units (as specified by Option Switch 41).
The ISOGEN record type (for example, 100 for pipe, 130 for valve, and so
RECORDTYPE
on).
CATEGORY The category – NONE, FAB, EREC, OFF.
UCI The unique component identifier.
Y The component position.
Seq Sequence number in the repeat file
If unique component identifiers are not present in the input file (IDF or PCF), the software
does not generate any component records.
Input Data
Welds_2 Recordset
The Welds_2 table contains the following fields:
Field Description
PIPELINE Pipeline reference.
DRG Drawing number.
WELD-NO Part number – ISOGEN generated, 1,2,3…
NS Nominal size in the current bore units (as specified by option switch 41).
SKEY The ISOGEN SKEY (for example, WW, WS, and so on).
START_CPT The unique component identifier for the component at the weld “start”.
START_X
START_Y The start component position for the weld.
START_Z
FINISH_CPT The unique component identifier for the component at the weld “finish”.
FINISH_X
FINISH_Y The finish component position for the weld.
FINISH_Z
The format of the repeat file is fixed. The presence of the REPEATABILITY-RETURN or –117
record in the .FLS or .OPT file, respectively, is sufficient to trigger I-Data Integrator to read the
data.
See Also
Input Data
Bending File
If you specify a Bending file in the .FLS file, or a –127 record in the SmartPlant Spoolgen .OPT
file, the software reads the generated file, consolidates it and then creates three intrinsic
recordsets: Bends, CutPieces, and Holes. These can be processed in the same way as other
intrinsic recordsets created from the Material Control, Welding, Spool Information or
Repeatability files.
Bends Recordset
Field Description
PIPELINE Indicates the pipeline reference (*).
SPOOL-ID Indicates the spool ID (*).
CUT-ID Indicates the cut piece ID (*).
PIPING-SPEC Indicates the piping specification (*).
ITEM-CODE Indicates the pipe item code (*).
ND Indicates the nominal diameter (*).
UMI Indicates the generated unique material identifier. Used to link to other tables (*).
NUMBER Indicates the bend number.
Y Indicates the bend position.
RADIUS Indicates the bend radius.
ANGLE Indicates the bend angle.
Input Data
CutPieces Recordset
Field Description
ITEM-CODE Indicates the item code. (*).
ND Indicates the nominal diameter (*).
START-X
START-Y Indicates the start point.
START-Z
FINISH-X
FINISH-Y Indicates the end point.
FINISH-Z
CUT-ID Indicates the cut piece ID.
PART-NUMBER Indicates the part number.
OD Indicates the outside diameter.
WALL-THICKNESS Indicates the pipe thickness (if set).
CUT-LENGTH Indicates the total length.
DEV-LENGTH Indicates the developed length (allowing for weld gaps, and so on).
START-COMPONENT Indicates the start component type (flange, for example).
START-COMP-CODE Indicates the start component item code.
START-COMP-PART-NO Indicates the part number.
START-COMP-LENGTH Indicates the length.
START-END-TYPE Indicates the IDF record number (Flange=105, for example).
FINISH-COMPONENT Indicates the finish component type (flange, for example).
Input Data
Field Description
FINISH-COMP-CODE Indicates the finish component item code.
Field Description
FINISH-COMP-PART-NO Indicates the part number.
FINISH-COMP-LENGTH Length.
FINISH-END-TYPE Indicates the IDF record number (Flange=105, for example).
NUM-HOLES-TO-BE-CUT Indicates the number of holes in cut piece.
Holes Recordset
Field Description
ITEM-CODE Indicates the item code (*).
ND Indicates the nominal diameter.
HOLE-NUM Indicates the hole number.
HOLE-COMP-PART-NO Indicates the part for component with hole.
HOLE-DIAMETER Indicates the hole diameter.
HOLE-INTSECN- ANGLE Indicates the intersection angle.
HOLE-CENTRE- OFFSET Indicates the offset.
HOLE-ROTATION- ANGLE Indicates the rotation angle.
HOLE-DISTANCE Indicates the distance from cut piece start.
 Fields marked with an asterisk ( * ) are always present. Other fields are present depending
on the content of the Bending file (which is subject to change). The Bends and Holes
recordsets are not created if there are no bends (pulled bends) or holes in the ISOGEN data.
 See the ISOGEN documentation for a full description of these parameters.
See Also
Input Data
Centerline Length File

If you specify a centerline length file in the .FLS file or a –109 record in the SmartPlant Spoolgen
.opt file, the software reads the generated file, consolidates it, and then creates an intrinsic
recordset called CentrelineLength. You can process this recordset in the same way as other
intrinsic recordsets that are created from the Material Control, Welding, Spool Information, Cut
Piece, Repeatability or Bending files.
CentreLineLength Recordset
Field Description
BATCH Indicates the batch/area identifier.
PIPELINE- REFERENCE Indicates the pipeline reference.
PIPING-SPEC Indicates the piping specification.
NS Indicates the nominal diameter.
Indicates the calculated centerline length for the pipeline/piping specification

CLL
/nominal size combination.
See Also
Output Data
SECTION 3
Output Data
SmartPlant Isometrics I-Data Integrator can create the output data formats listed below.
 Delimited (.csv)
 Alias XML (a special version of XML)
 Microsoft Access database tables
 Fixed Text
 Microsoft Excel spreadsheets
 AES/32 XML
AES/32 is a third party application program, which supplies costing data for projects.
For additional information, see www.nhd.com.
All output data is created in the same format.
Intrinsic Data Outputs

Internally, the data from the ISOGEN files is loaded into a series of recordsets, as shown in the
table below.
ISOGEN Report File Section I-Data Recordset Name
Material Control Pipeline header data (Titles) Pipelines
Material Control Component data (Data) Components
Spool Information File Spools
Weld Summary Welds
Bend Bends
Bending File Cut Pieces CutPieces
Holes Holes
Component data Components_2

Repeat File
Weld data Welds_2
Cut Piece List CutListSummary
CentreLine Length CentreLineLength
Drawing Cross Reference Drawings
Output Data
These recordsets can be output into the specified output files or processed using SQL
statements in the output options configuration file. To distinguish them further, these recordsets
are known as the intrinsic recordsets, which can be created by SQL statements or by linking to
external data sources.
External Data Outputs

External data, such as data contained within linked tables or read from batches of PCF and IDF
files, is never output.
See Also
Appendix: XML Configuration File Syntax (on page 39)
Output Data Formats (on page 28)
Output Data Formats

You define the format of the output data using the Output format list on the Main window. For
more information about these options, see SmartPlant Isometrics I-Data Integrator Main
Window Options in Process files interactively (on page 33).
Access Data
If you select Access in the Output format list, the software looks for a template database called
template.mdb in the same folder that contains the I-Data Integrator executable (I-Data
Integrator.exe).
 By default, the template.MDB file is delivered is delivered to the C:\Program

Files\SmartPlant\Isometrics\I-Data Integrator folder during installation.
 Alternatively, you can create your own template.MDB file. If the database resides in a
location other than the default location, you must specify the explicit path to the user-defined
template.MDB file in the XML output options input control file.
Output Data
Delimited Data
You can open and view delimited data deliverables using a standard text editor, such as
TextPad, or using Microsoft Excel.
 Excel
 Text Editor (TextPad)
AES/32 XML Data

For additional information about the AES/32 software product, see www.nhd.com.
Contact Intergraph Support if you want to integrate external, generated and ISOGEN
data with this software product.
See Also
Output Data
Automatically Generated Data

All intrinsic and generated recordsets have a RecordID field added. RecordID is an
auto-incremented field that can be useful in uniquely tagging a row in a given recordset.
External datasets created from sets of PCFs or IDFs have a FILENAME field added.
FILENAME is the name of the file that has been read in, with no path or extension.
I-Data Integrator also inserts a FILENAME field (base name of the original PCF or IDF) into all
intrinsic recordsets (Components, Welds, Components_2, Welds_2, CutPieces, Bends, Holes,
CutListSummary, CentrelineLength). However, this field is not populated unless the ISOGEN
post-processor is run as part of the ISOGEN execution. This creates additional entries in the
ISOGEN output files. When this is active, the software uses a combination of FILENAME +
PIPELINE-REFERENCE when filtering recordsets. The significance of this is that in some
cases, PIPELINE-REFERENCE is not unique. That is, the same pipeline reference can occur in
more than one IDF or PCF, where this represents a line that extends over more than one plant
area.
The ISOGEN post-processor, IDIPost.exe, is delivered with the software. For more
information, see ISOGEN Post-Processor in Configure the Software (on page 14).
Process Pipeline Files
SECTION 4

You can run I-Data Integrator interactively or directly from the command line, using a set of
switches to specify specific actions that you want the software to perform. Alternatively, you can
use the automation interface to instantiate I-Data Integrator using another application.
Automation Interface
The automation interface allows I-Data Integrator to be instantiated by another application more
efficiently than using the command line interface. You trigger the data generation process using
an ExecuteConfigFile method.
Before using the automation interface, you must first register it. For more
information, see Register the automation interface (on page 36).
.NET Implementation
Information applies to Visual C++, C# and VB.NET. Use the Application2 object. The key
function of the interface is:
 ExecuteConfigFile (String) - All data required to run I-Data Integrator is contained in the
configuration file. All the previous properties on the interface should be considered obsolete,
but have been retained for backward compatibility.
Visual Basic Implementation
Information applies to Visual Basic v6.0, using the obsolete Application object. On the Project >
References tab, select Alias I-Data Integrator Application.
Properties of the Automation Interface

 ConfigFile (String) - Specifies the path to the XML configuration file. This is equivalent to
the command line /u option.
 ErrorString (String, Readonly) - Returns a string containing a description of the problem if
an error occurs.
Events Raised by the Interface

 StatusChange (strText As String) - The event is raised when the status bar is updated.
The strText parameter is set to the string being posted in the status bar. This is intended to
allow a client application to show progress messages.
Private WithEvents appIDI As IDataIntegrator.Application
Private Sub appIDI_StatusChange(strText As String)
' Status change event
Label1 = strText
DoEvents
End Sub
 ErrorInGeneratedData (strError As String) -The event is raised if the software finds an
error during its Generate step, and allows the calling application to flag this to the user. The
strError string holds the error description.
 Example code (VB.NET)
Dim appIDI As IDataIntegrator.Application
Set appIDI = New IDataIntegrator.Application
appIDI.ExecuteConfigFile strXmlFilePath
 Example code (VB6)
Dim appIDI As IDataIntegrator.Application
Set appIDI = New IDataIntegrator.Application
‘ Set properties
appIDI.StyleFile = "c:\sampleproj\sampleproject\ap\isogen.fls"
appIDI.Clear = False
appIDI.ConfigFile = "c:\users\dev\isogen utilities\i-data
integrator\ap.xml"
appIDI.Format = "Access"
appIDI.LogFile = "c:\temp\appIDI.log"
appIDI.OutputFolder = "c:\sampleproj\sampleproject\ap\reports"
' Execute the application
appIDI.Execute
I-Data Integrator Main Window Options (on page 37)
What do you want to do?

 Process files interactively (on page 33)
 Process files using the command line (on page 34)
 View output files (on page 35)
 View the log file (on page 36)
 Register the automation interface (on page 36)
Process files interactively

When you execute post-processing activities interactively, you use the options on the Main
window to define the various parameters that are required for the current post-processing event.
1. Click Start > All Programs > Intergraph SmartPlant Isometrics > Tools > I-Data
Integrator
2. If necessary, click Browse , and navigate to the configuration file that you want to use.
Alternatively, click File > Open and then navigate to the configuration file that you want to
use.
 Unless otherwise specified, the software automatically uses the configuration file from
your last session with the software.
 If you specify an XML configuration that was created for a previous version of the
software, the following message is displayed:
Click Yes to update the configuration file so that it is compatible with the current version
of the software.
The I-Data Integrator software opens and displays the main window.
3. Next, specify the type of input data you want to use.
 By default, Use report files is selected, which instructs the software to read all of the
ISOGEN report data.
 If you select Input files only, the specific input files you want the software to read must
be specified in the configuration file that you are using to process the pipeline data.
4. In the Isometric drawing style section, do one of the following:
 Select Use I-Configure to specify the ISOGEN style defined within I-Configure and then
use the list boxes to select the Isometric directory, Project, and Isometric style that
you want to use.
 Select Browse for style and then click Browse to navigate to the ISOGEN.fls or
SPOOLGEN.opt file that you want to use.
5. Select an output type in the Output format list.
6. Click Browse and navigate to the Output directory folder where the post-processing
output data is to be written.
7. Click Generate to begin processing the pipeline data.

After processing is successfully completed, the software displays a message similar to the
example below.
8. Click OK to close the message box.
 The software remembers your configuration file between sessions and automatically stores
all the options displayed on the I-Data Integrator Main window in XML configuration file.
 You can also initiate processing from the command line or by using the automation
interface.
See Also
Output Data (on page 27)
Process files using the command line

You can execute I-Data Integrator using the command line. The software runs silently, writing all
output to a specified log file. You can specify a series of command line parameters to control the
execution of the software.
Syntax
I-Data Integrator/s style file /o output directory [/l log file ] [/f
output format] [/c]
/s - Specifies the path to the style file (FLS or OPT). Spaces are permitted in the path. This
parameter is required.
/s C:\SampleProj\SampleProject\Final-Basic\ISOGEN.fls
/o - Specifies the path to the folder to contain the output files. Spaces are permitted in the path
name. This parameter is required.
/o C:\SampleProj\SampleProject\Final-Basic\Reports
/l - Specifies a name for log file. This parameter is optional. If it is not specified, the log file is
written to the style file folder, with the name matconvert.log.
/l C:\SampleProj\SampleProject\Final-Basic\projectA.log
/f - Specifies the output format. This parameter is optional. If it is not specified, the first (default)
format from the list displayed on the SmartPlant Isometrics I- Data Integrator window is used.
This string is not case sensitive. For example, ACCESS is the same as access and Access.
/f Access
/f Delimited
/c - Optional clear flag (no parameters). If present on the command line, I-Data Integrator
automatically deletes all the ISOGEN data files after converting them to the specified format.
/u - Species the user configuration file used to pass the name of the user-specified XML
configuration file to I-Data Integrator when it is being run in batch.
/u user_output_options_file
Example Log File

I-Data Integrator executed at 07/01/02 15:41:58
Configuration file =
C:\SampleIsoDir\S5Tutorial\data\I-Data\Default.xml
Style = C:\SampleIsoDir\S5Tutorial\Final-Basic\ISOGEN.fls
Output Format = Access
Output directory = C:\SampleIsoDir\S5Tutorial\Final-Basic\Reports
Delete ISOGEN data = True
Data written to
C:\SampleIsoDir\S5Tutorial\Final-Basic\Reports\Materials.mdb
Table : Pipeline
Table : Components
See Also
View output files

After the software finishes processing the pipeline data files, you can quickly and easily review
the generated output data.
1. On the I-Data Integrator Main window, click View.
For Excel and Access output data, the software automatically opens the corresponding
Microsoft software and displays the output data.
2. For delimited, fixed text, and XML formats, use the Select File to View dialog box to
navigate to the file you want to view and then click Open.
The software displays the contents of the selected file.
View the log file

Processing results are written to the log file that you define in the configuration XML file. The log
file contains information such as the post-processing start and stop times, configuration
information, as well as input and output data. Also, any errors that occur during processing are
detailed in the log file. An example of a log file is shown below.
You can view the results data for the last generate event using your default text editor.
 On the Main window, click File > View Log File.
The software opens the log file using your default text editor:
Alternatively, navigate to your local Temp folder, and double-click I-Data Integrator.log.
Register the automation interface

1. Click Start > Run.
2. In the Open dialog box, type the following command:
regsvr32 c:\program files\alias\I-Data Integrator\I-Data
Integrator.exe
3. Click OK.
I-Data Integrator Main Window Options

Configuration file - Specifies the path to the user-defined XML configuration file, which defines
both the input and output options for the structure and content of the output format data files.
 A sample template file called default.xml is delivered with the software to the [Installation
Drive]\SampleIsoDir\SPITutorial\Data\I-Data Integrator\Configuration folder.
 When using the default template XML file, it is recommended that you copy it to a location
relevant to the current project, such as the project Data folder.
Input Data - Controls whether the software reads report files for the specified style. The Use
report files option is the initial setting. If you select Input files only, you must also specify a set
of IDF/PCF/POD files to be used in the output options.
Use I-Configure - Specifies the ISOGEN style defined with SmartPlant I-Configure when
working with SmartPlant Isometrics and SmartPlant Spoolgen. The three lists show all available
isometric directories, projects and styles. SmartPlant Isometrics I-Data Integrator stores and
restores the selected style between sessions from the configuration file
 Browse for style - Allows you to specify an ISOGEN style file directly using the Specify
ISOGEN FLS or SPOOLGEN.OPT dialog box. To open the dialog box and navigate to the
ISOGEN style file, click Browse .
 To specify a PDS DEF file, click PDS DEF File (*.DEF) in the Files of type list and then
navigate to the appropriate file.
 When you select a PDS DEF file in the Browse for style operation, the software
displays an additional field in which you can type location of the ISOGEN output files
created when executed from PDS (the DEF file does not contain this information).
Output format - Defines the output format for the data that is processed. You can select
Delimited, AES 32XML, Alias XML, Fixed Text, or Excel.
Output directory - Specifies the folder location where the output data is written.
View - Attempts to open any output previously generated by SmartPlant Isometrics I-Data
Integrator. If the output options indicate that multiple files could have been generated the folder
holding these files is opened.
Clear - Deletes any material control, weld summary or spool information files referenced in the
style file. You can use it after processing a set of data as a convenient way of setting up the
software for subsequent runs.
Generate - Starts the conversion of the specified material control, weld summary and spool
information data into the selected output format. Alternatively, you can click Tools > Generate
Material File.
Close - Exits the software. Alternatively, you can click File > Exit.
APPENDIX A
Appendix: XML Configuration File

Syntax
To convert ISOGEN report data to the required output format, you can modify the standard
template configuration file, Default.xml, that is delivered with the software. Alternatively, you can
create an XML configuration file from scratch using a text editor, such as Notepad.
In a default installation, the Default.xml file is delivered to the [Installation
Folder]\Program Files\SmartPlant Isometrics\I-Data Integrator folder.
The configuration file is in XML format. Its basic layout is shown in the example below.
Configuration File Syntax

The configuration file consists of the sections listed below, each of which contains specific
definitions that control pipeline processing. Some sections are further divided into smaller
sections that control specific functions.
A - <I-DATA-INTEGRATOR-SETTINGS>
Contains all the settings required to run the software. It largely reflects the options shown in the
Main window, with the addition of a few other options. This section of the configuration file is
mandatory.
Appendix: XML Configuration File Syntax
B - <I-DATA-INTEGRATOR-OUTPUT-OPTIONS>
Controls how the software behaves during the conversion process. It is used to specify links to
external data, what new generated data is to be created, and what scripts are to be run when
the dataset is processed. This section of the configuration file is typically divided into the four
sub-sections listed below.
 1 - <EXTERNAL-DATA>
 2 - <GENERATED-DATA>
 3 - <OUTPUT-CONTROLS>
 4 - <OUTPUT-FORMATS>
In This Appendix
<I-DATA-INTEGRATOR-SETTINGS> Section ..............................40
<I-DATA-INTEGRATOR-OUTPUT-OPTIONS> Section ................43
<I-DATA-INTEGRATOR-SETTINGS> Section
Contains the settings required to run I-Data Integrator. Any changes that you make to the
options in the I-Data Integrator Main window are also reflected in this section of the XML
configuration file.
<INPUT-DATA>
<INPUT-DATA Enabled="Yes" ProjManStyle="No" Filter="Yes" Clear="No">
<STYLE-DATA IsoDir="c:\SampleIsoDir" Project="S5Tutorial"
Style="Final-Basic"/>
<CONTROL-FILE
Path="C:\SampleIsoDir\SPITutorial\Final-Basic\isogen.fls"/>
The <INPUT-DATA> tag contains four attributes.
 ENABLED - Determines whether any report is to be processed. This attribute matches the
Use Report Files option in the software. Setting this option to Yes ensures that the ISOGEN
report files are read as part of the processing sequence.
 PROJMANSTYLE - Specifies how the software locates the reports to be read. If set to Yes,
I-Data Integrator uses the SmartPlant I-Configure project setting defined in the
<STYLE-DATA> tag to locate the report data. If set to No, the software uses the
<CONTROL-FILE> tag to locate the reports. This attribute matches the Use I-Configure or
Browse for style options in the Main window.
 FILTER - Controls which version of the pipeline is read if there are repeated pipelines in the
report files. If set to Yes, only the most recent version of the pipeline. This option is no
longer available through the user interface.
 Clear - Controls whether report files are deleted. If set to Yes, the report files are deleted
when processing completes. Usually, this attribute is set to No. It is equivalent to clicking
Clear in the Main window.
<LOG-FILE>
<LOG-FILE Enabled="Yes" Path="C:\Program
Files\SmartPlant\Isometrics\I-Data Integrator\idi.log"/>
The <LOG-FILE> tag contains two attributes.
 ENABLED - Specifies whether a log file is produced. If set to Yes, a log file is produced. If
set to No, a log file is not produced.
 PATH - Specifies the full path location and filename of the log file.
You must use the configuration file to set up the log file. Options to do so are not
available through the user interface.
<OUTPUT-DATA>
<OUTPUT-DATA Path="C:\SampleIsoDir" Type="5"/>
The <OUTPUT-DATA> tag contains two attributes.
 PATH - Specifies the folder where any output is to be written.
 TYPE - Defines the output format that is produced. The available values are listed below.
 0 - Delimited
 1 - AES/32 XML
 2 - Alias XML
 3 - Access
 4 - Fixed Text
 5 - Excel
You can change the PATH and TYPE attributes using the options in the Main window.
<TEMPLATE-DATABASE>
<TEMPLATE-DATABASE Path="C:\Data\DatabaseName.mdb"/>
The <TEMPLATE-DATABASE> tag contains a single attribute.
 PATH - Specifies the full path location and filename to the Access database that the
software uses as the internal working database. Queries and external data tables that are
required during generation of the output can be stored here instead of in the
<OUTPUT-OPTIONS> tag. Also, you can define the structure of some of the tables to be
filled to ensure that certain columns are present. The default file used is the template.MDB
file stored in default I-Data Integrator installation folder
In previous versions of the software, the database listed in the <OUTPUT-FORMATS>
tag would have been used as both the internal database and the output database. However, in
the current version of the software, this dual functionality can be split.
<PDS-OUTPUT-DIRECTORY>
<PDS-OUTPUT-DIRECTORY Path="C:\PDS"/>
The <PDS-OUTPUT-DIRECTORY> contains a single attribute.
 PATH - Specifies the location of the PDS DEF file, if one is being used.
<I-DATA-INTEGRATOR-OUTPUT-OPTIONS> Section
Controls how I-Data Integrator behaves during the conversion process. This section of the
configuration file is used to specify links to external data, what new generated data is to be
created, and what scripts are to be run when the dataset is processed. To control additional
specific functions, the <I-DATA-INTEGRATOR-OUTPUT-OPTIONS> section is further divided
into the smaller sections listed below, each of which is discussed in detail.
<EXTERNAL-DATA>
Defines new, external datasets, such as databases or spreadsheets containing data that is to be
integrated with the ISOGEN data. This section can also reference IDF, PCF, and POD data files
so that additional datasets can be generated. The <EXTERNAL-DATA> section is processed
after the ISOGEN data has been read into recordsets and before the GENERATED-DATA
section is processed.
The EXTERNAL-DATA section of the configuration file can contain a number of <DBLINK>,
<PCF>, <IDF>, and <POD> tags. Each <DBLINK> tag defines a table in an external data source
that is to become a new I-Data Integrator dataset. Each <PCF>, <IDF>, or <POD> tag defines a
folder containing PCF, IDF, and POD files, respectively. These external data files are
automatically read and the data in them loaded into new I-Data Integrator recordsets.
<DBLINK>
<DBLINK PROVIDER="ODBC;DSN=MDP_ANSI"
TABLE="mto_ansi.pdtable_12"
RECORDSET="SegmentData"/>
The <DBLINK> tag contains three attributes.
 PROVIDER - Specifies a string that contains the parameters needed to link to the external
data. This string is as defined by Microsoft for connecting to the specified data source. The
strings and their associated data source are listed below.
 ODBC;DSN=MDP_ANSI - Any ODBC data source created using the Control Panel >
Data Sources (ODBC) application. In the example above, MDP_ANSI is the name of
the data source being defined.
 Excel 8.0;Database=filename - The link to an Excel spreadsheet.
 MS Access;Database=filename - The link to an Access database.
 TABLE - Specifies the table in the external data source that is to become a new I-Data
Integrator dataset.
 RECORDSET - Specifies the name of the recordset.
<PCF>, <IDF> or <POD>

<PCF PATH='C:\SampleProj\SampleProject\Inputs' SCANMODE='Recursive'>

<EXTRACT DATA="PIPELINE" RECORDSET="PCF_PIPELINES"/>
<EXTRACT DATA="COMPONENTS" RECORDSET="PCF_COMPONENTS" />
<EXTRACT DATA="MATERIALS" RECORDSET="PCF_MATERIALS" />
<EXTRACT DATA="CONNECTIONS" RECORDSET="PCF_CONNECTIONS" />
</PCF>
The <PCF>, <IDF>, and <POD> tags define sets of piping data files to be used as a recordset.
The <PCF> and <IDF> tags have three attributes, whereas the <POD> tag has only the first two
attributes.
A configuration file can contain one of each of these three tags.
 PATH - Defines the folder to be searched for files with the relevant extension (.PCF, .IDF, or
.POD). All piping data files with the correct extension found in this folder are read, and the
data found in them is loaded into the specified recordset(s).
 SCANMODE - Controls which folders are searched. When set to Recursive, the software
scans all of the sub-folders below the one specified by the PATH attribute. If omitted, only
the folder specified by the PATH attribute is searched. When set to Linked, the software
uses the <IDI> tags in the report files to determine which input files have been run. The
<IDI> tags are added to the report files using the IDIPost.exe ISOGEN post-processor. This
does not work for POD files.
For more information about the ISOGEN post-processor, see Configure the Software
(on page 14).
 READTYPE - Controls how the software reads IDFs and PCFs. In previous versions of the
software, setting READTYPE to POD forced the software to read each IDF or PCF as a
POD file. In the current version of the software, IDFs and PCFs are automatically translated
to POD format before being read. To prevent this, and retain the old format for IDFs and
PCFs, you must set this attribute to PCF.
Each <PCF>, <IDF>, and <POD> tag can contain up to four <EXTRACT> tags. The input files
contain four types of data.
 Pipeline or Header - Contains information that applies to the whole pipeline specified in the
<PCF>, <IDF>, and <POD> tags.
 Component - Contains information about the individual components found in the <PCF>,
<IDF>, and <POD> tags.
 Materials - Contains item codes and item descriptions.
 Connections - Contains information on adjacent pipelines.
Each <EXTRACT> tag contains a single attribute.
 RECORDSET - Defines the name by which the external dataset is known in I-Data
Integrator.
<GENERATED-DATA>
Defines new recordsets that are to be derived from any External and ISOGEN recordsets, as
well as from any previously defined generated recordsets.
The <GENERATED-DATA> section can contain any number of <DEFINE-RECORDSET>,
<EXECUTE-SCRIPT>, and <EXECUTE-SQL> tags. Each <DEFINE-RECORDSET> tag
contains a SQL statement that defines the contents of the new recordset, each
<EXECUTE-SCRIPT> tag contains a definition of a VBScript file to execute, and each
<EXECUTE-SQL> tag contains a SQL statement to be run in the intermediate database. This
section is processed after the EXTERNAL-DATA section.
 The <DEFINE-RECORDSET>, <EXECUTE-SCRIPT>, and <EXECUTE-SQL> tags are

executed in the order in which they appear in the <GENERATED-DATA> section.
 By default, the software outputs all <GENERATED-DATA> recordsets. You can use the
<OUTPUT-CONTROLS> section to modify this behavior.
<DEFINE-RECORDSET>
<DEFINE-RECORDSET NAME='NEW-MATERIALS"
SQL="SELECT MATERIALS."
FROM [MATERIALS];"/>
Each <DEFINE-RECORDSET> tag contains two attributes.
 NAME - Defines the name for the new generated recordset.
 SQL - Defines the SQL statement that is executed to populate the generated recordset. The
SQL statement can reference any ISOGEN recordset, any external recordset, or any
previously declared generated recordset. In the example above, a new recordset called
NEW-MATERIALS is being defined by selecting everything from the ISOGEN-generated
recordset called MATERIALS.
 For information about the basic principles of SQL syntax, see Appendix: Basic SQL Syntax
(on page 51).
 Your SQL statement from the XML configuration file is stored in an Access query in the
temporary database.
 Typically, you can have a series of <GENERATE-RECORDSET> tags that reference
previously generated recordsets to gradually build up the required output over several
queries.
<EXECUTE-SCRIPT>
<EXECUTE-SCRIPT SCRIPT-FILE='path to a script' SCRIPT='script to
execute'
PARAMETERS='script parameters' />
Each <EXECUTE-SCRIPT> tag contains three attributes to define a script that is executed
against the current dataset. Two of the attributes are mandatory, and one is optional.
 SCRIPT-FILE - Specifies the path to the text file containing script(s), such as
'c:\scripts\script1.vbs'. This attribute is mandatory.
 SCRIPT - Specifies the script within the file to execute. This must correspond to the name of
a public function in the text file. This attribute is mandatory.
 PARAMETERS - Specifies the comma-separated list of parameters to be passed to the
script. This list must correspond to the argument list of the script being executed. This
attribute is optional.
<EXECUTE-SQL>
Each <EXECUTE-SQL> tag contains a mandatory sub-tag called <SQL>, which holds a SQL
action statement to be run directly in the temporary database. Any valid SQL action statement
can be put in the <SQL> tag. Although only linked or original tables can be affected, other
generated recordsets can be referred to within the tag. This allows table creation and editing
and appending data to existing tables.
It also can have two attributes, NAME and ON-ERROR. Setting ON-ERROR to CONTINUE,
allows I-Data Integrator to continue with its Generate step, even if the SQL action fails.
<OUTPUT-CONTROLS>
Contains any number of <OUTPUT-NAME> and <SUPPRESS-OUTPUT> tags.
<OUTPUT-NAME>
The <OUTPUT-NAME> tag has five possible attributes.
 RECORDSET - Defines the internal name of the I-Data Integrator recordset.
 NAME - Defines the name to be given to the data when it is written out to the specified
format. For example, the statement <OUTPUT-NAME RECORDSET="Components"
NAME="CPTS" />, specifies that the Components recordset (derived from the ISOGEN
Material Control file) is to be called CPTS when it is output. If a delimited format is chosen,
the output is CPTS.csv. If an Access database is specified, the output is the name given to
the table containing the data. If an Excel spreadsheet is specified, the name is the
worksheet name in which the data is to be written. If the worksheet does not exist in the
template, then it is created.
 SPLITBY - Specifies a field in the recordset. If this attribute is set, the recordset is split when
it is written out using the value in the SPLITBY field. For example, if you want to split a list of
components into components belonging to a pipeline, you can use the syntax shown in the
example below.
<OUTPUT-NAME RECORDSET="Components" SPLITBY="PIPELINE-REFERENCE" />
 PIPELINE-REFERENCE must be one of the fields in the Components recordset. When

the Components recordset is written out, each group of records sharing the same value
of PIPELINE-REFERENCE is written out into a separate file or table. This file or table is
given the value of the grouping field (with any illegal characters being replaced by “_”).
A sample Components recordset is shown below.
PIPELINE-REFERENCE ITEM-CODE N_S_
P-1 I1 4
P-1 I2 2
P-2 I-3 6
When written out, the Components recordset is split into two delimited files, as shown in
the next example.
P-1.CSV, P-1,I1,4, P-1,I2,2
P-2.CSV, P-2,I3,6
 NAME and SPLITBY are mutually exclusive.
 If using SPLITBY, you can override the default output extension for a particular
recordset using the optional attribute EXTENSION.
 START- CELL - Defines the location where the recordset is written. This defaults to cell A1.
Used only for Excel output.
 HEADER - Determines if the column names are written as the first row. Used only for Excel
output.
 EXTENSION - Overrides the default file extension for text file (either DELIMITED or FIXED)
output.
<SUPPRESS-OUTPUT>
The <SUPPRESS-OUTPUT> tag contains a single attribute, RECORDSET. If this attribute is set
to the name of one of the SmartPlant Isometrics I- Data Integrator recordsets, it prevents any
output being created for this recordset, such as any intermediate generated recordsets.
External recordsets are never output. They must be transferred to an intermediate
recordset if required for output.
<OUTPUT-FORMATS>
Contains data specific to each output format. The general syntax of the data is shown below.
<FORMAT attribute=”value” />.
The <OUTPUT-FORMATS> section can include the tags listed below.
<ACCESS>
<ACCESS TEMPLATE="APP.PATH\TEMPLATE.MDB" OUTPUT="XMAT"/>
The <ACCESS> tag can have two attributes:
 TEMPLATE - Specifies the template database used to create the output. The template
database can hold pre-configured reports. You can use the APP.PATH string to specify the
installed location of I-Data Integrator.
 OUTPUT - Specifies the name for the output Access database. The default name is
Materials.mdb.
<EXCEL>
<EXCEL TEMPLATE="APP.PATH\TEMPLATE.XLS" OUTPUT="MATERIAL"/>
The <EXCEL> tag can have two attributes:
 TEMPLATE - Specifies the template spreadsheet used to create the output. You can use
the APP.PATH string to specify the installed location of I-Data Integrator.
 OUTPUT - Specifies the name for the output Excel spreadsheet. The default name is
Materials.xls.
<DELIMITED>
<DELIMITED DELIMITER="TAB" EXTENSION="B"/>
<DELIMITED DELIMITER=";" QUOTECHAR="'" />
The <DELIMITED> tag can have three attributes.
 DELIMITER - Specifies the delimiter character. The default is “ ; ”. To specify a Tab
character as the delimiter, use DELIMITER="TAB".
 EXTENSION - Specifies the default extension to use for the delimited files. The default is
.csv. This can be overridden for different recordsets in the <OUTPUT-CONTROLS> section.
 QUOTECHAR - Specifies an option quote character. If used, all fields are prefixed and
suffixed with the specified character. To specify certain characters as quote characters, you
can use special XML strings as shown in the list below.
Character XML Syntax
Double quote ( " ) "
Single quote ( ' ) '
Left angle bracket ( < ) <
Right angle bracket ( > ) >
<MASTER-DETAIL>
The delimited format can also contain a special set of tags that control the output of a
“master/detail” type file. In this type of file, one record from the Master recordset is followed by
all the records from the Detail recordset that meet a criteria, usually that they share a value with
the Master recordset.
For example, records from the Pipelines and Components recordsets can be merged as follows:
Pipeline 1
Components for pipeline 1
Pipeline 2
Pipeline 3
The data must be enclosed between the <MASTER-DETAIL> tags, of which there can be any
number within the <DELIMITED> tag, as shown in the example below.
<MASTER-DETAIL
MASTER="SRECORDS"
DETAIL="VRECORDS"
HEADER= "K,DOW,ABS-TRAIN
6,104146,Spoolgen,v4,CUSTOMER-EXAMPLE.CSV,6/02/2002"
CRITERIA="PIPELINE-REFERENCE = MASTER.[LINE]"
SUPPRESS-DETAIL-FIELDS="PIPELINE-REFERENCE,Geandert" >
</MASTER-DETAIL>
There can be any number of <MASTER-DETAIL> tags within the <DELIMITED> tag. Its
attributes are listed below.
 DETAIL - Specifies the name of the recordset supplying the detail records.
 HEADER - Specifies a string that is output as the first line of the file. It is an optional
attribute.
The HEADER attribute can contain the macros listed below, which are substituted at
run time by I-Data Integrator.
 $DATE - Current system date
 $TIME - Current system time.
 $APP.TITLE - Title of the executable, such as SmartPlant Isometrics I-Data Integrator.
 $APP.EXENAME - Name of the I-Data executable, such as SmartPlant Isometrics.
 $APP.MAJOR - Major revision number.
 $APP.MINOR - Minor revision number.
 $APP.REVISION - Revision version number.

HEADER= ""K","DOW","ABS-TRAIN
6","104146","$APP.TITLE
$APP.MAJOR.$APP.MINOR.$APP.REVISION","v4","$D
ATE ($TIME)","
produces the following output:
"K","DOW","ABS-TRAIN 6","104146","I-Data Integrator
3.2.4","V4","29/08/2002 (16:39:55)",
The HEADER line is output exactly as specified, with the exception of the macro
substitutions. It is not affected by the QUOTECHAR and DELIMITER attributes for a
delimited file output.
 CRITERIA - Defines the way in which the Master and Detail recordsets are linked. It
consists of a string that contains a condition. The special syntax, MASTER.[fieldname], is
used to indicate that the value of the specified field in the current MASTER row is to be
substituted in the criteria string.
 SUPPRESS-DETAIL-FIELDS - Specifies a comma delimited list of fields in the Detail
recordset that are not to be output. Usually, the common field is suppressed.
 <MASTER-DETAIL> output impacts only the specified Master recordset and has no effect
on whether the Detail recordset is output as normal.
 The Detail recordset can appear as a Master recordset in another <MASTER-DETAIL> tag if
it is required to nest the output to more than one level.
<FIXED>
<FIXED RECORDSET="COMPONENTS" EXTENSION="STB">


<FIELD START="1" LENGTH="1" CONTENTS="|" />
<FIELD START="2" LENGTH="20" CONTENTS="PIPELINE" />
<FIELD START="23" LENGTH="20" CONTENTS="ITEM-CODE" />
<FIELD START="44" LENGTH="30" CONTENTS="QTY" />
</FIXED>
The <FIXED> tag specifies the format for a fixed format output file. It contains two attributes.
 RECORDSET - Specifies the name of the recordset that is used as the source of the data to
be written to the fixed format text file. In the case of fixed text output only, the recordset is
only written out if a <FIXED> tag occurs in the configuration file, with the RECORDSET
attribute set to the name of the recordset to be output.
 EXTENSION - Specifies the file extension. The default is .txt.
Appendix: Basic SQL Syntax
Each <FIXED> tag must contain one or more <FIELD> tags. These tags specify the
start position (the START attribute), length (the LENGTH attribute) and contents ( the
CONTENT attribute) of each column.
APPENDIX B

Although a full description of basic SQL syntax is beyond the scope of this document, the
following basic principles may be useful.
 SQL statements are not case sensitive.
 SQL statements can be split over several lines. Tabs and multiple spaces can be used to
format the statement in the configuration file so that it is easily readable.
 The simplest form of an SQL statement is to select records from a single table using the
form SELECT field names FROM table name WHERE criteria.
 Field names can be replaced by * to mean all fields.
 The WHERE clause can contain expressions such as Like that include wildcards. In a Like
expression, % means any sequence of characters and _ means any single character. For
example, NAME Like ‘%IT%’ returns all records where the NAME field contains the
characters IT.
 Enclose text strings within single quotes, as in WHERE NAME=’Smith’.
 Field names need to be enclosed in square brackets if they contain spaces or any
non-alphanumeric character, as in SELECT [PIPELINE-REFERENCE] FROM …
 When joining two tables together, field names must be qualified with the table name to
indicate the source of the data, as in SELECT MATERIALS.[ITEM-CODE],
COMPONENTS.[QTY].
 There are three main types of JOIN: LEFT, RIGHT, and INNER. Where two tables are linked
using a JOIN statement, the table referenced in the FROM statement is the LEFT table, and
the table referenced in the JOIN statement is the RIGHT table. In the statement SELECT
A.A, A.B, B.C FROM A INNER JOIN B ON A.A = B.A, A is the LEFT table and B is
the RIGHT table.
 In a LEFT join, all rows from the left table and any matching rows in the right table are linked
together. In a RIGHT join, all rows from the right table and any matching rows in the left
table are linked together. In an INNER join, only rows that match in both tables are linked.
Glossary
I
I-Configure
Application used by SmartPlant Isometrics and SmartPlant Spoolgen to create the projects and
styles that are used to produce isometric drawing and report file output.
IDF
Intermediate Data File - the original input file for ISOGEN.
intrinsic recordset
a set of data known as a table or recordset--a table is held in a disk file, whereas a recordset is
held in dynamic computer memory. Intrinsic recordsets generated by SmartPlant Isometrics
I-Data Integrator are required for the transfer of the consolidated data into the output data format
required by the user.
ISOGEN
The industry standard for automatic generation of piping isometrics.
isometric style
A set of ISOGEN settings, controls and drawing sheets that will produce a drawing in a
particular format.
item code
A code identifying a particular type of component, which defines uniquely the bores and
dimensions of the component.
Glossary
PCF
The ISOGEN Piping Component File. A PCF is a man-readable input file for ISOGEN.
PDS DEF File

contains most of the data that controls ISOGEN within PDS. The software can read the settings
from this Definition file, which is unique to PDS, in the same way that it does from a Personal
ISOGEN FLS or SPOOLGEN OPT file.
POD
The default file format for SmartPlant Isometrics data. POD stands for piping object data.
S
Spoolgen OPT File
each SPOOLGEN style is defined in an OPT file within the project directory. The OPT file
contains Option Switches, text positioning and AText records.
Index
Preface • 7
< Process files interactively • 33
<I-DATA-INTEGRATOR-OUTPUT-OPTION Process files using the command line • 34
S> Section • 43 Process Pipeline Files • 31
<I-DATA-INTEGRATOR-SETTINGS>
Section • 41 R
Recommended Workflow • 14
A Register the automation interface • 36
Appendix Repeatability Return File • 21
Basic SQL Syntax • 51
XML Configuration File Syntax • 39 S
Automatically Generated Data • 30
SmartPlant Isometrics I-Data Integrator • 9
Specify the XML configuration file • 16
B Spoolgen OPT File • 54
Bending File • 23
T
C The I-Data Integrator Interface • 13
Centerline Length File • 26
Configure the ISOGEN post-processor • 16 U
Configure the Software • 15
User-Specified Text (Field Names in Output
Data) • 20
D
Documentation Comments • 8 V
Documentation Set • 7
View output files • 35
View the log file • 36
I
I-Configure • 53 W
I-Data Integrator Main Window Options • 37
IDF • 53 What's New in SmartPlant Isometrics I-Data
Input Data • 19 Integrator • 8
intrinsic recordset • 53
ISOGEN • 53
isometric style • 53
item code • 53
O
Output Data • 27
Output Data Formats • 28
P
PCF • 54
PDS DEF File • 54
POD • 54

SPIsoI-Data User Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SPIsoI-Data User Guide

Uploaded by

Copyright:

Available Formats

SmartPlant Isometrics

Version 2014 (7.0)

U.S. Government Restricted Rights Legend

SmartPlant Isometrics I-Data Integrator.................................................................................................... 9

Configure the Software ............................................................................................................................. 15

Input Data ................................................................................................................................................... 19

Output Data ................................................................................................................................................ 27

Process Pipeline Files............................................................................................................................... 31

Appendix: XML Configuration File Syntax .............................................................................................. 39

Appendix: Basic SQL Syntax ................................................................................................................... 51

What's New in SmartPlant Isometrics I-Data Integrator

SmartPlant Isometrics I-Data Integrator

The second output dataset contains component data:

 A template database is supplied with I-Data Integrator, which includes a number of

The I-Data Integrator Interface

Setting Processing Options

Configure the Software

What do you want to do?

Specify the XML configuration file

Configure the ISOGEN post-processor

I-Configure File Property FLS Entry OPT Entry

MaterialList.SummaryFile MATERIAL-CONTROL -104

WeldList.SummaryFile WELD-SUMMARY-APPEND -125

Supplementary.SpoolInformation SPOOL-INFORMATION-FILE -154

Supplementary.BendingReport BENDING-FILE-APPEND -127

CutList.SummaryFile CUT-LIST-SUMMARY-APPEND -129

Supplementary.ReportFiles only CENTRELINE-LENGTH -109

Supplementary.RepeatFile REPEATABILITY-RETURN -117

Supplementary.ReportFiles only DRAWING-CROSS-REF-FILE -158

Supplementary.ReportFiles only SITE-ASSEMBLY-FILE-APPEND -164

Output FLS definition OPT Definition

MATERIAL CONTROL MATERIAL-LIST-DEFINITION -122

CUT-LIST-SUMMARY MATERIAL-LIST-DEFINITION -122

WELD SUMMARY WELDING-DEFINITION -120

SPOOL INFORMATION DRAWING-DEFINITION -123

DRAWING-CROSS-REF DRAWING-DEFINITION -158

SITE-ASSEMBLY-FILE-APPEND FUNCTION-DEFINITION -140

BENDING, CUTTING & HOLE

ISOGEN Input/Output File Configuration

User-Specified Text (Field Names in Output Data)

Repeatability Return File

PIPELINE Pipeline reference.

DRG Drawing number.

PT-NO Part number – ISOGEN generated, 1,2,3…

CATEGORY The category – NONE, FAB, EREC, OFF.

UCI The unique component identifier.

Y The component position.

Seq Sequence number in the repeat file

PIPELINE Pipeline reference.

DRG Drawing number.

WELD-NO Part number – ISOGEN generated, 1,2,3…

START_Y The start component position for the weld.

FINISH_Y The finish component position for the weld.

PIPELINE Indicates the pipeline reference (*).

SPOOL-ID Indicates the spool ID (*).

CUT-ID Indicates the cut piece ID (*).

PIPING-SPEC Indicates the piping specification (*).

ITEM-CODE Indicates the pipe item code (*).

ND Indicates the nominal diameter (*).

NUMBER Indicates the bend number.

Y Indicates the bend position.

RADIUS Indicates the bend radius.

ANGLE Indicates the bend angle.

PIPELINE Indicates the pipeline reference (*).