Skip to Main Content
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.

Status No status
Product PI Integrators
Created by Guest
Created on Aug 16, 2022

Add ability to export stored Events for Event-based analysis, not only interpolated

Currently we can export PI data using a given interval, returning evenly-spaced rows of data. However, for some uses i need to have the original events stored in PI, not interpolated. E.g. i need to create a report that contains every value that the operator has entered (e.g. a catalyst dosing volume) in the duration of an EventFrame. For that i would need Archived values like i have in OLEDB Enterprise.
  • Attach files
  • Guest
    Reply
    |
    Aug 16, 2022
    I have been ok with the event snapshots and the interpolated values, but I could see this functionality needed soon...
  • Guest
    Reply
    |
    Aug 16, 2022
    Cool! It looks like that feedback on the feedback site is not automatically cross-posted here. That's why we see so many ideas popping up on PI Square.
  • Guest
    Reply
    |
    Aug 16, 2022
    In response to Roger Palmen, "Cool! It looks like that feedback on the..." You are one of the people I follow on here as you are always insightful. So, I saw this idea from a PI Square notification in my email and thought it was a great idea. Thanks for posting here!
  • Guest
    Reply
    |
    Aug 16, 2022
    This is one of the few items that keep me away from getting rid of OLEDB Enterprise for my reporting.
  • Guest
    Reply
    |
    Aug 16, 2022
    Have you tried using a key column instead of interpolated data? Or is the issue then that you would need multiple attributes to be keys, not just one as the Asset View currently allows?
  • Guest
    Reply
    |
    Aug 16, 2022
    We had a similar challenge recently... Initially I was going with one view for each attribute but I was able to tidy it up using an AF template to add a child element for each attribute to include in the view, and then building one view that includes all instances of that template. Your proposal would certainly be cleaner though so it has my vote!