Skip to Main Content
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

Clear

Ideas

Showing 9 of 791

Indicate when not all records are being returned in PA

If too many records are returned based on the specified filters for PA request is to indicate that not all records are being shown. This causes confusion when customers thinks everything is being returned but it is being capped.
Nina NICHOLLS 3 months ago in Production Management (AMPLA MES) / Production Analyst 0 Future consideration

Add option to make the recurse button on PA enabled by default when logging into PA

Add the option to make the recurse button on PA enabled by default when logging into PA [Reason] The main purpose is to apply the with recurse across a group of users to view the multiple areas of the downtime events/charts for a given site.
Nina NICHOLLS 7 months ago in Production Management (AMPLA MES) / Production Analyst 0 Future consideration

Add ability to delete lot group reporting point record from PA

Currently, we can delete the Lot group reporting point record in the lot group standard view from the table LotGroupDataSet by using the Delete Script. There is no option to delete the record from the Production analyst in Inventory. Can you pleas...
Nina NICHOLLS about 1 year ago in Production Management (AMPLA MES) / Production Analyst 0 Needs review

Persist heirarchy node expansion state

Customer has requested for a feature where all the nodes in the navigation pane are expanded by default when PA is opened. Currently this feature is not available, raise it as an enhancement request. Thanks.
Nina NICHOLLS about 1 year ago in Production Management (AMPLA MES) / Production Analyst 0 Future consideration

Persist filter builder window size

AMPLA 8.2 PA window contents take up more space vs V5, resulting in having to resize the window to see all the contents at once. Having the resized window stay persistent will remove the need to constantly resize the window similar to how the edit...
Nina NICHOLLS about 1 year ago in Production Management (AMPLA MES) / Production Analyst 0 Future consideration

Indirect Tag for "SliceBy"

In our case (and I suspect others) we have many of the same type of equipment. It would be ideal to be able to specify a tag name pattern or something of that nature in the SliceBy call. This would avoid us having to iterate through a list of tags...
Elliott Middleton about 2 years ago in Historian & Client / Expressions 0 Submitted

Add store-forward to the SDK "SendValues()" method for slow data rates

For reliable, low data rate, but out-of-sequence data from non-process data sources. Requested by Mike Brost for an OEM application.
Elliott Middleton about 4 years ago in Historian & Client / API and SDK 0 Submitted

"aahIOSrvSvc" supports "Last" value from analog summary tags

Local summary tags are not exposed via "aahIOSrvSvc", but the corresponding “Live” query correctly returns the “Last” value from the summary tag. This came up via a support case from Aya Helmy Mohamed Mohamed
Elliott Middleton over 4 years ago in Historian & Client / Retrieval 0 Submitted

Change "wwOption" Returned for Auto-Summary

I want an indication of the data set used for my results set so I can better understand my data results. The "wwOption" column should indicate the type of data used (auto-summary vs. raw) instead of what was requested. (rows should indicate from w...
Jake Hawkes 4 months ago in Historian & Client / Retrieval 0 Submitted