Download - PDMS -Installation Guide

PDMS & Associated Products

Installation Guide

Disclaimer1.1 AVEVA does not warrant that the use of the AVEVA software will be uninterrupted, error-free or free fromviruses.

1.2 AVEVA shall not be liable for: loss of profits; loss of business; depletion of goodwill and/or similar losses; loss ofanticipated savings; loss of goods; loss of contract; loss of use; loss or corruption of data or information; anyspecial, indirect, consequential or pure economic loss, costs, damages, charges or expenses which may besuffered by the user, including any loss suffered by the user resulting from the inaccuracy or invalidity of any datacreated by the AVEVA software, irrespective of whether such losses are suffered directly or indirectly, or arise incontract, tort (including negligence) or otherwise.

1.3 AVEVA's total liability in contract, tort (including negligence), or otherwise, arising in connection with theperformance of the AVEVA software shall be limited to 100% of the licence fees paid in the year in which the user'sclaim 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 underwhich the AVEVA software was purchased, the clauses in the software licence shall take precedence.

CopyrightCopyright 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 suppliedwith 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 documentis commercially sensitive, and shall not be copied, reproduced, stored in a retrieval system, or transmitted withoutthe prior written permission of AVEVA Solutions Limited. Where such permission is granted, it expressly requiresthat this copyright notice, and the above disclaimer, is prominently displayed at the beginning of every copy that ismade.

The manual and associated documentation may not be adapted, reproduced, or copied, in any material orelectronic form, without the prior written permission of AVEVA Solutions Limited. The user may not reverseengineer, decompile, copy, or adapt the software. Neither the whole, nor part of the software described in thispublication may be incorporated into any third-party software, product, machine, or system without the prior writtenpermission of AVEVA Solutions Limited, save as permitted by law. Any such unauthorised action is strictlyprohibited, 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 termsand 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 notbe liable for any breach or infringement of a third party's intellectual property rights where such breach results froma user's modification of the AVEVA software or associated documentation.

AVEVA Solutions Limited, High Cross, Madingley Road, Cambridge, CB3 0HB, United Kingdom.

TrademarkAVEVA and Tribon are registered trademarks of AVEVA Solutions Limited or its subsidiaries. Unauthorised use ofthe AVEVA or Tribon trademarks is strictly forbidden.

AVEVA AVEVA Solutions Limited or itssubsidia

The cop product or software, its name orlogo be

AVEVA Solutions Limited

product/software names are trademarks or registered trademarks of ries, registered in the UK, Europe and other countries (worldwide).

yright, trademark rights, or other intellectual property rights in any other longs to its respective owner.

Revision Sheet

Date Version Comments / Remarks

September 2011 12.1.1 Issued

PDMS & Associated Products Installation Guide

Installation Guide

Contents Page


PDMS & Associated ProductsIntroduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1Assumptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1Guide Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1Associated Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:2

Hardware and Software Requirements . . . . . . . . . . . . . . . . . . . . . . . 2:1AVEVA PDMS 12.1 Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1Flexman License File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1.NET Framework Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1

Enable Microsoft Excel Interop Assembly. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1Font Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:4

AVEVA PDMS and Associated Products Installation . . . . . . . . . . . 3:1Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:12Uninstall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:13Modifying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:13Repairing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:14Healing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:15Modified New and Removed Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:15User Modified Appware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:15

Models, Sample Data and Example Projects. . . . . . . . . . . . . . . . . . . . . . . . . . . 3:15Changing Default File Replacement Behaviour . . . . . . . . . . . . . . . . . . . . . . . . 3:16

12 Seriesi


Post Deployed .bat files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:16Pre-Deployed .bat files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:16.bat file Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:17

Network (Admin) Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:17Create an Administrative Installation Point. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:17

Issues with Administrative Installation Points . . . . . . . . . . . . . . . . . . . . . . . . . 3:19.NET Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:19Signing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:20Using Files within the Source Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:20Network Throughput. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:21Advantages of a Network Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:21

Run PDMS and Associated Products from Network Locations. . . . . . . . . . . . 3:21Administrative Installation Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:22Patch Administrative Installations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:22

Copy a Local Deployment to a File Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:22Feature Id Reference List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:23Feature Tree Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:23

SelectionTree Selection & De-selection Rules . . . . . . . . . . . . . . . . . . . . . . . . . 3:24Selecting Features from the Command Line. . . . . . . . . . . . . . . . . . . . . . . . . . . 3:24Command Line Definable Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:25Sample Command Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:25

Set Up the Windows Environment. . . . . . . . . . . . . . . . . . . . . . . . . . . 4:1Windows Control Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:1Graphics Card Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:1Set the License File Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:2PDMS Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:2Run PDMS from a Command Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:4Customise PDMS Start-Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:4Create User Batch File to Run PDMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:5

Run PDMS in Batch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:5Plot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:6

Language Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:1Setting PDMS Default Text Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:2Prepare PDMS For Legacy Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:3

12 Seriesii


Run PDMS Under Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:1Spaces in Windows Pathnames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:1Link to Microsoft Excel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:1Windows Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:1

PDMS Projects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:1Sample Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:1Copy Project SAM to User Area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:1Users and Teams in the Sample Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:1MDBs in the Sample Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:2Sample Project and User Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:3

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:1General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:1License Manager Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:1Enter PDMS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:2Problems with Graphics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:3

Structure of PDMS on .NET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:1Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:1PDMSEXE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:1GUI Module Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:1.NET Loading Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:2Native DLLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:2

Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:2

Troubleshooting the .NET Installation . . . . . . . . . . . . . . . . . . . . . . 10:1Version Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:1Interface or a Dependency Missing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:1Interface Incompatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:2No Add-ins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:2Window Layout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:2Serialisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:2

Install AutoDRAFT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:1Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:1AutoDRAFT Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:1

12 Seriesiii


Configure AutoDRAFT with AutoCAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:1Install and Configure AutoCAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:2AutoCAD R2006. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:2AutoCAD R2007. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:2

AutoCAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:3Application Macros for use with DRAFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:3

Configure Area Based ADP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:1

MDS Installed Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:1Manual Configuration of the Product and Product Environment Variables . . 13:1Set Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:1Modification of Evars.bat for MDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:2Environment Variables for Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:2For Projects Used with MDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:2

Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:3Projects Released with this Product. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:3

12 Seriesiv

PDMS & Associated Products Installation GuideIntroduction

1 Introduction

The PDMS & Associated Products Installation Guide explains how to install and set upPDMS & Associated Products on a workstation running Microsoft Windows. For completelyup-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 givehints on ways of setting up and running PDMS on different computers in order to achievethe most efficient performance.

1.1 AssumptionsThe PDMS & Associated Products Installation Guide assumes that:

• Users are familiar with the concepts of folder/file hierarchies for storing data on disksand with basic Windows terminology and commands. If not, the user can also refer tothe operating system documentation while carrying out the installation.

• Users have already gained access to the PDMS installation files via a disk, from theAVEVA Web site, or by some other route.

• Users have Local Administrator rights.

1.2 Guide StructureThe 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 operatingsystem before running PDMS.

Language Support describes how to set up the Windows Environment touse PDMS with different Language options.

Run PDMS Under Windows gives some advice on using PDMS in a Windowsenvironment.

PDMS Projects describes the sample project that is supplied as partof PDMS, and how the user can set up projects.

Troubleshooting describes solutions for some of the errors that couldbe encountered when running PDMS.

12 Series1:1

http://www.aveva.com/products/support/support.html

http://www.aveva.com/products/support/support.html


1.3 Associated ProductsThe following are available as additional installation options when installing PDMS.

• Global, Global WCF Client and Global Server - for synchronisation of projects betweenworld-wide sites

• Schematic 3D Integrator - Integration application to make sure there is dataconsistency between P&ID and the 3D model

• Area Based ADP - Automates the production of volumetric drawings using specifiedtemplates, 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 usercan consider installing these at the same time. Those closely associated with PDMS includethe following DESIGN products:

• AVEVA Global Server - For synchronisation of PDMS products between world widesites

• AVEVA SQL Direct - Access the DESIGN Database directly from within softwareproducts that support Microsoft Universal Data Access interfaces

• AVEVA ImPlant-I - Translator for exporting Intergraph’s 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 inputto 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 andconfigured in a Microsoft .NET environment.

Troubleshooting the .NET Installation

describes solutions to some of the .NET relatedissues that might be encountered.

Install AutoDRAFT explains the procedure needed to install and configureAutoDRAFT.

Configure Area Based ADP describes how to configure Area Based ADP.

MDS Installed Configuration describes how to configure folder structure andnaming configurations.

Pipe Stress Interface Configuration

describes which standard settings need modifying tocomplete the installed version.

12 Series1:2


For details of the installation of these ‘add-on’ products, refer to the relevant installationguide. If they are required, it may be advisable to read these before installing PDMS.

12 Series1:3


12 Series1:4

PDMS & Associated Products Installation GuideHardware and Software Requirements

2 Hardware and Software Requirements

The user should refer to the Systems Requirements guide and make sure that the systemand network meets all of the requirements before attempting to install the software.

2.1 AVEVA PDMS 12.1 Software InstallationAVEVA PDMS software is supplied on a disk.

The disk contains• Release Notes• AVEVA Plant Suite 12.1 Help• an installable version of Microsoft’s .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 FileTo operate, AVEVA software must be able to access the correct Flexman license file, whichshould be installed on either the Server, on the users workstation, or on a networkedworkstation. Refer to the Flexman Installation and Configuration Guide. News and updateinformation 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 usethe items that are licensed to them. The user will get an on-screen notification towarn them when the license is due for renewal.

2.1.2 .NET Framework InstallationThe graphical user interface requires that Microsoft’s .NET Framework be installed. The.NET Framework is supplied on the disk and if it has not been previously installed theinstallation will install it automatically when the installation is run from the disk.

2.2 Enable Microsoft Excel Interop AssemblySeveral of AVEVA applications use a facility in the AVEVA GridControl to import an Excelfile, for example, Equipment Import, Cable Import, and Diagrams. To make sure that theExcel import facility will work the user must make sure that the Microsoft Excel InteropAssembly is enabled on each machine where it will be used.

12 Series2:1


Open the Add or Remove Programs utility from the Control Panel, and select the versionof Microsoft Office being used, the one shown here is Microsoft Office ProfessionalEdition 2003.

Click Change to display the Maintenance Mode Options.

12 Series2:2


Make sure Add or Remove Features is checked and click Next:

Check the option for Choose advanced customisation of applications, and click Next.

12 Series2:3


Under the Microsoft Office Excel application make sure that .NET ProgrammabilitySupport is enabled. If .NET Programmability Support is not enabled then select theoption Run from My Computer, and click Update.

2.3 Font SizeDuring the installation of Windows 7, the install process decides what it believes to be thebest setting for the font size and sets this as the Default. AVEVA only supports the settingSmaller and suggests that the user changes their setup to make Smaller the defaultsetting.

To change the default setting, right-click on the desktop.

Select Personalize from the menu to display the control panel.

12 Series2:4


Click Display to display the screen for setting the Font size.

12 Series2:5


Select Smaller and click Apply. The user will have to restart the system to save thesettings.

12 Series2:6

PDMS & Associated Products Installation GuideAVEVA PDMS and Associated Products Installation

3 AVEVA PDMS and Associated Products Installation

The AVEVA PDMS and Associated Products Installation is supplied on a disk in aninstallation called Plant. The disk contains an installable version of Microsoft’s .NETFramework. Also on the disk is a folder containing the Installation instructions and userdocumentation, and it is recommended that the user carefully read all of the Installationinstructions before installing the software.

It is recommended that the default settings are used for folder paths etc., unless the userhas good reasons for doing otherwise.

Important: AVEVA does not recommend the use of spaces in installation folder pathnames. However, the system will work, with some limitations. Refer tosection 1.3 of the User Bulletin for further information.

Using the disk to install AVEVA PDMS and Associated products, insert the disk and on theWelcome screen click Click for contents.

Alternatively the user can click the setup.exe file to install the software manually. Using thesetup.exe option bypasses the first three windows and displays the Plant Setup Wizardwindow.

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 ofits primary installation (like the .NET framework), before running its primary (MSI)installation. Users should never see missing dependency errors if installations are startedfrom the Setup.exe program.

Setup.exe also tells the primary installation to target the C:\ drive/volume, which is thepreferred default in most manual installations. However, if a more customised installation isrequired 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 Series3:1


A screen showing the available products is displayed.

Click AVEVA PDMS to display the Release Documents screen.

12 Series3:2


Click INSTALL to display the AVEVA Plant Setup Wizard.

12 Series3:3


The Plant Setup Wizard activates at this point and guides the user through the installation ofthe 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 calledthe SelectionTree. Each feature is depicted as a box with a description of the featuredisplayed in the right hand pane. The boxes representing each feature are depicted asfollows:

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 Series3:4

http://msdn.microsoft.com/en-us/library/aa371604(VS.85).aspx


Clicking Reset will de-select all currently selected features.

If the Feature is not Unavailable ( ), a Location Path showing where the program is tobe installed may be displayed, if so Browse becomes active.

If a Location Path is not displayed and Browse is inactive when a specific Feature ishighlighted and scheduled to be installed, then that Feature contains something whichembeds itself inside another program (whose path is separately configurable). ClickingBrowse, when active, displays the Change Destination Folder window which allows theuser to select a different folder name and location path.

Will be installed on local hard drive Selecting this option will install the featurelocally.

Entire feature will be installed on local hard drive

Selecting this option will install the feature andall its sub-features locally.

Entire feature will be unavailable Selecting this option prevents the currentfeature and all its sub-features from installing.

12 Series3:5


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. Thefollowing list is hoped to clarify this:

Feature Configurable Default Path

PDMS Yes C:\AVEVA\Plant\PDMS12.1.1\

PDMS Models Yes C:\AVEVA\Plant\Project12.1.1\

Global Client No C:\AVEVA\Plant\PDMS12.1.1\

Schematic 3D Integrator No C:\AVEVA\Plant\PDMS12.1.1\

Area Based ADP No C:\AVEVA\Plant\PDMS12.1.1\

Multi-Discipline Supports No C:\AVEVA\Plant\PDMS12.1.1\

ExPlant-A No C:\AVEVA\Plant\PDMS12.1.1\

ExPlant-I No C:\AVEVA\Plant\PDMS12.1.1\

Plant Suite Help No C:\AVEVA\Plant\PDMS12.1.1\Documentation\

12 Series3:6


Changing the Folder Path of the Feature "AVEVA Plant Suite" will affect all applicationsresiding in subfolders. For example:

if "AVEVA Plant Suite" = J:\Test\

Then

"PDMS" = J:\Test\PDMS12.1.1\

"PDMS Models" = J:\Test\Project12.1.1\

…

"Manuals" = J:\Test\PDMS12.1.1\Documentation\

However, if any of the other folders were to be directly changed, they would remain in thatstate 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 SpaceRequirement screen. Highlighted volumes indicates that there is not enough disk spaceavailable for the selected features. The user can remove some of the files from thehighlighted volumes, install fewer features or select a different destination volume. Click OKto return to the Custom Setup form.

Click Back to step back a stage, Cancel to terminate the Setup Wizard or Next to displaythe existing projects and Infrastructures Configuration screen and continue the installation.

12 Series3:7


The Configuration screen allows the user with existing projects and infrastructures tocustomise the installation.

The Projects Folder path can only be changed if the user has chosen to install the Plant orthe MDS models. To change the path click Browse to display the Change DestinationFolder 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 andthe Desktop Shortcuts options. Both options are dependant on the bat files being installed.

Unchecking the StartMenu Shortcuts checkbox deactivates the Desktop Shortcutsoption. The option is dependant on the StartMenu Shortcuts being installed.

Click Back to step back a stage, Cancel to terminate the Setup Wizard or Next to displaythe folder path Configuration screen.

Clicking Browse displays the Change Destination Folder window which allows the user toselect a different folder name and location path.

Click Back to step back a stage, Cancel to terminate the Setup Wizard or Next to displaythe Ready to Install AVEVA Plant screen.

12 Series3:8


Click Back to step back a stage, Cancel to terminate the Setup Wizard or Install to displaythe Installing AVEVA Plant screen.

12 Series3:9


The Installing AVEVA Plant screen displays a taskbar showing the status of theinstallation.

During the installation process the screen displays Cancel, which can be clicked to stop theinstallation. When selected a window is displayed asking for confirmation that the AVEVAPlant installation is to be cancelled.

Selecting Yes displays a screen showing the AVEVA Plant Setup Wizard was interrupted.

12 Series3:10


Click Finish to exit the screen and installation.

Selecting No on the confirm screen returns the user back to the Installing AVEVA Plantscreen and continues the installation.

12 Series3:11


When the installation has been completed, click Finish to exit the Setup Wizard.

3.1 Log FileDuring the installation, setup.exe creates a log file of the installation in the users TEMPdirectory named Plant12.11.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 Series3:12


3.2 UninstallComplete 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 theREMOVE property or by changing the installation state via the Add/Remove Programsapplet.

Note: Uninstalling the PDMS and associated Products installation will not uninstallMicrosoft's .NET Framework or downgrade the Windows Installer Service. The .NETFramework must be removed separately if required.

3.3 ModifyingThere 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

the subsequent window.

Once the Change option is selected the Custom Setup window is displayed allowing theuser to change which features are installed.

12 Series3:13

http://msdn.microsoft.com/en-us/library/aa370854.aspx



The Change option can not be used to change the Location Path. If the user wants tochange the Location Path, the current installation must be removed and then re-installedusing the new Location Path.

Note: Never move files by other means, as this may trigger healing, however Copying filesto other locations will not cause problems.

3.4 RepairingIf any programs stop working, or the installation has knowingly been damaged, then Repairmay 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

the subsequent window.

Repairing installations causes them to heal themselves. For more information refer toHealing.

12 Series3:14



3.5 HealingMSI technology has inbuilt self repairing mechanisms. As such it is generally unwise to alterfile and folder names, shortcuts or registry manually, as this may trigger the MSI whichdeployed 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 tominimise the ability of the MSI to heal itself in such cases.

Sample Data, Models, example projects and shortcuts, should not trigger healing if they aredeleted or altered. The consequence of making shortcuts editable/deletable is that MSIAdvertising will not function.

3.6 Modified New and Removed FilesIrrespective 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 bya repair or an installation depend upon the initial state of the computer.

3.6.1 User Modified AppwareIn MSI/Deployment terms, Modified appware files constitute un-versioned, language neutralfiles, whose "Created Date" and "Modified Date" differ. However, if appware files have beenmoved or handled in certain ways, then it is possible that the "Created Date" and "ModifiedDate" will not differ, in which case the file replacement behaviour of the installation will bedifferent.

In the case where an appware files "Created Date" and "Modified Date" is different, no MSIwill 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 notdiffer, the appware file with the newest date will prevail (by default). This scenario is mostlikely 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-sidedeployable, 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 meanthat AVEVA installations cannot be used to deploy appware, and those clients must maketheir own code merges.

3.7 Models, Sample Data and Example ProjectsIt 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 Series3:15




• 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 completelyremoving an installations ability to heal its Models, Samples and Examples. If a new copy isrequired, the installation must be completely removed, and then reinstalled. Repairing willnot restore Models, Samples or Examples.

Uninstalls, are achieved by deleting the root folders where the Models, Samples andExamples where deployed to. It is important to remove them if they are to be retained.

3.8 Changing Default File Replacement BehaviourIt is possible to alter default file replacement behaviour in circumstances where an MSIinstallation or Patch is launched from a command line. This is achieved with theREINSTALLMODE property or the /f command line switch. Otherwise default filereplacement rules will apply.

Default file replacement rules should suit most users.

It is desirable to change file replacement behaviour, in situations where the Date/Timestamps of files might not support the required replacement of files.

3.8.1 Post Deployed .bat filesThe .bat files which AVEVA installations deploy and edit are regarded as necessary for theapplications 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 filesIt is feasible to replace .bat files before deployment, in the case where deployments arestaged from Admin Installations. However the details and issues concerning AdminInstallations are beyond the scope of this manual.

It is also possible to add additional files to an MSI installation, but an MSI table editor ofsome sort would be required. This is not a trivial option, and may well require the services ofa professional re-packager. However it can be accomplished without compromising aninstallations ability to be patched.

12 Series3:16





3.8.3 .bat file ShortcutsAll the shortcuts pointing to the .bat files are of the non-advertised or normal type. As suchthey can be deleted and edited, without triggering healing.

3.9 Network (Admin) InstallationsAdministrative Installation Mode is a type of .msi installation, which only causes anuncompressed 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 theregenerated .msi file, rather than stored in external .cab files or in .cab files embeddedwithin 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 thisprocess.

3.9.1 Create an Administrative Installation PointTo create an admin installation from an installation, start the installation from the CommandLine as follows to display the AVEVA Plant Administration Point Setup screen:

MSIEXEC /A [Path to MSI File]

12 Series3:17




Click Next to display the AVEVA Plant Administration Point Distribution screen.

12 Series3:18


Enter the location where the Admin Installation is to be created. Clicking Browse displays awindow 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 anetwork location. There are several ways to “Trust” such locations, but Trusted it must be, ifprograms are to run across a network.

.NET security can cause issues when running PDMS across the network where the add-inassemblies reside on a different machine to the .NET runtime. The default security level forthe local intranet is not set to Full Trust, which means that programs may not be able toaccess resources on the local machine. To overcome this, the intranet security may be setto Full Trust, though this means that any .NET assembly may run. Alternatively, Full Trustmay be given to a specified group of strongly named assemblies.

12 Series3:19


Full Trust is configured using the code access security policy tool caspol. First of all theassemblies must be strongly named. Then caspol is run on each client machine to add allthe assemblies on a given server directory to a group and give Full Trust to this group asfollows:

To trust all assemblies in a given folder:caspol -m -ag LocalIntranet_Zone -url \\<ServerName>\<FolderName>\* FullTrust -n "<Name>" -d "<Description>"

OR to trust all assemblies with the same strong name:

CasPol.exe -m -ag LocalIntranet_Zone -strong –file \\<ServerName>\<FolderName>\<assemblyName> -noname -noversion FullTrust -n "Aveva" -d "Full trust for Aveva products"

where <ServerName> is the UNC (Uniform Naming Convention)

The format of a UNC path is:\\<servername>\<sharename>\<directory>

where:

caspol can be found in c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\ or is part ofthe .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 SigningNewer windows operating systems have code signing embedded into their security. Assuch, AVEVA have begun signing .msi files and .cab files for installations which are notrestricted to Windows XP or older operating systems.

Unfortunately, the Administrative Installation process recreates and/or alters the source .msifile and removes .cab files altogether, thus removing any file signatures. Changes to signedfile always invalidates its signature.

In this release AVEVA have signed all dll's and exe's that are supplied. However in order tocater 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 digitalsignature. By default the installation is set to deploy the .exe.config to disable the digitalsignature validation. To enable digital signature validation the command line optionCERTIFICATECHECK=1 should be set.

3.10.3 Using Files within the Source InstallationMSI databases can be authored to allow Features to be installed in the "Will be installed torun from network" state. AVEVA Installations do not currently support this mode; however itmay 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 Series3:20

http://www.microsoft.com/downloads/details.aspx?FamilyID=fe6f2099-b7b4-4f47-a244-c96d69c35dec&displaylang=en


edits do occur on the target computer, and they address the programs which reside insidethe source installation.

3.10.4 Network ThroughputAdmin installations can be very suitable for staging large deployments, becauseuncompressed installations usually travel better over networks because they are even morefragmented. The overall size is typically much larger; however this is still tends to be easieron Packet Switching Networks.

3.10.5 Advantages of a Network InstallationOnce computers address files across a network, it becomes crucial that the files areaccessible 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 LocationsRunning 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 areimpractical, given the many ways in which AVEVA programs can interact with each otherand with Project data. Not to mention other possible permutations.

So the following information is deliberately general and lacking in detail and it is aimed atassisting a highly skilled readership.

12 Series3:21


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 PointsThe Files and Folders extracted to an "Administrative Installation Point" are laid out in afundamentally identical way to a local installation. Additionally, files which are normallydeployed to operating system folders will also be visible, but will play no functional partunless deployed locally.

Some Configuration files will be incomplete, or have incorrect data in them, as they are notedited until they are deployed (Locally). These files may require manual editing and concernwhich Modules, Addins, Addons and "User Interface Modifications" are loaded.

3.11.2 Patch Administrative InstallationsA slightly different Patch is required for an administrative installation than for a localinstallation, and standard AVEVA patches target local installations. If such a Patch is appliedto an Administrative Installation Point, the patch will succeed. However, any localinstallations which have previously been deployed from it will cease to recognise it as theirsource installation. So as long as local deployments have not occurred, an Administrativeinstallation is patchable with an AVEVA patch. Similarly, if programs within the installationare addressed by a clients own means, then the Administrative Installation can be patchedat 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 anadministrative image, the patch must be extracted and the appropriated command lineused. The appropriate command switch is /C which extracts the contents to the currentfolder.

Note: Patches cannot be rolled back from Administrative Installation Points. A copy mustbe made before the patch is applied, in order to rollback.

Note: Patches cause changes to the .msi file, which invalidates any security certificatesapplied to the installation.

3.12 Copy a Local Deployment to a File ServerInstalling 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 forthe programs will fail to install. This is because file editing is performed with the localSystem Accounts credentials, which are not normally recognised by othercomputers.

12 Series3:22

http://www.microsoft.com/downloads/details.aspx?familyid=A5C84275-3B97-4AB7-A40D-3802B2AF5FC2&displaylang=en

http://www.microsoft.com/downloads/details.aspx?FamilyID=0856EACB-4362-4B0D-8EDD-AAB15C5E04F5&displaylang=en

http://msdn.microsoft.com/en-us/library/ms684190.aspx


3.13 Feature Id Reference List

3.13.1 Feature Tree HierarchyThe 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 ofvolumetric drawings of using specified templates,thus simplifying their update after a change to thePDMS model.

EXPLANTA ExPLANT-A DXF export driver

EXPLANTI ExPLANT-I DGN export driver.

GLOBALUSER Global Client Upgrades this installation to include the RemoteProcedure Call (RPC) Global Client. This is requiredto allow PDMS Users to invoke Global commands.

MDS Multi-DisciplineSupports

Multi-Discipline Supports (MDS) Add-on to PDMSfor the design, drawing and MTO of all kinds ofsupports, from a complicated frameworkencompassing integral hangers to a simple U-bolt.

MDSMOD Plant CompatibleModels

Sample data, including catalogues, for PDMS andassociated products.

MODELS PDMS Models Sample data, including catalogues, for PDMS andassociated products.

NUCLEAR NuclearApplications

Contains separately licensed products NuclearConcrete Design, Nuclear Room Manager andNuclear Concrete Quantities

PDMS PDMS PDMS, including applications. Includes separatelylicensed add-ons: Diagrams, Cable Design, LaserModel Interface, Query, SQL-Direct.

PIDINT Schematic 3DIntegrator

Integration application to ensure data consistencybetween P&IDs and the PDMS 3D model.

PLANT AVEVA PlantSuite

AVEVA PDMS and associated Products 12.1.1

12 Series3:23


PDMS -- ABA

PDMS -- ABA -- MDS

PDMS -- ABA -- MDS -- MDSMOD

PDMS -- EXPLANTA

PDMS -- EXPLANTI

PDMS -- NUCLEAR

PDMS -- MAN

3.14 SelectionTree Selection & De-selection RulesSuccessful Inclusion of a descendant Feature implies that all ancestor Features are alsoincluded. 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 (seeabove).

De-selection of a Feature overrides any commands or defaults which may have otherwiseincluded it. For example, suppose MDS is included, and ABA is excluded. The result will bethat PLANT and PDMS are installed, since they default to being installed. Removing ABAcauses MDS to be removed, since ABA is its Parent (Ancestor), (see SelectionTreeHierarchy diagram).

3.15 Selecting Features from the Command LineFeatures 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 thisdiscussion will be limited to the ADDLOCAL and REMOVE Properties. The ADDSOURCEProperty is considered less relevant, as the "Will be installed to run from network" Featureoption, 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 ADDLOCALProperty, whilst any Features intended not to be installed will be listed in the REMOVEProperty.

As previously stated, de-selection commands override inclusion commands. The reason forthis is because the REMOVE Property is evaluated after the ADDLOCAL property. Thepartial list below shows the order in which FeatureState Properties are evaluated by the MSIService:

1. ADDLOCAL 2. REMOVE 3. ADDSOURCE 4. ADDDEFAULT 5. REINSTALL

12 Series3:24











6. ADVERTISE

3.16 Command Line Definable DirectoriesThe following directories can be set on the Command Line, in the same way that Propertiesare assigned.

As with Properties, Directories for which the Id's are all uppercase, can be re-defined on aCommand 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.1

Note: There is no space around the equals (=) sign.

Note: The quotes surround the value, and would be unnecessary is the value had no spacewithin it.

3.16.1 Sample Command LinesA most definitive reference to MSI Command Line arguments can be found here. Thefollowing examples have been tested, but are only intended to demonstrate generalCommand Line principles.

In Windows 7 and Windows Server 2008 make sure that the command line has beenopened using the option Run as administrator so that the silent install application has thecorrect 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

PROJECT 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 (unlessapplication directories are set).

12 Series3:25





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 dialogand standard logging. Never attempt to Reboot

Create a basic logMSIEXEC /I [Path to MSI] ADDLOCAL=ALL REMOVE=ABA ROOTDRIVE=E:\ REBOOT=ReallySupress/l [Path to log file] /qb!-

Example 2 Installing projects to a different location and setting users writeable areas to a separate drive.

Installs all Features to the C:\

MSIEXEC /I [Path to MSI] ADDLOCAL=ALL ROOTDRIVE=C:\ PDMSUSER=D:\AVEVA\Data12.1.1\PDMSUSER PDMSWK=D:\AVEVA\Data12.1.1\PDMSWK DFLTS=D:\AVEVA\Data12.1.1\PDMSUI\DFLTS PROJECT=Q:\PDMS\12.1.1/l [Path to log file] /qb!-

Example 3 Removing an InstallationMSIEXEC /X [Path to MSI] /QB!

Example 4 Removing a Feature

Remove "ExPLANT-I" MSIEXEC /I [Path to MSI] REMOVE=EXPLANTI /qb!-

12 Series3:26

PDMS & Associated Products Installation GuideSet Up the Windows Environment

4 Set Up the Windows Environment

Setting up the Windows Environment section describes how to configure the Windowsoperating system before running PDMS. Following the installation of PDMS, the user shouldperform 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 infolder C:\AVEVA\Plant. If it has been installed elsewhere, substituteC:\AVEVA\Plant with the name of the installation folder.

4.1 Windows Control PanelThe Windows Control Panel contains tools that are used to change the way Windows looksand behaves. This Installation Guide describes how to use Control Panel tools to configureWindows 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 toSettings, and then click Control Panel. If the users computer is set up with the standard Start menu, click Start and then clickControl Panel.

4.2 Graphics Card SettingsThe user should set the display to a resolution of at least 1024 x 768 ( 1920 x 1200recommended) 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 Settingstab. Make the appropriate selections on the form for the graphics card.

Due to the rapidly changing list of hardware accelerated OpenGL graphics cardscommercially available, an up-to-date list of supported graphics cards, graphics devicedrivers and recommended device driver configuration cannot be included in this document.However, the AVEVA Support Web pages (http://www.aveva.com/support) contain a currentlist of both tested and supported graphics cards, along with advice on configuration ofgraphics device drivers.

12 Series4:1

http://www.aveva.com/engineeringit


4.3 Set the License File LocationBefore the user can use PDMS, the Flexman license system must be set up and connectedto the Flexman License Manager daemon, refer to the Flexman Installation andConfiguration Guide. A license file should be requested from AVEVA Customer Services.

4.4 PDMS Environment VariablesPDMS uses Windows Environment variables to locate folders containing PDMS system filesand users project data. This allows the user to locate these folders anywhere on the filesystem. The default location for PDMS system files is C:\AVEVA\plant\PDMS12.1.1\, unlessthe default location was changed during the installation.

PDMS is supplied with a file evars.bat in the PDMS executables folder which sets defaultvalues for the environment variables so that they point to the folder structure as installed. Italso 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 ofeach 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 betweenfolders, for example:

set PDMSUI=C:\Local PDMS\Appware;M:\Project PDMS\Appware; a:\Company PDMS\Appware

Note: that in order to define an environment variable that contains just one item includingspaces, it must explicitly include a final semicolon. For example:

set PDMSUI=C:\Local PDMS\Appware;

Length of Search Path Environment Variable

The lengths of PDMS search path environment variables can be up to a maximum of 5120characters.

Recursive Expansion of Environment Variables

An environment variable defining a search path can itself contain references to otherenvironment variables. For example:

set MPATH=%ROOT%\Standard Version;%ROOT%\Update Version

set ROOT=C:\Program Files\AVEVA; (note final semicolon)

Then on PDMS:

*$m%MYPATH%\mac

Will check in turn for:

C:\Program Files\AVEVA\Standard Version\mac

C:\Program Files\AVEVA\Update Version\mac

12 Series4:2


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 musthave write permission to these folders.

PDMSEXE Executable folder

C:\AVEVA\Plant\PDMS12.0.xxx

PDMSEXEMAIN Copy of PDMSEXE, but can be a search pathC:\AVEVA\Plant\PDMS12.0.xxx

PDMSUI Application User Interface folder (PML 1)C:\AVEVA\Plant\PDMS12.1.1\PDMSUI

PMLLIB Application User Interface folder (PML 2)C:\AVEVA\Plant\PDMS12.1.1\PMLLIB

PDMSDFLTS Applications defaults folderC:\AVEVA\Data12.1.1\PDMSUI\dflts

PDMSPLOTS Applications PLOTS folderC:\AVEVA\Plant\PDMS12.1.1\PDMSUI\plots

PLOTCADC Pointer to the PLOT executable.C:\AVEVA\Plant\PDMS12.1.1\plot\plot.exe

PDMSHELPDIR Online help data files.C:\AVEVA\Plant\PDMS12.1.1\Documentation

PDMSWK Temporary PDMS work file folderC:\AVEVA\Data12.1.1\PDMSWK

PDMSUSER Application Users save/restore setup area (or the users'home' folder)

C:\AVEVA\Data12.1.1\PDMSUSER\

PDMSREPDIR PDMS Applicationware Report Input and Output folder.C:\AVEVA\Plant\PDMS12.0\PDMSUI\reports

PDMSDFLTS Applications defaults folder. Note that individual users maynot have permission to change PDMS System defaults inC:\AVEVA\Data12.1.1\PDMSUI\dflts, but they should havetheir own local defaults area. This is achieved by setting aPDMSDFLTS search path, e.g. ‘C:\USERDFLTSC:\AVEVA\Data12.1.1\PDMSUI\dflts.

12 Series4:3


Project Environment Variables

For each PDMS project, the following environment variables must be set. For example, for aproject ABC:

PDMS is installed with sample project data (Refer to PDMS Projects). PDMS ProjectEnvironment variables for these projects are set in evars.bat.

4.5 Run PDMS from a Command WindowThe user can run PDMS from a Command window rather than using the Start/Programsmenu. To do this the user must set the PATH variable to include the folder where PDMS isinstalled.

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.1\) to the list of folders in the Path variable.

Once the Path variable includes the AVEVA PDMS folder, the user can run PDMS by typingpdms at a command prompt.

4.6 Customise PDMS Start-UpThere is a batch (.bat) file supplied in C:\AVEVA\Plant\PDMS12.1.1\ called pdms.bat whichallows 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.1 > 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 ofdialogs to help the user create the shortcut. Type in the location of pdms.bat, forexample: C:\AVEVA\Plant\PDMS12.1.1\pdms.batthen 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.1\ (the path name for the pdms.bat file) intheir PATH environment variable, just type pdms in a command window to execute thebatch 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 Series4:4


• Otherwise, navigate to the folder where the batch file is stored and type pdms orpdms.bat.

4.6.1 Create User Batch File to Run PDMSThe user can set up their own batch files to run PDMS. For example, the user may want torun 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\Plant\PDMS12.1.1\pdms.bat TTY SAM SYSTEM/XXXXXX /STRUC$M/mymacrofile

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 userSYSTEM/XXXXXX, in MDB /STRUC, and run the PDMS command macro mymacrofile.

4.7 Run PDMS in BatchPDMS 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 fileresumes 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 beused to make a PDMS script wait for PDMS to complete before continuing.

PDMSWait uses Windows facilities to wait for an event triggered by PDMSConsole whenPDMS finishes. Because the user can be running more than one PDMS session on any onecomputer, both PDMSWait and PDMSConsole look for an environment variablePDMS_CONSOLE_IDENTIFIER before doing this. The user can setPDMS_CONSOLE_IDENTIFIER 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 usethe 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_IDENTIFIER=%RANDOM%call %PDMSEXE%\pdmscall %PDMSEXE%\pdmswaitecho Returned to .bat at %TIME%

12 Series4:5


4.8 PlotTo plot in a Windows environment, AVEVA recommend that the user uses the plotcadc.batfile supplied in the AVEVA PDMS folder.

Note: The user may have to modify the plotcadc.bat file to suit their local printerinstallation.

The Network Plotter must be mapped using the NET USE command. Refer to the networkdocumentation for more information.

To run the plotcadc.bat file, give a command in the format:

C:\AVEVA\Plant\PDMS12.1.1\plotcadc.bat plotfile format printer options

Where options are the AVEVA PLOT utility options, and may be omitted. See the PLOTUser Guide for more information.

Note: The options must be enclosed in quotes.

Example:

plotcadc.bat c:\pdms\plot1 ps \\ntserver\NTPostScriptplotcadc.bat c:\pdms\plot1 hpgl \\ntserver\NThpgl 'CE=Y'

12 Series4:6

PDMS & Associated Products Installation GuideLanguage Support

5 Language Support

PDMS 12.1.1 introduces the use of Unicode for character storage throughout, with theexception 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. Thiswill enable the support of many more languages in the future.

There are aspects of the Unicode standard that are not yet implemented. PDMS currentlyhandles 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 ofbytes

Previous versions of PDMS have been supported only with certain language groups; thesame groups have been used to test PDMS 12.1.1 and are fully supported. No PDMS fontfiles are available for any other language; this means that TrueType fonts must be used ondrawings and that therefore it is not possible to produce plotfile output.

These groups are:• Latin-1• Latin-2• Latin-Cyrillic• Far Eastern

12 Series5:1


Supported Languages

5.1 Setting PDMS Default Text FormatBy default all sequential text files read by PDMS will be expected to be in UTF-8 format witha 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 formatwith a BOM present.

A simple command line 'transcoder' is also supplied; this may be used in some applicationsto 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 modifythe 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/Cyrillicalphabet

Bulgarian, Byelorussian, English, Macedonian, Serbo-Croatian, Ukrainian, Russian

Far Eastern Japanese, Korean, Simplified Chinese, Traditional Chinese

CADC_LANG Specifies the file encoding for reading external files which do nothave a Unicode BOM present. If the variable is unset, thisdefaults to LATIN-1. Files with the following Unicode BOMs willbe translated to UTF-8 on reading: UTF-16 little-endian, UTF-16big-endian, UTF-32 little-endian, UTF-32 big-endian.

CADC_LANG_NEW Specifies the file encoding for new files written. If the variable isunset, 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

12 Series5:2


5.2 Prepare PDMS For Legacy DatabaseThese settings should not be required for new projects but must be set correctly in order touse 'legacy' databases. This is particularly important if they are to be reconfigured toUnicode as the transcoding will be based on these settings.

The corresponding font family must be selected for DRAFT and ISODRAFT drawings. UseProject > Font Families and select the Font Type appropriate for the chosen language.

For details, see the Administrator User Guide and Administrator Command ReferenceManual.

LATIN2 ISO8859-2

LATIN3 ISO8859-5 Cyrillic

JAPANESE Japanese Shift-JIS

CHINESE Simplified Chinese (EUC)

KOREAN Korean (EUC)

TCHINESE Traditional Chinese (used in Taiwan for example) (EUC)

CP932 Japanese Shift-JIS

CP936 Simplified Chinese GBK

CP949 Korean

CP950 Traditional Chinese Big5

CP1250 Central European

CP1251 Cyrillic

CP1252 LATIN-1 + some extras (beware)

Command Languages covered

PROJECT CHARSET LATIN 1(default)

Danish, Dutch, English, Faroese, Finnish, French,German, Icelandic, Irish, Italian, Norwegian,Portuguese, Spanish, Swedish,

PROJECT CHARSET LATIN 2 Albanian, Czech, English, German, Hungarian, Polish,Rumanian, Serbo-Croat, Slovak, Slovene

PROJECT CHARSET LATINCYRILLIC

Bulgarian, Byelorussian, English, Macedonian, Serbo-Croatian, Ukrainian, Russian

PROJECT MBCHARSET JAP Japanese

PROJECT MBCHARSET KORFILE /<font filename>

Korean

PROJECT MBCHARSET CHI Simplified Chinese

PROJECT MBCHARSETTCHIN FILE /<font filename>

Traditional Chinese

12 Series5:3


12 Series5:4

PDMS & Associated Products Installation GuideRun PDMS Under Windows

6 Run PDMS Under Windows

6.1 Spaces in Windows PathnamesTo run macros with spaces in the filenames, the user must enclose the filename in quotes,without a leading slash. For example:

$m'c:\Program Files\Macros\space.mac' arg1 arg2

Due to the way in which PDMS parses its command lines, this format is also recommendedfor use with filenames containing Asian characters.

6.2 Link to Microsoft ExcelThe user can make reports load directly into a Microsoft Excel spreadsheet, as comma-separated files:

• Select Utilities > 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 marksif the argument contains embedded spaces. :\<excel folder>\.

6.3 Windows ParametersThe following setting can be used to improve performance when repositioning windows inPDMS. These are optional Windows Parameter settings.

Windows XP• Open the Control Panel. Select Display, then select the Appearance tab, click

Effects. On the Effects window, uncheck Show Window Contents While Draggingand Show shadows under menus.

12 Series6:1

PDMS & Associated Products Installation GuideRun PDMS Under Windows

12 Series6:2

PDMS & Associated Products Installation GuidePDMS Projects

7 PDMS Projects

7.1 Sample ProjectPDMS 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 pointswhen 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 AreaThe sample project is loaded automatically when the user installs PDMS. The user shouldcopy the sample project to their user area and run it as supplied. The project files are held intwo directories: sam000 holds all DESIGN data and catalogue data; sampic holds theDRAFT picture libraries.

7.1.2 Users and Teams in the Sample ProjectFree 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 Series7:1


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 correspondingconstructor module.

Each MDB contains databases with appropriate access rights. There are also teams andusers associated with each MDB with appropriate access rights.

7.1.3 MDBs in the Sample ProjectThe MDBs in the Sample Project section assumes that the user is already familiar withPDMS databases.

The sample project contains the following MDBs which can be used for demonstration ortraining 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 containssuitable pipework, steelwork and civils as a starting point.

HVAC An MDB for the HVAC Design tutorial. This MDB contains suitablesteelwork and civils as a starting point.

MASTER An MDB containing the master Catalogues and Specifications,LEXICON, Dictionaries etc.

12 Series7:2


7.1.4 Sample Project and User ProjectsThe user can add databases from the sample projects SAM and MAS to their own projectsfrom 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 andMAS have been set.

Note: On DRAFT Libraries: The user must have DRAFT libraries available in their currentproject before they can enter the module. The user may find it convenient to installthe libraries supplied by AVEVA in the MAS project (using the Install options), even ifthey 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 Productiontutorials. This MDB contains DESIGN data from which reportsand drawings can be produced. The user can also produceisometrics.

IMPSAMPLE An Imperial version of SAMPLE.

STRUC An MDB for the Structural Design tutorial.

12 Series7:3


12 Series7:4

PDMS & Associated Products Installation GuideTroubleshooting

8 Troubleshooting

Here are some suggestions about solving some problems the user may encounter whenusing PDMS under Windows.

8.1 General

8.2 License Manager Errors

Error: The dynamic link library DFORMD.dll could not be found in thespecified path.

Explanation: This is supplied with PDMS. Check the PATH variable has been set.The PATH setting must include ‘C:\AVEVA\Plant\PDMS12.1.1’

Error: STOP. The application failed to initialise properly (0xc0000135). Clickon OK to terminate the application.

Explanation: This occurs after a number of other errors. The most likely reason is aproblem with the PATH variable.

Error: When the user starts up lmgrd it says <time> (lmgrd) Can't makefolder C:\FLEXlm, errno: 2 No such file or folder, etc.

Solution: There is no C: drive for the license manager to write to. The SystemAdministrator 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 Explorer’s File menu, create a new folder (e.g.D:\C_drive) and make it current. Select File > Properties and selectthe Share tab. Click on Shared As: and then click OK.

Then from the Tools menu select Map Network Drive. Select C: fromthe Drive: drop-down list in the displayed form and type:\\hostname\C_drive 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 Series8:1


8.3 Enter PDMS

Explanation: The hostname used by AVEVA to create the license file does notcorrespond with the computer on which the user is running PDMS.The hostname comes from the variable COMPUTERNAME, whichcan be obtained by typing 'set|findstr COMPUTERNAME' in aCommand window. Compare this with the license file contents, andresubmit 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 fileor 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 hasbeen 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 correctlocation. 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 usernameand/or password.

Error: PDMSWK environment variable not set.

Solution: Set PDMSWK to c:\temp or some other folder where PDMS cancreate temporary files.

Error: Error 34 opening variables file.

Explanation: The user cannot create a file in the location pointed to by environmentvariable PDMSWK.

12 Series8:2


8.4 Problems with Graphics

Error: Project <xxx> is pre version 8.

Explanation: This can happen if the user has transferred the project from UNIXusing 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 graphicsboard that the user is using. Make sure the user has the version of thedisplay driver recommended on our supported display drivers Webpage.

Error: Incorrect colours.

Solution: Check the setting of the users Display. The colour resolution shouldbe 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 Series8:3


12 Series8:4

PDMS & Associated Products Installation GuideStructure of PDMS on .NET

9 Structure of PDMS on .NET

From AVEVA PDMS 12, the GUI uses the Microsoft .NET Framework environment includingthe latest WinForms/Infragistics based user interface components. Using the state-of-the-artInfragistics technology enables docking forms and toolbars in PDMS and provides a robustfoundation for the future provision of standard application programming interfaces.

This has changed the structure of pdms: this section gives a brief overview and the followingone outlines how to troubleshoot the installation.

9.1 OverviewThe Overview section describes the overall structure and components of the PDMS .NETinstallation, and the environment necessary to run it. Each PDMS GUI module now consistsof a .NET module, .NET interface and addin assemblies and native dlls plus some othershared components including 3rd party controls from Infragistics. The .NET components areprivate assemblies installed under the root directory %PDMSEXE%.

9.2 PDMSEXEAs before the environment variable %PDMSEXE% is used to locate the executable onmodule switch. It is also used to locate attlib.dat (attribute and noun definitions),message.dat (message definitions), desvir.dat (schema definition) etc. Normally PDMS isstarted from pdms.bat which is located in the users %PATH%. Both %PDMSEXE% and%PATH% should include the install directory.

9.3 GUI Module StructureEach GUI module is now structured in the same way. The basic structure for each modulelooks like this.

12 Series9:1

PDMS & Associated Products Installation GuideStructure of PDMS on .NET

where all components are installed in the %PDMSEXE%. directory (this is different from11.6 where the .NET wrapper interfaces were installed in separate subdirectories. At 12.0this has been simplified) So, when running a PDMS GUI module %PDMSEXE% is used tolocate the executable, .NET loading rules are used to load the interface assemblies andWin32 DLL loading rules are used to load the native components (and other Win32 DLLs onwhich pdms.dll depends).

9.3.1 .NET Loading RulesAll the .NET assemblies are Private assemblies and are installed under %PDMSEXE%(Assembly Base directory) or a subdirectory below. .NET loads private assemblies from thebase directory of the application. If it can’t find the private assembly here it uses theapplications configuration file called <module>.exe.config to see whether it contains anypath hints. Path hints are stored in the <probing> element, (this was used at 11.6 but is nolonger necessary at 12.1 since both .NET and native components live in the samedirectory).

9.3.2 Native DLLsNative dlls are loaded using Win32 DLL loading rules. These are:

• The directory from which the importing component loaded.• The (application's) current directory (where it’s run from)• The Windows directory (default: C:\Windows) (we don’t 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 inevars.bat located in the installation directory. Having different versions of PDMSEXE in the%PATH% may cause System.IO.FileLoad exceptions where components are loaded fromdifferent directories.

These rules apply to pdms.dll and all it's dependencies.

9.4 ComponentsAll components are installed in the %PDMSEXE% directory including .NET interfaces andaddins, Infragistics assemblies and native components.

12 Series9:2

PDMS & Associated Products Installation GuideTroubleshooting the .NET Installation

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 definitionwith name 'Aveva.Pdms.Database' does not match the assemblyreference.

Solution: All .Net assemblies must be the same version (apart from published .NETinterfaces where only major and minor version numbers must be thesame). Open File > Properties > Version > Assembly Version, and checkthat all version numbers are the same.

Error: An exception ‘System.IO.FileNotFoundException’ has occurred inmon.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. .NETloads private assemblies from the base directory of the application. If itcan’t find the private assembly here, it uses the application’s configurationfile called <module>.exe.config to see whether it contains any path hints.Path hints are stored in the <probing> element. Normally all assembliesshould be located in the %PDMSEXE% directory

12 Series10:1


10.3 Interface Incompatibility

10.4 No Add-ins

10.5 Window Layout

10.6 SerialisationSerialisation is the process used to store the window layout - e.g. history stacks, toolbarstate, docked window position - for the GUI in a .NET environment. For each module this

Error: An exception ‘System.MissingMethodException’ has occurred inmon.exe,or

An exception ‘System.IO.FileNotFoundException’ has occurred inmon.exe

Additional information: A procedure imported by 'Aveva.Pdms.Database.Implementation' could not be loaded

Solution: The interfaces between components are not compatible. Check thatFile > Properties > Version Assembly Version on all assemblies isconsistent. 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 isdeleted then the window layout will return to its default.

12 Series10:2


data is stored in C:\Documents and Settings\<username>\Local Settings\ApplicationData\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 Series10:3


12 Series10:4

PDMS & Associated Products Installation GuideInstall AutoDRAFT

11 Install AutoDRAFT

The Installing AutoDRAFT section explains the procedure needed to install and configureAutoDRAFT.

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 AutoDRAFTUser Guide. The DRAFT and ISODRAFT applicationware generates interface files forAutoCAD, which are then used by the scripts.

AutoDRAFT generates interface files for DRAFT, which can be imported using theirapplicationware.

11.1 CompatibilityThe version of AutoDRAFT released with AVEVA PDMS 12.1.1 is compatible with AutoCADReleases 2006 and 2007 within the limitations described in more details in AutoDRAFTUser Guide.

11.2 AutoDRAFT SoftwareAutoDRAFT software consists of three AutoCAD applications that run with AutoCADReleases 2006 and 2007, and AVEVA application macros to link these AutoDRAFTapplications 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 overlaysheets in DRAFT.

• AutoDRAFT Symbol Editor

The Symbol Editor is used to convert AutoCAD graphics into symbol templates withinDRAFT symbol libraries.

11.3 Configure AutoDRAFT with AutoCADThe AutoDRAFT software is installed under the PDMS executable folder:

12 Series11:1


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 runAutoDRAFT programs in AutoCAD.

Note: The AutoDRAFT software will operate properly only if AutoCAD can be run using theacad command. AutoDRAFT may not work if the AutoCAD executable acad hasbeen renamed, or if the acad command runs a user-supplied file which itself runsAutoCAD.

11.4 Install and Configure AutoCADIn order to use AutoDRAFT, AutoCAD must be installed and configured for each computerwhere AutoDRAFT will be used. The AutoCAD Installation and Performance Guide suppliedwith 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 ofAutoCAD are listed in the following sections. The environment variables are set within thesupplied pdms.bat file. These should be edited to suit the installed version of AutoCAD.

11.4.1 AutoCAD R2006set 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 followingas file paths:

• Location of autodraftACAD directory• Location of autodraftfonts directory

11.4.2 AutoCAD R2007set PDMS_ACAD=2007

12 Series11:2


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 followingas file paths:

• Location of autodraftACAD directory• Location of autodraftfonts directory

11.5 AutoCADBefore using the Drawing Editor make sure that AutoCAD has been correctly installed andconfigured by entering the command acad at the operating system command prompt.

11.6 Application Macros for use with DRAFTThe applicationware provides the additional menus and forms required to run theAutoDRAFT editors in AutoCAD directly from DRAFT and ISODRAFT.

12 Series11:3


12 Series11:4

PDMS & Associated Products Installation GuideConfigure Area Based ADP

12 Configure Area Based ADP

Before starting the configuration process make sure the project has been set up with aDrafting database (PADD) for the administrative elements of ABA and at least one Draftingdatabase (PADD) for the user elements. Make sure that access to the Draftingadministration database is controlled via the Drafting administration team.

1. Enter the Drafting module using the MDB for ABA administration and be sure to entervia Macro files, NOT Binaries.

2. Once in the Drafting module select the Draft > Administration from the Draft menuand 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 adetailed explanation of the elements defined in the Defaults file, refer to the DraftAdministrator Application User Guide.

The fields in the defaults file are as follows:

12 Series12:1


Defaults file Specifies the location directory and name of the defaults fileused to set or store the ABA default settings.

Library The top-level LIBY element which holds all the requiredABA administrative elements.

Templates Templates are stored below a DRTMLB, which is a libraryused to hold ABA drawing templates (DRTMPL). If morethat one Drawing template library is required, this should beset to a LIBY element and all DRTMPL placed below it.

Areas A LIBY for DLLBs which are used as drawlist libraries whichhold all the IDLI (ID List) elements that store the physicallimit co-ordinates for each of the ABA geographical areas.

Classifications a DLLB used to contain all the IDLI elements for each ABAclassification. A Classification is a set of database elementsthat have something in common e.g. Equipment elementswith 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 symbolse.g. north arrows.

Labelling A TRLB is a tag-rule library that contains all the ABA tagrules.

Tasks A TASKLB is a task library, which holds all the ABA taskse.g. plot - send drawing to a plot file.

Create Hierarchy This option is used to automatically create theadministrative 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 notthe elements contained within it.

To create the hierarchy specified in the defaults form, click

and select a db from the Create Aba Hierarchy formdisplayed.

The previously mentioned process will also create some

initial SYMBol elements. The icon will then turn to , whichindicates that the structure is OK.

12 Series12:2


The default settings for the Batch User can be set by clicking Batch User to display theBatch Username and Password form.

The application is supplied with a series of example data files that can be used to make atest 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 drawingscreated using ABA are to be stored.

Batchfile Location Gives the directory path where the batchfiles created byABA are to be stored.

User Name Specifies name of user that will enter the Base Product.

Password Specifies the password of the user.

12 Series12:3


Any data files must be loaded in the same order as shown in the Files list, since someelements rely upon the existence of other elements. To load a file, select the one theuser wants to load from the Files list and click Apply. Repeat this until all of thenecessary library files are loaded and click Dismiss.

Note: It is not possible to mix Metric and Imperial libraries since they utilise the sameelement names. If the user wants to mix them the user will need to modify the sourcedata files.

5. In the SAM project load each of the following files in order by selecting them in theFiles 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 Series12:4


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 administrativeelements (areas, classifications, tasks, labels, and drawing templates) for use by DRAFTusers.

Refer to the ABA Administrator and User Guides for further information.

12 Series12:5


12 Series12:6

PDMS & Associated Products Installation GuideMDS Installed Configuration

13 MDS Installed Configuration

MDS is installed directly into the main installation directory instead of being installed in aseparate 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 thatare installed for the main product. This means that if MDS has been installed then it will beavailable for a project design or outfitting session providing that the project has been set upfor MDS use (as described in the administration guide) and there is a valid MDS licenseavailable to the user.

13.1 Manual Configuration of the Product and Product Environment VariablesAll 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 VariablesEnvironment variables modifications are made to the base product's files evars.bat frompdms.bat.

Some of these environment variables can be "searchpaths".

AVEVA "searchpath" variables are modified from the initial setting %EnvVar%, using ablank* 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 pathname i.e. c:\aveva plant then environment variable settings need to be modified todeal with space delimeters. This is out of scope for this document but more detailedinformation regarding this topic can be found in the PDMS install guide.

SET EnvVar={newEnvVarValue} %EnvVar2% %EnvVar%

12 Series13:1


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 additionalPML code paths to their installation or otherwise include alternative locations for known files.

13.1.2 Modification of Evars.bat for MDSThe following environment variables are set up for MDS in the standard product evars.batfile:

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 rehash all”

Note: Write access is required to the PMLLIB folders to enable the several pml.indx files tobe updated.

13.1.3 Environment Variables for ProjectsExcept for the standard sample projects supplied with the products, the install cannot createthe 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 folderas the standard projects folder. Each of the sample projects (detailed in Projects) containsits own environment variable batch file (i.e. evarsMDS.bat) that is called from the standardevars.bat file.

13.1.4 For Projects Used with MDSNote: 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 thetwo extra folders created, and the relevant environment variables set to point to these twonew directories in the relevant evars batch file, e.g.

For a project called 'abc' create the two required folders by copying the …/MDS/ mdsdfltsand …/MDS/mdsinfo folders to where the 'abc' project folders are located, and rename themaccordingly, i.e. rename the copied folders mdsdflts and mdsinfo to abcdflts and abcinforespectively.

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

Cplmdsexe sets the executable location for the Witchhanger software interfaceif used.

12 Series13:2


Project Variables for MDS

and similar project environment variables for any other projects.

13.2 Projects

13.2.1 Projects Released with this ProductThere are five standard projects released with the Multi Discipline Supports product, theseare:

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 cataloguecomponent, catalogue application defaults and the designdatabases for use with the MDS application

MDU Multi Discipline Supports project containing the cataloguedatabase for the User defined MDS Ancillaries available in 12

PSL Pipe Supports Ltd Catalogue Project

12 Series13:3


12 Series13:4