A new AVEVA Engineering product was introduced with the release of AVEVA Plant and AVEVA Marine 12.1. This new product includes a new Tags module as well as a new ENGIneering Dabacon database type, designed and optimized for Engineering data. The Engineering product also includes Schematic Model Manager, which is no longer sold as a separate product.
15.1 Tags
The new Tags module provides an easy-to-use and powerful user interface for engineering users, allowing them to work on Engineering Lists & Schedules and related data.
Some of the more prominent features and functions of the Tags module are as follows:
• Easy-to-use User Interface: Familiar Microsoft Office 2010-like UI. See pictures overleaf.
• List Editing: Grid-based editing of list data in the new ENGI database. List views can be set up Project Wide by administrators. It is also possible for reg ular users to create and use their own specialized layouts. This includes grouping/filtering and bulk editing capabilities.
• Multi-discipline concurrent engineering: By using the new Distributed Attributes and Database Views mechanisms, it is possible to allow true parallel work between different disciplines, even on the same object.
• Navigation: In addition to the list editing, it is also possible to navigate the engineering or system hierarchy to find and edit individual items.
• Data Management functions: A number of management functions such as Status Control, Change Highlighting, Attribute History and Extracts are available to manage the lifecycles of engineering objects.
• Change Highlighting: It is possible to highlight and report on changes made by different users and disciplines. This also includes highlighting of changes made in diagrams.
• Diagram viewer: A built-in diagram viewer allows users to view and navigat e P&IDs and other schematics.
• Compare & Update: Engineering data can be compared and updated against a number of other AVEVA sources, such as Schematics, 3D, AVEVA Instrumentation etc. (see Compare/Update). It is also possible to compare individual items of the same kind against each other to find differences.
• Excel Import/Export: Engineering data can be imported from external sources and exported to external applications by using Excel Import/Export utilities.
• AVEVA NET Integration: Engineering data can be exported to AVEVA NET
• Reports: Project-quality formatted reports can be created direct from the Dabacon databases. As Engineering is based on the same platform as the 3D and Schematics tools, it is very easy to combine data from these sources into common reports.
For full details of this important new module, please see the AVEVA Tags User Guide.
15.1.1 Admin Tab
The Tags module includes a new concept for administration. There is an “Admin” tab in the ribbon bar which is only available for users that are:
Free users (Like SYSTEM)
Members of the TAGSADMIN team
Allocating users to the TAGSADMIN team allows superusers or department managers to perform certain admin tasks in Tags / engineering, without them having to be free users.
15.1.2 Tag Deletion
In the new Tags module, data for a single tag can be distributed over multiple databases to allow for different disciplines, possibly operating in different locations. For any tag, the data for each discipline is stored on a separate object but presented as if on a single object. It is thus possible to delete a tag but not have access to delete all of the distributed data, and this can result in orphan objects remaining.
The Delete Tag Orphans.pmlmac macro (available from AVEVA Support Knowledge Base) can be run in the Tags module to find and delete orphan objects. Please note that all relevant databases should be c urrent before running this macro (it contains a warning). It maintains a log of its results including any errors where it is unable to delete an object. It may need to be run at different locations to tidy up periodically.
15.1.3 Project Breakdown Structure Explorer *12.1.SP4*
The PBS (Project Breakdown Structure) Explorer allows the presentation of database content depending on a user‟s particular needs. It is accessible on the “Home” ribbon tab in the “Database” group:
The data can be shown as one or more u ser-defined structures. Each structure is shown in the Explorer as a hierarchy starting from a separate root node and can show database items organized according to their belonging to system, class, etc., depending on the definition in Lexicon (for more information, please refer to Project Breakdown Structure chapter in the Lexicon User Guide).
The PBS Explorer tree is generated at runtime from Lexicon definition. Its nodes can represent database items as well as just label texts generated from the definition. By selecting a node connected to a database item, the user can navigate the database hierarchy (set current element). In addition, a context menu with basic commands is available for relevant nodes.
15.1.4 Datasheets in AVEVA Engineering *12.1.SP4*
Datasheet instances can now be created and edited in Tags. Data entered in mapped fields in the datasheet will automatically be updated in the database. Datasheet instances are based on a previously created Datasheet template (see below) and can be revisioned .
Datasheets can be viewed read-only in AVEVA Diagrams if a schematic item is linked to the engineering item.
Templates are set up in Lexicon using the Datasheet Template Editor. The templates are based on Excel format, which allows for importing existing Excel templates and mapping attributes to the database. It is possible to add free text fields on the datasheet templates that are not stored in the database. User Defined Revision Schemas can be set up in Lexicon.
15.1.5 AVEVA NET Gateway *12.1.SP4*
The “Publish to AVEVA NET” function enables engineering data to be published to AVEVA NET.
If you are upgrading from PDMS 12.1.SP2, additional steps are needed to make the new 12.1.SP4 Datasheets option available in the “Publish to AVEVA NET” configuration form. This procedure is not required for a project that is created initially at 12.1.SP4.
For an existing project, either carry out the 3 steps below or see the alternative approach that follows:
1. Rename the old configuration file present in the project folder. For example, for the SAMPLE project rename the file AvevaNetExportConfigAddin.xml in the folder %SAMDFLTS%\PublishToAvevaNet.
2. The AVEVA NET Gateway Setup checks for the configuration file in the project folder, and if it is not found there, will copy the default file from %PDMSEXE%. Login to Tags; Click on “AVEVA NET Gateway Setup” menu in the Admin Tab and the datasheet option will be now available.
3. Re-implement any customisations that had been implemented in the original file.
An alternative approach is to replicate the “Reports” section under “Tags” module in the AvevaNetExportConfigAddin.xml file in the current project folder location.
After copying the “Reports” section, change the configuration name from “Reports” to “Datasheets”.
This will ensure that any changes made previously to the project configuration file are retained.
15.2 Schematic Model Manager
15.2.1 Use of units
Schematic Model Manager now uses the new units capabilities rather than its former specific units functions. This means that imported data is automatically converted to the appropriate units chosen for the project. In the Project Options dialogue, the Units tab has been removed.
The specific Units UDAs have been removed from the default file and will no longer be popu lated on import. Users can choose to use them but will need to set them up as required.
The Attribute Type is no longer needed in the Attribute Mapping file, so has been removed from the Attribute Mapping UI.
15.2.2 Units upgrade
Schematic data imported prior to 12.1 must be upgraded. A check is performed automatically on entry to Schematic Model Manager and the user will be warned if an upgrade is required. The upgrade process must be carefully considered by project administrators as it can affect multiple projec ts and locations. Firstly, schematic data is scanned to identify changes required. Secondly, UDA definitions are updated for the appropriate units. Thirdly, the changes identified are applied to the schematic data.
Please refer to the Schematic Model Manager User Guide for full details of this process.
15.2.3 Change Highlighting in Diagram
Changes in Diagrams may now be highlighted in Diagrams, Schematic Model Manager and Tags, using a new Diagram Change Highlighting add-in.
Please see section 14.1 in the Diagrams chapter.
Change the name from “Reports” to “Datasheets” after copying this section