product release letter - avevadownloads.aveva.com/10505/d10505.pdf · product release letter file:...

QA4/1, QA7/2 & QA11/3 - DNote v4.24 (6-May-14)

Product Release Letter

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 Neeraja Tottempudi

Test Manager, AVEVA Electrical & AVEVA Instrumentation

TPS Representative for EDS products Semra Hamitogullari Åberg

Manager, Training and Product Support (EDS)

File: d10505.docx

Last saved: 08th May, 2015 Copyright 2015 AVEVA Solutions Limited of 23

AVEVA Instrumentation 12.1.SP3 Fix 5 (32 bit)

Partial Release 10505-1

Windows 7 SP1 (32 bit or 64 bit) & Windows 8.1 (32 bit or 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 Code

Product Name Version 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

http://support.aveva.com/


File: d10505.docxx


Product Code

Product Name Version Number

Instrumentation Security Manager

V00FN690 AVEVA NET Instrumentation Gateway 12.1.SP3

Prerequisite for this release - operating system:

Minimum Supported O/S Version (for each supported platform)

Microsoft Windows 7 SP1 Professional (32 bit or 64 bit), Windows 8.1* Professional (32 bit or 64 bit)

Mandatory O/S Patches (for each supported platform)

Microsoft Windows 7 SP1 or Windows 8.1 base release

Build Operating System Microsoft Windows 7 SP1 (32 bit & 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 Full 12.1.SP3 release 10496-1 plus partial 12.1.SP3 Fix 1 release 10497-1




o See http://support.aveva.com

AVEVA Licensing System 1.3 and an appropriate licence file

o Please see AVEVA Licensing 1.3

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 6


http://support.aveva.com/services/products/30377/alic_30377.asp

http://www.microsoft.com/en-gb/download/details.aspx?id=17718


File: d10505.docxx


AVEVA Engineering 14.1.0 including Fixes 1, 2 and 3

AVEVA Engineering 14.1.SP1 including Fix 1

AVEVA Diagrams 14.1 including Fix 1

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

AVEVA Outfitting 12.1 and above

AVEVA E3D 1.1 and above

AVEVA NET Portal 4.7 and above

AVEVA NET Workhub & Dashboard 5.0 and above

AutoCAD 2012, 2013 & 2014

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 and 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 5.

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 Yes *Yes *12.1.SP2 Fix 5 needed to

import loop data

AVEVA Engineering

14.1 Yes No

14.1 Fix 1 & 2 Yes No

14.1 Fix 3 Yes Yes

14.1.SP1 & 14.1.SP1 Fix 1 Yes Yes

http://www.citrix.com/products/xenapp/overview.html?posit=glnav

http://usa.autodesk.com/adsk/servlet/item?siteID=123112&id=13959101

http://support.aveva.com/services/products/90266/amis_90266.asp


File: d10505.docxx


AVEVA Diagrams

14.1& 14.1 Fix 1 No Yes

PDMS Engineering


12.1.SP4 Fix 17 to Fix 21 Yes *No *See Note 1 below

PDMS Diagrams



PDMS Schematic Model Manager



PDMS Design



E3D Design

1.1 and fixes 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 10504-1, AVEVA Instrumentation 12.1 SP3 Fix 4.

To Install product release

Please run the file Instrumentation12.1.3.5.EXE.

Running this executable will upgrade the following installations to AVEVA Instrumentation

12.1.SP3 Fix 5:

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

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




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 5, release number 10505.



File: d10505.docxx


List of Enhancements

This release includes the following functional enhancements: Description

Windows Services Based Integration between AVEVA Instrumentation and AVEVA Engineering 14.1.SP1 Application integration via the AVEVA Integration Service has been extended with this release to now include AVEVA Engineering 14.1.SP1. Note: Not all AVEVA applications can integrated via this services methodology. See the Integration Matrix for more information. For client installation steps see Installation Steps for AVEVA Integration Service in Import Points to Note section of this document.

Intermediate or Local Field Junction Boxes Displayed on Termination Diagrams Options are now available at both project and drawing level to display additional connections on termination diagrams for intermediate, or local junction boxes. This enhancement is specifically for the case of when field instruments are connected into a smaller, local junction box and these smaller, local junction boxes are then connected to larger “primary” field junction box.

Additional Cable Catalogue User Fields An additional 30 user fields have been added to the cable catalogue. In addition to this, the Grid Manage capability has been extended to the Cable Catalogue grid and the Cable Drum Schedule grid, where these user fields may be displayed. All additional cable catalogue user fields are available to incorporate into lists and reports that access the cable catalogue table, as well as all drawing types that are capable of displaying cable data. When incorporated into any list, other than the Cable Catalogue list, these user fields will be read-only. This enhancement is common to both AVEVA Instrumentation 12.1.SP3 Fix 5 and AVEVA Electrical 12.1.SP3 Fix 6.

Duplicate/Virtual Instrument Tags Duplicate instrument tags can now be created via the AVEVA Instrumentation Engineer Instrument List to represent scenarios such as field instrument indication on DCS consoles. The ability to create duplicate/virtual tags is controlled by an overall project option that is disabled by default. Once enabled, duplicate/virtual tags can only be created if the location code for the instruments varies. Enabling the option will change the check for uniqueness from being based on “TagNo” to be based on “TagNo” + “ISALocation”. This check will also apply to importing instrument tags from MS Excel, or integrated AVEVA applications.

Note: This enhancement only applies to instrument tag number.

http://support.aveva.com/services/products/90266/amis_90266.asp


File: d10505.docxx


Incident number

Defect number

Module Description

65070 121712 Wiring Manager

Inst_ 11_Cable Catalogue

67051 128408 Designer Intermediate Junction Box in termination diagram

58063 98598 Engineer Duplicate/Virtual tags in Instrument Index (Engineer module)

61311 131343 Engineer Inst_2_Duplicate Virtual tags

n/a 137377 Engineer Tag Code Validation for integration

76601 159191 Engineer Refreshing the updated database not available second time around

List of Fault Corrections

This release addresses defects arising from the following support incidents:

Incident number

Defect number

Module Description

n/a 163501 Security Manager

After clicking Add User button in Security Manager Domain name and User name fields are empty

n/a 161772 Security Manager

Areas are not being greyed out if they are in RO access

76628 159238 Security Manager

Security manager Module not opening when upgraded first 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 Engineer

Adding new associated ProcessLine deletes exisiting Process Equipment


Can't open Security Manager with usual Password

n/a 153722 Wiring Manager

Changes to catalogue values need to get reflected in the cable 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


Can’t upgrade from 12.0.SP5 to 12.1.SP2

n/a 161292 Process Manager

Changes made for the User Defined properties of Process 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


Descriptions not updating for field device/instrument tags "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


File: d10505.docxx


Incident number

Defect number

Module Description


Locked pick-lists for cable user fields are not presented in the Edit Cable dialogue enabling any data to be entered


Exception is thrown when "Cable cores not terminated" Option is selected from Fixed reports


Field bus device Cable disappeared on Reopen with edit 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

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


Electrical Cables are not shown in AI by default when the project is shared


Cross patching with I/O modules error when selecting the “parent” enclosure in the Equipment View


Cable Schedule grid Layout is not respected


Issues Relating to Importing data from Schematics Model Manager

n/a 114363 Engineer User Count not Functioning when Importing Data


Cables created from an Instrumentation cable catalogue entry 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, 148810

Engineer Compare/Update: Filtering in compare and update in PDMS for instruments by function code

n/a 114356 Engineer Importing reports containing sub-reports into an upgraded project


Application crashes or exits if the user tries to perform Edit 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


Performance Issue, cable schedule Grid is taking more than 2 mins to open when security is enabled


Overall Screen is not saved for Cable catalogues with Group 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


Cable is changed from instrumentation to Electrical discipline 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


File: d10505.docxx


Incident number

Defect number

Module Description

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

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


Unable to login to projects through compare/update window if PDMS and AVEVA Instrumentation or Electrical are installed on different drives

Consolidated from previous fix releases

First released in Fix Version AVEVA Instrumentation 12.1.SP3 Fix 4, Release No. 10504-1

Incident number

Defect number

Module Description

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


Timeout upgrading large projects when resolving DB collation conflicts

74729, 74676

153479, 153472

Engineer Datasheet Document List publish to PDF problems


Unable to see cable block diagrams and enhanced cable block diagrams following project upgrades from SP3, Fix 1, Fix 2 and Fix 3


Audit log not capturing the fieldbus device creation


Incident number

Defect number

Module Description

74483 152635, 155521

Engineer Performance issues when creating sub-areas for project containing complex project breakdown structures

47658 152986, 154048,

Engineer Unable to import tagged items via AVEVA Diagrams Import when non mandatory fields are mapped

n/a 154194, 153903

Engineer Unable to import/update the loops from engineering 14.1


File: d10505.docxx



Incident number

Defect number

Module Description

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


Enhanced Termination Report not keeping changes when saved


Importing Security Manager settings from another project for 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

72821 148730 Engineer Reports referencing InstrumentList Area field failing when projects upgraded from SP2 to SP3


Application freezing when running I/O Fixed report following 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


Cannot open instrument grid after upgrade with security enabled


Overall Screen not being saved correctly creating new cable catalogue entries


Project upgrade problems related to modified templates for issued drawings.


Design Length in the Cable Details is importing 'Total Length' 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.


Routing Status in the Cable Details window shows Unrouted for a Routed cable


Add Button is enabled in "Cables on Cable Drum" Window of 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


File: d10505.docxx


Incident number

Defect number

Module Description

n/a 157699 Engineer Field mappings lost when reused for Excel Import


Incident number

Defect number

Product / Module

Description

68707 136043 Designer .DWG file not closed/released when drawing is issued


Display order of Enhanced Cable Block Diagrams in DESIGNER 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

71857 145918 Process Engineer

Process data properties pcFluidPhase and pcCorrosiveProps 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/10504/w10505.pdf



File: d10505.docxx


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 number

Defect number

Description Recommended Workaround

N/A 86688 Process Equipment & Process Line Associations not being captured in Audit Log

The action of associating an instrument with items of plant equipment or process lines within AVEVA Instrumentation is not currently being captured in the audit log

53942 89846 Picture/Logo Sizing on Datasheets

Problems have been discovered with 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, 130884

Problems printing/exporting to PDF

Intermittent problems have been 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 on the SQL Server login form

SQL Server login screen presented when creating new projects states, “This AVEVA product supports: SQL Server 2008 R2 (SP3)”. This note should state “SQL Server 2008 R2 (SP2)”.

68567, 71113

135586, 143355

Cable catalogue import problems Importing cable catalogue data from 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 from an I/O module by selecting the “parent” enclosure in the Equipment View

Work around is to select the specific I/O module (not the “parent” enclosure) and then remove the assigned I/O from the Edit Terminations dialogue for that specific I/O module.


File: d10505.docxx


Incident number

Defect number

Description Recommended Workaround

n/a 161004 Problems importing data into a shared project when duplicate properties exist in AVEVA Electrical and AVEVA Instrumentation

Ensure that property names are unique in AVEVA Electrical and AVEVA Instrumentation. See Importing Data into a Shared Project Where Duplicate Property Names Exisit for AVEVA Electrical and AVEVA Instrumentation in Important Points to Note section below

n/a 167477 CoreSize maps to CableCatalog.CoreSize when importing data in the Cable Catalogue from MS Excel

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.

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/10505/w10505.pdf

Please refer also to the Product Release Latest Update Note for the original full release,

http://downloads.aveva.com/10496/w10496.pdf.

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




File: d10505.docxx


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.

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.


File: d10505.docxx


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.

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.


File: d10505.docxx


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:

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

12.1.SP3 warning messages such as the following may be seen.


File: d10505.docxx


AutoCAD 2014 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

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

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.


File: d10505.docxx


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.

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.

http://www.aveva.com/en/Products_and_Services/Product_Support.aspx


File: d10505.docxx


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.

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


File: d10505.docxx


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.

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.


File: d10505.docxx


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

Display in Instrument List Grid


File: d10505.docxx


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…

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.


File: d10505.docxx


Installation Steps for AVEVA Integration Service

The following steps need to be followed to enable integration between AVEVA Instrumentation

12.1.SP3 Fix 5 and other AVEVA application via the new AVEVA Integration Service.

Server Setup

1. From the AVEVA Instrumentation 12.1.SP3 Fix 5 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.0 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 5 installer package extract the file

Instrumentation12.1.3.5.EXE

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

12.1.SP3, Fix 1, Fix 2, Fix 3 or Fix 4

3. Download and copy the AVEVA Integration Service 1.0 installer to all the workstations

running AVEVA Instrumentation 12.1.SP3 Fix 5

4. Run the installer AVEVA_Integration_Service 1.0.msi and install the Integration Client, not

the Integration Service

5. Follow the steps documented in the AVEVA Instrumentation 12.1.SP3 Fix 5 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


File: d10505.docxx


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

product release letter - avevadownloads.aveva.com/10505/d10505.pdf · product release letter file:...

Documents