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 21 of 776

Auto-sync objects from Data Services

Data services is the system of record and customer would like to see Advanced Analytics reflect the current state of objects (asset, streams, metadata) in Data Servies
Glenn Moffett 11 months ago in Advanced Analytics 0 Needs review

Support time series analysis in thread logic block

When doing time series analysis, right now there is no possiblity to let the thread look for a previous or next event (like in PI PE syntax). This makes time series analysis more challenging as one has to define a specific time range and look with...
Hans-Otto Weinhold 6 months ago in Advanced Analytics 0 Needs review

Better Preview possibilites of Thread reload

When creating a thread logic, right now there is no backfilling preview feature available which would allow to get a preview on an event creation logic within a logic block or when doing a calculation. It would be good to have a similar preview fe...
Hans-Otto Weinhold 6 months ago in Advanced Analytics 0 Needs review

Expose AVEVA Advanced Analytics outputs to Data Hub - e.g. recommendations

the key output from AAA is often not just the anomaly score. More interesting will be things like ideal running conditions, ideal model conditions.
Guest almost 2 years ago in Advanced Analytics 0 Needs review

Request for a new telemetered point type/table

SE PA WWW integrator has industry specific telemetered point type of Water Reservoir. Reservoirs are a type of telemetered point similar to an analog but with additional calculations for volume etc. Prior to binary release integrator modified the ...
Guest almost 4 years ago in Enterprise SCADA Server / Realtime API/SDK / Realtime Schema / Telemetry 1

Events duration column should be a timespan rather than a decimal

When viewing events in AVEVA Advanced Analytics, the duration column shows the event duration as a decimal value representing the number of hours the event was open. For example, a duration of 0.1 = 6 minutes. This is not immediately intuitive, an...
Guest about 1 year ago in Advanced Analytics 0 Needs review

Enhancements to use Device DataQuality: uncertain and error

We request enhancements to the ability for a protocol to indicate data quality to the krunch routines, as first requested in OASYS-518 (API for Protocols to indicate data to be krunched is questionable according to field device): https://aveva.aha...
Collin Heggerud over 1 year ago in Enterprise SCADA Server / Krunch and Data Manipulation / Realtime API/SDK 0

Enhance Omnicomm to make it easier for protocols to work with sub-remote status indicator.

An enhancement for protocol developers that is standard for all protocols.

Alternate timeseries hourly averaging algorithm

Enhancement request to either allow integrators to modify timeseries averaging algorithm or provide hooks to allow integrator to modify the operation. We implemented an alternative timeseries averaging algorithm on many installations. Prior to bin...
Guest almost 4 years ago in Enterprise SCADA Server / Historical / Realtime API/SDK 1

Y2K38 Preparedness

Big Picture User Experience The Year 2038 problem (also known as Y2038, or Y2K38, or the ‘Epochalypse’) is a time datatype bug involving the use a signed 32-bit integer to store of Unix time. The data type is only capable of representing integers ...