PDS Project Setup Technical Reference

Plant Design System (PDS)
Project Setup Technical Reference
Version 2011 (V12)
June 2011
DPDS3-PB-200023H
Copyright
Copyright © 1984-2011 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
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 ................................................................................................................................................. 9
What's New in Project Setup Technical Reference .............................................................................. 10
Introduction ................................................................................................................................................ 11
Concepts and Terminology ...................................................................................................................... 13
PDS System Requirements ...................................................................................................................... 15

Server Hardware and Software Requirements ..................................................................................... 15
Workstation (Client) Hardware and Software Requirements ................................................................ 16
System Configuration ............................................................................................................................... 19

File Server ...................................................................................................................................... 20
Database Server............................................................................................................................. 20
Software Server .............................................................................................................................. 20
Compute Server ............................................................................................................................. 20
Plot Server ...................................................................................................................................... 20
PDS License Server ....................................................................................................................... 20
Server Requirements ............................................................................................................................ 21
File Server ...................................................................................................................................... 21
Database Server............................................................................................................................. 21
Software Server .............................................................................................................................. 21
Compute Server ............................................................................................................................. 22
Plot Server ...................................................................................................................................... 22
SmartPlant License Manager Server ............................................................................................. 22
Quick Installation Guide for Windows 7.................................................................................................. 23
Loading and Configuring Software ......................................................................................................... 27

Operating Systems and Related Components ..................................................................................... 27
File Systems ................................................................................................................................... 27
Client Nodes ................................................................................................................................... 27
Server Nodes .................................................................................................................................. 28
Software Required for File Sharing ....................................................................................................... 30
Protocols Provided with Windows .................................................................................................. 30
PDS and Windows.......................................................................................................................... 30
Software Compatibility .................................................................................................................... 30
Software Required for Batch Processing .............................................................................................. 30
Core Graphics Software ........................................................................................................................ 31
Software Required for Plotting .............................................................................................................. 31
Database Software ............................................................................................................................... 32
PDS Products, Client Nodes ................................................................................................................. 32
PDS Products, Server Nodes ............................................................................................................... 36
Plant Design System (PDS) Project Setup Technical Reference 3

Contents
Relational Interface System (RIS) ............................................................................................................ 37

Why RIS? .............................................................................................................................................. 37
How RIS Communicates with the Database ......................................................................................... 37
Database Structure ............................................................................................................................... 38
3D Schemas.......................................................................................................................................... 39
2D Schemas.......................................................................................................................................... 40
Preparing for Project Creation ................................................................................................................. 41

Establishing Domain Users and Groups ............................................................................................... 41
Location of the proj File ......................................................................................................................... 41
Sharing the proj File Location Through LAN Manager ................................................................... 42
Default C Drive Permissions .......................................................................................................... 44
Universal Naming Convention ........................................................................................................ 45
Location of schemas File ...................................................................................................................... 49
Creating Batch Queues ......................................................................................................................... 52
Establishing Account Mapping .............................................................................................................. 53
Creating Project Directories and Required Shares ............................................................................... 54
Files Reside on a Windows Server ....................................................................................................... 56
Installing and Configuring SmartPlant License Manager ..................................................................... 59

Creating Required Databases/Database Users .................................................................................... 59
Creating a PDS 2D/3D Project Manually.................................................................................................. 61

Creating Project Directories Manually .................................................................................................. 62
Creating the 3D Project (Equipment and Piping) .................................................................................. 64
Creating a FrameWorks Project............................................................................................................ 70
Creating the EE Raceway Project......................................................................................................... 72
Adding Tables to the EE Raceway Reference Schema ....................................................................... 73
Changing Coordinate Systems and Working Units ............................................................................... 79
Creating PE-HVAC Projects ................................................................................................................. 81
Creating the 2D Project ......................................................................................................................... 89
Adding Disciplines to an Existing Project .............................................................................................. 93
Attaching Reference Data to the Project ................................................................................................. 95

Piping Reference Data .......................................................................................................................... 95
Equipment Reference Data ................................................................................................................. 101
Loading Default Data into the Piping Reference Database ................................................................ 103
Creating 3D Areas and Models .............................................................................................................. 109

Project Organization ........................................................................................................................... 109
3D Disciplines ..................................................................................................................................... 109
3D Areas ....................................................................................................................................... 114
3D Models .................................................................................................................................... 119
Model Creation for Other 3D Disciplines ...................................................................................... 125
3D Design Data and the Database ............................................................................................... 125
2D Disciplines ..................................................................................................................................... 125
Creating a Graphics-only Drawing ............................................................................................... 126
Creating a Database Drawing ...................................................................................................... 127
4 Plant Design System (PDS) Project Setup Technical Reference

Contents
System Administrator Responsibilities ................................................................................................ 131

Plotting in the PDS Environment......................................................................................................... 131
My Computer versus Network Printer Server ............................................................................... 131
Use of My Computer..................................................................................................................... 132
Use of Network Printer Server ...................................................................................................... 133
The queue_descript File ............................................................................................................... 133
Application-specific Considerations .............................................................................................. 133
Modifying Batch Queues for Redirected Processing .......................................................................... 135
Setting the RIS_PARAMETERS Environment Variable ............................................................... 141
Configuring the PDS Batch Mail Utility ......................................................................................... 142
Access Control .................................................................................................................................... 144
Copying a Set of Users to Another Project................................................................................... 148
Creating Backups and Maintaining a Backup Schedule ..................................................................... 148
PDS Project Archive to Back Up Project Data ............................................................................. 149
NTBACKUP or CPIO Backup of Project Data .............................................................................. 155
PDS Project Archive to Back Up Database .................................................................................. 156
NTBACKUP or CPIO Backup of Database Files .......................................................................... 156
RIS Backup of Database .............................................................................................................. 157
Database Vendor Backup of Database ........................................................................................ 157
Full versus Incremental Backups ................................................................................................. 158
Which Backup Methods Should I Use? ........................................................................................ 158
Creating and Maintaining Distributed Projects .................................................................................... 158
RAID Configuration ................................................................................................................................. 159

I/O Subsystem Components ............................................................................................................... 159
Intergraph Supported RAID Levels ..................................................................................................... 161
RAID 0 ................................................................................................................................................. 161
RAID 1 ................................................................................................................................................. 162
RAID 5 ................................................................................................................................................. 163
RAID 6 ................................................................................................................................................. 165
RAID 7 ................................................................................................................................................. 165
Hardware Versus Software RAID Implementations ............................................................................ 166
ISMP 5* or 6* RAID Subsystem Description ....................................................................................... 166
Configuring ISMP RAID for Performance and Availability .................................................................. 167
Scripts to Create Project Directories ..................................................................................................... 171

Script to Create Project Directories on Windows ................................................................................ 171
Log Files Produced by PDS Batch Jobs ............................................................................................... 179

PD_Design .......................................................................................................................................... 183
PD_Model ........................................................................................................................................... 183
PD_Draw ............................................................................................................................................. 183
PD_Report .......................................................................................................................................... 184
PD_Review ......................................................................................................................................... 184
PD_Clash ............................................................................................................................................ 184
PD_Project .......................................................................................................................................... 185
PD_Data .............................................................................................................................................. 185
Notes: .................................................................................................................................................. 187

Contents
PDS Project Creation Workbook ............................................................................................................ 189
PDS and FrameWorks Plus .................................................................................................................... 199

Setup Information ................................................................................................................................ 199
Intergraph SmartPlant License Manager...................................................................................... 199
Creating or Inserting a FrameWorks Plus Project ........................................................................ 200
Creating a Structural Discipline Design Area ............................................................................... 201
Creating a Model in PD_Shell ...................................................................................................... 203
Creating a Model by ASCII File .................................................................................................... 205
Shifting the FrameWorks Plus Global Origin to Match PDS Design Volume ............................... 208
FrameWorks Plus Categories ...................................................................................................... 213
FrameWorks Environment .................................................................................................................. 214
Modeling ....................................................................................................................................... 215
Drawing Environment ................................................................................................................... 215
Propagation .................................................................................................................................. 216
Generate ASCII File ..................................................................................................................... 219
Update/Regenerate Frozen View ................................................................................................. 219
Batch Cutout (PD_Shell) .............................................................................................................. 220
Verify Model (PD_Shell) ............................................................................................................... 224
CIM Steel Export (PD_Shell) ........................................................................................................ 224
FrameWorks Plus and SmartPlant Review ......................................................................................... 225
FrameWorks Plus Extended Labels Dialog Box .......................................................................... 226
FrameWorks Plus and PD_Clash ....................................................................................................... 227
FrameWorks Plus and Material Data Publisher .................................................................................. 228
Database Setup - Oracle ......................................................................................................................... 229

Oracle 11g........................................................................................................................................... 229
Oracle 10.2g........................................................................................................................................ 249
Oracle 10g........................................................................................................................................... 264
Removal of Older RIS Client (Oracle 10g) ................................................................................... 264
Production Database Installation (Oracle 10g) ............................................................................ 265
Oracle 10.2.0.5 Client Installation on Windows 7 ......................................................................... 267
Database Setup - Microsoft SQL ............................................................................................................ 269

MSSQL Server 2008 ........................................................................................................................... 269
Installing MSSQL 2008 ................................................................................................................. 269
Creating the User Database in MSSQL 2008 .............................................................................. 278
Creating Logins and Usernames for Schemas ............................................................................ 280
MSSQL Server 2005 ........................................................................................................................... 281
Installing MSSQL 2005 ................................................................................................................. 281
Creating the User Database in MSSQL 2005 .............................................................................. 284
The PDS queue_descript File ................................................................................................................. 287

Format of the queue_descript File ...................................................................................................... 288
General Processing Rules for Printers/Plotters .................................................................................. 289
PDS Print/Plot Jobs and the queue_descript File ............................................................................... 290
Interactive Jobs Which Print/Plot ........................................................................................................ 291
PDS Batch Jobs and the queue_descript File .................................................................................... 291

Contents
PDS and Windows ................................................................................................................................... 293

PDS and Windows 7 / Server 2008 .................................................................................................... 293
Registry Entries (Windows 7 / Server 2008) ................................................................................ 293
Location of RIS Schemas File (Windows 7 / Server 2008) .......................................................... 296
Environment Variables (Windows 7 / Server 2008) ..................................................................... 297
PDS and Windows 2000 ..................................................................................................................... 297
Registry Entries ............................................................................................................................ 297
Location of RIS Schemas File ...................................................................................................... 300
Environment Variables ................................................................................................................. 300
Active Directories and Windows 2000 Domain ............................................................................ 300
PDS Environment Variables ................................................................................................................... 301

Commands Set in PDS.CMD .............................................................................................................. 301
System Environment Variables ........................................................................................................... 305
PDS2D Environment Variables ........................................................................................................... 307
FrameWorks Plus Environment Variables .......................................................................................... 309
Index ......................................................................................................................................................... 313

Contents

Preface PDS
This document provides command reference information and procedural instructions for the
Plant Design System Project Setup Technical Reference 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

Preface PDS
What's New in Project Setup Technical Reference

The following changes have been made to the Project Setup Technical Reference Guide:
Version 2011 (V12)
 Added information about exporting members to a CIS/2 file. See CIM Steel Export
(PD_Shell) (on page 224) for more information. (P1 PB:114364)
 The PDS Batch Mail utility supports the SMTP mail notification method. For more
information, see Configuring the PDS Batch Mail Utility (on page 142). (P2 PB:114147)
 Clarified the scope and allowable length of file names when using the
$ENV{'NO_TRUNCATE'}='YES' PDS_Shell environment variable. For more information, see
Commands Set in PDS.CMD (on page 301). (P4 PB: 114627)
 Clarified support for Oracle 11g Release 2 database servers. For more information, see
Server Hardware and Software Requirements (on page 15).
 Material Data Publisher supports variable PDS_HVAC_SCHEMA_NAME to define the
PEHVAC project schema in cases where the HVAC project schema name and the PDS
project schema name are different. For more information, see System Environment
Variables (on page 305). (P3 PB:119401)

SECTION 1
Introduction
This document describes the procedure to create a PDS project using PD_Shell; however, an
alternate method exists. Express Project Creation is a tool provided with PDS versions 6.0 and
higher that runs in one of two modes---New User or Advanced User. New User mode asks a
minimal number of questions and forces the project to be located on a single node. Advanced
User mode is driven by an ASCII file that you can edit to suit your needs and used repeatedly.
Express Project Creation is described in the PDS Express Project Creation Quick Start Guide.
Project creation through PD_Shell is useful if you want to add a discipline to an existing project
(for example, add an EE Raceway project or insert an existing FrameWorks project).
Even if you use Express Project Creation, there are many important principles addressed in this
document (Windows O/S domains and groups, plotting setup, and so on) that are not described
in the PDS Express Project Creation Quick Start Guide. For this reason, this document is
suggested reading for all PDS project and system administrators.
This document describes the definition of project data and creation of project files including
database files, design files, and seed files. It is specifically designed to support the creation and
revision of project data for use by other PDS modules.
 System and project setup is typically done by a system manager because the procedure
requires the use of privileged logins. However, the system administrator needs to consult
with the PDS project manager since certain design choices can be made only at project
creation time.
 Other post-creation tasks can be accomplished by other non-administrator users. The
normal operation of PDS does not require administrative privileges.
The instructions in this document are not oriented towards a particular database engine.
Instructions for the installation of some database engines are contained in the appendices. For
assistance installing databases not discussed in the appendices, please see the Intergraph
World Wide Web page (http://www.intergraph.com), or contact Database Support at the
Intergraph Help Desk.
See Also
Concepts and Terminology (on page 13)

Introduction

SECTION 2
Concepts and Terminology

The PDS products use interactive graphics and a relational database to integrate the
engineering and design of a physical plant.
A project and all of its accompanying files must be defined before you can use any of the PDS
modules.
Before work can begin on a project, extensive system setup needs to be completed. The
following diagram outlines the basic flow for initial system setup and project creation.
This document discusses each step in the above diagram.

Concepts and Terminology

SECTION 3
PDS System Requirements

Before beginning an installation of Plant Design System (PDS), you need to verify that your
servers and end-user workstation computer(s) meet specific hardware recommendations and
software requirements.
In This Section
Server Hardware and Software Requirements .............................. 15
Workstation (Client) Hardware and Software Requirements ......... 16
Server Hardware and Software Requirements

Hardware Recommendations
 3 GHz Pentium 4 or multi-core processor (64-bit for medium and large projects)
 4 GB to 32 GB RAM depending on project size
 Digital tape or DVD backup system for server
 Access to DVD drive, either locally or through a network connection
 100 BaseT or higher network interface
Supported Operating Systems - Servers

 Microsoft Windows Standard/Enterprise Server 2003 SP2 (32-bit)
 Microsoft Windows Standard/Enterprise Server 2003 SP2 (64-bit)
 Microsoft Windows Standard/Enterprise Server 2003 R2 SP2 (32-bit and 64-bit)
 Microsoft Windows Standard/Enterprise Server 2008 R2 (32-bit and 64-bit)
Supported Database Servers

 Oracle 10g Release 2 (10.2.0.4) (32-bit and 64-bit servers, 32-bit client)
 Oracle 11g (11.0.0.0) (32-bit and 64-bit servers, 32-bit client)
 Oracle 11g Release 2 (11.2.0.2) (64-bit servers, 32-bit client)
 Microsoft SQL Server 2005 SP2 (32-bit and 64-bit servers)
 Microsoft SQL Server 2008 (32-bit and 64-bit servers)
 Microsoft SQL Server 2008 R2 (32-bit and 64-bit servers)
Software Prerequisites
 Adobe Reader (Required to view the Software License Agreement and software
documentation.)
 MicroStation J 07.01.05.03 (Must use the Complete setup type.)
 PARNU 05.02.00.37
 Batch Services 06.01.00.00 or higher
 IPLOT Organizer (with Microstation J support)
 IPLOTSRV (IPlot Server)

 RIS Shared Component (Client) 06.01.00.02

 RISMSFDS 06.00.00.00 (for SQL Server 2005 or 2008)
 RISORADS 06.00.00.03 (for Oracle 10g 32-bit or 64-bit)
 RISORADS 06.01.00.02 (for Oracle 11g and 11.2g 32-bit or 64-bit)
 SmartPlant License Manager 11.00.17.00 or higher
 SmartPlant P&ID (only required on systems that will be used for SmartPlant P&ID data
transfer.)
 SmartPlant Engineering Manager (only required on systems that will be used for SmartPlant
P&ID data transfer.)
Consult the Compatibility Matrix on the eCustomer website (under Downloads) to
determine the appropriate versions of SmartPlant P&ID and SmartPlant Engineering Manager
and any changes since this publication date.
Workstation (Client) Hardware and Software

Requirements
Hardware Recommendations
 3 GHz Pentium 4 processor or Core 2 Duo
 2 GB RAM
 Access to a DVD drive, either locally or through a network connection
 21" color monitor (capable of a minimum of 1024 x 768)
 Graphics cards designed for 3D intensive applications that meet the following requirements:
 Color depth of 65,536 colors or higher
 32-bit main RGBA pixel buffer
 Hardware OpenGL 1.1 support
 Hardware Z buffer: 32 bit
 128 MB RAM for single screens, 256 MB RAM for dual screens
 4-bit minimum overlay buffer support
 8-bit stencil buffer
 Hardware Alpha blending support
 Graphics acceleration set to full
 Hardware Anti-aliasing support recommended
 Latest available drivers should be installed
 100 BaseT network interface
Supported Operating Systems - Clients

 Microsoft Windows XP Professional SP3 (32-bit and 64-bit)
 Microsoft Windows 7 Professional or Enterprise with UAC 'On' at Level 3 (Default) (32-bit
and 64-bit)
Supported Database Clients

 Oracle 10g Release 2 (10.2.0.4) (32-bit client)
 Oracle 11g (11.0.0.0) (32-bit client)
 Oracle 11g Release 2 (11.2.0.2) (32-bit client)

 Adobe Reader (Required to view the Software License Agreement and software
documentation.)
 MicroStation J 07.01.05.03 (Must use the Complete setup type.)
 PARNU 05.02.00.37
 Batch Services 06.01.00.00 or higher
 IPLOT Organizer (with Microstation J support)
 IPLOTSRV (IPlot Server)
 RIS Shared Component (Client) 6.1.0.2
 SmartPlant License Manager 11.00.17.00 or higher
 SmartPlant P&ID 2007 or 2009 (only required on systems that will be used for SmartPlant
 SmartPlant Engineering Manager (only required on systems that will be used for SmartPlant
Consult the Compatibility Matrix on the eCustomer website to determine the appropriate
versions of SmartPlant P&ID and SmartPlant Engineering Manager and any changes since this
publication date.


SECTION 4
System Configuration
PDS can run on a stand-alone workstation or in a client-server environment. On a stand-alone
workstation, PDS, the Relational Database Management System (RDBMS), and plotting
software must all be loaded on a local disk. This requires a workstation with substantial
resources (disk, memory, CPU). In a typical PDS project, many users will be working with the
plant data. In addition, these users may be performing different tasks at the same time (2D
schematics, 3D modeling, isometric extraction, report generation, and so on). For this reason,
most projects are set up in a client-server environment.
In a client-server environment, each client machine accesses the resources it needs from
remote servers. These resources can fall into a number of different categories.
Data Execution Prevention (DEP) must be enabled. To check the status of DEP on
a machine, follow these steps:
Windows XP
1. Click Start > Control Panel > Performance and Maintenance > System.
2. Click the Advanced tab on the System dialog box.
3. In the System Startup area, click Edit.
4. In Notepad, find the text /noexecute=optin. Optin is the default setting for DEP and
indicates that it is enabled.
If you see /noexecute=alwaysoff, DEP is disabled. Replace alwaysoff with optin.
Windows 7
1. Click Start > All Programs > Accessories > Command Prompt.
2. In Command Prompt, type wmic OS Get DataExecutionPrevention_SupportPolicy and
press Enter.
3. The returned value is either 0, 1, 2, or 3.
a. A value of 0 indicates that DEP is disabled.
b. A value of 1 indicates that DEP is enabled for all processes.
c. A value of 2 indicates that DEP is set to OptIn.
d. A value of 3 indicates that DEP is set to OptOut and is enabled for all processes.
If the value is 0 (DEP is disabled), enter the following text in the Command Prompt
window to enable it: bcdedit.exe /set {current} nx OptIn.
See Also
Server Functional Descriptions (on page 20)
Server Requirements (on page 21)

File Server
A file server stores the project files associated with a PDS project. This includes seed files,
reference libraries, report format files, the actual 2D and 3D model files, and many other
associated support files. By storing all such files on a dedicated server, backups are made
easier and centralized access control can be established. A file server should have a large
amount of disk space, a tape backup device, and a high-speed networking subsystem.
Database Server
A database server stores the RDBMS used by the PDS software. Its requirements are similar to
those of the file server. Many users choose to use a single machine as the file and database
server for small-to-medium sized projects.
Software Server
Intergraph recommends that, for optimal performance, client machines be provided with
sufficient disk space such that all frequently used applications can be loaded locally. However,
infrequently used applications can be loaded in client mode. In this configuration, the client
machine mounts a disk from the software server and runs the software over the network. This
can place a significant load on the network, so it is not suggested for heavily used applications.
Compute Server
When a large number of jobs are being run that consume significant amounts of CPU time
(hidden line removal, large reports, isometric extractions, clash detection, and so on), it can be
advantageous to set up a compute server. In this configuration, the client workstations
reconfigure their local batch queues to be pipe queues that point to the compute server. When
batch jobs are submitted by the clients, they are redirected to the compute server, which
performs the calculations and returns output to the client.
Plot Server
Depending on the number of plotting devices in use, the number of plots being produced, and
the size and type of the plots, it can be advantageous to set up a plot server. This machine has
all I/O cards required to interface with the plotting devices, all server plotting software, and
sufficient memory to cache certain kinds of plots (typically large raster plots).
PDS License Server

When you purchase or lease PDS, you are provided a key that provides you with a number of
PDS licenses. Licenses are graded by functionality---3D, 2D, PID, and IDM. A PDS key contains
encoded information that tells the system how many of each kind of license you have and when
they expire. SmartPlant License Manager distributes these licenses as requested by the clients.
It keeps track of how many licenses of which type have been given out and how many remain in
the pool. If all licenses of a particular type are checked out, a new interactive request will fail
immediately while a batch job will be placed into a wait state.
Acting as a PDS license server places very little load on the selected node---its choice should be
based on it having a stable TCP/IP address (keys are installable only on a node having a
specific address) and its accessibility to the system administrator.
PDS is flexible in that these servers can be configured and decommissioned during the course
of a single project. Not all functions require a separate server in all circumstances. Multiple
server functions can be consolidated on a single machine. Specific recommendations as to what
functions need to be relocated to separate servers is beyond the scope of this book. It is to your

advantage to have a knowledgeable system administrator on staff who can monitor overall
system performance and identify trends in system usage that will point out when a particular
server is reaching the limits of its resources.
Server Requirements
File Server
We recommend that the file server run a Windows Server operating system. Clients computers
can access remote files using the networking software that comes delivered with Windows.
There is no reason why a computer running a non-server version of Windows cannot function as
a server, but there are restrictions that can limit its usefulness (for example, a maximum of 10
mounts per share).
Database Server
PDS accesses the database using the Relational Interface System (RIS). RIS allows a single
version of PDS to work with databases from various vendors in a manner that is transparent to
the PDS software. In the majority of installations, TCP/IP is the preferred communication
protocol. Other supported protocols include the DECnet protocol (DNP) and the Xerox
Networking System (XNS).
RIS is a client-server package; client machines running PDS access the database through the
RIS Client software (loaded on the client), which then communicates with the database through
a RIS data server (typically resident on the database server). The RIS client software comes
with PDS (RIS Shared Component, as seen in the PDS Component Loader). If the database
resides on a server running an operating system that is not supported by RIS, the option exists
to have the RIS client and server modules located on the client machine, and then access the
database through the database vendor's networking tools. This allows the database server to be
any machine supported by the database vendor. See Relational Interface System (RIS) (on
page 37), for a detailed description.
In addition, the database server needs to have a high-speed disk subsystem (to access data
efficiently) and a high-speed networking subsystem (to retrieve and send data to the network).
Modern servers are designed for these purposes, incorporating RAID (Redundant Array of
Independent Disks) technology and multiple networking cards as part of the basic design.
However, even the fastest server will be crippled if the physical network is not up to the task.
Software Server
A software server's requirements are identical to those of the file server. If the PDS software is
loaded in client mode, it will need to access the same software loaded in server mode using
LAN manager. The software server must have sufficient disk space to load all required PDS
products.

Compute Server
A compute server should have a powerful CPU (typically more than one) and a large amount of
main memory to allow it to complete its tasks without having to resort to swapping (where the
unused portion of a program, and/or the files it is accessing are temporarily stored on hard disk).
Because the compute server must run the PDS software, it must run a supported version of
Windows.
Often, the compute server will mount required resources from the file server. This will require
LAN Manager. It will also need to access the database through RIS. It will need to have Batch
Services loaded so client nodes can pipe batch jobs to the server.
Plot Server
The InterPlot product suite is a comprehensive plotting production system that supports a large
variety of plotters. InterPlot is designed on a client-server model, similar to RIS. Client
computers running PDS submit plots through the IPLOT client, which communicates with the
plotter through the IPLOT server software. In addition to the IPLOT server software, the plot
server may require an IPLOT metafile interpreter to deal with the specific characteristics of a
particular plotter. Plots are typically submitted across the network using TCP/IP or XNS. In
addition to the IPLOT software, Batch Services may be required on the plot server. See System
Administrator Responsibilities (on page 131) for a detailed description.
SmartPlant License Manager Server

Functioning as a SmartPlant License Manager license server places little load on the selected
computer. However, the computer must have a stable TCP/IP address and run a supported
version of Windows.

SECTION 5
Quick Installation Guide for Windows 7

This section describes the procedure for installing and configuring PDS on a Windows 7
computer that includes User Access Control (UAC).
For more information, see the Software Prerequisites section in Server Hardware and
Software Requirements (on page 15).
Computer Preparation
1. Log in as an administrator with local administration permissions.
2. Create a temporary folder on the C:\ drive, such as C:\temp. Ensure the folder security
allows users to write, read and execute. This should include the Intergraph Batch Manager
account.
3. Create a share for the temporary folder with the same permissions described in the previous
step.
4. Create the following folder structure: C:\win32app\ingr\share\.
5. Enable Remote Registry service, this service is not on by default in Windows 7.
If the Remote Registry service is not running, some of the batch processes
might fail.
Enabling Remote Registry service

To enable Remote Registry you should be a member of the local administration
group or its equivalent on the remote computer.
1. Select Start > Control Panel > Administrative tools > Services.
2. In the console pane, look for Remote Registry. Right-click on Remote Registry, and then
select Properties.
3. Set Startup Type to Automatic.
4. Click Start.
5. Click OK.
Registry Modification
Use extreme caution when modifying the registry. If you are unsure of what steps to
take, please contact Intergraph Support.
1. Start the Registry Editor (regedit.exe).
2. Locate the HKEY_LOCAL_MACHINE\SOFTWARE folder and create an Intergraph folder
by selecting Edit > New > Key.
For 64-bit operating systems, add the new key in the
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node folder.
3. Create a string value named Common in the Intergraph key with a value of
C:\win32app\ingr\share.

4. Add a new DWORD (32-bit) Value (Edit > New) named DisableUNCCheck with a value of
1 to the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Command Process key.
Choose the 32-bit DWORD type regardless of your operating system architecture.
5. Locate the
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurePipeServers\WINRE
G folder
There are three methods for modifying this key:
 Add the shared folders on the server to the allowed paths in the WINREG key. To add
all allowed paths, enter System\CurrentControlSet\Services\LanManServer\Shares
as the value for the AllowedPaths key in the WINREG folder.
 Grant access permission to the users or user groups from within the Registry Editor
from the Edit > Permissions command.
 Delete the WINREG key.
Installation
1. Install SmartPlant License Manager.
After installation, and in order to use a license to run PDS applications, you must run
SPLM as an administrator by right-clicking the start menu item and selecting Run as
administrator. Click Yes on the User Access Control dialog box.
2. Configure SmartPlant License Manager to point to the license computer. Do this in
SmartPlant License Manager by selecting Configure and Test > Select License Machine
for Client.
3. Perform a complete installation of Microstation J.
4. Install RIS Client. After installation, you must configure the RIS Client.
a. Select Start > All Programs > RIS > RIS Schema Manager.
b. Click Schema File, and select Show Schema File Location.
c. Click Locate Schema File.
d. Type the path of the schema file and filename in the Schema File Name field.
e. Click OK.
5. Install Intergraph Batch Manager.
6. Install PDS Applications. After installation, you must locate the pds.cmd file and configure
the batch queues.
a. Log in as an administrator.
b. Select Start > All Programs > PD_Shell > PDS Configure. Select Yes on the User
Access Control dialog box.
c. Locate the pds.cmd file with the Browse command.
d. Select Local Machine in the Update Registry Entry for section. This will setup the
location of the cmd file for anyone that has not already chosen to point the registry entry
to their “Current User” profile in the registry. Note that Current User entries override the
Local Machine entries for pointing to the pds.cmd file.
e. Click OK.
f. Select Start > All Programs > PD_Shell > PDS Queue as an administrator.
g. Select Yes on the User Access Control dialog box.

h. Configure your queues.
 If you are not an administrator on the computer, the queue creation process fails.
 If PDS2D was installed on the computer, the path variable in Environment Variables
must have the PDS path variable before the PDS2D variable.


SECTION 6
Loading and Configuring Software

This section describes the loading and configuration of specific software products. Both client
and server nodes are covered. The various products are covered in a bottom-up approach, with
the lowest level products described first.
Many computers have the D drive assigned to be a CDROM. If you are using a server where the
D drive is not a CDROM and plan to access the project from client nodes where the D drive is a
CDROM, you may encounter problems. If you plan to create projects on the D drive, verify that
no client nodes have the D drive assigned to be a CDROM. You can reassign drive letters so
that the CDROM on a client node is assigned to a letter other than D. You should make the
reassignment before you load software on that client node.
Operating Systems and Related Components

This section describes specifics regarding the configuration of the operating system. The
description is limited to Windows and Windows Server.
File Systems (on page 27)
Client Nodes (on page 27)
Server Nodes (on page 28)
File Systems
Windows support a number of file systems --- FAT, NTFS, and HPFS. A full description of the
differences can be found in the documentation that accompanies Windows. Comments on each
are listed below.
 Intergraph recommends that NTFS be used on all nodes. It offers a more robust file
recovery/corruption checking scheme as well as complete Windows security.
 Under Windows, FAT now includes support for long file names. Some limited testing of PDS
using FAT file systems has been done, but since FAT offers very little security (only on
shares) it is not recommended for use with PDS.
 PDS has not been tested using HPFS.
Client Nodes
All client nodes that will run PDS must have TCP/IP loaded. In Server Nodes (on page 28),
many other networking services are described - but at minimum, TCP/IP must be installed.
TCP/IP is essential for the operation of the PDS Licensing software and RIS.

Server Nodes
Any computer running Windows can, in a limited manner, function as a server. There are
limitations on the maximum number of client computers that can mount a share (10-users), and
also many of the advanced networking functions require at least one node on the network to run
Windows Server.
RAID
Servers can come with built-in support for hardware RAID (Redundant Array of Independent
Disks). RAID provides two primary benefits.
1. Performance---Data can be striped across drives, boosting performance of read operations.
2. Reliability---Certain RAID configurations offer protection from data loss due to disk failure.
If your server came with the operating system preloaded, then a RAID configuration of some
type has already been set up.
Before loading additional software and configuring network services, be sure to
examine the RAID configuration to determine its suitability for the system's intended use. If
changes to the RAID subsystem are required, the operating system and all software
components will have to be reloaded after reconfiguring RAID.
See RAID Configuration (on page 159), for a technical overview of RAID.
User Accounts
A Windows domain is a collection of computers that share a common user account database.
This allows all computers in the domain to be treated as a single unit for management of user
and group accounts. It provides a benefit to users when they browse the network for available
resources (since nodes are grouped by domains), and it makes it easier for system
administrators to manage the network. We recommend that a Windows domain be created and
that domain accounts be used. Additional information about planning, creating, and
administering domains can be found in the Windows documentation.
Use of Dynamic Host Control Protocol

Windows Server includes Dynamic Host Control Protocol, which allows assignment of internet
(TCP/IP) addresses to clients on demand. To run PDS in a DHCP-enabled network, the address
of all servers need to be fixed---particularly those of the database server and the licensing
server. The DHCP server must run Windows Server. Additional information on DHCP can be
found in the Windows Server Books Online.
Creation of a Windows Naming Service Server

It is also suggested that a Windows Naming Service server (WINS server) be created. A WINS
server maintains a database of the names of all network nodes. This allows nodes to browse
domains across a router and greatly reduces Internet Protocol (IP) broadcast traffic on the
network.
Data Execution Prevention Setting

Make sure the system Data Execution Prevention (DEP) setting is set to Turn on DEP for
essential windows programs and services only.
From a system running Windows XP:
1. Right-click on My Computer in the Start menu.
2. Select Properties.

3. Click the Advanced tab. In the Performance section, click Settings.
4. Click the Data Execution Prevention tab and check the setting.
5. Apply your changes and exit the Performance Options dialog box.
6. Click OK to exit the System Properties dialog box.
From a system running Windows 7/Server 2008, or later:
1. Right-click on Computer in the Start menu.
2. Select Properties.
3. Under Tasks, click Advanced system settings.
4. In the Performance section, click Settings.
5. Click the Data Execution Prevention tab and check the setting.
6. Apply your changes and exit the Performance Options dialog box.
7. Click OK to exit the System Properties dialog box.

Software Required for File Sharing

Protocols Provided with Windows
Microsoft provides the protocol listed below for use with Windows/Windows Server.
TCP/IP - Transmission Control Protocol/Internet Protocol (TCP/IP) has been around since the
1970s, and its primary advantage is that it provides communications across interconnected
networks where different operating systems may be in use. When NetBEUI and TCP/IP are both
installed on each node and NetBEUI has been set to be the first protocol used, Windows uses
NetBEUI for communications between nodes on the same LAN and TCP/IP for communications
across routers.
Additional information on this protocol can be found in the Windows Server Concepts and
Planning Guide.
PDS and Windows

Before you start loading applications, be sure to read, understand, and follow the information
provided in PDS and Windows (on page 293).
Software Compatibility
Download the PDS compatibility matrix (a Microsoft Excel spreadsheet) from the Intergraph
Knowledge Base (www.intergraph.com) for information on compatibility of PDS products with
MicroStation, Windows, databases, and other supporting products.
Software Required for Batch Processing

PDS accomplishes many tasks by the use of batch processes (create model, archive project,
extract iso, and so on). The benefits of using batch processes are:
 Batch processes run in the background---allowing the client node to continue with productive
work.
 Batch processes can be scheduled to run at a set time.
 Batch processes can be re-directed (piped) to another node that may have more suitable
resources to complete the required task.
Batch Services (SSBY734) allows PDS to run batch jobs. Batch Services must be loaded on
each machine that will run PDS. Batch Services is delivered on the PDS CD-ROM.
When Batch Services is loaded on a Windows node, there are two prompts in particular to pay
attention to. The first is: Do you want jobs to have access to the desktop? If you accept this
option, the currently running batch job will result in a collapsed DOS window being shown at the
bottom of the monitor. It is recommended that you accept this option when available, because it
is a prerequisite for the PDS batch mail utility when sending mail through MAPI, which will mail
you the log file (with possible error messages) from batch jobs. The newer SMTP mail interface
provides support for security limitations. For more information, see Preparing for Project
Creation (on page 41). The second is: Do you want all jobs to run as the same user? It is
recommended that you decline this option and establish account mappings later. See Preparing
for Project Creation (on page 41), for more information.
When loading the batch processing software, make sure you:
 Load the software into ~\win32app\ingr.
 Allow batch jobs to have access to the desktop.

 When finished loading software, check the PATH variable (in Control Panel > System) to
check for quotes (") in the system PATH. If you find that the batch processing software has
added quotes, either move the directory paths with the quotes to the end of the PATH
statement or remove the quote marks (if the directory path does not contain spaces). PDS
path statements must appear before path statements with quotation marks.
If you are running Windows 7, you cannot interact with the desktop during the Batch
Services installation process. Batch Running Script (BatchRunning.zip) is a utility that monitors
and reports the installation progress in your Taskbar.
Core Graphics Software

All software described in this section should be loaded before any PDS products are
loaded. Loading core products after PDS products have been loaded can lead to problems. If
you need to reload a core product after you have loaded PDS, you should reload PDS. If you
reload MicroStation, you must reload PD_Shell and IPLOT Client to ensure that you have the
correct user preference file.
MicroStation - All client nodes that run PDS should have MicroStation loaded. See the
README file or the compatibility matrix for more information on the versions of MicroStation that
are supported with that version of PDS.
SmartSketch® - Any client nodes that will generate Pipe Support drawings or perform data
transfer from SmartPlant® P&ID should have SmartSketch® loaded.
Software Required for Plotting

At a minimum, all client nodes must have IPLOT client installed if they want to print from that
client node. In addition, IPLOT server and the required metafile interpreter must be loaded on
servers that support directly-connected printers.
In many cases, the client computers will also need to have IPLOT server installed because
when you connect to printers using Connect to Printer, the connection that is made is a
temporary connection that is usable only by the currently logged-in user. The more useful printer
connection is made using Create printer, and to do this the computer must have IPLOT server
loaded.
After a single computer has established a connection to a printer using Create printer, other
client computers can submit plots to this same printer using this client as a gateway.
When loading plotting software, make sure you:
 Load the software into ~\win32app\ingr.
 When finished loading software, check the PATH variable (in Control Panel > System) to
check for quotes (") in the directory paths. If you find that the plotting software has added
quotes, either move the directory paths with the quotes to the end of the PATH statement or
remove the quote marks (if the directory path does not contain spaces). PDS path
statements must appear before path statements with quotation marks.
See System Administrator Responsibilities (on page 131) for more information regarding plotting
configuration.

Database Software
All client computers must have the RIS client software installed to access the database. The
database server will also need to have the RIS data server for the database in use. See
Relational Interface System (RIS) (on page 37), for more information.
In certain situations, depending on which products have been loaded, you may find
that multiple versions of the RIS client software exist on a particular computer. We suggest that
the Configure RIS version utility be used to remove older versions of the RIS client software.
Having multiple versions of the RIS client software loaded can lead to problems.
The database software must also be installed on the server. In most cases installing the
database is a two-part procedure:
1. Installation of the actual database product (which typically takes you through a procedure
where disk space is set aside, administrative users are created, backup devices are
designated, and so on).
2. Creation of individual databases for use by a particular PDS project. These steps are
described for a number of database products in the appendices.
For assistance with a database not covered in the appendix, consult Intergraph's web page
(http://www.intergraph.com), or contact the Database Support at the Intergraph Help Desk.
MDAC
Any client computers that will perform drawing resymbolization or data transfer from SmartPlant
P&ID should have the Microsoft Data Access Components (MDAC) loaded.
Oracle Client
If Oracle is being used as the relational database for the SmartPlant P&ID project, any client
nodes that will perform data transfer from SmartPlant P&ID should have Oracle client loaded.
PDS Products, Client Nodes

1. Log in to the computer as a domain user with local administrator rights.
2. Perform pre-installation tasks, "PDS and Windows (on page 293)" and "PDS Environment
Variables (on page 301)" 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.

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.

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 (on page 297) for more information.

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.

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.
PDS Products, Server Nodes

PDS products must be loaded to the server node if it is being used by clients having the same
products loaded in client mode, or if the server is being used to process redirected batch jobs.
If the server is used only for redirected batch jobs, then the required products can be loaded
local on the server. If the server is used for redirected batch jobs and also by client nodes
having the software loaded client mode, then the products can be loaded local on the server. If
the server is used only for clients having the software loaded client mode, then the products can
be loaded server mode on the server.
Also note that if a server is used for processing redirected batch jobs, it must also have
SmartPlant License Manager loaded and have access to a valid license server. See Preparing
for Project Creation (on page 41), for more information. If the server is used as a SmartPlant
License Manager license server, then it will have a SmartPlant License Manager key installed as
well.
As an example, the following products would have to be loaded on a server that is processing
batch isometric extractions and plotting them:
 PD_ISO
 PD_ISOGEN
 SmartPlant License Manager
 Batch Services
 MicroStation
 InterPlot Client (also InterPlot Server if printing to a network printer)
 RIS client
Note also that any redirected batch job which involves initializing a design file will require
MicroStation to be loaded on the computing server. An example of this is a PD Clash
interference check - the marker file must be opened by MicroStation as part of the batch job.
If the server is only a file server and/or database server, then MicroStation would not be
required.

SECTION 7
Relational Interface System (RIS)

The on-line RIS SQL Reference manual provides a detailed overview of RIS. This chapter
provides a brief summary.
In This Section
Why RIS? ....................................................................................... 37
How RIS Communicates with the Database.................................. 37
Database Structure ........................................................................ 38
3D Schemas .................................................................................. 39
2D Schemas .................................................................................. 40
Why RIS?
When Intergraph first developed applications that used databases, those applications were hard
wired to a particular database type. To support the use of a different database type, another
version of the application software would have to be written. A methodology was required such
that a single version of an application could interface with multiple database types---the solution
to this problem is RIS.
RIS decouples the database from the application. By doing so it allows multiple client nodes to
share a single copy of the database. RIS includes the networking software to access the remote
database, saving you money by not requiring the use of the database vendor's networking
software.
How RIS Communicates with the Database

The following diagram shows a complete RIS connection:
A RIS-enabled application (such as PDS) issues commands to the RIS client software. Typically
the RIS client software that is used is that loaded on the local machine; however, RIS supports a
locate client function that allows RIS to use the client software located on another node.
The use of the RIS locate client operation can lead to problems unless it has been
recommended by Intergraph Support.
The RIS client software reads the parms file that resides in the RIS product directory on the local
node. The parms file tells RIS where to find the schemas file. The schemas file can reside on
the local node or on a server, and contains a list of all accessible databases on the network.
Having found the information required to locate the database from the schemas file, RIS
establishes a connection to the database via the RIS data server. The RIS client issues
database-independent requests for information, and the RIS data server translates these into
database-specific requests for information.

In fact, RIS locates databases in a manner similar to how PDS locates projects.
The schemas file and the proj file serve similar functions---they allow the client application to
resolve a name into a location. The client application uses these files to locate projects and
databases anywhere on the network. Projects and databases can be located on multiple server
nodes, yet all can be listed in a single proj file/schemas file.
Database Structure
All databases have certain features in common. A database consists of tables, columns, and
rows.
Tables may be broken into 3 types:
Database Dictionary Tables

These are tables that the database uses for its own administration. They include things such as
where all of the files that comprise the database are located and lists of all database user
names. In some cases, a subset of the database dictionary tables may be included with each
user database.
RIS Dictionary Tables

The RIS dictionary tables are used by RIS and contain information that RIS needs to
communicate with PDS.
PDS Application Tables

The PDS application tables contain real data of use to PDS, such as pipeline, unit, and clash
information.
When creating a new PDS project, a number of schemas must be created.

A schema is a unique database/username combination. The schema is a way of mapping a

name to a database. When a schema is created, the database type, address, and username
must be identified. Then, PDS can refer to the database by specifying only its name.
When you create a schema for a database from within PDS, you must first complete the
information in the Create Schema form. After accepting this form, PDS issues a command to
RIS to create a schema for the specified database. RIS connects to the specified database and
creates all of the RIS dictionary tables. After completing this, PDS then connects to the same
database and creates the PDS application tables for that particular database type.
Information about creating schemas for a number of different databases is provided in the
appendices. For assistance with a database not covered in the appendices, consult Intergraph's
World Wide Web page (http://www.intergraph.com), or contact the Intergraph Help Desk.
Oracle, SQL Server, and RIS Schemas

Oracle and SQL Server both maintain a list of usernames that is different from that maintained
by the operating system. For this reason, a unique database username is created for each
schema.
Schema Database Database Username

Name Name
pd_proj1 pds pd_proj1

dd_proj1 pds dd_proj1
ra_proj1 pds ra_proj1
3D Schemas
PD - Project control schema. Contains the location of the project (3D, 2D, EE, FW) and all
associated reference data
DD - Design schema. Contains information specific to each 3D piping (and optionally
equipment) model.
RA - Approved reference schema. Contains approved reference data.
RU - Unapproved reference schema. Contains unapproved reference data.
EE - EE Raceway project schema. Contains information specific to each EE Raceway model.
RE - EE Raceway reference schema. Contains EE Raceway reference data.
See the Project Administrator (PD_Project) Reference Guide, for a list of the tables and columns
for each of these database schemas.

2D Schemas
PD - Project Control Data. Contains the location of all drawings and the 2D reference data.
PID - P&ID Task Schema. Contains information specific to each 2D PID drawing.
PIDM - P&ID Master Schema. Contains information posted from the PID schema.
PFD - PFD Task Schema. Contains information specific to each 2D PFD drawing.
PFDM - PFD Master Schema. Contains information posted from the PFD schema.
IN -- IDM Task Schema. Contains information specific to each 2D Instrument and associated
devices.
INM -- DM Master Schema. Contains information posted from the IN schema.
INR - IDM Reference Schema. Contains IDM reference data.
In addition to these schemas, there can be a backup schema for each of the schemas
listed above (PDBK, PIDBK, and so forth). The backup schemas can be used when retrieving
2D data from archives.

SECTION 8
Preparing for Project Creation

Additional preparations that must be made before creating a project are discussed in this
section. Some are one-time tasks, and others need to be done before any new project is
created.
In This Section
Establishing Domain Users and Groups ........................................ 41
Location of the proj File ................................................................. 41
Location of schemas File ............................................................... 49
Creating Batch Queues ................................................................. 52
Establishing Account Mapping....................................................... 53
Creating Project Directories and Required Shares ....................... 54
Files Reside on a Windows Server ................................................ 56
Establishing Domain Users and Groups

Generally, the Domain or System Administrator creates the domain users and groups for PDS
via the operating system. The PDS Administrator must work closely with the Domain
Administrator to ensure that PDS users are configured with the proper group assignments, as
well as the proper security and share permissions, to enable access to model files and reference
data files. If this is not done correctly, users may have problems accessing that data.
The PDS Administrator needs an understanding of how users and groups function in the
supported operating system. It is highly recommended that the Administrator reviews the
applicable operating system server documentation, or, if possible, attends a technical training
course for Server Administration.
Location of the proj File

The list of PDS projects is stored in a file named proj_file (also referred to as the proj file). This
file should be located on a server so that all client nodes can refer to a single copy. PDS 2D and
3D applications can share the same proj file. The procedure to do this includes 3 steps:
1. Create a directory for the proj_file on the server.
2. Apply permissions to the parent directory.
3. For PDS versions 7.3 and earlier, share the drive where the parent directory is located. For
PDS 8.0 SE and later, you can share the drive where parent directory is located, or you can
share the parent directory itself.
A directory should be created on the server for storing the proj file. In this example, a directory
c:\projfile is created on the server CADSRV. Security should be set to PDS\administrators---full
control and PDS\domain users---change on this directory.
Prior to version 8.0, PDS required that the root directory for the drive containing the proj file be
shared. Thus, if the proj file was located on the H: drive, it was necessary to share the H: root
directory. For version 8.0, it is only necessary to share the directory in which the proj file resides.
For example, if your PDS installation used the following directory structure:

h:\projects
h:\projects\project1
You could place proj files in the project1, project2, and project3 directories, and then share the
directories with different settings, to allow stricter control of user access by project, rather than
by drive.
See Also
Sharing the proj File Location Through LAN Manager (on page 42)
Default C Drive Permissions (on page 44)
Universal Naming Convention (on page 45)
Sharing the proj file location through LAN Manager

The directory where the proj file is located must also be shared. The directory should be shared
with the default permissions of Everyone/Full Control. Although it is possible to grant
permissions on the share, we suggest that the primary means of securing files be the file and
directory permissions as applied through Explorer.
Windows includes administrative shares for the top-level drives (C$, D$, and so on). These
shares are not usable by non-administrator users. While logged in as an administrator on the
server, select the directory to be shared (for example, c:\pdsadmin), and then right-click and
select Sharing from the right-click menu.

The next dialog box shows a Share Name of <drive>$, where <drive> is a drive letter (C, D, and
so on).
You can add a comment, and then click Permissions to add or remove privileges on the share,
but as discussed earlier, we suggest that permissions be applied to files and directories, not
shares.

Default C Drive Permissions

Most Windows computers are delivered by default the NTFS file systems. The default
permissions on your C drive are:

Note that the local administrators group (JOENS\Administrators) has full control on all files on
the C drive. Adding additional domain users into the local administrators group also grants them
the same privilege. If your server is running Windows Server, these would be the default
permissions:
Universal Naming Convention

When running PDS under Windows, the proj file is accessed differently if MicroStation 5.0 or
MicroStation 5.5 is being used. MicroStation 5.5 (and PDS 6.0) supports the use of the
Universal Naming Convention (UNC). One of the benefits of UNC is that remote files can be
accessed without having to mount the remote resource locally. For example, a file named
test.wri exists on the server CADSRV in the c:\temp directory and the C drive has been shared
with the appropriate permissions. This file can be accessed using Microsoft Write by keying in
write \\cadsrv\c\temp\test. If Windows Explorer is opened and the F5 key pressed (to refresh the
list of mounted resources), you can see that although the file on the server is being accessed,
no visible mount has been made to the server.
PDS 6.0 functions in a similar manner when MicroStation 5.5 is being used---when PD_Shell is
started, the first thing it does is read the proj file to display the list of projects. If Windows
Explorer is started, it shows that no additional mount has been made. Similarly, when models

from a PDS project residing on a Windows-based server are accessed through PDS using
MicroStation 5.5, no mounts are seen through Windows Explorer. The same project, accessed
through PDS using MicroStation 5.0 results in visible mounts being made for the proj file and
models.
Locating the proj File from Client Nodes---PDS 3D

To run the PDS 3D configuration utility, click Start > All Programs > PD_Shell > PDS
Configure , and specify the name and location of the PDS 3D control file, which is named
PDS.CMD. You can point to the delivered PDS.CMD file (the default file is located in the
C:\WIN32APP\INGR\PDSHELL folder), or you can copy and rename this control file to any
folder you want. The PDS.CMD file sets up the working environment and defines configuration
variables within PDS as well as starts the software. For information about what you can set in
the PDS.CMD file, see Commands Set in PDS.CMD (on page 301).
You must have administrator rights on the computer when running PDS Configure
in order for the utility to write the necessary registry entries correctly.
We recommend that you copy the PDS.CMD file to a location outside of the PDS installation
folders. This will prevent your command file from being overwritten if the PDS software is
re-installed, and allows you to use a different control file for each user on the computer.
For example, assume that you are logged in to the computer that is primarily used by Mary as
PDS\mary. Also assume that Mary has a folder c:\users\mary where her personal files are
stored. Other users may log into this computer and work while Mary is gone and would need to
access the pds.cmd file. Assume that another folder named c:\users\pds has been created for
the purpose of storing common files and that PDS\domain users have full control on this folder.
Local Machine - Select this option to save the PDS.CMD file location for everyone who logs
into this computer. All users will use the same PDS.CMD file. To continue the example above,
the PDS.CMD file should be placed in the c:\users\pds folder and the Local Machine option
selected.
Current User - Select this option to save the location of the PDS.CMD file for only yourself (the
username currently logged into the computer). Select this option to allow each user to have a
personal PDS.CMD file with personal settings and configurations. To continue the example

above, Mary would put the PDS.CMD file in her c:\users\mary folder and select the Current
User option.
PDS checks for administrative privileges of the current logged-on user. If you are an
administrator on the computer, both Local Machine and Current User options are available.
PDS reads the current user registry first to populate the data and if no entry for the current user
is found, then the local machine registry is read for data.
If you are logged on as a user without administrative privileges on the computer, you can
only write to the Current User settings. You will receive an error if you try to write to the Local
Machine settings.
If you are not sure of the location of the control file, click Browse to search the folders on your
computer, or on a networked computer, to specify the control file to be used.
In addition to storing the project file, the folder that you specify for the project file also
stores other important files related to PDS project administration. This folder should be backed
up on a regular basis.
All clients should be set up to have their pds.cmd file pointing to the same project file on the
server. The exception, however, is in certain cases where many projects are being managed.
Some system administrators prefer to maintain multiple project files, each listing a number of
related projects.
Click Modify to specify the computer name and the folder on that computer in which the project
file (proj_file) will be created (or where it already exists). If the PDS.CMD file does not exist in
the specified folder, PDS will ask if you want to copy the default PDS.CMD file to the specified
folder. Click Yes to copy the PDS.CMD file. After the file is copied, the Modify PDS 3D Control
File dialog box displays.
PROJ_FILE - Specifies the location of the proj_file on the computer specified by PROJ_ADDR.
The proj_file contains the location of all projects on the network. Be sure to include the closing
slash in the PROJ_FILE field.
PROJ_ADDR - Specifies the computer name and share on that computer that contains the
proj_file. If the proj_file is on a networked computer, type the name of the computer, a back
slash, and then the share name. In the example above, the computer is named "docdata" and
the share is named "d".

Locating the proj File from Client Nodes---PDS 2D

Double-click Set Options in the PDS 2D Applications program group to set the proj file location
for the PDS 2D applications. PDS 2D stores the location of the proj file in the ntparams.dat file
located in the \pds2d\cfg directory. Unlike the pds.cmd file used by PDS 3D, the ntparams.dat
file cannot be moved. This file should be backed up, or its settings should be written down in
case the 2D product is removed or reloaded.
The Networked Delivered Product Data fields are set to the location where PDS 2D is loaded
on the local machine. These fields should not require any changes. However, the Optional
Project Data fields need to be changed. The Database Proj File Path can be set to the same
location as that used by PDS 3D. You can use Browse to set this location, or type it directly into
the field. If you browse to an empty directory, a warning message displays.
If you click Browse, you will notice that separate fields are not provided for the node name and
the path. If you click Network to mount a drive from the server and select the proj file location,
the server will be mounted locally, and the proj file location will be set to the mount point. For
example, if the C drive from the server CADSRV is located through Browse, it is mounted as the
F drive. After selecting the projfile60 directory and clicking OK, the proj file location will be stored
as F:\projfile. For this to work, the server would have to be mounted as the F drive every time
you wanted to start PDS 2D. A better way to specify a remote proj file directory is to use the
Universal Naming Convention (UNC) format. In this example, the location of
\\CADSRV\c\projfile60 could be entered directly into the Database Proj File Path field.
The Graphics Only Project Files Path is set to a location where PDS 2D graphics-only
drawings are stored. The 2D disciplines (2D, PID, PFD, IDM) support the use of drawings that
are graphics only or graphics + database. A drawing created in graphics only mode can be
attached to the database at a later time if required. In this example, a new directory named 2D is

created under the c:\testproj\models directory for storing graphics-only drawings. The location of
graphics-only drawings is not stored in the database, therefore PDS 2D needs an alternate
means of determining where these drawings are stored. This information is stored in a file
named example.gpr which must be copied from the \pds2d\cfg directory into the project
directory. Once copied into the project directory, its name can be changed as long as the
extension remains .gpr. The information in this file must also be updated to match your
installation. An example file (named testprj.gpr) resides in the c:\testprj\project directory.
c:\testprj\2d\pds2d\
c:\testprj\2d\pid\
c:\testprj\2d\pid\forms\
c:\testprj\2d\pid\menus\
c:\testprj\2d\pfd\
c:\testprj\2d\pfd\forms\
c:\testprj\2d\pfd\menus\
c:\testprj\2d\pds2d\
The first seven lines have been modified to specify the reference data copied to the project
directory, and the last line has been modified to specify where new graphics-only drawings will
be created. The location of this file must be entered into the Graphics Only Project Files Path
on the Set Options form. The convention for locating this file across the network is the same as
used with the Database Proj File Path (use UNC path).
Location of schemas File

Just as the proj file points to the locations of all PDS projects, the schemas file points to the
locations of all databases. It is important that all users access the same schemas file (typically
stored on a server) so that all can share the same data. As with the proj file, a directory should
be created on the server for storing this file. In this example, it is named c:\ris. As with the proj
file, the security can be set on this directory to domain users---change and domain
administrators---full control.
The location of the schemas file is set using RIS Schema Manager. This utility is in the RIS
XX.XX (where XX represents the version number) program group. Having multiple versions of
the RIS client software loaded can lead to problems---make sure that you have only one RIS
XX.XX program group. You should have a RIS program group on all nodes where PDS is
loaded. If you load a RIS data server to a node where PDS is loaded, this may result in a newer
RIS client being loaded. In this case, you should remove the older version (using the Configure
RIS Version utility) and try to use the newer version of the RIS client software.
RIS communicates with remote nodes using a communication protocol such as TCP/IP,
XNS, or DNP. TCP/IP is used as an example throughout this document. RIS has no interaction
with file sharing protocols such as LAN manager. Installing or changing the settings of LAN
manager has no effect on the ability of RIS to communicate with a remote database or to access
a schemas file.
When using Windows, you have two options for getting to a schemas file on a server:
 Use TCPIP as the protocol and specify a valid login on the server.
 Specify a Local schemas file, but for the schema file location enter a UNC path that
specifies the location on the server.
Using TCPIP
To use TCPIP as the protocol, you have to install and configure FTP Server on the server node
(this procedure is not required for the clients). For Windows, you need to install Microsoft Peer
Web Server. For Windows Server, you need to install Microsoft Internet Information Server.

1. Click Start > Settings > Control Panel. Double-click on Network, and then select the
Services tab. Click Add.
2. Select Microsoft Peer Web Server on a Windows Workstation system or Microsoft
Internet Information Server on a Windows Server system. Click OK.
3. Enter the location of the Windows distribution media and press ENTER.
4. Click OK on the Welcome form to display a checklist of components which can be loaded.
The only required option is FTP Service. Selecting FTP Service will automatically select
Internet Service Manager as well. Click OK to install the required files into the default
directory.
5. The next form shows the default FTP Publishing Directory. This is the directory a user will
be put into if they establish an FTP session and the user they log in as does not have a
home directory specified. This can be changed to c:\temp. Click OK to install the FTP
Service.
6. You may get the message "The guest account is enabled - do you want to disable guest
access to the FTP service?" Clicking Yes is a prudent choice. The installation is complete
and you can exit out of Control Panel.
7. Click Start > Programs > Microsoft Peer Web Services > Internet Service Manager (on
a Windows) or Start > Programs > Microsoft Internet Server > Internet Service Manager
(on a Windows Server node). You should see an entry for your node and that the service is
running.
8. Double-click on the node name to activate the FTP Service Properties form. Disable Allow
Anonymous Connections (an optional choice - if taken, accept the form warning about
passwords being passed over the network) then select the Directories tab.
9. You should see an "Alias" for the home directory (c:\temp in this example). In this example it
is assumed that the schemas file is located somewhere on the C drive. Click Add. For the
directory, browse to the C drive and click OK. It should enter C: into the Directory box.
Make sure that the "Virtual Directory" button is selected, enter C: for the Alias.
The colon (:) after the drive letter in the alias name is critical! It must be included as
part of the alias name or RIS will find the schemas file but not display the schemas. At the
bottom of the form also make sure that Read and Write have been selected.
10. Click OK on the Directory Properties form. In the FTP Service Properties form you should
see the entry for your drive. Make sure that the colon (:) is included as part of the alias
name. Click OK on the FTP Service Properties form to apply the change. Exit from the
Internet Service Manager form.
11. Test the FTP service by going to another client open a DOS window and type ftp <server
name> to open a connection to the server. Type a valid login on the server, type dir to list
files in the c:\temp directory. Type get filename where filename is some file in the c:\temp
directory. This simply tests the FTP connection.
The username you specify in the Locate Schema File form must also be able to log in
at the FTP prompt as described above.

12. You can now do a Locate Schema File from a client node and specify TCPIP as the
protocol.
In this example, a file named schemas in the c:\ris directory on the server CADSRV has
been specified. The username/password is a login in the PDS domain that has the right to
log on locally on the server. In this example, the generic user pds has been used. All client
nodes should use the same operating system username when locating the schemas file.
When you click Apply, the system writes the location of the schemas file on the server into
the parms file. The schemas file is not created until a schema is created. As with the
proj_file directory, the directory where the schemas file is located should be backed up
regularly.
The Locate Schema File operation should be performed on all client nodes so that they all
refer to the same schemas file on the server. There is an exception to this rule, however. In
certain cases, where many projects are being managed, some system administrators prefer
to maintain multiple schemas files, each listing a number of related projects.
Using UNC path

You can use a UNC path to locate the schema file. Share the directory where the schemas file is
located and on the client node go into the Locate Schema File form. Click Local as the protocol
and for the schema file location type:
\\server\driveletter\dirname\schemas
As an example \\pdssmp1\c:\ris\schemas. FTP Server is not required for this to work.
Some systems have not worked with the colon after the drive letter. In this case, use the
following syntax:
\\pdssmp1\c\ris\schemas
Note however that locating the schemas file in this manner to a Windows Server node uses
Windows licenses (as seen in Control Panel > Licensing under "Windows Server"). Windows
Server is delivered with five user licenses. When user number six tries to access the schemas
file using the UNC path method, they will get an error. Increasing the number of licenses will fix
this problem, but you also cannot violate the terms of your license agreement (you must
purchase additional Client License Packs to legally allow you to have the extra connections). On
Windows Workstation nodes you are limited to 10 connections per share.

Creating Batch Queues

PDS automatically creates batch queues based on which products have been loaded locally or
in client mode. When you enter PD_Shell, it checks to see if all required batch queues exist and
displays a warning if any do not.
Click Create to display the PDS Queue Creation dialog box.
Note that in order to create the queues, you must be logged in as an administrator. In fact, you
need to be logged in as a user having administrator privileges who also has access to the
directory where the proj file is located. This is because the PDS Queue Creation Utility accesses
the queue.lst file, which is located in the same directory where the proj file is located. The
domain administrator meets both requirements - this user is added into the administrators group
of the local node automatically when the node joins the domain, and this user has access to the
share on the server where the proj file is located. In the PDS Queue Creation dialog box,
queues for all products have been selected for creation. By clicking Read Data from Local

Machine, the utility does not read information from the queue.lst file, but instead checks for
batch queues on the local machine. The fact that Remote Node was not selected for any of the
queues means that the created queues are batch rather than pipe queues. Jobs submitted to a
batch queue are processed locally, while jobs submitted to a pipe queue are routed to a remote
server.
When exiting the queue creation utility, you are asked whether or not you want to save the
queue information in the queue.lst file. The queue.lst file is stored in the same directory as the
proj file. The queue.lst file becomes important when redirected batch operations are done. See
System Administrator Responsibilities (on page 131), for a description of how to change from
batch queues to pipe queues.
See Also
Establishing Account Mapping (on page 53)
Establishing Account Mapping

After the required queues have been created, account mapping must be established. When a
batch job is submitted, the process initiates a separate login session from which all required
processes are spawned. The Batch Services account mapping determines which user name is
used. If improperly done, batch jobs fail to complete because of their inability to access the
required queue (the job never appears in the queue) or because of their inability to access the
required resources (the job runs, but errors are seen in the log files).
Account mapping is covered in the Batch Services Quick Start Guide. Some example account
mappings following the example are provided. Note that multiple account mappings can be
established on a single node. If multiple account mappings exist, the system searches them in a
specific order looking for a match. The search order is documented in the Batch Services Quick
Start Guide.
If you change the password on an account to which jobs are mapped, you must also
change that password inside the Batch Manager.
Intergraph PDS Support recommends that the number of account mappings be minimized
through the use of domain accounts to simplify system management.
Map From User Map To User

Account Account
Domain/Host Domain/Host
Example 1 PDS mary PDS mary
Example 2 PDS mary PDS pds
Example 3 PDS * PDS pds
Example 4 * * PDS pds
Comments on these sample account mappings follow. These comments assume that each
example is the only account mapping in use.
1. User mary is mapped to herself. If user mary is the active (logged in) user and she submits
a batch job, this job has access to all system resources that user mary has been granted
access to. If a user other than mary submits a batch job on this node, it fails since no
account mapping for any other username has been set.
2. User mary is mapped to the generic username pds. If user mary is the active user and she
submits a batch job, this job has access to all system resources that user pds has been
granted access to. If a user other than mary submits a batch job on this node, it fails since
no account mapping for any other username has been set.

3. Any user in the PDS domain is mapped to the generic username pds. If the active user is a
member of the PDS domain and submits a batch job, this job has access to all system
resources that user pds has been granted access to. If a user who is not in the PDS domain
submits a batch job on this node, it fails since no account mapping for any other domain has
been set.
4. Any user in any domain is mapped to the generic username pds in the PDS domain. A batch
job submitted by any user (who must have the right to log on locally) has access to all
system resources to which that user pds has been granted access.
The account mapping specified in example (3) is the preferred mapping. All users are mapped
to a common user for the purposes of batch processes. If the user is not logged in to the PDS
domain, then the batch job fails. This forces users to use their domain logins. For this to work,
the PDS\pds user must have access to all files required to complete the batch job. In addition,
the PDS\pds user must have the right to log on locally as specified in User Manager under
Policies > User Rights. If you have granted PDS\domain users the right to log on locally, then
the PDS\pds user need not be added to the list.
There is an exception to this suggested account mapping if batch plots are submitted to
connected plotters, then users will need to be self-mapped. See System Administrator
Responsibilities (on page 131) for more information.
If you are having problems with PDS batch jobs - be sure to check the Event Log. Often
times you can find a message in there that will help you find the problem.
Some system managers might attempt to use Batch Services account mapping as a way to
control access to system resources. This can be done, but often leads to end-user problems
such as the job running correctly when submitted interactively, but not when run in batch mode.
Intergraph PDS Support recommends that Batch Services account mappings be minimally
restrictive, and that access control to system resources be accomplished using Windows file
permissions and PDS Access Control.
If problems are encountered while performing PDS batch jobs, the associated log file(s) should
be checked. See Log Files Produced by PDS Batch Jobs (on page 179), for a listing of the log
file(s) produced by each PDS batch job.
Creating Project Directories and Required Shares

It is highly recommended that domain users and groups be used by regular designers as well as
those who create projects. See Domain Groups (on page 54), for more information. You might
think that the domain user name used to create projects should also be a member of the
administrators group. However, when a file is created by a user who is in the administrators
group, that file is owned by the administrator user. This can cause problems when
non-administrator users try to access the files. A domain user should be created for this
purpose, and that user should be specifically excluded from the administrators group. In this
example, the generic user pds is used.
See Also
Files Reside on a Windows Server (on page 56)
Domain Groups
A domain and domain user names have been created for use by all PDS users. In addition,
multiple users can be assigned to a group, so that access to resources can be granted to many
users at one time. Consider a continuation of the previous example:

PDS User Domain User Domain Group

name
Al PDS\al PDS\administrator
Jane PDS\jane PDS\designer
Bob PDS\bob PDS\designer
Mary PDS\mary PDS\designer, PDS\administrator
Janice PDS\janice PDS\users
pds PDS\pds PDS\users
Domain user names are created while logged on as administrator on the domain controller. User
groups can be created in a similar manner from within User Manager. From the User Manager
main menu, click User, then New Global Group. (For a description of the differences between
local groups and global groups, see the Windows NTS Concepts and Planning Guide.) You can
type a new group name (designers) and a description, and then select domain users to add to
the group (jane, bob, and mary). Granting this group access to a set of files grants the privilege
to all users in the group.
Users can also be a member of more than one group (mary), but in some cases one group may
encompass those privileges provided by another group. For example, making mary a member of
the administrators group probably grants her all of the privileges of the designers group and
more. Because of this, her membership in the designers group may not be necessary. Also, a
domain user is automatically a member of that domain's users group (janice).

Files Reside on a Windows Server

If Express Project Creation---New User Mode is being used, you can specify only a drive letter
for the project location. In this case, the top level drive (C, E, and so on) must be shared. If you
do not use Express Project Creation, you can share directories individually, which allows finer
control of user access for security purposes.
So, if Express Project Creation New User Mode is being used, and the project is being created
on the E drive, the following should be done---share the E drive and create a new directory
having the same name as the project to be created. Apply the following permissions to this
empty directory:
 PDS\domain users---change
 PDS\administrators---full control
 PDS\pds---full control
When creating the project, you should be logged in as the pds user. As directories are created
and files are copied into the previously created project directory, they will inherit the permissions
of that parent directory.
In fact, the change permission granted to the domain users grants them the ability to create new
projects as well as create/delete models. It is possible to grant the domain users read/write
access to the project files and restrict them from creating or deleting any project files if the
permissions for the domain users are set using special file access and special directory access.
To do this, click the project directory and display the File Manager Permissions dialog box.
Click the line that reads:
 PDS\domain users---change (RWXD) (RWXD)
The entries after the word change to reflect the current directory and file permissions. The
RWXD signifies that the domain users have read/write privilege as well as the ability to
add/delete files and directories. To restrict the domain users' ability to create or delete any
existing files/directories, click Special Directory Access from the Type of Access list. It shows
that Read, Write, Execute, and Delete have been granted. Turn off all privileges except Read,
and click OK. Under Special File Access, turn off the Delete privilege (leaving Read, Write,
and Execute in place). Click Replace Permissions on Subdirectories so that all directories
and existing files in the project are updated. When complete, this allows domain users read/write
access to existing files and directories, but prevents them from creating or deleting any.
Attempts to create new models fail immediately because the design file is created before the
database tables. However, if a domain user attempts to delete a model, the database tables are
deleted, and at the end of this process, the underlying design file is not deleted. Therefore, it is
mandatory that PDS Access Control also be used to prevent regular users from accessing the
commands to delete project data.
After the required top-level directories have been created and shared, the required
subdirectories must be created. Express project creation in both New User and Advanced User
mode creates these subdirectories for you. If you are using manual project creation, you must
create these directories. Scripts are provided in Scripts to Create Project Directories (on page
171) that create a directory structure comparable with that created by Express Project Creation.
These scripts also copy reference data from the RDUSRDB, PD_Data, PD_EQP, PD_Draw, and
PD_Shell product directories. If this reference data is not needed, these lines in the script can be
commented out.
Beginning with PDS 8.0 SE, the PDS interface allows you to enter a share name for
various path locations, rather than requiring the entire path including the drive letter, as was the
case in previous versions. As such, you can use individual shares to control access to the
different models and data in the PDS project without sharing the entire drive. For example, you

can set up access to the \projdir\eerway such that only Raceway designers have full control,
while other users have read access only. Another example would be to share each project
directory with only the users working on that project.


SECTION 9
Installing and Configuring SmartPlant

License Manager
Detailed information about the operation of SmartPlant License Manager is provided in the
SmartPlant License Manager Installation and User's Guide.
Creating Required Databases/Database Users

Before creating a new PDS project, preparations must be made for the various schemas that will
be created. New database user names must be created within the single database that all user
names share. These new user names must be unique and should be tied in some manner to the
schema name. In fact, if the database username is identical to the schema name, administration
is greatly simplified.
Additional information about the installation and creation of databases and user names is
provided in the appendices. PD_Shell includes example scripts (in the pdshell\sql directory) that
can be modified to create databases/user names for use with PDS projects. These scripts must
be examined and modified by the system administrator before use.

Installing and Configuring SmartPlant License Manager

SECTION 10
Creating a PDS 2D/3D Project Manually

This section describes the procedure for creating a 2D/3D project using PD_Shell. See PDS
Project Creation Workbook (on page 189), for a workbook that is useful not only in the initial
creation of the project, but in tracking its history as well.
If you are creating a new PDS project on Windows, you can use Express Project
Creation. This is much easier that creating the project using the manual method described in
this chapter. See Express Project Creation Quick Start Guide for more information.
If you need to add to or revise an existing project, you must manually create your project.
In This Section
Creating Project Directories Manually ........................................... 62
Creating the 3D Project (Equipment and Piping)........................... 64
Creating a FrameWorks Project .................................................... 70
Creating the EE Raceway Project ................................................. 72
Adding Tables to the EE Raceway Reference Schema ................ 73
Changing Coordinate Systems and Working Units ....................... 79
Creating PE-HVAC Projects .......................................................... 81
Creating the 2D Project ................................................................. 89
Adding Disciplines to an Existing Project ...................................... 93

Creating Project Directories Manually

Preparing for Project Creation (on page 41), describes the use of a script to create the project
directories and to copy the reference data into the appropriate directories. This script creates a
directory structure identical to that created by the Express Project Creation New User mode and
is used as an example. The resulting directory structure is as follows:
This directory structure and the reference data copied into these directories are described in the
following sections.
Beginning with PDS 8.0 SE, the PDS interface allows you to enter a share name for
various path locations, rather than requiring the entire path including the drive letter, as was the
case in previous versions. As such, you can use individual shares to control access to the
different models and data in the PDS project without sharing the entire drive. For example, you
can set up access to the \projdir\eerway such that only Raceway designers have full control,
while other users have read access only. Another example would be to share each project
directory with only the users working on that project.
projdir\2d - This is the default location for the 2D reference data. This directory is specified
when using the PDS 2D Seed Reference Data dialog box. 2D reference data requires an
additional 30MB of hard drive space.
projdir\clash - This is the default location for interference detection plots and reports.

projdir\design_review - This is the default location for data associated with the SmartPlant
Review session data such as the control file, label files, and copies of models.
projdir\dwg - PDS sorts orthographic drawings by a 3-digit numeric code representing the
drawing type (code list 2000). For example, foundation drawings are designated as type 535
drawings and stored in the 535 directory.
 The border directory contains default border files copied from the PD_Draw product
directory.
 The cell directory is the default location for cell libraries used in drawings.
projdir\iso - This is the default location for isometric drawings.
projdir\model_builder - This is the default location for Model Builder APL files.
projdir\models - This is the default location for architectural, equipment, HVAC, and piping
models.
projdir\project - This is the default location for project data such as seed files, clash marker
files, and other project-wide files. These files are copied into this directory during the project
creation process.
projdir\raceway - This is the default location for an EE Raceway project.
projdir\rdb - This is the location for the majority of the 3D reference data, The eqp directory
contains the approved and unapproved reference data for the PD_EQP application. Three files
are copied into these directories by the script:
 zi_eqpms.hlp---PD_EQP parametric Help file
 zi_eqpms.lib---PD_EQP graphic commodity library
 zi_tutlib.lib---PD_EQP tutorial library
This reference data is described in the Equipment Databases and Libraries section of the PDS
Equipment Modeling (PD_EQP) User's Guide.
The lib directory contains the approved and unapproved reference data libraries for both the
PD_EQP and PD_Design applications. In some cases, files copied into these directories have
the same name with different extensions (for example, assembly.l and assembly.l.t). In such
cases, just the .l file name is listed below:
assembly.l---Piping Assembly Library
labels.l---Label Description Library
long_bom.l---Long Material Description Library
pipe_gcom.l---Piping Graphic Commodity Library
pjs_tbl.l---Piping Job Specification Table Library
short_bom.l---Short Material Description Library
spclty_bom.l---Specialty Material Description Library
std_note.l---Standard Note Library
us_pcdim.l---Physical Dimension Table Library
This reference data is described in the Reference Data Overview section of the Reference Data
Manager (PD_Data) Reference Guide.
 The source directory is the default location for neutral files.
 The spec directory is the default location for PDS neutral files.
projdir\report - This is the default location for report format, discrimination, search criteria, and
output files.

Creating the 3D Project (Equipment and Piping)

After you set the proj file location and the schemas file location, start PD_Shell to enter the
PD_Shell main menu.

If the proj file is empty (no existing projects), then PD_Shell bypasses this form and displays the
Project Administrator main menu.
Click Project Setup Manager to display the Project Administrator menu.

If the proj file is empty, PD_Shell bypasses this form and displays the Project Data main menu.
Set Model System of Units and NPD_System of Units to the required settings. Type a Project
Number, and press RETURN (or TAB). The project number should agree with the project name
as specified in the script used to create the project directory structure (testprj, in the following
example).
The system checks to see if this project exists. If it does, those items that have already been
created for that project become unavailable (Project Control Schema, for example), and those
items that have not been created for that project or items for which more than one per project
can be created (FrameWorks Project, for example) become available.
Assuming that the project does not exist, the cursor moves to the Project Name field, and you
can add additional project information. Enter the node name and location of the project directory
in the Network Address field. Following the example, the directory would be set to
c:\testprj\project. It is important that the project subdirectory be specified so that all project
control data is stored in the correct location.
After you have specified all of the project information, you can set the three toggles on the right
side of the form.
Create/Do Not Create DBAccess tables - If set to Create, this option creates an mscodelist
table and a set of join tables for each Standard Note type. See Chapter 4, Revise Project---
DBAccess in the Project Administrator (PD_Project) Reference Guide for additional information.
Many of the PDS databases do not have a mscatalog table, and many of the PDS tables do not
have an mslink column. By default, DBAccess looks for this table in the database and this
column in the selected table and expects the mslink column to have unique integer values. You
can use the environment variables DBA_NO_MSCATALOG and DBA_MSLINK to tell DBAccess
to build its list of database tables from the database rather than from the mscatalog table and to
use a column other than mslink as the key column. For example, in the PD schema,
pdtable_113 has a column named model_index_no that has unique integer values. By setting
DBA_NO_MSCATALOG=Y and DBA_MSLINK=model_index_no, you can use the DBAccess
Edit Database function on this table and scroll through the available records.

Create/Use Existing Reference Schema - If set to Create New Reference Schema, the
software prompts you to create a new Material Reference Database when you click Piping
Approved RDB Schema. You also have the option to create an unapproved database.
If this toggle is set to Use Existing Reference Schema, the system displays a list of existing
projects when you click Piping Approved RDB Schema. Selecting a project name from this list
determines the name of the approved (and optionally unapproved) Material Reference
Databases. The Piping Unapproved RDB Schema button disappears---if the selected project
had both approved and unapproved reference databases, then the new project has both. If the
selected project has only an approved schema, then the new project has only an approved
reference schema.
Create/Use Existing Raceway Reference Schema - If set to Create New Raceway
Reference Schema, you are prompted to create a new EE Raceway reference schema when
you click Raceway RDB Schema.
If this toggle is set to Use Existing Raceway Reference Schema, the system displays a list of
existing projects when you click Raceway RDB Schema. Selecting a project name from this list
determines the name of the EE Raceway Reference Schema.
The system displays a list of all projects, whether they have EE Raceway reference
schemas defined or not. You must make sure that you have chosen a project with an EE
Raceway reference schema. Express Setup will verify this for you.
At this point, the Create Project form might look like the following figure.

Click Project Control Schema to display the Create Schema form for the PD schema.
See the appendices for instructions on completing this dialog box for a number of different
databases.
Press TAB to move from field to field in the Create Schema dialog box.Pressing
RETURN is the same as clicking Apply.
After this information is complete, click Apply. The software dismisses the dialog box and stores
the information in memory.
There is an important difference between Express Project Creation and manual project creation.
During Express Project Creation, schemas are created immediately. If the information is
incorrect, you are given the option to enter the information again before proceeding to the next
schema. During manual project creation (described in this chapter), information for all schemas
is entered before any are created. For this reason, it is important that you understand the
various fields on the Create Schema dialog box, and make sure to complete them correctly the
first time.

After entering the information for the Project Control schema, create the Piping Design schema.
Clicking this button displays the Database Structure Revision form.
This form adds user-extended attributes (columns) and makes other modifications to the Piping
and Equipment tables in the DD schema. See Piping Design Schema in the Project
Administrator (PD_Project) Reference Guide for more information.
You can add 24 attributes to each piping table (the first five entries in the list). Attributes can be
added to the piping tables even after the project and piping models have been created. You can
add 10 attributes to each equipment table (the last two entries in the list) at this time, but you
cannot add attributes to the equipment tables after the project has been created. If you are not
adding attributes to the DD schema, click √ without making any changes. The Create Schema
dialog box for the DD schema displays.
After completing this dialog box, click Piping Approved RDB Schema to display the Create
Schema dialog box for the RA schema.
If you want to maintain approved and unapproved versions of the piping reference data, click
Piping Unapproved RDB Schema to display the Create Schema dialog box for the RU
schema.
At this point, you can click √ on the Create Project form to create a 3D-only project. If you are
using FrameWorks, EE Raceway, or PDS 2D with this project, they can be added in now or after
the project has been created.
To avoid creating models with incorrect working unit settings, adjust the working unit
settings of FrameWorks Plus and Raceway seed files after creating the projects, and before
creating models.
For workshare projects; that is, projects for which the design work will take place at different
locations, you can use the Site Administrator commands to set different Site IDs for the various
design offices. The Site ID can be used to designate ownership of models and drawings by
design office, and to help transfer models and drawings among sites. Refer to the Project
Administrator (PD_Project) Reference Guide for more information of the Site Administrator
commands and Site ID attribute.

Creating a FrameWorks Project

Click FrameWorks Project to display the Create FrameWorks Project form.

The default FrameWorks Project Number is the same as the PDS project name. The software
creates a directory with the path FrameWorks File Directory/FrameWorks Project Number. In
this example, the form was completed as follows.
In this example, the FrameWorks project directory is c:\testprj\fwproj on the server CADSRV.
The project directory creation scripts do not create directories for FrameWorks projects---it is up
to you to make sure that they are defined so that they reside inside of the PDS project directory.
The Force Units and Standard Section Table fields are code lists. Click the field to display the
choices.
The path limit for FrameWorks Plus projects is 36 characters, including all required
punctuation, and the mod and frz entries in pdtable_113.
When you accept this form, the FrameWorks project directory is created immediately and
consists of the following subdirectories:
fwproj\drw---drawings
fwproj\esl---engineering section libraries
fwproj\frz---frozen view files including surface models
fwproj\int---interface files to other programs
fwproj\mod---models
fwproj\rpt---reports
All of these directories are initially empty.
settings of FrameWorks Plus seed files after creating the projects, and before creating models.

Creating the EE Raceway Project

Click Raceway Project Schema to initiate the creation of an EE Raceway project. When this
button is clicked, the Network Address field changes to Raceway Network Address. Enter the
name of the EE Raceway project directory into this field.
The project directory creation script creates a subdirectory named raceway in the project
directory for use by EE Raceway projects. This path may not be usable because of EE
Raceway's limitation on the maximum length of the project name. In this example, the EE
Raceway project directory that was created by the script is c:\testprj\raceway.
 The maximum length of the EE Raceway project directory is defined using the following
formula:
 Max path length (including all punctuation) = 36 - (length of PDS project number)
This formula is based on the length of the subdirectories created under the EE Raceway project
directory and the maximum length of a model path name that can be stored in pdtable_113.
To store the EE Raceway project in the PDS project directory, where the PDS project resides at
the top level of a Windows drive, the maximum length of the PDS project number is nine
characters.
Let us see why---if an EE Raceway project directory of c:\myproj\myproj.prj\rway\dgn\ is
required, there are 18 characters of punctuation and path that exist regardless of what the PDS
project number is, therefore:
36 - (length of PDS projnum) = (length of PDS projnum) + 18
36 - 18 = 2 * (length of PDS projnum)
(length of PDS projnum) = (36-18)/2 = 9
Also note that if the standard directory naming structure is used, the longest directory will be
c:\myproj\rdb\source\eden_piping\, which also allows for a maximum project number of nine
characters.
The EE Raceway project directory must exist before you click Apply.

After filling in the Raceway Network Address and Directory and creating the specified directory,
click √ on the Create Project form to display the Create Schema dialog box for the EE schema.
When completed, click Apply to return to the Create Project form. New fields are displayed.
The location of the rway.sql and rway.cmd file must be entered into this dialog box. These files
are located in the eerway\db directory.
After completing this information, click Confirm. The fields that you just completed disappear.
Click Raceway RDB Schema to display the Create Schema dialog box for the RE Raceway
reference schema. Complete this dialog box and click Apply.
Adding Tables to the EE Raceway Reference Schema

The EE Raceway project schema tables are automatically created from within PDS. However,
the reference schema tables are not. To add the tables to the reference schema, you can use
the EE Raceway/Nucleus products. Although this should be done after exiting PD_Shell, the
instructions are provided here for clarity. You may want to skip to Changing Coordinate Systems
and Working Units (on page 79), and then return to this section after the project has been
created.

Setting the EE Raceway Environment Variables

From the EE Nuc program group, double-click EE Configure. This displays the Configure EE
Environment dialog box.
The location of the ee.cfg file is shown---in this case a new location has been entered. When a
raceway project is created through PDS, an ee.cfg is created in the PDS project directory. This
ee.cfg file should be used (as shown in the previous figure).
Environment variables are set by selecting them from the User Environment Variables list. They
then display at the bottom of the dialog box, where new values can be entered. After entering
the new value for an environment variable, click Set to record the change. The new value for the
environment variable displays in the top part of the dialog box.
Note that although PDS uses the ee.cfg file in the PDS project directory, PDS does not require
the environment variables in this file (such as EE_SCHEMA and EES_REFDB) to be set to valid
values (they can be left as UNINITIALIZED). This is because PDS gets the information it needs
about the EE Raceway project from the Project Control (PD) schema (the names of the project
and reference databases are stored in pdtable_102, and the names of the models are stored in
pdtable_113).
However, when accessing the same project through EE Raceway, these values must be set. It
is suggested that the ee.cfg in each PDS project directory have its environment variables set for
that project. As an example:
 PDS project proj1 is located on the server in e:\proj1. Its associated EE Raceway project is
in e:\proj1\ee. The ee.cfg file is e:\proj1\project\ee.cfg. Start the EE Configure utility and set
the EE File Name to \\server\e:\proj1\project\ee.cfg. Set EE_SCHEMA to ee_proj1 and
EES_REFDB to re_proj1. Set PROJECT_LOCATION to \\server\e:\proj1\ee and
SYS_PASSW_FILE to \\server\e:\proj1\project\ee.pwd.
 PDS project proj2 is located on the server in e:\proj2. Its associated EE Raceway project is
in e:\proj2\ee. The ee.cfg file is e:\proj2\project\ee.cfg. Start the EE Configure utility and set
the EE File Name to \\server\e:\proj2\project\ee.cfg. Set EE_SCHEMA to ee_proj2 and

EES_REFDB to re_proj2. Set PROJECT_LOCATION to \\server\e:\proj2\ee and

SYS_PASSW_FILE to \\server\e:\proj2\project\ee.pwd.
Now when entering either of these EE Raceway project through PDS, the ee.cfg file in that
projects project directory is used regardless of how the settings are seen through the EE
Configure utility. When entering either of these projects through EE Raceway, you would have to
go into the EE Configure utility and set the EE File Name to the ee.cfg file located in the project
directory of the associated PDS project.
If you are using PDS V5, the use of UNC paths is not supported. To initialize the ee.cfg
environment variables, the EE Raceway project location must be mounted using File Manager.
Following the previous examples, the E drive from the server could be mounted as the local F
drive. To initialize the ee.cfg file for project proj1 you would start the EE Configure utility, set the
EE File Name to f:\proj1\project\ee.cfg, set the EE_SCHEMA and EES_REFDB as shown
previously, and set the PROJECT_LOCATION and SYS_PASSW_FILE to
f:\proj1\project\ee.pwd. To initialize the ee.cfg file for project proj2 you would set the EE File
Name to f:\proj2\project\ee.cfg, set the EE_SCHEMA and EES_REFDB as shown previously,
and set the PROJECT_LOCATION and SYS_PASSW_FILE to f:\proj2\project\ee.pwd. Note that
this requires that all client nodes have the E drive from the server mounted locally as the F drive.
Although there are many other environment variables specified here, the only ones that need to
be set now are the first four in the list.
After setting these environment variables, you can start the EE Nucleus product. The main
menu displays your project in the list.

Click Database Utilities to display the Database Utilities form.

Click Update Reference Schema to display the Update Reference Schema form.
Type the name of the RE schema, leaving the Schema Password field empty. Click √ to use
the delivered SQL and CMD files to create the database tables and to load default reference
data into them. When complete, an output file is displayed.

Check this file carefully for errors! The output file is saved in the eerway\tmp directory.
After checking the output file for errors, click X to dismiss the form. Then click Restore on the
other forms.

Changing Coordinate Systems and Working Units

To change the coordinate system, click Specify Coordinate System to display the Plant
Coordinate System Definition form.
See Specify Coordinate System in the Project Administrator (PD_Project) Reference Guide for
more information on this form. The use of the Plant Coordinate System (PCS) is useful when the
Plant Monument is located a great distance from the design file origin. It allows the use of very
large coordinates, which would be outside the MicroStation design cube if the Plant Monument
(the center or origin of the design cube) remained 0,0,0.
The PCS can be specified up to the time that the first design area is created. After this,
the PCS cannot be set.

Click Revise Working Units to display the Revise Working Units form.
See Revise Working Units in the Project Administrator (PD_Project) Reference Guide for more
information on this form.
All models that you used in this project must have the same working units to ensure correct
results in reference file displays, drawings, interference detection, and so on. Because of this,
you should never change the working units after the project has been created.
Revising the ddl files and/or seed files after the project has been created can have
disastrous consequences. If the project settings need to be changed after the project has been
created, call Intergraph Support at 1-800-633-7248 for assistance.
When you start a project that uses non-PDS applications, be sure that the working units used by
those applications are the same as those used by PDS.
After specifying the working units, click √ to return to the Create Project form. Now you are
ready to create the project. After you click √ on the Create Project form, the default project
control data is written into the projdir\project directory; then the PD, DD, RA, RU, EE, and RE
schemas are created.

Creating PE-HVAC Projects

The steps for creating a project and a design file are listed below; detailed information on the
project environment dialog boxes is located in the Project Architectural Nucleus Reference
Guide.
Install PARNU and PEHVAC from the PDS CD.
Configuring Your Project

1. The project list file, projlist.txt, is an ASCII file that specifies the name and network location
of the associated project.
Use the PE-HVAC Configure icon to define the location (node and path) of the project list
file. Click Modify on the PE-HVAC Configure dialog box, and type the file location in the
Path field.
The projlist.txt file should be in the same location as the PDS proj_file. Each time you create
a new Pehvac project you need to add an entry in this file.
The format of the projlist.txt is as follows:
project_name project_ project_path pds_project_n
node ame
hv_project local_ c: pds
machine_ \demo\hvac\hv_
name project
demo server x:\PDS\models pds
\hvac
You will need to create this file with all existing projects that are currently available to
the user. You will need only one list file for all of the users on the network since all of the
users may point to the same project list file. This project list file must be located in the
directory that is specified by the information written into the control file by the PE-HVAC
Configure utility (HVAC_PROJ_PATH).
2. A project control file, peh.cmd, is required for each client workstation. This file defines the
environment variables necessary to locate the PE-HVAC products and the relational
database files; it also defines the location of the project list file.
Use the PE-HVAC Configure icon to define the location of the control file. A configuration file
is delivered with PE-HVAC (in the win32app\ingr\pehvac directory); you can reference this
file, you can copy the delivered file to another directory, or you can reference an existing
peh.cmd file.
Use backward slashes to reference a control file that is located on a server. Do not
include the file name; it is automatically appended.
3. A new project data location file, envar.txt, allows you to define project-specific variables on a
per-project basis without having to define environment variables. Copy the delivered
envar.txt file from the pehvac\support directory into the project directories.
You need to modify the envar.txt file to access specific reference data. Each time you select
this project, the information from the envar.txt file is used.
Creating a Project
1. Create a HVAC project directory c:\pds\hvac. (If you want to create the project on the server
then do a hard mount to the server and drive where you want to create the project).

2. Change the working directory for PARNU to the project location (c:\pds\hvac or
X:\PDS\models\hvac where X is the mounted server drive).
3. Select the P-Arnu icon, and from File > Properties, specify a working directory.While
loading P-Arnu; the project files are placed in the \users\projects directory.
You may have to first create a working directory through Windows Explorer.
4. Enter PARNU and create a project. (This will create a new directory using the project name.
Suppose you named your project as HV_PROJECT then this will create a directory
X:\PDS\models\hvac\HV_PROJECT)
5. Double-click the P-Arnu icon from the BDM (Building Design and Management) program
group.
The Project Environment command group is activated.
6. Click Create from the group.

The Create Project dialog box is displayed.
7. Fill out the dialog box to meet your specifications, and click OK.
The project is created, and you can either continue to create projects or click Cancel to
dismiss the dialog box.
When you dismiss the Create Project dialog box, you are returned to the Project
Environment command group.
8. Copy the envar.txt file (x:\win32app\ingr\pehvac\support\envar.txt) into your project directory
(c:\pds\hvac\hv_project. This file is required for each project ).
9. (OPTIONAL) Copy directory tables from the PEHVAC deliverable to the PDS project RDB
directories. X:\pds\rdb\hvdata. The directories you need to copy are:
 DBA directory from x:\win32app\parnu\dba
 EDEN directory from x:\win32app\pehvac\eden
 Support directory from x:\win32app\pehvac\support
10. Edit the envar.txt to point the variables to the desired locations. (Change mynode to server
or client name).
(If you did the previous optional step, then you will need to change the location of directories
as required. If you did not do the optional step, then you can modify the envar.txt file to
change the node location to one of the machines that has Parnu and Pehvac loaded. If you
point to a specific machine for the variables then that machine needs to be ON and the
pehvac and parnu directories should be shared.) It is recommended to store your
customized data not in the product directory. Reloading the Software would delete those
files.
Example:
.

# AP_TABLE
# Set to a directory that contains support files specific for PEHVAC.
#
AP_TABLE server c:\win32app\ingr\pehvac\tables\
.
.
PHV_REFERENCE server c:\win32app\ingr\pehvac\support\tables\
#
# imperial support tables directory
#
PHV_IMPERIAL server c:\win32app\ingr\pehvac\support\tables\imperial\
11. Click Apps from the Project Environment command group.
The Applications dialog box is activated, and the applications you have loaded on your
machine and any projects you have created are displayed.
12. If you have not already done so, use the PE-HVAC Configure icon to specify the location of
the projlist.txt file.
13. Select PE-HVAC from the Application list; then select the project you want to use form the
Project list, and click OK.
The project list form is displayed.
14. Select a project from the displayed list. Then click OK.

The first time you enter a PE-HVAC project, the Reference Database Operations dialog box
is displayed.
15. Create prj_demo and hrf_demo users in your relational database. The prj_demo schema is
used to maintain designed data. Each project requires its own prj_schema. The hrf_demo
schema is used to store the Reference data. The hrf_demo schema can be used by different
projects. (the Reference database is required to be able to place elements. The Project
database is used for reports and necessary if you want to create envelope files and labels.)
If your Pehvac Project schema does not have the same name as your PDS project (e.g.
prj_demo instead of prj_pds you need to set the following system variable:
PDS_HVAC_SCHEMA_NAME=demo
16. Start Parnu. Select Database > Create and select the Pehvac project. After the schema is
created, select Pehvac under Applications to load Pehvac tables.
17. If you are going to use an existing PE-HVAC reference database, click Select and select the
database from the list. If you need to create a new reference database, click Create.

The Create Schema dialog box is displayed.
18. This dialog box lets you create a schema, or unique database/user combination, for the
reference database.
19. Click Load/Unload to load equipment into your reference database.
PE-HVAC displays the Reference Database dialog box.

20. Select the Load option and the devices and labels that you want to load into your reference
database. You can select all of the devices at one time by selecting the Select button under
each list.
When you have filled out the dialog box to meet your requirements, click OK.
PE-HVAC loads the devices into your reference database.
21. Click Cancel when you are finished loading devices into your reference database.
PE-HVAC returns you to the Reference Database Operations dialog box.
22. Click Cancel to dismiss the Reference Database Operations dialog box.
The PE-HVAC command group is activated. Also, if there are no design files present in the
project you selected, the Create Design File dialog box is automatically activated.
23. Fill out the Create Design File dialog box to meet your specifications, and click OK.
The design file is created. Continue to create design files, or choose Cancel to return to the
PE-HVAC command group.
24. Click Design to enter the design file.

The Enter Design File dialog box is activated, displaying any design files you have created.
25. Select a design file, and click OK.

You are taken into the design file graphic environment.
26. Select Settings > Design File.
27. Set MU:SU:PU to the PDS project settings (1:12:2032 English or 1:1000:80 metric).
After starting PE-HVAC, the Initialization Complete message is displayed. If this message
does not display, make sure you have installed and configured PE-HVAC properly and that
you have sufficient free disk space. After the message is displayed, the PE-HVAC Main
menu is added to the MicroStation toolbar. You can then freely access any PE-HVAC or
MicroStation commands.
Any model you create in PEHVAC will need to be created again through PDS. Creating
models for PEHVAC through PDS does not create physical models, it will create only the
required PDS database entries in pdtable_113.
Adding Design File to the PDS Project

1. Enter PDS > Project Administrator > Project Environment Manager > Model Setup.
2. Select HVAC under disciplines and specify the location for your models.
(c:\demo\hvac\hvproject - local - or g:\pds\models\hvac\demo)
3. Enter PDS > Project Administrator > Project Environment Manager > Create.
4. Select Create Design Area in HVAC and create a design area. It is useful to name the
design area after the PEHVAC project.
5. Select Create Model in HVAC.

Creating the 2D Project

After the 3D project creation has completed, the 2D project creation starts automatically if PID
Project was selected when you clicked √ on the Create Project dialog box. First, additional
2D-related tables are added to the PD schema.
After creating the additional tables in the PD schema, the Site/Project Name must be
completed in the PDS 2D Project Manager form. Other fields in this form are completed
automatically based on the project information supplied when the 3D project was created.

After entering the Site/Project Name, the PDS 2D Application Manager form displays.
This form is described in the PDS 2D System Setup Guide. As part of the 2D project creation,
the first three buttons are used.
The PDS 2D reference data must be seeded first. Click Seed Reference Data to display the
Seed Reference Data form.
Press TAB to move from field to field in these forms rather than pressing RETURN.
From the Seed Project Number list, you can select exd_English or Translated RDB. Selecting
exd_English copies new PDS 2D reference data from the local node to the specified directory.
Selecting Translated RDB makes entries in the PD schema that point to the location of existing
reference data (that may have been translated from an older version). Click √ to copy over the
PDS 2D reference data to the specified directory. The PDS 2D reference data occupies
approximately 12MB.

When finished, click PID from the Application list in the PDS 2D Application Manager form.
Click exd_English, and modify the Reference Database Path to point to the 2d\pid directory.
Click √ to copy the PDS 2D PID reference data. The PDS 2D PID reference data occupies
approximately 11MB. When finished, click PFD as the application, modify the Reference
Database Path to point to the 2d\pfd directory, and repeat. The PDS 2D PFD reference data
occupies approximately 7MB.
After seeding the reference data, the associated schemas can be created. The PDS 2D
application does not require an additional schema---its tables are stored in the PD schema.
However, not all 2D tables are added to the PD schema as a result of starting the 2D project
creation process. Select PDS 2D from the PDS 2D Application Manager form. Then click
Create Tables to add the additional 2D tables to the PD schema.
Click PID on the PDS 2D Application Manager form, and then click Create Schema. You are
asked if you want to create a Task or Master schema.
The Task schema is the working copy of the design data for a project, while the Master schema
is an approved copy of the task schema which is frozen at some point in time. With the toggle
set to Task, click √ to display the Create Schema dialog box for the PID Task Schema. It is
similar to the Create Schema dialog boxes seen earlier in the project creation process, and is
completed in a similar manner.
The 2D schema name is not entered into the Create Schema dialog box automatically---be sure
to enter the prefix that corresponds with the schema type being created (for example, pid_ for
the PID Task schema). Also be especially cautious when entering information to create ALL 2D
schemas---if the wrong information is entered, you are returned to the 3D Create Project form!
The following chart is provided to assist in the creation of the 2D schemas. The list is sorted
according to the order of the applications in the drop down list:
Schema Name Schema Prefix
Project Control PD_ (will already exist if 3D project has been

created)
* Project Control Backup PDBK_
PID Task PID_
* PID Task Backup PIDBK_
PID Master PIDM_
* PID Master Backup PIDMBK_
PFD Task PFD_
* PFD Task Backup PFDBK_
PFD Master PFDM_
* PFD Master Backup PFDMBK_
IN Task IN_

* IN Task Backup INBK_

IN Master INM_
* IN Master Backup INMBK_
INR Task INR_
* INR Task Backup INRBK_
INR Master N/A
INR Master Backup N/A
(*) indicates that this schema is usable only by PDS 2D 6.1 or higher. N/A indicates that this
schema need not be created.
After the PID schema has been created, click Create Tables from the PDS 2D Application
Manager form. The Task/Master toggle form displays again. Set the toggle to Task. Click √ to
initiate the creation of the tables in the PID Task schema. You receive feedback as each table is
created.
With PID still selected as the application, click Create Schema again. This time, set the toggle
to Master, and click √ to display the Create Schema dialog box for the PID Master schema.
Complete this dialog box, click Apply to create the schema, and then create the database
tables, making sure the toggle is set to Master.
If you leave the toggle set to Task and click Create Schema, the software informs you that this
schema has already been created. If you add tables to a schema that has already had its tables
created, the software sees that they exist and does not re-create them.
After creating the PID Task and Master schemas, click PFD as the application, click Create
Schema, and create the PFD Task schema. Click Create Tables, and set the toggle to Task.
Click √ to create the Task tables. You must create the PID Master schema before you create
and PID Master tables. Click Create Tables again, and set the toggle to Master. Click √ to
create the Master tables.
Use the PDS Project Creation Workbook (on page 189), to track the creation of the 2D
schemas and the addition of tables to these schemas.
Click IN as the application, and create the IN Task and Master schemas as well as the tables for
each schema. Click INRDB as the application, and create the inrdb Task schema. In a similar
manner, other 2D schemas can be created as required. Any schema not created now can be
added in the future. Note, there is no need to create the INRDB Master schema.
Project Creation Requirements for Using SmartPlant to IDM Data Transfer

If you intend to transfer data between the SmartPlant P&ID and IDM applications, there are
special project setup requirements that must be met before using this feature. Refer to the
SmartPlant P&ID to IDM Transfer section of the PDS IDM User's Guide for details.

Adding Disciplines to an Existing Project

Disciplines not added to a project at project creation can be added afterwards. To add a
discipline to an existing project, enter PD_Shell, pick the project, and then click Project
Administrator. See Creating the 3D Project (Equipment and Piping) (on page 64), for more
information. Click Project Setup Manager, and if FrameWorks/ModelDraft is loaded, then the
Insert FrameWorks Data/Insert ModelDraft Data button displays.
Inserting FrameWorks/ModelDraft Data

Multiple FrameWorks/ModelDraft projects can be created within a single PDS project, so the
Insert FrameWorks/ModelDraft Data button is always active. The Insert
FrameWorks/ModelDraft Data forms are identical to those seen when creating a new 3D
project except that a list of existing FrameWorks/ModelDraft projects displays at the bottom of
the form.
If the information for a new FrameWorks/ModelDraft project is entered in this form, the new
directories/files are created in the specified location. To add an existing FrameWorks/ModelDraft
project into a PDS project, enter the location of the existing project into this form. When you click
√, PDS checks for existing directories/files and uses them rather than creating new ones.
To assist in adding in existing FrameWorks/ModelDraft projects into a PDS project, see Using
PDS with FrameWorks.
creating models.
Creating an EE Raceway Project

Only one EE Raceway project can be created per PDS project. If an EE Raceway project has
already been created, then the Raceway Project Schema and Raceway Reference Schema
buttons are not available. If an EE Raceway project has not yet been created, these buttons are
available. Clicking Raceway Project Schema starts the process to create the new EE Raceway
project. See Creating the EE Raceway Project (on page 72), for more information.
creating models.
Creating a 2D Project
Only one 2D project can be created per PDS project. If a 2D project has already been created,
the PID Project button is still available because additional 2D applications can be added to the
2D project after its creation. The PID Project button can be clicked to start the 2D project
creation for a new 2D project or to enter the 2D project creation environment to add disciplines
to an existing 2D project. See Creating the 2D Project (on page 89), for more information.


SECTION 11
Attaching Reference Data to the Project

After you have successfully created a new project, you must attach and initialize the PDS 3D
reference data. The PDS 3D reference data is extensive, and a detailed description of it can be
found in the Reference Data Manager (PD_Data) Reference Guide.
PDS 3D reference data for both the Piping and Equipment modules comes delivered in the
following formats:
 Look-up data stored in a database
 Look-up data stored in indexed files (also called libraries)
Data is stored in both indexed files and databases because in certain instances it is faster to
read the information from an indexed file than from a database.
Both the Piping and Equipment modules support the use of approved and unapproved reference
data. If a project has both approved and unapproved reference data defined, the software will
use the approved versions by default. The RDB revision commands (for example, the spec
writing commands) use the unapproved versions by default.
Piping Reference Data

Piping reference data that comes delivered with the RDUSRDB product is listed below:
Name File Name
Piping Job Specification Table us_pjstb.l

Library
Physical Data Library us_pcdim.l
Short Material Description Library us_shbom.l
Long Material Description Library us_lgbom.l
Specialty Material Description us_spbom.l
Library
Piping reference data that comes delivered with the PD_Shell product is listed below:
Name File Name
Graphic Commodity Library pip_gcom.l

Piping Assembly Library assembly.l
Label Description Library labels.l
Standard Note Library std_note.l
The script which creates the project directory structure also copies these files from the product
directories into the project directories. Do not use the reference data files that are located in the
product directory, since reloading or removing the product could result in the loss or alteration of
the reference data. However, there is no reason why one project cannot share the reference
data of another project.

You may notice that for some of the reference data, additional files having the same name but a
different extension are also defined. The Piping Job Specification Table Library, for example,
includes the files whose functions are described below:
Name Function
us_pjstb.l actual library used by the PDS software

us_pjstb.l.t text library for extracting individual files
and tables for revisions
us_pjs.l.r revision management data for use with
the RDB revision management
commands
The names and locations of the reference data files described above are stored in a
database---specifically pdtable_102 in the PD schema. This information must be specified to the
database as a separate step after the project has been created manually. Express Project
Creation does this automatically. To enter this information, enter PD_Shell and click Reference
Data Manager. A warning message displays informing you that the Standard Note Library
cannot be found:

Dismiss this dialog box---you will specify the location of the Standard Note Library later in the
process. The Reference Data Manager main menu displays after you dismiss the warning.

This form is described in greater detail in Chapter Three of the Reference Data Manager
(PD_Data) Reference Guide. Click Reference Database Management Data to display the
Reference Database Management Data form.
Clicking any one of the entries in this list displays the current name and location of that
reference data in the lower part of the form. The only item in this list that has been set is the
Material Specification Reference Database (which contains the names of the RA and optionally
the RU schemas). Locations have not been set for any of the other libraries---clicking any of the
other listed items will not display anything in the lower part of the form.

Rather than setting the location for each library individually, it is easier to use the Default All
Library Locations button to set all library locations. Libraries are copied into the
c:\testprj\rdb\lib\approved and c:\testprj\rdb\lib\unapproved directories by the project directory
creation script (see Creating Project Directories Manually (on page 62), for more information). In
this example, click Default All Library Locations, and complete the form as shown in the
following figure:
Remember to press RETURN (or TAB) after each entry!

Click √ to write the library locations to the PD schema. The full specification of a library consists
of the directory path entered into this form and file names for each of the libraries. This can be
seen by clicking one of the items in the list after you have completed the Default All Library
Locations operation. For example, if you click Piping Job Specification Table Library, the
location displays as shown in the following figure.
In the RDUSRDB product directory, the name of the Piping Job Specification Table Library is
us_pjstb.l, but the Default All Library Locations operation has set it to pjs_tbl.l. The project
directory creation script takes this into account, and when the files associated with the Piping
Job Specification Table Library are copied from the product directory to the project directory,
the names are changed to reflect this. This renaming operation has also been done for the
Short, Long, and Specialty Material Description Libraries as well as the Graphic
Commodity Library.
The system does not verify the location of the libraries at the time this information is
entered into the Reference Database Management Data form. If errors have been made, you
will receive warnings at the time you enter a piping or equipment model, or enter the applicable
Reference Data Manager command.
You will notice that the Default All Library Locations operation has also set the international
Physical Data Libraries (DIN, JIS, and so on). These will not be used unless specified as
described in the Reference Data Manager (PD_Data) Reference Guide. They can be left as set
by the Default All Library Locations operation, or they can be deleted by selecting each field,
pressing DELETE, and then pressing ENTER. When you have done this for each field, click √ to
write the changes into the PD schema.
The Reference Database Management Data form must be accepted each time a
change is made to any of the reference data items. It is a good idea to pick another reference
data item from the list, then pick the item that was changed to verify that the change was made.

At the end of the listing of reference data, the location of the optional Commodity Synonym
Library is defined. This is not set by the Default All Library Locations operation. The Commodity
Synonym Library need not be set in order to start using the project. See Chapter 15 of the
Reference Data Manager (PD_Data) Reference Guide for a description of using the Commodity
Synonym Library. In this example, the Orthographic Drawing Borders directory can be set to
c:\testprj\dwg\border. The project directory creation script copies the default drawing borders
from the PD_Draw product directory into this directory.
In this example, the reference data libraries were copied into the project directory by the project
directory creation script. An alternative approach would be to use the Copy All Standard
Libraries function. The use of this function is described in Chapter Four of the Reference Data
If you are changing reference data items, you can use the Approved -> Unapproved button to
copy whatever was entered into the approved fields into the unapproved fields. You would then
need to edit the unapproved path (typically inserting the characters "un" in front of the word
approved) before pressing ENTER and then clicking √ to accept the form.
Equipment Reference Data

The equipment design module of PDS 3D shares some of the reference data used by the piping
module. To review or set the equipment reference data, click Equipment Modeling from the
PD_Shell main menu to display the Equipment Modeling Options form.

This form is described in Chapter Eight of the PDS Equipment Modeling (PD_EQP) User's
Guide. Click Database Library File Manager to display the Equipment Database Library
Management form.
This form operates in a manner similar to the Reference Database Management Data form
described previously. Some of the reference data items have been set to default values. The
Graphic Commodity Library, Tutorial Definition Library, Cell Library, and Forms Library have
been set to the PD_EQP product directory on the node where the project was created. This is
not typically used because the product may be removed or reloaded.
Set the locations for the displayed items as follows:
Graphic Commodity Library - Set the Directory field to projdir\rdb\eqp\approved, and set
the Specification field to zi_eqpms.lib.
Tutorial Definition Library - Set the Directory field to projdir\rdb\eqp\approved, and set the
Specification field to zi_tutlib.lib.
Equipment Physical Data library - Leave the Directory and Specification fields blank.
Piping Physical Data Library - Set the Directory field to projdir\rdb\lib\approved, and set the
Specification field to us_pcdim.l.
Piping Job Specification Table Library - Set the Directory field to projdir\rdb\lib\approved,
and set the Specification field to pjs_tbl.l.
Piping Design Standard Note Library - Set the Directory field to projdir\rdb\lib\approved,
and set the Specification field to std_note.l.
Cell Library - Leave the Directory and Specification fields blank.
Forms Directory Location - Leave the Directory and Specification fields blank.

Regarding the specification of the Forms Directory Location, if you are using PDS V6, and if
you have made no customizations to the PD_EQP parametric forms, you can leave this field
blank, and the software will look for the equipment forms in the PD_EQP product directory on
the client node. For this to work, PD_EQP must be loaded to the client node in client, local, or
server mode.
If you are using PDS V5, or if you have customized the PD_EQP parametric forms and are
storing them on a server, the Forms Directory Location must be set to a valid location. Rather
than loading PD EQP on the server, you can copy the PD EQP forms to a directory on the
server, share this directory, and specify it as the Forms Directory Location. One possible
directory structure is shown:
projdir
projdir\eqp
projdir\eqp\forms (copy of pdeqp\forms directory)
projdir\eqp\sym (copy of pdeqp\sym directory)
In this example, the Forms Directory Location would be set to the projdir\eqp directory. Both
the forms and sym directories must be found in this path.
The project directory creation script copies the Graphic Commodity Library, the Tutorial
Definition Library, and the Eden Description Help File from the PD_EQP product directory into
the projdir\rdb\eqp\approved and projdir\rdb\eqp\unapproved directories. The Graphic
Commodity Library and Tutorial Definition Library locations can be set to these locations---the
default files names match those used by the project directory creation script, so only the node
and path have to be checked.
The Eden Description Help File corresponds to the default equipment delivered in the
Equipment Graphic Commodity Library and does not need to be specified to the database. The
software looks for it in the same directory as the Equipment Graphic Commodity Library. If new
pieces of equipment are defined, the help file must be re-created using the Create Help Library
function in the PD_EQP Eden Data Manager (accessed by clicking Graphic Library Manager
then Eden Data Management from the Equipment Modeling Options form).
The Equipment Physical Data Library does not need to be set at this time. See the Define
Libraries section in the PDS EDEN Interface Reference Guide for details on when this library
can be used. The Piping Physical Data Library must be set---it can also be set to the same
location as in the Piping module (us_pcdim.l). The Piping Standard Note Library and the Piping
Job Specification Table Library can be set to the same locations as in the Piping module
(std_note.l and pjs_tbl.l respectively).
Loading Default Data into the Piping Reference

Database
After defining the locations for the Piping and Equipment reference libraries, default reference
data can be loaded to the reference databases. The project creation script copies the following
neutral files from the product directories into the project directories (specifically, into the
projdir\rdb\spec directory):
File Name Description
1c0031.pcd Piping Commodity Specification Data for the 1C0031 Piping Materials
Class

2c0032.pcd Piping Commodity Specification Data for the 2C0032 Piping Materials
Class
classes.pmc File that lists all the delivered Piping Materials Classes and their attributes
component.data Component Insulation Exclusion Data
constol.data Piping Construction Tolerance Exclusion Data
flange.data Flange Insulation Exclusion Data
implied.data Piping Commodity Implied Material Data
instrment.data Instrument Component Specification Data
pcd_size.data Piping Commodity Size-Dependent Material Data
specialty.data Piping Specialty Specification Data
taps.data Tap Properties Data
Neutral files are located in the following directories:
 rdusrdb\spec_data contains all .pcd files, classes.pmc, implied.data, taps.data,
US_lgbomdata, US_shbom.data, and US_spbom.data.
 pddata\sample\data contains component.data, constol.data, flange.data, instrment.data,
pcd_size.data, and specialty.data.
In addition to the files listed, the pddata\sample\data directory contains a sample metric
spec (metric_npd.pcd and metric_npd.pmc).
A detailed description of this reference data can be found in Chapter Five of the Reference Data
Before loading any of these files to the database, the classes.pmc file must be edited to reflect
the fact that not all available Piping Materials Classes are being loaded. The classes.pmc file
lists many Piping Materials Classes---of these, only two will be used (1c0031 and 2c0032). Edit
the classes.pmc file using any text file editor and delete all piping material classes except
1c0031 and 2c0032.
It is important to edit the classes.pmc file; PDS uses this file to determine the available
Piping Materials Classes.

From the Reference Data Manager main menu, click Piping Job Specification Manager to
display the Piping Job Specification Manager main menu.

If you click Piping Materials Class, click Load/Replace, and follow the example used so far,
the form would look like the following figure:
These buttons are used if the pipe support functionality is used. Contact Intergraph
support (http://support.Intergraph.com) additional information about pipe supports.
The Submit Immediately toggle will display after you enter the node, file path, and name. This
toggle may be set to Delayed Submit, but for a batch job of this type, a delayed submission is
not typically required.
Click √ to submit the batch job. The batch job will be submitted to the PDreference queue. If
"desktop access" was enabled for Batch Services, a collapsed DOS window displays at the
bottom of the screen. You can also start the Batch Manager and check to see that the batch job
made it into this queue and is running.
If the collapsed DOS window never appears, or if the job never appears in the
PDreference queue, either the Batch Services account mapping has not been set or you have
some other problem related to the setup of Batch Services. This problem must be fixed before
continuing.
If the Piping Materials Class file is successfully loaded into the database, a log file (pmc.log) will
be created in the temp directory on the machine where the batch queue resides. Typically this
will be the node that submitted the batch job, but if the PDreference queue has been defined as
a pipe queue and the job was routed to another server, the output file will reside in the temp
directory on that server. The log file should be examined for any error messages.

Click X to exit this form, and click Piping Commodity Data. Note that the system has recalled
the node and path from which the classes.pmc file was loaded. When you click Load, a new
toggle displays.
In this case, a single file spec (1c0031) was loaded; however, multiple specs could be loaded in
a single step. The toggle could be set to List of Files instead of Single File, and a file that lists
multiple specs could be entered. The list.pcd file located in the rdusrdb\spec_data directory is an
example of such a file.
In a similar manner, the file associated with the 2c0032 spec (2c0032.pcd) could also be loaded.
Note that as each spec is loaded, the results are all written into the same log file (pcd.log), so if
a number of specs have been submitted to load, the log file should be checked immediately
after the completion of each batch job.
The complete list of neutral files and their associated log files follows:
Option Name Input File Log File
Piping Materials Class Data classes.pmc pmc.log

Piping Commodity Data c0031.pcd, and so on pcd.log (for all)
Piping Specialty Specification Data specialty.data speclty.log
Instrument Data instrment.data instment.log
Tap Properties Data taps.data taps.log
Size-Dependent Material Data pcd_size.data pcd_size.log
Project Implied Material Data implied.data implied.log

Option Name Input File Log File
Component Insulation Exclusion Data component.data compinsu.log

Flange Insulation Exclusion Data flange.data flnginsu.log
Construction Tolerance Exclusion Data constol.data cons_tol.log
If approved and unapproved reference databases exist, the Piping Job Specification Manager
will load the information into the unapproved database. The Unapprove -> Approve button can
then be used to post information from the unapproved to the approved reference database.
When running this command, a warning message appears to remind you that the information in
the approved reference database will be overwritten with that from the unapproved.
The log file for this operation is named copyspec.log.

Information about the other options (delete, report, and so on) can be found in the Piping Job
Specification Manager section of the Reference Data Manager (PD_Data) Reference Guide.

SECTION 12
Creating 3D Areas and Models

After you have created the project and initialized the reference data, you can create models and
drawings. The 3D Disciplines (on page 109) and 2D Disciplines (on page 125) disciplines are
discussed separately.
Project Organization
Disciplines - Such as Piping, Equipment, HVAC, and Structural.
Design Areas - Which represent a specified volume of the physical plant.
Models - Which correspond to a specific 3D volume for a discipline within the specified design
area. Each model is a MicroStation design file on the disk.
3D Disciplines
The following disciplines are delivered with the PDS 3D applications:
 Piping
 Equipment
 Structural
 HVAC
 Raceways
 Architecture

Additional disciplines can be created if necessary up to a total of ten disciplines. To create a

new discipline, start PD_Shell, click the project name, and enter Project Administrator. This
brings up the Project Administrator main menu:

This menu is described in detail in Chapter Three of the Project Administrator (PD_Project)
Reference Guide. Click Project Environment Manager to display the Project Environment
Manager main menu.

This menu is described in detail in Chapter Five of the Project Administrator (PD_Project)
Reference Guide. Click Create to display the Create Options main menu.

This menu is also described in Chapter Five of the Project Administrator (PD_Project)
Reference Guide. Click Create Discipline Data, enter the name of the new discipline in the
Discipline Name field, and press RETURN.
Click √ to create the new discipline. If the discipline will contain as-built models created with the
PlantGen application, click PLANTGEN Discipline to allow PlantGen data to be recognized by
the Review Attributes command and various labeling commands. In this example, a discipline
named clash is created.
See Also
3D Areas (on page 114)
3D Models (on page 119)
Model Creation for Other 3D Disciplines (on page 125)
3D Design Data and the Database (on page 125)

3D Areas
PDS 3D design areas can be defined as dynamic or based on a predefined volume. This
becomes very important when you perform interference detection. Consider the area definition
shown below.
Although this is shown in two dimensions, the area definitions are in fact three-dimensional
volumes. There is a single structural area encompassing the entire plant defined as S1. Piping
area P1 encompasses equipment areas E1--E3, and piping area P3 encompasses equipment
areas E4--E6. The main piping thoroughfare is defined as P2.
The benefit of breaking the plant into areas is that it allows the plant to be divided into more
manageable amounts of data for various functions (such as isometric extraction, SmartPlant
Review sessions, interference detection, and so on). For instance, if changes are made in
equipment area E4, interferences can be run just in this area rather than checking the clashes
for the entire project. This can save substantial time because interference detection is a
compute-intensive operation.
When working in an area created using a predefined volume, the system does not stop you from
placing piping or equipment outside the boundaries of the area. However, when interference
detection is run using the Pre-Defined Volume option the system does not report a clash that
existed outside the predefined volume.
Another approach is not to use predefined volumes for your actual design areas. In this case, a
piping area grows to accommodate all of the piping placed within it. A strategy that can be
combined with this approach is to create a user-defined clash discipline used only for
interference detection. The design areas for the user-defined clash discipline are created with
predefined volumes, while the design areas for the other disciplines (piping, equipment, and so
on) are not. Many project administrators find this approach to be quite useful. Additional
information regarding the theory of clash area management is covered in the PD_Clash class
and in its accompanying documents.

To create a new 3D area, click Create from the Project Environment main menu and then click
Create Design Area Data. Click the discipline from the list of available disciplines, and click √ to
display the Create Design Area main menu. If the piping or equipment discipline is selected,
the system reads the working units and plant monument from the Type 63 data in the seed file
and displays the following information.
When this form displays, the predefined volume toggle is set to Interference Management
Design Area if the piping, equipment, or raceway discipline was selected. This toggle is off for
all other disciplines. The default origin of the predefined volume is set to the origin of the Plant
Coordinate System (PCS 0,0,0).
Seed Files and the Type 63 Data

When you create a new project, a number of seed files are copied from the product directories
into the project directory.
File Name Source Location Purpose
borderifc.dgn pdshell\border Border file for clash plots

drwsdz.dgn pdshell\seedz Drawing seed file
eqpsdz.dgn shell\seedz Equipment model seed file
mdlsdz.dgn pdshell\seedz Piping model seed file
rwysdz.dgn EERWAY\dgn\seed EE Raceway model seed file

File Name Source Location Purpose
projname.dgn applicable pdshell\seedz and model seed Clash marker file

file
When you create the project, you have the opportunity to modify the working units and plant
monument. This information is written to the Piping, Equipment, and Drawing seed files shown
in the previous table. In addition to containing information that results in the display of graphical
data, MicroStation design files can also contain information that does not result in the display of
graphical data but is read by other applications for other purposes. One example of this is what
is referred to as the Type 63 data. This information stores many project-wide parameters that
are applied to new models and areas at the time they are created. For this reason, changes to
this information are permitted only at certain times. For example, the working units can be set
only at project creation, and the plant monument must be defined before any areas or models
are created.
Seed Data
Chapter Six of the Project Administrator (PD_Project) Reference Guide describes all of the
Project Data Manager options. Click Seed to display the Revise Seed Files menu.
The Revise 3D Plant Design Data function includes options to specify a plant monument and
options to set the date/time format and coordinate readout format. Changes made here affect
the seed files or existing models. Coordination of these settings in a project being executed at
multiple sites is of paramount importance. The seed file report can be used for this purpose.
The Revise Model Data function (Revise button under the Piping Model Data category)
includes settings for MTO reporting options, whether the approved or unapproved reference

data is used, and the setting of the model file symbology. The model file symbology is an
important system setting and dictates if graphic symbology is based on model category, fluid
code, or construction status. Some of these changes can be applied to previously created
models and others cannot so it is important to inspect/coordinate seed file settings at the
beginning of the project.
The Propagate Piping Model Data function (Propagate button under the Piping Model Data
category) allows selected seed file settings to be applied to existing models. You can propagate
the following Type 63 data to existing models:
 Component Placement
 Piping Data Control
 Physical Units Options
 Nozzle Transfer
 Material Takeoff
 Design Review Label
 Reference Database File Specifications
 Design Checks
 End Prep table
 Symbology---Diagnostic Markers
 Date/Time Format
The only model data that cannot be applied to existing models is the Default Active Segment
Data and the Level and Color options, which should not be revised after piping models have
been created.
The Revise Equipment Data function includes settings for the equipment graphic symbology and
whether or not the approved or unapproved reference data is used. Changes made here affect
the equipment model seed file; therefore, any required changes should be made before creating
any equipment areas.
The Revise Drawing Data function includes settings for graphic symbology, label text sizes, and
whether or not the approved or unapproved reference data is used. Changes made here affect
the drawing seed file; therefore, any required changes that cannot be propagated to existing
drawings (see the following list) should be made before creating any drawings.
The Propagate Drawing Data function allows selected seed file settings to be applied to existing
drawings. You can propagate the following Type 63 data to existing drawings:
 Label Text Sizes
 Reference Database File Specifications
 Mass Annotation Data
 PDS Drawing Annotation Category Data
 User-Defined Drawing Annotation Category Data
 Hidden Line Data
 Coordinate Label Data
 Prefix/Suffix Data for Coordinate Labels
 Miscellaneous Label Data
 Date/Time Format
The only drawing data that cannot be applied to existing drawings is the Drawing Category data,
which should not be revised after drawings have been created.
The Revise Interference Check Data function includes settings for clash construction tolerances
and assignment of clash responsibility by discipline. Changes made here affect the project
marker file, therefore any required changes that cannot be propagated to existing area marker
files (see the following list) should be made before creating any models.

The Propagate Interference Check Data function allows selected seed file settings to be applied
to existing area marker files. You can propagate the following Type 63 data to existing marker
files:
 Construction Tolerances
 Responsibility Matrix
 Envelope Emulation Data
 Clash Plot Graphics Option
The Report of Seedfile Data function allows you to produce a report of all seed file settings. This
report can be very useful when setting up a distributed project.
Plant Monument
The plant monument defines the origin of the Plant Coordinate System (PCS), which may or
may not coincide with the origin of the MicroStation coordinate system. See the PDS 3D Theory
User's Guide for information.
If you will not run Interference detection by Area for this discipline, then the toggle can be set to
No Interference Management Design Area. This will cause the software not to create the area
marker file.
If predefined volumes are not used for interference detection, then the predefined volume can
remain 0,0,0. Enter a Design Area Name, and press RETURN. Enter a Description, and press
RETURN. Click √ to create the design area.
In a similar manner, areas for other disciplines can be created.

3D Models
After you create design areas, you can create models within these areas. From Project
Administrator, click Project Environment Manager > Create > Create Model. Click the
discipline, and then click √. Choose the area from the next form, and click √ to display the
Create Model Data main menu.
In addition to the Model Number, Model Name, and Model Description, the Model Directory
and Workstation/Server Name must also be entered. Default values for Model Directory, and
Workstation/Server Name can be established using the Model Setup function. This is already
specified if you created the project using Express Project Creation.
For workshare projects; that is, projects with a Site ID defined, the Site ID field allows you to
specify which work site owns the model.

From the Project Environment main menu, click Model Setup and the discipline for which you
want to establish a default directory for the creation of new models. The form has been
completed to follow the example started earlier.
The Color, Style, and Weight toggles allow you to establish default reference model symbology
for the selected discipline. The use of these settings is described in the Model Setup section of
the Project Administrator (PD_Project) Reference Guide. Note that the information for the
Structural and Raceways disciplines has already been set.
For the Model Directory setting, you can enter either the full path or the share name. For
example, you could enter h:\projects\project1\models\piping or \project1\models\piping. In either
case, the parent directory should be shared. For more information, see Creating Project
Directories and Required Shares (on page 54).
Click √ to write the default model file location into the PD schema.

Returning to the Create Model Data form, the information entered in the Model Setup Data
form is reflected in the Model Directory and Workstation/Server Name fields.
A Model Number (which results in a default Model Name) and Model Description can be
entered. A Model Status can be selected by clicking the Model Status field. This reads a list of
available model status conditions from code list 1605 in the Standard Note Library.
Standard Note Library

The Standard Note Library contains code list information used in many fixed-choice situations.
As an example, you do not want the users to be able to enter their own Model Status in the form
shown above---you want to restrict them to a list. This eliminates typographical errors and
reduces database storage requirements. Rather than storing the text associated with the word
"Undefined", an integer representing its position in the code list is stored.
The Standard Note Library is listed in its entirety in Appendix B of the Reference Data Manager
(PD_Data) Reference Guide. To examine, edit, or modify the delivered standard note entries,
use the Standard Note Library Manager (under the Reference Data Manager button). Click
Revise on the Standard Note Library Manager main menu to display a list of all delivered
standard note types. Scroll down to standard note type 1605 (Model Status), click it, and then
click √ to display a listing of the available Model Status choices. Additional information regarding
the use of the Standard Note Library Manager can be found in the section having the same
name in the Reference Data Manager (PD_Data) Reference Guide.

The following figure shows the completed Create Model form for this example:

Click √ to display the Design Volume Coordinate System Definition form.
In addition to the plant monument, PDS supports the use of a Design Volume Coordinate
System (DVCS). See the PDS 3D Theory User's Guide for more information.
The DVCS for a model can be changed after it has been created. In versions 7.0 and
later, the plant monument can be changed with the Update Plant Monument function even
after the model or project has been created.

Database Tables for 3D Models

Piping and Equipment models have database tables associated with them (created in the DD
schema) that must be created. If the database tables do not exist, PDS will not display the
models in the list of available models. After creating Piping or Equipment models, click Create
Database Tables from the Create Options main menu. Other disciplines do not require this
step.
Typically, a delayed submission is not required for this type of batch job. The batch job is
submitted to the Pdcreate_model queue. Check in Batch Manager to see that the job is in the
queue and is running. When finished, a log file named crtmodel.rep is written into the temp
directory (or mailed to you if PDS batch mail is set up)---a sample follows:
Piping Files Processed :
Created Model p1
Created Model p2
Equipment Files Processed :
No Models found in discipline to process
Model Creation Completed
Elapse time = 2:15
CPU time = 2:14
Make sure that all models that were created have their database tables created;
otherwise, they are unusable. Performing this operation more than once will not result in the
creation of duplicate database table. Only those models that have not had their tables created
will be processed.

Model Creation for Other 3D Disciplines

The creation of Equipment models follows the same procedure as that for the creation of Piping
models.
Other disciplines (FW/MDR, EE, HVAC, ARCH) do not have separate database tables in the DD
schema associated with them. If you create a new model for one of these disciplines and then
run the Create Database Tables operation, no models will be listed in the log file. This is normal.
Creation of model files for HVAC, Architecture, and any user-defined disciplines is not possible
through PD_Shell---the models must be created using the non-PDS application (Project
Architect, PE HVAC, and so forth) and then located through PD_Shell. To do this, create an
area and a model, and in the Create Model form, specify the location of an existing HVAC or
Architecture model. PDS will create an entry in the PD schema (specifically pdtable_113). These
models can then be used by PDS as reference files, and in some cases for interference
detection.
Non-PDS models cannot be opened through PD_Shell.
3D Design Data and the Database

When working in PD_Design, information about piping segments and components is written into
the DD schema tables associated with that model at the time these items are placed in the
model. The Database Verification Manager operation verifies that the graphics and the database
are in agreement.
When working in PD_EQP, information about equipment and nozzles is not written into the
database at the time the information is placed. This information is not normally required, but
information from the equipment models can be loaded to the DD schema for users' reporting
purposes using the Load Design Database function in the Equipment Modeling Options main
menu. PDS does not use the Equipment data in the DD schema. Instead, the data is read from
the user data attached to the MicroStation graphic elements.
It is important to understand that the intelligence associated with equipment models is stored in
the design file, but this is not the case for piping models. If the contents of the DD schema are
lost the piping models will lose their intelligence. Because of this, it is important that backups of
the database be made using PDS Archival or some other method.
2D Disciplines
The 2D disciplines (2D, PID, PFD, IDM) support the use of drawings that are graphics only or
graphics + database. A drawing created in graphics only mode can be attached to the database
at a later time if required.
See Also
Creating a Graphics-only Drawing (on page 126)
Creating a Database Drawing (on page 127)

Creating a Graphics-only Drawing

After you have copied the example.gpr file into your project directory, edited/renamed it, and
specified its location in the 2D Set Options form (see Locating the proj File from Client Nodes --
PDS 2D), you can double-click the Create Drawing icon in the PDS 2D Applications program
group to display the Create Graphics Only Design File dialog box.
If there are syntax errors in the .gpr file, it will not display in the Graphics Only Project Files
list. From the P&ID Seed File list, you can choose seed1.dgn or seed2.dgn---seed2.dgn has a
border, while seed1.dgn does not. Click Task, and enter the full path of the drawing to be
created. You can use Universal Naming Convention (UNC) file names in this field. The drawing
name should have a .pid extension so that it can be brought into the database if required.

To open the graphics-only PID drawing, double-click the Graphics Only icon in the PDS 2D
Applications program group to display the Graphics Only dialog box.
Click your Graphics only project file from the list, and click Browse to find the drawing to be
opened---its full path displays in the Design File path. Click OK to start MicroStation and open
this drawing.
Creating a Database Drawing

Before creating a database drawing, you must create a unit. PDS 2D units serve the same
function as PDS 3D areas---to allow related drawings to be grouped together. From the PDS 2D
Applications program group, start the Database Environment application. If the Database Proj
File has been correctly set, your project will display in the list. Click your project from the list,
select PID as the Task, and click OK to enter the database environment. MicroStation starts,
and the 2D reference data and RDBMS are initialized. After initialization has completed, from
the Env command on the menu bar, click PDS 2D > Show Active Project. For the example
project, the following form displays.

From the Env command on the menu bar, click PDS 2D > Show Units---you should get a
warning that no units were found. Dismiss this warning to display the Units form.
If you are running PDS2D on a computer that has more than one CPU, the environment
variable MS_PROCESSORS must be set to 1.See the PDS2D README file for details.
From the Env command on the menu bar, click Commands > Create. You are prompted to
Select entry to create. Click the Units form in the area where the asterisk (*) displays. The gray
buttons to the left are called row select buttons and should not be used at this time. After
clicking here, you are prompted to Select the project. Click the project name in the Project form.
Do not use the row select button---click on the project name. The Unit for Project form displays.
Enter information in the right-hand side of this form, pressing RETURN after each entry. After
completing all three fields, click Accept from the Env command on the menu bar to save the
entry. The unit is created and appears in the Units form.

From the Env command on the menu bar, click P&ID > TDB > Show Drawings to create a PID
drawing for this unit. A warning displays that no drawings were found. Dismiss this to display the
PID Drawings form.
From the Env command on the menu bar, click Commands > Create. You are prompted Select
entry to create. Click the area underneath the column heading Drawing no (do not use the row
select gadget) on the PID Drawings form. You are then prompted to Select Unit gadget. Click
your unit code in the Units form to display the Drawings for Unit form.
The following attributes are filled in with default values:

 Drawing Title
 Task Name
 Seed design file number
 Creation date
 Current version number
In this example, the following values have also been set. Press RETURN after entering each
value.
Drawing number pid_1 system converts name to upper case

Design file pid_1.pid must end with .pid extension
number
Network address cadsrv server where project is located
Path name c:\testprj\models directory created for these drawings
\2d
Creator Initials (your initials)

Click Accept from the Env command on the menu bar to create the PID drawing. The drawing
displays in the PID Drawings form, and the .pid file is created in the specified directory.
To enter graphics, click Env > Commands > Edit Graphics. When prompted Select entry to
edit, click the name of your drawing in the Drawing no column of the PID Drawings form. Do
not use the row select gadget.

SECTION 13
System Administrator Responsibilities

This section describes a number of different tasks that are typically the responsibility of the
System Administrator.
In This Section
Plotting in the PDS Environment ................................................... 131
Modifying Batch Queues for Redirected Processing ..................... 135
Access Control ............................................................................... 144
Creating Backups and Maintaining a Backup Schedule ................ 148
Creating and Maintaining Distributed Projects .............................. 158
Plotting in the PDS Environment

Submitting a plot though PDS results in a batch job being submitted to a queue that can be
viewed using Batch Manager. This batch job will send its output to a specified printer. In the
Windows environment, Print Manager handles spooling jobs to the printer. Plot jobs submitted to
a Windows batch queue open the design and reference files, prepare the I/Plot metafile, and
send this output to the I/Plot client software. The I/Plot client software passes the metafile
across the network to the I/Plot server software to be plotted. The I/Plot server software
communicates with plotting devices through print connections.
See Also
My Computer versus Network Printer Server (on page 131)
Use of My Computer (on page 132)
Use of Network Printer Server (on page 133)
The queue_descript File (on page 133)
Application-specific Considerations (on page 133)
My Computer versus Network Printer Server

Windows printers are created using the Add Printer wizard in the Printers folder. There are two
choices available, My Computer and Network. Printers created using My Computer are called
created printers and those created using Network are called connected printers. It is extremely
important to understand the difference. If you encounter plotting problems and call Intergraph
support, this is one of the first questions you'll be asked.
A node with a created printer has everything required to communicate directly with the printer
loaded locally, no other node is required to accomplish the connection. A node with a connected
printer only has a pointer to a printer that was created and shared on another node.
A connected printer is a property of the user you are logged in as at the time the connection was
made. If you log off and back on as a different user, the printer connections made by the
previous user are not known. A created printer is known to all users on a node, that is to say it is
the property of the node and not the user.
The account mapping specified in Batch Manager will depend on whether or not you use
connected or created printers. If you are doing batch plots through PDS and are using
connected printers, each user must be mapped to their own login (PDS\john = PDS\john)
because the connected printer is a property of the current user.

If you are doing batch plots through PDS and are using created printers, user can map to a
generic user (PDS\* = PDS\pdsbatch). This is acceptable since the created printer is a property
of the computer, and therefore known to all users of that computer.
If you do not do batch plots through PDS but submit plots directly using the I/Plot dialog box,
then the generic mapping as described for created printers can be used.
Use of My Computer
The My Computer option creates a printer that can be shared so that other nodes may connect
to it. The use of My Computer requires that I/PLOT client, I/PLOT server, and the printer driver
be loaded on the local node.
1. Click Start > Settings > Printers.
2. Double-click Add Printers.
3. Select My Computer then click Next.
4. Enter a name, and select the correct driver from the list. As an example, an HP Laserjet
4MV, is connected directly to the network. To communicate with this particular printer, the
DLC protocol must first be loaded from Control Panel > Network.
Do not use spaces in printer names. For example, use hplaser instead of HP
LaserJet. PDS supports up to 14 characters in the printer name.
5. Select the appropriate driver from the list (in this example, the HP LaserJet 4MV), and type
a description. This description will be visible from Printer > Properties. If it is shared, this
description will be visible when others try to connect to this printer.
6. Click the Print to port. If the printer is directly connected to the node, you would click the
corresponding local port (COM1, LPT1, and so on). If it is a network printer, you would click
Other and then the network type (Hewlett-Packard Network Port in this example). For the
HP network printer, a MAC address would be chosen from the list, and other printer-specific
options could be set before proceeding.
7. Choose whether or not to Share This Printer on Network. If you are sharing the printer,
type a share name, and optionally type a description.
At this point the printer configuration is complete. The printer is visible from the Printers
folder. You should test the printer connection by printing to it from a text editor or by plotting
to it from I/Plot.
For plotters connected directly into the network or to a Windows system, the Form setting
should be examined and changed from its default value to match the true size of the paper
used in the plotter.

Use of Network Printer Server

When connecting to a shared network printer, the Network Printer Server option creates a
printer connection that is usable only by the active user. In this configuration, only I/PLOT client
is require on the machine.
Connecting to a Printer Shared from a Windows Node

1. Click Start > Settings > Printers.
2. Double-click Add Printers.
3. Select Network printer server, then click Next.
4. If Expand by Default is turned on, the system will go out and look for shared printers. If you
have multiple domains on your LAN, you may have to browse to find the domain and node.
After the node has been located, double-click it to show the shared printers on that node.
5. Click the shared printer you want to use, and click OK to establish a connection to that
printer. Note that the printer name appears in Print Manager as \\nodename\printer.
Do not use spaces in printer names. For example, use hplaser instead of HP
LaserJet. PDS supports up to 14 characters in the printer name.
6. If you have more than one printer defined for your computer, you are prompted if you want
to make the new printer your default printer.
7. Test the printer connection by printing/plotting to it.
The queue_descript File

The queue_descript file is created in the project directory when the project is created. It is used
by PDS 3D to display the list of available queues for printing/plotting as well as those available
for running hidden lines and isometric extractions. It is used while working interactively as well
as by batch jobs spawned by PDS 3D. The options included in the queue_descript file are:
Pdprint - Used by all PDS 3D software for interactive/batch printing of reports and plotting.
Pddraw_plot - Used by the batch queues Pdplot and Pdplot_model to plot the drawing or piping
model selected.
Pdhline - Used to select the queue/node for the processing of the vector hidden line renderings.
Pdifc_plot - Used by the batch queue Pdclash_server to plot interference clashes.
Pdiso_plot - Used by the queue Pdiso_batch for automatic plotting of isometrics, or used by the
interactive Iso software to plot isometric extractions.
Pdiso_batch - Used to select the queue/node for the processing of batch isometric extractions.
Application-specific Considerations
This section describes plotting issues that are unique for a particular application.
PD_EQP Considerations
 All print options use the queue_descript file's list of available printer queues. (Pdprint)
 On Windows, if the PD_EQP software cannot find any of the queues listed in the
queue_descript file, a list of all available printer connections from the Print Manager
displays.
 All batch options use the queue_descript file's list of available batch queues. (Pdeqp_batch)
 On Windows, if the PD_EQP software is unable to find any of the queues listed in the
queue_descript file, the list of all available batch queues from the Batch Manager displays.

PD_Draw Considerations
 If you are submitting a batch job from a Windows node to a remote queue on another
Windows node, the list of available print/plot connections is derived from the remote
Windows node.
 If the PD_Draw software is unable to find any of the queues listed in the queue_descript file
and you are not crossing platforms, the list of all available printer connections from the Print
Manager will be displayed on a Windows node.
 In PD_Draw, you can specify a plot size and send it to a different size queue. If you specify
a small size to a larger queue (A size to an E size queue, for example), you should get the
small plot in the lower left corner of a large sheet of paper. If you specify a large size to a
smaller queue (E size to an A size queue, for example), you should get a correctly scaled
plot for the queue specified. In other words, the software will scale down to match the queue
size but will not scale up to match the queue size.
PD_Design Considerations
 For PD_Design, the software will scale as you specify and will then check to see if that size
will fit onto the paper for the queue that you specified. If it will fit, it will plot it to the scale that
you specified. If it does not fit, the plot fails, and an error message is generated.
PD_Review Considerations
 For PD_Review, the software will scale as you specify and then will check to see if that size
will fit onto the paper for the queue that you specified. If it will fit, it will plot it to the scale that
you specified. If it does not fit, the plot fails, and an error message is generated.
PDS 2D Considerations
 For PDS 2D, the software only displays the queues that match the size that you specified.
For example, if you are trying to get an A size plot, you should see only A size queues.
PD_ISO Considerations
 PD_ISO does not scale for plotting. The user predefines the iparm files and selects the
settings before plotting. The iparm file includes scale, size, queue name, and so on. The plot
queue name from the iparm file is displayed to the user who may use the displayed plot
queue or select another one.
 All printing and plotting options use queues listed under the Pdprint and Pdiso_plt headings
in the queue_descript file. On Windows, if the PD_ISO software is unable to find any of the
queues listed in the queue_descript file, the list of all available printer connections from the
Print Manager is displayed.
 All batch options use queues listed under the Pdiso_batch heading in the queue_descript
file. On Windows, if the PD_ISO software cannot find any of the queues listed in the
queue_descript file, a list of all available batch queues from the Batch Manager is displayed.
Additional information about the queue_descript file and some examples can be found in The
PDS queue_descript File (on page 287).

Modifying Batch Queues for Redirected Processing

When batch jobs are submitted, the processes execute on the client node. In some cases it may
be necessary to redirect these processes to a server node that has more compute power and
memory. A batch (local) queue can be changed to a pipe (remote) queue using the PDS Queue
utility.
1. While logged in as an administrator on the local node, start Batch Manager.
If all PDS queues are created local, the dialog box will display as follows:
The fact that the Queue Type is set to batch indicates that all queues are local to this node.
2. Exit Batch Manager and start the PDS Queue utility. In order to create Queues on a
computer using UAC, you must right-click the PDS Queue utility and select Run as
administrator.
3. You may get a message that All Products Have Queues Created. Accept this warning.
The Queue Creation utility displays Reading information from the queue.lst file and the
local machine.
The queue.lst file is not to be confused with the queue_descript file. The queue.lst file is
located in the same directory with the proj file, and is used by the PDS Queue Creation
utility.

The PDS Queue Creation utility dialog box displays.
When this dialog box displays, all products are dithered (in this example) because the PDS
Queue Creation utility has determined that queues for all products have been created.
4. By turning on Enable all for configuration, all products become available.
5. Select the product whose queues will be reconfigured (in this example, PD_Clash). After
clicking the product, you can click the list by the Queue Name field to display the list of all
queues that product uses. If ALL is selected, all of the queues that appear in the list will be
reconfigured.
6. In the next figure, you can see that the Pdclash_server queue has been chosen to be
reconfigured, the Remote Node box has been checked, and the name of the server has
been entered.

Note that when the pipe queue is created, neither the existence of the remote node
nor the existence of the corresponding batch queue are checked; you must be certain that
the server name is correct and that the corresponding batch queue exists on the specified
server.
If the queue already exists, the software turns on Overwrite Existing Queue. You must
leave the setting turned on to re-create the existing queue as the new pipe queue.
7. Click OK to display the following message regarding the queue.lst file:
When creating a pipe queue to a remote node, clicking Yes on this dialog box will write
information for the specified queue(s) into the queue.lst file. By default, the queue.lst file has
entries that look like this:
[PD_Clash Queues]
node=
When a client node that is using this proj file creates a pipe queue used by this discipline
and saves the information to the queue.lst file, the information will be changed. Considering
the example of the Pdclash_server queue that was created as a pipe queue to the node
CADSRV, the PD_Clash entry in the queue.lst file would now look like this:
[PD_Clash Queues]
node=
PDclash_server=CADSRV
When another client node is creating PD_Clash pipe queues using the PDS Queue
Configuration utility and Read data from ASCII file has been selected, the node CADSRV
will appear in the Remote Node field. In this manner, the System Administrator can create
all required pipe queues from one client, change the permissions of the queue.lst file to read
only, and then other clients will see the preferred location to create their pipe queues to.
Changing the permissions of the queue.lst file to read-only will not stop clients from creating
pipe queues to other nodes, but it will show them where they should be created to and also
stop them from altering the information in this file.
Some queues are shared by more than one application. For example, the PDreport queue
is used by PD_Clash and PD_Projec as well as PD_Report. If PD_Clash pipe queues are
created, the information for the PDreport queue will also appear in the PD_Report and
PD_Projec sections of the queue.lst file.

8. After creating the pipe queue using the PDS Queue Creation utility, go back into Batch
Manager and make sure that the queue was successfully created to the correct destination.

With the queue selected as shown above, click Queue > Properties from the menu bar, then
click the Destinations tab to see where this pipe queue's destination is.
This is a quick way to check where batch jobs sent to this queue will be processed. It is possible
to add additional destinations to this pipe queue; if the first destination in the list is disabled, the
next one will be used. See the on-line help for additional information.
After the pipe queue has been created, the following items should also be checked to make sure
the pipe queue can be used successfully:
Does a batch queue by the same name exist on the specified server?
A batch queue with the same name must exist on the server. In this example, the
PDclash_server batch queue must exist on the node CADSRV.
Has compatible account mapping been set up?

This is where the use of domain users and groups is critical! Consider the following example:
Client node = PDS1
Logged in user = PDS\mary
Batch services account mapping = PDS\* = PDS\pds
Server node = CADSRV

Batch services account mapping = PDS\* = PDS\pds
File permissions on the project files are:
Everyone Read
PDS\Administrators Full Control
PDS\Domain Users Change
PDS\pds Full Control

When PDS\mary submits a batch job on node PDS1 which is piped to the same queue on the
node CADSRV, she will be mapped to the PDS\pds user. Because this user has access to the
project files the batch job will complete successfully.
Can the server access the correct schemas file?

Once the batch job starts processing on the server, it will need to attach to the required
databases. This means that the server must be able to find the correct schemas file. If all nodes
are using the same schemas file, then it may simply be a matter of performing the Locate
Schema File operation on the server and locating the shared schemas file. If the batch job
cannot attach to the required database an error similar to the following will be seen in the error
log (probably located in the c:\temp directory on the server):
*******************************************
* RIS Error: RIS_E_UNKNOWN_SCHEMA (0x8a94a142) *
* *
* default schema pd_xxxxxx *
* *
* No such schema was found in the schema file or *
* a mismatch in the schema password. *
* *
****************************************************
If different schemas files are in use, it may be necessary to use an environment variable,
RIS_PARAMETERS, to tell the server which schemas file to use. See Setting the
RIS_PARAMETERS Environment Variable (on page 141), for a description of this.
In addition to problems finding the correct schemas file, the batch job may have problems
accessing the required project files. This typically happens when a local project is being used
with local batch queues, and later the queues are change to pipe queues. Because the project
directories have not been shared on the local node, the batch job running on the server cannot
access the project files. In this case, the batch log is typically empty. Items to check are:
whether or not the correct directories have been shared, what the permissions are on the share,
and what the permissions are on the files being shared.
The best way to test redirected batch processing is to start Batch Manager and use the Server >
Connect command to connect to your remote server and display its queues. When entering the
server name preface it with \\ (for example, \\CADSRV). Arrange the two windows so that both
the local pipe queues and the remote batch queues can be seen. With this set up, submit a
batch job. Then, quickly switch to Batch Manager to see that the request made it to the server.
When the batch job is finished, the output will be sent to the c:\temp directory (or wherever the
TEMP environment variable is set to) on the server. See Log Files Produced by PDS Batch Jobs
(on page 179), for a complete listing of log files produced by PDS batch jobs.
See Also
Setting the RIS_PARAMETERS Environment Variable (on page 141)
Configuring the PDS Batch Mail Utility (on page 142)

Setting the RIS_PARAMETERS Environment Variable

In most cases, where a single schemas file is in use by all nodes, this environment variable
does not have to be set. If multiple schemas files are in use, then this environment variable will
need to be set to tell the server where to find the correct schemas file.
When a RIS-enabled application needs to access the database, it looks in the parms file in the
\win32app\ingr\share\risxx.xx directory to find out where the schemas file is. This file can point to
only one schemas file. For example, if the schemas file used by the majority of the PDS projects
is located in the c:\ris directory on the server, then you would log on to the server, and do a
Locate Schema File operation, and point to this file. If another schemas file is being used for a
different set of projects, a copy of the parms file that points to that schemas file should be copied
to the server.
For example, the majority of the projects use the databases listed in the schemas file located in
the c:\ris directory on the server. However, one project uses a different set of databases listed in
a schemas file on Mary's node in the c:\ris directory on her node (PDS1). For her to be able to
submit batch processes to the server, the server must know how to get to these databases. A
copy of the parms file from Mary's node could be copied to the c:\ris directory on the server and
named mary_parms. On Mary's node the environment variable RIS_PARAMETERS would then
be set to c:\ris\mary_parms.
When a batch job is sent from Mary's node to the server, the value of RIS_PARAMETERS will
also be sent to the server. When the batch process needs to attach to a database, rather than
using the parms file in the \win32app\ingr\share\risxx.XX directory (on the server) to find the
schemas file, it will look in the location specified by RIS_PARAMETERS (in this example,
c:\ris\mary_parms). This parms file points to the schemas file back on Mary's node, and the
required databases will be located.
However, setting RIS_PARAMETERS not only affects batch jobs, but also interactive jobs. Once
RIS_PARAMETERS is set to c:\ris\mary_parms, then when Mary starts PDS interactively RIS
will look in the same place on Mary's node. Therefore, a c:\ris directory must be created on
Mary's node and the same parms file copied there and renamed to mary_parms.
All of this will work just fine provided that the value of RIS_PARAMETERS makes it to the server
unaltered. The following factors must be considered:
 When the batch job is received by the server, the Batch Services account mapping on the
server is consulted to see which user this job will run as. In this example, PDS\mary is
mapped to PDS\pds. If, on the server, the PDS\pds user has a user environment variable
named RIS_PARAMETERS and it is set to a different value, then this value will be used,
and the correct databases will not be found.
 Assuming the batch job has been received by the server and the PDS\pds user does not
have a conflicting user environment variable setting for RIS_PARAMETERS, things can still
go wrong. If a system environment variable (used for ALL users) named
RIS_PARAMETERS has been set to a conflicting value, then this value will be used, and the
correct databases will not be found.
The use of the RIS_PARAMETERS environment variable must be carefully thought out so that
its value, as set on a client node, is not overwritten after it reaches the server.

Configuring the PDS Batch Mail Utility

When batch jobs are redirected to the server, the resulting log files are typically placed in the
c:\temp directory on the server. You can also have the log files from certain batch processes to
be mailed to a specified user.
The PDS Batch Mail utility supports the following mail methods:
 MAPI
 SMTP
SMTP is more convenient because it sends mails directly to users while MAPI requires users to
periodically check the event log for the information.
Security controls from Microsoft Outlook 2003 and later prevent emails from being sent
automatically through MAPI; therefore, you must use SMTP when configuring the PDS Batch
Mail utility for Microsoft Outlook 2003 and later.
Enabling the PDS Batch Mail Utility through MAPI

1. The server must have the capability to send mails from the user name that the batch job is
mapped to. For example, if batch jobs are mapped to the user PDS\pds, then you should be
able to log in as that user on the server and send mails.
2. On the server node, Batch Services must be loaded with the Interact with Desktop option,
which results in a collapsed DOS window at the bottom of the screen whenever a batch job
is running.
3. The following environment variables must be set (either in Control Panel or in the .profile):
PDS_MAIL_RECIPIENT---must be set to an address recognizable by the mail provider. The
easiest way to validate this setting is to send mail to the user, and specify the same string
used for the environment variable in an interactive mail session.
PDS_MAIL_LOGIN and PDS_MAIL_PASSWORD---must be set if the specified user does
not have an active mail session for the same user account. For example, if you stay logged
in to your mail provider all day in the same account that the batch jobs are mapped to, you
do not have to set these two variables. In addition, PDS_MAIL_PASSWORD is required
only if you mail provided requires it when you activate a mail session.
Setting environment variables on Windows is accomplished using Control Panel > System.
As an example, batch jobs submitted by Mary while logged in on her node as PDS\mary are
mapped to PDS\pds and then redirected to CADSRV. On CADSRV, all batch jobs are mapped
to PDS\pds (*\* = PDS\pds). The pds user logged in on the server and set the
PDS_MAIL_RECIPIENT, PDS_MAIL_LOGIN, and PDS_MAIL_PASSWORD environment
variables as user environment variables. These were all set for Mary's email address (mmartin).
The pds user also verified that while logged in on the server that email can be sent to user
mmartin. When batch jobs are initiated by Mary on her node, she will now get email that
includes the batch job log file.
There is one problem with this setup---because all batch jobs are mapped to PDS\pds on the
server, Mary will be receiving the email when anyone submits a batch job to the server. For
each user to receive the email from their own batch jobs, the user's true identity must be
preserved throughout the course of the batch job. In this case, rather than:
Mary's node PDS\* = PDS\pds
Server *\* = PDS\pds
You would need:
Mary's node PDS\* = PDS\mary
Server PDS\mary = PDS\mary

Mary's node PDS\mary = PDS\mary

Server PDS\mary = PDS\mary
In the first case, Mary will receive the email from any batch job initiated by a PDS domain user
while logged in on her node. In the second case, Mary will receive only the email resulting from
batch jobs that she initiates.
One additional note for those using Microsoft Exchange Server as the email provider, the
PDS_MAIL_LOGIN environment variable must be set to the profile name (as seen using
Control Panel > Mail and Fax > Show Profile).
Enabling the PDS Batch Mail Utility through SMTP

To use the SMTP mail notification, your mail system must be able to handle SMTP mails. In
some systems, a program called SMTP gateway provides this functionality. The gateway allows
mails to be sent between users running various mail packages. Contact your mail administrator
to see if your installation supports the SMTP mail notification.
In addition, you must set the PDS_MAIL_SMTP_ADDRESS environment variable. When
sending mails, the utility checks this variable to determine whether to use SMTP. If it is not set, it
will use MAPI.
The PDS Mail Utility must be able to recognize the SMTP address to which the mails are sent.
The following methods are available to provide this information. The method you choose
depends on whether a direct or an indirect SMTP address is available for the receiver. For
example, if the mail address is jsmith@mymachine.b101.mycomp.com, you can use the direct
method. If you want to use the address jsmith@mycomp.com, an alias for the previous address,
you must use the indirect method. Contact your mail administrator to determine your mail
situation.
Direct SMTP Mail Support
If you want to send mails to a direct SMTP address, then set the PDS_MAIL_SMTP_ADDRESS
environment variable with this address. The PDS_MAIL_SMTP_HOST environment variable is
not required.
Indirect SMTP Mail Support
If you want to send mails to an indirect SMTP address, then set the
PDS_MAIL_SMTP_ADDRESS environment variable with this address, and set the
PDS_MAIL_SMTP_HOST environment variable with the SMTP host (the computer that is
running SMTP).
When SMTP sends mails, it displays the sender's address as PDSMAIL [username@hostname]
where username is the user logged onto the system and hostname is the name of the system
where the job is running.

Access Control
The PDS Access Control Manager is fully documented in Chapter 12 of the Project
Administrator (PD_Project) Reference Guide. This section provides a brief description.
PDS Access Control Manager restricts access to PDS functions based on a PDS Access
Control user name. Users enter their PDS Access Control user name at the PD_Shell main
menu and then select a project. Based on the user name and the project selected, certain
options are enabled. The PDS Access Control user names do not have to coincide with the
operating system logins. For example, a user may be granted access to a PDS function by
virtue of their PDS Access Control user name, but yet may have insufficient privileges to perform
the selected function based on their operating system login. The System Administrator should
make sure that users operating system logins and PDS Access Control user names offer
equivalent privileges.
Information about PDS Access Control is stored in two files---the PDS_user_id file and the
PDS_access file. The PDS_user_id file is located in the directory where the proj file is located
and contains the list of all usernames. The PDS_access file is unique for each project and is
located in the project directory. In this manner, a single set of users can be created, and those
users can be granted different access permissions for each project listed in the proj file.
If access control is not used on a set of projects, there will be no PDS_user_id file in the
directory where the proj file is stored. In the PD Shell form, type system in the User ID field to
display the following form:

The Initials, User Name, and Password fields are initially empty and have been completed as
shown in this example. Press RETURN after you finish each field. Click √ to set the password
for the System user and create the PDS_user_id file.
Make sure to write down the System user name password---there is no way to recover
this password if you forget it.
If you forget the System user name password, you will have to delete the PDS_user_id file and
start over. Once you do this, the user IDs in the new file may no longer match the user IDs as
stored in the PDS_access file in the project directories, so they will have to be deleted and user
privileges for each project will have to be set again.
After setting the password for the System user, the Access Control Manager form displays.
At this point you must enable access control for the selected project. Click Enable Access
Project Control, and select the project name from the Projects list. The following form displays:
Click √ to enable access control for this project. PDS Access Control user names must be
created next. For this example the following users will be created:

User ID Initials User Name
pipedes PD Piping Designer

pipeadm PA Piping Administrator
eqpdes ED Equipment Designer
eqpadm EA Equipment Administrator
In the Access Control Manager form, type the initials for the user to be created (in this
example, PD) into the Initials field, and press RETURN. Type pipedes as the User ID and press
RETURN---note that the Password field disappears. This is because the system manager does
not set the passwords for the users; each of the users must set their own password. This is
done when each the user enters his or her user ID into PD_Shell for the first time.
The User ID will appear in a number of different places if PDS Access Control is enabled.
This includes File Lock Manager (will show who a file is locked by) and reports produced by
PD_Report (will show as whom the report was requested by).
After entering the Initials and User ID, type the User Name, and press RETURN. At this point,
a project name must be selected from the list of Projects because access controls for a user are
set on a per-project basis. Select the project from the list (in this example, testprj), and then set
the permissions for this user. In the Categories field, select which discipline this user will need
access to---in this case piping. When you select a Category the Privilege Levels field displays.
By selecting Categories and Privilege Levels for a user, certain functions in PD_Shell and the
other PDS 3D applications are made available to that user. A complete explanation of which
options are enabled by each choice are described in the Authorization Data section of the
chapter on Access Control in the Project Administrator (PD_Project) Reference Guide.

Because this user is the Piping Designer, click Design, Propagation, Reporting/Plotting, and
Checking/Comparison in the Piping category. After turning on these privileges, another
Category can be selected from the list and additional Privileges for that category granted (the
Privileges for each Category appear the same, as shown in the Privilege Levels list). For
example, you may want to grant the Piping Designer privileges in the Project Data and Pipe
Stress Analysis categories as well. Note that privileges granted to a user can be changed by the
System user at any time. After granting all required privileges to a user, click √ to create the
record in the PDS_access file which is stored in the project directory of that project.
Note that while you are in the PDS Access Control Manager, a file named PDS.lck is created in
the directory where the proj file is located. If another user attempts to run the Access Control
Manager while you are running it, a warning displays.
A common problem is that if Access Control terminates abnormally, the PDS.lck file may be left
behind, preventing other users from running the Access Control Manager. Removing the
PDS.lck file will remedy this situation---however, you should make certain that no one is actually
running Access Control Manager when doing this!
In a similar manner, you can create additional users and grant them privileges for the selected
project. We suggest that after creating or revising a user name you click the left bending arrow
to reset the form before creating or revising the next user. When finished, exit out of PD_Shell,
and then restart it. The project for which Access Control was enabled will no longer appear in
the list. One of the user names created earlier must be entered. If this is the first time a user is
entering PD_Shell, the password must be set and verified. After doing this, all the projects using
access control display (in red letters) with the list of other projects. When a project is selected,
PDS will read the information for that user from the PDS_access list in that project. PDS will
then make certain options available and grey other options out.

To remove a project from access control, you would remove the PDS_access file from the
project directory, and perform the Disable Access Control function while running the Access
Control Manager as the system manager.
See Also
Copying a Set of Users to Another Project (on page 148)
Copying a Set of Users to Another Project

A feature introduced in PDS 06.00 is the ability to report on the set of users for one project, and
use this report as a means of copying those users and privileges to another project.
To start this process, enter the PDS Access Control Manager as the System user. Click the
project having the access controls in place, and then click Create Report at the lower right
corner of the Access Control Manager form. Click √ to create a report named access.rpt stored
in the project directory for that project.
To copy these users and privileges to another project, enable access control for that project.
Copy the access.rpt file from the source project to the destination project, and then run Load
User Definition to create the users in the destination project. The PDS_access file is created in
the destination project. It has the same user names and privileges as the source project.
Creating Backups and Maintaining a Backup

Schedule
Backups of the PDS project files can be created using two methods:
1. Using PDS Archive to copy the project files and their associated database information to a
directory.
2. Using NTBACKUP to copy the project files to tape.
Backups of the RDBMS data associated with a PDS project can be created using three
methods:
1. Using PDS Archive to copy the project files and their associated database information to a
directory.
2. Using NTBACKUP to copy the database files to tape.
3. Using RIS or the database-vendor provided backup utilities to copy the database information
directly to tape or to disk.
The advantages and disadvantages of each method will be described. A complete description of
PDS Project Archive can be found in the PDS Project Administrator (PD_Project) Reference
Guide.
See Also
PDS Project Archive to Back Up Project Data (on page 149)
NTBACKUP or CPIO Backup of Project Data (on page 155)
PDS Project Archive to Back Up Database (on page 156)
NTBACKUP or CPIO Backup of Database Files (on page 156)
RIS Backup of Database (on page 157)
Database Vendor Backup of Database (on page 157)
Full versus Incremental Backups (on page 158)
Which Backup Methods Should I Use? (on page 158)

PDS Project Archive to Back Up Project Data

PDS Project Archive creates a complete archive of a project that can include the following
information:
2D and 3D project files (models and drawings)
2D and 3D reference data (libraries and seed data)
3D interference data
3D reports
SmartPlant Review data
Isometrics
Associated database data
The PDS Project Archive utility provides you with the option to archive all of this data or just
selected information.
Advantages
The PDS project archive is particularly useful if a single model or a single reference library
needs to be retrieved. Because PDS Archive uses risunload to automatically extract
information from the database, the information in the models and the corresponding information
from the database is backed up at the same time.
Disadvantages
The PDS project archive can be quite large depending on the size of your project. All information
and files recorded in the database must exist.
Procedures
PDS Project Archival is described in the Project Administrator (PD_Project) Reference Guide.
Additional tips are provided in the PD_Project README file. In a Windows environment, an
interactive project archival can be done to disk on the local node or on a remote node.
Interactive and Scheduled project archivals require a batch job, so make sure that the account
mapping for the user initiating the archive specifies a user who has access to the project files as
well as the destination directory for the archive.

Interactive project archival results in a project archive being created immediately. When
Scheduled Project Archive is run, no archive is actually performed. Instead, a set of files are
produced that will cause the project to be archived at specified intervals. As an example, the
Scheduled Project Archive form has been completed as shown in the following figure:

In the next form, select Backup on Hard Disk and specify a directory on the server CADSRV
(c:\archives\testprj, in this example). In the Project Archival Options form, select Project Data.
This causes the time interval gadgets to appear as shown in the following figure:

Rather than setting the archive time and interval at this point, continue selecting the parts of the
project you want to archive. When Model Data is selected, a form displays that allows you to
select the models you want to archive:

After making your choice, click √ to return to the Project Archival Options form. When you select
Drawing Data a form similar to that for Model Data appears. When you select 2D Project the
following form displays:
You must type the Base Node and Base Path before you make any other selections. In this
example, the Base Node is the server (CADSRV) and a valid path has been entered
(c:\archives\temp). When you select the first 2D archival option, the Base Node and Base Path
are validated. Every 2D archival option except Project Data brings up an additional form where
either all of the specified data or a subset can be selected. After selecting all needed 2D archival
options, click √ to return to the Project Archival Options form.
After you have selected any additional parts of the 3D project to archive, set the archival time
and frequency as the last step. The use of these options is described in the Project
Administrator (PD_Project) Reference Guide (DPDS3-PB-200030*). If you make a mistake
entering the time, you can reset the form by simply checking and unchecking an archival
category. After setting the archival time (in this example, 11pm each night), click √ on the
Project Archival Options form to create the scheduled archival files and Batch Services entry.
You will now find three files located in the directory specified in the Archival Creation/Revision
form:
archive_1.cmd
testprj
testprj_2
An entry is also created in Batch Services.
At this time, the file archive_1.cmd will be run using the PDSPERL shell. The archive_1.cmd file
can be examined with a text editor:

$ENV{'IFC_PROD'} = 'PDS';
$ENV{'PROJ_NO'} = 'testprj';
$ENV{'PROJ_FILE'} = 'c:\projfile\\';
$ENV{'PROJ_ADDR'} = 'cadsrv';
system 'echo pdsperl -S pdsqsub.cmd 4 pdarch.exe testprj.arc
c:\archives\testprj PDS1 1 | qsub -eo -o PDS1:c:\temp\testprj.arl -r
arc_testprj -x -q PDarchival ';
The system 'echo.... line whose purpose is to submit a batch job to the PDarchival queue. This
file can be interpreted as follows:
The project name is testprj and the proj file is on CADSRV in the directory c:\projfile (determined
from lines 2, 3, and 4). The file that specifies the archive options is named c:\archives\testprj and
is stored on node PDS1. The log file will be named c:\temp\testprj.arl and will be found on node
PDS1.
The file testprj is a binary file and cannot be examined with a text editor. The file testprj_2
specifies the archive options for the 2D project, and this file can be examined with a text editor:
2D_LOG 'pds1' 'c:\temp\' 'testprj.arc'
2D_BASEDIR 'cadsrv' 'c:\archives\temp\'
2D_IMPORT
2D_PROJ pds2d T
This file can contain many other options. The options to note at this point are the location of the
log file (c:\temp\testprj.arc on node PDS1) and the location of the 2D project archive working
directory (c:\archives\temp on node CADSRV).
When the Batch Services job starts at 11pm, it in turn runs the archive_1.cmd file. This file sets
environment variables and initiates a batch job. The batch job performs the archive and
produces the log files. For this to complete successfully, the configuration of the schedule
service and the Batch account mapping must be checked.
Jobs run from the scheduler are associated with a user name which must have a valid account
mapping established in Batch Manager. This can be seen by going into Control Panel >
Services and double-clicking on the Schedule service. The Startup Type should be set to
Automatic, and a user name should be specified. The default user name associated with the
schedule service is the System Account. This account may not map correctly to a valid user in
batch manager. An example is provided below:
Schedule service runs as System account on node PDS1
On node PDS1, account mapping is set as PDS\* = PDS\pds
When a job is initiated, it runs as PDS1\system user. Because this user is not in the PDS
domain, the batch job will not be initiated.
One option would be to use a *\* = PDS\pds account mapping in Batch Services so that the
system account will map to a PDS domain user name.
In this example, the schedule service has been set to run using the domain administrator user
name (PDS\administrator). This solves a number of problems:
1. The domain administrator (PDS\administrator) is automatically added into the local
administrators group when the client node joins the domain.
2. Because a PDS domain user has been specified for the schedule service, the scheduled
project archive will work because this user meets the PDS\* = PDS\pds account mapping in
Batch Services and because this user has access to all project files on the server.
In this example, the project being archived is on the server, and the batch process that will
create the archive of this project is run on a client node (PDS1 in this example).

Frequently, it is necessary to run the batch job on the server rather than on a client machine.
However, the server may not have a graphics console on it and it may not be capable of running
PDS interactively, such that the scheduled project archive cannot be created on the server. In
this case, the scheduled project archive can be created on a client node, the files can be moved
to a server, and the Batch Services job can be created on the server to run the copied files.
Checklist for Copying Scheduled Project Archive Files to Another Node:

1. Make sure the scheduled project archive runs successfully on the node where it was
created.
2. Copy the files from the client to the server (in this example, from c:\archives on PDS1 to
c:\archives on CADSRV).
3. Verify that the same user name is specified for the schedule service and that equivalent
Batch account mapping has been specified on the server.
4. Modify the archive_1.cmd file to reflect the new location. Changes from the original are bold:
$ENV{'IFC_PROD'} = 'PDS';
$ENV{'PROJ_NO'} = 'testprj';
$ENV{'PROJ_FILE'} = 'c:\projfile\\';
$ENV{'PROJ_ADDR'} = 'cadsrv';
system 'echo pdsperl -S pdsqsub.cmd 4 pdarch.exe testprj.arc
c:\archives\testprj PDS1 1 | qsub -eo -o PDS1:c:\temp\testprj.arl -r
arc_testprj -x -q PDarchival ';
The file has been modified to reflect the fact that the testprj file is on a different node in the
same directory. The log file will still be found in the c:\temp directory, but on the server node
rather than the client node.
5. Modify the testprj_2 file to reflect the new locations. Changes from the original are in bold:
2D_LOG 'cadsrv' 'c:\temp\' 'testprj.arc'
2D_BASEDIR 'cadsrv' 'c:\archives\temp'
2D_IMPORT
2D_PROJ pds2d T
The only change that has been made is to specify that the log file be put on the server rather
than the client.
Create a new Batch Services job on the server to create the archive.
It is suggested that you perform PDS Archives of active projects. This provides an easy way
to recover a single model or a single library as well as any associated database information.
This provides insurance against users accidentally deleting a project file or if a project file
becomes corrupted.
NTBACKUP or CPIO Backup of Project Data

The utility provided with the operating system can be used to make a backup to tape of the
entire project directory. On Windows, third party backup utilities are available which can also be
used for this purpose.
Advantages
The operating system-level backup is quick and will copy all project data. The retrieval process
is typically easier as well. This type of backup is also useful should you experience a disk failure.

Disadvantages
If the project is spread across multiple nodes some data may be omitted. The database
information will not be captured. Retrieving a single file may be difficult.
Procedures
The NTBACKUP utility can be driven from a command file. This command file can be run
regularly by creating an AT job to run it. An example job to back up all drives on the server is
shown below:
NTBackup Backup C: E: F: G: H: /D"Full Backup of C, E, F, G, H"
/L"c:\users\default\backup.log"
This will perform a full backup of all drives, label the volume as "Full Backup of C, E, F, G, H",
and put the log file in c:\users\default\backup.log. If this command were put into a file
(c:\users\admin\backup.bat, for example), this file could be run every morning at 3am using the
following command:
at 3:00 /interactive /every:M,T,W,TH,F,S,Su c:\users\admin\backup.bat
The NTBACKUP utility also supports incremental backups from a command line---see the
Windows documentation for additional details.
Note that if the database is running when the backup runs, the database files will be
skipped (as will any other files that are open).
We recommend that backups of the disk files be performed as insurance against disk failure.
Furthermore, all of the files associated with the database should be backed up together at a time
when the database is shut down. This provides insurance against database failure. How
frequently this is done is left to the discretion of the System Administrator.
PDS Project Archive to Back Up Database

The database information is automatically backed up as needed by PDS Project Archive.
NTBACKUP or CPIO Backup of Database Files

The utility provided with the operating system can be used to make a backup of the files that
comprise the database. On Windows, third party backup utilities are available which can also be
used for this purpose.
Advantages
Making an operating system-level backup of the database files is highly recommended. It is
useful should you experience a disk failure.
Disadvantages
If you ever need to use it to recover the database, everyone's work will return to the point in time
when the backup was made. Also, when the database is restarted it may not be synchronized
with the data in the models.
Procedures
See NTBACKUP or CPIO Backup of Project Data (on page 155). The database must be shut
down when its files are copied to tape.

RIS Backup of Database

The Intergraph RIS client product, includes the risunload and risload utilities, which can be used
to dump data out of the database or load it back in.
Advantages
A risunload file is portable. You can do a risunload from one type of RIS-supported database
and risload into another.
Disadvantages
To do a risunload or a risload, RIS must be functional and the schema must work (the Data
Definition operation from within RIS Schema Manager must not return any errors). If the schema
is broken, a risunload is not possible.
Procedures
The risunload utility can be run interactively or from a command line. However, there is no
reason to perform risunloads of the database (as a separate step outside of PDS archival)
unless you are moving between database types.
Database Vendor Backup of Database

All database vendors supply some type of backup tool with the database system. Many of these
tools can be run interactively or from a command line as part of a regularly scheduled backup
routine.
Advantages
Speed and security - the database vendor backup utility is typically very fast and can archive the
information for all databases in the system or just the data for a single PDS database. Also, if
the schema is broken and risunload cannot be used, the database-level export can still be done.
Disadvantages
Recovers the entire database or all information for a single PDS database. It is not possible (or
at least very difficult) to retrieve the data for a single model. This is also true for risload.
Procedures
Each database vendor includes a backup utility with their product. Some examples are listed
below:
Oracle exp and imp

MS SQL dump database and load database
All of these utilities can be run from command lines or from batch files using AT. If PDS archives
and disk file backups are being performed on a regular basis, performing database dumps may
not be necessary.

Full versus Incremental Backups

Another consideration is that many of the database-vendor backup utilities as well as the
NTBACKUP utility offer the ability to do incremental backups (backing up just those files that
have changed since the last backup was made). One strategy is to do nightly PDS archives and
a combination of full and incremental file backups such that each drive gets a full backup at least
once a week. The backups should be organized so that all files associated with the database
are backed up each night. On a Windows database server, this will require that the database be
shut down (because NTBACKUP will not backup open files).
Which Backup Methods Should I Use?

Regarding the backup methods described above, the general rule is the more of these you can
afford to do, the better. If you can do a PDS Archive, a database-level dump of the database,
and an operating system-level backup of the project files and database files every night you will
be able to recover from any type of system failure. However, performing these backups takes
time, and the projects should be inactive while all of these backups are being performed.
Experimentation will be required to determine how long these procedures take to run at your
site, and how many of them can be done during the time when the system is not in use.
Creating and Maintaining Distributed Projects

When multiple sites are working on a single project, there are two basic approaches to
coordinate the work between the various sites:
1. All sites work with a single copy of the project (at one site).
2. Each site maintains a local copy of the project and a master is maintained at a single site.
The first approach is the safest, since only one version of the database and project exist. For
this approach to be successful, the participating companies must all have access to high-speed
communications lines so that the delays introduced by the network are as short as possible.
Even with T1-type high-speed lines, if the participants are spread over a wide geographic region
this approach may not be feasible.
The second approach is more popular among existing PDS customers. The parent site creates
the project, performs any necessary database customizations, creates all areas and models
(even though these models may be empty), and then archives the project and sends it to each
of the other participants who then recover it (using PDS Inactive Project Retrieval).
As team members complete their portions of the work, they use PDS Project Archival to archive
just the models/areas they have worked on. This is sent to the parent, who then uses PDS
Import Project Retrieval to import the new versions of these models. If the remote site performs
a complete project archive, the parent site can still extract specific models using PDS Import
Project Retrieval.
Creating and maintaining distributed projects can be a complex undertaking, especially as the
size of the project grows. The new PDS user is encouraged to become active in the local PDS
Users Group and other forums where PDS users exchange ideas and tips about how to use
PDS efficiently.

APPENDIX A
RAID Configuration
All current Intergraph Intel based servers include Redundant Array of Independent Disk (RAID)
technology. RAID technology benefits Intergraph customers in two ways:
1. Reliability---RAID technology offers protection from disk failure for user data.
2. Performance---RAID technology allows data to be striped across multiple disk drives,
boosting performance on read operations.
The technology and concepts of RAID are complex. A full understanding is required to exploit all
the capabilities of the latest generation of Intergraph servers. This appendix covers the following
topics:
 I/O subsystem components.
 Explanation of different RAID levels supported by Intergraph servers.
 Hardware versus software implementation.
 Purchasing considerations.
 Configuring a RAID capable system for optimum database performance.
After reading this section, you should understand RAID technology and how best to apply it to
problems in your organization. Additional information regarding RAID, and Intergraph servers in
general, can be found at our home page http://www.intergraph.com.
I/O Subsystem Components

The disk subsystem consists of three logical components: disk drives, SCSI channels, and host
bus adapter as shown in the following figure:
Each component is a potential bottleneck for system performance. Using the most advanced
technology and making intelligent configuration decisions maximizes the I/O throughput of a
server.
Peripheral expansion bus

The most prevalent bus on large Intel-based servers is the Extended Industry Standard
Architecture (EISA) bus. The EISA bus is a 32-bit technology with a 33MB/second peak transfer
rate. The future for the peripheral expansion bus is the Intel developed Peripheral Component
Interconnect (PCI) standard. The PCI bus offers 133MB/second peak transfer rate and will meet
the industry needs for some time to come.

RAID Configuration
Disk controller
The standard for connecting disks to the controller is the Small Computer Synchronous Interface
(SCSI). A fast and wide SCSI-2 channel has a peak bandwidth of 20MB/second. Most
controllers use fast and wide SCSI-2, very few of the available drives are fast and wide, so the
full capability of the SCSI channel is not used. In a server, multiple SCSI channels are essential
for high performance. The ISMP22 server uses two PCI-based SCSI controllers, each with a
single channel. The ISMP5* or 6* uses a single EISA-based controller with five channels. High
performance controllers such as the one use in the ISMP5* or 6* series feature on-board cache
and support for RAID in hardware.
Disks
Despite continuing advances in density and performance, magnetic disk drives use technology
which has changed little in the last thirty years. A disk drive consists of one or more platters
which rotate at high speed and a collection of read/write heads which move over the surface of
the platters. Disk drive vendors usually refer to three measurements when specifying the
performance of a disk drive:
Average seek time---the time needed to get from one position on the disk to another. The worst
case for seek time is if the heads have to move the full radius of the platter and the platter has to
rotate almost a complete revolution before the heads are positioned correctly.
Average access time---a combination of the seek time and the time actually required to read
data from the disk.
Transfer rate---the rate at which data can be transferred from the drive to the controller.
Intergraph servers use fast SCSI-2 disk drives. A fast SCSI-2 drive can transfer data at a
theoretical peak rate of 10MB/second. In practice, drives can sustain about 4MB/second. The
SCSI-2 channel (fast & wide) offers a peak of 20MB/second. This leads to several conclusions
about performance in an I/O subsystem:
 For peak performance, a SCSI-2 channel should not support more than four disk drives.
 Two 1GB drives can offer better performance than one 2GB drive as they have a potential
transfer rate of up to about 8MB/second. A single 2GB drive is limited to about 4MB/second.
 Disk drives spread across multiple channels offer better performance than the same number
of drives on a single channel.

RAID Configuration
Intergraph Supported RAID Levels

Servers offer a variety of RAID and associated capabilities. Some are implemented entirely in
software, some in hardware, and some require a combination of both.
Before describing the different RAID levels supported platforms, it is necessary to explain some
technical terms.
Stripe size - The smallest block of data that is written to a physical drive. Typically this is 4KB.
Stripe width - The number physical drives being used for a logical disk stripe.
Read/Modify/Write - In RAID 5, if a write occurs which is less than the stripe size, then the
subsystem must read in data from a drive, merge it with the data to be written, and then
calculate parity. This leads to poor write performance in RAID 5 if most writes are smaller than
the stripe size.
Volume set - Windows supports the ability to concatenate space on drives to form a single large
logical drive. This is different from a RAID 0 stripe because the space is used sequentially. In a
volume set, data is written to the first drive in the set until that drive is filled. Then, data is written
to each subsequent drive until that drive is filled.
Write-back cache - Many modern disk controllers have several megabytes of cache on board.
Onboard cache allows the controller greater freedom in organizing scheduling reads and writes
to disks attached to the controller. Usually the controller allows a system administrator to control
the way in which the cache is used. In write-back mode, the controller reports a write operation
as complete as soon as the data is in the cache. This improves write performance at the
expense of reliability. If power fails or the system crashes, then data in the cache is lost,
resulting in damage to the file system.
Systems using write-back cache policy should be protected by an Uninterruptible Power
Supply (UPS) which reduces the chance of serious data loss.
Write through-cache - Opposite of write-back. When running in a write-through mode, the
controller does not report a write as complete until it is written to the disk drives. This reduces
read/write performance by forcing the controller to suspend an operation while it satisfies the
write request.
RAID 0
RAID 0 is the simplest type of RAID to implement. It is also known as striping. In RAID 0, data is
spread across multiple physical disks offering faster read/write performance than a single drive.
A three-disk stripe has approximately 3 times the bandwidth of a single drive because read/write
operations to the stripe can occur in parallel. The RAID 0 diagram shows how data would be
distributed in a three-disk stripe. The benefit of RAID 0 is performance, the prime disadvantage
is reliability. If a single drive has a Mean Time Between Failure (MTBF) of 50,000 hours, then
the MTBF for data on the stripe is:

RAID Configuration
For a three-disk stripe, the MTBF would be 12,666 hours. This RAID 0 limitation makes it
unsuitable for most applications requiring high-availability for the data. Because of the effect on
reliability, RAID 0 is only suited for environments where system uptime is unimportant.
RAID 1
RAID 1 is often referred to as disk mirroring. In RAID 1, physical disk drives are grouped in
pairs. Any data written to the first drive in the pair is also written to the second drive---which
halves the amount of space available for data. Because the chance of both drives failing
simultaneously is small, the chance of losing data to a disk failure is small. Because write
performance is governed by the performance of a single disk in RAID 1, it offers no benefits for
write operations. Read operations are improved because data can be read from either disk.
The disadvantage of RAID 1 is cost. Every MB of disk storage requires 2MB of actual disk
space.

RAID Configuration
RAID 5
RAID 5 combines the reliability of RAID 1 with many of the performance benefits of RAID 0. In
RAID 5, a parity block is calculated. The parity data in combination with data on undamaged
drives allows reconstruction of data on a failed drive. The figure below illustrates how RAID 5
organizes data on a three-disk stripe. The rule is that a data block and its corresponding parity
information are never written to the same physical device.
In the example, if drive 1 fails, then block 1 can be reconstructed from the block 2 and the parity
information for block 1&2. Similarly, block 3 would be reconstructed from block 4 and the parity
for blocks 3&4. The parity block on drive 1 can be reconstructed from blocks 5 and 6. Read
performance of a RAID 5 stripe is similar to RAID 0. In write operations, the performance is
degraded when compared to RAID 0 for two reasons:
1. More data is written. The controller (for systems using hardware RAID) or the operating
system (for systems using software RAID) must calculate the parity block and write the data
and parity block.
2. If the data being written involves modifying a block on any of the disks, then that block has
to be read in, merged with the new data, and rewritten to the drive along with its newly
calculated parity information.
RAID 5 is widely regarded as the best RAID level for database and file sharing
operations in a multi-user environment. RAID 5 allows each disk to satisfy requests
simultaneously.
Consider the following set of requests:
Application 1 requests block 1
Because each block is on a different physical device, the blocks can be read simultaneously.
Write performance of a RAID5 stripe depends on the size of the average write. There are three
scenarios for a write operation:
1. Operation replaces all the data blocks in a stripe, results in operations to:
 Calculate parity block
 Write data blocks
 Write parity block
2. Operation replaces a block of data in a stripe, results in operations to:
 Read parity block

RAID Configuration
 Calculate new parity block

 Write data block
3. Operation updates a block of data in a stripe, results in operations to:
 Read block to be modified
 Read associated parity block
 Merge new data with old data
 Calculate new parity block
 Write data block
The mix of these three types of operations governs write performance. Under ideal conditions, a
RAID5 stripe is never as good as RAID 0 for performance. Some of the overhead can be
reduced by putting a large cache on the controller, allowing the controller more freedom in
scheduling read and write operations. Even with a large cache, a RAID 5 stripe has poor write
characteristics. Obviously RAID 5 requires more disk space than RAID 0 (but less than RAID 1).
The overhead is:
For a RAID 5 stripe on three 1GB drives, the usable space is:
Which leaves 2GB of usable space. The space efficiency of a RAID 5 stripe increases as more
physical drives are added to the stripe. This also improves performance.
The mechanism used to recover data in a RAID 5 array is simple, consider the following
example:
0 1 0 1 1 0 1 1 Data 1
1 1 0 1 1 1 0 1 Data 2
1 0 0 0 0 1 1 0 Intermediate XOR
0 1 1 1 0 0 1 0 Data 3
1 1 1 1 0 1 0 0 Error Correction Code
If a drive fails so that Data 2 is no longer available, then it can be re-created from the using XOR
as follows:
Data2 = ((ECC xor Data1) xor Data3)
0 1 0 1 1 0 1 1 Data 1
1 1 1 1 0 1 0 0 Error Correction Code
1 0 1 0 1 1 1 1 ECC xor Data 1
0 1 1 1 0 0 1 0 Data 3
1 1 0 1 1 1 0 1 Result=Data2
If a drive fails, then RAID 5 is forced to synchronize all the drives to read a missing block
because all the data is required. Although RAID 5 continues to function with a failed drive, the
performance for both read and write operations is reduced.

RAID Configuration
RAID 6
RAID 6 combines levels 0 and 1 offering the performance of RAID 0 and the reliability of RAID
1. Rather than grouping drives as pairs, a RAID 0 stripe is mirrored to a second stripe on a
duplicate set of disks. RAID 6 is sometimes referred to as RAID 10.
RAID 6 is the best combination of reliability and performance. Unfortunately, it halves the disk
capacity of a server and doubles its cost.
RAID 7
In the past, servers have had to treat each disk individually. This is often referred to as RAID 7.
The following table covers the advantages and disadvantages of the different RAID levels on
servers
RAID Level Advantages Disadvantages
RAID 0 Read/Write performance Reliability

RAID 1 Read performance and data $/GB cost is doubled
reliability
RAID 5 Read performance and data $/GB cost is increased, and write
reliability performance is reduced
RAID 6 Read/Write performance $/GB cost is doubled

RAID Configuration
Hardware Versus Software RAID Implementations

The Windows operating system implements RAID technology in software. This makes RAID with
all its reliability advantages available on all platforms that support Windows. The disadvantages
of a software implementation are:
 Performance: In a software implementation, any extra work such as calculating parity in
RAID 5 is the job of the main CPU.
 Reliability: It is more difficult to protect the drive containing the operating system from drive
failure because the operating system must be able to boot before the protection is available.
A hardware-based RAID subsystem overcomes these problems:
 Performance: Any calculation of parity data or duplication of disk writes happens at the
controller. This frees the system CPU(s) to handle its normal tasks.
 Reliability: The hardware-based RAID subsystem offers protection of data as the system
boots. If a drive containing part of the operating system fails, the controller reconstructs the
operating system at boot time allowing the machine to operate.
A combination of Windows and a hardware-based RAID subsystem offer the best of both
worlds. If a hardware-based RAID controller fails completely, the system is down until the
controller can be replaced. If a system is fitted with two controllers, then a RAID 0 stripe can be
created on each controller. Using the software capabilities, the stripe on the first controller can
be mirrored to the second controller. Mirroring across controllers removes the controller as a
single point of failure.
Using a RAID host bus adapter is not the only hardware RAID solution. Many vendors sell
solutions in which several drives and a controller are combined. The whole package appears to
the system as a SCSI device. The advantages of this type of solution are:
 Can be fitted to any machine which supports SCSI devices.
 Looks like a single SCSI device and requires no device driver on the host.
The problem with SCSI-SCSI solutions is scalability. Because the device connects through a
single SCSI channel, it cannot exceed the bandwidth of that SCSI channel. SCSI-SCSI solutions
are useful for small RAID arrays where the SCSI channel bandwidth is not an issue. In
installations supporting many drives, SCSI-SCSI solutions do not scale well for performance.
ISMP 5* or 6* RAID Subsystem Description

The only servers with hardware-based RAID subsystems are the ISMP 5* and 6* families. The
controller included in these systems has the following features:
 Bus mastering EISA interface. Peak transfer 33MB/second.
 Intel I960 RISC processor to handle all calculations and to optimize disk access.
 4-16MB cache.
 Five fast and wide SCSI II channels supporting four devices/channel.
 Separate dedicated SCSI processor for each channel.
 Supports RAID 0,1,5,6,7 in hardware.
 Driver support for Windows.
When discussing the configuration of the RAID controller, several terms are used which require
some explanations:
Logical disk - the disk drive the operating system sees. A logical disk is made up of parts of
several physical disks. This is also referred to as System Drive in some documentation.
System pack - Before logical drives are created, the physical disks must be grouped into packs.

RAID Configuration
Configuring ISMP RAID for Performance and

Availability
Configuring a system with RAID technology involves balancing several factors:
 Performance
 Disk capacity
 Reliability
The first rule for configuring a server is that the more physical disks you have, the more flexibility
and potential performance is available. This cost benefit is offset by the performance benefits of
more physical drives.
If the system has sufficient disk space to allow all data to be stored on RAID 6 drives, then
do so as this combines maximum performance and reliability. To implement RAID 6 a
minimum of six disk drives are required. If six drives are available, they can be divided between
RAID 5 and RAID 6 storage (RAID 5 for the operating system, PDS software, and PDS project
files; and RAID 6 for the database software and the database files). This configuration is popular
with many PDS customers.
Before configuring the RAID subsystem, a system administrator must break up the various
functions of the server and its applications into those which primarily write and those which are
primarily read.
Operation/Use Read/Write Comments RAID

Bias levels
Database system Read After the database has been RAID
tables created, changes to the 0,5,6
database tables are rare.
Database data tables Read Mostly read-oriented unless RAID
database has a lot of write 0,5,6
activity.
Database indexes Read Mostly read-oriented unless RAID
database has a lot of write 0,5,6
activity.
Database transaction Write Databases keep a log of all RAID
logs operations on the database. 0,1,6,7
This allows rapid recovery after
system failure.
Reference files Read Reference files attached to a RAID
MicroStation drawing are 0,5,6
read-only.
Shared applications Read Applications shared on client RAID
seats are read-only. 0,5,6
For example, a database server has two conflicting I/O requirements:
1. High performance read access for tables and indexes.
2. High performance write access for the transaction log.
The database transaction log is critical to the performance and maintenance of the system. If the
system crashes, the transaction log is used to ensure the integrity of the data. This is only

RAID Configuration
possible if the transaction log is protected from system failure. Protecting the transaction log has
several implications:
 The transaction log should be on a device where caching is disabled. The transaction log
relies on the operating system to report the completion of a write operation. If caching is
enabled, then the controller reports a write as complete as soon as data is in cache.
 If possible, the transaction log should be on a device protected fully by RAID. Unfortunately,
RAID 5 is a bad choice for this because RAID 5 write performance without using the
controller cache is very limited.
 For optimal system integrity, the system should be protected by a UPS.
The following examples show recommended setups for ISMP5* or 6* configurations from 2 to 8
drives:
Drives Packs System drive 1 System drive 2 System drive 3 System drive 4
2 Two RAID 7 WB RAID 7 WT
packs,
each with
one drive.
3 One pack RAID 5 WB RAID 1 WT
1.5GB 500MB
4 One pack RAID 5 WB 2GB RAID 1 WT
500MB
5 Pack of RAID 5 WB 2GB RAID 1 WT RAID 1 WB
three 500MB 500MB
Pack of
two
6 Pack of RAID 5 WB RAID 5 WB RAID 1 WT RAID 1 WB 500MB
four Pack 1.5GB 1.5GB 500MB
of two
7 Pack of RAID 5 WB 2GB RAID 5 WB 2GB RAID 1 WT RAID 1 WB 500MB
five Pack 500MB
of two
8 Pack of RAID 5 WB RAID 5 WB RAID 1 WT RAID 1 WB 500MB
six Pack 2.5GB 2.5GB 500MB
of two
The principles used to define these configurations can be generalized as follows:
 Two physical drives is very limiting. Assuming you need more than 1GB of real space and
reliability is important, then RAID 7 is the only possibility.
 The database log should go on a logical drive with write-through cache enabled. These
drives are indicated by bold type in the table.
 If possible, have at least two system packs. This prevents the write-through cached drives
from badly affecting the performance of the rest of the system.
 Many older DOS and Windows applications cannot install on drives larger than 2GB. In
many situations, a C drive size of 2GB or smaller is advisable.
The configurations recommended in the previous table show the importance of having many
drives. Try to remember this when ordering servers from any vendor. If performance is
important, you should order as many drives as you can afford.

RAID Configuration
For a system which is used for file sharing of primarily read-only data, the recommended
configurations are simpler:
Drives System System drive 1 System drive 2 System drive 3 System drive 4
packs
2 Two packs, RAID 7 WB RAID 7 WB
each with
one drive.
3 Pack of RAID 5 WB 1GB RAID 5 WB 1GB

three
4 Pack of four RAID 5 WB 1GB RAID 5 WB 1GB RAID 5 WB 1GB
5 Pack of five RAID 5 WB 1GB RAID 5 WB 1GB RAID 5 WB 1GB RAID 5 WB 1GB
6 Pack of six RAID 5 WB RAID 5 WB RAID 5 WB RAID 5 WB

1.25GB 1.25GB 1.25GB 1.25GB
7 Pack of RAID 5 WB RAID 5 WB RAID 5 WB 1.5GB RAID 5 WB 1.5GB

seven 1.5GB 1.5GB
8 Pack of RAID 5 WB RAID 5 WB RAID 5 WB RAID 5 WB

eight 1.75GB 1.75GB 1.75GB 1.75GB
These are general guidelines. Each installation is likely to have unique requirements. If possible,
design a benchmark which reflects typical usage for your server. Use the benchmark to try a
variety of different configurations before putting the server into production.

RAID Configuration

APPENDIX B
Scripts to Create Project Directories

These scripts create standard PDS directories and copy the delivered specs and libraries into
this structure on Windows. These scripts require PERL.EXE (pdsperl.exe in PDS) which is
delivered in the pdshell/bin directory.
 The following scripts are provided as examples and should not be used until a system
manager at your site has reviewed them to ensure that they will be usable in your
environment.
 Intergraph Corporation assumes no risks or responsibilities regarding the use of these
scripts. They are provided for customers to use at their own discretion.
You can download a copy of these scripts from the World Wide Web. These scripts and other
utilities are at the following web address: http://support.intergraph.com.
Script to Create Project Directories on Windows

Type the following lines into a file named mkpdsdir_nt.sh.
To execute this script, type (in a command line window) perl mkpdsdir_nt.sh.
Make sure that the directory defined for PROJDIR exists and that the product directories
are correct.
The project will require about 65MB of disk space.
# THIS SCRIPT HAS BEEN PROVIDED AS AN EXAMPLE AND SHOULD NOT BE USED
# UNTIL A SYSTEM MANAGER AT THE CUSTOMER SITE HAS REVIEWED IT TO
# ENSURE THAT IT WILL BE USABLE IN A PARTICULAR ENVIRONMENT.
#
# INTERGRAPH CORPORATION ASSUMES NO RISKS OR RESPONSIBILITIES REGARDING
# THE USE OF THIS FILE. IT IS PROVIDED FOR CUSTOMER USE AT THEIR OWN
# DISCRETION.
#
# This script creates "standard" PDS directories and copies the delivered
# specs and libraries into this structure. Requires PERL.EXE, but the one
# delivered in pdshell/bin seems to work OK.
#
# To execute, type (in DOS window) "perl mkpdsdir_nt.sh"
#
# NOTE: Make sure that the directory defined for PROJDIR exists and that
# the product directories are correct!!
#
# The project will require about 65MB
#
@rem = '
@echo off
perl %0.cmd %1 %2 %3 %4 %5 %6 %7 %8 %9
goto endofperl
';
#

# Define Project Directory - SET THIS EACH TIME!!

#
$PROJDIR = 'h:\proj2';
#
# Define Product Base Directories
#
$PDSHELL = 'C:\win32app\ingr\pdshell';
$PDREPORT= 'C:\win32app\ingr\pdreport';
$PDDRAW = 'C:\win32app\ingr\pddraw';
$PDDATA = 'C:\win32app\ingr\pddata';
$PDEQP = 'C:\win32app\ingr\pdeqp';
$RDUSRDB = 'C:\win32app\ingr\rdusrdb';
#
# Create PDS Project Directories
#
print "\n";
print "Creating Project Directories...\n";
$newdir = $PROJDIR."\\2d";
mkdir ($newdir, 770);
$newdir = $PROJDIR."\\2d\\pds2d";
$newdir = $PROJDIR."\\2d\\pfd";
$newdir = $PROJDIR."\\2d\\pid";
$newdir = $PROJDIR."\\clash";
$newdir = $PROJDIR."\\clash\\plot";
$newdir = $PROJDIR."\\clash\\report";
$newdir = $PROJDIR."\\design_review";
$newdir = $PROJDIR."\\dwg";
$newdir = $PROJDIR."\\dwg\\535";


$newdir = $PROJDIR."\\dwg\\border";
$newdir = $PROJDIR."\\dwg\\cell";
$newdir = $PROJDIR."\\iso";
$newdir = $PROJDIR."\\model_builder";
$newdir = $PROJDIR."\\models";
$newdir = $PROJDIR."\\models\\arch";
$newdir = $PROJDIR."\\models\\eqp";
$newdir = $PROJDIR."\\models\\hvac";
$newdir = $PROJDIR."\\models\\piping";
$newdir = $PROJDIR."\\project";
$newdir = $PROJDIR."\\raceway";
$newdir = $PROJDIR."\\rdb";
$newdir = $PROJDIR."\\rdb\\eqp";
$newdir = $PROJDIR."\\rdb\\eqp\\approved";
$newdir = $PROJDIR."\\rdb\\eqp\\unapproved";
$newdir = $PROJDIR."\\rdb\\lib";
$newdir = $PROJDIR."\\rdb\\lib\\approved";
$newdir = $PROJDIR."\\rdb\\lib\\unapproved";
$newdir = $PROJDIR."\\rdb\\source";
$newdir = $PROJDIR."\\rdb\\source\\assembly";
$newdir = $PROJDIR."\\rdb\\source\\eden_eqp";
$newdir = $PROJDIR."\\rdb\\source\\eden_piping";


$newdir = $PROJDIR."\\rdb\\source\\eqp";
$newdir = $PROJDIR."\\rdb\\source\\eqp\\tdf";
$newdir = $PROJDIR."\\rdb\\source\\std_note";
$newdir = $PROJDIR."\\rdb\\source\\table";
$newdir = $PROJDIR."\\rdb\\spec";
$newdir = $PROJDIR."\\report";
$newdir = $PROJDIR."\\report\\discrimination";
$newdir = $PROJDIR."\\report\\format";
$newdir = $PROJDIR."\\report\\mto";
$newdir = $PROJDIR."\\report\\search";
#
# Create Sample PDS Delivered Specs
#
print "\n";
print "Copying Sample Spec Data...\n";
$oldfile = $RDUSRDB."\\spec_data\\classes.pmc";
$newfile = $PROJDIR."\\rdb\\spec\\classes.pmc";
&copy_files ($oldfile, $newfile);
$oldfile = $RDUSRDB."\\spec_data\\1c0031.pcd";
$newfile = $PROJDIR."\\rdb\\spec\\1c0031.pcd";
$oldfile = $RDUSRDB."\\spec_data\\2c0032.pcd";
$newfile = $PROJDIR."\\rdb\\spec\\2c0032.pcd";
$oldfile = $RDUSRDB."\\spec_data\\taps.data";
$newfile = $PROJDIR."\\rdb\\spec\\taps.data";
$oldfile = $RDUSRDB."\\spec_data\\implied.data";
$newfile = $PROJDIR."\\rdb\\spec\\implied.data";
$oldfile = $PDDATA."\\sample\\data\\instrment.data";
$newfile = $PROJDIR."\\rdb\\spec\\instrment.data";
$oldfile = $PDDATA."\\sample\\data\\specialty.data";
$newfile = $PROJDIR."\\rdb\\spec\\specialty.data";
$oldfile = $PDDATA."\\sample\\data\\component.data";
$newfile = $PROJDIR."\\rdb\\spec\\component.data";
$oldfile = $PDDATA."\\sample\\data\\constol.data";
$newfile = $PROJDIR."\\rdb\\spec\\constol.data";
$oldfile = $PDDATA."\\sample\\data\\flange.data";

$newfile = $PROJDIR."\\rdb\\spec\\flange.data";
$oldfile = $PDDATA."\\sample\\data\\pcd_size.data";
$newfile = $PROJDIR."\\rdb\\spec\\pcd_size.data";
print "\n";
print "Copying Reference Data Base Options...\n";
$oldfile = $PDDATA."\\sample\\data\\rdb_options";
$newfile = $PROJDIR."\\project\\RDB_options";
print "\n";
print "Copying Piping Job Spec Library...\n";
$oldfile = $RDUSRDB."\\us_pjstb.l";
$newfile = $PROJDIR."\\rdb\\lib\\unapproved\\pjs_tbl.l";
$oldfile = $RDUSRDB."\\us_pjstb.l.t";
$newfile = $PROJDIR."\\rdb\\lib\\unapproved\\pjs_tbl.l.t";
$oldfile = $RDUSRDB."\\us_pjstb.l.r";
$newfile = $PROJDIR."\\rdb\\lib\\unapproved\\pjs_tbl.l.r";
$oldfile = $RDUSRDB."\\us_shbom.l";
$newfile = $PROJDIR."\\rdb\\lib\\unapproved\\short_bom.l";
$oldfile = $RDUSRDB."\\us_lgbom.l";
$newfile = $PROJDIR."\\rdb\\lib\\unapproved\\long_bom.l";
$oldfile = $RDUSRDB."\\us_spbom.l";
$newfile = $PROJDIR."\\rdb\\lib\\unapproved\\spclty_bom.l";
print "\n";
print "Copying Standard Note Library...\n";
$oldfile = $PDSHELL."\\lib\\std_note.l";
$newfile = $PROJDIR."\\rdb\\lib\\unapproved\\std_note.l";
$oldfile = $PDSHELL."\\lib\\std_note.l.t";
$newfile = $PROJDIR."\\rdb\\lib\\unapproved\\std_note.l.t";
print "\n";
print "Copying Label Description Library...\n";
$oldfile = $PDSHELL."\\lib\\labels.l";
$newfile = $PROJDIR."\\rdb\\lib\\unapproved\\labels.l";
print "\n";
print "Copying Piping Assembly Library...\n";
$oldfile = $PDSHELL."\\lib\\assembly.l";
$newfile = $PROJDIR."\\rdb\\lib\\unapproved\\assembly.l";
$oldfile = $PDSHELL."\\lib\\assembly.l.t";
$newfile = $PROJDIR."\\rdb\\lib\\unapproved\\assembly.l.t";
print "\n";
print "Copying Graphic Commodity Library...\n";
$oldfile = $PDSHELL."\\lib\\pip_gcom.l";

$newfile = $PROJDIR."\\rdb\\lib\\unapproved\\pipe_gcom.l";
$oldfile = $PDSHELL."\\lib\\pip_gcom.l.t";
$newfile = $PROJDIR."\\rdb\\lib\\unapproved\\pipe_gcom.l.t";
print "\n";
print "Copying Physical Data Library...\n";
$oldfile = $RDUSRDB."\\us_pcdim.l";
$newfile = $PROJDIR."\\rdb\\lib\\unapproved\\us_pcdim.l";
$oldfile = $RDUSRDB."\\us_pcdim.l.t";
$newfile = $PROJDIR."\\rdb\\lib\\unapproved\\us_pcdim.l.t";
$oldfile = $RDUSRDB."\\us_pcdim.l.r";
$newfile = $PROJDIR."\\rdb\\lib\\unapproved\\us_pcdim.l.r";
print "\n";
print "Copying Eqp Tutorials...\n";
$oldfile = $PDEQP."\\dat\\zi_eqpms.lib";
$newfile = $PROJDIR."\\rdb\\eqp\\unapproved\\zi_eqpms.lib";
$oldfile = $PDEQP."\\dat\\zi_eqpms.hlp";
$newfile = $PROJDIR."\\rdb\\eqp\\unapproved\\zi_eqpms.hlp";
$oldfile = $PDEQP."\\dat\\zi_tutlib.lib";
$newfile = $PROJDIR."\\rdb\\eqp\\unapproved\\zi_tutlib.lib";
print "\n";
print "Copying unapproved to approved...\n";
$dir = $PROJDIR."\\rdb\\lib\\unapproved";
opendir (D, $dir) || die "Can't open $dir: $!\n";
@filelist= sort grep (!/^[.]/
&& !/^[.][.]/
&& (tr/A-Z/a-z/ || 1), readdir(D));
closedir(D);
foreach $fil (@filelist)
{
$oldfile = $PROJDIR."\\rdb\\lib\\unapproved\\".$fil;
$newfile = $PROJDIR."\\rdb\\lib\\approved\\".$fil;

}
$dir = $PROJDIR."\\rdb\\eqp\\unapproved";
&& !/^[.][.]/
closedir(D);
{
$oldfile = $PROJDIR."\\rdb\\eqp\\unapproved\\".$fil;
$newfile = $PROJDIR."\\rdb\\eqp\\approved\\".$fil;

}
print "\n";
print "Copying Sample Report Format...\n";
$dir = $PDREPORT."\\sample";
&& !/^[.][.]/
closedir(D);
{
$oldfile = $PDREPORT."\\sample\\".$fil;
$newfile = $PROJDIR."\\report\\format\\".$fil;

}
print "\n";
print "Copying Drawing Borders...\n";
$dir = $PDDRAW."\\border";
&& !/^[.][.]/
closedir(D);
{
$oldfile = $PDDRAW."\\border\\".$fil;
$newfile = $PROJDIR."\\dwg\\border\\".$fil;

}
sub copy_files
{
$cmd = "copy ".$oldfile." ".$newfile;
system ($cmd);
}
__END__
:endofperl


APPENDIX C
Log Files Produced by PDS Batch Jobs

The PDS batch mail utility will allow for the mailing of these log files in a Windows environment.
If the batch mail utility has not been set up, log files will be left in the temp directory.
PD_Design
Command File Name Location
Design Checker dsgnchkr.log temp
<project_name>.dcl temp directory
Approval Manager pdapprov.rep temp directory
<project_name>.apl temp directory
Approval by Line ID same as approval
manager
Database Verification dbv.log temp directory
<project_name>.dvl temp directory
P&ID Comparison pdpidrpt.log temp directory
pdpidrpt.cmp temp directory
P&ID Named Item Report pdpidcmp.log temp directory
piditem.cmp temp directory
Plot Model plot.log temp directory
m<model_index_no>.ptl temp directory
Inspection Iso Manager pdinsiso.rep temp directory
PD_Model
Model Builder pdmodbld.log temp directory
PD_Draw
Create Drawing drw<drawing_type_no>.lo temp directory
g
crdrwque.log temp directory
VHL hline.log temp directory
<drawing_indx_no>.hlg temp directory


Plot Drawing plot.log temp directory
<drawing_indx_no>.ptl temp directory
Update Annotation Labels udl_log.<drawing_type_n temp directory
o>
PD_Report
MTO rpt_error.log temp directory
PD_Review
DesignReview Label Builder labelbld.log temp directory
<dri_control>.err dri file directory
DesignReview Label Sender drtrans.rvw temp directory
drtrans.log temp directory
Plot Model plot.log temp directory
m<model_index_no>.ptl temp directory
PD_Clash
Interference Checker <project or area>.ilg temp directory
<project or area>.icl temp directory
Envelope Builder <project or area>.blg temp directory
<project or area>.ebl temp directory
Clash Report rpt_error.log temp directory
Plot Manager <project or area>.icl temp directory
Approval Manager/plot <project or area>.icl temp directory
PD_Project
Create Model from ASCII cmdlasci.log temp directory
List
<project_name>.cma temp directory
Create Database Tables crtmodel.rep temp directory
<project_name>.cml temp directory


Copy Model cpymodel.log temp directory
<model_index_no>.cpl temp directory
Delete Model dltmodel.log temp directory
<model_index_no>.dml temp directory
Project Data Mgr/propagate propagate.log temp directory
<project_name>.pgl temp directory
Report on Named Item rptnmdit.log temp directory
<project_name>.rnl temp directory
Archival <project_no>.arc temp directory
archive.log project
directory
Active Retrieval <project_no>.rtv temp directory
retrieve.log project
directory
Inactive Retrieval <project_no>.rtv temp directory
retrieve.log project
directory
Import <project_no>.rtv temp directory
import.log project
directory
Project Control Mgr rpt_error.log temp directory
PD_Data
Load PJS/pmc pmc.log temp directory
Load PJS/commodity pcd.log temp directory
Load PJS/specialty splty.log temp directory
Load PJS/instrument instment.log temp directory
Load PJS/taps taps.log temp directory
Load PJS/size-dependent pcd_size.log temp directory
Load PJS/implied implied.log temp directory
Load PJS/exclusion compinsu.log temp directory
Load PJS/flange exclusion flnginsu.log temp directory
Load PJS/construction cons_tol.log temp directory


PJS Report Manager rpt_error.log temp directory
Table Checker rpt_error.log temp directory
PJS Table Library pjstbl.log temp directory
Graphic Commodity Library eden.log temp directory
Physical Data Library phstbl.log temp directory
Piping Assemblies pal.log temp directory
Short Material Descript shbom.log temp directory
Lib/load
Lib/revise
Lib/report
Long Material Descript lgbom.log temp directory
Lib/load
Lib/revise
Lib/report
Specialty Mat Descript splty.log temp directory
Lib/load
Lib/revise
Lib/report
Standard Note Load DB stdnote.log temp directory
RDB Conflict Report <project or area>.rlg temp directory
<project or area>.rcl temp directory
Table Change Report <project or area>.rlg temp directory
Geo. Ind. Std. Report <project or area>.rlg temp directory
The temp directory is defined by the environment variable TEMP. If the TEMP
environment variable is undefined, the environment variable TMP is used. If neither of these
environment variables is set, C:\temp is used as the temp directory.

PD_Design
Design Checker dsgnchkr.log temp directory

<project_name>.dcl
Approval Manager pdapprov.rep
<project_name>.apl
Approval by Line ID same as approval
manager
Database Verification dbv.log
<project_name>.dvl
P&ID Comparison pdpidrpt.log
pdpidrpt.cmp
P&ID Named Item pdpidcmp.log
Report
piditem.cmp
Plot Model plot_log
m<model_index_no>.ptl
Inspection Iso Manager pdinsiso.rep
PD_Model
Model Builder pdmodbid.log temp directory
PD_Draw
Create Drawing drw<drawing_type_no>.lo temp directory

g
crdrwque.log
VHL hline.log
<drawing_indx_no>.hlg
Plot Drawing plot.log
<drawing_indx_no>.ptl
Update Annotation Labels udl_log<drawing_type_no
>

PD_Report
MTO rpt_error.log temp directory
PD_Review
DesignReview Label labelbld.log temp directory

Builder
<dri_control>.err dri file directory
DesignReview Label drtrans.rvw temp directory
Sender
drtrans.log
Plot Model m<model_index_no>.ptl temp directory
PD_Clash
Interference Checker <project or area>.ilg temp directory

<project or area>.icl
Envelope Builder <project or area>.blg
<project or area>.ebl
Clash Report rpt_error.log
Plot Manager <project or area>.icl
Approval Manager/plot <project or area>.icl

PD_Project
Create Model from ASCII cmdlasci.log temp directory

List <project_name>.cma
Create Database Tables crtmodel.rep
<project_name>.cml
Copy Model cpymodel.log
<model_index_no>.cpl
Delete Model dltmodel.log
<model_index_no>.dm
l
Project Data Mgr/propagate propagate.log
<project_name>.pgl
Report on Named Items rptnmdit.log
<project_name>.rnl
<project_no>.arc
Archival <project_no>.arc
archive.log project directory
Active Retrieval <project_no>rtv temp directory
retrieve.log project directory
Inactive Retrieval <project_no>.rtv temp directory
import.log project directory
Import <project_no>.rtv temp directory
import.log project directory
Project Control Mgr. rpt_error.log temp directory
PD_Data
Load PJS/pmc pmc.log temp directory

Load PJS/commodity pcd.log
Load PJS/specialty splty.log
Load PJS/instrument instrument.log
Load PJS/taps taps.log
Load PJS/size-dependent pcd_size.log
Load PJS/implied implied.log

Load PJL/exclusion compinsu.log

Load PJS/flange exclusion flnginsu.log
Load PJS/construction cons_tol.log
PJS Report Manager rpt_error.log
Table Checker rpt_error.log
PJS Table Library pjstbl.log
Graphic Commodity Library eden.log
Physical Data Library phstbl.log
Piping Assemblies pal.log
Short Material Descript Lib/load shbom.log
Short Material Descript shborn.log
Lib/revise
Short Material Descript shbom.log
Lib/report
Long Material Descript Lib/load lgbom.log
Long Material Descript lgbom.log
Lib/revise
Long Material Descript lgbom.log
Lib/report
Specialty Mat Descript Lib/load splty.log
Specialty Mat Descript splty.log
Lib/revise
Specialty Mat Descript splty.log
Lib/report
Standard Note Load DB stdnote.log
RDB Conflict Report <project or area>.rlg
<project or area>.rcl
Table Change Report <project or area>.rlg
Geo. Ind. Std. Report <project or area>.rlg

Notes:
The temp directory is defined by the environment variable TEMP. if the TEMP environment
variable is undefined, the environment variable TMP is used. If neither of these environment
variables is set, C:\temp is used as the temp directory.


APPENDIX D
PDS Project Creation Workbook

We highly recommend that you take the time when setting up the project to fill out the forms
contained in this appendix. You will find that they will be a convenient reference throughout the
life of the project.
Company:
Contact:
Project:
Date:

Notes:









APPENDIX E
PDS and FrameWorks Plus

This appendix explains how to incorporate FrameWorks Plus into the PDS environment.
In This Appendix
Setup Information .......................................................................... 199
FrameWorks Environment ............................................................. 214
FrameWorks Plus and SmartPlant Review ................................... 225
FrameWorks Plus and PD_Clash .................................................. 227
FrameWorks Plus and Material Data Publisher............................. 228
Setup Information
You need to set up a project, a structural discipline design area, and create a FrameWorks Plus
model before you can use FrameWorks Plus in the PDS environment.
Always press ENTER when entering values in PD_Shell.
See Also
FrameWorks Plus Categories (on page 213)
Creating a Model in PD_Shell (on page 203)
Creating a Model by ASCII File (on page 205)
Creating a Structural Discipline Design Area (on page 201)
Creating or Inserting a FrameWorks Plus Project (on page 200)
Intergraph SmartPlant License Manager (on page 199)
Shifting the FrameWorks Plus Global Origin to Match PDS Design Volume (on page 208)
Intergraph SmartPlant License Manager

If you installed FrameWorks Plus using a PDS serial number, FrameWorks Plus uses one PDS
3D seat whenever you access FrameWorks Plus whether through PD_Shell, through the
FrameWorks Plus icon, or by using the mdl load fwp key-in. FrameWorks Plus also uses one
PDS 3D seat if you launch a batch process to create a SmartPlant Review file, an envelope file,
or batch cutouts.
Starting with version 7.2, FrameWorks Plus installed with a FrameWorks Plus serial number (as
opposed to a PDS serial number) also requires Intergraph SmartPlant License Manager.
FrameWorks Plus uses one FrameWorks Plus seat whenever you open FrameWorks Plus.
FrameWorks Plus also takes one FrameWorks Plus seat when you use one of the command
line utilities. For more information about the command line utilities, see Command Prompt
Commands.
Because FrameWorks Plus uses a PDS seat or a FrameWorks Plus seat, you need to have
Intergraph SmartPlant License Manager software on the same computer as FrameWorks Plus.
See the SmartPlant Licensing Manager Installation and User’s Guide for more information.

Creating or Inserting a FrameWorks Plus Project

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.
 The total path length to the FrameWorks Plus project including the drive letter and the
required \'s is limited to 36 characters.
 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.
FrameWorks Project Number - Specifies the FrameWorks Plus project name (the top- level
project directory that appears in the Windows NT 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.
For example:
FrameWorks Plus Project Number: fwstr
---AND---
FrameWorks 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.
Creating a Structural Discipline Design Area

The design area is used to define virtual areas within the overall pds project. You need to
associate a FrameWorks Plus project to a PDS design area. The design area is stored in
pdtable_112. The association between the design area and the FrameWorks Plus project is
stored in pdtable_117.

To delete a FrameWorks Plus subproject, you must delete the entries in pdtable_116 and
pdtable_117.
Design Area Name - Type a name for the structural discipline design area.
Use the same name for the Design Area as the FrameWorks Plus subproject for easier
tracking.
Description - Type a description for the design area.
Structural Sub Project - Select the FrameWorks Plus project you want to associate with this
design area. Click the field to see the available structural projects.
No Interference Management Design Area / Interference Management Design Area -
Specifies if you want to define an Interference Management Design Area for this design area.
We recommend that you select "No Interference Management Design Area."
If you select Interference Management Design Area, a design_area_name.3 clash marker file is
created in the pds project directory. (The 3 extension indicates the structural discipline number
from pdtable_111).
Create a Structural Discipline Design Area

1. Click Start > Programs > PD_Shell > PD_Shell.
4. Click Project Environment Manager.
5. Click Create.
6. Click Create Design Area Data
7. Select Structural Discipline.
8. Click Accept.
9. Type a Design Area Name.

10. Type a description for the Design Area.

11. Select the FrameWorks Plus project as the Structural Subproject by placing a data point in
the field and selecting the subproject from the list of FrameWorks Plus subprojects.
12. Make sure No Interference Management Design Area is selected.
13. Click Accept.
Creating a Model in PD_Shell

After the FrameWorks Plus project is added to the PDS project and the Design Area has been
assigned, you can create FrameWorks Plus models.
Model creation creates two entries in pdtable_113. The first entry stores the information about
the model.dgn file. The second entry stores information about the model.prp file.
Model Number - Type a name for the model. Model names are limited to 10 characters.
Seed Model - Select the seed model to use to create the model. The seed directory is defined in
the project\data\config.dat file. If no seed model is selected, PDS creates a standard model
based on the selected units.
Frozen Model Name - Displays the name of the propagated model file. This is the Model
Number name with a .prp extension.
Model Description - Type a description for the model.
Model Directory - Displays the directory the propagated model is created in. This directory is
set when you create the FrameWorks Plus subproject and cannot be changed.
Workstation/Server Name - Displays the name of the computer on which the model is saved.
This is computer is set when you created the project and cannot be changed.
Application Type - Displays the structural application type. Do not change this value.
Model Status - Select a model status from the entries for code list set 1605. Model status is
used for clash to exclude models for clash detection. 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.
Force Units - Select the force units for loads placed in this model. We recommend that all
models in the same project use the same force units. This option is not available if you are using
a seed model.
You cannot change force units after the model is created.
Standard Section Table - Select the standard section table you want to use for the model. This
option is not available if you are using a seed model.
You cannot change the standard section table after the model is created.
User Section Table - Select the user section table you want to use for the model. You can
change the user section table after the model is created. The user section library must have
been created using FrameWorks Plus Manager or from the command line. This option is not
available if you are using a seed model.
Third Party Software - Select the analysis software you plan to use on this model. You can
select another application after the model is created. This option is not available if you are using
a seed model.
Design Code - Select the design code you plan to use on this model. You can select another
design code after the model is created. This option is not available if you are using a seed
model.
Propagated and Sparse / Propagated Only - Select whether to create either a propagated and
sparse model, or just a propagated model.
Propagate and Sparse / Propagate Only toggle defines the process for Batch Propagation inside
PDS with the Frozen Model Name model.
Propagate Only copies the project related seed file into the project\frz directory and renames it,
and propagates into the file.
Propagate and Sparse copies the model.dgn file from the project\mod directory to the project\frz
directory and propagates into the file.
The batch propagation process uses the symbology from the first 3D isometric view defined in
the FrameWorks Plus model.
The model.prp file is used for Attach PDS Reference Model command, creating Isometric ASCII
reference file, and SmartPlant Review sessions and labels. To generate Isometric ASCII file and
to identify structural members for Pipe Support placement, you must use Propagate and Sparse
option.
We recommend that you regularly compress your .prp files. An easy way to compress is to use
the Compress Directory command in MicroStation Manager.
Sparse Model Name - Displays the name of the sparse model. This is the Model Number name
with a .dgn extension.
Sparse Model Directory - Displays the directory the sparse model is created in. This directory
is set when you create the FrameWorks Plus subproject and cannot be changed.
Sparse Workstation/Server Name - Displays the name of the computer on which the model is
saved. This is computer is set when you created the project and cannot be changed.
Create a Model
1. Click Start> Programs> PD_Shell> PD_Shell.
4. Click Project Environment Manager.

5. Click Create.
6. Click Create Model.
7. Click Structural from the list of Disciplines.
8. Click Accept.
9. Select the design area that is specific to the FrameWorks Plus Sub Project.
If you did not let PDS know about the FrameWorks Plus project by using the Insert
FrameWorks Data option before creating the design area, a message stating This is not a
ModelDraft Model displays.
This message displays for any model that is not part of a FrameWorks Plus subproject. This
message implies that any model created in this way is considered dumb graphics. It will be
available as a reference file, but it will be ignored for such operations as the SmartPlant
Review intelligent tag creation and envelope file generation.
You can easily integrate existing models you created with FrameWorks Manager by using
the Create Model command in PD_Shell. The Create Model command detects the existing
model and prompts you to confirm the model name. If you accept, PD_Shell creates entries
in pdtable_113 for the existing model.
10. Type a Model Number. This is the model name.
11. Select a seed model.
12. Type a Frozen Model Name.
13. Type a description for the model.
14. Select a Model Status.
15. Select Force Units for the loads in the model.
16. Select a Standard Section Table.
17. Select a User Section Table.
18. Select a Third Party Software. This is the software you plan to use for analytical design.
19. Select a Design Code.
20. Select Propagated and Sparse or Propagated Only.
21. Select Accept.
Creating a Model by ASCII File

After the FrameWorks Plus project is added to the PDS project and the Design Area has been
assigned, you can create FrameWorks Plus models using ASCII input files.
The command can be used to create model definitions for existing ModelDraft or
FrameWorks Plus models without writing over the existing design files.
Model creation creates two entries in pdtable_113. The first entry stores the information about
the model.dgn file. The second entry stores information about the model.prp file.
The ASCII files used to create a model must be in order by the keywords listed below. The
software will not function if the keyword order is incorrect.
The Force Units, Standard Section Table, and User Section Table come from the FrameWorks
Plus project information that is stored in the project database. The Third Party software defaults
to STAAD and the design code defaults to AISC-ASD. These defaults are the same defaults if
you were creating model interactively. A detailed log file is created in c:\temp\caxxx.
After an area is created using the keyword Area_Desc title is not accepted, neither is the
Sub_Proj_Number title accepted. When the structural area is created, it is associated with a FW
subproject specified. This subproject information is retrieved from the area when you create a
model.

Keywords
Discipline: The discipline name exactly as it appears in the PD_Shell environment (example:
Discipline: Structural) is required information.
Area_Name: A required 20-character design area name; it must be unique across disciplines
(example: Area_Name:Struct_A).
Area_Desc: An optional 40-character description for the design area being created (example:
Area_Desc:Struct_A).
This option 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).
This option is only for use in combination with Area_Description.
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).
This option is only for use in combination with Area_Marker_file.
Sub_Proj_Number: Required information for structural models. It defines the structural
subproject.
This option is required when creating a new area in combination with Keyword
Area_Desc
Model_Number: A required up to 10-character Structural model number of the model to be
created (example: Model_Number:Model_A).
Model_Desc: Optional up to 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).
Not supported for structural since 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.
Not supported for structural since defined in the subproject
Network_Address: An optional 26-character node name of the system on which the model file
is to be stored This value is not specified or the keyword is missing, the default values as
defined with the Model Setup option, are used.
Not supported for structural since defined in the subproject
Application_Type: An optional value indicating the discipline association for interference
checking purposes. It associates the design model with a different discipline for reporting
clashes. The default is the discipline where the design model is created (example:
Application_type:Structural).
Model_type: For structural models only, the type of structural model to be created. Its value is
set as follows: both or propagate settings will NOT create a physical file. These settings ONLY
create an entry in the project schema's pdtable_113.
 both: defines a model_type =2 in pdtable_113. It defines that while running batch
propagation the prp file will contain the sparse model (which is a single line model) and a 3D
model (which is the so-called propagated model.

 propagated: creates a model_type =0 entry in pdtable_113. Running batch propagation on

a model with this status will result in a propagated only model.
 sparse: The only Model_Type setting that actually creates physical files. This setting will
cause the software, if the model does not already exist, to execute the FW+ cremod utility
that will create all 14 files in the FW+ project\mod directory... Also a corresponding entry in
pdtable_113 will be created.
Model_Status: An optional value. Should be followed by a number value from the standard note
code list 1605 and can be used for excluding models from being processed by PD_Clash.
Sample for new area creation and model creation:
Discipline:Structural
Area_Name:ascii
Area_Desc:ascii
Area_Marker_File:Yes
Area_Volume_Low:-100,-250,-50
Area_Volume_High:150,30,120
Sub_Proj_Number:ascii
Model_Number:mod1
Model_Desc: first ascii
Model_Type:sparse
Application_Type:Structural
Model_Number:mod1
Model_Desc:2nd ascii prp
Model_Type:propagated
Model_Number:mod2
Model_Desc: 2ndascii
Model_Type:sparse
Model_Number:mod2
Model_Desc:2nd ascii prp
Model_Type:propagated
Sample to create a sparse and propagated model in existing Design area:
Discipline:Structural
Area_Name:ascii1
Model_Number:mod3
Model_Desc:3rd ascii
Model_Type:sparse
Model_Number:mod3
Model_Desc:3rd ascii prp
Model_Type:both

Shifting the FrameWorks Plus Global Origin to Match PDS

Design Volume
A PDS design volume is analogous to an auxiliary coordinate system (ACS). FrameWorks Plus
does not support auxiliary coordinate systems, so you cannot shift the global origin (GO) in a
FrameWorks Plus model to match the global origin in a PDS design volume.
However, you can use MicroStation to create an ACS macro for every coordinate system
required on a project and add the macros to a customized MicroStation menu. The learning
curve for designers is short, and modeling FrameWorks Plus items is straight forward.
You can create an ACS macro for every coordinate system required on the project and add it to
a customized MicroStation menu. Using an automated macro ensures that all designers are
using the same coordinates. Mid-project adjustments can be implemented easily because the
macro only exists in one location on the project. You no longer have to open every drawing and
model to create the same ACS. The macro also removes the requirement to audit each design
file because only one macro in a central location is used to define the ACS.
Using Coordinate Systems in FrameWorks Plus

In addition to the plant coordinate system, the Design Volume Coordinate System (DVCS)
option within PDS allows for a separate coordinate system that can be defined for an individual
model. FrameWorks Plus however does not use this PDS functionality when the program is
used through the PDS Application Suite (PD_Shell).
To overcome this limitation you can create an Auxiliary Coordinate System within the
FrameWorks Plus model to coincide with the PDS DVCS.
To create an Auxiliary Coordinate System within a FrameWorks Plus model, you use macros to
do the following:
 Speed up the initialization of the new coordinate system by loading this macro upon startup
of a model.
 Provide a standard to be used across models and projects to lessen the chance of input
errors.
Limitations of using ACS

 Extracting coordinates from the model does not honor the ACS (for example, SDNF, MDP).
 SmartPlant Review does not recognize multiple ACS.
 Coordinate systems shifted outside of the MicroStation design cube are not possible with
ACS.
If you require coordinates in your model far outside the limits of the MicroStation design
cube, then you can truncate the coordinates to fit. For example, instead of East 3,450,000
use East 50,000, and have the designers add the additional numbers.
 There are also some differences when using key-ins or checking coordinates in the design
file while using the ACS. For designers who use key-ins and not AccuDraw, use the
following:
AD= (instead of DL=)
AX= (instead of XY=)
See Also
Create an Auxiliary Coordinate System within a model (on page 209)
Automatically load an Auxiliary Coordinate System within a model (on page 211)
Create a prompt to appear before loading (see "Create a prompt for automatic loading" on page

Create an Auxiliary Coordinate System within a model

The following example shows how to create an Auxiliary Coordinate System that is offset 100 ft
East and 75 ft North from the DGN file's default 0,0,0 location. This example uses the name
Unit#1 for the ACS.
1. Select Utilities > Macros from the MicroStation command bar.
The Macros dialog box opens.

2. Click New on the Macros dialog box.
The MicroStation BASIC Editor dialog box opens.

3. Into the BASIC Editor dialog box, enter the following text which creates an Auxiliary
Coordinate System that is offset 100 ft East and 75 ft North from the DGN file's default 0,0,0
location.
'Author : INTERGRAPH Corp

'Project : Some Project
'Template file : Unit1ACS.bas
'Date : 3/1/2010
'DEFINE ACS SYSTEM FOR UNIT 1
Sub main
Dim startPoint As MbePoint
Dim point As MbePoint, point2 As MbePoint
'First remove existing ACS from design file if update required
MbeSendKeyin "Delete Acs UNIT#1"
'Define ACS 0,0,0 origin within MicroStation design file
MbeSendKeyin "Define Acs Points "
MbeSendKeyin "XY=100,75,0"
'Define ACS X Axis (if rotation required use DI=distance,angle)
MbeSendKeyin "DL=100"
'Define ACS Y Axis (if rotation required use DI=distance,angle)
MbeSendKeyin "DL=-100,100"
'Save and Attach New ACS to design file
MbeSendKeyin "Save Acs UNIT#1"
MbeSendKeyin "Attach Acs UNIT#1"
MbeSendKeyin "Attach Acs"
MbeSendKeyin "Reset"
'Set your tentative point readout to use the new Coord System
MbeSendKeyin "SET TPMODE ACSDelta"
MbeSendKeyin "SET TPMODE ACSLocate"
End Sub

4. Click File > Save to save the macro. Name it something useful. For example, the previous
example could be named Unit1ACS.bas.
You can now select Run from the Macro menu for this new macro and your Auxiliary
Coordinate System will be set up and active.
You must load this macro every time you enter this model in order for this ACS to be
active.
See Also
Automatically load an Auxiliary Coordinate System within a model (on page 211)
Create a prompt for automatic loading (on page 211)
Automatically load an Auxiliary Coordinate System within a model

To load a Macro in Microstation by default, complete the following steps:
 Find the MDL called runmacro.ma and place it in the .../mdlsys/asneeded/ folder.
 While in a FWP PDS model define the variable: "MS_DGNAPPS = runmacro" under
WORKSPACE>CONFIGURATION
 While in a FWP PDS model define the variable: "MS_DGNMACROS=Unit1ACS.bas" This is
the name of the Macro we created above.
Now every time you enter a model your Macro will load.
This example is very basic and provides the user with the ability to load a single ACS base on a
yes or no button response. It is possible to create a dialog box with a list of Auxiliary Coordinate
systems from which to choose. See the MicroStation Help file "BASIC Editor" for some
information on this topic.
See Also
Create a prompt for automatic loading (on page 211)
Create a prompt for automatic loading

While still in the BASIC editor for your Macro, you can create a prompt to accept the setting of
the ACS when the model is loaded.
1. Click Edit > Custom Dialog > Edit.

The Builder dialog box opens. Here you define the dialog box to open and the options
associated with it.
2. Click New.
A new dialog box opens allowing you to edit the text.
3. To include a message, add a label from the Builder Tools menu and place that label on the
dialog box.
4. In the Builder window labeled PushButton, double-click the items you want to label.
5. Change the text for these items to provide Yes and No buttons, and a label asking what to
do next.
6. Save the dialog box and return to your Script
Edit script to accept input from the user

The following is an edit to the example using this new Startup dialog box.

'Author : INTERGRAPH Corp

Project : Some Project
'Template file : Unit1.bas
'Date : 3/1/2010
'DEFINE ACS SYSTEM FOR UNIT 1
Sub main
Dim startPoint As MbePoint
Dim point As MbePoint, point2 As MbePoint
Dim Button As Long
Dim Msg As Integer
Button = MbeOpenModalDialog (1)

If (Button = MBE_BUTTON_OK) Then
'First remove existing ACS from design file if update required
MbeSendKeyin "Delete Acs UNIT#1"
'Define ACS 0,0,0 origin within MicroStation design file
MbeSendKeyin "Define Acs Points "
MbeSendKeyin "XY=100,75,0"
'Define ACS X Axis (if rotation required use DI=distance,angle)
MbeSendKeyin "DL=100"
'Define ACS Y Axis (if rotation required use DI=distance,angle)
MbeSendKeyin "DL=-100,100"
'Save and Attach New ACS tp design file
MbeSendKeyin "Save Acs UNIT#1"
MbeSendKeyin "Attach Acs UNIT#1"
MbeSendKeyin "Attach Acs"
MbeSendKeyin "Reset"
'Set your tentative point readout to use the new Coord System
MbeSendKeyin "SET TPMODE ACSDelta"
MbeSendKeyin "SET TPMODE ACSLocate"
'Once the ACS is set pass a Message Box to the user saying it was
set
Msg = MbeMessageBox ("Your Auxiliary Coordinate system is set to
Unit#1")
Else
'Here we can tell the user via the Microstation prompt that the
Call MbeWritePrompt ("Your have declined to set an Auxiliary
Coordinate system")
End If
End Sub
FrameWorks Plus Categories

FrameWorks Plus categories are defined in the ..\pdshell\categ\framewks.txt file delivered with
PD_Shell. This file maps FrameWorks Plus model levels to the categories used in several
applications such as SmartPlant Review, PD_Draw, and VHL. If you change the default level
scheme for 3D views in FrameWorks Plus, you need to change the framewks.txt file accordingly.
Failure to edit the framewks.txt file will result in the wrong categories being turned off or on. For
example, you want to turn off grids, but the beams disappear instead.
We recommend that you keep a separate framewks.txt file for each project you have and save
the file in the project directory.

FrameWorks Environment
This form provides access to the FrameWorks Plus environment from within PD Shell.
Modeling - Used to select a design area and a model to enter. For more information, see
Modeling (on page 215).
Drawing Environment - Used to create, delete, and enter drawings. For more information, see
Drawing Environment (on page 215).
Propagation - Used to create propagated models and binary files for SmartPlant Review labels.
For more information, see Propagation (on page 216).
Generate ASCII File - Used to create an ASCII file that provides the location of all structural
components and grid lines in the project. This information is used to reference a single structural
column or a pair of grid lines on an isometric drawing. For more information, see Generate
ASCII File (on page 219).
Update/Regenerate Frozen View - Used to update or regenerate frozen views in your
FrameWorks Plus models in batch mode. For more information, see Update/Regenerate Frozen
View (on page 219).
Batch Cutout - Used to create or update solid cutouts in batch mode. For more information, see
Batch Cutout (PD_Shell) (on page 220).
Verify Model - Scans your model checking for zero length members, overlapping members, and
members with invalid sections. For more information, see Verify Model (PD_Shell) (on page
224).
CIM Steel Export - Exports all members to a CIS/2 file based on specific member criteria. For
more information see, CIM Steel Export (PD_Shell) (on page 224).

Modeling
The command is used to enter the FrameWorks Plus modeling environment. Selecting a Design
Area displays all the models in that Design Area. Selecting a model opens the FrameWorks Plus
model in MicroStation.
Drawing Environment
The command is used to enter the FrameWorks Plus drawing composition environment. After
selecting a project, you can create drawings, delete drawings, or go into the drawing
composition environment.
There are no entries in the PDS database for the drawings. The drawings are generic
MicroStation design files.
 Create --- Used to create new drawings in the selected project.
 Delete --- Used to delete drawings from the selected project.
 Composition --- Used to enter a drawing in the selected project.
Create
This form is used to create a drawing in the active project. PD_Shell copies the dseedm.dgn or
dseedf.dgn seed files (depending on the project units) from the ..\fwplus\seed directory to the
project \drw subdirectory.
Drawing Name - Type a name for the drawing you want to create. The drawing name is limited
to 8 characters.
Delete
This form is used to delete a drawing from the active project. Select the drawing to delete from
the list, and then click Accept.
Composition
This form is used to enter the FrameWorks Plus drawing composition environment. Select the
drawing you want to open, and then click Accept.
Create
This form is used to create a drawing in the active project. PD_Shell copies the dseedm.dgn or
dseedf.dgn seed files (depending on the project units) from the ..\fwplus\seed directory to the
project \drw subdirectory.
Drawing Name - Type a name for the drawing you want to create. The drawing name is limited
to 8 characters.

Delete
This form is used to delete a drawing from the active project. Select the drawing to delete from
the list, then click Accept.
Composition
This form is used to enter the FrameWorks Plus drawing composition environment. Select the
drawing you want to open, then click Accept.
Propagation
This form is used to create propagated models based on the option defined during model
creation. The output will be a propagated or propagated and sparse model.
 If you create your propagated model using this command, you should use this command to
keep the propagated model up to date. Do not use the update or regenerate commands or
any of the related commands inside of FrameWorks Plus to update a propagated model.
 You may see this message in the log file, "Unable to locate saved view information. Saved
view information is re-created." This message is not an error message but happens because
the software first deletes the propagated file and then re-creates it.
Propagate Only copies the project related seed file into the project\frz directory and renames it,
and propagates into the file.
Propagate and Sparse copies the model.dgn file from the project\mod directory to the
project\frz directory and propagates into the file.
The batch propagation process uses the symbology from the first 3D isometric view defined in
the FrameWorks Plus model. If no 3D isometric view exists in the model, the software creates a
temporary view using the default isometric settings.
The model.prp file is used for Attach PDS Reference Model command, creating Isometric ASCII
reference file, and SmartPlant Review sessions and labels. To generate Isometric ASCII file and
to identify structural members for Pipe Support placement, you must use Propagate and Sparse
option.
We recommend that you regularly compress your .prp files. An easy way to compress is to use
the Compress Directory command in MicroStation Manager.
Make sure the user section libraries are attached and accessible in the FrameWorks Plus
model.
All Models - Click this button to propagate all the models.
Selected Areas - Click this button to select an area(s) in which you want all models propagated.
Selected Models - Click this button to select the model(s) to propagate.
Submit Batch Immediately / Delayed Batch Submit Time - Choose whether to propagate the
selected models now, or propagate them at a later time.
Ignore Smartcuts - Select this checkbox to ignore SmartCuts when creating the propagated
model.
Schedule Propagation - Select to schedule a reoccurring propagation job.

Scheduled Model Propagation

The Scheduled Model Propagation option is used to specify a periodic schedule for running
batch model propagation.
Before Using This Command

To write schedule data to a hard disk location, confirm the directory path exists and that you
have permission to write files to the directory.
 The log on user (system account or "this account") will impact how you set the account
mapping in Batch Manager. For additional information, see the System Administrator
Responsibilities section of the PDS Project Setup Technical Reference.
 Scheduled Model Propagation does not perform a propagation at the time it is created.
Instead, command files are created to alert the system to perform a propagation at a
specified time of day. The command files are launched by the system scheduler utility.
Operating Sequence
1. Select Schedule Propagation from the FrameWorks Propagate Model form.
The Scheduled Model Propagation form is displayed.
2. Select the required option.
 Create/Revise Model Propagation Schedule (on page 217) --- Creates a scheduled
envelope/clash batch job.
 Create/Revise Model Propagation Schedule (on page 217) --- Revises an existing
 Delete Model Propagation Schedule (on page 218) --- Deletes a scheduled
 Review Schedule (FWP) (on page 218) --- Reviews previously defined envelope/clash
schedules.
Create/Revise Model Propagation Schedule

These options are used to create or revise a schedule for running batch model propagation on a
periodic basis. You can establish multiple scheduled jobs for each project.
Shell Script - The Shell Script field is filled in automatically using the convention
fwprop_<archival_index_no>.
Number - Type up to 24 alphanumeric characters for the name of the model propagation
schedule.
Description - Type up to 40 alphanumeric characters for the description of the model
propagation schedule.
File Specification and Path - Type the file name and directory path for the Model Propagation
Data file. This file defines the time of day for the propagation, the frequency of the propagation,
and the settings for the propagation.
1. Select the Create or Revise option from the Scheduled Model Propagation form.
For the Revise option, a list of all scheduled propagation batch jobs for the active project is
displayed.
2. Select the schedule to be revised; then click Confirm.

The Scheduled Model Propagation Creation/Revision form is displayed showing the

information about the selected scheduled propagation batch job.
3. Type the following information to define a Propagation schedule for the active project.
Number
Description
File Specification
Path
4. Click Confirm to accept the specified information.
A form is displayed to define the schedule frequency and time.
5. Select the frequency of the propagation batch job: Daily, Weekly, or Monthly.
A set of fields is displayed to type the day and time.
6. Select the day of the week/month, and set the time of day (hours and minutes) for the
propagation batch job. Then click Confirm.
A form is displayed to define the Propagation options.
7. Select the appropriate Model Propagation options. Refer to Propagation (on page 216) for
information on these options.
8. Click Confirm.
A set of Model Propagation Command files is created. The file specification for the script is
formed automatically as follows: fwprop_<archival_index_no>
If the time of the scheduled propagation is changed, a new at entry is created and the old
entry must be deleted.
Delete Model Propagation Schedule

The Delete option deletes an existing Model Propagation schedule file.
1. Select the Delete option from the Scheduled Model Propagation form.
A list of propagation schedules for the active project is displayed.
2. Select the propagation schedule to be deleted; then click Confirm.
Accept to Delete FW Propagation Data.
3. Click Confirm to delete the selected schedule.
A warning is displayed with instructions to delete the schedule.
Review Schedule (FWP)

The Review Schedule option lists all scheduled model propagation jobs for the active project
and displays the following basic data.
archival number
frequency of propagation
time of day for propagation
network address for propagation
1. Select the Review Schedule option from the Scheduled Model Propagation form.
The Review Model Propagation Schedule form is displayed.
2. Click Cancel to display the Scheduled Model Propagation form.

Generate ASCII File

The Generate ASCII File command creates an ASCII file used by PDS ISOGEN Intergraph
option 71 to place reference dimensions in the isometric drawing. The ASCII file contains the
names and locations of all structural columns and grids in the PDS project. The created ASCII
file is saved to the PDS main project directory and named fw_projname.dat.
A single structural data file (ASCII file) is created for the entire project. No structural models can
be excluded from being referenced. However, you can edit the file and split out the information
into separate files or you can move the prp files you do not want to process to a different
location. You can then add a variable to the pds.cmd file to select which ASCII file to reference
when generating isometric drawings.
To generate Isometric ASCII file and to identify structural members for Pipe Support
placement, you must use Propagate and Sparse option and the files have to be propagated
using the PDS batch propagation command.
Using unique column and grid label names makes it easier to locate the element in the model.
To use this variable, add the following line to the pds.cmd file:
$ENV{'ISOUSRREFDUM'} = 'path\file.dat';
where path is the path to the project directory and file.dat is the name of the ASCII file you want
to use.
Editing the ASCII File

If you have generated the ASCII file and want to use the variable to control which structural
columns and grid lines are referenced, you need to edit the file and save the individual structural
models (or groups of models) into separate files.
The default grid line reference data file is in the project directory and is named fw_projname.dat.
Open this file using any ASCII editor.
The first column of each line describes the type of data that line contains:
 0 - The line contains the name of the structural model and its UORs extents.
 1 - The line contains structural column information with the column name and the beginning
and end column points in UORs.
 2 - The line contains East/West gridline information with the gridline label and beginning and
end points in UORs.
 3 - The line contains North/South gridline information with the gridline label and beginning
and end points in UORs.
When splitting the generated file into smaller files, be sure to keep all model information together
(that is, cut from one "0" line to the line before the next "0" line).
Update/Regenerate Frozen View

The Update/Regenerate Frozen View command updates or regenerates frozen view graphics in
batch mode.

Do not use this command to update a propagated model.
List Area - Displays the models or selected area that you want to update or regenerate.
Update/Regenerate - Select whether you want to update all models, models in selected areas,
or only selected models.
Update or Regenerate option - Select whether you want to Update the frozen views or
Regenerate the frozen views.
Update automatically updates the permanent, Frozen View graphics to reflect any structural
model changes. The Update Frozen command compares the status of the member graphics in
the Frozen View to the current model status and adds or removes members from the Frozen
View accordingly.
Regenerate recreates all Frozen View graphics from the current model using the current Model
View's display style and settings. All existing graphics in the selected Frozen View are deleted
and replaced with the new graphics.
Include Attached FWPlus Models - Select to include attached FrameWorks Plus models when
the frozen views are updated or regenerated.
Update User Graphics - If this option is on, generic MicroStation elements in the Model View
are also updated or regenerated along with the FrameWorks Plus members. Generic
MicroStation elements that you have added directly to the frozen file (not the model file) using
MicroStation are not affected by this command.
Batch Cutout (PD_Shell)

The Batch Cutouts command automatically places cutouts in slab and solid members where
they intersect with other members. The intersecting member can be a FrameWorks Plus linear
member, a FrameWorks Plus solid member, or generic MicroStation elements (including
MicroStation solids but not wedges, spheres, or torus). Cutouts, unlike holes, automatically
update when the intersecting member is moved, re-sized, or deleted.

Using Batch Cutout may cause unpredictable results in the project and models. For
example, when running batch cutouts, you have no way of knowing which models are attached
or detached to other models. You may lose cutouts if someone else unknowingly detaches a
piping model for example. In addition, you may have set different clearance options in different
models. The batch cutouts process can potentially overwrite those clearance settings. Be
especially diligent when using batch cutouts.
Cutouts are not available for walls.
Guidelines for Solid Cutouts

 FrameWorks Plus does not include the thickness of PDS equipment insulation (if any) when
calculating the cutout size.
 The element that intersects the solids must go all the way through the solid for a cutout to be
created. Elements that do not go all the way through the solid will not create a cutout.
 Cutouts that are invalid holes are not placed.
 If you manually move or copy a cutout (hole) using the Move Member or Copy Member
commands, you will break the link between the cutout and the object that created the cutout.
After the link is broken, the cutout (hole) will not update the next time you run cutouts.
 FrameWorks Plus does not place cutouts for intersecting elements that would cause a
curvilinear cutout (such as a pipe bend or an arc member).
List of Models - Display the model on which the batch cutout process will run.
Clearance - Specifies the distance between the inside of the cutout and the outside of the item
being cut around. This distance is added evenly to all sides of the item. If you are placing a
sleeve around a pipe, the distance between the inside of the sleeve and the outside of the pipe
is the Clearance value. The Clearance value you type in must be in inches for imperial projects
and millimeters for metric projects.
Be careful when defining the Clearance value when cutouts will be created around closed
shapes such as I-section or channels. The Clearance is added evenly to all sides of the shape.
If you define a Clearance that is greater than half the distance between sides of a closed shape,

FrameWorks Plus will not place the cutout. For example, the distance between an I-section's
flanges is 8.5 inches. If you define a Clearance greater than 4.25 inches, the cutout will not be
placed.
Increment - Specifies the value by which to increment the cutout diameter around a circular
penetration (such as a pipe). For example, if you set the Increment to 2" (inches), the cutout
diameter is always divisible by 2 (2", 4", 6", 8", ... 22", 24", 26", and so forth). Similarly, if you set
the Increment to 3", the cutout diameter is always divisible by 3 (3", 6", 9", 12", and so forth).
Setting the Increment value to 0 causes the cutout diameter to be the outside diameter of the
penetrating object plus the Clearance value, if any.
The Increment value you type in must be in inches for imperial projects and millimeters for
metric projects.
You can use the Increment Factor setting to control the rounding up or rounding down of the
cutout diameter to the next allowed size.
Increment Factor - Specifies if the cutout is rounded up or rounded down to the next Increment
size. For example, you place a 10.875 inch pipe with 3 inch clearance and a 2 inch Increment.
You can use this Increment Factor to control whether a cutout with a 16" diameter or a cutout
with a 18" diameter is placed.
If the Increment Factor is set to 0, the cutout is always rounded up to the next increment
divisible size. If the Increment Factor is set to 1, the cutout is always rounded down to the next
increment divisible size. Typically, you would want to set the Increment Factor to 0.5.
If the Increment Factor is between 0.01 and 0.99, FrameWorks Plus calculates whether to round
up or down based on the following algorithm.
Compute the cutout diameter by adding the outside diameter of the pipe with two times the
Clearance value. For example, if the pipe diameter is 10.875" and the Clearance is set to 3", the
cutout diameter would be 16.875" (10.875 + 2 x 3 = 16.875).
FrameWorks Plus reads the remainder (non-integer) part of the cutout diameter. In this case,
0.875 inches.
1. Multiply the Increment and the Increment Factor then compare the results to the remainder
read in step 2. If the remainder is less than the calculation, round down. If the remainder is
greater than the calculation, round up. For this example, say the Increment is set to 2". The
following table shows the results of different Increment Factors.
Remainder from Increment X Increment Resulting Action
step 2 Factor
0.875 2x0=0 0.875 greater than 0 so round cutout

diameter up to 18 inches
0.875 2 x 0.25 = 0.5 0.875 greater than 0.5 so round cutout
diameter up to 18 inches
0.875 2 x 0.5 = 1 0.875 less than 1 so round cutout diameter
down to 16 inches
0.875 2 x 0.75 = 1.5 0.875 less than 1.5 so round cutout
diameter down to 16 inches
0.875 2x1=2 0.875 less than 2 so round cutout diameter
down to 16 inches
Override Original Settings - Toggle on to override the clearance value of an existing cutout
with a new clearance value. This will override all clearance settings in the individual models.
Include Member Fireproofing - The software should consider member fireproofing when
calculating the cutout size. The fireproofing thickness is considered when calculating the cutout

size even if the fireproofing setback is such that the fireproofing does not intersect the solid
member.
Include Piping Insulation Thickness - The software should consider piping insulation
thickness when calculating the cutout size. The piping insulation does not need to be graphically
displayed in order to be used in the calculation.
Report Action - Defines the action to perform when members intersect solids.
 Place Holes & Report -- Places a hole in the solid for the intersecting member to pass
through. The shape of the intersecting member is used as a pattern for the solid's hole. The
size of the hole will be the exact size of the intersecting member unless you specify a
Clearance value.
 Place Holes, Sleeves, & Report -- Places a hole in the solid for the intersecting member to
pass through. If the intersecting member is round, a pipe sleeve is also placed.
Pipe sleeves are placed only if the intersecting member is perpendicular to the slab
or solid. Members that intersect at an angle will not have pipe sleeves placed.
 No Action - Report in Logfile -- Writes the number of members that intersect solids to the
logfile.
Sleeve Type - Specifies the member type you want to use for the sleeve. FrameWorks Plus
uses the default section of the selected member type for the pipe sleeve section. We
recommend you place sleeves using cardinal point 1. This option is only available if the Place
Sleeve option is selected.
FWP Linear Members - Specifies that FrameWorks Plus should place cutouts for FrameWorks
Plus linear members that intersect a solid.
The section shape of the linear member must intersect both faces of the solid for
FrameWorks Plus to place a cutout.
FWP Solid Members - Specifies that FrameWorks Plus should place cutouts for FrameWorks
Plus solids members that intersect a solid.
MSTN Solids, Surfaces & Cones - Specifies that FrameWorks Plus should place cutouts for
MicroStation solid elements that intersect a solid.
FrameWorks Plus will not create cutout for wedge, sphere, or torus MicroStation shapes.

Verify Model (PD_Shell)

The Verify Model command scans your model checking for zero length members, overlapping
members, and members with invalid sections. These invalid member definitions can cause
problems when writing your model out to an analysis input deck file. You can also run the verify
model process from a command line. For more information, see Verify Model Key-in.
All Models - Select to verify all models in the project.
Selected Areas - Select to verify models only in an area that you specify.
Selected Models - Select to verify only the models that you specify.
Submit Batch Immediately - Submits the batch job to verify the models as soon as you click
Accept.
Delay Batch Submit Time - Submits the batch job at a time you specify.
CIM Steel Export (PD_Shell)

This command exports all members to a CIS/2 file based on user-defined member criteria.
During export, the software creates the fwcsexp<model number> folder in the user Temp
directory in which the following log files are saved.
 fwcsexpque.log - Contains information about the success or failure of the export. Possible
causes for an unsuccessful export include attempting to export a model that does not exist
or not having access permissions on the model you are attempting to export.
 <Model Number>_FWCIMSteelExport.log - Contains information about each model. The
software creates a log file for each model selected for export.
For more information about CIM Steel Export, see "Exporting Models from FrameWorks
Plus" in the Frameworks Plus Reference Guide
All Models - Select to export all models in the project.
Selected Areas - Select to export models only in the user-defined area.
Selected Models - Select to export only the user-defined models.
Submit Batch Immediately - Submit the batch job to export the models as soon as you click
Accept.
Delay Batch Submit Time - Submit the batch job at a time you specify.
Define CIM Steel Export Options – Select to specify units, author, organization, and member
criteria. By default, the software uses US Imperial units, and all member types and member
classes are selected.
Units - Specify the units for the CIS/2 file.
Author - Enter your name.
Organization - Enter the name of your organization.
Type – Select the member design types you want to write to the CIS/2 file. By default, all types
are selected.
Class – Select the member classes you want to write to the CIS/2 file. By default, all classes are
selected.

FrameWorks Plus and SmartPlant Review

When batch propagating a model from PD_Shell or freezing a view with the Generate
Propagated Model option on from within FrameWorks Plus, a modelname.drv file is created in
the project's frz directory. This file contains the hard coded SmartPlant Review labels. To use a
customized label, you need to create the label file using DesignReview Label Builder.
To customize the labels for DesignReview Label Builder, you need to go to Reference Data
Manager> Label Description Library Manager> Revise Label Data> Display Attribute Labels.
Then select the label you want to edit.
Labels 325 to 330 are reserved for FrameWorks Plus:
325 - Labels for beams.
326 - Labels for columns.
327 - Labels for braces.
328 - Labels for area elements.
329 - Labels for arcs.
330 - Labels for volume elements.
You cannot use a different number for any FrameWorks Plus labels. When editing labels, you
cannot add attributes to the available attribute list.
After editing labels, you need to click Unapproved --> Approved to move your edits to the
Approved Library.
FrameWorks Plus member names in SmartPlant Review labels are limited to 16
characters. However, FrameWorks Plus supports member names up to 24 characters. To view
all 24 characters in SmartPlant Review, you need to delete the entry for the element name and
insert the ASCII USER ATTRIBUTES 24 character attribute instead.
Refer to the DesignReview Integrator (PD_Review) Reference Guide for more information on
how to create a SmartPlant Review session and labels in DesignReview integrator.
If you change the default level scheme in FrameWorks Plus, you need to edit the framewks.txt
file in the main PDS project/core directory. This file defines the category levels in PD_Draw and
SmartPlant Review. If you change the FrameWorks Plus level scheme but do not edit this file,
the wrong items will disappear when you turn off categories in SmartPlant Review.
In order to generate labels containing new attributes and named group information for
SmartPlant Review, the data needs to be published using SmartPlant Review Publisher. For
more information, see FrameWorks Plus Extended Labels Dialog Box (on page 226).

FrameWorks Plus Extended Labels Dialog Box

Displays when you click the Labels button on the main SmartPlant Review Publisher dialog box,
allowing you to select the binary label information from FrameWorks Plus that you want added
to the SPR label database (MDB2). Only the labels selected here are added to the label
database during the publishing process.
Optional input template file - Allows you to select a label template file (SPRFWPlusLabels.bin)
to use while publishing your project. The settings you specify using this dialog box are saved in
this file so that you can retrieve them each time you publish the project or to use as a template
each time you set up a project for publication. You may have only one label template file per
project and the file must be named SPRFWPlusLabels.bin. You must re-create the label
database (re-publish) each time you want to change the set of binary labels available in the
published project.
File output directory - Allows you to specify the location for the label template file. This path
should point to either the project folder (where the .dri file is located or from where the design file
was opened) or to the same folder where the SmartPlant Review Publisher executable is
located (C:\Program Files\SmartPlant\Review Publisher). If SmartPlant Review Publisher does
not find SPRFWPlusLabels.bin file in either the project or application folder, the binary label data
is not added to the published label database.
Linear and Arc Element Names - When clicked, only linear (structural members like beams
and cross braces) and arc element labels appear for selection in the Label list.
Solid Element Names - When clicked, only solid element (slabs, walls, and solid) labels appear
for selection in the Label list.

Select labels to display - Displays the available binary labels according to the button selected
above. Check the box by the label name to add that label to the label database. Click the arrow
in the column header to sort this list alphabetically, either ascending or descending.
Select All - Click to add all labels in the list to the label database. This button is useful if you
want all but a few of the labels to be included. Simply click this button, then uncheck the labels
that you do not want added to the label database.
Clear All - De-selects all checked labels in the list.
Save - Saves the specified list of labels to the label template file (SPRFWPlusLabels.bin), which
is then used by SmartPlant Review Publisher to add the selected label data to the label
database during the publishing process.
FrameWorks Plus and PD_Clash

The PD_Clash Envelope Builder uses the same executables as those delivered with
FrameWorks Plus. If you install a newer version of FrameWorks Plus, more than likely there
have been fixes made to the envelope builder executables. Before creating any envelope files,
you need to update executables in the PD_Clash bin directory with the files delivered with
FrameWorks Plus. This will ensure that you get the same results when creating envelope files
from within FrameWorks Plus as from within PD_Shell. From a command line, type:
<prod_dir>\bin\clashupd.bat <path_to_clash_bin>
where prod_dir is where you installed FrameWorks Plus and path_to_clash_bin is where you
installed PD_Clash.
For example
c:\ingr\fwplus\bin\clashupd.bat c:\ingr\clash\bin
Creating Envelope Files

There are three ways to create an envelope file for a model:
 Inside PD_Shell using PD_Clash. Start PD_Shell and select a project. Select Interference
Manager. Select Envelope Builder and select Envelope Builder again.
You can create envelope files for interference checking using a command line key-in. The
command syntax is:
 <prod_dir>\bin\fwenvel <proj_dir>\mod\modelfile.dgn <proj_dir>\frz\envfile.env
 where prod_dir is the directory where FrameWorks Plus is loaded. For example:
c:\win32app\ingr\fwplus. proj_dir is the directory that contains the FrameWorks Plus project.
For example: c:\struct\project.
 If the envfile.env file exists, FrameWorks Plus overwrites the existing file with the newly
created file.
 Inside FrameWorks Plus using the File > Interference Checking command.
If you create envelope files inside FrameWorks Plus, the Envelope Verification command
in PD_Shell always indicates that the envelope files are not up to date because the model file
(.dgn file) is always saved and closed after the envelope file was created.
If you want to view your envelope file (it is a binary file), you need to run Envelope Diagnostics
which creates a MicroStation file called "modelname.til" in the FrameWorks Plus project's ..\frz
sub-directory. The software will open that file in MicroStation and attach your model.prp file as a
reference file (if available). You can then compare the envelope graphics to the model graphics.
In addition, a model.evd (an ASCII file) gets created in your temporary directory. Check the .evd
file for errors and warnings.

If there are errors, the envelope file is invalid. You will need to go back into FrameWorks Plus
and run the File> Verify Model command to check for overlapping members and members with
invalid sections.
Cutbacks are not written to the envelope file. However, PD_Clash can determine if there
is a clash between FWP members (even if cutbacks were applied) or not.
Because the FrameWorks Plus member names appear in the report, all FrameWorks Plus
member names should be unique. Using unique member names makes locating the member in
graphics easier.
To review and approve clashes, use PD_Clash Interference Approval Manager or the PDS
integrated commands inside FrameWorks Plus.
FrameWorks Plus and Material Data Publisher

You can now export FrameWorks Plus member data using the PDS Material Data Publisher
Utility. The Material Data Publisher utility (MDP) allows users to generate relational database
tables containing all the material data associated with a PDS model and publish these tables to
a new database schema (MTO_PROJNAME). These tables make the model data available for
easier reporting outside of PD_Report.
The Material Data Publisher uses selection set files to determine what data to publish. The MDP
interface allows you to select specific disciplines, model areas, and models within the project to
publish, and to save different sets of models in separate selection set files.
When the data is published, it can be accessed through ORACLE, INFORMIX, SQL, ODBC
clients such as Microsoft Access, and other database utilities for reporting, tracking, and
ordering.
Please refer to the PDS Material Data Publisher help for more information about MDP.
For the list of tables and attributes that are exported from FrameWorks Plus, from within
FrameWorks Plus click Help > Printable Guides. Then select FrameWorks Plus Material Data
Publisher Chart from the list of documents.
 If a member is partially flooded, the software considers it fully flooded when calculating the
center of buoyancy.
 FrameWorks Plus does not calculate center of buoyancy or the buoyancy force for members
with arbitrary sections.
 If the Material Data Publisher detects a corrupted model, it continues with the next model.

APPENDIX F
Database Setup - Oracle

This appendix describes the setup procedure for Windows and Oracle. Please visit the
Intergraph eCustomer website (www.intergraph.com) for installation instructions for Oracle
beyond Version 11g.
These instructions were created to help Intergraph personnel install Oracle quickly, and
may not generate an optimal configuration for your production environment. Please refer to
Oracle documentation for more detailed instructions.
All domain verified user names and passwords must use ASCII7/English
characters. Oracle does not support non-ASCII / English characters in domain user names or
passwords and will not work. This limitation is an Oracle limitation, not Intergraph's.
In This Appendix
Oracle 11g ..................................................................................... 229
Oracle 10.2g .................................................................................. 248
Oracle 10g ..................................................................................... 264
Oracle 11g
This section covers the installation of Oracle 11g on systems running Windows server. Before
loading Oracle, it is recommended that RIS Oracle Data Server (RISORADS) be loaded. For
more information on installing different versions of Oracle, see the Technical Notes and
Whitepapers section of the eCustomer site.
1. By default, the setup program will install the database software and create all database files
on the C drive. The database software requires a varied amount of space, which can be
large, so plan your installation accordingly. Having installed RISORADS and identified
where the database software and database files will be installed, double-click the setup
executable located in the Oracle 11g installation directory. The system will initialize the
Oracle Universal Installer first showing a command window then the following dialog box.

Select the Oracle Database 11g option, and click Next.
2. Select Advanced Installation, and click Next.

3. Select Custom, and click Next.
4. Define the name of your Oracle Instance and define the Oracle Base Location (Oracle
BASE is a new feature in V11 of Oracle), then click Next.

5. Oracle will run a Product-Specific Prerequisite Check application. After that process
finishes and all checks pass, click Next.
6. Choose your options from the available components list.

The following default components are not needed:
 Oracle Real Application Testing
 Oracle Programmer
There is a new option called Oracle Windows Interfaces which provides ODBC access
OLE options and is a suggested install.

7. When you are done click Next.
8. Select Create a database on the Create Database screen, and click Next.

9. If the component Oracle Services for Microsoft Transaction Server 11.1.0.6.0 is selected
for install, then at this point the installer prompts for Port Number. Retain the default, and
click Next.

10. At this point the installer displays a Summary screen that outlines your choices so far and
allows for review. If needed, you can click Back and change settings. Click Install.

11. The system will start the install process providing you with a dialog showing its progress as
it does the installation:

When the installation is finished the system will display the Configuration Assistants
dialog box and will continue the installation process. It will seem as if the system is hung at
this point but the status in the Tool Name window will state the Oracle Net Configuration
Assistant is In progress.
12. The software will then display the Oracle Net Configuration Assistant dialog box. Select
the Perform typical configuration option, and click Next.

13. The software displays the database setup screen.

The Step # of # option at the top of the dialog does not work properly in this release
of Oracle.
Select the General Purpose Transaction Processing option, and click Next.

14. Type the name of your database in the next dialog box, and click Next.
15. In the Management Options dialog box, leave the Configure Enterprise Manager and
Configure Database Control for local management options checked and click Next.

16. Provide a password for the sys, system, dbsnmp and sysman administration account
users. You can do this by providing different passwords for each or the same for all of them.
When you are finished, click Next.

17. On the Step 5 of 14 dialog box, select the File System option, and click Next.
18. In the next dialog choose the location for your database file as outlined by your
administrator. Keep in mind space and processor needs. When you are finished, click Next.

19. If flash recovery is to be used in your installation, select the option in the next dialog and
click Next.

20. The next dialog box will allow the installation of a sample schema for your use. Clear the
Sample Schemas option and, and click Next.
21. Select the default options in the Initialization Parameters dialog box, and click Next.

22. In the Security Settings dialog box, select the Revert to pre-11g settings option, and click
Next.

23. In the next dialog you can choose from a new option in V11g Oracle to setup and utilize
automatic maintenance tasks. The default setup is turned on. Select the option that meets
your needs and click Next.

24. Make the appropriate changes to the Database Storage dialog box, and click Next.
(Example changes could include changing the USERS01.DBF to PDS01.DBF and so on.)
25. Select the Create Database option from the final dialog box, and click Finish.

26. The software displays a final Confirmation dialog box which shows you the options you
have set. Click OK.

27. The software will now start to install the database and will provide you the following dialog
box showing the installation progress.
28. You will be provided some confirmation dialog boxes outlining the progress of the options
you choose. Click Exit when done.
You can now use iSQL Plus to create users and RIS to create schemas against this database.
For sample scripts see:
C:\Win32App\INGR\PDSHELL\sql\oracle\

Oracle 10.2g
This section covers the installation of Oracle 10.2g on systems running Windows server. Prior to
loading Oracle, it is recommended that RIS Oracle Data Server (RISORADS) be loaded.
1. By default, the setup program will install the database software and create all database files
on the C drive. The database software requires a varied amount of space, which can be
large, so plan your installation accordingly. Having installed RISORADS and identified
where the database software and database files will be installed, double-click the setup
executable located in the Oracle 10.2g installation directory. The system will initialize the
Oracle Universal Installer first showing a command window then the following dialog box.
Choose Advanced installation and click Next.

2. Select the Custom option, and click Next.
3. Define the Name of your Oracle instance, and click Next.

4. Choose your options from the available components list, and click Next.
The Oracle Programmer options are not needed, but it is suggested to install iSQL
Plus.
The product will run some tests to see that your computer is compatible and that it meets
the minimum requirements for Oracle installation. If all checks do not Succeed please see
Oracle installation guide for help. After you have all checks completed and passed, click
Next.

5. On the Create a database dialog box, select the Create a Database option, and click Next.

6. The software displays the Summary dialog box that outlines your choices so far and allows
for review. If necessary, click Back and change settings. Click Install.

7. The system will start the install process providing you with a dialog box showing its progress
as it does the installation.

8. When the installation is finished the system will display the Configuration Assistants
dialog box and will continue the installation process. It will seem as if the system is hung at
this point but the status in the Tool Name window will state the Oracle Net Configuration
Assistant is In progress.

9. The software will then display the Oracle Net Configuration Assistant dialog box. Select
the Perform typical configuration option, and click Next.
10. Select the General Purpose option, and click Next.

11. Type the name of your database in the next dialog box, and click Next.
12. In the Management Options dialog box, leave the Configure the Database with
Enterprise Manager and User Database Control for Database Management options
selected, and click Next.

13. Provide a password for the sys, system, dbsnmp and sysman administration account
users. You can do this by providing different passwords for each or the same for all of them.
Click Next.

14. On the Step 5 of 11 dialog box, select the File System option, and click Next.
15. In the next dialog choose the location for your database file as outlined by your
administrator. Keep in mind space and processor needs. Click Next.

16. If flash recovery is to be used in your installation, select the option in the next dialog, and
click Next.

17. The next dialog box will allow the installation of a sample schema for your use. Clear the
Sample Schemas option and, and click Next.
18. Choose the default options in the Initialization Parameters dialog box, and click Next.

19. Make the appropriate changes to the Database Storage dialog box, and click Next.
(Example changes could include changing the USERS01.DBF to PDS01.DBF and so on.)
20. Select the Create Database option from the final dialog box, and click Finish.

21. The system displays a final Confirmation dialog box which displays the options you have
set. Click OK.

22. The software starts to install the database. It displays the following dialog box showing the
installation progress.
23. You will be provided some confirmation dialog boxes outlining the progress of the options
you choose. Click Exit when done.
You can now use iSQL Plus to create users and RIS to create schemas against this database.
For sample scripts see:
C:\Win32App\INGR\PDSHELL\sql\oracle\
Oracle 10g
Oracle 10g topics:
Removal of Older RIS Client (Oracle 10g) (on page 264)
Production Database Installation (Oracle 10g) (on page 265)
Removal of Older RIS Client (Oracle 10g)

Loading the RIS Oracle data server version 5.7 for Oracle 10g also loads a version of the RIS
client software. If the machine is purely a database server and does not run any applications
(that use RIS) then this may not be a problem. If the machine is a client as well as a database
server then you may need to remove any older versions of the RIS client software. If you have
multiple versions of RIS client software on your machine your applications may not behave as
you expect.
If you are running applications that use the RIS V4 client, you will have to remove it and upgrade
your schemas to V5 after loading the RIS V5 Oracle data server. This is because the RIS V5
Oracle data server does not support connections from RIS V4 clients.
If you are running applications that use RIS V5 client you may have to remove the older versions
(5.0, 5.1) after loading the Oracle data server.

The older versions of the RIS client software can be removed by running the Configure
RIS Version utility from the "highest number" program group. For example, if RIS client 05.02,
05.03, and 05.04 are all loaded, you would run the Configure RIS Version utility in the RIS 05.04
program group. As a precaution, make a copy of the schema file if it is located in any of the
older RIS product directories.
Production Database Installation (Oracle 10g)

These instructions take you through the Oracle 10g install where you do not let the install utility
create the "starter database." In this procedure the Oracle system files are installed and a
database is created using the Database Assistant.
In this example, the database software and files will be installed on the C drive. On a typical
ISMP server, all system drives are spread across all available physical drives by virtue of the
RAID configuration. For this reason the "old UNIX strategy" of scattering the database files
across multiple disks to avoid an I/O bottleneck on a single physical disk may not apply.
The following steps describe the Oracle installation process.
1. Double-click setup.exe to start the installation process.
2. On the Welcome screen, select Advanced Installation, and then click Next.
3. On the Specify File Locations screen, verify that the Source and Destination locations
are correct, and then click Next.
4. Select Custom Installation Type, and then click Next.
5. On the Available Product Components screen, make sure that the necessary Oracle
products are selected.
The following products can be omitted:
 Enterprise Edition Options
 Oracle Development Kit
 Oracle 10g Windows Documentation
Make sure that iSQL Plus is selected.
6. On the Available Product Components screen, click Next.
7. On the Create Database screen, select Yes, and then click Next.
8. On the Summary screen, review the displayed options. If they are correct, click Install.
Otherwise, click Back and reselect the options.
9. After the installation is complete, the Oracle Installer will start a Net Configuration Assistant.
Fill the Select Typical Configuration check box and click Next.
10. Change the Global Database Name/SID to pds and click Next.
11. Select Configure the Database with Enterprise Manager and click Next.
12. Set the passwords for SYS and SYSTEM, and then click Next.
13. Select File System as the Storage Option, and then click Next.
14. Select a database storage location for the database files and click Next.
15. If you want to use Flash Recovery, fill the Specify Flash Recovery Area check box,
specify the Flash Recovery Area and Flash Recovery Area Size settings, and then click
Next.
If you do not want to use Flash Recovery, clear the Specify Flash Recovery Area check
box and click Next.
16. If you want to use Oracle Text, Oracle Data Mining, or Oracle Ultra Search, fill the
appropriate check boxes, specify the settings, and click Next.

If you do not want to use these options, clear the check boxes and click Next.
17. On the Initialization Parameters screen, click Custom, review the default initialization
parameters, and then click Next.
18. Make changes as necessary on the Database Storage screen.
Intergraph recommends the following settings:
Tablespaces
 Expand Tablespaces. Turn off Autoextend for each of the tablespaces.
System
 On the Storage tab, select Managed in Dictionary.
 Initial 100 KB
 Next 100 KB
 Minimum Size 0 KB
 Increment Size by 1%
 Minimum number 1
 Maximum number 121.
Users
 Change the name to pds
 Change the size to 300 MB
 Under Storage, select Managed in Dictionary
 Initial 50 KB
 Next 50 KB
 Maximum number 121
Index
 If it exists, delete the Index tablespace.
Temp
 Change the name to temp_segs
 Change the size to 30 MB
 Under Storage, select Managed in Dictionary
 Initial 100 KB
 Next 100 KB
 Maximum number 121
19. Click Next.
20. On the Creation Options screen, fill the Create Database check box and click Finish.
21. On the verification screen, make sure all the settings are correct and click OK.
22. Database usernames can now be created. Two sql scripts are provided with PDS to create
the database usernames using Oracle 10g. The scripts are located in the
c:\win32app\ingr\pdshell\sql\oracle folder and are called pdsroles.sql and

create_10g.sql. The pdsroles.sql script is used to create the PDSUSER role needed for the
PDS database usernames. The pdsroles.sql script is run only once and can be run from
within SQL Plus by entering @c:\win32app\ingr\pdshell\sql\oracle\pdsroles. After running
the pdsroles.sql script, the create_10g.sql script is edited and run. Below is an excerpt from
create_10g.sql for the pd_proj1 username.
CREATE USER pd_proj1 PROFILE DEFAULT IDENTIFIED BY pd_proj1
DEFAULT TABLESPACE USERS TEMPORARY TABLESPACE TEMP ACCOUNT UNLOCK;
GRANT CONNECT, RESOURCE, PDSUSER TO pd_proj1;
23. A schema can now be created against this Oracle user name. In the Create Schema form
the database user name will be the user name you created in SQL Plus (pd_proj1). The
database management system location will be where you installed Oracle (c:\ora90, in this
example). The database name will be the same as your SID (pds in this example). The o/s
user name and network address will be specific to your server.
 You must be able to log in on the database server as the specified o/s user name.
 A new Oracle user name must be created for each new schema that you wish to create.
An Oracle user name and all of the objects that user owns can be deleted (from within
SQL Plus) using the following command:
drop user username cascade;
24. By default, Oracle 10g is installed to a folder such as d:\oracle\product\10.1.0\Db_1. You
must modify the permissions for the Db_1 folder to allow Read and Execute, List Folder, and
Read access to the operating system user specified when creating the RIS schema.
If these permissions are not granted, you may see an error message similar to the following
message:
RIS Error: RIS_E_INV_OPEN_DB (0x8a948e22)
CREATE SCHEMA sch2 ON DATABASE (oracle DBNAME orcl, OSTYPE NT, DIR
d:\oracle\product\10.1.0\Db_1, REMOTE (TCP db2003))
Underlying dbms could not open database
Oracle Error -12557
Error while trying to retrieve text for ORA-12557
This error does not occur if you create the schema on the database server while you
are logged on as an administrator.
Oracle 10.2.0.5 Client Installation on Windows 7

For Windows 7 client support, you need to install the Oracle 10g Release 2, and then the Oracle
10.2.0.5 patch. You can download the Oracle 10.2.0.3 client media from the Oracle TechNet site
or obtain it from Intergraph.
Use the following steps to download the client and complete installation:
1. Open a new browser session, and then go to the Oracle website at
http://www.technet.oracle.com.
2. Select Download > Databases > Database 10g and locate the Oracle Database 10g
Release 2 client (32- or 64-bit) downloadable zip file.
3. Follow the instructions provided by Oracle to download and install the client software.
The software currently says it is for MS Vista / 2008R1. This is the software you will
need.
4. During the client installation, check the following options:

Checking operating system requirements

Checking service pack requirements
When finished, the Status field will indicate User Verified as illustrated:
5. Complete the Oracle Client installation.

6. Obtain the 10.2.0.5 patch from Intergraph’s Oracle support group (or your Oracle
maintenance provider if Intergraph does not provide maintenance for your Oracle licenses).
7. Install and apply the 10.2.0.5 patch to the 10.2.0.3/10.2.0.4 Oracle Client.

APPENDIX G
Database Setup - Microsoft SQL

This appendix covers the installation of Microsoft SQL Server (MSSQL) on systems running a
Windows-based server. Prior to loading MSSQL, we recommend that the RIS MSSQL Data
server (RISMSFDS) be loaded.
In This Appendix
MSSQL Server 2008 ...................................................................... 269
MSSQL Server 2005 ...................................................................... 281
MSSQL Server 2008

This document covers the installation of Microsoft SQL Server (MSSQL) v2008 on systems
running Windows server. Prior to loading MSSQL, it is recommended that RIS MSSQL Data
Server (RISMSFDS) be loaded.
Installing MSSQL 2008

By default, the setup program will install the database software and create all database files on
the C drive. The database software requires approximately 100 MB, while another 120 MB will
be required for a database sufficient for a PDS project.
1. After you have installed RISMSFDS and identified where the database software and
database files will be installed, double-click the setup executable located in the SQL Server
2008 installation directory.

2. Click Installation on the left side of the dialog box.
3. Click New SQL Server stand-alone installation or add features to an existing

installation.

4. Check for any Setup Support Rules errors, and click OK.
5. Enter the product key, and click Next.

6. Accept the license terms, and click Next.
7. Select Setup Support Files, and click Install.

8. Check for any Setup Support Rules errors, and click Next.
9. Select Database Engine Services and Management Tools – Basic as features to be

installed. Specify the Shared feature directory and Shared feature directory (x86), Click
Next.

10. Select Default instance and specify Instance root directory, and click Next.
11. Review the Disk Space Requirements, and click Next.

12. Change the Account Name box to NT AUTHORITY\SYSTEM for SQL Server Agent and
SQL Server Database Engine, click Next.
13. Select Mixed Mode. Specify a password for the SQL Server system administrators. Add
SQL Server administrators as needed, and click Next.

14. On the Error and Usage Reporting dialog box, click Next.
15. Check for any Installation Rules errors, and click Next.

16. Review the features to be installed, and click Install (installation may take several minutes).
17. After installation is complete, click Next.
18. Click Close.

Creating the User Database in MSSQL 2008

1. From the Start menu, select Programs -> Microsoft SQL Server 2008 -> SQL Server
Management Studio.
2. From the Server type list, select Database Engine.

From the Server name list, select the local server name.
From the Authentication list, select Windows Authentication for users specified as SQL
Server administrators.
3. Click Connect.

SQL Server Management Studio has an explorer-style interface that lets you manage your
databases and perform a number of administrative duties. Pick the server name from the left
window pane, and you should see a number of folders in the right pane that allow you to
perform a variety of tasks on you installation.
4. In the left window pane, expand the server name where the PDS database will be created,
right click on Databases and select New Database.

5. Enter a Database name and click OK to create the database; the new files should be seen
in the specified directory.
Creating Logins and Usernames for Schemas

1. In Management Studio, select File -> Open -> File.
If PDS is loaded, browse to C:\win32app\ingr\pdshell\sql\mssql\create_2005 to open the
delivered script.
Or, use the below script to create a user and login.
CREATE LOGIN pd_proj1 WITH PASSWORD = 'pd_proj1', CHECK_POLICY = OFF
go
USE PDS
go
CREATE USER pd_proj1 FOR LOGIN pd_proj1
go
Create Schema pd_proj1 authorization pd_proj1
go
Alter user pd_proj1 with default_schema = pd_proj1
go
sp_addrolemember 'db_owner', 'pd_proj1'
go
This script creates a login, and then it attaches to a database, creates a username (with the
same name), associates that username with the previously created login, and grants that
user privilege to create and delete objects in the current database. The login is created once
per SQL Server and the username is created once per database. A single login can be
associated with multiple usernames in multiple databases.
When revising the short script shown above to create all logins/users for a project, just
remember to create all the logins before you connect to the pds database, then after
connecting to the pds database create all users and grant privileges.

2. Select Parse and Execute to create logins and users

The only messages you should see include “Command(s) completed successfully”.
3. You can now create schemas against this database. From RIS schema manager, go into
the Create Schema form and enter the following info:
schema name = “pd_ proj1”
net address = “name of db server”
db username = “pd_ proj1/ pd_ proj1”
o/s type = “Windows NT”
db type = “MSSQL”
db name = “pds”
o/s username = “valid login on the db server”
You can then drop this test schema and proceed to create your PDS project.
MSSQL Server 2005

This section covers the installation of Microsoft SQL Server (MSSQL) version 2005 on systems
running a MS Windows Server. Prior to loading MSSQL 2005, it is suggested that the RIS
MSSQL Data server (RISMSFDS) be loaded.
Installing MSSQL 2005

By default, the setup program installs the database software and creates all database files on
the C drive. The database software requires approximately 100MB (not including the on-line
books). Another 120MB would be required for a database sufficient for a PDS 2D/3D project.
Installation
Follow the steps below to install MSSQL Server version 2005.
1. Having installed RISMSFDS and identified where the database software and database files
will be installed, start the setup program by double-clicking on autorun.exe.
2. Select Local Computer and then click Next.
3. Choose the option Create a new instance of SQL Server and then click Next to continue.
4. Enter your Company/Name and continue.
5. Accept Yes: on the next screen.
6. Choose the options below and then click Next to continue.
 SQL Server Database Services
 Workstation Components
7. On the next screen accept the Default selection, which installs a default instance (i.e. one
identified by the name of the computer on which you are installing MSSQL).
For RIS to work with MSSQL 2005, the current installation of MSSQL should be
the Default Instance on the machine. If there's already a default instance, then RIS will not
be able to communicate with the MSSQL Server. Also, you can have only one default
instance per computer and the next one that you create must be a named instance.
8. Click Next to continue.
9. In the Setup Type form, select Typical. You can also specify different locations for program
and data files by using the Browse buttons.
If you have another installation of MSSQL from which you would like to import data,
then select Custom and then choose the same Sort Order as in the other installation so

that you can import/export data between the two. THIS IS A VERY IMPORTANT CHOICE
THAT MUST BE MADE IF YOU ARE USING A RIS-BASED APPLICATION. Even if you
start using an ODBC-based application, if there is a chance that you will want to connect to
this server using a RIS-based application, then you must select a case-sensitive sort order.
10. After changing or accepting the default the sort order to Dictionary Order – Case Sensitive,
accept the defaults for the remaining choices in this form. Continue on to the Service
Accounts form.
11. In the Services Accounts form, change the Service Settings to Use the built-in System
account. Click Next to continue.
12. Select either Windows Authentication Mode or Mixed Mode. If you select Mixed Mode, you
must specify a password for the MSSQL 2005 system administrator user (sa).
If you are creating PDS-specific logins for each project, this is possible only when you
are set up in Mixed Mode.
13. Click Next to continue. If you selected Custom in the previous form, you are presented with
the Collation Settings form. Choose the sort order other than the default, which is Dictionary
order, case-insensitive, for use with 1252 Character Set.
-or-
Accept the default Dictionary order, case-insensitive, for use with 1252 Character Set
option.
You will need to take into account the Sort Order if you would like to install databases
for other applications (INTOOLS, SPPID) on the same instance. The above will also work
with INTOOLS.
14. Click Next to continue.
15. Click Next on the Error and Usage Report Settings.
16. Accept the defaults on the screen and then click Next.
17. Accept Next again to go to the Licensing Mode form. Select your licensing mode and click
Continue.
18. Select Install. Wait for the install to finish (this may take several minutes).
19. Click Next and then click Finish.
20. At this point, MDAC 2.6 is installed. Files are copied to your local drive, and services are
installed and started. You are then asked to reboot.
Configuration Using the Microsoft SQL Server Management Studio

Microsoft SQL Server Management Studio has an explorer-style interface that lets you manage
your databases and perform many administrative duties.
1. After rebooting go to the folder: ..\Microsoft SQL Server\MSSQL\Data directory (default is
C:\Program Files\Microsoft SQL Server). There you find the data files (mdf) and log files (ldf)
for the delivered databases which include:
 Master
 Model
 Msdb
 Tempdb
If you have installed another instance of MSSQL 2005 on the same machine, the
location is: \Program Files\Microsoft SQL Server\MSSQL$instance_name\Data\ directory.
The files you are concerned with at this point are master, model, and tempdb.
 The master database contains information about the entire MSSQL setup. This includes
the locations of all data files, the list of all users and logins, and much more.

 The model database can be thought of as a "seed file" that is used as the basis for
creation of new databases.
 The tempdb database is where information is temporarily stored when performing
operations such as sorts.
2. From the Start Menu, select Microsoft SQL Server Management Studio.
3. In the Connect to Server dialog box, select the Server Name gadget and select <Browse
for More>.
4. Select Database Engine and select the local server from the list. Click OK.
5. Select Connect to connect to the database.
6. Select your server name in the left pane. In the right pane, you see the folders that enable
you to perform a variety of tasks on your installation.
7. Right-click on your server name and select Properties.
8. Under the General tab, note if auto-start is set.
9. Under the Memory tab, note that MSSQL can now dynamically allocate memory as
required, or run with a fixed amount. Depending on the amount of memory available on your
server and on the additional workload, you may wish to either:
 Use Dynamic Allocation with an upper limit in place
 Use Fixed Allocation and specify the amount to use
10. You can examine the settings under the remaining tabs and then click Apply to save your
edits.
11. Leave the settings for the master, model, and tempdb at their default settings. Click OK to
exit the application.

Creating the User Database in MSSQL 2005

After you have installed MSSQL 2005, follow the steps below to create a database for PDS to
use.
1. From the Start Menu, select Microsoft SQL Server Management Studio.
2. Select Databases in the left pane and right-click to select New Database.
General Page
3. Enter a database name of pds.
4. Under Database Files verify/modify the file name/location as needed.
5. Set the initial size for the Data File Type to 100M and the initial size of the Log File Type to
20M.
Options Page.
6. Click OK to create the database and the new files display in the specified directory.
Creating Logins and User Names

Having created the pds database, You need to create logins and user names for the schemas to
use. The suggested way to do this is to create a script and then run this script from inside
Management Studio. A sample script named create_2005.sql is delivered with PD_Shell in the
pdshell\sql\mssql\ directory.

CREATE LOGIN pd_proj1 WITH PASSWORD = 'pd_proj1', CHECK_POLICY = OFF

go
USE PDS
go
CREATE USER pd_proj1 FOR LOGIN pd_proj1
go
Create Schema pd_proj1 authorization pd_proj1
go
Alter user pd_proj1 with default_schema = pd_proj1
go
sp_addrolemember 'db_owner', 'pd_proj1'
go
This script creates a login, then:
1. The script "attaches" to a database.
2. Creates a user name (with the same name), associates that user name with the
previously-created login.
3. Grants that user privilege to create and delete objects in the current database (for details
see the online books or the Transact-SQL Reference Guide). The login is created once per
MSSQL Server and the user name is created once per database. A single login can be
associated with multiple user names in multiple databases.
When revising the short script shown above to create all logins/users for a project, remember to
create all the logins before you connect to the pds database. Then after connecting to the pds
database, create all users and grant privileges. A sample script to create all users for a typical
PDS project is delivered with PD Shell in the sql\mssql directory.
To run this script:
1. Start the Management Studio and select Open File.
2. Browse to the create_2005.sql file, which was made earlier.
3. Load this file and run it by selecting the green arrow that points to the right from the menu
bar. The only messages you see include "new login created" and "granted database
access."
Creating Database Schemas

Follow the steps below to create schemas against this database.
1. From RIS schema manager, go into the Create Schema form and enter the following
information:
schema name = pd_ proj1
net address = name of db server
db username = pd_ proj1/ pd_ proj1
/s type = Windows NT
db type = MSSQL
db name = pds
o/s username = valid login on the db server
2. If the schema creation is successful, you can drop this test schema and proceed to create
your PDS project.

Creating Database Backups

There are a number of ways to backup your database once it has been created. One way is to
use Management Studio as described below.
1. Select a database.
2. In the RHS, select Management and right-click to select Back Up.
3. Complete the forms to create a backup.
To create a recurring backup:
1. Expand the Maintenance folder and select Maintenance Plan.
2. Right-click and select New Maintenance Plan or Maintenance Plan Wizard.
3. These maintenance plans can be quite extensive and include updating of system statistics,
etc. You can de-select all of the options and choose to schedule a recurring daily backup.
After creating the backup plan you should monitor the location of the output file and make
sure it is being updated every day, and also make sure that this backup file is being written
to tape after it has been created.

APPENDIX H
The PDS queue_descript File

The information in the queue_descript file controls which queues are used by PDS for its batch
options. The default entries included in the queue_descript file are:
PDprint, PDprint_1, PDprint_2, and so on

Used to print reports from interactive processing as well as batch processing.
PDdraw_plot, PDdraw_plt_1, PDdraw_plt_2, and so on

Used by the batch queues Pdplot and Pdplot_model to plot the drawing or piping model
selected.
PDifc_plot, PDifc_plt_1, PDifc_plt_2, and so on

Used by the batch queue Pdclash_server to plot interference clashes.
PDhline, PDhline_1, PDhline_2, and so on

Selects the queue/node for the processing of the vector hidden line software.
PDiso_plot, PDiso_plt_1, PDiso_plt_2, and so on

Used by the queue Pdiso_batch for automatic plotting of isometric extractions, or from the
Interactive Isometric software to plot isometric extractions.
PDiso_batch, PDiso_bat_1, PDiso_bat_2, and so on

Selects the queue/node for the processing of the batch isometrics.
The content of the queue_descript file are interpreted differently depending on the system
configuration. This appendix describes those differences. The following is an example
queue_descript file to be referenced in this appendix:
! Sample queue_descript file....
! Blank lines and comment lines beginning with '!' in the first column
! are allowed anywhere in the file.
PDprint network printer,\\PDSTRF\LaserJet
PDprint_1 Windows Connected Printer on a Windows node, \\PLAW\laserjet
PDprint_2
PDprint_3
PDprint_4
PDprint_5
PDiso_batch Process Locally,PDisocreate
PDiso_bat_1 Process on PDSSK
PDiso_bat_2 Process on PDSBCNT

Format of the queue_descript File

Entries in the queue_descript are defined as:
Printer/Plotter
 PDprint is the PDS-recognized printer name.
 The PDS printer name is followed by a TAB.
 After the TAB, the description which is displayed to the user is entered, network printer in
this example.
 If the optional printer name is being used, a comma is next.
 The optional printer name \\PDSTRF\LaserJet is entered last.
It is valid to omit the optional printer name. The PDS software would then search for a printer
named PDprint. If PDprint is associated with a user-defined printer name, such as
\\PDSTRF\LaserJet, the software looks for \\PDSTRF\LaserJet instead of PDprint. For example:
PDprint network printer
---OR---
Batch Queue Definition

PDiso_ batch Process Locally, PDisocreate
 PDiso_batch is the PDS-recognized queue name.
 The PDS queue name is followed by a TAB.
 After the TAB, the description which displays to the user is entered, Process Locally in this
example.
 If the optional queue name is being used, a comma is next.
 The optional queue name PDisocreate is entered last.
It is valid to omit the optional queue name. The PDS software would then search for a queue
named PDiso_batch. If PDiso_batch is associated with a user-defined queue name, such as
PDisocreate, the software looks for PDisocreate instead of PDiso_batch. For example:
PDiso_batch Process Locally
---OR---
PDiso_batch Process Locally, PDisocreate

General Processing Rules for Printers/Plotters

When a PDS job prints or plots, the PDS software shows you which printers are available. If
submitting a batch job which prints/plots, the software determines if the job is processed locally,
or if it is piped to another node, and displays a list of printers available to the batch job.
Local Processing
If the batch job is processed locally, the PDS software looks on the local node for printers that
match those in the queue_descript file. Those printers that are valid on the local node are
displayed. If there are no printers on the local node that match those listed in the
queue_descript, the PDS software displays all of the printers defined on the local node.
Remote Processing on the Same Platform

If the batch job is piped to another node of the same type, the PDS software searches the
destination/processing node for valid printer names that are listed in the queue_descript file.
Valid printers are displayed. If there are no printers on the destination node that match those
listed in the queue_descript, the PDS software displays all of the printers on the destination
node.
Remote Processing on Different Platforms

If the PDS batch job is piped across platforms, no printer validation is done. Because printers
cannot be validated, all printers (for example, the PDprint list when printing, the PDdraw_plot list
when plotting drawings or piping models, and so on) in the queue_descript file are displayed. It
is up to you to make the descriptions in the queue_descript file explicit enough so that a valid
printer on the processing node can be selected from the list.
Configuration for this Example

Client Computers:
nt_one No printer connections.
Batch job PDiso_batch piped to server
nt_s_one.
Batch job PDiso_bat_1 piped to computer
nt_three.
nt_two Printer connections \\PDSTRF\LaserJet and
\\PLAW\laserjet.
All batch jobs are locally executed.
nt_three Printer connection \\nt_s_one\printer1.
All batch jobs are locally executed.
Servers:
nt_s_one Printer connections \\PDSTRF\LaserJet and
\\PLAW\laserjet.

PDS Print/Plot Jobs and the queue_descript File

Some PDS batch jobs have the ability to submit their output for printing/plotting. PD_Report
material take off reports and the PD_Data/physical library data manager/report option are good
examples of this. In general, PDS references the queue_descript file for printer/plotter definitions
associated with the PDprint and PDprint_* entries for print jobs, with PDdraw_plot and
PDdrw_plt_* entries for draw plot jobs, and so on, and displays a list of printers. The specifics
vary somewhat depending on the configuration. The following descriptions use the previous
node configuration.
Submitted Locally
If the PDS batch job is being processed locally, and you have elected to print the output at the
completion of the batch job, the PDS software reads the project queue_descript file, and
validates printers on the local node. Any printer that it finds on the local node which matches the
printer (or optional printer) name in the queue_descript file is displayed.
Using the example queue_descript file and initiating the batch process on node nt_two, the
following printer descriptions display:
network printer
Windows Connected Printer on a computer
If none of the printers in the queue_descript file exist on the local node, all of the printers on the
local node are displayed. Using the example queue_descript file and initiating the batch process
on computer nt_three, the following printer descriptions display:
\\nt_s_one\printer1
This is because none of the other printers described in the que_descript file exist on computer
nt_three.
Submitted From One Computer to Another Computer

If the PDS batch job is piped from one computer to another computer, and you have elected to
print the output at the completion of the batch job, the PDS software will read the project
queue_descript file and validate printers on the processing computer. This means that the
software searches the processing computer for printer names as defined in the queue_descript
file. All valid printers on the processing computer are displayed.
Using the example que_descript file and initiating the batch process on computer nt_one (with
the goal of redirecting the batch job to server nt_s_one), the following printer descriptions
display:
network printer
Windows Connected Printer on a Computer
If none of the printers in the queue_descript file exist on the processing computer, all of the
printers on the processing computer are displayed. Using the example queue_descript file and
using computer nt_one to pipe a batch job to computer nt_three, the following list of printer
descriptions displays:
ilp814@cx_s_one
\\nt_s_one\printer1
This is because none of the other printers described in the que_descript file exist on computer
nt_three.

Interactive Jobs Which Print/Plot

If you are printing interactively from within PDS (for example, Project Data Manager Report of
Type 63 Data), the PDS software reads the project queue_descript file and validates printers for
the local node. Any printer that it finds on the local node which matches the printer name in the
queue_descript file displays. If none of the printers in the queue_descript file exist on the local
node, all of the printers available on the local node will display.
PDS Batch Jobs and the queue_descript File

The hidden-line removal process which is started through Drawing Manager and isometric
drawing extraction process which is started through Isometric Drawing Manager/Batch are PDS
batch jobs which access the queue_descript file. The PDS software reads the project
queue_descript file and validates the batch queues on the local node.
For isometric extraction, if there are no valid batch queues found in the queue_descript file, all
batch queues on the local node display.


APPENDIX I
PDS and Windows

This appendix describes the changes that must be made to your client and server nodes when
moving to Windows 2000, Server 2008 or Windows 7. If you have problems with any of the
procedures described here please log a problem to the Help Desk.
In This Appendix
PDS and Windows 7 / Server 2008 ............................................... 293
PDS and Windows 2000 ................................................................ 297
PDS and Windows 7 / Server 2008

A number of changes must be made to your client node before PDS is installed on a machine
running the Windows 7 / Server 2008 operating system.
Registry Entries (Windows 7 / Server 2008) (on page 293)
Location of RIS Schemas File (Windows 7 / Server 2008) (on page 296)
Environment Variables (Windows 7 / Server 2008) (on page 297)
Registry Entries (Windows 7 / Server 2008)

This section covers PDS installation prerequisites for Windows 7 / Server 2008.
During the PDS installation, do not install any of the products into a folder with a space in
the path. For example, by default, Iplot will load into the "c:\Program Files" folder. You must
change the path to a folder without spaces, for example: "d:\win32app\ingr\iplot".
The Remote Registry service must be running. You need to enable Remote
Registry service, as it is not on by default in Windows 7. If this service is not running, then some
of the batch processes might fail. To enable the service, refer Enabling Remote Registry
service.
To enable Remote Registry you should be a member of the local administration
group or its equivalent on the remote computer.
1. Select Start > Control Panel > Administrative tools > Services.
2. In the console pane, look for Remote Registry. Right-click on Remote Registry, and then
select Properties.
3. Set Startup Type to Automatic.
4. Click Start.
5. Click OK.
32-Bit Operating Systems

If No Intergraph Products Loaded
1. Start the registry editor (regedt32.exe).
2. Locate the HKEY_LOCAL_MACHINE > SOFTWARE folder and double-click on it.
3. Create the INTERGRAPH folder by selecting EDIT > ADD KEY from the registry editor
menu bar.

PDS and Windows
If the Intergraph network adapter has been loaded, this folder will already exist.
4. Enter Intergraph for the KEY NAME. Note that it is case-sensitive.
5. Leave the CLASS field empty.
6. An Intergraph key now displays under the SOFTWARE folder.
7. Highlight the new Intergraph key and select EDIT > ADD VALUE from the registry editor
menu bar.
8. Enter COMMON for the VALUE NAME. Note that it is case-sensitive.
9. Select REG_SZ from the drop-down list for the DATA TYPE and click OK.
10. Enter C:\win32app\ingr\share in the String Editor form. The information that appears in
the right-hand side of the registry editor when you open the Intergraph folder should look like
this:
COMMON: REG_SZ: c:\win32app\ingr\share
Intergraph Products Already Loaded
1. Start the registry editor and locate the HKEY_LOCAL_MACHINE on the Local Machine
window.
2. Locate the SOFTWARE folder and double-click on it.
3. Open the INTERGRAPH key and look on the right-hand side.
The COMMON value should be set as shown below:
Common:REG_SZ:C:\Program Files\Common Files\Intergraph
4. If so, change the string for the COMMON key to read C:\win32app\ingr\share.
5. Go to the C:\Program Files\Common Files\Intergraph directory using Explorer and note
which Intergraph products have files loaded in this location. Remove these products and
reload them.
64-bit Operating Systems

If No Intergraph Products Loaded
2. Locate the HKEY_LOCAL_MACHINE > SOFTWARE > Wow6432Node folder and
double-click on it.
3. Create the INTERGRAPH folder by selecting EDIT > ADD KEY from the registry editor
menu bar.
If the Intergraph network adapter has been loaded, this folder will already exist.
4. Enter Intergraph for the KEY NAME. Note that it is case-sensitive.
6. An Intergraph key now displays under the SOFTWARE folder.
7. Highlight the new Intergraph key and select EDIT > ADD VALUE from the registry editor
menu bar.
8. Enter COMMON for the VALUE NAME. Note that it is case-sensitive.
9. Select REG_SZ from the drop-down list for the DATA TYPE and click OK.
10. Enter C:\win32app\ingr\share in the String Editor form. The information that appears in
the right-hand side of the registry editor when you open the Intergraph folder should look like
this:

PDS and Windows
1. Start the registry editor and locate the HKEY_LOCAL_MACHINE on the Local Machine
window.
2. Locate the SOFTWARE > Wow6432Node folder and double-click on it.
3. Open the INTERGRAPH key and look on the right-hand side.
4. If so, change the string for the COMMON key to read C:\win32app\ingr\share.
5. Go to the C:\Program Files\Common Files\Intergraph directory using Explorer and note
which Intergraph products have files loaded in this location. Remove these products and
reload them.
Creation of "DisableUNCCheck"
This change should be made on all Windows 7 workstations and Windows 2008 Servers, where
the COMMAND PROCESSOR key does not already exist. The time at which you do this is not
critical (i.e.-if you have already loaded products you can still make this change).
1. Start the Registry Editor and locate the HKEY_LOCAL_MACHINE on the Local Machine
window.
2. Go to SOFTWARE > MICROSOFT to open the Microsoft folder.
3. Select EDIT > ADD KEY from the registry editor menu bar.
4. Enter COMMAND PROCESSOR for the Key Name. Note that it is a case-sensitive. Make
sure you leave a blank space between the two words.
6. If you have done this correctly, you should see the COMMAND PROCESSOR folder under
the MICROSOFT folder.
7. Highlight the new COMMAND PROCESSOR key and from the Registry Editor menu bar
and select EDIT > ADD VALUE.
8. Enter DisableUNCCheck for the Value Name. Note that this is a single word and it is
case-sensitive.
9. Select REG_DWORD from the drop-down list for the Data Type and then click OK.
10. Select the Hex radio button in the DWORD Editor, and enter 1 (numeric one) in the Data
field.
The information that displays in the right side of the Registry Editor when you open the
COMMAND PROCESSOR folder should look like this:
DisableUNCCheck::REG_DWORD:0x1
Winreg Key
All paths defined within the PDS project are defined with a NODENAME and the actual PATH to
the file or directory on the node. There is a registry entry named HKEY_LOCAL_MACHINE >
System > CurrentControlSet > Services > LanManServer > Shares that contains a listing of the
Shares available on the server, and the local path to those shares. The mount code used by
PDS takes the NODENAME and PATH from the PDS project, accesses the registry key,
HKEY_LOCAL_MACHINE > System > CurrentControlSet > Services > LanManServer > Shares,
and attempts to resolve the NODENAME and PATH into a UNC path. Once successful, this
UNC path is passed back to PDS to access the needed files. This explains why in a new
installation of PDS, when the WINREG key of the server has not been modified, only users who
are administrators on the server can successfully use PDS.

PDS and Windows
In the past, it was recommended that you delete the WINREG key to resolve this problem. But,
by adding the path to the HKEY_LOCAL_MACHINE > System > CurrentControlSet > Services >
LanManServer > Shares key to the AllowedPaths sub-key of the WINREG key, all users will
have access to the information needed to resolve the NODENAME and PATH into a UNC path
for use by PDS.
This modification is needed on all server nodes and should be done prior to project creation.
This modification is also needed on any client nodes that will use remote batch queues to pipe
PDS batch jobs to another machine for processing.
1. Include Path.
a. Open the registry on the server using regedt32.exe.
b. Find the key HKEY_LOCAL_MACHINE > System > CurrentControlSet > Control >
SecurePipeServers > WINREG > AllowedPaths.
c. Select the AllowedPaths registry key.
This is a multi-line value.
d. Double click on the value to open the Multi-String Editor.
e. Enter System\CurrentControlSet\Services\LanManServer\Shares and then click OK.
f. All users should now be able to use PDS without requiring Administrative rights on the
server.
g. Reboot the server.
2. Delete the Winreg key.
a. Start the registry editor and again locate the HKEY_LOCAL_MACHINE on the Local
Machine window.
b. Locate the folder SYSTEM > CurrentControlSet > Control > SecurePipeServers >
Winreg.
c. Delete the winreg key by selecting it and pressing the Delete key on your keyboard.
d. Reboot the server.
The common errors associated with the WINREG key are listed below.
'Maximum Number of Shares Exceeded'
'Error 67, Error Mounting Remotename'
'Net address and directory could not be mounted verify the specified control files'
'Error in Number of Columns' when trying to create Equipment Models'
'No Matching Sharename for drive letter:\path'
Empty log files when routing PDS batch queues to a remote machine for processing.
Location of RIS Schemas File (Windows 7 / Server 2008)

When using Windows 7 / Server 2008 you have two options for the schemas file location. The
first option is to specify a LOCAL schemas file and enter a UNC path that specifies the location
on the server. The second option is to use TCP\IP as the protocol and specify a valid login on
the server.
UNC Path
You can also use a UNC path to locate the schema file.
1. Share the directory where the schemas file is located.
2. Open the Locate Schema File form on the client node.
3. Select Local as the protocol for the schema file location.

PDS and Windows
4. Enter: \\server\driveletter\dirname\schemas.
As an example: \\pdssmp1\c:\ris\schemas.
FTP Server is not required for this to work.
 Some systems have not worked with the colon after the drive letter. In this case, use the
following syntax: \\pdssmp1\c\ris\schemas.
 Locating the schemas file in this manner uses Windows Server 2008 licenses (as seen in
Control Panel > Licensing).
TCP\IP
1. Install and configure FTP Server on the server.
2. Locate the schemas file from a client node and specify TCP\IP as the protocol.
Environment Variables (Windows 7 / Server 2008)

Windows creates default temp and tmp paths of %USERPROFILE%\Appdata\local\temp for
each user. You need to delete or modify the users default paths for temp\tmp and create path
names without spaces.
PDS and Windows 2000

Topics:
Registry Entries (on page 297)
Location of RIS Schemas File (on page 300)
Environment Variables (on page 300)
Active Directories and Windows 2000 Domain (on page 300)
Registry Entries
Creation/Modification of "Common" key
This section covers PDS installation prerequisites for Windows-based computers.
During the PDS installation, do not install any of the products into a directory with a space
in the path. For example, by default Iplot will load into the "Program Files" directory. Change the
path to a directory without spaces, for example "d:\win32app\ingr\iplot".
No Intergraph Products Loaded

2. Locate the HKEY_LOCAL_MACHINE>SOFTWARE folder and double-click on it.
3. Create the INTERGRAPH folder by picking EDIT > ADD KEY from the registry editor menu
bar.
If Intergraph network adapter has been loaded, this folder will already exist.
4. Enter Intergraph for the KEY NAME.
Note that it is case-sensitive. You can leave the CLASS field empty.
5. You should now see an Intergraph key under the Software folder.
6. Highlight the new INTERGRAPH key and pick EDIT > ADD VALUE from the registry editor
menu bar.

PDS and Windows
7. Enter COMMON for the VALUE NAME.

Note that it is case-sensitive.
8. Pick REG_SZ from the dropdown list for the DATA TYPE and pick OK.
9. Enter C:\win32app\ingr\share in the String Editor form.
The information that appears in the right-hand side of the registry editor when you open the
Intergraph folder should look like this:

1. Start the registry editor and locate the HKEY_LOCAL_MACHINE on Local Machine window.
2. Locate the SOFTWARE folder and double-click on it.
3. Open the INTERGRAPH key and look in the right-hand side.
If so, change the string for the COMMON key to read C:\win32app\ingr\share. Then go to
the C:\Program Files\Common Files\Intergraph directory using Explorer and note which
Intergraph products have files loaded in this location. Remove these products and reload
them.
Creation of DisableUNCCheck
This change should be made on all Windows 7 workstations and Windows 2008 Server nodes,
where the COMMAND PROCESSOR key does not already exist. The time at which you do this
is not critical (i.e.-if you have already loaded products you can still make this change).
1. Start the Registry Editor and locate the HKEY_LOCAL_MACHINE on Local Machine
window.
2. Go to SOFTWARE > MICROSOFT (open Microsoft folder).
3. Pick EDIT > ADD KEY from the registry editor menu bar.
4. Enter COMMAND PROCESSOR for the Key Name. Note that it is a case-sensitive and be
sure to leave a blank space between the two words.
6. If you have done this correctly, you should see your Command Processor folder under the
Microsoft folder.
7. Highlight the new COMMAND PROCESSOR key and from the registry editor menu bar pick
EDIT > ADD VALUE.
8. Enter DisableUNCCheck for the Value Name. Note that this is a single word and it is
case-sensitive.
9. Pick REG_DWORD from the drop-down list for the Data Type and then click OK.
10. Pick the Hex radio button in the DWORD Editor, and enter 1 (numeric one) in the Data
field. The information that appears in the right-hand side of the registry editor when you
open the Command Processor folder should look like this:
294 PDS and Windows 2000
APPENDIX I PDS Project Setup
DisableUNCCheck::REG_DWORD:0x1

PDS and Windows
Winreg Key
All paths defined within the PDS project are defined with a NODENAME and the actual PATH to
the file or directory on the node. There is a registry entry named HKEY_LOCAL_MACHINE >
System > CurrentControlSet > Services > LanManServer > Shares that contains a listing of the
Shares available on the server, and the local path to those shares. The mount code utilized by
PDS takes the NODENAME and PATH from the PDS project, accesses the registry key
HKEY_LOCAL_MACHINE > System > CurrentControlSet > Services > LanManServer > Shares
and attempts to resolve the NODENAME and PATH into a UNC path. Once successful, this
UNC path is passed back to PDS to access the files needed. This explains why in a new
installation of PDS, when the WINREG key of the server has not been modified, only users who
are administrators on the Server can successfully use PDS.
In the past, we have recommended deleting the WINREG key to resolve this problem. But, by
adding the path to the HKEY_LOCAL_MACHINE > System > CurrentControlSet > Services >
LanManServer > Shares key to the AllowedPaths sub-key of the WINREG key, all users will
have access to the information needed to resolve the NODENAME and PATH into a UNC path
for use by PDS.
This modification is needed on all server nodes and should be done prior to project creation.
This modification is also needed on any client nodes that will use remote batch queues to pipe
PDS batch jobs to another machine for processing.
Include Path
1. Open the registry on the server using regedt32.exe. Find the key HKEY_LOCAL_MACHINE
> System > CurrentControlSet > Control > SecurePipeServers > WINREG > AllowedPaths.
2. Select the AllowedPaths registry key.
This is a multi-line value.
3. Double click on the value. This will open the Multi-String Editor.
4. Add the following:
System\CurrentControlSet\Services\LanManServer\Shares
5. Click the OK button. All users should now be able to use PDS without requiring
Administrative rights on the server.
6. Reboot the server.
Delete the Winreg Key

1. Start the registry editor and again locate the HKEY_LOCAL_MACHINE on Local Machine
window.
2. Locate the following folder:
SYSTEM > CurrentControlSet > Control > SecurePipeServers > Winreg
3. Delete the winreg key by selecting it and pressing the Delete key on your keyboard.
4. Reboot the server.
The common errors associated with the WINREG key are: 'Maximum Number of
Shares Exceeded', 'Error 67, Error Mounting Remotename'. 'Net address and directory
could not be mounted verify the specified control files', 'Error in Number of Columns' when
trying to create Equipment Models', 'No Matching Sharename for drive letter:\path', and
empty log files when routing PDS batch queues to a remote machine for processing.

PDS and Windows
Location of RIS Schemas File

When using Windows 2000, you have two options for the schemas file location. The first option
is to specify a LOCAL schemas file and enter a UNC (Universal Naming Convention) path that
specifies the location on the server. The second option is to use TCP\IP as the protocol and
specify a valid login on the server.
Use of UNC Path

You can use a UNC path to locate the schema file.
1. Share the directory where the schema file is located.
2. Open the Locate Schema File form on the client node.
3. Pick Local as the protocol for the schema file location.
4. Enter: \\server\driveletter\dirname\schemas
As an example \\pdssmp1\c:\ris\schemas. FTP Server is not required for this to work.
Some systems have not worked with the colon after the drive letter. In this case, use the
following syntax: \\pdssmp1\c\ris\schemas.
Locating the schema file in this manner uses Windows 2000 Server licenses (as seen in
Control Panel>Licensing).
Use of TCP\IP
1. Install and configure FTP Server on the server.
2. Locate the Schema File from a client node and specify TCP\IP as the protocol.
Environment Variables
Windows 2000 creates default temp and tmp paths of %USERPROFILE%\Local
Settings%\temp for each user. You need to delete or modify the users default paths for
temp\tmp and create path names without spaces.
1. Right-click on My Computer.
2. Choose Properties > Advanced > Environment Variables.
3. Highlight the temp variable and press the delete button (or press the edit button and change
the path to c:\temp).
4. Highlight the tmp variable and press the delete button (or press the edit button and change
the path to c:\temp).
An alternative to setting each users environment variable on every Windows 2000
machine they log into is to create a Roaming User profile for each user and delete or set the
temp and tmp paths once.
Active Directories and Windows 2000 Domain

Active Directory Services and the Windows 2000 Domain should be installed and configured per
Microsoft instructions.

APPENDIX J
PDS Environment Variables

This section contains a list of environment variables set in the config file or the Control Panel
User variables. These variables are for commands that are not accessed or set within the PDS
environment.
In This Appendix
Commands Set in PDS.CMD......................................................... 301
System Environment Variables ..................................................... 305
PDS2D Environment Variables ..................................................... 307
FrameWorks Plus Environment Variables ..................................... 309
Commands Set in PDS.CMD

The PDS.CMD file sets up the working environment within PDS and starts the software. Each
user can have their own PDS.CMD file or all users can share the same PDS.CMD file.
Example of a PDS.CMD File

@rem = '
@echo off
pdsperl %0.cmd %1 %2 %3 %4 %5 %6 %7 %8 %9
goto endofperl
';
$ENV{'GRAPHICS_TOP'} = 'YES';
$ENV{'PROJ_FILE'} = 'proj1\\';
$ENV{'PROJ_ADDR'} = 'docdata\d';
$PD_SHELL = $ARGV[0];
$appname = "$PD_SHELL\\bin\\pdshell";
#
# If more than one argument, then
# first argument is the path to the utility
# second argument is the executable file name
#
if($#ARGV>$[)
{
$appname=$ARGV[0].$ARGV[1];
if($#ARGV>$[+1)
{
shift;
shift;
foreach $argi (@ARGV)
{
$appname .= ' '.$argi;
}
}
}
system "$appname";
__END__
:endofperl
If you want to add environment variables to the PDS.CMD file, add them before the "$PD_Shell
= $ARGV[0];" line.
You MUST include an extra backslash for every backslash that is used in pathing
text in the pds.cmd file. For example, if the path you want is \\pdsserver\z\projfile, then you need
to define the path in the pds.cmd like this: \\\\pdsserver\\z\\projfile.
The following environment variables can be set in the pds.cmd file.

ISO Environment Variables

 $ENV{'ISOPATH'} = 'node:directory path\\';
The exported ISOPATH value is loaded by default into the output path directory slot on the
Add Default Set form. It is also used as the default path, ISO output node:Path, when
extracting an interactive isometric.
 $ENV{'ISOOPTION'} = 'node:directory path\defaults file';
The exported ISOOPTION value is loaded by default into the Options File field on the Add
Default Set form. It is also used as a default for the options file, ISO Options File, when
extracting an interactive isometric.
 $ENV{'ISOSEED'} = 'node: directory path\seed file';
The exported ISOSEED value is loaded by default into the Seed File field on the Add
Default Set form. It is also used as a default for the seed design file, ISO Seed Design File,
when extracting an interactive isometric.
 $ENV{'ISOPLOT'} = 'node:directory path\iparm file';
The exported ISOPLOT value is loaded by default into the Plot File field on the Add Default
Set form. It is also used as a default for the plot parameters file, ISO Seed Plot File, when
plotting an interactive isometric.
 $ENV{'ISOBORDER'} = 'node:directory path\border file';
The exported ISOBORDER value is loaded by default into the Border File field on the Add
Default Set form.
 $ENV{'ISOBATCH'} = 'node:directory path\isobat\\';
The exported ISOBATCH value is loaded by default into the Batch Job Input File field on
the Create Batch Job Input form. The isobat file name is optional. If left blank here it can
be set for each batch job input, ensuring a unique input file name.
 $ENV{'ISOREPORT'} = 'node:directory path\isorpt';
The exported ISOREPORT value is loaded by default into the Output File field on the
Batch Data Reports form. The isorpt file name is optional. If left blank here it can be set for
each batch data report, ensuring a unique file name.
 $ENV{'ISOBATCHQUE'} = 'PDisocreate';
The exported ISOBATCHQUE value is loaded by default into the Process Queue field on
the Schedule Batch Job form.
 $ENV{'ISO_ASCII_LOAD'} = 'node:directory path\isoascii';
The exported ISO_ASCII_LOAD value is loaded by default into the Filename field on the
Bulk Load Lines From ASCII File form.
 $ENV{'PDISOFONT'} = 'XX';
The exported PDISOFONT value defines the font that will be used on the output isometric,
both on the face of the ISO, and on the MTO on the ISO. The defined font must be a
mono-spaced font.
 $ENV{'SYMDGN'} = 'node:directory path\symbol.dgn';
 $ENV{'SYMNDX'} = 'node:directory path\symbol.ndx';
 $ENV{'SYMLIB'} = 'node:directory path\symbol.lib';
The exported values SYMDGN, SYMNDX and SYMLIB are loaded into the Symbol Design
Node:File, Symbol Index Node:File and Symbol Library Node:File fields respectively on
the Isometric Symbol Editor form.
 $ENV{'ISOUSRREFDIM'} = 'node:directory path\filespec.dat';
where,

node
= the hostname of the project file server,
directory path
= the directory path containing the reference data file,
filespec.dat
= the name of the gridline reference data file.
For example,
 $ENV{'ISOUSRREFDIM'} = 'pdsserv1:e:\proj1\project\fw_bldg_a.dat';
After this variable is set, the data in the file filespec.dat will be referenced as a result of
enabling Intergraph option 71 in the isometric options file. Note that this file will be used in
place of the file fw_projname.dat which is the gridline reference data file by default. When
utilizing this variable, the following rules will apply:
If the ISOUSRREFDIM variable is set and points to the proper location of a valid gridline
reference data file, this file will be used for placing gridline references on the isometric
drawing if Intergraph option 71 is turned on.
If the ISOUSRREFDIM variable is set improperly (for example, UNCpath or filespec are
mis-typed) and Intergraph option 71 is turned on, then no references will appear on the face
of the iso. That is, the result will be as if no gridline reference data file exists in the project
directory.
If the ISOUSRREFDIM variable is not set in the pds.cmd file but option 71 is turned on, then
the software will, by default, search for the file fw_projname.dat in the project directory. If it
exists and contains valid data, then the gridline reference dimensions will be extracted from
this file.
PD_Report Environment Variables

 $ENV{‘MDP_IMPLIED_USE_DESIGN_DB’} = 1
Used to report NPD for gaskets and bolts from the Commodity Code labels in the short
description. If MDP_IMPLIED_USE_DESIGN is defined, the software retrieves component
NPD values from the Design database. If the variable is not defined, the software retrieves
the values from the Spec database.
PD_Stress Environment Variables

 $ENV{'STRESSPATH'} = 'node:directory path\\';
The exported STRESSPATH value is loaded by default into the Stress Output:Node field on
the Stress Analysis form.
 $ENV{'STRESSOPTION'} = 'node:users\stress\default file';
The exported STRESSOPTION value is loaded by default into the Stress Options File field
on the Stress Analysis form.
PD_Draw Environment Variables

 $ENV{'VHL_PPOPS'} = 'command arguments';
The VHL_PPOPS export variable combines a number of arguments with the use of one
environment variable, with the arguments separated by a space. These arguments execute
certain pre-processing and post-processing options when creating vector hidden line
graphics. For example: $ENV{'VHL_PPOPS'} = 'arc backp cell join';
Invokes arc restroking, backplane elimination, cell re-creation and joining of partial
elements.

PD_Equip Environment Variables

 $ENV{'PD_EIFORMS '} = '\\\\servername\\sharename\\directory\\';
Alternative method to define the Equipment forms directory location. The exported variable
allows an individual to use a different set of forms, other than those defined in the
Equipment Database Library File Manager. This allows an individual to test things without
modifying real data. If this location is undefined in the data manager, PDS uses the forms in
the local machine's eqp directory; c:\win32app\ingr\PDEQP\forms; if it is defined, then every
user sees the same forms; if it is exported, it overrides the project setting. This directory
path setting needs to be on the local machine.
PD_Shell Environment Variables

 $ENV{'iplot_output_directory'} = 'drive:\directory path';
The iplot_output_directory variable determines the output location for iplot files on the local
machine.
 $ENV{'iplot_dlog_input_monitor'} = 'false';
The iplot_dlog_input_monitor exported variable is used so that PDS will recognize the iplot
variable when used at the command line within PDS. This variable was used as a fix to PDS
5.1 due to problem keying in iplot command at the MicroStation keyin window within
PD_DESIGN. This command was tested with PDS 6.3.X and Iplot 9.0 and the variable is no
longer needed.
 $ENV{'PDS_ARCH_TMP'} =' directory path\\';
This exported variable is used to enhance the Project Archival and Retrieval functions.
When a Scheduled Project Archive is created, you can specify that the archive be FTP'd to
a remote site when complete. The archive will first be created in the TEMP directory of the
local node, FTP'd to the remote node, and then deleted from the local node. The location of
where the scratch archive is created can be changed using the environment variable
PDS_ARCH_TMP (which is useful if the location specified by TEMP cannot accommodate
the archive).
 $ENV{'PD_IFORMS'} = '\\\\servername\\sharename\\directory\\';
Used to define the PD_Shell forms location rather than the pdshell\forms\ directory on the
local machine. Please keep in mind that the folder \\servername\sharename\directory\ must
still have a directory under it named forms as that is what this command is looking for.
 $ENV{'PD_EDITOR'} = 'node:directory path\editor executable';
Used to define the text editor to be used when revising data through the PD_Shell forms.
 $ENV{'PROJ_FILE'} = 'directory path';
Used to define the directory path of the PDS projfile for the current project specifications.
 $ENV{'PROJ_ADDR'} = 'Your Proj File Network Address';
Used to specify the node name of the projfile location.
 $ENV{'PDS_COMMIT_INTERVAL'} = 'xx';
Used to control the commit interval in all database loading activities in the Project Retrieval
Commands. This has the same impact as adjusting the -c option in a risload command line.
The default commit value is 25.
 $ENV{'NO_TRUNCATE'} = 'YES';
Used to specify whether to use long filenames for dimension tables. Setting this variable to
YES allows long filenames. A value of NO limits dimension table filenames to 11 characters
(8 characters in the filename, and a 3-character extension).

The variable also works for files extracted from the Graphic Commodities library, the Piping
Job Specifications library, and the Assembly library. When you are loading to the libraries
with the variable defined:
 The filename convention is not limited to 11 characters. Single files can be loaded with
the length of the name limited by the size of the PDS key-in field.
 The length of individual file names listed in a Load List file are not limited to the size of
the key-in field and can have additional characters.
 $ENV{'PDS_PF_DISCIPLINE'} = 'discipline_indx_no'; or
$ENV{'PDS_PF_DISCIPLINE'} = 'discipline_name';
Used to specify the Pelican Forge discipline number for the project. This variable can be set
to either the discipline number or discipline name from pdtable_111. This variable can also
be set as a system environment variable.
 $ENV{'PDME_LABEL_SEP_CHAR'} = '-';
Used to specify the concatenation character for multi-line PDME label text. The default
character is a dash '-'. There is not restriction on the length of characters that you can use.
 $ENV{'PDS_USER_UMENUPREF'} = 'mymenufile.rsc';
Used to specify the user menu preference resource file.
 $ENV{'PDS_USER_FONTRSC'} = 'myfonts.rsc';
Used to specify the font resource file.
 $ENV{'PDS_USER_CONFIG'} = 'myconfig.cfg';
Used to specify the config resource file.
Project Archival Manager Environment Variables

 $ENV{'SUPRESS_UPDATE_LABELS'} = 'YES';
Once this variable is set, the Import Project Retrieval and Scheduled Project Import
commands do not update labels while importing the drawings. The label retains the existing
definition.
System Environment Variables

The following variables are set in the environment variables for the system, using Control Panel
> System > Environment Variables.
 RIS_PARAMETERS=directory path
Used in situations where there are different schema files in use.
 PDS_MAIL_REICPIENT
PDS_MAIL_LOGIN
PDS_MAIL_PASSWORD
Used to mail the log files from certain batch jobs processed to a specified user when the
batch jobs are running on the server. Please see the stipulations and settings in the PDS
Project Setup Guide.
 PDS_REPORT_LOG=1
If PDS_REPORT_LOG environment variable is set to any value other than zero, the
REPORT_ERROR_LOG will not be appended to the end of the report. It will be placed in an
error log file within the temp subdirectory for the given report generated. This environment
variable will only remove the error statements from the end of the report.
 PDS_FULL_ASCII=1

Used in conjunction with Frameworks Plus for foreign language compatibility. The
environment variable, PDS_FULL_ASCII, is intended to permit the use of full 8-bit ASCII
characters as required for many foreign language locales (using an OS meant for the locale
or using the English OS set for the locale). The problem was caused by character data
verification routines in a few places in PDS which do not permit the most significant bit
(MSB) to be set. It should be clarified that PDS is not fully certified in this mode, but is to be
verified by those requesting the fix.
 DBA_NO_MSCATALOG=Y
DBA_MSLINK=model_index_no
Many of the PDS databases do not have a mscatalog table, and many of the PDS tables do
not have an mslink column. By default, DBAccess looks for this table in the database and
this column in the selected table and expects the mslink column to have unique integer
values. You can use the environment variables DBA_NO_MSCATALOG and DBA_MSLINK
to tell DBAccess to build its list of database tables from the database rather than from the
mscatalog table and to use a column other than mslink as the key column. For example, in
the PD schema, pdtable_113 has a column named model_index_no that has unique integer
values. By setting DBA_NO_MSCATALOG=Y and DBA_MSLINK=model_index_no, you can
use the DBAccess Edit Database function on this table and scroll through the available
records.
 PDS_HVAC_SCHEMA_NAME=prj_[myhvacprojname]
To create labels for PE_HVAC models, the name of the PE_HVAC project database must
be prj_[pdsprojectname], where [pdsprojectname] is the exact name of the PDS project. If
you want to use a different PE_HVAC project schema name, you can set the
PDS_HVAC_SCHEMA_NAME to prj_[myphvprojname], where [myhvprojname] is the name
you want to use for the PE_HVAC project.
In Material Data Publisher (MDP), you can also use this variable to define the PEHVAC.prj
schema when the HVAC project schema name is different from the PDS project schema
name. As in the previous example, set the PDS_HVAC_SCHEMA_NAME to
prj_[hvacprojectname], where [hvacprojectname] is the name of the PEHVAC project
schema you want to use.
 AREA_VOLUME_GRAPHICS_COLOR
AREA_VOLUME_GRAPHICS_WEIGHT
AREA_VOLUME_GRAPHICS_STYLE
AREA_VOLUME_GRAPHICS_LEVEL
These variables specify the symbology used to display area volume graphics in the Piping,
Equipment, Raceway, PE_HVAC, and FrameWorks Plus environments.
 PDS_PF_DISCIPLINE=discipline_indx_no or
PDS_PF_DISCIPLINE=discipline_name
Used to specify the Pelican Forge discipline number for the project. This variable can be set
to either the discipline number or discipline name from pdtable_111. This variable can also
be set in the pds.cmd file. Setting this environment variable causes PDS to treat Support
Modeler more like a standard PDS discipline, including the ability to retrieve the .drv and
.env files for an archive.
 PD_NO_COMPRESS=1
Stops the validation of the end-of-file marker in Microstation upon exit and the compression.
Set this environment variable in you are having performance problems on a WAN when
exiting a PDS model.
 MDP_IMPLIED_USE_DESIGN_DB=1
Used to report NPD for gaskets and bolts from the Commodity Code labels in the short
description. If MDP_IMPLIED_USE_DESIGN is defined, the software retrieves component

NPD values from the Design database. If the variable is not defined, the software retrieves
the values from the Spec database. This variable also works when set in the Commands Set
in PDS.CMD (on page 301).
PDS2D Environment Variables

Control Panel
The following environment variables that affect the PDS2D modules are set using Control
Panel > System > Environment Variables.
 MS_PROCESSORS=1
Used when running PDS2D on a machine with more than one CPU.
Source: PDS Project Setup Guide, June 1998, page 130
 NQS_JOB=1
Used by PDS2D with scheduling NT Batch. If set, Batch jobs are run using NT Batch. If not
set, Batch jobs are run using the NT Schedule Service.
 P2D_DONT_SHOW_STARTUP=any value
If this variable is not set, the form will display automatically when you enter IDM. If set to 0
or 1 the form shows up.
Source: IDM User's Guide, January 1998, page 29
 P2D_GENDOC_LOG_FILE=Directory path
Used to specify the directory for the Generate Document log file. If not set this file is
generated as gendoc2d.log and resides in the temp directory.
Source: PDS2D RDB Administrator's Reference Guide, January 1998, page 122
 P2D_PRTDOC_LOG_FILE=Directory path
Used to specify the directory for the Print document log file when using the PDS 2D print
document command. If not set this file is generated as p2dprtdoc.log and resides in the
temp directory.
 P2D_PLOT_LOG_FILE=Directory path
Used to specify the directory for the Plot log file when using the PDS Plotting commands.
The log file is named p2d_plot.log and resides in the user's temp directory.
 P2D_IMPORT_LOG_FILE=Directory path
Used to specify the directory for the import/export log file. By default the log file is named
import.log and resides in the user's temp directory.
Source: PDS 2D 6.3.1 Document Addendum, June 1998, page 22
 P2D_IMPORT_LOG_MODE=Minimum
Used to eliminate the non-error messages in the import log.
Source: PDS 2D 6.3.1 Document Addendum, June 1998, page 22
 P2D_IMPORT_UPDATE_MODE=MINIMUM
The log file created by import has been enhanced and a new import option has been added
to update the database after each line in the import file. This option makes it easier to
resolve problems if an error occurs during import. This also eliminates the need to put
#UPDATE statements in import files. This option is triggered by setting the environment
variable to the value "MINIMUM".
Source: PDS2D 06.00.02.07 Readme File

 P2D_PLOT_SHOW_CMD=any value
Used so that when working with commands that submit plots (either of the plot commands,
print document or generate document), the command lines sent to the system to create the
plot will be output into the log file along with the rest of the log messages.
 PDS_MENU_AUTOACTCUSTOM=any value
Sets the user's custom menu to be automatically activated when entering graphics.
 P2D_EDTGRA_INIT=Directory path to a Perl script
P2D_EDTGRA_EXIT=Directory path to a Perl script
Used to specify the directory path of the Perl script used when entering or exiting a drawing.
(P2D_EDTGRA_INIT is entering). For more information on the EDTGRA environment
variables see page 304 of the PDS2D RDB Reference Guide Jan, 1998.
 P2D_USER_EXTENSION=XXX
Related to the IDM standalone menu. This variable lets you define the extension of the
winmenu file in the project data you wish to use. If this variable is set, the menu used is
located at the project's pds2d\rdb\data directory and is expected to be named winmenu.XXX
where XXX is the value of this environment variable.
 P2D_USER_WINMENU=location of winmenu file to use
If the IDM Standalone user wants to use a winmenu which is not located in the project, set
this variable to the UNC file spec of the file to use. The file must follow the syntax rules of
the winmenu file. If not set the menu used if the default winmenu file or the winmenu file
specified by P2D_USER_EXTENSION.
 PDS_MENU = directory path for the saved customer MDL menu file
If not set, the NT software sets the menu to the pds2d\cfg\directory.
 PDS_MENU_GRAPAL = directory location of graphic palettes
Points to directory of graphic palettes. If not set the system will default to the same location
as the PDS_MENU variable.
cfgdat.bat File
The following environment variables that affect the PDS2D modules are set in the cfgdat.bat file,
which is delivered in the win32app\ingr\pds2d\cfg\ directory.
 PDS_USER_NO=integer value
Used by PDS2D for access control in conjunction with the acc_control file to determine
which users have what types of access on which tables. If not defined the user has full
access.
Source: PDS2D RDB Reference Guide, January 1998, page 269
 P2D_INIT_QUEUES=any value
Initializes queue list once during setup instead of when the first command is called that
requires the list.
GRAPHICS_TOP=YES
DATABASE_TOP=YES
Used to tell NT to always place the forms on top of window. GRAPHICS_TOP is used in
graphics forms and DATABASE_TOP is used when working in database forms.
 XFORMSCALE=INTEGER VALUE
YFORMSCALE=INTEGER VALUE
XFORMSCALE is the scaling you wish to apply to forms in the x-direction, and
YFORMSCALE is the scaling for the y-direction. These environment variables, if defined,
always override default scaling. The value is a percentage of the scaling. For example a

10% increase in size would be set as XFORMSCALE=1.1. The syntax states there are no
spaces on either side of the equal sign. The default form size is 1280x1024 but can be
different based on your hardware configuration.
 P2D_USR_FRM_FONT=FONT NAME
Used to set a font other than Arial for the database windows.
 PDS2D_VIEW_OPT=directory path of PostScript viewer executable
Used to choose a postscript viewer to view externally.
 FTASKMENU=YES OR FTASKMENU=NO
Set to Yes to use the MicroMenu forms or set to No to use the MDL palettes. No is the
default.
 FTASKMENU_X=pixel value where the menu palette will appear
If using the hybrid menu, the x coordinate of the upper left of the form will be displayed. If
value is greater than the resolution, the form appears at the bottom of the screen. If the
value is negative, the form appears at the top of the screen.
 FTASKMENU_Y=pixel value where the menu palette will appear
If using the hybrid menu, the y coordinate of the upper left of the form will be displayed. If
value is greater than the resolution, the form appears at the bottom of the screen. If the
value is negative, the form appears at the top of the screen.
 P2D_DBWIN_X=X coordinate value
Defines the x coordinate at which the database windows begin.
 P2D_DBWIN_Y=Y coordinate value
Defines the y coordinate at which the database windows begin.
 USE_3_BY_4=any value
Used to set the software to use the 3x4 window layout instead of the 2x3 window layout.
 P2D_PLOT_QPR_OPTS="options"
Sets plotting options to be carried out at plot submission. For a detailed listing of the plotting
options see the 2D RDB Administrators Guide page 204 and the IPLOT User's Guide.
 FORM_LIST_LEN=integer
Sets the forms to be cached. By default beginning with PDS 06.03.01.00 the forms will not
be cached. If user wishes forms to be cached the value is set to be an integer.
FrameWorks Plus Environment Variables

There are several environment variables in the ..\fwplus\data\config.dat file that you can set to
customize FrameWorks Plus.
When you create a project (or open a model in a project created prior to version 3.2),
FrameWorks Plus copies the config.dat file in the ..\fwplus\data folder to the project's \data
folder. The project config.dat file is the one FrameWorks Plus reads when opening a model in
that project. FrameWorks Plus does not read the config.dat file in the ..\fwplus\data directory.
Because the config.dat file is kept on a project basis, you can edit the individual project
config.dat files to have different setting for different projects. This is especially useful if you
access imperial and metric projects from the same computer.

You can set environment variables in Start > Settings > Control Panel > System >
Advanced > Environment Variables; however, we do not recommend it. FrameWorks Plus
reads the config.dat file last when starting, and overwrites any duplicate environment variables
that were defined in your control panel. Having environment variables defined in both the control
panel and the config.dat file can cause confusion when trying to change variable settings.
You can use UNC (Universal Naming Convention) paths for directory locations. For example,
instead of mounting a server that contains your section tables, you can define the directory
using the syntax: FW_ESL_DIR= \\servername\sharename\esl\
 FWBIN—Sets the location of the FrameWorks Plus bin directory.
 FW_AUTO_COMPRESS—Specifies if the model database should be compressed
automatically when you exit the model. Set to 0 (zero) to not compress the model. Set to 1 to
compress the model.
Compressing a very large model can cause a pause during model exiting while the
model database is being compressed.
 FW_BDR_DIR—Sets the location of drawing border files.
 FW_DATA—Sets the location of the FrameWorks Plus data directory. This is useful when
you want to use different grade.dat and attributes.dat files for different projects.
 FW_ESL_DIR—Sets the location of standard section libraries (aisc, cisc, and so forth).
 FW_USER_ESL—Sets the location of user section libraries. You must put corresponding
cell libraries for arbitrary sections in this same location. We recommend that you define this
environment variable after creating a new project. This variable requires a UNC path name
so that the user section table works correctly when you run the Propagation command from
the PD-Shell Frameworks Plus dialog box.
 FW_NMDGRPS—Defines the location of the .ngp file (the named groups file) to use. If not
defined here, the project .ngp file is used by default.
 FW_PRODUCT—Sets the location of the main FrameWorks Plus directory. This variable
must be set to start FrameWorks Plus using the mdl load fwp MicroStation key-in and to
create models using the command-line key-in command cremod.
 FW_PREFERENCE—Sets the full directory path and file name for the default preference
file. Use this environment variable to use a preference file other than the default fw.rsc or
fwm.rsc file. You can also set the default preference editor by using the File> Central
Preference Editor command.
 FW_PROJDIR—Sets the location of the directory that contains the project.
 FW_RSC_DIR—Specifies the directory path to FrameWorks Plus resource, or preference,
files.
 FW_SEEDDIR—Sets the location of seed files used to create new models inside PD_Shell.
 FW_SOLID_STROKE—Specifies the stroking tolerance factors for the maximum distance
between a solid's actual curve and the approximating vectors. The greater the number, the
less processing time that is required to display the solid or calculated the solid's
volume/surface. However, the curve representation, and any volume calculations, will not be
as precise. For example, a setting of 0.1 will cause faster processing, but the results will be
less precise than a setting of 0.001.
We recommend that you use a higher stroking tolerance setting until you are ready to
produce your final deliverables. Then you need to use a lower stroking tolerance setting for
these operations.
 FW_SDNF_NUMOFSOLIDS_PER_INSTANCE—Specifies that the steel detailing neutral
file (SDNF) be imported in multiple stages. Defining this variable is necessary only if the
SDNF contains a large number of holes and solids.

 FW_VOLUME_TOL—Specifies the tolerance for calculating the volume of solid elements

(slabs, wall, and generic solids). The lower the tolerance, the longer the volume calculation
will take, but it will be more accurate. Set this tolerance with care. For example, volume
calculations on a slab with a circular hole can take several hours if the tolerance is set to
0.0001. However, with the tolerance set to 0.01, the calculation would take 5 seconds.
 FWSUPFONTNUM—Specifies the font for the FrameWorks Plus member support labels,
the pie-shaped labels used to identify supports applied to a member. Do not edit this
environment variable unless you plan to create your own support labels. The default font is
34.
 FWRELFONTNUM—Specifies the font for the FrameWorks Plus member release labels, the
box-shaped labels used to identify releases applied to a member. Do not edit this
environment variable unless you plan to create your own release labels. The default font is
35.
 PML_CEL—Sets the location of the cell file that contains PML tutorials.
 FW_STAAD_VER—Specifies the version of STAAD that you are using. Must be set to
version 14.2 or later.
 Sg—Defines the gravity of seawater. This value is multiplied by the water density to
compute the density of seawater and is used by FrameWorks Plus in MDP buoyancy
calculations.
 WaterDensity_e—Defines the density of water in imperial units.
 WaterDensity_m—Defines the density of water in metric units.
 HullGap_e—Specifies the default value that appears in Create Rule Based Joint for Set to
to define the required gap between the target and secondary member measured along the
supporting member. Used in imperial models.
 HullGap_m—Specifies the default value that appears in Create Rule Based Joint for Set to
to define the required gap between the target and secondary member measured along the
supporting member. Used in metric models.
 CLGapFactor_e—Specifies the factor to use to calculate the maximum centerline gap
between the target member and the secondary member for a rule-based joint. The factor
specified here is multiplied by the diameter of the supporting member. The result is
compared with the actual centerline gap. If the gap is greater than the result, eccentricity is
introduced into the joint and a message appears. Used in imperial models.
 CLGapFactor_m—Specifies the factor to use to calculate the maximum centerline gap
between the target member and the secondary member for a rule-based joint. The factor
specified here is multiplied by the diameter of the supporting member. The result is
compared with the actual centerline gap. If the gap is greater than the result, eccentricity is
introduced into the joint and a message appears. Used in metric models.
 RBJTolerance_e—Specifies the percentage tolerance that you will accept between the
actual gap and the required gap. FrameWorks Plus computes the tolerance using the
following equation: [(Actual gap - Required gap) / Required gap] x 100% = tolerance
percentage. The calculated tolerance is compared with the tolerance specified here. Used in
imperial models.
 RBJTolerance_m—Specifies the percentage tolerance that you will accept between the
actual gap and the required gap. FrameWorks Plus computes the tolerance using the
following equation: [(Actual gap - Required gap) / Required gap] x 100% = tolerance
percentage. The calculated tolerance is compared with the tolerance specified here. Used in
metric models.
 LminTolerance_e—Not used in FrameWorks Plus version 7.2 or earlier.
 LminTolerance_m—Not used in FrameWorks Plus version 7.2 or earlier.

 DiameterToRoll_e—Defines the rolling process. Pipe sections less than or equal to this
dimension are hot rolled. Diameters greater than this value are rolled plate. This flag is
indicated in the MDP table 533, column 11. Used in imperial models.
 DiameterToRoll_m—Defines the rolling process. Pipe sections less than or equal to this
dimension are hot rolled. Diameters greater than this value are rolled plate. This flag is
indicated in the MDP table 533, column 11. Used in metric models.
 FW_MDP_CONTONERR—Continues with the next model if the MDP process encounters
any MDL aborts in the current model. To use the (USE) function, uncomment the flag
FW_MDP_CONTONERR = 1 in config.dat in the ..\fwplus\data folder.
 pdmdpSrv.exe (c:\win32app\ingr\pdshell\share\pdmdpSrv.exe) runs for every model

during the MDP process; hence, its pop-up command prompt displays for every model.
 If ustation.exe crashes with a Dr.Watson error, this function is not supported. It only runs
if there are aborts in the fwpmdp application (MDL aborts).
The fw.cfg and ist.cfg Files

When you install FrameWorks Plus, the fw.cfg and ist.cfg files are delivered to the MicroStation
folder $Microstation\config\appl and to the FrameWorks Plus folder (c:\win32app\ingr\fwplus by
default). When FrameWorks Plus starts, either standalone or through PD_Shell, the ist.cfg and
fw.cfg files in the MicroStation folder are used. If FrameWorks Plus cannot find the two files in
that folder, then the files in the FrameWorks Plus folder are used.

Index
Create an Auxiliary Coordinate System
2 within a model • 209
Create/Revise Model Propagation Schedule
2D Disciplines • 125 • 217
2D Schemas • 40 Creating 3D Areas and Models • 109
Creating a Database Drawing • 127
3 Creating a FrameWorks Project • 70
3D Areas • 114 Creating a Graphics-only Drawing • 126
3D Design Data and the Database • 125 Creating a Model by ASCII File • 205
3D Disciplines • 109 Creating a Model in PD_Shell • 203
3D Models • 119 Creating a PDS 2D/3D Project Manually •
3D Schemas • 39 61
Creating a Structural Discipline Design Area
• 201
A Creating and Maintaining Distributed
Access Control • 144 Projects • 158
Active Directories and Windows 2000 Creating Backups and Maintaining a
Domain • 300 Backup Schedule • 148
Adding Disciplines to an Existing Project • Creating Batch Queues • 52
93 Creating Logins and Usernames for
Adding Tables to the EE Raceway Schemas • 280
Reference Schema • 73 Creating or Inserting a FrameWorks Plus
Application-specific Considerations • 133 Project • 200
Attaching Reference Data to the Project • Creating PE-HVAC Projects • 81
95 Creating Project Directories and Required
Automatically load an Auxiliary Coordinate Shares • 54
System within a model • 211 Creating Project Directories Manually • 62
Creating Required Databases/Database
B Users • 59
Batch Cutout (PD_Shell) • 220 Creating the 2D Project • 89
Creating the 3D Project (Equipment and
Piping) • 64
C Creating the EE Raceway Project • 72
Changing Coordinate Systems and Working Creating the User Database in MSSQL
Units • 79 2005 • 284
CIM Steel Export (PD_Shell) • 224 Creating the User Database in MSSQL
Client Nodes • 27 2008 • 278
Commands Set in PDS.CMD • 301
Composition • 216 D
Concepts and Terminology • 13
Configuring ISMP RAID for Performance Database Setup - Microsoft SQL • 269
and Availability • 167 Database Setup - Oracle • 229
Configuring the PDS Batch Mail Utility • 142 Database Software • 32
Copying a Set of Users to Another Project • Database Structure • 38
148 Database Vendor Backup of Database •
Core Graphics Software • 31 157
Create • 215 Default C Drive Permissions • 44
Create a prompt for automatic loading • 211 Delete • 216
Delete Model Propagation Schedule • 218
Drawing Environment • 215

Index
E L
Environment Variables • 300 Loading and Configuring Software • 27
Environment Variables (Windows 7 / Server Loading Default Data into the Piping
2008) • 297 Reference Database • 103
Equipment Reference Data • 101 Location of RIS Schemas File • 300
Establishing Account Mapping • 53 Location of RIS Schemas File (Windows 7 /
Establishing Domain Users and Groups • 41 Server 2008) • 296
Location of schemas File • 49
F Location of the proj File • 41
Log Files Produced by PDS Batch Jobs •
File Systems • 27 179
Files Reside on a Windows Server • 56
Format of the queue_descript File • 288
FrameWorks Environment • 214 M
FrameWorks Plus and Material Data Model Creation for Other 3D Disciplines •
Publisher • 228 125
FrameWorks Plus and PD_Clash • 227 Modeling • 215
FrameWorks Plus and SmartPlant Review • Modifying Batch Queues for Redirected
225 Processing • 135
FrameWorks Plus Categories • 213 MSSQL Server 2005 • 281
FrameWorks Plus Environment Variables • MSSQL Server 2008 • 269
309 My Computer versus Network Printer
FrameWorks Plus Extended Labels Dialog Server • 131
Box • 226
Full versus Incremental Backups • 158 N
Notes: • 187
G NTBACKUP or CPIO Backup of Database
General Processing Rules for Files • 156
Printers/Plotters • 289 NTBACKUP or CPIO Backup of Project
Generate ASCII File • 219 Data • 155
H O
Hardware Versus Software RAID Operating Systems and Related
Implementations • 166 Components • 27
How RIS Communicates with the Database Oracle 10.2.0.5 Client Installation on
• 37 Windows 7 • 267
Oracle 10.2g • 249
I Oracle 10g • 264
Oracle 11g • 229
I/O Subsystem Components • 159
Installing and Configuring SmartPlant
License Manager • 59 P
Installing MSSQL 2005 • 281 PD_Clash • 184
Installing MSSQL 2008 • 269 PD_Data • 185
Interactive Jobs Which Print/Plot • 291 PD_Design • 183
Intergraph SmartPlant License Manager • PD_Draw • 183
199 PD_Model • 183
Intergraph Supported RAID Levels • 161 PD_Project • 185
Introduction • 11 PD_Report • 184
ISMP 5* or 6* RAID Subsystem Description PD_Review • 184
• 166 PDS and FrameWorks Plus • 199
PDS and Windows • 293

Index
PDS and Windows 2000 • 297 Server Nodes • 28

PDS and Windows 7 / Server 2008 • 293 Server Requirements • 21
PDS Batch Jobs and the queue_descript Setting the RIS_PARAMETERS
File • 291 Environment Variable • 141
PDS Environment Variables • 301 Setup Information • 199
PDS Print/Plot Jobs and the queue_descript Sharing the proj File Location Through LAN
File • 290 Manager • 42
PDS Products, Client Nodes • 32 Shifting the FrameWorks Plus Global Origin
PDS Products, Server Nodes • 36 to Match PDS Design Volume • 208
PDS Project Archive to Back Up Database • Software Required for Batch Processing •
156 30
PDS Project Archive to Back Up Project Software Required for File Sharing • 30
Data • 149 Software Required for Plotting • 31
PDS Project Creation Workbook • 189 System Administrator Responsibilities • 131
PDS System Requirements • 15 System Configuration • 19
PDS2D Environment Variables • 307 System Environment Variables • 305
Piping Reference Data • 95
Plotting in the PDS Environment • 131 T
Preface PDS • 9
Preparing for Project Creation • 41 The PDS queue_descript File • 287
Production Database Installation (Oracle The queue_descript File • 133
10g) • 265
Project Organization • 109 U
Propagation • 216 Universal Naming Convention • 45
Update/Regenerate Frozen View • 219
Q Use of My Computer • 132
Quick Installation Guide for Windows 7 • 23 Use of Network Printer Server • 133
Using Coordinate Systems in FrameWorks
Plus • 208
R
RAID 0 • 161 V
RAID 1 • 162
RAID 5 • 163 Verify Model (PD_Shell) • 224
RAID 6 • 165
RAID 7 • 165 W
RAID Configuration • 159 What's New in Project Setup Technical
Registry Entries • 297 Reference • 10
Registry Entries (Windows 7 / Server 2008) Which Backup Methods Should I Use? •
• 293 158
Relational Interface System (RIS) • 37 Why RIS? • 37
Removal of Older RIS Client (Oracle 10g) • Workstation (Client) Hardware and
264 Software Requirements • 16
Review Schedule (FWP) • 218
RIS Backup of Database • 157
S
Scheduled Model Propagation • 217
Script to Create Project Directories on
Windows • 171
Scripts to Create Project Directories • 171
Server Hardware and Software
Requirements • 15

PDS Project Setup Technical Reference

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

PDS Project Setup Technical Reference

Uploaded by

Copyright:

Available Formats

Plant Design System (PDS)

Project Setup Technical Reference

Version 2011 (V12)

Concepts and Terminology ...................................................................................................................... 13

PDS System Requirements ...................................................................................................................... 15

System Configuration ............................................................................................................................... 19

Quick Installation Guide for Windows 7.................................................................................................. 23

Loading and Configuring Software ......................................................................................................... 27

Plant Design System (PDS) Project Setup Technical Reference 3

Relational Interface System (RIS) ............................................................................................................ 37

Preparing for Project Creation ................................................................................................................. 41

Installing and Configuring SmartPlant License Manager ..................................................................... 59

Creating a PDS 2D/3D Project Manually.................................................................................................. 61

Attaching Reference Data to the Project ................................................................................................. 95

Creating 3D Areas and Models .............................................................................................................. 109

4 Plant Design System (PDS) Project Setup Technical Reference

System Administrator Responsibilities ................................................................................................ 131

RAID Configuration ................................................................................................................................. 159

Scripts to Create Project Directories ..................................................................................................... 171

Log Files Produced by PDS Batch Jobs ............................................................................................... 179

Plant Design System (PDS) Project Setup Technical Reference 5

PDS Project Creation Workbook ............................................................................................................ 189

PDS and FrameWorks Plus .................................................................................................................... 199

Database Setup - Oracle ......................................................................................................................... 229

Database Setup - Microsoft SQL ............................................................................................................ 269

The PDS queue_descript File ................................................................................................................. 287

6 Plant Design System (PDS) Project Setup Technical Reference

PDS and Windows ................................................................................................................................... 293

PDS Environment Variables ................................................................................................................... 301

Index ......................................................................................................................................................... 313

Plant Design System (PDS) Project Setup Technical Reference 7

8 Plant Design System (PDS) Project Setup Technical Reference

List of PDS Documentation

Plant Design System (PDS) Project Setup Technical Reference 9

What's New in Project Setup Technical Reference

10 Plant Design System (PDS) Project Setup Technical Reference

Plant Design System (PDS) Project Setup Technical Reference 11

12 Plant Design System (PDS) Project Setup Technical Reference

Concepts and Terminology

This document discusses each step in the above diagram.

Plant Design System (PDS) Project Setup Technical Reference 13

14 Plant Design System (PDS) Project Setup Technical Reference

PDS System Requirements

Server Hardware and Software Requirements

Supported Operating Systems - Servers

Supported Database Servers

Plant Design System (PDS) Project Setup Technical Reference 15

 RIS Shared Component (Client) 06.01.00.02

Workstation (Client) Hardware and Software

Supported Operating Systems - Clients

Supported Database Clients

16 Plant Design System (PDS) Project Setup Technical Reference

Plant Design System (PDS) Project Setup Technical Reference 17

18 Plant Design System (PDS) Project Setup Technical Reference

Plant Design System (PDS) Project Setup Technical Reference 19

PDS License Server

20 Plant Design System (PDS) Project Setup Technical Reference

Plant Design System (PDS) Project Setup Technical Reference 21

SmartPlant License Manager Server

22 Plant Design System (PDS) Project Setup Technical Reference

Quick Installation Guide for Windows 7

Enabling Remote Registry service

Plant Design System (PDS) Project Setup Technical Reference 23

24 Plant Design System (PDS) Project Setup Technical Reference