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

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

[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

More interval/row count options in the Excel add-in

Already available in the function, but not exposed in the UX "wizard"
Guest over 1 year ago in Historian & Client / Excel add-in 0 Submitted

Graphical Meter Summary screen & prediction - color codes

For example, if the meter has "System Predictions" enabled, the current meter reading is usually "System Estimate" data. Baseline colour for estimate is BLUE. The expectation is that, the current Gas Day's cell within the Graphical Meter Summary g...
Leslie Leung 6 months ago in Measurement Advisor / Analytics 0

[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 7 months ago in Historian & Client / PlantSCADA 1 Submitted

HC - Trend: add the capability to limit the number of pens in a chart

As <actor> I want to be able to limit the number of pens a user can add in a chart so that it does not become too cluttered and does not increase the CPU/Memory load on the system.
Guest 7 months ago in Historian & Client / Trend 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 about 2 years ago in Historian & Client / Alarm & Event 2 Submitted