PDMS and Associated Products Installation Guide

PDMS & Associated Products
Installation Guide
Disclaimer
1.1 AVEVA does not warrant that the use of the AVEVA software will be uninterrupted, error-free or free from
viruses.
1.2 AVEVA shall not be liable for: loss of profits; loss of business; depletion of goodwill and/or similar losses; loss of
anticipated savings; loss of goods; loss of contract; loss of use; loss or corruption of data or information; any
special, indirect, consequential or pure economic loss, costs, damages, charges or expenses which may be
suffered by the user, including any loss suffered by the user resulting from the inaccuracy or invalidity of any data
created by the AVEVA software, irrespective of whether such losses are suffered directly or indirectly, or arise in
contract, tort (including negligence) or otherwise.
1.3 AVEVA's total liability in contract, tort (including negligence), or otherwise, arising in connection with the
performance of the AVEVA software shall be limited to 100% of the licence fees paid in the year in which the user's
claim is brought.
1.4 Clauses 1.1 to 1.3 shall apply to the fullest extent permissible at law.
1.5 In the event of any conflict between the above clauses and the analogous clauses in the software licence under
which the AVEVA software was purchased, the clauses in the software licence shall take precedence.
Copyright
Copyright and all other intellectual property rights in this manual and the associated software, and every part of it
(including source code, object code, any data contained in it, the manual and any other documentation supplied
with it) belongs to, or is validly licensed by, AVEVA Solutions Limited or its subsidiaries.
All rights are reserved to AVEVA Solutions Limited and its subsidiaries. The information contained in this document
is commercially sensitive, and shall not be copied, reproduced, stored in a retrieval system, or transmitted without
the prior written permission of AVEVA Solutions Limited. Where such permission is granted, it expressly requires
that this copyright notice, and the above disclaimer, is prominently displayed at the beginning of every copy that is
made.
The manual and associated documentation may not be adapted, reproduced, or copied, in any material or
electronic form, without the prior written permission of AVEVA Solutions Limited. The user may not reverse
engineer, decompile, copy, or adapt the software. Neither the whole, nor part of the software described in this
publication may be incorporated into any third-party software, product, machine, or system without the prior written
permission of AVEVA Solutions Limited, save as permitted by law. Any such unauthorised action is strictly
prohibited, and may give rise to civil liabilities and criminal prosecution.
The AVEVA software described in this guide is to be installed and operated strictly in accordance with the terms
and conditions of the respective software licences, and in accordance with the relevant User Documentation.
Unauthorised or unlicensed use of the software is strictly prohibited.
Copyright 1974 to current year. AVEVA Solutions Limited and its subsidiaries. All rights reserved. AVEVA shall not
be liable for any breach or infringement of a third party's intellectual property rights where such breach results from
a user's modification of the AVEVA software or associated documentation.
AVEVA Solutions Limited, High Cross, Madingley Road, Cambridge, CB3 0HB, United Kingdom.
Trademark
AVEVA and Tribon are registered trademarks of AVEVA Solutions Limited or its subsidiaries. Unauthorised use of
the AVEVA or Tribon trademarks is strictly forbidden.
AVEVA product/software names are trademarks or registered trademarks of AVEVA Solutions Limited or its
subsidiaries, registered in the UK, Europe and other countries (worldwide).
The copyright, trademark rights, or other intellectual property rights in any other product or software, its name or
logo belongs to its respective owner.
AVEVA Solutions Limited
Revision Sheet
Date Version Comments / Remarks
September 2011 12.1.1 Issued
J anuary 2012 Copyright added to all pages.
Screens updated from 12.1.1 to 12.1.SP2
PDMS & Associated Products Installation Guide
Installation Guide
Contents Page
12 Series i
Copyright 1974 to current year.
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
PDMS & Associated Products
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
Assumptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
Guide Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
Associated Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:2
Hardware and Software Requirements . . . . . . . . . . . . . . . . . . . . . . . 2:1
AVEVA PDMS 12.1 Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1
Flexman License File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1
.NET Framework Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1
Enable Microsoft Excel Interop Assembly. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1
Font Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:4
AVEVA PDMS and Associated Products Installation . . . . . . . . . . . 3:1
Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:12
Uninstall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:13
Modifying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:13
Repairing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:14
Healing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:15
Modified New and Removed Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:15
User Modified Appware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:15
Models, Sample Data and Example Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:15
Changing Default File Replacement Behaviour . . . . . . . . . . . . . . . . . . . . . . . . 3:16
12 Series ii
Post Deployed .bat files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:16
Pre-Deployed .bat files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:16
.bat file Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:17
Network (Admin) Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:17
Create an Administrative Installation Point. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:17
Issues with Administrative Installation Points . . . . . . . . . . . . . . . . . . . . . . . . . 3:19
.NET Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:19
Signing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:20
Using Files within the Source Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:20
Network Throughput. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:21
Advantages of a Network Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:21
Run PDMS and Associated Products from Network Locations. . . . . . . . . . . . 3:21
Administrative Installation Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:22
Patch Administrative Installations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:22
Copy a Local Deployment to a File Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:22
Feature Id Reference List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:23
Feature Tree Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:23
SelectionTree Selection & De-selection Rules . . . . . . . . . . . . . . . . . . . . . . . . . 3:24
Selecting Features from the Command Line. . . . . . . . . . . . . . . . . . . . . . . . . . . 3:24
Command Line Definable Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:25
Sample Command Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:25
Set Up the Windows Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:1
Windows Control Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:1
Graphics Card Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:1
Set the License File Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:2
PDMS Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:2
Run PDMS from a Command Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:4
Customise PDMS Start-Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:4
Create User Batch File to Run PDMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:5
Run PDMS in Batch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:5
Plot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:6
Language Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:1
Setting PDMS Default Text Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:2
Prepare PDMS For Legacy Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:3
12 Series
iii
Run PDMS Under Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:1
Spaces in Windows Pathnames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:1
Link to Microsoft Excel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:1
Windows Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:1
PDMS Projects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:1
Sample Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:1
Copy Project SAM to User Area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:1
Users and Teams in the Sample Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:1
MDBs in the Sample Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:2
Sample Project and User Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:3
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:1
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:1
License Manager Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:1
Enter PDMS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:2
Problems with Graphics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:3
Structure of PDMS on .NET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:1
PDMSEXE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:1
GUI Module Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:1
.NET Loading Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:2
Native DLLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:2
Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:2
Troubleshooting the .NET Installation . . . . . . . . . . . . . . . . . . . . . . 10:1
Version Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:1
Interface or a Dependency Missing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:1
Interface Incompatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:2
No Add-ins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:2
Window Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:2
Serialisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:2
Install AutoDRAFT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:1
Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:1
AutoDRAFT Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:1
12 Series iv
Configure AutoDRAFT with AutoCAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:1
Install and Configure AutoCAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:2
AutoCAD R2006. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:2
AutoCAD R2007. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:2
AutoCAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:3
Application Macros for use with DRAFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:3
Configure Area Based ADP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:1
MDS Installed Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:1
Manual Configuration of the Product and Product Environment Variables . . 13:1
Set Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:1
Modification of Evars.bat for MDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:2
Environment Variables for Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:2
For Projects Used with MDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:2
Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:3
Projects Released with this Product. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:3
Introduction
12 Series 1:1
1 Introduction
The PDMS & Associated Products Installation Guide explains how to install and set up
PDMS & Associated Products on a workstation running Microsoft Windows. For completely
up-to-date information, refer to the AVEVA Website at http://www.aveva.com/products/
support/support.html and the Customer Support Hardware pages. The Web pages also give
hints on ways of setting up and running PDMS on different computers in order to achieve
the most efficient performance.
1.1 Assumptions
The PDMS & Associated Products Installation Guide assumes that:
Users are familiar with the concepts of folder/file hierarchies for storing data on disks
and with basic Windows terminology and commands. If not, the user can also refer to
the operating system documentation while carrying out the installation.
Users have already gained access to the PDMS installation files via a disk, from the
AVEVA Web site, or by some other route.
Users have Local Administrator rights.
1.2 Guide Structure
The PDMS & Associated Products Installation Guide is divided into the following sections:
Hardware and Software
Requirements
lists the hardware and software requirements.
AVEVA PDMS and Associated
Products Installation
describes how to install and license the software.
Set Up the Windows
Environment
explains how to configure the Windows operating
system before running PDMS.
Language Support describes how to set up the Windows Environment to
use PDMS with different Language options.
Run PDMS Under Windows gives some advice on using PDMS in a Windows
environment.
PDMS Projects describes the sample project that is supplied as part
of PDMS, and how the user can set up projects.
Troubleshooting describes solutions for some of the errors that could
be encountered when running PDMS.
12 Series 1:2
Introduction
1.3 Associated Products
The following are available as additional installation options when installing PDMS.
Global, Global WCF Client and Global Server - for synchronisation of projects between
world-wide sites
Schematic 3D Integrator - Integration application to make sure there is data
consistency between P&ID and the 3D model
Area Based ADP - Automates the production of volumetric drawings using specified
templates, thus simplifying their update after a change to the model
Multi-Discipline Supports - For the design, drawing and MTO of all kinds of supports
ExPlant-A - DXF export driver
ExPlant-I - DGN export driver
Nuclear Applications - Specialised applications for the design and managing of nuclear
power plants
There are various AVEVA products that can be used in conjunction with PDMS. The user
can consider installing these at the same time. Those closely associated with PDMS include
the following DESIGN products:
AVEVA Global Server - For synchronisation of PDMS products between world wide
sites
AVEVA SQL Direct - Access the DESIGN Database directly from within software
products that support Microsoft Universal Data Access interfaces
AVEVA ImPlant-I - Translator for exporting Intergraphs 3D graphics to PDMS
AVEVA ImPlant-STL - For translating stereolithography (STL) files that have been
generated from non-AVEVA mechanical CAD systems into macro files that can be input
to PDMS
AVEVA OpenSteel - Transfer steel detailing data via SDNF
AVEVA PML Publisher - Programmable Macro Language functions, object forms and
macros can be encrypted using the tools available
Model Management - for change & status control of engineering objects (e.g. pipes,
welds, ) from system DESIGN through detailing and into deliverable production
AVEVA P&ID - AutoCad based application that enables the creation of intelligent P&IDs
AVEVA Flexman - License file required to run the software.
Structure of PDMS on .NET outlines the way in which PDMS in installed and
configured in a Microsoft .NET environment.
Troubleshooting the .NET
Installation
describes solutions to some of the .NET related
issues that might be encountered.
Install AutoDRAFT explains the procedure needed to install and configure
AutoDRAFT.
Configure Area Based ADP describes how to configure Area Based ADP.
MDS Installed Configuration describes how to configure folder structure and
naming configurations.
Pipe Stress Interface
Configuration
describes which standard settings need modifying to
complete the installed version.
Introduction
12 Series 1:3
For details of the installation of these add-on products, refer to the relevant installation
guide. If they are required, it may be advisable to read these before installing PDMS.
12 Series 1:4
Introduction
Hardware and Software Requirements
12 Series 2:1
2 Hardware and Software Requirements
The user should refer to the Systems Requirements guide and make sure that the system
and network meets all of the requirements before attempting to install the software.
2.1 AVEVA PDMS 12.1 Software Installation
AVEVA PDMS software is supplied on a disk.
The disk contains
Release Notes
AVEVA Plant Suite 12.1 Help
an installable version of Microsofts .NET Framework
Flexman License Server
Insert the disk in the Workstation disk drive, and then follow the instructions.
If the disk does not start, click Start > Run and then browse for the Start.htm.
2.1.1 Flexman License File
To operate, AVEVA software must be able to access the correct Flexman license file, which
should be installed on either the Server, on the users workstation, or on a networked
workstation. Refer to the Flexman Installation and Configuration Guide. News and update
information is also available for Flexman on the AVEVA support web-site.
Note: Although the disk contains several AVEVA products, the user will only be able to use
the items that are licensed to them. The user will get an on-screen notification to
warn them when the license is due for renewal.
2.1.2 .NET Framework Installation
The graphical user interface requires that Microsofts .NET Framework be installed. The
.NET Framework is supplied on the disk and if it has not been previously installed the
installation will install it automatically when the installation is run from the disk.
2.2 Enable Microsoft Excel Interop Assembly
Several of AVEVA applications use a facility in the AVEVA GridControl to import an Excel
file, for example, Equipment Import, Cable Import, and Diagrams. To make sure that the
Excel import facility will work the user must make sure that the Microsoft Excel Interop
Assembly is enabled on each machine where it will be used.
12 Series 2:2
Open the Add or Remove Programs utility from the Control Panel, and select the version
of Microsoft Office being used, the one shown here is Microsoft Office Professional
Edition 2003.
Click Change to display the Maintenance Mode Options.
12 Series 2:3
Make sure Add or Remove Features is checked and click Next:
Check the option for Choose advanced customisation of applications, and click Next.
12 Series 2:4
Under the Microsoft Office Excel application make sure that .NET Programmability
Support is enabled. If .NET Programmability Support is not enabled then select the
option Run from My Computer, and click Update.
2.3 Font Size
During the installation of Windows 7, the install process decides what it believes to be the
best setting for the font size and sets this as the Default. AVEVA only supports the setting
Smaller and suggests that the user changes their setup to make Smaller the default
setting.
To change the default setting, right-click on the desktop.
Select Personalize from the menu to display the control panel.
12 Series 2:5
Click Display to display the screen for setting the Font size.
12 Series 2:6
Select Smaller and click Apply. The user will have to restart the system to save the
settings.
AVEVA PDMS and Associated Products Installation
12 Series 3:1
3 AVEVA PDMS and Associated Products Installation
The AVEVA PDMS and Associated Products Installation is supplied on a disk in an
installation called Plant. The disk contains an installable version of Microsofts .NET
Framework. Also on the disk is a folder containing the Installation instructions and user
documentation, and it is recommended that the user carefully read all of the Installation
instructions before installing the software.
It is recommended that the default settings are used for folder paths etc., unless the user
has good reasons for doing otherwise.
Important: AVEVA does not recommend the use of spaces in installation folder path
names. However, the system will work, with some limitations. Refer to
section 1.3 of the User Bulletin for further information.
Using the disk to install AVEVA PDMS and Associated products, insert the disk and on the
Welcome screen click Click for contents.
Alternatively the user can click the setup.exe file to install the software manually. Using the
setup.exe option bypasses the first three windows and displays the Plant Setup Wizard
window.
Manual installations can be easier if run from the Setup.exe program, which ships with each
.msi installation supplied on disk. Each Setup.exe checks and installs the dependencies of
its primary installation (like the .NET framework), before running its primary (MSI)
installation. Users should never see missing dependency errors if installations are started
from the Setup.exe program.
Setup.exe also tells the primary installation to target the C:\ drive/volume, which is the
preferred default in most manual installations. However, if a more customised installation is
required then running the primary MSI directly becomes the better approach. In such cases,
run time dependencies (Like the .NET framework) must be deployed beforehand.
Using Setup.exe displays the Plant Setup Wizard window.
12 Series 3:2
A screen showing the available products is displayed.
Click AVEVA PDMS to display the Release Documents screen.
12 Series 3:3
Click INSTALL to display the AVEVA Plant Setup Wizard.
12 Series 3:4
The Plant Setup Wizard activates at this point and guides the user through the installation of
the product. Click Next to display the Custom Setup screen.
The Custom Setup window displays every configurable aspect of the installation.
Configurable Features are displayed on the left hand side of the window, in a control called
the SelectionTree. Each feature is depicted as a box with a description of the feature
displayed in the right hand pane. The boxes representing each feature are depicted as
follows:
Clicking a box displays a drop-down menu.
- Feature will be installed (Locally)
- Feature will be installed (Locally), but not all sub-Features will.
- Feature will be unavailable (Not Installed), as will all descendants.
12 Series 3:5
Clicking Reset will de-select all currently selected features.
If the Feature is not Unavailable ( ), a Location Path showing where the program is to
be installed may be displayed, if so Browse becomes active.
If a Location Path is not displayed and Browse is inactive when a specific Feature is
highlighted and scheduled to be installed, then that Feature contains something which
embeds itself inside another program (whose path is separately configurable). Clicking
Browse, when active, displays the Change Destination Folder window which allows the
user to select a different folder name and location path.
Will be installed on local hard drive Selecting this option will install the feature
locally.
Entire feature will be installed on
local hard drive
Selecting this option will install the feature and
all its sub-features locally.
Entire feature will be unavailable Selecting this option prevents the current
feature and all its sub-features from installing.
12 Series 3:6
Addins and Addons are examples of this sort of thing, as they have no folders of their own,
and they reside inside other programs.
It may appear confusing that some Features do/do not have configurable folder paths. The
following list is hoped to clarify this:
Feature Configurable Default Path
PDMS Yes C:\AVEVA\Plant\PDMS12.1.SP2\
PDMS Models Yes C:\AVEVA\Plant\Project12.1.SP2\
Global Client No C:\AVEVA\Plant\PDMS12.1.SP2\
Schematic 3D Integrator No C:\AVEVA\Plant\PDMS12.1.SP2\
Area Based ADP No C:\AVEVA\Plant\PDMS12.1.SP2\
Multi-Discipline Supports No C:\AVEVA\Plant\PDMS12.1.SP2\
ExPlant-A No C:\AVEVA\Plant\PDMS12.1.SP2\
ExPlant-I No C:\AVEVA\Plant\PDMS12.1.SP2\
Plant Suite Help No C:\AVEVA\Plant\PDMS12.1SP2\Documentati
on\
12 Series 3:7
Changing the Folder Path of the Feature "AVEVA Plant Suite" will affect all applications
residing in subfolders. For example:
if "AVEVA Plant Suite" =J :\Test\
Then
"PDMS" =J :\Test\PDMS12.1.SP2\
"PDMS Models" =J :\Test\Project12.1.SP2\
"Manuals" =J :\Test\PDMS12.1.SP2\Documentation\
However, if any of the other folders were to be directly changed, they would remain in that
state regardless of changes to the "AVEVA Plant Suite" folder or other underlying folders.
To check if enough disk space is available click Disk Usage to display the Disk Space
Requirement screen. Highlighted volumes indicates that there is not enough disk space
available for the selected features. The user can remove some of the files from the
highlighted volumes, install fewer features or select a different destination volume. Click OK
to return to the Custom Setup form.
Click Back to step back a stage, Cancel to terminate the Setup Wizard or Next to display
the existing projects and Infrastructures Configuration screen and continue the installation.
12 Series 3:8
The Configuration screen allows the user with existing projects and infrastructures to
customise the installation.
The Projects Folder path can only be changed if the user has chosen to install the Plant or
the MDS models. To change the path click Browse to display the Change Destination
Folder window which allows the user to select a different folder name and location path.
Unchecking the Install bat files and: checkbox deactivates the StartMenu Shortcuts and
the Desktop Shortcuts options. Both options are dependant on the bat files being installed.
Unchecking the StartMenu Shortcuts checkbox deactivates the Desktop Shortcuts
option. The option is dependant on the StartMenu Shortcuts being installed.
the folder path Configuration screen.
Clicking Browse displays the Change Destination Folder window which allows the user to
select a different folder name and location path.
the Ready to Install AVEVA Plant screen.
12 Series 3:9
The Selection Review pane displays the installations options selected by the user. The
user can now click Back to step back a stage and change their installation option, Cancel to
terminate the Setup Wizard or Install to display the Installing AVEVA Plant screen.
12 Series 3:10
The Installing AVEVA Plant screen displays a taskbar showing the status of the
installation.
During the installation process the screen displays Cancel, which can be clicked to stop the
installation. When selected a window is displayed asking for confirmation that the AVEVA
Plant installation is to be cancelled.
Selecting Yes displays a screen showing the AVEVA Plant Setup Wizard was interrupted.
12 Series 3:11
Click Finish to exit the screen and installation.
Selecting No on the confirm screen returns the user back to the Installing AVEVA Plant
screen and continues the installation.
12 Series 3:12
When the installation has been completed, click Finish to exit the Setup Wizard.
3.1 Log File
During the installation, setup.exe creates a log file of the installation in the users TEMP
directory named Plant12.1.2.log. To locate the log file, select Start > Run and type
%TEMP% in the text field.
Click OK to display the users TEMP directory.
12 Series 3:13
3.2 Uninstall
Complete removal of an installation can be accomplished by several methods.
Removing it from Start > Settings > Control Panel > Add/Remove Programs applet
Right clicking on the MSI file that installed it, and selecting Uninstall
Running the command MSIEXEC /X [Path to Original MSI]
Running the command MSIEXEC /X {ProductCode of MSI}
Removal of individual Features is also possible from the command Line, using the
REMOVE property or by changing the installation state via the Add/Remove Programs
applet.
Note: Uninstalling the PDMS and associated Products installation will not uninstall
Microsoft's .NET Framework or downgrade the Windows Installer Service. The .NET
Framework must be removed separately if required.
3.3 Modifying
There are several ways to modify an installed installation. For example:
Changing it from Start > Settings > Control Panel > Add/Remove Programs applet
Right clicking on the MSI file that installed it, and selecting Install, then selecting
Change at the subsequent window.
Running the command MSIEXEC /I [Path to Original MSI], then selecting Change at
the subsequent window.
Running the command MSIEXEC /I {ProductCode of MSI}, then selecting Change at
Once the Change option is selected the Custom Setup window is displayed allowing the
user to change which features are installed.
12 Series 3:14
The Change option can not be used to change the Location Path. If the user wants to
change the Location Path, the current installation must be removed and then re-installed
using the new Location Path.
Note: Never move files by other means, as this may trigger healing, however Copying files
to other locations will not cause problems.
3.4 Repairing
If any programs stop working, or the installation has knowingly been damaged, then Repair
may fix the problem.
There are several ways to repair an installation. For example:
Changing it from Start > Settings > Control Panel > Add/Remove Programs applet
Right clicking on the MSI file that installed it, and selecting Install, then selecting Repair
at the subsequent window.
Running the command MSIEXEC /F [Path to Original MSI], then selecting Repair at the
subsequent window.
Running the command MSIEXEC /F {ProductCode of MSI}, then selecting Repair at
Repairing installations causes them to heal themselves. For more information refer to
Healing.
12 Series 3:15
3.5 Healing
MSI technology has inbuilt self repairing mechanisms. As such it is generally unwise to alter
file and folder names, shortcuts or registry manually, as this may trigger the MSI which
deployed the files to redeploy them.
However, it is expected that some users will want to alter Appware, "Sample Data"
Shortcuts and .bat file variables. As such, AVEVA installations have been designed to
minimise the ability of the MSI to heal itself in such cases.
Sample Data, Models, example projects and shortcuts, should not trigger healing if they are
deleted or altered. The consequence of making shortcuts editable/deletable is that MSI
Advertising will not function.
3.6 Modified New and Removed Files
Irrespective of whether an MSI is installing, changing state, or repairing, files are removed/
deployed/overwritten based upon certain file version rules. As such, the changes caused by
a repair or an installation depend upon the initial state of the computer.
3.6.1 User Modified Appware
In MSI/Deployment terms, Modified appware files constitute un-versioned, language neutral
files, whose "Created Date" and "Modified Date" differ. However, if appware files have been
moved or handled in certain ways, then it is possible that the "Created Date" and "Modified
Date" will not differ, in which case the file replacement behaviour of the installation will be
different.
In the case where an appware files "Created Date" and "Modified Date" is different, no MSI
will ever overwrite such a file. So Modified appware will never be upgraded (by default),
changed or bug fixed by an AVEVA MSI or Patch.
In the case where a modified appware files "Created Date" and "Modified Date does not
differ, the appware file with the newest date will prevail (by default). This scenario is most
likely to happen when installing a Patch or an MSI which is not classed as a "Service Pack"
or a "Full Release", since releases with more minor designations are not side-by-side
deployable, as they are intended as upgrades to pre-existing releases.
Once appware has been modified, it must fall to the author/owner to maintain the changes,
since there is no reliable way to reconcile code differences. In extreme cases this may mean
that AVEVA installations cannot be used to deploy appware, and those clients must make
their own code merges.
3.7 Models, Sample Data and Example Projects
It is in the nature of Models, Samples and Examples, that:
The constituent parts are often interdependent in some way.
Interdependencies will vary between releases and can be difficult and risky to migrate
automatically.
Their file footprint is apt to change drastically.
They will not always be required.
They may be moved, copied and shared.
File paths and folder names may change in time.
12 Series 3:16
Parts of them may be re-used in other scenarios.
They can be supported or migrated across many versions of an application.
Many different programs may work with them and with data derived from them.
Hence, it is felt that Models, Samples and Examples:
Should be regarded as separate entities in their own right.
Have a lifecycle which is likely to differ from the applications which they service.
May be released with installations which install applications, but should be as easy as
possible to divorce from such installations.
Are unsuited to Repair or Patching by installations.
Are risky to de-install/remove when applications are removed.
Should be released holistically.
Should be available separately from application installations in special cases.
May suit release in a simple compressed archives (.zip file or self extracting executable
say).
Current AVEVA MSI installations attempt to address these requirements by completely
removing an installations ability to heal its Models, Samples and Examples. If a new copy is
required, the installation must be completely removed, and then reinstalled. Repairing will
not restore Models, Samples or Examples.
Uninstalls, are achieved by deleting the root folders where the Models, Samples and
Examples where deployed to. It is important to remove them if they are to be retained.
3.8 Changing Default File Replacement Behaviour
It is possible to alter default file replacement behaviour in circumstances where an MSI
installation or Patch is launched from a command line. This is achieved with the
REINSTALLMODE property or the /f command line switch. Otherwise default file
replacement rules will apply.
Default file replacement rules should suit most users.
It is desirable to change file replacement behaviour, in situations where the Date/Time
stamps of files might not support the required replacement of files.
3.8.1 Post Deployed .bat files
The .bat files which AVEVA installations deploy and edit are regarded as necessary for the
applications to work, and so could be repaired by the installation if they are removed.
However, they can be edited or replaced post deployment without risk, as long as the files
"Created Date" and "Modified Date" is different (this stops an MSI from overwriting the file).
3.8.2 Pre-Deployed .bat files
It is feasible to replace .bat files before deployment, in the case where deployments are
staged from Admin Installations. However the details and issues concerning Admin
Installations are beyond the scope of this manual.
It is also possible to add additional files to an MSI installation, but an MSI table editor of
some sort would be required. This is not a trivial option, and may well require the services of
a professional re-packager. However it can be accomplished without compromising an
installations ability to be patched.
12 Series 3:17
3.8.3 .bat file Shortcuts
All the shortcuts pointing to the .bat files are of the non-advertised or normal type. As such
they can be deleted and edited, without triggering healing.
3.9 Network (Admin) Installations
Administrative Installation Mode is a type of .msi installation, which only causes an
uncompressed copy of the original installation to be generated to a specified location
(TARGETDIR). It does not install applications, it creates another installation.
The installations media (deployable files) is unpacked into a subfolder beneath the
regenerated .msi file, rather than stored in external .cab files or in .cab files embedded
within the .msi file itself. The resultant folder structure created resembles that, which a
(Typical) local deployment would create by default.
Administrative installations do not become installed onto the computer which spawned it.
They only transform the source installation into an uncompressed variant of itself during this
process.
3.9.1 Create an Administrative Installation Point
To create an admin installation from an installation, start the installation from the Command
Line as follows to display the AVEVA Plant Administration Point Setup screen:
MSIEXEC /A [Path to MSI File]
12 Series 3:18
Click Next to display the AVEVA Plant Administration Point Distribution screen.
12 Series 3:19
Enter the location where the Admin Installation is to be created. Clicking Browse displays a
window allowing the user to navigate to the required location.
Click Install to start the installation.
Conversely, the following Command Line will achieve the same result quietly:
MSIEXEC /A [Path to MSI File] /QN TARGETDIR=[Path to Admin Installation]
3.10 Issues with Administrative Installation Points
3.10.1 .NET Security
.NET security defaults to not allowing .NET program code to execute if it resides in a
network location. There are several ways to Trust such locations, but Trusted it must be, if
programs are to run across a network.
.NET security can cause issues when running PDMS across the network where the add-in
assemblies reside on a different machine to the .NET runtime. The default security level for
the local intranet is not set to Full Trust, which means that programs may not be able to
access resources on the local machine. To overcome this, the intranet security may be set
to Full Trust, though this means that any .NET assembly may run. Alternatively, Full Trust
may be given to a specified group of strongly named assemblies.
12 Series 3:20
Full Trust is configured using the code access security policy tool caspol. First of all the
assemblies must be strongly named. Then caspol is run on each client machine to add all
the assemblies on a given server directory to a group and give Full Trust to this group as
follows:
To trust all assemblies in a given folder:
caspol - m- ag Local I nt r anet _Zone - ur l \ \ <Ser ver Name>\ <Fol der Name>\ *
Ful l Tr ust - n " <Name>" - d " <Descr i pt i on>"
OR to trust all assemblies with the same strong name:
CasPol . exe - m- ag Local I nt r anet _Zone - st r ong f i l e
\ \ <Ser ver Name>\ <Fol der Name>\ <assembl yName> - noname - nover si on
Ful l Tr ust - n " Aveva" - d " Ful l t r ust f or Aveva pr oduct s"
where <ServerName>is the UNC (Uniform Naming Convention)
The format of a UNC path is:
\ \ <ser ver name>\ <shar ename>\ <di r ect or y>
where:
caspol can be found in c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\ or is part of
the .NET Framework 2.0 SDK which can be downloaded from:
http://www.microsoft.com/downloads/details.aspx?FamilyID=fe6f2099-b7b4-4f47-a244-
c96d69c35dec&displaylang=en
3.10.2 Signing
Newer windows operating systems have code signing embedded into their security. As
such, AVEVA have begun signing .msi files and .cab files for installations which are not
restricted to Windows XP or older operating systems.
Unfortunately, the Administrative Installation process recreates and/or alters the source .msi
file and removes .cab files altogether, thus removing any file signatures. Changes to signed
file always invalidates its signature.
In this release AVEVA have signed all dll's and exe's that are supplied. However in order to
cater for installations where internet access is not permitted/available we provide an
.exe.config files for each exe file that tells the operating system not to validate the digital
signature. By default the installation is set to deploy the .exe.config to disable the digital
signature validation. To enable digital signature validation the command line option
CERTIFICATECHECK=1 should be set.
3.10.3 Using Files within the Source Installation
MSI databases can be authored to allow Features to be installed in the "Will be installed to
run from network" state. AVEVA Installations do not currently support this mode; however it
may be made available if requested.
The "Will be installed to run from network" option is otherwise known as run-from-network.
In this mode, files are not copied onto the target computer, but registry, shortcuts and file
<servername> The Network name
<sharename> The name of the share
<directory> Any additional directories below the shared directory.
12 Series 3:21
edits do occur on the target computer, and they address the programs which reside inside
the source installation.
3.10.4 Network Throughput
Admin installations can be very suitable for staging large deployments, because
uncompressed installations usually travel better over networks because they are even more
fragmented. The overall size is typically much larger; however this is still tends to be easier
on Packet Switching Networks.
3.10.5 Advantages of a Network Installation
Once computers address files across a network, it becomes crucial that the files are
accessible whenever required. This then begs questions regarding:
Network Reliability
Network Performance
File Server Reliability
File Server Performance
Change Synchronisation
Change Granularity
Common reasons for storing programs on file Servers are:
To avoid the network loading of large and un-staggered rollouts.
To guarantee the user base is working with the same files.
To prevent tampering with programs and settings.
To maintain a tradition.
All of these issues are of course resolvable with locally deployed applications
Note: Direct editing of .msi's is discouraged in favour of Transforms (.mst files).
3.11 Run PDMS and Associated Products from Network
Locations
Running programs directly from network locations is discouraged because:
AVEVA installations have been redesigned to deploy well across networks.
Network reliability and performance is less of a factor.
Patch rollback functionality only works with local installations.
However, it is recognised that network based programs suit circumstances where:
Multiple instances of the same program are required.
An embedded tradition of working this way exists.
Change impacts Quality Control systems.
So this information is provided to facilitate successful over network operation.
Definitive instructions on how to run AVEVA programs from network file servers are
impractical, given the many ways in which AVEVA programs can interact with each other
and with Project data. Not to mention other possible permutations.
So the following information is deliberately general and lacking in detail and it is aimed at
assisting a highly skilled readership.
12 Series 3:22
The following things must happen if programs are to be run directly from a file server:
The programs and the projects environment must be correctly defined.
Appropriate .NET Trust should be granted to the programs network location.
Visual Studio 2008 C++Runtimes should be pre-installed.
.NETFramework Redistributable should be pre-installed.
The appropriate shortcuts and drive mappings should be provisioned.
3.11.1 Administrative Installation Points
The Files and Folders extracted to an "Administrative Installation Point" are laid out in a
fundamentally identical way to a local installation. Additionally, files which are normally
deployed to operating system folders will also be visible, but will play no functional part
unless deployed locally.
Some Configuration files will be incomplete, or have incorrect data in them, as they are not
edited until they are deployed (Locally). These files may require manual editing and concern
which Modules, Addins, Addons and "User Interface Modifications" are loaded.
3.11.2 Patch Administrative Installations
A slightly different Patch is required for an administrative installation than for a local
installation, and standard AVEVA patches target local installations. If such a Patch is applied
to an Administrative Installation Point, the patch will succeed. However, any local
installations which have previously been deployed from it will cease to recognise it as their
source installation. So as long as local deployments have not occurred, an Administrative
installation is patchable with an AVEVA patch. Similarly, if programs within the installation
are addressed by a clients own means, then the Administrative Installation can be patched
at any time with impunity. Since in this event the Installation has not been deployed (Locally)
and so only the media state has any effect.
AVEVA patches are supplied inside an executable wrapper. To apply them to an
administrative image, the patch must be extracted and the appropriated command line
used. The appropriate command switch is /C which extracts the contents to the current
folder.
Note: Patches cannot be rolled back from Administrative Installation Points. A copy must
be made before the patch is applied, in order to rollback.
Note: Patches cause changes to the .msi file, which invalidates any security certificates
applied to the installation.
3.12 Copy a Local Deployment to a File Server
Installing normally to a local computer and then copying the programs to a network location,
as a way to create a network based installation has several advantages over an
"Administrative Installation Point":
The fundamental configuration file editing has happened.
The Local installation need only include the required applications.
Note: Running a normal (Local) installation, and choosing a network drive as a target for
the programs will fail to install. This is because file editing is performed with the local
System Accounts credentials, which are not normally recognised by other
computers.
12 Series 3:23
3.13 Feature Id Reference List
3.13.1 Feature Tree Hierarchy
The following diagram shows the Plant installations SelectionTree by Feature Id's. Ancestor
(Parent) Features to the Left, Descendant (Child) Features to the Right.
PDMS
PDMS -- MODELS
PDMS -- GLOBALUSER
PDMS -- GLOBALUSER -- GLOBALWCF
PDMS -- PIDINT
Feature Id Title Description
ABA Area Based ADP Area-based Automatic Drawing Production (ABA)
Add-on to PDMS that automates the production of
volumetric drawings of using specified templates,
thus simplifying their update after a change to the
PDMS model.
EXPLANTA ExPLANT-A DXF export driver
EXPLANTI ExPLANT-I DGN export driver.
GLOBALUSER Global Client Upgrades this installation to include the Remote
Procedure Call (RPC) Global Client. This is required
to allow PDMS Users to invoke Global commands.
MDS Multi-Discipline
Supports
Multi-Discipline Supports (MDS) Add-on to PDMS
for the design, drawing and MTO of all kinds of
supports, from a complicated framework
encompassing integral hangers to a simple U-bolt.
MDSMOD Plant Compatible
Models
Sample data, including catalogues, for PDMS and
associated products.
MODELS PDMS Models Sample data, including catalogues, for PDMS and
associated products.
NUCLEAR Nuclear
Applications
Contains separately licensed products Nuclear
Concrete Design, Nuclear Room Manager and
Nuclear Concrete Quantities
PDMS PDMS PDMS, including applications. Includes separately
licensed add-ons: Diagrams, Cable Design, Laser
Model Interface, Query, SQL-Direct.
PIDINT Schematic 3D
Integrator
Integration application to ensure data consistency
between P&IDs and the PDMS 3D model.
PLANT AVEVA Plant
Suite
AVEVA PDMS and associated Products 12.1.SP2
12 Series 3:24
PDMS -- ABA
PDMS -- ABA -- MDS
PDMS -- ABA -- MDS -- MDSMOD
PDMS -- EXPLANTA
PDMS -- EXPLANTI
PDMS -- NUCLEAR
PDMS -- MAN
3.14 SelectionTree Selection & De-selection Rules
Successful Inclusion of a descendant Feature implies that all ancestor Features are also
included. For example, suppose the MDS Feature is required. This implies that PLANT,
PDMS and ABA must also be included, since they are ancestors of the MDS Feature (see
above).
De-selection of a Feature overrides any commands or defaults which may have otherwise
included it. For example, suppose MDS is included, and ABA is excluded. The result will be
that PLANT and PDMS are installed, since they default to being installed. Removing ABA
causes MDS to be removed, since ABA is its Parent (Ancestor), (see SelectionTree
Hierarchy diagram).
3.15 Selecting Features from the Command Line
Features can be in the following states:
Run Locally
Run from Source
Not Present
Advertised
There are several ways of controlling Feature states, but for the sake of clarity this
discussion will be limited to the ADDLOCAL and REMOVE Properties. The ADDSOURCE
Property is considered less relevant, as the "Will be installed to run from network" Feature
option, is not available to Features within this installation.
The ADDLOCAL and REMOVE Properties are comma separated lists of an installations'
Feature Id's. Any Features intended to be "Run Locally", will be listed in the ADDLOCAL
Property, whilst any Features intended not to be installed will be listed in the REMOVE
Property.
As previously stated, de-selection commands override inclusion commands. The reason for
this is because the REMOVE Property is evaluated after the ADDLOCAL property. The
partial list below shows the order in which FeatureState Properties are evaluated by the MSI
Service:
1. ADDLOCAL
2. REMOVE
3. ADDSOURCE
4. ADDDEFAULT
5. REINSTALL
12 Series 3:25
6. ADVERTISE
3.16 Command Line Definable Directories
The following directories can be set on the Command Line, in the same way that Properties
are assigned.
As with Properties, Directories for which the Id's are all uppercase, can be re-defined on a
Command Line. They must also be addressed in uppercase on the Command Line,
because Id's are case sensitive.
e.g. PRODUCTDIR="C:\Some Path with Spaces in it\"
Will make PDMS install to:
"C:\Some Path with Spaces in it"
Rather than to:
C:\AVEVA\Plant\PDMS12.1.SP2
Note: There is no space around the equals (=) sign.
Note: The quotes surround the value, and would be unnecessary is the value had no space
within it.
3.16.1 Sample Command Lines
A most definitive reference to MSI Command Line arguments can be found here. The
following examples have been tested, but are only intended to demonstrate general
Command Line principles.
In Windows 7 and Windows Server 2008 make sure that the command line has been
opened using the option Run as administrator so that the silent install application has the
correct User Access Control (UAC).
Directory Id Explanation
PDMSUSER Specifies the pdmsuser directory location
PDMSWK Specifies the pdmswk directory location
DFLTS Specifies the PDMSUI\DFLTS directory location
PROJ ECT Specifies the directory to extract the models to
PRODUCTDIR Specifies the root product directory location
TARGETDIR Target location for an Administrative Installation
ROOTDRIVE The Partition where All Applications will be targeted (unless
application directories are set).
12 Series 3:26
Example 1 Installing Everything with Exceptions
Installs all Features except "Area Based ADP" to the "E:\" drive
Unattended Installation showing a progress bar with no cancel button, no finished dialog
and standard logging. Never attempt to Reboot
Create a basic log
MSI EXEC / I [ Pat h t o MSI ] ADDLOCAL=ALL REMOVE=ABA ROOTDRI VE=E: \
REBOOT=Real l ySupr ess/ l [ Pat h t o l og f i l e] / qb! -
Example 2 Installing projects to a different location and setting users writeable areas
to a separate drive.
Installs all Features to the C:\
MSI EXEC / I [ Pat h t o MSI ] ADDLOCAL=ALL ROOTDRI VE=C: \
PDMSUSER=D: \ AVEVA\ Dat a12. 1. SP2\ PDMSUSER PDMSWK=D: \ AVEVA\ Dat a12. 1. SP2\ PDMSWK
DFLTS=D: \ AVEVA\ Dat a12. 1. SP2\ PDMSUI \ DFLTS PROJ ECT=Q: \ PDMS\ 12. 1. SP2/ l [ Pat h
t o l og f i l e] / qb! -
Example 3 Removing an Installation
MSI EXEC / X [ Pat h t o MSI ] / QB!
Example 4 Removing a Feature
Remove "ExPLANT-I"
MSI EXEC / I [ Pat h t o MSI ] REMOVE=EXPLANTI / qb! -
Set Up the Windows Environment
12 Series 4:1
4 Set Up the Windows Environment
Setting up the Windows Environment section describes how to configure the Windows
operating system before running PDMS. Following the installation of PDMS, the user should
perform the following steps:
Check the settings for the graphics board: See Graphics Card Settings.
Make sure the Flexman License Manager daemon is running, and set the environment
variables relating to Flexman: Refer to Set the License File Location.
Configure Windows parameters for PDMS: Refer to PDMS Environment Variables.
The user can then run PDMS by clicking on the PDMS shortcut or icon, which will set
up the remaining environment variables required.
Note: In the following instructions it is assumed that AVEVA PDMS has been installed in
folder C:\AVEVA\Plant. If it has been installed elsewhere, substitute
C:\AVEVA\Plant with the name of the installation folder.
4.1 Windows Control Panel
The Windows Control Panel contains tools that are used to change the way Windows looks
and behaves. This Installation Guide describes how to use Control Panel tools to configure
Windows to run PDMS.
Open the Control Panel as follows:
Windows XP
If the users computer is set up with the Classic Start menu, click Start, point to
Settings, and then click Control Panel.
If the users computer is set up with the standard Start menu, click Start and then click
Control Panel.
4.2 Graphics Card Settings
The user should set the display to a resolution of at least 1024 x 768 ( 1920 x 1200
recommended) and the colour depth to True colour or 16.7 million colours.
To set the display settings, open the Control Panel. Select Display and select the Settings
tab. Make the appropriate selections on the form for the graphics card.
Due to the rapidly changing list of hardware accelerated OpenGL graphics cards
commercially available, an up-to-date list of supported graphics cards, graphics device
drivers and recommended device driver configuration cannot be included in this document.
However, the AVEVA Support Web pages (http://www.aveva.com/support) contain a current
list of both tested and supported graphics cards, along with advice on configuration of
graphics device drivers.
12 Series 4:2
4.3 Set the License File Location
Before the user can use PDMS, the Flexman license system must be set up and connected
to the Flexman License Manager daemon, refer to the Flexman Installation and
Configuration Guide. A license file should be requested from AVEVA Customer Services.
4.4 PDMS Environment Variables
PDMS uses Windows Environment variables to locate folders containing PDMS system files
and users project data. This allows the user to locate these folders anywhere on the file
system. The default location for PDMS system files is C:\AVEVA\plant\PDMS12.1.SP2\,
unless the default location was changed during the installation.
PDMS is supplied with a file evars.bat in the PDMS executables folder which sets default
values for the environment variables so that they point to the folder structure as installed. It
also sets the PATH variable to include the PDMSEXE folder containing PDMS executables.
The user may need to modify this file to reflect the folder structure of their own installation.
The following is a list of the variables the user may need to reset, with a brief description of
each one and the default setting.
Note: all environment variables must be entered in UPPERCASE.
Search Paths of Folders Containing Spaces
Search paths of folders can contain spaces, by using a semicolon as the separator between
folders, for example:
set PDMSUI =C: \ Local PDMS\ Appwar e; M: \ Pr oj ect PDMS\ Appwar e;
a: \ Company PDMS\ Appwar e
Note: that in order to define an environment variable that contains just one item including
spaces, it must explicitly include a final semicolon. For example:
set PDMSUI =C: \ Local PDMS\ Appwar e;
Length of Search Path Environment Variable
The lengths of PDMS search path environment variables can be up to a maximum of 5120
characters.
Recursive Expansion of Environment Variables
An environment variable defining a search path can itself contain references to other
environment variables. For example:
set MPATH=%ROOT%\ St andar d Ver si on; %ROOT%\ Updat e Ver si on
set ROOT=C: \ Pr ogr amFi l es\ AVEVA; (note final semicolon)
Then on PDMS:
*$m%MYPATH%\ mac
Will check in turn for:
C: \ Pr ogr amFi l es\ AVEVA\ St andar d Ver si on\ mac
C: \ Pr ogr amFi l es\ AVEVA\ Updat e Ver si on\ mac
12 Series 4:3
PDMS System Environment Variables
The following environment variables refer to the location of PDMS system files.
PDMS User Environment Variables
The following environment variables refer to the location of users PDMS folders. Users must
have write permission to these folders.
PDMSEXE Executable folder
C:\AVEVA\Plant\PDMS12.0.xxx
PDMSEXEMAIN Copy of PDMSEXE, but can be a search path
C:\AVEVA\Plant\PDMS12.0.xxx
PDMSUI Application User Interface folder (PML 1)
C:\AVEVA\Plant\PDMS12.1.SP2\PDMSUI
PMLLIB Application User Interface folder (PML 2)
C:\AVEVA\Plant\PDMS12.1.SP2\PMLLIB
PDMSDFLTS Applications defaults folder
C:\AVEVA\Data12.1.SP2\PDMSUI\dflts
PDMSPLOTS Applications PLOTS folder
C:\AVEVA\Plant\PDMS12.1.SP2\PDMSUI\plots
PLOTCADC
Pointer to the PLOT executable.
C:\AVEVA\Plant\PDMS12.1.SP2\plot\plot.exe
PDMSHELPDIR Online help data files.
C:\AVEVA\Plant\PDMS12.1.SP2\Documentation
PDMSWK Temporary PDMS work file folder
C:\AVEVA\Data12.1.SP2\PDMSWK
PDMSUSER Application Users save/restore setup area (or the users
'home' folder)
C:\AVEVA\Data12.1.SP2\PDMSUSER\
PDMSREPDIR PDMS Applicationware Report Input and Output folder.
C:\AVEVA\Plant\PDMS12.0\PDMSUI\reports
PDMSDFLTS Applications defaults folder. Note that individual users may
not have permission to change PDMS System defaults in
C:\AVEVA\Data12.1.SP2\PDMSUI\dflts, but they should
have their own local defaults area. This is achieved by
setting a PDMSDFLTS search path, e.g. C:\USERDFLTS
C:\AVEVA\Data12.1.SP2\PDMSUI\dflts.
12 Series 4:4
Project Environment Variables
For each PDMS project, the following environment variables must be set. For example, for a
project ABC:
PDMS is installed with sample project data (Refer to PDMS Projects). PDMS Project
Environment variables for these projects are set in evars.bat.
4.5 Run PDMS from a Command Window
The user can run PDMS from a Command window rather than using the Start/Programs
menu. To do this the user must set the PATH variable to include the folder where PDMS is
installed.
Windows XP
Open the Control Panel.
Select System, and pick the Advanced tab.
Click on the Environment Variables.
Edit the system variable Path to add the PDMS folder (for example,
C:\AVEVA\Plant\PDMS12.1.SP2\) to the list of folders in the Path variable.
Once the Path variable includes the AVEVA PDMS folder, the user can run PDMS by typing
pdms at a command prompt.
4.6 Customise PDMS Start-Up
There is a batch (.bat) file supplied in C:\AVEVA\Plant\PDMS12.1.SP2\ called pdms.bat
which allows entry into PDMS.
The user can run PDMS using this batch file in any of the following ways:
Use the shortcut in the Windows Start menu, Start > All Programs > AVEVA Plant >
Design > PDMS 12.SP2 > Design
The user can create a shortcut on their desktop to run their batch file. With the cursor in
the desktop area, right-click and select New > Shortcut. This shows a sequence of
dialogs to help the user create the shortcut. Type in the location of pdms.bat, for
example:
C:\AVEVA\Plant\PDMS12.1.SP2\pdms.bat
then press Next and give the shortcut a name.
Press Finish.
The user should now be able to double-click on the shortcut icon to enter PDMS.
If the user has C:\AVEVA\Plant\PDMS12.1.SP2\ (the path name for the pdms.bat file)
in their PATH environment variable, just type pdms in a command window to execute
the batch file.
ABC000 Project database folder
ABCISO Project ISODRAFT options folder
ABCMAC Project Inter-DB connection macro folder
ABCPIC Project DRAFT picture file folder
ABCDFLTS Project configuration settings
12 Series 4:5
Otherwise, navigate to the folder where the batch file is stored and type pdms or
pdms.bat.
4.6.1 Create User Batch File to Run PDMS
The user can set up their own batch files to run PDMS. For example, the user may want to
run DESIGN checking utilities every night, or update batches of drawings overnight.
Begin by creating a batch file, for example, runpdmsmacro.bat.
Type the following line into this file:
C: \ AVEVA\ Pl ant \ PDMS12. 1. SP2\ pdms. bat TTY SAM SYSTEM/ XXXXXX /
STRUC $M/ mymacr of i l e
Where:
TTY tells PDMS not to start the PDMS GUI. This gives command line only operation.
SAM is the project name.
SYSTEM/XXXXXX is the PDMS username/password to be used when running the
command macro
/STRUC selects the required MDB
mymacrofile is the pathname of a PDMS command macro, containing the commands
that the user wants to execute in PDMS.
In this example, running runpdmsmacro.bat will enter PDMS in project SAM, as user
SYSTEM/XXXXXX, in MDB /STRUC, and run the PDMS command macro mymacrofile.
4.7 Run PDMS in Batch
PDMS creates a separate PDMSConsole process to manage the command-line input/
output for all modules. When PDMS is invoked from a .bat file, processing of this file
resumes as soon as the user leaves MONITOR - even though the user is still using PDMS.
To help manage this situation, PDMSWait.exe is distributed as part of PDMS and can be
used to make a PDMS script wait for PDMS to complete before continuing.
PDMSWait uses Windows facilities to wait for an event triggered by PDMSConsole when
PDMS finishes. Because the user can be running more than one PDMS session on any one
computer, both PDMSWait and PDMSConsole look for an environment variable
PDMS_CONSOLE_I DENTI FI ER before doing this. The user can set
PDMS_CONSOLE_I DENTI FI ER to any unique string. In a .bat file the user can use the
%RANDOM% or %TIME% values provided by Windows; in a Perl script, the user can use
the process number, accessible as $$.
This will start PDMS, then wait until it has finished before resuming the script.
The MONITOR Reference Manual provides more details on running PDMS batch programs.
Example:
set PDMS_CONSOLE_I DENTI FI ER=%RANDOM%
cal l %PDMSEXE%\ pdms
cal l %PDMSEXE%\ pdmswai t
echo Ret ur ned t o . bat at %TI ME%
12 Series 4:6
4.8 Plot
To plot in a Windows environment, AVEVA recommend that the user uses the plotcadc.bat
file supplied in the AVEVA PDMS folder.
Note: The user may have to modify the plotcadc.bat file to suit their local printer
installation.
The Network Plotter must be mapped using the NET USE command. Refer to the network
documentation for more information.
To run the plotcadc.bat file, give a command in the format:
C: \ AVEVA\ Pl ant \ PDMS12. 1. SP2\ pl ot cadc. bat plotfile format printer options
Where options are the AVEVA PLOT utility options, and may be omitted. See the PLOT
User Guide for more information.
Note: The options must be enclosed in quotes.
Example:
pl ot cadc. bat c: \ pdms\ pl ot 1 ps \ \ nt ser ver \ NTPost Scr i pt
pl ot cadc. bat c: \ pdms\ pl ot 1 hpgl \ \ nt ser ver \ NThpgl ' CE=Y'
Language Support
12 Series 5:1
5 Language Support
PDMS 12.1.SP2 introduces the use of Unicode for character storage throughout, with the
exception of data migrated from previous versions or deliberately created in this 'legacy'
format. This simplifies its installation so that, in general, no special settings are required,
other than making sure that the appropriate language support is installed in Windows. This
will enable the support of many more languages in the future.
There are aspects of the Unicode standard that are not yet implemented. PDMS currently
handles the following correctly:
Left to Right languages; and therefore not, for example, Arabic and Hebrew
Pre-composed characters; for example, the single character but not the combiners a
+' =>
Upper and lower casing of characters, where both cases have the same number of
bytes
Previous versions of PDMS have been supported only with certain language groups; the
same groups have been used to test PDMS 12.1.SP2 and are fully supported. No PDMS
font files are available for any other language; this means that TrueType fonts must be used
on drawings and that therefore it is not possible to produce plotfile output.
These groups are:
Latin-1
Latin-2
Latin-Cyrillic
Far Eastern
12 Series 5:2
Language Support
Supported Languages
5.1 Setting PDMS Default Text Format
By default all sequential text files read by PDMS will be expected to be in UTF-8 format with
a Byte Order Mark (BOM) present to identify them. This includes PML files, Datal files etc.
Similarly by default all sequential text files written by PDMS will be in Unicode UTF-8 format
with a BOM present.
A simple command line 'transcoder' is also supplied; this may be used in some applications
to convert files to a different encoding. This is installed with PDMS and is called transc.exe;
further details can be found using its -h command line option.
In order to change these defaults, environment variables are available for users to modify
the way PDMS handles sequential text files:
These variables may be set to a variety of values:
Name Description Languages covered
Latin 1 ISO 8859-1 Latin alphabet 1 Danish, Dutch, English, Faroese, Finnish,
French, German, Icelandic, Irish, Italian,
Norwegian, Portuguese, Spanish,
Swedish,
Latin 2 ISO 8859-2 Latin alphabet 2 Albanian, Czech, English, German,
Hungarian, Polish, Rumanian, Serbo-
Croat, Slovak, Slovene
Latin-Cyrillic ISO 8859-5 Latin/Cyrillic
alphabet
Bulgarian, Byelorussian, English,
Macedonian, Serbo-Croatian, Ukrainian,
Russian
Far Eastern J apanese, Korean, Simplified Chinese,
Traditional Chinese
CADC_LANG Specifies the file encoding for reading external files which do not
have a Unicode BOM present. If the variable is unset, this
defaults to LATIN-1. Files with the following Unicode BOMs will
be translated to UTF-8 on reading: UTF-16 little-endian, UTF-16
big-endian, UTF-32 little-endian, UTF-32 big-endian.
CADC_LANG_NEW Specifies the file encoding for new files written. If the variable is
unset, the default is Unicode UTF-8 format with a BOM present.
UTF8 Unicode UTF-8 (the default)
UTF16LE UTF-16 little-endian
UTF16BE UTF-16 big-endian
UTF32LE UTF-32 little-endian
UTF32BE UTF-32 big-endian
LATIN1 ISO8859-1
Language Support
12 Series 5:3
5.2 Prepare PDMS For Legacy Database
These settings should not be required for new projects but must be set correctly in order to
use 'legacy' databases. This is particularly important if they are to be reconfigured to
Unicode as the transcoding will be based on these settings.
The corresponding font family must be selected for DRAFT and ISODRAFT drawings. Use
Project > Font Families and select the Font Type appropriate for the chosen language.
For details, see the Administrator User Guide and Administrator Command Reference
Manual.
LATIN2 ISO8859-2
LATIN3 ISO8859-5 Cyrillic
J APANESE J apanese Shift-J IS
CHINESE Simplified Chinese (EUC)
KOREAN Korean (EUC)
TCHINESE Traditional Chinese (used in Taiwan for example) (EUC)
CP932 J apanese Shift-J IS
CP936 Simplified Chinese GBK
CP949 Korean
CP950 Traditional Chinese Big5
CP1250 Central European
CP1251 Cyrillic
CP1252 LATIN-1 +some extras (beware)
Command Languages covered
PROJ ECT CHARSET LATIN 1
(default)
Danish, Dutch, English, Faroese, Finnish, French,
German, Icelandic, Irish, Italian, Norwegian,
Portuguese, Spanish, Swedish,
PROJ ECT CHARSET LATIN 2 Albanian, Czech, English, German, Hungarian, Polish,
Rumanian, Serbo-Croat, Slovak, Slovene
PROJ ECT CHARSET LATIN
CYRILLIC
Bulgarian, Byelorussian, English, Macedonian, Serbo-
Croatian, Ukrainian, Russian
PROJ ECT MBCHARSET J AP J apanese
PROJ ECT MBCHARSET KOR
FILE /<font filename>
Korean
PROJ ECT MBCHARSET CHI Simplified Chinese
PROJ ECT MBCHARSET
TCHIN FILE /<font filename>
Traditional Chinese
12 Series 5:4
Language Support
Run PDMS Under Windows
12 Series 6:1
6 Run PDMS Under Windows
6.1 Spaces in Windows Pathnames
To run macros with spaces in the filenames, the user must enclose the filename in quotes,
without a leading slash. For example:
$m' c: \ Pr ogr amFi l es\ Macr os\ space. mac' ar g1 ar g2
Due to the way in which PDMS parses its command lines, this format is also recommended
for use with filenames containing Asian characters.
6.2 Link to Microsoft Excel
The user can make reports load directly into a Microsoft Excel spreadsheet, as comma-
separated files:
Select Utilities > Standard Reporting > Reports > Modify from the PDMS main
menu bar.
Pick a report template.
Click Open to display the Modify Report Template window.
Select Options > Other Formats from the Modify Report Template window menu bar
to display the Report Format window. From the Report Format window:
Choose the CSV option from the Format drop-down list.
Click OK to return to the Modify Report Template window.
Select the Overwrite radio button.
For the filename enter %PDMSUSER%/fname.csv (the .csv extension is important).
In the System command text box enter.
'cmd/c C:\<excel folder>\excel.exe %PDMSUSER%\fname.csv'.
where C:\<excel folder> is the location of Excel on the users system.
Note: It is necessary to enclose Windows command arguments in double quotation marks
if the argument contains embedded spaces. :\<excel folder>\.
6.3 Windows Parameters
The following setting can be used to improve performance when repositioning windows in
PDMS. These are optional Windows Parameter settings.
12 Series 6:2
Run PDMS Under Windows
Windows XP
Open the Control Panel. Select Display, then select the Appearance tab, click
Effects. On the Effects window, uncheck Show Window Contents While Dragging
and Show shadows under menus.
PDMS Projects
12 Series 7:1
7 PDMS Projects
7.1 Sample Project
PDMS is supplied with a sample project, which can be used in several ways:
It provides the user with examples of the use of PDMS.
It provides the user with sample libraries, catalogues and specifications which enables
the user to use PDMS before they set up their own, and can be used as starting points
when the user does start to create their own.
The sample project is actually two projects in PDMS terms:
MAS (Master) provides data in read-only databases. This data should not be deleted or
changed in any way, or the rest of the sample project will become unusable.
SAM (Sample) contains several MDBs which can be modified, and so they can be used
for training,
7.1.1 Copy Project SAM to User Area
The sample project is loaded automatically when the user installs PDMS. The user should
copy the sample project to their user area and run it as supplied. The project files are held in
two directories: sam000 holds all DESIGN data and catalogue data; sampic holds the
DRAFT picture libraries.
7.1.2 Users and Teams in the Sample Project
Free User
The Free user has username/password SYSTEM/XXXXXX.
General Users
Team Username/password
ADMIN ADMIN/ADMIN
CABLE CABLE/CABLE
CATS CATS/CATS
DEMO DEMO/DEMO
EQUI EQUI/EQUI
HANGER HANGER/HANGER
HVAC HVAC/HVAC
12 Series 7:2
PDMS Projects
General User with Administration Rights
There is a user named ADMIN who is a member of all teams except MASTER. In particular,
ADMIN is a member of the following teams:
CATADMIN
DRAFTADMIN
HSADMIN
ISOADMIN
Membership of these teams gives special administration rights within the corresponding
constructor module.
Each MDB contains databases with appropriate access rights. There are also teams and
users associated with each MDB with appropriate access rights.
7.1.3 MDBs in the Sample Project
The MDBs in the Sample Project section assumes that the user is already familiar with
PDMS databases.
The sample project contains the following MDBs which can be used for demonstration or
training purposes:
NUCLEAR NUCLEAR/NUCLEAR
PIPE PIPE/PIPE
SAMPLE SAMPLE/SAMPLE
STRUC STRUC/STRUC
TEAMA USERA/A
TEAMB USERB/B
TEAMC USERCC
TEAMD USERD/D
TEAME USERE/E
TEAMF USERF/F
TEAMG USERG/G
CATS An MDB for practise using Catalogues and Specifications.
DEMO A demonstration MDB.
EQUI An MDB for the Equipment tutorials.
HANGER An MDB for the Support Design tutorial. This MDB contains
suitable pipework, steelwork and civils as a starting point.
HVAC An MDB for the HVAC Design tutorial. This MDB contains suitable
steelwork and civils as a starting point.
MASTER An MDB containing the master Catalogues and Specifications,
LEXICON, Dictionaries etc.
PDMS Projects
12 Series 7:3
7.1.4 Sample Project and User Projects
The user can add databases from the sample projects SAM and MAS to their own projects
from within PDMS ADMIN, using the Install options on the main menu bar.
Note: These options are only available if the project environment variables for SAM and
MAS have been set.
Note: On DRAFT Libraries: The user must have DRAFT libraries available in their current
project before they can enter the module. The user may find it convenient to install
the libraries supplied by AVEVA in the MAS project (using the Install options), even if
they want to create their own libraries for the project.
NUCLEAR An MDB for the Nuclear Applications.
PIPE An MDB for the Pipework Design and Pipework Spooling tutorials.
SAMPLE An MDB for the Reporting from PDMS and Drawing Production
tutorials. This MDB contains DESIGN data from which reports
and drawings can be produced. The user can also produce
isometrics.
IMPSAMPLE An Imperial version of SAMPLE.
STRUC An MDB for the Structural Design tutorial.
12 Series 7:4
PDMS Projects
Troubleshooting
12 Series 8:1
8 Troubleshooting
Here are some suggestions about solving some problems the user may encounter when
using PDMS under Windows.
8.1 General
8.2 License Manager Errors
Error: The dynamic link library DFORMD.dll could not be found in the
specified path.
Explanation: This is supplied with PDMS. Check the PATH variable has been set.
The PATH setting must include C:\AVEVA\Plant\PDMS12.1.SP2
Error: STOP. The application failed to initialise properly (0xc0000135). Click
on OK to terminate the application.
Explanation: This occurs after a number of other errors. The most likely reason is a
problem with the PATH variable.
Error: When the user starts up lmgrd it says <time>(lmgrd) Can't make
folder C:\FLEXlm, errno: 2 No such file or folder, etc.
Solution: There is no C: drive for the license manager to write to. The System
Administrator or a Power User, has to make a shared disk called C:.
This can be done on a networked or non-networked computer.
Within the Windows Explorers File menu, create a new folder (e.g.
D:\C_drive) and make it current. Select File > Properties and select
the Share tab. Click on Shared As: and then click OK.
Then from the Tools menu select Map Network Drive. Select C: from
the Drive: drop-down list in the displayed form and type:
\ \ host name\ C_dr i ve in the Path box. Then click on OK. (C:)
should now appear in the list of available drives in Explorer
Error: <time>(lmgrd) "<host>": Not a valid server hostname, exiting.
12 Series 8:2
Troubleshooting
8.3 Enter PDMS
Explanation: The hostname used by AVEVA to create the license file does not
correspond with the computer on which the user is running PDMS.
The hostname comes from the variable COMPUTERNAME, which
can be obtained by typing 'set|findstr COMPUTERNAME' in a
Command window. Compare this with the license file contents, and
resubmit if necessary.
Pop-up Mess.: FLEXlm: checkout failed: Cannot connect to license server (-15,
10:10061) WinSock error code.
Explanation: lmgrd has not been started up - see above for details.
Pop-up Mess.: FlexLM: checkout failed: Cannot find license file (-1,73:2) No such file
or folder.
Explanation: lmgrd has not been started up - see above for details.
Pop-up Mess.: FlexLM: checkout failed: Licensed number of users already reached (-
4,132).
Explanation: The permitted number of users specified in the users license file has
been exceeded.
Error: (43,9) Environment Variable not defined for project name.
Explanation: The environment variable for the project has not been set,
e.g. XYZ000.
Error: (43,1) Project <xxx>not available!
Error 7 allocating system database.
Explanation: The environment variable for the project does not point to the correct
location. Either the disk and/or folder do not exist or are not readable.
Error: <username>not found. Invalid username or password.
or
Bad Password
Explanation: The user is trying to enter PDMS without a valid PDMS username
and/or password.
Error: PDMSWK environment variable not set.
Solution: Set PDMSWK to c:\temp or some other folder where PDMS can
create temporary files.
Error: Error 34 opening variables file.
Explanation: The user cannot create a file in the location pointed to by environment
variable PDMSWK.
Troubleshooting
12 Series 8:3
8.4 Problems with Graphics
Error: Project <xxx>is pre version 8.
Explanation: This can happen if the user has transferred the project from UNIX
using FTP in ASCII rather than Binary format.
Error: Cannot pick certain items in DESIGN 3D shaded views.
Solution: There is probably a problem with the display driver for the graphics
board that the user is using. Make sure the user has the version of the
display driver recommended on our supported display drivers Web
page.
Error: Incorrect colours.
Solution: Check the setting of the users Display. The colour resolution should
be set to True Colour or 16.7 million colours.
Error: Graphics speed (for example in 3D views) is poor.
Solution: Check the setting of the users Display.
12 Series 8:4
Troubleshooting
Structure of PDMS on .NET
12 Series 9:1
9 Structure of PDMS on .NET
From AVEVA PDMS 12, the GUI uses the Microsoft .NET Framework environment including
the latest WinForms/Infragistics based user interface components. Using the state-of-the-art
Infragistics technology enables docking forms and toolbars in PDMS and provides a robust
foundation for the future provision of standard application programming interfaces.
This has changed the structure of pdms: this section gives a brief overview and the following
one outlines how to troubleshoot the installation.
9.1 Overview
The Overview section describes the overall structure and components of the PDMS .NET
installation, and the environment necessary to run it. Each PDMS GUI module now consists
of a .NET module, .NET interface and addin assemblies and native dlls plus some other
shared components including 3rd party controls from Infragistics. The .NET components are
private assemblies installed under the root directory %PDMSEXE%.
9.2 PDMSEXE
As before the environment variable %PDMSEXE% is used to locate the executable on
module switch. It is also used to locate attlib.dat (attribute and noun definitions),
message.dat (message definitions), desvir.dat (schema definition) etc. Normally PDMS is
started from pdms.bat which is located in the users %PATH%. Both %PDMSEXE% and
%PATH% should include the install directory.
9.3 GUI Module Structure
Each GUI module is now structured in the same way. The basic structure for each module
looks like this.
12 Series 9:2
Structure of PDMS on .NET
where all components are installed in the %PDMSEXE%. directory (this is different from
11.6 where the .NET wrapper interfaces were installed in separate subdirectories. At 12.0
this has been simplified) So, when running a PDMS GUI module %PDMSEXE% is used to
locate the executable, .NET loading rules are used to load the interface assemblies and
Win32 DLL loading rules are used to load the native components (and other Win32 DLLs on
which pdms.dll depends).
9.3.1 .NET Loading Rules
All the .NET assemblies are Private assemblies and are installed under %PDMSEXE%
(Assembly Base directory) or a subdirectory below. .NET loads private assemblies from the
base directory of the application. If it cant find the private assembly here it uses the
applications configuration file called <module>.exe.config to see whether it contains any
path hints. Path hints are stored in the <probing>element, (this was used at 11.6 but is no
longer necessary at 12.1 since both .NET and native components live in the same
directory).
9.3.2 Native DLLs
Native dlls are loaded using Win32 DLL loading rules. These are:
The directory from which the importing component loaded.
The (application's) current directory (where its run from)
The Windows directory (default: C:\Windows) (we dont install anything here)
The directories that are listed in the PATH environment variable
Therefore normally the %PATH% is used to locate native dlls. This is normally set in
evars.bat located in the installation directory. Having different versions of PDMSEXE in the
%PATH% may cause System.IO.FileLoad exceptions where components are loaded from
different directories.
These rules apply to pdms.dll and all it's dependencies.
9.4 Components
All components are installed in the %PDMSEXE% directory including .NET interfaces and
addins, Infragistics assemblies and native components.
Troubleshooting the .NET Installation
12 Series 10:1
10 Troubleshooting the .NET Installation
10.1 Version Error
10.2 Interface or a Dependency Missing
Error: System.IO.FileLoadException: The located assembly's manifest definition
with name 'Aveva.Pdms.Database' does not match the assembly
reference.
Solution: All .Net assemblies must be the same version (apart from published .NET
interfaces where only major and minor version numbers must be the
same). Open File >Properties >Version >Assembly Version, and check
that all version numbers are the same.
Error: An exception System.IO.FileNotFoundException has occurred in
mon.exe.
Additional information: File or assembly name Aveva.Pdms.Database.
Implementation, or one of its dependencies, was not found.
Solution: All the .NET assemblies are Private assemblies and are installed under
%PDMSEXE% (Assembly Base directory) or a subdirectory below. .NET
loads private assemblies from the base directory of the application. If it
cant find the private assembly here, it uses the applications configuration
file called <module>.exe.config to see whether it contains any path hints.
Path hints are stored in the <probing>element. Normally all assemblies
should be located in the %PDMSEXE% directory
12 Series 10:2
10.3 Interface Incompatibility
10.4 No Add-ins
10.5 Window Layout
10.6 Serialisation
Serialisation is the process used to store the window layout - e.g. history stacks, toolbar
state, docked window position - for the GUI in a .NET environment. For each module this
Error: An exception System.MissingMethodException has occurred in
mon.exe,
or
An exception System.IO.FileNotFoundException has occurred in
mon.exe
Additional information: A procedure imported by 'Aveva.Pdms.Database.
Implementation' could not be loaded
Solution: The interfaces between components are not compatible. Check that
File > Properties > Version Assembly Version on all assemblies is
consistent. Also check that pdms.dll is being loaded from the same
%PDMSEXE% directory as the .NET interface implementation assembly.
This will be determined by the %PATH% environment variable.
Problem: Add-ins missing from module
Solution: Add-ins loaded by each module are defined in the following xml files:
DesignAddins.xml
DraftAddins.xml
IsodraftAddins.xml
SpoolerAddins.xml
If Add-ins are missing, check that these files exist in %PDMSEXE%
Problem: Window layout is not restored e.g. Add-ins position and/or docked state,
Solution: The file <module><version>WindowLayout.xml in the %PDMSUSER%

directory stores this information for the each GUI module. If this file is
deleted then the window layout will return to its default.
12 Series 10:3
data is stored in C:\Documents and Settings\<username>\Local Settings\Application
Data\Aveva\PDMS.
This directory may contain other serialisation data for example saved searches.
Problem: Window layout is not restored correctly for given module.
Solution: Delete serialisation data for given module.
12 Series 10:4
Install AutoDRAFT
12 Series 11:1
11 Install AutoDRAFT
The Installing AutoDRAFT section explains the procedure needed to install and configure
AutoDRAFT.
AutoDRAFT may be run in stand-alone mode or it may be run from DRAFT or ISODRAFT.
The user can use the adraftde, adraftbe and adraftse scripts as described in AutoDRAFT
User Guide. The DRAFT and ISODRAFT applicationware generates interface files for
AutoCAD, which are then used by the scripts.
AutoDRAFT generates interface files for DRAFT, which can be imported using their
applicationware.
11.1 Compatibility
The version of AutoDRAFT released with AVEVA PDMS 12.1.SP2 is compatible with
AutoCAD Releases 2006 and 2007 within the limitations described in more details in
AutoDRAFT User Guide.
11.2 AutoDRAFT Software
AutoDRAFT software consists of three AutoCAD applications that run with AutoCAD
Releases 2006 and 2007, and AVEVA application macros to link these AutoDRAFT
applications with DRAFT or ISODRAFT.
The three AutoCAD applications are:
AutoDRAFT Drawing Editor
The Drawing Editor is used to modify drawings transferred from a DRAFT application.
AutoDRAFT Frame Editor
The Frame Editor is used to transfer AutoCAD drawings into backing sheets or overlay
sheets in DRAFT.
AutoDRAFT Symbol Editor
The Symbol Editor is used to convert AutoCAD graphics into symbol templates within
DRAFT symbol libraries.
11.3 Configure AutoDRAFT with AutoCAD
The AutoDRAFT software is installed under the PDMS executable folder:
12 Series 11:2
Install AutoDRAFT
The autodraftACAD folder contains .bat files, AUTODRAFT scripts, AutoLISP programs,
AutoCAD customisation files and an AutoCAD linestyle file.
The autodraftfonts folder contains AutoCAD font files. All of these are needed to run
AutoDRAFT programs in AutoCAD.
Note: The AutoDRAFT software will operate properly only if AutoCAD can be run using the
acad command. AutoDRAFT may not work if the AutoCAD executable acad has
been renamed, or if the acad command runs a user-supplied file which itself runs
AutoCAD.
11.4 Install and Configure AutoCAD
In order to use AutoDRAFT, AutoCAD must be installed and configured for each computer
where AutoDRAFT will be used. The AutoCAD Installation and Performance Guide supplied
with AutoCAD describes how to do this.
AutoCAD should be configured to locate the extra menus and fonts used in AutoDRAFT.
The method depends on the AutoCAD version, typically:
Add the appropriate paths to the autodraftACAD and autodraftfonts directories to the
> Tools > Options > Support File Search Path field.
The AutoDRAFT environment variable setting commands applicable to each release of
AutoCAD are listed in the following sections. The environment variables are set within the
supplied pdms.bat file. These should be edited to suit the installed version of AutoCAD.
11.4.1 AutoCAD R2006
set PDMS_ACAD=2006
set PDMS_ACAD_PATH=pathname for AutoCAD R2006 files
e.g. C:\Program Files\AutoCAD 2006;C:\Program Files\Common Files\Autodesk Shared
set ACAD_VERSION=%PDMS_ACAD%
set path=location of autodraftACAD directory;%PDMS_ACAD_PATH%; %path%
Before running AutoDRAFT, the user needs to run AutoCAD R2006 and add the following
as file paths:
Location of autodraftACAD directory
Location of autodraftfonts directory
11.4.2 AutoCAD R2007
set PDMS_ACAD=2007
Install AutoDRAFT
12 Series 11:3
set PDMS_ACAD_PATH=pathname for AutoCAD R2007 files
e.g. C:\Program Files\AutoCAD 2007;C:\Program Files\Common Files\Autodesk Shared
set ACAD_VERSION=%PDMS_ACAD%
set path=location of autodraftACAD directory;%PDMS_ACAD_PATH%; %path%
Before running AutoDRAFT, the user needs to run AutoCAD R2007 and add the following
as file paths:
Location of autodraftACAD directory
Location of autodraftfonts directory
11.5 AutoCAD
Before using the Drawing Editor make sure that AutoCAD has been correctly installed and
configured by entering the command acad at the operating system command prompt.
11.6 Application Macros for use with DRAFT
The applicationware provides the additional menus and forms required to run the
AutoDRAFT editors in AutoCAD directly from DRAFT and ISODRAFT.
12 Series 11:4
Install AutoDRAFT
Configure Area Based ADP
12 Series 12:1
12 Configure Area Based ADP
Before starting the configuration process make sure the project has been set up with a
Drafting database (PADD) for the administrative elements of ABA and at least one Drafting
database (PADD) for the user elements. Make sure that access to the Drafting
administration database is controlled via the Drafting administration team.
1. Enter the Drafting module using the MDB for ABA administration and be sure to enter
via Macro files, NOT Binaries.
2. Once in the Drafting module select the Draft > Administration from the Draft menu
and then Draft > Area Based ADP.
3. Select the Settings > Area Based ADP Defaults from the menu.
4. When the defaults form appears it shows the settings in the supplied DRA-ABA-
DEFAULTS file. This is the hierarchy required for running the ABA application. For a
detailed explanation of the elements defined in the Defaults file, refer to the Draft
Administrator Application User Guide.
The fields in the defaults file are as follows:
12 Series 12:2
Defaults file Specifies the location directory and name of the defaults file
used to set or store the ABA default settings.
Library The top-level LIBY element which holds all the required
ABA administrative elements.
Templates Templates are stored below a DRTMLB, which is a library
used to hold ABA drawing templates (DRTMPL). If more
that one Drawing template library is required, this should be
set to a LIBY element and all DRTMPL placed below it.
Areas A LIBY for DLLBs which are used as drawlist libraries which
hold all the IDLI (ID List) elements that store the physical
limit co-ordinates for each of the ABA geographical areas.
Classifications a DLLB used to contain all the IDLI elements for each ABA
classification. A Classification is a set of database elements
that have something in common e.g. Equipment elements
with a PURPose of PUMP.
Keyplans A SHLB is a sheet library used to hold all the OVER
(overlay) elements for the keyplans.
Symbols A SYLB is a symbol library that contains all ABA symbols
e.g. north arrows.
Labelling A TRLB is a tag-rule library that contains all the ABA tag
rules.
Tasks A TASKLB is a task library, which holds all the ABA tasks
e.g. plot - send drawing to a plot file.
Create Hierarchy This option is used to automatically create the
administrative hierarchy specified in the Defaults form.
To use this functionality:
Modify the names to the desired settings.
If the required structure exists, Create Hierarchy will show
However, if it does not exist, Create Hierarchy will show .
Note: This only detects the existence of the LIBY, but not
the elements contained within it.
To create the hierarchy specified in the defaults form, click
and select a db from the Create Aba Hierarchy form
displayed.
The previously mentioned process will also create some
initial SYMBol elements. The icon will then turn to , which
indicates that the structure is OK.
12 Series 12:3
The default settings for the Batch User can be set by clicking Batch User to display the
Batch Username and Password form.
The application is supplied with a series of example data files that can be used to make a
test run of ABA using the standard supplied AVEVA sample project SAM.
The administrator also has the facility to easily load these supplied example data files.
They are accessible by clicking Input File which displays the File Browser form.
Logfile Location Gives the directory path where the log files for drawings
created using ABA are to be stored.
Batchfile Location Gives the directory path where the batchfiles created by
ABA are to be stored.
User Name Specifies name of user that will enter the Base Product.
Password Specifies the password of the user.
12 Series 12:4
Any data files must be loaded in the same order as shown in the Files list, since some
elements rely upon the existence of other elements. To load a file, select the one the
user wants to load from the Files list and click Apply. Repeat this until all of the
necessary library files are loaded and click Dismiss.
Note: It is not possible to mix Metric and Imperial libraries since they utilise the same
element names. If the user wants to mix them the user will need to modify the source
data files.
5. In the SAM project load each of the following files in order by selecting them in the
Files list and then click Apply.
6. For an Imperial project, load the substitute files marked IMPERIAL
sam_area-METRIC.datal builds a series of example limit areas
sam_discipline.datal builds a series of example disciplines
sam_keyplan-METRIC builds the keyplans used by the relevant tasks
sam_tagrule.datal builds a series of example tagrules
sam_template-METRIC.datal builds a series of sample templates
12 Series 12:5
Once these data files have been loaded, the user can run ABA and produce some drawings.
ABA is now configured. Drafting administrators can now create the required administrative
elements (areas, classifications, tasks, labels, and drawing templates) for use by DRAFT
users.
Refer to the ABA Administrator and User Guides for further information.
12 Series 12:6
MDS Installed Configuration
12 Series 13:1
13 MDS Installed Configuration
MDS is installed directly into the main installation directory instead of being installed in a
separate folder
Note: This is also the case for ABA
As a result of this change MDS is now run using the standard set of PDMS shortcuts that
are installed for the main product. This means that if MDS has been installed then it will be
available for a project design or outfitting session providing that the project has been set up
for MDS use (as described in the administration guide) and there is a valid MDS license
available to the user.
13.1 Manual Configuration of the Product and Product
Environment Variables
All MDS environment variables are set in the evars.bat file in the main installation directory.
These are defined initially during the MDS installation process however.
if the installer wants to create their own environment variable files
OR,
if at the time of install, the following is true,
any modifications are made to the product internal structure/naming
(This product has the same internal structure/naming as the base product, eg,)
( \product\pmllib has same function as \base\pmllib )
then the evars need manual (re-)definition and must be modified as follows.
13.1.1 Set Environment Variables
Environment variables modifications are made to the base product's files evars.bat from
pdms.bat.
Some of these environment variables can be "searchpaths".
AVEVA "searchpath" variables are modified from the initial setting %EnvVar%, using a
blank* as the separator and usually PREfixing the new value, in the form.
Note: *If the installation of PDMS has been made into a directory with spaces in the path
name i.e. c:\aveva plant then environment variable settings need to be modified to
deal with space delimiters. This is out of scope for this document but more detailed
information regarding this topic can be found in the PDMS install guide.
SET EnvVar={newEnvVarValue}%EnvVar2% %EnvVar%
12 Series 13:2
This will force items in newEnvVarValue to be used in preference to those in %EnvVar2% or
%EnvVar%
Searchpath variables need only be changed if the administrator wishes to include additional
PML code paths to their installation or otherwise include alternative locations for known files.
13.1.2 Modification of Evars.bat for MDS
The following environment variables are set up for MDS in the standard product evars.bat
file:
If the user modifies the pmllib configuration after the install, the first operation when first
running the product is to select the Command window and run the command,
pml r ehash al l
Note: Write access is required to the PMLLIB folders to enable the several pml.indx files to
be updated.
13.1.3 Environment Variables for Projects
Except for the standard sample projects supplied with the products, the install cannot create
the environment variables for users projects.
When the user creates projects they must set these adding into one of,
the user's Environment variables set (not recommended)
as instructions in one of the startup batfiles
The standard installation of MDS installs all of the sample MDS projects into the same folder
as the standard projects folder. Each of the sample projects (detailed in Projects) contains
its own environment variable batch file (i.e. evarsMDS.bat) that is called from the standard
evars.bat file.
13.1.4 For Projects Used with MDS
Note: MDS defines two additional environment variables, 'mdsdflts' & 'mdsinfo', for the
AVEVA project folders \MDS\mdsdflts and \MDS\mdsinfo used by MDS.
All other projects, which will be required to use the MDS applications, will need to have the
two extra folders created, and the relevant environment variables set to point to these two
new directories in the relevant evars batch file, e.g.
For a project called 'abc' create the two required folders by copying the /MDS/ mdsdflts
and /MDS/mdsinfo folders to where the 'abc' project folders are located, and rename them
accordingly, i.e. rename the copied folders mdsdflts and mdsinfo to abcdflts and abcinfo
respectively.
mdsplots Folder containing the plot files of MDS standard support types.
Licadmdsexe sets the executable location for the Licad software interface if used.
Pslmdsexe sets the executable location for the PS designer software interface if
used.
Cplmdsexe sets the executable location for the Witchhanger software interface
if used.
12 Series 13:3
Project Variables for MDS
and similar project environment variables for any other projects.
13.2 Projects
13.2.1 Projects Released with this Product
There are five standard projects released with the Multi Discipline Supports product, these
are:
mdsreports destination of the MDS report files.
Mds000 project MDS, 000 files
Mdsmac project MDS, mac files
Mdspic project MDS, pic files
Mdsiso project MDS, iso files
Mdsdflts project MDS, dflts files
Mdsinfo project MDS, info files
CPL Carpenter and Paterson Catalogue Project
LIS LISEGA Catalogue Project
MDS Multi Discipline Supports project containing the catalogue
component, catalogue application defaults and the design
databases for use with the MDS application
MDU Multi Discipline Supports project containing the catalogue
database for the User defined MDS Ancillaries available in 12
PSL Pipe Supports Ltd Catalogue Project
12 Series 13:4

PDMS and Associated Products Installation Guide

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

PDMS and Associated Products Installation Guide

Încărcat de

Drepturi de autor:

Formate disponibile

PDMS & Associated Products

Solution: The file <module><version>WindowLayout.xml in the %PDMSUSER%

S-ar putea să vă placă și