Skip to Main Content
AVEVA™ PI System™ 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, 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.

Status Future Consideration
Categories General
Created by Brian Rock
Created on Apr 12, 2023

Classic Mode for Adapters

One of the big issues we have with adapters (outside of the lack of write capability) is not having the same control over creating and editing tags that we have with PI interfaces. As we talked about the adapter automatically creates PI tags or uses a CSV file to map existing PI tags. This just isn’t feasible for us in our existing environments and even in a new build would be extremely difficult to maintain. It would be nice if there was a “classic mode” setting(s) that could be configured on the adapter where it would it would disable the automatic tag creation and allow the user to create and edit PI tags using the classic point class (instead of just using base class) attributes to get its source data information (instrumenttag, location1-6, etc.). This would allow us and other existing legacy PI users to be able to transition over to adapters much easier.

  • Attach files
  • sahilp
    Jun 30, 2023

    I like this idea. All point config are stored and engineered centrally, while the adapter has a cache for disconnected start-up which is also human-readable.

    Since the adapters only create tags which are in the Data Selection, one way to hack this function in the short term is to first create all your tags (even as classic tags) in PIBuilder and pretend you are working with an OPC DA interface. You set:-

    • tagname

    • instrument tag (matching opcua nodeid)

    • excdev

    And then you can massage this into a csv with the equivalent columns needed for the data selection. csv to json is built in to powershell, so then you are done.

    To be clear, this is a total hack. It would be great if AVEVA can implement the request in the future.

    One way to integrate the function in the adapter would be to use the POINTSOURCE as we are used to and either periodically, or on demand the adapter can query the DA in the usual way and then transform the point config into the correct JSON which is then absorbed into the adapter config on the fly.


    • adapters should be cross-platform, while SDK and API are windows only, so querying the PIDA directly would not be doable

    • querying the PIDA directly requires additional firewall port to open

    • GetPointsBySearch would be a vaild way to get the points from a WebAPI, but the Omf endpoint may have a minimal install which excludes the full webapi.

    • Not sure how well this feature would play with AVEVA Data Hub

  • Admin
    Jiyeon Hwang
    May 15, 2023

    Thank you for your input on this topic. I will mark this for future consideration as we look at ways to help customers with migrating from Interfaces and Connectors to Adapters. Would you be able to share which Interface(s) you are currently using so that we can make note of them?

    3 replies