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

Allow protocol specific extensibility of dnlist ADE Form

The dnlist ADE form has protocol specifics built in for BSAP and Fisher ROC but does not allow any extensibility so it is difficult to add "Download by List" functionality to a new protocol (such as DNP3).
Collin Heggerud over 1 year ago in Enterprise SCADA Server / ADE / PnT / MoC / Protocols and Commlines / Telemetry 1 Will not implement

Testing as a Service

Multiple customers have offered to share their test scripts with us to improve our ability to test usage that better matches customer environments.

Collect doesn't collect current real-time value at top of hour

Customer Requirement Our customers require the ability to maintain complete Timeseries historical trends (collect samples), including timestamped samples polled after a PLC communication loss (outage could be for several hours/days). The customer ...
Guest almost 4 years ago in Enterprise SCADA Server / Historical / Realtime 2 Waiting for information

Expansion of point description field string length

SE PA WWW previously modified database schema and structure now with binary release modifications tot he database structure are limited. Support for modifying existing types including changing string length is not supported. SE PA WWW typically...
Guest almost 4 years ago in Enterprise SCADA Server / Realtime Schema 3 Will not implement

Support extensions in ISM with > 1024 characters

Can we add an item onto the backlog to support extensions in ISM with > 1024 characters. Since we are using ISM for recording certain configuration, an example situation is a JSON template which may easily be larger than this, which will make a...
Andy Davidson almost 4 years ago in Information Standards Manager 0

NMC should not log confusing messages if the ADLDS Cross Domain Replication sender is also a receiver from another ADLDS realm

The current 2023 system designs being provided to customers include an es/deployment system with it's own ADLDS realm. AOR area/group changes are made there first and it is the global table owner for its realm. The primary production system is set...
Hugh Arai almost 2 years ago in Enterprise SCADA Server / Administration / Installation / Replication 0 Reviewing

GroupArea in the area table only contains the first 20 groups

Do we actually have a limit of 20 groups per area? Some testing has shown that one can add more then 20 groups into an area. The GroupAreaJoin table populates all of them correctly however the "group[0-19].name” array-field in the area table only ...
Bradley Tomanik over 2 years ago in Enterprise SCADA Server / Administration / Installation / Realtime 1 Already exists

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 ...

Tag Labels

From Jon Tomkins. Following up on an old enhancement request from the Aussies on ISM. It may not be seen as high priority but wanted to flag a pain point for implementation – when we are attempting configuration management of compositions, as toda...
Andy Davidson almost 3 years ago in Information Standards Manager 0

Required Version label is confusing

From Jon Tonkins: If a version is set to something like 1.0.2.*, understand this actually means ‘use latest version’. This reads confusingly as it looks like it should only be 1.0.2.something but can then be 1.0.3, etc.
Andy Davidson almost 3 years ago in Information Standards Manager 0