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

All ideas

    Ability to enforce a naming rule/validation

    The ability to require that objects be created to conform to a specific naming convention has been requested a couple of times. For example, meters need to follow a convention like M####-## where the # represent a number. The -## may follow a conv...
    Mike Demcoe about 2 years ago in Measurement Advisor / Administration / Installation 0

    First Classififer field

    Rio Tinto currently populates a custom field called 'First Classifier' that is populated when an operator enters cause,classification. Currently, this is achieved via action/code items dependent on RCEs generated by downtime reporting points. Rio ...
    Nina NICHOLLS about 4 years ago in Production Management (AMPLA MES) 2 Will not implement

    Leverage eDNA Historian as a Trend Data Storage Method in Citect

    The eDNA History service is a high performance, lightweight historian. This Historian database would be a great replacement for the older flat file storage mechanism used by Citect. The eDNA historian would provide lossless, highly compressed stor...
    Guest about 6 years ago in Plant SCADA / Alarms 0 Future Consideration

    Option to disable copying of comments on auto split

    https://dev.azure.com/AVEVA-VSTS/Issue%20Management%20System/_workitems/edit/1840711 Customer would like the option to configure if comments are copied when downtime records are split
    Nina NICHOLLS about 4 years ago in Production Management (AMPLA MES) 1 Will not implement

    KPI targets based on calendar loopkup should look at target for each sub period

    [Problem Summary]Merhnoosh have found an issue with calendar items used as a target for Metrics KPIs. When you have a calendar item bound to a period (ie daily target), and is used as a target for a metrics KPI, Ampla doesn’t calculate the correct...
    Nina NICHOLLS over 6 years ago in Production Management (AMPLA MES) 0 Planned

    Cluster field when adding a pen to the process analyst should be a pull-down menu

    When adding a pen to the process analyst, it would be great if the cluster field was a pull down with the available clusters listed from the project. With multi-cluster projects, this would help filter out the trend tag lists, as the end-user does...
    Guest over 6 years ago in Plant SCADA / Alarms 0 Future Consideration

    Allow customers to latch alarms

    Here is one problem customers are encountering with our alarming philosophy, where we replace the existing alarm with a new one with the current alarm state: Because the alarm for exceeding hi-hi isn’t latched, operators are missing that MAOP was ...
    Collin Heggerud over 6 years ago in Enterprise SCADA Server / Alarms / Control Room Management 0

    ADE permit to use symbols (),.-/

    On ADE, Address1 and Address2 fields in the Station table of ADE do not permit the use of symbols such as (),.-/, even though these characters can be part of legitimate addresses.
    Gerald Tseng about 2 years ago in Enterprise SCADA Server / ADE / PnT / MoC 0

    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 about 2 years ago in Enterprise SCADA Server / Krunch and Data Manipulation / Realtime API/SDK 0

    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 about 2 years ago in Enterprise SCADA Server / ADE / PnT / MoC / Protocols and Commlines / Telemetry 1 Will not implement