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

24 (6-May-14)

Product Release Letter

AVEVA Instrumentation 12.1.SP3 Fix 9 (32 bit)

Partial Release 10517-1

Windows 7 SP1 (32 bit or 64 bit) & Windows 8.1 (64 bit)
Dear Customer
This letter introduces and describes this release, which is supported on the indicated platform(s).

This Release Contains

A partial release of AVEVA Instrumentation, which upgrades the full release 10496-1 AVEVA
Instrumentation 12.1.SP3.

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 (Plant): 12.1.SP3
Instrumentation Engineer
Instrumentation Designer
Instrumentation Wiring Manager
Process Engineer
Instrumentation Security Manager
V00FN427 AVEVA Instrumentation with following modules (Marine): 12.1.SP3
Instrumentation Engineer
Instrumentation Designer
Instrumentation Wiring Manager
Process Engineer
Instrumentation Security Manager
V00FN690 AVEVA NET Instrumentation Gateway 12.1.SP3

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
AVEVA Electrical and AVEVA Instrumentation
Product Manager
System Test Manager Kishore Grandhi
Test Manager
TPS Representative for EDS products Semra Hamitogullari Åberg
Manager, Training and Product Support (EDS)

File: d10517.docx
Last saved: 3rd June, 2016  Copyright 2016 AVEVA Solutions Limited Page 1 of 26
 Product Release Letter
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)
Mandatory O/S Patches (for each Microsoft Windows 7 SP1 or Windows 8.1 base
supported platform) release
Build Operating System Microsoft Windows 7 SP1 (64 bit)

* See Windows 8.1 Support in Important Points to Note section of this document for information
about required Microsoft .NET Framework versions when deploying AVEVA Instrumentation
12.1.SP3 with Windows 8.1.

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 Instrumentation 12.1.SP3
o Full 12.1.SP3 release 10496-1
o See http://support.aveva.com
 AVEVA Licensing System 1.3 or 2.0 and an appropriate licence file
o Please see AVEVA Licensing
o AVEVA Flexman licensing no longer supported
o ALS 1.3 is not supported for Windows 8.1 and therefore it must be installed on a
machine with a supported operating system. Please read the ALS 1.3 installation
guide for details
 Microsoft .NET Framework 4.0
o The English version is included in the Product folder under Microsoft .NET
Framework 4.0 English. For all other versions please see
http://www.microsoft.com/en-gb/download/details.aspx?id=17718
o See Windows 8.1 Support in Important Points to Note section of this document
 Microsoft Office 2007, 2010 or 2013 (32 bit or 64 bit)
o Required to open datasheets within AVEVA Electrical and AVEVA Instrumentation
12.1.SP3

Works (is compatible) with:

 AVEVA Electrical 12.1.SP3 Fix 11
 AVEVA Engineering 14.1.0 including Fixes 1, 2, 3 & 4
 AVEVA Engineering 14.1.SP1 including Fix 1, 2 & 3
 AVEVA Diagrams 14.1 including Fix 1, 2 & 3
 AVEVA Integration Service 1.0, 1.1 & 1.2
 AVEVA Administration 1.2 and above
 AVEVA P&ID 12.1 and above (32 or 64 bit)
o 12.1.SP2 Fix 1 or above recommended*
 AVEVA PDMS 12.1 and above

File: d10517.docx
Last saved: 3rd June, 2016  Copyright 2016 AVEVA Solutions Limited Page 2 of 26
 Product Release Letter
 AVEVA Outfitting 12.1 and above
 AVEVA E3D 1.1 & 2.1
 AVEVA NET Portal 4.7 and above
 AVEVA NET Workhub & Dashboard 5.0 and above
 AutoCAD 2013, 2014 & 2015
o VBA Enabler for AutoCAD not required for AVEVA Instrumentation 12.1.SP3
 Microsoft Excel 2007, 2010 and 2013
 Microsoft SQL Server 2008 R2 SP2, 2012 & 2012 SP1
o SQL Server Express also supported
 Citrix XenApp 6.5 (64 bit)**

* 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
http://usa.autodesk.com/adsk/servlet/item?siteID=123112&id=13959101

Integration Matrix
This fix/update release of AVEVA Instrumentation 12.1.SP3 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
only for the latest versions.
The following table indicates which method of integration can be deployed with AVEVA
Instrumentation 12.1.SP3 Fix 9.
AVEVA P&ID Local Integration Services Integration Notes
12.1 to 12.1.SP2 Fix 1 Yes No
12.1.SP2 Fix 2, 3, 4, 5, 6 & 7 Yes *Yes *12.1.SP2 Fix 5 and above
needed to import loop data
AVEVA Engineering
14.1 Yes No
14.1 Fix 1 & 2 Yes No
14.1 Fix 3 & 4 Yes Yes
14.1.SP1 & 14.1.SP1 Fix 1, 2 & 3 Yes Yes
AVEVA Diagrams
14.1& 14.1 Fix 1, 2 & 3 No Yes
PDMS Engineering
12.1 to 12.1.SP2 Fix 36 Yes No
12.1.SP4 Fix 17 to Fix 23 Yes *No *See Note 1 below
PDMS Diagrams
12.1 to 12.1.SP2 Fix 36 Yes No

File: d10517.docx
Last saved: 3rd June, 2016  Copyright 2016 AVEVA Solutions Limited Page 3 of 26
 Product Release Letter
12.1.SP4 Fix 17 to Fix 23 Yes *No *See Note 1 below
PDMS Schematic Model Manager
12.1 to 12.1.SP2 Fix 36 Yes No
12.1.SP4 Fix 17 to Fix 23 Yes *No *See Note 1 below
PDMS Design
12.1 to 12.1.SP2 Fix 36 Yes No
12.1.SP4 Fix 17 to Fix 23 Yes *No *See Note 1 below
E3D Design
1.1 and fixes Yes *No *See Note 1 below
2.1 Yes *No *See Note 1 below

Notes:
1. Will be supported in the future release of AVEVA Instrumentation
2. 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 previous fix release 10512-1, AVEVA Instrumentation 12.1 SP3 Fix 8.

To Install product release

Please run the file Instrumentation12.1.3.9.EXE.

Running this executable will upgrade the following installations to AVEVA Instrumentation
12.1.SP3 Fix 9:

 AVEVA Instrumentation 12.1.SP3 (Full release 10496-1)

 AVEVA Instrumentation 12.1.SP3 Fix 1 (Partial release 10497-1)

 AVEVA Instrumentation 12.1.SP3 Fix 2 (Partial release 10500-1)

 AVEVA Instrumentation 12.1.SP3 Fix 3 (Partial release 10503-1)

 AVEVA Instrumentation 12.1.SP3 Fix 4 (Partial release 10504-1)

 AVEVA Instrumentation 12.1.SP3 Fix 5 (Partial release 10505-1)

 AVEVA Instrumentation 12.1.SP3 Fix 6 (Partial release 10510-1)

 AVEVA Instrumentation 12.1.SP3 Fix 7 (Partial release 10512-1)

 AVEVA Instrumentation 12.1.SP3 Fix 8 (Partial release 10516-1)

Run the file AVEVA.AutoCADUpdate.exe to update AutoCAD binaries that enable the AutoCAD
based features of AVEVA Instrumentation to function correctly.

NOTE: This update should be applied for all supported versions of AutoCAD (2013, 2014, 2015)
and for both 32-bit or 64-bit operating systems.

File: d10517.docx
Last saved: 3rd June, 2016  Copyright 2016 AVEVA Solutions Limited Page 4 of 26
 Product Release Letter
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.

First released on
This product release is first available via the AVEVA support website http://support.aveva.com as
AVEVA Instrumentation 12.1.SP3 Fix 9, release number 10517.

List of Fault Corrections

This release addresses defects arising from the following support incidents
Incident Defect Module Description
number number
90810 196127* Designer Decimal comma problems when producing drawings
91209 195847* Wiring Limit of 88 conductors when creating cable catalogue entries
Manager
91834 198721* Wiring Connections lost when IO module channel numbering changed
Manager
91839 198722* Wiring Unnecessary locks imposed in Wiring Manager
Manager
91863 198049 Wiring Enabling security impacts cable schedule grid performance
Manager
91911 197480* Engineer Exception when trying to delete a datasheet form
93573 200068 Engineer Units displayed multiple times in grids
92621 199166* Engineer Changing loop tag is not updating associated instrument area
paths
92948 199407* Process 3rd party license file message when viewing datasheets from
Engineer Process Engineer
93568 200066* Engineer Unit conversion problems on datasheets
93572 200067* Engineer Problems using a decimal separator that is different to the
regional settings
92534 199170* Engineer Problems splitting values and units for fractional values i.e. ½”
94136 202021* Engineer Instrument data sheet issues after upgrade from SP1

Note: * indicates that the issue is not corrected in AVEVA Instrumentation 12.1.SP4 but will be
corrected in AVEVA Instrumentation 12.1.SP4 Fix 1.

Consolidated from previous fix releases

First released in Fix Version AVEVA Instrumentation 12.1.SP3 Fix 8, Release No. 10516-1
Incident Defect Module Description
number number
89733 192187 Engineer Problems with report change highlighting when security is
enabled
87755 193467 Designer Problems when using decimal comma in hook-up BOM
quantities
n/a 193469 Engineer Compare/Update does not display data if the source
application contains item(s) previously created in AVEVA
Electrical or Instrumentation

File: d10517.docx
Last saved: 3rd June, 2016  Copyright 2016 AVEVA Solutions Limited Page 5 of 26
 Product Release Letter
Incident Defect Module Description
number number
n/a 194184 Engineer Records imported as new instead of updated into AVEVA
Instrumentation Engineer
n/a 194188 Engineer Unable to save projects which have been added into Aveva
Electrical or AVEVA Instrumentation data service settings
window for AVEVA Integration Service

First released in Fix Version AVEVA Instrumentation 12.1.SP3 Fix 7, Release No. 10512-1
Incident Defect Module Description
number number
86166 183914 Security Problems Importing Security Manager Setting from One Project
Manager Into Another
86740 185036 Wiring Creating Equipment from Complex Major Equipment
Manager Catalogue Items causing SQL timeout
85888 183250 Engineer Area Description and Area Short Description field length
increase
81882 174631 Wiring Error Message is displayed while assigning PLC IO to IO
Manager module

First released in Fix Version AVEVA Instrumentation 12.1.SP3 Fix 6, Release No. 10510-1
Incident Defect Module Description
number number
76813 161919 Engineer Loop copy wizard not working for loops in same area
79466 168295 Designer Cable numbers not aligned properly on termination drawings
81451 173474 Engineer Problems with 'Order By' Attribute in grids
77356 161349 Engineer LoopKey association missing in Integration Services
79082 167426 Engineer Adding New Instrument causes a NullReferenceException Error
79339 167935 Engineer Revisions Button in the actions pane doesn't work if security
rights are enabled
78563 166669 Designer Template displays instead of the drawing once the template is
modified
79575 168710 Engineer Exception when ISALocation is not included in the excel
mappings when duplicate virtual tagging is enabled
78592, 165110, Designer Global Datalink Edit is not available
75207 164942
79577 168712 Engineer Error when creating loop wiring from the Loop Detail window
77290 164963 Engineer Problems copying a loop without using the Copy wizard
78556 168970 Wiring Recursivity SQL errror message
Manager
77495 161843 Wiring Exception when creating an Area via Equipment View
Manager
75271 156109 Engineer Area path not updated correctly by Copy Wizard when
incorporated into tag number
75876 157339 Wiring Possible to add cables of different catalogue type to same
Manager cable drum
74436 152556 Wiring Complex wiring rules featuring multiple junction boxes not
Manager working correctly
74714 154778 Designer Problems with looping wire graphics on termination diagrams
77671 168865 Wiring Wire Rule copy does not work correctly after second copy
Manager
80018 169982 Designer Cable number not visable on temination diagrams

File: d10517.docx
Last saved: 3rd June, 2016  Copyright 2016 AVEVA Solutions Limited Page 6 of 26
 Product Release Letter
Incident Defect Module Description
number number
79646, 168917, Security Problems upgrading project to latest version
79480 168357 Manager
79465 168293 Designer Cable pairs and screen are overlapping on termination
diagrams
79496 168551 Engineer Open Datasheet doesn’t commit changes to record
79575 168710 Engineer Exception when ISA location is not included in the excel
mappings
82590 176045 Engineer, Poor performance opening Process Data grid
Process
Engineer
82999 176561 Designer Unable to enter date drawn, design, checked or approved
83280 177220 Security Upgrade issue when data contains apostrophe
Manager
83024 176623 Engineer Not possible to import data from Excel when Area No contains
dot
82962 176587 Engineer Grid view sorting not saved
n/a 165850 Wiring Edit Termination throwing warning message, “Your project
Manager database is not compatible with this version of AVEVA Inst I/O
assignments. Please contact AVEVA.”
n/a 170020 Engineer Unhandled exception is seen when trying to create a loop
(which has duplicate instruments in different locations
assigned) through copy wizard
n/a 167228 Engineer Services integration validation message is incorrect when
trying to update the record which is given No Access
n/a 168916 Wiring ArgumentException “Item has already been added” error
Manager message appears on edit of I/O catalogue of I/O module from
equipment view tab
n/a 168582 Security Project and SQL Authentication Login Security Check failing
Manager for Service Integration with AVEVA Instrumentation
n/a 167447 Wiring Saved mapping is changed and not able to use saved mapping
Manager for IO Allocation import
n/a 161086 Engineer Unable to delete the value in the user defined property
through bulk select in Instrument grid
n/a 170764 Engineer, Description in not displayed in Wiring manager when
Wiring “Requires Power Supply” option is checked and wiring is
Manager created for an Instrument in Engineer
n/a 170426 Engineer, Description in not Updated in Engineer when updated from
Wiring Equipment List Grid in Wiring manager
Manager
n/a 167709 Engineer Area value not displaying correctly in Loops sub-grid
n/a 168028 Engineer Data entered against Instrument and Process data properties
is not copied by copying the loop without using CopyWizad
n/a 168040 Engineer Suffix not appended to Instruments by copying the loop
without using CopyWizad
n/a 168116 Engineer Sorting is not working while assigning Instruments to Loop in
Loop Edit window and also through Copy Loop withoout using
Copywizad
n/a 170441 Engineer, Description in not updated in Engineer when changed via
Wiring Equipment List grid in Wiring manager
Manager
n/a 165278 Wiring E3D2.1 option not appearing in local integration Cable Design
Manager Import Configuration window

File: d10517.docx
Last saved: 3rd June, 2016  Copyright 2016 AVEVA Solutions Limited Page 7 of 26
 Product Release Letter
Incident Defect Module Description
number number
n/a 177911 Engineer Problems when field and property captions contain
apostrophes

First released in Fix Version AVEVA Instrumentation 12.1.SP3 Fix 5, Release No. 10505-1
Incident Defect Module Description
number number
n/a 163501 Security After clicking Add User button in Security Manager Domain
Manager name and User name fields are empty
n/a 161772 Security Areas are not being greyed out if they are in RO access
Manager
76628 159238 Security Security manager Module not opening when upgraded first
Manager time
76599 159188 Engineer Exception error when importing without any grid open
76597 159186 Engineer The compare/update window incorrect
73641 150868 Engineer Error when creating loop wiring from the Loop Detail window
67120 128810 Engineer Compare/Update: Filtering in compare and update in PDMS for
instruments by function code
70831 143614 Engineer Layout of Grid Views Not Saving
71804 145772 Process Adding new associated ProcessLine deletes exisiting Process
Engineer Equipment
78222 163986 Security Can't open Security Manager with usual Password
Manager
n/a 153722 Wiring Changes to catalogue values need to get reflected in the cable
Manager schedule audit log
77261 161032 Engineer Bulk editing new property on the instrument grid not saving
after refresh
76551 159189 Engineer Changing the attribute and using the copy wizard brings
about an exception
77958 163135 Security Can’t upgrade from 12.0.SP5 to 12.1.SP2
Manager
n/a 161292 Process Changes made for the User Defined properties of Process
Manager equipment grid is not captured in the Audit log manager
window
n/a 161589 Engineer Clicking on Select all for copying in the copy window throws
an Argument exception and further modifying the suffix and
clicking on next says unable to update area
n/a 163422 Wiring Descriptions not updating for field device/instrument tags
Manager "linked" between WM and Engineer
n/a 161401 Designer Drawing and Hookup drawing files are not getting published
into the AVEVA NET portal staging area in designer module
13818 70641 Engineer User is able to import from Excel plant areas that are not in
the pick list
77426 162301 Wiring Locked pick-lists for cable user fields are not presented in the
Manager Edit Cable dialogue enabling any data to be entered
n/a 162124 Wiring Exception is thrown when "Cable cores not terminated" Option
Manager is selected from Fixed reports
n/a 156745 Wiring Field bus device Cable disappeared on Reopen with edit
Manager termination window
77790 162561 Engineer Issue with Compare/Update in Diagrams 12.1.SP3 Fix 4
77382 161504 Engineer Not possible to import instrument from Excel the application
crashes

File: d10517.docx
Last saved: 3rd June, 2016  Copyright 2016 AVEVA Solutions Limited Page 8 of 26
 Product Release Letter
Incident Defect Module Description
number number
76698 159846 Engineer Argument Exception occurred in
Aveva.instrumentation.Engineer.exe
n/a 137377 Engineer Tag Code validation when importing via integrated AVEVA
applications
53797 89628 Engineer DB Update with P&ID changes Instrument type FIT to FI
69782 139433 Wiring Electrical Cables are not shown in AI by default when the
Manager project is shared
75084 154232 Wiring Cross patching with I/O modules error when selecting the
Manager “parent” enclosure in the Equipment View
78275 164145 Wiring Cable Schedule grid Layout is not respected
Manager
n/a 114361 Wiring Issues Relating to Importing data from Schematics Model
Manager Manager
n/a 114363 Engineer User Count not Functioning when Importing Data
n/a 164843 Wiring Cables created from an Instrumentation cable catalogue entry
Manager and shared with Electrical are being greyed out and any cable
created after that are greyed out immedialtely after creation
n/a 76411 Engineer Instrument and Loops can be imported with an area value that
is not present in the project
n/a 157335 Engineer Invalid data imported against locked pick-list fields from
AVEVA Diagrams 12.1.SP4
n/a 160636, Engineer Compare/Update: Filtering in compare and update in PDMS for
148810 instruments by function code
n/a 114356 Engineer Importing reports containing sub-reports into an upgraded
project
n/a 114359 Wiring Application crashes or exits if the user tries to perform Edit
Manager Terminations on the Marshalling Panel with many DIN rails
n/a 161235 Engineer An exception is thrown when pasting the data in to the note
field in the data sheet excel sheet
n/a 156029 Wiring Performance Issue, cable schedule Grid is taking more than 2
Manager mins to open when security is enabled
n/a 151759 Wiring Overall Screen is not saved for Cable catalogues with Group
Manager Type as Cores and No. of Cores as 1
n/a 156480 Engineer Duplicate AREA being created
n/a 157205 Engineer AVEVA Integration Service with Diagrams, Imported Loop type
value is not getting updated in loop tag dailog
n/a 163394 Wiring Cable is changed from instrumentation to Electrical discipline
Manager when an instrumentation cable is assigned with shared cable
catalogue
n/a 163933 Engineer Local Integration - Count for "Existing tag will be Update" is
shown wrong
n/a 164123 Engineer No Access records are seen when invoking property definition
window and close the grid
n/a 164259 Engineer Local Integration - Import wizard showing wrong count for
Unchanged Existing Tags
n/a 164427 Designer Location Code is unavailable in the Datalinks for loop
drawings
n/a 165649 Engineer After importing records from AVEVA Engineering14.1,I via
Local Integration, results log displays user defined and system
defined property definition twice
n/a 166125 Engineer Unable to create a record by changing the Area no. or
Function through copy wizard window

File: d10517.docx
Last saved: 3rd June, 2016  Copyright 2016 AVEVA Solutions Limited Page 9 of 26
 Product Release Letter
Incident Defect Module Description
number number
n/a 166153 Engineer Description for Tags is not shown in "select connected Tag ... "
window while creating wiring for instruments
n/a 78865 Designer User claims functionality is not working properly for Seed
Files, Hookup Templates and Hookup Item Catalogue Entries
n/a 114357 Engineer Problems Importing Large Datasets
n/a 89032 Wiring Unable to login to projects through compare/update window
Manager if PDMS and AVEVA Instrumentation or Electrical are installed
on different drives

First released in Fix Version AVEVA Instrumentation 12.1.SP3 Fix 4, Release No. 10504-1
Incident Defect Module Description
number number
74797 153485 All General performance improvements in grid management and
MS Excel import
74238 152269 Engineer Deleted instrument and loop data not captured in audit log
when security is enabled
73663 150923 Security Timeout upgrading large projects when resolving DB collation
Manager conflicts
74729, 153479, Engineer Datasheet Document List publish to PDF problems
74676 153472
74678 153025 Wiring Unable to see cable block diagrams and enhanced cable block
Manager diagrams following project upgrades from SP3, Fix 1, Fix 2
and Fix 3
n/a 152467 Wiring Audit log not capturing the fieldbus device creation
Manager

First released in Fix Version AVEVA Instrumentation 12.1.SP3 Fix 3, Release No. 10503-1
Incident Defect Module Description
number number
74483 152635, Engineer Performance issues when creating sub-areas for project
155521 containing complex project breakdown structures
47658 152986, Engineer Unable to import tagged items via AVEVA Diagrams Import
154048, when non mandatory fields are mapped
n/a 154194, Engineer Unable to import/update the loops from engineering 14.1
153903

First released in Fix Version AVEVA Instrumentation 12.1.SP3 Fix 2, Release No. 10497-1
Incident Defect Module Description
number number
62991 114814 Engineer Field List for filters in Grid Manager and Report Manager not
in alpha-numeric order.
69996 140150 Designer Physical .dwg file not removed when a drawing is deleted from
Designer grid if Sheet Number increased to 3 digits in Project
Options
67739 131346 Wiring Enhanced Termination Report not keeping changes when
Manager saved
72022 147101 Security Importing Security Manager settings from another project for
Manager AI overwriting AE Security Manager settings and vice-versa
67840 134620 Wiring
Manager Segment Check Report generates timeout exception
68841 136466 Engineer Area Path field cannot be moved in grids and is always fixed
to left hand side

File: d10517.docx
Last saved: 3rd June, 2016  Copyright 2016 AVEVA Solutions Limited Page 10 of 26
 Product Release Letter
Incident Defect Module Description
number number
72821 148730 Engineer Reports referencing InstrumentList Area field failing when
projects upgraded from SP2 to SP3
72822 148731 Wiring Application freezing when running I/O Fixed report following
Manager upgrade from SP2 to SP3
72698 148439 Security
Manager Project Packager failing with SQL Server Authentication.
73503 150360 Engineer Filtering reports via properties or process data not working
correctly
73493 150512 Engineer Poor performance of Instrument List grid actions if user is not
an Administrator
73136 150832 Engineer Erratic UI behaviour when editing instruments
73582 150660 Security Cannot open instrument grid after upgrade with security
Manager enabled
73921 151476 Wiring Overall Screen not being saved correctly creating new cable
Manager catalogue entries
73882 151874 Security Project upgrade problems related to modified templates for
Manager issued drawings.
n/a 149424 Wiring Design Length in the Cable Details is importing 'Total Length'
Manager value instead of 'Total length excluding excess' value
n/a 129169 Engineer Updates not appearing in Instrument List grid when clicking
Apply button on Instrument Edit dialogue
n/a 149933 Engineer Savings changes to instrument data taking too long.
n/a 150015 Wiring Routing Status in the Cable Details window shows Unrouted
Manager for a Routed cable
n/a 150730 Wiring Add Button is enabled in "Cables on Cable Drum" Window of
Manager Cable Drum Detail even if applied secuiry is Read-only
n/a 139807 Engineer Exception with .xlsx Datasheets when publishing to AVEVA
NET
n/a 139813 Engineer Exception with .xlsx Document List when publishing to AVEVA
NET
n/a 143193 Engineer Changes made to display order not being preserved using grid
manage tools
n/a 150912 Designer Check for new CBD's is enabled in the menu even if access to
drawings is read-only
n/a 150914 Designer Revison command enabled for right-click even if access to
drawings is read-only
n/a 150958 Engineer Instrument Copy Selected command is removing filters from
the grid
n/a 157699 Engineer Field mappings lost when reused for Excel Import

First released in Fix Version AVEVA Instrumentation 12.1.SP3 Fix 1, Release No. 10497-1
Incident Defect Product / Description
number number Module
68707 136043 Designer .DWG file not closed/released when drawing is issued
68716 136083 Wiring Display order of Enhanced Cable Block Diagrams in DESIGNER
Manager New Drawings dialogue is by document internals I.D. and not
by document name/number
69246 137959 Engineer Unable to Import from Excel into Browse Data by Form Type
67735 131352 Engineer Browse-Data-By-Form-Type Not Working
n/a 141412 Engineer With duplicate cells in BDBFT grid unable to Import from Excel
into Browse Data by Form Type

File: d10517.docx
Last saved: 3rd June, 2016  Copyright 2016 AVEVA Solutions Limited Page 11 of 26
 Product Release Letter
Incident Defect Product / Description
number number Module
71857 145918 Process Process data properties pcFluidPhase and pcCorrosiveProps
Engineer are not available for inclusion within data entry grids or for MS
Excel import mapping
71858 145919 Engineer Loop Copy Wizard is not copying associated instrument data

PRODUCT QUALITY STATEMENT

The development, maintenance and testing of AVEVA Solutions’ software products is carried out in
accordance with the company’s KEYSTONE 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
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
This document has been prepared before Acceptance Testing. This product release will be
subjected to an acceptance test by AVEVA’s Product Readiness Authority (PRA).

Any exceptions found during Acceptance Testing or after release will be reported in the
Product Release Latest Update note on AVEVA's support web site
http://downloads.aveva.com/10517/w10517.pdf

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 86688 Process Equipment & Process Line The action of associating an
Associations not being captured instrument with items of plant
in Audit Log equipment or process lines within
AVEVA Instrumentation is not
currently being captured in the audit
log

File: d10517.docx
Last saved: 3rd June, 2016  Copyright 2016 AVEVA Solutions Limited Page 12 of 26
 Product Release Letter
Incident Defect Description Recommended Workaround
number number
53942 89846 Picture/Logo Sizing on Problems have been discovered with
Datasheets the sizing of images inserted into
datasheet templates when the
corresponding datasheets are
previewed within AVEVA
Instrumentation. This problem is a
defect within the 3rd party
components used by AVEVA
Instrumentation and Electrical and
has been reported to the respective
suppliers. To avoid this issue please
insert any image files in BMP format
N/A 129886, Problems printing/exporting to Intermittent problems have been
130884 PDF observed printing and exporting to
PDF from both AVEVA Electrical and
AVEVA Instrumentation 12.1.SP3. This
may be due to limitations in the 3rd
party control used for this document
creation in a 64-bit environment. If
you experience problems printing or
exporting to PDF, please contact
AVEVA Technical Support
70587 141871 Version of SQL Server is incorrect SQL Server login screen presented
on the SQL Server login form when creating new projects states,
“This AVEVA product supports: SQL
Server 2008 R2 (SP3)”. This note
should state “SQL Server 2008 R2
(SP2)”.
68567, 135586, Cable catalogue import problems Importing cable catalogue data from
71113 143355 MS Excel requires 4 additional
columns adding to the spread sheet.
These columns are; “Line Type”, “Line
Colour”, “Line Width” and “Arrow
Head”. Please see the Cable Catalogue
Import section of the Important Points
to Note below.
74471 152589 Not possible to unassign I/O Work around is to select the specific
from an I/O module by selecting I/O module (not the “parent”
the “parent” enclosure in the enclosure) and then remove the
Equipment View assigned I/O from the Edit
Terminations dialogue for that
specific I/O module.
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 Exisit for AVEVA
Electrical and AVEVA Instrumentation
in Important Points to Note section
below

File: d10517.docx
Last saved: 3rd June, 2016  Copyright 2016 AVEVA Solutions Limited Page 13 of 26
 Product Release Letter
Incident Defect Description
number number
n/a 167477 CoreSize maps to
CableCatalog.CoreSize when
importing data in the Cable
Catalogue from MS Excel
n/a 179594 If the location code is blank,
duplicate virtual instruments with
the same (blank) location code
can be created when performing
multiple updates from MS Excel.
This occurs even if the project
option is enabled to create
duplicate virtual tags only in
different project locations
n/a 170917 When changes are made within
the AVEVA Electrical or AVEVA
Instrumentation Integration
Service Editor, clicking refresh is
not displaying the changes.
For example, when the
authentication type for project
ABC is changed from "Windows"
to "Project Authentication", after
clicking refresh, the changes are
not reflected in the Integration
Service editor dialogue
n/a 180184 Exception error when creating
properties where the property
name contains an apostrophe
83642 178035 Problems creating panels
containing a very large number of
terminals
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/10517/w10517.pdf
Please refer also to the Product Release Latest Update Note for the original full release,
http://downloads.aveva.com/10496/w10496.pdf.
File: d10517.docx
Last saved: 3rd June, 2016  Copyright 2016 AVEVA Solutions Limited
Recommended Workaround
When importing cable catalogue from
MS Excel, the Excel column name
“CoreSize” is automatically mapped to
“CableCatalog.CoreSize”.
Furthermore, the AVEVA
Instrumentation Field “CoreSize” is
not available for selection from the
pick-list.
By simply leaving the mapping as
“CoreSize” to
“CableCatalog.CoreSize”, the import
from MS Excel will work without any
problems.
Ensure that location code is
populated prior to importing or re-
importing the instrument tags, or use
export with ID option to create an
Excel file used to update existing
instrument tags.
Click on Save button to see changes
reflected in Integration Service editor
dialogue
User defined properties do not
support the inclusion of apostrophes
within the property name. Please do
not attempt to include apostrophes in
user defined property names.
Increase value of
USERProcessHandleQuota in registry.
See Problems Creating Panels
Containing a Very Large Number of
Terminals in Important Points to Note
section of this document
Page 14 of 26
 Product Release Letter
Important Points to Note

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 importing when deploying 12.1.SP3. 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

Windows 8.1 Support

When creating projects using AVEVA Instrumentation or AVEVA Electrical, 3rd party technology is
leveraged to “unpackage” the empty or demo project structures. This technology only supports
Microsoft .NET Framework up to version 3.5.

Windows 8.1 installs Microsoft .NET Framework version 4.5 and this will not allow AVEVA
Instrumentation or AVEVA Electrical to create projects.

Windows 8.1 does not include .NET 3.5 by default. However users can enable this feature via
Program and Features.

See this link for more information http://support.microsoft.com/kb/2785188

Note: If users are upgrading from Windows 7 to Windows 8.1, .NET Framework 3.5 is fully
enabled.

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

When running the new Project Packager utility, if these assemblies are not detected, the following
message will be displayed.

File: d10517.docx
Last saved: 3rd June, 2016  Copyright 2016 AVEVA Solutions Limited Page 15 of 26
 Product Release Letter

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.

Upgrading projects with the new AVEVA Project Authentication enabled

Once the new AVEVA Project Authentication has been enabled, projects can be upgraded in two
ways. Both these methods require a SQL Server user login with the ‘dbowoner’ 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-SP3 project is selected, you will be
first asked to enter the AVEVA Project user name and password.

File: d10517.docx
Last saved: 3rd June, 2016  Copyright 2016 AVEVA Solutions Limited Page 16 of 26
 Product Release Letter
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.

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 will have to be created by your SQL
Server administrators.

Changing Authentication Type

AVEVA Instrumentation and AVEVA Electrical 12.1.SP3 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, or 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:

File: d10517.docx
Last saved: 3rd June, 2016  Copyright 2016 AVEVA Solutions Limited Page 17 of 26
 Product Release Letter
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 - has to perform these task

AutoCAD 2014 File Loading Security Concern

When launching AutoCAD 2014 (and above) from AVEVA Instrumentation 12.1.SP3, or AVEVA
Electrical 12.1.SP3 warning messages such as the following may be seen.

AutoCAD 2014 (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 2014 (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
a. AVEVA Instrumentation - C:\Program Files (x86)\AVEVA\Instrumentation12.1.3
b. AVEVA Electrical - C:\Program Files (x86)\AVEVA\Electrical12.1.3\ACAddIn
7. The trusted location paths detailed above are based on the default installation folders for
AVEVA Instrumentation 12.1.SP3, or AVEVA Electrical 12.1.SP3
8. Once the trusted locations have been added, the Security Concern messages should no
longer be displayed when launching AutoCAD 2014 (and above) from within AVEVA
Instrumentation 12.1.SP3, or AVEVA Electrical 12.1.SP3

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.

File: d10517.docx
Last saved: 3rd June, 2016  Copyright 2016 AVEVA Solutions Limited Page 18 of 26
 Product Release Letter
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 of all 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.

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

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 3 and
later releases.

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.

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.

File: d10517.docx
Last saved: 3rd June, 2016  Copyright 2016 AVEVA Solutions Limited Page 19 of 26
 Product Release Letter
Properties Named with Underscores
Property names containing underscores are not supported in AVEVA Electrical and AVEVA
Instrumentation 12.1.SP3. To avoid problems with datasheet creation, reporting and grid
management, do not create properties that contain underscores.

Importing Data via Microsoft Excel where duplicate field/column names are detected
For AVEVA Instrumentation and AVEVA Electrical 12.1.SP3 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 will have to
be split out into separate xls or xlsx files and imported via these individual files. Alternatively, the
mapping will have to be re-defined.

Integrating with AVEVA P&ID

AVEVA Instrumentation 12.1.SP3 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.SP3.
This may become an issue on live projects as AVEVA Instrumentation 12.1.SP3 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 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.SP3 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.SP3 and AVEVA P&ID.

File: d10517.docx
Last saved: 3rd June, 2016  Copyright 2016 AVEVA Solutions Limited Page 20 of 26
 Product Release Letter
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.

Importing Cable Catalogue Data via Microsoft Excel

Within the new Enhanced Cable Block Diagrams functionality, delivered with AVEVA
Instrumentation and AVEVA Electrical 12.1.3.SP3, users can now control how cables appear on the
cable block diagrams. These graphical controls are accessible via the cable catalogue. Each cable
catalogue entry has the following new properties on the Design Data tab of the Cable Catalogue
Details dialogue.

Changing these properties will alter the graphical representation for any cable created from the
associated catalogue entry.

To enable the successful import of cable catalogue data from MS Excel, values for these new
properties should be present in the xls or xlsx file. Columns should be added to the Excel spread
sheet(s) as below.

The column data shown above is the default data for cable catalogue entries and can be set to
other values if required. Once the spread sheet is picked for importing data, user should map the
new columns as follows.

File: d10517.docx
Last saved: 3rd June, 2016  Copyright 2016 AVEVA Solutions Limited Page 21 of 26
 Product Release Letter

Once these columns and fields are mapped, all data will import successfully

Two known issues have been noted with the importation of cable catalogue data and Enhanced
Cable Block Diagram data:

1. Exporting the Cable Catalogue to MS Excel does not automatically create and populate
these columns in the spread sheet.

2. If these columns are not mapped and data imported for new cable catalogue entries,
subsequent editing of the new cable catalogue entry will result in an error. This is because
the Enhance Cable Block Diagram properties are empty.

Duplicate named fields and properties causing problems importing data from MS Excel
AVEVA Instrumentation and AVEVA Electrical 12.1.SP3 now allows 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.

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

File: d10517.docx
Last saved: 3rd June, 2016  Copyright 2016 AVEVA Solutions Limited Page 22 of 26
 Product Release Letter

Display in Instrument List Grid

Mapping Screen

Leading Spaces in Column Name Causing Problems Importing from MS Excel

An 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…

File: d10517.docx
Last saved: 3rd June, 2016  Copyright 2016 AVEVA Solutions Limited Page 23 of 26
 Product Release Letter

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.

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.

Installation Steps for AVEVA Integration Service

The following steps need to be followed to enable integration between AVEVA Instrumentation
12.1.SP3 Fix 9 and other AVEVA application via the new AVEVA Integration Service.

Server Setup

1. From the AVEVA Instrumentation 12.1.SP3 Fix 9 installer package, extract the file
InstrumentationIntService.msi

a. Note What is InstrumentationIntService.msi.txt

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 projects to the AVEVA
Instrumentation Integration Service

Client Setup

1. From the AVEVA Instrumentation 12.1.SP3 Fix 9 installer package extract the file
Instrumentation12.1.3.9.EXE

2. Install this fix/update on all workstations currently running AVEVA Instrumentation

12.1.SP3, Fix 1 to Fix 8

3. Download and copy the AVEVA Integration Service 1.x installer to all the workstations
running AVEVA Instrumentation 12.1.SP3 Fix 9

File: d10517.docx
Last saved: 3rd June, 2016  Copyright 2016 AVEVA Solutions Limited Page 24 of 26
 Product Release Letter
4. Run the installer AVEVA_Integration_Service 1.x.msi and install the Integration Client, not
the Integration Service

5. Follow the steps documented in the AVEVA Instrumentation 12.1.SP3 Fix 9 Common
Functionality Guide section 7.4.1 AVEVA Integration Import Configuration to setup
integration between AVEVA Instrumentation and other AVEVA applications

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”
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
6. Create a user defined property without a caption in AVEVA Instrumentation and include
this in a mapping
a. Workaround is to ensure that all user defined properties has captions defined

Problems Creating Panels Containing a Very Large Number of Terminals

AVEVA Electrical and AVEVA Instrumentation currently have a limitation whereby it is possible to
create a maximum of 5040 terminals within a single enclosure (junction box, panel etc.). This
limitation is due to a default Windows form “maximum handle count per user process” registry
setting of 2710. This value of 2710 correlates to approximately 5040 terminals without
connections, and 2500 terminals with connections within AVEVA Electrical and AVEVA
Instrumentation. If you experience problems creating enclosures with more than 5040/2500
terminals, the registry setting “USERProcessHandleQuota” will have to be changed.

USERProcessHandleQuota is located under

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\Windows\ as shown
below.

File: d10517.docx
Last saved: 3rd June, 2016  Copyright 2016 AVEVA Solutions Limited Page 25 of 26
 Product Release Letter

Modify USERProcessHandleQuota and change the Value data from 2710 (Hexadecimal) to 4000
(Hexadecimal).

Once the change has been made, it is advisable to restart the workstation. After restart, the
maximum number of terminals that can be created within a single enclosure will be increased to
8004 without connections, and 5002 terminals with connections. This registry change will happen
automatically when the forthcoming 12.1.SP4 versions of AVEVA Electrical and AVEVA
Instrumentation are installed.

Note: Setting USERProcessHandleQuota to a value greater than 4000 may cause Windows to
become unstable.

File: d10517.docx
Last saved: 3rd June, 2016  Copyright 2016 AVEVA Solutions Limited Page 26 of 26