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 Declined
Product AVEVA™ PI Server
Categories Asset Framework (AF)
Created by Kenneth Barber
Created on Aug 19, 2022

RELATED IDEAS

Automatically update the ConfigString of attributes and attribute templates when renames occur

The ConfigString of attributes and attribute templates stores information such as references to PI Points, substitution parameters and formula parameters that refer to other attributes or attribute templates, and the source unit (abbreviation of the UOM of the referenced PI Point). Currently, the ConfigString will automatically update to reflect the renaming of a referenced PI Point, but not the renaming of attributes, attribute templates, or the source unit. Please consider automatically propagating all renames to the ConfigStrings that use them.
  • ADMIN RESPONSE
    Aug 19, 2022
    The configstring of a PI Point data reference contains the server ID, server name, point ID and point name. This enables the software to have a way to uniquely identify the configuration when the point name is changed since the ID's are unique. When a "Create or Update Data Reference" is performed on a PI Point DR, all substitution parameters are instantiated and "locked in". Storing all this additional information in every attribute, which there can be millions, would be detrimental to storage and memory need. As such we currently have no plans to implement this idea.
  • Attach files
  • psantosmoreno
    Reply
    |     Aug 19, 2022
    I completely agree. It is not very common to modify the name of an attribute, but if you do, it is needed to check if there is any Formula, String Builder, Table Lookup or even any PI Point Data Reference event frame attribute that uses it in order to modify there the name...
  • Kenneth Barber
    Reply
    |     Aug 19, 2022
    The renaming of attributes is much more common in PI systems whose Asset Framework hierarchy is not finished or is constantly being changed. For example, "Avg Flow" might later become "Average Flow", and that, in turn, might be renamed to "5-Minute Average Flow" if we want to add a "10-Minute Average Flow". You might also want to rename attributes for consistency across the PI Asset Framework, and the inconsistencies might not be discovered until the Asset Framework hierarchy is closer to completion. For example, "Run Status" might be called any of "Running Status" or "Running" or "On/Off Status".