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 No status
Product PI Connectors
Categories General
Created by Allison Muraski
Created on Aug 20, 2022

RELATED IDEAS

Enable an integrity scan or compmax behavior for PI Connector for e-terrahabitat

The Connector only sends values that have changed. Not having the option to perform an integrity scan or functionality similar to compmax causes confusion to users looking at data in PI Vision. Some points can go for extended periods of time without changing. In those cases trends can be misleading by interpolating between very old values that have not changed with newly updated values.
  • Attach files
  • Ryan Sullivan
    Reply
    |     Aug 20, 2022
    Use Case: A Breaker trips and the Megawatts drop to 0. The breaker is restored 2 weeks later and the Megawatt value starts reporting 5. Interpolation (trends & sampled data) values between the 0 and the 5 for that 2 week duration will report back incorrect & misleading values since no other values/timestamps were stored between the 0 and the 5 since the connector only sends values that have changed.
  • Kenneth Barber
    Reply
    |     Aug 20, 2022
    "compmax" is not the best wording. I think that you mean compression (in the exception & compression sense), which solved this issue by saving both the event with the changed value and the previous event.