Int PDMS

Download as pdf or txt
Download as pdf or txt
You are on page 1of 92

SmartPlant Materials

PDMS Interface User's Guide

Version 2011 R1 SP2 (7.1.2)

November 2014

DMAR1-PE-200010I
Copyright
Copyright © 2000-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 Materials PDMS Interface 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.
e. 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, Intergraph Smart, PDS, SmartPlant, SmartMarine, FrameWorks, I-Sketch, IntelliShip, ISOGEN,
SmartSketch, SPOOLGEN, SupportManager, SupportModeler, Sapphire, and FreeView 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. MicroStation is a registered trademark of Bentley Systems, Inc. Other brands and product names are
trademarks of their respective owners.

SmartPlant Materials PDMS Interface User's Guide 3


4 SmartPlant Materials PDMS Interface User's Guide
Contents
Preface .......................................................................................................................................................... 7
Documentation Comments ..................................................................................................................... 7

Introduction .................................................................................................................................................. 9

Configuration ............................................................................................................................................. 11
DBA Settings ......................................................................................................................................... 11
Project Defaults ..................................................................................................................................... 11
SQL_PATH ........................................................................................................................................... 11
Definition of the PDMS Interface........................................................................................................... 12

Ident Transfer ............................................................................................................................................. 13


Ident Transfer Files ............................................................................................................................... 13
Detail Text (PDMS_D.DAT) ............................................................................................................ 13
Component Data (PDMS_C.DAT) .................................................................................................. 14
Geometrics (PDMS_G.DAT) .......................................................................................................... 15
Flange-Bolt-Points (PDMS_F.DAT)................................................................................................ 16
Single Bolt Idents (PDMS_BS.DAT)............................................................................................... 17
Bolt Length (PDMS_B.DAT) ........................................................................................................... 18
Material (PDMS_M.DAT) ................................................................................................................ 19
Attributes for Ident Transfer .................................................................................................................. 20
Attribute Translation for PDMS ............................................................................................................. 21
Tables for PDMS ................................................................................................................................... 22
Table Translation for PDMS.................................................................................................................. 22
Table Attributes ..................................................................................................................................... 24
Importing GTYPE and SKEY Data........................................................................................................ 24
Assignment of Interface Details to Parts ............................................................................................... 26
PDMS CATREFs Defined per Commodity Code .................................................................................. 27
PDMS Groups ....................................................................................................................................... 28
PDMS Configurations ........................................................................................................................... 29
G-Type Attribute Mapping ..................................................................................................................... 31
PDMS Files for Ident Transfer .............................................................................................................. 37

Specification Transfer ............................................................................................................................... 39


PDMS Specon File ................................................................................................................................ 40
PDMS Insulation File ............................................................................................................................ 40
Attributes for Spec Transfer .................................................................................................................. 41
Attribute Translation for PDMS ............................................................................................................. 43
Tables for PDMS ................................................................................................................................... 44
Importing GTYPE Data ......................................................................................................................... 44
Table Translation for PDMS.................................................................................................................. 45
Table Attributes ..................................................................................................................................... 47
Assigning Bolts to Specification Parts................................................................................................... 47
PDMS CATREFs Defined per Commodity Code .................................................................................. 49
Assignment of Interface Details to Parts ............................................................................................... 50
Short Code – Gtype Mapping ............................................................................................................... 50

SmartPlant Materials PDMS Interface User's Guide 5


Contents

Post Processing .................................................................................................................................... 51


GType Configurations ........................................................................................................................... 52
Copy Product Group Details ........................................................................................................... 53
PDMS File for Spec Transfer ................................................................................................................ 54
Missing CATREFs .......................................................................................................................... 59
Missing GTypes .............................................................................................................................. 60

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


Installing the PDMS Interface Software ................................................................................................ 61
Creating Standards for COCO table, GMSE, PTSE, DTSE ................................................................. 61
Creating UDA Attributes ........................................................................................................................ 63
Creating a Catalog in PARAGON Module ............................................................................................ 63
Creating Component Data .................................................................................................................... 66
Creating Specifications ......................................................................................................................... 67
Example ................................................................................................................................................ 68

Appendix: File Examples .......................................................................................................................... 69


Specon File ........................................................................................................................................... 69
Specon Delta Files ................................................................................................................................ 72
A. Creating a New Specification ..................................................................................................... 72
B. Creating a New Component in an Existing Specification........................................................... 72
C. Modifying a Component in a Specification ................................................................................ 73
D. Removing a Component ............................................................................................................ 73
Spec Insulation File ............................................................................................................................... 74
PDMS_B.DAT ....................................................................................................................................... 74
PDMS_BS.DAT ..................................................................................................................................... 75
PDMS_C.DAT ....................................................................................................................................... 77
PDMS_D.DAT ....................................................................................................................................... 79
PDMS_F.DAT ....................................................................................................................................... 80
PDMS_G.DAT ....................................................................................................................................... 82
PDMS_M.DAT....................................................................................................................................... 83

Appendix: CIPs .......................................................................................................................................... 85

Index ........................................................................................................................................................... 91

6 SmartPlant Materials PDMS Interface User's Guide


Preface
This document describes the PDMS interface.

Documentation Comments
Send documentation comments or suggestions to PPMdoc@intergraph.com
(mailto:ppmdoc@intergraph.com?subject=documentation comments).

SmartPlant Materials PDMS Interface User's Guide 7


Preface

8 SmartPlant Materials PDMS Interface User's Guide


SECTION 1

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 types of transfers: ident transfer and specification
transfer. Some steps are the same for both kind of transfers, and some are only for one type 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. For more information about the
purpose of each individual file, see Ident Transfer (on page 13).
These files are loaded into PDMS.

SmartPlant Materials PDMS Interface User's Guide 9


Introduction

10 SmartPlant Materials PDMS Interface User's Guide


SECTION 2

Configuration
Check the following configuration settings:

DBA Settings
PLUS_EXECUTABLE: Enter the SQL plus version with which the scripts will be worked.
PDMS_DOWNLOAD_DEST: To enable the file download, you must specify the file destination
on the application server. Here is an example of the value:
C:\SPMAT\download\
PDMS_DOWNLOAD_URL: To enable the file download, you must specify the URL of the file
destination on the application server. Here is an example of the value:
your_as_server/download
The name of the application server is followed by a virtual directory name.
For more information about these DBA settings, see SmartPlant Materials DBA Settings,
available from the Printable Guides page in the software.

Project Defaults
ZI_PDMS_ZI: Must be set to Y if you want to download all created spoolfiles bundled in a ZIP
file.
For more information about project defaults, see SmartPlant Materials Project Defaults,
available from the Printable Guides page in the software.
To know which steps are necessary to enable the ZIP feature in SmartPlant Materials, refer to
the SmartPlant Materials Installation and Migration Guide, also available from the Printable
Guides page in the software.

SQL_PATH
The application server registry entry for SQL_PATH points to the folder where the files
necessary for the PDMS interface are located.
These scripts are delivered with the SmartPlant Materials installation and are automatically
placed in the right location.

SmartPlant Materials PDMS Interface User's Guide 11


Configuration

Definition of the PDMS Interface


To define the PDMS interface for use in SmartPlant Reference Data, enter PDMS in
the Interface field on the A.70.01 Interfaces screen. Descriptions can be entered in the Short
Desc and Description fields.

12 SmartPlant Materials PDMS Interface User's Guide


SECTION 3

Ident Transfer
Depending on the file type (PDMS 20.01 Create PDMS Files), various files are created. The
ones you need depend on 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)
Contains detail text information.
<START> CATA SECT SDTE
SKEY
RTEXT
STEXT
TTEXT

CATA: m_pck_pdms_custom.get_cata('I' ,ident)


Look at the example PL/SQL-Code. With the parameter values ‘I’ and
ident, the function fetches the project identifier of the ident that 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

SmartPlant Materials PDMS Interface User's Guide 13


Ident Transfer

You can also influence the building of text built here; it comes from the CIP
m_pck_pdms_custom.text.
If a commodity code has no SKEY (SKEY = ‘NONE’), a blank line for SKEY will be written.

pdms_d.del Contains information about detail text that is no longer 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 errors 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 errors that appeared during the component data
transfer.

14 SmartPlant Materials PDMS Interface User's Guide


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' ,ident)


Look at the example PL/SQL-Code. With the parameter values ‘I’ and
ident, the function fetches the project identifier of the ident that 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)

CATE: default is CCI_CODE (S.30.I.01 Interface Dependent),


CIP (M_PCK_PDMS_CUSTOM.CATE, input INTERFACE_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, Comes from the CIP m_pck_pdms_custom.


DTREF: 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 on PDMS 30.02 G-Type Attribute Mapping

BLFRA: CCI_CODE || INPUT_1 || INPUT_2 … || ‘-F’


When the item is not bolted, BLRFA is empty.

SmartPlant Materials PDMS Interface User's Guide 15


Ident Transfer

pdms_g.del Contains information about SCOM that is 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 in
PDMS, too.)

pdms_g.err Contains information about errors that occurred during the geometric
transfer.

Flange-Bolt-Points (PDMS_F.DAT)
Contains all the information of the bolt ident that is referenced in the PDMS_G.dat file.
<START> CATA SECT CATE BTSE
NUMBER
DIAMETER
BTYPE
BTHK

CATA: m_pck_pdms_custom.get_cata('I' ,ident)


Look at the example PL/SQL-Code. With the parameter values ‘I’ and
ident, the function fetches the project identifier of the ident that 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)

CATE: default is CCI_CODE (S.30.I.01 Interface Dependent),


CIP (M_PCK_PDMS_CUSTOM.CATE, input INTERFACE_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 one bolt is needed, the software counts up from 1 to the
number of needed bolts. For each number of needed bolts, the software
inserts a new <START> section.

16 SmartPlant Materials PDMS Interface User's Guide


Ident Transfer

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

BTYPE: defined on PDMS 30.01, second block. Result comes from


m_pck_pdms_custom.GET_BTYPE(p_ident,p_attr_id ). When no attribute
on PDMS 30.01 is defined or the result of the function is NULL, ‘BOLT’ is
the default.

BTHK: defined on PDMS 30.01

On PDMS 30.01, you can define an additional attribute for the value that is added to the flange
thickness.
Also on PDMS 30.01, you can define more than one bolt.

pdms_f.del Contains information about SCOM that is no longer contained opposite the
last run in the PDMS_F.dat.

pdms_f.err Contains information about errors that occurred during the flange bolt
transfer.

Single Bolt Idents (PDMS_BS.DAT)


Contains all the 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' , ident)


Look at the example PL/SQL-Code. With the parameter values ‘I’ and
ident, the function fetches the project identifier of the ident that 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)

BLTA: COMMODITY_ID || '-'|| INPUT_1 ||'-BLTA'

SmartPlant Materials PDMS Interface User's Guide 17


Ident Transfer

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: extra length of the bolt

BITEM: if a nut or washer is needed

BITLE: diameter of the nut or washer

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 that 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 longer 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 in PDMS, too.)

pdms_bs.err Contains information about errors that occurred during the bolt set
transfer.

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

Bolt Length (PDMS_B.DAT)


Contains the 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', commodity_id)


Look at the example PL/SQL-Code. With the parameter values ‘CC’ and
commodity_id, the function fetches the project identifier of the commodity
code that 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)

BLTA: COMMODITY_ID || '-'|| INPUT_1 ||'-BLTA'

18 SmartPlant Materials PDMS Interface User's Guide


Ident Transfer

LTAB: COMMODITY_ID || '-'|| INPUT_1 ||'-LTAB'

DTAB: COMMODITY_ID || '-'|| INPUT_1

BoltLength: INPUT_2,
All commodity codes that are listed in the rule defined on PDMS 30.01
Configure PDMS field Rule for Bolts

IDENT: IDENT

pdms_b.del Contains information about SCOM that is 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 in PDMS, too.)

pdms_b.err Contains information about errors that occurred during the bolt 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)


Look at the example PL/SQL-Code. With the parameter values ‘CC’ and
commodity_id, the function fetches the project identifier of the commodity
code that 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', INTERFACE_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', INTERFACE_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

SmartPlant Materials PDMS Interface User's Guide 19


Ident Transfer

YTEXT: default is SHORT_DESC of table detail (or table detail link)


CIP (M_PCK_PDMS_CUSTOM.FIND_IN_CCD, input COMMODITY_ID,
'MATXT', INTERFACE_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', INTERFACE_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 a blank line will be written for
YTEXT and/or ZTEXT.

pdms_m.err Contains information about errors that occurred during the material text
transfer.

Attributes for Ident Transfer


Use the A.50.01 Attributes screen 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 PDMS interface on A.50.I.02.

20 SmartPlant Materials PDMS Interface User's Guide


Ident Transfer

For the GTYPE attribute, insert the following Derived From clause:

Attribute Translation for PDMS


Use the A.50.I.02 screen to enter the translation for the PDMS interface for all defined attributes
that will be used on PDMS 30.02 G-Type Mapping, second block, Type 'Geometry.'

SmartPlant Materials PDMS Interface User's Guide 21


Ident Transfer

Tables for PDMS


Use the A.50.02 screen to define tables.

Here you must define the tables for the PDMS interface. They must belong to the INTERFACE
table type.
You need one table for GTYPEs and one for SKEYs. The names of the tables are free format.

Table Translation for PDMS


You need a translation for the following tables:

Table name Translation for PDMS interface

GTYPE (freeformat) GTYPE

SKEY (freeformat) SKEY

Material tables MATXTxxxxxxx

22 SmartPlant Materials PDMS Interface User's Guide


Ident Transfer

SmartPlant Materials PDMS Interface User's Guide 23


Ident Transfer

Table Attributes
This screen shows the GTYPE attribute with the SKEY table. Enter TD.CHAR1 in the Physical
Attribute field.

Importing GTYPE and SKEY Data


You can import the default data for the GTYPE and SKEY tables. SmartPlant Materials displays
the default data, which you can add, modify, and delete.

GTYPE Data
In the Import Type field, use the LOV to insert PDMS_GTYPE. In the Table Type Description
field, enter an existing table type description, and in the Table Type field, select INTERFACE.

24 SmartPlant Materials PDMS Interface User's Guide


Ident Transfer

In the Table Name field, enter the table name, which was defined in the previous step, for the
table GTYPE.

Enter an existing table group (S.20.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.

SKEY Data
In the Import Type field, use the LOV to insert PDMS_SKEY. In the Table Type Description
field, enter an existing table type description, and in the Table Type field, select INTERFACE.
In the Table Name field, enter the table name, which was defined in the previous step, for the
table SKEY.

SmartPlant Materials PDMS Interface User's Guide 25


Ident Transfer

Enter 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 Display Import Rows button to see the default data.
Click the Start Import button.

Assignment of Interface Details to Parts


Assign the related GType and SKEY to the part for the GTYPE and SKEY tablenames.
If a part has no SKEY, use SKEY NONE. This is very important because only parts with a
mapping to the related GTYPE and SKEY will be taken into account.

26 SmartPlant Materials PDMS Interface User's Guide


Ident Transfer

PDMS CATREFs Defined per Commodity Code


The following screen shows how the SmartPlant Materials commodity codes are assigned to the
PDMS CATREFs.

In this case, the catalog reference for PDMS is D31CG5WHM1TB000 and specifically for the
commodity code "D31CG5WHM1TB000" given above. Use the LOV in the Interface field in the
Interface Codes block to select ‘PDMS’ from the list. Then enter the PDMS specific code in the
Interf. Comm. Code field.
By default, the CATREF is reduced to 20 characters during the transfer.

SmartPlant Materials PDMS Interface User's Guide 27


Ident Transfer

PDMS Groups
Define a rule for the PDMS ident transfer. Enter at least one group code. This rule transfers all
idents that 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.
Define a rule on 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.

28 SmartPlant Materials PDMS Interface User's Guide


Ident Transfer

PDMS Configurations
Use the PDMS 30.01 Configure PDMS screen to configure the origin and/or the defaults of the
data for the PDMS transfer on PDMS 20.01.
These settings are project- or product group-specific. Product group settings affect only the
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), and
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 the RTEXT, STEXT, and TTEXT attributes. The text of the
isometric is distributed on the parts list at construction. The SKEY attribute of the detail text
selects the corresponding symbol in ISOGEN.
The material text name is typed in the specification and the catalog and describes the material
of the component. The text is stored in the XTEXT, YTEXT, and ZTEXT attributes. The text of
the isometric is distributed on the parts list at construction.

Definition for Bolts


Enter the defined rule (PDMS 20.04) for the bolts.
This rule contains all single bolts.

SmartPlant Materials PDMS Interface User's Guide 29


Ident Transfer

Suffixes and Fix Values


 GMREF Suffix - Default suffix for the GMREF (geometry set reference to a 3D geomset)
GMREF is a reference indicator to a 3D 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 - 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 are used for construction to positioning
and orientation, and to verify the connection of the elements. P-Points are also required by
the construction of the 3D geomset in PARAGON.
 DTREF Suffix - 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.
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 specific to the project.

Attributes for Flange Bolt Points


Enter the attributes for the bolt diameter, number of bolts, flange thickness, an additional
attribute for flange thickness, and the bolt type.

Settings for Specon Files


You can set the Catref to the ident code in the Specon files for the elbolets and weldolets. For
this purpose, use the Rule for Elbolets & Weldolets field in the Spec Transfer block at the
bottom of the screen. Select a rule defined on PDMS 20.04 PDMS Groups from the LOV in this
field to identify the elbolets and weldolets. If the rule for elbolets and weldolets is specified here,
the components (idents) identified as elbolets and weldolets by this rule will be set in the Specon
file.
If the Append to Catref? check box is selected, the translated values of PBORs from S.40.01
Nominal Sizes Window 2 will be appended to the Catref.

30 SmartPlant Materials PDMS Interface User's Guide


Ident Transfer

The translated values are defined in the Dn Translation field on S.40.01 Window 2.

Geometric and Attributes for Insulation


In the Geometric for Insulation field, enter the geometry table that contains information about
the insulation.
Enter attributes in the DN from, DN to, Temp from, Temp to, and Thickness fields.

G-Type Attribute Mapping


The PDMS 30.02 screen is used to configure the origin of the attribute data for the PDMS
transfer on PDMS 20.01 for the several GTypes.
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

SmartPlant Materials PDMS Interface User's Guide 31


Ident Transfer

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).
The needed parameter list can vary from G-type to G-type. The parameter positions (Parameter
Seq) can have another meaning within different G-types.

32 SmartPlant Materials PDMS Interface User's Guide


Ident Transfer

GType FILT

SmartPlant Materials PDMS Interface User's Guide 33


Ident Transfer

GType CROS

Type Geometric
For all geometry attributes that will be used, you must have a translation for the PDMS interface
on A.50.I.02 Interface Attributes.
For the attributes such as 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
(Unit field ). If you have entered an interface dependent unit (A.10.14), then the interface unit is
used as the 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, PDMS knows that
you are working with the metric unit mm (millimeter).

34 SmartPlant Materials PDMS Interface User's Guide


Ident Transfer

Type Commodity Code


If you use the Type ‘Commodity Code’, you can enter a tablename, which is from Type
‘COMMATTR’ (or a table link) and exists as a detail in the commodity rule.

SmartPlant Materials PDMS Interface User's Guide 35


Ident Transfer

With the selection in the Value defined in field on PDMS 30.02, you define 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
|| 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

36 SmartPlant Materials PDMS Interface User's Guide


Ident Transfer

||
|| 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;

PDMS Files for Ident Transfer


Enter the job code, short description, and description (optional) in the corresponding fields at the
top of this screen.
The File Options group allows you to define the kind of PDMS files you want to create,
explained at the beginning of this document.

SmartPlant Materials PDMS Interface User's Guide 37


Ident Transfer

Enter the export path for the PDMS files in the Export Path field, and enter the export file name
in the Export File field.
The Project Filter field specifies how the idents are filtered according to the project or product
group: only idents from the logged in project or also from the attached product group.
The Spec Filter field specifies how to filter the idents against specifications. The purpose of this
setting is to reduce the amount of output data.
Use the Restrictions button or the next block arrow to insert the predefined rules for this PDMS
job.

Enter your predefined rules (PDMS 20.04 PDMS Groups). You do not need to enter the rules
for the bolts, which are only defined for the PDMS 30.01 Configure PDMS screen.
Click the Create File button to start the PDMS ident transfer. A message appears to inform you
about the SQL Plus version. This information about the DBA setting is useful if there is a
problem in the 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.

38 SmartPlant Materials PDMS Interface User's Guide


SECTION 4

Specification Transfer
Create a standard Specon file or an Insulation Spec (PDMS 10.02 Create PDMS Spec-File
screen).
In addition to the Specon file, you can create various files on the PDMS 20.01 Create PDMS
Files screen. The files are: PDMS_D.DAT, PDMS_C.DAT, PDMS_B.DAT, PDMS_BS.DAT, and
PDMS_M.DAT. For more information, see Ident Transfer (on page 13).
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 check box on 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 in the Spec Code field to open PDMS 10.03 Show Log Entries to view the job
marked as the delta job. After the spec transfer finishes, the actual job will become a delta job.
Generally, delta creation depends on the setting of the 'Spec Rev Delta Handling' item. If it is set
to 'Autonomous' and the spec transfer has finished, the delta indicator of all jobs of the same
spec revision (except the actual one) is cleared, but the delta indicator of other revisions is left. If
a new job is started afterwards (in another revision) and it will 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. Revisions are
autonomous related to another (multiple delta indicators are allowed per spec, one per each
revision).
If 'Spec Rev Delta Handling' is set to 'Merge', and the spec transfer has finished, the delta
indicator of all jobs of the same spec (code, type, project) is cleared (except the actual one). If a
new job is started afterwards (in another revision) and it will 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.
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
will be updated as soon as 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 can check Reset to let the update-file contain all current lines, not only those that changed.
The Copy option tells the transfer to read the SmartPlant Materials spec or copy the result set of
a job that is marked as 'Master' on PDMS 10.03. If you choose Copy, the contents of the actual
SmartPlant Materials spec do not play any role.

SmartPlant Materials PDMS Interface User's Guide 39


Specification Transfer

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. They are set by a CIP
m_pck_pdms_custom.prep_output_heading(p_log_id).
If several definitions of Header Format and Default Format exist, the section shown below is
repeated with different values.
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

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
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

40 SmartPlant Materials PDMS Interface User's Guide


Specification Transfer

Attributes for Spec Transfer


On this screen, all attributes needed by the PDMS interface must be defined.

You must not enter the attributes TYPE and NAME, because these are always part
of the header and also always come at the beginning. Here only those attributes are defined that
you need in addition.
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 on A.50.I.02 for ‘PDMS’ interface with the
translation ‘BDIA’

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

CMPPREF ‘/’ and Ident

DETAIL '/' and Ident

PBOR0 Nominal Size

SmartPlant Materials PDMS Interface User's Guide 41


Specification Transfer

PBOR1 Nominal Size

PBOR2 Nominal Size

PBOR3 Nominal Size

PBOR4 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 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 on
A.50.I.02 for ‘PDMS’ interface translated as ‘LGTO’

MATXT default is return value of M_PCK_PDMS_CUSTOM.S2008

TEMP_ Output1 in the Geometric Table for Insulation


FROM

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

42 SmartPlant Materials PDMS Interface User's Guide


Specification Transfer

Attribute Translation for PDMS


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

SmartPlant Materials PDMS Interface User's Guide 43


Specification Transfer

Tables for PDMS


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

You need at least one table for the PDMS header, SHOP, STYP, BTYP, ANGLE, GTYPE, and
RADIUS.
It is important that the name of the table be PDMS_HEADER_XY , where XY is a combination of
numbers.

Importing GTYPE Data


You can import the default data for the GTYPE table. SmartPlant Materials displays the default
data, which you can add, modify, and delete.
In the Import Type field, use the LOV to insert PDMS_GTYPE. In the Table Type Description
field, enter an existing table type description, and in the Table Type field, select INTERFACE.

44 SmartPlant Materials PDMS Interface User's Guide


Specification Transfer

In the Table Name field, enter the table name, which was defined in the previous step, for the
table GTYPE.

Enter an existing table group (S.20.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.

Table Translation for PDMS


You need a translation for the following tables:

Table name Translation for PDMS interface

GTYPE (freeformat) GTYPE

SHOP (freeformat) SHOP

STYP (freeformat) STYP

BTYP (freeformat) BTYP

ANGLE (freeformat) ANGLE

RADIUS (freeformat) RADIUS

Material tables MATXTxy

SmartPlant Materials PDMS Interface User's Guide 45


Specification Transfer

It is important that the translation of the material table be MATXTxy , where xy is a combination
of free format characters.

46 SmartPlant Materials PDMS Interface User's Guide


Specification Transfer

Table Attributes
Here you can define the attributes from which the description of a PDMS file is composed.

You must at least enter the table attributes for PDMS_HEADER_XY.

Assigning Bolts to Specification Parts


For the specification transfer, you must assign the bolt commodity codes to the specification line
item ident. SmartPlant Materials needs this information for the bolt heading section in the PDMS
spec file.

SmartPlant Materials PDMS Interface User's Guide 47


Specification Transfer

Enter the accompanying commodity code of the bolts in the Bolt Commodity Code field. You
can use this commodity code in your CIP to build the bolt references in the spec file. The
internal column name in the table m_spec_items is bolt_commodity_id.

48 SmartPlant Materials PDMS Interface User's Guide


Specification Transfer

PDMS CATREFs Defined per Commodity Code


The following screen shows how the SmartPlant Materials commodity codes are assigned to the
PDMS CATREFs.

In this case, the catalog reference for PDMS is D31CG5WHM1TB000 and specifically for the
commodity code "D31CG5WHM1TB000" given above. Use the LOV in the Interface field in
the Interface Codes block to select ‘PDMS’ from the list. Then enter the PDMS specific code in
the Interf. Comm. Code field.
By default, the CATREF is reduced to 20 characters during the transfer.

SmartPlant Materials PDMS Interface User's Guide 49


Specification Transfer

Assignment of Interface Details to Parts


Assign the related details to the part for the table names.

Short Code – Gtype Mapping


Select the SmartPlant Materials short codes. Changing or deleting is not possible here.
SmartPlant Materials short codes are defined on the S.10.08 screen if one is missing.

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

50 SmartPlant Materials PDMS Interface User's Guide


Specification Transfer

In the GType field, enter a Gtype. The entry is checked against the S.20.I.03 tablename for
Gtypes (Translation = GYTPE). If a Gtype is missing, it must be entered on S.20.I.03. An LOV is
available and contains all valid Gtypes from S.20.I.03.
During the transfer, the Gtype is reduced to 4 characters.
In the GType Config field, select a pre-defined GType configuration from the LOV.
With the PBORx check boxes, you can define at which places the nominal sizes should be
stored in the spec file.
You can order the PBOR values in the Specon file such that the larger bore value comes first
and then the smaller bore. For this purpose, the Order PBORs check box must be selected. If
this check box is selected, the PBORs are ordered from larger bore to smaller bore for the
selected GType.

Post Processing
The PDMS 10.04 Create Procedures and PDMS 10.05 Spec Type Procedure Relations
screens allow for the definition of post processing procedures for the PDMS interface.
On the PDMS 10.04 Create Procedures screen, you can define and maintain procedures.

Enter the name of the procedure in the Procedure field. Then define the procedure in
the Procedure Body field. Click the Check button to validate the syntax of the procedure.
Validation is also done automatically for each record when scrolling through this block. The
validation result is always displayed in the Check Result field. Click the Execute button to
execute the selected procedure immediately. The Standard check box indicates a standard
procedure delivered with the software.
On the PDMS 10.05 Spec-Type-Procedure Relations screen, you can link the procedures to
the spec type and run them automatically after the Specon file is generated.

SmartPlant Materials PDMS Interface User's Guide 51


Specification Transfer

Select the spec type in the first (S.50.02 Specification Types) block. Then assign the
procedures to the selected spec type in the second (Spec-Type-Procedures) block. Enter a
sequence number in the Seq field; this number controls the order of the procedure execution.
Select the procedure from the LOV in the Procedure field. The Project/PG field is filled
automatically with the login project/product group.

GType Configurations
The architecture of the PDMS attributes is flexible enough that a new attribute can be added
without any restriction of having the attribute as a physical column in the table
M_PDMS_SPEC_IDENTS. A provision for the addition of 40 attributes has been provided.
A.50.03 attribute mappings are no longer considered during the export of the Specon file.
The PDMS 10.06 GType Configurations screen is used to store GType configurations and
GType configuration details.

This screen allows flexible attribute handling. On this screen, you can map the attribute to the
physical attribute of table M_PDMS_SPEC_IDENTS. There is a provision for 40 attribute
mappings. You can specify the default value for an attribute.
You can control which attribute is to be written to the file by selecting the Header Column?
check box.
You can also control whether to prefix the attribute value with Specon the word TEXT by
selecting the appropriate option from the drop-down list in the Prefix Text? field. The following
options are available:
 Always - TEXT is always prefixed to the attribute value.
 Alpha Numeric - TEXT is prefixed only when the attribute value is alphanumeric.
 Never - TEXT is not prefixed.
You can specify a default value for the attribute in the Default Value field in the Gtype Config
Details block of PDMS 10.06. The DEFAULTS section of the Specon file will consider the
values specified in this field.
This configuration can then be linked to the GType on the PDMS 10.01 Short Code-GType
Mappings screen. The GType will be exported as per the GType Config linked.

52 SmartPlant Materials PDMS Interface User's Guide


Specification Transfer

Copy Product Group Details


You can modify product group GType configuration details in a project. Using the Copy product
group details button, you can copy the GType configuration details from the product group to
the current (login) project.
The Copy product group details button is only enabled for GType configurations created in the
product group. When you are logged in to a project, the GType configuration details of this
project are displayed. The details of the product group are only displayed if there are no details
with the current PROJ_ID. The button is not available in the product group.
When you click the button, the GType configuration details are copied to the project, and the
button label changes to Use product group details.

Clicking the Use product group details button displays a message that the current project
configuration details will be deleted and replaced by the product group details.

Click Yes to continue. The button label changes back to Copy product group details.

SmartPlant Materials PDMS Interface User's Guide 53


Specification Transfer

PDMS File for Spec Transfer


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

The Missing CATEREFs and Missing GTypes buttons allow you to search for missing
information. You can click them before or after the transfer has finished. For more information,
see Missing CATREFs (on page 59) and Missing GTypes (on page 60).
You can specify the order-by criteria within the GTypes using the Sort Order in GTypes button.
Click this button to open a new window where you can specify the order preferences of the
attribute codes used in GType configurations. The contents of the generated Specon file will be
ordered according to these preferences. The order preferences are project dependent.
After querying on this screen, all pipe classes of the project appear. You can use the Spec Type
field to filter the specifications based on the selected specification types.
Using the Display Options group, you can filter the displayed specs based on their revision and
whether they are issued or not. Select All to display all specs regardless of their revision and
issue status; select Highest Rev. Issued or not to display only the highest revision of a spec
regardless of whether they are issued or not; select Not Issued and Highest Rev to display
only the specs that are not issued and that have the highest revision number.
If the default ZI_PDMS_IS is set to Y, the not issued specifications do not appear on
PDMS 10.02.
You can click the left Select All button to mark the Sel check box of all displayed specifications.
Click the left Deselect All button to cancel the current selection.

54 SmartPlant Materials PDMS Interface User's Guide


Specification Transfer

You can click the right Select All button to mark the Delta check box of all displayed
specifications. Click the right Deselect All button to cancel the current selection.
The two check boxes on the left side indicate whether or not all necessary mapping work has
been done for the pipe class in each case.
 CR - A Catalog Reference in S.30.I.01 was assigned (definition PDMS-CATREF per
SmartPlant Materials commodity code) to all commodity codes of the pipe class
 GT - A GType in PDMS 10.01 was assigned (mapping of GTypes, header, details with
SmartPlant Materials short codes and option codes) to all short codes of the pipe class.
With the PBOR translation feature, the PBORs can be translated from either IN to MM or MM to
IN when creating PDMS spec files. If the value of the dropdown list in the PBOR Translation
field is set to ‘IN to MM,' the PBORs will be translated from IN to MM for a specification being
transferred to PDMS. If PBOR Translation is set to ‘MM to IN,' the PBORs will be translated
from MM to IN.
The PBOR translation is considered only if UOM is not turned on.
Before you can start the transfer, you must select at least one specification by selecting the Sel
indicator and entering a path in the Export Path field (manual input, via LOV, or Save button).
If the Run CIP indicator next to the Transfer selected Specs button is selected, the custom
procedure M_PCK_PDMSEXP_CUSTOM.PUBLISH will be executed after the transfer job
finishes successfully.
When you click the Transfer selected Specs button, a message appears. Click Yes to start the
transfer.

Several job information messages appear in the status line:


 Creating temporary data
 Transfer in progress
 Creation of Specfile completed
After the ‘Creation of Specfile completed’ message appears, the transfer is finished.
After the transfer has been concluded, the following files will be created:

File Type of file Location

PDMS_OUTPUT_xxxxx.log logfile UTL file directory


This logfile can be deleted
with the Del Log button.

insxxxx.spec specfile defined path in Export Path field

SmartPlant Materials PDMS Interface User's Guide 55


Specification Transfer

When the creation of the spec file is completed, the following message appears.

Click Yes to generate the component files. The PDMS 20.01 Create PDMS Files screen opens.
Specify the job information (except project filter and spec filter) on PDMS 20.01, and then click
the Create File button to create the component files. The content of the component files is
driven by the idents of the specifications selected on the PDMS 10.02 Create PDMS Spec-File
screen.
Both the spec files and the component files are downloaded into a single zip file.
When the component file generation is done, the following message appears.

Click OK to continue. Next you can decide to download the created files.

Click Yes to download the files or No to end the job. Then close PDMS 20.01 to go back to
PDMS 10.02.

56 SmartPlant Materials PDMS Interface User's Guide


Specification Transfer

When the transfer is completed, you can double-click in the Spec Code field to open the PDMS
10.03 Show Log Entries screen.

In the first (Specification Headers) block, the selected specification is displayed with revision
and descriptions.
In the second block, the revisions of the transfer jobs for the selected specification are displayed
depending on the setting of the Display Revisions group. The jobs are shown with the job
number, revision, and date and time when it was executed. If the Master check box is checked,
you can use this job as a master for the next transfer run. Select the Delta check box to use the
job's result to compare with the next transfer result. The Action field shows the action of the
transfer job. The available options are listed below.
 First creating - The first time when creating a transfer file for this specification.
 New - A new spec file regardless of any delta logic.
 Update from previous inserted - A job including delta management.
The number of records written to the NEW file is shown in the New field. The number of records
written to the INSERT file is shown in the Insert field. The number of modified lines is shown in
the Modified field. The number of records written to the DELETE file is shown in the Deleted
field. When this job has created an insulation spec file, the Insu indicator is checked. The Reset
check box is used for delta management. If the Master Job field is filled with a job number, the
actual job result was copied from the result of this job. If the Delta Job field is filled with a job
number, the actual job result was compared to the result of this job number.

SmartPlant Materials PDMS Interface User's Guide 57


Specification Transfer

Click the Next Block button to open Window 2 with the data of the selected job.

The GType Config data corresponding to the job are shown in the second (GType Configs)
block. For each GType the specification item idents data is shown in the third (PDMS Spec Item
Idents) block.
While generating a Specon file from the PDMS 10.02 Create PDMS Spec-File screen,
when two PBORs (for example, PBOR0 and PBOR1) are checked and there is no value
specified for the INPUT_2 of the corresponding specification, the INPUT_1 value is considered
as the value for INPUT_2 also.
If the project default ZI_PDMS_SN is set to Y, the Add, Delete, Modify, and New specification
files are merged into a single specification file. The merged specification file name is prefixed
with ‘mer’. The contents of the merge file are structured as follows:
$* Piping specification File for all items
<< new specs >>
$*
$* Piping specification File for additionally inserted items
$* ----------------------------------------------------------
<< inserted specs >>
$*
$* Piping specification File for modified items
$* ----------------------------------------------------------
<< modified specs >>
$*
$* Piping specification File for deleted items
$* ----------------------------------------------------------
<< deleted specs >>

58 SmartPlant Materials PDMS Interface User's Guide


Specification Transfer

You can link a specification to others. Right-click in the Spec Code field to open the pop-up
menu.

Select the Spec Links option to open a new window where you can link other specifications to
the selected specification.

Missing CATREFs
Click the Missing CATREFS button. A new window opens, displaying a list of all the commodity
codes for the pipe class to which no catalog references have been assigned yet.

You can enter the missing catalog references when you click the Maintain CATREFs in
S.30.I.01 button. Click the Back button to close this window.

SmartPlant Materials PDMS Interface User's Guide 59


Specification Transfer

Missing GTypes
Click the Missing Gtypes button. A new window opens, displaying a list of all the short codes of
the pipe classes to which no GType has been assigned.

You can enter the missing GTypes when you click the Maintain missing GTypes button. Click
the Back button to close this window.

60 SmartPlant Materials PDMS Interface User's Guide


SECTION 5

Loading SmartPlant Materials Files into


PDMS (User Guide)
This section explains how to import data from SmartPlant Materials into PDMS.

Installing the PDMS Interface Software


Follow these steps:
1. Copy the cpsimportmarian directory from the installation media to the %PMLLIB% directory.
2. Run PDMS (any module) and use the PML REHASH ALL command.

Creating Standards for COCO table, GMSE, PTSE,


DTSE
Piping components use the standard COCO table, GMSE, PTSE, and DTSE, created as follows:
1. Run PARAGON.
2. Run the SmartPlant Materials-COCO.mac macro using the following command:

SmartPlant Materials PDMS Interface User's Guide 61


Loading SmartPlant Materials Files into PDMS (User Guide)

$M %PMLLIB%\cpsimportmarian\MARIAN-COCO.mac

3. Run the SmartPlant Materials-CATA.mac macro using the following command:


$M %PMLLIB%\cpsimportmarian\MARIAN-CATA.mac

If the command runs successfully, the following information appears:

62 SmartPlant Materials PDMS Interface User's Guide


Loading SmartPlant Materials Files into PDMS (User Guide)

Creating UDA Attributes


The PDMS interface software uses the following UDA attributes :IDENT1, :IDENT2, :IDENT3,
:IDENT4, :IDENT5, created as follows:
1. Run LEXICON.
2. Run the MARIAN-UDA macro using the following command:
$M %PMLLIB%\cpsimportmarian\MARIAN-UDA.mac

Creating a Catalog in PARAGON Module


The catalog is created from files exported from SmartPlant Materials, as follows:
1. Run PARAGON.
2. Run the program for creating the catalog using the command:
$M %PMLLIB%\cpsimportmarian\cpsimportcata.mac

SmartPlant Materials PDMS Interface User's Guide 63


Loading SmartPlant Materials Files into PDMS (User Guide)

3. On the Import dialog box, enter information as needed.

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.
4. Click Select file. The following dialog box appears:

64 SmartPlant Materials PDMS Interface User's Guide


Loading SmartPlant Materials Files into PDMS (User Guide)

5. Select the type of file and its directory location, and then click OK.
6. On the Import dialog box, click Import.
The files are imported in the following order:
 *_M.DAT - Material text
 *_D.DAT - Detail text
 *_B.DAT - Bolt diameter table
 *_BS.DAT - Standard bolts elements

SmartPlant Materials PDMS Interface User's Guide 65


Loading SmartPlant Materials Files into PDMS (User Guide)

 *_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.

Creating Component Data


Component data is created from the *_C.DAT file. Follow these steps:
1. Run the PROPCON module.
2. Run the program for creating the catalog using the following command:
$M %PMLLIB%\cpsimportmarian\cpsimportcmpd.mac

66 SmartPlant Materials PDMS Interface User's Guide


Loading SmartPlant Materials Files into PDMS (User Guide)

3. On the Import dialog box, enter information as needed.

Follow the same steps as described in Creating a Catalog in PARAGON Module (on page
63).

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

SmartPlant Materials PDMS Interface User's Guide 67


Loading SmartPlant Materials Files into PDMS (User Guide)

Example

68 SmartPlant Materials PDMS Interface User's Guide


APPENDIX A

Appendix: File Examples


In This Appendix
Specon File .................................................................................... 69
Specon Delta Files ......................................................................... 72
Spec Insulation File ....................................................................... 74
PDMS_B.DAT ................................................................................ 74
PDMS_BS.DAT ............................................................................. 75
PDMS_C.DAT ................................................................................ 77
PDMS_D.DAT ................................................................................ 79
PDMS_F.DAT ................................................................................ 80
PDMS_G.DAT ............................................................................... 82
PDMS_M.DAT ............................................................................... 83

Specon File
$* Piping specification File for all items
$* Created by SmartPlant Materials 2011 (7.0.1) SP 1 - Copyright 1988 - 2010,
Intergraph Corporation
$* SPMat - PDMS SPECS INTERFACE - SPEC CREATING DATE : 13-JAN-10
$* on 13-01-2010 at 15:23 $*
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

SmartPlant Materials PDMS Interface User's Guide 69


Appendix: File Examples

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

70 SmartPlant Materials PDMS Interface User's Guide


Appendix: File Examples

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

SmartPlant Materials PDMS Interface User's Guide 71


Appendix: File Examples

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

Specon 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'

72 SmartPlant Materials PDMS Interface User's Guide


Appendix: File Examples

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 example, 15858200-D replaces /6497796-D in case A.

D. Removing a Component
Reference is made to cases A, B, and C, which are supposed to be loaded before D.

FILE NAME: e.g. delete_b511_12345.spec

OLD SPECIFICATION /B511

REMOVE */AAFSBF0DD
REMOVE */AAFSBF0EE
REMOVE */AAFSBF0FF

SmartPlant Materials PDMS Interface User's Guide 73


Appendix: File Examples

This format is necessary to remove components that are no longer needed from the spec. 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 SmartPlant Materials 2011 (7.0.1) SP 1 - Copyright 1988 - 2010,
Intergraph Corporation
$* SPMat - PDMS SPECS INTERFACE - SPEC CREATING DATE : 13-JAN-10
$* on 13-01-2010 at 15:23 $*
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#
$*-- Created by SmartPlant Materials 2011 (7.0.1) SP 1 - Copyright 1988 -
2010, Intergraph Corporation
$*--License-No.
32CB-13A481-C06A6B85AEF077C327FE95D9CA5364-1CADF-25073CE-0-0
$*-- ******************
$*-- * *
$*-- ******************
$*--
$*--
$*--
$*--

74 SmartPlant Materials PDMS Interface User's Guide


Appendix: File Examples

$*-- 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#
$*-- Created by SmartPlant Materials 2011 (7.0.1) SP 1 - Copyright 1988 -
2010, Intergraph Corporation
$*--License-No.
32CB-13A481-C06A6B85AEF077C327FE95D9CA5364-1CADF-25073CE-0-0
$*-- ******************
$*-- * *
$*-- ******************
$*--
$*--
$*--
$*--
$*-- 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----------------

SmartPlant Materials PDMS Interface User's Guide 75


Appendix: File Examples

$*-- -------------------------------------------------------
$*--

$*-- **** 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

76 SmartPlant Materials PDMS Interface User's Guide


Appendix: File Examples

PDMS_C.DAT
$*#PDMS Interface - SingleBolt#
$*-- Created by SmartPlant Materials 2011 (7.0.1) SP 1 - Copyright 1988 -
2010, Intergraph Corporation
$*--License-No.
32CB-13A481-C06A6B85AEF077C327FE95D9CA5364-1CADF-25073CE-0-0
$*-- ******************
$*-- * *
$*-- ******************
$*--
$*--
$*--
$*--
$*-- 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

SmartPlant Materials PDMS Interface User's Guide 77


Appendix: File Examples

<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 4PDMS_C.DAT

$*#PDMS Interface - CmpData#


$*-- Created by SmartPlant Materials 2011 (7.0.1) SP 1 - Copyright 1988 -
2010, Intergraph Corporation
$*--License-No.
32CB-13A481-C06A6B85AEF077C327FE95D9CA5364-1CADF-25073CE-0-0
$*-- ******************
$*-- * *
$*-- ******************
$*--
$*--
$*--
$*--
$*-- 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

78 SmartPlant Materials PDMS Interface User's Guide


Appendix: File Examples

<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#
$*-- Created by SmartPlant Materials 2011 (7.0.1) SP 1 - Copyright 1988 -
2010, Intergraph Corporation
$*--License-No.
32CB-13A481-C06A6B85AEF077C327FE95D9CA5364-1CADF-25073CE-0-0
$*-- ******************
$*-- * *
$*-- ******************
$*--
$*--
$*--
$*--
$*-- 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

SmartPlant Materials PDMS Interface User's Guide 79


Appendix: File Examples

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#
$*-- Created by SmartPlant Materials 2011 (7.0.1) SP 1 - Copyright 1988 -
2010, Intergraph Corporation
$*--License-No.
32CB-13A481-C06A6B85AEF077C327FE95D9CA5364-1CADF-25073CE-0-0
$*-- ******************
$*-- * *
$*-- ******************
$*--
$*--
$*--
$*--
$*-- 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. **************

80 SmartPlant Materials PDMS Interface User's Guide


Appendix: File Examples

<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

SmartPlant Materials PDMS Interface User's Guide 81


Appendix: File Examples

STUD
PARAM 12

PDMS_G.DAT
$*#PDMS Interface - Catref#
$*-- Created by SmartPlant Materials 2011 (7.0.1) SP 1 - Copyright 1988 -
2010, Intergraph Corporation $*--License-No.
32CB-13A481-C06A6B85AEF077C327FE95D9CA5364-1CADF-25073CE-0-0
$*-- ******************
$*-- * *
$*-- ******************
$*--
$*--
$*--
$*--
$*-- 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

82 SmartPlant Materials PDMS Interface User's Guide


Appendix: File Examples

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
1. $*#PDMS Interface - Detail#
$*-- Created by SmartPlant Materials 2011 (7.0.1) SP 1 - Copyright 1988 -
2010, Intergraph Corporation
$*--License-No.
32CB-13A481-C06A6B85AEF077C327FE95D9CA5364-1CADF-25073CE-0-0
$*-- ******************
$*-- * *
$*-- ******************
$*--
$*--
$*--
$*--
$*-- 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. **************

SmartPlant Materials PDMS Interface User's Guide 83


Appendix: File Examples

<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

84 SmartPlant Materials PDMS Interface User's Guide


APPENDIX B

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,

SmartPlant Materials PDMS Interface User's Guide 85


Appendix: CIPs

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.

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

86 SmartPlant Materials PDMS Interface User's Guide


Appendix: CIPs

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

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);

SmartPlant Materials PDMS Interface User's Guide 87


Appendix: CIPs

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.

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,

88 SmartPlant Materials PDMS Interface User's Guide


Appendix: CIPs

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;
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,

SmartPlant Materials PDMS Interface User's Guide 89


Appendix: CIPs

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.

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.

90 SmartPlant Materials PDMS Interface User's Guide


Index

A G
A. Creating a New Specification • 72 Geometrics (PDMS_G.DAT) • 15
Appendix G-Type Attribute Mapping • 31
CIPs • 85 GType Configurations • 52
File Examples • 69
Assigning Bolts to Specification Parts • 47 I
Assignment of Interface Details to Parts •
26, 50 Ident Transfer • 13
Attribute Translation for PDMS • 21, 43 Ident Transfer Files • 13
Attributes for Ident Transfer • 20 Importing GTYPE and SKEY Data • 24
Attributes for Spec Transfer • 41 Importing GTYPE Data • 44
Installing the PDMS Interface Software • 61
Introduction • 9
B
B. Creating a New Component in an L
Existing Specification • 72
Bolt Length (PDMS_B.DAT) • 18 Loading SmartPlant Materials Files into
PDMS (User Guide) • 61
C
M
C. Modifying a Component in a
Specification • 73 Material (PDMS_M.DAT) • 19
Component Data (PDMS_C.DAT) • 14 Missing CATREFs • 59
Configuration • 11 Missing GTypes • 60
Copy Product Group Details • 53
Creating a Catalog in PARAGON Module • P
63 PDMS CATREFs Defined per Commodity
Creating Component Data • 66 Code • 27, 49
Creating Specifications • 67 PDMS Configurations • 29
Creating Standards for COCO table, PDMS File for Spec Transfer • 54
GMSE, PTSE, DTSE • 61 PDMS Files for Ident Transfer • 37
Creating UDA Attributes • 63 PDMS Groups • 28
PDMS Insulation File • 40
D PDMS Specon File • 40
D. Removing a Component • 73 PDMS_B.DAT • 74
DBA Settings • 11 PDMS_BS.DAT • 75
Definition of the PDMS Interface • 12 PDMS_C.DAT • 77
Detail Text (PDMS_D.DAT) • 13 PDMS_D.DAT • 79
PDMS_F.DAT • 80
PDMS_G.DAT • 82
E PDMS_M.DAT • 83
Example • 68 Post Processing • 51
Preface • 7
F Project Defaults • 11
Flange-Bolt-Points (PDMS_F.DAT) • 16
S
Short Code – Gtype Mapping • 50

SmartPlant Materials PDMS Interface User's Guide 91


Index

Single Bolt Idents (PDMS_BS.DAT) • 17


Spec Insulation File • 74
Specification Transfer • 39
Specon Delta Files • 72
Specon File • 69
SQL_PATH • 11

T
Table Attributes • 24, 47
Table Translation for PDMS • 22, 45
Tables for PDMS • 22, 44

92 SmartPlant Materials PDMS Interface User's Guide

You might also like