Upload
lamkhanh
View
219
Download
3
Embed Size (px)
Citation preview
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 Owner Charles Moses
AVEVA Electrical Senior Product Specialist
Product Manager Chris Binns
AVEVA Electrical and AVEVA Instrumentation Product Manager
System Test Manager Neeraja Tottempudi
Test Manager
TPS Representative for EDS products Semra Hamitogullari Åberg
Manager, Training and Product Support (EDS)
File: d10509.doc Last saved: 06th July, 2015 Copyright 2015 AVEVA Solutions Limited Page 1 of 24
AVEVA Electrical 12.1.SP3 Fix 8 (32 bit)
Partial Fix Release 10509-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 Electrical, which upgrades the full release 10495-1 AVEVA Electrical 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
V00FN288 AVEVA Electrical with following modules (Plant): 12.1.SP3
Electrical Engineer
Electrical Designer
Electrical Wiring Manager
Security Manager
V00FN429 AVEVA Electrical with following modules (Marine): 12.1.SP3
Electrical Engineer
Electrical Designer
Electrical Wiring Manager
Security Manager
V00FN697 AVEVA NET Electrical Gateway 12.1.SP3
Product Release Letter
File: d10509.doc Last saved: 06th July, 2015 Copyright 2015 AVEVA Solutions Limited Page 2 of 24
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 SP 1 or Windows 8.1 base release
Build Operating System Microsoft Windows 7 SP1 Professional (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 Electrical 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 Electrical 12.1.SP3
o Full 12.1.SP3 release 10495-1
o Full 12.1.SP3 release 10495-1 plus partial 12.1.SP3 Fix 2 release 10499-1
o Full 12.1.SP3 release 10495-1 plus partial 12.1.SP3 Fix 3 release 10501-1
o Full 12.1.SP3 release 10495-1 plus partial 12.1.SP3 Fix 4 release 10502-1
o Full 12.1.SP3 release 10495-1 plus partial 12.1.SP3 Fix 5 release 10506-1
o Full 12.1.SP3 release 10495-1 plus partial 12.1.SP3 Fix 7 release 10508-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 Instrumentation 12.1.SP3 Fix 6 AVEVA Engineering 14.1.0 including Fixes 1, 2, 3 and 4 AVEVA Engineering 14.1.SP1 including Fix1 and 2 AVEVA Diagrams 14.1 including Fix1 and 2 AVEVA Integration Service 1.0 & 1.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
Product Release Letter
File: d10509.doc Last saved: 06th July, 2015 Copyright 2015 AVEVA Solutions Limited Page 3 of 24
AVEVA E3D 1.1 and above AVEAVA NET Portal 4.7 and above AVEVA NET Work hub and Dashboard 5.0 and above AutoCAD 2013, 2014 & 2015*
VBA Enabler for AutoCAD not required for AVEVA Electrical 12.1.SP3 o Designer Drawing functionality not supported with AutoCAD 2012
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) ETAP 14.0 & above (64 Bit Software only) **
* 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 * There is an issue with Designer Drawing using AutoCAD 2015. See Defect number 174934 in Significant Defects and Recommended Workarounds section ** Please contact OTI for confirmation of release date ETAP 14.0 is compatible with:
Microsoft Excel 2007, 2010 and 2013 Microsoft SQL Server 2008 R2, 2012 and 2014 Microsoft SQL Express is also supported
Integration Matrix
This fix/update release of AVEVA Electrical 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 Electrical 12.1.SP3 Fix 8.
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 6, 7 needed to
import loop data into AVEVA
Instrumentation
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 Fix1 & 2 Yes Yes
AVEVA Diagrams
14.1 & 14.1 Fix1 & 2 No Yes
PDMS Engineering
12.1 to 12.1.SP2 Fix36 Yes No
12.1.SP4 Fix 17 to Fix 23 Yes *No *See Note 1 below
Product Release Letter
File: d10509.doc Last saved: 06th July, 2015 Copyright 2015 AVEVA Solutions Limited Page 4 of 24
PDMS Diagrams
12.1 to 12.1.SP2 Fix36 Yes No
12.1.SP4 Fix 17 to Fix 23 Yes *No *See Note 1 below
PDMS Schematic Model Manager
12.1 to 12.1.SP2 Fix36 Yes No
112.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 Electrical
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 10508-1, AVEVA Electrical 12.1.SP3 Fix 7.
To install product release
Please run the file Electrical12.1.3.8.exe. Running this executable will upgrade the following installations to AVEVA Electrical 12.1.SP3 Fix 7:
o AVEVA Electrical 12.1.SP3 (Full release 10495-1)
o AVEVA Electrical 12.1.SP3 Fix 2 (Partial release 10499-1)
o AVEVA Electrical 12.1.SP3 Fix 3 (Partial release 10501-1)
o AVEVA Electrical 12.1.SP3 Fix 4 (Partial release 10502-1)
o AVEVA Electrical 12.1.SP3 Fix 5 (Partial release 10506-1)
o AVEVA Electrical 12.1.SP3 Fix 7 (Partial release 10508-1)
Due to the AutoCAD issue below AVEVA Electrical 12.1.SP3 Fix 6 was withdrawn. In order to fix Incident Number 77987 (Area No is not available for Designer Drawing Symbols) and 79704 (Designer Drawing has an AutoCAD error during opening of the application) on 32 or 64-bit machines, an extra installer has been added to the release. It is called AVEVA.AutoCADUpdate.exe.
Run the file AVEVA.AutoCADUpdate.exe to update AutoCAD binaries that enable the AutoCAD based features of AVEVA Electrical to function correctly.
NOTE: This update should be applied for all supported versions of AutoCAD (2013, 2014, 2015) and for both 32-bit and 64-bit operating systems. To install this update successfully, right-click on the .exe and then select "Run as Administrator" from the options.
Product Release Letter
File: d10509.doc Last saved: 06th July, 2015 Copyright 2015 AVEVA Solutions Limited Page 5 of 24
IMPORTANT NOTE This 12.1.SP3 Fix 8 must be installed directly on top of AVEVA Electrical 12.1.SP3 or AVEVA Electrical 12.1.SP3 Fix 2, Fix 3, Fix 4, Fix 5 or Fix 7. Please uninstall AVEVA Electrical 12.1.SP3 Fix 1 prior to installing this fix if you have it installed.
First released on
This product release is first available on AVEVA support website http://support.aveva.com as AVEVA Electrical 12.1.SP3 Fix 8, release number 10509
List of Enhancements
This release includes the following functional enhancements: Description
ETAP Interface Within the Engineer module there is the option to import and export ETAP engineering data. The configuration dialogue allows the project to setup the interface folder location and the names of the xml files used to import and export the engineering data. Configuration dialogue allows the project to map any ETAP field to an existing database field or new property field. The Engineer module’s ETAP Import uses a compare / update wizard which includes a graphical representation of the power distribution. In order to help users there are 2 package projects available that are synchronised with example projects in the ETAP 14 release. These can be found in an ETAP folder which itself is in the application install folder under Program Files (x86). One package project (ETAPCleanProject.pkg) is an empty project ready to receive project data from ETAP 14. The second package project (SourceDataForETAP.pkg) is a populated project ready to send project data to an empty ETAP 14. For the full details of the ETAP Element Types supported with this release please see training documentation Note: This fix release has been tested against the released version of ETAP 14
Incident number
Defect number
Module Description
47199 72951 Designer We need to be able to import SCSUBE into AVEVA Electrical
List of Fault Corrections
This release addresses defects arising from the following support incidents:
Incident number
Defect number
Module Description
77205 160891 Designer SLD Designer Drawing Explorer is missing none load tags and none power cables
82370 175462 Engineer Exception when creating a project from a Package
77203 160885 Engineer Load List report does not include field attributes that show power values for both load and supply tags
75483 164940 Designer AVEVA Designer Drawing changing AutoCAD environment colour to black automatically
78277 165224 Security Manager
While updating the length in AVEVA Electrical from Outfitting the wrong license is being used and not being released
78617 165206 Engineer When External Cable Sizing has been executed the Number of Cables value is always being set to 1
Product Release Letter
File: d10509.doc Last saved: 06th July, 2015 Copyright 2015 AVEVA Solutions Limited Page 6 of 24
Incident number
Defect number
Module Description
81164 172879 Engineer When using 'Move Compartment to' option an exception is displayed in Distribution Diagram screen
81165 172880 Engineer Exception is displayed when using bulk edit in the Browse Data by Form Type
78980 166804 Engineer Need to add Area Path column in Wiring Manager module's Equipment List
80001 171857 Engineer Need to see Speed attribute in Load Schedule
81166 172881 Engineer Need to see equipment User Fields in datasheets
81167 172882 Engineer Need to see equipment User Fields in load schedule
81694 174070 Engineer Cable Check Report comparing wrong current values
81697 174074 Engineer Cable Schedule 'Need Re-Sizing' field is not being set correctly on press of Refresh button
72059 146448 Engineer Issue when Importing Compartment Elements From Other Project
69948 140069 Engineer Exception when importing compartment element symbols from other project
79466 168295 Designer Cable numbers not aligned properly on termination drawings
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
78592, 75207
165110, 164942
Designer Global Datalink Edit is not available
77495 161843 Wiring Manager Exception when creating an Area via Equipment View
75876 157339 Wiring Manager
Possible to add cables of different catalogue type to same cable drum
79465 168293 Designer Cable pairs and screen are overlapping on termination diagrams
79496 168551 Engineer Open Datasheet doesn’t commit changes to record
82999 176561 Designer Unable to enter date drawn, design, checked or approved
83280 177220 Security Manager Upgrade issue when data contains apostrophe
n/a 165850 Wiring Manager
Edit Termination throwing warning message, “Your project database is not compatible with this version of AVEVA Inst I/O assignments. Please contact AVEVA.”
n/a 170441 Engineer, Wiring Manager
Description in not updated in Engineer when changed via Equipment List grid in Wiring manager
81451 173474 Engineer Problems with 'Order By' Attribute in grids
Consolidated from previous fix releases
First released in Fix Version AVEVA Electrical 12.1.SP3 Fix 7, Release No. 10508-1
Incident number
Defect number
Module Description
79704 169101 Designer Designer Drawing has an AutoCAD error during opening of the application
Product Release Letter
File: d10509.doc Last saved: 06th July, 2015 Copyright 2015 AVEVA Solutions Limited Page 7 of 24
First released in Fix Version AVEVA Electrical 12.1.SP3 Fix 6, Release No. 10507-1
Incident number
Defect number
Module Description
75326 155048 Engineer Missing required columns in cable Catalogue Import Wizard
78428 164621 Engineer Cables are updated as an instrumentation cable after they have been sized
78560 164983 Wiring Manager
It is not possible to delete cables if DrumLocked field is not the grid view
77535 161844 Engineer When Security is enabled, error is caused by the report being run containing a sub report that no longer exists
76457 158795 Engineer Issues with Earth Resistor, Motor when importing Loads from excel
76458 158796 Engineer Excel load import is creating invalid circuits within Distribution Board tag
78455 164666 Designer Issue in Cabinet/Panel drawing designer symbols folder
78472 164683 Engineer ElecFaultCurrent field is missing in Datasheets
76636 159295 Wiring Manager Issue when updating cable Design Length as zero from E3D TM
76401 158634 Engineer Area No changing for Equipment without changes to audit log
75701 156500 Wiring Manager
Cannot delete unused Enhanced Cable Block Diagram Symbol from symbol library
74992 153914 Engineer Wiring Rule Name column changing appearance in Load Grid
75771 156821 Engineer Re-arrangement of columns in Cable Schedule grid is not being saved correctly
75474 155952 Engineer Unable to delete 2 Supply tags
75695 156454 Engineer 4 buttons of the Compartment Typical window are not presented on Windows 7 Enterprise K (Korean)
75499 155879 Engineer Transformer User Defined symbol does not have the Remove Out Connector and Remove the ER connector
75500 155891 Engineer Single Line Diagrams in Distribution Diagram missing Earth Resistor associated with supply transformer tag
75640 156251 Wiring Manager
Need Shield reference adding to Cable Catalogue and allow 1/C cable to have Shield data
72862 148820 Engineer Claimed items could be edited by other users
77295 161186 Engineer In Designer module import from other project option is not working for Installation Detail
77987 163341 Designer AREANO is not available for Designer Drawing Symbols. See To install product release: for further details if project is using 32-bit machines
78093 163632 Engineer Installation Detail Item Catalogue failure to import from other project
78233 78410
163999 164618
Wiring Manager
Grid View is not reporting correct Core Size but it is represented correctly in Form View
77319 161243 Engineer Latest release shows the banner as “Not For Commercial Use” as part of install
First released in Fix Version AVEVA Electrical 12.1.SP3 Fix 5, Release No. 10506-1
Incident number
Defect number
Product / Module
Description
74533 152747 Engineer AVEVA Diagrams receives Busbar and Winding data from AVEVA Electrical
Product Release Letter
File: d10509.doc Last saved: 06th July, 2015 Copyright 2015 AVEVA Solutions Limited Page 8 of 24
69909 139973 Designer Schematics drawing - Loads compartment datalinks are not correct
74287 152352 Engineer During Compare/Update Import for ETAP it is not possible to uncheck all the user fields
74289 152358 Engineer During Compare/Update Import for ETAP two compartments are being created for a coupler
72074 146531 Engineer Out Memory Issue when user runs Excel import more than 30 times
74678 153025 Wiring Manager
Unable to see CBD and ECBD under AVEVA Electrical Wiring Manager Cable Block Diagrams Menu
72114 146622 Engineer Distribution Diagrams Null Reference Exception when Access Control is enabled
74275 152342 Engineer When importing a motor tag via excel without mapping MotorCatalogueNo the Data Source for Calculation is not set
74797 153486 All General performance improvements in grid management and MS Excel import
73663 150923 Security Manager
Timeout upgrading large projects when resolving DB collation conflicts
74729, 74676
153479153472
Engineer Datasheet Document List publish to PDF problems
74678 153025 Wiring Manager
Unable to see cable block diagrams and enhanced cable block diagrams following project upgrades from SP3, Fix 1, Fix 2 and Fix 3
First released in Fix Version AVEVA Electrical 12.1.SP3 Fix 4, Release No. 10502-1
Incident number
Defect number
Product / Module
Description
74658 152986 Engineer Unable to import tagged items via AVEVA Diagrams Import when non mandatory fields are mapped
N/A 153518 Engineer Unable to import tagged items via AVEVA P&ID Import when non mandatory fields are mapped
First released in Fix Version AVEVA Electrical 12.1.SP3 Fix 3, Release No. 10501-1
Incident number
Defect number
Product / Module
Description
73604 150736 Designer Unable to create Designer SLD after windows date format changed
73446 150202 Engineer Reassign of tag equipment is not working in Supply Details dialogue
70660 142024 Engineer Exception when re-assigning loads/supplies importing from Excel
69252 138008 Engineer Unable to select more than 4 single conductor cables or edit cable numbers
70296 140980 Engineer ElecFaultCurrent is missing in Drawing Designer Symbols
71449 144632 Wiring Manager
Incorrect Cable Route Status update in compare and update with E3D Cable Design
146569 72081 Engineer Automatic mapping for certain fields in the Load Import are not correct i.e. Function, Number
71127 143377 Engineer Unhandled exception error when right clicking in Compartment Typical dialogue box
72229 147071 Engineer Distribution Diagrams Read Only Assignments error
70661 142025 Engineer It is possible to reassign loads and move elements in an MCC assigned to a read-only area
Product Release Letter
File: d10509.doc Last saved: 06th July, 2015 Copyright 2015 AVEVA Solutions Limited Page 9 of 24
70662 142028 Engineer It is possible to change some details for Transformers assigned to read-only areas via the Transformer Detail window
73450 150208 Engineer Exception when selecting "Copy Selected" in the motor catalogue
67071 128487 Engineer Cable Sizing Check Report is not working correctly for cable length
71617 145295 Engineer New load connections being incorrectly identified as circuit breaker in KOL Distribution Diagram window
First released in Fix Version AVEVA Electrical 12.1.SP3 Fix 2, Release No. 10499-1
Incident number
Defect number
Product / Module
Description
73088 149449 Designer This is an AVEVA Electrical 12.1.SP3 Fix 1 patch issue. The patch is replacing 64 bit files with 32 bit which causes an error. The error is that it is not possible to load any designer drawings and a message is displayed in the AutoCAD command window
First released in Fix Version AVEVA Electrical 12.1.SP3 Fix 1, Release No. 10498-1
Incident number
Defect number
Product / Module
Description
72260 147162 Engineer The equipment voltage is not set correctly from excel on import for load items other than motor which causes the equipment current to also be set incorrectly
72593 147959 Engineer Distribution Diagrams Supplies creation error when creating tag containing a busbar
72594 147965 Engineer Distribution Diagrams tag creation error when 'Forced Tagging for KOL' enabled in Options dialogue
72873 148865 Engineer During the excel import the equipment voltage is not been checked against project voltage when an items voltage is not set to the applications default voltage it gets imported with the wrong 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
Limited independent system testing has been carried out on this product, as released, to verify that it installs correctly in all supported configurations that any new functionalities have been correctly implemented and identified defects have been corrected.
Product Release Letter
File: d10509.doc Last saved: 06th July, 2015 Copyright 2015 AVEVA Solutions Limited Page 10 of 24
Acceptance Testing
AVEVA’s Product Readiness Authority (PRA) is satisfied that the System Testing for this release is sufficient to assure product quality. Any exceptions found after release will be reported in the Product Release Latest Update Note on AVEVA's support web site http://downloads.aveva.com/10509/w10509.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 number
Defect number
Description Recommended Workaround
47066 72738 When user wants to create wiring rule for VFD there is a requirement for multiple power cables. Also there are data links missing when motor schematic requires a variable speed drive
None except edit AutoCAD drawing manually after creation
54821 91710 When user connects a Motor to a Variable Speed Drive and the Motor has had its diversity factor set to 50% then at the Variable Speed Drive shows the average power over time and not the maximum demand
For reports the user can do the calculation within the report to show the maximum demand of the motor
64338 118534 When project has Busbar with compartment data connected to Variable Speed Drive connected to Motor not all the data links are available for the Motor Schematic drawing
None except edit AutoCAD drawing manually after creation
58648 101031 When the tag number format was changed only the Cable Number was clouded, the Tag number and the ferrule number was not clouded
None except edit AutoCAD drawing manually after creation
54257 90276 When the tag number format was changed only the Cable Number was clouded, the Tag number and the ferrule number was not clouded
None except edit AutoCAD drawing manually after creation
54822 91711 Power Factor field is required for Supply tags
None
52297 86351 The user is permitted to create a new cable from supply equipment to load equipment when the loads have NOT being assigned to Supplies. When cables are created in this manner and the user wants to size the cable from the cable schedule the user is prevented from doing so. If the user then assigns loads to supplies after the cable has been created, the user is still unable to size the cable from the cable schedule
The user has to delete the cable from the cable schedule, re-create the cable (after assignment), and then the cable can sized
64437 67071
118885 Currently if the number of terminals is changed (or the number of cores in a cable) then all of the data link names will change resulting in the user having to re-edit the already completed schematic template
The user having to re-edit the already completed schematic template
Product Release Letter
File: d10509.doc Last saved: 06th July, 2015 Copyright 2015 AVEVA Solutions Limited Page 11 of 24
Incident number
Defect number
Description Recommended Workaround
68566 135590 When trying to copy load schedule reports none of the sub-reports are being copied over
Manually recreate sub reports
54827 91717 The circuit naming for Distribution Boards is a concatenation of Circuit Number plus Phase Identifier
None
57968 103836 Customer types in Edit Data links form the following SQL-request containing Cyrillic symbols: (select Description from Equipment where EquipmentNo= 'QF1 Ввод1'). However in the text field we got the abracadabra. This occurs on AutoCad 2010/2013
None
66472 126455 The main characteristic of this new equipment type is that there are 2 or more inputs (supplies) and only 1 output
At present the only option is to use a MCC with 2 incomers feeding a busbar feeding 1 output
45024 71208 Copying a transformer in the supplies tab
does not copy over the winding impedance data
Add data manually
58624 100927 When importing from excel the Remarks attribute (for instance) and the text in the Excel file is larger than the attribute declaration in SQL (nvarchar(100)). The import reports an error (the message is not clear at all) and the data is not imported
None
N/A 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
Product Release Letter
File: d10509.doc Last saved: 06th July, 2015 Copyright 2015 AVEVA Solutions Limited Page 12 of 24
Incident number
Defect number
Description Recommended Workaround
N/A 136620 Intermittent “Warning 1946” error displayed when installing AVEVA Electrical and AVEVA Instrumentation
Warning messages beginning “Warning 1946” relating to short-cut links not being set have been observed intermittently whilst installing AVEVA Electrical and AVEVA Instrumentation 12.1.3. Clicking OK to close this warning should enable the installation to complete. No problems have been observed trying to then launch any of the AVEVA Electrical or AVEVA Instrumentation modules
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
N/A 139807, 139813
Exception error displayed when publishing datasheets and document lists to AVEVA NET portal if xlsx is the chosen file format and MS Office 2010 is deployed with AVEVA Instrumentation.
Documents must be created in xls format and not xlsx. AVEVA NET Gateways for AVEVA Electrical currently has problems related to xlsx file format support. Updated AVEVA NET Gateways for AVEVA Electrical will be incorporated into a fix for SP3 as soon as possible
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)”
70661 72229
142025 147071
It is possible to re-assign loads and move elements in an MCC assigned to a read-only area. For Read Only MCC and Read Only Load Distribution Diagrams allows the assignment of Load to the MCC
Problem applies to right mouse-click in both the Distribution Diagram and also the Supply Details window. No work around currently
Product Release Letter
File: d10509.doc Last saved: 06th July, 2015 Copyright 2015 AVEVA Solutions Limited Page 13 of 24
Incident number
Defect number
Description Recommended Workaround
70662 142028 It is possible to change some details for Transformers assigned to read-only areas via the Transformer Detail window
Problem applied to adding windings, adding output voltages and assigning/un-assigning loads. No work around currently
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
71635 145327 Issue with Cable Catalogue 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
71660 145355 Load schedule report does not show any data in AVEVA Electrical 12.1.SP3 after upgrade
If the load schedule report does not show any data then the filter string property needs to be cleared from edit layout of the report. Please see the Load Schedule Report error section of the Important Points to Note below
N/A 145632 After user has mapped attributes and saved mappings, then pressed Next button to Select Valid Records screen and pressed Back button to Select Mappings screen, the mapping some of fields are not showing any caption name e.g. "EqType" rather than "EqType (Equipment Type)"
Close Import Wizard and restart Import
Product Release Letter
File: d10509.doc Last saved: 06th July, 2015 Copyright 2015 AVEVA Solutions Limited Page 14 of 24
Incident number
Defect number
Description Recommended Workaround
N/A 146360 Irrespective to type of equipment, all the fields that are mapped in configuration window are seen when import is perform from AVEVA Engineering 14.1 to AVEVA Electrical - Engineer
Ensure when mapping fields for Load or Supply equipment types the same attribute in AVEVA Engineering 14.1 is used to map to the same attribute in AVEVA Electrical for both Load and Supply equipment types. Alternatively, if the same attribute in AVEVA Electrical for Load is mapped to a different AVEVA Engineering attribute compared to AVEVA Electrical attribute for Supply then the attribute value for the 2 mapping needs to be the same
72002 146381 Although cable size correctly stored in database the Cable Catalogue Details and Cable Sizing dialogues are displaying Decimal full stop rather than comma
Reset Size from within Cable Catalogue Detail
72059 146448 When Importing Compartment Elements From Other Project properties are not having the data transferred
Map fields manually
72095 146591 When Importing Compartment Elements Catalogue data from Excel type, Catalogue No, Model fields are not automatically mapped to correct field. Import for Rated Current is incorrect when decimal comma option is selected
Map fields manually. Update Rated Current value after import or import values with decimal set as point
N/A 146945 When AVEVA Electrical calculated attributes are mapped as part of Excel Load import then the power fields are not updated
Ensure AVEVA Electrical calculated fields are not part of Excel Load import
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 Exist for AVEVA Electrical and AVEVA Instrumentation in Important Points to Note section below
N/A 174934 There is a system error when opening Designer Drawing on AutoCAD (2015). This is because the default setting for ‘STARTUP’ is set to 2
When opening AutoCAD 2015 for Designer Drawing there is a warning message telling the user that ‘STARTUP’ needs to be set to 0
Product Release Letter
File: d10509.doc Last saved: 06th July, 2015 Copyright 2015 AVEVA Solutions Limited Page 15 of 24
Incident number
Defect number
Description Recommended Workaround
N/A 176958 When rated current data found in Supply Details dialogue is imported from etap and the power factor does not equal one then changing rated current value causes an automatic update before user has completed data entry
Update rated load field value found in Supply Details dialogue. The Rated Current field value is then calculated correctly
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
Click on Save button to see changes reflected in Integration Service editor dialogue
n/a 180184 Exception error when creating properties where the property name contains an apostrophe
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.
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/10509/w10509.pdf Please refer also to the Product Release Latest Update Note for the original full 12.1.SP3 release, http://downloads.aveva.com/10495/w10495.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 Number Suffix
Product Release Letter
File: d10509.doc Last saved: 06th July, 2015 Copyright 2015 AVEVA Solutions Limited Page 16 of 24
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 ‘dbowner’ role for the project. The recommended method is to upgrade the projects via AVEVA Security Manager. Security Manager by-passes the AVEVA Project Authentication and only allows Windows authentication or SQL Server authentication to connect to the project. If selecting Windows authentication, you will be asked to enter the Security Manager Administrator username and password. Providing your Windows domain account has a ‘dbowner’ role for the project, you will be able to upgrade the project. If selecting SQL Server Authentication, you will be asked to enter a SQL Server login name and password. Providing a login username and password is entered that has a ‘dbowner’ role for the
Product Release Letter
File: d10509.doc Last saved: 06th July, 2015 Copyright 2015 AVEVA Solutions Limited Page 17 of 24
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.
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.
Product Release Letter
File: d10509.doc Last saved: 06th July, 2015 Copyright 2015 AVEVA Solutions Limited Page 18 of 24
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. Either 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 (and above) 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
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
Product Release Letter
File: d10509.doc Last saved: 06th July, 2015 Copyright 2015 AVEVA Solutions Limited Page 19 of 24
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. Particular fields that may be an issue after the project has been upgraded are:
CatalogueNo for Equipment Type Transformer EquipmentType for Equipment Type Motor Voltage for Equipment Type MCC
Properties Named with Underscores
Property names containing underscore is 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.
Product Release Letter
File: d10509.doc Last saved: 06th July, 2015 Copyright 2015 AVEVA Solutions Limited Page 20 of 24
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 integrated AVEVA 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 functionality, delivered with AVEVA Instrumentation and AVEVA Electrical 12.1.3.SP3, users can now control how cables appear on the enhanced 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
Product Release Letter
File: d10509.doc Last saved: 06th July, 2015 Copyright 2015 AVEVA Solutions Limited Page 21 of 24
Three 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.
3. Some values for properties such as OAS/Coll and Cores will not be imported or created correctly.
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.
Leading Spaces in Column Name Causing Problems Importing from MS Excel
A problem occurs if users attempt to import data from Excel if fields are mapped to Excel columns that have names with leading or trailing spaces. To avoid this problem, please ensure that all leading or trailing spaces have been removed for any Excel columns names mapped for data import. The message displayed states, “Field ‘ABC’ does not exist in the current import file.” For example…
Product Release Letter
File: d10509.doc Last saved: 06th July, 2015 Copyright 2015 AVEVA Solutions Limited Page 22 of 24
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.
Load Schedule Report error
If the load schedule report does not show any data in AVEVA Electrical 12.1.SP3 after upgrade but it does show data in AVEVA Electrical 12.1.SP1 /12.1.SP1 then the filter string property needs to be cleared from edit layout of the report in AVEVA Electrical 12.1.SP3. The example below shows the field that needs to be cleared.
This filter string property error is fixed in AVEVA Electrical 12.1.SP3
Product Release Letter
File: d10509.doc Last saved: 06th July, 2015 Copyright 2015 AVEVA Solutions Limited Page 23 of 24
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 Electrical 12.1.SP3.8 Fix and other AVEVA application via the new AVEVA Integration Service.
Server Setup
1. From the AVEVA Electrical 12.1.SP3 Fix 8 installer package, extract the file ElectricalIntService.msi
a. Note What is ElectricalIntService.msi.txt
2. Copy ElectricalIntService.msi on to the machine (located on your network) that is hosting the AVEVA Integration Service
3. Run the ElectricalIntService.msi installer to add the AVEVA Electrical Integration Service
4. Follow AVEVA Integration Service 1.0 Installation Guide section 5.3 AVEVA Instrumentation/Electrical to add AVEVA Electrical projects to the AVEVA Electrical Integration Service
Client Setup
1. From the AVEVA Electrical 12.1.SP3 Fix 8 installer package extract the file Electrical12.1.3.8.EXE
2. Install this fix/update on all workstations currently running AVEVA Electrical 12.1.SP3, Fix 1, Fix 2, Fix 4, Fix 3, Fix 4, Fix 5 or Fix 7
3. Download and copy the AVEVA Integration Service 1.0 installer to all the workstations running AVEVA Electrical 12.1.SP3 Fix 8
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 Electrical 12.1.SP3 Fix 8 Common Functionality guide section 7.4.1 AVEVA Integration Import Configuration to setup integration between AVEVA Electrical and other AVEVA applications
Scenarios Whereby a Blank Compare/Update Dialogue is Presented
1. Importing one object type i.e. Loads when a grid for a different object type is active i.e. Supplies
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
Product Release Letter
File: d10509.doc Last saved: 06th July, 2015 Copyright 2015 AVEVA Solutions Limited Page 24 of 24
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 Electrical and include this in a
mapping a. Workaround is to ensure that all user defined properties has captions defined