SmartPlant Reference Data How to Create Project Piping Classes Based on Standard Classes

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

Copyright Copyright © 2005-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

Table of Contents

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

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

How to Create Standard Piping Classes ..........................................................................6 Target Role ......................................................................................................................... 6 Session Goal ....................................................................................................................... 6 Workflow Prerequisites ...................................................................................................... 6 Budget Hours: Concept Transfer to Users .......................................................................... 6

Detailed Workflows ...........................................................................................................7 Simple Copy from Standard Classes ................................................................................... 7 Update from Modified Standard Classes ............................................................................ 9 Aggregation of Different Standard Classes ...................................................................... 11

SmartPlant Reference Data How to Create Project Piping Classes Based on Standard Classes 3

Preface

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

It describes the processes creating project piping classes based on standard classes.

Send documentation comments or suggestions to PPMdoc@intergraph.com.

4 SmartPlant Reference Data How to Create Project Piping Classes Based on Standard Classes

Overview

Overview This document describes the process of creating project pipe classes based on standard pipe classes.

Standard pipe classes are created in many companies as master copies for their project classes. This is done to allow the project to create classes easier and faster. It also allows the project to modify these classes to the project needs. The creation of the master classes in the product group can be done in different ways, described below:.

• Master spec in the product group contains ALL spec items. Projects can copy them and modify them to suit the projects needs ( i.e. comply with client standards or different national regulations). In this case, the spec contains the full list of required specification items such as pipe, flanges, fittings gaskets, bolts, compensators, and valves. The advantage of this method is the classes are complete and can be handled class by class as standard. For example, they can be used in the tender phase for estimation without any great effort. The problem is that in many cases the project classes do not comply with the standard class and many modifications are necessary. In the industry, valves and gaskets are responsible for most of the changes to the plant.

• To overcome the above mentioned problem, standard classes can be created as pipe and fitting classes, allowing problematic items such as valves, gaskets and compensators to be removed from the classes. To standardize the classes for those items, special valve, gasket, and compensator classes are created that fit to a wider range of classes. This allows you later in the project to aggregate the standard class+gasket class+valve class and filter the items that are actually needed.

SmartPlant Reference Data How to Create Project Piping Classes Based on Standard Classes 5

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 project piping classes based on standard classes.

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

Session Goal This session will enable users to understand the processes for creating piping classes based on standard 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 4-8 hours to train users in this workflow.

6 SmartPlant Reference Data How to Create Project Piping Classes Based on Standard Classes

Detailed Workflows

Detailed Workflows

Simple Copy from Standard Classes It is recommended to use a project specific specification type for the project specs. The advantage is that the standard specs do not interfere with the list of project specs.

You can also create new commodity codes from an existing piping class. For more information, see “Create New Commodity Codes from the Piping Class” in the How to Create Standard Piping Classes guide.

The spec type has to be created in S50.02. It is very important that the spec type structures in this screen are filled with those spec types contained in the master specs. In this example “PROJECT_BP.”

Picture 1

The copy job is started in screen S5005 Spec Copy.

After selection of the spec type, the first block allows you to create a new specification code that can be filled by the copy job. The first block can also be used to query for an existing spec which that can be updated or added by the copy job. Save the record in the first block before switching to the second block.

The second block allows selection of a source specification. The content of the source identified in the second block is copied into the spec identified in the first block.

SmartPlant Reference Data How to Create Project Piping Classes Based on Standard Classes 7

Detailed Workflows

Picture 2

As mentioned above, the second block is defining the source specification. Copy actions for individual items of the spec can be changed using the drop down lists for each field.

Picture 3

8 SmartPlant Reference Data How to Create Project Piping Classes Based on Standard Classes

Detailed Workflows

If a destination spec is empty, only the insert is possible and will be done if ‘both’ is selected.

The field “Comm Code” shown in Picture 3 does NOT control copy actions for the commodity codes of the spec items! It only copies spec item details used for the specification dependent commodity code creation. The use of this functionality is not part of this document.

The copy function is started by commodity code of the actual record. After copy is complete, the record is saved and can be queried. To start the copy job again, an update in the second block is necessary: for example, any character is inserted into the “comment” field and saved.

Update from Modified Standard Classes If the standard specification has to be modified and this class has been used previously as a copy source for project specs, the copied specification can be updated with the new entries from the source.

Source specification

Picture 4

SmartPlant Reference Data How to Create Project Piping Classes Based on Standard Classes 9

Detailed Workflows

Copied Specification

Picture 5

Modified Source Specification

Picture 6

10 SmartPlant Reference Data How to Create Project Piping Classes Based on Standard Classes

Detailed Workflows

Modified Destination Specification

Picture 7

Spec line item updates occur based on a reference is stored for each item in the copy record. The relationship between the original and copied item is available for subsequent updates.

If this information is not present because the specification has been copied before the introduction of this feature, you can use the checkbox “Use Order Seq” in S.50.05 and use the field “Order Seq” (S.50.06) to select the correct specification item for update. This requires the field “Order Seq” to be unique in the destination specification. If the checkbox is checked, the database relation is not used even it exists!

Aggregation of Different Standard Classes As mentioned in the overview section of this document, standard classes can be created as pipe and fitting classes, valve classes, and gasket classes. The copy functionality allows you to combine those classes into one project class.

A small standard class for pipe and fittings was shown in the previous examples.

SmartPlant Reference Data How to Create Project Piping Classes Based on Standard Classes 11

Detailed Workflows

The following shows an example for a standard valve class.

Picture 8

The following shows an example for a standard gasket class

Picture 9

Using screen S5005, these classes can be aggregated into the project class by creating several copy records for the same destination spec. Screen S50.05 only shows one record at the time, the following shows a query of the List of Values (LOV) that displays three source spec records.

12 SmartPlant Reference Data How to Create Project Piping Classes Based on Standard Classes

Detailed Workflows

Picture 10

SmartPlant Reference Data How to Create Project Piping Classes Based on Standard Classes 13

Detailed Workflows

The copy job has to be started for each record. Results are shown below:

Picture 11

14 SmartPlant Reference Data How to Create Project Piping Classes Based on Standard Classes