Product Release Letter: Aveva P&Id 12.2.1.8 64-Bit Partial Fix Release 90362 Tested Using Autocad 2020 64-Bit
Product Release Letter: Aveva P&Id 12.2.1.8 64-Bit Partial Fix Release 90362 Tested Using Autocad 2020 64-Bit
Please do not install this fix release in a Windows 8.1 or Windows 10 32-bit environment. This is a
fix release that has been fully tested using AutoCAD® 2020 64-bit, Windows 8.1 64-bit and
Windows 10 64-bits environment.
The separately licensed products or product components installable from or upgraded by this
release are as follows:
Product Version
Product Name
Code Number
V02FN001 AVEVA P&ID 12.2
V00FN426 AVEVA P&ID (Marine) 12.2
For further information please contact your local AVEVA support office, which can be found at
http://support.aveva.com
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.
User needs to download .Net framework 4.7.2 from the below link.
https://www.microsoft.com/net/download/visual-studio-sdks
Note: For further details of .Net framework system requirements, please see
https://docs.microsoft.com/en-us/dotnet/framework/get-started/system-requirements
Microsoft C++ redistributable 2013(x86) from below link.
https://www.microsoft.com/en-in/download/details.aspx?id=40784
Microsoft C++ redistributable 2013(x64) from below link.
https://www.microsoft.com/en-in/download/details.aspx?id=40784
The AVEVA ARMS License should be installed to either a machine on your network or the Internet
Application Server in order to work with AVEVA P&ID applications.
License keys are obtained from AVEVA.
Note: AVEVA P&ID has been tested using AVEVA ARMS license version 5.0.
Note: For further details of AVEVA Licensing system, please see http://support.aveva.com
AVEVA P&ID 12.2.SP1.4 and later versions supports the AVEVA LaaS commercial model.
User need to configure LaaS account from AVEVA Licencing System (ALS). If you do not have an
account or LaaS agreement, please contact your account manager.
Note:
a. P&ID common launcher will be displayed always on screen until all the P&ID sessions are
closed. This is applicable for both on-premise and LaaS environments.
b. LaaS with AVEVA P&ID is not supported on Windows7SP1 machines.
c. LaaS with AVEVA P&ID is supported on Windows8.1 and Windows 10 with 64-bit.
- For better consistency, grouping all applications together that write to the same
database types:
• AVEVA Engineering to ENGI dbs
• AVEVA SMM & AVEVA Diagrams to SCHE dbs
• AVEVA PDMS & AVEVA E3D to DESI dbs
- Integrating 3rd party P&ID solutions with AVEVA 3D solutions requires the P&ID data,
connectivity and topology to be loaded into Dabacon Schematic database. This requires
selling an AVEVA Diagrams license for loading data into Dabacon through the SMM
license feature included in its product code.
- Contact AVEVA Support if you need any advice around this topic
Important Notes: This fix release has been fully tested using AutoCAD 2020 along with
AutoCAD 2019, AutoCAD 2018 and AutoCAD 2017 because base P&ID version (12.2.SP1) do not
support AutoCAD 2020.
o In case AutoCAD® is newly installed on the machine, please open AutoCAD® application at
least once before creating/updating AVEVA P&ID Project.
o For AutoCAD 2020, users must load the executable files before creating/upgrading the P&ID
application. Please refer section “AutoCAD® PC Install” from ‘AVEVA P&ID Installation Manual’
for the loading process.
➢ Using Compare/Update
o Compare and Update login details has been changed for connecting to AVEVA Electrical and
AVEVA Instrumentation projects which are created with windows authentication and using
AVEVA Integration Service 1.6.0.1 and above versions.
“FirstName.LastName”
“Domain\FirstName.LastName”
Note: This change does not apply to AI/AE projects using SQL authentication mode.
All the source (External/AVEVA) products supported by AVEVA integration service 1.6.1.1
and below version will be supported by AVEVA P&ID through integration.
• AVEVA Instrumentation 12.1 SP4 and above (requires Microsoft .NET Framework 4.5.1)
• AVEVA Electrical 12.1 SP4 and above (requires Microsoft .NET Framework 4.5.1)
o Microsoft Office 2013, Office 2016 and Office 365 on Windows 8.1 and above
Supersedes:
This release supersedes the previous fix release for AVEVA P&ID 12.2.SP1.Fix7.
For generating SVG and EIWM XML files in P&ID application please refer section “3.2.4.3 AVEVA
NET Gateway for AVEVA P&ID 5.0.5 and above installation” from ‘AVEVA P&ID Installation
Manual’ for the loading process.
Note : User requires separate license for AVEVA NET Gateway for AVEVA P&ID 5.0.5. For further
details of AVEVA Licensing System, please see http://support.aveva.com
The AVEVA NET Gateway for AVEVA P&ID 5.0.5 should be installed to either a machine on
your network or the Internet Application Server in order to work with AVEVA P&ID
applications. License keys are obtained from AVEVA.
Note: AVEVA P&ID has been tested using AVEVA ARMS license version 4.1.
To ensure size of P&ID Drawings output exported from AVEVA NET Gateway user must follow the
below steps:
1. Go to Project Administrator -> AVEVA NET -> Settings -> Scale Factor For, user will find
the ‘Imperial Drawing’ as shown below.
3. Before exporting the P&ID Drawings to AVEVA NET, users must open each drawing and
Save it.
4. After step 3 is completed, users can export the drawings to AVEVA NET using Batch
Utility or directly from core application.
Design in Context functionality has been implemented in P&ID application. Using this
functionality, the user can fetch the related documents from AVEVA NET Server into P&ID
application.
Note: Design in Context is compatible with AVEVA NET Dashboard 5.1 also.
B) To retrieve the documents in Design application, the steps below need to be carried out at
AVEVA NET Dashboard machine.
1. Navigate to [AVEVA NET Dashboard installation folder] \Import\Server\Bootstrap,
delete the existing ‘DICRelatedDocumentsSearch.XML’ file (if available) and then place
“DesignInContextSearchConfiguration.xml”
2. Go to ‘AVEVA NET Import Controller’ and select the newly placed file under Bootstrap
and then ‘Force Update of File’.
3. To reset IIS – click Start, Open Command Window via “Run as Administrator” option,
then type IISRESET.
C) Accessing AVEVA NET Dashboard feature and viewing documents in Viewer window
User can access AVEVA NET Dashboard through the following Web browsers:
1. Always install AVEVA Integration Service Components first followed by installation of AVEVA
Schematic Middle Tier Components on the client/server machine.
2. Users would have to install ‘AVEVA Integration Service component’ from separate application
called “AVEVA Integration Service 1.x”.
3. The ‘AVEVA P&ID Database Service’ component which is required for AVEVA Integration
Services to work has to be installed from ‘AVEVA Schematic Middle Tier installation’ available
with latest P&ID fix.
4. The ‘AVEVA Plant & Marine Interfaces’ component from ‘AVEVA Schematic Middle Tier
installation’ need to be installed on the client/server machine which is required to work
integration between AVEVA Schematics and AVEVA Engineering products with AVEVA P&ID
application (SAVEWORK).
5. Please refer ‘AVEVA Integration Service Installation.pdf’ file available with the product
“AVEVA Integration Service 1.x” for installing Integration service in the Client/Server
machine. This product would be available with separate license file. Please install the License
on a Client/Server machine for running the Integration Services. Please find below
information for license installation.
Note: Users should take care of below scenarios before running integration service.
Scenario1:
If the license file is installed in the server machine, then it should be updated with the AIS
1.x license details and all the client machines having ALS applications must be pointed to
the Server machine to run the Integration Services in client machines.
Scenario2:
If the license file is installed in the client machine, then it should be updated with the AIS
1.x license details to start the Integration Services.
The Below information is for the users using Middle Tier Components.
This release includes the folder “Middle Tier installation ONLY” with the “AVEVA Schematics Middle
Tier 3.x” installer, please run this file to install the Middle Tier components in the Middle Tier
Machine. Please also run this file in the local User Machine if the integration with other AVEVA
products is required (e.g. AVEVA Instrumentation and AVEVA Electrical).
AVEVA Integration Service helps an easy, quick and effective data transfer between different data
sources (AVEVA and non-AVEVA product data) installed in different machines on the same network.
The integration service should be installed on a server system (preferably having AVEVA
Engineering). It allows administrators to configure a variety of data sources like AVEVA Electrical,
AVEVA Instrumentation, AVEVA Engineering, AVEVA Schematic Model Manager, MS Excel, MS SQL
SERVER, etc. Data sources configured on the integration service can be consumed by one or more
AVEVA applications connecting to this service.
To send AVEVA P&ID data successfully for SQL authenticated projects to AVEVA Integration Services
we must setup the connection details including username and password at the
PIDReportDataWinService interface as shown below.
Project Wizard Note: After installing this Base, P&ID projects must be upgraded by using the
Project Wizard. It is mandatory to synchronise all the project drawings using “Synchronise Utility” to
populate the drawing names in the P&ID database so that propagation for off-sheet connector will
work. It is also recommended to export to P&ID reports after synchronising.
DEXPI Note:
1. The user should not use DEXPI export/import (XML format) functionality to transfer P&ID
drawings between AVEVA P&ID Projects. This functionality is designed to exchange
engineering data between CAD vendors. The user can use Document Manager to transfer
drawings between AVEVA P&ID Projects.
2. AVEVA P&ID export using Proteus schema 4.0.1 will not produce xml file which is
complaint with the instrumentation model as it is in current development.
3. DEXPI Proteus schema 4.0.1 is under review and development by the DEXPI group and
therefore AVEVA P&ID export/import using this schema will have some limitations that will
be overcome when DEXPI group finalize the schema.
4. The user needs to restart P&ID application if ISO 15926 Version is changed in Project
Administrator -> ISO 15926 Import/Export -> Settings.
5. DEXPI import feature does not create drawing entities with complete 100% fidelity. It may
need to manually edit / tweak drawing components after they are imported.
1. SQL server database should be setup using Windows Authentication to reduce the possibility
of security breaches into SQL database server.
2. Project and SQL Authentication are more vulnerable to security breaches hence they are not
advice for UE deployment.
We advise to existing customers working with projects already implemented using earlier
versions of AVEVA P&ID at UE environment to change SQL Authentication mode to windows
authentication to reduce possibility of potential security breaches into SQL database server.
For user upgrading existing projects already deployed into UE environment using previous
releases to AVEVA P&ID 12.2.SP1.8 we do advice to the project SQL DBA administrator
assuming project database is setup using windows Authentication to remove manually super
user “Pid_Admin_Master” from Microsoft SQL Server using Microsoft SQL Server Management
Studio following the step 15 to step 19.
15. Login to database server using Windows Authentication with administrator credentials, make
sure there is no other user(s) connected to the server.
19. Temporary SQL server user Pid_admin_master should no longer be available at the database
server.
In this release
Incident Defect Description
number number
159976 399179 We use the AVEVA integration service to integrate AM-Outfitting's
nozzle data, pipe data into P&ID.
However, size is not updated in P&ID nozzle, pipe properties.
Please refer to attached file (S&I Corporation)
160061 399364 Cannot delete symbols from the details view of the symbol explorer
(DSME Daewoo Shipbuilding & Marine Engineering)
159789 398683 Unable to roll back the Lock Layer for the Equipment Label
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.
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) prior to release.
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. https://support.aveva.com/
Note:
1. The replication
synchronization performance
depends on the Latency and
bandwidth of the networks.
2. Performing test between 2
SQL database server located at
the same location ( Hyderabad)
over a traditional network LAN
NA 215763 Latency and Bandwidth for Replication.
(Local Area Network)
connection.
3. Performing test between 2
SQL database server located at
2 different sites (Hyderabad and
Cambridge) using a WAN (Wide
Area Network) connection.
4. We use mix of 2 way Merge
replication and 1 Way
Transaction replication for tables
on all our databases, defining a
publisher and a subscriber SQL
servers.
Our region P&ID specialist should advice replication depending on the customer requirement
circumstances and available infrastructure, for instance, if “merge” or “transactional” replication is
the best option for them or if replication for reporting database is required or not.
For the latest list of exceptions and other updates, please see the Product Release Latest Update
Note on AVEVA's support web site https://support.aveva.com/
Please refer also to the Product Release Latest Update Note for the original full release,
https://support.aveva.com/