SmartPlant Materials PDMS Interface - Hyundai …spmat.hec.co.kr/marian_webentry/Pdfs/INT-PDMS.pdf · Intergraph Corporation is not responsible for any error that may appear ... YY’

SmartPlant Materials PDMS Interface

Version 2008 (6.3.1) June 2008 DMAR1-PE-200010G

Copyright Copyright © 2000-2008 Intergraph Corporation. All Rights Reserved. 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.

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 Huntsville, Alabama 35894-0001

Warranties and Liabilities All warranties given by Intergraph Corporation about equipment or software are set forth in your purchase contract, and nothing stated in, or implied by, this document or its contents shall be considered or deemed a modification or amendment of such warranties. 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 discussed in this document is furnished under a license and may be used or copied only in accordance with the terms of this license.

No responsibility is assumed by Intergraph for the use or reliability of software on equipment that is not supplied by Intergraph or its affiliated companies. THE USER OF THE SOFTWARE IS EXPECTED TO MAKE THE FINAL EVALUATION AS TO THE USEFULNESS OF THE SOFTWARE IN HIS OWN ENVIRONMENT.

Trademarks Intergraph, the Intergraph logo, SmartSketch, FrameWorks, SmartPlant, INtools, MARIAN, PDS, and IntelliShip are registered trademarks of Intergraph Corporation. Microsoft and Windows are registered trademarks of Microsoft Corporation. Other brands and product names are trademarks of their respective owners.

Table of Contents

SmartPlant Materials PDMS Interface 3

Table of Contents Introduction ........................................................................................................................5

Configuration Requirements ............................................................................................6

Ident Transfer ....................................................................................................................8

Ident Transfer Files .......................................................................................................8 Detail Text (PDMS_D.DAT) .............................................................................................. 8 Component Data (PDMS_C.DAT) ..................................................................................... 9 Geometrics (PDMS_G.DAT) ............................................................................................ 10 Flange-Bolt-Points (PDMS_F.DAT) ................................................................................ 11 Single Bolt Idents (PDMS_BS.DAT) ............................................................................... 13 Bolt Length (PDMS_B.DAT) ........................................................................................... 14 Material (PDMS_M.DAT) ................................................................................................ 15

Defining the Attributes Required for the Ident Transfer ............................................16 Entering the Attribute Translation for PDMS ............................................................17 Defining the Tables Required for PDMS ...................................................................18 Entering the Table Translation for PDMS ..................................................................19 Entering the Table Attributes .....................................................................................20 Importing Data for the GTYPE and SKEY Tables ....................................................21 Assigning the Interface Details to the Parts ................................................................24 Defining the PDMS-CATREFs per SmartPlant Materials Commodity Code ............25 Defining the PDMS Groups ........................................................................................26 Entering the PDMS Configurations ............................................................................28 Defining G-Type Attribute Mapping ..........................................................................31 Creating PDMS Files for the Ident Transfer ..............................................................36

Specification Transfer .....................................................................................................38

PDMS Specon File .....................................................................................................40 PDMS Insulation File .................................................................................................41 Defining the Attributes Required for the Spec Transfer .............................................42 Entering the Attribute Translation for PDMS ............................................................44 Defining the Tables Required for PDMS ...................................................................45 Importing Data for the GTYPE Table ........................................................................46 Entering the Table Translation for PDMS ..................................................................47 Entering the Table Attributes .....................................................................................48 Entering a Table Group ..............................................................................................49 Entering the Specific Interface Details .......................................................................50 Assigning Screws and Bolts to the Specification Parts ..............................................51 Defining PDMS-CATREF per SmartPlant Materials Commodity Code ...................52 Assigning the Interface Details to the Parts ................................................................53 Mapping GTypes, Header, and Details with SmartPlant Materials Short Codes and Option Codes ..........................................................................................................................54

Table of Contents

4 SmartPlant Materials PDMS Interface

Creating the PDMS File for the Spec Transfer ...........................................................56

Accessing Files in a Web Environment ..........................................................................59

Loading SmartPlant Materials Files into PDMS (User Guide) ...................................60

1. Installing the PDMS Interface Software ...............................................................60 2. Creating Standards for COCO table, GMSE, PTSE, DTSE .................................61 3. Creating UDA Attributes ......................................................................................62 4. Creating a Catalog in PARAGON Module ..........................................................62 5. Creating Component Data ...................................................................................65 6. Creating Specifications .........................................................................................67 7. Example ................................................................................................................67

Appendix: File Examples ...............................................................................................68

SpecCon File ...............................................................................................................68 SpecCon Delta Files ..................................................................................................70

A. Creating a New Specification....................................................................................... 70 B. Creating a New Component in an Existing Specification ............................................ 70 C. Modifying a Component in a Specification ................................................................. 71 D. Removing a Component ............................................................................................... 71

Spec Insulation File ....................................................................................................72 PDMS_B.DAT ............................................................................................................73 PDMS_BS.DAT .........................................................................................................74 PDMS_D.DAT ...........................................................................................................77 PDMS_F.DAT ............................................................................................................78 PDMS_M.DAT ...........................................................................................................81

Appendix: CIPs ................................................................................................................82

Introduction


Introduction This guide describes how to configure the PDMS interface in SmartPlant Materials. There are several steps required to work with the PDMS interface.

The PDMS interface contains two different kinds of transfers: Ident Transfer and Specification Transfer. Some steps are the same for both kind of transfers and some are only for one kind of transfer.

The transfer generates a set of ASCII files that can be separated into one file for the Specifications (SPECON) and a set of files for the Ident-Transfer. See the Ident Transfer chapter for more details on the purpose of each individual file created.

These files are loaded into PDMS.

Configuration Requirements


Configuration Requirements Please check the following configuration settings:

1. DBA Setting for PLUS_EXECUTABLE is set properly.

Enter the SQL plus version, with which the scripts shall be worked.

Configuration Requirements


2. The ApplicationServer RegistryEntry for SQL_PATH points to the folder where the below mentioned files are located.

• pdms2001.sql

• pdms2001d_gm.sql

• pdms2001m_gm.sql

• pdms2001c_gm.sql

• pdms2001g_gm.sql

• pdms2001b_gm.sql

• pdms2001bs_gm.sql

• pdms2001f_gm.sql

• pdms2001p.sql

• pdms2001_ig.sql

These scripts were delivered with the SmartPlant Materials installation and should be automatically at the right place.

3. Definition of the PDMS Interface in A.70.01

Enter PDMS, the interface name, in A.70.01 Interfaces screen.

Ident Transfer


Ident Transfer Depending on the File Type (PDMS 20.01 Create PDMS Files), various files are created. The ones you will need depend on to the way you work with PDMS and the way you want to use your existing data in PDMS. A PDMS expert should help you make this decision.

Ident Transfer Files

Detail Text (PDMS_D.DAT) Contain the detail text information

<START> CATA SECT SDTE SKEY RTEXT STEXT TTEXT CATA: m_pck_pdms_custom.get_cata('I' ,p_ident) Look at the example PL/SQL-Code. The parameters ‘I’ and ident the function look for the project-identifier of the ident, which should be transferred. SECT: default is part SHORT_DESC (if not defined then ‘PART:PART_ID),

CIP (M_PCK_PDMS_CUSTOM.SECT, input COMMODITY_ID and NLS_ID of PDMS 30.01 Configure PDMS field Nls for RTEXT/XTEXT)

SDTE: IDENT || ‘-D’ SKEY: default is TD_CODE of table name which was translated as SKEY

(S.20.08 second window), CIP (M_PCK_PDMS_CUSTOM.S2008, input COMMODITY_ID, TRANSLATION ‘SKEY’ and INTERFACE_ID)

RTEXT: commodity code LAYOUT_SHORT with nls of PDMS 30.01 Configure PDMS field Nls for RTEXT/XTEXT

STEXT: commodity code LAYOUT_SHORT with nls of PDMS 30.01 Configure PDMS field Nls for STEXT/YTEXT

TTEXT: commodity code LAYOUT_SHORT with nls of PDMS 30.01 Configure PDMS field Nls for TTEXT/ZTEXT

You can also influence the building of text built here; it comes from the CIP_pck_pdms_custom.text.

Ident Transfer


If a commodity code has no SKEY (SKEY = ‘NONE’), then blank line for SKEY will be written.

pdms_d.del contains information about detail text which are no more contained opposite the last run in the Pdms_d.dat (Ident). (When an ident in SmartPlant Materials is deleted, it is written in this file. It should be deleted in PDMS, too.)

pdms_d.err contains information about faults that occurred during the detail text transfer

Component Data (PDMS_C.DAT) Contains the weight and unit information of an Ident.

<START> CMPW CMPT CMPD CWEI BFLE CMPW: PDMS 30.01 Configure PDMS field CMPW CMPT: default is SCOM (CCI_CODE || INPUT_1 || INPUT_2 …) || ‘-C’

CIP (M_PCK_PDMS_CUSTOM.SCOM, input INTERFACE_ID, COMMODITY_ID, IDENT,0)

CMPD: IDENT || ‘-C’ CWEI: unladen weight,

CIP (M_PCK_REQ_CUSTOM.WEIGHT, input IDENT) BFLE: filling weight,

CIP (M_PCK_PDMS_CUSTOM.BFLE_WEIGHT, input IDENT and unladen weight)

................................................................................................................................................ pdms_c.del contains information about weights that are no longer contained

opposite the last run in the Pdms_c.dat (Ident). (When an ident in SmartPlant Materials is deleted, it is written in this file. It should be deleted in PDMS, too.)

pdms_c.err contains information about faults that appeared during the component data transfer

Ident Transfer


Geometrics (PDMS_G.DAT) Contains the geometric information and all needed references to geom. set, point set, data set and bolt reference

<START> CATA SECT CATE SCOM GTYPE GMREF PTREF DTREF PARAM N1 .. N13 BLRFA CATA: m_pck_pdms_custom.get_cata('I' ,p_ident)

Look at the example PL/SQL-Code, with the Parameters ‘I’ and ident the function looks for the

project-identifier of the ident, which should be transferred. SECT: default is part SHORT_DESC (if not defined then ‘PART:PART_ID),


CATE: default is CCI_CODE (S.30.I.01 Interface Dependent), CIP (M_PCK_PDMS_CUSTOM.CATE, input INTERAFCE_ID, COMMODITY_ID)

SCOM: default is SCOM (CCI_CODE || INPUT_1 || INPUT_2 …) || ‘-SCOM’ CIP (M_PCK_PDMS_CUSTOM.SCOM, input INTERFACE_ID, COMMODITY_ID, IDENT,0)

GTYPE: default is TD_CODE of table name which was translated as GTYPE (S.20.08 second window), CIP (M_PCK_PDMS_CUSTOM.GTYPE, input INTERFACE_ID and COMMODITY_ID)

GMREF, PTREF, DTREF: Comes from the CIP m_pck_pdms_custom. GPD_REF(INTERFACE_ID , COMMODITY_ID , v_IDENT, l_gmref , l_Ptref ,l_dtref). This procedure has three output-parameters that are the result fields. PARAM: defined in PDMS 30.02 G-Type Attribute Mapping

BLFRA: CCI_CODE || INPUT_1 || INPUT_2 … || ‘-F’ When the item is not bolted, BLRFA is empty.

pdms_g.del contains information that SCOM are no longer contained opposite the last run in the Pdms_g.dat. (When an ident in SmartPlant Materials is deleted, it is written in this file. It should be deleted is PDMS, too.)

pdms_g.err contains information about faults that occurred during the geometric transfer

Ident Transfer


Flange-Bolt-Points (PDMS_F.DAT) Contains all information of the bolt Ident which are referenced in pdms_g.dat file

<START> CATA SECT CATE BTSE NUMBER DIAMETER BTYPE BTHK CATA: m_pck_pdms_custom.get_cata('I' ,p_ident) Please look at the example PL/SQL-Code, with the Parameters ‘I’ and ident the function looks for the project-identifier of the ident, which should be transferred. (When an ident in SmartPlant Materials is deleted, it is written in this file. It should be deleted is PDMS, too.) SECT: default is part SHORT_DESC (if not defined then ‘PART:PART_ID),


CATE: default is CCI_CODE (S.30.I.01 Interface Dependent), CIP (M_PCK_PDMS_CUSTOM.CATE, input INTERAFCE_ID, COMMODITY_ID)

BTSE: same as CATE || ‘-F:XX:YY’ :XX = reference the parameter 12 or 13 of the pdms_g.dat file (:12,:13) :YY = number of bolt (NUMBER) NUMBER: number of needed bolts (from BTSE),

defined attribute of PDMS 30.01 Configure PDMS field Attribute for No of Bolts, Geometry which has a Commodity Geometric Relation to the commodity codes of the Screw Bolt Rule and the three defined attributes of PDMS 30.01 Configure PDMS fields Attribute for Bolt Diameter, Attribute for No of Bolts and Attribute for Flange Thickness and the same diameter as the IDENT If more than 1 bolt is needed, then will be count up from 1 to number of needed bolts. For every number of needed bolts will be inserted a new <START> section

DIAMETER: bolt diameter defined attribute of PDMS 30.01 Configure PDMS field Attribute for Bolt Diameter, Geometry which has a Commodity Geometric Relation to the commodity codes of the Screw Bolt Rule and the three defined attributes of PDMS 30.01 Configure PDMS fields Attribute for Bolt Diameter, Attribute for No of Bolts and Attribute for Flange Thickness and the same diameter as the IDENT

Ident Transfer


BTYPE: defined in PDMS.30.01, second block. Result comes from M_pck_pdms_custom.GET_BTYPE(p_ident,p_attr_id ). When no attribute in PDMS.30.01 is defined or the result of the function is NULL, ‘BOLT’ is the default.

BTHK: defined in PDMS.30.01 In PDMS.30.01, you can define an additional attribute for the value that is added to the flange thickness. In PDMS.30.01, you can define more than one bolt.

pdms_f.del contains information about SCOM which are no more contained

opposite the last run in the Pdms_f.dat.

pdms_f.err contains information about faults that occurred during the flange bolt transfer.

Ident Transfer


Single Bolt Idents (PDMS_BS.DAT) Contain all information of the bolt Ident

<START> CATA SECT BLTA BLIS SBOL BDIA NSTD 0 XTRA BITEM BITLE CATA: m_pck_pdms_custom.get_cata('I' ,p_ident) Please have a look into the example PL/SQL-Code, with the Parameters ‘I’ and ident the function looks for the project-identifier

of the ident, which should be transferred. SECT: default is part SHORT_DESC (if not defined then ‘PART:PART_ID),


BLTA: COMMODITY_ID || '-'|| INPUT_1 ||'-BLTA' BLIS: COMMODITY_ID || '-'|| INPUT_1 ||'-BLIST' SBOL: COMMODITY_ID || '-'|| INPUT_1 || '-BS' BDIA: bolt diameter NSTD: COMMODITY_ID || '-'|| INPUT_1 0: new parameter in PDMS, is always default 0 XTRA: BITEM: BITLE: The Insert into the table m_pdms_bolt_refs is moved completely into a CIP, M_pck_pdms_custo.file_bolt_ref (p_pcc_id => internal ID from the Job which is started in PDMS.20.01, p_commodity_Id => Primary of the commodity-code, p_input_1 => Diameter of the Bolt-ident)

pdms_bs.del contains information about SCOM that is no more contained

opposite the last run in the Pdms_bs.dat. (When an ident in SmartPlant Materials is deleted, it is written in this file. It should be deleted is PDMS, too.)

pdms_bs.err contains information about faults that occurred during the bolt set transfer.

In the m_pdms_bolt_ref_errs table, you can report any data-errors or problems during the CIP. This file contains these messages.

Ident Transfer


Bolt Length (PDMS_B.DAT) Contain the several length information of the bolt Ident.

<START> CATA SECT BLTA LTAB DTAB (BoltLength1 … BoltLengthN) IDENT 1 .. IDENT N CATA: m_pck_pdms_custom.get_cata ('CC' ,p_commodity_id) Please have a look into the example PL/SQL-Code, with the Parameters ‘CC’ and commodity_id the function looks for the

project-identifier of the commodity-code which should be transfered. SECT: default is part SHORT_DESC (if not defined then ‘PART:PART_ID),


BLTA: COMMODITY_ID || '-'|| INPUT_1 ||'-BLTA' LTAB: COMMODITY_ID || '-'|| INPUT_1 ||'-LTAB' DTAB: COMMODITY_ID || '-'|| INPUT_1 BoltLength: INPUT_2,

All commodity codes which are listed in the rule defined in PDMS 30.01 Configure PDMS field Rule for Bolts

IDENT: IDENT pdms_b.del contains information about SCOM which are no longer contained

opposite the last run in the Pdms_b.dat. (When an ident in SmartPlant Materials is deleted, it is written in this file. It should be deleted is PDMS, too.)

pdms_b.err contains information about faults that occurred during the bolt transfer.

Ident Transfer


Material (PDMS_M.DAT) Contains the material text information.

<START> CATA SECT SMTE XTEXT YTEXT ZTEXT CATA: m_pck_pdms_custom.get_cata ('CC' ,p_commodity_id) Please have a look into the example PL/SQL-Code, with the Parameters ‘CC’ and commodity_id the function looks for the project-identifier of the commodity-code which should be transferred. SECT: default is part SHORT_DESC (if not defined then ‘PART:PART_ID’),

CIP (M_PCK_PDMS_CUSTOM.SECT, input COMMODITY_ID and NLS_ID of current login)

SMTE: default is TD_CODE || ‘_’ || TAB_ID (or table detail link) || ‘-M’ CIP (M_PCK_PDMS_CUSTOM.FIND_IN_CCD, input COMMODITY_ID, 'MATXT', INTERACE_ID, NLS_ID, 'CODE') For NLS_ID will be used the defined nls_id of PDMS 30.01 Configure PDMS field Nls for RTEXT/XTEXT

XTEXT: default is SHORT_DESC of table detail (or table detail link) CIP (M_PCK_PDMS_CUSTOM.FIND_IN_CCD, input COMMODITY_ID, 'MATXT', INTERACE_ID, NLS_ID, 'DESC') For NLS_ID will be used the defined nls_id of PDMS 30.01 Configure PDMS field Nls for RTEXT/XTEXT

YTEXT: default is SHORT_DESC of table detail (or table detail link) CIP (M_PCK_PDMS_CUSTOM.FIND_IN_CCD, input COMMODITY_ID, 'MATXT', INTERACE_ID, NLS_ID, 'DESC') For NLS_ID will be used the defined nls_id of PDMS 30.01 Configure PDMS field Nls for STEXT/YTEXT

ZTEXT: default is SHORT_DESC of table detail (or table detail link) CIP (M_PCK_PDMS_CUSTOM.FIND_IN_CCD, input COMMODITY_ID, 'MATXT', INTERACE_ID, NLS_ID, 'DESC') For NLS_ID will be used the defined nls_id of PDMS 30.01 Configure PDMS field Nls for TTEXT/ZTEXT

If no Nls is defined for STEXT/YTEXT and/or TTEXT/ZTEXT, then will be written a blank line for YTEXT and/or ZTEXT.

pdms_m.err contains information about faults that occurred during the material text transfer.

Ident Transfer


Defining the Attributes Required for the Ident Transfer

Use screen A.50.01 to define all attributes needed by the PDMS interface for the Ident Transfer and all attributes for the pdms_g.dat parameter list (PDMS 30.02 G-Type Mapping, second block, Type ‘Geometry’). Only those attributes can be used for the Ident Transfer. All attributes need a translation for the interface PDMS in A.50.I.02.

For the attribute GTYPE insert the following Derived From clause:

Ident Transfer


Entering the Attribute Translation for PDMS

Use screen A.50.1.02 to enter the translation for the interface PDMS for all defined attributes that will be used in PDMS 30.02 G-Type Mapping, second block, Type Geometry.

Ident Transfer


Defining the Tables Required for PDMS Use screen A.50.02 to define tables.

Here you must define the tables for the PDMS interface. They should be belong the INTERFACE attribute type.

You need one table for GTYPEs and one for SKEYs. The name of the tables are free format.

Ident Transfer


Entering the Table Translation for PDMS You need a translation for the following tables:

Table name Translation for interface PDMS

GTYPE (freeformat) GTYPE

SKEY (freeformat) SKEY

Material tables MATXTxxxxxxx

Ident Transfer


Entering the Table Attributes

This screen shows entering the attribute GTYPE to the table SKEY. Insert TD.CHAR1 for the Physical Attribute.

Ident Transfer


Importing Data for the GTYPE and SKEY Tables You can import the default data for table GTYPE and SKEY. SmartPlant Materials displays default data, which you can insert, update and delete.

Insert the Import Type (by LOV) PDMS_GTYPE. Insert an existing Table Type Description for the Table Type ‘INTERFACE’. Insert the Table Name, which was defined in previous step, for the table GTYPE.

Insert a existing Table Group (S20.I.02 Specific Interface Groups).

Ident Transfer


Do not change the Mapname GTYPE. This is the interface table translation for PDMS.

Click the Display Import Rows button to see the default data.

Click the Start Import button. The import starts now.

Insert the Import Type (by LOV) PDMS_SKEY. Insert an existing Table Type Description for the Table Type ‘INTERFACE’. Insert the Table Name, which was defined in previous step, for the table SKEY. Insert an existing Table Group (S20.I.02 Specific Interface Groups).

Do not change the Mapname ‘SKEY’. This is the interface table translation for PDMS.

Click the button Display Import Rows to see the default data.

Click the button Start Import. The import starts now.

Ident Transfer


Ident Transfer


Assigning the Interface Details to the Parts Assign the related G-Type and SKEY to the part for Tablename GTYPE and SKEY.

If one part has no SKEY, then use the SKEY NONE. This is very important, because only parts with a mapping to the related G-TYPE and SKEY will be taking into account.

Ident Transfer


Defining the PDMS-CATREFs per SmartPlant Materials Commodity Code

The following screen demonstrates how the SmartPlant Materials Commodity Codes are assigned to the PDMS CATREFs.

In this case, the catalog reference for PDMS would be EDE90--B01--0-3E00B9 and specifically for the Commodity Code “EDE90--B01--0-3E00B9”given above. If you cannot find a PDMS interface through the LOV function in the field Interface, please enter it in A.70.01. Please enter only PDMS as the interface code in A.70.01; otherwise, SmartPlant Materials cannot identify this terminus.

Ident Transfer


Defining the PDMS Groups

Define a Rule for the PDMS Ident Transfer. Enter at least one Group Code. This Rule will transfer all Idents, which are under this Group Code.

You can also break down to a Part Code and Commodity Code, if you want to transfer a subset of Idents for this Group Code.

In the third block, you can reduce the commodity codes. Only commodity codes with the inserted Table Details will be used.

Ident Transfer


Define a rule in PDMS 20.04 for all bolt material.

This information will be used for pdms_b.dat and pdms_bs.dat. The INPUT_1 of the bolt idents must be the diameter; the INPUT_2 must be the bolt length.

You can also break down to a Part Code and Commodity Code, if you want to transfer a subset of Bolt Idents for this Group Code.

In the third block, you can reduce the commodity codes. Only commodity codes with the inserted Table Details will be used.

Ident Transfer


Entering the PDMS Configurations Use Screen PDMS 30.01, Configure PDMS, to configure the origin and/or defaults of the data for PDMS-Transfer in PDMS 20.01.

These settings are project or product group specific. Product group settings affect only attached projects that do not have their own configuration. You can use the functionality to copy the product-group-configuration to the logged on project.

Languages for Detail Text

Enter the NLS for RTEXT/XTEXT, STEXT/YTEXT (optional, only for several languages), TTEXT/ZTEXT (optional, only for several languages):

The detail text name is typed in the Specification and the Catalog and describes the manner of the component. The text is stored in RTEXT,STEXT, and TTEXT attributes. The text of the isometric is distributed on the parts list at the construction. The SKEY attribute of the detail text selects the corresponding symbol in ISOGEN.

Ident Transfer


The material text name is typed in the specification and the catalog and describes the material of the component. The text is stored in XTEXT, YTEXT, and ZTEXT attributes. The text of the isometric is distributed on the parts list at the construction.

Definition for Bolts:

Enter the defined Rule (PDMS 20.04) for the bolts.

This rule contain all single bolts.

Attributes for Flange Bolt Points:

Enter the Attribute for Bolt Diameter, Attribute for No of Bolts, and Attribute for Flange Thickness, an additional attribute for flange thickness and the bolt type.

Suffixes and Fix Values:

• GMREF Suffix. GMREF Suffix will be the default suffix for the GMREF (geometry set reference to a 3D geomset)

GMREF is a reference indicator to a 3Ds Geomset element.

A 3D geomset is a grouping of the primitive elements that make up a piping component, joint or fitting. It specifies the dimensions, orientation and obstruction geometry of each primitive. The geomset defines what is drawn for a particular component by PARAGON (and other PDMS modules), and also defines the obstruction geometry of the component for use when clash checking. Each component is built up from a combination of three-dimensional primitives.

• PTREF Suffix PTREF Suffix will be the suffix for the PTREF (point set reference).

PTREF is a reference indicator to 3D point set element.

A PTSET is a group of P-Point elements. P-Points will be used for construction to positioning, orientation and verify the connection of the elements. P-Points will also be required by the construction of the 3D geomset in PARAGON.

• DTREF Suffix DTREF Suffix will be the suffix for the DTREF (dataset reference)

Design Datasets (DDSE) are used to store the properties of design template items, which may then be used to define the template’s parameters. Each property is stored in a Design Data (DDAT) element under a DDSE, with each DDAT being identified by a keyword held in its DKEY attribute. The property definition can be specified by an expression held in the DDPR (Design Data Property) attribute, while a default value for the property (to be used if the expression cannot be evaluated for any reason) can be stored in the DDDF (Design Data Default) attribute.

Ident Transfer


Unlike a design reference to a catalog component, which can access only a single catalog dataset via its DTREF setting, a reference to a design template can access more than one design dataset. A local design dataset is owned directly by the current element, a template design dataset is owned by the first template below the current element, while a current design dataset is at the same level as the current element and has the same owner.

• CMPW Default name for the component data element CMPW (Component World)

You can copy a configuration from the product-group into the project. There you can modify the configuration project-specific.

Geometric and Attributes for Insulation:

Enter the Geometry Table, which contains the information of the Insulation.

Enter the Attributes for DN from, DN to, Temp from, Temp to, and for Thickness.

Ident Transfer


Defining G-Type Attribute Mapping Screen PDMS 30.02 is used to configure the origin of the attribute data for PDMS-Transfer in PDMS 20.01 for the several G-Types.

There are several possibilities for the origin of the attributes

Attributes of the Geometric

Attributes came from CIP Customer defined Procedure (M_PCK_PDMS_CUSTOM)

Attributes of the Commodity Code Details

Table Name

Table Details

ATTR_CHAR 1 - 3

ATTR_NUM 1 - 3

You can query all g-types, which are table details of the table with the interface translation ‘GTYPE’ for PDMS (A.50.I.01 Interface Tables).

Ident Transfer


The needed parameter list can have passed away of g-type to g-type. The parameter positions (Parameter Seq) can have another meaning within different g-types.

G-Type FILT

G-Type CROS

Type Geometric:

For all Geometry Attributes, which will be used, you must have a translation for the interface PDMS in A.50.I.02 Interface Attributes.

For the attributes like diameter, length, thickness, and so on, PDMS needs a suffix (in), if you want to use the imperial unit system. The default suffix will be the unit code of the attribute (field Unit). If you have entered an interface dependent unit (A.10.14), then the interface unit is used as suffix. With the Use Unit indicator you can determine which attribute needs a suffix. This is only required for the unit inch. If no suffix is attached to the parameter, then PDMS knows that you are working with the metric unit mm (millimeter).

Ident Transfer


Type Commodity Code:

If you use the Type ‘Commodity Code’, then you can enter a Tablename, which is from Type ‘COMMATTR’ (or a Table Link) and exists as detail in the Commodity Rule.

Ident Transfer


With the selection of the field ‘Value defined in’, you determine the origin of the value. The available fields are: TD_CODE, ATTR_CHAR1, ATTR_CHAR2, ATTR_CHAR3, ATTR_NUM1, ATTR_NUM2, and ATTR_NUM3.

Type CIP:

If you want to get the values from a CIP (Customer defined Procedure), you can select all functions from the valid package M_PCK_PDMS_CUSTOM (owner M_SYS) with the input parameter P_IDENT.

M_PCK_PDMS_CUSTOM specification:

/*

|| function example_cip_pdms3002

||

|| this is only an example for a CIP function, which will be used in PDMS 30.02

Ident Transfer


|| G-Type Attribute Mapping. The input parameter must be named P_IDENT.

|| The return value will be written to the PDMS_G.DAT file as VARCHAR2(19)

||

*/

FUNCTION example_cip_pdms3002 (P_IDENT IN M_IDENTS.IDENT%TYPE)

RETURN VARCHAR2;

M_PCK_PDMS_CUSTOM body:

/*

|| function example_cip_pdms3002

||

|| this is only an example for a CIP function, which will be used in PDMS 30.02

|| G-Type Attribute Mapping. The input parameter must be named P_IDENT.

|| The return value will be written to the PDMS_G.DAT file as VARCHAR2(19)

||

*/

FUNCTION example_cip_pdms3002 (P_IDENT IN M_IDENTS.IDENT%TYPE)

RETURN VARCHAR2

IS

v_return VARCHAR2(19);

BEGIN

v_return := 'CIP example';

--

RETURN v_return;

END example_cip_pdms3002;

Ident Transfer


Creating PDMS Files for the Ident Transfer

Enter the Job Code, Short Desc, and Description (optional), File Options means what kind of PDMS-Files you want to create, explained in the beginning of the document.

Project Filter means only idents from the logged in project or also from the attached product group.

Specfilter means to filter the idents against specifications. The purpose of this setting is to reduce the amount of output data. Probably the export will take a little bit more time and the export path for the PDMS files and the export file name. To insert the path, you can also use the ‘Save’ button.

Use the Restrictions button or the next block arrow to insert the predefined Rules for this PDMS job.

Ident Transfer


Enter your predefined Rules (PDMS 20.04 PDMS Groups). You don’t need to enter the Rules for the Bolts, which were only defined for the PDMS 30.01 Configure PDMS screen.

Click the Create File button to start the PDMS Ident Transfer. A message appears which informs you about the used SQL Plus version. This is only Help about the DBA-Setting if there is a problem in creation of the spool-files.

After the transfer has finished, you can see all relevant job information in the History Information section.

Click the button to display error information about the PDMS Ident Transfer.

Specification Transfer


Specification Transfer Create a standard Specon file or a Insulation Spec (Screen PDMS 10.02 Create PDMS Spec-File).

In addition to the Specon file, you can create various files in Screen PDMS 20.01-Create PDMS Files. The files are: PDMS_D.DAT, PDMS_C.DAT, PDMS_B.DAT, PDMS_BS.DAT and PDMS_M.DAT (For details, see Chapter ‘Ident Transfer’, Page 8.)

The ways you want to work in PDMS and use your existing PDMS data determine the files you need. A PDMS expert should help you make this decision.

Select the Delta-checkbox in PDMS 10.02 to compare the spec against a delta result. Four files are created:

• The new-file containing all lines from the actual spec.

• The insert-file containing all lines that are added (new NAMEs) compared to the delta-result.

• The modify-file containing all lines that have the same NAME but other attributes changed.

• The delete-file containing all lines that were removed in comparison to the delta-result (NAME).

Double-click the spec code item to view in PDMS 10.03 on the job marked as delta-job to compare. After the spec transfer finished, the actual job will become delta-job.

Generally, the delta-creation depends on the setting of the item 'Spec Rev Delta Handling'. If it is set to 'Autonomous' and the spec transfer finished, the delta indicator of all jobs of the same spec revision (except the actual one) is unset, but the delta indicator of other revisions is left. If a new job is started afterwards (in another revision) and it shall pick up a delta, it first looks if there is a delta job in its own revision and only if not, looks in a lower revision. This means the revisions are autonomous related to another (multiple delta inds are allowed per spec, one per each revision).

If 'Spec Rev Delta Handling' is set to 'Merge', and the spec transfer finished, the delta indicator of all jobs of the same spec (-code, type, project) is unset (except the actual one). If a new job is started afterwards (in another revision) and it shall pick up a delta, it looks from the latest to the oldest revision of the same spec and compares the job to the first delta job found. This means the revisions are merged related to another with respect to the delta creation.

If you plan to transfer the same spec in different revisions in the same run, the delta job indicator when a spec is transferred. The delta-job can also be in another spec



revision than the actual one, so you might get unexpected results running the same spec in different revisions in the same run.

You may check ‘Reset’ to let the update-file contain all current lines; not only those that changed.

‘Copy’ tells the transfer to read the SmartPlant Materials spec or copy the result set of a job, which is marked as 'Master' in PDMS 10.03. If you choose copy, the contents of the actual SmartPlant Materials spec does not play any role.



PDMS Specon File NEW SPECIFICATION /SPEC_CODE MATREF =0 fix value 0 FLUREF =0 fix value 0 RATING 0.100 fix value 0.100 LINETYPE NULL fix value NULL Text 'PIPING' fix value ‘PIPING’ BLTM 'NEW' fix value ‘NEW’ HEADING fix value HEADING TYPE NAME fix value TYPE NAME

and all defined attributes of the Header Format (PDMS 10.01) DEFAULTS fix value DEFAULTS

ATTR_CHAR1 of table detail, defined in Default Format (PDMS 10.01)

values of defaults values of heading

These settings are not fixed. It is set by a CIP (Procedure m_pck_pdms_custom.prep_output_heading(p_log_id).

If several definitions of Header Format and Default Format exist, then will be start with a new section of:

HEADING fix value HEADING TYPE NAME fix value TYPE NAME






PDMS Insulation File NEW SPECIFICATION /SPEC_CODE MATREF =0 fix value 0 FLUREF =0 fix value 0 RATING 0.000 fix value 0.000 LINETYPE NULL fix value NULL BSPEC=0 fix value 0 Text 'INSUL' fix value ‘INSUL’ HEADING fix value HEADING TYPE NAME fix value TYPE NAME






Defining the Attributes Required for the Spec Transfer

Please note that you may not enter the attributes TYPE and NAME, since these are always part of the header and also always come at the beginning. Here only those attributes are defined which you need in addition.

In this screen, all attributes needed by the PDMS interface must be defined. The following table explains where SmartPlant Materials gets the information if the attribute in the PDMS header is referenced.

Attribute Source in SmartPlant Materials

ANGLE default is return value of M_PCK_PDMS_CUSTOM.S2008

BLTREF '/' and bolt_commodity_id and '-' and the value of the geometry attribute for the related ident, which is mapped in A.50.I.02 for interface ‘PDMS’ with the translation ‘BDIA’

CATREF interface commodity code (S.30.I.01 Window 2)

CMPPREF ‘/’ and Ident

DETAIL '/' and Ident

PBOR0 Nominal Size

PBOR1 Nominal Size



PBOR2 Nominal Size

PBOR3 Nominal Size

RADIUS default is return value of M_PCK_PDMS_CUSTOM.S2008

STYP default is return value of M_PCK_PDMS_CUSTOM.S2008

SUFF IF option code = 1 THEN will be SUFF = ‘PREF',

Else SUFF will be take the first three characters of the option code

SHOP default is return value of M_PCK_PDMS_CUSTOM.S2008

BDIA input 1

BTYP default is return value of M_PCK_PDMS_CUSTOM.S2008

BAUL the value of the geometry attribute for the related ident, which is mapped in A.50.I.02 for interface ‘PDMS’ translated as ‘LGTO’

MATXT default is return value of M_PCK_PDMS_CUSTOM.S2008

TEMP_ FROM Output1 in the Geometric Table for Insulation

TEMP_TO Output2 in the Geometric Table for Insulation

DN_FROM Nominal Size 1 in the Geometric Table for Insulation

DN_TO Nominal Size 2 in the Geometric Table for Insulation

INS_THK Output3 in the Geometric Table for Insulation



Entering the Attribute Translation for PDMS

Use this screen to enter the translation for the interface PDMS for the attribute ‘BAUL’. The translation must be ‘LGTO’.



Defining the Tables Required for PDMS

Use this screen to define the tables that will be needed for the PDMS interface.

You need at least one table for PDMS header, PDMS default, SHOP, STYP, BTYP, ANGLE, GTYPE, and RADIUS.

It is important that the name of the table be PDMS_HEADER_XY , whereby XY is a combination of numbers.



Importing Data for the GTYPE Table You can import the default data for table GTYPE and SKEY. You can insert, update and delete the default data delivered with SmartPlant Materials.

Insert the Import Type (by LOV) PDMS_GTYPE. Insert an existing Table Type Description for the Table Type ‘INTERFACE’. Insert the Table Name that was defined in previous step, for the table GTYPE.

Insert an existing Table Group (S20.I.02 Specific Interface Groups).

Do not change the Mapname ‘GTYPE’. This is the interface table translation for PDMS.

Click the Display Import Rows button to see the default data.

Click the Start Import button. The import starts now.



Entering the Table Translation for PDMS You need a translation for the following tables:

Table name Translation for interface PDMS

GTYPE (freeformat) GTYPE

SHOP (freeformat) SHOP

STYP (freeformat) STYP

BTYP (freeformat) BTYP

ANGLE (freeformat) ANGLE

RADIUS (freeformat) RADIUS

Material tables MATXTxy

It is important that the translation of the material table be MATXTxy , whereby xy is a combination of freeformat characters



Entering the Table Attributes

Here the definition is made from which attributes the description of a PDMS file is composed.

You must at least entering the table attributes for PDMS_HEADER_XY and PDMS_DEFAULTS.

In the Physical Attribute column, the sequence of the attributes is defined.

Physical Attribute must be TD.CHAR1.



Entering a Table Group

To work with defaults is not mandatory. You can leave it empty in PDMS:10.01.



Entering the Specific Interface Details

The Table Detail field serves as order sequence, whereas in the freely definable attribute the actual default value is entered.

From the example, it is apparent that through the Table Group the type of PDMS default is defined. The entry in Table Detail controls the sequence of the listed attributes and the field “Default” contains the actual default value.



Assigning Screws and Bolts to the Specification Parts

For the Specification Transfer you need to assign the bolt Commodity Codes to the Specification Line Item Ident. SmartPlant Materials need this information for the bolt heading section in the PDMS Spec file. Enter the accompanying Commodity Code of the bolts in the field Bolt Commodity Code. You can use this commodity code in your CIP to build the bolt references in the spec-file. The internal column name on the table m_spec_items is bolt_commodity_id.



Defining PDMS-CATREF per SmartPlant Materials Commodity Code

The following screen demonstrates how the SmartPlant Materials Commodity Codes are assigned to the PDMS CATREFS.

In this case, the catalog reference for PDMS would be EDE90--B01--0-3E00B9 and specifically for the Commodity Code “EDE90--B01--0-3E00B9”given above. If you cannot find a PDMS interface through the LOV function in the field Interface, please enter it in A.70.01. Please enter only PDMS as the interface code in A.70.01; otherwise, SmartPlant Materials cannot identify this terminus.

Important

• CATREF is reduced during the transfer to 20 characters.



Assigning the Interface Details to the Parts Assign the related details to the part for the table names.



Mapping GTypes, Header, and Details with SmartPlant Materials Short Codes and Option Codes

Select the SmartPlant Materials-Short Code. Changing or deleting is not possible here. The SmartPlant Materials Shortcodes are defined in screen S.10.08 if one is missing.

In the second block, you create the assignment of the SmartPlant Materials Shortcodes to the PDMS terms.

Enter Gtype. The entry is checked against “S.20.I.03” tablename for Gtypes (Translation = GYTPE). If a Gtype should be missing it must be entered in S.20.I.03. LOV is available and contains all valid Gtypes from S.20.I.03.

During the transfer the Gtype is reduced to 4 characters

Select a DefaultFormat you have entered. The entry is checked against the “S.20.I.02” table PDMS_DEFAULTS. LOV is available and contains all groups from the S.20.I.02 table PDMS_DEFAULTS. The default is optional.

Select one of the header formats you entered. The entry is checked against A.50.02. LOV is available and contains all PDMS_HEADER_XX tables from A.50.02.



With the checkboxes PBORx, you can define on which places the Nominal-sizes should be stored in the spec-file.



Creating the PDMS File for the Spec Transfer

With the aid of the screen PDMS.10.02, ASCII files can be created from SmartPlant Materials pipe classes, which in turn can be read into PDMS.

After displaying and doing execute querying the screen, all pipe classes of the project are displayed.

The two check boxes on the left hand side indicate whether or not all necessary mapping work has been done for the pipe class in each case. • CR ⇒ To the Allen Commodity Codes of the pipe class a Catalog

Reference in S.30.I.01 was assigned (Definition PDMS-CATREF per SmartPlant Materials Commodity Code).

• GT⇒ To the Allen ShortCodes of the pipe class a GType in PDMS.10.01 was assigned (Mapping of GTypes, Header, Details with SmartPlant Materials Short Codes and Option Codes).

Before you can start the transfer, you must select at least one specification (Sel indicator) and entering an Export Path (manual input, via LOV or button ‘Save’).



After clicking one of the buttons, a message appears. Click ‘Yes’ to start the transfer.

Several job information messages appear in the status line:

Creating temporary datas

Transfer in progress

Creation of Specfile completed

After the job information ‘Creation of Specfile completed’, the transfer has finished.

After the transfer has been concluded, the following files will be created:

PDMS_OUTPUT_xxxxx.log logfile UTL file directory

- this logfile can be deleted with the button ‘Del Log’

insxxxx.spec specfile defined path in field Export Path

Different buttons gives you information about missing information:

Missing CATREFs (before ore after the transfer has finished)

Click the Missing CATREFS button. You will then get a list of all Commodity Codes for the pipe class to which no catalog references have been assigned yet. By operating the button Maintain CATREFs in S.30.I.01. You can enter the missing catalog references.



Missing Gtypes (before or after the transfer has finished)

Click the Missing Gtypes button. You will then receive a list of all Short Codes of the pipe classes to which no GType has been assigned. Here too you can assign the missing Gtypes with the Maintain button.

Accessing Files in a Web Environment


Accessing Files in a Web Environment In a Web environment, files are written to the application server. In a Web environment, the following step necessary : You are prompted if you want to download the generated files. To enable the download you have to maintain the DBA setting in A.60.04 for PDMS_DOWNLOAD_DEST to determine the destination of the text file on the application server. The value can look like this:

d:\marian551\pdms_files\

The path can be chosen deliberately, but it must exist on the application server. Append a trailing backslash here.

After the file is created, you are prompted if you want to download the file. Confirming, you get a new browser window that supplies the file. Maintain the DBA setting in A.60.04 for PDMS_DOWNLOAD_URL

The value can look like this: Your_web_server/pdms

The name of your web server is followed by a virtual directory name. Do not append a trailing slash. Note, that you have to define an alias in the web server configuration. In the 6iserver.conf file on the application server there should be a line looking like the following:

Alias /pdms/ "d:\marian551\pdms_files/"

The right hand entry must match the PDMS_DOWNLOAD_DEST except that the backslash is replaced by a slash. The left-hand entry must match the PDMS_DOWNLOAD_URL, but the server name is omitted and a trailing slash is added.

You have also the possibility to download the spool-files in a ZIP. When you want a ZIP-File that includes all spool-files, set the project-default ZI_PDMS_ZI to ‘Y’. Please refer to the SmartPlant Materials Installation Guide which steps are necessary to enable the ZIP-Feature in SmartPlant Materials.

Loading SmartPlant Materials Files into PDMS (User Guide)



This chapter explains how to import data from SmartPlant Materials into PDMS.

1. Installing the PDMS Interface Software Keep following steps:

a) Copy the cpsimportmarian directory from the installation CD to the %PMLLIB% directory.

b) Run PDMS (any module) and use the PML REHASH ALL command.



2. Creating Standards for COCO table, GMSE, PTSE, DTSE

Piping components use standard COCO table, GMSE, PTSE a DTSE, created as follows:

a) Run PARAGON.

b) Run the SmartPlant Materials-COCO.mac macro using the following command: $M %PMLLIB%\cpsimportmarian\MARIAN-COCO.mac

c) Run the SmartPlant Materials-CATA. Macros using the following command: $M %PMLLIB%\cpsimportmarian\MARIAN-CATA.mac



If the command runs successfully, the following information displays:

3. Creating UDA Attributes The PDMS Interface software uses the following UDA attributes :IDENT1, :IDENT2, :IDENT3, :IDENT4, :IDENT5, created as follows:

a) Run LEXICON.

b) Run the MARIAN-UDA macro using the following command: $M %PMLLIB%\cpsimportmarian\MARIAN-UDA.mac

4. Creating a Catalog in PARAGON Module The catalog will be created from files exported from SmartPlant Materials, as follows:

a) Run PARAGON.

b) Run the program for creating catalog using command: $M %PMLLIB%\cpsimportmarian\cpsimportcata.mac



c) The following form displays:

Import SmartPlant Materials Catalog dialog box fields:

• MARIAN File – name of file selected for processing

• Events – list of files being processed

• Import mode – Use Add only to put elements in the catalog. Use Add, Change to put elements in the catalog or change their attributes.

• Norm, pressure – The *_G.DAT file must be generated from SmartPlant Materials for particular norms and nominal pressure. Imported norm and pressure are shown selected in the example.



• Select file – selection of file for processing. The following form appears:

d) Select the type of file and its directory location .

• Import –Imports the relevant file. Import files in the following order: - *_M.DAT - Material text

- *_D.DAT - Detail text

- *_B.DAT - Bolt diameter table

- *_BS.DAT - Standart bolts elements

- *_F.DAT - Bolt set

-*_G.DAT - Piping components

After the files are imported, the DAT.LOG file is created in the directory that contains the *.DAT files. These log files contain the import information for the imported files.



5. Creating Component Data Component data are created form file *_C.DAT. Follow these steps:

a) Run the PROPCON module.

b) Run the program for creating the catalog using the following command: $M %PMLLIB%\cpsimportmarian\cpsimportcmpd.mac



c) Follow the same steps as described in the Creating a Catalog in PARAGON module step.



6. Creating Specifications Specifications are created the standard way in SPECON.

7. Example

Appendix: File Examples


Appendix: File Examples SpecCon File $* Piping specification File for all items $* Created by MARIAN 5.5.2 - Copyright 1988 - 2002, Intergraph Corporation $* MARIAN - PDMS SPECS INTERFACE - SPEC CREATING DATE : 05-DEC-02 $* on 05-12-2002 at 19:25 $* Number of Records: 57 $*-- **** Project - No. ************** $* PROJECT 'LIB_INGR' $*-- **** Project - No. ************** NEW SPECIFICATION /FLOW_DIR MATREF =0 FLUREF =0 RATING 0.100 LINETYPE NULL Text 'PIPING' BLTM 'NEW' HEADING TYPE NAME PBOR0 SUFF SHOP CATREF DETAIL MATXT CMPREF BLTREF DEFAULTS - - - = = TUBE */I4199422 100 PREF TRUE /PDPR---B01--1-KP00_100-SCOM /4199422-D /B01-2_32248-M /4199422-C =0 TUBE */I4199423 125 PREF TRUE /PDPR---B01--1-KP00_125-SCOM /4199423-D /B01-2_32248-M /4199423-C =0 TUBE */I4199424 15 PREF TRUE /PDPR---B01--1-KP00_15-SCOM /4199424-D /B01-2_32248-M /4199424-C =0 TUBE */I4199425 150 PREF TRUE /PDPR---B01--1-KP00_150-SCOM /4199425-D /B01-2_32248-M /4199425-C =0 TUBE */I4199426 20 PREF TRUE /PDPR---B01--1-KP00_20-SCOM /4199426-D /B01-2_32248-M /4199426-C =0 TUBE */I4199427 200 PREF TRUE /PDPR---B01--1-KP00_200-SCOM /4199427-D /B01-2_32248-M /4199427-C =0 TUBE */I4199428 25 PREF TRUE /PDPR---B01--1-KP00_25-SCOM /4199428-D /B01-2_32248-M /4199428-C =0 TUBE */I4199429 250 PREF TRUE /PDPR---B01--1-KP00_250-SCOM /4199429-D /B01-2_32248-M /4199429-C =0 TUBE */I4199430 300 PREF TRUE /PDPR---B01--1-KP00_300-SCOM /4199430-D /B01-2_32248-M /4199430-C =0 TUBE */I4199431 32 PREF TRUE /PDPR---B01--1-KP00_32-SCOM /4199431-D /B01-2_32248-M /4199431-C =0 TUBE */I4199432 350 PREF TRUE /PDPR---B01--1-KP00_350-SCOM /4199432-D /B01-2_32248-M /4199432-C =0 TUBE */I4199433 40 PREF TRUE /PDPR---B01--1-KP00_40-SCOM /4199433-D /B01-2_32248-M /4199433-C =0 TUBE */I4199434 400 PREF TRUE /PDPR---B01--1-KP00_400-SCOM /4199434-D /B01-2_32248-M /4199434-C =0 TUBE */I4199435 50 PREF TRUE /PDPR---B01--1-KP00_50-SCOM /4199435-D /B01-2_32248-M /4199435-C =0 TUBE */I4199436 500 PREF TRUE /PDPR---B01--1-KP00_500-SCOM /4199436-D /B01-2_32248-M /4199436-C =0 HEADING TYPE NAME PBOR0 STYP SUFF SHOP CATREF DETAIL MATXT CMPREF BLTREF DEFAULTS - - - = = = FLAN */I4199485 200 FV PREF TRUE /FDFV---B52&CE_200-SCOM /4199485-D /B52_32248-M /4199485-C /991302-22-BS FLAN */I4199486 250 FV PREF TRUE /FDFV---B52&CE_250-SCOM /4199486-D /B52_32248-M /4199486-C /991302-22-BS FLAN */I4199487 300 FV PREF TRUE /FDFV---B52&CE_300-SCOM /4199487-D /B52_32248-M /4199487-C /991302-22-BS FLAN */I4199488 350 FV PREF TRUE /FDFV---B52&CE_350-SCOM /4199488-D /B52_32248-M /4199488-C /991302-22-BS FLAN */I4199489 400 FV PREF TRUE /FDFV---B52&CE_400-SCOM /4199489-D /B52_32248-M /4199489-C /991302-26-BS FLAN */I4199490 500 FV PREF TRUE /FDFV---B52&CE_500-SCOM /4199490-D /B52_32248-M /4199490-C /991302-26-BS HEADING TYPE NAME PBOR0 STYP SUFF ANGLE SHOP CATREF DETAIL MATXT CMPREF BLTREF DEFAULTS - - - = = = = ELBO */I4199439 100 TEXT'E90' PREF 90 TRUE /EDE90--B01--0-3E00B9_100-SCOM /4199439-D /B01_32248-M /4199439-C =0 ELBO */I4199440 125 TEXT'E90' PREF 90 TRUE /EDE90--B01--0-3E00B9_125-SCOM /4199440-D /B01_32248-M /4199440-C =0 ELBO */I4199441 15 TEXT'E90' PREF 90 TRUE /EDE90--B01--0-3E00B9_15-SCOM /4199441-D /B01_32248-M /4199441-C =0 ELBO */I4199442 150 TEXT'E90' PREF 90 TRUE /EDE90--B01--0-3E00B9_150-SCOM /4199442-D /B01_32248-M /4199442-C =0 ELBO */I4199443 20 TEXT'E90' PREF 90 TRUE /EDE90--B01--0-3E00B9_20-SCOM /4199443-D /B01_32248-M /4199443-C =0 ELBO */I4199444 200 TEXT'E90' PREF 90 TRUE /EDE90--B01--0-3E00B9_200-SCOM /4199444-D /B01_32248-M /4199444-C =0 ELBO */I4199445 25 TEXT'E90' PREF 90 TRUE /EDE90--B01--0-3E00B9_25-SCOM /4199445-D /B01_32248-M /4199445-C =0 ELBO */I4199446 250 TEXT'E90' PREF 90 TRUE /EDE90--B01--0-3E00B9_250-SCOM /4199446-D /B01_32248-M /4199446-C =0 ELBO */I4199447 300 TEXT'E90' PREF 90 TRUE /EDE90--B01--0-3E00B9_300-SCOM /4199447-D /B01_32248-M /4199447-C =0 ELBO */I4199448 32 TEXT'E90' PREF 90 TRUE /EDE90--B01--0-3E00B9_32-SCOM /4199448-D /B01_32248-M /4199448-C =0 ELBO */I4199449 350 TEXT'E90' PREF 90 TRUE /EDE90--B01--0-3E00B9_350-SCOM /4199449-D /B01_32248-M /4199449-C =0



ELBO */I4199450 40 TEXT'E90' PREF 90 TRUE /EDE90--B01--0-3E00B9_40-SCOM /4199450-D /B01_32248-M /4199450-C =0 ELBO */I4199451 400 TEXT'E90' PREF 90 TRUE /EDE90--B01--0-3E00B9_400-SCOM /4199451-D /B01_32248-M /4199451-C =0 ELBO */I4199452 50 TEXT'E90' PREF 90 TRUE /EDE90--B01--0-3E00B9_50-SCOM /4199452-D /B01_32248-M /4199452-C =0 ELBO */I4199453 500 TEXT'E90' PREF 90 TRUE /EDE90--B01--0-3E00B9_500-SCOM /4199453-D /B01_32248-M /4199453-C =0 ELBO */I4199454 65 TEXT'E90' PREF 90 TRUE /EDE90--B01--0-3E00B9_65-SCOM /4199454-D /B01_32248-M /4199454-C =0 ELBO */I4199455 80 TEXT'E90' PREF 90 TRUE /EDE90--B01--0-3E00B9_80-SCOM /4199455-D /B01_32248-M /4199455-C =0 HEADING TYPE NAME PBOR0 STYP SUFF SHOP CATREF DETAIL MATXT CMPREF BLTREF DEFAULTS - - - = = = VALV */I4199505 200 GLOB PREF FALSE /V-VALVEV024-W-_200-SCOM /4199505-D /B010_32248-M /4199505-C /991302-22-BS VALV */I4199506 250 GLOB PREF FALSE /V-VALVEV024-W-_250-SCOM /4199506-D /B010_32248-M /4199506-C /991302-22-BS VALV */I4199507 300 GLOB PREF FALSE /V-VALVEV024-W-_300-SCOM /4199507-D /B010_32248-M /4199507-C /991302-22-BS VALV */I4199508 350 GLOB PREF FALSE /V-VALVEV024-W-_350-SCOM /4199508-D /B010_32248-M /4199508-C /991302-22-BS VALV */I4199509 400 GLOB PREF FALSE /V-VALVEV024-W-_400-SCOM /4199509-D /B010_32248-M /4199509-C /991302-26-BS HEADING TYPE NAME PBOR0 STYP SUFF SHOP CATREF DETAIL MATXT BLTREF DEFAULTS - - - = = = GASK */I4199361 200 GASK PREF FALSE /G-FD---R01--D00_200-SCOM /4199361-D /R01_32248-M =0 GASK */I4199362 250 GASK PREF FALSE /G-FD---R01--D00_250-SCOM /4199362-D /R01_32248-M =0 GASK */I4199363 300 GASK PREF FALSE /G-FD---R01--D00_300-SCOM /4199363-D /R01_32248-M =0 GASK */I4199364 350 GASK PREF FALSE /G-FD---R01--D00_350-SCOM /4199364-D /R01_32248-M =0 GASK */I4199365 400 GASK PREF FALSE /G-FD---R01--D00_400-SCOM /4199365-D /R01_32248-M =0 GASK */I4199366 500 GASK PREF FALSE /G-FD---R01--D00_500-SCOM /4199366-D /R01_32248-M =0 HEADING TYPE NAME BDIA BTYP CATREF DETAIL MATXT CMPREF BLTREF DEFAULTS - - - = BOLT */991302-22-BS 22 STUD =0 /991302-D /357_32248-M =0 /991302-22-BS BOLT */991302-26-BS 26 STUD =0 /991302-D /357_32248-M =0 /991302-26-BS BOLT */MARIAN-NUT-22 22 NUT =0 /NUT.DT =0 =0 =0 BOLT */MARIAN-WASH-22 22 WASH =0 /WASH.DT =0 =0 =0 BOLT */MARIAN-NUT-26 26 NUT =0 /NUT.DT =0 =0 =0 BOLT */MARIAN-WASH-26 26 WASH =0 /WASH.DT =0 =0 =0



SpecCon Delta Files

A. Creating a New Specification FILE NAME: e.g. new_b511_12345.spec

NEW SPECIFICATION /B511 LINETYPE NULL TEXT 'PIPING' HEADING TYPE NAME PBOR1 PBOR2 STYP SHOP CATREF DETAIL MATXT CMPREF BLTREF DEFAULTS - - - - = = FLAN */AAFSBF0DD 15.00 15.00 TEXT 'FLSW1' TRUE /AAFSBF0DD /6497796-D /S54U_502950-M /6497796-C =0 EXTRA :TP-IDENT 'C5FN5D' EXTRA :TP-COMMCODE 'FSW1S54U22D01' FLAN */AAFSBF0EE 20.00 20.00 TEXT 'FLSW1' TRUE /AAFSBF0EE /6397957-D /C54X_502950-M /6397957-C =0 EXTRA :TP-IDENT 'C5CWFZ' EXTRA :TP-COMMCODE 'FSW1C54X22D01'

B. Creating a New Component in an Existing Specification FILE NAME: e.g. insert_b511_12345.spec OLD SPECIFICATION /B511 HEADING TYPE NAME PBOR1 PBOR2 STYP SHOP CATREF DETAIL MATXT CMPREF BLTREF DEFAULTS - - - - = =

FLAN */AAFSBF0FF 25.00 25.00 TEXT 'FLSW1' TRUE /AAFSBF0FF /6397958-D /C54X_502950-M /6397958-C =0

EXTRA :TP-IDENT 'C5CWG0' EXTRA :TP-COMMCODE 'FSW1C54X22D01'

FLAN */AAFSBF0HH 40.00 40.00 TEXT 'FLSW1' TRUE /AAFSBF0HH /6397959-D /C54X_502950-M /6397959-C =0

EXTRA :TP-IDENT 'C5CWG1' EXTRA :TP-COMMCODE 'FSW1C54X22D01' The same format is used as defined in case A.



C. Modifying a Component in a Specification Reference is made to case A) and B) which are supposed to be loaded before C) FILE NAME: e.g. modify_b511_12345.spec OLD SPECIFICATION /B511 HEADING NAME TYPE PBOR1 PBOR2 STYP SHOP CATREF DETAIL MATXT CMPREF BLTREF DEFAULTS - - - - = = */AAFSBF0DD FLAN 15.00 15.00 TEXT 'FLSW1' TRUE /AAFSBF0DD /15858200-D /S54U_502950-M /6497796-C =0 EXTRA :TP-IDENT 'C5FN5D' EXTRA :TP-COMMCODE 'FSW1S54U22D01' */AAFSBF0EE FLAN 20.00 20.00 TEXT 'FLSW1' TRUE /AAFSBF0EE /632500007-D /C54X_502950-M /6397957-C =0 EXTRA :TP-IDENT 'C5CWFZ' EXTRA :TP-COMMCODE 'FSW1C54X22D01' */AAFSBF0FF FLAN 25.00 25.00 TEXT 'FLSW1' TRUE /AAFSBF0FF /63002456-D /C54X_502950-M /6397958-C =0 EXTRA :TP-IDENT 'C5CWG0' EXTRA :TP-COMMCODE 'FSW1C54X22D01' */AAFSBF0HH FLAN 40.00 40.00 TEXT 'FLSW1' TRUE /AAFSBF0HH /6397959-D /C54X_502950-M /22200-C =0 EXTRA :TP-IDENT 'C5CWG1' EXTRA :TP-COMMCODE 'FSW1C54X22D01' In this case columns NAME and TYPE shall be swapped. In this sample 15858200-D replace /6497796-D in case A)

D. Removing a Component Reference is made to case A) B) and C) which are supposed to be loaded before FILE NAME: e.g. delete_b511_12345.spec OLD SPECIFICATION /B511 REMOVE */AAFSBF0DD REMOVE */AAFSBF0EE REMOVE */AAFSBF0FF This format is necessary to remove from the spec, items no more needed. Old information will be switched from an active spec to a hold spec named LIMBO by PDMS No header is needed to proceed. The spec header contains

DESC ‘Revision date …..’ This is controlled by a CIP



Spec Insulation File $* Insulation specification File $* Created by MARIAN 5.5.3 - Copyright 1988 - 2002, Intergraph Corporation $* MARIAN - PDMS SPECS INTERFACE - SPEC CREATING DATE : 13-JUN-03 $* on 13-06-2003 at 09:33 $* Number of Records: 5 $*-- **** Project - No. ************** $* PROJECT 'LIB_INGR' $*-- **** Project - No. ************** NEW SPECIFICATION /INSU1 MATREF =0 FLUREF =0 RATING 0.000 LINETYPE NULL BSPEC =0 Text 'INSUL' HEADING TYPE NAME TEMP PBOR0 CATREF DETAIL INSU */IN4497032 101,200 10mm,50mm /IS40 /DE.INS INSU */IN4497033 101,200 80mm,200mm /IS50 /DE.INS INSU */IN4497034 201,400 10mm,50mm /IS60 /DE.INS INSU */IN4497035 201,400 80mm,200mm /IS80 /DE.INS INSU */IN4497036 0,100 10mm,200mm /IS40 /DE.INS



PDMS_B.DAT $*#PDMS Interface - BOLT_DIAMETERS# $*--MARIAN 5.5.2 $*--License-No. 32CB-13A481-C06A6B85AEF077C327FE95D9CA5364-1CADF-25073CE-0-0 $*-- ****************** $*-- * * $*-- ****************** $*-- $*-- $*-- Copyright 1988 - 2002, Intergraph Corporation $*-- $*-- $*-- Call parameters: $*-- $*-- PDMS Copy Job ID : 5261 $*-- Job Code : PDMS $*-- Project (PG) : LIB_INGR $*-- Started on : 20-NOV-2002 $*-- Server side log file : E:\oradata\m54\utl\PDMS_78960.log $*-- Spoolfile : C:\temp\pdms\pdms_b.dat $*-- Spoolfile : C:\temp\pdms\pdms_b.del $*-- Errors and Warnings in : C:\temp\pdms\pdms_b.err $*-- $*-- ------------------------------------------------------- $*-- ---------------- Data Section starts ---------------- $*-- ------------------------------------------------------- $*-- $*-- **** Project - No. ************** $*PROJECT '' $*-- **** Project - No. ************** <START> LIB_INGR Hex_Bolt 991300-22-BLTA 991300-22-LTAB 991300-22 ( 45 50 55 60 65 70 80 90 100 110 120 130 140 150 160 180 200 220 ) 4199215 4199216 4199217 4199218 4199219 4199220 4199221 4199222 4199205 4199206 4199207 4199208 4199209 4199210 4199211 4199212 4199213 4199214



PDMS_BS.DAT

$*#PDMS Interface - SingleBolt# $*--MARIAN 5.5.2 $*--License-No. 32CB-13A481-C06A6B85AEF077C327FE95D9CA5364-1CADF-25073CE-0-0 $*-- ****************** $*-- * * $*-- ****************** $*-- $*-- $*-- Copyright 1988 - 2002, Intergraph Corporation $*-- $*-- $*-- Call parameters: $*-- $*-- PDMS Copy Job ID : 5261 $*-- Job Code : PDMS $*-- Project (PG) : LIB_INGR $*-- Started on : 20-NOV-2002 $*-- Server side log file : E:\oradata\m54\utl\PDMS_78960.log $*-- Spoolfile : C:\temp\pdms\pdms_bs.dat $*-- Delete File : C:\temp\pdms\pdms_bs.del $*-- Errors and Warnings in : C:\temp\pdms\pdms_bs.err $*-- $*-- ------------------------------------------------------- $*-- ---------------- Data Section starts 1---------------- $*-- ------------------------------------------------------- $*-- $*-- **** Project - No. ************** $*PROJECT '' $*-- **** Project - No. ************** <START> LIB_INGR Hex_Bolt 991300-22-BLTA 991300-22-BLIST 991300-22-BS 22 991300-22 0 0 NUT WASH 20 3 <START> LIB_INGR Hex_Bolt 991300-26-BLTA 991300-26-BLIST 991300-26-BS 26 991300-26 0 0 NUT WASH 24 4



<START> LIB_INGR Screw_Bolts 991302-22-BLTA 991302-22-BLIST 991302-22-BS 22 991302-22 0 0 NUT NUT WASH WASH 22.5 22.5 3 3 <START> LIB_INGR Screw_Bolts 991302-26-BLTA 991302-26-BLIST 991302-26-BS 26 991302-26 0 0 NUT NUT WASH WASH 27 27 4 4



PDMS_C.DAT $*#PDMS Interface - CmpData# $*--MARIAN 5.5.2 $*--License-No. 32CB-13A481-C06A6B85AEF077C327FE95D9CA5364-1CADF-25073CE-0-0 $*-- ****************** $*-- * * $*-- ****************** $*-- $*-- $*-- Copyright 1988 - 2002, Intergraph Corporation $*-- $*-- $*-- Call parameters: $*-- $*-- PDMS Copy Job ID : 5261 $*-- Job Code : PDMS $*-- Project (PG) : LIB_INGR $*-- Started on : 20-NOV-2002 $*-- Server side log file : E:\oradata\m54\utl\PDMS_78960.log $*-- Spoolfile : C:\temp\pdms\pdms_c.dat $*-- Spoolfile : C:\temp\pdms\pdms_c.del $*-- Errors and Warnings in : C:\temp\pdms\pdms_c.err $*-- $*-- ------------------------------------------------------- $*-- ---------------- Data Section starts ---------------- $*-- ------------------------------------------------------- $*-- $*-- **** Project - No. ************** $*PROJECT '' $*-- **** Project - No. ************** <START> WEIGHT EDE90--B01--0-3E00B9_100-C 4199439-C 0 0 <START> WEIGHT EDE90--B01--0-3E00B9_125-C 4199440-C 0 0 <START> WEIGHT EDE90--B01--0-3E00B9_15-C 4199441-C 0 0 <START> WEIGHT EDE90--B01--0-3E00B9_150-C 4199442-C 0 0 <START> WEIGHT EDE90--B01--0-3E00B9_20-C 4199443-C 0 0



PDMS_D.DAT $*#PDMS Interface - Detail# $*--MARIAN 5.5.2 $*--License-No. 32CB-13A481-C06A6B85AEF077C327FE95D9CA5364-1CADF-25073CE-0-0 $*-- ****************** $*-- * * $*-- ****************** $*-- $*-- $*-- Copyright 1988 - 2002, Intergraph Corporation $*-- $*-- $*-- Call parameters: $*-- $*-- PDMS Copy Job ID : 5261 $*-- Job Code : PDMS $*-- Project (PG) : LIB_INGR $*-- Started on : 20-NOV-2002 $*-- Server side log file : E:\oradata\m54\utl\PDMS_78960.log $*-- Spoolfile : C:\temp\pdms\pdms_d.dat $*-- Deletefile : C:\temp\pdms\pdms_d.del $*-- Errors and Warnings in : C:\temp\pdms\pdms_d.err $*-- $*-- ------------------------------------------------------- $*-- ---------------- Data Section starts ---------------- $*-- ------------------------------------------------------- $*-- $*-- **** Project - No. ************** $*PROJECT '' $*-- **** Project - No. ************** <START> LIB_INGR Elbow_90° 4199439-D ELBW Elbow 90° St37.0 DIN 2605 - no entry <START> LIB_INGR Elbow_90° 4199440-D ELBW Elbow 90° St37.0 DIN 2605 - no entry <START> LIB_INGR Elbow_90° 4199441-D ELBW Elbow 90° St37.0 DIN 2605 - no entry <START> LIB_INGR Elbow_90° 4199442-D ELBW Elbow 90° St37.0 DIN 2605 - no entry



PDMS_F.DAT $*#PDMS Interface - FLANGE-BOLT-POINTS# $*--MARIAN 5.5.2 $*--License-No. 32CB-13A481-C06A6B85AEF077C327FE95D9CA5364-1CADF-25073CE-0-0 $*-- ****************** $*-- * * $*-- ****************** $*-- $*-- $*-- Copyright 1988 - 2002, Intergraph Corporation $*-- $*-- $*-- Call parameters: $*-- $*-- PDMS Copy Job ID : 5261 $*-- Job Code : PDMS $*-- Project (PG) : LIB_INGR $*-- Started on : 20-NOV-2002 $*-- Server side log file : E:\oradata\m54\utl\PDMS_78960.log $*-- Spoolfile : C:\temp\pdms\pdms_f.dat $*-- Delete File : C:\temp\pdms\pdms_f.del $*-- Errors and Warnings in : C:\temp\pdms\pdms_f.err $*-- $*-- ------------------------------------------------------- $*-- ---------------- Data Section starts ---------------- $*-- ------------------------------------------------------- $*-- $*-- **** Project - No. ************** $*PROJECT '' $*-- **** Project - No. ************** <START> LIB_INGR Globe_Valve V-VALVEV024-W-_200-F V-VALVEV024-W-_200-F:12:1 1 22 STUD PARAM 12 <START> LIB_INGR Globe_Valve V-VALVEV024-W-_200-F V-VALVEV024-W-_200-F:12:2 2 22 STUD PARAM 12 <START> LIB_INGR Globe_Valve V-VALVEV024-W-_200-F V-VALVEV024-W-_200-F:12:3 3 22 STUD PARAM 12 <START> LIB_INGR Globe_Valve V-VALVEV024-W-_200-F V-VALVEV024-W-_200-F:12:4



4 22 STUD PARAM 12 <START> LIB_INGR Globe_Valve V-VALVEV024-W-_200-F V-VALVEV024-W-_200-F:12:5 5 22 STUD PARAM 12 <START> LIB_INGR Globe_Valve V-VALVEV024-W-_200-F V-VALVEV024-W-_200-F:12:6 6 22 STUD PARAM 12 <START> LIB_INGR Globe_Valve V-VALVEV024-W-_200-F V-VALVEV024-W-_200-F:12:7 7 22 STUD PARAM 12 <START> LIB_INGR Globe_Valve V-VALVEV024-W-_200-F V-VALVEV024-W-_200-F:12:8 8 22 STUD PARAM 12

PDMS_G.DAT $*#PDMS Interface - Catref# $*--MARIAN 5.5.2 $*--License-No. 32CB-13A481-C06A6B85AEF077C327FE95D9CA5364-1CADF-25073CE-0-0 $*-- ****************** $*-- * * $*-- ****************** $*-- $*-- $*-- Copyright 1988 - 2002, Intergraph Corporation $*-- $*-- $*-- Call parameters: $*-- $*-- PDMS Copy Job ID : 5261 $*-- Job Code : PDMS $*-- Project (PG) : LIB_INGR $*-- Started on : 20-NOV-2002 $*-- Server side log file : E:\oradata\m54\utl\PDMS_78960.log $*-- Spoolfile : C:\temp\pdms\pdms_g.dat $*-- Delete File : C:\temp\pdms\pdms_g.del $*-- Errors and Warnings in : C:\temp\pdms\pdms_g.err



$*-- $*-- ------------------------------------------------------- $*-- ---------------- Data Section starts ---------------- $*-- ------------------------------------------------------- $*-- $*-- **** Project - No. ************** $*PROJECT '' $*-- **** Project - No. ************** <START> LIB_INGR Elbow_90° EDE90--B01--0-3E00B9 EDE90--B01--0-3E00B9_100-SCOM ELBO ELBW-G ELBW-P ELBW-D 100 100 0 BWD BWD 0 0 0 152 90 0 0 0 nulref <START> LIB_INGR Elbow_90° EDE90--B01--0-3E00B9 EDE90--B01--0-3E00B9_125-SCOM ELBO ELBW-G ELBW-P ELBW-D 125 125 0 BWD BWD 0 0 0 190 90 0 0 0 nulref <START> LIB_INGR Elbow_90° EDE90--B01--0-3E00B9 EDE90--B01--0-3E00B9_15-SCOM ELBO ELBW-G ELBW-P ELBW-D 15 15 0 BWD BWD 0 0 0 28 90 0 0 0 nulref <START> LIB_INGR Elbow_90° EDE90--B01--0-3E00B9 EDE90--B01--0-3E00B9_150-SCOM ELBO ELBW-G ELBW-P ELBW-D 150 150 0 BWD BWD 0 0 0 229 90 0 0 0 nulref



PDMS_M.DAT $*#PDMS Interface - Detail# $*--MARIAN 5.5.2 $*--License-No. 32CB-13A481-C06A6B85AEF077C327FE95D9CA5364-1CADF-25073CE-0-0 $*-- ****************** $*-- * * $*-- ****************** $*-- $*-- $*-- Copyright 1988 - 2002, Intergraph Corporation $*-- $*-- $*-- Call parameters: $*-- $*-- PDMS Copy Job ID : 5261 $*-- Job Code : PDMS $*-- Project (PG) : LIB_INGR $*-- Started on : 20-NOV-2002 $*-- Server side log file : E:\oradata\m54\utl\PDMS_78960.log $*-- Spoolfile : C:\temp\pdms\pdms_m.dat $*-- Errors and Warnings in : C:\temp\pdms\pdms_m.err $*-- $*-- ------------------------------------------------------- $*-- ---------------- Data Section starts ---------------- $*-- ------------------------------------------------------- $*-- $*-- **** Project - No. ************** $*PROJECT '' $*-- **** Project - No. ************** <START> LIB_INGR Elbow_90° B01_32248-M St37.0 <START> LIB_INGR Flat_Gasket R01_32248-M Rubber_/BASF_Quality_63 <START> LIB_INGR Globe_Valve B010_32248-M St37.2 <START> LIB_INGR Hex_Bolt -_32248-M - <START> LIB_INGR Pipe B01-2_32248-M St37.0 <START> LIB_INGR Screw_Bolts 357_32248-M 21CrMoV57 <START> LIB_INGR Welding_Neck_Flange B52_32248-M S235JRG2

Appendix: CIPs


Appendix: CIPs PROCEDURE SET_S2008(p_log_id IN NUMBER); Is called by the creation of the spec-file. This procedure summarizes all calls to attributes in the spec-file which are mapped in the SmartPlant Materials-screen S.20.08. FUNCTION bfle_weight(p_ident IN m_idents.ident%TYPE, p_weight IN NUMBER) RETURN NUMBER; You can write in c.dat-file a second weight. This CIP calculates this weight. FUNCTION CATE (P_INTERFACE_ID IN m_interfaces.interface_id%TYPE, P_COMMODITY_ID IN m_commodity_codes.commodity_id%TYPE) RETURN VARCHAR2;

Returns the cate. Standard is the commodity code interfaced translation for PDMS.

PRAGMA RESTRICT_REFERENCES(CATE, WNDS,WNPS); FUNCTION CATE_TEXT (P_INTERFACE_ID IN m_interfaces.interface_id%TYPE, P_COMMODITY_ID IN m_commodity_codes.commodity_id%TYPE) RETURN VARCHAR2;

This function is used for the g.dat file. It is additional information about the cate. FUNCTION GTYPE (P_INTERFACE_ID IN m_interfaces.interface_id%TYPE, P_COMMODITY_ID IN m_commodity_codes.commodity_id%TYPE) RETURN VARCHAR2;

Returns the gtype for the g.dat file. FUNCTION CATE_STEXT (P_INTERFACE_ID IN m_interfaces.interface_id%TYPE, P_COMMODITY_ID IN m_commodity_codes.commodity_id%TYPE) RETURN VARCHAR2;

This function is used for the g.dat file. It is additional information about the cate. FUNCTION SCOM (P_INTERFACE_ID IN m_interfaces.interface_id%TYPE, P_COMMODITY_ID IN m_commodity_codes.commodity_id%TYPE, P_IDENT IN M_IDENTS.IDENT%TYPE, P_LOG_ID IN NUMBER ) RETURN VARCHAR2;

This function is used for the g.dat-file and the spec-file. Standard is that the function returns the cate and information about the Nominal Sizes.

Appendix: CIPs


FUNCTION s2008(p_commodity_id NUMBER , p_translation VARCHAR2 , p_interface_id NUMBER ) RETURN VARCHAR2;

This function looks for the mappings in S.20.08, for the styp, btyp, radius, angle, shop. FUNCTION SECT (P_COMMODITY_ID IN m_commodity_codes.commodity_id%TYPE, P_NLS_ID IN m_nls.nls_id%TYPE) RETURN VARCHAR2;

Returns the section for all PDMS.20.01 related files. Standard is that the function returns the part nls for the nls_id which is defined in PDMS.30.01 for RTEXT-Nls. FUNCTION FIND_IN_CCD (P_COMMODITY_ID NUMBER ,P_TRANSLATION VARCHAR2 ,p_INTERFACE_ID NUMBER ,p_nls_id NUMBER ,p_code_or_desc VARCHAR2) RETURN VARCHAR2;

Looks for the material-reference or the description. It is used in the specfile or for the m.dat-file.

PROCEDURE GENERAL_SPEC_FILE_UPDATE(P_LOG_ID IN m_pdms_logs.id%TYPE); With this procedure you can manipulate the spec-file-result at least. After this call there is no manipulation inside the standard-package. FUNCTION example_cip_pdms3002 (P_IDENT IN M_IDENTS.IDENT%TYPE) RETURN VARCHAR2; FUNCTION GET_UNIT(p_commodity_id IN m_commodity_codes.commodity_id%TYPE, p_digit IN m_obj_parm_det.detail_id%TYPE) RETURN VARCHAR2; Looks for the unit of several Attributes. FUNCTION get_insu_name (p_gd_id IN m_geom_details.gd_id%TYPE) RETURN VARCHAR2;

This function returns the needed name reference for the spec file

FUNCTION get_insu_type RETURN VARCHAR2;

This function returns the needed g-type reference for the spec file FUNCTION get_insu_temp (p_gd_id IN m_geom_details.gd_id%TYPE, p_temp_from_value IN VARCHAR2, p_temp_to_value IN VARCHAR2) RETURN VARCHAR2;

This function returns the needed temp for the spec file

Appendix: CIPs


FUNCTION get_insu_pbor0 (p_gd_id IN m_geom_details.gd_id%TYPE, p_dn_from_value IN VARCHAR2, p_dn_to_value IN VARCHAR2, p_unit IN VARCHAR2) RETURN VARCHAR2;

=> this function returns the needed pbor0 for the spec file FUNCTION get_insu_catref (p_gd_id IN m_geom_details.gd_id%TYPE, p_insu_thk_value IN VARCHAR2) RETURN VARCHAR2;

=>this function returns the needed catref reference for the spec file FUNCTION get_insu_detail (p_gd_id IN m_geom_details.gd_id%TYPE) RETURN VARCHAR2; => this function returns the needed detail reference for the spec file FUNCTION get_insu_heading RETURN VARCHAR2; =>this function returns the needed heading fields for the spec file FUNCTION set_insu_fields (p_name IN m_pdms_spec_gds.name%TYPE, p_type IN m_pdms_spec_gds.type%TYPE, p_temp IN m_pdms_spec_gds.temp%TYPE, p_pbor0 IN m_pdms_spec_gds.pbor0%TYPE, p_catref IN m_pdms_spec_gds.catref%TYPE, p_detail IN m_pdms_spec_gds.detail%TYPE, p_unit0 IN m_pdms_spec_gds.unit0%TYPE) RETURN VARCHAR2; => User defined heading fields for Insulation Specifications FUNCTION get_insu_g_dat (p_field IN VARCHAR2, p_gn_id IN m_geom_names.gn_id%TYPE, p_dn IN m_nominal_size_details.dn%TYPE, p_unit IN m_units.unit_code%TYPE DEFAULT NULL) RETURN VARCHAR2;

=> this function returns the needed values for the insulation _g.dat file PROCEDURE GENERAL_PDMS2001(p_pcc_id IN m_pdms_copy_ccs.pcc_id%TYPE); This procedure is called from a transfer started in PDMS.20.01. This procedure call is the last step in the transfer and you have the possibility to modify any format or data in the output files. PROCEDURE PREP_OUTPUT(p_log_id IN m_pdms_logs.id%TYPE); Gives you the possibility to add additional attributes into the spec-file. For this purpose, please use the SUB_SEQ_ID on the table m_pdms_lines. The attributes for one line must have the same seq_id with the sub_seq_id in the order in which the attributes should be written in the spec-file. This procedure is called for the file with new lines.

Appendix: CIPs


PROCEDURE PREP_OUTPUT_DEL(p_log_id IN m_pdms_logs.id%TYPE); Gives you the possibility to add additional attributes into the spec-file. For this purpose, please use the SUB_SEQ_ID on the table m_pdms_lines. The attributes for one line must have the same seq_id with the sub_seq_id in the order in which the attributes should be written in the spec-file. This procedure is called for the file with deleted lines. PROCEDURE PREP_OUTPUT_INS(p_log_id IN m_pdms_logs.id%TYPE); Gives you the possibility to add additional attributes into the spec-file. For this purpose, please use the SUB_SEQ_ID on the table m_pdms_lines. The attributes for one line must have the same seq_id with the sub_seq_id in the order in which the attributes should be written in the spec-file. This procedure is called for the file with inserted lines. PROCEDURE PREP_OUTPUT_MOD(p_log_id IN m_pdms_logs.id%TYPE); Gives you the possibility to add additional attributes into the spec-file. For this purpose, please use the SUB_SEQ_ID on the table m_pdms_lines. The attributes for one line must have than the same seq_id with the sub_seq_id in the order in which the attributes should be written in the spec-file. This procedure is called for the file with modified lines. FUNCTION prep_out_set_delete_desc (p_log_id IN m_pdms_logs.id%TYPE) RETURN VARCHAR2;

=> this function returns a header line for the delete-file

FUNCTION TEXT (P_IDENT IN m_idents.ident%TYPE, P_NLS_ID IN m_nls.nls_id%TYPE, p_COMMODITY_ID m_commodity_codes.commodity_id%TYPE) RETURN VARCHAR2;

Returns the detail-text in the d.dat-file. PROCEDURE spec_bolt_ref (p_commodity_id IN m_commodity_codes.commodity_id%TYPE, p_ident IN m_idents.ident%TYPE, p_spec_item_id IN m_spec_items.spec_item_id%TYPE, p_type IN m_pdms_spec_idents.type%TYPE, p_pdms_si_id IN m_pdms_spec_idents.pdms_si_id%TYPE); CIP to fill the Bolt-related data into the specfile. PROCEDURE file_bolt_ref(p_pcc_id IN m_pdms_copy_ccs.pcc_id%TYPE, p_commodity_id IN m_commodity_codes.commodity_id%TYPE, p_input_1 IN m_idents.input_1%TYPE); CIP to fill the SingleBolt-File. FUNCTION COCO (p_commodity_id IN m_commodity_codes.commodity_id%TYPE) RETURN VARCHAR2;

Appendix: CIPs


Get the connection-type for g.dat-file. FUNCTION GET_BTYPE(p_ident IN m_idents.ident%TYPE, p_attr_id IN m_attrs.attr_id%TYPE) RETURN VARCHAR2 ; Get the bolttype for f.dat-file. FUNCTION IDENT_ATTRS (P_IDENT IN m_idents.ident%TYPE, P_INTERFACE_ID IN m_interfaces.interface_id%TYPE) RETURN VARCHAR2;

Fill the parad-line in the g.dat-file. PROCEDURE GPD_REF(P_INTERFACE_ID IN NUMBER, P_COMMODITY_ID IN NUMBER, P_IDENT IN NUMBER, p_gmref OUT VARCHAR2, p_tref OUT VARCHAR2, p_dref OUT VARCHAR2 ); This procedure returns the gmref, ptref, dtref fields for the g.dat-file. FUNCTION get_flbp(p_commodity_id IN NUMBER, p_parad IN VARCHAR2) RETURN PLS_INTEGER; FUNCTION GET_IDENT_CODE(p_ident IN NUMBER) RETURN VARCHAR2; This function gives you the possibility to translate the ident-code which you see in the b.dat file(as a user-defined-attribute). FUNCTION DTSE (P_COMMODITY_ID IN m_commodity_codes.commodity_id%TYPE, P_INTERFACE_ID IN m_interfaces.interface_id%TYPE) RETURN VARCHAR2;

Only for the dataset used. The dataset describes the attribute-set which you transfer with the g.dat-file. This file-type is only available when in PDMS.30.01 the checkbox ‘With dataset?’ is marked. FUNCTION SKEY (P_INTERFACE_ID IN m_interfaces.interface_id%TYPE, P_COMMODITY_ID IN m_commodity_codes.commodity_id%TYPE) RETURN VARCHAR2;

Returns the skey for the d.dat-file. FUNCTION GET_CATA(p_type IN VARCHAR2, p_pk IN NUMBER) RETURN VARCHAR2; Returns the Cata for all result-files. Depending on if the file is ident or commodity-code driven, the standard-function looks for the proj_id from the ident or commodity code.

Appendix: CIPs


PROCEDURE FILL_COMP_ATTRS(p_pcc_Id IN NUMBER, p_pw_id IN NUMBER, p_ident IN NUMBER ); Give you the possibility to fill data into m_pdms_weight_attrs which you can spool out into the c.dat-file. The example-code used for this purpose the screen A.60.13 Ident Attribute Functions. PROCEDURE PREP_OUTPUT_HEADING(p_log_id IN m_pdms_logs.id%TYPE, p_log_type IN m_pdms_lines.log_type%TYPE); Fill the heading lines like ‘MATREF’, ‘RATING’. You can change the default here.

Documents

SmartPlant Materials PDMS Interface - Hyundai …spmat.hec.co.kr/marian_webentry/Pdfs/INT-PDMS.pdf · Intergraph Corporation is not responsible for any error that may appear ... YY’