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

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

Telemetry Server - Enable OPC UA Server [IMS Number: 4073363]

Problem: We have a request from a third-party team to connect with our system via an OPC UA Server due to their security requirements. Currently, they are using Top Server to connect with substation alarms from site RTUs, but we are exploring an a...
Guest about 1 year ago in Device Integration 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 almost 5 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 almost 3 years ago in Historian & Client / Alarm & Event 2 Submitted

"Export/Import configuration to file"

It's a bit sad that in a serious product, in order to transfer the driver configuration from one computer to another, you have to look for configuration files somewhere and move them to the appropriate directory on the target computer. This is esp...
Piotr Polok over 1 year ago in Device Integration 1 Planned

MQTT drive support InTouch data Publisher to MQTT Broker

MQTT drive currently only supports system platform data publisher and does not support InTouch data publisher.
Shaobao Hu over 1 year ago in Device Integration 0 Planned

OPC A&E (and/or OPC UA A&C) to support Areas

We have alarms split into several Areas. When we connect using an OPC AE Client it only shows the correct custom properties for alarms with Area 0. Seems the integrated OPC A&E Server connects to the Alarm database with a user which only can v...
Guest over 4 years ago in Device Integration 1

Is there any plan for OI Server to support SIMATIC S7-200 SMART?

SIMATIC S7-200 SMART is a cost-effective small PLC product tailored by Siemens for Chinese customers, and the SIMATIC S7-200 SMART firmware version has been upgraded to V3.0 this year. https://w2.siemens.com.cn/smart/Product/S7
Shaobao Hu over 1 year ago in Device Integration 1

MQTT Last Will Message

As of current state, the publishers that do not use Sparkplug B and rely on vanilla JSON format do not get benefit of Data Quality change for tags where a Last Will Message has been received by the Subscriber. A simple fix to implement is the abil...
Lakshay Mundeja almost 2 years ago in Device Integration 0 Planned

Mitsubishi FX5U PLC driver for Plant SCADA

MELSECQ protocol can be used to communicate with FX5U, but the addressing system is different. MELSECQ expects Hexadecimal addressing while FX5U expects Octal addressing system.
Jiri Rysavik about 2 years ago in Device Integration 0