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

    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

    Enumerated value tag type

    Similar to a "discrete" with "message" strings, but with N integer states instead of just 0/1.
    Elliott Middleton almost 2 years ago in Historian & Client / Data Acquisition 0 Submitted

    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.
    Collin Heggerud almost 2 years ago in Enterprise SCADA Server / API / SDK / Developer Relations / Krunch and Data Manipulation / Omnicomm / Realtime API/SDK / Telemetry 0

    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.
    Jake Hawkes almost 2 years ago in Enterprise SCADA Server / API / SDK / Developer Relations / Cloud / Compile / Build  / Documentation / Interoperability / Other API/SDK / Security and DMZ 0 Reviewing

    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

    Reliable data collection from InTouch

    Support reliable data collection for applications with InTouch and Historian, such as with Redundant Tag Servers. This should parallel how Redundant Engines and Redundant DI Objects work with Historian in a System Platform solution. A lower priori...
    Elliott Middleton about 4 years ago in Historian & Client / InTouch 0 Submitted

    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

    HCAP Ping Utility

    A command line utility to test HCAP/HCAL connectivity.
    Elliott Middleton over 2 years ago in Historian & Client / Install and Upgrade / Maintenance and Management 0 Submitted

    More complete information about store-forward operations sending to Insight

    The customer has the following question regarding Aveva Insight. They use the Aveva Insight Publisher to publish the data from a vessel to the online Aveva Insight Historian using the store-and-forward functionality as the connection at sea is not...
    Elliott Middleton over 2 years ago in Historian & Client / Store and Forward 1 Unlikely to implement

    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 ...
    Jake Hawkes over 2 years ago in Enterprise SCADA Server / Architecture / Krunch and Data Manipulation / Protocols and Commlines / Realtime / Realtime API/SDK 0 Reviewing