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 Mar 25, 2022

RELATED IDEAS

AVEVA NET Validation should ensure that there is no duplicate Class Names

A customer is using ISM to help configure AVEVA NET (AIM) and AVEVA Engineering and want to ensure that the Class Names are unique. Currently ISM only ensures uniquness at the ID level and that is usually within Context.

As this is a fundamental way that ISM works We should not change this, however we should support the customer's request we should therefore have the option in to identify Duplicate Names as an error as part of the validation process.

This has already been worked on and exisits in code but has not ever been released

Original Customer Request:

I can create as many classes as I want, all named the same thing. That's not good. It works contrary to how other Aveva systems enforce naming. It doesn't matter if they have different IDs, Aveva Engineering and Aveva NET do NOT like this if you use an ISM export to try to configure them.


  • Attach files