D 10545

QA4/1, QA7/2 & QA11/3 - DNote v4.
25 (21-Dec-15)
Product Release Letter

AVEVA Instrumentation 12.1.SP5 Fix 5
Partial Fix Release 10545-1
Windows 7 SP1 (32 bit or 64 bit), Windows 8.1 (64 bit) &
Windows 10 (64 bit)
Dear Customer
This letter introduces and describes this release, which is supported on the indicated platform(s).
This Release Contains

A full partial of AVEVA Instrumentation, which upgrades the full release 10526-1 AVEVA
Instrumentation 12.1.SP5.
The separately licensed products or product components installable from or upgraded by this
release are as follows:
Product Version
Product Name
Code Number
V00FN278 AVEVA Instrumentation with following modules: 12.1.SP5
Instrumentation Engineer
Instrumentation Designer
Instrumentation Wiring Manager
Process Engineer
Instrumentation Security Manager
V00FN690 AVEVA NET Instrumentation Gateway 12.1.SP5
For further information please contact your local AVEVA support office, which can be found at
http://support.aveva.com
This document has been prepared and approved by the following:

Job Title Name
Product Manager & Owner Chris Binns
Product Manager
System Test Manager Kishore Grandhi
Test Manager
Development Manager Mac Lewis
Development Manager
TPS Representative for EDS products Semra Hamitogullari Åberg
Manager, Training and Product Support (EDS)
File: d10545.docx
Last saved: 18 March 2019  Copyright 2019 AVEVA Solutions Limited Page 1 of 24
Prerequisite for this release - operating system:
Minimum Supported O/S Version (for Microsoft Windows 7 SP1 Professional (32 bit or 64
each supported platform) bit), Windows 8.1 Professional (64 bit), Windows 10
Professional (64 bit)
Mandatory O/S Patches (for each Microsoft Windows 7 SP1, Windows 8.1 base release
supported platform) or Windows 10 base release
Build Operating System Microsoft Windows 7 SP1 (32 bit & 64 bit)
Please note that recommended/supported hardware and software configurations are constantly subject to review, so
please consult the AVEVA support web pages for the latest recommendations.
Prerequisite for this release - products:

• AVEVA Licensing System 2.0, 3.0 or 4.0 and an appropriate license file
• Microsoft .NET Framework 4.5.1
o The English version is included in the product folder under Microsoft .NET
Framework 4.5.1 English
o For all other language versions please see https://www.microsoft.com/en-
gb/download/details.aspx?id=40779
• Microsoft Office 2010, 2013 & 2016* (32 bit or 64 bit)
o *Including Microsoft Office 365 local client install
▪ Online applications and OneDrive folders are not supported
o Microsoft Excel is required to open datasheets and edit datasheet templates within
AVEVA Electrical and AVEVA Instrumentation 12.1.SP5 Fix 5
* Installations of Microsoft Office 2013 & 2016 will also require the 2007 Office System Driver
installing to enable importing data from Microsoft Excel. If Microsoft Office 2007 or 2010 has
previously been installed, this driver may already be in place and the additional download and
installation will not be required.
Works (is compatible) with:

• AVEVA Electrical 12.1.SP5 Fix 5
• AVEVA Engineering 14.1.0 including Fix 1 & above
• AVEVA Engineering 14.1.SP1 including Fix 1 & above
• AVEVA Engineering 14.2 including Fix 1 to Fix 5
• AVEVA Diagrams 14.1 including Fix 1 & above
• AVEVA Diagrams 14.1 SP1 including Fix 1 & above
• AVEVA Diagrams 14.1 SP2 including Fix 1, Fix 2 & Fix 3
• AVEVA Integration Service 1.0 to 1.5.1.1 and 1.5.2
• AVEVA Administration 1.2, 1.3, 1.4 & 1.5
• AVEVA P&ID 12.1 and above (32 or 64 bit)
o 12.1.SP2 Fix 1 or above recommended*
o 12.1.SP3 to Fix 8
File: d10545.docx
• AVEVA P&ID 12.2 Fix1
• AVEVA PDMS & AVEVA Marine (Hull and Outfitting) 12.1 and above
• AVEVA E3D 1.1 & 2.1 Fix 1 to Fix 19
• AVEVA NET Portal 4.7.7 and above
• AVEVA NET Workhub & Dashboard 5.0.1 Fix 3, 5.1, 5.0.2, 5.1, 5.1.2.2, 5.1.3.1 and 5.1.4.2
• AutoCAD 2016 SP1, 2017 & 2018
o VBA Enabler for AutoCAD not required for AVEVA Instrumentation 12.1.SP5 Fix 5
• Microsoft Excel 2010, 2013 and 2016*
o *Including Microsoft Office 365 deployed version
• Microsoft SQL Server 2012 SP3, 2014 SP2, 2016 SP1 and 2017
o SQL Server Express also supported
• Citrix XenApp 7.8 (64 bit)** and Citrix XenDesktop 7.8 (64-bit)
• https://citrixready.citrix.com/
* See Integrating with AVEVA P&ID in the Important Points to Note section of this release letter.
** Please check that the version of AutoCAD deployed within a Citrix environment is certified for
Citrix use and that the AutoCAD licensing is compliant. Click this link for more information
https://knowledge.autodesk.com/support/autocad/getting-
started/caas/simplecontent/content/autodesk-citrix-ready-certified-products.html
Integration Matrix
AVEVA Instrumentation 12.1.SP5 Fix 5 supports a new method of integrating the AVEVA products.
The AVEVA Integration Service removes the need to have the applications that you wish to
integrate installed on the same workstation. Instead the integration is managed by a windows
service (running on a separate machine) that all project participants can access via the network.
This new method of integration is not available for all AVEVA applications yet and where available
primarily only for the latest versions.
The following table indicates which method of integration can be deployed with AVEVA
Instrumentation 12.1.SP5 Fix 5.
AVEVA P&ID Local Integration Services Integration Notes
12.1 to 12.1.SP2 Fix 1 Yes No
12.1.SP2 Fix 2 & above Yes *Yes *12.1.SP2 Fix 5 and above
needed to import loop data
12.1.SP2 Fix 11 & above No *Yes *12.1.SP2 Fix 5 and above

needed to import loop data
Local integration is not
supported with AVEVA P&ID
12.1.SP2 Fix 11 to Fix 13
12.1.SP3 to 12.1.SP3 Fix 8 No Yes Local integration is not
12.1.SP3
12.2 Fix 1 No Yes Local integration is not
12.1.SP2 Fix11 onwards
AVEVA Engineering
File: d10545.docx
14.1, 14.1 Fix 1 & Fix 2 Yes No
14.1 Fix 3 & above Yes Yes
14.1.SP1, 14.1 SP1 Fix 1 & above Yes Yes

14.2 to 14.2 Fix 5 Yes Yes
AVEVA Diagrams
14.1& 14.1 Fix 1 & above No Yes

14.1.SP1 Fix 1 & above No Yes
14.1.SP2 Fix 1, Fix 2 & Fix 3 No Yes
PDMS & Marine Engineering

12.1 to 12.1.SP2 Fix 39 & above Yes No
12.1.SP4 Fix 17 & above Yes No
PDMS & Marine Diagrams

PDMS & Marine Schematic Model
Manager
PDMS & Marine Design

12.1.SP4 Fix 17 & above Yes *No *See Note 1 below
12.1.SP5 & above Yes *No *See Note 1 below

E3D Design
1.1, 2.1, 2.1 Fix 1 & above Yes *No *See Note 2 below
2.1 Fix 4 to Fix 19 Yes Yes
Notes:
1. Will be supported in the future release of AVEVA Instrumentation
2. E3D 2.1 Fix 4 and above is recommended for integration via AVEVA Integration Service due
defects related to integration being corrected in this fix release
3. See Scenarios Whereby a Blank Compare/Update Dialogue is Presented in the Important
Points to Note section of this document
Supersedes:
This release supersedes the partial release 10543-1 AVEVA Instrumentation 12.1.SP5 Fix 4.
To install product release:

Please run the file Instrumentation12.1.5.5.EXE.
Running this executable will upgrade the following installations to AVEVA Instrumentation
12.1.SP5:
• AVEVA Instrumentation 12.1.SP5 (Full release 10526-1)
File: d10545.docx
• AVEVA Instrumentation 12.1.SP5 Fix 1 (Partial release 10533-1)
To install this update successfully, right-click on the .exe and then select "Run as Administrator"
from the options. Once the installation has completed a system restart will be required.
Notes:
1. Due to the upgrade of 3rd party components to support Windows 10, if both AVEVA
Instrumentation and AVEVA Electrical are installed on the same machine, both applications
must be upgraded to SP5 Fix 5.
2. If pre-SP5 versions of both AVEVA Instrumentation and AVEVA Electrical are installed on
the same machine, both AVEVA Instrumentation and AVEVA Electrical must be upgraded to
12.1.SP5 base release before applying the SP5 Fix 5 update to either AVEVA
Instrumentation or AVEVA Electrical.
3. For “clean” installations, both AVEVA Instrumentation 12.1.SP5 base and AVEVA Electrical
12.1.SP5 must be installed before applying the SP5 Fix 5 update to either AVEVA
Instrumentation or AVEVA Electrical.
4. Once installed on a machine running both AVEVA Instrumentation and AVEVA Electrical, if
the 12.1.SP5 Fix 5 is to be removed, the uninstall must be performed for both AVEVA
Instrumentation and AVEVA Electrical.
5. If 12.1.SP5 Fix 5 has been removed from a machine, subsequent refresh installations of
12.1.SP5 base release will not work. To refresh the base release of 12.1.SP5 remove all fix
and base releases and reinstall all again from scratch. This applies to AVEVA
Instrumentation, AVEVA Electrical and combined installations.
The reason for the these install and uninstall instructions is due to certain 3rd party, shared
components being stored in the “Windows\SysWOW64” folder. When SP5 Fix 5 is installed, the
latest required components will be installed in this shared location. Installation of an older SP5
version (after installing Fix 5) will overwrite the latest components with older components causing
an error.
First released on:

This product release is first available on AVEVA support website http://support.aveva.com as
AVEVA Instrumentation 12.1.SP5.5, release number 10545.
File: d10545.docx
List of Enhancements
None in this fix release.
List of Fault Corrections

This release addresses defects arising from the following support incidents:
Incident Defect Product / Description
number number Module
131974 307571 Engineer Problems importing instrument data when P&ID document
number contains dots/periods “.”
135491 313972 Wiring Timeout opening Edit Terminations window
Manager
135506, 314007, Wiring Signal lost from cores and wires upon save
138383 324865 Manager
135491 313972 Wiring Timeout when trying to open the Edit Terminations window
Manager for a junction box
136951 318724 Designer Automatic Insertion Blocks not working
138380 323414 Wiring Assigned IO not visible against I/O module channels
Manager
n/a 324440 Wiring Add Link (Left) is not working in Edit Terminations window
Manager
n/a 324439 Wiring Delete All Links not working in Edit Terminations window
Manager
n/a 324434 Wiring Delete Selected Link not working in Edit Terminations window
Manager
n/a 323391 Wiring Exception error when executing Split Terminal Strip in Edit
Manager Terminations window
n/a 320890 Wiring User unable to terminate both ends of the cable through Excel
Manager import
n/a 327443 Wiring Cross-patch functionality not working
Manager
Consolidated from previous releases
First released in AVEVA Instrumentation 12.1.SP5 Fix 4, Release No. 10543-1

112266 244473 Security Error during the deployment a project from the package.
Manager
112915 246386 Engineer Problems trying to update selected attributes using compare &
update.
110863 256317 Designer Problems with revision datalinks on termination diagrams.
122424 274370 Engineer Problems with tag formatting and Excel import.
125925 282986 Engineer Log file required for update errors when importing data via
compare & update.
127635 287708 Wiring Save options presented when closing ECBD's even if user has
Manager read-only or no access.
129701 293898 Engineer Access rights to process data not functioning as expected.
130054 295002 Security Problems following the extraction of a packaged project.
Manager
130254 298362 Security Problems importing security settings from another project.
Manager
File: d10545.docx
131555 298696 Security Problems upgrading from SP3 to SP5.
Manager
n/a 288196 Engineer Records are not deleted from the Process Data grid after
deleting a datasheet with the checkbox to Delete Process
Properties ticked.
n/a 290520 Designer Drawing revisions copied when a drawing is copied.

113559 248195 Engineer Data entered via a datasheet or the Browse Data By Form Type
grid is not being saved
113877 249008 Designer Data not displaying on Loop diagrams
116262 256183 Wiring Importing devices from Excel is not observing the sequence
Manager value
111086 257222 Wiring Exception error when changing terminal markings
Manager
116679 257352 Wiring Importing DIN rails from Excel not possible
Manager
117426 259366 Wiring When importing components, the correct DIN rails are not
Manager created
124324 279086 All Performance of grids with very large data sets
124763 280125 Engineer Tag code validation is not working when importing
Instruments and Loops from Excel
130054 295002 Security Problems following the extraction of a packaged project
Manager
122140 273463 Security Everyone group is not working the same on access right by
Manager area and by object
116024 270472 Wiring Duplicate Drum Tag in Cable Drum Schedule Grid
Manager
121395 273660 Wiring Equipment Import Using Equipment ID
Manager
125705 282539 Engineer Compare/Update error messaging missing
128204 289265 Engineer Upgrading to AVEVA Instrumentation / Electrical 12.1.SP5.2
130039 295001 has altered some of my reports
124165, 278783, Wiring Slow performance on opening cable grid
131143 297925 Manager
124613 280439 Wiring Need to increase cableNo column on the cables table to 100
Manager characters
116024 270472 Wiring Duplicate Drum Tag in Cable Drum Schedule Grid
Manager
121395 273660 Wiring Equipment Import Using Equipment ID is not working
Manager
124613 280439 Wiring Need to increase cableNo column on the cables table to 100
Manager characters
n/a 283556 Engineer Not able to import data into Process Equipment grid through
Service Integration with Engineering 14.2
n/a 283069 Engineer Exception error when switching grid on very large projects
n/a 283097 Engineer Exception error when loading grids on very large projects with
security enabled
n/a 253297 Engineer Compare/Update screen is blank when importing AVEVA
Instrumentation data from Engineering 14.2 fix2
File: d10545.docx

75969 168271 Engineer Manually mapped fields lose mapping if auto-create
properties actioned following manual mapping.
116733 257548 Engineer Area path not updating properly when the area path delimiter
is changed.
116827, 257707, Process Importing process lines or process equipment via MS Excel is
116864 257840 Engineer not checking tag codes and tag format.
116178 259667 Engineer Updating instrument property values is affecting other
userfields.
117564 259818 Wiring Users can import equipment via MS Excel despite having No
Manager Access to a particular area.
115993 260067 Engineer Service integration configuration settings lose key attributes.
117659 260177 Designer Error when updating issued ECBD’s via Designer module.
117660 260184 Designer Revision clouds not displayed on termination diagram title
block.
117662 260185 Designer Problems with clouding issued ECBD’s
113558 248202 Engineer Can't remove voltage requirement from Instrument after being
assigned.
114175 249996 Engineer Problems importing an instrument catalogue via MS Excel.
118454 263430 Engineer Creating wiring using wiring rules is not terminating the
cables.
120864, 274672, Wiring Junction Box Allocation not creating wiring.
119819, 250032, Manager
124933 272097,
280650
120597 269014 Wiring ECBD error when editing cables
Manager
120603 269043 Engineer Exception opening loop and instrument grid
118844 264474 Engineer Compare/Update problems with large datasets
125705 252539 Engineer Compare/Update error messaging missing
115653 265313 Wiring Error opening user defined symbols
Manager
119615 266589 Process Process line/equipment property values deleted when deleting
Engineer an instrument
n/a 258956 Wiring Importing empty DIN rail creates a terminal
Manager

76090, 242496, Engineer Cables are terminated when running instrument wiring rules
111459 157847 even if the “Terminate” check-box is unchecked.
114151 249844 Wiring I/O allocation dialogue is empty.
Manager
99188, 212787, Engineer Creation of a Document List does not create an Index Sheet
113481 248054 after update.
110028 240259 Engineer Compare & Update identifying existing instruments as “New”.
110143 238916 Wiring Not able to assign instruments to I/O module channels.
Manager
File: d10545.docx
110147 238954 Wiring Exception error when accessing Control Rooms and DCS
Manager Cabinets via the Equipment View when security is enabled.
109710 237901 Security Problems importing security settings from one project to
Manager another.
n/a 236417 Engineer Integration via AVEVA Integration Service not working on
Korean O/S.
110153 238978 Wiring Not possible to edit rooms and buildings via the Equipment
Manager View when security is enabled.
108034 234539 Engineer Problem of userfields mixed up between Engineer and Wiring
Manager grid views.
108822 235594 Security Problems upgrading projects on Korean O/S.
Manager
110140 242123 Wiring Problems with releasing claims on Cable Block Diagrams.
Manager
First released in AVEVA Instrumentation 12.1.SP5, Release No. 10526-1

98665, 21165, Designer Cannot delete or update drawings in designer if
101743 218290 ‘SheetAlphaNum’ is missing from the view
97538 209487 Wiring Enhanced Termination Report messed up
Manager
60423 106741 Wiring Cable catalogue import from Excel ignores CoreSize and
Manager GroupType "C"
71098 143304 Security AIReports.mdb password missing in packaged project
Manager
98097 210417 Security Security Manager settings not being applied
Manager
96480 206680 Wiring Updating an Enhanced Termination Report via Designer resets
Manager ferrule data to show signal numbers
79297 179932 Engineer Problems with decimal comma when entering value via the
Browse Data by Form Type grid
84331 183055 Wiring ‘Link to Instrument Tag’ command problems
Manager
86637 184846 Designer Instrument property and ProcessData property datalinks not
working correctly with Hookup drawings
88334 189118 Wiring I/O module channel numbering problems
Manager
88356 189154 Designer Problems with hook up quantities when decimal comma set in
Windows Regional Settings
102553 220430 Security Cannot upgrade projects. Unknown database version.
Manager
101044 216528 Security Project creation error with SQL Authenticate user
Manager
n/a 211994 Engineer Bulk copy selected is not working in Instruments grid
n/a 211827 Wiring Symbols are changed in all ECBDs when they changed for one
Manager ECBD in upgraded projects
n/a 209113 Engineer Exception when inserting a sub-report
File: d10545.docx
n/a 210237 Engineer SCActuator (AI) and SCSubEquipment (AE) are not available in
AVEVA Integration Service configuration window for importing
from AVEVA Diagrams 14.1
n/a 204651 Engineer Highlight Issue Changes button is appearing in quick reports
for Instruments grid
n/a 197835 Designer Unable to close warning messages, when index number is
zero for same drawing number
n/a 189895 Engineer Instrument List is not displaying comma separated decimal
values properly when instruments with comma separated
decimal values are imported from excel
n/a 190101 Engineer Change loop option is disabled when security settings are
applied
n/a 190287 Designer Check for New Loops, Check for new CBDs etc. is creating new
drawings in read only area
n/a 216507 Engineer Function code pick-lists are empty for loops and instruments
in upgraded projects
n/a 215152 Engineer Out of memory exception occurred after adding a sub-report
via report Edit Layout window
PRODUCT QUALITY STATEMENT

The development, maintenance and testing of AVEVA Solutions’ software products is carried out in
accordance with the AVEVA Quality Management System lifecycle processes and this document
includes a summary of the testing carried out on this release and a list of significant defects
known to exist at the time of release.
Development Testing
Developers have carried out unit testing of each enhancement and/or fix in the development
environment to verify that any new functionalities have been correctly implemented and identified
defects have been corrected.
Regression tests have been run in the development environment to verify that enhancements
and/or fixes have not adversely affected the integrity of the product.
System Testing
Independent system testing has been carried out on the product, as released, to verify that it
installs correctly in all supported configurations and that product functionality operates as
intended, subject to any known exceptions listed below.
Acceptance Testing
AVEVA’s Product Readiness Authority (PRA) is satisfied that the System Testing for this release is
sufficient to assure product quality.
Any exceptions found after release will be reported in the Product Release Latest Update Note on
AVEVA's support web site http://downloads.aveva.com/10545/w10545.pdf
File: d10545.docx
Exceptions – Significant Defects and Recommended Workarounds
AVEVA intends to fix the defects listed below in a fix release or service pack as soon as reasonably
possible.
Incident Defect Description Recommended Workaround
number number
n/a 161004 Problems importing data into a Ensure that property names are
shared project when duplicate unique in AVEVA Electrical and AVEVA
properties exist in AVEVA Instrumentation. See Importing Data
Electrical and AVEVA into a Shared Project Where Duplicate
Instrumentation Property Names Exists for AVEVA
Electrical and AVEVA Instrumentation
in Important Points to Note section
below
n/a 177419 Publishing reports to AVEVA NET This is a limitation in the SP5 release.
can only be done one at a time Reports should be selected
individually to publish to AVEVA NET.
n/a 172254 Bulk Edit of drawings via No work around, however performing
Designer Drawings list show the bulk edit will still work.
“False” for Show IJB Connections
and Show Ferrule Numbers even
when some of these values are
checked/true
78110 163668 Can’t have two projects (created Connect AVEVA support for
from different versions of AVEVA assistance
Instrumentation) connected to
same SQL instance with different
IDOAdmin password
n/a 194428 Digit grouping symbol of Work around is to ensure that when
dot/period in Windows Regional the spread sheet is created/exported,
Settings causing problems upon the digit grouping symbol of comma
import from Excel is used
n/a 188370 Compare/Update window blank is Work around is to ensure that all
properties mapped for properties (especially those mapped
integration that do not have for integration) have captions defined
captions defined
n/a 221398 Project login box popping up Login box pops up 3 times when the
when configuring integration AVEVA Electrical or AVEVA
from AVEVA P&ID and AVEVA Instrumentation project is being
Engineering if Project accessed. Simply enter password 3
Authentication is enabled times and configuration can continue
successfully.
104865 225142 Problems using copy wizard Copy equipment using basic copy
when copying process equipment method and not via the wizard.
using Process Engineer module.
Equipment cannot be copied if
the tag format does not
incorporate ‘Area’ and the option
to use Area to check for
uniqueness is enabled.
105325 226121 Changes made to cable numbers Update cable tag numbers once the
in junction box allocations cables and wiring has been created.
dialogue are not saved or passed
to created cable.
File: d10545.docx
Incident Defect Description Recommended Workaround
number number
103522 222146 No access error displayed when Add the ‘Administrator’ to a user
adding a new field device to an group that has full access to cable
enhanced cable block diagram for block diagrams.
‘Administrator’ users.
103181 221572, Integration configuration object No workaround. To be addressed in
225619 type mappings visualisation first fix release for SP5.
problems. When selecting the
required tables, the name can be
truncated.
n/a 265075 Empty Compare/Update form Remove the column name data in the
when exchanging cable data with view to enable the Compare/Update
E3D if Column Name is populated form to function correctly.
for attributes added to cable
based views in AVEVA
Administrator (Lexicon).
n/a 294815 Out of memory exception pops Do not switch between grids.
up when switching from one grid
to Instruments grid with Security
enabled when there are more
than 200 thousand instruments;
16 thousand loops; 90 thousand
datasheets.
Please refer also to the Product Release Latest Update Note for the original full release,
http://downloads.aveva.com/10526/w10526.pdf
For the latest list of exceptions and other updates, please see the Product Release Latest Update
Note on AVEVA's support web site http://downloads.aveva.com/10545/w10545.pdf.
Important Points to Note

1. Mapping Tag Codes to Enable Integration
2. Project Packager and Microsoft’s Shared Management Objects (SMO)
3. Upgrading projects with the new AVEVA Project Authentication enabled
4. Changing Project Authentication Type
5. AutoCAD 2015, 2016 & 2017 File Loading Security Concern
6. Defining Process Equipment and Process Line Tag Formats
7. Area Numbers on Reports following Project Upgrades
8. How to avoid Timeout error during loading of grids
9. Importing Records where Field and Property Names Match
10. Properties Named with Underscores
11. Importing Data via Microsoft Excel where duplicate field/column names are detected
12. Integrating with AVEVA P&ID
13. Importing Data into a Shared Project Where Duplicate Property Names Exist for AVEVA
Electrical and AVEVA Instrumentation
14. Duplicate named fields and properties causing problems importing data from MS Excel
15. Leading Spaces in Column Name Causing Problems Importing from MS Excel
File: d10545.docx
16. Problems Initialising AVEVA Engineering for Integration
17. Installation Steps for AVEVA Integration Service
18. Scenarios Whereby a Blank Compare/Update Dialogue is presented
19. Upgrade problems if a project contains a pick-list named “Yes/No”
20. Importing terminal label values from MS Excel
21. AVEVA Instrumentation Enhanced Cable Block Diagram symbol named “Field Device”
causes project upgrade problems
22. AutoCAD “STARTUP” and “STARTMODE” system variable
23. ECBD Title Blocks
Mapping Tag Codes to Enable Integration
When importing tagged objects via Microsoft Excel, or other AVEVA applications as part of the
AVEVA Integrated Engineering & Design solution, all component parts (tag codes) of the tag
number should be mapped to ensure accurate data transfer. This was the recommended approach
for 12.1.SP2 and is now mandatory for some integration when deploying 12.1.SP3 to 12.1.SP5 Fix
5. These additional mandatory fields will ensure that it is not possible to import mismatched tag
code and tag number data.
Example: Instrument Tag 01-FT-001/A (tag format, Area – Function – Number / Suffix)
Mandatory Fields to map for import:
• Tag Class
• Tag Format
• Area Path
• Area
• Function
• Number
• Suffix
Back
Project Packager and Microsoft’s Shared Management Objects (SMO)
Certain Microsoft assemblies required for the new Project Packager functionality to run are not
shipped with AVEVA Instrumentation or AVEVA Electrical 12.1.SP5 Fix 5.
When running the new Project Packager utility, if these assemblies are not detected, the following
message will be displayed.
File: d10545.docx
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 new Project Packager will run without any problems.
Note: This is a one-time action per machine.
Back
Upgrading projects with AVEVA Project Authentication enabled
Once AVEVA Project Authentication has been enabled, projects can be upgraded in two ways. Both
these methods require a SQL Server user login with the ‘dbowner’ role for the project.
The recommended method is to upgrade the projects via AVEVA Security Manager. Security
Manager by-passes the AVEVA Project Authentication and only allows Windows authentication or
SQL Server authentication to connect to the project.
If selecting Windows authentication, you will be asked to enter the Security Manager Administrator
username and password. Providing your Windows domain account has a ‘dbowner’ role for the
project, you will be able to upgrade the project.
If selecting SQL Server Authentication, you will be asked to enter a SQL Server login name and
password. Providing a login username and password is entered that has a ‘dbowner’ role for the
project, the project will upgrade. If a SQL login username and password is entered that does not
have a ‘dbowner’ role for the project, the upgrade will not be permitted.
The other method of upgrading a project is via the actual applications such as Engineer or Wiring
Manager. If one of these applications is launched and a pre-SP5 Fix 4 project is selected, you will
be first asked to enter the AVEVA Project user name and password.
Once you have entered these credentials, you will be asked if you wish to upgrade the project. If
you say yes to the various messages, you will be asked to enter the AVEVA Security Manager
Administrator username and password.
File: d10545.docx
Lastly you will see this SQL Server Admin Login dialogue.
The reason for this dialogue being presented is because the SQL login user being leveraged by the
new Project Authentication (IDOADMIN) does not have a ‘dbowner’ role for the project. To upgrade
the project from this point, a different SQL login username and password must be entered that
does have a ‘dbowner’ role for the project. This SQL login must be created by your SQL Server
administrators.
Back
Changing Project Authentication Type
AVEVA Instrumentation and AVEVA Electrical 12.1.SP3 to 12.1.SP5 Fix 5 allow projects to be
configured with 3 different authentication methods. These are Windows authentication, SQL Server
authentication and the new AVEVA Project authentication.
If the authentication type for a project needs to be changed, for example from Windows
authentication to AVEVA Project authentication, this must be done via Security Manager.
Irrespective of the authentication method (Windows or SQL Server) selected to connect to the
project via Security Manager, the user login on the SQL Server must have a ‘sysadmin’ role to
perform this task. Both changing authentication method for a project and changing the AVEVA
Project authentication password requires a login on the server with a ‘sysadmin’ role.
Most users will not have a ‘sysadmin’ role on the server. Therefore, to perform these tasks one of
two things must happen:
1. The SQL Server administrator assigns temporary a ‘sysadmin’ role to the user attempting
to change authentication method or AVEVA Project authentication password
2. A different user – that has a ‘sysadmin’ role on the server - must perform these task
Back
File: d10545.docx
AutoCAD 2016 SP1, 2017 & 2018 File Loading Security Concern
When launching AutoCAD 2016 (and above) from AVEVA Instrumentation 12.1.SP5 Fix 5, or AVEVA
Electrical 12.1.SP5 Fix 5 warning messages such as the following may be seen.
AutoCAD 2016 (and above) has inbuilt functionality for checking trusted locations of dll’s that are
being loaded. To prevent these types of message being displayed, implement the following steps:
1. Open any drawing in AutoCAD 2016 (and above)

2. Right click in the drawing area
3. Go to last option "Options"
4. Open 1st tab "Files"
5. Expand Node "Trusted Locations"
6. Add the following paths under the “Trusted Locations” node
AVEVA Instrumentation with a 32-bit O/S
C:\Program Files (x86)\AVEVA\Instrumentation12.1.5\AutoCAD2013\ACAddin32
AVEVA Instrumentation with a 64-bit O/S
C:\Program Files (x86)\AVEVA\Instrumentation12.1.5\AutoCAD2013\ACAddin64
For AVEVA Instrumentation the add-ins under the AutoCAD 2013 folder will work for all
supported versions of AutoCAD.
AVEVA Electrical with a 32-bit O/S
C:\Program Files (x86)\AVEVA\Electrical12.1.5\AutoCAD2016\ACAddIn32
AVEVA Electrical with a 64-bit O/S
File: d10545.docx
7. The trusted location paths detailed above are based on the default installation folders for
AVEVA Instrumentation 12.1.SP5 Fix 5 or AVEVA Electrical 12.1.SP5 Fix 5
8. Once the trusted locations have been added, the Security Concern messages should no
longer be displayed when launching AutoCAD 2015 (and above) from within AVEVA
Instrumentation 12.1.SP5 Fix 5 or AVEVA Electrical 12.1.SP5 Fix 5.
Back
Defining Process Equipment and Process Line Tag Formats
When defining tag formats for Process Equipment and Process Lines within the AVEVA
Instrumentation Process Engineer module, care should be taken when selecting fields to be used
as tag codes.
If a field has been defined in the project database to store process line data and this field is
selected as a process equipment tag code, data entered against this tag code will not be saved
correctly.
An example of this is “Rating”. Both process equipment and process lines can store a rating value.
However, in the database these are two separate fields; “PipeRating” and “Rating”. If “Rating”
(instead of “PipeRating”) is selected as a process line tag code, any data entered will not save
correctly.
To avoid this problem, first enter some data via the edit dialogues against the fields you wish to
use as tag codes. Next, add these fields to the Process Equipment or Process Line grids using the
Grid Manager function. Finally, check exactly which fields the data is written to by examining the
field names via Grid Manager.
AVEVA Product Development intend to enhance the way that Tag Code data is presented in a
future version, to ensure that it is easier to identify which fields should be used for process
equipment tag codes and which fields should be used for process line tag codes.
Back
Area Numbers on Reports following Project Upgrades
After upgrading projects, Instrument or Loop reports may no longer display area values. This is
because the area number is no longer stored in the InstrumentList or LoopList tables. Instead the
area data is now stored in the Area table. To fix the problem, edit the affected reports to display
the AreaNo data from the Area table instead of the AreaNo data from the InstrumentList or
LoopList tables. For further assistance, please contact AVEVA Technical Support
Back
How to avoid Timeout error during loading of grids
A timeout issue was reported for 12.1.SP2 when loading very large data sets via the default grids
in AVEVA Electrical and AVEVA Instrumentation. This has been addressed in 12.1.SP2 Fix 5 and
later releases.
File: d10545.docx
However, if any users have created their own grids and apply filters to these grids, the process of
filtering will slow down the loading of the grids and the timeout problem may resurface.
To avoid this problem users can adjust the existing setting “CommandTimeoutSeconds” in the
inst.ini file. Users can set higher values to avoid any timeout errors.
This is applicable for both AVEVA Electrical and AVEVA Instrumentation and all the grids.
Back
Importing Records where Field and Property Names Match
Problems will occur if data import is attempted where fields and properties are named identically.
To avoid this, ensure that properties are not named the same as any existing fields in the target
database tables.
The warning message will appear during import even if the Property is not mapped to the
equipment type.
Back
Properties Named with Underscores
Property names containing underscores are not supported in AVEVA Electrical and AVEVA
Instrumentation 12.1.SP5 Fix 5. To avoid problems with datasheet creation, reporting and grid
management, do not create properties that contain underscores.
Back
Importing Data via Microsoft Excel where duplicate field/column names are detected
For AVEVA Instrumentation and AVEVA Electrical 12.1.SP5 Fix 5 a solution has been implemented
for a problem discovered importing data via the Browse Data by Form Type grid. The problem
related to duplicate field and column names present in the grid and Excel spread sheets.
AVEVA Instrumentation and AVEVA Electrical will now display any duplicate column/field name
with a numeric suffix appended within the mapping screens for import. This change will impact all
grids where data can be imported via Microsoft Excel.
For example, if two “Description” fields/columns are detected, they will be presented as
“Description” and “Description1”. This will apply to all work sheets within a workbook. In the
example just described, the duplicate column name could be present on different worksheets.
A consequence of this change is that existing mappings defined in pre-SP3 projects may not
work, especially for importing data via the Equipment List in Wiring Manager. Here data for the
Major Equipment, Components etc. can be imported from multiple worksheets within the same
workbook. To re-use mapping defined in pre-SP3 projects, the multiple worksheets must be split
out into separate .xls or .xlsx files and imported via these individual files. Alternatively, the
mapping should be re-defined.
Back
File: d10545.docx
Integrating with AVEVA P&ID
AVEVA Instrumentation 12.1.SP5 Fix 5 can integrate with all released versions of AVEVA P&ID -
from 12.1 onwards - to enable the exchange of instrumentation data. However, there is a limit to
the maximum number of fields and properties published by AVEVA Instrumentation that AVEVA
P&ID can manage. Once this limit of 1024 has been exceeded, integration with AVEVA P&ID will no
longer function. AVEVA P&ID 12.1.SP2 Fix 1 (and above) has been modified to manage in excess of
1024 fields or properties and is therefore the version of AVEVA P&ID that is recommended for use
if integrating with AVEVA Instrumentation 12.1.SP5 Fix 5.
This may become an issue on live projects as AVEVA Instrumentation 12.1.SP5 Fix 5 publishes
both fields and properties for import and export. The creation of many new properties could push
the total of published fields and properties past the 1024 limit and would necessitate the use of
AVEVA P&ID 12.1.SP2 Fix 1 or higher in this scenario.
NOTE: Any existing compare/update mappings defined for projects using AVEVA Instrumentation
12.1.SP2, or earlier will still be available for use once a project has been upgraded to 12.1.SP5 Fix
5 and will still work with AVEVA P&ID 12.1.SP2.
AVEVA P&ID 12.1.SP2 Fix 1 is only required to define new compare/update mappings between
AVEVA Instrumentation 12.1.SP5 Fix 5 and AVEVA P&ID.
Back
Importing Data into a Shared Project Where Duplicate Property Names Exist for AVEVA Electrical
and AVEVA Instrumentation
Importing data into shared projects can be problematic if identically named properties exist in
both AVEVA Electrical and AVEVA Instrumentation. For example, if a Motor property named
“Prop01” is created in AVEVA Electrical and an Instrument property named “Prop01” is created in
AVEVA Instrumentation, importing data into AVEVA Electrical from other AVEVA integrated
applications can fail. To avoid this problem, ensure that all properties – in both AVEVA Electrical
and AVEVA Instrumentation – are named uniquely.
Back
Duplicate named fields and properties causing problems importing data from MS Excel
AVEVA Instrumentation and AVEVA Electrical 12.1.SP5 Fix 5 now allow both fields and properties
to be incorporated into the grids for data manipulation. Both field and property data can also be
imported from MS Excel via the grids. Exposing all the existing properties has led to some
instances where fields and properties with the same name and caption are displayed in the
mapping screen when importing from Excel. An example of this can be found within the
Instrument List. Now both InstrumentList.Description and ProcessData.Description are displayed
as “Description (Description)” when mapping the columns to fields.
File: d10545.docx
To enable users to differentiate between the two fields it is recommended that the captions are
updated. For example, change the caption for InstrumentList.Description from “Description” to
“Instrument Description” as follows.
Manage InstrumentList Grid
Display in Instrument List Grid
Mapping Screen
Back
File: d10545.docx
Leading Spaces in Column Name Causing Problems Importing from MS Excel
A problem occurs if users attempt to import data from Excel if fields are mapped to Excel columns
that have names with leading or trailing spaces. To avoid this problem, please ensure that all
leading or trailing spaces have been removed for any Excel columns names mapped for data
import. The message displayed states, “Field ‘ABC’ does not exist in the current import file.”
For example…
In this case the column “Degree of protection” existed in Excel, but there are trailing spaces at the
end of the column name. Removing these spaces enabled the data to import successfully.
Back
Problems Initialising AVEVA Engineering for Integration
When configuring AVEVA Electrical or AVEVA Instrumentation to integrate with AVEVA Engineering
please ensure that AVEVA Engineering is not running on the background. If users attempt to
integrate AVEVA Electrical or AVEVA Instrumentation with AVEVA Engineering running, a fail to
initialise error message will be displayed. To avoid this, simply ensure that AVEVA Engineering is
not running in the background whilst trying to configure the integration with AVEVA Electrical and
AVEVA Instrumentation.
Back
Installation Steps for AVEVA Integration Service
The following steps need to be followed to enable integration between AVEVA Instrumentation
12.1.SP5 Fix 5 and other AVEVA applications via the AVEVA Integration Service.
Server Setup
1. From the AVEVA Instrumentation 12.1.SP5 Fix 5 installation (MSI) folder on the DVD,
extract the file InstrumentationIntService.msi
File: d10545.docx
2. Copy InstrumentationIntService.msi on to the machine (located on your network) that is

hosting the AVEVA Integration Service
3. Run the InstrumentationIntService.msi installer to add the AVEVA Instrumentation

Integration Service
4. Follow AVEVA Integration Service 1.x Installation Guide section 5.3 AVEVA
Instrumentation/Electrical to add AVEVA Instrumentation/Electrical projects to the AVEVA
Instrumentation Integration Service
5. Follow AVEVA Integration Service 1.x Service Guide section 3.3.5 AVEVA Instrumentation, or
section 3.3.6 AVEVA Electrical to add AVEVA Electrical or AVEVA Instrumentation as a data
source
Client Setup
1. Download and copy the AVEVA Integration Service 1.x installer to all the workstations
running AVEVA Instrumentation 12.1.SP5 Fix 5
2. Run the installer AVEVA_Integration_Service 1.x.msi and install the Integration Client, not
the Integration Service
3. Follow the steps documented in the AVEVA Instrumentation 12.1.SP5 Common
Functionality Guide section 7.4.1 AVEVA Integration Import Configuration to setup
integration between AVEVA Instrumentation and other AVEVA applications
Back
Scenarios Whereby a Blank Compare/Update Dialogue is presented

1. Importing one object type i.e. Loops when a grid for a different object type is active i.e.
Instruments
a. Workaround to have grid active for object types being imported
2. Attempting to import using a group/mapping for product version “A” whilst connecting to
product version “B”
a. Workaround is to ensure that the selected group/mapping relates to the connected
product version
3. Attempting to import using a group/mapping for project hosted on machine “A” whilst
connecting to machine “B”
File: d10545.docx
a. Workaround is to ensure that the selected group/mapping relates to the connected
machine
4. Mapped dabacon UDAs are deleted or their name is changed via Lexicon
a. Workaround is to remove mapped UDA from mapping before deleting or changing
via Lexicon
5. Delete and Add again the same project configuration in the Integration Settings Editor
a. Workaround is to recreate mapping once the project configuration has been added
back
Back
Upgrade problems if a project contains a pick-list named “Yes/No”

If a pre-12.1.SP5 Fix 5 project contains a pick-list named “Yes/No” (as shown below) this will
cause a problem when upgrading the project to 12.1.SP5 Fix 5.
This is because the 12.1.SP5 Fix 5 upgrade process is trying to add a pick-list named “Yes/No”,
related to the cable installation management reports and grids. Therefore, a conflict will occur,
and an exception error displayed whilst the software attempts to upgrade the project to 12.1.SP5
Fix 5. To enable the upgrade to complete without errors, the pick-list in the pre-12.1.SP5 Fix 5
project must be renamed.
Steps to follow:
1. Remove “Yes/No” pick-list for all applicable grids via the Manage options
2. Rename “Yes/No” pick-list, for example “Yes-No”
3. Add the renamed pick-list back to all applicable grids via the Manage options
Back
Importing terminal label values from MS Excel

When importing terminal label values from a Microsoft Excel spreadsheet, the column headers for
equipment number and terminal label value cannot contain spaces, see below.
File: d10545.docx
If terminal label values are not being imported, the equipment number column header can contain
spaces.
This problem will be addressed in a fix release for AVEVA Instrumentation and AVEVA Electrical
12.1.SP5.
Back
AVEVA Instrumentation Enhanced Cable Block Diagram symbol named “Field Device” causes
upgrade problems
If an Enhanced Cable Block Diagram symbol has been created in AVEVA Instrumentation Wiring
Manager named “Field Device”, problems can be experienced upgrading projects. This is because
AVEVA Electrical Wiring Manager out-of-the-box has an Enhanced Cable Block Diagram symbol
also named “Field Device” and the upgrade process currently sees this as a conflict.
To avoid this project upgrade problem simply name the symbol in AVEVA Instrumentation Wiring
Manager as “Field Device AI", or similar.
This problem will be addressed in a fix release for AVEVA Instrumentation and AVEVA Electrical
12.1.SP5.
Back
AutoCAD STARTUP and STARTMODE system variable

For the AVEVA Electrical and AVEVA Instrumentation drawing creation functionality to work
successfully, the AutoCAD system variables “STARTUP” & “STARTMODE” must be set to 0 (zero).
To set this variable simply launch AutoCAD and type “STARTUP” or “STARTMODE” at the command
line. The out-of-the-box settings are 1, simply change these to 0 (zero) and close AutoCAD.
Once these variables are set, AutoCAD will remember the values.
Back
Enhanced Cable Block Diagram Title Block Clouding

To prevent ECBD title blocks from being clouded when changes have not been made to the title
block data, the internal AutoCAD block that (defines the drawing title block) within the ECBD seed
file needs to be specified.
If the ECBD seed file is edited, a new option is presented whereby users can now select the Title
Block name. This name is read from the internal block table within the actual .dwg file.
Back
File: d10545.docx

D 10545

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

D 10545

Caricato da

Copyright:

Formati disponibili

QA4/1, QA7/2 & QA11/3 - DNote v4.

Product Release Letter

Partial Fix Release 10545-1

This Release Contains

This document has been prepared and approved by the following:

Prerequisite for this release - products:

Works (is compatible) with:

12.1.SP2 Fix 11 & above No *Yes *12.1.SP2 Fix 5 and above

14.1.SP1, 14.1 SP1 Fix 1 & above Yes Yes

14.1& 14.1 Fix 1 & above No Yes

PDMS & Marine Engineering

PDMS & Marine Diagrams

PDMS & Marine Design

12.1.SP5 & above Yes *No *See Note 1 below

To install product release:

• AVEVA Instrumentation 12.1.SP5 (Full release 10526-1)

• AVEVA Instrumentation 12.1.SP5 Fix 2 (Partial release 10537-1)

• AVEVA Instrumentation 12.1.SP5 Fix 3 (Partial release 10540-1)

• AVEVA Instrumentation 12.1.SP5 Fix 4 (Partial release 10543-1)

First released on:

List of Fault Corrections

Consolidated from previous releases

First released in AVEVA Instrumentation 12.1.SP5 Fix 4, Release No. 10543-1

Incident Defect Product / Description

Incident Defect Product / Description

Incident Defect Product / Description

First released in AVEVA Instrumentation 12.1.SP5 Fix 1, Release No. 10533-1

Incident Defect Product / Description

First released in AVEVA Instrumentation 12.1.SP5, Release No. 10526-1

Incident Defect Product / Description

PRODUCT QUALITY STATEMENT

Important Points to Note

Mapping Tag Codes to Enable Integration

Mandatory Fields to map for import:

Project Packager and Microsoft’s Shared Management Objects (SMO)

Upgrading projects with AVEVA Project Authentication enabled

Changing Project Authentication Type

1. Open any drawing in AutoCAD 2016 (and above)

AVEVA Instrumentation with a 32-bit O/S

C:\Program Files (x86)\AVEVA\Instrumentation12.1.5\AutoCAD2013\ACAddin32

AVEVA Instrumentation with a 64-bit O/S

C:\Program Files (x86)\AVEVA\Instrumentation12.1.5\AutoCAD2013\ACAddin64

AVEVA Electrical with a 32-bit O/S

C:\Program Files (x86)\AVEVA\Electrical12.1.5\AutoCAD2016\ACAddIn32

C:\Program Files (x86)\AVEVA\Electrical12.1.5\AutoCAD2017\ACAddIn32

C:\Program Files (x86)\AVEVA\Electrical12.1.5\AutoCAD2018\ACAddIn32

AVEVA Electrical with a 64-bit O/S

C:\Program Files (x86)\AVEVA\Electrical12.1.5\AutoCAD2016\ACAddIn64

C:\Program Files (x86)\AVEVA\Electrical12.1.5\AutoCAD2017\ACAddIn64

Defining Process Equipment and Process Line Tag Formats

Area Numbers on Reports following Project Upgrades

How to avoid Timeout error during loading of grids

Importing Records where Field and Property Names Match

Properties Named with Underscores

Manage InstrumentList Grid

Display in Instrument List Grid

Problems Initialising AVEVA Engineering for Integration

Installation Steps for AVEVA Integration Service

2. Copy InstrumentationIntService.msi on to the machine (located on your network) that is

3. Run the InstrumentationIntService.msi installer to add the AVEVA Instrumentation

Scenarios Whereby a Blank Compare/Update Dialogue is presented

Upgrade problems if a project contains a pick-list named “Yes/No”

Importing terminal label values from MS Excel

12.1.SP2 Fix 11 & above No Yes 12.1.SP2 Fix 5 and above

12.1.SP5 & above Yes No See Note 1 below