PDS_Project_Administrator_PD_Project.pdf

(1)

Plant Design System (PDS)

Project Administrator (PD_Project)

Version 2010 (V11)

Wednesday, November 17, 2010 DPDS3-PB-200030G

(2)

Copyright

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.

(3)

Plant Design System (PDS) Project Administrator (PD_Project) 3

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

(8)

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)

(9)

S

E C T I O N

1

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.

(10)

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.

(11)

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.

(12)

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.

(13)

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.

(14)

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.

(15)

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.

(16)

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.

(17)

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.

(18)

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.

(19)

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.

(20)

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.

(21)

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.

(22)

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.

(23)

 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™).

(24)

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.

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

(25)

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.

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

(27)

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.

(28)

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.

(29)

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.

(30)

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.

(31)

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.

(32)

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

(33)

S

E C T I O N

2

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.

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.

(34)

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.

(35)

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

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.

(36)

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 <ENTER> or <Tab> key for the data to

be entered into the system. You can also press <ENTER> or <Tab> to move through a set of key-in fields.

Delete - If you make a mistake while keying in text, press the <Delete> 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.

(37)

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 <D>, 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 <Return>. 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

(38)

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

(39)

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

(40)

(41)

S

E C T I O N

3

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.

(42)

(43)

S

E C T I O N

4

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

(44)

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.

PDS_Project_Administrator_PD_Project.pdf

Plant Design System (PDS)

Project Administrator (PD_Project)

Contents

List of PDS Documentation

What's New in Project Administrator (PD_Project)

S

1

For more information, see

PDS Overview

Project Setup

System Setup

2D Setup

3D Setup

Preliminary Design

Process Flow Diagram (PFD)

Detailed Design - 2D

Process & Instrumentation Diagram (P&ID)

Instrument Data Manager (IDM)

Detailed Design - 3D

Equipment Modeling (PD_EQP)

FrameWorks Plus (FW+)

Reference Data Manager (PD_Data)

Drawing Manager (PD_Draw)

PDS Stress Analysis Interface (PD_Stress)

Interference Checker/Manager (PD_Clash)

PDS Isometric Interface (PD_ISO, PD_ISOGEN)

Report Manager (PD_Report)

EE Raceway Modeling

Design Review Integrator (PD_Review)

Project Organization

Project Administrator Overview

Project Environment Manager

Project Data Manager

Project Setup Manager

Project Control Manager

Project Archival Manager

System Manager

File Lock Manager

Access Control Manager

Export to PDME

System Setup

See Also

System Configurations

Servers

Workstations

Loading Products

See Also

Lo a d in g Ba s e lin e S o ftwa re

Windows Baseline

Lo a d in g P DS P ro d u c ts

Advantages and Disadvantages of Remote Access

PDS 3D Installation Options

PDS Products

Using the Client Option

Loading PDS for Windows

Lo a d in g Da ta b a s e P ro d u c ts

Database Information

For more information, see:

P DS a n d th e Re la tio n a l In te rfa c e S ys te m (RIS )

Preparing the Server and Workstations for PDS

S

2

See Also

PD Shell

PD_Shell Form Conventions

Common Tools on the PD_Shell Forms

Standard Commands

Path Location Fields

S

3

S

4