Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Asset Information Management

TABLE OF CONTENTS

Content

Save PDF
Save selected topicSave selected topic and subtopicsSave all topics
Share
Share to emailCopy topic URL
  • Last UpdatedSep 10, 2024
  • 5 minute read

This release contains the following significant enhancements and defect fixes:

Core Functionality

Reference

Type

Description

2391777

960246950

Defect

In the Dashboard, some attribute values containing an @ symbol were wrongly being displayed as mailto links.

2627889

Enhancement

In Summary Views, when filtering a data group, if the results for a particular class are zero, then the class name is no longer shown.

2628410

960318608

Defect

When viewing documents, tags that wrapped onto multiple lines may not have been highlighted.

Any files that had this issue will NOT need to be re-processed.

2854631

Defect

When switching tabs in a Content Card, some tabs were gathering multiple close icons.

2914658

Enhancement

To better support data modelled on CFIHOS standards, more data can be displayed in Summary Views.

The set of panels that can appear on Summary Views comprises of:

  • Details Header

  • Attributes panel

  • Links panel

  • Tags panel

  • Equipment panel

  • Parts / Components panel

  • Documents and 3D Models panel

  • Events panel

  • Activities / Tasks panel

  • Relationship Explorer

    As before, the panels themselves will only be shown where relevant data is present.

Location data was only available for the general Tag Summary View. Now Location data is also shown for Event, Activity and Document Summary Views.

Any "is implemented by"/"implements" relationships are now shown, for example:

2914661

Defect

In the Dashboard, labels used for class hierarchies in Search and Visual Reports always showed the class ID. They now correctly follow the configuration setting for Label Types.

2914682

960318717

Enhancement

In the Dashboard, Tag Content Cards now display any "has document" associations in the Related Documents tab.

3004287

960355515

Defect

In the Dashboard, when viewing files rendered in SVG and using the Print option in the viewer, then printouts may have had text wrongly shifted to the right.

3020285

960366343

Defect

When viewing documents, tags that contained some special characters may not have been fully highlighted.

Any files that had this issue will NOT need to be re-processed.

3045887

960378366

Defect

When downloading documents viewed in the Dashboard, larger files (>1GB) may have resulted in an unhandled server error.

Now, the case is handled with an appropriate error message.

3057849

960385339

960391859

Defect

Filters for dropdowns in Query Forms and the Query Form Designer had stopped working correctly.

3057879

960387873

Defect

When using Advanced Search in the Dashboard and adding a filter, the text entry box for the filter was adding a % symbol as soon as characters were typed. The I=bar cursor was then out of position and the % symbol could not be removed.

3074149

Process

Updated the release to the latest Microsoft patches.

Document Connector

Reference

Type

Description

2275878

Enhancement

Support for importing documents from OpenText Core has been added.

See the documentation at:

https://docs.aveva.com/bundle/asset-information-management/page/1363308.html

3055329

Enhancement

When onboarding a tenant, values for TenancyId are now case- insensitive.

Data Pipeline

Reference

Type

Description

2496205

960367287

960385693

Defect

Intermittently, some meta data loads were failing to fully load.

2914678

Enhancement

The Registers Gateway has been enhanced to allow the definition of:

  • naming and numbering templates based on context

  • enumerated lists (lists of values) based on context.

    This is to better support the ability to have multiple assets (based on context) in one instance. Even if different assets follow the same class library, their naming and numbering templates and enumerated lists are often different.

    This will be documented as part of a wider appraisal of ISM to AIM-A configuration.

2914688

Enhancement

The time to process 2D files has been significantly improved.

This has included upgrading to the new AVEVA Gateway for 2D Data. Existing files do NOT need to be re-processed.

For more information on configuring the new Gateway, see the below section: Using the AVEVA Gateway for 2D Data - Transformation Configurations and https://docs.aveva.com/bundle/asset-information-management/page/1174973.html

For more information on defects fixed, see:

https://docs.aveva.com/bundle/gateways/page/1264080.html

3016326

960318694

960334567

Defect

The Data Pipeline now reads the ISM extensions for Units of Measurement (UoM) - both scale and constant. This in turn enables the appropriate search functionality based on UoMs to work.

3029814

Enhancement

When importing IDs into the Data Pipeline, curly brackets, { and }, are invalid. However, if they do appear in IDs, they are now replaced with parenthesis, ( and ) respectively, and a warning is raised in the log file.

See the documentation at:

https://docs.aveva.com/bundle/asset-information-management/page/1166281.html

Data Pipeline - Load Reporting

Reference

Type

Description

3040986

960386534

Defect

When viewing log files in the Load Reporting Portal, all errors and warnings were being truncated to 80 characters (except in verbose mode).

The messages are no longer truncated.

Using the AVEVA Gateway for 2D Data – Transformation Configurations

  1. Pattern: A set of regular expression rules used to find specific objects. A regular expression is a template that helps identify tags. For example: [A-Z]{3}-\d{2}\s\d\/\d\x22-[A-Z]{3}-\d{7}-[A-Z]{2}-[A-Z]

    • [A-Z]{3}: This part matches exactly three uppercase letters from A to Z.

    • -\d{2}: This matches a hyphen followed by exactly two digits (0-9).

    • \s: This matches a single whitespace character.

    • \d/\d: This matches a digit followed by a forward slash and another digit.

    • \x22: This matches a double quotation mark (").

    • -[A-Z]{3}: This matches a hyphen followed by exactly three uppercase letters from A to Z.

    • -\d{7}: This matches a hyphen followed by exactly seven digits (0-9).

    • -[A-Z]{2}: This matches a hyphen followed by exactly two uppercase letters from A to Z.

    • -[A-Z]: This matches a hyphen followed by a single uppercase letter from A to Z.

  2. Expansion: A set of regular expression rules used to find additional objects that should be included. It's an extension of the template used for Patterns (see point 1).

  3. Char (Character): This identifies a particular symbol used within the expansion to mark where it should be added. It's like a signpost indicating where to add extra things.

  4. Interpolate: This tells the system whether a range of values should be inserted based on the expansion result. It's like deciding whether to fill in the gaps between identified objects.

  5. KeepPattern (optional): This regular expression is used to narrow down the results matched by the original pattern. It helps to filter out specific subsets of the initial matches. For example in [A-Z]{1,2}-\d{4},

    • [A-Z]{1,2}: This part matches one or two uppercase letters from A to Z.

    • -: This matches a hyphen.

    • \d{4}: This matches exactly four digits (0-9).

      So, overall, this pattern would match strings that start with one or two uppercase letters followed by a hyphen and then exactly four digits. For example, it would match patterns like "A-1234" or "AB-5678".

  6. SearchCriteriaPattern (optional): These additional regular expression patterns are applied to the values of attributes. For instance, if you have text such as "P-101ASDFP-102ASDFP-103" and you want to identify codes within the text such as "P-101A" and "P-102A", then the search pattern might be something like "[A-Z]-\d{3}[A-Z]". This helps you find specific patterns within a larger text.

Sample File for importing:

For AutoCAD the name of the file must be: drawingfile-ac2d-transformconfiguration.xml. For MicroStation the name of the file must be: drawingfile-ms2d-transformconfiguration.xml

<?xml version="1.0" encoding="utf-8"?>

<MappingTemplate guid="d2d0574d-5e6a-4158-9841-23ff436623b0" componentVersion="2.10.0.0" sourceProductName="AVEVA™ Gateway for 2D Data" componentName="BaseMapping" creationDate="2023-12-20" createdBy="j.smith">

<ObjectMappings>

<Object>

<Conditions>

<Attribute name="ObjectID" pattern="A-Z]{3}-\d{2}\s\d\/\d\x22-[A-Z]{3}-\d{7}-[A-Z]{2}-[A-Z]" />

</Conditions>

<SearchCriteria attribute="ObjectID">

<Search>

<Patterns createAlias="false">

<Pattern value="[A-Z]{1,2}-\d{4}" />

</Patterns>

<ClassID value="unknown" />

</Search>

</SearchCriteria>

<ClassID value="unknown" />

</Object>

<Object>

<Conditions>

<Attribute name="ObjectID" pattern="[A-Z]{3}-\d\.\s\d{2}\x22-[A-Z]{2}-\d{3}-\d{4}-[A-Z]{2}-[A-Z]" />

</Conditions>

<Transforms>

<Keep pattern="[A-Z]{4}-\d{5}" />

</Transforms>

<SearchCriteria attribute="ObjectID">

<Search>

<Patterns createAlias="false">

<Pattern value="[A-Z]{1,2}-\d{4}" />

</Patterns>

<ClassID value="unknown" />

</Search>

</SearchCriteria>

</Object>

<Object>

<Conditions>

<Attribute name="ObjectID" pattern="[A-Z]{3}-\d\.\s\d{2}\x22-[A-Z]{2}-\d{3}-\d{4}-[A-Z]{2}-[A-Z]" />

</Conditions>

<Transforms>

<Keep pattern="[A-Z]{4}-\d{5}" />

</Transforms>

</Object>

<Object>

<Conditions>

<Attribute name="ObjectID" pattern="[A-Z]{3}-\d{2}\s\d\/\d\x22-[A-Z]{2}-\d{6}-[A-Z]{3}-[A-Z]" />

</Conditions>

</Object>

<Object>

<Conditions>

<Attribute name="ObjectID" pattern="[A-Z]{3}-\d\s\d\/\d\x22-[A-Z]{3}-\d{7}-[A-Z]{2}-[A-Z]" />

</Conditions>

</Object>

<!--untag not matched texts-->

<Object>

<ObjectID value="" />

</Object>

</ObjectMappings>

</MappingTemplate>

Related Links
TitleResults for “How to create a CRG?”Also Available in