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

When converting an element to a template, suggest substitution parameters based on the ConfigString

Currently, if the ConfigString of an attribute looks like this: \\ServerName\TagName;UOM=uom then if you right-click on the element and go to Convert → Convert To Template, the Substituted column will suggest this: \\ServerName\%Element%.%Attribute%.%ID%;UOM=uom regardless of whether TagName is in the format %Element%.%Attribute%.%ID%. Instead, consider suggesting substitution parameters based on the ConfigString. For example, if %Server% evaluates to "ServerName" and %Attribute% evaluates to "TagName", then make the following suggestion: \\%Server%\%Attribute%;UOM=uom
  • ADMIN RESPONSE
    Aug 19, 2022
    The current behavior with element template with PI Point attributes is to have a default substitution parameter as you described regardless of whether you're creating the attribute from scratch or if you change an element to a template. Your suggestion of changing this default only when changing an element to a template assumes that the PI Point name can be replaced with a %attribute% substitution parameter. We have no data to support whether this is an improvement or not and it would be a change in behavior only for a specific use case. The default %element%.%attribute% maybe suitable if you have an element name for your asset and an attribute name for your measurement. So for example, if you have an element=pump and an attribute=flow, the current default would result in a PI Point name = pump.flow, if you were to create the PI Point from the element template. We currently do not have enough data to support a change in this behavior.
  • Attach files
  • Kenneth Barber
    Reply
    |     Aug 19, 2022
    Of course, OSIsoft will have to decide what to do when there are conflicts. For example, if the tag name is ABC, the element name is AB, and the attribute name is BC, do we use A%Attribute%, %Element%C, or nothing? Also, I wouldn't expect such a feature to consider substitution parameters involving ancestors, such as %..\..\Element%, since there would be too many cases to check and these substitution parameters are uncommonly used anyways.