PDS_Project_Administrator_PD_Project.pdf

Plant Design System (PDS) Project Administrator (PD_Project)

Version 2010 (V11) Wednesday, November 17, 2010 DPDS3-PB-200030G

Copyright Copyright © 1984-2010 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 from Intergraph Corporation.

U.S. Government Restricted Rights Legend Use, duplication, or disclosure by the government is subject to restrictions as set forth below. For civilian agencies: This was developed at private expense and is "restricted computer software" submitted with restricted rights in accordance with subparagraphs (a) through (d) of the Commercial Computer Software - Restricted Rights clause at 52.227-19 of the Federal Acquisition Regulations ("FAR") and its successors, and is unpublished and all rights are reserved under the copyright laws of the United States. For units of the Department of Defense ("DoD"): This is "commercial computer software" as defined at DFARS 252.227-7014 and the rights of the Government are as specified at DFARS 227.7202-3. Unpublished - rights reserved under the copyright laws of the United States. Intergraph Corporation P.O. Box 240000 Huntsville, AL 35813 Street address: 170 Graphics Drive, Madison, AL 35758

Terms of Use Use of this software product is subject to the End User License Agreement ("EULA") delivered with this software product unless the licensee has a valid signed license for this software product with Intergraph Corporation. If the licensee has a valid signed license for this software product with Intergraph Corporation, the valid signed license shall take precedence and govern the use of this software product. Subject to the terms contained within the applicable license agreement, Intergraph Corporation gives licensee permission to print a reasonable number of copies of the documentation as defined in the applicable license agreement and delivered with the software product for licensee's internal, non-commercial use. The documentation may not be printed for resale or redistribution.

Warranties and Liabilities All warranties given by Intergraph Corporation about equipment or software are set forth in the EULA provided with the software or applicable license for the software product signed by Intergraph Corporation, 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, FrameWorks, I-Convert, I-Export, I-Sketch, SmartMarine, IntelliShip, INtools, ISOGEN, MARIAN, SmartSketch, SPOOLGEN, SupportManager, and SupportModeler are trademarks or registered trademarks of Intergraph Corporation or its subsidiaries in the United States and other countries. Microsoft and Windows are registered trademarks of Microsoft Corporation. Oracle, JD Edwards, PeopleSoft, and Retek are registered trademarks of Oracle Corporation and/or its affiliates. MicroStation is a registered trademark of Bentley Systems Inc, all rights reserved. Other brands and product names are trademarks of their respective owners.

Contents Preface PDS ................................................................................................................................................. 7 What's New in Project Administrator (PD_Project) ................................................................................. 8 Introduction .................................................................................................................................................. 9 PDS Overview ......................................................................................................................................... 9 Project Setup .................................................................................................................................. 10 Preliminary Design ......................................................................................................................... 12 Detailed Design - 2D ...................................................................................................................... 13 Detailed Design - 3D ...................................................................................................................... 14 Project Organization ....................................................................................................................... 22 Project Administrator Overview ...................................................................................................... 22 System Setup ................................................................................................................................. 24 System Configurations ................................................................................................................... 24 Loading Products............................................................................................................................ 25 Database Information ..................................................................................................................... 31 Preparing the Server and Workstations for PDS ............................................................................ 32 PDS Environment ...................................................................................................................................... 33 PD Shell ................................................................................................................................................ 33 PD_Shell Form Conventions .......................................................................................................... 35 Common Tools on the PD_Shell Forms ......................................................................................... 36 Batch Processes........................................................................................................................................ 41 Project Administrator ................................................................................................................................ 43 Project Setup Manager.............................................................................................................................. 45 Create Project ....................................................................................................................................... 46 Project Control Schema.................................................................................................................. 48 FrameWorks Plus Project ............................................................................................................... 49 Raceway Project Schema .............................................................................................................. 51 Piping Design Schema ................................................................................................................... 51 Piping RDB Schema ....................................................................................................................... 56 Raceway RDB Schema .................................................................................................................. 56 Specify Coordinate System ............................................................................................................ 56 Revise Project - Attribute Display ......................................................................................................... 58 Revise Project - Add Attributes ............................................................................................................. 60 Revise Project - DBAccess ................................................................................................................... 62 Delete Project Information .................................................................................................................... 65 Delete Reference Data ................................................................................................................... 67 Site Administrator .................................................................................................................................. 69 Create Site ...................................................................................................................................... 70 Revise Site ..................................................................................................................................... 71 Delete Site ...................................................................................................................................... 72 Insert FrameWorks Data ....................................................................................................................... 73 Insert Electrical Raceway Data ............................................................................................................. 75

Plant Design System (PDS) Project Administrator (PD_Project)

3

Contents Insert ModelDraft Data .......................................................................................................................... 76 Project Environment Manager ................................................................................................................. 81 Project Environment Manager Form ..................................................................................................... 82 Create Options Form ............................................................................................................................ 84 Create Discipline Data .................................................................................................................... 85 Create Design Area Data ............................................................................................................... 86 Create Model .................................................................................................................................. 86 Model Setup Data Form ................................................................................................................. 91 Copy Model .................................................................................................................................... 93 Create Database Tables ..................................................................................................................... 101 Create Model Data from ASCII File .............................................................................................. 102 Revise Options Form .......................................................................................................................... 106 Revise Project Data ...................................................................................................................... 107 Revise Project Location ................................................................................................................ 108 Revise Discipline Data ........................................................................................................................ 120 Revise Model Data ....................................................................................................................... 121 Revise Area Model Association .................................................................................................... 122 Revise Site ID for Models ............................................................................................................. 124 Delete Options Form ........................................................................................................................... 127 Delete Discipline ........................................................................................................................... 128 Delete Design Area Form ............................................................................................................. 130 Delete Model ................................................................................................................................ 131 Report Options Form .......................................................................................................................... 132 Report - Models ............................................................................................................................ 133 Report - Named Items .................................................................................................................. 135 Create Design Area Data......................................................................................................................... 139 Create Design Area Data Form .......................................................................................................... 139 Revise Design Area Data.................................................................................................................... 141 Project Data Manager .............................................................................................................................. 145 Project Data Manager Form................................................................................................................ 145 Seed Options Form ...................................................................................................................... 146 Model ............................................................................................................................................ 237 Equipment .................................................................................................................................... 244 Raceway Model ............................................................................................................................ 248 Drawing ........................................................................................................................................ 249 Interference .................................................................................................................................. 253 Project Control Manager ......................................................................................................................... 257 Project Control Manager Form............................................................................................................ 257 Report Format Form (Project Administrator) ................................................................................ 262 Report Discrimination Data Form ................................................................................................. 266 Report Form (Project Administrator) ............................................................................................ 270 Report Management Defaults Form (Project Administrator) ........................................................ 278 Package ........................................................................................................................................ 280 Project Search Criteria (Project Administrator) ............................................................................ 285

4

Plant Design System (PDS) Project Administrator (PD_Project)

Contents Project Archival Manager ....................................................................................................................... 289 Project Archival Manager Form .......................................................................................................... 289 Project Archival............................................................................................................................. 291 Scheduled Project Archival .......................................................................................................... 309 Active Project Retrieval ................................................................................................................ 317 Inactive Project Retrieval .............................................................................................................. 320 Model/Drawing Data Retrieval for Workshare Projects ...................................................................... 327 Import Project Retrieval ................................................................................................................ 328 Schedule Project Import ............................................................................................................... 334 Model/Drawing Import for Workshare Projects ................................................................................... 338 System Manager ...................................................................................................................................... 341 Edit Project Directory File ................................................................................................................... 342 Manage Project Directory File............................................................................................................. 343 Create Project Directory File ............................................................................................................... 345 File Lock Manager ................................................................................................................................... 347 Access Control Manager ........................................................................................................................ 351 Access Control Manager Password Form .......................................................................................... 351 Access Control Files ........................................................................................................................... 356 Authorization Data .............................................................................................................................. 357 User Functions .................................................................................................................................... 363 Export to PDME ....................................................................................................................................... 365 Export to PDME Command Configuration File ................................................................................... 368 Overwrite /Regenerate Intermediate File ............................................................................................ 369 P&I Drawings ...................................................................................................................................... 370 PFD ..................................................................................................................................................... 371 IDM ...................................................................................................................................................... 373 Orthographic Drawings ....................................................................................................................... 374 Isometric Drawings ............................................................................................................................. 376 Structural Drawings ............................................................................................................................. 378 MTO Reports....................................................................................................................................... 379 DesignReview Sessions ..................................................................................................................... 380 Document Types ................................................................................................................................. 381 PDS/PDME Document Index Format ................................................................................................. 382 Upgrading Existing Projects .................................................................................................................. 395 6.0/6.1 to 6.3 Update Process ............................................................................................................ 397 5.* to 6.0 Update Process ................................................................................................................... 399 4.3 to 5.0 Update Process .................................................................................................................. 402 4.2 Update Process ............................................................................................................................ 408 4.1 Update Process ............................................................................................................................ 410 Index ......................................................................................................................................................... 413

Plant Design System (PDS) Project Administrator (PD_Project)

5

Contents

6

Plant Design System (PDS) Project Administrator (PD_Project)

Preface PDS This document provides command reference information and procedural instructions for the Plant Design System (PDS) Project Administrator (PD_Project) task.

List of PDS Documentation                             

DPDS3-PB-200003 - DesignReview Integrator (PD_Review) Reference Guide DPDS3-PB-200004 - Drawing Manager (PD_Draw) User's Guide DPDS3-PB-200005 - EE Raceway Modeling Reference Guide DPDS3-PB-200006 - Interference Checker/Manager (PD_Clash) User's Guide DPDS3-PB-200010 - PDS 3D Theory User's Guide DPDS3-PB-200013 - PDS EDEN Interface Reference Guide Volume I : Piping DPDS3-PB-200015 - PDS Equipment Modeling (PD_EQP) User's Guide DPDS3-PB-200017 - PDS ISOGEN Reference Guide, Vol. 1 DPDS3-PB-200022 - PDS Piping Component Data Reference Guide DPDS3-PB-200023 - PDS Project Setup Technical Reference DPDS3-PB-200025 - PDS Stress Analysis Interface (PD_Stress) User's Guide DPDS3-PB-200026 - Pipe Supports Modeler Reference Guide DPDS3-PB-200028 - Piping Design Graphics (PD_Design) Reference Guide DPDS3-PB-200030 - Project Administrator (PD_Project) Reference Guide DPDS3-PB-200033 - Project Engineer HVAC (PE-HVAC) Reference Guide DPDS3-PB-200034 - Reference Data Manager (PD_Data) Reference Guide DPDS3-PB-200035 - Report Manager (PD_Report) User's Guide DPDS3-PB-200041 - PDS EDEN Interface Reference Guide Volume 2 : Equipment DPDS3-PB-200042 - PDS EDEN Interface Reference Guide Volume 3 : Pipe Supports DPDS3-PE-200016 - PDS Express Project Creation Quick Start Guide DPDS3-PE-200052 - PDS Ortho Draw User's Guide DPDS3-PE-200029 - Piping Model Builder (PD_Model) Reference Guide DPDS3-PE-200031 - Project Engineer HVAC Getting Started Guide DPDS3-PE-200032 - Project Engineer HVAC Overview DPDS3-PE-200045 - PDS Label Library Merger Utility DPDS3-PE-200047 - PDS Reference Data Auditing Tool DPDS3-PE-200048 - Pipe Supports Explorer Utility DPDS3-PE-200050 - Batch Services Quick Start Guide DPDS3-PE-200051 - Batch Services User's Guide

Plant Design System (PDS) Project Administrator (PD_Project)

7

Preface PDS

What's New in Project Administrator (PD_Project) The following changes have been made to Project Administrator. Version 2010 (11.0)  Added a new topic, Export to PDME Command Configuration File, to assist with exporting. (P4 PB:101336)  A new control called Spacing Between Name Label and Coordinate Label has been added to the Project Data Manager > Seed > Revise Drawing Data > Miscellaneous Label Data form. Use this control to define the spacing factor between two name labels or between a name label and a coordinate label. This value is multiplied by the text height to determine the line spacing between the coordinate label and the name label. (P2 PB:53029)  Insulation Envelope graphic symbology has been added to the Project Data Manager > Equipment Model > Revise Equipment Data > Graphic Symbology > Envelopes. (P2 PB:54531)  The logged-in user must have administrator privileges to upgrade a project. (P2 PB:79475)  A new utility, ChkDgnv7, can be used to find any MicroStation V8 design files in a project. After running the utility, an ASCII-based log file is generated at a user-defined location. The log file provides a report on files contained in the project. You can then remove the MicroStation V8 files from the project. (P1 PB:67644)  Documented in INTERGRAPH_OPTIONS_BLOCK (30) that "In PDS reference data, a reinforcing weld (RWeld) is defined as a component; however, ISOGEN software treats an Rweld the same as other welds included as part of a pipe. Therefore, an Rweld will not appear separately in the MTO on the face of the isometric drawing." (P3 PB: 109277)  Documented the regeneration utility for scheduled incremental import of FWP models. (P3 PB: 79329)

8

Plant Design System (PDS) Project Administrator (PD_Project)

SECTION 1

Introduction Welcome to the Project Administrator (PD_Project) module of the Plant Design System of software. Intergraph's plant design software can be used to design any type of plant, from petrochemical plants, offshore platforms, chemical and pharmaceutical plants, consumer products (food, beverages, cosmetics, soap, paper, and so forth), to power plants, waste water treatment plants, and cogeneration facilities. Specifically, the Plant Design System (PDS) integrates many discipline-specific software modules; these modules automate the many phases of a plant design project. Project Administrator (PD_Project) is one of these modules.

For more information, see PDS Overview (on page 9) Project Setup (on page 10) Preliminary Design (on page 12) Detailed Design - 2D (on page 13) Detailed Design - 3D (on page 14) Project Organization (on page 22) Project Administrator Overview (on page 22) System Setup (on page 24) Database Information (on page 31) Preparing the Server and Workstations for PDS (on page 32)

PDS Overview Designing a plant with the Intergraph plant design modular software system comprises four phases: Project Setup - 2D and 3D design files, project files, and databases. Preliminary Design - feasibility studies, cost estimates, general layouts, and process flow diagrams. Detailed Design - process, instrumentation, piping layouts, and material control.

Plant Design System (PDS) Project Administrator (PD_Project)

9

Introduction Design Review - 3D model walk-through.

Project Setup Before work can begin on a project, extensive system setup needs to be completed. The following outlines the basic flow for initial system setup and project creation. This system and project setup is usually done by the system manager. Once the project has been set up, other tasks are done by the designer.

10

Plant Design System (PDS) Project Administrator (PD_Project)

Introduction System Setup PDS can run either standalone on a workstation or configured in a server/client relationship. Due to the size and scope of PDS projects, most companies use a server/client relationship. A PDS server can act as a database server, a file server, and/or a product server. Network File System (NFS) is a program that accesses files on the server for processing on the client computers. PDS uses relational databases to store information about virtually all aspects of the project, including  Project data, such as file names and locations.  Reference data, such as piping commodity descriptions.  Design data, such as temperature and pressure values that are associated with graphic elements. The PDS products attach to the relational databases through the Relational Interface Software (RIS) program. RIS supports popular Relational Database Management Systems, such as Oracle and Microsoft SQL Server.

2D Setup The PDS2D product is the base platform loaded on each computer that will be using PDS 2D application software, such as P&ID, PFD, and IDM. PDS2D is the interface to the PDS 2D application product line. It can be either loaded with the client option to access software on a product server or installed locally. PDS2D enables you to perform project administrative functions. These functions include tasks such as establishing and modifying reference data files, projects, units, and drawings. A 2D project uses two database schemas.  A project control database.  A design database.

Plant Design System (PDS) Project Administrator (PD_Project)

11

Introduction The projcreate utility creates the schema information for the installed database. Once the database files have been created, you can access the 2D environment to create units and drawings for the project. Units are logical divisions of the schematic world of a plant.

3D Setup The PD_Shell product is loaded on each computer that will be using the PDS 3D products. Other PDS 3D products can be either loaded on the computer using the client option or installed locally. A 3D project uses three database schemas.  A project control database.  A material/reference database.  A design database. The 2D and 3D project share a common project control database. The Project Administrator module enables you to create the database files, seed files, and project environment files. A 3D project is divided into design areas by disciplines. Disciplines represent the various 3D modeling applications (such as Piping, Equipment, and HVAC). A design area represents a specific volume of the project for a given discipline. Each design area comprises a set of models that contain the actual design data.

Preliminary Design Process Flow Diagram (PFD)

Conceptual design of a plant includes feasibility studies, cost estimates, and process simulations. Third-party process simulation packages such as ASPEN or SimSci allow engineers to perform preliminary calculations such as chemical equilibriums, reactions, heat and material balances, and/or design pressures and temperatures. The data produced from these calculations is transferred to PDS where a process flow diagram (PFD) is developed.

12

Plant Design System (PDS) Project Administrator (PD_Project)

Introduction

Detailed Design - 2D Process & Instrumentation Diagram (P&ID)

Equipment, instrumentation, and piping schematics are drawn from process flow data using the Process & Instrumentation Diagrams (P&ID) product. The P&IDs display the overall process in much greater detail than the PFD. The P&ID shows all piping, instrumentation, and controls that are associated with a specific process area, as well as all process vessels, pumps, motors, and so forth. The P&ID identifies the types of instrumentation and controls that are required by the process and assigns tag numbers to each instrument item. The P&ID reflects the overall process control through either distributive control systems (DCS), programmable logic controllers (PLC), or stand-alone controller philosophy. When taking graphic information from the drawing and writing it to the database (propagating), the drawing is checked for conformance to design rules as the drawing information is loaded into a relational database. Once the drawing conforms to the design rules, the drawing information can be posted to a master database. The reference database (RDB) includes files such as cell libraries, report definitions, database definitions, and label formats that support actions performed during the design creation task. The RDB supports the international engineering standards of the American National Standards Institute (ANSI) and the Deutsche Institut fur Normung (DIN).

Instrument Data Manager (IDM) After the P&ID defines the process controls, you must define the individual data values for all of the instruments. The Instrument Data Manager (IDM) program is a database that maintains an occurrence for each instrument in a project. IDM receives instrument data, either from the P&ID or through manual input, and produces reports for instrumentation specification and design. The instrument task provides consistency checks and reports on the items that do not conform to the standards or the design rules. The instrument specification reports are prepared in accordance with the Instrumentation Society of America (ISA) standards.

Plant Design System (PDS) Project Administrator (PD_Project)

13

Introduction

Detailed Design - 3D Equipment Modeling (PD_EQP)

Equipment Modeling (PD_EQP) enables designers to model the equipment defined in the P&ID. Stylistic representations of equipment items are produced, with or without nozzles, by entering data from equipment data sheets noting dimensions and weights. Upon completion, the equipment item is placed in the 3D model. Within PD_EQP, designers can create a physical envelope that defines the space occupied by an equipment item along with space envelopes that define maintenance and access areas. This process is instrumental for interference checking later in the modeling process.

14

Plant Design System (PDS) Project Administrator (PD_Project)

Introduction FrameWorks Plus (FW+)

Structures must be designed to carry the loads from piping, equipment, personnel, and other factors to the ground. FrameWorks Plus is used to lay out structural frames, foundations, slabs, and walls. Piping designers, equipment modelers, and structural designers, by sharing reference files, can see the location of each other's objects. The structural engineer referencing other models can place loads in the 3D model and apply other analytical characteristics to use with a third-party analysis solver. After a design run, the new cross-section properties can be read back into the model to automatically update all the associated symbolized 2D drawings. Other outputs can be obtained from the data model, such as material lists, output to third-party steel detailing programs, interference envelopes, and graphic and non-graphic data made available to the rendering and walk-through products such as SmartPlant Review.

Piping Design Graphics (PD_Design)

Plant Design System (PDS) Project Administrator (PD_Project)

15

Introduction PD_Design enables designers to create a 3D model of the piping and in-line instruments defined in the P&ID by routing the pipelines through space. When placing the instruments and valves, designers must consider pipeline flexibility, method of construction, and ease of access for maintenance and operations. Designers can route pipe in the 3D model as a centerline representation; moreover, a 3D shaded model can be displayed when necessary. The centerline is intelligent and contains all the information that relates to a pipeline, such as the piping material class, nominal diameter, fluid code, insulation parameters, temperatures and pressures, and so forth. The alphanumeric data required for each pipeline can be entered interactively or transferred from the P&ID. This can be done as the pipe is routed, or it can be added or revised later. A pipeline can be connected to a specific nozzle or routed from a point in space. Components such as valves, instruments, and branches can be placed on the pipeline as it is routed. Values for the alphanumeric data-such as line sequence number, nominal diameter, material class, temperatures and pressures-can be set during routing. Interactive design checks are performed for each component placement. These checks ensure matching or compatible diameters, pressure ratings, end preparations, and other consistency criteria. Pipe supports can be modeled giving either a detailed space envelope or a logical representation of the function of the support, such as an anchor, spring, or guide.

Reference Data Manager (PD_Data) Placement of the piping components is driven by the specification. The reference data provides the selection criteria for the piping commodity items that are found in the piping job specification and the piping commodity libraries that are delivered with the product. This data is contained in the RDB and can be used by other projects. The Reference Data Manager (PD_Data) is specifically designed to define and modify the reference data for the PDS 3D modules. This reference data ensures consistency in the definition of piping specifications and commodity libraries. It is used to control and standardize the PDS 3D modules to reflect company practices and standards.

16

Plant Design System (PDS) Project Administrator (PD_Project)

Introduction Drawing Manager (PD_Draw)

Designers use the Drawing Manager (PD_Draw) product to create and/or revise orthographic production drawings. PD_Draw can be used with other PDS 3D products to place annotation labels that identify intelligent items and model coordinates, to plot the drawings, and to produce reports for drawings and model data.

PDS Stress Analysis Interface (PD_Stress)

The stress analyst uses the PDS Stress Analysis Interface (PD_Stress) product to generate a neutral file from the 3D piping and equipment models for stress analysis. PD_Stress interfaces to a number of commercial packages that accept ASCII format.

Plant Design System (PDS) Project Administrator (PD_Project)

17

Introduction Interference Checker/Manager (PD_Clash)

Interference Checker/Manager (PD_Clash) creates envelope files for all models in the specified project, design area, or for individual models that have an envelope builder that is specific to each discipline in the Interference Checker/Manager. It also collects envelope data for the models that have envelope files that were previously created by one of the other PDS modules. The checker/manager processes the specified design volume and identifies all of the interference clashes. It then produces reports that allow the designer to review interferences and review and/or revise the approval status of the interferences. The software places graphical markers for the project, produces plots of clashes, and produces an interference report file.

PDS Isometric Interface (PD_ISO, PD_ISOGEN)

PDS Isometric Interface (PD_ISO, PD_ISOGEN) enables designers to extract isometric drawings from the plant model, either interactively or through a batch process. The interactive extraction can be used for testing the interface and verifying a specific pipeline. Batch generation of isometrics is used for generating production drawings on a project. With either function, a bill of materials is automatically generated and attached to the isometric drawing. An optional MTO file can be generated which can be printed or used as input to the material control system.

18

Plant Design System (PDS) Project Administrator (PD_Project)

Introduction Report Manager (PD_Report)

You can generate material take-off reports (MTOs) on piping and equipment models with the PD_Report program. The MTO process generates reports by using the graphical data in the specified models to refer to the design database, reference database, project database, and material description libraries for the data on which to report. This data includes implied materials, such as bolts, gaskets, and welds, that are not represented in the model but are necessary for the specified connectivity. PD_Report also maintains the data that defines the format, content and approval status of the reports.

Project Engineer HVAC (PE-HVAC)

Plant Design System (PDS) Project Administrator (PD_Project)

19

Introduction PE-HVAC enables designers to place fittings and devices while laying out duct routes. You can define the active parameters for duct characteristics such as width, depth, shape, material, construction status, and service.

EE Raceway Modeling

Electrical Engineer Raceway Modeling (EERWAY) enables designers to extract data from the RDB and create a 3D model using the centerline and/or three-line component graphics. With this 3D model, you can create interference envelopes and run interference detection, produce MTOs, and extract raceway drawings.

20

Plant Design System (PDS) Project Administrator (PD_Project)

Introduction Design Review Integrator (PD_Review) The PD_Review interface provides an intelligent link to Intergraph's SmartPlant Review package. You can use SmartPlant Review to walk through a PDS model-in full shaded mode-and review the design and alphanumeric data.

Engineering data, such as instrument numbers, equipment numbers, line numbers, and line sizes, is available when walking through the model. Comments are stored in a separate tag file and can be accessed later during the review session. On subsequent walk-throughs, the original comment can be reviewed along with the responsible designer's actions. Also with SmartPlant Review, the model can be used to train operations and maintenance personnel before or after the plant is constructed. SmartPlant Review is not included in the PDS package and must be purchased separately.

Plant Design System (PDS) Project Administrator (PD_Project)

21

Introduction

Project Organization Because a process plant can be extremely large, PDS uses the following organization to break the plant into smaller pieces that can be handled more easily. A project is a convenient grouping of either all or part of the items that constitute a plant. The project is the fundamental structure for working in PDS. Each project contains all of the information that is required to work in a PDS task. A project and all of its accompanying files must be defined with the Project Administrator before you can use any of the other PDS 3D modules. The Project Administrator controls the creation and modification of Piping projects. Each Piping project consists of a project control database, project design database, piping and equipment models, reference models (structural, HVAC, and electrical raceway), a set of drawings, and a collection of reference data. The reference data can be specific to one project, or it can be shared by more than one project. A model corresponds to a 3D design volume. The design volume is a subdivision of the plant based on work responsibility, completion of schedules, and computer response time. The location of a design volume and the details of the Design Volume Coordinate System are specified as reference data in the project definition. The model is created at full scale and is only scaled to produce drawings. A drawing is produced from the model. Although drawings can be created at different scales, they all use the actual model graphics to avoid discrepancies with the model. Each model represents a unique partition of the design database. This enables you to access all the data for a single model (independently of the other project data) for the purpose of creating or modifying information. You can also perform interference checking and create reports based on data from all the models in a project.

Project Administrator Overview The Project Administrator (PD_Project) module enables you to define project data and create project files including database files, design files, seed files, and reports. It is specifically designed to support the creation and revision of project data for use by other PDS 3D modules. For more information, see: Upgrading Existing Projects (on page 395) Project Administrator contains the following basic components:

Project Environment Manager The Project Environment Manager component creates, revises, and deletes disciplines, design areas, and model files; revises the project/client information; revises the disk location of a project or file; and creates a report of information in the project control database. The Project Control Database contains information that relates to every aspect of a project.

Project Data Manager Each project contains seed files that are used when creating a project, a design area, a model design volume, or a drawing file. The Project Data Manager enables you to revise these seed files or similar data in existing model, drawing, and envelope files. This data includes settings for the following basic information:  Definition of coordinate systems and volumes.  Definition of physical units.  Formats for coordinate labels and other annotation graphics.  Formats for message displays such as coordinate readout.  Graphic symbology for each model and drawing category.

22

Plant Design System (PDS) Project Administrator (PD_Project)

Introduction      

Graphic symbology for non-component graphics. Tables of hard and soft compatibility parameters. Tolerance values for design checks, interference detection, and segment and pipe length thresholds. Tables for end preparation and pressure ratings. Names of specific files and tables for component placement and material take-off. Selection of approved or unapproved RDB data for the project or model.

Project Setup Manager The Project Setup Manager component enables you to create a new project or delete an existing project. You must create a project before you can access any of the other PDS 3D activities. When you create a project, the system creates the associated database schemas for use in storing and accessing the project control data, design data, and reference data.

Project Control Manager The Project Control Manager component enables you to create a package of project documents for use in revision control. A package can include any of the documents that are associated with a project, such as isometric drawings, orthographic drawings, and reports. You can define package information in the project control database and report on this information for revision control.

Project Archival Manager The Project Archival Manager component enables you to back up a complete project or a subset of the project files. You can also retrieve all or part of an archived project.

System Manager The System Manager component enables you to revise the project directory file. The project directory file contains the names and locations of all the projects on the network.

File Lock Manager The File Lock Manager enables you to unlock files that are currently locked by another user or process.

Access Control Manager The Access Control Manager provides the PDS system manager with the ability to restrict the end user's access to data on the basis of the project number, the type of data, and privileges assigned to the user.

Export to PDME The Export to PDME prepares a data set that consists of user-defined documents and a document index for import into the Plant Data Management Environment (PDME™).

Plant Design System (PDS) Project Administrator (PD_Project)

23

Introduction

System Setup This section describes the basics steps for setting up the PDS 3D workstation products. The majority of the work is required for the initial setup of a server and workstations to run the PDS 3D products. Once this setup has been completed, you can easily add new projects.

Refer to the PDS Project Setup Technical Reference for detailed information on the initial setup of a PDS system. If you are already running a PDS project, you can skip this information. Refer to Upgrading Existing Projects (on page 395), for information on upgrading an existing project for use with the 6.0 version of PDS.

See Also System Configurations (on page 24) Loading Products (on page 25)

System Configurations This section outlines the system hardware and software considerations required to support PDS. PDS can run either standalone on a workstation or configured in a client/server relationship. Due to the size and scope of PDS projects, most companies use a client/server relationship.

Servers PDS uses the following types of servers based on logical functions: Database Server - This is the location of the relational database files. All database files are created and stored on this machine. Software Server - This is the location of the PDS application products. By using a software server, you can load all the PDS software in a central location and have individual workstations access the software through Network File System (NFS) software. File Server - This is the central location used to store project files such as reference data libraries, seed files, model files, drawings, and reports. Compute Server - This is the location for processing compute-intensive activities such as interference checking and hidden-line removal.

24

Plant Design System (PDS) Project Administrator (PD_Project)

Introduction Depending on your system requirements, you can designate one server to perform all of these duties, or you can split them across multiple machines.

Workstations A client is a node (usually a workstation) that accesses data or performs a function on the remote resource (usually a server). In most PDS configurations, the files reside on the server, and processing takes place on the client workstation.

Loading Products You should load the appropriate PDS products and their prerequisites to the server(s) and workstation(s) that are to be used on your network.

See Also Loading Baseline Software (on page 26) Loading PDS Products (on page 26) Loading Database Products (on page 31)

Plant Design System (PDS) Project Administrator (PD_Project)

25

Introduction

Lo a d in g Ba s e lin e S o ftwa re Windows Baseline PDS requires the standard Microsoft baseline products as well as all of the following specific products:  Baseline software including Microsoft Windows and service packs (contact Intergraph support or check web pages for current recommendations).  TCPIP protocol.  SmartPlant License Manager.  MicroStation J. MicroStation must be loaded before loading Iplot or any of the PDS products.  RIS_share - The RIS client software.  Interplot Products - Iplot client is mandatory. Iplot server may be required depending on the plotter configuration.  Batch Services

Lo a d in g P DS P ro d u c ts The PDS application software can be loaded on the local workstations or loaded on a server and accessed remotely through the network. You should load the most heavily used products locally and access the remainder of the products remotely. The only PDS products required to exist on local workstations are PD_SHELL and SmartPlant License Manager. The remaining PDS products can be loaded on a server or on a local workstation.

Advantages and Disadvantages of Remote Access Accessing the PDS products remotely makes system maintenance easier. You can upgrade to the latest version of software by upgrading the server. Accessing the PDS products remotely introduces performance sacrifices at initialization.

PDS 3D Installation Options The product installation procedures for each of the PDS 3D products provide the following download options: Local (default) - The complete product is downloaded to the applicable workstation, and the applicable batch queues are created automatically. Client - The system prompts for the software server node to be used for the executable software to conserve disk space on the client workstation. The applicable batch queues are created automatically in the same manner as for the local option. Server - This option is the same as the local option. MicroStation is not required on the software server.

PDS Products Load the following PDS products on the software server and PDS workstations using one of the options described above. To set up a software server for use by a set of client workstations, all of the following products should be installed using the server option: SmartPlant License Manager - This product controls access to the PDS products. It is required on all PDS workstations.

26

Plant Design System (PDS) Project Administrator (PD_Project)

Introduction PD_Shell - This product controls execution of all other PDS 3D products. This product is required on all PDS workstations and must be installed with the local option. PD_Project (Project Administrator) - The system creates the following Batch Queues: PDarchival, PDcreate_model, PDcopy_model, PDdelete_model, PDprojec_report, and PDproject_data. PD_Data (Reference Data Manager) - The system creates an Batch Queue named PDreference. PD_Design (Piping Designer) - The system creates the following Batch Queues: PDapproval_mgr, PDdb_verify, PDdesign_checks, and PDpid_report. PD_Draw (Drawing Manager) - The system creates the following Batch Queues: PDhline, PDplot, and PDcreate_dwg. PD_Review (DesignReview Integrator) - The system creates an Batch Queue named PDlabel_builder. PD_Clash (Interference Manager) - The system creates the following Batch Queues: PDclash_checker and PDclash_server. PD_Report (Report Manager) - The system creates a Batch Queue named PDreport. PD_EQP (Equipment Modeling) - The system creates the following Batch Queues: PDloadeqp and PDeqp_report. PD_ISO (ISO Extraction Interface) - The system creates the following Batch Queues: PDisocreate and PDisoplot. RD_USRDB (U.S. Practice Reference Database) RD_DINRDB (DIN Reference Database) VHL (Vector Hidden Line Manager) PDS2D (PDS 2D Applications) - The system creates an Batch Queue named PDS2DQUEUE. SmartPlant P&ID Integration Tools - If SmartPlant P&ID is not loaded on the computer, the system loads the tools necessary for transferring data from SmartPlant P&ID to PDS 3D.

Using the Client Option For each of the products loaded with the client option, the system prompts for the node name of the PDS software server and the file path for the product directory (such as c:\win32app\ingr\pddesign) on the software server. Note: The system adds an entry to the registry with the provided information.

Loading PDS for Windows 1. Log in to the computer as a domain user with local administrator rights. 2. Perform pre-installation tasks, "PDS and Windows" and "PDS Environment Variables" in PDS Project Setup Technical Reference guide for registry and environment variable setup information. 3. Install Microstation J, SmartPlant License Manager, RIS, Batch Services, and PDS.

Plant Design System (PDS) Project Administrator (PD_Project)

27

Introduction 4. When you start the PDS component loader, you are prompted to enter your name and serial number.

If you have purchased FrameWorks Plus or PDS PID Standalone separately from PDS, then you should have a FrameWorks Plus or PDS PID Standalone serial number that is separate from the PDS serial number. These products should be loaded with the individual product's serial number. 5. After entering this information, the Intergraph PDS Component Loader dialog box displays.

28

Plant Design System (PDS) Project Administrator (PD_Project)

Introduction SmartPlant License Manager and RIS Client are not included in the Component Loader. They are delivered on the PDS CD, but must be installed individually. 6. When you choose a specific product to load, a dialog box showing its load options displays.

7. If you choose Local as the installation type, the software is loaded to the local disk. If you choose Client as the installation type, the Server Name field becomes active, and the Local install path field changes to Server install path. You must now enter the software server name and the path where this PDS product was loaded in server mode. If you choose Server as the installation type, the Local install path changes to Server install path. 8. All client nodes must have PD_Shell and SmartPlant License Manager (SPLM) loaded to the local disk.Other products can be loaded local or in client mode. Frequently-used products should be loaded locally, while infrequently used products can be loaded in client mode. 9. The node from which projects will be created must have all required products loaded locally. An exception is the 3D reference data, RDUSRDB or RDDINRDB, and the PDS 2D reference data, both of which can be loaded on a server and referenced from the client node during project creation. If projects are created using Express Project Creation/New User Mode, then the required reference data must be loaded locally. The Component Loader runs a check of the registry key string HKEY_LOCAL_MACHINE > SOFTWARE > Intergraph > Common in preparing for delivery of the RIS Shared Components. If this registry keystring does not exist, the Component Loader creates it with a value of c:\win32app\ingr\share. If the keystring does exist, it must be no longer than 22 characters and must not contain any spaces. If either of these rules is violated, a warning dialog box displays, and the RIS Components will not be delivered. See Registry Entries for more information.

Plant Design System (PDS) Project Administrator (PD_Project)

29

Introduction 10. When you select the PDS components to load and click the Load Components button, the Online Software License Agreement displays.

11. Click Yes to continue. 12. To configure SmartPlant License Manager: a. From the Start menu, click Programs > Intergraph SmartPlant License Manager > SmartPlant License Manager. Windows machine running User Access Control you must right-click and select Run as Administrator. b. Click Configure and Test, and then click Select. c. Click Select License Machine for Client, and then click Select. d. Type the SmartPlant License server computer name, and then click OK. e. Close all remaining SmartPlant License Manager dialog boxes when you have finished. 13. To configure RIS: a. Select RIS Schema Manager under the RIS start menu folder. b. Define the location of your schema file. 14. To configure PDS: a. Select PDSHELL – PDS configure. b. Select the needed cmd file. You are provided with an option to save this setting to either the HKEY_LOCAL_MACHINE registry location or the HKEY_CURRENT_USER location. Only users with administration rights on the computer can save this information in the HKLM setting. If the Current User setting is selected and set, then this registry setting is used and the HKLM setting is ignored. To change the setting for this user in the future you need to either change or delete the HKCU setting.

30

Plant Design System (PDS) Project Administrator (PD_Project)

Introduction 15. To create the PDS queues: a. While still logged into the machine as an administrator, select PD_SHELL – PDS Queue. b. Create the PDS queues. You need to change the temp and tmp variables to both point to C:\temp for ALL users that might need to work on this computer. Also if PDS2D was installed on the machine, the path variable in environment variables for the user running the Create PDS Queue command must have the pdshell path variable (normally c:\win32app\ingr\pdshell\share) before the PDS2D variable (normally c:\win32app\ingr\pds2d\binnt) for the Create PDS Queue command to work properly.

Lo a d in g Da ta b a s e P ro d u c ts Oracle and Microsoft SQL Server each require that a separate installation program be run after or during the process of downloading the database products. These installation programs involve significant decisions regarding the size of the database to be created, the maximum number of users to be supported, the frequency of automatic backups, and other important issues. It is recommended that a system manager who has reviewed the database installation programs install and configure the databases. For more information on installing a database on your workstation or server, see the PDS Project Setup Technical Reference.

Database Information PDS uses databases to store information that is applicable to all aspects of the project, including project control data and reference data. PDS also uses databases to associate nongraphic information and user-definable attributes with graphic elements in the design files. PDS 3D provides a consistent interface for the maintenance of these databases. All databases you create for PDS are relational databases, meaning that they are based on a relational data model - a relation being a two-dimensional table made up of rows and columns. Most relational databases have a Structured Query Language (SQL) interface. The PDS 3D products attach to the relational databases through Intergraph Corporation's Relational Interface System (RIS). RIS is a generic relational database interface that isolates the SQL interface differences in specific vendors' relational database management systems (RDBMSs). It provides a generic networked access to all databases that are generated with popular RDBMSs supported by RIS, including Oracle and SQL Server. For information on installing the RDBMS systems on your workstation or server, see the PDS Project Setup Technical Reference.

For more information, see: PDS and the Relational Interface System (RIS) (on page 31)

P DS a n d th e Re la tio n a l In te rfa c e S ys te m (RIS ) PDS 3D uses RIS to define information in an RDBMS. An RIS schema identifies a unique database/user combination in the commercial database system. Users are established for different RDBMSs in different ways; in fact, the concept of a database differs greatly from one RDBMS to another. The various interfaces provided in PDS allow you to maintain databases through RIS efficiently, without requiring you to know the differences between RDBMSs or the syntax of the RIS create schema statement. Notes:

Plant Design System (PDS) Project Administrator (PD_Project)

31

Introduction 



RIS works in conjunction with existing databases. You must have RIS implemented on your network and also have one of the Relational Database Management Systems (RDBMSs) supported by RIS, such as Oracle or SQL Server. Intergraph Corporation recommends that database creation and manipulations be performed at the system manager level. The system manager should be familiar with the theory and practice of the Relational Interface System to be successful. See the PDS Project Setup Technical Reference Guide. The Component Loader runs a check of the registry keystring HKEY_LOCAL_MACHINE>SOFTWARE>Intergraph>Common in preparing for delivery of the RIS Shared Components. If this registry keystring does not exist, the Component Loader creates it with a value of c:\win32app\ingr\share. If the keystring does exist, it must be no longer than 22 characters and must not contain any spaces. If either of these rules is violated, a warning dialog box displays, and the RIS Components will not be delivered. For information on modifying the registry keystring, see the Project Setup Technical Reference.

Preparing the Server and Workstations for PDS Intergraph recommends using dedicated login accounts for running PDS. This section describes the steps required to define the necessary accounts on a PDS software/file server and the client workstations. See the PDS Project Setup Technical Reference Guide for additional information.

32

Plant Design System (PDS) Project Administrator (PD_Project)

SECTION 2

PDS Environment The PDS 3D software supports a variety of applications. All the supported applications use a common interface that is controlled by the PD Shell program. This ensures consistency across applications and minimizes the amount of time required to learn the product. The PDS 3D modules provide a simple user interface through extensive use of forms. The modules also provide an on-line Help capability for easy access to information while working in the product. The PD_Shell Environment and all batch jobs in the PDS 3D products interface to Intergraph's Network Licensing System.

See Also PD Shell (on page 33)

PD Shell The PD Shell program provides access to the various functions that are associated with the PDS 3D Modules. You can access the Plant Design System Environment form by clicking Start > All Programs > PD_Shell > PD_Shell. This executes a control script that defines all of the environment variables that are needed to run the product, and it identifies the location of the product files. These files can be located on the workstation or a server on the network. See pds.cmd for more information on this file. The script also activates the Plant Design System Environment form.

Plant Design System (PDS) Project Administrator (PD_Project)

33

PDS Environment To make colors easier to read on flat screens and projectors, a zip file with modified color for PDS forms is delivered as alternatecolorfb.zip.

This form identifies the active project(s) and provides access to all the PDS functions. Schematics Environment — Provides access to the PDS 2D modules that are used to create and modify piping and instrumentation diagrams, process flow diagrams, and instrumentation database records. Equipment Modeling — Provides access to the Equipment Modeling module, which provides an interactive graphics environment that is used to create and revise equipment model graphics and database information. FrameWorks Environment — Provides access to the FrameWorks module, which provides an environment that is used to create and revise structural models, create and revise structural drawings, and propagate structural models. Piping Designer — Activates an interactive command environment that is used to create piping and in-line instrumentation in the model; revise existing model graphics and database information; and verify the integrity of the data in the model. Electrical Raceway Environment — Provides access to the Electrical Raceway module, which provides an interactive environment that is used to create and revise raceway models and access raceway utilities. Piping Design Data Manager — Provides access to a set of options that are used to verify the integrity of the graphic and database information that is associated with a model. Piping Model Builder — Enables you to create piping graphics from a nongraphics environment. This module is used with PD_Design to create an accurate 3D model of the piping network. Pipe Support Designer — Activates an interactive command environment that is used to create pipe supports in the model, and revise existing pipe support model graphics and database information.

34

Plant Design System (PDS) Project Administrator (PD_Project)

PDS Environment Pipe Stress Analysis — Activates a set of forms that are used to extract information from piping models for input to third-party pipe stress analysis products. Interference Manager — Activates a set of forms that are used to check for interferences among project models and to control approved interferences. Isometric Drawing Manager — Activates a set of forms that are used to extract isometric drawings from piping models and to review or plot the created isometric drawings. Drawing Manager — Activates a set of forms that are used to create and manipulate drawings and drawing views; provide access to the interactive graphics environment for drawings; and provide access to a plot manager and vector hiddenline manager. DesignReview Integrator — Activates a set of forms that are used to extract information to form label files for use in SmartPlant Review and to review data from a SmartPlant Review session. Report Manager — Activates a set of forms that are used to create and revise report format files and report on information in a project including Material Take-Off reports. Project Administrator — Provides access to a set of forms that are used to create a project, create and revise project files, define project seed data, and control the project. Reference Data Manager — Provides access to a set of forms that are used to control the reference data for a project including Piping Job Specification data, Graphic Commodity Data, Alphanumeric Commodity Data, Standard Note Library, Label Description Library, and Piping Assembly Library. User ID — Used for access control. This field also sets the Review User ID for use in the Interference Manager module. If access control has been defined, you must key in a valid user ID as defined by your system manager to gain access to the projects. Refer to Access Control Manager, page 467, for more information on using access control. If access control has not been defined, no entry is required for this field. Password — Key in the password for the specified user ID. Project List Field — Displays the defined projects for the network and allows you to select the active project. The system lists all the defined PDS projects (2D-only, 3D-only, and 2D & 3D). An error is displayed if you select an option that is incompatible with the active project. For example, if the active project is a 2D-only project, you cannot access the Interference Manager module. If access control has been defined, only those projects for which you have some level of access are displayed. Message Area — Displays prompts and messages that are associated with the active process. Error messages are displayed in red.

PD_Shell Form Conventions The following conventions describe how to respond to the various buttons, lists, and prompts that make up the environments. The display size of forms and dialog boxes in the non-Microstation graphics environment are independent of the size of the workstation's display system. Most forms contain the same basic features: buttons, fields, text, and other gadgets. In general, anything you find on a form is called a gadget. You move through the PD_Shell forms by selecting function buttons or other gadgets from the form. Select means to place the screen cursor (which appears as an arrow) on top of a screen gadget and press . For most of the forms with scrolling lists, you can double-click on a row to select and accept the data in that row. This performs the same action as selecting a row (which highlights) and then selecting the Accept button.

Plant Design System (PDS) Project Administrator (PD_Project)

35

PDS Environment You use the select action to select functions, access other forms, activate data fields, toggle buttons, select from lists, scroll through data displayed on the screen, and so on. The following summarizes other basic actions you use in the environments: Enter - When keying in any data in a key-in field, press the or key for the data to be entered into the system. You can also press or to move through a set of key-in fields. Delete - If you make a mistake while keying in text, press the key to erase character(s) to the left of the cursor.

Common Tools on the PD_Shell Forms There are many gadgets in the environments that are common to most or all of the forms. The following describes these tools.

Standard Commands The PD_Shell forms have a set of standard buttons in the upper right corner of most of the form windows. The available commands vary from form to form depending on the type of operation. The Help button activates on-line Help for the active form. Help remains active until you delete the Help window. The Shell button exits the active form and returns control to the base manager that is associated with the active form. For most forms this returns to the Plant Design System Environment form. The Top button exits the active form and returns control to the top form of the active branch. The Cancel button cancels or exits from the active form. Control returns to the immediately preceding form in the hierarchy. The Accept button accepts a selection or operation. Depending on the active form or option, the active form remains active so that you can repeat a similar operation or control returns to the preceding form. The Restart button clears any key-in fields on the form that have values you can modify.

36

Plant Design System (PDS) Project Administrator (PD_Project)

PDS Environment Scrolling List Some screen menus have a scrolling list of projects or applications. You need to scroll a list only if more options are available than can be displayed in the window. To scroll a list, select the arrow buttons on the side of the list. The list scrolls up or down depending on which arrow you select. The scrolling list has an arrow pointing up and an arrow pointing down. These arrows scroll lists line by line. There is a button that slides between these two arrows to indicate your position on the list. To page through the list, select the space above or below the sliding button. The list pages up or down accordingly. You can also select the slider and, while pressing , slide the button up or down the bar. The items scroll through the window as you move the button. The size and position of the button on the scroll bar is an indication of the number of lines and the relative position within the list. All commands that display a list of design areas or models order the list alphanumerically by the design area number or model number in ascending order. In some forms with scrolling lists, you can double-click on a row to select and accept the data in that row. This performs the same action as selecting a row (which highlights) and then selecting the Accept button. Key-in Fields Screens that accept keyboard input have key-in fields. These fields are box-shaped and dark gray. You can select a key-in field and key in a new value. A bar cursor appears in the active key-in field. Key in your input, and press . To change a field, re-select the field and key in the new information. Key-in fields have a maximum number of characters depending on the item that is being defined. If you select a key-in field for a code-listed attribute, the system activates a form that lists the code list values for the selected field. MicroStation requires lowercase characters for the file specification and path name of all design files. Therefore, the system automatically converts any input for the file specification and

Plant Design System (PDS) Project Administrator (PD_Project)

37

PDS Environment path name of a design file (such as a model or drawing) to lowercase before loading into the Project Control Database. Display-List Boxes A display-list box is located at the end of some key-in fields. It lets you select data from a list instead of keying in information. For example, there is a display list associated with the Authorization key-in field shown. At the end of the field, there is a small box with horizontal dashes. When you select this display list box with the screen cursor, an associated list of valid input values displays. Select an item from the list to enter its value into the field. Shift Left and Shift Right buttons At the bottom of some key-in and display fields, there are two buttons marked with arrows. These buttons are called shift left and shift right buttons. Often, you can key in more characters than a field display shows. Shift Left moves the text display to the front of the field; Shift Right moves the text display to the end of the field. Toggle A toggle field on a screen menu enables you to select one of two possible choices, one of which is always displayed. Place a data point on the toggle field to toggle between the two choices. Roll-Through List A roll-through list shows one choice at a time of a list that can be several items long. Place a data point on the roll-through list to scroll through the available options. The option displayed is active. Standard Window Icons When using this software, you can press along the edge of a form or any area not occupied by a button, key-in field, or other gadget, to display a box of icons. You can manipulate form windows just like any other workstation window. The following list defines the available window icons. Collapse/Restore Repaint Pop-to-bottom

38

Plant Design System (PDS) Project Administrator (PD_Project)

PDS Environment Modify/Resize Pop-to-top Restore Size

Path Location Fields Some key-in fields are used to specify paths for various files and folders, such as project folders, model files, reference data files, drawing files, and isometric drawing files. Prior to PDS 8.0, these path fields required the user to enter a full path, including the drive name, such as d:\project1\piping\models. Beginning with PDS 8.0, path fields accept share names as input. For example, if you have the project1 folder set up as a share, you could enter \project1\piping\models or project1\piping\models as the path for piping models. This new functionality allows administrators to set different permissions for shares used by different sets of users. For more information on setting up shares and permissions, see the PDS Project Setup Technical Reference.

Plant Design System (PDS) Project Administrator (PD_Project)

39

PDS Environment

40

Plant Design System (PDS) Project Administrator (PD_Project)

SECTION 3

Batch Processes When you install the PDS 3D applications, the system creates the necessary batch queues for that application. Refer to Loading Products (on page 25) in the Project Administrator Reference Guide for a listing of the batch queues. PDS 3D uses these batch queues to allow you to continue working in the environment while the system processes a request. Many of the batch processes can be delayed for submission at a specified time.

Plant Design System (PDS) Project Administrator (PD_Project)

41

Batch Processes

42

Plant Design System (PDS) Project Administrator (PD_Project)

SECTION 4

Project Administrator The Project Administrator controls the handling of databases and files within a project. It provides functions for creating and manipulating a project, managing files, and setting up the system. Select the Project Administrator option from the Plant Design System Environment form. The Project Administrator form is displayed.

Select the option to be performed. Project Environment Manager - Enables you to create, revise, and delete disciplines, design areas, and model files; revise the project/client information or disk location of a project or model; or create a report of information in the project control database and design database (see Project Environment Manager Form (on page 82)). Project Data Manager - Enables you to revise the RDB seed data used to create model files, drawings, and envelope files and to revise the RDB data for existing model files, drawings, or interference marker files (see Project Data Manager Form (on page 145)). Project Setup Manager - Enables you to create a project and the related database files or to delete an existing project (see Project Setup Manager). Project Control Manager - Enables you to create a package of project documents for use in revision control. You can define package information in the project control database and report on this information for revision control (see Project Control Manager Form (on page 257)). Project Archival Manager - Enables you to archive a complete project or subsets of a project and retrieve all or part of an archived project (see Project Archival Manager Form (on page 289)).

Plant Design System (PDS) Project Administrator (PD_Project)

43

Project Administrator System Manager - Enables you to revise the project directory file (see Edit Project Directory File (on page 342)). File Lock Manager - Enables you to unlock files currently locked by another user or process (see File Lock Manager (on page 347)). Access Control Manager - Enables you to modify user passwords for use with the Access Control option (see Access Control Manager). Export to PDME - Enables you to prepare a data set that consists of documents and a document index for import into the Project Data Management Environment (PDME) (see Export to PDME (on page 365)). The following steps outline the basic operations for setting up a project: 1. Create a project using the Project Setup Manager option. The first time you enter the PDS environment, the system branches directly to the Project Administrator form since no initial project data exists. The Express Project Creation utility can be used. See the Express Project Setup document for details. 2. Modify the seed data for the project using the Project Data Manager option. This enables you to make any changes to the delivered model or drawing reference data before any model files or drawings are created. 3. Create a design area for the piping discipline using the Project Environment Manager option. 4. Create the model data for a set of model files using the Project Environment Manager option. 5. Create the database tables for the defined model files using the Create Database Tables option in the Project Environment Manager.

44

Plant Design System (PDS) Project Administrator (PD_Project)

SECTION 5

Project Setup Manager The Project Setup Manager enables you to create a new project, revise an existing project, or delete an existing project. You must create a project before you can access any of the other PDS 3D activities. When you create a project, the system creates the associated database schemas for use in storing and accessing the project control data, design data, and reference data.

Before Using this Command Note: The Express Project Creation utility can also be used to create the project. The other functions described here can then be used to revise this project as required. Refer to System Setup (on page 24), for information on product prerequisites. A RIS database must exist on the server (or workstation). You must have privileges to create or delete a project. Create Project - Defines a new project and create associated database files. Revise Project - Attribute Display (on page 58) - Defines attributes within the design database to be displayed/not displayed for database operations. Revise Project - Add Attributes (on page 60) - Adds user-defined attributes to an existing design database. Revise Project - DBAccess (on page 62) - Revises the database structure to support DBAccess reporting of PDS data in the relational database.

Plant Design System (PDS) Project Administrator (PD_Project)

45

Project Setup Manager Delete Project Information (on page 65) - Deletes an existing project and associated database and model files. Site Administrator (on page 69) - Defines master and satellite sites. Insert FrameWorks Data - Defines FrameWorks data that is required to access the structural application within the PD_Shell environment. This is option is diplayed when the structural project data has not been defined for the active project. Insert Electrical Raceway Data (on page 75) Defines the location of project and reference data that is required to access the Electrical Raceway module within the PD_Shell environment. This option is displayed when the Raceway project data has not been defined for the active project. Delete FrameWorks Sub-Project (on page 78) - Deletes the FrameWorks Plus Sub-Project attached to the active project.

Create Project This option enables you to define a new project and create the associated database files. In defining the project, you can modify the design schema, set up the coordinate system, and modify the working units. You can use Create Project to create a project that consists only of 3D data, one that consists only of 2D data, or one that consists of several integrated modules such as 3D, 2D, Electrical Raceway, and structural. For an integrated project, you can create all the database schemas at one time, or you can create only the PDS 3D schemas initially and add the PDS 2D and/or Electrical Raceway schemas later. This document describes the steps to create a PDS 3D Project. Refer to the PDS Project Setup Technical Reference for information on creating a 2D-Only project or creating a fully integrated project. A PDS 3D project uses three database schemas: 1. Project Control schema. 2. Design Data schema. 3. Material Reference Data schema. (This is optionally two database schemas if you elect to use both approved and unapproved specification data.) You can define these database schemas in a single database, or you can spread the schemas over several different databases. You can also share a Material Reference Data schema among multiple projects. PDS 2D shares the project control database with the PDS 3D project. Each PDS 2D application (such as P&ID, PFD, and IDM) requires an application schema. You can also create the following Electrical Raceway database schemas:  Raceway Project Schema.  Raceway Reference Schema.

Before Using This Command You must setup the necessary database files before you can create the project database schemas. See the PDS Project Setup Technical Reference for details. 1. Choose Create Project from the Project Administrator form. The Create Project Data form is displayed. 2. Key in Data or Select Option. Set the Model System of Units and NPD System of Units to the required setting: English or Metric.

46

Plant Design System (PDS) Project Administrator (PD_Project)

Project Setup Manager 3. Key in the project/client information. Key in up to 15 characters for the project number. This also Project Number forms the name of the database schemas (with the prefixes pd_, dd_, and so forth). Project Name

Key in up to 40 characters for the project name.

Company Name

Key in up to 40 characters for the name of the company.

Job Number

Key in up to 40 characters for the job number.

Plant Name

Key in up to 40 characters for the name of the plant.

4. Select the Location of Project Data fields, and key in the following information. Each project on the network should be defined in a separate project directory. Key in the network address or node name of the workstation or Network server to contain the project data (for example, pds_serv). Address Directory

Key in the directory path for the location of the project data (for example, d:\proj\3dcore\).

5. Define the Project Marker file. The default is the project number with the extension .dgn. 6. Set the toggle to Do Not Create Tables for DBAccess to create the database schemas without the additional database structure required for DBAccess reporting. —OR— Set the toggle to Create Tables for DBAccess to create the additional database structure required for DBAccess reporting of PDS data. This option will create a mscodelist table and a set of join tables for each standard note type (both system-required and user-defined) for each of the PDS schemas. Refer to Revise Project - DBAccess (on page 62) for more information on this option. 7. Set the toggle to Create New Reference Schema to define a new Material Reference Database for this project. This is the default option. —OR— Set the toggle to Use Existing Reference Schema to use a previously created Material Reference Database for the project being created. This automatically deactivates the Piping Unapproved RDB Schema option. When you select the Piping Approved RDB Schema option, the system displays a list of project numbers for previously created projects. Selecting a project number determines the schema names for the approved and unapproved (if applicable) Material Reference Databases. Note: If you intend to have multiple projects share the same approved and unapproved Material Reference Database, it is suggested that you create an artificial project for the purpose of maintaining and verifying the data within the Material Reference Database. 8. Set the toggle to Create New Raceway Reference Schema to define a new Raceway Reference Database for this project. This is the default option. —OR— Set the toggle to Use Existing Raceway Reference Schema to use a previously created Raceway Reference Database for the project being created. When you select the Raceway RDB Schema option, the system displays a list of project numbers for previously created projects. 9. Create the database schemas for the new project.

Plant Design System (PDS) Project Administrator (PD_Project)

47

Project Setup Manager Project Control Schema (on page 48) P&ID Project - When this option is highlighted (the default), the system creates the project for both 2D data and 3D data. This data is required if you intend to access the P&ID product from within the PD_Shell environment. If this option is selected, but the P&ID product does not exist in the specified location, the system displays a warning dialog box when you create the project. FrameWorks Plus Project (on page 49) Raceway Project Schema (on page 51) Piping Design Schema (on page 51) 10. Create the reference database schemas for the new project. Piping Approved RDB Schema (see "Piping RDB Schema" on page 56) Piping Unapproved RDB Schema (see "Piping RDB Schema" on page 56) Raceway RDB Schema (on page 56) 11. Select the Optional Selections to modify the project setup. Specify Coordinate System (on page 56) Revise Working Units 12. Choose the Confirm button to accept the specified information and to create the project. The following messages are displayed:

Creating Project Create project database Creating RIS table Creating project database .... Creating design database .... Creating reference database .... Creating Raceway Project Schema Tables .... Creating Raceway RDB Schema Tables .... Successfully created project The system also copies the database definition files, seed files, queue description file, drawing plot size table, and category text files to the project directory. The system returns to the Project Setup form. You can now create design areas and models using the Project Environment Manager.

Project Control Schema Choose the Project Control Schema option from the Project Data form to define the project environment database. This database schema contains the project environment data such as design area and model specifications.

48

Plant Design System (PDS) Project Administrator (PD_Project)

Project Setup Manager The following illustration indicates the completed form display for an Oracle database. The form fields vary slightly depending on the type of database being created and the operating system of the database server.

Completion of the Create Schema form is covered in the database specific appendices of the PDS Project Setup Technical Reference.

FrameWorks Plus Project The FrameWorks Project option creates the project data required to integrate structural data into a PDS 3D project. This data is required to access the FrameWorks product within the PD_Shell environment. You can create one or more structural subprojects within the PDS project being created. The system stores the structural subproject data within tables 116 and 117 of the Project Control Database. For each subproject being created, the appropriate data is loaded into the Structural Subproject Control Data Table (PDtable_116).

Before Using This Command Note: The system reads the registry to determine if the FrameWorks Plus product is loaded. If not, this option is disabled.

Plant Design System (PDS) Project Administrator (PD_Project)

49

Project Setup Manager 1. Choose the FrameWorks Project option from the Create Project form.

The Project Number is filled in automatically based on the PDS project number being created. 2. Enter Project Directory and Node. Key in the location information for the structural project files.

50

FrameWorks Project Number

Key in the number of the structural subproject (for example, str).

FrameWorks Project Name

Key in the description of the structural subproject.

FrameWorks File Directory

Key in the directory path name for the location of the structural models. For FrameWorks Plus, the system appends the project number to the specified file directory to arrive at the base path. For example, if the project number is str and the file directory is d:\pdsproj\, the base path for structural subdirectories is d:\pdsproj\str\.

FrameWorks Network Address

Key in the node name or network address for the location of the structural models.

Plant Design System (PDS) Project Administrator (PD_Project)

Project Setup Manager FrameWorks Force Units

Specifies the force units for the model(unit for specifying load force).

FrameWorks Standard Section Table

Specifies the main standard section table for this model. You cannot change the standard section table after the model is created.

The system stores this data in the Project Control Database for use in creating structural models in the Project Environment and to support FrameWorks network operations within the PD_Shell environment. 3. Accept or Revise Information. Choose the Confirm button to accept the specified structural subproject information. The system creates a structural project subdirectory structure at the specified network address and path name. It copies supplementary data from the FrameWorks product directory to the structural project directory. In this process, the structural symbology data, symbology.md, is copied as symbology.sms. 4. The system clears the input fields to enable you to specify additional subprojects. When you are finished defining the structural subprojects, choose Cancel to return to the Create Project form.

Raceway Project Schema The Raceway Project Schema creates the project data required to integrate electrical raceway data into a PDS 3D project. You can run this option at the time you are creating an integrated project or at a later time. This enables you to create the electrical raceway data for an existing 3D project without having to enter the EE Nucleus, create a raceway project, and then insert the raceway data. Note: See the PDS Project Setup Technical Reference for information regarding the creation of the EE Raceway project.

Piping Design Schema Choose the Piping Design Schema option from the Project Data form to define the design database schema for the project. The design schema is used to store data such as piping component attributes that is associated with the model design file. Before creating the database, you can modify certain database attributes or add user-defined attributes to the database. For piping, you can add up to 24 user-extended attributes per table. For equipment, you can add up to 10 user-extended attributes per table. 1. Revise the Design Database Structure. The Database Structure Revision form is displayed.

Plant Design System (PDS) Project Administrator (PD_Project)

51

Project Setup Manager You can modify certain attribute lengths, add user- defined attributes, define attributes to be displayed, define attributes to be case sensitive, or use the default database structure.

2. Identify Table for Modification. Select the table to be modified from the display on the left side of the form. For the selected table, the system lists all the attributes that can be altered are listed. For example, if you select Piping Component Data, the following attributes are displayed:

3. Modify Lengths or Select Other Option. Select the attribute you want to change. Then key in a number within the displayed range to specify the length of the attribute. 4. To add additional attributes to the selected table, choose the User-defined Attributes (on page 55) option.

52

Plant Design System (PDS) Project Administrator (PD_Project)

Project Setup Manager If you cannot add additional attributes to the specified table, a warning message is displayed. Otherwise, the fields change to display the number of the next available attribute.

a. Key in Attribute Name. Key in the description for the new attribute. b. Select Attribute Type. Select the attribute type for the specified attribute: Decimal (real), Long Integer, Short Integer, Alphanumeric, or Standard Note. For an alphanumeric attribute, you are prompted for the number of characters. For a standard note attribute, you are prompted for the Standard Note Type. Key in the number of the code list set (such as 330). The Standard Note option is disabled for equipment tables. c. Accept Attribute Data or Modify. Choose Confirm to accept the displayed information and to add the specified attribute. The system verifies that the added attribute does not conflict with any RIS reserved keywords. Then the Database Structure Revision form is displayed. 5. To define the attributes within the selected table that are to be displayed for database operations, choose the Attributes to be Displayed/Case Insensitive (on page 55) option. 6. To define the attributes within the selected table that you want to be case insensitive for database operations, choose the Attributes to be Case Insensitive option. Attributes that are identified as case insensitive are treated as uppercase regardless of the case entered during data input.

Plant Design System (PDS) Project Administrator (PD_Project)

53

Project Setup Manager The fields update to display the attributes for the selected table.

a. Select Attributes to be CASE INSENSITIVE. Select the attributes that you want to be case insensitive from the list of attributes. b. Accept or Select Additional Attributes. Choose Confirm to change the data type of the selected attribute(s). The Database Structure Revision form is redisplayed. c. The selected attributes will have their alphanumeric data automatically converted to uppercase in the following situations. When a row is being created in the database. When a row is being updated in the database. When a value for such a column in a table is being used as search criteria for a database query In terms of case sensitivity, you must consistently define alphanumeric data that is to be transferred from the P&ID database to the Piping Design database to successfully transfer the data. d. Presently, all alphanumeric data, with the following exceptions is considered to be case sensitive. The following alphanumeric data will always be considered to be uppercase and cannot be changed. Piping materials class. Schedule/thickness. Pressure rating. Commodity code. Any attributes that are designated as case insensitive will have their data type changed from character to upper_case in the design.ddl file in the project directory.

54

Plant Design System (PDS) Project Administrator (PD_Project)

Project Setup Manager If, after creating a project, you determine that an attribute was inadvertently selected or not selected for case insensitivity, you can edit the design.ddl file manually to reverse the selection. However, this will not update any previously created data. 7. Choose Confirm to exit the form and to proceed to the Create Schema form. See the PDS Project Setup Technical Reference appendices for details on completion of the Create Schema form.

Us e r-d e fin e d Attrib u te s You can select User Defined Attributes to add additional attributes to the selected database table. If you cannot add additional attributes to the specified table, the system displays a warning. The system activates a form and displays the number of the next available attribute. 1. Key in Attribute Name. Key in the description for the new attribute. 2. Select Attribute Type. Select the attribute type for the specified attribute: Float (real), Integer (long integer), Short (short integer), Character, or Code Listed. For a character attribute, you are prompted for the number of characters. For a code-listed attribute, you are prompted for the code list. Key in the number of the code list set (such as 330). 3. Accept Attribute Data or Modify Choose Confirm to accept the displayed information and to add the specified attribute. The Database Structure Revision form redisplays.

Attrib u te s to b e Dis p la ye d /Ca s e In s e n s itive You can select Attributes to be Displayed to define the attributes within the selected table to be displayed/not displayed for database operations. You can select Attributes to be Case Insensitive to define the attributes within the selected table to be case insensitive for database operations. Attributes identified as case insensitive, will be treated as uppercase regardless of the case entered during data input. 1. The attributes for the selected table are displayed. 2. Select Attributes to NOT be Displayed. Select the attributes to be modified from the list of attributes. 3. Accept or Select Additional Attributes. Choose Confirm to accept the displayed information for the attribute. The Database Revision form is redisplayed.

Plant Design System (PDS) Project Administrator (PD_Project)

55

Project Setup Manager

Piping RDB Schema The Piping Reference Database Schema is used to store the piping job specification data for the project. This may optionally be two database schemas if you elect to use both approved and unapproved spec data. Choose the Piping Approved RDB Schema option from the Project Data form to define the reference database schema for approved reference data. Select the Piping Unapproved RDB Schema option to define the reference database schema for unapproved reference data. The process for creating the schema is the same for the approved and unapproved reference database schemas. Note: If the toggle is set to Use Existing Reference Schema, the system displays a list of project numbers for previously created projects when you select the Piping Approved RDB Schema option. Select a project number to define the schema names for the approved and unapproved (if applicable) Material Reference Databases.

Loading the Reference Database Schema The Reference Database schema for approved data must be loaded with reference data using the Reference Data Manager. Refer to the PDS Project Setup Technical Reference for detailed information on this process. This process must be executed after you have created the project schema and associated reference database schema.

Raceway RDB Schema You can create an Electrical Raceway Reference Database schema or have the project being created reference an existing Raceway Reference Database created for a different project. Choose the Raceway RDB Schema option from the Project Data form to define the reference database schema for electrical raceway. Note: If the toggle is set to Use Existing Raceway Reference Schema, the system displays a list of project numbers for previously created projects when you select the Raceway RDB Schema option. Choose a project number to define the schema names for the Raceway Reference Database. Note: For further information see the PDS Project Setup Technical Reference.

Specify Coordinate System This option enables you to revise the coordinate system parameters for the project. You can set the name of the coordinate system and specify the coordinate system monument. The plant monument is applied to the seed files that are used to create piping and equipment models, drawings, and interference marker files. Therefore, this value must be defined before any of the project environment data is created. The default values for the plant monument can be used for most projects. You may need to modify the plant coordinate system if you need to use coordinate values that are too large to fit into the MicroStation file, due to limitations imposed by the working units for the model.

56

Plant Design System (PDS) Project Administrator (PD_Project)

Project Setup Manager Refer to Create Model (on page 86), and Design Volume Coordinate System Definition (on page 239), for information on defining a design volume coordinate system (DVCS). A DVCS is only required if different models need to have their coordinates referenced from a different point.

1. Plant Coordinate System Description Key in up to 40 characters to describe the Plant Coordinate System to be used for the project. 2. Plant Coordinate System Monument Key in the easting, northing, and elevation coordinates to be assigned to the center of the design volume for the plant. This point corresponds to the MicroStation position 0,0,0. 3. Choose the Confirm button to accept the specified coordinate system data and to return to the Create Project form. OR Choose the Cancel button to exit the form without changing the coordinate system definition.

Plant Design System (PDS) Project Administrator (PD_Project)

57

Project Setup Manager Example

Example Plant Coordinate System Monument Coordinates in the Plant Coordinate System (PCS) are in relation to the plant monument. For example, if the plant monument was modified from its default setting of 0,0,0 to be E. 300', N. 250' and EL. 10', then a point 200 feet east and 150 feet north away from the plant monument would be at E. 500', N. 400' and EL. 10' in the Plant Coordinate System.

Revise Project - Attribute Display This command is used to define attributes within the design database to be displayed or not displayed for database operations. By default, all attributes are displayed. 1. Choose the Revise Project - Attribute Display option from the Project Setup Manager form.

58

Plant Design System (PDS) Project Administrator (PD_Project)

Project Setup Manager The Revise Project-Attribute Display form is displayed.

2. Select Table for Display Revision. Select the table to be modified from the form.

Plant Design System (PDS) Project Administrator (PD_Project)

59

Project Setup Manager The attributes for the selected database table are displayed.

3. Select Attributes to NOT be Displayed. Select the attributes to not be displayed from the list of attributes. 4. Accept or Select Additional Attributes. Choose the Confirm button to accept the displayed information. You are returned to Step 2. 5. When you have finished selecting attributes, choose the Confirm button to accept the attribute revisions. The Project Setup form is redisplayed.

Revise Project - Add Attributes This command is used to revise the Design Database structure after the project has been created. You can revise the Piping Segment Data Table, the Piping Component Data Table, the Piping/Tubing Data Table, the Instrument Component Data Table, the Pipe Support Data Table, the Equip_group, and the Equip_nozzle. You can add user-specified columns to the Piping Design Database, and you can also change the standard note type for any user-specified column in the Piping Design Database. This includes treating a user-specified column, where the data type is short integer, as a standard note for the first time. When adding attributes to an existing project, ensure that no piping models from that project are in use or locked. If the project models are in use or are locked, a type 63 or database attribute mismatch will occur. Any such mismatches must be manually corrected with EDG and RIS dumps. 1. Choose the Revise Project - Add Attributes option from the Project Setup Manager form.

60

Plant Design System (PDS) Project Administrator (PD_Project)

Project Setup Manager The Modify Project Database Revision form is displayed.

2. Select Design Table or Exit. Select the database table to be modified from the list at the top of the form. Any existing user-defined and system attributes are displayed (excluding the default system attributes). The system-added attributes are displayed in a different color to indicate that you cannot revise them. 3. Edit New Entry or Select Entry to Edit. Select an existing user-defined attribute from the scroll area to change the standard note type. —OR— Select the attribute name field to add a new user-defined attribute. Key in the attribute name, and select the attribute type (decimal, short integer, long integer, or alphanumeric).

For an alphanumeric attribute, you must also specify the number of characters. For a short integer attribute, you can select the standard note field to define a standard note type (such as 330) for the attribute. 4. Repeat Step 3 to add any additional attributes. Then choose the Confirm button to accept the modifications.

Plant Design System (PDS) Project Administrator (PD_Project)

61

Project Setup Manager

Revise Project - DBAccess This command revises an existing project to include the additional database structure required to support DBAccess reporting of PDS data in the relational database. The system creates an mscodelist table and a set of join tables for each standard note type (both those required by the system and those created by the user) in the appropriate schemas of the relational database. You can revise the database structure that is required for DBAccess reporting by adding the appropriate entries for any new user-defined standard note types. Once this option has been processed, any piping models that are created with the Create Database Tables or Copy Model options of the Project Environment Manager will be created with the necessary database structure for DBAccess reporting.

Before Using This Command You must specify the maximum length of the text for each standard note type in the Standard Note Library before creating the relational database structure. This maximum length is used to create the standard note data in the relational database. The maximum lengths must be specified in an ASCII file named stnote_max_len that must reside in the project directory. Entries in this file consist of one line for each standard note type with the following format. !note type max length short? 35 15 * 36 10 The note type and the maximum length are separated by one or more spaces or tabs. An asterisk (*) following the maximum length indicates that the short version of the standard note data be loaded into the relational database. The default is that the long version be loaded. Comments can be placed anywhere in the file and must be preceded by an exclamation point (!). You can determine which standard note data is loaded or not loaded into the relational database. If the maximum length for a standard note type is defined as zero (0) or the standard note type is not included in stnote_max_len, the data for that standard note type will not be loaded. A default note length file is delivered with the PD_Shell product in the file win32app\ingr\pdshell\lib\stnote_max_len. These maximum lengths were determined on the basis of the long option of standard note data reporting. To minimize relational database size, you should exercise discretion in specifying the maximum length. The maximum length for any standard note type is restricted to 240 characters by RIS.

62

Plant Design System (PDS) Project Administrator (PD_Project)

Project Setup Manager ! This file contains the maximum text length allowed for each note/code type. The ! format required is one entry per line with the note/code type appearing first and ! then the maximum length separated by spaces. Comments are designated by an exclamation ! point in the first column. An "*" to the right of the maximum length number designates ! to use the short description. ! 35 15 * 36 10 37 10 50 15 * 69 20 125 5 130 10 145 55 148 60 160 15 180 45 * 190 10 200 5 210 5 220 6 230 6 330 20 340 3 360 30 365 25 380 50 390 5 400 30 420 60 425 6 430 60 499 350 530 25 550 40 570 25 575 60 576 50 577 50 578 25 999 40 1010 5 1028 10 1056 5 1064 20 1074 15 1100 20 1201 15 1202 2 1203 15

Plant Design System (PDS) Project Administrator (PD_Project)

63

Project Setup Manager 1204 1205 1207 1310 1312 1410 1620 1630 1710 1720 2000

35 30 30 25 30 15 16 36 30 60 15

1. Select the Revise Project - DBAccess command from the Project Setup form.

2. Accept to Create Tables for DBAccess or Specify Submit Time. Choose Submit to Batch Immediately to begin processing the database as soon as you exit the form. —OR— Choose Delayed Submit to Batch to specify a day and time to process the database. 3. Choose the Confirm button to accept the specified time. Note: This command creates the required database structure changes for DBAccess reporting, but does not load the standard note data into that database structure. Use the Load Database option of the Standard Note Library Manager to create or update standard note data from the Standard Note Library into the relational database. Refer to the Reference Data Manager Reference Guide for a description of this feature.

64

Plant Design System (PDS) Project Administrator (PD_Project)

Project Setup Manager

Delete Project Information This option is used to delete an existing project. It deletes all the files that are associated with the project, including the project database files, seed files, queue description, drawing plotsize table, category text files, design areas specifications, model files, and drawings. You can also delete all or part of the reference data that is associated with a project. The system automatically deletes any applicable Table Revision Management Libraries when deleting the Material/Reference Database. Note that the system will not check to see if any of this data is being used by another project. If applicable, the Delete Project command will  Automatically delete the optional data added to support DBAccess reporting.  Recognize any seed drawings that have been defined on the basis of a specific drawing type.  Delete the following electrical raceway data:  The raceway models and the corresponding interference envelopes.  The raceway seed model, rwysdz.dgn, in the project directory.  The raceway design database.  Optionally, the raceway Reference Database and the raceway Graphic Commodity Library.  Delete all associated structural subprojects, including the model management data, the structural design areas, the structural models, and the structural drawings that correspond to each of the structural subprojects being deleted.

1. Choose Delete Project from the Project Setup Manager form.

Plant Design System (PDS) Project Administrator (PD_Project)

65

Project Setup Manager 2. Select Project to Delete. Select the project to be deleted from the display window. —OR— Key in System Manager Password. If access control has been defined, key in the system manager password to list all the projects. 3. Go to Step 4 to delete the entire approved and unapproved Reference Databases for the project. —OR— Choose the Delete Reference Data (on page 67) option to select the approved and unapproved reference data to be deleted. See Delete Reference Data (on page 67) for information on this option. 4. Choose the Confirm button to delete the selected project. 5. Deleting project projname. All files that are associated with the project are deleted from the project directory. Also, the project name is deleted from the list of available projects. 6. Choose the Cancel button to return to the Project Setup form. 



66

When a schema is dropped in an Oracle database, the tables are not removed from the Oracle database. (That is, if you want to delete a schema, drop the tables first; then drop the schema.) If Delete Project fails, it will offer you a chance to delete the project name from the list of available projects. At the prompt, choose the Confirm button to remove the project name despite the error.

Plant Design System (PDS) Project Administrator (PD_Project)

Project Setup Manager

Delete Reference Data This option is used to select the approved and unapproved reference data to be deleted. The system lists all the Reference Database data for the selected project.

Select RDB File Type for Deletion Select the data to be deleted, or select from the options at the bottom of the form. Then choose the Confirm button to return to the Delete Project form. The form options enable you to delete the following additional reference data that may be shared by multiple projects. For each of these options, the system warns that the data may be shared by other projects. It will not actually verify whether any of the data is being used by another project.

Isometric Data This option deletes isometric drawing management data, including isometric drawings, isometric drawing borders, and defaults files. You can delete all isometric drawing management data that is associated with the project through the Isometric Drawing Management Data Table of the Project Control Database. You can select individual isometric drawing management data from a list of all such data.

Search Criteria Files This option sets the optional search criteria data for the project, as specified through the Report Manager, for deletion.

Plant Design System (PDS) Project Administrator (PD_Project)

67

Project Setup Manager Format Files This option displays all the defined report format files for the project. You can select the individual format files to be deleted from the list, or you can select one of the options at the bottom of the form.

Select Design Source - Design data reports are used by the Report Manager and the Drawing Manager to report data from the Piping Design Database. This option selects all design data report formats associated with the project being deleted. Select Project Source - Project data reports are used by the Project Control Manager and the Interference Report Manager to report data from the Project Control Database. This option selects all project data report formats that are associated with the project being deleted. Select Reference Source - Reference data reports are used by the Reference Database Report Manager to report data from the Material Reference Database. This option selects all reference data report formats that are associated with the project being deleted.

Select All Rows This option selects all the items on the Delete Reference Data form for deletion. The system highlights all the items selected for deletion.

68

Plant Design System (PDS) Project Administrator (PD_Project)

Project Setup Manager

Site Administrator The Site Administrator command enables you to create a work site, revise an existing work site, or delete an existing work site. Setting up multiple work sites allows you to designate ownership of models and drawings by design office, and to transfer models and drawings among sites using the Project Archival and Retrieval commands. Note: If your workshare setup requires importing models from non-workshare projects, you must create a site with the Site_ID OFFSITE.

Create Site - Creates a work site. Revise Site - Revises an existing work site. Delete Site - Deletes an existing work site.

Plant Design System (PDS) Project Administrator (PD_Project)

69

Project Setup Manager

Create Site This command allows you to create a new work site, and to designate a master site.

Site ID - The Site ID of the site. This value is used in the project database to determine site ownership of models and drawings. This value can contain up to 10 characters. If your project setup requires importing data from non-workshare sites, you must create a site with the Site_ID OFFSITE. Site Description - Text description of the site. This description can contain up to 40 characters. Model Index Range - The range of index numbers for models owned by this site. New models created in projects assigned to this site will have index numbers between the minimum and maximum values set on this form. These values can only be set by the master site administrator. Drawing Index Range - The range of index numbers for drawings owned by this site. New drawings created in projects assigned to this site will have index numbers between the minimum and maximum values set on this form. These values can only be set by the master site administrator. Drawing View Index Range - The range of index numbers for drawing views owned by this site. New drawing views created in projects assigned to this site will have index numbers between the minimum and maximum values set on this form. These values can only be set by the master site administrator. Piping Partition Numbers Range - The range of index numbers for piping partitions owned by this site. New piping models created in projects assigned to this site will have partition numbers between the minimum and maximum values set on this form. These values can only be set by the master site administrator.

70

Plant Design System (PDS) Project Administrator (PD_Project)

Project Setup Manager The maximum value for piping partition numbers is 8192. Equipment Partition Numbers Range - The range of index numbers for equipment partitions owned by this site. New equipment models created in projects assigned to this site will have partition numbers between the minimum and maximum values set on this form. These values can only be set by the master site administrator. The maximum value for equipment partition numbers is 8192. Master Site / Satellite Site toggle - This read-only toggle shows whether the site is the master site for the project or a satellite site. By default, the first site created is the master site. 1. Select Create Site on the Site Administrator form. The Create Site form displays. 2. Set the values as necessary for the new site. Note: The first site you create will be the master site. Subsequent sites will all be satellite sites. 3. Click Accept. The system adds the new site data to the database.

Revise Site This command allows you to modify the attributes of an existing work site.

Site ID - The Site ID of the site. This value is used in the project database to determine site ownership of models and drawings. This value can contain up to 10 characters. Site Description - Text description of the site. This description can contain up to 40 characters.

Plant Design System (PDS) Project Administrator (PD_Project)

71

Project Setup Manager Model Index Range - The range of index numbers for models owned by this site. New models created in projects assigned to this site will have index numbers between the minimum and maximum values set on this form. These values can only be set by the master site administrator. Drawing Index Range - The range of index numbers for drawings owned by this site. New drawings created in projects assigned to this site will have index numbers between the minimum and maximum values set on this form. These values can only be set by the master site administrator. Drawing View Index Range - The range of index numbers for drawing views owned by this site. New drawing views created in projects assigned to this site will have index numbers between the minimum and maximum values set on this form. These values can only be set by the master site administrator. Piping Partition Numbers Range - The range of index numbers for piping partitions owned by this site. New piping models created in projects assigned to this site will have partition numbers between the minimum and maximum values set on this form. These values can only be set by the master site administrator. The maximum value for piping partition numbers is 8192. Equipment Partition Numbers Range - The range of index numbers for equipment partitions owned by this site. New equipment models created in projects assigned to this site will have partition numbers between the minimum and maximum values set on this form. These values can only be set by the master site administrator. The maximum value for equipment partition numbers is 8192. Master Site / Satellite Site toggle - This read-only toggle shows whether the site is the master site for the project or a satellite site. By default, the first site created is the master site. 1. Select Revise Site on the Site Administrator form. The Revise Site form displays. 2. Select the site to revise. The Revise Site Data form displays. 3. Set the values as necessary for the site. 4. Click Accept. The system updates the database.

Delete Site This command deletes an existing work site. You cannot delete a site if it still owns any drawings or models, or if the active project is set to the site. 1. Select Delete Site on the Site Administrator form.

72

Plant Design System (PDS) Project Administrator (PD_Project)

Project Setup Manager The Delete Site form displays.

2. Select the site to delete. 3. Click Accept. If the site still owns any models or drawings, or if the active project is assigned to the site, an error message displays. Otherwise, the system deletes the site from the database.

Insert FrameWorks Data To avoid creating models with incorrect working unit settings, adjust the working unit settings of FrameWorks Plus seed files after creating the projects, and before creating models. The first step in using FrameWorks Plus with PDS is to integrate existing FrameWorks Plus projects into a PDS project or to create a FrameWorks Plus project in the PDS project. If the FrameWorks Plus project already exists, only database entries are created in the "pd_project-database" in pdtable_116. Note: The total path length to the FrameWorks Plus project including the drive letter and the required \'s is limited to 36 characters. FrameWorks Project Number - Specifies the FrameWorks Plus project name (the top-level project directory that appears in the Windows Explorer). This string can contain letters and/or numbers but no other special characters except the underscore (_) character. Names are limited to 14 characters. FrameWorks Project Name - Type a description for the project. FrameWorks File Directory - Type the full path to the directory where you want to store the project. Make sure you do not duplicate the project name in this path.

Plant Design System (PDS) Project Administrator (PD_Project)

73

Project Setup Manager For example: FrameWorks Plus Project Number: fwstr -ANDFrameWorks Plus File Directory: c:\pds_proj_dir\project Will give you: c:\pds_proj_dir\project\fwstr\ c:\pds_proj_dir\project\fwstr\data c:\pds_proj_dir\project\fwstr\drw c:\pds_proj_dir\project\fwstr\esl c:\pds_proj_dir\project\fwstr\frz c:\pds_proj_dir\project\fwstr\int c:\pds_proj_dir\project\fwstr\mod c:\pds_proj_dir\project\fwstr\rpt Entering an extra \fwstr on the end of the FrameWorks Plus File Directory name could complicate the directory structure. If you key in c:\pds_proj_dir\project\fwstr for the directory name and fwstr for the Number, you will get c:\pds_proj_dir\project\fwstr\fwstr for the final FrameWorks Plus Subproject directory name. FrameWorks Network Address - Specifies the computer on which the FrameWorks Plus project is located. Enter the computer's name. Force Units - Specifies the force units to use by default for the member loads placed in this project. The force units are stored in the Standard Note Library List 1640. Standard Section Table - Specifies the standard section table to use by default for models created in this project. There are several standard section tables delivered with FrameWorks Plus. The standard section table location is read from the ..\fwplus\data\config.dat file. User Section Table - Specifies the user section table to use by default for models created in this project. List of Existing FrameWorks Projects - Lists all existing FrameWorks projects. Create or Insert FrameWorks Plus Projects 1. Click Start > Programs > PD_Shell > PD_Shell. 2. Select a PDS project. 3. Click Project Administrator. 4. Click Project Setup Manager. 5. Click Insert FrameWorks Project. 6. Type the FrameWorks Project Number. 7. Type a FrameWorks Project Name. 8. Type a FrameWorks File Directory. 9. Type the FrameWorks Network Address. 10. Select the Force Units for the project. 11. Select the Standard Section Table for the project. 12. Select Accept.

74

Plant Design System (PDS) Project Administrator (PD_Project)

Project Setup Manager

Insert Electrical Raceway Data This option is required to integrate an Electrical Raceway project into the PD_Shell environment for a previously created PDS project. It defines the location of an existing Electrical Raceway project directory and Reference Database. This option is only displayed on the Project Setup Manager main form if no electrical raceway data has been defined for the active project. To avoid creating models with incorrect working unit settings, adjust the working unit settings of Raceway seed files after creating the projects, and before creating models.

Before Using This Command The Electrical Raceway project to be inserted must have already been created with the Electrical Raceway product. Make sure there is no schema password for the Raceway schema. The system expects that an electrical project configuration file, .EErc, reside in the project directory. This configuration file assigns an environment variable, EES_REFDB, to define the relational database schema name for the project's Electrical Raceway Reference Database. 1. Choose the Insert Electrical Raceway Data option from the Project Setup Manager main form. The Insert Electrical Raceway Project form is displayed.

2. Enter Raceway Project Directory and Node. Key in the node name and the directory path for the directory where the electrical raceway project currently exists, including the *.prj directory in the path name. (This is the the location of the .prj file.). 3. Key in the schema name for the electrical raceway reference database.

Plant Design System (PDS) Project Administrator (PD_Project)

75

Project Setup Manager 4. Choose the Confirm button to accept the specified raceway project information. The network address and path name are stored in the Project Control Database as the default location for creating electrical raceway models. Note: If the name of the Raceway project schema is not EE_, you must edit PDtable102 through RIS and change the name of the Raceway project schema. This is required for labels to work properly in PDS.

Insert ModelDraft Data This option is required to integrate ModelDraft into the PD_Shell environment for a previously created PDS project. It defines the location of the ModelDraft project directory. This option is only displayed on the Project Setup Manager main form for any of the following situations:  For an existing project, where structural data was created with the ModelDraft product in a previous PDS release.  A structural project was created with the 5.0 ModelDraft product before having created the 3D project through the Create Project command.  A 3D project was created with 5.0 PDS without defining the ModelDraft project data.

Before Using This Command The environment variables MD and MP must be defined in the PD_Shell environment shell script (control.sh) to define the location of the ModelDraft and MicasPlus products. If the ModelDraft product does not exist in the specified location, the system displays a dialog box with a warning message when you try to create ModelDraft project data. 1. Choose Insert ModelDraft Data from the Project Setup Manager main form.

76

Plant Design System (PDS) Project Administrator (PD_Project)

Project Setup Manager The Insert ModelDraft Project form is displayed.

2. Enter MDR Project Directory and Node. Key in the location information for the ModelDraft project files.  ModelDraft Project Name - Key in the name of the ModelDraft subproject.  ModelDraft File Directory - Key in the directory path name for the location of the structural models.  ModelDraft Network Address - Key in the node name or network address for the location of the structural models.  ModelDraft Mount Point - Key in the prefix of the mount point for the location of the structural models (such as /usr3). The prefix is required because the structural PDS file includes the mounted path name rather than a network address and a path name. The specified mount point must be created on each machine that will access the ModelDraft product. This value cannot be changed after the project is created. The system stores this data in the Project Control Database for use in creating structural models in the Project Environment and to support ModelDraft network operations within the PD_Shell environment. 3. Accept or Revise ModelDraft Information. Choose the Confirm button to accept the specified ModelDraft subproject information. The defined subprojects are listed in the scroll field at the bottom of the form. The system also verifies that the specified data defines a valid ModelDraft project directory.  If the ModelDraft project does not exist, the system creates a structural project subdirectory structure at the specified network address and path name. It copies supplementary data from the ModelDraft product directory to the structural project directory. In this process, the structural symbology data, symbology.md, is copied as symbology.sms.

Plant Design System (PDS) Project Administrator (PD_Project)

77

Project Setup Manager 

If the ModelDraft project exists, the system updates the ModelDraft project information in the Project Control Database but does not create any directory files. 4. The system clears the input fields to allow you to specify additional subprojects. When you are finished defining the structural subprojects, choose the Cancel button to return to the Create Project form. Warning: If structural models already exist for the inserted ModelDraft project, use the Create Model from ASCII File command rather than the Create Model command to add the necessary model information to the project database. This command deletes FrameWorks sub-projects from the current PDS project. This command does not delete the FrameWorks Plus project directory or its subdirectories. It only removes the FrameWorks Plus entries from the PDS project database. You can use Windows Explorer to remove the actual project. 1. Choose Delete FrameWorks Sub-Project from the Project Setup Manager form.

The system displays the Delete FrameWorks Project form. 2. Select the project to be deleted from the display window. 3. Choose the Confirm button to delete the selected project.

78

Plant Design System (PDS) Project Administrator (PD_Project)

Project Setup Manager

Plant Design System (PDS) Project Administrator (PD_Project)

79

SECTION 6

Project Environment Manager The Project Environment Manager is used to create, revise, and delete disciplines, design areas, and model files; revise the project information location of a project or model; or create a report of information in the project control database and design database. The Project Control database is created as part of a new project. (See the Project Setup Manager.) The project is the fundamental structure for working in PDS. Each project contains all the information required to design a plant in the PDS environment. PDS uses the following organization to divide the project:  A discipline is a grouping based on application. The project is initially created with the following disciplines: Piping, Equipment, Structural, HVAC, Raceway and Architecture. Additional user-defined disciplines (up to a total of ten) can also be created.  A design area represents a specified volume of the project for a specific discipline. Design areas are used to divide the project into smaller areas for operations to be performed only on a subset of the entire plant, such as interference checking or reporting.  A model corresponds to a specific 3D volume for a discipline within the specified design area. A model represents the smallest subdivision of the project based on work responsibility. Because PDS projects do not support MicroStation V8 drawing files, you can use the ChkDgnv7 utility to find any MicroStation V8 design files in a project. After running the utility, an ASCII-based log file is generated at a user-defined location. The log file provides a report on files contained in the project. You can then remove any MicroStation V8 files from the project. After you create a project and you begin working, the error message below displays if PDS finds a MicroStation V8 file:

To locate the problem file(s) in the project, run the utility as described below. The utility can only be run from a Windows command line. 1. Locate the ChkDgnV7 utility in the [drive]:\WIN32APP\INGR\PDPROJEC\bin folder. 2. Open a Windows command line and go to the above folder containing the utility. 3. Enter the following syntax to run the utility: chkdgnv7 [PDS project name] [Log file name]

Plant Design System (PDS) Project Administrator (PD_Project)

81

Project Environment Manager PDS Project name - the name of the project file you want to use. All files contained in that project are checked. Log file name - the name of the text file that is generated by the utility. Type in the path and file name you want to use. The project name in the syntax is case sensitive.

The utility generates the log file at the specified location. 4. Open the file using any ASCII text editor to see a report on the project files. For any MicroStation V8 files, the message, "Unsupported V8 file found in the path..." displays. 5. Repeat steps 3-4 for each project you want to check. 6. Exit the Windows command line window when you have finished. You can run this command-line utility at any time.

Project Environment Manager Form The Project Environment Manager form is used to:  Create and Delete Disciplines, Design Areas, and Model Files.  Revise the project information.  Relocate an entire project, a single model, or a drawing to a new location.  Revise the definitions for Disciplines, Design Areas, and Model Files.  Report on models or drawings in the Project Control Database.  Report on Named Items in Piping and Equipment models.  Define the default location for new models. For more information, see the Project Environment Manager Form. Create - Displays the Create Options form to create disciplines, design areas, and model files. Revise - Displays the Revise Options Form (on page 106) to edit the description of the project, or of a discipline, area or model. The project directory or a single model or drawing may also be moved. Delete - Displays the Delete Options Form (on page 127) to delete disciplines, design areas, or models. Report - Displays the Report Options Form (on page 132) to create reports on the project and named items in the models.

82

Plant Design System (PDS) Project Administrator (PD_Project)

Project Environment Manager Model Setup - Displays the Model Setup Data Form (on page 91) to specify the default network address and path name for new models on a per-discipline basis.

1. Select the Project Administrator option. Select the Project Administrator option from the Plant Design System Environment form. The Project Administrator form is displayed. 2. Select the Project Environment Manager option. Select the Project Environment Manager option from the Project Administrator form. The Project Environment Manager form is displayed. 3. Select Option. Select the Create, Revise, Delete, Report, or Model Setup option. The selected Create Options, Revise Options, Report Options, or Model Setup Options form is displayed.

Plant Design System (PDS) Project Administrator (PD_Project)

83

Project Environment Manager

Create Options Form The Create Options form is used to create disciplines, design areas or models for the active project. For Piping, Equipment and Raceway models, seed files from the project directory are used to create the new model. The Project Data Manager can be used to edit the project seed files prior to (and in some cases even after) model creation. Create Discipline Data (on page 85) - Creates a user-defined (non-PDS) discipline. Create Design Area Data (on page 86) - Creates a design area within a discipline. Multiple design areas can be defined for each discipline. Create Model (on page 86) - Used to create a new Piping, Equipment, Structural or Raceway model for the specified design area or to create a model definition for the other non-PDS disciplines. Copy Model - Copies a model within the current project or to another project. Create Database Tables (on page 101) - Creates the database tables for Piping and Equipment models. Create Model Data from ASCII File (on page 102) - Creates multiple models based on the parameters in a text file.

1. Select Create Option. Select the Create option from the Project Environment Manager form. The Create Options form is displayed. 2. Select Option. 3. Select the Create Discipline Data, Create Design Area Data, Create Model, Copy Model, Create Database Tables, or Create model from ASCII File option.

84

Plant Design System (PDS) Project Administrator (PD_Project)

Project Environment Manager The selected Create Discipline Data, Create Design Area Data, Create Model, Copy Model, Create Database Tables, or Create model from ASCII File form is displayed.

Create Discipline Data The Create Discipline Data option is used to create up to ten disciplines for the active project. Projects are initially created with the Piping, Equipment, Structural, HVAC, Raceway, and Architecture disciplines. When this option is selected, the existing discipline definitions are displayed in the Disciplines list. Disciplines - A listing of the existing disciplines. Discipline Name - The name of the new discipline to be created. PLANTGEN Discipline toggle - Only one discipline per project can be designated as a PLANTGEN discipline. Clash Discipline toggle - Only one discipline per project can be designated as a Clash discipline. The Clash discipline is used to define area volumes for envelope generation and interference checking. The volume can be defined in plant coordinates or using a defined Design Volume Coordinate System (DVCS). Note: No models can be created in the Clash discipline, either manually or by ASCII file.

1. Select Create Discipline Data Option. Select the Create Discipline Data option from the Create Options form. The Disciplines field is updated. 2. Type Discipline Name. Type the name of the discipline to be created and press the Enter key.

Plant Design System (PDS) Project Administrator (PD_Project)

85

Project Environment Manager 3. Select the PLANTGEN Discipline or Clash Discipline option, if applicable. 4. Accept Discipline Information. Choose the Confirm button to accept the specified discipline information. The specified discipline data is written to the Project Control Database, and the Disciplines list is updated with the new entry. —OR— Select another option to cancel the discipline definition.

Create Design Area Data The Create Design Area Data option creates new design areas for the a discipline. A design area can optionally specify a fixed volume of the project area. The volume for a design area can define a unique area or overlap that of another design volume. Numerous operations in PDS can be performed on the entire project, on all models in a specified area, or on single models in an area. The volumes associated with a design area have a marked effect on interference checking. For a complex discipline such as Piping, divide the project into several areas rather than specify one design area for the entire project volume. Design Area Name - Type a name for the design area. Design area names should not contain embedded spaces or other special characters such as, but not limited to, ^&#%$. However, you can use the underscore (_) character, A-Z, a-z, and 0-9 in design area names. Description - Type a description for the design area. Interference Management Design Area - Select whether or not this is a interference management design area.

Create Model The Create Model option is used to create a new model in a discipline. For Piping, Equipment, Structural and Raceway disciplines, the create model operation will create a design file that can be opened through the PDS environment. For Architectural, HVAC and user-defined disciplines, only an entry in the project control database is created (the design file would be created through an alternate method). A default location for new models can be defined for new models (See Model Setup Data Form (on page 91)). This location can be changed at the time the model is created. To simplify the management of your project, it is recommended that files associated with a single project, be located on as few nodes as possible. By default, the piping, equipment, and raceway PDS modules use project seed files to create new models. However, structural PDS uses the seedf.dgn file (English units) or the seedm.dgn file (Metric units). These seed files are delivered in the fwplus/seed directory. You can also specify seed files in a different directory using the FW_SEED.DIR variable in the FrameWorksPlus config.dat file. (The default value for this variable is FW_SEEDDIR=$(PROD)SEED/.) For FrameWorks Plus models, you can also specify seed models to create new models. The location for seed models is specified by the FW_SEEDMODELDIR variable. If this variable is not set, the system searches the $(PROD)SEED directory for applicable .mod files. For non-PDS disiplines, the seed file location is specified by an entry in pdtable_113.

86

Plant Design System (PDS) Project Administrator (PD_Project)

Project Environment Manager Before Using This Command Use the Project Data Manager to revise the information in the seed file before creating a model. Certain seed file changes must be made before any models are created. See Seed Options Form (on page 146) for additional information on this topic. Use the Model Setup option to define the default location for models of a discipline. The default location for structural and raceway models is determined when the Structural and Raceway projects are created. If you are planning to establish a workshare project with different sites, create the site data using the Site Administrator commands before creating any models in the project. This workflow will ensure that model index and partition index numbers are not duplicated between workshare sites.

Non-Frameworks Plus Models Model Number - Type up to 10 characters for the name/number of the design file to be created/defined. (For structural models, the number is limited to 10 characters.) Model names should not contain embedded spaces or other special characters such as, but not limited to, ^&#%$. However, you can use the underscore (_) character, A-Z, a-z, and 0-9 in model names. Model Name - The system verifies the specified name is valid for use as a design file name. The software fills in the Model Name automatically by appending .dgn to the specified model number. For structural models, entries for a .dgn file is created in the project control database. However, only the .dgn file is created on disk/ The .frz file, must be created with the same name, from within Frameworks. The Model Name may be edited. Model Directory - If a default location was specified in the Model Setup Options, the node name and path appear in this field. The location of Structural and Raceway models cannot be changed.

Plant Design System (PDS) Project Administrator (PD_Project)

87

Project Environment Manager Workstation/Server Name - This field defaults to the node name and path specified in the Model Setup Options. Type a network address or node name to specify the system on which the model file is to be created. Application Type - This field defaults to the active discipline and sets the responsible discipline attribute in PDtable_113. The responsible discipline attribute is used by the envelope builder and the Interference Checker to determine the actual discipline if the Discipline Matrix is used. For example, this provides a method to use a piping model for HVAC ducting and have the clashes from that model treated by the Interference Checker as HVAC components in to assign responsibility for the clash. Refer to the Interference Checker/Manager (PD_Clash) User's Guide for more information. Model Status - Select a value for model status from the list. The model status can be used to create subsets of models for clash checking or for SmartPlant Review. Site ID - This field specifies which work site owns the model. When creating models from the master site, the Site ID can be set to any site appearing in pdtable_105. When creating models from a satellite site, the Site ID is automatically set to the value for the satellite site. The master site can create models for any site. A satellite site can only create models for itself. The Site_ID field displays only for a workshare project; that is, a project whose site_id attribute is set in pdtable_101.

Framework Plus Models Seed Model - Specifies the name of the seed model to use as a basis for the new FrameWorks Plus model. Frozen Model Name - The name of the frozen model for this FrameWorks Plus model. An entry is created in pdtable 113 for the sparse (modname.dgn) and frozen (modname.prp) files for each FrameWorks Plus model. The frozen model file is created by opening the sparse file, creating views, placing FrameWorks Plus members, freezing a view then propagating the model file. Force Units - Specifies the force units for the model (unit for specifying load force). Standard Section Table - Specifies the main standard section table for this model. You cannot change the standard section table after the model is created. User Section Table - Specifies a user section table for this model. All user section tables, if any, in the project's \sl directory display for selection. You can select another user section table after the model is created if needed. Third Party Software - Specifies which third party analysis/design software to use for the model. If necessary, you can change the selection after the model is created. Design Code - Specifies the design code to use for the model. If necessary, the selection can be changed after the model is created. Sparse Model Name - Displays the system assigned Sparse Model Name. This name is based on the model name. Propagated and Sparse toggle - Determines whether the frozen files have centerlines displayed as part of the members. Sparse Model Directory - Displays the system assigned Sparse Model Directory. This is based on the Model Directory. Sparse Workstation/Server Name - Displays the system assigned sparse workstation/server name. This is based on the model Workstation/Server Name. If a seed model is selected, the following values are grayed out, because they are defined in the seed model:  Force Units  Standard Section Table

88

Plant Design System (PDS) Project Administrator (PD_Project)

Project Environment Manager  User Section Table  Third Party Software  Design Code 1. Select Option. Select the Create Model Data option from the Create Options form. 2. Select Discipline. Select the discipline for the model file to be created from the list of displayed disciplines and choose Confirm. The Select Area for Create Model Data form is displayed showing available design areas.

3. Select Design Area. Select the design area for the model file to be created from the list of design areas; then choose the Confirm button.

Plant Design System (PDS) Project Administrator (PD_Project)

89

Project Environment Manager The Create Model Data form is displayed.

4. Specify Model Information. Type the Model Number, Model Name, Model Description, Model Directory, Workstation/Server Name, Application Type, and Model Status. Model names should not contain embedded spaces or other special characters such as, but not limited to, ^&#%$. However, you can use the underscore (_) character, A-Z, a-z, and 0-9 in model names. 5. For structural models, provide the additional information: Seed Model, Application Type, toggle for Propagated Only, Sparse Model Name, Sparse Model Directory, and Sparse Workstation/Server Name. Note: Additional information can be specified for FrameWorks models: Force Units, Standard Section Table, and User Section Table. 6. Accept or Specify Attribute. Choose the Confirm button to accept the displayed model data.

90

Plant Design System (PDS) Project Administrator (PD_Project)

Project Environment Manager The specified model management data is written to the Project Control Database. If the discipline is Piping, Equipment, or EE Raceway the Design Volume Coordinate System Definition form is displayed.

Refer to Design Volume Coordinate System Definition (on page 239), for information on the Design Volume Coordinate System Definition form. For Piping and Equipment models, an additional operation to create database tables must also be performed before these models can be used by PDS.

Model Setup Data Form The Model Setup Data form is used to specify the default network address and directory path to be used when creating new model files. You can specify a different default location for each discipline. You can also define the default reference model symbology for each discipline. When this data has been defined, the Create Model option automatically displays the network address and path name defined for the discipline. You can accept this default data or revise the network address and/or path name to be different from the default. Depending on how the project was created, the default location of the electrical raceway and/or structural models may be defined during project creation. Disciplines - A display only field listing the previously created disciplines. Network_Address - A 26-character node name of the system on which the model file is to be stored (example: Network_Address:jwdoe_3). Directory - The directory in which the model file is to be stored. Color - The Select Color form is displayed, providing the active color settings for the project. Select the color from the form, and choose the Confirm button. Style - Select a line style option.

Plant Design System (PDS) Project Administrator (PD_Project)

91

Project Environment Manager Weight - Place a data point along the slider to set the line weight. 1. Select the Model Setup Option. Select the Model Setup option from the Project Environment Manager form. The Model Setup Data form is displayed.

2. Select Discipline. Select the discipline for the model setup data to define. 3. Select Model Setup Data for Revision or Select Another Discipline. Type the node name and directory path to define the default file location for models of the selected discipline. 4. You can define the default reference model symbology for the active discipline by setting any of the toggles to Enabled. You can also select which symbology option(s) to use. These settings affect the reference model display in the Piping Designer graphics environment.

5. Accept Revision to Model Setup Data. Choose the Confirm button to accept the specified model setup data. 6. Repeat Steps 2 through 5 to define setup data for another discipline. —OR— Choose the Cancel button to dismiss the form.

92

Plant Design System (PDS) Project Administrator (PD_Project)

Project Environment Manager

Copy Model The Copy Model option creates a copy of an existing model file within the current project or to another project. All contents of the specified file are copied to the new file. This option can be used with Piping, Equipment, Structural, or Raceway models. For more information, see the Copy Model option, page 117. The Copy Model command makes the following database-related changes based on the setting for Copy in the Piping Data Control option of the Project Data Manager. The copy setting is determined by the setting in the destination model. Refer to Piping Data Control (on page 182), for more information.  If the copy option is set to Append Prefix, the system adds two asterisks (**) as a prefix to name attributes to signify the piping segment or component has been copied and the name attribute may require updating. The following attributes are considered name attributes for this operation:  line number label  piping component number  pipe tag number  instruct component number  pipe support number  line id  If the copy option is set to No Prefix, the ** prefix is removed when copying a piping segment or a component with a name attribute that includes the ** prefix from a previous copy operation.  Regardless of how this option is set, name attributes that are undefined (blank) will not have the prefix added. The following database-related changes are also made:  For piping components, pipes, and instrument components, the weld numbers at each welded end are set to undefined (blank). The alphanumeric description ID of a piping segment is automatically deleted by a copy operation.  For piping segments, the approval status is set to not approved.  When copying a model from the same project or a different project, the copied model inherits the Site ID of the active project. This change applies only to workshare projects; that is, projects whose site_id attribute is set in pdtable_101.

Inter-Project Copies With Different System of Units When copying a piping model from another project, the system automatically converts certain attributes, such as face-to-face dimension or surface area, when the system of units for those attributes changes from the source project to the destination project. The following data is subject to units conversion in copying piping from one project to another:  Piping Segment Data  insulation thickness  insulation density  heat tracing temperature  Piping Component Data  maximum temperature  face-to-face dimension

Plant Design System (PDS) Project Administrator (PD_Project)

93

Project Environment Manager







94

 dimension a  dimension b  dimension c  surface area  empty weight  water weight  operator weight (or branch reinforcement width or orifice size)  heat tracing temperature  piping outside diameter (five connect points)  face-to-center dimension (five connect points)  gasket gap (five connect points) Piping/Tubing Data  maximum temperature  piping outside diameter  pipe length  surface area  empty weight  water weight  cold spring length  heat tracing temperature  gasket gap (both ends) Instrument Component Data  face-to-face dimension  dimension a  dimension b  dimension c  surface area  empty weight  water weight  operator weight  heat tracing temperature  insulation thickness  insulation density  piping outside diameter (five connect points)  face-to-center dimension (five connect points)  gasket gap (five connect points) Pipe Support Data  weight  isometric dimension a  isometric dimension b  isometric dimension c  isometric dimension d

Plant Design System (PDS) Project Administrator (PD_Project)

Project Environment Manager  isometric dimension e  spring gap length Note: Do not use the inter-project copy option to copy a piping model between projects using different graphic symbology options or having different database structures. For example, do not copy a piping model from a project that uses model categories to a project that uses Fluid Code symbology.

Copying Raceway Models When copying Raceway models, it is possible to propagate the sheet names from seed files to copied models. Additionally, the lock status of of a seed file (locked or unlocked) is honored when a model is copied. The following matrix shows the various combinations possible when copying Raceway models.

Model Number - Type up to 10 characters for the name/number of the design file. Model Name - The system fills in the Model Name field automatically by appending a .dgn extension to the specified model number. The Model Name may be edited. Model Description - Type up to 36 characters for the directory path where the model file is to be created. Application Type - This field should only be change if you need to override the default discipline for interference purposes. For example, this provides a way to use a piping model for HVAC ducting and have the clashes from that model treated by the Interference Checker as HVAC components in terms of assigning responsibility for the clash. Define Offset - Select this option to specify the Easting, Northing, and Elevation coordinates for an offset to be applied to the copied model. Attach Equipment Model - Select this option from the Copy Model Data form to specify an equipment model to be attached to the model to be copied. Verify Piping Materials Class - This toggle verifies the piping materials class of each piping segment to be copied from the source project to the destination project previously defined in the Material Reference Database of the destination project. Only those segments with valid piping materials classes are copied. If the toggle is set to No Verification of Piping Materials Class the file contents are copied without checking piping materials classes. Copy P&ID Node Numbers - When copying models within the same project, set the P&ID Node Number toggle to enable or disable the copying of P&ID node numbers from one piping model to another piping model. The default is Copy P&ID Node Numbers. When copying models

Plant Design System (PDS) Project Administrator (PD_Project)

95

Project Environment Manager between projects, the Copy Piping Model command automatically disables copying of the P&ID node numbers from one piping model to another piping model. Site_ID - This field specifies the work site to which the model will be copied. When copying models from the master site, the Site ID can be set to any site appearing in pdtable_105. When copying models from a satellite site, the Site ID is automatically set to the value for the satellite site, and cannot be changed. The master site can copy models to any site. A satellite site can only copy models into itself. Note: The Site_ID field displays only for a workshare project; that is, a project whose site_id attribute is set in pdtable_101. Submit Immediately or Submission is Delayed - Select Submit Immediately to begin copying the model as soon as you exit the form. —OR— Select Delayed Submission to specify a time to process the copy. 1. Select Copy Model Option. Select the Copy Model option from the Create Options form. The Select Source Model's Project Form (on page 98) is displayed. 2. Select Design Area. Select a design area for the model file to be copied from the list of design areas; then choose the Confirm button. A list of models for the selected design area is displayed on the Select Model to be Copied form.

3. Select Model. Select the existing model design file to be copied; then choose the Confirm button. The Select Area for Copied Model form is displayed. 4. Select Design Area.

96

Plant Design System (PDS) Project Administrator (PD_Project)

Project Environment Manager

5.

6.

7.

8.

9.

10. 11.

12.

13.

Select the design area for the model file to be created from the list of design areas; then choose the Confirm button. The Copy Model Data form is displayed. Specify Model Information. Type the Model Number, Model Description, and Application Type information for the design file to be created. Define a Design Volume Offset. Select Define Offset to define a design volume offset for the model to be copied. The Copy Model Data - Offset form is displayed. For more information, see Design Volume Offset (on page 99). Attach Equipment Model. Select Attach Equipment Model to specify an equipment model to be attached to the model to be copied. The Attach Equipment Model (on page 100) form is displayed. Set Verify Piping Materials Class toggle. Set the toggle to Verify Piping Materials Class or No Verification of Piping Materials Class. Set the P&ID Node Number toggle Copy P&ID Node Numbers or Do Not Copy P&ID Node Numbers. Note: The default is Copy P&ID Node Numbers. If copying from the master site in a workshare environment, select the Site ID into which to copy the model. Select Submit Immediately to begin copying the model as soon as you exit the form. —OR— Select Submission is Delayed to specify a time to process the copy. Accept Model data. Choose the Confirm button to accept the specified data. The Design Volume Coordinate System Definition form is displayed. Refer to Design Volume Coordinate System Definition (on page 239), for information about this option. Submit Copy Request. Choose the Confirm button on the Design Volume Coordinate System Definition form. The copy request is submitted to the batch queue PDcopy_model and the Select Model to be Copied form is displayed.

Plant Design System (PDS) Project Administrator (PD_Project)

97

Project Environment Manager

S e le c t S o u rc e Mo d e l's P ro je c t Fo rm The Select Source Model's Project form displays a list of available projects, allowing selection to copy when establishing a new project. This form works with Piping, Equipment, Raceway, and Structural models. It copies all contents of the specified file to the new file.

Project - This field lists the available projects for source model selection. Each project contains all the information required to design a plant in the PDS environment. Discipline -A grouping of the projects based on application. The Project Control Database is initially created with the following disciplines: Piping, Equipment, Structural, and Raceway. 1. Select Copy Model Option. Select the Copy Model option from the Create Options form. The system displays the Select Source Models Project form. 2. Accept or Select Source Project. Select the project for the model file to be copied from the list of projects. 3. Set Discipline Toggle. Set the discipline toggle to Piping or Equipment for the model file to be copied. 4. Choose the Confirm button to accept the project and discipline.

98

Plant Design System (PDS) Project Administrator (PD_Project)

Project Environment Manager

De s ig n Vo lu m e Offs e t The Design Volume Offset option is used to specify the Easting, Northing, and Elevation coordinates for an offset to be applied to the copied model.

1. Select Define Offset. Select Define Offset on the Copy Model Data form to define a design volume offset for the model to be copied. The Copy Model Data - Offset form is displayed. 2. Specify Offsets. Type the Easting, Northing, and Elevation coordinates for an offset to be applied to the copied model. 3. Accept offsets. Choose Confirm to accept coordinates. The Copy Model Data form is displayed.

Plant Design System (PDS) Project Administrator (PD_Project)

99

Project Environment Manager

Atta c h Eq u ip m e n t Mo d e l The Attach Equipment Model option is used to specify an equipment model to be attached to the model to be copied.

1. Select Attach Equipment Model. Select Attach Equipment Model from the Copy Model Data form to specify an equipment model to be attached to the model to be copied. The Select Equipment Area for Attachment form is displayed. 2. Select Design Area. Select the equipment model file to be attached to the new model design file. 3. Choose Confirm. The Select Reference Model to be Attached form is displayed. 4. Specify Reference Model. Select a reference model to be attached and choose Confirm. The Copy Model Data form is displayed.

100

Plant Design System (PDS) Project Administrator (PD_Project)

Project Environment Manager

Create Database Tables The Create Database Tables option creates tables for piping and equipment models in the design (DD) schema. This is a batch job that can be submitted immediately or at a specified time.

1. Select the Create Database Tables Option. Select Create Database Tables from the Create Options form. The Submit Immediately toggle is displayed. 2. Accept the Create Options form to submit the batch job immediately. —OR— Select Submission is Delayed to specify a time to process the models. 3. Submit Model Creation Request. Choose the Confirm button. When the Create Options form is accepted, the model creation request is submitted to the PDcreate_model batch queue for processing.

Plant Design System (PDS) Project Administrator (PD_Project)

101

Project Environment Manager

Create Model Data from ASCII File The Create Model Data from ASCII File creates areas, models and drawings from an ASCII input file. For piping, equipment, structural, and raceway models, design files are created. For other disciplines, only the model definitions are created. For Piping and Equipment models, you can also specify a Design Volume Coordinate System for each model. Note: This command can be used to create model definitions for existing ModelDraft or Frameworks Plus models without writing over the existing design files.

Format Information in the ASCII files is the same as that entered into the forms seen in the PDS Environment.  The format used to define the model management data is a set of entries of the form: Keyword:data.  There must be a colon (:) separating the keyword and the data.  For any entry in this list, there is a maximum of 132 characters per line of data.  The ASCII file(s) to be used to create a model, must be in order by the keywords listed below. The software will not function at all if the order is wrong.  For structural models, the Force Units, Standard Section Table and User Section Table values come from the FrameWorks Plus information in the project database. The default value for the Third Party Software option is STAADIII, and the default value for the Design Code is AISC-ASD. These defaults are the same values that appear in a model create using the Create Model Interactive command.

Keywords The following keywords are used to define the data; they are the same as the fields specified in the Create Design Area form and the Create Model Data form, including structural models: Site_ID - An optional value for the site ID. If no value is specified, the site ID will be the same as the project site ID set in pdtable_101. If the project does not belong to a site, the site ID is set to NULL. This keyword is case sensitive. This keyword should only appear once in a particular ASCII file. If models are to be created for multiple site IDs, a separate ASCII file is required for each site ID. Discipline - The discipline name exactly as it appears in the PD_Shell environment (example: Discipline:Piping). This is required information. Area_Name - A required 20-character design area name; it must be unique across disciplines (example: Area_Name:Piping_A). Area_Desc - An optional 40-character description for the design area being created (example: Area_Desc:Piping Area A). Note: This keyword is required when creating a new area. If the area already exists, use Area_Name only. Area_Marker_File - An option to indicate that you want an interference marker file for the area (example: Area_Marker_File:Yes). Note: This option is only for use in combination with Area_Desc. Area_Volume_Low/High - An option that indicates if the design area will have a predefined volume for interference checking purposes. This is required if Area_Marker_File is Yes; the low volume and high volume represent the limits of the volume processed by the interference checker (example: Area_Volume_Low:-100,-250,-50 Area_Volume_High:150,30,120).

102

Plant Design System (PDS) Project Administrator (PD_Project)

Project Environment Manager Note: This option is only for use in combination with Area_Marker_File. Sub_Proj_Number - Required information for new structural models. It is the structural subproject number of the FrameWorks Plus or ModelDraft subproject.(example: Sub_Proj_Number:fw_proj1) Note: This option is required when creating a new area in combination with Area_Desc. Model_Number - A required 10-character piping model number of the model to be created (example: Model_Number:Model_A). Model_Desc - A required 40-character description of the model to be created (example: Model_Desc:Model A Description). File_Spec - An optional 14-character file specification of the model to be created. If a value is not specified or the keyword is missing, the file specification defaults to the model number with the extension .dgn (example: Model_A.dgn). Note: This option is not supported for structural models, because the file specification is defined in the subproject. Path_Name - An optional 35-character directory path where the model file is to be created (example: d:\proj\models\). If this value is not specified or the keyword is missing, the default values as defined with the Model Setup option are used. Note: This option is not supported for structural models, because the file specification is defined in the subproject. Network_Address - An optional 26-character node name of the system on which the model file is to be stored (example: Network_Address:jwdoe_3). This value is not specified or the keyword is missing, the default values as defined with the Model Setup option, are used. Note: This option is not supported for structural models, because the file specification is defined in the subproject. DVCS_Desc - A optional 40-character Design Volume Coordinate System description. This entry is only used by piping and equipment models (example: DVCS_Desc:Design Vol Coordinate System of Model A). Monument_in_DVCS - Optional easting, northing, and elevation values (separated by commas) of the center of the Design Volume Coordinate System (example: Monument_In_Dvcs:100,100,100). This data is only used by piping and equipment models. If the data is not specified, the Design Volume Coordinate System's monument defaults to the center of the model. DVCS_Monument_in_Plant - Optional easting, northing, and elevation values (separated by commas) of the Design Volume Coordinate System monument in terms of the Plant Coordinate System (example: DVCS_Monument_in_Plant:200,200,100). This data is only used by piping and equipment models. If the data is not specified, the Design Volume Coordinate System's monument defaults to the center of the model. Orientation_of_DVCS - An optional value indicating the orientation of the x-axis in a Plan View as defined by one of the following values: East (the default value if not specified otherwise) North An angle measured clockwise from the MicroStation X-axis (example: Orientation_of_DVCS:45). This data is only used by piping and equipment models. If the data is not specified, the East axis of the Design Volume Coordinate System is aligned with the x-axis of the MicroStation design file coordinate system. Application_Type - A optional value indicating the discipline association for interference checking purposes. It associates the design model with a different discipline for reporting

Plant Design System (PDS) Project Administrator (PD_Project)

103

Project Environment Manager clashes. The default is the discipline where the design model is created (example: Application_type:Piping). Model_type - For structural models only, the type of structural model to be created. Its value is set as follows: sparse - Creates project control database information for a sparse model in the \MOD directory and creates the required files in this directory. propagated - Specifies model_type=0 in pdtable_113. Running batch propagation on a file with this status results in a propagated-only model. This value creates an entry in the project control database for a propagated design file in the \FRZ directory. both - Specifies model_type=2 in pdtable_113. This value specifies that while running batch propagation, the .prp file will contain the sparse model (a single line model) and a 3D model (the propagated model). This value creates a project control database entry for a propagated model in the \FRZ directory. The only Model_Type value which actually creates physical files is sparse. This value, if the model does not already exist, executes the FrameWorks Plus cremod utility, which creates all 14 files in the FW+ project\MOD directory as well as a corresponding entry in pdtable_113. The propagated and both values do NOT create physical files; they only create entries in pdtable_113. Model_Status - An optional value for the model status from code list set 1605. This value is used to exclude models from being processed in PD_Clash. The following is an example of a simple file used to create one piping models and one structural model that belong to the HUNTSVILLE site: Discipline:Piping Area_Name:Piping_A Area_Desc:Piping Area A Model_Number:A2pipe1 Model_Desc:Piping Model 1 from ASCII File_Spec:A2pipe1.dgn Path_Name:C:\users\acme\proj1\ Network_Address:pds_serv DVCS_Desc:Model DVCS Monument_in_DVCS:-1000,0,0 DVCS_Monument_in_Plant:350,325,0 Orientation_of_DVCS:North Application_Type:Piping Discipline:Structural Area_Name:SA1 Area_Desc:FrameWorks Plus Area A Steel Sub_Proj_Number:fwproj1 Area_Marker_File:Yes Area_Volume_Low:-100,-250,-50 Area_Volume_High:150,30,120 Model_Number:steel1 Model_Desc:Structural Model 1 from ASCII Model_Type:both Path_Name:c:\users\acme\stproj1 Network_Address:pds_serv Application_Type:Structural Site_ID:HUNTSVILLE The following listing is an example of an ASCII file used to create structural models and project control database information.

104

Plant Design System (PDS) Project Administrator (PD_Project)

Project Environment Manager Discipline:Structural Area_Name:AS1 Area_Desc:Frameworks Plus Area Steel Area_Marker_File:Yes Area_Volume_Low:-100,-250,-50 Area_Volume_High:150,30,120 Sub_Proj_Number:fwproj1 Model_Number:steel1 Model_Desc: linear Model_Type:sparse Application_Type:Structural Model_Number:steel1 Model_Desc:linear prp Model_Type:both Application_Type:Structural

Before Using This Command Create an ASCII file to define the models to be created using the specified conventions. For structural models and areas, the FrameWorks Plus Project must have been created using the Project Administrator > Project Setup Manager > Insert FrameWorks Project command. 1. Select Create Model from ASCII File Option. Select the Create Model from ASCII File option from the Create Options form. The Create Model from ASCII File form is displayed.

2. Specify ASCII File Spec. Type the information for the location of the ASCII file in the ASCII File Name, Directory and Network Address fields. 3. Submit Immediately or Submission is Delayed

Plant Design System (PDS) Project Administrator (PD_Project)

105

Project Environment Manager Select Submit Immediately to begin processing the request as soon as you exit the form. —OR— Select Submission is Delayed to specify a time to process the request. 4. Accept the specified time. Choose the Confirm button to accept the specified time. The request is submitted to the batch queue PDcreate_model. Note: For Piping and Equipment models created using this method, the tables in the Piping Design Database must still be created. Use the Create Database Tables option of the Project Environment Manager for this.

Revise Options Form The Revise Options form is used to revise the information in the Project Control Database. You can revise the descriptive data for the project and disciplines, design areas, or model files. An entire project or a single model can also be relocated. Select the Revise option from the Project Environment form to display the Revise Options form.

Revise Project Data (on page 107) - Displays the Revise Project Data form which is used to revise the project/client information for the active project. Revise Project Location (on page 108) - Displays the Revise Project Location options to move project data to another location or to update file pointers if the project data was moved outside of the PDS environment. Revise Discipline Data (on page 120) - Revises the name of the selected discipline.

106

Plant Design System (PDS) Project Administrator (PD_Project)

Project Environment Manager Revise Design Area Data (on page 141) - Revises the description of a design area or modifies the volume coordinates of the design area. Revise Model Data (on page 121) - Revises the name of a model file or modifies the description. Revise Area Model Association (on page 122) - Assigns a model file to a different design area (moves the model from one design area to another). Revise Site ID for Models (on page 124) - Assigns a model file to a different work site.

Revise Project Data The Revise Project Data form is used to revise the project/client information for the active project. The system displays existing information for the project (initially defined when the project was created).

Project Name - Type up to 40 characters for the project name or project description. This does not affect the project number. Job Number - Type up to 40 characters for the job number. Company Name - Type up to 40 characters for the name of the client. Plant Name - Type up to 40 characters for the location of the project. Site ID - The Site ID specifies the work site to which the project belongs. Displays the Select Site form. Select a site from the list and click Accept to change the Site ID. 1. Select the Revise Project Data Option. Select the Revise Project Data option from the Revise Options form. 2. Select Attribute for Revision. 3. Select the Project Name, Job Number, Company Name, or Plant Name field to be revised.

Plant Design System (PDS) Project Administrator (PD_Project)

107

Project Environment Manager 4. Type Revisions. Type any changes to the project/client information. 5. If necessary, select the Site ID field to display the Select Site form and assign the project to a different work site. On the Select Site form, select a site and choose Accept. The Revise Project Data form displays. 6. Accept Specification. Choose the Confirm button to accept the specification. The project data is updated in the Project Control Database.

Revise Project Location The Revise Project Location option provides the tools to move the project information from one location to another. In similar manner, models and drawings can be moved through the PDS environment, or if they were moved outside of the PDS environment, their new locations can be specified to the project control database.

Before Using This Option You must have the necessary privileges to move the files to the specified directory. Warning: Back up the project in case of system failure. This is a move operation, not a copy; therefore, the files will be deleted from the old location. The following options are available:  Move Project Directory (on page 109) - Displays the Move Project Data form to move project data (including seed files, Interference Marker files, DDL files).

108

Plant Design System (PDS) Project Administrator (PD_Project)

Project Environment Manager 

 

 

Update Project File Specifications (on page 110) - Displays the Update Project Location form to perform the same function as Move Project Data except that no files are copied. The project files must already reside at the destination. This option can be used if the project information was moved outside of the PDS environment. Move Models (on page 112) - Displays the Move Models form to move model files from one location to another. Update Model File Specifications (on page 113) - Displays the Update Model File Specifications form to perform the same function as Move Models except no files are copied. The files must already reside at the destination. This option can be used if model files were moved outside the PDS environment. Move Drawings (on page 115) - Displays the Move Drawings form to move drawing files from one location to another. Update Drawings File Specifications (on page 118) - Displays the Update Drawing File Specifications form to perform the same function as Move Drawings except no files are copied. The files must already reside at the destination. This option can be used if drawings were moved outside the PDS environment.

Mo ve P ro je c t Dire c to ry The Move Project Data form is used to move the following data:  Project seed files (including raceway seed files for integrated projects and any alternate drawing seed files)  Project plot plan model  Interference marker files  Queue description file  Drawing plot size table  Category text files Note: When you move a project, the project files are moved and the proj file updated to reflect the new location, but it is a good practice to make sure that all required files have been moved from the old project directory to the new project directory. New Network Address - Type up to 26-characters to identify the new network address for the project data.

Plant Design System (PDS) Project Administrator (PD_Project)

109

Project Environment Manager New Directory - Type up to 50-characters to identify the new directory for the project data.

1. Select Move Project Directory from the Revise Project Location form. The Move Project Directory form is displayed. 2. Specify Network Address/Path Name. Type the destination node name and directory for the project data in the New Network Address and New Path fields. Note: The specified directory must be a valid directory that already exists. 3. Initiate the request. Choose the Confirm button to initiate the request. The project files are moved to the specified destination.

Up d a te P ro je c t File S p e c ific a tio n s The Update Project File Specifications option updates the project control database with the new location for the project files. It should be used if the project files already exist in the new project directory. This option is identical to Move Project Directory, except no files are moved. The system reports an error if the project files do not exist at the specified new location. New Network Address - Type up to 26-characters to identify the network address of the project data.

110

Plant Design System (PDS) Project Administrator (PD_Project)

Project Environment Manager New Directory - Type up to 50-characters to identify the new directory of the project data.

1. Select Update Project File Specifications. 2. Select Update Project file Specifications from the Revise Project Location form. The Update Project Location form is displayed. 3. Specify New Network Address/Path Name. Type the destination node name and directory for the project data in the New Network Address and New Path fields. Note: The project files must exist in the new directory. 4. Initiate the Request. Choose the Confirm button to initiate the request. The project control database is updated with the new location.

Plant Design System (PDS) Project Administrator (PD_Project)

111

Project Environment Manager

Mo ve Mo d e ls The Move Models option moves selected model files to a specified location. It moves all model-specific data (model_number.*) including the interference envelope file associated with the model. For piping models, it also includes any diagnostic report files. Model Number - A 10-character name/number of the design file. This field is display only. Source Address - The network address of the model files to be moved. This field is display only. Source Directory - The source directory identification of the model files to be moved. This field is display only. Destination Address - The network address where the model files are to be moved. This field can be modified. Destination Directory - The directory identification where the model files are to be moved. This field can be modified. Move All to Same Destination toggle - Displays the fields to identify destination address and directory for all models in the active area. Move All to Default Location - Moves all model files to a previously specified default location in the active area. 1. Select the Move Models Option. Select Move Models from the Revise Project Location form to move a model design file or set of files. The active disciplines for the project are displayed. 2. Select Discipline. Select a discipline; then choose the Confirm button. The design area for the current discipline are displayed. 3. Select Design Area. Select the area of the models to be moved; then choose the Confirm button.

112

Plant Design System (PDS) Project Administrator (PD_Project)

Project Environment Manager The Move Model Files form is displayed, enabling you to specify the destination.

4. Specify Destinations. Select model file(s), and type the destination(s). Use the scroll arrows to scroll through the listings. —OR— Select Move All to Same Destination to move all the listed files to a specified destination. —OR— Select Move All to Default Location to move all the listed files to the specified default drawing directory as specified in the Model Setup Data form. 5. Accept Destination(s). Choose the Confirm button to accept the defined destination(s).

Up d a te Mo d e l File S p e c ific a tio n s The Update Model File Specifications option is used to update the project control database with the new locations of project models. This option should be used if the model files already exist in the destination directory. This option is identical to Move Models, except no files are copied. The system reports an error if the model files do not exist at the specified destination. Model Number - A 10-character name/number of the design file. This field is display only. Source Address - The network address for the model files to be updated. This field is display only. Source Directory - The source directory identification of the model files to be updated. This field is display only. Destination Address - The network address where the model files have been moved or copied.

Plant Design System (PDS) Project Administrator (PD_Project)

113

Project Environment Manager Destination Directory - The directory identification where the model files have been moved or copied. Move All to Same Destination toggle - Displays the fields to identify destination address and directory for all models. Move All to Default Location - Moves all model files to a previously specified default location. 1. Select the Update Model File Specifications Option. Select Update Model File Specifications from the Revise Project Location form to update a model or set of models. The active disciplines for the project are displayed. 2. Select Discipline. Select a discipline; then choose the Confirm button. The design areas for the current discipline are displayed. 3. Select Design Area. Select the area for the model file(s) to be updated; then choose the Confirm button. The Update Model File Specification form is displayed, enabling you to specify the new locations.

4. Specify Destinations. Select model file(s), and type the destination(s). Use the scroll arrows to scroll through the listings. —OR— Select Move All to Same Destination to move all the listed files to a specified destination. —OR—

114

Plant Design System (PDS) Project Administrator (PD_Project)

Project Environment Manager Select Move All to Default Location to move all the listed files to the specified default drawing directory as specified in the Model Setup Data form. 5. Accept Destination(s). Choose the Confirm button to accept the defined destination(s).

Mo ve Dra win g s The Move Drawings option moves selected drawing files to a specified location. It moves all drawing-specific data (drawing_number.*) with the drawing. If applicable, the system recognizes any seed drawings defined on the basis of a specific drawing type. Drawing Number - A 10-character name/number of the drawing. This field is display only. Source Address - The network address for the drawings to be moved. This field is display only. Source Directory - The source directory identification of the drawings to be moved. This field is display only. Destination Address - The network address where the drawings will be moved. This field can be modified. Destination Directory - The directory identification where the drawings will be moved. This field can be modified. Move All to Same Destination toggle - Displays the fields to identify destination address and directory for all drawings in the current type. Move All to Default Location - Moves all drawings in the current type to a specified default location. 1. Select the Move Drawings Option. Select Move Drawings from the Revise Project Location form to move a drawing file or set of files.

Plant Design System (PDS) Project Administrator (PD_Project)

115

Project Environment Manager The Move Drawings form is displayed, enabling you to select the drawing type to move.

2. Select Drawing Type. Select a drawing type, then choose the Confirm button.

116

Plant Design System (PDS) Project Administrator (PD_Project)

Project Environment Manager The fields update to show all the drawings in that drawing type.

3. Specify Destinations. Select drawing file(s), and type the destination(s). You can use the scroll arrows to scroll through the listings. —OR— Select Move All to Same Destination to move all the listed drawings to a specified destination. —OR— Select Move All to Default Location to move all the listed drawings to the specified default drawing directory as specified in the Model Setup Data form. 4. Accept Destination(s). Choose the Confirm button to accept the defined destination(s).

Plant Design System (PDS) Project Administrator (PD_Project)

117

Project Environment Manager

Up d a te Dra win g s File S p e c ific a tio n s The Update Drawings File Specifications option is used to update the project control database with the new locations of selected drawings. It should be used if the files already exist in the destination directory. This option is identical to Move Drawings, except no files are copied. The system reports an error if the drawing files do not exist at the specified destination. Drawing Number - The name/number of the drawing. This field is display only. Source Address - The network address for the drawings to be updated. This field is display only. Source Directory - The source directory identification of the drawings to be updated. This field is display only. Destination Address - The network address where the drawing files have been moved or copied. This field can be modified. Destination Directory - The directory identification where the drawing files have been moved or copied. This field can be modified. Move All to Same Destination toggle - Displays the fields to identify a destination address and directory for all drawings. Move All to Default Location - Moves all drawing files to a previously specified default location. 1. Select the Update Drawing File Specifications Option. Select Update Drawing File Specifications from the Revise Project Location form to update a drawing file or set of files. The active drawing types for the project are displayed. 2. Select Drawing Type. Select a drawing type; then choose the Confirm button.

118

Plant Design System (PDS) Project Administrator (PD_Project)

Project Environment Manager The Update Drawing File Specification form is displayed, enabling you to specify the destination.

3. Specify Destinations. Select drawing file(s), and type the destination(s). Use the scroll arrows to scroll through the listings. —OR— Select Move All to Same Destination to move all the listed files to a specified destination. —OR— Select Move All to Default Location to move all the listed files to the specified default drawing directory. 4. Accept Destination(s). Choose the Confirm button to accept the defined destination(s).

Plant Design System (PDS) Project Administrator (PD_Project)

119

Project Environment Manager

Revise Discipline Data The Revise Discipline Data option is used to modify the name of an existing discipline. This option should not be used to change the meaning of any disciplines. Discipline Name - A unique name must be assigned to each new discipline. PLANTGEN Discipline toggle - Only one discipline per project can be designated as a PLANTGEN discipline.

1. Select the Revise Discipline Data Option. 2. Select the Revise Discipline Data option from the Revise Options form. A list of available disciplines is displayed. 3. Select Discipline. Select the discipline to be modified, then choose the Confirm button. The Discipline Name field and PLANTGEN Discipline toggle are displayed on the Revise Options form. 4. Specify Discipline Name. Type the new name for the selected discipline. 5. Accept or Select Option or Discipline. Choose the Confirm button to accept the specified discipline information. The list of disciplines is updated to reflect the specified change.

120

Plant Design System (PDS) Project Administrator (PD_Project)

Project Environment Manager

Revise Model Data The Revise Model Data option is used to change the name, description, application type or model status of an existing model file. 1. Select the Revise Model Data Option. Select the Revise Model Data option from the Revise Options form. A list of disciplines is displayed. 2. Select Discipline. Select the discipline of the model file to be modified; then choose the Confirm button. The design areas for the selected discipline are displayed. 3. Select Design Area. Select the Design Area of the model file to be modified; then choose the Confirm button. The model files for the selected design area are displayed. 4. Select Model. Select the model to be revised; then choose Confirm. The model number and description are displayed.

5. Select Attribute for Revision or Select Another Model. Type any modifications to the model number or model description. To change the Application Type and/or Model Status, select the field and select the setting from the displayed list. Note: If you change the model number, the names of any related files in the model directory are automatically changed to match the new model number. Exceptions to this action are

Plant Design System (PDS) Project Administrator (PD_Project)

121

Project Environment Manager models that have been sent to SmartPlant Review and output files that are placed in a location other than the model directory. This option supports only the following disciplines: Piping, Equipment, Raceway, and Microstation. The Structural discipline is not supported. For HVAC models, it is recommended that you change the model name in the HVAC environment before updating the name in the PDS project, so that the filelist.dat file for the HVAC project will be updated. 6. For structural models, set the toggle to Propagated and Sparse or Propagated Only. 7. Accept or Cancel Changes. Choose the Confirm button to process the specified change(s). —OR— Choose the Cancel button to dismiss the form. The system verifies the specified name is valid for use as a design file name. The project control database is updated and a prompt to select another model file.

Revise Area Model Association The Revise Area Model Association option is used to associate a model file with a specified design area. This has the effect of moving the model file from one design area to another. 1. Select Revise Area Model Association. Select the Revise Area Model Association option from the Revise Options form. A list of disciplines is displayed. 2. Select Discipline. Select the discipline for the model file to be modified; then choose the Confirm button. The design areas for the selected discipline are displayed. 3. Select Design Area. Select the existing design area for the model file to be modified; then choose the Confirm button.

122

Plant Design System (PDS) Project Administrator (PD_Project)

Project Environment Manager The Revise Area Model Association form is displayed showing the available models.

4. Select Model. Select the model to be revised from the form.

Plant Design System (PDS) Project Administrator (PD_Project)

123

Project Environment Manager 5. Select Area Association for Model. Select the new design area for the model; then choose the Confirm button. The selected model record is updated.

Revise Site ID for Models This option allows you to reassign models to different work sites by changing the site ID by project, area, or model. Note: This option is only available at the master site.

By Project - Displays models by project for Site ID revision. For more information, see Revise Site ID for Models By Project (on page 125). By Area - Displays models by design area for Site ID revision. For more information, see Revise Site ID for Models By Area (on page 126). By Model - Displays individual models for Site ID revision. For more information, see Revise Site ID for Models By Model (on page 127).

124

Plant Design System (PDS) Project Administrator (PD_Project)

Project Environment Manager

Re vis e S ite ID fo r Mo d e ls By P ro je c t This option allows you to update the Site ID for models in the active project. Note: This option is only available at the master site. Model Number – Lists all the models in the active project. Source Site_ID – Displays the current site to which the model belongs. Destination Site_ID – Specifies the new site to which the model will belong. Change All to Same Site_ID – Allows you to change all models in the active project to belong to the same site.

Specific Models 1. Select By Projects from the Revise Site_ID for Models form. The Revise Site_ID for Models form displays. 2. Select the Destination Site_ID to change. The Select Site form displays. 3. Select a site. 4. Click Accept. The Revise Site_ID for Models form displays with the new Site ID.

All Models in Project 1. Select By Projects from the Revise Site_ID for Models form. The Revise Site_ID for Models form displays. 2. Click Change All to Same Site_ID. The Site_ID for All Models field displays.

3. Select the Site_ID for All Models field. The Select Site form displays. 4. Select a site. 5. Click Accept. The Revise Site_ID for Models forms displays with all models assigned to the new Site ID.

Plant Design System (PDS) Project Administrator (PD_Project)

125

Project Environment Manager

Re vis e S ite ID fo r Mo d e ls By Are a This option allows you to change the Site ID for models in a particular design area. Note: This option is only available at the master site.

Specific Models 1. 2. 3. 4. 5. 6.

Select By Area from the Revise Site_ID for Models form. Select a discipline. Click Accept. Select an area. Click Accept. Select the Destination Site_ID to change. The Select Site form displays. 7. Select a site. 8. Click Accept. The Revise Site_ID for Models form displays with the new Site ID.

All Models in Area 1. 2. 3. 4. 5. 6.

Select By Area from the Revise Site_ID for Models form. Select a discipline. Click Accept. Select an area. Click Accept. Click Change All to Same Site_ID. The Site_ID for All Models field displays.

7. Select the Site_ID for All Models field. The Select Site form displays. 8. Select a site. 9. Click Accept. The Revise Site_ID for Models forms displays with all models assigned to the new Site ID.

126

Plant Design System (PDS) Project Administrator (PD_Project)

Project Environment Manager

Re vis e S ite ID fo r Mo d e ls By Mo d e l This option allows you to change the site ID for individual models. Note: This option is only available at the master site. 1. Select By Model from the Revise Site_ID for Models form. 2. Select a discipline. 3. Click Accept. 4. Select an area. 5. Click Accept. 6. Select a model. 7. Click Accept. 8. Select the Destination Site_ID to change. The Select Site form displays. 9. Select a site. 10. Click Accept. The Revise Site_ID for Models form displays with the new Site ID.

Delete Options Form The Delete Options form is used to delete disciplines, design areas, and model design files. Items must be deleted from the bottom up. That is, you must delete all the models for a design area before you can delete the design area, and you must delete all the design areas for a discipline before you can delete the discipline. Delete Discipline (on page 128) - Deletes the specified discipline name from the active project. Delete Design Area Form (on page 130) - Displays the Delete Design Area form to delete the specified design area for the selected discipline.

Plant Design System (PDS) Project Administrator (PD_Project)

127

Project Environment Manager Delete Model (on page 131) - Displays the Delete Model form to delete individual model files and the corresponding Design Database tables.

1. Select Delete Options. Select the Delete option on the Project Environment Manager form. The Delete Options form is displayed. 2. Select Option. Select the Delete Discipline, Delete Design Area, or Delete Model option. The associated discipline, design area or model form is displayed.

Delete Discipline The Delete Discipline option is used to delete a specified discipline from the active project. A discipline file cannot be deleted when it contains any design area or model files. You must delete the individual files before removing the discipline.

128

Plant Design System (PDS) Project Administrator (PD_Project)

Project Environment Manager Note: The system does not allow you to delete the six original PDS disciplines.

1. Select the Delete Discipline Option. Select the Delete Discipline option from the Delete Options form. A list of user-defined disciplines is displayed. 2. Select Discipline or Another Option. Select the discipline to be deleted from the list of disciplines for the project. 3. Select Another Discipline or Option. Choose the Confirm button to delete the specified discipline name. The system checks the project control database. If the discipline does not contain any design, data, the system deletes the discipline from the database and removes the name from the list of disciplines.

Plant Design System (PDS) Project Administrator (PD_Project)

129

Project Environment Manager

Delete Design Area Form The Delete Design Area option is used to delete a specified design area from the active project. You cannot delete a design area that contains any model files. You must delete the individual files before removing the design area. For piping design areas, this option also deletes any Isometric Drawing Management data associated with the selected design area.

Design Area and Description - Displays a list of the available Design Areas with the associated Design Area Descriptions. 1. Select the Delete Design Area Option. 2. Select the Delete Design Area option from the Delete Options form. A list of disciplines is displayed. 3. Select Discipline or Another Option. Select the discipline for the design area to be deleted, then choose the Confirm button. The design areas for the selected discipline are displayed. 4. Select Design Area. Select the design area to be deleted. 5. Accept or Select Another Design Area. Choose the Confirm button to delete the selected design area. The design area is deleted from the project control database and the design area name is deleted from the list of design areas. The area marker file (if present) is also deleted.

130

Plant Design System (PDS) Project Administrator (PD_Project)

Project Environment Manager

Delete Model The Delete Model option is used to delete a specified model from the active project. For piping, equipment, and raceway models, it deletes the design file and removes the associated database tables from the project control database and project design database. For ModelDraft models, it deletes both the propagated model and the sparse model. For other disciplines, it only removes the database entry from the project control database. The model deletion is processed as a batch job. Deleting a model requires write privilege to all other models and drawings in the project to determine if the model being deleted is a reference model to any other model or drawing in the project. If any other model or drawing in the project is in use for write access, the model is not deleted. Caution: Since all other models and drawings are checked to see if the model being deleted is attached as a reference file, the delete model operation may take a long time in large projects. It will also take a long time if the system is unable to open (for any reason) a model or drawing for checking. Model Number - A 10-character name/number of the design file. This field is display only. Model Description - The directory path where the model file resides.

1. Select the Delete Model Option. Select the Delete Model option from the Delete Options form. A list of disciplines is displayed. 2. Select Discipline or Another Option. Select the discipline of the model to be deleted; then choose the Confirm button. A list of design areas is displayed.

Plant Design System (PDS) Project Administrator (PD_Project)

131

Project Environment Manager 3. Select Design Area. Select Delete Design Area Form (on page 130) then choose the Confirm button. All the models for the selected design area are displayed. 4. Select Model. Select the model to be deleted. 5. Accept or Select Another Model. Select Submit Immediately to begin deleting the model as soon as you exit the form. —OR— Select Submission is Delayed to specify a time to process the deletion. 6. Accept Deletion. Choose the Confirm button to accept the deletion. The deletion request is submitted to the batch queue PDdelete_model. At the specified time, the request begins processing and the model file is deleted with its associated database files.

Report Options Form The Report Options form is used to create reports of project environment data from the Project Control Database.

Report - Models (on page 133) - Displays the Report - Models form, which creates a report of all the model files for the active project.

132

Plant Design System (PDS) Project Administrator (PD_Project)

Project Environment Manager Report - Named Items (on page 135) - Displays the Report - Named Items form which creates a report for a specified named item in any of the project model files.

Report - Models The Report - Models option creates a report of the model files in the Project Design Database. This report lists all the models in the active project by discipline and design area. It lists the models alphanumerically by model number in ascending order. Note: The Project Control Manager can also be used to generate a customized model management report. Refer to Project Control Manager Form (on page 257), for more information on this option. A sample report format for model management data is delivered in the file ~/pdprojec/sample/model_mgt.fmt. Print/Delete - Submits the generated report output file to the specified print queue and deletes the output file. Print/Save - Submits the generated report output file to the specified print queue and saves the output file. Save - Saves the output file without printing. 1. Select the Report - Models Option. Select the Report - Models option from the Report Options form. A set of printing options are displayed in the middle of the form.

2. Select the printing option. Select Print/Delete, Print/Save, or Save. 3. Accept the Confirm and Create the Report. The created report file is written to the file model_report in the project directory.

Plant Design System (PDS) Project Administrator (PD_Project)

133

Project Environment Manager The following shows the basic layout of the report.

134

Plant Design System (PDS) Project Administrator (PD_Project)

Project Environment Manager

Report - Named Items The Report - Named Items option creates a report on a Named Item in the Project Design Database. This report contains a list of model files which contain the Named Item, their associated area specifications, and their associated disciplines. Named Items Options - A report may be generated based on the selected option: Piping Component Number Line Number Label Instrument Component Number Equipment & Nozzle Number Line ID Pipe Equipment Number Pipe Support Data entry field - Type selection data associated with the chosen Named Item Option. Submit Immediately or Submission is Delayed Select Submit Immediately to begin copying the model as soon as you exit the form. —OR— Select Submission is Delayed to specify a time to process the copy.

1. Select the Report-Named Item form. Select the Report-Named Item form from the Report Options form. The Report-Named Item form is displayed. 2. Select Option. Select the option for the type of Named Item to be reported. One of the following prompts is displayed based on the option you select: 3. Specify Line Number Label. Type the line number label to be reported. The Line Number Label is composed of several attributes as defined in the Label Description Library.

Plant Design System (PDS) Project Administrator (PD_Project)

135

Project Environment Manager 4. Specify Line ID. Type the line identification to be reported. The Line ID is composed of the Unit Code, Line Number, and the fluid code. Specify Component Number Specify Instrument Number Specify Pipe Number Specify Pipe Support Number Type the tag number of the item(s) to be reported. 5. Specify Equipment Number. Type the equipment identification. 6. Specify Nozzle Number. Type the equipment number/nozzle ID. Note: You can specify more than one value for the selected attribute. 7. Submit Immediately or Submission is Delayed. Select Submit Immediately to begin the report as soon as you exit the form. —OR— Select Submission is Delayed to specify a time to process the report. 8. Accept Data. After specifying all the values to be reported, choose the Confirm button to accept the data defined for the search and to submit the job to the batch queue for processing. The Project Design Database is searched for the named item(s), and a report of the associated model specification is created in a file named project.rni in the /temp directory.

136

Plant Design System (PDS) Project Administrator (PD_Project)

Project Environment Manager

Plant Design System (PDS) Project Administrator (PD_Project)

137

SECTION 7

Create Design Area Data The Create Design Area Data option creates new design areas for the a discipline. A design area can optionally specify a fixed volume of the project area. The volume for a design area can define a unique area or overlap that of another design volume. Numerous operations in PDS can be performed on the entire project, on all models in a specified area, or on single models in an area. Note: The volumes associated with a design area have a marked effect on interference checking. For a complex discipline such as Piping, divide the project into several areas rather than specify one design area for the entire project volume.

Create Design Area Data Form The Create Design Area Data form is used to specify the Design Area Name, Design Area Description and also if the area has a predefined volume. Design Area Name - Specifies a name for the new Design Area. Type up to 10 characters for the new Design Area Name. Do not use special characters such as the at symbol(@), the pound sign (#), the percent symbol (%), the caret symbol (^), the ampersand (&), the asterisk (*), the exclamation point (!), or the pipe symbol (|). Description - Specifies a description for the new Design Area. Type up to 40 characters for the description of the new Design Area, or press Enter to skip this field. Interference Management Design Area toggle - When this toggle is selected, an interference management marker is created for the design area. This file is used to display interference markers to review and control clashes. (The system uses the design area name as the name of the marker file with the extension ., for example, pipea1.1.) If the toggle is set to Interference Management Design Area, the Volume fields are active to define the volume coordinates for the design area. The decision to use predefined volume definitions for design areas requires careful planning. See the Interference Checker/Manager (PD_Clash) guide for additional discussion of this topic. Type the easting, northing, and elevation coordinates to define the volume of the design area. Use negative values to specify coordinates in the west or south.

Plant Design System (PDS) Project Administrator (PD_Project)

139

Create Design Area Data Define DVCS - Activates the Design Volume Coordinate System Definition form, allowing you to specify DVCS settings. This button only appears if you are creating a design area in the Clash discipline.

1. Select Option. Select the Create Design Area Data option from the Create Options form. The Create Design Area form is displayed. 2. Select Discipline. Select the discipline for the design area to be created from the list of displayed disciplines. 3. Select Option or Discipline. Choose the Confirm button to accept the specified discipline name. —OR— Select another option to cancel the design area definition. 4. Specify Design Area Name. Type a Design Area Name. The system verifies the specified name is valid for use as a design file name. 5. Specify Design Area Description. Select the Design Area Description field and type the description text. 6. For Structural design areas, select the Sub-Project field, and select a structural project from the list. 7. For Clash discipline design areas using DVCS, select Define DVCS and use the Design Volume Coordinate System Definition form to enter the DVCS settings. Click Accept on

140

Plant Design System (PDS) Project Administrator (PD_Project)

Create Design Area Data the Design Volume Coordinate System Definition form to return to the Create Design Area form. 8. Set Interference Management Design Area toggle. Set the toggle to Interference Management Design Area to create an interference management file for the design area and specify a predefined volume. OR Set the toggle to No Interference Management Design Area to use the project-wide marker file, rather than creating a marker file for this area. Note: This step is not necessary for Clash discipline areas. 9. Accept or Specify Design Area Data. When all information has been defined, choose the Confirm button to accept the definition of the design area. The design area specification is written to the project control database. If a predefined volume was specified, the project marker file is copied to create an interference marker file for that area.

Revise Design Area Data The Revise Design Area Data option is used to revise an existing design area name, description, or predefined volume definition. This option provides file locking for the design area Interference Management models using data in the Project Control Data base. Design Area Name - Specifies a Design Area Name for the revised Design Area. Type up to 10 characters for the new Design Area Name or press ENTER. Do not use special characters such as the at symbol(@), the pound sign (#), the percent symbol (%), the caret symbol (^), the ampersand (&), the asterisk (*), the exclamation point (!), or the pipe symbol (|). Description - Specifies a Design Area Description of the revised Design Area. Type up to 40 characters for the description of the Design Area, or press to skip this field. 1. Select Option. Select the Revise Design Area Data option from the Revise Options form. A list of available disciplines is displayed. 2. Select Discipline. Select the discipline containing the design area to be modified, and choose the Confirm button.

Plant Design System (PDS) Project Administrator (PD_Project)

141

Create Design Area Data The Revise Design Area Data (on page 141) form displays with a list of available design areas.

3. Select Design Area. Select the Design Area to be modified, and choose Confirm.

142

Plant Design System (PDS) Project Administrator (PD_Project)

Create Design Area Data The data associated with the selected design area is displayed.

4. Select Attribute for Revision. Type any modifications to the Design Area name or description. The system verifies the specified name is also valid for use as a design file name. 5. Type the easting, northing, and elevation coordinates to define/change the volume of the design area. Use negative values to specify coordinates in the west or south. 6. Accept Modifications. Choose the Confirm button to accept the modifications. The selected Design Area Specification record is updated. Caution: Choose the Cancel button if no changes were made.

Plant Design System (PDS) Project Administrator (PD_Project)

143

Create Design Area Data

144

Plant Design System (PDS) Project Administrator (PD_Project)

SECTION 8

Project Data Manager The Project Data Manager is used to examine and/or revise the settings used when creating new models or to otherwise tailor the behavior of PDS to meet the needs of the project. This data is used when creating a design area interference marker file, a model design volume, a drawing file, or an interference envelope file. The following conventions describe the forms in the Project Data Manager.  The operation of each form is described in a linear fashion for clarity. However, the options on the form can be selected in any order.  The Shell and Top options can be used to jump back along the command stack rather than exiting the forms one at a time. See PD_Shell Form Conventions (on page 35) under PD Shell.

Project Data Manager Form The Project Data Manager form is used to:  Revise the 3D Plant Design data and RDB seed data used to create model, drawing, and interference marker files.  Revise the 3D Plant Design data and RDB data for existing Piping and Equipment model design volumes.  Revise the 3D Plant Design data and RDB data for existing drawings.  Revise the RDB data for interference marker files. Seed - Displays the Seed Options form, to review or revise the project data stored in the seed files and the project marker file. For more information, see Seed Options Form (on page 146). Piping Model - Displays the Model Options form, to review or revise the project data stored in Piping model files. For more information, see Model (on page 237). Equipment Model - Displays the Equipment Options form, to review or revise the project data stored in Equipment model files. For more information, see Equipment (on page 244). Raceway Model - Displays the Raceway Options form, to review or revise the project data stored in Raceway model files. For more information, see Raceway Model (on page 248). Drawing - Displays the Drawing Options form, to review or revise the project data stored in drawing files. For more information, see Drawing (on page 249).

Plant Design System (PDS) Project Administrator (PD_Project)

145

Project Data Manager Interference - Displays the Interference Options form, to review or revise the project data for interference marker files. For more information, see Interference (on page 253).

1. Select the Project Data Manager Option. Select the Project Data Manager option from the Project Administrator form. 2. Select Option. Select the Seed, Model, Equipment, Drawing, or Interference option. The selected Seed Options, Model Options, Equipment Options, Drawing Options, or Interference Options form is displayed.

Seed Options Form The Seed options form is used to revise the seed files for creating new design volumes and drawings, or revise the project marker file for creation of area interference marker files. A report of all the seed file settings for the active project can also be created. 3D Model Data - Revise - Revises 3D PDS data in the seed files for the active project. For more information, see Revise 3D Model Data (on page 238).

Interference Check Data  

146

Revise - Used to specify settings used when analyzing interference envelopes. For more information, see Revise Interference Check Data (on page 161). Propagate - Applies settings from the project Interference Management model to all design area Interference Management models within the active project or to a list of selected

Plant Design System (PDS) Project Administrator (PD_Project)

Project Data Manager Interference Management models. For more information, see Propagate Interference Check Data (on page 167). Equipment Data Equipment Data - Revise - Revises data in the equipment seed file for the active project. For more information, see Revise Equipment Data (on page 169). Piping Model Data  Revise Seed Files - Revises data in the piping seed file for the active project. For more information, see Revise Piping Model Data (on page 178).  Propagate Seed Files - Applies settings from the active piping model seed file to all piping models within the active project or to a list of selected piping models. For more information, see Propagate Piping Model Data (on page 214). Drawing Data  Revise - Revises data in the drawing seed file for the active project. For more information, see Revise Drawing Data - Seed File (on page 216).  Propagate - Applies settings from the specified drawing seed file to all drawings within the active project, all drawings of a specified type, or a list of selected drawings. For more information, see Propagate Drawing Data (on page 233). Report of Seed File Data - Creates a report of all project seed file settings. For more information, see Report of Seed File Data (on page 236).

1. Select Seed Option Select the Seed option from the Project Data Manager form. The Seed Options form is displayed.

Plant Design System (PDS) Project Administrator (PD_Project)

147

Project Data Manager 2. Select Option Select the 3D Plant Design Data - Revise, Interference Check Data - Revise or Propagate, Equipment Data - Revise, Piping Model Data - Revise or Propagate, Drawing Data - Revise or Propagate, or Report of Seedfile Data option. The selected 3D Plant Design Data - Revise, Interference Check Data - Revise or Propagate, Equipment Data - Revise, Piping Model Data - Revise or Propagate, Drawing Data - Revise or Propagate, or Report of Seedfile Data form is displayed.

Re vis e 3D Mo d e l Da ta The Revise 3D Model Data option is used to revise the 3D PDS data in the seed files for the active project. When this option is selected, the Revise 3D Model Data form is displayed, providing access to the modification options. These options affect all of the project seed files and the project marker file. Coordinate System Definition (on page 149) - Modifies the coordinate system parameters for the project seed file. Angular/Slope Label/Readout (on page 152) - Used to specify the label format for angular dimensioning and slope dimensioning. Date/Time Format (on page 153) - Used to specify the data and time format to be used in the PD_Shell environment. Coordinate Label/Readout Descriptions (on page 155) - Defines the short descriptions for the coordinate axes and coordinate systems. Coordinate Label/Readout Format (on page 157) - Defines layout of the coordinate label and coordinate display. Coordinate Label/Readout Units (on page 158) - Defines the system of units display for coordinate labels and coordinate readout displays.

148

Plant Design System (PDS) Project Administrator (PD_Project)

Project Data Manager Coordinate Label/Readout Precision (on page 160) - Defines the accuracy (roundoff) to be used for dimension labels and readouts.

1. Select the Revise 3D Plant Design Data option from the Seed Options form. The Revise 3D Model Data form is displayed. 2. Select Option. Select the Coordinate System Definition, Angular/Slope Label/Readout, Date/Time Format, Descriptions, Format, Units, or Precision option. The selected Coordinate System Definition, Angular/Slope Label/Readout, Date/Time Format, Descriptions, Format, Units, or Precision form is displayed.

Co o rd in a te S ys te m De fin itio n The Coordinate System Definition option is used to modify the coordinate system parameters for the project seed file. The coordinate system name and the monument (center point) of the coordinate system can be specified. The plant monument is applied to the seed files used to create piping and equipment models, drawings, and interference marker files. This value is defined when a project is created with the Project Setup Manager. The default values for the plant monument can be used for most projects.

Plant Design System (PDS) Project Administrator (PD_Project)

149

Project Data Manager Refer to Create Model (on page 86), and Design Volume Coordinate System Definition (on page 239), for information to define a design volume coordinate system (DVCS).

Plant Coordinate System Description - Type up to 40-characters describing the Plant Coordinate System to be used for the project. Plant Coordinate System Monument - These fields display the easting, northing, and elevation coordinates assigned to the center of the design volume for the plant. This point corresponds to the MicroStation position 0,0,0. Note: If no design areas or models have been created, the coordinates of the plant monument can be revised. Once design areas or models have been created, these fields become review only.

150

Plant Design System (PDS) Project Administrator (PD_Project)

Project Data Manager Example of Plant Coordinate System Monument

Coordinates in the Plant Coordinate System (PCS) are in relation to the plant monument. For example, if the plant monument was modified from its default setting of 0,0,0 to be E. 300', N. 250' and EL. 10', then a point 200 feet east and 150 feet north away from the plant monument would be at E. 500', N. 400' and EL. 10' in the Plant Coordinate System. For more information, see the 3D Coordinate Systems section in the PDS 3D Theory User's Guide. 1. Select Option. Select the Coordinate System Definition option from the Revise 3D Plant Design Data form. The Plant Coordinate System Definition form is displayed. 2. Specify Plant Coordinate System Description. Type the Plant Coordinate System Description for the project. 3. Specify Plant Coordinate System Monument. Type the Easting, Northing, and Elevation for the project. 4. Accept Coordinate System Definition. Choose the Confirm button to accept the displayed Coordinate System Definition. The Revise 3D Model Data form is displayed.

Plant Design System (PDS) Project Administrator (PD_Project)

151

Project Data Manager

An g u la r/S lo p e La b e l/Re a d o u t The Angular/Slope Label/Readout option is used to specify the label format for angular dimensioning and slope dimensioning. Decimal degrees or degrees and minutes can be used. The accuracy (roundoff) can also be specified for the angular/slope values. Angular Label - Toggle the format for angular dimensioning text between Decimal Degrees and Degrees and Minutes. Angular Readout - Toggle the format for angular readout values between Decimal Degrees and Degrees and Minutes. Label/Readout Degrees Accuracy - The displayed options vary depending on the format settings for Angular Label and Angular Readout. Select the precision to be used for angular dimensioning and slope dimensioning text. Degree Short Description and Minute Short Description - These fields are only displayed if the format is set to degrees and minutes. In each field, type a single character to specify the indicators for degrees and minutes. Angular Input - Select this field to toggle the format to define angular input. A horizontal angle can be measures as either a clockwise offset (looking at a plan view) from North (North-0) or a couter-clockwise offset (looking at a plan view) from East (East=0). Slope Readout Formation - Select the dimension format for slope readout values.

1. Select Option. Select the Angular/Slope Label/Readout option from the Revise 3D Plant Design Data form. 2. Specify Angular Label.

152

Plant Design System (PDS) Project Administrator (PD_Project)

Project Data Manager

3.

4.

5.

6.

7. 8.

Toggle the format for angular dimensioning text between Decimal Degrees and Degrees and Minutes. Select Angular Readout. Toggle the format for angular readout values between Decimal Degrees and Degrees and Minutes. Select Label/Readout Degrees Accuracy. Displayed options vary depending on the format settings for Angular Label and Angular Readout. Select the precision to be used for angular dimensioning and slope dimensioning text. Specify Degree Short Description and Minute Short Description. Note: These fields are only displayed if the format is set to degrees and minutes. In each field, type a single character to specify the indicators for degrees and minutes. Select Angular Input. Toggle the format used to define angular input. A horizontal angle can be measured as either a clockwise offset (looking at a plan view) from North (North=0) or a counter-clockwise offset (looking at a plan view) from East (East=0). Specify Slope Readout Formation. Select the dimension format to be used for slope readout values. Accept Angular/Slope Label/Readout Information. Choose the Confirm button to accept the specified Angular/Slope Label/Readout information. The Revise 3D Model Data form is displayed.

Da te /Tim e Fo rm a t The Date/Time Format option is used to specify the display format for the data and time in the PD_Shell environment. The defined setting is also respected by the Plot Manager and the Automated Title Block option. When the Date/Time Format option is chosen, the Date/Time Format form is displayed. Note: For existing seed files, the default date/time format is used until another option is selected. The specified format can be propagated to other drawings or a format specified for an individual drawing within the project. dow MMM DD hh:mm:ss YYYY - The 3-character day of the week, 3-character month, 2-character day, 2-character hour, 2-character minute, 2-character second and 4-character year, separated by spaces representation of the current date and time. This is the default option. DD - MMM - YYYY hh:mm:ss - The 2-character day, 3-character month, 4-character year, 2-character hour, 2-character minute and 2-character second, separated by spaces, representation of the current date and time. DD - MM - YY - The 2-character day, 2-character month and 2-character year, separated by hyphens, representation of the current date and time. MM / DD / YY - The 2-character month, 2-character day and 2-character year, separated by slashes, representation of the current date and time. DD / MM / YY - The 2-character day, 2-character month and 2-character year, separated by slashes, representation of the current date. MMM DD , YYYY - The 3-character month abbreviation, 2-character day and 4-character year representation of the current date.

Plant Design System (PDS) Project Administrator (PD_Project)

153

Project Data Manager DD MMM YYYY - The 2-character day, 3-character month abbreviation and 4-character year representation of the current date. MM / DD - The 2-character month and 2-character day representation of the current date. DD / MM - The 2-character day and 2-character month representation of the current date. Format

Example

dow MMM DD hh:mm:ss YYYY

Mon Feb 28 11:37:23 1994 (default)

DD - MMM - YYYY hh:mm:ss

28-Feb-1994 11:37:23

DD - MM - YY

28-02-94

MM / DD / YY

02/28/94

DD / MM / YY

28/02/94

MMM DD , YYYY

FEB 28, 1994

DD MMM YYYY

28 FEB 1994

MM / DD

02/28

DD / MM

28/02

1. Select Option. Select the Date/Time Format option from the Revise 3D Plant Design Data form. 2. Select Format Select the format from the displayed options. The system uses the current date as a sample to display the options.

154

Plant Design System (PDS) Project Administrator (PD_Project)

Project Data Manager 3. Accept Date/Time Format. Choose the Confirm button to accept the selected Date/Time Format. The Revise 3D Model Data form is displayed.

Co o rd in a te La b e l/Re a d o u t De s c rip tio n s Coordinate labels are used to display coordinate values (locations) in the model or in a drawing. Coordinate readouts are used to display coordinate values in forms and reports. This option is used to define the short descriptions for the coordinate axes and coordinate systems.

Coordinate Label Format and Coordinate Readout Format -These fields at the top of the form display a typical coordinate label and readout using the active option. As settings are changed, these fields are updated to reflect the new format. Coordinate System Design Volume Label - Type up to 12-alphanumeric characters to change the selected Coordinate System Design Volume Label value. Coordinate System Design Volume Readout - Type up to 6-alphanumeric characters to change the selected Coordinate System Design Volume Readout value. Coordinate System Plant Label - Type up to 12-alphanumeric characters to change the selected Coordinate System Plant Label value. Coordinate System Plant Readout - Type up to 6-alphanumeric characters to change the selected Coordinate System Plant Readout value. Coordinate System World Label - Type up to 12-alphanumeric characters to change the selected Coordinate System World Label value. Coordinate System World Readout - Type up to 6-alphanumeric characters to change the selected Coordinate System World Readout value.

Plant Design System (PDS) Project Administrator (PD_Project)

155

Project Data Manager Coordinate Axis East Label - Type up to 6-alphanumeric characters to change the selected Coordinate Axis East Label value. Coordinate Axis East Readout - Type up to 2-alphanumeric characters to change the selected Coordinate Axis East Readout value. Coordinate Axis West Label - Type up to 6-alphanumeric characters to change the selected Coordinate Axis West Label value. Coordinate Axis West Readout - Type up to 2-alphanumeric characters to change the selected Coordinate Axis West Readout value. Coordinate Axis North Label - Type up to 6-alphanumeric characters to change the selected Coordinate Axis North Label value. Coordinate Axis North Readout - Type up to 2-alphanumeric characters to change the selected Coordinate Axis North Readout value. Coordinate Axis South Label - Type up to 6-alphanumeric characters to change the selected Coordinate Axis South Label value. Coordinate Axis South Readout - Type up to 2-alphanumeric characters to change the selected Coordinate Axis South Readout value. Coordinate Axis Elevation Label - Type up to 6-alphanumeric characters to change the selected Coordinate Axis Elevation Label value. Coordinate Axis Elevation Readout - Type up to 2-alphanumeric characters to change the selected Coordinate Axis Elevation Readout value. Dimensioning -Toggle the setting between English and English/Metric. 1. Specify Coordinate System Label. Type up to 12 alphanumeric characters to change the selected coordinate system. Specify Label value. 2. Specify Coordinate System Readout. Type up to 2 alphanumeric characters to change the selected coordinate system Readout value. 3. Specify Coordinate Axis. Type up to 6 alphanumeric characters to change the Label name of the selected coordinate axis. Type up to 2 alphanumeric characters to change the Readout code for a coordinate axis. 4. Select Dimensioning. Toggle the setting between English and English/Metric. 5. Accept Coordinate Label/Readout Descriptions. Choose the Confirm button to accept the specified Coordinate Label/Readout Descriptions information. The Revise 3D Model Data form is displayed.

156

Plant Design System (PDS) Project Administrator (PD_Project)

Project Data Manager

Co o rd in a te La b e l/Re a d o u t Fo rm a t The Coordinate Label/Readout Format option is used to define the layout of the coordinate label and coordinate display. The coordinate label is composed of the coordinate value, the coordinate axis short description, and the coordinate system short description. The coordinate readout is composed of the coordinate value, the coordinate axis readout value, and the coordinate system readout value. Any changes to the coordinate label/readout short descriptions also affect this form.

Coordinate Label - Defines the position of the coordinate value, coordinate axis, and coordinate system in the label format. The active setting (indicated by the selected option) defines the label structure to be used for PDS coordinate labels. Description On/Off - Specifies whether the coordinate system short description is to be included with the coordinate label. (For example, On = 10' 10" East Site; Off = 10' 10" East.) Coordinate Readout - These options define the position of the coordinate value, coordinate axis short code, and coordinate system short code in the coordinate value readout. The active option (indicated by the selected option) is used for coordinate displays. Description On/Off - Specifies whether the coordinate system short code is to be included in the coordinate readout. (For example, On = 10' 10" E Site; Off = 10' 10" E.) Label -> Readout - Sets the Coordinate Readout option to match the defined Coordinate Label option. 1. Select the Coordinate Label/Readout Format option from the Revise 3D Plant Design Data form. 2. Select Coordinate Label.

Plant Design System (PDS) Project Administrator (PD_Project)

157

Project Data Manager

3.

4.

5.

6.

7.

Select one of the options to define the position of the coordinate value, coordinate axis, and coordinate system in the label format. Select Description On/Off. Select this field to specify whether the coordinate system short description is to be included with the coordinate label. Select Coordinate Readout. Select one of the options to define the position of the coordinate value, coordinate axis short code, and coordinate system short code in the coordinate value readout. Select Description On/Off. Select this field to specify whether the coordinate system short code is to be included in the coordinate readout. Select Label -> Readout. Choose this option to set the Coordinate Readout option to match the defined Coordinate Label option. Accept Coordinate Label/Readout Units. Choose the Confirm button to accept the specified Coordinate Label/Readout Units information. The Revise 3D Model Data form is displayed.

Co o rd in a te La b e l/Re a d o u t Un its The Coordinate Label/Readout Units option is used to define the system of units display for coordinate labels and coordinate readout displays. When this option is selected, the Coordinate Label/Readout Units form is displayed. The fields on the form vary depending on whether the project units are English or metric. Coordinate Label Format - Displays the system of units for coordinate labels. Coordinate Readout Format - Displays the system of units for coordinate readout displays. Label Units - Selects a Master Units Only or Master Units and Subunits format. Readout Units - Selects a Master Units Only, Master Units and Subunits, or Subunits Only format. Coordinate Label - Selects upper/lower case label to be displayed when placing metric drawing labels. Note: This option is only available for metric projects. Metric System of Units Label - Selects a Master Units Only, Master Units and Subunits, or Subunits Only format. Master Units Short Description - Up to 2-characters indicator for each Label, Readout, and Metric System of Units for master units. Subunits Short Description - Up to 2-characters indicator for each Label, Readout, and Metric System of Units to define subunits. Master Units and Subunits Separator - A single character for each Label, Readout, and Metric System of Units to define a separator between subunits and fractions.

158

Plant Design System (PDS) Project Administrator (PD_Project)

Project Data Manager Subunits and Fraction of Subunits Separator - A single character for each Label, Readout, and Metric System of Units to define a separator between subunits and fractions.

1. Select the Coordinate Label/Readout Units option from the Revise 3D Plant Design Data form. 2. Select Label Units and Readout Units. Select a master unit/subunit format from the displayed options. 3. Select Metric/English System of Units Label. Select a master unit/subunit format from the displayed options. 4. Specify Short Description. Type up to 2 characters to change the indicator for master units or subunits. 5. Specify Master Units and Subunits Separator. 6. Type a single character to define a separator between master units and subunits. 7. Specify Subunits and Fraction of Subunits Separator. Type a single character to define a separator between subunits and fractions. 8. Select Label  Readout. Choose this option to set the Coordinate Readout options to match the defined Coordinate Label options. 9. Accept Coordinate Label/Readout Format. Choose the Confirm button to accept the specified Coordinate Label/Readout Format information. The Revise 3D Model Data form is displayed.

Plant Design System (PDS) Project Administrator (PD_Project)

159

Project Data Manager

Co o rd in a te La b e l/Re a d o u t P re c is io n The Coordinate Label/Readout Precision option is used to define the accuracy (roundoff) to be used for dimension labels and readouts. When selected, this option displays the Coordinate Label/Readout Precision form. Fields on this form vary depending on whether the project units are English or metric. Label Precision - Specifies the roundoff factor to be used for linear dimension labels. The options vary depending on whether the toggle at the lower left of the form is set to Label Fraction or Label Decimal. Readout Precision - Specifies the roundoff factor to be used for linear dimension readouts. The options vary depending on whether the toggle at the lower right of the form is set to Readout Fraction or Readout Decimal. Metric System of Units Label Precision - Specifies the precision to be used for the secondary system of units. The options vary depending on the setting for secondary units. Label Mode toggle - Specifies either Fraction or Decimal for the label. Label Fraction/Alphnumeric Font - Toggles the label fraction format to Label Alphanumeric Fraction to display fractions in alphanumeric format (1/2) or to Label Fraction Font to display fractions using the fraction font (½). Note: The option is only displayed if the Label Mode or Readout Mode toggle is set to Label Fraction or Readout Fraction and the system of units is English. Readout Fraction/Decimal - Toggles the Readout format to Readout Decimal or Readout Fraction.

1. Select the Coordinate Label/Readout Precision option fro the Revise 3D Plant Design Data form.

160

Plant Design System (PDS) Project Administrator (PD_Project)

Project Data Manager 2. Specify Label Precision. Select the roundoff factor to be used for linear dimension labels. 3. Select Readout Precision. Select the roundoff factor to be used for linear dimension readouts. 4. Select Metric System of Units Label Precision. 5. Select the precision to be used for the secondary system of units. 6. Select Label and Readout Toggles. Toggle the Label mode and Readout mode to either Fraction or Decimal. 7. Select Label Fraction. Toggle the label fraction format to Label Alphanumeric Fraction or Label Fraction Font. 8. Accept Coordinate Label/Readout Precision. Choose the Confirm button to accept the specified Coordinate Label/Readout Precision information. The Revise 3D Model Data form is displayed.

Re vis e In te rfe re n c e Ch e c k Da ta The Revise Interference Check Data option is used to specify emulation data for use in analyzing interference envelopes. In interference detection, the system uses a set of cylinders to emulate the volume of a model graphic. These settings determine the number and size of the cylinders to be used. (These settings can be overridden during the operation of the Interference Checker.) Refer to the PDS Interference Checker/Manager Reference Guide for more information on the interference checking process. When the Revise Interference Check Data option is selected, the Interference Check Data form is displayed. Torus - Identifies the number of cylinders (per 90 degrees) to be used when representing a torus (elbow). Truncated Cone - Identifies the cylinder length to be used to represent a cone (reducer or valve body). Semi-ellipsoid - Identifies the cylinder length to be used to represent a semi-ellipsoid (cap or head). Weld Construction Tolerance Disabled/Weld Construction Tolerance Enabled - By default, weld tolerances are disabled, but may be activated with this toggle. Once weld construction tolerances are enabled, they appear in the graphic display of the clash envelopes. Slicing Tolerance - Displays the thickness of the slice that the software uses to subdivide the shapes in a model to do the internal computations. This should not be confused with Construction Tolerances (sometimes referred to as construction clearances), which are used to maintain distances between items in the model. Caution: Because the Slicing Tolerance is related to the size of model items, use Cautionif you edit this value to a larger number as some small items may be missed. Construction Tolerance Disabled/Enabled - By default, construction tolerances are disabled for an existing interference marker model. If inter-discipline construction tolerances are enabled, the system displays the Define Construction Tolerances button. Define Construction Tolerances (on page 164) - Displays the Construction Tolerance form. This option is only active when Construction Tolerance is enabled. Interference Marker Symbology - Levels Unapproved and Approved - The Levels, Unapproved, Approved fields set the design file level for unapproved and approved interference clash markers.

Plant Design System (PDS) Project Administrator (PD_Project)

161

Project Data Manager Interference Marker Symbology - Weight - Select the line weight used to display interference markers. Interference Marker Symbology - Color - Select the color used to display interference markers. Intersection Threshold - Defines the amount of overlap allowed before the intersection of two components is considered a clash. Valid Intersection Threshold values are within the range of 20 to 1000 Units of Resolution (UORs). The default value is 20 UORs. Select Action Discipline - Assigns responsibility for resolving inter-discipline interference clashes. Clash Plot Graphics - Default/Detail - Set the toggle to Default or Detail to specify the detail for clash plot graphics used by the Interference Checker plot.

1. Select Revise Interference Check Data. Select the Revise Interference Check Data option from the Seed Options form. The Interference Check Data form is displayed. 2. Specify Torus. Type the number of cylinders to represent a torus. 3. Specify Truncated Cone. Type the cylinder length to represent a cone. 4. Specify Semi-ellipsoid. Type the cylinder length to represent a semi-ellipsoid. Length and distance entries are in working units (MU:SU:PU format). For these fields the smaller the value the greater the precision and the slower the processing time for interference detection.

162

Plant Design System (PDS) Project Administrator (PD_Project)

Project Data Manager 5. Specify Slicing Tolerance. Type the allowable clearance for clash detection. 6. Select Construction Tolerances. Select the Construction Tolerances Enabled/Disabled field to toggle the setting between Enabled and Disabled. Displays the Define Construction Tolerance button. Select Define Construction Tolerances (on page 164). Select this field to Define Construction Tolerances. The Construction Tolerance form is displayed. 7. Select Interference Marker Symbology. Select the field for the symbology value to be revised (Levels, Unapproved, Approved). Place a data point along the slider to set the design file level.

8. Specify Weight. Place a data point along the slider to set the weight.

9. Select Color. Select the Color button. The Select Color form is displayed with the active color settings for the project. Select the color from the form; then choose the Confirm button. The Interference Check Data form is displayed. 10. Select Intersection Threshold. Type the UORs or Subunits in the appropriate text box. Valid values are within the range of 20 to 1000 UORs (1/64" to 1/2" or 0.25 mm to 12.5 mm). A warning is displayed. If the Intersection Threshold value is valid, the warning states that "Actual Clashes may not be reported based on the intersection value of XXXX UORs." If the Intersection Threshold Value entered is above 1000 UORs, the system changes the value to 1000 UORs and displays the previous warning. If the Intersection Threshold Value entered is less than 20, the system changes the value to 20 UORs. 11. Select Action Discipline (on page 166). Select the Select Action Discipline button. The Select Action Discipline form is displayed. Select a Discipline to assign as Action Discipline. The Responsible and Not Responsible fields fill in with current discipline assignments. Select a discipline to change the status between Responsible and Not Responsible. The selected discipline moves from one column to the other. 12. Accept Action Discipline. Choose the Confirm button to accept the specified Action Discipline information. The Interference Check Data form is displayed. 13. Select Clash Plot Graphics.

Plant Design System (PDS) Project Administrator (PD_Project)

163

Project Data Manager Set the toggle to Default to specify that the Interference Checker plot the default clash plot graphics. Set the toggle to Detail to specify that the Interference Checker plot more detailed clash plot graphics. 14. Accept Interference Check Data. Choose the Confirm button to accept the specified Interference Check Data. The Seed Options form is displayed.

De fin e Co n s tru c tio n To le ra n c e s The Define Construction Tolerances option is used to define the construction tolerance values between disciplines. The Interference Checker modifies each interference envelope by increasing its dimensions by one-half of the applicable construction tolerance for the two disciplines being compared. When the Define Construction Tolerances option is selected, the Construction Tolerance form is displayed. Horizontal Beam Angular Tolerance - An angle in degrees to define the allowed angular tolerance from horizontal for discriminating between beams and other linear structural members. The system recognizes a beam as a linear structural member that is within the specified tolerance. This parameter allows the Interference Checker to resolve the problem of piping legitimately resting on structural beams. If the centerline of the piping is parallel to the horizontal plane and the bottom of the piping is coincident with the top of the structural member, the construction tolerance is ignored and an interference clash is not reported (unless the insulation of the pipe clashes with the beam). Disciplines - The list of disciplines includes any user-specified, non-PDS disciplines, but is limited to a total of ten disciplines.

164

Plant Design System (PDS) Project Administrator (PD_Project)

Project Data Manager Construction Tolerances for HVAC - The construction tolerance in model subunits for each paired combination of disciplines, such as piping versus piping or piping versus structural. Type the construction tolerance in model subunits for each paired combination of disciplines, such as piping versus piping or piping versus structural. The list of disciplines includes any user-specified, non-PDS disciplines, but is limited to a total of ten disciplines.

1. Select Define Construction Tolerances. Select the Define Construction Tolerances option from the Revise Interference Check Data form. The Construction Tolerance form is displayed. 2. Specify Beam Tolerance. Type an angle in degrees to define the allowed angular tolerance from horizontal for discriminating between beams and other linear structural members. 3. Select Discipline. Select a discipline from the list. The defined construction tolerances between the selected discipline and the other disciplines are displayed. 4. Specify Construction Tolerances for Disciplines. Type the construction tolerance in model subunits for each paired combination of disciplines, such as piping versus piping or piping versus structural. The Interference Checker modifies each interference envelope by increasing some or all of its dimensions by one-half of the applicable construction tolerance for the two types of disciplines being compared.

Plant Design System (PDS) Project Administrator (PD_Project)

165

Project Data Manager

S e le c t Ac tio n Dis c ip lin e The Select Action Discipline option is used to to specify the assignment of responsibility to resolve inter-discipline interference clashes on the basis of a matrix of disciplines. For example, you can specify that piping versus structural clashes are to be assigned to the piping group, whereas equipment versus structural clashes are to be assigned to the structural group. All intra-discipline clashes are assigned to that discipline automatically for resolution. The plots of interference clashes that can be plotted with the Interference Checker or from the Interference Manager graphics environment include the assignment of responsibility for resolution of the clash on the plot. Each interference clash that is plotted is assigned automatically to one of the disciplines that has been specified in the Project Control Database. The following default matrix is provided:  The responsibility for interference clashes between piping and any other discipline is assigned to piping.  The responsibility for interference clashes between equipment and any other discipline (other than piping) is assigned to equipment.  The responsibility for interference clashes between electrical raceway and any other discipline (other than piping and equipment) is assigned to electrical raceway.  The responsibility for interference clashes between HVAC and any discipline (other than the previously mentioned disciplines) is assigned to HVAC.  The responsibility for interference clashes between architectural and any other discipline (other than the previously mentioned disciplines) is assigned to architectural. When the Select Action Discipline option is selected, the following form is displayed:

1. Select Option.

166

Plant Design System (PDS) Project Administrator (PD_Project)

Project Data Manager Select the Select Action Discipline option from the Revise Interference Check Data form. The Select Action Discipline form is displayed. 2. Select Discipline. Select one of the disciplines. The assigned responsibilities for that discipline are displayed. 3. Select Responsible and Not Responsible. Select a discipline to change the responsibility. For example, if the HVAC field is selected in the Responsible field, it switches to the Not Responsible field. 4. Accept Action Discipline. Choose the Confirm button to accept the specified Action Discipline. The Interference Check Data form is displayed.

P ro p a g a te In te rfe re n c e Ch e c k Da ta The Propagate Interference Check Data option applies settings from the project Interference Management model to all the design area Interference Management models within the active project or a list of selected Interference Management models. The following seed data is propagated:  The construction tolerance toggle setting and the construction tolerance matrix. For more information, see Revise Interference Check Data (on page 161) , and Define Construction Tolerances (on page 164).  Assignment of responsibility matrix. For more information, see Revise Interference Check Data (on page 161).  Envelope emulation data. For more information, see Revise Interference Check Data (on page 161).  Clash Plot Graphics Option. For more information, see Revise Interference Check Data (on page 161).  Intersection Threshold Data. For more information, see Revise Interference Check Data (on page 161). 1. Select Option. Select the Propagate Interference Check Data option from the Revise Seed File form.

Plant Design System (PDS) Project Administrator (PD_Project)

167

Project Data Manager The Propagate Data to Marker Files is displayed, providing access to the propagation options.

2. Select Option(s) for Propagation Select the option(s) for the parameters to be distributed. The active settings are highlighted. 3. Propagate Parameters. Set the toggle to All Marker Files to propagate the selected parameters to all the Interference Management models in the active project. —OR— Set the toggle to Selected Marker Files to select the marker files to be updated from a list of files. 4. Set submission toggle. Set the submission toggle to Submit Immediately to begin processing the request as soon as the form is exited. —OR— Set the toggle to Submission is Delayed to specify a day and time to process the request. 5. Accept time. Choose the Confirm button to accept the specified time. If All Marker Files is active, go to Step 8. If Selected Marker Files was selected, a list of disciplines is displayed. 6. Select design area marker file.

168

Plant Design System (PDS) Project Administrator (PD_Project)

Project Data Manager Select the discipline for the design area marker file(s) to be updated; then choose the Confirm button. The Select Design Area form is displayed. 7. Select Design Area. Select the design area(s) for the Interference Management models to be updated. 8. Accept to Submit for Processing or Select Discipline for additional Markers. Repeat steps 6 and 7 to select additional Interference Management models. 9. Accept Propagate Interference Check Data information. Choose the Confirm button to process the request. The request is submitted to the batch queue named PDproject_data.

Re vis e Eq u ip m e n t Da ta The Revise Equipement Data option is used to revise the data in the equipment seed file for the active project. When the Revise Equipment Data option is selected, the Revise Equipment Data form is displayed.

Graphic Symbology - Provides access to the graphic symbology options for equipment models. For more information, see Graphic Symbology (on page 170). Nozzle Default Placement Options - Used to revise the active units for nozzle diameter or the defaults for table suffix used for nozzle definitions. For more information, see Nozzle Default Placement Options (on page 174). Reference Database File Specifications - Used to specify whether to use the approved or unapproved Reference Database files for equipment modeling in the project. For more

Plant Design System (PDS) Project Administrator (PD_Project)

169

Project Data Manager information, see Reference Database File Specifications - Specify Approved or Unapproved (on page 176). Interference Envelope Emulation Data - Used to specify emulation data for use in analyzing interference envelopes for equipment models. For more information, see Interference Envelope Emulation Data (on page 177).

Gra p h ic S ym b o lo g y The Graphic Symbology option provides access to the graphic symbology options for equipment models. When the Graphic Symbology option is selected, the Graphic Symbology form is displayed.

The Equipment Graphic Symbology option is used to define the display level, color code, line weight, and line style for the various types of equipment graphics. The description of the graphic categories can also be changed for Primitives/Parametrics, Nozzles, Semi-intelligent, and Dumb Graphics. The description of graphic categories cannot be changed for Envelopes, Steel, and Miscellaneous. Select the type of equipment data to revise from the Graphic Symbology form.  Primitives/Parametrics  Nozzles  Envelopes  Steel  Semi-Intelligent  Dumb Graphics  Miscellaneous

170

Plant Design System (PDS) Project Administrator (PD_Project)

Project Data Manager New fields are displayed on the Graphic Symbology form. The fields vary depending on the selected category of equipment graphics. The following form represents the form for Primitives/Parametrics:

1. Select symbology value. Select the field for the symbology value to be revised. Use the scroll bar to page through the available categories. 2. Specify Category. For Primitives/Parametrics, Nozzles, Semi-intelligent, and Dumb Graphics type to 40 characters to change the category description. For Envelopes, Steel, and Miscellaneous this field is display only. This value is displayed when any related operations are performed in the PDS 3D products. 3. Select Level. Place a data point along the slider to set the MicroStation display level.

4. Select Color. The Select Color form is displayed with the active color settings for the project. Select the color from the form, and choose the Confirm button. 5. Select Weight.

Plant Design System (PDS) Project Administrator (PD_Project)

171

Project Data Manager Place a data point along the slider to set the weight.

6. Select Symbology. Select the desired symbology option.

7. Accept Graphic Symbology. Choose the Confirm button to accept the specified Graphic Symbology. The Project Data Manager - Equipment form is displayed.

P rim itive s /P a ra m e tric s , No zzle s , S e m i-In te llig e n t, Du m b Gra p h ic s Use this form to define the display level, color code, line weight, and line style (symbology) for these types of equipment graphics. You can also change the graphics category description. The form below represents the Primitives/Parametrics equipment graphics option.

Category - Change the category description. You can use up to 40 characters for the new description. Level - Set the MicroStation display level on which graphics are to be placed. All graphics are placed on the defined graphic level.

172

Plant Design System (PDS) Project Administrator (PD_Project)

Project Data Manager Color - Open the Select Color form, which displays the default color. Select a color or color number (as defined in the current PDS color form). Weight -Set the line weight for the graphics.

Symbology - Set or modify the symbol line style. When you select the line style name in the Symbology column, the system displays the available line styles.

En ve lo p e s , S te e l, a n d Mis c e lla n e o u s Use this form to define the display level, color code, line weight, and line style (symbology) for these types of equipment graphics.The form below represents the Envelopes equipment graphics option.

Category - Read-only field. Level - Set the MicroStation display level on which graphics are to be placed. All graphics are placed on the defined graphic level.

Plant Design System (PDS) Project Administrator (PD_Project)

173

Project Data Manager Color - Open the Select Color form, which displays the default color. Select a color or color number (as defined in the current PDS color form). Weight -Set the line weight for the graphics.

Symbology - Set or modify the symbol line style. When you select the line style name in the Symbology column, the system displays the available line styles.

No zzle De fa u lt P la c e m e n t Op tio n s This option is used to revise the active units for nozzle diameter or the defaults for table suffix used for nozzle definitions. When this option is selected, the Nozzle Default Placement Options form is displayed. System of Units - Defines the active system of units for nominal diameter for nozzles. Select this field to toggle the setting to English or Metric. Small is = - Specifies the Nominal Piping Diameter ranges that classify nozzles as large. Table Name - Identifies the name of the Nominal Piping Diameter table used to verify valid nominal diameter values for nozzles.

174

Plant Design System (PDS) Project Administrator (PD_Project)

Project Data Manager Define Table Suffix By End Type - Bolted, Female or Male - Identifies the table suffix value from CL576 (5 = US Practices).

1. Select Option. Select the Nozzle Default Placement Options form the Revise Equipment Data form. The Nozzle Default Placement Options form is displayed. 2. Select Nominal Piping Diameter and System of Units. Define the active system of units for nominal diameter for nozzles. Select this field to toggle the setting to English or Metric. 3. Select Small is = xxIN. Specify the NPD ranges that classify nozzles as small, medium, or large. To change a diameter value, select the appropriate field and type the new value. 4. Specify Nominal Piping Diameter Table Name. Identifies the name of the NPD table used to verify valid nominal diameter values for nozzles. 5. Select Default Table Suffix by End Type. Select the table suffix field to be modified and type a new value from CL576 (5 = US Practices). 6. Accept Nozzle Default Placement Options. Choose the Confirm button to accept the Nozzle Default Placement Options. The Revise Equipment Data form is displayed.

Plant Design System (PDS) Project Administrator (PD_Project)

175

Project Data Manager

Re fe re n c e Da ta b a s e File S p e c ific a tio n s - S p e c ify Ap p ro ve d o r Un a p p ro ve d The Reference Database File Specifications option is used to specify whether to use the approved or unapproved Reference Database files for equipment modeling in the project. When this option is selected, the Reference Database File Specifications form is displayed. Database File - Identifies the Piping Reference Database for the project. Approval Status - Specifies the RDB to be approved or unapproved for the selected item. Network Address - Displays the Network Address for the selected item. Directory - Displays the Directory location for the selected item. Specification - Displays the Specification name for the selected item.

1. Select Option. 2. Select the Reference Database File Specifications option from the Revise Equipment Data form. The Reference Database File Specifications form is displayed. 3. Select Database file. Use the Scroll Area to select the field to review one of the library or table names. The name and location of the file for the selected field is identified.  Graphic Commodity Library - ~\pdeqp\dat\zi_eqpms.lib  Tutorial Definition Library - ~\pdeqp\dat\zi_tutlib.lib  Equipment Physical Data Library  Piping Physical Data Library - \rdusrdb\us-pcdim.1  Piping Design Standard Note Library - \rdusrdb\stp_note.1

176

Plant Design System (PDS) Project Administrator (PD_Project)

Project Data Manager  Piping Specification Table Library - ~\rdusrdb\pjs_tbl.1  Cell Library - ~\pdeqp\dat\equip.cel  Forms Directory Location - ~\pdeqp 4. Specify Approval Status. Specify to use the approved RDB or unapproved RDB for the selected item. 5. Accept Reference Database File Specifications. Choose the Confirm button to accept the Reference Database File Specifications. The Revise Equipment Data form is displayed.

In te rfe re n c e En ve lo p e Em u la tio n Da ta The Interference Envelope Emulation Data option is used to specify emulation data used to analyze interference envelopes for equipment models. In interference checking, the system uses a set of cylinders to emulate the volume of a model graphic. These settings determine the number and size of the cylinders to be used. (These settings can be overridden during the operation of the Interference Checker.) Distance Between Two Planes For Clash Checking - Identifies the allowable clearance for clash detection. Items within the specified distance are considered to clash. Number of Emulated Cylinders Per 90 Degree for Torus - Identifies the number of cylinders to be used in representing a torus (elbow). Length of Emulated Cylinders for Cone - Identifies the cylinder length to be used in representing a cone. Length of Emulated Cylinders for Semi Ellipsoid - Identifies the cylinder length to be used in representing a semi-ellipsoid (cap or head).

Plant Design System (PDS) Project Administrator (PD_Project)

177

Project Data Manager 1. Select Option. Select the Interference Envelope Emulation Data option from the Revise Equipment Data form. The Interference Envelope Emulation Data form is displayed. Select the appropriate field, and type any changes to the envelope emulation data. Length and distance values are in working units (MU:SU:PU format). For these fields, the smaller the value the greater the precision and the slower the processing time for Interference Checking. 2. Specify Distance Between Two Planes for Clash Checking. Identify the allowable clearance for clash detection. Items within the specified distance are considered to clash. 3. Specify Number of Emulated Cylinders Per 90 Degree for Torus. Identify the number of cylinders to be used when representing a torus (elbow). 4. Specify Length of Emulated Cylinders for Cone. Identify the cylinder length to be used when representing a cone. 5. Specify Length of Emulated Cylinders for Semi-Ellipsoid. Identify the cylinder length to be used when representing a semi-ellipsoid (cap or head). 6. Accept Interference Envelope Emulation Data. Choose the Confirm button to accept the specified Interference Envelope Emulation Data. The Revise Equipment Data form is displayed.

Re vis e P ip in g Mo d e l Da ta The Revise Piping Model Data option is used to revise the piping model data in the seed files for the active project. Component Placement - Used to specify the graphic commodity library tables, the symbols to be used for special graphics, and the tolerance values for the automatic component placement and for determining the end of a pipe or the proximity of a component. For more information, see Component Placement (on page 179). Piping Data Control - Enables/disables access to the weight table, processes schedule/thickness overrides, and specifies working units and classifications for nominal piping diameter. For more information, see Piping Data Control (on page 182). Physical Units - Used to to set the active physical units for Insulation Density, Surface Area, Dry/Wet Weights, and Maximum Temperature in the Piping Job Spec. For more information, see Physical Units (on page 186). Nozzle Transfer - Used to specify the nozzle attributes to be transferred to the associated piping segment when connecting to a nozzle. For more information, see Nozzle Transfer (on page 189). Material Takeoff - Used to specify the source of commodity information, units for bolt length and diameter, and item names used to reference a commodity item in the Graphic Commodity Library. For more information, see Material Takeoff (on page 190). Design Review Label - Used to select which model component types will not have SmartPlant Review labels generated by the Label Builder. For more information, see Design Review Label (on page 192). Default Segment Data - Used to define certain segment parameters that are stored in the type 63 elements. For more information, see Default Segment Data (on page 193). Reference Database File Specifications - Used to review file names for Reference Database files, graphic commodity data, dimension tables, and spec tables. For more information, see Reference Database File Specifications - Review File Names (on page 195).

178

Plant Design System (PDS) Project Administrator (PD_Project)

Project Data Manager Design Checks Options - Used to specify hard and soft design rule consistency check parameters for components and line route segments and to specify the tolerance values to be used when processing design checks. For more information, see Design Checks Options (on page 197). Design Checks End Prep Table - Used to select the classification of end preparations to review or modify. For more information, see Design Checks End Prep Table (on page 199). Symbology Diagnostic Markers - Used to specify the graphic symbology to be used for view-independent symbols (markers), the symbols to be used for special graphics, and the line weight for marker graphics. For more information, see Symbology Diagnostic Markers (on page 201). Symbology - Model - Used to specify the model symbology for component placement and to indicate whether color codes are based on model category, fluid code, or construction status. For more information, see Symbology - Model (on page 203). Insulation - Used to define symbology for insulation graphics. For more information, see Symbology - Insulation (on page 205). Symbology Level and Color - Used to set the symbology for the model, fluid code, or construction status as specified by the Symbology Model setting. For more information, see Symbology Level and Color (on page 207).

Co m p o n e n t P la c e m e n t The Component Placement option is used to specify the names for the graphic commodity library tables, the symbols to be used for special graphics, and the tolerance values for automatic component placement and determining the end of a pipe or the proximity of a component. Refer to the Reference Database Manager Reference Guide for a detailed description of these tables and modules.

Plant Design System (PDS) Project Administrator (PD_Project)

179

Project Data Manager Bend Deflection Table - Defines which full size and reducing components are to be placed within a specified angle range. The angle is defined as the smallest angle the continuation of one pipe run makes with the other run. Commodity Name Table - Correlates the component types coded in the software for automatic component placement with the applicable item names (AABBCC codes). Pipe Length Threshold Table - Defines the minimum and preferred allowable pipe lengths that can be placed (either manually or by automatic component placement). The maximum length of the default Pipe Length Threshold Table name is 13 characters. Segment Pipe Run Length Threshold Table - Defines the minimum allowable segment run length that can be placed from the design session during centerline routing. The values defined in this table do not apply to the segment run created by the software when placing components end to end. Weld Type Table - Defines the weld type code for a given pair of fabrication category values. The fabrication category values are determined from the connect point data at each of the mating welded ends. Flange Data Module - Defines the name of the Eden module that generates the table name for use in determining flange outside diameter and flange thickness. Reinforcing Weld Data Module - Defines the name of the Eden module that determines the values for reinforcing welds during branch reinforcement calculations. (Refer to the PDS Piping Component Data Reference Guide.) Reinforcing Pad Data Module - Defines the name of the Eden module that determines the values for reinforcing pads during branch reinforcement calculations. (Refer to the PDS Piping Component Data Reference Guide.) Pipe Commodity Name - Indicate the commodity item names to be used for segment type in the active segment parameters. Tube Commodity Name - Indicates the commodity item names to be used for segment type in the active segment parameters. Angular Tolerance (Automated Component) - Indicates the acceptable deviation in degrees for flow centerline alignment. If an attempt is made to place a component at an angle outside the tolerance, the system displays a warning message. Vicinity Tolerance - Indicates the acceptable clearance in working units for use in component placement. If an attempt is made to place a component within the specified tolerance, the system displays a warning message.

180

Plant Design System (PDS) Project Administrator (PD_Project)

Project Data Manager Commodity Synonyms - When commodity synonyms are enabled, a user-defined Commodity Synonym Library can be used to define the relationship between commodity names used in the P&ID task and commodity names in PDS 3D. (Refer to the Reference Data Manager (PD_Data) Reference Guide for more information on this library.)

1. Select Option. Select the Component Placement option from the Revise Piping Model Data form. The Component Placement form is displayed. 2. Specify Bend Deflection Table. Select the Bend Deflection Table field and type the associated table name. 3. Specify Commodity Item Name Table. Select the Commodity Item Name Table field and type the associated table name. 4. Specify Pipe Length Threshold Table. Select the Pipe Length Threshold Table field and type the associated table name. 5. Specify Segment Pipe Run Length Threshold Table. Select the Segment Pipe Run Length Threshold Table field and type the associated table name. 6. Specify Weld Type Table. Select the Weld Type Table field and type the associated table name. 7. Specify Flange Data Module. Select the Flange Data Module field and type the associated Eden module name. 8. Specify Reinforcing Weld Data Module. Select the Reinforcing Weld Data Module field and type the associated Eden module name.

Plant Design System (PDS) Project Administrator (PD_Project)

181

Project Data Manager 9. Specify Reinforcing Pad Data Module. Select the Reinforcing Pad Data Module field and type the associated Eden module name. 10. Specify Pipe Commodity Name and Tube Commodity Name. Select the Pipe Commodity Name field and type the associated commodity name. 11. Specify Angular Tolerance (Automated Component). Select the Angular Tolerance field and type the associated tolerance information. 12. Specify Vicinity Tolerance. Select the Vicinity Tolerance field and type the acceptable clearance information. 13. Select Commodity Synonyms. Set the toggle to Disable Commodity Synonyms or Enable Commodity Synonyms. 14. Accept Component Placement information. Choose the Confirm button to accept the Component Placement information. The Revise Model Data form is displayed.

P ip in g Da ta Co n tro l The Piping Data Control option is used to enable/disable access to the weight table, select the option for processing schedule/thickness override, and specify working units and classifications for nominal piping diameter. Fluid Code Control - Specifies whether the system will use the setting for the fluid code in the Piping Materials Class data of the Piping Job specification to limit the acceptable fluid code(s) while modeling. The default is to not limit the fluid code values. Weight Table - Specifies whether a weight table is to be used to find the dry weight of a component. Using a weight table is required for those cases where, for a specific geometric industry standard, material causes the dry weight data to differ, but not the dimensional data. Geometric Industry Standard - Specifies the geometric industry standard to be used for the company practice Physical Data Library. When this toggle is set to Default, the geometric industry standard range is defined to be from 31,000 through 31,999. This setting is required if you plan to use any of the following industry practices: European B, International A, or International B. When this toggle is set to Expanded, the geometric industry standard range for company practice is defined to be from 28,000 through 31,999. This is the active option for any piping models created with the 4.0 version of PDS. P&ID Database - Specifies whether the Master or the Task PID database is used, if both are available for the project. Branch Component Assoc for Isometric Drawings - Specifies whether the branch component will be associated with the header line or branch line during isometric extraction. Note: This property only applies to olet geometry branch components. Tees, crosses and wyes follow the ISOGEN convention of being owned by the line at CP1 of the fitting. Copy - Specifies whether to append ** as a prefix to name attributes (for example, line number label and component number) to signify that the segment or component was copied and that the name attribute may require updating. Piping Segment Data - Specifies whether the Brief list or the Complete list of piping segment data should be displayed as the default in the Piping Designer graphics environment. Refer to Default Segment Data (on page 193) , for more information on segment data. T-P Data for Service Limits Verification - Specifies whether temperature and pressure values are to meet the minimum normal operating and normal design specifications.

182

Plant Design System (PDS) Project Administrator (PD_Project)

Project Data Manager System of Units for Nominal Piping Diameter - Sets a default system of units for nominal piping diameter independently of the system of units for the model. The setting for NPD units can be toggled between English units and metric units. This setting can be overridden while working in the model. System of Units for Corrosion Allowance - Used to set the system of units for corrosion allowance to English or metric. Rule for Insulation Purpose when set to None - Specifies whether the system clears the insulation density on the segment when the segment insulation purpose is set to 1 (blank) or 2 (none). If the insulation density is undefined, setting the insulation purpose to blank or none will NOT change the insulation density when this toggle is set to Do Not Clear Density. The insulation density will be set to undefined when this toggle is set to Clear Density and the insulation purpose is set to blank or none. Note: In the graphical environment, the following commands will respect this toggle when the insulation purpose is set to blank or none: Sketch, Load Active Segment, and Revise Attributes. Schedule Thickness Override Option - Specifies how the piping segment override schedule/thickness is to be treated during wall thickness calculations and branch reinforcement calculations. Three options are available: Larger of Override and Spec, Override Value Only, and Override but Report Error. If the Larger of Override and Spec option is selected, the override schedule/thickness (if it has been defined) is used if it exceeds the value in the Piping Job Specification. If an override schedule/thickness has not been defined, the value from the Piping Job Specification is used. If the Override Value Only option is selected, the override schedule/thickness (if it has been defined) is used instead of the value in the Piping Job Specification. If the Override but Report Error option is selected, the override schedule/thickness (if it has been defined) is used if it exceeds the value in the Piping Job Specification. Otherwise, an error is reported. The override schedule/thickness is never used for any situation where the value from the Piping Job Specification is 'not required'. If either the piping segment schedule/thickness override or the pipe schedule/thickness is defined as a schedule value, the schedule is converted to a wall thickness value for comparison. This conversion uses NPD, termination type, table suffix, and weight code. Field Name for Nominal Piping Diameter - Specifies the field name to be used with NPD units (for example, IN or " for English or mm for metric).

Plant Design System (PDS) Project Administrator (PD_Project)

183

Project Data Manager Maximum Number of Blocks for Piping Design File - Sets the maximum size (in blocks) for a piping model. If a design file reaches this maximum value, the system displays a dialog box warning the maximum size has been reached when exiting the Piping Designer graphics environment.

1. Select Option. Select the Piping Data Control option from the Revise Piping Model Data form. The Piping Data Control form is displayed. 2. Select Fluid Code Control. Set the toggle to Yes or No, indicating whether to limit acceptable fluid code values while modeling. 3. Select Weight Table. Set the toggle to Yes or No, indicating whether to use a weight table to find the dry weight of a component. 4. Select Geometric Industry Standard. Set the toggle to Default or Expanded, indicating the range to use. 5. Select P&ID Database. Select the task or master P&ID database. 6. Select Branch Component Assoc for Isometric Drawings. Set the toggle to Header or Branch, indicating whether the branch component is to be associated with the header line. 7. Select Copy.

184

Plant Design System (PDS) Project Administrator (PD_Project)

Project Data Manager

8.

9.

10. 11. 12. 13.

14. 15. 16.

Set the toggle to Append Prefix or No Prefix, indicating whether to append ** as a prefix to name attributes. Select Piping Segment Data. Set the toggle to Complete or Brief, indicating the complete or brief list of piping segment data should be displayed. Select T-P Data for Service Limits Verification. Set the toggle to Minimum or No Minimum to indicate if temperature and pressure valves are to meet minimum normal operating and design specifications. Select System of Units for Nominal Piping Diameter. Set the toggle to English or Metric. Select System of Units for Corrosion Allowance. Set the toggle to English or Metric. Select Rule for Insulation Purpose when set to None. Set the toggle to Clear Density or Do Not Clear Density. Select Schedule Thickness Override Option. Select Larger of Spec and Override, Always Use Override, or Override, but Report Error. Select Field Name for Nominal Piping Diameter. Type a 2-character alphanumeric field name. Specify Maximum Number of Blocks for Piping Design File. Type up to 5-character numeric maximum size. Accept Piping Data Control information. Choose the Confirm button to accept the Piping Data Control information. The Revise Piping Model Data form is displayed.

Plant Design System (PDS) Project Administrator (PD_Project)

185

Project Data Manager

P h ys ic a l Un its The Physical Units option is used to set the active physical units for Insulation Density, Surface Area, Dry/Wet Weights, and Maximum Temperature in the Piping Job Spec. When Physical Units is selected, the Physical Units Options form is displayed.

1. Select the Physical Units option from the Revise Piping Model Data form. The Physical Units Options form is displayed. 2. Select Insulation Density. The available settings for Insulation Density are displayed.

186

Plant Design System (PDS) Project Administrator (PD_Project)

Project Data Manager 3. Select a setting from the list.

The Physical Units Options form is displayed. 4. Select Surface Area. The available settings for Surface Area are displayed. 5. Select a Surface Area setting. Select a setting from the Surface Area list. This setting provides surface area values for painting requirements.

The Physical Units Options form is displayed. 6. Select Weight. The available settings for weight are displayed. 7. Select physical units for weight measurement.

Plant Design System (PDS) Project Administrator (PD_Project)

187

Project Data Manager Select the physical units to be used when performing dry and wet weight calculations. The active setting is used to supply data to the stress analysis interface.

The Physical Units Options form is displayed. 8. Select Maximum Temperature (Spec). The available settings for maximum temperature are displayed. 9. Select units. Select the units to be used in performing design checks for components.

The Physical Units Options form is displayed.

188

Plant Design System (PDS) Project Administrator (PD_Project)

Project Data Manager

No zzle Tra n s fe r The Nozzle Transfer option is used to specify the nozzle attributes to be transferred to the associated piping segment when connecting to a nozzle. These settings determine the basis for data comparisons between a nozzle and associated piping in Piping Design. Only the data designated to be transferred will be used for data comparisons.

1. Select Option. Select the Nozzle Transfer option from the Revise Piping Model Data form. The Nozzle Data Transfer form is displayed. 2. Select Attributes. Select the attributes to be transferred. The selected attributes are highlighted. 3. Accept Nozzle Data Transfer information. Choose the Confirm button to transfer the highlighted attributes. The Revise Model Data form is displayed. Notes: To remove the highlight from a selected attribute (and to not transfer the attribute), select the attribute.  Nominal piping diameter and piping materials class are transferred automatically.

Plant Design System (PDS) Project Administrator (PD_Project)

189

Project Data Manager

Ma te ria l Ta ke o ff The Material Takeoff option is used to specify the source of commodity information, units for bolt length and diameter, and specify item names used to reference a commodity item in the Graphic Commodity Library. Refer to the Reference Data Manager Reference Guide for information about the stud table, bolt length calculations, and the bolt commodity code table. Bolt Length Roundoff - Specifies the manner by which bolt lengths are to be determined. Three options are available: Preferred Bolt Length Table, Bolt Roundoff Factor, and No Roundoff. If the Preferred Bolt Length Table option is selected, the preferred bolt length table is used. If the Bolt Roundoff Factor option is chosen, the specified roundoff factor is multiplied by the exact bolt length to calculate the bolt lengths. If No Roundoff is selected, the exact length is used. Length Calculation - Specifies the method to be used to calculate bolt length. The bolt length is read from the stud table. The table value can be determined using the rating and table suffix (Almost Precise) or using termination type, rating, and table suffix (Precise). Bolt Commodity Code - Specifies the method to be used to determine the commodity code for bolts (Piping Job Specification or Bolt Commodity Code Table) for use in material takeoff. Field Fit Length - Toggle the setting between Off or On. If this field is On, the system displays a field to input the Field Fit Length Table name. Bolt Diameter Units - Specifies the system of units for bolt diameter. Bolt Length Units - Specifies the system of units for bolt length. Gasket Search - Specifies the Gasket Search to be Default or Alternate. Header Weld for RPAD - Specifies the setting of Report or Do Not Report. When set to Report, the header welds for reinforcing pads are automatically generated. Branch Weld for RPAD - Specifies the setting of Report or Do Not Report. When set to Report, the branch welds for reinforcing pads are automatically generated. Commodity Code - Specify the setting of Size Independent or Size Dependent. If the field is set to Size Dependent, two additional options are displayed: Source of Implied Data and Source of Material Description. Source of Implied Data - Specifies the source of the commodity code for reporting implied data from the Piping Commodity Implied Material Data Table. The default option (System Commodity Code) specifies the system is to use the commodity code defined in the Piping Commodity Specification Data Table (Table 202 attribute 18). The Size-Dependent Commodity Code option specifies the system is to use the commodity code defined in the Piping Commodity Size-Dependent Material Data Table (Table 211 attribute 7). The length of the commodity_code attribute must be an even number when using this table. Source of Material Description - Specifies the source of the commodity code for reporting a component's material description. The default option (System Commodity Code) specifies the system is to use the commodity code defined in the Piping Commodity Specification Data Table (Table 202 attribute 18). The Size-Dependent Commodity Code option specifies the system is to use the commodity code defined in the Piping Commodity Size-Dependent Material Data Table (Table 211 attribute 7). The length of the commodity_code attribute must be an even number when using this table. Gasket Commodity Name, Bolt Commodity Name, and Nut Commodity Name - Indicates the default commodity item names to be used to report implied materials (gaskets, bolts, and nuts) unless a specific override is set for the component being reported. Bolt Length Table - Specifies the name of the table that defines the low and high range for calculated bolt lengths and the corresponding preferred or purchased lengths of the bolt. This field is only used if the Bolt Length Roundoff option is set to Preferred Bolt Length Table.

190

Plant Design System (PDS) Project Administrator (PD_Project)

Project Data Manager Bolt Length Roundoff Factor - Specifies the value for the bolt roundoff factor in subunits. This value is only used if the Bolt Length Roundoff option is set to Bolt Roundoff Factor. Field Fit Length Table - Specifies the name of the table which defines the field fit length. This value is only used if the Field Fit Length option is set to On. 1. Select Option. Select the Material Takeoff option from the Revise Piping Model Data form. The Material Takeoff Options form is displayed. 2. Select Bolt Length Roundoff. Select Preferred Bolt Length Table, Bolt Roundoff Factor, or No Roundoff. If Preferred Bolt Length Table is selected, the Bolt Length Table field is displayed. If Bolt Roundoff Factor is selected, the Bolt Length Roundoff Factor field is displayed. If No Roundoff is selected, no roundoff field is displayed. 3. Select Length Calculation. Specify the method of Precise or Almost Precise to be used to calculate bolt length. 4. Select Bolt Commodity Code. Specify the method of Piping Job Spec or Bolt Commodity Code Table to be used to determine the Comomdity code for bolts. 5. Select Field Fit Length. Specify On or Off for the Field Fit Length. If On is selected, the Field Fit Length Table field is displayed. 6. Select Bolt Diameter Units. Specify Metric or English for the system of units for bolt diameter. 7. Select Bolt Length Units. Specify Metric or English for the system of units for bolt units. 8. Select Gasket Search. Specify Alternate or Default for the gasket search. 9. Select Header Weld for RPAD. Specify Do Not Report or Report. 10. Select Branch Weld for RPAD. Specify Do Not Report or Report. 11. Specify Gasket Commodity Name. Type the default gasket commodity name. 12. Specify Bolt Commodity Name. Type the default bolt commodity name. 13. Specify Bolt Length Roundoff Factor. This field displays only if Bolt Roundoff Factor is selected for the Bolt Length Roundoff option. Type the name of the Bolt Length Roundoff Factor table. 14. Specify Field Fit Length Table. This field displays only if On is selected for the Field Fit Length option. Type the name of the Field Fit Length Table. 15. Select Commodity Code. Specify Size Dependent or Size Independent. If Size Dependent is selected, the Source of Implied Data and Source of Material Description options display.

Plant Design System (PDS) Project Administrator (PD_Project)

191

Project Data Manager 16. Select Source of Implied Data. Specify Size Dependent Commodity Code or System Commodity Code. 17. Select Size Dependent Commodity Code. Specify Size Dependent Commodity Code or System Commodity Code. 18. Accept Material Takeoff Options. Choose the Confirm button to accept Material Takeoff Options. The Revise Model Data form is displayed.

De s ig n Re vie w La b e l The Design Review Label option is used to select which model component types will not have SmartPlant Review labels generated by the Label Builder. By default, all labels are generated.

1. Select Option. Select the Design Review Label option from the Revise Piping Model Data form. 2. Select Label(s). Select the label(s) to be processed for SmartPlant Review. The labels to be processed are highlighted. Note: A highlighted label can be cancelled by selecting it to remove the highlight. Only highlighted labels are processed. 3. Accept Label(s). Choose the Confirm button to save the settings and to dismiss the form. The Revise Model Data form is displayed.

192

Plant Design System (PDS) Project Administrator (PD_Project)

Project Data Manager

De fa u lt S e g m e n t Da ta The Default Segment Data option is used to define certain segment parameters that are stored in the type 63 elements.

Attribute Name - The name of the segment parameter. Default Value - Specifies the default value for the segment parameter. Propagation Status - Specifies whether the parameter will be included when a segment is added using the Connect to Design command. This option applies only to user defined attributes. Active / Blank Value - Specifies whether a non-propagated parameter will be set to match the active segment data or set to a blank value. This option applies only to user defined parameters with a Propagation Status of No. 1. Select Option. Select the Default Segment Data option, from the Revise Model Data form. The Default Segment Parameters form is displayed. The RDB data is attached, and the following messages are displayed: Initializing Piping Design Database Initializing Piping Job Specification Database Note: The physical units for maximum temperature are automatically loaded as the default temperature units for segment attributes. 2. Select Option for Revision. Select a parameter, and type the new value.

Plant Design System (PDS) Project Administrator (PD_Project)

193

Project Data Manager Note: The scroll bar can be used to page through the segment parameters. If a code-listed value is selected, the standard note values for the selected parameter are displayed on a separate form. 3. For user defined parameters, select the appropriate Propagation Status and Active / Blank Value options. 4. Select Standard Note. Select a standard note value. Use the scroll bar to page through the available standard notes.

5. Choose the Confirm button to accept the selected value and to dismiss the standard note form. Note: If the cursor is moved to a code-listed value by pressing the Enter key (rather than placing a data point), the system will not activate the standard note form. The code list text can be typed (such as MMA for fluid code) or the index number (such as 444). 6. Accept Default Segment Parameters. Choose the Confirm button to accept the defined segment parameters. The Revise Model Data form is displayed.

194

Plant Design System (PDS) Project Administrator (PD_Project)

Project Data Manager

Re fe re n c e Da ta b a s e File S p e c ific a tio n s - Re vie w File Na m e s The Reference Database File Specifications option is used to review the file names for Reference Database Files, graphic commodity data, dimension tables, and spec tables. Whether to use approved or unapproved RDB data can be determined for each item. The file specifications are defined through the Reference Data Manager. Refer to the Reference Database Manager Reference Guide for a detailed description of these files. The following RDB files are available: Material/Specification Reference Database - Identifies the Piping Reference Database for the project. Piping Job Specification Table Library - Identifies the location of the Spec Table library (pjstb.l). Short Material Description Library - Identifies the library containing the short bill-of-material description for all piping commodity items and the BOM description addenda for taps (us_shbom.l). Long Material Description Library - Identifies the library containing the long BOM description for all piping commodity items (us_lgbom.l). The long BOM description is only used for requisitions. Specialty Material Description Library - Identifies the library that contains the BOM description for engineered items, in-line instruments, and pipe supports (us_spbom.l). This library is customer-specific and is not delivered with the software. Standard Note Library - Identifies the location of the standard note library (std_note.l). Label Description Library - Identifies the location for the label description library (labels.l). Piping Assembly Library -- Identifies the location for the Piping Assembly library. This library contains the symbol definitions for assemblies (assembly.l). Graphic Commodity Library - Identifies the library containing the Eden modules used to place components in the model (pip_gcom.l). Physical Data Library - Identify the library files containing the physical data tables for a range of geometric industry standards (us_pcdim.l). Commodity Synonym Library - Identifies the user-defined library containing the map for translating the commodity names used in Piping to those used in the P&ID task. Approval Status - Sets the directory path to approved or unapproved. Network Address - Displays the network address for the selected file specification. Directory - Displays the directory path for the selected file specification.

Plant Design System (PDS) Project Administrator (PD_Project)

195

Project Data Manager Specification - Displays the specification for the selected reference database file.

1. Select Option. Select the Reference Database File Specifications option from the Revise Piping Model Data form. The Reference Database File Specifications form is displayed. 2. Select Option for Revision. Select the RDB file from the list of files. The file for the selected field is identified in the fields at the bottom of the form. 3. Accept RDB files. Choose the Confirm button to accept any changes to the RDB files and to dismiss the form. The Revise Piping Model Data form is displayed.

196

Plant Design System (PDS) Project Administrator (PD_Project)

Project Data Manager

De s ig n Ch e c ks Op tio n s Design checks are used to ensure that connected pressurized piping and instrumentation in the model is compatible in terms of a set of design rules. This option is used to specify hard and soft design rule consistency check parameters for components and line route segments and to specify the tolerance values to be used to process design checks. These tolerances are used to define the acceptable tolerances between connected components. Any discrepancy greater than the defined tolerance is reported as an inconsistency. Interactive Check - Selects the applicable parameter toggle setting of Check (*) or No Check. This determines which parameters are compared during interactive consistency checks. Notes: Schedule/thickness interactive design checks do not work, because at the time that the check is done during placement, the wall thickness has not been calculated. The Batch Design Checker does check the schedule/thickness and reports errors.  The interactive design check for outside diameter does not work. Design Checker - Selects the applicable parameter toggle the setting of Check (*) or No Check. This allows the options for post-placement design checks to be specified independently of the interactive design checks in the model. Until a selection is made, the state of each post-placement Design Checks option defaults to the same state as the corresponding interactive Design Checks option. Note: The design check for outside diameter does not work. Hard/Soft - Selects the applicable parameter toggle of Hard or Soft. A hard inconsistency constitutes an error, and a soft inconsistency constitutes a warning. Flow Centerline Alignment Tolerances - An angle value in degrees to indicate the acceptable tolerance for flow centerline alignment between connected components. Insulation Thickness Tolerances - A value in subunits to indicate the acceptable tolerance for insulation thickness.

Plant Design System (PDS) Project Administrator (PD_Project)

197

Project Data Manager Enable/Disable Piping Segments Flow Direction Check - Toggles to determine whether flow direction is to be checked for piping segments.

1. Select Option. Select Design Checks Options from the Revise Piping Model Data form. The Design Consistency Check form is displayed. 2. Select Interactive Check. Select the applicable parameter to toggle the setting between Check (*) and No Check. 3. Select Design Checker. Select the applicable parameter to toggle the setting between Check (*) and No Check. 4. Select Hard/Soft. Select the applicable parameter to toggle the setting between Hard and Soft. 5. Specify Flow Centerline Alignment. 6. Type an angle value in degrees to indicate the acceptable tolerance for flow centerline alignment between connected components. 7. Specify Insulation Thickness. Type a value in subunits to indicate the acceptable tolerance for insulation thickness. 8. Accept Design Consistency Check Specifications. Choose the Confirm button to accept Design Consistency Check specifications. The Revise Model Data form is displayed.

198

Plant Design System (PDS) Project Administrator (PD_Project)

Project Data Manager

De s ig n Ch e c ks En d P re p Ta b le The Design Checks End Prep Table option is used to select the classification of end preparations to review or modify. All of these options make up the End Prepartion Compatibility Table. For each of the options, compatibility can be specified between different end preparations. (Refer to code list set 330 for a description of the various end preparations.) Bolted Connections compatibilities can be defined for up to 60 End Preps. Male Connections compatibilities can be defined for up to 30 End Preps. Female Connections compatibilities can be defined for up to 29 End Preps.

1. Select Option. Select the Design Checks End Prep Table option from the Revise Piping Model Data form. The End Prep Compatibilities options form is displayed. 2. Select Category. Select the category of End Preparations to be modified: Bolted, Male, or Female.

Plant Design System (PDS) Project Administrator (PD_Project)

199

Project Data Manager The End Prep Compatibilities form is displayed. This fields on this form are specific to the selected category. The following form reflects the Bolted Connections.

3. Select End Prep. Select the individual end prepartion whose compatibility is to be reviewed or modified. The available compatibilities for the selected end preparation are displayed. The active compatibilities are highlighted.

4. Change Compatibility. To change a compatibility, select the appropriate field from the Compatibilities for list. The options toggle between compatible (highlighted) and incompatible.

200

Plant Design System (PDS) Project Administrator (PD_Project)

Project Data Manager Use the scroll bar to page through the available end preparations.

5. Accept Compatibilities. Choose the Confirm button to accept the defined compatibilities. The End Preps and Compatibilities for RFFE fields are reset. 6. Select Another End Preps —OR— Cancel. Select another End Preps or choose Cancel. When Cancel is selected, the End Prep Compatibilities options form is displayed.

S ym b o lo g y Dia g n o s tic Ma rke rs The Symbology Diagnostic Markers option is used to specify the graphic symbology to be used for view independent symbols (markers), the symbols to be used for special graphics, and the line weight for marker graphics. Symbol Font Number - Identifies the symbol font for symbology. Text Height - Identifies the text height for symbology. Text Width - Identifies the text width for symbology. Field Weld Symbol Name - The character number (within the Symbol Font) of the symbol to be assigned for field welds. Isometric Drawing Limit Symbol Name - The character number (within the Symbol Font) of the symbol to be assigned for isometric drawing limits. No permanent graphics are placed in the model for a field weld or isometric drawing limit. This information can be displayed while working in the model by using the Temporary Symbology command. Diagnostic Markers - Displays the slide bar to select the text weights for Diagnostic Markers. Automated Placement Markers - Displays the slide bar to select the line and text weights for Automated Placement Markers. These markers are used to indicate errors (such as an attempt to place a component that is not defined in the active Piping Materials Class) in automated component placement. Piping errors are indicated by a P, and components are indicated by a C. Model Reconstruction Markers - Displays the slide bar to select the line and text weights for Model Reconstruction Markers. These markers are used to indicate errors that are detected during model reconstruction.

Plant Design System (PDS) Project Administrator (PD_Project)

201

Project Data Manager Field Weld and Isometric Drawing Symbol - Displays the slide bar to select the line and text weights for Field Weld and Isometric Drawing Symbol. These markers are used as temporary symbology to indicate the location of field welds or isometric drawing limits along a pipeline.

1. Select Option. Select the Symbology Diagnostic Markers option from the Revise Piping Model Data form. The Symbology for Markers form is displayed. 2. Specify Symbol Font Number. Type any changes to the symbol font information. 3. Specify Text Height and Text Width. Type any changes to the text size. 4. Specify Field Weld Symbol Name. Type the character number (within the Symbol Font) of the symbol to be used for field welds. 5. Specify Isometric Drawing Symbol Name. 6. Type the character number (within the Symbol Font) of the symbol to be used for isometric drawing limits. 7. Select Diagnostic Markers. Select the line weights for Diagnostic markers from the displayed slide bar. 8. Specify Automated Placement Markers. Select the line weights for Automated Placement Markers from the displayed slide bar. 9. Specify Model Reconstruction Markers.

202

Plant Design System (PDS) Project Administrator (PD_Project)

Project Data Manager Select the line weights for Model Reconstruction Markers from the displayed slide bar. 10. Specify Field Weld and Isometric Drawing Symbol. Select the line weights for Field Weld and Isometric Drawing Symbol from the displayed slide bar. 11. Accept Symbology for Markers. Choose Confirm to accept settings for Symbology for Markers. The Revise Model Data form is displayed.

S ym b o lo g y - Mo d e l The Symbology - Model option is used to specify the model symbology for component placement and to indicate whether color codes are based on model category, fluid code, or construction status. Piping Commodity Weights - Displays the slide bar to select the line weights for Piping Commodity Weights. Piping Specialty Weights - Displays the slide bar to select the line weights for Piping Specialty Weights. Instrument Weights - Displays the slide bar to select the line weights for Instrument Weights. Piping/Tubing Weights - Displays the slide bar to select the line weights for Piping/Tubing Weights. Pipe Support Weights - Displays the slide bar to select the line weights for Pipe Support Weights. Model Symbology - Select the model symbology option (Simple or Detailed) to be used when placing components. This setting can be overridden while working in the model.  Simple model symbology displays flanged components such as valves without showing the flange, thereby using less design file space. The displayed valve diameter is the same as the size of the flange, and the flange is reported in the MTO.  Detailed model symbology displays the flange at the ends of all flanged components. Color - Define this option before any models are created; do not change this option after any model data has been defined. For a description of the color codes defined as a function of model category, see Model Category (on page 207). For a description of the color codes defined as a function of fluid code ranges, see Fluid Code (on page 210). For a description of the color codes and line styles defined as a function of construction status, see Construction Status (on page 212). A dialog box is displayed if the Color option is revised under the following conditions.  If this option is revised for the piping seed model when only the piping seed model exists, (as at project creation) a message displays warning to select the proper option and it should not be changed once design data has been created.  If this option is revised for the piping seed model when one or more piping models have been created, a message displays warning the model symbology option should not be changed once design data has been created.

Plant Design System (PDS) Project Administrator (PD_Project)

203

Project Data Manager 

If the model symbology option is revised for an individual piping model, a message displays warning the model symbology option should not be changed once design data has been created.

1. Select Option. Select the Symbology - Model option from the Revise Piping Model Data form. The Graphic Symbology form is displayed. 2. Specify Weights. Select the category for the MicroStation line weights of symbol graphics: Piping Commodity, Piping Specialty, Instrument, Piping/Tubing, and Pipe Support. When one of these fields is selected, a slide bar is displayed. Place a data point along the slide bar to change the line weight.

3. Select Model Symbology. Select the model symbology option (Simple or Detailed) to be used when placing components. 4. Select Color. Select the option (Model Category, Fluid Code, or Construction Status) to define the use of color in segregating model graphics. 5. Accept Graphic Symbology. Choose Confirm to accept Graphic Symbology.

204

Plant Design System (PDS) Project Administrator (PD_Project)

Project Data Manager The Revise Model Data form is displayed.

S ym b o lo g y - In s u la tio n The Symbology - Insulation option is used to define graphic symbology for insulation display within a piping model. Level - The drawing level on which insulation graphics are to be placed. All insulation graphics are placed on the defined graphic level. Default Color - The Select Color form is placed with the default insulation color selected. A color or color number (as defined in the current PDS color form) may be selected from the form. Weight - Displays the slide bar to select the line weights for insulation graphics. All insulation are placed using the selected line weight.

Style - Displays line style for insulation graphics. All insulation will be placed using the selected line style.

Place Insulation Graphics or Do Not Place Insulation Graphics toggle - A toggle setting which defines whether insulation graphics are placed in the model. Note: This toggle setting can also be set in the Piping Design Graphics software under the Active Options command. Important: Internal insulation (i.e., refactory lining) will not result in the creation of insulation graphics. Insulation purpose values within the range of 30-39 will be recognized as refactory lining, and will not generate insulation graphics Placement of Insulation Graphics is controlled by adding or removing the model category Insulation Graphics in PD_Draw or the PD_Design software. For more information about adding or removing model categories refer to the Drawing Manager (PD_Draw) User's Guide or the Piping Design Graphics (PD_Design) Reference Guide. Insulation Purpose - This field is for display only. It lists all of the available types of insulation as defined in code list 220. See Appendix G of the Piping Component Data Reference Guide to review code list 220. Color - Displays the associated color for each Insulation Purpose. A maximum of 20 Insulation Purposes can be defined. After the initial 20, the Default Color is assigned. The Select Color form is displayed with the default insulation color selected. Select a color or color number (as defined in the current PDS color form) to assign a specific color to an insulation purpose or select Undefined to remove the currently assigned color. Select Confirm to accept the currently defined colors. Notes:  The Color setting overrides the color defined in the Default Color field.  A maximum of 20 Insulation Purposes can be defined. Subsequent Insulation Purposes are assigned the Default Color. Tip: If a customized Select Color form is being used with insulation graphics, the form will need to be modified, COLOR.fb, to add the Undefined button. The form can be modified COLOR.fb using DB Access. Modify the form using the following information: gadget_label = 99

Plant Design System (PDS) Project Administrator (PD_Project)

205

Project Data Manager key = 3099 Text = 'Undefined'

1. Select Option. Select the Symbology - Insulation option from the Revise Piping Model Data form. The Insulation Graphics Symbology form is displayed. 2. Specify Level. Type the drawing level on which insulation graphics are to be placed. 3. Select Default Color. The Select Color form is placed with the default insulation color selected. Select a color or color number (as defined in the current PDS color form) from the form; then choose the Confirm button. 4. Select Weight. Select the Weight field and place a data point along the slider to set the weight. 5. Select Style. Select the Style field and choose a line style for insulation graphics. 6. Select Place Insulation Graphics/Do Not Place Insulation Graphics. Select a toggle setting to define if insulation graphics are placed in the model. 7. Select Color. Select the Color field. The Select Color form is displayed with the default insulation color selected. Select a color or color number (as defined in the current PDS color form) to assign a specific color to an insulation purpose or select Undefined to remove the currently assigned color. Select Confirm to accept the currently defined colors. 8. Accept Insulation Graphics Symbology.

206

Plant Design System (PDS) Project Administrator (PD_Project)

Project Data Manager Choose Confirm to accept Insulation Graphics Symbology. The Revise Model Data form is displayed.

S ym b o lo g y Le ve l a n d Co lo r The Symbology Level and Color option varies depending on the active model symbology as defined with the Symbology Model command. Depending on the active option, the system displays one of the following forms: Model Category (on page 207) Fluid Code (on page 210) Construction Status (on page 212) When the Level and Color options are selected, the system displays a dialog box warning this option should not be changed once design data has been created.

Mo d e l Ca te g o ry If the model symbology color option is set to Model Category, the Level and Color option activates the Graphic Symbology - Model Category form, which may be used to specify:  Levels and color codes by model category.  Nominal piping diameter ranges (small, medium, and large) used when determining levels for piping segments, commodity items, pipes, engineered items, and in-line instruments.  Levels and color codes for labels and markers. The color codes are only used if color is defined as a function of Model Category in the Graphic Symbology form. Nominal Piping Diameter: Small is = - Defines the size for a large piping diameter. Model Category - Display only field which identifies the Model Category. Approved or Not Approved - Display only assignment of Approved or Not Approved for the corresponding Model Category. Nominal Piping Diameter - Display only assignment of the Nominal Piping Diameter size. Level - Displays the drawing level for the associated Model Category.

Plant Design System (PDS) Project Administrator (PD_Project)

207

Project Data Manager Color - Displays the Select Color form with the currently selected color highlighted.

1. Select Option. Select the Level and Color option on the Revise Model Data form. The Graphic Symbology - Model Category form is displayed. 2. Specify Nominal Piping Diameter. Type the values to define the nominal piping diameter ranges (small, medium, and large). 3. Specify Level. Select the level field for a specific category and type the level value. The scroll arrows can be used to page through the category data. 4. Specify Color. Select the appropriate Color field.

208

Plant Design System (PDS) Project Administrator (PD_Project)

Project Data Manager The Color form is displayed with the currently selected color highlighted.

Note: DBAccess can be used to modify the Color form (color.fb) to include up to 256 color choices. This I/Form may be customized to display as many as 66 colors. Use the following characteristics to specify the colors for any of the 66 buttons on this I/Form:  Text or a symbol to designate the color  Gadget number = 100 + color value  Key = 3100 + color value Please refer to the DBAccess documentation for more information on customizing I/Forms. 5. Accept Color. Choose the Confirm button to accept the displayed color selection. The Graphic Symbology - Model Category form is displayed. 6. Accept Graphic Symbology - Model Category. Choose the Confirm button to accept any changes to the graphic symbology by model category. The Revise Model Data form is displayed.

Plant Design System (PDS) Project Administrator (PD_Project)

209

Project Data Manager

Flu id Co d e If the model symbology color option is set to Fluid Code, the Level and Color option displays the Graphic Symbology - Fluid Code form, to specify:  Levels and colors for piping and components as a function of fluid code ranges.  Levels and color codes for piping segments and pipe supports.  Levels and color codes for labels and markers. Notes: It is recommended that you have codelist 125 (fluid code) defined and loaded before setting these values.  The fluid codes should be grouped into like categories. For example, all utility water fluids in the range of 2-19. Model Category - Display only field which identifies the Model Category. Approved or Not Approved - Display only assignment of Approved or Not Approved for the corresponding Model Category. Upper Range - Defines the fluid code ranges. Only upper ranges are stored; the lower range is assumed to be one greater than the previous upper range. Up to twelve fluid code ranges can be defined. Level - Displays the drawing level for the associated Fluid Code. Color - Displays the Select Color form with the currently selected color highlighted.

The scroll arrows can be used to page through the fluid code/category data.

210

Plant Design System (PDS) Project Administrator (PD_Project)

Project Data Manager The remaining fluid code category data is shown in the following figures:

1. Specify Upper Range. Select the fluid code range and type new information for the associated Model Category. Note:  Up to twelve fluid code ranges can be defined. 2. Specify Level. Select level information and type the new numeric value. 3. Specify Color. Select the color field for a specific associated Model Category. The Select Color form is displayed. 4. Select Color.

Plant Design System (PDS) Project Administrator (PD_Project)

211

Project Data Manager Select a color and choose the Confirm button to accept. The Graphic Symbology - Fluid Code form is displayed. 5. Accept Graphic Symbology - Fluid Code. Choose the Confirm button to accept any changes to the fluid code symbology data. The Revise Model Data form is displayed.

Co n s tru c tio n S ta tu s If the model symbology color option is set to Construction Status, two symbology options are displayed on the Revise Model Data form: Level and Color and Style.

Level When the Level option is selected, the Graphic Symbology - Construction Status form is displayed. This form is used to specify the level assignments by category. Small is .

Specification/Material Reference Database PDtable_240 The system adds the Pipe Support Group Table (PDtable_240). Piping Support Group table number = 240, number of columns = 3 1 , system_unique_no , integer 2 , support_group , character (6) 3 , group_descr , character (40) PDtable_241 The system adds the Piping Support Commodity Reference Data Table (PDtable_241). Piping Support Commodity Reference Data table number = 241, number of columns = 11 1 , system_unique_no , integer 2 , support_group , character (6) 3 , commodity_name , character (6) 4 , npd_from , short 5 , npd_to , short 6 , tdf_table_name , character (8) 7 , temp_table , character (8) 8 , sched_table , character (8) 9 , attachment_type , short 10 , model_code , character (6) 11 , material_desr , character (50) PDtable_242 The system adds the Piping Support Material Reference Data Table (PDtable_242). Piping Support Material Reference Data

398

Plant Design System (PDS) Project Administrator (PD_Project)

Upgrading Existing Projects table number = 242, number of columns = 10 1 , system_unique_no , integer 2 , commodity_name , character (6) 3 , npd_from , short 4 , npd_to , short 5 , geometric_standard , short 6 , material_index , character (16) 7 , drawing_seed , character (16) 8 , item_key0 , character (2) 9 , item_key1 , character (2) 10 , item_key2 , character (2) PDtable_243 The system adds the Piping Support Description Data Table (PDtable_243). Piping Support Description Data table number = 243, number of columns = 7 1 , system_unique_no , integer 2 , material_index , character (6) 3 , sequence_number , short 4 , quantity , short 5 , dimension_att_no , short 6 , implied_status , short 7 , material_descr , character (80)

5.* to 6.0 Update Process The following files will be revised by upgrading a project:  Project Control Database and its corresponding definition (project.ddl)  Piping Design Database and its corresponding definition (design.ddl)  Reference Database and its corresponding definition (reference.ddl)  piping seed file and all piping models  drawing seed file(s) and all drawings  area marker files  all approved and unapproved Reference Database Libraries

Summary of Database Changes Project Control Database PDtable_118 The system adds the Inspection Iso Data table (PDtable_118) to the Project Control Database; it is used to maintain the inspection iso search criteria, and the maximum inspection assigned on a line. The following is a summary of the structure of this table: Inspection Iso Data table number = 118, number of columns = 3 1 , inspection_iso_id , character(24) 2 , inspection_status , short 3 , max_inspection_key , short PDtable_127

Plant Design System (PDS) Project Administrator (PD_Project)

399

Upgrading Existing Projects The system updates the Reference Model Display Category Setup Data Table (PDtable_127) to include six new columns: four to record your choice of which levels are to be used when running vector hidden line removal, and two new columns for symbology. 7, vhl_category_msk_a 8, vhl_category_msk_b 9, vhl_category_msk_c 10 , vhl_category_msk_d 11 , vhl_ref_symbology 12 , vhl_symbology

Piping Design Database PDtable_12 The system updates the Piping Segment Data Table (PDtable_12_n) to include two new columns. 75 , inspection_iso_id , character(24) 76 , index_to_pi_dwg , integer The system appends the columns to the end of the table (after any columns that you may have added). PDtable_34 The system updates the Piping Component Data Table (PDtable_34_n) to include eight new columns. 119 , last_placed_date , integer 120 , generic_comp_no , character(20) 121 , inspection_key , short 122 , cp_1_inspect_key , short 123 , cp_2_inspect_key , short 124 , cp_3_inspect_key , short 125 , cp_4_inspect_key , short 126 , cp_5_inspect_key , short The columns are appended to the end of the table (after any columns that you may have added). PDtable_50 The system updates the Piping/Tubing Data Table (PDtable_50_n) to include four new columns. 58 , last_placed_date , integer 59 , inspection_key , short 60 , end_1_inspect_key , short 61 , end_2_inspect_key , short The columns are appended to the end of the table (after any columns that you may have added). PDtable_67 The system updates the Instrument/Component Data Table (PDtable_67_n) to include eight new columns. 126 , last_placed_date , integer 127 , generic_comp_no , character(20) 128 , inspection_key , short 129 , cp_1_inspect_key , short 130 , cp_2_inspect_key , short 131 , cp_3_inspect_key , short 132 , cp_4_inspect_key , short 133 , cp_5_inspect_key , short The columns are appended to the end of the table (after any columns that you may have added). PDtable_80

400

Plant Design System (PDS) Project Administrator (PD_Project)

Upgrading Existing Projects The system updates the Pipe Support Data Table (PDtable_80_n) to include two new columns. 37 , last_placed_date , integer 38 , inspection_key , short The columns are appended to the end of the table (after any columns that you may have added).

Material Reference Database PDtable_203 and PDtable 20 The system updates the Piping Specialty Specification Data table (PDtable_203) and the Instrument Component Specification Data table (PDtable_204) to include a new column to record the type of input form for instruments and piping specialties. 26 , input_form_type , short , SN 990

Summary of Library Changes Label Description Library This library has been modified to include the following new label numbers: 332 = Segment Data - Line1 333 = Segment Data - Line2 334 = Segment Data - Line3 335 = Inspection Iso Id (SmartPlant Review Labels) 390 = PLANTGEN PIPE 391 = PLANTGEN COMPONENT 392 = PLANTGEN EQP/MISC 393 = PLANTGEN NOZZLE 394 = PLANTGEN STR/CIVIL 395 = PLANTGEN HVAC 396 = PLANTGEN RACEWAY 397 = PLANTGEN SUPPORT (Clash Labels) 2240 = PLANTGEN PIPE 2241 = PLANTGEN COMPONENT 2242 = PLANTGEN EQP/MISC 2243 = PLANTGEN NOZZLE 2244 = PLANTGEN STR/CIVIL 2245 = PLANTGEN HVAC 2246 = PLANTGEN RACEWAY 2247 = PLANTGEN SUPPORT (Drawing Labels) 2500 = PLANTGEN PIPE 2501 = PLANTGEN COMPONENT 2502 = PLANTGEN EQP/MISC 2503 = PLANTGEN NOZZLE 2504 = PLANTGEN STR/CIVIL 2505 = PLANTGEN HVAC 2506 = PLANTGEN RACEWAY 2507 = PLANTGEN SUPPORT Label number 335 is required for Inspection Iso Management Data. Standard Note Library

Plant Design System (PDS) Project Administrator (PD_Project)

401

Upgrading Existing Projects The following modifications have been made:  Standard Note 990 now includes input_form_type attribute values for the instrument and piping specialties.  Standard Note 31, Object Type, was added to control some aspects of automatic label placement.  New codelists should be loaded to your existing Standard Note Library. Follow these steps:  Reference the delivered 6.0 Standard Note Library on the Reference Data Management Data form.  Extract neutral files for the new codelists.  Add the neutral files to your existing Standard Note Library.

4.3 to 5.0 Update Process The following files will be revised by upgrading a project.  Project Control Database and its corresponding definition (project.ddl)  Piping Design Database and its corresponding definition (design.ddl)  Reference Database and its corresponding definition (reference.ddl)  piping seed model  all piping models  seed drawings  all orthographic drawings  all approved and unapproved Reference Database Libraries

Project Control Database PDtable_103 The system updates the Project Control Data Table (PDtable_103) to include ten new columns: 30 , mdl_status_low_dr , short , SN 1605 31 , mdl_status_high_dr , short , SN 1605 32 , mdl_status_low_ic , short , SN 1605 33 , mdl_status_high_ic , short , SN 1605 34 , area_owner_option , short 35 , eqp_insulation_opt , short 36 , eqp_con_tol_option , short 37 , clash_rpt_index_no , integer 38 , report_search_path , character(36) 39 , report_search_node , character(26) 



 

402

Columns 30 and 31 define the range of values for a model's model status that are considered to be preliminary or temporary with respect to the SmartPlant Review process and should be automatically eliminated by the DesignReview Label Builder. A default value of minus one is inserted for these columns. Columns 32 and 33 define the range of values for a model's model status that are considered to be preliminary or temporary with respect to interference checking and should be automatically eliminated by the Interference Checker. A default value of minus one is inserted for these columns. Column 34 reflects the state of the single design area ownership versus dual design area ownership option for the Interference Checker. Column 35 reflects the state of the include insulation versus exclude insulation option for the Envelope Builder with respect to equipment models.

Plant Design System (PDS) Project Administrator (PD_Project)

Upgrading Existing Projects 

Column 36 reflects the states of the options to enable or disable the use of construction tolerances with each of the eight equipment envelope types.  Column 37 designates the specific clash management report to by used by the Interference Checker in project mode.  Columns 38 and 39 designate the default location for the report search criteria data. A default value of zero is inserted for columns 33 to 36. A default value of blank is inserted for columns 37 to 39. PDtable_104 The system updates the Project Archival Management Data Table (PDtable_104) to include four new columns to be used in displaying a list of the scheduled archival options. 7 , month_map , integer 8 , day_of_week_map , integer 9 , day_map , integer 10 , time_of_day , integer A default value of zero is inserted for all columns. PDtable_111 The system updates the Engineering Discipline Data Table (PDtable_111) to include two new columns to record the user's specification of the discipline matrix. 4, discipline_matrix_a , integer 5, discipline_matrix_b , integer Default values of zero are inserted for these columns. The system updates the Design Area Data Table (PDtable_112) within the Project Control Database to include a new column to record the user's selection of the specific clash management report to by used by the Interference Checker in either design area mode or pre-defined volume mode for the specific design area. 15 , clash_rpt_index_no , integer A default value of minus one is inserted for this column. PDtable_113 The system updates the Model Data Table (PDtable_113) within the Project Control Database to include a new column to record the user's specification of a status for the model. 17 , model_status , short , SN 1605 The model status can be used to eliminate certain models, such as those considered to be preliminary or temporary, from clash checking or from SmartPlant Review. The values for model status are determined from standard note type 1605 in the Standard Note Library. A default value of one is inserted for this column. PDtable_116 and PDtable_117 The system adds two tables to the Project Control Database to support the existence of more than one structural sub-project within a project. The project upgrade process will determine whether the Structural Sub-Project Control Data Table (PDtable_116) and the Design Area Per Sub-Project Data Table (PDtable_117) have been created in the Project Control Database. If not, the schema will be revised automatically to include these tables. These tables are required for extensions to the integration of ModelDraft into the PD_Shell environment. The system also adds the appropriate schema information to the Project Control Database definition file (project.ddl) in the project directory. The following is a summary of the structure of the two tables. Structural Sub-Project Control Data table number = 116, number of columns = 6

Plant Design System (PDS) Project Administrator (PD_Project)

403

Upgrading Existing Projects 1, sub_project_ndx_no , short 2, sub_project_no , character(15) 3, sub_project_name , character(40) 4, sub_project_path , character(50) 5, sub_project_node , character(26) 6, sub_project_mount , character(50) Design Area Per Sub-Project Data table number = 117, number of columns = 2 1, area_index_no , short 2, sub_project_index_no, short The sub-project number in the Structural Sub-Project Control Data Table will have its default value defined to be the same as the project number from the Project Description Data Table (PDtable_101). Likewise, the sub-project name will have its default value defined to be the same as the project name from the Project Description Data Table. PDtable_126 The system updates the Drawing Setup Data Table (PDtable_126) in the Project Control Database to include nine new columns. 8 , cell_file_spec , character(14) 9 , cell_path_name , character(36) 10 , cell_net_address , character(26) 11 , plot_catgy_mask_a , integer 12 , plot_catgy_mask_b , integer 13 , label_mask_a , integer 14 , label_mask_b , integer 15 , label_mask_c , integer 16 , label_mask_d , integer Columns 8, 9, and 10 are used to record the user's selection of the cell library to be used on the basis of the orthographic drawing type. A default value of blank is inserted for these columns. Columns 11 and 12 are used to record the user's selection of the default drawing categories to be plotted on the basis of the orthographic drawing type. Columns 13 through 16 are used to record the user's selection of the label types to be available in drawing annotation on the basis of the orthographic drawing type. A default value of zero is inserted for the last six columns. PDtable_131 The system updates the Clash Job Data Table (PDtable_131) in the Project Control Database to include eight new columns to record the interference checking options. 8, clash_check_option , short , SN 1208 9, volume_filter_option, short , SN 1209 10 , volume_low_x , integer 11 , volume_low_y , integer 12 , volume_low_z , integer 13 , volume_high_x , integer 14 , volume_high_y , integer 15 , volume_high_z , integer A default value of one is inserted for the first two columns. A default value of zero is inserted for the six volume columns. PDtable_132 The system updates the Clash Data Per Project Table (PDtable_132) to include two new columns to record the recent sequence number and the design area index number for the primary design

404

Plant Design System (PDS) Project Administrator (PD_Project)

Upgrading Existing Projects area associated with component B, if applicable. The pre-existing recent sequence number column and the design area index number column in this table will be associated with the primary design associated with component A. The following is a summary of the columns being added to the Clash Data Per Project Table. 15 , recent_seq_no_b , integer 16 , area_index_no_b , short A default value of zero is inserted for these columns. PDtable_141 The system updates the Report Data Table (PDtable_141) to include a new column to record the index to the search criteria that may be specified optionally as part of the report. 20 , search_index_no , integer A default value of zero is inserted for this column. PDtable_145 The system adds PDtable_145 to the Project Control Database to support additional search criteria options within the Report Manager. This table is required for enhancements to the Report Manager. The system also adds the appropriate schema information to the Project Control Database definition file (project.ddl) in the project directory. The following is a summary of the structure of this table. Report Search Criteria Data table number = 145, number of columns = 11 1, search_index_no , integer , index 1 2, search_number , character(24) 3, search_description, character(40) 4, search_file_spec , character(14) 5, path_name , character(36) 6, network_address , character(26) 7, lock_owner , character(10) 8, lock_status , short 9, lock_date , integer 10 , revision_date , integer 11 , rpt_search_source , short , SN 1310 PDtable_151 The system updates the SmartPlant Review Management Data Table (PDtable_151) in the Project Control Database to include nine new columns. 17 , session_rev_date , integer 18 , label_rev_date , integer 19 , label_file_spec , character(14) 20 , label_path_name , character(36) 21 , label_net_address , character(26) 22 , month_map , integer 23 , day_of_week_map , integer 24 , day_map , integer 25 , time_of_day , integer Columns 17 and 18 are used to record the creation/revision dates for the SmartPlant Review session's management data and the SmartPlant Review model's labels. Columns 19 through 25 are used for scheduling the label creation of a SmartPlant Review model. A default value of zero is inserted for all columns.

Plant Design System (PDS) Project Administrator (PD_Project)

405

Upgrading Existing Projects Piping Design Database PDtable_34 The system updates the Piping Component Data Table (PDtable_34_n) within the Piping Design Database to include four new columns. 115 , vlv_operator_dim_a , double 116 , vlv_operator_dim_b , double 117 , vlv_operator_dim_c , double 118 , vlv_operator_dim_d , double The system appends the columns at the end of the table (after any columns which may have been previously added by the user). PDtable_67 The system updates the Instrument Component Data Table (PDtable_67_n) within the Piping Design Database to include four new columns. 122 , vlv_operator_dim_a , double 123 , vlv_operator_dim_b , double 124 , vlv_operator_dim_c , double 125 , vlv_operator_dim_d , double The columns are appended at the end of the table (after any columns which may have been previously added by the user).

Piping Models and Orthographic Drawings The system revises the Type 63 data of all piping models and all orthographic drawings to distinguish between the new columns, which are being added automatically by PDS, and any columns which may have been added previously by the user. Each orthographic drawing will be automatically upgraded to append additional Type 63 data to support enhancements.

Material Reference Database PDtable_202 The system updates the Piping Commodity Specification Data Table (PDtable_202) within the Material Reference Database to include a new column to record the type of input form to be used by the Reference Data Manager in specifying piping commodity data. 28 , input_form_type , short , SN 990 A default value of zero is inserted for this column. PDtable_233 The system adds the Piping Construction Tolerance Exclusion Data Table (PDtable_233) to the project's Material Reference Database. This table is required to support Interference Checker. The system also appends the appropriate schema information to the Material Reference Database definition file (reference.ddl) in the project directory. The following is a summary of the structure of the Piping Construction Tolerance Exclusion Data Table. Piping Construction Tolerance Exclusion Data table number = 233, number of columns = 7 1, system_unique_no , integer 2, commodity_name , character(6) 3, model_code, character(6) 4, gcp_npd_from , short 5, gcp_npd_to, short

406

Plant Design System (PDS) Project Administrator (PD_Project)

Upgrading Existing Projects 6, rcp_npd_from 7, rcp_npd_to, short

, short

PDtable_221 The system updates the Reference Database Revision Management Data Table (PDtable_221) to include a new column, construction tolerance exclusion revision date (column 8) to record the revision management date for this reference data. A default value of undefined (zero) is inserted for this column. If applicable, both the approved Material Reference Database and the unapproved Material Reference Database will be upgraded.

Shared Reference Data The following rules apply when the Material Reference Database is being shared by more than one project.  The new table will not be added multiple times for a Material Reference Database that is being shared.  Only the reference.ddl file in the project directory will be updated, if the Material Reference Database is being shared with at least one other project and has been previously upgraded for that project.  All the projects which share a Material Reference Database must be upgraded at the same time. If this is not feasible, you must create a new Material Reference Database for the project that is to be upgraded.  You cannot create a new project with the 5.0 PDS release that shares the Material Reference Database with another project that is being completed with an earlier PDS release.

Libraries The system updates the Label Description Library (approved and unapproved) to correct a problem with labels that include user-defined attributes. A library which is being shared by two or more projects will not be upgraded multiple times. The upgrade to the Label Description Library will make it impossible to copy a Label Description Library from a project using an earlier release into a project using the 5.0 release. For releases prior to the 4.2 PDS release, a problem existed in the Reference Data Manager, such that the binary tree structure in a reference data library (such as the Graphic Commodity Library) could be corrupted without the user immediately detecting any problems with that library. Although the software problem was corrected in the 4.2 PDS release, the data problem that resulted may have persisted beyond that release, particularly if the library has not been compressed. As a final step within the project upgrade process, the system will verify the integrity of the binary tree structure within each of the reference data libraries. If an error is detected, a specific warning message will be reported, both interactively and in the upgrade log. In this event, you should contact Intergraph immediately for assistance in repairing the library.

Update Notes The feature to display additional clash management data on clash plots will require a change to the format of the clash plot border. As a result, you must copy the clash plot border (borderifc.dgn) from the IF_Check product directory into the project directory. The automated upgrade process will not automatically copy the new plot clash border into the project directory, since you may have customized the clash plot border, such as adding the company name or logo.

Plant Design System (PDS) Project Administrator (PD_Project)

407

Upgrading Existing Projects

4.2 Update Process The following files will be revised by upgrading a project.  Project Control Database and its corresponding definition (project.ddl)  Piping Design Database and its corresponding definition (design.ddl)  Material Reference Database and its corresponding definition (reference.ddl)  piping seed model  all piping models  seed drawing  all orthographic drawings

Project Control Database The system updates the Model Data Table (PDtable_113) within the Project Control Database to include a new column, model type (column 16). This column records the type of structural model, sparse or propagated. The following steps are performed to update the Project Control Database.  The system reads the column name for the new column from the Project Control Database definition (project.ddl) in the PD_Shell product.  The system appends column 16 to the end of the Model Data Table. A default value of zero (propagated structural model) is inserted for this column.  The system appends the column name for the new column to the Project Control Database definition (project.ddl) in the project directory and updates the number of columns for this table. Note: The automated project upgrade cannot determine the model management data for the sparse model from the data for the corresponding propagated model, since there was no file management correlation between the two models (prior to the 4.3 PDS release). Therefore, you must load the model management data for the sparse structural models through the Project Environment Manager, once the project has been upgraded. For any previously created structural models, refer to Create Model Data from ASCII File (on page 102), for information on creating model management data from an ASCII list. The system updates the Model Setup Data Table (PDtable_115) within the Project Control Database to include two new columns, reference model symbology (column 4) and symbology display option (column 5). These new columns record the selection of the default reference model symbology display on the basis of the discipline. The following steps are performed to upgrade the Project Control Database.  The system reads the column names for the new columns from the Project Control Database definition (project.ddl) in the PD_Shell product.  The system appends columns 4 and 5 to the end of the Model Setup Data Table. Default values of undefined (zero) are inserted for these columns.  The system appends the column names for the new columns to the Project Control Database definition (project.ddl) in the project directory and updates the number of columns for this table. The system updates the Drawing Setup Data Table (PDtable_126) within the Project Control Database to include a new column, seed drawing option (column 7). This column records the selection of the seed drawing to be used within that drawing type. The following steps are performed to upgrade the Project Control Database.

408

Plant Design System (PDS) Project Administrator (PD_Project)

Upgrading Existing Projects 

The system reads the column name for the new column from the Project Control Database definition (project.ddl) in the PD_Shell product.  The system appends column 7 to the end of the Drawing Setup Data Table. A default value of zero (use the project seed drawing) is inserted for this column.  The system appends the column name for the new column to the Project Control Database definition (project.ddl) in the project directory and updates the number of columns for this table. The system performs the following changes to the structure of the clash management data in the Project Control Database to improve performance.  indexes the unique clash id in the Clash Review History Table (PDtable_135) of the Project Control Database.  indexes the recent sequence number in the Clash Data Per Project Table (PDtable_132) of the Project Control Database.  removes the indices for model index number a and model index number b in the Clash Data Per Project Table (PDtable_132) of the Project Control Database.  removes the indices for unique sequence number and clash type in the Clash Data Per Job Table (PDtable_133) of the Project Control Database. PDS 4.3 creates isometric drawing management data, when a new piping design area is created with the Project Environment Manager. In previous releases, the isometric drawing management data had to be created as a separate activity through the Isometric Drawing Manager. To support this feature, the system creates isometric drawing management data for any existing piping design areas for which iso design areas have not been created. For each piping design area that does not have the corresponding isometric drawing management data, the system creates a row in the Isometric Design Area Definition Data Table (PDtable_183) that is associated with the applicable Design Area Data Table (PDtable_112). All other columns in this table are loaded with blank (or zero) values.

Piping Design Database The system updates the Piping Segment Data Table within the Piping Design Database to include a new column, color code, for piping segments. The column is added automatically at the end of the table (after any existing user-defined columns). The default name for this column is color_code. If you need to change the name of this column ,for example to resolve a conflict with the name of a user-defined column, you must edit the design.ddl in the PD_Shell product directory, prior to updating a project. The color code column has a default length of 8 characters, but you can increase that length to a maximum of 20 characters. The system updates the Instrument Component Data Table within the Piping Design Database to include a new column, bend angle, for instrument components. The column is added automatically at the end of the table (after any existing user-defined columns). To distinguish between these columns, which are being added automatically by PDS, and any user-defined columns, additional data must be revised in the Type 63 data of all piping models and all orthographic drawings.

Material Reference Database The system determines whether the following tables have been created in the project's Material Reference Database. Component Insulation Exclusion Data Table (PDtable_231) Flange Insulation Exclusion Data Table (PDtable_232) If not, the following steps are performed to upgrade the Material Reference Database.

Plant Design System (PDS) Project Administrator (PD_Project)

409

Upgrading Existing Projects 

The system revises the schema to include the Component Insulation Exclusion Data Table (PDtable_231) and the Flange Insulation Exclusion Data Table (PDtable_232). These tables are required to support enhancements to the Piping Envelope Builder; however, the use of these enhancements is optional.  The system adds the appropriate schema information to the Material Reference Database definition file (reference.ddl) in the project directory.  The system updates the Reference Database Revision Management Data Table (PDtable_221) to include two new columns, component insulation exclusion revision date (column 6) and flange insulation exclusion revision date (column 7), to record the revision management dates for this reference date.  The system reads the column names for the new columns from the Material Reference Database definition (reference.ddl) in the PD_Shell product.  The system appends the two new columns to the end of the Reference Database Revision Management Data table. Default values of undefined (zero) are inserted for these columns.  The system appends the column names for the new columns to the Material Reference Database definition (reference.ddl) in the project directory and updates the number of columns for this table. If applicable, both the approved Material Reference Database and the unapproved Material Reference Database will be upgraded.

4.1 Update Process The following files will be revised by upgrading a project.  Project Control Database and its corresponding definition (project.ddl)  Approved Physical Data Libraries  Unapproved Physical Data Libraries  Approved Piping Job Specification Table Library  Unapproved Piping Job Specification Table Library Note: You must have write privileges for all of the above files as well as for the directory(ies) where the Physical Data Libraries and Piping Job Specification Table Library reside.

Project Control Database The system updates the Component Clash Data Table (PDtable_134) within the Project Control Database to include a new attribute, component model status (column 7), to record the applicable discipline's model (or approval) status for that specific component. The following steps are performed to upgrade the Project Control Database.  The system reads the column name for the new column from the Project Control Database definition (project.ddl) in the PD_Shell product.  The system appends column 7 to the end of the Component Clash Data Table. A default value of zero (undefined) is inserted for this column.  The system appends the column name for the new column to the Project Control Database definition (project.ddl) in the project directory and updates the number of columns for this table.

Reference Data The system updates the approved and unapproved (if applicable) Physical Data Library (or Libraries) and Piping Job Specification Table Library to provide revision management dates for

410

Plant Design System (PDS) Project Administrator (PD_Project)

Upgrading Existing Projects each table entry. A library which is being shared by two or more projects will not be upgraded multiple times. Once upgraded, the user can share this library with any other project being completed with a previous CLIX PDS release.

Plant Design System (PDS) Project Administrator (PD_Project)

411

Upgrading Existing Projects

412

Plant Design System (PDS) Project Administrator (PD_Project)

Index 2 2D Project • 307

4 4.1 Update Process • 410 4.2 Update Process • 408 4.3 to 5.0 Update Process • 402

5 5.* to 6.0 Update Process • 399

6 6.0/6.1 to 6.3 Update Process • 397

A Access Control Files • 356 Access Control Manager • 351 Access Control Manager Password Form • 351 Active Project Retrieval • 317 Angular/Slope Label/Readout • 152 Archival Creation/Revision • 311 Archived User Data • 309 Attach Equipment Model • 100 Attributes to be Displayed/Case Insensitive • 55 Authorization Data • 357

B Batch Processes • 41

C Common Tools on the PD_Shell Forms • 36 Complete Project • 307 Component Placement • 179 Construction Status • 212 Coordinate Label Data • 227 Coordinate Label/Readout Descriptions • 155 Coordinate Label/Readout Format • 157 Coordinate Label/Readout Precision • 160 Coordinate Label/Readout Units • 158 Coordinate System Definition • 149 Copy Model • 93 Create Database Tables • 101

Create Design Area Data • 86, 139 Create Design Area Data Form • 139 Create Discipline Data • 85 Create Model • 86 Create Model Data from ASCII File • 102 Create Options Form • 84 Create Package • 280 Create Project • 46 Create Project Directory File • 345 Create Site • 70

D Database Information • 31 Date/Time Format • 153 Default Segment Data • 193 Define Construction Tolerances • 164 Delete Archival Schedule • 315 Delete Design Area Form • 130 Delete Discipline • 128 Delete Model • 131 Delete Options Form • 127 Delete Package • 284 Delete Project Information • 65 Delete Reference Data • 67 Delete Site • 72 Design Checks End Prep Table • 199 Design Checks Options • 197 Design Review Label • 192 Design Volume Coordinate System Definition • 239 Design Volume Offset • 99 DesignReview Management Data • 302 DesignReview Sessions • 380 Detailed Design - 2D • 13 Detailed Design - 3D • 14 Discrimination Data Creation Form • 268 Discrimination Data Deletion Form (Project Administrator) • 269 Document Types • 381 Drawing • 249 Drawing Category Data • 218 Drawing Data • 299

E Edit Project Directory File • 342 Envelopes, Steel, and Miscellaneous • 173 Equipment • 244 Export to PDME • 365

Plant Design System (PDS) Project Administrator (PD_Project)

413

Index Export to PDME Command Configuration File • 368

F File Lock Manager • 347 Fluid Code • 210 Format Creation/Revision Form (Project Administrator) • 263 Format Deletion Form (Project Administrator) • 265 FrameWorks Plus Project • 49 FrameWorks Projects • 305

N Nozzle Default Placement Options • 174 Nozzle Transfer • 189

G

O

Graphic Symbology • 170

Orthographic Drawings • 374 Overwrite /Regenerate Intermediate File • 369

H Hidden Line Data • 226

P

I IDM • 373 Import Project Retrieval • 328 Inactive Project Retrieval • 320 Insert Electrical Raceway Data • 75 Insert FrameWorks Data • 73 Insert ModelDraft Data • 76 Interference • 253 Interference Envelope Emulation Data • 177 Interference Management Data • 300 Introduction • 9 Isometric Drawing Management Data • 304 Isometric Drawings • 376

L Label Text Sizes • 219 Loading Baseline Software • 26 Loading Database Products • 31 Loading PDS Products • 26 Loading Products • 25

M Manage Project Directory File • 343 Mass Annotation Data • 221 Material Takeoff • 190 Miscellaneous Label Data • 231 Model • 237 Model Category • 207 Model Data • 296 Model Setup Data Form • 91

414

Model/Drawing Data Retrieval for Workshare Projects • 327 Model/Drawing Import for Workshare Projects • 338 Move Drawings • 115 Move Models • 112 Move Project Directory • 109 MTO Reports • 379

P&I Drawings • 370 Package • 280 PD Shell • 33 PD_Shell Form Conventions • 35 PDS and the Relational Interface System (RIS) • 31 PDS Drawing Annotation Category Data • 222 PDS Environment • 33 PDS Overview • 9 PDS/PDME Document Index Format • 382 PFD • 371 Physical Units • 186 Pipe Support Drawing Data • 300 Piping Data Control • 182 Piping Design Schema • 51 Piping RDB Schema • 56 Preface PDS • 7 Prefix/Suffix Data for Coordinate Labels • 229 Preliminary Design • 12 Preparing the Server and Workstations for PDS • 32 Primitives/Parametrics, Nozzles, Semi-Intelligent, Dumb Graphics • 172 Project Administrator • 43 Project Administrator Overview • 22 Project Archival • 291 Project Archival Manager • 289 Project Archival Manager Form • 289 Project Archival Options Form • 293 Project Archival Types • 309 Project Control Data • 295 Project Control Manager • 257

Plant Design System (PDS) Project Administrator (PD_Project)

Index Project Control Manager Form • 257 Project Control Schema • 48 Project Data Manager • 145 Project Data Manager Form • 145 Project Environment Manager • 81 Project Environment Manager Form • 82 Project Organization • 22 Project Search Criteria (Project Administrator) • 285 Project Setup • 10 Project Setup Manager • 45 Propagate Drawing Data • 233 Propagate Interference Check Data • 167 Propagate Piping Model Data • 214

R Raceway Model • 248 Raceway Project Schema • 51 Raceway RDB Schema • 56 Reference Data • 302 Reference Database File Specifications Drawing Files • 220 Reference Database File Specifications Review File Names • 195 Reference Database File Specifications Specify Approved or Unapproved • 176 Regenerate FrameWorks Plus Frozen Views • 337 Report • 243, 246, 252 Report - Models • 133 Report - Named Items • 135 Report Approval Form (Project Administrator) • 275 Report Creation Form (Project Administrator) • 271 Report Data • 301 Report Deletion Form (Project Administrator) • 274 Report Discrimination Data Form • 266 Report Discrimination Data Form (Project Administator) • 267 Report Form (Project Administrator) • 270 Report Format Form (Project Administrator) • 262 Report Management Defaults Form (Project Administrator) • 278 Report Multiple Submit Form (Project Administrator) • 277 Report of Seed File Data • 236 Report Options Form • 132 Report Revision Form (Project Administrator) • 273 Review Schedule • 316

Revise 3D Drawing Data • 250 Revise 3D Model Data • 148, 238, 245 Revise Area Model Association • 122 Revise Design Area Data • 141 Revise Discipline Data • 120 Revise Drawing Data • 251 Revise Drawing Data - Seed File • 216 Revise Equipment Data • 169 Revise Equipment Data - Model Data • 246 Revise Interference Check Data • 161 Revise Model Data • 121 Revise Model Data - Seed Files • 242 Revise Options Form • 106 Revise Package • 283 Revise Piping Model Data • 178 Revise Project - Add Attributes • 60 Revise Project - Attribute Display • 58 Revise Project - DBAccess • 62 Revise Project Data • 107 Revise Project Location • 108 Revise Site • 71 Revise Site ID for Models • 124 Revise Site ID for Models By Area • 126 Revise Site ID for Models By Model • 127 Revise Site ID for Models By Project • 125

S Schedule Project Import • 334 Scheduled Project Archival • 309 Seed Options Form • 146 Select Action Discipline • 166 Select Source Model's Project Form • 98 Site Administrator • 69 Site Data • 306 Specify Coordinate System • 56 Structural Drawings • 378 Symbology - Insulation • 205 Symbology - Model • 203 Symbology Diagnostic Markers • 201 Symbology Level and Color • 207 System Configurations • 24 System Manager • 341 System Setup • 24

U Update Drawings File Specifications • 118 Update Model File Specifications • 113 Update Project File Specifications • 110 Upgrading Existing Projects • 395 User Data • 308 User Functions • 363 User-defined Attributes • 55

Plant Design System (PDS) Project Administrator (PD_Project)

415

Index User-Defined Drawing Annotation Category Data • 224

W What's New in Project Administrator (PD_Project) • 8

416

Plant Design System (PDS) Project Administrator (PD_Project)