Aveva Unified

AVEVA™ Engineering 15.
7 Installation Guide
aveva.com
© 2022 AVEVA Group plc and its subsidiaries. All rights reserved.
No part of this documentation shall be reproduced, stored in a retrieval system, or transmitted by any means,
electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of AVEVA.
No liability is assumed with respect to the use of the information contained herein.
Although precaution has been taken in the preparation of this documentation, AVEVA assumes no responsibility
for errors or omissions. The information in this documentation is subject to change without notice and does not
represent a commitment on the part of AVEVA. The software described in this documentation is furnished under
a license agreement. This software may be used or copied only in accordance with the terms of such license
agreement.
ArchestrA, Avantis, Citect, DYNSIM, eDNA, EYESIM, InBatch, InduSoft, InStep, IntelaTrac, InTouch, OASyS,
PIPEPHASE, PRiSM, PRO/II, PROVISION, ROMeo, SIM4ME, SimCentral, SimSci, Skelta, SmartGlance, Spiral
Software, WindowMaker, WindowViewer, and Wonderware are trademarks of AVEVA and/or its subsidiaries. An
extensive listing of AVEVA trademarks can be found at: https://sw.aveva.com/legal. All other brands may be
trademarks of their respective owners.
Publication date: Thursday, September 22, 2022
Publication ID: 1007559
Contact Information
AVEVA Group plc
High Cross
Madingley Road
Cambridge
CB3 0HB. UK
https://sw.aveva.com/
For information on how to contact sales and customer training, see https://sw.aveva.com/contact.
For information on how to contact technical support, see https://sw.aveva.com/support.
To access the AVEVA Knowledge and Support center, visit https://softwaresupport.aveva.com.
Contents
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Assumptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Guide Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
AVEVA Licensing System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
AVEVA Flex Licensing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Font Size. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
AVEVA Engineering Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

SEE Electrical 3D Panel+. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Uninstall. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Change, Repair and Remove. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Healing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Modified New and Removed Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Models, Sample Data and Example Projects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Change Default File Replacement Behaviour. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Network (Admin) Installations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Issues with Administrative Installation Points. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Run AVEVA Engineering from Network Locations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Copy a Local Deployment to a File Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Command Line Definable Directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Set Up the Windows Environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Windows Control Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Set the License File Location. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Customise AVEVA Engineering Start-Up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Create User Batch File to Run AVEVA Engineering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Run AVEVA Engineering in Batch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
© 2022 AVEVA Group plc and its subsidiaries. All rights reserved. Page 3
AVEVA™ Engineering 15.7 Installation Guide
Contents
Language Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Setting AVEVA Engineering Default Text Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Prepare AVEVA Engineering For Legacy PDMS Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Run AVEVA Engineering Under Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Structure of AVEVA Engineering on .NET. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
AVEVA_DESIGN_EXE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
UI Module Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
.NET Loading Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Native DLLs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Tag Management Register Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Right Click Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
SQL Server Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Enable TLS Encryption between Service and SQL Server. . . . . . . . . . . . . . . . . . . . . . . . 80
TMR Service - HTTPS Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Exposing an instance of SQL server to be used by networks users. . . . . . . . . . . . . . . . 90
Granting Access to an Existing SQL Server User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
TMS Project Upgrade to TMR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
1 Introduction
The AVEVA Engineering Installation Guide explains how to install and set up AVEVA Engineering on a workstation
running Microsoft Windows. For completely up-to-date information, refer to the AVEVA Website at and the
Customer Support Hardware pages.
Assumptions
The AVEVA Engineering Installation Guide assumes that:
• Users are familiar with the concepts of folder/file hierarchies for storing data on disks and with basic
Windows terminology and commands. If not, the user can also refer to the operating system documentation
while carrying out the installation.
• Users have already gained access to the installation files for AVEVA Engineering via the AVEVA Download site.
• Users have Local Administrator rights.
• Adobe PDF Reader is installed.
Guide Structure
The AVEVA Engineering Installation Guide is divided into the following sections:
Requirements lists the hardware and software requirements.
AVEVA Engineering Installation describes how to install and license the software.
Set Up the Windows Environment explains how to configure the Windows operating system
before running AVEVA Engineering.
Language Support describes how to set up the Windows Environment to use
AVEVA Engineering with different Language options.
Run AVEVA Engineering Under Windows gives some advice on using AVEVA Engineering in a
Windows environment.
Structure of AVEVA Engineering on .NET outlines the way in which AVEVA Engineering is installed
and configured in a Microsoft NET environment.
Tag Management Register Installation describes how to install and configure the Tag
Management Register software.
2 Requirements
AVEVA Engineering operates on Windows 10 and Windows Server 2019. AVEVA Engineering will operate with
less but system performance will be compromised.
AVEVA Engineering uses Microsoft .NET Framework version 4.8 (supplied with AVEVA Engineering and installed if
necessary). Refer to AVEVA Engineering Installation for installation instructions.
Note: Serialized settings of the user interface configuration are saved in the following location on Windows 10:
C:\Users\<username>\AppData\Local\Aveva\Engineering\15.7
Note: Microsoft .Net Framework 4.8 can only be installed on Windows 10 versions 1607 and above.For Windows
10 Versions 1903 and above, .NET Framework 4.8 is preinstalled.
To check the windows 10 Version for the PC, type winver in the Start menu search box and then press enter to
display the About Windows window.
A PassMark ® Rating of 1600 or 2000 for mobile computers is recommended.
Requirements
A minimum screen resolution of 1280x1024 is recommended, although most users use either two such screens
or a wide-screen (1920x1200) display.
Internet Explorer 8 or later is also required.
If AVEVA Engineering is installed with AVEVA Database Cache Service the user must activate Microsoft Message
Queuing (MSMQ) as a prerequisite of the installation. Refer to the Database Cache Service Installation Guide for
further information.
The user interface requires the use of the Arial Unicode MS font, which is supplied with Microsoft Office (version
2000 onwards) and is usually installed automatically. If this font is not installed, some of the text in the user
interface may become illegible.
The layout of some GUI forms may also be adversely affected if the screen font size is not set to the smallest size,
which is usually default. Refer to Font Size for further information.
Graphics cards
AVEVA Engineering requires 3D graphics hardware, capable of running DirectX 11, to ensure optimum
performance for both design and drafting. DirectX 11 is included as an integral part of the Windows 10 operating
systems.
AVEVA strongly recommends that appropriate hardware is used for AVEVA Engineering.
If appropriate graphics hardware is not detected on entry, AVEVA Engineering may still be used but the displayed
warning is given and certain graphical effects, including use of laser data is limited.
Following extensive testing of current market Graphics Cards and AVEVA Engineering, a recommended
configuration is summarised in the table below.
Desktop Laptop
Graphics Card
nVIDIA® Quadro® K600. nVIDIA® Quadro® K1000M.
"AMD FirePro™ V3800 or V3900. "AMD FirePro™ M2000.
AVEVA strongly recommends that clients should test their chosen card or laptop in their own environment before
purchase.
Availability and support of graphics cards changes frequently; a full updated list of graphics cards that have been
verified with AVEVA Engineering is available via the IT Configuration area of the AVEVA Support Site ().
PC Configuration
OS Windows 10
CPU Intel x64 compatible - CPU with high performance in each processor core.
Requirements
RAM 32 GB of high speed RAM.

HDD The amount of disk space should be configured according to the customer's requirement
based on the number and size of projects. To secure data and improve performance, the use
of RAID 0+1 or 5 storage is recommended; 15k rpm drives are preferred.
Display High resolution widescreen display recommended (1920 x 1200); dual screens also
supported. Minimum resolution 1280x1024.
File System NTFS.
Network Gigabit Ethernet (GbE) LAN.
Firewall Microsoft ICF disabled.
Other Mouse - three button with a scroll wheel.
Server Configuration
OS Windows Server 2019.
CPU Modern architecture multiple core processors recommended.
RAM 32 GB RAM. Additional RAM increases the caching capability and thereby the performance.
HDD The amount of disk space should be configured according to the customer's requirement
based on the number and size of projects. To secure data and improve performance, the use
of RAID 0+1 or 5 storage is recommended; 15k rpm drives are preferred.
File System NTFS.

Network Gigabit Ethernet (GbE) LAN. 64-bit capable network adapter. The network should provide at
least 1 Gb/sec for each workstation. Two or more network cards are recommended for
increased performance and redundancy
SEE Electrical 3D Panel+ Requirements

Processor Intel® Core™ i7 >3 Ghz or equivalent.
NVIDIA GeForce® GTX Graphics Card with 4GB memory or equivalent.
Memory (RAM) >16 GB.
The minimum system requirements are:
10 GB of hard disk space for use of the standard 3D symbol library.
25GB of hard disk space for use with the entire library of 3D symbols.
Note: This requirement will increase with time.
AVEVA Engineering 14 series to 15 series
When you consider moving project data created with AVEVA Engineering 14 series to run with the
AVEVA Engineering 15 series, AVEVA recommends that you contact AVEVA Technical Support for the
latest advice and guidance. The following should be noted when considering this transition:
Requirements
• There is a large degree of change between AVEVA Engineering 14 and 15 series. This means it might not be
appropriate to simply point AVEVA Engineering 15 software at projects that have ENGI databases created
with AVEVA Engineering 14.2 or earlier. If this is done, it is possible that database corruption could occur.
This would show up in DICE reports as Fatal Errors. Repair will require a Reconfigure process, which could be
significant and encompass all project databases. The steps required to avoid corruption vary depending on
project structure/content, please discuss your exact needs with AVEVA Technical Support.
• The Mandatory/Optional Upgrade process does not transform database content. It sets a flag on the
database that stops earlier software versions being used. It is optional so that you keep the option to be able
to switch back to an earlier version of software if you see any risk in using new software versions.
Note: If you do use the Mandatory/Optional Upgrade on a database, you cannot Undo that transaction.
AVEVA strongly recommends having a full back-up available should you want to secure the ability to return to
the database using previous software versions.
The AVEVA Engineering group is reviewing documentation relating to data and project upgrade processes.
However, AVEVA strongly recommends to contact your local AVEVA Technical Support when considering a project
or database upgrade, particularly if you are moving to the AVEVA Engineering 15 series.
AVEVA Licensing System

To operate, AVEVA software must be able to access the correct AVEVA Licensing System file, which should be
installed on either the Server, on the users workstation, or on a networked workstation. Refer to the AVEVA
Licensing System Installation Guide for further information. News and update information is also available for
AVEVA Licensing System on the AVEVA support web-site.
Note: Although the DVD/Download contains several AVEVA products, the user will only be able to use the items
that are licensed to them. The user will get an on-screen notification to warn them when the license is due for
renewal.
AVEVA Flex Licensing

AVEVA Flex licensing provides customers with the flexibility to adjust where credits are charged for their usage.
The customer agrees to a Flex/Connect agreement. The agreement outlines the number of credits purchased
and the contract period available for the credits to be consumed, which can be used to access both on-premises
and Cloud/SaaS products.
During the contract period, the customer consumes products and services with credits charged based on the rate
plan. Both AVEVA and customer users can track the usage within AVEVA Connect.
For example, for any AVEVA Connect account, the Flex agreement is created and based on the requirement of
the customer. Credits are assigned to be utilized and the required products are added to that account. When
users start consuming the products accordingly, the credits are utilized as per the agreement. Refer to AVEVA
Connect documentation for further information.
The example report indicates how the flex credits are consumed based on the product utilization
Requirements
Font Size
During the installation of Windows 10, the install process decides what it believes to be the best setting for the
font size and sets this as the Default. AVEVA recommends to keep the default, that is 100% display size.
To change the default setting, right-click on the desktop, then from the displayed menu select Display Settings.
The Display window is displayed, modify the display settings to those displayed. If any changes are made, click
Keep Changes.
Requirements
3 AVEVA Engineering Installation
AVEVA Engineering is supplied via the AVEVA Download site. It is recommended that the user carefully read all of
the Installation instructions before installing the software.
It is recommended that the default settings are used for folder paths etc., unless the user has good reasons for
doing otherwise.
Manual installations can be easier if run from the Setup.exe program. Each Setup.exe checks and installs the
dependencies of its primary installation (like the .NET framework), before running its primary (MSI) installation.
Users should never see missing dependency errors if installations are started from the Setup.exe program.
Setup.exe also tells the primary installation to target the C:\ drive/volume, which is the preferred default in most
manual installations. However, if a more customised installation is required then running the primary MSI
directly becomes the better approach. In such cases, run time dependencies (like the .NET framework) must be
deployed beforehand.
AVEVA Engineering will not work if it is installed on a drive other than the C:\ drive with spaces in the installation
path.
.ETAP Import/Export
Initially during the installation of Engineering 15.x, only the export related files, 'ETAPExportTrans.xslt' and
'ValueValidation.xml' were placed in the installation directory, for example "C:\Program Files
(x86)\AVEVA\Engineering15.x".
Now the Export and Import related files (ETAPExportTrans.xslt, ValueValidation.xml; ETAPImportTrans.xslt,
ETAPAttribute.xml. ETAPImportTrans.xslt and ValueValidation.xml files) are placed in the following locations.
AVEVA Engineering Installation
Export
ETAPExportTrans.xslt A translation file which converts the AVEVA Engineering data into a
format ETAP can interpret.
ValidValidation.xml Runs validations in the ETAPExportTrans.xslt file.
Import
ETAPAttribute.xml Contains all the ETAP attributes which are used to map to their
corresponding AVEVA Engineering attributes.
ETAPImportTrans.xslt A translation file which converts the ETAP data into a format AVEVA
Engineering can interpret.
ValidValidation.xml Runs validations in the ETAPExportTrans.xslt file.
Microsoft .NET Framework Installation

If installation of Microsoft .Net Framework version 4.8 is required, navigate to the DotNet48 folder in the
Engineering download folder.
Open the ndp48-x86-x64-allos-enu.exe file to display the User Account Control window.
Click Yes to continue installation of the the application.

The Extracting files window is displayed, showing the progress of the file extraction, which the user can stop by
clicking Cancel.
After the download has been completed, the Microsoft .Net logo is displayed followed by the Microsoft .Net
Framework window.
The user must read the License Terms and then select the I have read and accept the license terms check box to
continue the installation.
After clicking Install, the Microsoft .Net Framework window displays task bars showing the status of the
installation.
Once the installation has completed, the Microsoft .Net Framework window displays a message confirming the
user has finished the installation of Microsoft .Net Framework.
The computer must be restarted to complete the Microsoft .Net Framework installation.
Note: For the purposes of this section of the installation guide the windows displayed during the installation
have the version number obscured. However the information and functionality available from the windows are
applicable to this version.
The AVEVA Engineering Setup Wizard activates at this point and guides the user through the installation of the
product.
Click Back to step back a stage, Cancel to terminate the Setup Wizard or Next to display the Client Cache Service
screen.
If Microsoft Message Queuing Service (MSMQ) is enabled the Client Cache Service screen confirms this.
If MSMQ is not enabled the Client Cache Service screen displays a warning that the service is not enabled.
To enable MSMQ, click Programs and Features to display the Control Panel.
In the left hand pane, click Turn Windows features on or off to display the Windows Features.
Select all of the Microsoft Message Queue (MSMQ) Server check boxes to enable the Microsoft Message Queue
(MSMQ) Server Core component.
Click Next to return to the AVEVA Engineering setup.

Click Next to display the End-User License Agreement window.
The user must read the End-User License Agreement and then select the I accept check box to activate Next.
Note: If the user does not select the check box, Next will not activate and the installation cannot continue.
After clicking Next the Custom Setup screen is displayed.
The default installation and its location is displayed in the Custom Setup screen.
To change the installation click the icons in the tree, to change the location of the installation, click Browse to
navigate to the required location.
Click Reset to return to the defaults.
Click Disk Usage to display the use of the hard drive.
Click Back to step back a stage, Cancel to terminate the Setup Wizard or Next to display the Initial Configuration
screen and continue the installation.
The Initial Configuration screen allows the user with existing projects and infrastructures to customise the
installation.
De-selecting the Install setup files and: check box deactivates the Start Menu Shortcuts and the Desktop
Shortcuts options. Both options are dependent on the setup files being installed.
De-selecting the Start Menu Shortcuts check box deactivates the Desktop Shortcuts option. The option is
dependent on the Start Menu Shortcuts being installed.
Clicking Browse displays the Change Destination Folder window which allows the user to select a different folder
name and location path.
Click Back to step back a stage, Cancel to terminate the Setup Wizard or Next to display the Additional Software
screen.
Check the box to install the SEE Electrical 3D Panel+ v2r2 SP2 software.
Note: Choosing this installation option will automatically install SEE Electrical 3D Panel+ v2r2 SP2 software at the
end of the AVEVA Engineering installation.
Click Back to step back a stage, Cancel to terminate the Setup Wizard or Next to display the License
Configuration screen.
Click Back to step back a stage, Cancel to terminate the Setup Wizard or Install to display the Installing AVEVA
Engineering screen.
The Installing AVEVA Engineering screen displays a taskbar showing the status of the installation.
During the installation process the screen displays Cancel, which can be clicked to stop the installation. When
selected a window is displayed asking for confirmation that the installation is to be cancelled.
Selecting Yes displays a screen showing the AVEVA Engineering Setup Wizard was interrupted.
Click Finish to exit the screen and installation.

Selecting No on the confirmation screen returns the user back to the Installing AVEVA Engineering screen and
continues the installation.
Once the installation has finished a window is displayed confirming the user has completed the installation of
AVEVA Engineering.
The user has the option to download the latest projects which are compatible with AVEVA Engineering. To do
this the user must select the Download the latest Projects check box and click Finish.
A web browser window is displayed, select Save then Run.
The Windows Installer Installation Wrapper window is displayed, showing the progress of the download, which
the user can stop by clicking Cancel.
After the download has been completed, the Windows Installer Download Bootstrap Security Warning window
is displayed.
Click Run to install the latest projects, the Windows Installer window is displayed showing the progress of the
installation, which the user can stop by clicking Cancel or click Don’t Run to cancel the installation.
After the installation has completed the AVEVA™ Projects Setup screen is displayed.
Click Cancel to terminate the Setup Wizard or Next to display the Custom Setup screen.
The Custom Setup screen displays every configurable aspect of the installation. Configurable Features are
displayed on the left hand side of the window, in a control called the SelectionTree. Refer to for further
information. Each feature is depicted as a box with a description of the feature displayed in the right hand pane.
The boxes representing each feature are depicted as follows:
- 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.
Clicking a box displays a drop-down menu.
Will be installed on local hard drive Selecting this option will install the feature locally.
Entire feature will be installed on local hard drive Selecting this option will install the feature and all its sub-
features locally.
Entire feature will be unavailable Selecting this option prevents the current feature and all
its sub-features from installing.
Clicking Reset will de-select all currently selected features.

If the Feature is not Unavailable ( ), a Location Path showing where the program is to be installed may be
displayed, if so Browse becomes active. During the installation of AVEVA Engineering the user chose the folder
location for the projects. If the chosen folder location is different from the default location displayed, the user
must click Browse and change the location to match.
Click Next to display the Ready to install AVEVA™ Projects screen.
Click Back to step back a stage, Cancel to terminate the Setup Wizard or Install to display the Installing AVEVA™
Projects screen.
The Installing AVEVA™ Projects screen displays a taskbar showing the status of the installation.
During the installation process the window displays Cancel, which can be clicked to stop the installation. When
selected, a window is displayed asking for confirmation that the installation is to be cancelled.
Selecting No on the confirmation window returns the user back to the Installing AVEVA™ Projects screen and
continues the installation.
Selecting Yes displays a window showing the AVEVA™ Projects Setup Wizard was interrupted.
Click Finish to exit the window and installation.

When the installation is complete the Completed Installation screen is displayed.
Click Finish to exit the Setup Wizard.
The user should refer to the APS_Project_description.pdf and ACP_Projects_description.pdf for further
information. These files are installed during the installation of the projects in the location selected by the user.
SEE Electrical 3D Panel+

If the install the SEE Electrical 3D Panel+ v2r2 SP2 software check box was selected, the software will now install.
AVEVA LaaS/Flex licensing is available for the SEE Electrical 3D Panel+ application.
Log File
During the installation, setup.exe creates a log file of the installation in the users TEMP directory named
Engineeringxx.x.log. To locate the log file, type %TEMP% in the Windows search text field.
Uninstall
Complete removal of an installation can be accomplished by several methods.
• Removing it from the Control Panel via the Add or Remove Programs option in the usual way. To open the
Control Panel, type Control Panel in the Start menu search box and then press enter.
• 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}. Refer to for further information.
Removal of individual Features is also possible from the command Line, using the REMOVE property or by
changing the installation state via the Add/Remove Programs options.
Note: Uninstalling the AVEVA Engineering installation will not uninstall Microsoft's .NET Framework or
downgrade the Windows Installer Service. The .NET Framework must be removed separately if required.
Change, Repair and Remove

There are several ways to change an installation. For example:
• Change it from Control Panel via the Add or Remove Programs option in the usual way. To open the Control
Panel, type Control Panel in the Start menu search box and then press enter.
• Right clicking on the MSI file that installed it, and selecting Install, then selecting Change, Repair or Remove
at the subsequent window.
After selecting an option the AVEVA Engineering Setup window is displayed.
Click Cancel to display a Confirmation window. Click Yes to cancel or No to return to the setup screen.
Click Next to display the Change, Repair, or Remove Installation screen.
Change Displays the Custom Setup screen, which allows the user to change which features that are
installed.
Repair Displays the Reinstall or Repair AVEVA Engineering screen, which allows the user to repair any
errors in the most recent installation by fixing missing and corrupt files, shorts and registry
entries.
Remove Displays the Ready to remove AVEVA Engineering screen which allows the user to remove the
installation.
Note: Never move files by other means, as this may trigger healing, however Copying files to other locations will
not cause problems.
Change
There are several ways to change an installation. For example:
• Change it from Control Panel via the Add or Remove Programs option in the usual way. To open the Control
• 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.
Refer to for further information.
Once the Change option is selected, the Custom Setup screen is displayed, allowing the user to change which
features that are installed. The functionality of the Custom Setup screen is described at the beginning of the
AVEVA Engineering Installation section of this Installation Guide.
Repair
Repair of an installation can be accomplished by several methods:
• Repair it from Control Panel via the Add or Remove Programs option in the usual way. To open the Control
• Right clicking on the MSI file that installed it, and selecting Repair.
• Running the command MSIEXEC /I [Path to Original MSI], then selecting Repair at the subsequent window.
• Running the command MSIEXEC /I {ProductCode of MSI}, then selecting Repair at the subsequent window.
Refer to for further information.
Once the Repair option is selected the Reinstall or Repair AVEVA Engineering screen is displayed, allowing the
user to repair any errors in the most recent installation by fixing missing and corrupt files, shorts and registry
entries.
The functionality allows the user to reinstall the application, detect and repair any errors in the most recent
installation and repair shortcuts.
Note: The default is the detect and repair option.
Click Next to display the Ready to repair AVEVA Engineering screen.
Click Repair to repair the installation, the Repairing AVEVA Engineering progress window is displayed.
When prompted click Next, once the repairs have been completed, click Finish.
Remove
Displays the Ready to remove AVEVA Engineering window which allows the user to remove the installation.
Note: Never move files by other means, as this may trigger healing, however copying files to other locations will
not cause problems.
Healing
MSI technology has in built self repairing mechanisms. As such it is generally unwise to alter file and folder
names, shortcuts or registry manually, as this may trigger the MSI which deployed the files to redeploy them.
However, it is expected that some users will want to alter Appware, Sample Data, shortcuts and .bat file
variables. As such, AVEVA installations have been designed to minimise the ability of the MSI to heal itself in such
cases.
Sample Data, Models, example projects and shortcuts, should not trigger healing if they are deleted or altered.
The consequence of making shortcuts editable/deletable is that MSI Advertising will not function.
Modified New and Removed Files

Irrespective of whether an MSI is installing, changing state, or repairing, files are removed/deployed/overwritten
based upon certain file version rules.Refer to for further information. As such, the changes caused by a repair or
an installation depend upon the initial state of the computer.
User Modified Appware
In MSI/Deployment terms, Modified appware files constitute un-versioned, language neutral files, whose
"Created Date" and "Modified Date" differ. However, if appware files have been moved or handled in certain
ways, then it is possible that the "Created Date" and "Modified Date" will not differ, in which case the file
replacement behaviour of the installation will be different. Refer to for further information.
In the case where an appware files "Created Date" and "Modified Date" is different, no MSI will ever overwrite
such a file. So Modified appware will never be upgraded (by default), changed or bug fixed by an AVEVA MSI or
Patch.
In the case where a modified appware files "Created Date" and "Modified Date" does not differ, the appware file
with the newest date will prevail (by default). This scenario is most likely to happen when installing a Patch or an
MSI which is not classed as a "Service Pack" or a "Full Release", since releases with more minor designations are
not side-by-side deployable, as they are intended as upgrades to pre-existing releases.
Once appware has been modified, it must fall to the author/owner to maintain the changes, since there is no
reliable way to reconcile code differences. In extreme cases this may mean that AVEVA installations cannot be
used to deploy appware, and those clients must make their own code merges.
Models, Sample Data and Example Projects

It is in the nature of Models, Samples and Examples, that:
• The constituent parts are often interdependent in some way.
• Interdependencies will vary between releases and can be difficult and risky to migrate automatically.
• Their file footprint is apt to change drastically.
• They will not always be required.
• They may be moved, copied and shared.
• File paths and folder names may change in time.
• Parts of them may be re-used in other scenarios.
• They can be supported or migrated across many versions of an application.
• Many different programs may work with them and with data derived from them.
Hence, it is felt that Models, Samples and Examples:
• Should be regarded as separate entities in their own right.
• Have a lifecycle which is likely to differ from the applications which they service.
• May be released with installations which install applications, but should be as easy as possible to divorce
from such installations.
• Are unsuited to Repair or Patching by installations.
• Are risky to de-install/remove when applications are removed.

• Should be released holistically.
• Should be available separately from application installations in special cases.
• May suit release in a simple compressed archives (.zip file or self extracting executable say).
Current AVEVA MSI installations attempt to address these requirements by completely removing an installation’s
ability to heal its Models, Samples and Examples. If a new copy is required, the installation must be completely
removed, and then reinstalled. Repairing will not restore Models, Samples or Examples.
Uninstalls are achieved by deleting the root folders where the Models, Samples and Examples were deployed to.
It is important to move them if they are to be retained.
Change Default File Replacement Behaviour

It is possible to alter default file replacement behaviour in circumstances where an MSI installation or Patch is
launched from a command line. Refer to for further information..This is achieved with the REINSTALLMODE
property or the /f command line switch. Otherwise default file replacement rules will apply. Refer to and for
further information.
Default file replacement rules should suit most users.
It is desirable to change file replacement behaviour in situations where the Date/Time stamps of files might not
support the required replacement of files.
Post Deployed .bat files
The .bat files which AVEVA installations deploy and edit are regarded as necessary for the applications to work
and so could be repaired by the installation if they are removed. However they can be edited or replaced post
deployment without risk as long as the files "Created Date" and "Modified Date" is different (this stops an MSI
from overwriting the file).
Pre-Deployed .bat files
It is feasible to replace .bat files before deployment in the case where deployments are staged from Admin
Installations. However the details and issues concerning Admin Installations are beyond the scope of this
manual.
It is also possible to add additional files to an MSI installation but an MSI table editor of some sort would be
required. This is not a trivial option and may well require the services of a professional re-packager. However it
can be accomplished without compromising an installations ability to be patched.
.bat file Shortcuts
All the shortcuts pointing to the .bat files are of the non-advertised or normal type. As such they can be deleted
and edited and will not triggering healing.
Network (Admin) Installations

Administrative Installation Mode is a type of .msi installation which only causes an uncompressed copy of the
original installation to be generated to a specified location (TARGETDIR). It does not install applications, it creates
another installation. Refer to and for further information.
The installation’s media (deployable files) is unpacked into a subfolder beneath the regenerated .msi file, rather
than stored in external .cab files or in .cab files embedded within the .msi file itself. The resultant folder structure
created resembles that which a (Typical) local deployment would create by default.
Administrative installations do not become installed onto the computer which spawned it. They only transform
the source installation into an uncompressed variant of itself during this process.
Create an Administrative Installation Point
To create an admin installation from an installation, start the installation from the Command Window as follows
to display the AVEVA Engineering Administration Point Setup screen:
MSIEXEC /A [Path to MSI File]
Click Next to display the AVEVA Engineering Administration Point Distribution screen.
Enter the location where the Admin Installation is to be created. Clicking Browse displays a window allowing the
user to navigate to the required location.
Click Install to start the installation.
Conversely, the following Command Line will achieve the same result quietly:
MSIEXEC /A [Path to MSI File] /QN TARGETDIR=[Path to Admin Installation]
Issues with Administrative Installation Points

Signing
Newer Windows operating systems have code signing embedded into their security. As such, AVEVA have begun
signing .msi files and .cab files for installations which are not restricted to Windows 10 or older operating
systems.
Unfortunately, the Administrative Installation process recreates and/or alters the source .msi file and
removes .cab files altogether, thus removing any file signatures. Changes to a signed file always invalidates its
signature.
In this release AVEVA have signed all dll's and exe's that are supplied. However in order to cater for installations
where internet access is not permitted/available AVEVA provide a .exe.config file for each exe file that tells the
operating system not to validate the digital signature. By default the installation is set to deploy the .exe.config to
disable the digital signature validation. To enable digital signature validation the command line option
CERTIFICATECHECK=1 should be set.
Using Files within the Source Installation
MSI databases can be authored to allow Features to be installed in the "Will be installed to run from network"
state. AVEVA Installations do not currently support this mode; however it may be made available if requested.
The "Will be installed to run from network" option is otherwise known as run-from-network. In this mode, files
are not copied onto the target computer, but registry, shortcuts and file edits do occur on the target computer,
and they address the programs which reside inside the source installation.
Network Throughput
Admin installations often cross networks more efficiently than large compressed installations. However AVEVA
installations are highly compressed and comply with the recommended file size limits. So Admin Installations are
not recommended purely for deployment purposes. Unless there is a requirement to run programs over a
network, Admin Installations are discouraged.
Advantages of a Network Installation
Once computers address files across a network, it becomes crucial that the files are accessible
whenever required. This then begs questions regarding:
• Network Reliability
• Network Performance
• File Server Reliability
• File Server Performance
• Change Synchronisation
• Change Granularity
Common reasons for storing programs on file Servers are:
• To avoid the network loading of large and un-staggered rollouts.
• To guarantee the user base is working with the same files.
• To prevent tampering with programs and settings.
• To maintain a tradition.
All of these issues are of course resolvable with locally deployed applications
Note: Direct editing of .msi's is discouraged in favour of Transforms (.mst files) because it will invalidate the
installation certificates.
Run AVEVA Engineering from Network Locations

Running programs directly from network locations is discouraged because:
• AVEVA installations have been redesigned to deploy well across networks.
• Network reliability and performance is less of a factor.
• Patch rollback functionality only works with local installations.
However, it is recognised that network based programs suit circumstances where:

• Multiple instances of the same program are required.
• An embedded tradition of working this way exists.
• Change impacts Quality Control systems.
So this information is provided to facilitate successful over network operation.
Definitive instructions on how to run AVEVA programs from network file servers are impractical, given the many
ways in which AVEVA programs can interact with each other and with Project data. Not to mention other
possible permutations.
So the following information is deliberately general and lacking in detail and it is aimed at assisting a highly
skilled readership.
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 2010 C++ Runtimes should be pre-installed.
• .NETFramework Redistributable should be pre-installed.
• The appropriate shortcuts and drive mappings should be provisioned.
Administrative Installation Points
The Files and Folders extracted to an "Administrative Installation Point" are laid out in a fundamentally identical
way to a local installation. Additionally, files which are normally deployed to operating system folders will also be
visible, but will play no functional part unless deployed locally.
Some Configuration files will be incomplete, or have incorrect data in them, as they are not edited until they are
deployed (Locally). These files may require manual editing and concern which Modules, Addins, Addons and
"User Interface Modifications" are loaded.
Patching Administrative Installations
A slightly different Patch is required for an administrative installation than for a local installation, and standard
AVEVA patches target local installations. If such a Patch is applied to an Administrative Installation Point, the
patch will succeed. However, any local installations which have previously been deployed from it will cease to
recognise it as their source installation. So as long as local deployments have not occurred, an Administrative
installation is patchable with an AVEVA patch. Similarly, if programs within the installation are addressed by a
client’s own means, then the Administrative Installation can be patched at any time with impunity. Since in this
event the Installation has not been deployed (Locally) and so only the media state has any effect.
AVEVA patches are supplied inside an executable wrapper. To apply them to an administrative image, the patch
must be extracted and the appropriated command line used. The appropriate command switch is /C which
extracts the contents to the current folder.
Note: Patches cannot be rolled back from Administrative Installation Points. A copy must be made before the
patch is applied, in order to rollback.
Note: Patches cause changes to the .msi file, which invalidates any security certificates applied to the installation
files.
Copy a Local Deployment to a File Server

Installing normally to a local computer and then copying the programs to a network location, as a way
to create a network based installation has several advantages over an "Administrative Installation
Point":
• The fundamental configuration file editing has happened.
• The Local installation need only include the required applications.
Note: Running a normal (Local) installation, and choosing a network drive as a target for the programs will
fail to install. This is because file editing is performed with the local System Accounts credentials, which are
not normally recognised by other computers. Refer to for further information.
Command Line Definable Directories

The following directories can be set on the Command Line, in the same way that Properties are
assigned.
Directory Id Explanation
AVEVA_DESIGN_USER Specifies the AVEVA_DESIGN_USER directory location.

AVEVA_DESIGN_WORK Specifies the AVEVA_DESIGN_WORK directory location.
AVEVA_DESIGN_DFLTS Specifies the DATAxx.x.x\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. Refer to for further
information.
ROOTDRIVE The Partition where All Applications will be targeted (unless application
directories are set). Refer to for further information.
As with Properties, Directories for which the Id's are all uppercase, can be re-defined on a Command
Line. They must also be addressed in uppercase on the Command Line, because Id's are case
sensitive.
e.g. PRODUCTDIR="C:\Some Path with Spaces in it\"
Will make AVEVA Engineering install to:
"C:\Some Path with Spaces in it"
Rather than to:
C:\AVEVA\Engineeringxxxx
Note: There is no space around the equals (=) sign.
Note: The quotes surround the value, and would be unnecessary if the value had no space within it.
Sample Command Lines
A most definitive reference to MSI Command Line arguments can be found, refer to for further information. The
following examples have been tested, but are only intended to demonstrate general Command Line principles.
In Windows 10 and Windows Server 2019 make sure that the command line has been opened using the option
Run as administrator so that the silent install application has the correct User Access Control (UAC).
Example 1: Installing AVEVA Engineering with a custom installation directory and Projects
directory setting an All Users License Server
msiexec /i "Full Path to .MSI file" PRODUCTDIR=D:\ENG141 PROJECT=D:\Projects LICENSETYPE=0
LICENSESERVER=744@LicenseServer /qb!-
Example 2: Installing the product & projects to different locations, setting users writeable areas
to a separate drive, configuring a License Server and not creating Desktop Shortcuts
The installation will run without user intervention and generate a log file in the Users Temp directory.
Installs all Features to the C:\
msiexec /i "Full Path to .MSI file" PRODUCTDIR= "%ProgramFiles%\AVEVA\Engineeringxxxx"
PROJECT=D:\Projects AVEVA_DESIGN_DFLTS=D:\DFLTS AVEVA_DESIGN_USER=D:\USERDATA LICENSETYPE=0
LICENSESERVER=744@LicenseServer DESKTOPSHORTCUTS=0 /qb!- /l %temp%\Engineering.log
Example 3: Removing an Installation
msiexec /x "Full Path to .MSI file" /qb!-
4 Set Up the Windows Environment
Setting up the Windows Environment section describes how to configure the Windows operating
system before running AVEVA Engineering. Following the installation of AVEVA Engineering, the user
should perform the following steps:
• Check the settings for the graphics board: Refer to Windows Control Panel.
• Check the license environment. Refer to Set the License File Location.
• Configure Windows parameters for AVEVA Engineering: Refer to Environment Variables.
• The user can then run AVEVA Engineering by clicking on the AVEVA Engineering shortcut or icon, which will
set up the remaining environment variables required.
Note: In the following instructions it is assumed that AVEVA Engineering has been installed in folder
C:\Program Files (x86)\AVEVA\Engineeringxxx. If it has been installed elsewhere, substitute C:\Program
Files (x86)\AVEVA\Engineeringxxxx with the name of the installation folder.
Windows Control Panel

The Windows Control Panel contains tools that are used to change the way Windows looks and behaves. The
AVEVA Engineering Installation Guide describes how to use Control Panel tools to configure Windows to run
AVEVA Engineering. To open the Control Panel, click Start > Control Panel.
Graphics Card Settings
The user should set the display to a resolution of at least 1024 x 768 (1920 x 1200 recommended) and the colour
depth to True colour or 16.7 million colours.
To set the display settings, open the Control Panel. Select Appearance and Personalization, Display, Change
display settings, Advanced settings. Make the appropriate selections for the graphics card.
Run AVEVA Engineering from a Command Window
The user can run AVEVA Engineering from a Command window rather than using the Start/Programs
menu. To do this the user must set the PATH variable to include the folder where AVEVA Engineering is
installed.
• Open the Control Panel.
• Select System and Security, System and click the Advanced system settings.
• Click Environment Variables.
• Edit the system variable Path to add the folder, for example, C:\Program Files (x86)\AVEVA\Engineeringxxxx
to the list of folders in the Path variable.
Set Up the Windows Environment
Once the Path variable includes the folder, the user can run AVEVA Engineering by typing Engineering at a
command prompt.
Set the License File Location

Before the user can use AVEVA Engineering, the AVEVA Licensing System must be set up and connected, refer to
the AVEVA Licensing System Guide. A license file should be requested from AVEVA Customer Services.
Environment Variables
AVEVA Engineering uses Windows Environment variables to locate folders containing AVEVA Engineering system
files and users project data. This allows the user to locate these folders anywhere on the file system. The default
location for AVEVA Engineering system files is C:\Program Files (x86)\AVEVA\Engineeringxxxx, unless the default
location was changed during the installation.
AVEVA Engineering is supplied with a file evars.bat which sets default values for the environment variables so
that they point to the folder structure as installed. It also sets the PATH variable to include the
AVEVA_DESIGN_EXE folder containing AVEVA Engineering executables.
The user may need to modify this file to reflect the folder structure of their own installation. The following is a
list of the variables the user may need to reset, with a brief description of each one and the default setting.
Note: all environment variables must be entered in UPPERCASE.
Search Paths of Folders Containing Spaces
Search paths of folders can contain spaces, by using a semicolon as the separator between folders, for
example:
set PMLUI=C:\Local AVEVA Engineering\Appware;M:\Project AVEVA Engineering\Appware;
a:\Company AVEVA Engineering\Appware
Note: that in order to define an environment variable that contains just one item including spaces, it must
explicitly include a final semicolon. For example:
set PMLUI=C:\Local AVEVA Engineering\Appware;
Length of Search Path Environment Variable
The lengths of AVEVA Engineering search path environment variables can be up to a maximum of 5120
characters.
Recursive Expansion of Environment Variables
An environment variable defining a search path can itself contain references to other environment
variables. For example:
set MPATH=%ROOT%\Standard Version;%ROOT%\Update Version
set ROOT=C:\Program Files (x86)\AVEVA; (note final semicolon)
Then on AVEVA Engineering:
*$m%MYPATH%\mac
Will check in turn for:
C:\Program Files (x86)\AVEVA\Standard Version\mac

C:\Program Files (x86)\AVEVA\Update Version\mac
System Environment Variables
The following environment variables refer to the location of AVEVA Engineering system files.
AVEVA_DESIGN_EXE Executable folder
C:\Program Files (x86)\AVEVA\Engineeringxxx
PMLUI Application User Interface folder (PML 1)
C:\Program Files (x86)\AVEVA\Engineeringxxxx\PMLUI
PMLLIB Application User Interface folder (PML 2)
C:\Program Files (x86)\AVEVA\Engineeringxxxx\PMLLIB
AVEVA_DESIGN_DFLTS Applications defaults folder
C:\Program Files (x86)\AVEVA\Plant\PMLUI\dflts
User Environment Variables
The following environment variables refer to the location of users AVEVA™ E3D Design folders. Users
must have write permission to these folders.
AVEVA_DESIGN_WORK Temporary AVEVA™ Engineering work file folder
AVEVA_DESIGN_USER Application Users save/restore setup area (or the users 'home' folder)
AVEVA_DESIGN_REP_DIR AVEVA Engineering Applicationware Report Input and Output folder.

C:\Program Files (x86)\AVEVA\Engineeringxx\PMLUI\reports
AVEVA_DESIGN_DFLTS Applications defaults folder.

Project Environment Variables
For each AVEVA Engineering project, the following environment variables must be set. For example, for
a project ABC:
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
AVEVA Engineering is installed with sample project data. AVEVA Engineering Project Environment variables for
these projects are set in evars.bat.
Customise AVEVA Engineering Start-Up

There is a batch (.bat) file supplied in C:\Program Files (x86)\AVEVA\Engineeringxxxx called engineering.bat
which allows entry into AVEVA Engineering.
The user can run AVEVA Engineering using this batch file in any of the following ways:
• Use the shortcut in the Windows Start menu, Start > All Programs > AVEVA > Engineer > AVEVA
Engineeringxxxx
• The user can create a shortcut on their desktop to run their batch file. With the cursor in the desktop area,
right-click and select New > Shortcut. This shows a sequence of dialogs to help the user create the shortcut.
Type in the location of engineering.bat, for example:
C:\Program Files (x86)\AVEVA\Engineeringxxx\engineering.bat
then click Next and give the shortcut a name.
click Finish.
The user should now be able to double-click on the shortcut icon to enter AVEVA Engineering.
Note: Shortcuts can also be created during installation by checking the Create Start Menu Shortcuts check
box on the Initial Configuration screen.
• If the user has C:\Program Files (x86)\AVEVA\Engineeringxxx\ (the path name for the engineering.bat file) in
their PATH environment variable, just type engineering in a command window to execute the batch file.
• Otherwise, navigate to the folder where the batch file is stored and type engineering or engineering.bat.
Create User Batch File to Run AVEVA Engineering

The user can set up their own batch files to run AVEVA Engineering. For example, the user may want to run
design checking utilities every night, or update batches of drawings overnight.
Begin by creating a batch file, for example, runAVEVAEngineeringmacro.bat.
Type the following line into this file:
C:\Program Files (x86)\AVEVA\Engineeringxxxx\engineering.bat TTY APS SYSTEM/XXXXXX /ALL $M/
mymacrofile
Where:
• TTY tells AVEVA Engineering not to start the AVEVA Engineering GUI. This gives command line only
operation.
• APS is the project name.
• SYSTEM/XXXXXX is the AVEVA Engineering username/password to be used when running the command
macro
• /ALL selects the required MDB
• mymacrofile is the pathname of an AVEVA Engineering command macro, containing the commands that the
user wants to execute in AVEVA Engineering.
In this example, running runAVEVAEngineeringmacro.bat will enter AVEVA Engineering in project APS, as user
SYSTEM/XXXXXX, in MDB /ALL, and run the AVEVA Engineering command macro mymacrofile.
Run AVEVA Engineering in Batch

AVEVA Engineering creates a separate Console process to manage the command-line input/output for all
modules. When AVEVA Engineering is invoked from a .bat file, processing of this file resumes as soon as the user
leaves MONITOR ‑ even though the user is still using AVEVA Engineering.
To help manage this situation, PDMSWait.exe is distributed as part of AVEVA Engineering and can be used to
make an AVEVA Engineering script wait for AVEVA Engineering to complete before continuing.
PDMSWait uses Windows facilities to wait for an event triggered by PDMSConsole when AVEVA Engineering
finishes. Because the user can be running more than one AVEVA Engineering session on any one computer, both
PDMSWait and PDMSConsole look for an environment variable PDMS_CONSOLE_IDENTIFIER before doing this.
The user can set PDMS_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 use the process number,
accessible as $$.
Example
set PDMS_CONSOLE_IDENTIFIER=%RANDOM%
call %AVEVA_DESIGN_EXE%\Engineering
call %AVEVA_DESIGN_EXE%\pdmswait
echo Returned to .bat at %TIME%
This will start AVEVA Engineering, then wait until it has finished before resuming the script.
5 Language Support
AVEVA Engineering uses Unicode for character storage throughout, with the exception of data migrated from
older versions of PDMS. 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.
There are aspects of the Unicode standard that are not yet implemented. AVEVA Engineering currently
handles the following correctly:
• Left to Right languages; and therefore not, for example, Arabic and Hebrew
• Pre-composed characters; for example, the single character á but not the combiners a + ' => á
• Upper and lower casing of characters, where both cases have the same number of bytes
Setting AVEVA Engineering Default Text Format

By default all sequential text files read by AVEVA Engineering will be expected to be in UTF-8 format with a Byte
Order Mark (BOM) present to identify them. This includes PML files, Datal files etc. Similarly by default all
sequential text files written by AVEVA Engineering will be in Unicode UTF-8 format with a BOM present.
A simple command line 'transcoder' is also supplied; this may be used in some applications to convert files to a
different encoding. This is installed with AVEVA Engineering and is called transc.exe; further details can be found
using its -h command line option.
In order to change these defaults, environment variables are available for users to modify the way
AVEVA Engineering handles sequential text files:
CADC_LANG Specifies the file encoding for reading external files which do not have a Unicode
BOM present. If the variable is unset, this defaults to LATIN-1. Files with the
following Unicode BOMs will be translated to UTF-8 on reading: UTF-16 little-
endian, UTF-16 big-endian, UTF-32 little-endian, UTF-32 big-endian.
CADC_LANG_NEW Specifies the file encoding for new files written. If the variable is unset, the default
is Unicode UTF-8 format with a BOM present.
These variables may be set to a variety of values:
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
Language Support
LATIN1 ISO8859-1
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)
Prepare AVEVA Engineering For Legacy PDMS Databases

These settings should not be required for new projects but must be set correctly in order to use 'legacy'
databases. This is particularly important if they are to be reconfigured to Unicode as the transcoding will be
based on these settings.
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 LATIN CYRILLIC Bulgarian, Byelorussian, English, Macedonian, Serbo-
Croatian, Ukrainian, Russian
PROJECT MBCHARSET JAP Japanese
PROJECT MBCHARSET KOR FILE /<font filename> Korean
PROJECT MBCHARSET CHI Simplified Chinese

PROJECT MBCHARSET TCHIN FILE /<font filename> Traditional Chinese
Run AVEVA Engineering Under Windows
Spaces in Windows Pathnames

To run macros with spaces in the filenames, the user must enclose the filename in quotes, without a
leading slash. For example:
$m'c:\Program Files\Macros\space.mac' arg1 arg2
Due to the way in which AVEVA Engineering parses its command lines, this format is also recommended for use
with filenames containing Asian characters.
Windows Parameters
The following setting can be used to improve performance when repositioning windows in AVEVA E3D
Design. These are optional Windows Parameter settings.
• Open the Control Panel. Select System and Security > System, then select Advanced system settings. Click
the Advanced tab and the select the Performance Settings option to display the Performance Options
window. Uncheck Show Window Contents While Dragging.
6 Structure of AVEVA Engineering on .NET
The AVEVA Engineering UI uses the Microsoft .NET Framework environment including the latest WinForms/
Infragistics based user interface components. Using the state-of-the-art Infragistics technology enables docking
windows and provides a robust foundation for the future provision of standard application programming
interfaces.
Overview
Overview describes the overall structure and components of the AVEVA Engineering .NET installation, and the
environment necessary to run it. Each AVEVA Engineering GUI module now consists of a .NET module, .NET
interface and addin assemblies and native dlls plus some other shared components including 3rd party controls
from Infragistics. The .NET components are private assemblies installed under the root directory
%AVEVA_DESIGN_EXE%.
AVEVA_DESIGN_EXE
As before the environment variable %AVEVA_DESIGN_EXE% is used to locate the executable on module switch. It
is also used to locate attlib.dat (attribute and noun definitions), message.dat (message definitions), desvir.dat
(schema definition) etc. Normally AVEVA Engineering is started from engineering.bat which is located in the
user’s %PATH%. Both %AVEVA_DESIGN_EXE% and %PATH% should include the install directory.
UI Module Structure
Each UI module is now structured in the same way. The basic structure for each module looks like this.
where all components are installed in the %AVEVA_DESIGN_EXE%. directory. So, when running a AVEVA
Engineering GUI module %AVEVA_DESIGN_EXE% is used to locate the executable, .NET loading rules are used to
Structure of AVEVA Engineering on .NET
load the interface assemblies and Win32 DLL loading rules are used to load the native components (and other
Win32 DLLs on which Aveva.Core.dll depends).
.NET Loading Rules

All the .NET assemblies are Private assemblies and are installed under %AVEVA_DESIGN_EXE% (Assembly Base
directory) or a subdirectory below. .NET loads private assemblies from the base directory of the application. If it
can’t find the private assembly here it uses the applications configuration file called <module>.exe.config to see
whether it contains any path hints. Path hints are stored in the <probing> element.
Native DLLs
Native dlls are loaded using Win32 DLL loading rules. These are:
• The directory from which the importing component loaded.
• The (application's) current directory (where 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 in evars.bat located in the
installation directory. Having different versions of AVEVA_DESIGN_EXE in the %PATH% may cause
System.IO.FileLoad exceptions where components are loaded from different directories.
These rules apply to pdms.dll and all dependencies.
Components
All components are installed in the %AVEVA_DESIGN_EXE% directory including .NET interfaces and addins,
Infragistics assemblies and native components.
7 Tag Management Register Installation
The Tag Management Register must be installed and configured before the TMR service can be used. If installing
an new engineering build then a matching TMR installation is required.
Launch TMRSetup.msi, the AVEVA Tag Management Register Setup Wizard activates at this point and guides the
user through the installation of the service. Click Cancel to terminate the setup or Next to display the End-User
License Agreement window.
The user must read the End-User License Agreement and then click to select the I accept the terms in the
License Agreement check box to activate Next.
Note:
If the user does not select the check box, Next will not activate and the installation cannot continue.
Tag Management Register Installation
After click Next the Destination Folder window is displayed, the default installation and its location is displayed.
Click Change to navigate to another location, click Back to return to the End-User License Agreement window or
click Next to display the Ready to install AVEVA Tag Management Register window.
Click Install to proceed with the installation, click Back to return to the previous window or click Cancel to
terminate the installation.
The Installing AVEVA Tag Management Register widow is displayed.
The Status taskbar shows the progress of the installation, if required the installation can be terminated click
Cancel and then click Yes to cancel the installation. Once the TMR service has been successful installed, a
window is displayed confirming the installation of the TMR Service.
Click Finish, the TMR shortcut is displayed on the desktop.
Click the TMR shortcut, the TMR service manager window is displayed, use the functionality to install and
manage TMR service.
Click Install, the Install/Configure window is displayed, use the functionality to configure the TMR service (To
install the TMR service with https, refer to TMR Service - HTTPS Configuration).
Service name: Enter a relevant name for the service.

URL:Enter the URL the TMR service will be available, use the format: http://<HostName>:PortNumber.
Note:
Host name in most cases will be the machine name where service is being installed, PortNumber can be any four
digit port number that is not already in use, (no two services can run on the same port number, the port number
by default is 7060). The URL can be configured to use HTTPS scheme, refer to TMR Service - HTTPS Configuration.
AD groups: Enter the name of an active directory group (members allowed access to the TMR service).
AD users: Enter the name of the active directory users (in addition to the AD groups).
Config folder: Enter or browse to the location of the TMR service configuration file. The service configuration file
Appsettings.json is kept in this folder. If SQL lite db is selected as the datasource for the service then SQL lite db
file is also be placed in this folder (folder is created if it does not exist).
Note:
Avoid file paths with spaces.
Db type: Select the datasource for the TMR service, in the production environment a Sql Server should be
selected, SQL lite can be selected for test and development environment as recommended in the Install/
Configure window.
Sql server - If Sql server is selected as the datasource for TMR service then some connection parameters are
required (refer to SQL Server Configuration) to configure the pre-requisites for this section.
Name/Address - the name/address of the SQL server for example - AUMELLCU0750\SQLEXPRESS17.
Admin username - enter the login name of a SQL server login that has privilege's to create a database.
Admin password - enter the SQL server authentication password of the admin user.
Note:
The admin username and password is not stored it is only used once to create the service database.
Connection username - enter the Login name of a SQL server login that will be used to read/write to service
database.
Note:
This user is created in SQL Server if it does not already exist. It is strongly recommended that an existing
username is provided as per the policy of this interface. If an existing user is used then an extra step needs to be
executed in SQL Server Management studio to associate the user with service database, this step should be
executed after an successful install and before starting the service, refer to Granting Access to an Existing SQL
Server User.
Connection password - enter the SQL server authentication password of the connection user. If an existing
username is used then the entered password must be exactly the same as it is in the SQL Server for the existing
username.
Note:
The Connection username and password is stored as encrypted string in the appsettings.json config file
Connection encrypt - Only check this check box if TLS Encryption between Service and SQL Server is required.
For this option to work some configuration for SQL Server is required, refer to Enable TLS Encryption between
Service and SQL Server.
Upon successful installation, the service is available for selection in the TMR service manager window.
Select the TMR service in the TMR service manager window, click Start to start the selected TMR service, if
successful the status of the TMR service is displayed as 'Running'
If the service does not start, click Event Log to troubleshoot any issues.
To refresh the TMR service, the TMR service manager window, click Refresh.
To uninstall the TMR service select the service in the TMR service manager window, click Uninstall.
To stop the TMR service select the service in the TMR service manager window, click Stop.
To test a connection select the TMR service in the TMR service manager window , click Test connection
(Swagger page for the URL).
To edit the logon details, select the TMR service in the TMR service manager window then click Edit logon
details to display the Edit Login Details window use to edit the login details.
Connecting a project to the TMR Service

Before logging into the configuration module, the system administrator needs have access to a writable
configuration database as the settings URL and Project Name are saved and retrieved from the config database.
Once service is installed and running then it’s URL needs to be added to the project from config module.
Note:
If the project name needs to modified log in into the Lexicon module navigate to Home > Standards
modify
the existing TMR ProjectNameKey and save the change.
Once the modification has been done copy both 9100 and 9101 files from the databases folder in the AVEVA
Administration installation location and replace them in the AVEVA Engineering installation's databases folder,
so that the url and project name can be given under the settings.
Right Click Menu

Functionality is also available from the right-click menu:
Start Starts the selected service.

Stop Stops the selected service.
Restart Restarts the selected service.

Edit Configuration Edits the configuration file of the selected service.
Edit Logon Details Edits the logon details for the selected service.
Uninstall Uninstalls the selected service.
8 SQL Server Configuration
In the production mode, the TMR service must use the SQL server as its data source.
1. Download SQL server express from . The SQL Server 2019 window is displayed.
2. Select the Basic installation type

3. Upon a successful installation, make a note of the SQL server instance name as highlighted below.
SQL Server Configuration
4. Install SQL Server Management Studio (SSMS) (that is compatible with SQL server 2019, if not already
installed).
Note:
Installing SSMS is optional but it can be helpful when troubleshooting any connectivity issues for the SQL
server and also aids the creation of logins required by the TMR service.
5. Download the SSMS installer and install, upon successful installation the setup completed window is
displayed.
6. Run SQL Server management studio, the Connect to Server window is displayed
7. Enter the server name (which is made up of two parts – the instance name – step three and the machine
name for example machine name: INHYZD311and the SQL Server Instance Name SQLEXPRESS01).
8. Click Connect.
9. From the Object Explorer of the Microsoft SQL Server Management Studio window, select the server name.
10. Right click and select Properties to display the Server Properties window.
11. From the Select a Page pane of the Server Properties window, select Security.
12. Select the SQL Server and Windows Authentication mode radio button.
13. Click OK.
14. A restart message is displayed, click OK.
15. From the Object Explorer, right click on the server name, select Restart.
16. Once the server has restarted, from the Object Explorer expand Security > Logins folder.
17. Right click sa login and select Properties to display the Login Properties.
Note:
Inbuilt 'sa' user has elevated privileges, hence is should be used with caution. In the production environment
the 'sa' user should not be used, database admin should setup a different user that has privileges to create a
database and can provide other users access to this database.
18. From the Select a page pane of the Login Properties window, select the Status page.
19. Select the Enabled radio button.

20. From the Select a page pane of the Login Properties window, select General.
21. Set the password and confirm the password (this login can be used as the Admin login for TMR service by
entering sa in the Admin username and the password).
22. From the Objects Explorer pane of the Microsoft SQL Server Management Studio window, right click Logins.
23. Select New Logins.
24. From the Select a page pane of the Login New window, select General.
25. Select the SQL Server Authentication radio button.
26. In the Login name field enter a login name for example: UserForTMR.
27. Set a password and confirm the password (this login can be used as the Connection login for TMR service by
entering the chosen username for example: UserForTMR in the Connection username and the Connection
password).
9 Enable TLS Encryption between Service
and SQL Server
Note:
This configuration is for a production environment where a customer requires Transport Layer Security (TLS)
encryption for service to SQL Server communication.
The connection between the TMR SQL Server and TMR Service can be configured to use TLS to encrypt data that
is transmitted across a network. TLS can be used for server validation when a client connection requests
encryption.
To vouch for the identity of the server machine and the SQL Server instance a certificate from a public
certification authority is to be used. Such server validation requires that the certificate to be installed in the
trusted root certificate store of the computer on which the client application is running. Encryption with a self-
signed certificate is possible , but a self-signed certificate offers only limited protection.
Characteristics of Certificate to be used for TLS encryption with a SQL Server

• A certificate must be issued for Server Authentication
• The name of the certificate should be FQDN of the computer
• The certificate must be in either the local computer certificate store or the current user certificate store.
• The SQL Server Service Account must have the necessary permission to access the TLS certificate.
• The certificate must be created by using the KeySpec option of AT_KEYEXCHANGE.
• The Subject property of the certificate must indicate that the common name (CN) is the same as the FQDN.
Command to Generate a Self Signed Certificate

1. Substitute the FQDN of the server machine with the command displayed below and execute the command
using powershell as an administrator.
New-SelfSignedCertificate -Type SSLServerAuthentication -Subject “CN="<FQDN of
computer>” -FriendlyName ‘SQL Server TLS Certificate’ -DnsName
“$env:COMPUTERNAME”,’localhost.’ -KeyAlgorithm ‘RSA’ -KeyLength 2048 -Hash ‘SHA256’
-TextExtension ‘2.5.29.37={text}1.3.6.1.5.5.7.3.1’ -NotAfter (Get-
Date).AddMonths(36) -KeySpec KeyExchange -Provider ‘Microsoft RSA SChannel
Cryptographic Provider’ -CertStoreLocation Cert:\LocalMachine\My
The certificate can then be exported from the local machine certificate store, which can then be used later to
import in the client machine trusted certificates store.
Enable TLS Encryption between Service and SQL Server
Configure SQL server

The server an be configured as below to force encrypted connections:
1. In SQL Server Configuration Manager, expand SQL Server Network Configuration, right-click Protocols for
<server instance>, and then select Properties.
2. In the Protocols for <instance name> Properties window, from the Certificate tab, select the desired
certificate from the Certificate drop down then click OK.
3. From the Flags tab, in the ForceEncryption field, select Yes then click OK.
4. Restart the SQL Server service.
TMR Service(Client) side configuration

1. For an SQL Server installation, from the Install/Configure window, click to check the Connection Encrypt
checkbox.
2. Install the certificate in the trusted root certificate of the machine in the client machine
10 TMR Service - HTTPS Configuration
Note:
This configuration is for production environment where a customer might want to expose the TMR API on a
HTTPS endpoint.
The following describes the steps required to configure SSL for the TMR Service while hosting on http.sys. A valid
X.509 certificate must be obtained (for testing a self signed certificate is required).
Generate a Self Signed Certificate

The following procedure must be carried on the machine where the AVEVA TMR Service is installed and running.
1. Click the Windows icon on the taskbar, search for Windows PowerShell and Run as administrator.
2. In command prompt type hostname and then press Enter to obtain the hostname.
3. Customize the hostname with your hostname.
4. Run the command $cert = New-SelfsignedCertificate -certstorelocation
cert:localmachine\my -dnsname "hostname" to create a self signed certificate and assign to a variable
$cert.
5. Run $cert command to see the created certificate with the Thumbprint and Subject details
6. Create a variable with the desired password $secPassword = ConvertTo-securestring -string
'password!123' -Force -AsPlainText.
7. Run the command $certPath = "Cert:\localMachine\my\$($cert.Thumbprint)" to store the certificate details
to a variable.
8. Export the certificate to the output folder, Export-PfxCertificate -Cert $certPath -Filepath
D:\Certificate\cert.pfx -Password $secPassword, a cert.pfx certificate is created in the filepath
D:\Certificate\cert.pfx.
Install SSL Certificate to Personal Certificates store in the server

machine(where the TMR service is running)
1. Right click the generated pfx file.
2. Select Install PFX.
3. Select Local Machine, then click Next.
4. Click Next, enter the password.
5. Click to check the Mark this Key as Exportable checkbox.
TMR Service - HTTPS Configuration
6. Click Next.
7. Click Automatically Select the certificate store.
8. Click Next then Finish.
9. Click OK.
Installing SSL Certificate to Trusted Root Certification Authorities store in

the client machine
1. Right-click the generated pfx file then select 'Install PFX'.
2. Select Local Machine, then click Next.
3. Click Next, then enter the password.
4. Click to check the Mark this Key as Exportable checkbox.
5. Click Next.
6. Click Place all certificates in the following store then click Browse.
7. Select Trusted Root Certification Authorities then click OK.
8. Click Next then Finish.
9. Click OK.
Bind the SSL Certificate to the TMR service port number

1. From command prompt, run the following command to register the X.509 certificate on the machine where
TMR Service is installed.
netsh http add sslcert ipport=<IP>:<PORT> certhash=<THUMBPRINT> appid="{<GUID>}"
Example:
netsh http add sslcert ipport=10.2.1.21:443
certhash=b69e312e5776c534e60a89a4ec77c83336209836 appid="{9412ee86-c21b-4eb8-bd89-
f650fbf44931}"
Note:
Use this command if need to delete the certificate registration for any reason : netsh http delete
sslcert ipport=<IP>:<PORT>
GUID for the TMR Service is "1dd51bb7-74be-4a78-8f0a-bfe2332a0bc7"

2. Run netsh http add urlacl url=<URL> user=<USER> command to pre-register the url prefix on the
server.
Example : netsh http add urlacl url=http://inhydd1491:6800/ user=company name\user name
3. Carry out the following steps to install the TMR service, modify the URL to use https instead of http:
4. From the TMR service manager window, start the service.
The service page is displayed.
Note:
If the certificate is not added to the trusted root certification authorities in client machine the service page is
displayed as shown below.For the purposes of this guide a self signed certificate is used, hence the page is
displayed with a certificate error "ERR_CERT_AUTHORITY_INVALID".
Under Advanced prompts for login, click Continue.
TLS configuration for multiple TMS service on the same machine using same
certificate
Repeat the steps as above, change the port number during the service installation and use that port while
binding the ssl certificate to the port step.
Alternatively generate self signed certificate using OpenSSL
1. Download openssl : http://code.google.com/p/openssl-for-windows/downloads/detail?
name=openssl-0.9.8k_X64.zipF.
2. Follow the steps detailed on https://www.ibm.com/docs/en/api-connect/2018.x?topic=overview-
generating-self-signed-certificate-using-openssl to create a self signed certificate.
a. Run openssl req -newkey rsa:2048 -nodes -keyout key.pem -x509 -days 365 -out certificate.pem
b. For openssl cnf error change command:openssl req -newkey rsa:2048 -nodes -keyout key.pem
-x509 -days 365 -out certificate.pem -config "C:\openssl\ssl\openssl.cnf".
3. Install the certificates to localsystem/personal store.
Alternatively, follow the steps detailed on https://docs.microsoft.com/en-us/powershell/module/pki/new-
selfsignedcertificate to generate a self signed certificate.
11 Exposing an instance of SQL server to be
used by networks users
1. Open the SQL Server Configuration Manger.

2. Navigate to SQL Server Network Configuration and expand.
3. Select Protocols for the server name, in this example - SQLEXPRESS01.

4. Ensure the TCP/IP protocol is enabled – right click TCP/IP and click enable, the following warning is
displayed. Click OK.
5. Navigate to SQL Server Services to display the available services.

6. Select the service, right click Properties.
Exposing an instance of SQL server to be used by networks users
7. Change the start mode to Manual and start the service (ensure the state is running).
8. Navigate to SQL Server Services, right click the SQL Server <instance name>, click Restart.
12 Granting Access to an Existing SQL
Server User
1. From the Microsoft SQL Server Management Studio window, open the Object Explorer.
2. Expand Security then Logins
3. Right click UserForTMR, then select Properties the Login Properties – UserFor TMR window is displayed.
Granting Access to an Existing SQL Server User
4. From the Select a page pane of the Login Properties – UserForTMR window, select User Mapping.
5. Click to check the check box in the Map column for the database to which access has to be granted.
Granting Access to an Existing SQL Server User
6. Click to check the db owner check box to give the user full access.
13 TMS Project Upgrade to TMR
By default, a new project starts as a non-Tag Management project, the administrator must set the TMR URL to
make it Tag Management enabled and restart the Configuration module.
Use the following procedure to upgrade an existing Tag Management System project to be compatible with TMR.
Step one is optional but recommended.
1. Remove the working and consumer extracts for the Tag management master database, for example – the
working and consumer extracts in the ATP project are displayed below.
Note:
Before making any modifications to the project ensure that a DICE check has been run and there are no
issues reported.
2. Modify the team membership of all users that need to create tags in AVEVA Engineering (this provides the
tag creating users write access to the Tag management system master database. (For example: in the ATP
project INST.ENG user's team membership needs to be modified so that INST.ENG user is member of
TMSRLSD team. In the ATP project the TMSRLSD team is the owner of UDE_TMS_RLSD database which in
Engineering 15.7 is set as the Tag management system master database).
TMS Project Upgrade to TMR
3. Modify the MDBs that are used to login into AVEVA Engineering for purpose of tag creation. These MDBs
need to have Tag management system master database as the first Engineering database in the MDBs. This
change is required to ensure that all new tags are created in the Tag management system master database,
as TMR management business logic will create any new tags in first writable Engineering database. Taking
the ATP project as an example, UDE-ENG MDB will need to be modified so that UDE_TMS_RLSD is the first
database in the MDB.
TMS Project Upgrade to TMR
4. Install the TMR service and connect to project, refer to the Tag Management Register Installation for further
information.
5. Run the upgrade utility from configuration module to synchronize the DABACON project tags with the TMR.
6. Carry out an optional cleanup:
a. Remove MDBs specific to the TMS for example: in ATP project "UDE_TMS_RLSD" and "UDE_TMS_WKK"
MDBs can be deleted.
b. Remove users specific to the TMS for example: in ATP project "TAGS.ADMIN" user can be deleted.
Note:
An upgrade of non Tag Management Service enabled project to be TMR enabled is not supported at this
time.

Aveva Unified

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Aveva Unified

Uploaded by

Copyright:

Available Formats

AVEVA™ Engineering 15.

AVEVA Engineering Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Set Up the Windows Environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Run AVEVA Engineering Under Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Structure of AVEVA Engineering on .NET. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Tag Management Register Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

SQL Server Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Enable TLS Encryption between Service and SQL Server. . . . . . . . . . . . . . . . . . . . . . . . 80

TMR Service - HTTPS Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Exposing an instance of SQL server to be used by networks users. . . . . . . . . . . . . . . . 90

Granting Access to an Existing SQL Server User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

TMS Project Upgrade to TMR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

A PassMark ® Rating of 1600 or 2000 for mobile computers is recommended.

RAM 32 GB of high speed RAM.

File System NTFS.

SEE Electrical 3D Panel+ Requirements

AVEVA Licensing System

AVEVA Flex Licensing

ValidValidation.xml Runs validations in the ETAPExportTrans.xslt file.

ValidValidation.xml Runs validations in the ETAPExportTrans.xslt file.

Microsoft .NET Framework Installation

Click Yes to continue installation of the the application.

Click Next to return to the AVEVA Engineering setup.

Click Finish to exit the screen and installation.

- Feature will be installed (Locally), but not all sub-Features will.

- Feature will be unavailable (Not Installed), as will all descendants.

Clicking a box displays a drop-down menu.

Clicking Reset will de-select all currently selected features.

Click Finish to exit the window and installation.

Click Finish to exit the Setup Wizard.

SEE Electrical 3D Panel+

Change, Repair and Remove

Modified New and Removed Files

Models, Sample Data and Example Projects

• Are risky to de-install/remove when applications are removed.

Change Default File Replacement Behaviour

Network (Admin) Installations

Issues with Administrative Installation Points

Run AVEVA Engineering from Network Locations

However, it is recognised that network based programs suit circumstances where:

Copy a Local Deployment to a File Server

Command Line Definable Directories

AVEVA_DESIGN_USER Specifies the AVEVA_DESIGN_USER directory location.

Windows Control Panel

Set the License File Location

C:\Program Files (x86)\AVEVA\Standard Version\mac

AVEVA_DESIGN_REP_DIR AVEVA Engineering Applicationware Report Input and Output folder.

AVEVA_DESIGN_DFLTS Applications defaults folder.

Customise AVEVA Engineering Start-Up

Create User Batch File to Run AVEVA Engineering

Run AVEVA Engineering in Batch

Setting AVEVA Engineering Default Text Format

Prepare AVEVA Engineering For Legacy PDMS Databases

PROJECT CHARSET LATIN 1 (default) Danish, Dutch, English, Faroese, Finnish,

PROJECT MBCHARSET CHI Simplified Chinese

Spaces in Windows Pathnames

.NET Loading Rules

The Installing AVEVA Tag Management Register widow is displayed.

Click Finish, the TMR shortcut is displayed on the desktop.

Service name: Enter a relevant name for the service.

Connecting a project to the TMR Service

Right Click Menu

Start Starts the selected service.

Restart Restarts the selected service.