AVEVA™ Products Feedback Portal

Welcome to our new feedback site!


We created this site to hear your enhancement ideas, suggestions and feedback about AVEVA products and services. All of the feedback you share here is monitored and reviewed by the AVEVA product managers.

To start, select the product of your interest in the left column. Then take a look at the ideas in the list below and VOTE for your favorite ideas submitted by other users. POST your own idea if it hasn’t been suggested yet. Include COMMENTS and share relevant business case details that will help our product team get more information on the suggestion. Please note that your ideas will first be moderated before they are made visible to other users of this portal.

This page is for feedback for specific AVEVA solutions, excluding PI Systems and Data Hub. For links to these other feedback portals, please see the tab RESOURCES below.

Add a new idea Subscribe
Portfolio area Information Standards Manager
Created by Geoffrey Coad
Created on Feb 14, 2022

RELATED IDEAS

Supress inheritance of Naming Templates

ADO link: https://dev.azure.com/AVEVA-VSTS/Information%20Management/_backlogs/backlog/All%20Teams/Features/?workitem=1532319


A general naming template is associated at high level in the hierarchy, on more specialised classes it should be possible to "replace" the naming template (WorleyParsons)

It is rare, but not unheard of, for a Class to have multiple Naming templates for an individual Project - particularity in a greenfield scenario, it may be more common in brownfield.

Within a greenfield scenario a principle Number template may be associated at a high level class, however in lower level classes it would be superseded by a different naming template at the point of instantiation, ensuring we only have a one to one relationship between Class and Naming Template.

In a brownfield scenario we may need to have a One to Many relationship between Class and Naming Template to account for legacy templates as well as new/current ones.

At the moment AVEVA ISM aggregates the templates on a class, wee need to be able define the behaviour, potentially at the Class Library level.

  • Attach files