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 30 of 859

    [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 6 months ago in Historian & Client / Data Acquisition 0 In Roadmap

    Expand Alarm generation

    Expand alarm generation. Add 10 user defined fields for each alarm so that the user can save alarm-related information
    Guest over 1 year ago in Application Server / Alarming 2

    AVEVA Historian official support for Proxmox VE

    I would like to propose the inclusion of Proxmox Virtual Environment (VE) as a supported hypervisor platform for AVEVA Historian. Proxmox VE is a robust, open-source virtualization solution that combines KVM and LXC with a powerful web interface a...
    Jeffrey Tambach 6 months ago in Historian & Client / Install and Upgrade 0 Submitted

    Increase Uptime by Retrieving License Statuses for Alarming in OMI/WIN-911 from SP

    The System Monitor has a rule category called "License Server Alerts". This allows the monitor to catch; "Alert on licenses that expire within X day(s)", for example. Additionally, through the rule category named "SMC Logger (Filter)" it is possib...
    Jørgen Myklebust about 1 year ago in Application Server / Alarming 2

    Custom alarm severities

    Our need is to have more than just 4 alarm severities / criticities. It will allow better alarm management with more than 4 colors, severity...
    Florent Michelfelder over 1 year ago in Application Server / Alarming 0

    Add an API to interact with AlarmManager from Script

    Sometimes it is desired to display Alarm Information on a graphic in a way that the standard Alarm Client doesn't lend itself to. It would be helpful to have a set of APIs to interact with the AlarmManager data to query and return current alarms, ...
    Jim MacDonald over 1 year ago in Application Server / Alarming 1

    [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 6 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 6 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 6 months ago in Historian & Client / Data Acquisition 3 In Roadmap

    Make Inhibit State/Alarm Limits persist across redeployment of objects.

    In all of our client's systems, we give them the ability to modify both the alarm limit/mode for analog alarms, and to inhibit tags that contain alarms (supervisors only). Problem is that if these tags are then redeployed without preserve runtime ...
    Guest 11 months ago in Application Server / Alarming 0