AVEVA Instrumentation

Installation
User Guide
AVEVA Solutions Limited

Disclaimer
AVEVA Instrumentation provides instrument sizing calculations for estimation purposes only, end users of the
software should not rely on the calculations produced by the software for design purposes. End users should seek
the advice of certified equipment suppliers prior to specifying or purchasing equipment.

To the fullest extent permissible at law:

a) AVEVA does not warrant that the use of the AVEVA software will be uninterrupted, error-free or free from viruses;

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

c) AVEVA's total liability in contract, tort (including negligence), or otherwise, arising in connection with the
performance of the AVEVA software shall be limited to 100% of the licence fees paid in the year in which the
customer's claim is brought.

In the event of any conflict between the above clauses and the analogous clauses in the software licence under
which the AVEVA software was purchased, the clauses in the software licence shall take precedence.

Copyright
All intellectual property rights, including but not limited to, copyright in this manual and the associated software,
(including source code, object code, and any data) belongs to or is validly licensed by AVEVA Solutions Limited or
its subsidiaries.

All rights are reserved to AVEVA Solutions Limited and its subsidiaries. The information contained in this document
is commercially sensitive, and shall not be copied, reproduced, stored in a retrieval system, or transmitted without
the prior written permission of AVEVA Solutions Limited. Where such permission is granted, it expressly requires
that this Disclaimer and Copyright notice is prominently displayed at the beginning of every copy that is made.

The manual and associated documentation may not be adapted, reproduced, or copied, in any material or
electronic form, without the prior written permission of AVEVA Solutions Limited. The user may also not reverse
engineer, decompile, copy, or adapt the associated software. Neither the whole, nor part of the product described in
this publication may be incorporated into any third-party software, product, machine, or system without the prior
written permission of AVEVA Solutions Limited, save as permitted by law. Any such unauthorised action is strictly
prohibited, and may give rise to civil liabilities and criminal prosecution.

The AVEVA products described in this guide are to be installed and operated strictly in accordance with the terms
and conditions of the respective licence agreements, and in accordance with the relevant User Documentation.
Unauthorised or unlicensed use of the product is strictly prohibited.

Copyright 2000 to current year. AVEVA Solutions Limited and its subsidiaries. All rights reserved.

The AVEVA Instrumentation user interface is based on the Microsoft® Office Fluent™ user interface.

Trademarks
AVEVA and Tribon are registered trademarks of AVEVA Group plc or its subsidiaries. AVEVA product names are
trademarks or registered trademarks of AVEVA Solutions Limited or its subsidiaries. Unauthorised use of
trademarks belonging to AVEVA Group plc or its subsidiaries is strictly forbidden.

Microsoft® Office Fluent™ user interface. Fluent is a trademark of Microsoft Corporation and the Fluent user
interface is licensed from Microsoft Corporation. The Microsoft Office User Interface is subject to protection under
U.S. and international intellectual property laws and is used by AVEVA Solutions Limited under license from
Microsoft.

DevExpress® redistributables are used by AVEVA under license from Developer Express Inc. Copyright © 2000-
2014 Developer Express Inc.

AVEVA Solutions Ltd, High Cross, Madingley Road, Cambridge, CB3 0HB, United Kingdom.
Installation User Guide

Revision Sheet

Date Version Comments / Remarks

March 2012 12.1 Copyright added to all pages.
March 2013 12.1 SP1 Updates incorporated
August 2013 12.1 SP2 Updates incorporated
July 2014 12.1 SP3 Updates incorporated
March 2016 12.1 SP4 Updates incorporated
December 2016 12.1.SP5 Updates incorporated
April 2017 12.1.SP6 Updates incorporated
February 2019 12.2 Updates incorporated
January 2020 12.2 Fix 2 Updates incorporated
June 2020 12.2.SP1 Updates incorporated
August 2020 12.2.SP2 Updates incorporated
February 2021 12.2.SP3 Updates incorporated
Installation User Guide
 Instrumentation Installation User Guide

Instrumentation Installation User Guide

Contents Page

Installation
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
Database Systems Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
Project Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
Guide Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1

Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1
Client Computer Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1
Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1
Microsoft .NET Framework 4.8 Runtime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1
Project Packager and Microsoft’s Shared Management Objects (SMO). . . . . . 2:1
AVEVA Instrumentation Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:2
Installing a Full Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:2
Installing a Partial Release (Fix Release) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:3
Unattended Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:3
Unattended Installation of a Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:3
Unattended installation of a Fix Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:3
Licensing Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:3
Using Licensing as a Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:4
Using the Client-based AVEVA Licensing System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:4

Project Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:1

Create a New Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:2

© Copyright 2000 to current year. i 12.2 and above only

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 Instrumentation Installation User Guide

SQL Server Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:5

SQL Server Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:6
Project Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:7
AVEVA Instrumentation User Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:8
AutoCAD Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:8

© Copyright 2000 to current year. ii 12.2 and above only

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 Instrumentation Installation User Guide
Introduction

1 Introduction

AVEVA Instrumentation is a client-server application. The application modules are installed

on client (end-user) workstations and the database is installed on a server that is accessible
by all users on the network.
AVEVA Instrumentation also requires a common project folder which is accessible to all the
project users in which templates are stored and to which files such as drawings and
datasheets are saved.

1.1 Database Systems Supported

AVEVA Instrumentation supports the Enterprise, Standard and Express versions of
Microsoft SQL Server 2016 SP1, 2017 and 2019.
Hardware and software requirements can be found at these locations:

SQL Server 2016 SP1 and 2017: SQL Server 2016 and later requirements

SQL Server 2019 SQL Server 2019 requirements

The Express version of SQL Server 2019 is available as a free download from the Microsoft
website.

1.2 Project Folders

For each project, AVEVA Instrumentation uses a separate group of folders to store project-
specific files. Ideally, all these folders should be under a single project ‘root’ folder. The
folders are created by AVEVA Instrumentation on project setup (if they do not already exist).
The project folders need to be accessible to all users that require access to AVEVA
Instrumentation documents. For example, the AVEVA Instrumentation team must have
network security rights to read/write to these folders.

1.3 Guide Structure

Introduction Introduction to the AVEVA Instrumentation application.

© Copyright 2000 to current year. 1:1 12.2 and above only

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 Instrumentation Installation User Guide
Introduction

Installation Describes the minimum requirements for each end-user PC

and the procedure for installing AVEVA Instrumentation.

Project Setup Describes how to setup an AVEVA Instrumentation project.

© Copyright 2000 to current year. 1:2 12.2 and above only

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 Instrumentation Installation User Guide
Installation

2 Installation

For details of the installation requirements and procedures, refer to:

• Client Computer Requirements
• Compatibility
• Microsoft .NET Framework 4.8 Runtime
• Project Packager and Microsoft’s Shared Management Objects (SMO)
• AVEVA Instrumentation Setup
• Unattended Installation
• Licensing Setup

2.1 Client Computer Requirements

For the latest client computer requirements please refer to the Release Letter.

2.2 Compatibility
For the latest compatibility information please refer to the Release Letter.

2.3 Microsoft .NET Framework 4.8 Runtime

All AVEVA Instrumentation modules use Microsoft's .NET Framework 4.8, so the .NET
Framework 4.8 runtime must be installed on a client workstation. Install the .NET
Framework 4.8 runtime before installing AVEVA Instrumentation on it.
The English language version is included in the product folder under “Microsoft .NET
Framework 4.8 English”.
Download other language versions can be downloaded for free from the Microsoft website.
See https://support.microsoft.com/en-us/topic/microsoft-net-framework-4-8-language-pack-
offline-installer-for-windows-4bee217e-4096-6922-eba9-3e3c27342ff6.

2.4 Project Packager and Microsoft’s Shared

Management Objects (SMO)
Certain Microsoft assemblies required for the Project Packager functionality to run are not
shipped with AVEVA Instrumentation.
When running the new Project Packager utility, if these assemblies are not detected, the
following message will be displayed.

© Copyright 2000 to current year. 2:1 12.2 and above only

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 Instrumentation Installation User Guide
Installation

By clicking the links, in the order indicated, users will be able to download the required msi
files and install the assemblies. Once installed, the Project Packager will run without any
problems.

Note: This is a one-time action per machine.

Note: Refer to the Security Manager documentation for the procedure for packaging
projects.

2.5 AVEVA Instrumentation Setup

Windows Administrator rights on the workstation are required to install AVEVA
Instrumentation.
Both full releases and partial releases are downloaded from the AVEVA support site. Refer
to the support site for further information.
To install a full release, run the setup.exe file to start the AVEVA Instrumentation Setup
wizard.
To install a fix release, run the .exe file for that fix, for example
Instrumentation12.2.1.1.exe.

Note: If you are not an Administrator on the client PC, right-click on the .exe file and click
Run as Administrator.

Continue at:
• Installing a Full Release
• Installing a Partial Release (Fix Release)

2.5.1 Installing a Full Release

If installing a full release, the following steps will install AVEVA Instrumentation:
• Start the installation wizard as described above. On the welcome screen, click the Next
button to proceed.
• Select the required shortcuts.
• Select the products to be installed. By default, all modules except Process Engineer,
and Security Manager are selected for installation. Security Manager should only be
installed for Project Administrators who wish to manage user's access rights to project
data when using SQL Server. Click Next to proceed.
• Click Install to install the product.
• Click Finish to complete the installation.

© Copyright 2000 to current year. 2:2 12.2 and above only

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 Instrumentation Installation User Guide
Installation

2.5.2 Installing a Partial Release (Fix Release)

Note: A partial release must be installed over the top of the previous full release of the
product.

If installing a partial (Fix) release, the following steps will upgrade the current installation to
the new version:
• Start the installation wizard as described above. On the welcome screen click Next to
proceed.
• Click Install to install the product.
• Click Finish to complete the installation.

2.6 Unattended Installation

An unattended installation of AVEVA Instrumentation, including updates, may be
implemented using the Microsoft System Centre Configuration Manager.

2.6.1 Unattended Installation of a Package

To install Plant, execute the following at the command line using the System Centre
Configuration Manager:
msiexec /i "file location"\setup.msi /quiet PROPERTY="Plant"
To install Marine, execute the following:
msiexec /i "file location"\setup.msi /quiet PROPERTY="Marine"
To install both products, execute the following:
msiexec /i "file location"\setup.msi /quiet INSTALLLEVEL=6
If the installation process is successful, the appropriate shortcut or shortcuts will be added to
the desktop, and the AVEVA Plant and/or Marine folder(s), containing the AVEVA
Instrumentation module shortcuts, will be added to the Start menu.
The programs files will be installed at:
C:\Program Files(x86)\AVEVA

2.6.2 Unattended installation of a Fix Release

To install an AVEVA Instrumentation fix release, using the System Centre Configuration
Manager, execute the following at the command line:
msiexec.exe /p "file location"\"name".msp /quiet REINSTALLMODE="ecmus"
REINSTALL="ALL"

2.7 Licensing Setup

The licensing of the AVEVA Instrumentation product product can be managed in one of two
ways:
• On a “Licensing as a Service” (LaaS) basis using the customer’s AVEVA Connect
account. See Using Licensing as a Service.
• On a client basis (i.e. on a client’s PC or server) using the AVEVA Licensing System
(ALS) security system. See Using the Client-based AVEVA Licensing System.

© Copyright 2000 to current year. 2:3 12.2 and above only

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 Instrumentation Installation User Guide
Installation

2.7.1 Using Licensing as a Service

In order to connect to the licensing service via AVEVA Connect, each end-user PC must
have the following System Environment Variables setup on it:

Name Value
AVEVA_CONNECT_AUTHORITY_URL https://identity.capdev-connect.aveva.com/
identity
AVEVA_LICENSE_SERVER_LIST https://test-license.capdev-connect.aveva.com/
;4545@licsrvhyd1;4545@licsrvhyd2

2.7.2 Using the Client-based AVEVA Licensing System

Client-based licensing for the AVEVA Instrumentation product is managed by AVEVA
Licensing System (ALS) security system.

Note: Versions 2.0, 3.0, 4.0, and 4.1 of the ALS are supported. Be aware that a new
license file will be required after upgrading to a later version.

To operate, AVEVA software must be able to access the correct ALS license file, which
should be installed on either the Server, on the workstation, or on a networked workstation.
ALS is a network license service which hands out floating licenses to clients, meaning that
licenses are not tied to a certain workstation but can be used from any workstation where
the software is installed, as long as the total number of licenses in use does not exceed the
number of licenses purchased.
The ALS guide is available on the AVEVA support site.
AVEVA Instrumentation is supported for use with Citrix for multi-site working.

© Copyright 2000 to current year. 2:4 12.2 and above only

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 Instrumentation Installation User Guide
Project Setup

3 Project Setup

After installation, either a new AVEVA Instrumentation project (and database) must be
setup, or an existing project Workgroup file must be selected. The Workgroup file is a data
file that holds the details of all AVEVA Instrumentation projects located on the system.
Run an AVEVA Instrumentation module. If this is the first time an AVEVA Instrumentation
application (or module) has been run on the workstation, the Browse For Folder window
will be displayed.

To select an existing project, use the dialog to select the folder in which the project
Workgroup file is located and click OK.

Note: If multiple AVEVA Instrumentation users are to work on the project then this
Workgroup file folder should be located on a common network drive accessible to all
these users.

The AVEVA Instrumentation Workgroup file is a Microsoft Access database that contains a
single table that holds the names and locations of the AVEVA Instrumentation projects.

© Copyright 2000 to current year. 3:1 12.2 and above only

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 Instrumentation Installation User Guide
Project Setup

Note: To reset a workstation’s Workgroup file (e.g. if the wrong folder was selected), simply
delete the file ‘Inst.ini’. This file will located in:
Users\<user name of installer>\AppData\Roaming
If this does not exist, AVEVA Instrumentation will ask for the Workgroup file once
again.
Continue at:
• Create a New Project
• SQL Server Setup
• SQL Server Security
• AVEVA Instrumentation User Security
• AutoCAD Setup

3.1 Create a New Project

Note: SQL Server Administration rights are required to create a SQL project database. The
Server Name is also required.

The Create a New AVEVA Instrumentation Project window is displayed either after a
Workgroup file has been selected as described previously, or when New is clicked on the
Select an AVEVA Instrumentation Project window (accessed from the Open Project
option in the Setup tab of Engineering modules).

© Copyright 2000 to current year. 3:2 12.2 and above only

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 Instrumentation Installation User Guide
Project Setup

Project Name or No: Enter the Project name or number.

Project Fields: Populate the other project fields such as Project Description, Plant Name,
Client Name etc.
Share with Electrical: If project equipment and cables are to be shared with an AVEVA
Electrical project, check this checkbox.

Note: Once sharing has been selected, it cannot be deselected.

SQL Server: Click the [...] button to display the SQL Server login window, used to create
the new project database on a selected SQL Server. Refer to SQL Server Setup for details.
Copy: Select one of the following options as required:
Empty Project: The default option. A new blank project with no project data and the
default security settings will be created if this option is selected.
Demo Project: AVEVA Instrumentation includes a ‘Demo Project’ database which can
be copied for the purposes of evaluating or testing AVEVA Instrumentation. Select this
option if the new project is to be a copy of the AVEVA Instrumentation Demo Project.
Packaged Project: Projects can be “packaged”, that is saved to a single package
(.pkg) file. When new projects are created, a packaged project can be selected.
Project setting and data are copied from the packaged project.

© Copyright 2000 to current year. 3:3 12.2 and above only

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 Instrumentation Installation User Guide
Project Setup

Note: Refer to the Security Manager documentation for the procedure for packaging
projects.

When the Packaged Project option is selected, the Package File field and ... button
become active. Click the ... button to browse for and select the required package file.
The location and file name of the selected file is the displayed in the Package File
field.
Project Folder: This is the ‘root’ project folder. By default, once entered (or browsed to), the
other project folder names are automatically completed using this root. These can
subsequently be edited if required (see below).
If the project is a copy of the demo or of a packaged project, most of these fields will be
automatically completed. They may be amended if required.

Note: AVEVA Instrumentation will create all the project folders if they do not already exist
when Save is clicked.

File Locations/Folders:
Design Database: The SQL Server Database Name.

Note: If multiple AVEVA Instrumentation users are to work on the project then these folders
should be located on a common network drive accessible to all these users and the
mapped drive letter must be the same for all these users.

Other Folders: All other folder names are user definable but (logically) should reside
under the same root folder for ease of management. Although in theory everything
could be located in the same folder, this would be difficult to manage as the number of
files grows. Therefore it is recommended that each group of files is located in a
different sub-folder.
When the project details have been entered, click Save.
AVEVA Instrumentation will then create the new project database on the nominated Server.
AVEVA Instrumentation will also create all the project folders if they do not already exist.
If a packaged project was selected to copy from, a window displaying the progress of the
extraction of data from the package file is displayed:

Once created AVEVA Instrumentation will show the new project in the Select an AVEVA
Instrumentation Project window.
When an AVEVA Instrumentation module is started, if only a single project has been created
(i.e. is listed in the Workgroup file), this project will be automatically selected and opened.
If more than one project has been created, then the Select an AVEVA Instrumentation
Project window is displayed, from which the required project can be selected:

© Copyright 2000 to current year. 3:4 12.2 and above only

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 Instrumentation Installation User Guide
Project Setup

To create further projects, select the New button on the Select an AVEVA Instrumentation
Project window. The Create a New AVEVA Instrumentation Project window is then
displayed, and should be completed as described above.
The Select an AVEVA Instrumentation Project window can also be opened by selecting
the Open Project option from the Project tab of AVEVA Instrumentation modules.

Note: To remove a project from the list in the Select an AVEVA Instrumentation Project
window, open the Projects.Mdb Access database located in the Workgroup folder
and delete the appropriate record. The SQL server database on the database server
will not be affected.

The project details, including project folders, may be edited after a project has been created
by selecting the Edit Project option from the Project tab of AVEVA Instrumentation
modules (once a user has logged on to the project). However, AVEVA Instrumentation will
not move any existing files to any new folders. After folder creation, this must be done
manually.

3.2 SQL Server Setup

Note: SQL Server Administration rights are required for AVEVA Instrumentation to create
the SQL database. The Server Name is also required.
Login information is not saved anywhere and is used once to connect to the Server
to create the database.

The SQL Server Login window is displayed when the button next to the SQL Server Name
field on the Create a New AVEVA Instrumentation Project window is pressed (see Create
a New Project). This is used to create the new project database on a selected SQL Server.

© Copyright 2000 to current year. 3:5 12.2 and above only

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 Instrumentation Installation User Guide
Project Setup

Enter a valid server name.

Login using Windows Authentication or SQL Server Authentication. This login must be a
valid SQL Server Administrator account login.

Important: Do not use the AVEVA Instrumentation Admin login.

Test that the entered details are valid by clicking Test Connection.
Clicking OK will run a script to create the new AVEVA Instrumentation database.

AVEVA Instrumentation Admin Account

The AVEVA Instrumentation SQL database creation script creates a special AVEVA
Instrumentation Admin account for the database with ‘dbo’ rights on the database. This
account is used by AVEVA Instrumentation to enable future updates and upgrades for the
database.

Manual AVEVA Instrumentation SQL Server Database Creation

The above window runs a script named ‘EmptySQLDb.exe’ located in the AVEVA
Instrumentation program files folder ‘EmptyDbs’ (typically: ‘c:\program files\AVEVA\
Instrumentation12.1\EmptyDbs’). This file can also be run manually if a user has SQL
Admin rights. However, if this file is run manually, then the SQL Administrator should ensure
the Admin account exists and has ‘dbo’ rights to the new database. Contact AVEVA
Instrumentation to request the password for this account.

3.3 SQL Server Security

By default, AVEVA Instrumentation uses Windows Authentication to allow users access to
AVEVA Instrumentation databases on a SQL Server. To enable users to access each
AVEVA Instrumentation database, the SQL Server Administrator must add each user login
to the database and allocate them to a role named ‘Users’, which gives these users
permissions to access AVEVA Instrumentation database objects. This is performed using

© Copyright 2000 to current year. 3:6 12.2 and above only

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 Instrumentation Installation User Guide
Project Setup

the AVEVA Instrumentation Security Manager.

Alternatively, add a user’s Windows Domain name to the SQL Server database with a
‘Users’ role.
In AVEVA Instrumentation Security Manager, select the Project > Add New User to SQL
Server Project option. This displays a window enabling login as SQL Server administrator.
After entering the Server Name and Database Name (and either logging in using Windows
Authentication or logging in with admin user name and password), this window will be
displayed:

Select the project database(s) to add the new user to.

Enter the User Domain Login Name.
Select required Access/Rights (Read-Write or Read-Only).
Then click Save to add the user to the database(s).
Repeat this procedure for all new users.

3.3.1 Project Security

In addition to Windows Authentication or SQL Server Authentication a third option of Project
Authentication is available at the user level. Individual projects can have Project level user
log ins and passwords individual to each user that have to be entered each time the project
is accessed. Refer to the AVEVA Instrumentation Security Manager documentation for more
information.

© Copyright 2000 to current year. 3:7 12.2 and above only

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 Instrumentation Installation User Guide
Project Setup

3.4 AVEVA Instrumentation User Security

An AVEVA Instrumentation administrator can set security rights for users to enable/disable
access to AVEVA Instrumentation functionality including:
• Access to AVEVA Instrumentation application modules. Users can be restricted from
using any module (license).
• Access to AVEVA Instrumentation objects can be restricted to read-only (e.g. a user
cannot add/edit an instrument or cable etc.) or no access (i.e. the user cannot view an
instrument or cable etc.).
• Access to project data in Plant Areas can be restricted if required. Users can be given
Full, Read-only or No access to data in plant areas as appropriate.
AVEVA Instrumentation objects include project items such as cables, instruments and
catalogues. Functionality such as data import can also be restricted as required.
By default, all new projects have the User Security Rights features disabled. If User Security
is required it must be turned on using the AVEVA Instrumentation Security Manager
application. Users must then be allocated to 'Security Groups' such as Engineers and
Designers, Read-Only Users etc. Refer to the AVEVA Instrumentation Security Manager
documentation for more information.

Note: Once security is switched on, by default users will have no access until they are
added to a Security group.

3.5 AutoCAD Setup

On every client PC on which AutoCAD is going to be used to produce drawings etc. from
AVEVA Instrumentation, the following variables must be set to 0 (zero):
• STARTUP
• STARTMODE
If they are left at their default AutoCAD setting (for example), an error will be caused when a
user attempts to open AutoCAD from AVEVA Instrumentation.

© Copyright 2000 to current year. 3:8 12.2 and above only

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 Instrumentation Installation User Guide

Index

A S
ALS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:4 SMO . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1
AutoCAD Setup . . . . . . . . . . . . . . . . . . . . 3:8 SQL Server
AVEVA Connect . . . . . . . . . . . . . . . . . . . 2:4 Security . . . . . . . . . . . . . . . . . . . . . . 3:6
AVEVA Licensing System . . . . . . . . . . . . 2:4 Setup . . . . . . . . . . . . . . . . . . . . . . . . 3:5

C U
Compatibility . . . . . . . . . . . . . . . . . . . . . . 2:1 Unattended Installation . . . . . . . . . . . . . 2:3
Computer Requirements . . . . . . . . . . . . . 2:1 User Security . . . . . . . . . . . . . . . . . . . . . 3:8

D
Database Systems
Supported . . . . . . . . . . . . . . . . . . . . . 1:1

I
Instrumentation Setup . . . . . . . . . . . . . . . 2:2

L
LaaS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:4
Licensing as a Service . . . . . . . . . . . . . . 2:4
Licensing Setup . . . . . . . . . . . . . . . . . . . 2:3

P
Project Folders . . . . . . . . . . . . . . . . . . . . 1:1
Project Packager and Microsoft’s Shared Man-
agement Objects (SMO) . . . . . . 2:1
Project Security . . . . . . . . . . . . . . . . . . . . 3:7
Project Setup . . . . . . . . . . . . . . . . . . . . . 3:1

© Copyright 2000 to current year. Index page 1 12.2 and above only
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
 Instrumentation Installation User Guide

© Copyright 2000 to current year. Index page 2 12.2 and above only
AVEVA Solutions Limited and its subsidiaries.
All rights reserved.