smartplant materials importing pds...

SmartPlant Materials Importing PDS Specifications

Version 2008 (6.3.1) June 2008 DMAR1-PE-200055F

Copyright Copyright © 2005-2008 Intergraph Corporation. All Rights Reserved.

Including software, file formats, and audiovisual displays; may be used pursuant to applicable software license agreement; contains confidential and proprietary information of Intergraph and/or third parties which is protected by copyright law, trade secret law, and international treaty, and may not be provided or otherwise made available without proper authorization.

Restricted Rights Legend Use, duplication, or disclosure by the government is subject to restrictions as set forth below. For civilian agencies: This was developed at private expense and is “restricted computer software” submitted with restricted rights in accordance with subparagraphs (a) through (d) of the Commercial Computer Software - Restricted Rights clause at 52.227-19 of the Federal Acquisition Regulations (“FAR”) and its successors, and is unpublished and all rights are reserved under the copyright laws of the United States. For units of the Department of Defense (“DoD”): This is “commercial computer software” as defined at DFARS 252.227-7014 and the rights of the Government are as specified at DFARS 227.7202-3. Unpublished – rights reserved under the copyright laws of the United States. Intergraph Corporation Huntsville, Alabama 35894-0001

Warranties and Liabilities All warranties given by Intergraph Corporation about equipment or software are set forth in your purchase contract, and nothing stated in, or implied by, this document or its contents shall be considered or deemed a modification or amendment of such warranties. Intergraph believes the information in this publication is accurate as of its publication date.

The information and the software discussed in this document are subject to change without notice and are subject to applicable technical product descriptions. Intergraph Corporation is not responsible for any error that may appear in this document.

The software discussed in this document is furnished under a license and may be used or copied only in accordance with the terms of this license.

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

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

Table of Contents

SmartPlant Materials Importing PDS Specifications 3

Table of Contents Overview .............................................................................................................................4

Extraction of PDS ASCII Files .........................................................................................5

Extraction of Piping Material Class Data .....................................................................7 Extraction of Piping Commodity Data .........................................................................9 Extraction of Tap Properties Data ..............................................................................11 Extraction of Table Checker Report ...........................................................................13 Extraction of Physical Data Library Tables ...............................................................17 Extraction of Piping Job Specification Tables ...........................................................18 Extraction of Standard Note Library Code Lists ........................................................19 Extraction of Short and Long Description Library .....................................................21 Physical Data Library Tables and PJS Tables List File ..............................................23 Table Checker Report List File ..................................................................................24

Commodity Code Rule Review .......................................................................................25

Defining Preparatory Data .............................................................................................30

Define Code List Attribute Data and Table Detail Data ............................................31 Commodity Rule Attributes .............................................................................................. 32 Interface Attributes ........................................................................................................... 44

Define Commodity Group and Part Data ...................................................................50 Define Model Code to Piping Commodity Type Translation ........................................... 50 Define Piping Commodity Type Code List Attribute Data .............................................. 52 Define Piping Commodity Type Table Detail Data .......................................................... 54

Define Zydex to Short Code to Piping Commodity Chars Translation Data .............57 Define Units Data .......................................................................................................60

Data Entry Using SmartPlant Materials Screen PDS 50.02 ........................................62

Code List and Table Detail Data ................................................................................62 Commodity Group and Part Data ...............................................................................64 Zydex to Short Code to Piping Commodity Chars Translation Data .........................66 Units Data ...................................................................................................................67

Configuring SmartPlant Materials for Specification Import ......................................69

Specification Import Process ..........................................................................................71

Index ..................................................................................................................................76

Overview

4 SmartPlant Materials Importing PDS Specifications

Overview This document defines all the inputs required for extracting ASCII files from PDS in order to parse them and store their data into SmartPlant Materials. This is needed in order to start the process of importing Specs into SmartPlant Materials. The document also describes the mechanism to define the preparatory data. The preparatory data is used to configure a new Product Group in order to maintain data integrity and consistency during importing of the Specs. The document also gives a brief listing of the steps that are carried out during programmatic configuration of the Product Group.

Section 2 describes broad steps for generating ASCII files from PDS. Section 3 gives a brief note of the Commodity Code Rule that is being used in SmartPlant Materials for PDS Spec Import. Section 4 defines the Preparatory data. Section 5 describes the mechanism of populating preparatory data into SmartPlant Materials tables. Section 6 describes the steps that need to be taken before initiating PDS Spec Import process in SmartPlant Materials. Section 7 briefly describes the steps that are carried out programmatically during PDS Spec import into SmartPlant Materials.

Note

• The configuration of the Product Group is done programmatically only once. Hence, the user should ensure the completeness of the preparatory data before initiating import of individual Specs into SmartPlant Materials.

Extraction of PDS ASCII Files


Extraction of PDS ASCII Files The inputs required by the Parser program of the PDS Spec Import Screen (Ref: PDS 50.01) in SmartPlant Materials are listed below:

1. Piping Material Class Data 2. Piping Commodity Data 3. Taps Properties Data 4. Table Checker Report 5. Physical Data Library Tables 6. Piping Job Specification Tables 7. Standard Note Library Code Lists

• Code List 145

• Code List 148

• Code List 180

• Code List 330

• Code List 332

• Code List 400

• Code List 499

• Code List 550

• Code List 575

• Code List 576

• Code List 578 8. Short and Long Description Library 9. Physical Data Library Tables and Piping Job Specification Tables (PJS) List file 10. Table Checker Report List file



Fig 1: PDS 5001 Spec Import

The following are the steps to be followed in PDS, in order to extract the ASCII files required by the Parser program:

• Select the PDS Project.

• Click Reference Data Manager.

The above two steps are common and should be followed for the next seven sections.

Please note that for generating reports from PDS (discussed in sections below), it is suggested to use the delivered spec_order.max file, which will govern the reporting criteria for Piping Job Specification Manager (PCD, PMC, taps data, etc.), while generating the report in case if the User has customized the spec_order.max file for their Project. However, the user may later revert to his /her original spec_order.max file once the extraction is over.

The user must also ensure that the below mentioned PDS environment variable, if it exists in the PDS.cmd file, should be commented prior to extraction of Piping Job Specification Tables.

#$ENV{'NO_TRUNCATE'}='YES';



Extraction of Piping Material Class Data Follow the steps below to extract the Piping Material Class Data:

• Click Piping Job Specification Manager.

• Click Piping Material Class Data.

• Click Report.

• Set toggle to Report On Approved Spec.

• Click Accept to arrive at the screen shown below.

Fig 2: Piping Material Class

• Enter the File Name, for example, “CLASSES.PMC”.

• Click Accept.



Fig 3: Sample Piping Material Class Data File

Note

• The parsing process supports Dynamic Sequence/Order for the attributes in the PMC file. The default Sequence may be as follows: “Sequence= 2 3 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 22 23”

However, the number of attributes and the Attribute Number in the PMC file are fixed.



Extraction of Piping Commodity Data Follow the steps below to extract Piping Commodity Data:


• Click Piping Commodity Data.

• Click Report.


• Click Accept.

• Select the Piping Material Class.

Fig 4: Piping Commodity Data

• Enter the File Name as the name of the Piping Material Class selected with file extension ‘PCD’. For example, if the Piping Material Class selected is 1C0031, then the name to be keyed in is “1C0031.PCD”.

• Click Accept.

Repeat the above process for each Piping Material Class.



Fig 5: Sample Piping Commodity Data File

Notes

• Ensure that the file name for Piping Commodity Data is “Piping Material Class name concatenated with .PCD“. For example, if the Piping Material Class is 1C0031, then we have the corresponding PCD file as 1C0031.PCD.

• The parsing process supports Dynamic Sequence/Order for the attributes in the PMC file. The default Sequence may be as follows: “Sequence= 3 4 6 7 8 9 10 11 12 13 14 15 16 17 18 5 19 22 21 25 23 24 26 27”




Extraction of Tap Properties Data Follow the steps below to extract the Tap Properties Data:


• Click Tap Properties Data.

• Click Report.



Fig 6: Tap Properties Data

• Enter the File Name, for example, “TAPS.DATA”.

• Click Accept.



Fig 7: Sample Taps Properties Data File

Note

• The parsing process supports Dynamic Sequence/Order for the attributes in the PMC file. The default Sequence may be as follows: “Sequence= 3 4 5 6 7 8”




Extraction of Table Checker Report To extract Table Checker Report, the user must:

1. Create Table Checker Report Format. 2. Create Discrimination Data. 3. Generate Table Checker Report.

Steps 2 and 3 are to be repeated for each Piping Material Class.

STEP 1: Follow the steps below in order to create the format for the table checker report:

• Click Table Checker.

• Click Report Format.

• Click Create to arrive at the screen shown below.

Fig 8: Table Checker Format Creation

• Enter the Number as tbl_chk_2.fmt.

• Enter the Description as Table Checker Report Format.

• Enter the File Specification as tbl_chk_2.fmt (Intergraph-delivered Format file).



• Click Accept.

• Click Exit Form.


STEP 2: Follow the steps below to create discrimination data for the table checker report:

• Click Report Discrimination Data.

• Click Create.

Fig 9: Table Checker Discrimination Data

• Enter the Number, Description, and File Specification as Piping Material Class (for example, 1C0031).

• Click Select Piping Material Class.

• Select the Piping Material Class.

• Click Accept.

• Set toggle to Approved Piping Job Spec.

• Click Accept.





STEP 3: Follow the steps below to generate the table checker report:

• Click Report.

• Click Create.

Fig 10: Table Checker Report Creation

• Enter the Report Number as Piping Material Class (for example, 1C0031).

• Enter the Report Title as TABLE CHECKER REPORT FOR <<Piping Material Class Name >> (for example, TABLE CHECKER REPORT FOR 1C0031).

• Enter the Report File Spec, for example, Piping Material Class Name concatenated with “_2.rpt” (1C0031_2.rpt).

• Select the Report Format File created in Step1. (In our case, it is tbl_chk_2.fmt.)

• Click Accept.

• Select the Report Discrimination Data same as Piping Material Class Name.

• Click Accept.



Fig 11: Sample Table checker Report

Notes

• SmartPlant Materials only supports the Table Checker Report Format Type 2.

• The Table Checker Report has to be extracted Spec-wise; for each Spec, the Report must be generated as a separate file.



Extraction of Physical Data Library Tables Follow the steps below to extract Physical Data Library Tables:

• Click Physical Data Library Manager.

• Select U.S. Practice.


Fig 12: Physical Data Library Manager

• Click Extract Data.

• Click Extract All.

• Click Accept.



Extraction of Piping Job Specification Tables Piping Job Specification Tables include all the tables referenced within the Piping Material Class file such as Diameter tables, Fluid Code Tables, Wall Thickness Tables, Branch Tables, Material Tables, Gasket Separation Tables, Pressure Temperature Tables, Bend Deflection Tables, and Pipe Length Tables.

Follow the steps below to extract Piping Job Specification Tables:

• Click Piping Job Specification Tables to arrive at the screen shown below.

Fig 13: Specification Tables

• Click Extract.

• Click Extract All.

• Click Accept.



Extraction of Standard Note Library Code Lists Follow the steps below to extract Standard Note Library Code Lists. In this section, Code List 148 has been taken as an example. The same process needs to be repeated for all the desired Code Lists.

• Click Standard Note Library to arrive at the screen shown below.

Fig 14: Standard Note Library

• Click Extract.

• Select Code List 148 Materials Description.

• Click Accept.



Fig 15: Sample CL148 Data File



Extraction of Short and Long Description Library Follow the steps below to extract Short and Long Description Libraries:

Short Description Library • Click Material Description Library Manager.

• Click Short Description Library.

• Click Report.

• Select File Type Commodity.

• Click Accept.

Fig 16: Short Description Library

• Enter the File Name, for example, “SHBOM.RPT”.

• Click Accept.

• Set toggle to Approved Library.

• Click Accept.



Long Description Library • Click Material Description Library Manager.

• Click Long Description Library.

• Click Report.

Fig 17: Long Description Library

• Enter the File Name, for example, “LGBOM.RPT”.

• Click Accept.

• Set toggle to Approved Library.

• Click Accept.



Physical Data Library Tables and PJS Tables List File

Once all the Piping Job Specification files and the Physical Data Library Tables are extracted, the map between the extracted name and the original name is listed in the file as “PD_tbl_list”.

Fig 18: Sample “PD_tbl_list” Data File

Note

• The Parser routine of PDS Spec Import requires the PD_Tbl_list file in a format as mentioned above. It is generated automatically when the PJS and Physical Data Library files are extracted in the above said format provided that the User has commented the PDS environment variable #$ENV{'NO_TRUNCATE'}='YES'; if existing in the PDS.cmd file, prior to extraction of Piping Job Specification Tables. The user must ensure that the generated “PD_tbl_list” file is also located in the common file folder where all the other extracted files reside.



Table Checker Report List File All the table checker report file names should be manually listed in a file, for example, “Table Checker Report List.txt”. This file is not generated from PDS.

Fig 19: Sample “Table Checker Report List.txt” Data File

Note

• The user must ensure that all the ASCII files (PDS-generated and manually created ones) are placed in a common folder.

Commodity Code Rule Review


Commodity Code Rule Review Commodity codes in SmartPlant Materials are created according to user-definable rules. They generate a short description that is used in Piping Classes, Bills of Materials, and requisitions, and a long description that is used for Purchasing. The default delivered commodity code structure does not contain any geometric (dimensional) data such as Nominal Pipe Size, Schedule, or Wall Thickness.

The benefit of not including geometric detail is that fewer commodity codes need to be created and maintained. In addition, SmartPlant Materials will generate unique idents for each size and schedule combination that the commodity code has.

Commodity Code Rule Used for PDS Spec Import

Plain Piping and Nipples

1st character "P"

1-3 Piping Commodity Type

4-5 Pressure Rating

6-7 End Preparation

8-9 Surface Preparation or Lining Material

10-12 Geometric Industry Standard or Manufacturer

13-15 Materials Industry Standard and Grade

16-17 Manufacturing Method

18-19 Nipple Length or Purchase Length

20-21 Geometric Industry Practice

Tubing and Hose

1st character "T"


4-5 Pressure Rating

6-7 End Preparation






16-17 Tubing and Hose Requisition Classification


Valves

1st character "V"


4-5 Pressure Rating

6-7 End Preparation

8-9 Valve Trim

10-12 Valve Manufacturer and Model Number or Geometric Industry Standard


16-17 Valve Requisition Classification

18-19 Lining Material


Miscellane-ous Fittings

1st character "M"


4-5 Pressure Rating

6-7 End Preparation




16-17 Miscellaneous Fitting Requisition Classification




Flanges

1st character "F"


4-5 Pressure Rating

6-7 End Preparation

8-9 Flange Face Surface Finish



16-17 Flange Requisition Classification


Gaskets

1st character "G"

1-2 Gasket Type

3-4 Pressure Rating

5-6 Gasket Thickness

7-9 Gasket Industry Standard



Bolts

1st character "B"

1-2 Bolt Type

3-5 Bolting Geometric Industry Standard or Manufacturer

6-8 Bolting Materials Industry Standard and Grade

9-10 Bolt Coating




Nuts

1st character "N"

1-2 Nut Type

3-5 Nut Geometric Industry Standard or Manufacturer

6-8 Nut Materials Industry Standard and Grade


Washers

1st character "W"

1-2 Washer Type

3-4 Washer Set Quantity

5-6 Bolt Diameter

7-8 Washer Thickness

9-11 Washer Geometric Industry Standard or Manufacturer

12-14 Washer Materials Industry Standard and Grade


Miscellane-ous Parts

1st character "A"


4-5 Pressure Rating

6-8 Valve Manufacturer and Model Number



15-16 Miscellaneous Part Requisition Classification




Stock Piping Specialties

1st character "S"

1-3 Piping Specialty Type

4-5 Pressure Rating

6-7 End Preparation




16-17 Piping Specialty Requisition Classification


Stock Instruments

1st character "I"

1-3 Instrument Type

4-5 Pressure Rating

6-7 End Preparation




16-17 Instrument Requisition Classification


Defining Preparatory Data


Defining Preparatory Data After completion of the parsing procedure, the standard set of preparatory data is populated in the respective SmartPlant Materials tables and the data is reflected in the screen PDS 50.02. The user can further customize the data and can further define his or her set of new data also as per requirement. For defining the data, the user must follow the process given below.

Please ensure that the modification or insertion of data is done in PDS 50.02 once the Parsing process completes and before the Spec Import is initiated. This is to avoid duplication of data.

The user must ensure the completeness of the following preparatory data before initiating the Spec Import process in SmartPlant Materials:

• Code List Attribute data and Table Detail data

• Commodity Group and Part data

• Zydex to Short Code to Piping Commodity Chars Translation data

• Units Data

The standard preparatory data is already provided as a part of the SmartPlant Materials installation. The user can Query / Modify / Delete standard data after the completion of the parsing procedure. The user can also add new records in the preparatory data. The mechanism of defining the preparatory data is described below:



Define Code List Attribute Data and Table Detail Data

Presently, the Parsing Process automates the generation of code list Attribute data and Table Detail Data for all the attributes (for example, CL330 End Preparation) for which code lists exist in PDS and are supplied as ASCII files for PDS Import. For attributes that do not have a code list (for example, Rating) and for attributes that do not have PDS sources, a minimum set of data has been provided as standard data. This data gets reflected in SmartPlant Materials screen PDS 50.02 during Parsing.

It is the sole responsibility of the user to ensure the completeness of data for attributes like Rating and so forth. Below are the provisions for defining the data.

We can broadly classify all the attributes into two types for functional purposes:

• Commodity Rule attributes

• Interface attributes

Commodity Rule attributes are attributes that are part of the Commodity Key Rule.

Interface attributes are the attributes that are meant for Spec export purposes.

Depending on the attribute under consideration, the user must prepare the data in either or both of the Code List Attributes Data and Table Detail Data.

Code List Attribute Data

Translation Name

Short Description

Long Description Code List Number (Attribute Value)

Table Detail Data

Translation Name

Code List Number

(Attribute Value)

Table Details Description



Commodity Rule Attributes The following table lists the Commodity Rule attributes and their translation names:

Attribute Name Translation Name

End Preparation CL330

Geometric Industry Standard or Manufacturer

CL575

Materials Industry Standard and Grade

CL145

Pressure Rating RATING

Valve Trim VT

Surface Preparation or Lining Material

SPLM

Flange Face Surface Finish FFSF

Gasket Type GTYP

Bolt Type BTYP

Nut Type NTYP

Washer Type WTYP

Valve Manufacturer and Model Number

VMMN

Manufacturing Method MMTH

Bolt Coating BCOT

Washer Set Quantity WSQ

Geometric Industry Practice GIP

Requisition Classification RC

Nipple length or Purchase Length NLPL

Gasket Thickness GTHK

Bolt Diameter BDIA

Washer Thickness WTHK



Attributes with PDS Source The following attributes come from PDS Reference Data. For these attributes, the user must define data in both Code List Attribute Data and Table Detail Data:

• End Preparation

• Geometric Industry Standard or Manufacturer

• Materials Industry Standard and Grade

• Pressure Rating

Define End Preparation The End Preparation code list is generated from PDS as an ASCII file. The End Preparation attribute corresponds to the PDS Code List CL330.

Fig 20: Sample CL330 code list as available in PDS Help

Example:

Consider the following entries of CL330 from PDS Help:

11 = 'FFFE' [Flat-face flanged end]

301 = 'BE' [Beveled end]

Code List Attribute Data for the End Preparation attribute is defined as below.



• The Translation Name for the End Preparation attribute is CL330.

• FFFE and BE correspond to the Short Description field of the Code List Attribute Data.

• Flat-face flanged end and Beveled end correspond to the Long Description field of the Code List Attribute Data.

• 11 and 301 corresponds to the Code List Number (Attribute Value) field of the Code List Attribute Data.

Translation Name

Short Description

Long Description Code List Number (Attribute Value)

CL330 FFFE Flat-face flanged end 11

CL330 BE Beveled end 301

Table Detail Data for End Preparation is defined as below.

• The Translation Name for the End Preparation attribute is CL330.

• The Code List Number (Attribute Value) is the same as the Code List Number (Attribute Value) of the Code List Data.

• The Table Detail values can be formulated as below: • Get the number of digits that this particular attribute occupies in the

Commodity Code Rule. For End Preparation, this is two. • Because the number of digits is two, start assigning the table detail

values from AA. The first Code List number is assigned table detail AA, the next AB, and so on.

• The Description field corresponds to the Long Description field of the Code List Data and to the Short Description if the Long Description is not present.

Translation name

Code List Number

(Attribute Value)


CL330 11 AA Flat-face flanged end

CL330 301 AB Beveled end

Exception The user must define Table Detail data for certain GCP and RCP End Preparation combinations occurring in PCD files.



The user has to get in all the possible End Preparation Combinations from PCD files such that “GCP End Prep Not Equals RCP End Prep” and “GCP End Prep Not Equals ‘-‘” and “RCP End Prep Not Equals ‘-‘”. These combinations have to be defined only in Table Detail Data.

For example, say that the GCP End Preparation and RCP End Preparation values in a PCD file are 11 and 301 respectively.

• The Code List Number (Attribute Value) in this case will be 11 and 301 concatenated by ‘x’.

• The table detail shall be the next in the sequence, say AC.

• The Description shall be the descriptions corresponding to the Code List Numbers (Attribute Value) concatenated by ‘x’.

Translation name

Code List Number

(Attribute Value)

Table Details

Description

CL330 11x301 AC Flat-face flanged end x Beveled end



Define Geometric Industry Standard The Geometric Industry Standard code list is generated from PDS as an ASCII file. The Geometric Industry Standard corresponds to Code List CL575 of PDS.


Defining Code List Attribute Data and Table Detail Data for the Geometric Industry Standard is similar to defining the data for the End Preparation except for the following differences:

• The translation name is CL575.

• The Table Detail values shall be assigned as AAA, AAB, and so on as the Geometric Industry Standard Attribute occupies three characters in the Commodity Code Rule.

• No data shall be defined that has the character ‘x’ in between.



Define Materials Industry Standard and Grade The Materials Industry Standard and Grade code list is generated from PDS as an ASCII file. The Materials Industry Standard and Grade corresponds to Code List CL145 of PDS.


Defining Code List Attribute data and Table Detail data for the Materials Industry Standard and Grade is similar to defining the Geometric Industry Standard.



Define Pressure Rating • The user should identify all the distinct GCP and RCP Rating values that

appear in PCD files.

• Derive the Interpreted Rating value from the distinct GCP and RCP values that appear in PCD files. The Interpretation logic is as described below. • If the rating value consist of alphanumeric characters (including

special characters), then the value of rating for interpretation will be the first continuous set of numeric characters excluding '.' .

• If the rating value is expressed in terms of alphabetic characters only, then the value of rating for interpretation will be all the characters.

• If the first character of the specified Rating value is 'S', then the value of rating for interpretation will be all the characters.

For example:

Rating Value as in PCD Interpreted Rating Value

CL125 125

125 125

125# 125

OT125 125

CL2000 2000

S-XS S-XS

• For each distinct Interpreted Rating value, define an entry in the Code List Attribute data and Table Detail data.

For example, let’s assume that the Rating values in the PCD files are:

• CL125

• CL2000

• 125

• 125#

The Code List Attribute data for Pressure Rating is defined as below.

• The Translation name for the Pressure Rating attribute is RATING.

• The Short Description is equal to the interpreted Rating value.

• The Long Description values shall be the identified Rating values that appear in the PCD file (that is, CL125, CL2000 ...) or the same as the Short Description value.



• Assign a unique number in the Code List Number (Attribute Value) field of the Code List Attribute Data.

Translation name

Short Description Long Description Code List Number

(Attribute Value)

RATING 125 CL125 1

RATING 2000 CL2000 2

Table Detail Data for Pressure Rating is defined as below.

• The Translation name for the Pressure Rating attribute is RATING.

• The Code List Number (Attribute Value) shall be the same as the Code List Number (Attribute Value) of the Code List Attribute Data.

• Because Pressure Rating occupies two positions of the Commodity Code Rule, the user shall start assigning table detail values from AA.

• The Description field corresponds to the Short Description field of the Code List Attribute Data.

Translation name

Code List Number Table Details Description

RATING 1 AA 125

RATING 2 AB 2000

The user must ensure that in the Table Detail data for ‘Pressure Rating’, there exists one and only one record as below.

Translation name


RATING - - -



Notes

• The user must ensure that in the Code List Attribute data for ‘End Preparation’, ’Geometric Industry Standard’, ’Materials Industry Standard and Grade’, and ‘Pressure Rating’, there exists one and only one record as below.

Translation name


(Attribute Value)

<<Translation Name>>*

Undefined Undefined X**

• The user must ensure that in the Table Detail data for ‘End Preparation’, ’Geometric Industry Standard’, ‘Materials Industry Standard and Grade’, and ‘Pressure Rating’, there exists one and only one record as below.

Translation name



X** ZZ Undefined

• The Table Detail values for an attribute must be unique; that is, there should not be two Code List Numbers (Attribute Value) with the same Table detail values.

* Refer to the appropriate sections in the Defining Preparatory Data chapter for Translation Names of Commodity Rule Attributes.

** X can be any number in this record.



Attributes without a PDS Source The following list of attributes are not from PDS data:

• Valve Trim

• Surface Preparation or Lining Material

• Flange Face Surface Finish

• Gasket Type

• Bolt Type

• Nut Type

• Washer Type

• Valve Manufacturer and Model Number

• Manufacturing Method

• Bolt Coating

• Washer Set Quantity

• Geometric Industry Practice

• Requisition Classification

• Nipple length or Purchase Length

• Gasket Thickness

• Bolt Diameter

• Washer Thickness

For these attributes, the user must define a minimum of two records in either or both the Code List Attribute data and Table Detail data as described below.

Attributes to be Defined in both Code List Attribute Data and Table Detail Data • Valve Trim

• Surface Preparation or Lining Material

• Flange Face Surface Finish

• Gasket Type

• Bolt Type

• Nut Type

• Washer Type



• Valve Manufacturer and Model Number

• Manufacturing Method

The user must define the data for Valve Trim as follows:

Code List Attribute Data

Translation name


VT - - -

VT Undefined Undefined X*

Table Detail Data

Translation name


VT - - -

VT X* ZZ Undefined

*X can be any number in this record.

The user must define data for the other attributes of this group in a similar way. The Table Detail values may change depending on the number of digits the attribute occupies in the Commodity Code Rule. Please refer to the appropriate sections in the Defining Preparatory Data chapter for the corresponding Translation Names.

Attributes to be Defined only in Table Detail Data Listed below are the attributes for which the Code List Number (Attribute Value) is not “NULL”:

• Bolt Coating

• Washer Set Quantity

• Geometric Industry Practice

• Requisition Classification



For example, the user must define the data for Bolt Coating as follows:

Table Detail Data

Translation name

Code List Number

(Attribute Value)


BCOT - - -

BCOT X* ZZ Undefined

*X should be any number in this record.

The user must define data for the other attributes of this group in a similar way. The Table Detail values may change depending on the number of digits the attribute occupies in the Commodity Code Rule. Please refer to the appropriate sections of the Defining Preparatory Data chapter for the corresponding Translation Names.

Listed below are the Attributes for which the Code List Number (Attribute Value) field is “NULL”:

• Nipple length or Purchase Length

• Gasket Thickness

• Bolt Diameter

• Washer Thickness

For example, the user must define the data for Nipple length or Purchase Length as follows:

Table Detail Data

Translation name

Code List Number

(Attribute Value)


NLPL - -

NLPL ZZ Undefined

The user must define data for the other attributes of this group in a similar way. The Table Detail values may change depending on the number of digits the attribute occupies in the Commodity Code Rule. Please refer to the appropriate sections in the Defining Preparatory Data chapter for the corresponding Translation Names.



Interface Attributes The following table lists the Interface attributes and their corresponding translation names:

Attribute Name SmartPlant Materials Translation Name

Corresponding PDS Code List Number

Fabrication Category CL180 CL180

Commodity Option CL400 CL400

Modifier CL550 CL550

Weight Code CL578 CL578

Schedule SCHEDULE CL332

Table Suffix TS CL576

For these attributes, the Table Detail data need not be defined, as these are not part of the Commodity Code Rule. Only Code List Attribute Data needs to be defined for these attributes.

Code Lists corresponding to these attributes are generated from PDS as an ASCII file.

Define Fabrication Category The Fabrication Category corresponds to Code List CL180.

Fig 23: Sample CL180 data as available in PDS Help

Consider an entry of CL180 from PDS Help:



7 = 'CSFF, Contractor supplied, field fabricated'

Code List Data for the Fabrication Category can be defined as below:

• The Translation name for the Fabrication Category attribute is CL180.

• ‘CSFF’ corresponds to the Short Description field of the Code List Data.

• ‘Flat Contractor supplied, field fabricated'’ corresponds to the Long Description field of the Code List Data.

• ‘7’ corresponds to the Code List Number (Attribute Value) field of the Code List Attribute Data.

Translation name

Short Description

Long Description Code List Number

(Attribute Value)

CL180 CSFF Contractor supplied, field fabricated'

7

Define Commodity Option The Commodity Option corresponds to Code List CL400.

Fig 24: Sample CL400 Data as available in PDS Help



Defining the Code List Data for the Commodity Option is similar to defining the Fabrication Category. Use the Short Description for the Long Description if the Long Description is absent.

Define Modifier The Modifier corresponds to Code List CL550.


Defining the Code List Data for the Modifier is similar to defining the Fabrication Category. Use the Short Description for the Long Description wherever the Long Description is absent.



Define Weight Code The Weight Code corresponds to Code List CL578.


Defining the Code List Data for the Modifier is similar to defining the Fabrication Category.



Define Schedule The Schedule corresponds to Code List CL332.


Defining the Code List Data for the Schedule is similar to defining the Fabrication Category.

Exception:

The user must ensure that the Code List Data for schedule contains at a minimum the following records:

Translation name

Short Description


SCHEDULE Undefined Undefined 1

SCHEDULE MATCH Match Schedule of Pipe

2

SCHEDULE NREQD Not Required 3

SCHEDULE CALC Calculate 4



Define Table Suffix The Table Suffix corresponds to Code List CL576.


Defining the Code List Attribute Data for the Table Suffix is similar to defining the Fabrication Category

Note

• The user must ensure that the Code List Attribute data of all Interface attributes contains two records as below.

Translation name

Short Description



Undefined Undefined X**


- - -

*Refer to the appropriate sections of the Defining Preparatory Data chapter for Translation Names corresponding to the Interface attributes.

**X can be any number in this record.



Define Commodity Group and Part Data Presently, SmartPlant Materials provides a standard set of data from which the Commodity Group and Part data can be derived. It is possible that the user may have his or her own Model Codes. For these Model Codes, the user must define the data following the methodology given below; otherwise, the Spec Import process fails because it cannot derive the Commodity Group and Part.

The user must ensure that the same Model Code is not defined twice, which may result in the wrong derivation of the Commodity Group and Part, or even the Spec Import process may fail due to duplicate data. If the definition for a Model Code exists, the user should not define it.

Please note that the standard set of data is visible in the SmartPlant Materials screen PDS 50.02 only after completion of the Parsing process. It is at this point the user must modify or add missing data so that the problems of duplicate data being keyed in can be eliminated.

For all Model Codes, the user shall define the following data:

1. Model Code to Piping Commodity Type Translation data 2. Piping Commodity Type Code List Attribute Data 3. Piping Commodity Type Table Detail Data

Define Model Code to Piping Commodity Type Translation Model Code to Piping Commodity Type Translation data:

Model code Piping Commodity Type

Model Code - The PDS Model Code that appears in PCD files.

Piping Commodity Type - The Short name given to the Model Code.

The user must determine the corresponding Piping Commodity Type for all Model Codes. For each Model Code, the user should assign a short name (Piping Commodity Type). The probable source from PDS Help for Piping Commodity Type corresponding to a model code is Description of the Model Code.



Fig 29: Model Codes Source from PDS Help

For example, consider the following Model Code:

“Long pattern, bolted or male ends gate valve (MC=GAT)”.

Here the description of the Model Code GAT is ‘Long pattern, bolted or male ends gate valve’. The short name derived from this description, say ‘Long pattern gate valve’, will form the Piping Commodity Type.

Similarly, for the Model Codes GATSP, GATF, and GATR, the Piping Commodity Type will be “Short pattern gate valve”, “Gate valve full port”, and “Gate valve reduced port”, respectively.


GATSP Short pattern gate valve

GAT Long pattern gate valve

GATF Gate valve full port

GATR Gate valve reduced port



Define Piping Commodity Type Code List Attribute Data The user must create entries in the Code List Attribute Data.

• The Translation Name for Piping Commodity Type is fixed to PCT.

• The Short Description will be the same as the corresponding Piping Commodity Type of “Model Code to Piping Commodity Type Translation”.

• The Long Description will be the description of the corresponding Model Code.

• The Code List Number (Attribute Value) is a unique number.

Below are the steps for defining Piping Commodity Type Code List Attribute Data:

1. Get all the Piping Commodity Types from the Model to the Piping Commodity Type Translation.

2. Order the Piping Commodity Types such that all the Piping Commodity Types corresponding to each category (Valves, Flanges, and so forth) are contiguous. Also, order the Piping Commodity Types within each category as per the usage of the corresponding Model Code; that is, because Model Code GAT is used more frequently, the Piping Commodity Type corresponding to GAT should be the first of all the Gate Valves’ Piping Commodity Types.

3. Start assigning unique Code List Numbers.

For Example:

Consider the example of the AABBCC Code 6Q1C01 Gate Valve.

The list of Piping Commodity Types corresponding to the Model Codes within AABBCC Code 6Q1C01 are as follows (Ref: Model Code to Piping Commodity Type Translation):

• Short pattern gate valve

• Long pattern gate valve

• Gate valve full port

• Gate valve reduced port



Because the Model Code GAT is more frequently used, the corresponding Piping Commodity Type will be the first upon reordering.

• Long pattern gate valve

• Short pattern gate valve

• Gate valve full port

• Gate valve reduced port

Assign Code List Numbers (Attribute values):

• Long pattern gate value 2

• Short pattern gate value 3

• Gate valve full port 4

• Gate valve reduced port 5

The Long description corresponds to the Description of the Model Code.

Consider the Long pattern, bolted or male ends gate valve (MC=GAT) (SN=V1) [Reference Fig 29: Model Codes Source from PDS].

Here ‘Long pattern, bolted or male ends gate valve’ corresponds to the Long description for the Model Code ‘GAT’.

Translation Name


PCT Long pattern gate value

Long pattern, bolted or male ends gate valve

2

PCT Short pattern gate value

Short pattern gate valve 3

PCT Gate valve full port Regular pattern, female ends, full port gate valve

4

PCT Gate valve reduced port

Regular pattern, female ends, reduced port gate valve

5



Define Piping Commodity Type Table Detail Data The user must create entries in the Table Detail Data. The Translation Name for the Piping Commodity Type is ‘PCT’. The Code List Number corresponds to the Code List Number (Attribute Value) of the Code List Attribute Data for the Piping Commodity Type. The Table Detail value shall be three character unique combinations. The Description corresponds to the Short Description of the Code List Attribute Data for the Piping Commodity Type.

For example, consider the Gate Valve 6Q1C01. The Code List Number (Attribute Value) and Description correspond to the Code List Number (Attribute Value) and Short Description of the Code List Attribute data for the Piping Commodity Type.

The first character of the Table Detail for the Piping Commodity Type is fixed. The defined first characters are as below:

Category Table Detail(1st Character)

Plain Piping and Nipples P

Tubing and Hose T

Valves V

Miscellaneous Fittings M

Flanges F

Gaskets G

Bolts B

Nuts N

Washers W

Miscellaneous Parts A

Stock Piping Specialties S

Stock Instruments I

For the Code List value "PCT" (in PDS 50.02 on the Code List Table Details tab page), there should not be any table detail value starting with 'B', 'G', ''N', or 'W'.



For example, for Valves, the first character for the Table Detail is V, and then you can start assigning the Table Detail as shown below:

Translation Name

Code List Number


PCT 2 VAA Long pattern gate value

PCT 3 VAB Short pattern gate value

PCT 4 VAC Gate valve full port

PCT 5 VAD Gate valve reduced port

The Commodity Group and Part Data for SmartPlant Materials are derived from the Table Detail values of the Piping Commodity Type. The first character of the Table Detail is considered to be the Commodity Group, and the next two characters are considered to be the Commodity Part.

For example, if the Table Detail data for the Long pattern gate valve is ‘VAA’, then the first character ‘V’ is the Commodity Group and the next two characters ‘AA’ are the Commodity Part.

Exceptions: The Commodity Group and Part data for the following Model Codes are fixed:

Model Code Commodity Group Commodity Part

RWELD M FD

RPAD M FB

M451 M CE

M902 M CV

PIPB P BA



The Commodity Group and Part data for the following AABBCC Codes are fixed:

AABBCC Code Commodity Group Commodity Part

PIPING P AA

6Q3C89 P BA

6Q3C95 G G

6Q3C97 B B

6Q3C98 N N



Define Zydex to Short Code to Piping Commodity Chars Translation Data

The user should define a Short Code, Truncated Short code, and Piping Commodity Chars data for a given ‘PDS Commodity Name’ (AABBCC Code).

Follow these steps to define “Zydex to Short Code to Piping Commodity Chars Translation” data:

1. List out all the AABBCC Codes that appear in the PCD files. 2. Against each AABBCC Code, assign a Short Code. The probable choice for this

data from the PDS Help is the Description field corresponding to AABBCC Code.

Fig 30: AABBCC Codes Source from PDS Help

The Truncated Short Code is a short name given to the Short Code (maximum of 10 characters).



Piping Commodity Chars data • For a given AABBCC Code, list out all the Model Codes. The Model

Code that corresponds to a given AABBCC Code is obtained from PDS Help [Reference Fig 29: Model Codes source from PDS].

• For each Model Code, the Piping Commodity Chars data is derived as described below:

For example, consider the Model Code ‘GAT’.

The Piping Commodity Type corresponding to the Model Code ‘GAT’ from “Model to Piping Commodity Type Translation” data is ‘Long pattern gate valve’.


GAT Long pattern gate valve

Model code to Piping Commodity Type Translation data

The Code List Number corresponding to the Piping Commodity Type ‘Long pattern gate valve’ from “Piping Commodity Type Code List Attribute data” is ‘2’.

Translation Name


PCT Long pattern gate value

Long pattern, bolted or male ends gate valve

2

Piping Commodity Type Code List Attribute data

The Piping Commodity Type Chars corresponding to Code List Number ‘2’ from “Piping Commodity Type Table Detail Data” is ‘VAA’.

Translation Name

Code List Number


PCT 2 VAA Long pattern gate value

Piping Commodity Type Table Detail Data



For example, consider the AABBCC Code 6Q1C01, Gate valve (in-line):

• The Short Code is equal to the Description against the AABBCC Code. In this case, it is Gate valve (in-line).

• The Truncated Short Code is the short name (maximum of 10 characters) given to the Short Code. Hence, it may be GAT_VAL.

• For determining the Piping Commodity Chars, we follow the steps described below: • All the Model Codes corresponding to the AABBCC Code 6Q1C01

are GATSP, GAT, GATF, and GATR • These Model Codes lead to the Piping Commodity Chars VAB, VAA,

VAC, and VAD, respectively.

AABBCC Code

Short Code Truncated Short Code

Piping Commodity Chars

6Q1C01 Gate valve (in-line)

GAT_VAL VAA


GAT_VAL VAB


GAT_VAL VAC


GAT_VAL VAD



Define Units Data The user must define the Units of Measure data and specify the Unit Set to System to Units of Measure data.

Units of Measure data

Unit Set Units of Measure (UOM)

Unit Set to System to Units of Measure data

Unit Set Unit System Units of Measure (UOM)

The PDS source for the Units data is Code Lists CL1010, CL1028, CL1056, CL1064, CL1074, and CL1162.

Unit Set: This data corresponds to the Description of the Code list sets CL1010, CL1028, and so forth. The Unit Set data should be limited to a maximum length of 10 characters.

Unit System: The Unit System should be METRIC and IMPERIAL.

Unit of Measure: This data corresponds to the Unit name field of the Code lists sets CL1010, CL1028, CL1056, CL1064, CL1074, and CL1162, except Blank.

For example, consider the PDS Code List CL 1056.

Fig 31: Units Data Source from PDS Help

Here, the Code List set 1056 description is “Temperature Units”. The appropriate short name for the Unit set may be ‘TEMP’.

The Units of Measure in this case may be ‘degF’, ‘degC’, ‘degR’, and ‘K’.



The record entries for the Temperature Units data would hence look like:

Units of Measure data Unit Set Units of Measure (UOM)

TEMP degF

TEMP degC

TEMP degR

TEMP K

Unit Set to System to Units of Measure data This data should be defined so that there is one record for each Unit Set and Unit System combination.

The Units of Measure will be one of the Units of Measure of the Unit set that is most likely to be used for that Unit System

For example:


TEMP METRIC degC

TEMP IMPERIAL degF

Notes

• The user should ensure that there exists one and only one record in the Units of Measure data as:

Unit Set Units of Measure (UOM)

ALL -

• The user should also ensure that there exist two records in the Unit Set to System to Units of Measure data as:


ALL METRIC -

ALL IMPERIAL -

Data Entry Using SmartPlant Materials Screen PDS 50.02


Data Entry Using SmartPlant Materials Screen PDS 50.02 Code List and Table Detail Data

The user can enter the Code List data on the Code List – Attributes tab of the SmartPlant Materials PDS 50.02 screen. For more information, see the Defining Preparatory Data chapter, Define Codelist Attribute Data and Table Detail Data section.

Fig 32: PDS 50.02 Code List - Attributes Tab

• The Translation Name field of the Code List Attribute Data corresponds

to the Code List field of the Code List – Attributes tab on the PDS 50.02 screen.

• The Code List Number field of the Code List Attribute Data corresponds to the Attribute Value field of the Code List – Attributes tab on the PDS 50.02 screen.

• The Short Description field of the Code List Attribute Data corresponds to the Short Desc field of the Code List – Attributes tab on the PDS 50.02 screen.

• The Long Description field of the Code List Attribute Data corresponds to the Long Description field of the Code List – Attributes tab on the PDS 50.02 screen.



The user can enter the Table Detail data on the Code List –Table Details tab of the SmartPlant Materials PDS 50.02 screen. For more information, see the Defining Preparatory Data chapter, Define Codelist Attribute Data and Table Detail Data section.

Fig 33: PDS 50.02 Code List-Table Details Tab

• The Translation Name field of the Table Detail Data corresponds to the Code List field of the Code List – Table Details tab on the PDS 50.02 screen.

• The Code List Number field of the Table Detail Data corresponds to the Attribute Value field of the Code List – Table Details tab on the PDS 50.02 screen.

• The Table Details field of the Table Detail Data corresponds to the Table Detail field of the Code List – Table Details tab on the PDS 50.02 screen.

• The Description field of the Table Detail Data corresponds to the Short Desc field of the Code List – Table Details tab on the PDS 50.02 screen.



Commodity Group and Part Data 1. The user can enter the Model Code in the Piping Commodity Type Translation

Data on the Model Code to PCT tab on the SmartPlant Materials PDS 50.02 screen. For more information, see the Defining Preparatory Data chapter in the Define Model Code to Piping Commodity Type Translation section.

Fig 34: PDS 50.02 Model Code to PCT Tab

• The Model Code field of the Model Code to Piping Commodity Type Translation corresponds to the Model Code field of the Model Code to PCT tab on the PDS 50.02 screen.

• The Piping Commodity Type field of the Model Code to Piping Commodity Type Translation corresponds to the Piping Commodity Type field of the Model Code to PCT tab on the PDS 50.02 screen.

2. The user can enter the Piping Commodity Type Code List Attribute Data on the Code List – Attributes tab on the PDS 50.02 screen. [Reference Fig 32: PDS 50.02 Code List-Attributes Tab]. For more information, see the Defining Preparatory Data chapter, Define Piping Commodity Type Code List Attribute Data section.

• The Translation Name field of the Define Piping Commodity Type Code List Attribute Data corresponds to the Code List field of the Code List –Attributes tab on the PDS 50.02 screen.

• The Code List Number field of the Define Piping Commodity Type Code List Attribute Data corresponds to the Attribute Value field of the Code List – Attributes tab on the PDS 50.02 screen.



• The Short Description field of the Define Piping Commodity Type Code List Attribute Data corresponds to the Short Desc field of the Code List – Attributes tab on the PDS 50.02 screen.

• The Long Description field of the Define Piping Commodity Type Code List Attribute Data corresponds to the Long Description field of the Code List –Attributes tab on the PDS 50.02 screen.

3. The user can enter the Piping Commodity Type Table Detail Data on the Code List – Table Details tab on the SmartPlant Materials PDS 50.02 screen [Reference Fig 33: PDS 50.02 Code List-Table Details Tab]. For more information, see the Defining Preparatory Data chapter, Define Piping Commodity Type Table Detail Data section.

• The Translation Name field of the Define Piping Commodity Type Table Detail Data corresponds to the Code List field of the Code List – Table Details tab on the PDS 50.02 screen.

• The Code List Number field of the Define Piping Commodity Type Table Detail Data corresponds to the Attribute Value field of the Code List –Table Details tab on the PDS 50.02 screen.

• The Table Details field of the Define Piping Commodity Type Table Detail Data corresponds to the Table Detail field of the Code List – Table Details tab on the PDS 50.02 screen.

• The Description field of the Define Piping Commodity Type Table Detail Data corresponds to the Short Desc field of the Code List – Table Details tab on the PDS 50.02 screen.



Zydex to Short Code to Piping Commodity Chars Translation Data

The user can enter the Zydex to Short Code to Piping Commodity Chars Translation data on the Zydex to Short Code to Parts tab on the SmartPlant Materials PDS 50.02 screen. For more information, see the Defining Preparatory Data chapter, Define Zydex to Short Code to Piping Commodity Chars Translation Data section.

Fig 35: PDS 50.02 Zydex to Short Code to Parts Tab

• The AABBCC Code field of the Define Zydex to Short Code to Piping Commodity Chars Translation Data corresponds to the Zydex field of the Zydex to Short Code to Parts tab on the PDS 50.02 screen.

• The Short Code field of the Define Zydex to Short Code to Piping Commodity Chars Translation Data corresponds to the Short Code field of the Zydex to Short Code to Parts tab on the PDS 50.02 screen.

• The Truncated Short Code field of the Define Zydex to Short Code to Piping Commodity Chars Translation Data corresponds to the Trunc Short Code field of the Zydex to Short Code to Parts tab on the PDS 50.02 screen.

• The Piping Commodity Chars field of the Define Zydex to Short Code to Piping Commodity Chars Translation Data corresponds to the Piping Comm Chars field of the Zydex to Short Code to Parts tab on the PDS 50.02 screen.



Units Data 1. The user can enter the Units of Measure data on the Unit of Measure tab on the

SmartPlant Materials PDS 50.02 screen. For more information, see the Defining Preparatory Data chapter, Define Units Data section.

Fig 36: PDS 50.02 Unit of Measure Tab

• The Unit Set field of the Units of Measure data corresponds to the Unit Set field on the Unit of Measure tab on the PDS 50.02 screen.

• The Units of Measure field of the Units of Measure data corresponds to the UOM field on the Unit of Measure tab on the PDS 50.02 screen.



2. The user can enter the Unit Set to System to Units of Measure data on the Unit Set to System tab on the SmartPlant Materials PDS 50.02 screen.

Fig 37: PDS 50.02 Unit Set to System Tab

• The Unit Set field of the Unit Set to System to Units of Measure data

corresponds to the Unit Set field on the Unit Set to System tab on the PDS 50.02 screen.

• The Unit System field of the Unit Set to System to Units of Measure data corresponds to the Unit System field on the Unit Set to System tab on the PDS 50.02 screen.

• The Units of Measure field of the Unit Set to System to Units of Measure data corresponds to the UOM field on the Unit Set to System tab on the PDS 50.02 screen.

Configuring SmartPlant Materials for Specification Import



The user must perform the following steps before he invokes the PDS Import process through the SmartPlant Materials PDS 50.01 screen:

• Ensure that all the PDS ASCII files extracted were placed in a single folder on the Database Server Machine (for example, D:\oradata\MD2\PDS_INDIA).

• The following grants must be given to M_SYS user: • CREATE ANY DIRECTORY • DROP ANY DIRECTORY

• Create a new Product Group.

• Log into the newly created Product Group.

• Set the parse options (PDS 50.01: Window 3, Reference: Fig 39: PDS 50.01 Spec Import – Parsing Options (with default configuration data): • The user can check the check boxes corresponding to ‘Fluid Code’,

‘Table Checker’, ‘Pipe Length Table’, ‘TAP Data Table’, ’Material Description’, ‘Bend Deflection Table’, ‘Materials Table’, ‘Temperature /Pressure Table’, and ‘Gasket Separation’ in order to make them optional while parsing. This means that if the file is available as an ASCII file from PDS, then it will be parsed and the data is imported in the respective SmartPlant Materials data structure(s). If the file is not available, it will be ignored. The parsing program will NOT error out and stop; rather, it should continue with the execution of other program units downstream. Un-checking a check box makes the corresponding file mandatory for parsing. This means that if the file is not available, the parsing program should error out and the parsing transaction will stop.

• The user must also specify the file names for ‘Piping Material Class’, ‘Standard Notes’, ‘Physical Data List’, ‘TAPS Table’, ‘Material Description’, ‘Table Checker Report List’, ‘Material grade’, ‘ Fabrication Category’, ‘End preparation’, ‘Schedule Thickness’, ‘ Option Code’, ‘Table Suffix’, ‘Weight Code’, ‘Modifier’, and the ‘Geometric Standard’ files that are extracted from PDS. The parser program takes into account the file names as specified on this screen for parsing these files.



• The user can specify whether to generate the physical log file by checking the ‘Generate Physical Logs’ check box. The physical log file (for all the transactions on screen PDS 50.01 with log messages of the next executing processes) will be generated at the location specified as the Setting Value corresponding to the DBA Settings Name ‘LOG_FILE_DEST’ on the A.60.04 DBA Settings screen.

• Specify the physical path (for example, D:\oradata\MD2\PDS_INDIA in our case) of the single folder on the Database Server machine where the PDS-generated and manually-created ASCII files are placed, in the Directory Path field on the PDS 50.01 screen.

Fig 38: PDS 50.01 Spec Import

Fig 39: PDS 50.01 Spec Import – Parsing Options (with default configuration

data)

Specification Import Process


Specification Import Process • The parsing process can now be initiated by clicking the Parse button

(PDS 50.01 screen).

• Once the parser program of PDS Spec Import (PDS 50.01) is initiated, the parser program does the following: • First, the parser routine creates a Database directory object (directory

name PDS_TBLS_PATH) with the path specified in the Directory Path field on the PDS 50.01 screen and grants READ privilege to the DBA, M_PROJECT_ROLE, and PUBLIC Roles.

• The Parser routine then scans the PDS ASCII files and loads the parsed data into the following SmartPlant Materials Database tables upon success:

PDS Data Type (ASCII file ) Database table loaded

Piping Material Class Data M_PDSI_PIP_MAT_CLS_TBLS

Piping Commodity Data M_PDSI_PIP_COMM_DATA_TBLS

Physical Data Library and Piping Job Specification List file

M_PDSI_PDL_LIST_DATA_TBLS

Diameter Tables M_PDSI_DIA_TBLS

Wall Thickness Tables M_PDSI_THCK_TBLS

Fluid Code Tables M_PDSI_FLDCDE_TBLS

Branch Tables M_PDSI_BRANCH_TBLS

Materials Data Tables M_PDSI_MAT_TBLS

Gasket Tables M_PDSI_GSKT_TBLS

Pressure Temperature Tables M_PDSI_PT_TBLS

Tap Properties Data M_PDSI_TAP_DATA_TBLS

Bend Deflection Tables M_PDSI_BEND_DEF_TBLS

Pipe Length Tables M_PDSI_PIPE_LEN_TBLS

Material Description and Standard Notes Code Lists

M_PDSI_CL_MATNOTES

Table Checker Report (scanned only for finding Physical Tables associated with a Commodity Code)

M_PDSI_CC_DIM_TBLS

Geometric Data (derived from PCD files)

M_PDSI_GEOM_DATA



Physical Tables M_PDSI_PHYSICAL_TBLS_DATA

Mandatory Code Lists M_PDSI_CL_ATTRS

M_PDSI_CL_TDS

Short and Long BOM files M_PDSI_SHT_LONG_BOMS

• The routine populates the standard data into the underlying tables of the PDS 50.02 screen. The user must check and ensure for the completeness of the data on the PDS 50.02 screen.

• When the parse process completes successfully, the listing of parsed Specs with details are shown on the PDS 50.01 screen. The Validate Data button becomes enabled. Please note that at this point the Specs have only been parsed and parsed data is kept in temporary tables. The parsed Specs have NOT been imported into SmartPlant Materials data structures.

• The user can click the View Parsed Data button to navigate to the PDS 50.01 screen: Window 4 and query / view the parsed data. [Reference Fig 40: PDS 50.01 Spec Import – View Parsed Data].

• The user can select PDS Data Type from the List Box, and the screen for corresponding parsed data will be displayed. [Reference Fig 41: PDS 50.01 Spec Import – View Parsed Data (Bend Deflection Table)].

Fig 40: PDS 50.01 Spec Import – View Parsed Data

Fig 41: PDS 50.01 Spec Import – View Parsed Data (Bend Deflection Table)



The list of PDS Data Types for which the Parsed data can be viewed are listed below:

PDS Data Type (ASCII file )

Piping Material Class Data

Bend Deflection Tables

Branch Tables

Diameter Tables

Fluid Code Tables

Gasket Tables

Material Description and Standard Notes Code Lists

Physical Tables

Pipe Length Tables

Piping Commodity Data

Pressure Temperature Tables

Tap Properties Data

Wall Thickness Tables

• Please note that at this time (after successful parsing), the Spec Import button is still disabled, but the Validate data button is enabled. The Spec Import button gets enabled only after successful validation of the data. The Validate data functionality has been provided to prevent most of the potential data errors from occurring at a later stage during the import process by helping the user to identify the data that may not be defined properly and by allowing the user to ensure for correctness before starting the import process.

The validation process checks the following data inconsistencies:

• Data inconsistency occurring in the ASCII files that are parsed

• Data inconsistency occurring in the Spec Import Preparatory data (PDS 50.02)

If any data inconsistency occurs in the ASCII files, then the user needs to parse the corrected ASCII files again.

If any data inconsistency occurs in the Spec Import Preparatory data, then the user needs to correct the data on the PDS 50.02 screen.

In both of the above cases, the user needs to validate the data again before initiating Spec Import.



• The user can now select the Spec(s) to be imported into SmartPlant Materials by checking the corresponding check box and clicking the Spec Import button.

• On click of the Spec Import button, the Product Group gets configured first. During configuration of the Product Group, the following steps are carried out programmatically. The configuration of the Product Group is done only once for a Product Group.

• Define the default standard ANSI. Also, make it the Default standard if it already exists. • Create Unit Systems - IMPERIAL & METRIC - if they do not

exist. • Create Unit of Measure (From Preparatory Data). • Create Unit Sets (From Preparatory Data). • Create a Company with code INGR. • Set the Default Unit System as IMPERIAL . • Create Interface PDS if it does not exist. • Populate the Short Codes. • Create all Commodity Rule Tables (including associated

Attributes). • Create Industry Commodity Rules. • Create link tables with all the Commodity Rule Tables. • Create all Interface Tables. • Create all Objects (along with Object Parameters). • Create (Geometric) table structure for each type of Object. • Populate all (Commodity Attribute and Interface) Code List tables. • Create Spec Rule. • Create Spec Type and Spec Structure. • Create SmartPlant Materials Data Structures for Fluid Code. • Create SmartPlant Materials Data Structures for Corrosion

Allowance. • Create SmartPlant Materials Data Structures for Gasket

Separation. • Create SmartPlant Materials Data Structures for V&D Macro. • Create SmartPlant Materials Data Structures for Thickness

Equation. • Create SmartPlant Materials Data Structures for Material Class

(Material of Construction).



• Create SmartPlant Materials Data Structures for Thickness Table / Wall Thickness Table.

• Associate the table for Standard Note-A with Spec Rule. • Associate the table for Standard Note-B with Spec Rule. • Associate the table for Material Description with Spec Rule. • Create SmartPlant Materials Data Structures for Bend Deflection

Table with Spec Rule. • Associate the table for Pressure/Temp with Spec Rule. • Create SmartPlant Materials Data Structures for Pipe Length

Table. • Create SmartPlant Materials Data Structures for Material Data

Table. • Create SmartPlant Materials Data Structures for Tap Table. • Create SmartPlant Materials Data Structures for storing PCD RCP

End Prep (if GCP = RCP). • Create SmartPlant Materials Data Structures for storing Schedule

(for Zydex PIPING and GCP Schedule '*C%'). • Create all Commodity Groups and Parts. • Identify Group and Part and update every row of PCD. • Populate Preferable Values for PCD Attributes. • Create Physical Data Table Structures. • Create Physical Data Table Rules.

• After the successful configuration of the Product Group, the selected specs are imported into SmartPlant Materials. The data is reflected in the corresponding SmartPlant Materials screens.

Index


Index

attribute data piping commodity type code list, 52

attributes having PDS source, 33 interface, 44 not having PDS source, 41

code list attribute defining, 31

commodity code rule review, 25 commodity group and part data, 50, 64 commodity option, 45 configuration

configure SmartPlant Materials for specification import, 69

data entry SmartPlant Materials screen PDS 50.02, 62

end prep, 33 extraction

PDS ASCII files, 5 fabrication category, 44 geometric industry standard, 36 import

configure SmartPlant Materials for specification import, 69

specification import process, 71 interface attributes, 44 library code lists

standard note, 19 library tables

physical data library tables, 17, 23 long description library, 22 materials industry standard and grade, 37 model code to piping commodity type translation, 50 modifier, 46 PDS ASCII files, 5 physical data library tables, 17 piping commodity data, 9 piping commodity type

table detail data, 54 piping commodity type code list, 52 piping job specification tables, 18 piping material class data, 7 PJS tables list file, 23 preparatory data

defining, 30 pressure rating, 38 schedule, 48 short description library, 21 standard note library code lists, 19 table checker report, 13

list file, 24 table detail data

defining, 31 table suffix, 49 tap properties data, 11 units data, 60, 67 weight code, 47 Zydex, 57, 66

smartplant materials importing pds...

Documents