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

    [PlantSCADA] Ability to Historize other Data Type (like INT/REAL)

    4.1 Be able to Historize other Data Type (like INT/REAL) of tag variables , not just the Digital/String Data Types Looks like this is done by choice or some other reasons, e.g. name clashes. The Connector code currently explicitly filters out vari...
    Marcell Marjee 10 months ago in Historian & Client / Data Acquisition 0 In Roadmap

    Ability to store the output of Expressions into a new tag

    Configure a new tag with its source being the output of an expression. Point would update when any of the source points updated.
    Jake Hawkes 3 months ago in Historian & Client / Data Acquisition / Expressions 0 Submitted

    Alarm Event Type is Application Write for InTouch tags, but is expecting it to be User Write

    User has standalone intouch application with primary alarm provider and logger node and RDS node. When looking at events specifically (such as changing alarm setpoint) the operator logged in does not reflect properly in alarm/event viewer. For exa...
    Jake Hawkes 4 months ago in Historian & Client / Alarm & Event / Security and Users 0 In Development

    [PlantSCADA] Better support for tag config changes on PlantSCADA end

    4.3 Changes to Plant SCADA configuration Where there are changes from the PlantSCADA side, a restart of the connector is required however there are many cases of where the users forget to do this. A reminder message may help. Looks like this is do...
    Marcell Marjee 10 months ago in Historian & Client / Data Acquisition 0 In Roadmap

    [PlantSCADA] Fault tolerance to errors on the PlantSCADA side

    2.0 Fault Tolerance of the connector to SCADA misconfiguration If there is a misconfiguration on the SCADA side, for example after the system is running, then it can lead to the ctapi connection being dropped and no logs for all tags, and not just...
    Marcell Marjee 10 months ago in Historian & Client / Data Acquisition 1 In Roadmap

    [PlantSCADA] Make connector activity visible in PlantSCADA UI

    The main issue is that if you stop Plant SCADA while a backfilling operation is ongoing but the Connector is still working, then we get the issue that data is written on wrong blocks into historian. To successfully complete the backfill operation,...
    Mats-Peter Cansund 10 months ago in Historian & Client / Data Acquisition 3 In Roadmap

    [PlantSCADA] Support Redundancy in Connector

    Objective is reliable data acquisition, even when Citect nodes failover (as with redundant AppEngine). Ideally, this would also include support for "partner" Historians, but that can be treated separately. Requires: - [Citect Utilities] Support re...
    Marcell Marjee 11 months ago in Historian & Client / PlantSCADA 1 Submitted

    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 over 4 years ago in Historian & Client / InTouch 0 Submitted

    "Single Record" view of alarms

    Combine ".Set", ".Clear" and ".Ack" records into a single record for simpler reporting. Possible today with SQL, but complicated. Better to have a targeted "extension table" for this use case. Also needed for REST Would be useful for the current A...
    Elliott Middleton over 2 years ago in Historian & Client / Alarm & Event 2 Submitted

    Enumerated value tag type

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