AVEVA™ PI System™ Feedback Portal

Welcome to our 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, 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 and comments are visible to all other users.


This page is for feedback specifically for AVEVA PI System. For links to our other feedback portals, please see the tab RESOURCES below.

Add a new idea Subscribe
Status No status
Product PI Interfaces
Categories PI Interface for RDBMS
Created by Kenneth Reiss
Created on Jul 15, 2026

RELATED IDEAS

Tag groups should be based on both InstrumentTag and ExDesc fields

Assume the following use case. There is a database table which stores quality limits (Lower, Target, and Upper) for product quality attributes. These could include attributes like Sample Counts, Minor Defect Counts, Major Defect Counts, Critical Defect Counts, etc.

An elegant setup for RDBMS tags would be to have tag groups that return 3 columns of data (Lower, Target, Upper). If the same InstrumentTag field is used for multiple groups of tags with the quality code passed as a parameter in the ExDesc field, only the first group of tags receives data.

The interface should accept the same SQL file being specified for multiple tag groups, having the differentiating factor being the parameter passed via the ExDesc field. This would reduce the SQL file count, in my case, from nearly 30 to 1. This benefit grows exponentially when the same query can be used for multiple lines (2 lines means 60 SQL files are required, instead of 1 file with the produce line also being passed as a parameter).

  • Attach files