AVEVA Instrumentation 12.1 SP1 Fix 1 - Release Letterdownloads.aveva.com/10481/d10481.pdf · AVEVA PDMS 12.1 and above AVEVA Marine 12.1 and above AVEVA E3D 1.1 AVEVA NET All Supported

QA4/1, QA7/2 & QA11/3 - DNote v4.20 (29-Sep-09)

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 Chris Binns

Head of Operations Antony Spilman

Development Manager Phil Robins

Test Manager Kam Kundra

Head of Product Maged Selim

Senior Product Business Manager Dave Gibson

File: d10481.docx

Last saved: 13-Aug-2013 Copyright 2013 AVEVA Solutions Limited Page 1 of 17

AVEVA Instrumentation 12.1.SP2

Full Release 10481-1

Windows XP (32 Bit) and Windows 7 (32 and 64 Bit)

Dear Customer This letter introduces and describes this release, which is supported on the indicated platform(s).

This Release Contains

A full release of AVEVA Instrumentation, which replaces the full release 10451-1 AVEVA Instrumentation 12.1 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.SP2

Instrument Engineer

Instrument Designer

Wiring Manager

Process Engineer

Security Manager

V00FN427 AVEVA Instrumentation with following modules: (Marine) 12.1.SP2

Instrument Engineer

Instrument Designer

Wiring Manager

Process Engineer

Security Manager

V00FN690 AVEVA NET Instrumentation Gateway 12.1.SP2


d10481.docx 13-Aug-2013 Copyright 2013 AVEVA Solutions Limited Page 2 of 17

Prerequisite for this release - operating system:

Build Operating System Microsoft XP Professional (32 Bit)

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

Microsoft XP Professional (32 Bit), Windows 7 Professional (32 and 64 Bit)

Mandatory O/S Patches (for each supported platform)

XP SP3 and above, Windows 7 Base release and above

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:

Microsoft .NET Framework 4.0 Flexman 5.2 and an appropriate Flexman license For further details of Flexman License Server 5.2, please see http://support.aveva.com.

AVEVA Licensing Library

All products in this release include the AVEVA licensing library cadcflex 5.2 please refer to the Flexman 5.2 Installation and Configuration Guide (or later) or the Licensing section of the AVEVA support website http://support.aveva.com for a list of licensing features supported by this version of cadcflex.

Works (is compatible) with:

AVEVA P&ID 12.1 (32 or 64 bit) AVEVA PDMS 12.1 and above AVEVA Marine 12.1 and above AVEVA E3D 1.1 AVEVA NET All Supported versions AutoCAD 2012 and 2013 Microsoft Excel 2007 and 2010 Microsoft SQL Server 2008 R2 and 2012, SQL Server Express also supported

No longer works (is not compatible) with:

AutoCAD 2011 Note: Whilst AVEVA do not foresee any problems running AVEVA Instrumentation 12.1.SP2 with AutoCAD 2011, this version of AutoCAD has not been tested with Aveva Instrumentation 12.1.SP2 and is therefore not officially certified for use. Any problems encountered deploying AVEVA Instrumentation 12.1.SP2 with AutoCAD 2011 will not be addressed in any subsequent fix release, or service pack.

Supersedes

10473-1 AVEVA Instrumentation 12.1.SP1

To Install product release

Please run the setup.msi which is visible on the CD/DVD. This is a Full installation of AVEVA Instrumentation 12.1.SP2.

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

http://support.aveva.com/



First released on

This product release is first available on AVEVA DVD AVEVA Plant Instrumentation and Electrical 12.1.SP2, release number 41249-1

List of Enhancements

This release includes the following functional enhancements: In this release

Description

Decimal Comma support The use of comma (,) as the decimal symbol or separator for numeric values is now supported in AVEVA Instrumentation and AVEVA Electrical 12.1.SP2. The use of decimal comma or decimal point is controlled by the Windows Region and Lanuage Settings. The language settings with AVEVA Instrumentation or AVEVA Electrical have no influence over the decimal symbol. Therefore the applications can be set to use English (for example) as the language and Portuguese as the Windows region setting. This wille enable all the AVEVA Instrumentation UI to be presented in English and support the use of the comma as the decimal symbol. Values stored in the project database will still maintain a decimal point to facilitate integration between AVEVA Instrumentation and other AVEVA applications. For full details please refer to the AVEVA Instrumentation 12.1.SP2 Update presentation AVEVA Instrumentation 12.1.SP2 Feature Update.pdf

Duplicate Sub-Areas It is now possible to create “duplicate sub-areas”. For example it is now possible to define the following:

Plant 1 > Area 01 > System 01

Plant 1 > Area 02 > System 01 For full details please refer to the AVEVA Instrumentation 12.1.SP2 Update presentation AVEVA Instrumentation 12.1.SP2 Feature Update.pdf



Description

Wiring Rule Enhancements - Spare and Reserved terminal status It is now possible to assign a status of Spare or Reserved against terminals in junction boxes and panels. This will allow users to prevent connections being made to these terminals when allocating instruments (and associated cables) to junction boxes and panels. When using the Junction Box Allocation functionality within AVEVA Instrumentation Wiring Manager, connections to spare or resrved terminals will be skipped. The status of spare or reserved can be assigned to either the left, right or both sides of a terminal. Manual connections to terminals set as spare are permitted and the status of spare is removed. The terminal sides are coloured blue to indicate that someone has set them as spare, thereby giving a visual indication that connections should not be made to these terminals. However users are not actually prevented from making manual connections. Manual connections to terminals set as reserved are permitted but only after the user has acknowledged a warning message indicating that these terminals are reserved and agreeing to continue with the connection. Once again following the connection being made, the reserved status is removed. The terminal sides are coloured gray to indicate that someone has set them as reserved thereby giving a visual indication that connections should not be made to these terminals. For full details please refer to the AVEVA Instrumentation 12.1.SP2 Update presentation AVEVA Instrumentation 12.1.SP2 Feature Update.pdf

Wiring Rule Enhancements – Wiring Pattern vs. Catalogue Sequence The connection sequence designed within a wiring rule is now preserved even if this contradicts the core group sequence order defined in the cable catalogue. For example, a 1pr OAS screen cable could be defined in the cable catalogue with cores in a sequence of 1W, 1B, OAS. In a wiring rule a cable of this type could be connected in the same sequence at the field device end, but switched around at the junction box end i.e. 1W, 1B, OAS at the field device and 1B, 1W, OAS at the junction box. With the advent of AVEVA Instrumentation 12.1.SP2 the connection sequence defined in the wiring rule will overrule the group sequence defined in the cable catalogue and the cable will be connected as per the wiring rule. For full details please refer to the AVEVA Instrumentation 12.1.SP2 Update presentation AVEVA Instrumentation 12.1.SP2 Feature Update.pdf



Description

Process Data Datasheet Datalink Improvements When editing the properties of an instrument datasheet template it is now possible to set the maximum number of process plant connections that the datasheet template will be expected to handle. This helps in reducing the number of datalink options presented when mapping cells on the datasheet template. Furthermore the list of tables presented when mapping datalinks has been greatly reduced. Previously the following were presented:

• InstProcessData>ProcessEquipment1 (to x) • InstProcessData>ProcessLine1 (to x) • Common>PETag1 (to x) • Common>PLLine1 (to x) • ProcessEquipment>PETag1 (to x) • ProcessLine>PLLine1 (to x)

This list has been reduced to the following:

• InstProcessData>PlantConnection1 (to x) • ProcessProperties>PlantConnection1 (to x)

InstProcessData is the table that stores the process equipment or line form data. ProcessProperties is the table that stores the extended properties for process equipment and line. For full details please refer to the AVEVA Instrumentation 12.1.SP2 Update presentation AVEVA Instrumentation 12.1.SP2 Feature Update.pdf



Description

Flexible Tagging AVEVA Instrumentation 12.1.SP2 introduces a basic level of object classification that will enable the following:

Class level tag formats to enable different tag formats depending on class type i.e. control valve tag format different to pressure transmitter tag format etc.

Multiple tag formats per class to enable the tag format of a class type to vary depending on location, process, service etc.

Classification possible for Process Equipment, Process Lines, Loops, Instruments as well electrical loads and supplies in AVEVA Electrical

AVEVA Instrumentation is no longer restricted to having a single tag format for instruments per project and the format of these tags is unrestricted. Tag formats can now be made up of (potentially) unlimited numbers of parts (tag codes). These tag codes (fields in tables) can be created by users to suit any project requirements. Tag formats and tag function codes are assigned to the project object classes thereby controlling which tag formats and function codes are available for selection on a class by class basis. Project administrators are free to define as many, or as few tag classes as they require. The minimum is 1 class type for each object type. AVEVA Instrumentation 12.1.SP2 ships with a set of example classes based on the class types used by Aveva P&ID. These can be deleted or altered on a project by project basis.

For full details please refer to the AVEVA Instrumentation 12.1.SP2 Update presentation AVEVA Instrumentation 12.1.SP2 Feature Update.pdf Also see Import and Integration section of this document Consolidated from previous fix releases First released in fix version AVEVA Instrumentation 12.1.SP1 Fix3, Release No. 10478

Description

Enhanced Microsoft Excel Export and Import Controls within Security Manager New user Access Types added to Security Manager:

• Full Access (No Excel Import) • Full Access (No Excel Export • Full Access (No Excel Import/Export) • Read Only (No Excel Export)

The above Access Types are in addition to the existing Security Manager Access Types. Any users that are part of user groups - assigned one of these Access Types - will have restrictions imposed upon them relating to export and import actions they can perform via MS Excel. Associated buttons with the AVEVA Instrumentation fluent UI will be enables or disabled depending on the Access Type assigned. For full details please refer to the AVEVA Instrumentation 12.1.SP2 Update presentation AVEVA Instrumentation 12.1.SP2 Feature Update.pdf

Use of special characters in drawing numbers In previous versions of AVEVA Instrumentation the use of characters use as the period/dot for drawing numbers was not allowed. With this fix release the use of such characters in drawing numbers is permitted.



First released in fix version AVEVA Instrumentation 12.1.SP1 Fix2, Release No. 10477

Description

Resolution of Database Collation Issues during project upgrades AVEVA Instrumentation 12.1.SP1 Fix 1 often failed to successfully upgrade legacy projects if database collation conflicts were detected. This new fix release of AVEVA Instrumentation 12.1.SP1 will automatically detect and silently resolve any database collation issues when projects are upgraded. First released in fix version AVEVA Instrumentation 12.1.SP1 Fix1, Release No. 10474

Description

Pick List Grid Enhancements Users with applicable permissions can now assign a pick list to (almost) any field or property displayed in any data access grid. Limitations & Restrictions:

Fields that are read-only within the default grids cannot have pick lists assigned to them.

It is not possible to change the pick lists for fields that have pick lists assigned to them in the out-of-the-box default grids. For example Manufacturer and Model No.

Assigning a pick-list to a field within a grid will not automatically convert any applicable text boxes on dialogues to a pick-list

If a field is assigned a pick-list and this pick-list is locked, the applicable text box on a dialogue will become read-only

If data is imported that is not part of a locked pick-list data set, the import of the entire record will fail as the software will not accept that item of data

AVEVA Electrical and AVEVA Instrumentation still maintain independent pick lists For full details please refer to the AVEVA Instrumentation 12.1.SP2 Update presentation AVEVA Instrumentation 12.1.SP2 Feature Update.pdf Enhanced Russian Version Translation The Russian language version of AVEVA Instrumentation has been improved based on feedback from that region

List of Fault Corrections

This release addresses defects arising from the following support incidents: In this release

SI Number Defect Number

Title

19493 70818 Datalinks missing for second conductor in cables for loop diagrams

32053 27813 Wiring rule core connection sequence being overwritten by the cataloge group sequence order

40523 71012 Unable to insert a sub-area with the same name

43080 71058 Spare terminals defined in wiring rules are not transferred to destination terminal strips



SI Number Defect Number

Title

47140 72818 Problems in calculation module when applying different regional settings

47246 72996 The cable length decimal separation symbol is being lost transferring data from PDMS to AVEVA Instrumentation

48186 75125 Problems importing instruments from AVEVA Schematics Model Manager

48823 78127 Too many decimal places present when exporting catalogue data to Excel

53901 89758 Editing DC project voltages changes the 'frequency' from DC to 50

54777, 54891

91703, 91812

Instruments that could be equipment or line mounted required two different datasheet templates when they should only need one template

55019 92154 Copying an instrument from the instrument catalogue is not copying the property data

55250 92414 Wiring manager allowing duplicate cable no's

55402 92876 Unable to access Loops Grid

55488 93037 Unable to delete ferrule markings once applied with a ferrule rule

55802 93835 Overflow Exception occurred in Wiring Manager following upgrade

55842 94241 All available instruments are not displayed for assiging to hook ups

55856 94627 Cable source and destination data getting mixed up on termination diagrams when cables are connected TS left to TS left within the same panel

56219 94547 Copying instrument catalogues from one project to another is not copying the instrument properties

56223, 57954

94549, 98313

Editing project data is saying that paths and fields cannot be blank even though they are populated

56288 94650 Cables and Jumpers overlapping on termination diagrams

56929 96044 Importing instruments using 'ForeignKEY' inserts a new tag instead of updating the exisitng tags

57670 97569 Unable move field devices into groups correctly

57938 98285 Exception Error when creating or modifying terminal strip or earth bars after upgrade

58101 98724 Maximum number of instruments assigned to a hook up is 99. This needs to be increased to 100+

58116 98849 Single Core Cables having -1 suffix appended that cannot be removed

58218 99122 Area field copied with COPY DATA command in Instrument Details dialogue

Consolidated from previous fix releases First released in fix version AVEVA Instrumentation 12.1.SP1 Fix3, Release No. 10478

SI Number

Defect Number

Title

55802 93835 OverflowException occurred in Wiring Manager following upgrade


SI Number

Defect Number

Title

56165 94352 Database Collition problems after installing Fix 1




SI Number

Defect Number

Title

55262 92434 Problems using period (full stop/dot) in file name when creating data sheets

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

Independent system testing has been carried out on the product, as released, to verify that it installs correctly in all supported configurations and that product functionality operates as intended, subject to any known exceptions listed below.

Acceptance Testing

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/10481/w10481.pdf

Exceptions – Significant Defects and Recommended Workarounds

Thermowell Vibration Calculations

The unit conversion feature within Text Box “Pipe Internal Diameter” does not function as expected. After entering value “10in” and pressing enter, the expected result is that the value to convert to millimetres. This conversion is not currently working.

Instruments & Loops Imported with an Area value not present in the project

When importing instrument and loop records in AVEVA Instrumentation via excel, it is currently possible to import these records with area values that are not present in the target project. To avoid this problem ensure that the target project has all required area values defined prior to import.

Incorrect Data in Instrument Type Catalogue

Within the Instrument type catalogue in the “empty” AVEVA Instrumentation project there are a couple of anomalies. Firstly “PZT – Pressure Transmitter” exists twice. One of these

http://downloads.aveva.com/10481/w10481.pdf



entries can be deleted safely. Secondly the description for TSLL is “Temperature Switch Low High”. This can be safely changed to “Temperature Switch Low Low”.

User claims functionality is not working properly for Seed Files, Hookup Templates and Hookup Item Catalogue Entries

For Seed Files, Hookup Templates and Hookup Item Catalogue entries messaging is not being displayed when attempting to edit these items via the grids if locked by multiple users. It is also possible to delete these items, even if they are supposedly locked by multiple users.

User Count not Functioning when Importing Data

When importing data into AVEVA Instrumentation, the user count is not displaying correctly if other users are still logged into the project. The User Count always remains zero. This problem affects importing data from Excel, Engineering Tags and Schematic Model Manager.

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.

Issues Relating to Importing data from Schematics Model Manager The LoopService field is being displayed when configuring the property mapping for SCOINSTRUMENTS. This field should only be displayed when mapping loop objects SCLOOP. Simply ignore this field and does not map it for SCOINSTRUMENT object types. Similarly the following fields are being displayed and can be ignored; DataSheetNo, General Hookup, Process Hookup, Pneumatic Hookup, Mounting Hookup.

Problems Importing Large Datasets Importing large datasets into AVEVA Instrumentation can cause out-of-memory errors to be displayed and the import fail. To avoid this, break the datasets up into sets of no more than 10,000 records and import these one at a time.

Importing reports containing sub-reports into an upgraded project Importing reports containing sub-reports into an upgraded project does not import the sub-reports. To work around this issue, first import the sub-report. Then import the host report and within edit layout, set the sub-reports reportsource.

User defined wiring rule not terminating if “Terminate” check box uncheck when first applied

If a user defined wiring rule is applied to an instrument (with an associated junction box) and the “Terminate” check box is unchecked, it is not possible to then automatically terminate the instrument cable in the junction box by re-applying the wiring rule with the “Terminate” check box is checked. The cable will have to be terminated manually.

Application crashes or exits if the user tries to perform Edit Terminations on the Marshalling Panel with many DIN rails

The problem described above has been discovered for a Cabinet or Panel containing 30+ DIN rails with multiple Terminal Strips on each rail. It was found that the count of USER Objects being created by AVEVA Instrumentation Wiring Manager in a single windows



session is being exceeded. Every application created its own USER objects. In windows, the maximum limit can be set by editing the following key in the registry. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows\USERProcessHandleQuota This value can be set to a number between 200 and 18000. The default value is 10,000 (Decimal). Increasing the value from 10000 to 18000 and restarting windows will alleviate the problem.

Exception occurs while Importing Process Properties with incorrect data type value via Excel

When importing Process Properties via Excel, the category of the Excel cells must match the data type of the property. If they do not match, for example property is Numeric and cell is Text, then the import will fail.

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

The current work around is for users to run PDMS as “administrator”. It will then be possible to login to AVEVA Electrical from Compare/Update window.

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 has been reported to the respective suppliers. To avoid this issue please insert any image files in BMP format.

Taskbar button icons are wrong on upgrade projects using Windows 7 We believe the root cause of this issue is a corrupt icon cache. The following has solved the issue on some machines. The following link has some simple steps in it to rebuild the icon cache on a Windows 7 machine. http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/bea47202-d869-4155-8c8f-2a5b8bd7be1d/

SQL Timeout when upgrading large projects This problem has been reported when upgrading large projects to version 12.1.SP1 if the performance of the SQL Server is poor. To prevent this problem edit the file C:\Users\<User Name>\AppData\Roaming\inst.ini and add/modify the sections in red below:

[ElecProjects] Culture=en ProjectsDb=C:\Project Folder Current Project=01 - Elec Project 1 Current ProjectID=26 TransactionScopeTimeoutSeconds=1500 CommandTimeoutSeconds=300

http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/bea47202-d869-4155-8c8f-2a5b8bd7be1d/

http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/bea47202-d869-4155-8c8f-2a5b8bd7be1d/



[Projects] Culture=en Current Project=01 - Inst Project 1 Current ProjectID=39 ProjectsDb=C:\Project Folder TransactionScopeTimeoutSeconds=1500 CommandTimeoutSeconds=300

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/10481/w10481.pdf

Importing and Integration

Due to the changes in AVEVA Instrumentation and AVEVA Electrical to enable fully flexible tagging, additional data is now required to facilitate importing tags from Microsoft Excel and also from other AVEVA integrated products such as AVEVA P&ID and AVEVA Diagrams. The fields now required for import are:

Tag Number (as per previous versions)

Area (as per previous versions)

Area Path (new requirement for SP2)

Class (new requirement for SP2)

Tag Format (new requirement for SP2)

Importing from Excel

If tags are to be imported from Microsoft Excel the fields listed above should be populated as circled below.

Mapping the tag component fields (tag codes) is not mandatory, but it is recommended.

Importing from AVEVA Integrated Applications

If integration is required between AVEVA Instrumentation or AVEVA Electrical 12.1.SP2 and integrated applications such as AVEVA P&ID, AVEVA Engineering Tags, AVEVA Diagrams or AVEVA Schematic Model, additional attributes will have to be added for the new required fields and mapped for import/export. New User Defined Attributes (UDA’s) will be required for Area Path, Tag Class and Tag Format and these attributes will have to be added to existing mappings and populated for Compare/Update to work successfully. To perform successful Compare/Update actions for loop and instruments these UDA’s will have to be added to projects deploying AVEA P&ID, AVEA Engineering Tags, AVEA Diagrams and AVEA Schematic Model.

http://downloads.aveva.com/10481/w10481.pdf



The following example shows the mapping for importing instruments from AVEVA Engineering Tags. Note the additional mapped fields/attributes of TagFormat, ClassName and AreaPath.

These fields will need to be mapped and populated for the integration to be successful. As with importing tags from Excel, it is recommended that each component part of the tag number is mapped and imported, however this is not mandatory. Similar mappings are required to integrate with Aveva P&ID, AVEA Diagrams and AVEA Schematic Model. Please refer to the AVEVA Instrumentation 12.1.SP2 Release Update presentation for more information. This document contains notes and screen captures for all integration scenarios.

Importing Loops from AVEVA P&ID

As it is not possible to define user defined attributes for loops within Aveva P&ID, these attributes must be created and populated using Aveva P&ID Reports. Within Aveva P&ID Reports under Preferences > Table Columns the new attributes/columns can be added.



Once added, these attributes can be populated for loop via Aveva P&ID Report grids and mapped to exchange data with AVEVA Instrumentation via Compare/Update.

The following image shows the loop attributes created via Aveva P&ID Reports mapped for exchange via Compare/Update.



Previously Integrated Projects

To enable continued integration of AVEVA Instrumentation with other AVEVA schematic applications on existing projects, the following steps must be followed.

Upgrade AVEVA Instrumentation projects to 12.1.SP2 o This creates Area Path, Tag Class and Tag Format data in the AVEVA

Instrumentation database

Create new UDA’s for Area Path, Tag Class and Tag Format in integrated application o Aveva P&ID, AVEA Engineering Tags, AVEA Diagrams , AVEA Schematic Model

Add Compare/Update mappings for Area Path, Tag Class and Tag Format

Execute Compare/Update to pull new data from AVEVA Instrumentation o This populates Area Path, Tag Class and Tag Format from the AVEVA

Instrumentation database

Complimentary application data should now be updated and in synch with AVEVA Instrumentation

Non-integrated Projects – AVEVA Instrumentation as destination for data

To enable integration of AVEVA Instrumentation with other AVEVA schematic applications on projects where data has not yet been exchanged, the following steps have to be followed.

NOTE: This scenario assumes that the AVEVA Instrumentation database is empty and is the destination for the exchanged data.

Create new UDA’s for Area Path, Tag Class and Tag Format in source application o Aveva P&ID, AVEA Engineering Tags, AVEA Diagrams , AVEA Schematic Model

Populate these UDA’s in the source application o Area Path, Tag Class, Tag Format

Upgrade AVEVA Instrumentation project to 12.1.SP2, or create a new project

Add mappings for Area Path, Tag Class and Tag Format in AVEVA Instrumentation



Execute Compare/Update to pull new data into AVEVA Instrumentation

Data should now be updated and in synch

Non-integrated Projects – AVEVA Instrumentation as source of data

To enable integration of AVEVA Instrumentation with other AVEVA schematic applications on projects where data has not yet been exchanged, the following steps have to be followed.

NOTE: This scenario assumes that the AVEVA Instrumentation database is populated and is the source for the exchanged data.

Upgrade AVEVA Instrumentation project to 12.1.SP2, or create a new project o This creates Area Path, Tag Class and Tag Format data

Create new UDA’s for Area Path, Tag Class and Tag Format in destination application o Aveva P&ID, AVEA Engineering Tags, AVEA Diagrams , AVEA Schematic Model

Add mappings for Area Path, Tag Class and Tag Format in destination application

Execute Compare/Update to pull new data into destination application

Data should now be updated and in synch

General Integration Points

If Area Path and Tag Class are not mapped and populated, Compare/Update will not work

If Area Path and Tag Class are mapped, but Tag Format is blank, AVEVA Instrumentation will assign the primary tag format for the tag class

Aveva P&ID will not allow UDA’s to be created for Loops o These UDA’s must be created and populated using AVEVA P&ID Reports

For more information on integration please refer to the AVEVA Instrumentation 12.1.SP2 Release Presentation available for download from the AVEVA website.



Release Timeline and Upgrade Path

Documents

AVEVA Instrumentation 12.1 SP1 Fix 1 - Release Letterdownloads.aveva.com/10481/d10481.pdf · AVEVA PDMS 12.1 and above AVEVA Marine 12.1 and above AVEVA E3D 1.1 AVEVA NET All Supported