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
Status Shipped
Portfolio area Production Management (AMPLA MES)
Created by Nina NICHOLLS
Created on Nov 4, 2019

RELATED IDEAS

Better User Management

https://schneiderampla.atlassian.net/browse/CE-1896

[Raised by]
Customer Company: Rio Tinto Iron Ore (Perth)
Customer Contact: Ben Jones (ben.jones@riotinto.com)

[Enhancement Request]

This is another one from Rio Tinto IO which they are hoping would be considered for 2020 for when they plan to upgrade their Ampla server. The enhancements are:

  • Another mechanism that would make user administration simpler without the users having to access Ampla Studio for user configuration.

  • Ability to deploy/updates users to multiple Ampla systems (Prod, Dev, Test) in one go.

  • Ability to distinguish between individual users in an Ampla User that maps to an AD group, as explained below:

Consider an Ampla User called AmplaOperators that maps to CORP\AmplaOperators. CORP\UserX belongs to CROP\AmplaOperators and consequently to AmplaOperators. What they want is that, if UserX performs an Ampla acction such as classify a record, Ampla registers that against CORP\UserX (instead of AmplaOperators) without the need to create another user in Ampla for CORP\UserX. So, Rio Tinto wants to add users to the AD group and have Ampla still be able to map actions to their individual members without the need to create individual Ampla users.

I have also attached the email discussion on this request:

  • Attach files