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

Retrieval

Showing 4 of 774

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 almost 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 about 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 3 months ago in Historian & Client / Retrieval 0 Submitted