smartplant materials how to create standard piping...

SmartPlant Materials How to Create Standard Piping Classes

Version 2008.5 (6.3.6) October 2009 DMAR1-PE-200084B

Copyright Copyright © 2004-2009 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.

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.

Trademarks Intergraph, the Intergraph logo, PDS, SmartPlant, SmartSketch, FrameWorks, INtools, MARIAN, ISOGEN, and IntelliShip are registered trademarks and SupportModeler and SupportManager are 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 How to Create Standard Piping Classes 3

Table of Contents

Preface .................................................................................................................................4

Overview .............................................................................................................................5

How to Create Standard Piping Classes ..........................................................................7

Target Role ...................................................................................................................8 Session Goal .................................................................................................................9 Workflow Prerequisites ..............................................................................................10 Budget Hours: Concept Transfer to Users ..................................................................11

Detailed Workflows .........................................................................................................12

Specification Types ....................................................................................................13 Specification Rules .....................................................................................................14 Spec Management (CWS) (S.50.06 Spec Items) ........................................................15 Ident Filter ..................................................................................................................22 Create New Commodity Codes from the Piping Class ..............................................37 Standard Report S.50.R.11 Piping class .....................................................................40

Preface

4 SmartPlant Materials How to Create Standard Piping Classes

Preface This document is a user’s guide for SmartPlant® Materials 6.2.

It describes the processes to create standard piping classes.

Send documentation comments or suggestions to [email protected].

Overview


Overview This document describes how to create standard piping classes.

In an enterprise or project piping environment, thousands of piping components are available. Countless variations of pipes, fittings, bolts, gaskets valves and other components exist. A piping class defines a subset of components to be used for specific media, pressure and temperature conditions. Since only a correct pipe class can guarantee accurate operation of the plant, the pipe class is a very important document and the downstream processes must follow the rules created in the pipe class.

In the design process of a plant, a process diagram is first created. In a process diagram, the material flows and material properties (physical conditions, pressure, temperature, and other data) are shown. The process diagram has no relation to the components that will be used for construction and, normally, does not contain any pipe class data.

Based on the process diagram, the P&ID is created, adding more detail describing the process. The media flows and their conditions are described in more detail. The P&ID specifies the temperature/pressure relation and the diameters as well as the selection of pipe classes for all lines. Based on the pipe class definition components, such as valves and reducers, are pre-selected and an initial material estimation is produced. In the downstream process of piping design, the pipe class and the P&ID are used as basic documents for further engineering.

A pipe class generally contains the following information:

• Pipe class header information o Pipe class code and description

o Allowed media for the pipe class

o Allowed Pressure/temperature ranges

o General material

o Allowed diameter (Diameter table)

o Allowed schedules per diameter (Schedule Table)

o Corrosion allowance

o Allowed branches (Branch table)

o Allowed gasket type and form

o Special notes

o Release index and revision index

• Pipe class item information

o Definition of components including commodity code and size range for allowed component types

Overview


• Pipe class ident information

o The pipe class information ultimately defines a unique ident for each size and specification item. Such an ident defined in a SmartPlant Materials pipe class is called “Spec item ident”,

The definition of a pipe class in SmartPlant Materials is created based on the following process workflow diagram.

How to create piping How to create piping specificationsspecifications

S50.01Spec Rule

S50.02Spec Type

S50.06CWS

Spec Items

S50.06Spec Header

groups

S50.06Spec Header

notes

S50.06Spec Header

limits

S50.06Spec Header

groups

S50.06Spec Header

details

S50.06Spec Header

notes

S50.06Spec HeaderFilter tables

S50.06Spec HeaderBranch table

S50.06Spec Item

results

S50.13Issue/revise Spec

(OPTIONAL)

Publish pipingSpec report

Translate Pipingspec into CAD

systems languages

S50.06Spec Itemdefinition

S50.06Spec Item

notes

S50.06Spec Item

Filter tables

Picture 1

Pipe classes include components and general information created in SmartPlant Reference Data and may be created either in the product group (corporate standards) or at the project level. Pipe classes may be copied from the product group or other projects and can be modified for project use. Once created in the current project, they are independent from another project or product group.

Pipe classes in SmartPlant Materials are called specifications, since this functionality can also be used for other disciplines than piping.

How to Create Standard Piping Classes


How to Create Standard Piping Classes The goal of this document is to explain the specific tasks and best practices for creating standard piping classes.



Target Role The target audience for this document is home-office-based, piping and super users.



Session Goal This session will enable users to understand the processes creating standard piping classes.



Workflow Prerequisites This document assumes that the SmartPlant Materials introduction, overview session as well as the session for the creation of idents has been completed.



Budget Hours: Concept Transfer to Users It will take 16 -24 hours to train users in this workflow.

Detailed Workflows


Detailed Workflows Based on the workflow shown in the overview, the specification type and rule information are preconditions for the creation of piping specifications.

Detailed Workflows


Specification Types The specification type is used to categorize and organize the specifications. The specification types can be used for any kind of organizing; for example, based on companies department, plant types, main specification material, media, and other information.

Specification types are defined in Screen S.50.02. Each specification type is assigned to a specification rule. At least one rule must exist before a specification type can be created.

If the specification copy function is used, the specification type structure has to be defined. In S.50.05 Specification copy, only those specifications that are possible copy sources are shown in the second block, which are assigned to the spec type of the spec defined as destination in the first block. If no spec type exists in the second block of this screen, the specification copy function is not available within this specification type. More details are provided in the document “How to create project piping classes based on standard classes.”

Picture 2

Detailed Workflows


Specification Rules In SmartPlant Materials, a specification rule allows you to assign tables and attributes to the specification header and to specification items.

As described in the overview section of this document, a specification header offers a lot of describing information. Most of the describing information, such as general material, can be assigned by SmartPlant Materials’ table details (identical to commodity code table) defined in A.50.02 Tables names. The specification rule allows you to use any table type defined in A.50.02.

Only the tables assigned to the specification header can be used later for detailed description of the specification at the specification header level.

Picture 3

The above example allows you to assign table details to each specification based on the tables service, rating class, material, and nominal corrosion allowance.

In the third block of Screen S.50.01, attributes are assigned to the specification header and specification line items. Both types of assignments are used for further documentation, reports, or for CIP execution in downstream SmartPlant Materials modules. There is one special attribute that can be assigned to the spec items. This is the hard coded attribute “ASS_NO.” which is used for the creation of spec dependent assemblies. Assemblies are not described in this document.

Detailed Workflows


Spec Management (CWS) (S.50.06 Spec Items) With service pack 10, the name of the screen S.50.06 “Spec Items” changed to “Specification Management.” Screen S.50.06 is now a core workflow screen (CWS), centralizing the functions of several basic screens (S.50.03/06/07/08 and some other standardization screens such as S10/20/30.xx…).

As described above, S.50.06 Specification Management offers the full functionality for creating specifications and managing specifications, the specification header, and specification item information.

S.50.06 allows creation of new specifications as well as updates to existing specifications. The field “Rev” represents the specification revision. The specification revision concept is described in the document “How to manage spec revisions.”

In the right section of the first block, tab folders are available for “Spec header description.” “Spec type description,” and “Variable Attributes.” The first two tab screens allow inserting or viewing the appropriate description. The third tab screen “Variable Attributes” allows inserting and viewing variable attributes that were previously defined for this spec rule in Screen S.50.01.

The spec code field is a free format code field that in most companies is filled with a meaningful code such as the nominal pressure, the main material group, and a sequential number.

Detailed Workflows


Picture 4

Spec Header Geometrics, Spec Groups, Details, Notes and Limits The second block of S.50.06 maintains the following:

• Spec header geometrics Special geometric tables are assigned to the specification. Filter tables used to define the wall thickness information for the specification, branch tables and other tables are used for additional documentation issues. Details will be given in the section “Ident Filter” in this document.

Detailed Workflows


• Specification groups and details: The specification group screen allows you to select tables based on available table names in S.50.01. Table groups can be used to classify the detail information of the table. For example, a table “MATERIAL” can be classified into groups “Stainless Steel,” “Carbon Steel,” “plastics” and others.

Picture 5

The specification details screen allows you to assign detail information for all preselected tables.

Picture 6

Note: These definitions are used exclusively for documentation. There are NO standard downstream processes in SmartPlant Materials that use these values or view them. Use these values in reports and CIPs if needed. ( See chapter “Standard report S.50.R.11 Piping class”)

• Specification notes Specification notes are predefined text blocks that can be assigned to specifications. Notes are comparable to the specification table details used to document specifications purposes and rules.

Detailed Workflows


Picture 7

General notes used in a specification must be predefined in screen S.50.09.

• Specification limits One common requirement to detail a specification completely is the definition of limits for pressure/temperature pairs. Limit definition is managed in the following sub screen and used exclusively for documentation purposes.

Picture 8

Detailed Workflows


Specification Items The specification item screen opens by a double click on the spec code in S.50.06.

Picture 9

Important fields:

Short Code The Short Code is a spec independent abbreviation for spec materials. The Short Code is MANDATORY field whether it is highlighted green or not. The Short Code’s main task is to give a quick and easy option to create manual estimations. Manual estimations are often created when no commodity codes exist in a spec. The Short Code allows you to insert bill of materials (BOM) data based on spec code, short code, sizes, and quantity. When commodity codes and subsequent idents are added to the specification, SmartPlant Materials is able to find the appropriate ident based on the above mentioned values.

The Short Code is created and managed in screen S.10.08. It can be reached by a simple double click on the field “Short Code.”

Special features for Short Code:

• S.10.08 includes a second window called “parts to short codes.” Use this data to filter the possible groups and parts in S.50.06 depending on the previously defined Short Code.

• The Short Code defines header geometrics for specific spec items. For example, the branch table header geometric definition can work with all items that have a Short Code “BR90” or ”BR45.” With this definition, the user can make sure that only branches are filtered by the branch table, contrary to the wall thickness filter table with which the branch table doesn’t work.

• Short Code “%,” This special short code exists in any SmartPlant Materials database. This short code is normally used for a general filter table for wall thickness in the spec header geometric definition. This placeholder therefore can be used to assign a filter table to all specification items.

Detailed Workflows


Group/part Mandatory field that requires the commodity group and part for a spec item.

Commodity Code As mentioned above, the commodity code can be added later. To receive the ultimate result of a specification, the specification item idents and the commodity code is needed.

An additional field behind the tab page is “Geometrics.”

Picture 10

Geometric 1: Geometric 1 is not a mandatory field. After a commodity code is assigned, this field is populated by the first available geometric table that has a geometric relation with the selected commodity code. Depending on the type of specification items and on the method used to standardize the idents, this results in unique spec item idents only if the idents are created from a geometric table containing unique diameter input values. If this is not the case, a filter table has to be assigned. See the section “Ident Filter” in this documents.

From1 to 1:

Size range for the first nominal size of a component.

From2 to 2:

Size range for the second nominal size of a component. This only has to be filled in very rare cases such as for nipples and weldolets. In all the other cases, the component is used for all size 2 sizes depending on the filter or ident table.

Detailed Workflows


Detailed Workflows


Ident Filter As mentioned in the overview chapter of this document, the ultimate aim of a piping specification is to define, based on specification items, a list of idents which are uniquely defined over the nominal diameter sizes.

In the below screen shot, a typical geometric table is shown that is not unique based on the nominal diameter sizes.

Picture 11

Each nominal diameter appears four times with different schedules, which means with different wall thicknesses. Based on the engineering work of a specification engineer, the schedule for each nominal size is calculated for the specification and stored in a filter table.

Working with filter tables has the advantage that the S.40.12 tables (geometric tables used for the creation of idents) can be created independent of the specification.

Detailed Workflows


Picture 12

The filter table represents the applicable schedule over all sizes. A typical best practice is to create filter table codes in accordance with the specification code in order to make maintenance easier.

This filter table can be assigned to the specification via the specification header geometrics or the geometric 1.

Assign Filter Table to Spec Header Geometrics A filter table is to list different components, such as pipe, fittings, flanges and reducers. The best and easiest way to filter all of these components is the filter definition via spec header geometrics. See the screenshot below.

Picture 13

Detailed Workflows


The spec header filter normally filters several different specification items that can have different allowed nominal sizes; thus, the filter only works for schedules and not for nominal sizes. If nominal size and schedule filtering is required for a component, it must be filtered by the spec item filter.

Check the field “filter” for the filter table defined in spec header geometrics.

It is very important that all spec items to be filtered by the spec header geometric filter table have the field “geometric 1” at spec item level EMPTY. This rule defines for any specification item an exception filter table simply by assigning a different filter table to the specification item record.

Picture 14

The filter result is shown in the next screen shot.

Picture 15

The idents shown above are now reduced by the filter table to one unique ident per nominal size. As a comparison, the next screen shot shows the same data once again without filter.

Detailed Workflows


Picture 16

Using the same process described, items with two sizes also can be filtered based on the following rule:

The schedule filter uses the filter nominal sizes for the nominal size 1 and nominal size 2. Using this rule, all items filtered will have the same schedule per nominal size regardless if it is the first or second size.

The following examples explains this rule and filtering method.

The same filter table is valid that was used for the pipe.

Picture 17

Detailed Workflows


The selected specification item is an eccentric reducer with the following idents:

Picture 18

Detailed Workflows


The table below shows that a successful filter match occurs only if the NPS/SCH pairs for sizes “1” and “2” match the filter table. The matching lines (“Y”) show that the reducer automatically follows the standard schedule table with its schedules.

Filter table Idents with Schedule S-10S and S-40S

NPS SCH NPS 1 NPS2 SCH_1 SCH_2 successful filter match

1 S-10S 1,5 1,0 S-10S S-10S Y 1 1/2" S-10S 1,5 1,0 S-40S S-40S N

2 S-40S 1,5 1,0 S-80S S-80S N 2 1,0 S-40S S-10S Y 2 1,0 S-80S S-80S N 2 1,0 S-40S S-40S N 2 1,5 S-10S S-10S N 2 1,5 S-40S S-40S N 2 1,5 S-40S S-10S Y 2 1,5 S-80S S-80S N

The result in SmartPlant Materials is shown in the next screen shot.

Picture 19

Important: This method of filtering items with two sizes is ONLY possible using the spec header geometrics.

Detailed Workflows


Assign Filter Table to Spec Item Geom1 Filtering at spec item level is very similar to the header filter method. The primary difference occurs with items of more than one size.

To explain the difference, the same example as above is used. The screen shot below shows what happens with the idents for the eccentric reducer if the same filter table is assigned to the spec item level.

Picture 20

Detailed Workflows


To filter the eccentric reducer on spec item level, the filter table must be created as shown in the next screen shot.

Picture 21

Detailed Workflows


The result of assigning this filter table assigned to the spec item is shown in the screen shot below.

Picture 22

The first four input fields are the basis for the filter. The filter only returns the exact matches.

The advantage for this process is the user can influence the filter results directly. For example, this method can be used if the prices for standard reducers are much lower than the prices for reducers with different schedule ends.

The disadvantage is that this process requires a bit more work.

Assign Branch Filter Table to spec Header Geometrics Branches require an additional filter method on top of the wall thickness filter. Because the different possible branches overlap in header/branch sizes, one specific branch must be preselected for each header/branch size combination. This is done with the branch table in SmartPlant Materials.

Detailed Workflows


Picture 23

The branch table in SmartPlant Materials is a predefined geometric table with a fixed format.

Beside the header and branch definition, the important fields are the commodity group and part fields. If a specification item with a Short Code field value mentioned in the spec header geometric branch table definition appears in the specification, only the idents pass through the filter that belong to the specified commodity group and part from branch table and the same nominal size combination defined in the branch table on INPUT_1 and INPUT_2.

If the ident has one nominal size and is a branch, INPUT_1 of ident will only be checked against the Dn Branch field of the branch table.

Important

• Branch tables in S.50.03 cannot be used with the wildcard short code value %.

Branch tables can only be assigned on spec header geometric level because they are valid for several different branch items.

Specification items that should be filtered by a branch table must all have the same short code.

The branch filter workflow in SmartPlant Materials S.50.06 is shown below.

Detailed Workflows


Assign the branch table to the spec header geometrics.

Picture 24

Detailed Workflows


Branch specifications items

Picture 25

Detailed Workflows


View the specification item idents for a reduced tee without branch filter

Picture 26

Detailed Workflows


View the specification item idents for a reduced tee with branch filter.

Picture 27

Detailed Workflows


The branch table data is also viewable through SmartPlant Materials standard reports, for example, in S.50.R.11.

Detailed Workflows


Create New Commodity Codes from the Piping Class

The following example explains how to create a commodity code on the fly when it is missing from the specification. In this example, a pipe component with material A107 is missing. The component itself as well as the required code list (Table Detail) entry needs to be created. The new component and commodity code can be created by duplicating an existing commodity code and modifying the data.

1. Click in the S 50.06. Specification Management screen to view Specification Items associated with the spec.

2. Under Specification Items, select the row you want to copy, and then click New

Record to add a row below it.

3. Copy the Short Code, Group, Part, and Commodity Code in the new row to insert a new component into the piping specification.

4. Click the Geometic tab.

5. Modify the From 1 and To 1 size ranges.

6. Click Save.

7. Double-click the Commodity Code..

Detailed Workflows


8. Copy the Commodity Code in S.30.01 Commodity Codes.

9. Select the row with the duplicated comodity code.

10. Select the P_MATERIAL row on the Details tab, and then change the property in the Detail column to C0.

11. Click Yes in the message box.

12. Type A107 in the Short Desc box

13. Click Build One Commodity.

14. Click Only CC in the Build the Commodity Code and Idents message box.

15. Click OK when the commodity code created message appears.

16. The Commodity Code box is updated with the new code.

Detailed Workflows


17. Copy the commodity code and paste it in the Commodity Code box of the new row on S.50.05 Specification Management Window 2.

18. Click Save.

19. Query for the new material entry in S.20.02 Tablenames and Details. The new material apppears.

20. Complete the code list details required for PDS.

Detailed Workflows


Standard Report S.50.R.11 Piping class Below the complete report S.50.R.11 is shown except the last page for the branch table.

SmartPlant Reference Data is very configurable. Because a predefined report can never be developed exactly matching these configurations, this report allows you to easily customize the content for most fields.

Detailed Workflows


In order to allow this report to show specific specification header table details or commodity code details, procedures (CIP) in the custom package M_PCK_S50R11_custom are available.

This document cannot function as a development guide for CIPs. Attached is an example how the customization for this report works.

The above screen shot from the specification report shows the “RATING” (the area highlighted green is the fixed programmed part that comes from the report definition itself) and the “CL300, ASME …” (the area highlighted in yellow that comes from the database definition for the specification BP_10S01).

The custom package receives the spec header id from the report as an input parameter. The spec header id is the SmartPlant Materials internal unique key for specifications.

Based on the spec_header_id, the function now can be programmed to find the valid value for “RATING” in the database.

Picture 28

Detailed Workflows


The screen shot above shows that the function has to search for the table “RATING_CLASS” in the database table “M_SPEC_HEADER_DETAILS.” The function has to transfer to the report the short description of the detected table detail as the return value.

Example function: FUNCTION GET_RATING (P_SPEC_HEADER_ID IN m_spec_header_details.spec_header_id%TYPE) return varchar2 is --daclaration of variables, using this the variable takes over the data type from the field, where it tetrieves later on the value from, This ensures the correct data type! p_get_rating m_table_detail_nls.SHORT_DESC%type -- PL/SQL Block begin -- This select statement selects the short desc into the return variable select tdn.short_desc into p_get_rating from m_table_detail_nls tdn, m_table_details td, m_spec_headers sh, m_spec_header_details shd, m_dict_tabs dt where tdn.nls_id=1 and tdn.td_id=td.td_id and td.td_id= shd.td_id and shd.td_tab_id=dt.tab_id and dt.table_name='RATING CLASS' and shd.spec_header_id=sh.spec_header_id and sh.spec_header_id=P_SPEC_HEADER_ID; /* return selection */ return p_get_rating; exception when no_data_found then return 'no data found in GET_rating'; end; --GET_RATING

smartplant materials how to create standard piping...

Documents