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 Declined
Product AVEVA™ PI Server
Categories Data Archive
Created by Guest
Created on Aug 20, 2022

RELATED IDEAS

Store multiple events at the same timestamp

I have a particular application for storing partial discharge events into the PI Server.  Many of the events are at the same timestamp, which result in multiple events at the same time.
  • ADMIN RESPONSE
    Aug 20, 2022
    We are declining this item as we don't feel it's the right fit with our overall product strategy. Thank you for your feedback, and please continue sharing your thoughts on how we can better serve you.
  • Attach files
  • Guest
    Reply
    |     Aug 20, 2022
    I am familiar with the reason for this request. The customer does monitoring of the power grid, such as high voltage insulation condition monitoring. They store partial discharge events, where 1 or more discharge event (or burst) can be detected and assigned a single timestamp. We suggested the following workaround. If a burst of data came in at time X, the data would be stored in PI at X, X+1s, X+2s,X+3s,... and so on up to a max of about 20 or so values. This might work because these bursts of data occur approximately every 500 seconds or so, which means that a grouping of 20 events could be identified as coming from a single burst of events. While this workaround might affect the way that a trend might appear, the customer is very interested to display the data in XY plots and this workaround might not affect the XY plot in the least. Of course, the XY plot must be done using values from 2 or more different data streams. They have approximately 9 related data streams in each burst.