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

Add a Confirmed Write methods

All methods exposed through AF SDK and other Developer Technologies are "fire and forget". Please add methods, at least for time series data, which return when the data has been processed. A write operation that returns when data has been processed allows to postpone dependent operations until the acknowledgement is received. A client application using a Confirmed Write needs to handle failures and a Confirmed Write requires an active communication channel. For this reason the implementation should be un-buffered. Offer Confirmed Write methods through AF SDK and later with other dependent Developer Technologies.
  • ADMIN RESPONSE
    Aug 20, 2022
    Thank you very much for sharing your feedback on the PI Server. After further evaluation, we have decided to decline this item, as we are not planning on implementing it in the near future due to other high priority items across the PI System. Thank you for your feedback, and know that we are listening and reviewing every item that gets submitted!
  • Attach files
  • Guest
    Reply
    |     Aug 20, 2022
    I was asked to share a use case for this request. A custom AF SDK application is writing time series data to PI Points (Attributes with PI Point DR) and communicating to a 2nd application that the writes are complete. This is done by creating Event Frames. The second application, created by another party, is watching out for new Event Frames and triggers reading time series data for further processing. Customer and partner designing this handshake were not aware that Event Frames are created in the PIFD database which is a totally different data container than the PI Data Archive, receiving the time series data. The second application was experiencing issues because the time series data was not completely processed, when the reads were performed. Confirmed writes would have been a useful option in this case but could also turn out being useful in other cases.