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.

Add a new idea Subscribe
Status No Status
Product AVEVA™ PI System Access (PSA)
Categories General
Created by GaryYegiazaryan
Created on Jan 11, 2024

RELATED IDEAS

Align all developer tools to have access to the same data

The different PI developer tools do not have the ability to retrieve the same data. For example, a user cannot retrieve PI connection statistics from the AFSDK. That is only accessible via PowerShell (Get-PIConnectionStatistics).

In C# or PI WebAPI I should be able to retrieve the same data that PowerShell can. This allows me to not be locked into only using PowerShell.

  • Attach files
  • Asle Frantzen
    Reply
    |     Mar 1, 2024

    We have a product that monitors PI Points to record versions and who changed the configuration. This is still using PI SDK, since there's no access to the PI Server Message Log using PI AF SDK.

    Would love to get access to this using a more modern method!

  • Tyler Engelhardt
    Reply
    |     Jan 11, 2024

    I agree, developer tools should be able to extract the same data. But I think this is mostly in part due to a design issue.

    AVEVA needs to adopt an API first approach to the developer experience. In that scenario, it will be easier to develop SDKs for various languages and a CLI, since they'd all use the same API as the backend. Most platforms have been using this approach for years now.