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 Data Archive
Created by Guest
Created on Aug 20, 2022

RELATED IDEAS

Confirm connection before writing to PI DA

No description provided
  • ADMIN RESPONSE
    Aug 20, 2022
    In this particular example, my understanding is that the user uninstalled PI SDK 2014 and downgraded to PI SDK 2012. As a result, the what was running application that continuously writes data to PI Data Archive lost its connection and had to perform a re-connection. Unfortunately we have no control over user action that removes the underlying data access mechanism (in this case, uninstalling PI SDK) and we also do not know that this has occurred. We need to avoid "verify" a connection before trying to write the data as this is an additional overhead of a remote procedure call. Repeated RPC's for the sole purpose of verifying connection status negatively affects performance of the entire system. My recommendation is that the user who is removing the underlying data access mechanism should be aware that this may affect other applications and perform the necessary steps to avoid disrupting the data flow. As an example, user can first stop the application, perform the removal/installation of software, then restarting the application.
  • Attach files
  • Guest
    Reply
    |     Aug 20, 2022
    Customer observed that while installing PI SDK, another application which was continously connected with PI Server, disconnected. So when application tried to write data through the PI Buffer, for the first time after the PI SDK installation, it failed. Customer propose an enhancement that verifies that the program is connected to the PI Server before trying to write the data. And if it is not connected, to allow the conecction, so it does not fail in the subsequent writing of data.