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.

Status In Roadmap
Portfolio area Historian & Client
Products Data Acquisition
Created by Marcell Marjee
Created on Oct 15, 2025

[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 done by choice. The connector currently needs very little configuration to log SCADA data to Historian. When the Connector service is started or recovered from disconnection, it will automatically discover tags from SCADA and add/modify the corresponding Historian tags as required. The flip side is that it removes customisation possibility from the users.

In terms of detecting whether the tag configuration are up-to-date, it is possible for the Connector to periodically call ServerGetProperty() Cicode function via CTAPI to compare the date time of the RDB file loaded on the SCADA server against what is used by the Connector.

  • Attach files