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 Connectors
Categories General
Created by Clint Ramsey
Created on Aug 20, 2022

RELATED IDEAS

Allow the AF root element name to be configurable

The root element in AF is determined by the Connector code.  Allow the name of the root element to be specified by the user.
  • Attach files
  • Guest
    Reply
    |     Aug 20, 2022
    Also allow for there to be an option for no root element. For example, in the UFL connector there is a root element "UFL" even if the "Root PI Asset Path" is not specified.
  • Guest
    Reply
    |     Aug 20, 2022
    Always placing the AF hierarchy under the /UFL element limits the usefulness of the connector. I may want to associate my ufl elements (thinking hundreds to thousands) to parent elements to facilitate collections, rollups, child-parent relationships. Assuming weak references to the UFL build AF structure is a solution is not manageable and does not enable these use cases. Also allow for the UFL to build AF structure based off of user named templates, not UFL.. The prefix is nice that it associates a source of the data, but why? Let the end-user configure this, or have option to specify an optional prefix. As built this is too rigid for every use case.
  • Andy
    Reply
    |     Aug 20, 2022
    There is a much problematic issue with how the PI Connector works and is related to the fact that cannot reference existing AF elements that it has not created. This means PI Connector DOES NOT COMPLY to any existing Data Governance in place in you AF Asset Hierarchy, as it will create it's own Element Templates and Event Frame Templates under it's own hierarchy. This is a design issue, it must be possible to pass reference elements and templates that already exist.
  • maryjo.chelmins
    Reply
    |     Aug 20, 2022
    I encountered this the first time I used a Connector, and it made me which I had stuck with the Interface option for UFL instead. Please make this enhancement a reality.