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

Get Custom Property Reference by script

Allow retrieving a reference from a custom property to reuse it in a graphic. Example: indicate to the user the attribute used in a display and be able to find it in Historian.
Hugues Alexis over 1 year ago in Application Server / Scripting 0

Need a replacement for PrintScreen() function that works in OMI

OMI is missing a way to programmatically print to printer. Like the PrintScreen function in InTouch. Should be able to print the whole application or only part of it, i.e. a popup window.Ref: IMS#2206203
Øyvind Hansen about 1 year ago in Application Server / Scripting 1

Add keyword to exit remaining script execution.

It would be great if the scripting for both objects and graphics allowed us to exit early so we can avoid nested control flow statements. It would make scripts easier to read and work with. Maybe some keyword like exit script, similar to exit for/...
Timothy Nunnink about 1 year ago in Application Server / Scripting 0

Request for doc on how to configure Alarm mapping on AVEVA Historian Plant SCADA Connector documentation.

ADO Work Item #4782855 — [HELP] Alarm mapping on AVEVA Historian Plant SCADA Connector documentation. https://dev.azure.com/AVEVA-VSTS/_workitems/edit/4782855 DESCRIPTION We don’t have any information documented about the Alarm mapping details be...
Jake Hawkes 6 months ago in Historian & Client 0 In Roadmap

[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 about 1 year 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 about 1 year 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 about 1 year 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 2 years ago in Historian & Client / Excel add-in 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 8 months ago in Historian & Client / Alarm & Event / Security and Users 0 In Development

[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