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 10, 2022

RELATED IDEAS

Plugin Management

AVEVA Information Standards Manager is built upon the idea of an inner core product and additional surrounding layers of functionality provided by Extensions and Plugins. This section is going to look at the future of the plugin functionality.

When ISM was only being designed as an on-premises product, it was expected that plugins could be created by consuming applications, rather than all plugins being supported by the ISM Product team, and Customers would be able to write their own Plugins as needed, which would greatly improve the configurability of ISM and enable Class Library to drive product configuration without needing to change the core functionality which defines Class library without the concept of product.

One of the advantages of this approach was that customers would only need to use the plugins that they required, whereas in our cloud implementation; as all the plugins are in the single multi-tenant version; all customers have access to every plugin , whether they want them or not, and we are not able to restrict access to specific plugins on a commercial basis.

Currently we have Plugins to manage:

  1. Import of formats into ISM

  2. Validating Class Libraries

  3. Exporting class Libraries in various formats (e.g. Permissible Grid)

We should implement a process where we are able to restrict, or grant, access to plugins and APIs at the account level

  • Attach files