cf10481 PDF

AVEVA Instrumentation 12.1.
SP2 Product Feature Update

Chris Binns Product Manager Electrical & Instrumentation
AVEVA Instrumentation 12.1.SP2 New Features

Pick-list enhancements Enhanced Excel export/import controls in Security Manager Decimal comma support Duplicate sub-areas AVEVA Diagrams Licensing AVEVA Engineering/Tags rebrand Fluent UI changes Wiring rule enhancements Process Data datasheet datalink improvements Flexible tagging
Copyright 2013 AVEVA Solutions Limited and its subsidiaries. All rights reserved.
Pick-List Enhancements
Pick-list Enhancements
Originally released in 12.1.SP1 Fix 1 Users with applicable permissions can now assign a pick-list to (almost) any field or property displayed in any data access grid Also applicable to AVEVA Electrical
Description field for pick-list values
Users can now add descriptive entries against pick-list values
Assign pick-lists to fields
Pick-lists can be assigned directly to fields in the grids via the Grid Manager dialogue
Assign pick-lists to fields
Pick-list values accessible via the grids Capability applies to both out-of-the-box pick-lists and user defined pick-lists
Locked Pick-lists
If a pick-list is locked, users can only select data from the pick-list value list via the grids. Data cannot be entered manually
If a locked pick-list is assigned to a field via Grid Manager, and that field is displayed as a text box on a dialogue, the text box becomes read-only on the dialogue. The text box will not automatically convert to a pick-list. It will remain a read-only text box. If an unlocked pick-list is assigned to a field via Grid Manager, and that field is displayed as a text box on a dialogue, the text box remains open on the dialogue. The text box will not automatically convert to a pick-list. It will remain an open text box. If an attempt is made to import a value to a field assigned to a locked pick-list, and that value is not incorporated within the value list for the pick-list, then the import of that value will fail. If that value is attributed to a new record/tag, then the import of that record/tag will fail entirely.
Bulk Edit of Tags
The application of pick-lists to fields in the grids will also apply to the bulk edit dialogues as below
Pick-lists on Datasheets
Any fields that have pick-lists assigned to them via grids, will not appear automatically as pick-lists on datasheets Once a cell on a datasheet template has been mapped to a field, the cell still has to be right-clicked and associated with the corresponding pick-list Locked pick-lists will still prevent data from being manually entered via the datasheet that is not incorporated within the value-list for the locked pick-list
Enhanced Excel Export/Import Controls
Enhanced Excel export/import controls

Enhancements within Security Manager Originally released in 12.1.SP1 Fix 3 Exporting and importing of data via Excel can now be controlled by user groups within Security Manager New Access Types such as Full Access (No Excel Import/Export) added Also applicable to AVEVA Electrical

Excel Export/Import Controlled by User Groups
New Access Types with options to control Excel Import/Export
Full Access (No Excel Import) Full Access (No Excel Export Full Access (No Excel Import/Export) Read Only (No Excel Export)
These access types are assigned to user groups as below In this example all the Instrument Designers have Full Access but cannot export or import instrument or loop tags via Excel

UI Response
Once security is enabled for the project and an Instrument Designer logs in, the Excel export and import buttons are disabled
Decimal Comma Support

Windows Region & Language settings observed to support decimal comma vs. decimal point Application language settings do not influence this setting Example: language set as English and the Decimal Symbol comma Data still stored in database as decimal point to facilitate integration with existing AVEVA application
Will change once all AVEVA apps support decimal comma

Windows Region and Language settings
Format = Portuguese (Brazil) Decimal Symbol = ,

AVEVA Instrumentation
Language = English Control Valve Sizing data utilising decimal comma instead of decimal point

AVEVA Electrical
Language = English Load Detail pick-lists and motor catalogue data displaying decimal comma instead of decimal point
Duplicate SubAreas
Duplicate Sub-Areas
Users can now create duplicate areas as sub-areas For example the following is now permitted
Plant 1 > Area 01 > System 01 Plant 1 > Area 02 > System 01
AVEVA Diagrams Licensing

Change details
Previously when integrating AVEVA Diagrams data into AI/AE the integration choice was AVEVA Schematic Model Import This was confusing for customers who bought Diagrams (as they did not know of a Schematic model) It was also problematic for sales because the Schematic option was using PDMS module number 97, Schematic Model manager Schematic Model Manager is not bundled with Diagrams and therefore when connecting it tries to take out a PIDMANAGER license which is not part of Diagrams licensing

Change details continued
This licensing issue has been addressed in 12.1.SP2 A new integration option AVEVA Diagrams has been added to the integration panel in the Manage tab and to setup The new option now checks out the correct AVEVA Diagrams license
AVEVA Tags / Engineering rebranding
AVEVA Tags/Engineering rebranding

Previously within the AVEVA Integration section of the UI there was a button labelled AVEVA Tags Import This has been renamed as AVEVA Engineering Import and provides the choice of modules:
AVEVA Schematic Model Import AVEVA Tags Import
Fluent UI Changes
Fluent UI Changes
Data Management tab now labelled Manage
AVEVA Integration pane now labelled Integration
Contextual Menu now displays List Tools or Catalogue Tools Changes made to align with other AVEVA Schematic apps
Wiring Rule Enhancements

Spare and Reserved terminal Status
Terminals can now have status of Spare or Reserved Status can be assigned to the left, right or both sides of a terminal Status observed during both automatic and manual termination Automatic terminations will always skip spare or reserved terminals Manual terminations are permitted to spare terminals without any messaging Manual terminations to reserved terminals are permitted following warning messaging

Wiring pattern sequence vs. catalogue sequence
The connection order of the wiring rule is always preserved even if this does not match the core sequence order defined in the cable catalogue
Spare and Reserved Terminals

Right-click options to set terminal status
Spare or Reserved Left, Right or Both

Status colour coding
Blue = Spare Grey = Reserved
Junction Box Allocation

Spare and Reserved terminals skipped Cable core grouping is preserved

Allocation of multiple instruments
Reserved terminals skipped Continuous terminations on next available terminals

Manual connection to spare terminal
Automatically removes spare status of terminal side
Manual connection to reserved terminals

Connection attempted to terminal 5 Messaging displayed User can choose to continue with connection

Manual connection to reserved terminals contd..
Reserved status removed from terminal side(s)
Wiring Pattern vs. Catalogue Sequence

Example
Cable catalogue type IEF184AA001 Core Sequence
1 = 1W 2 = 1B
Wiring Patterns vs. Catalogue Sequence

Wring Rule
Wiring rule defined with cores connected to JB switched
Connections at JB opposite way around from catalogue sequence order
Wiring Patterns vs. Catalogue Sequence

Terminations
Connection sequence order defined in wiring rule preserved Wiring rule sequence overrules catalogue sequence
Process Data Datasheet datalink improvements
Process Data datasheet datalink improvements

Mapping datalinks for associated process equipment and process line simplified
Max no. of plant connections set at datasheet template level
Helps to limit amount of datalinks listed for mapping

Table selection when mapping datalinks reduced from:
InstProcessData>ProcessEquipment1 InstProcessData>ProcessLine1 Common>PETag1 Common>PLLine1 ProcessEquipment>PETag1 ProcessLine>PLLine1
To simply:
InstProcessData>PlantConnection1 ProcessProperties>PlantConnection1

InsProcessData = form data held in the InstProcessData table

ProcessProperties = extended properties for process objects
Flexible Tagging
Flexible Tagging
Previous tag formatting options too restrictive SP2 introduces a basic level of 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 or service etc. Classification possible for Process Equipment, Process Lines, Loops, Instruments as well as electrical loads and supplies
Tag formats can be made up of (potentially) unlimited numbers of parts (tag codes)
Flexible Tagging
Flexible Tagging continued
Tag Codes (fields in tables) can be created by users to suit any project requirements
Most existing fields in tables such as InstrumentList and LoopList can be used as tag codes Pick-lists can be assigned to any tag code via Grid Manager Users can define their own tag code delimeters
Tag function codes (types) associated with classes

The selection of tag class controls which function codes are made available for selection
No need to assign instrument tag format at project creation

No longer restricted to 1 tag format for all tags
Flexible Tagging
Flexible Tagging continued
Legacy project upgrades will assign a base class to existing tags along with migrating the tag format
Flexible Tagging
Class Definitions
A basic level of classification has been introduced All tags must have a class type Tag formats assigned at the class level A class must have 1 primary tag format A class can have multiple alternate format Projects can be configured to use one class (per object type) or multiple classes Out-of-the-box classes shipped that align with Aveva P&ID
Flexible Tagging
Class Definitions
Classes are required for the following object types:
Loops Instruments Process Lines Process Equipment Electrical loads (AVEVA Electrical) Electrical supplies (AVEVA Electrical)
Most out-of-the-box classes can be deleted if not required

Exceptions:
Loop ILP Instrument INS Process Equipment EQU Process Line PMA and PSU
Flexible Tagging
Class Definitions and Tag Formats
Users can create new classes if required Classes can be exported and imported via Excel to enable exchange between projects Tag Formats are associated with classes via the Class Definitions dialogue
Flexible Tagging
Class Definitions and Tag Formats
Each class has minimum 1 primary tag format Alternate tag formats are not mandatory The example below shows ISA with Area (delimiters) as being the primary tag format All the other ISA tag formats are assigned as alternate tag formats for the class
Flexible Tagging
Tag Formats
Project creation no longer requires the instrument tag format to be specified
All tag formats shipped with 12.1.SP1 still ship with SP2
Flexible Tagging
Tag Formats
New Tag Format dialogue redesigned No limitation on how many parts or Tag Codes make up a tag number
Flexible Tagging
Tag Codes
Most fields in the source tables can be used as a tag code Users can add their own fields to the source tables to be used as tag codes Datatype and maximum value length can be specified
Flexible Tagging
Tag Codes
Once added, tag codes are available for tag formats
Delimiters can be entered manually if they are not already incorporated in the pick-lists Space and no space (blank) supported as delimiters Some characters cannot be used as delimiters i.e. %, @, !
Flexible Tagging
Type Catalogue
Function Codes within the type catalogues are now associated with the classes Association with class determines availability of function codes when creating a new tag
Flexible Tagging
Type Catalogue
Classes associated with function codes via the New/Edit Type dialogue If types are not associated with a class, the Function code pick-list will be empty when creating a tag of that particular class
Flexible Tagging
Pick-lists and Tag Codes
Pick-lists are assigned to tag codes via the Grid Manager dialogue Pick-lists are created as per 12.1.SP1
Flexible Tagging
Separate New/Edit tag dialogue
User selects the class and tag format before entering the tag data Primary tag format always presented first in the pick-list Selecting a different tag format dynamically changes the dialogue structure
Flexible Tagging
New/Edit Tag dialogue
Tag number now displayed as a label Blue arrow clicked to edit tag number Area path shown to interpret duplicate subareas
Flexible Tagging
Importing Tag from Excel
Mandatory fields required to import data from Excel:
Tag No Class Name Format Name Area Path Area
Recommended fields:
Individual Tag Codes Mapping these fields will ensure that the tag code fields in AVEVA Instrumentation are in synch with the tag number
Flexible Tagging
Integration with complimentary AVEVA applications
Integration of AVEVA Instrumentation with other AVEVA Schematic applications requires the mapping of 3 new fields:
Area Path Tag Class Tag Format
These 3 fields must be created as UDAs within the complimentary applications such as AVEVA P&ID These 3 fields must be populated in both AVEVA Instrumentation and the integrated application for Compare/Update to work
Flexible Tagging
Previously integrated projects To enable successful integration the following steps must be executed:
Upgrade AVEVA Instrumentation projects to 12.1.SP2
Creates Area Path, Tag Class and Tag Format data
Create new UDAs for Area Path, Tag Class and Tag Format in integrated application Add mappings for Area Path, Tag Class and Tag Format Execute Compare/Update to pull new data from AVEVA Instrumentation Complimentary application data should now be updated and in synch
Flexible Tagging
Non-integrated projects AVEVA Instrumentation as destination for the data
Create new UDAs for Area Path, Tag Class and Tag Format in source application i.e. Aveva P&ID Populate these UDAs in the source application 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
Flexible Tagging
Non-integrated projects AVEVA Instrumentation as Source for the data
Upgrade AVEVA Instrumentation project to 12.1.SP2, or create a new project
Creates Area Path, Tag Class and Tag Format data
Create new UDAs for Area Path, Tag Class and Tag Format in destination application i.e. Aveva P&ID 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
Flexible Tagging
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 UDAs to be created for Loops
These UDAs must be created and populated using AVEVA P&ID Reports See Aveva P&ID mapping information in this document and AVEVA Instrumentation 12.1.SP2 Release Letter
Flexible Tagging
Integration with AVEVA Engineering Tags
AVEVA Engineering Tags required mappings
New mappings highlighted Note new UDAs in AVEVA Tags
Instruments Loops
Flexible Tagging
Integration with AVEVA Diagrams
AVEVA Diagrams required mappings
New mappings highlighted Note new UDAs in AVEVA Diagrams
Instruments
Loops
Flexible Tagging
Integration with AVEVA Schematic Model
AVEVA Schematic Model required mappings
New mappings highlighted Note new UDAs in AVEVA Schematic Model
Instruments
Loops
Flexible Tagging
Integration with AVEVA P&ID
AVEVA P&ID required mappings for loops
AVEVA P&ID does not allow UDAs to be created for loops The new UDAs required for integration of loop data must be created and populated using Aveva P&ID Reports
Flexible Tagging
Integration with AVEVA P&ID
AVEVA P&ID required mappings
New mappings highlighted Note new UDAs in AVEVA P&ID and P&ID Reports
Instruments Loops
Flexible Tagging
Loop Edit dialogue > Add Tag
If the instrument class primary tag format contains Function code, functionality as per 12.1.SP1
Flexible Tagging
Loop Edit dialogue > Add Tag
If the instrument class primary tag format does not contains Function code, then the instrument tag must be created from scratch or picked from the instrument list
Flexible Tagging
Project Level Tag Format Update
Tag Format dialogue Update Tags option Example:
Existing tag contain Plant No
Flexible Tagging
Project Level Tag Format Update
Example:
Remove Plant No from tag format and apply to all applicable tags
Plant No removed from all applicable tags
Flexible Tagging
Tag Level Tag Format Update
Select applicable tags in grid Pick Bulk Update Tag Format Select tags to change and pick new tag format Tag formats update New tag format now applied
Flexible Tagging
Tag Level Class Update
Tag class can also be changed via this dialogue For example, change a general instrument to a control valve by removing the lock on class
Flexible Tagging
Copy Wizard
Tag Copy Wizard now groups the tags by tag format
Thank you

cf10481 PDF

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

cf10481 PDF

Загружено:

Авторское право:

Доступные форматы

AVEVA Instrumentation 12.1.

SP2 Product Feature Update

AVEVA Instrumentation 12.1.SP2 New Features

Enhanced Excel Export/Import Controls

Enhanced Excel export/import controls

Enhanced Excel export/import controls

Enhanced Excel export/import controls

Decimal Comma Support

Decimal Comma Support

Decimal Comma Support

Decimal Comma Support

Decimal Comma Support

AVEVA Diagrams Licensing

AVEVA Diagrams Licensing

AVEVA Diagrams Licensing

AVEVA Tags / Engineering rebranding

AVEVA Tags/Engineering rebranding

Wiring Rule Enhancements

Wiring Rule Enhancements

Wiring Rule Enhancements

Spare and Reserved Terminals

Spare and Reserved Terminals

Junction Box Allocation

Spare and Reserved Terminals

Spare and Reserved Terminals

Manual connection to reserved terminals

Spare and Reserved Terminals

Wiring Pattern vs. Catalogue Sequence

Wiring Patterns vs. Catalogue Sequence

Connections at JB opposite way around from catalogue sequence order

Wiring Patterns vs. Catalogue Sequence

Process Data Datasheet datalink improvements

Process Data datasheet datalink improvements

Helps to limit amount of datalinks listed for mapping

Process Data datasheet datalink improvements

Process Data datasheet datalink improvements

Process Data datasheet datalink improvements

Tag function codes (types) associated with classes

No need to assign instrument tag format at project creation

Most out-of-the-box classes can be deleted if not required

Plant No removed from all applicable tags

Вам также может понравиться