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 PI Integrators
Categories AVEVA™ PI Integrator for Business Analytics
Created by Kelsey Bobeck
Created on Aug 16, 2022

RELATED IDEAS

Add offset options

I'd like the ability to configure offsets so that 1) my Views are consistently run for the same time intervals (important for statistical calculations) and 2) I can stagger the publishing of my Views to improve performance. If I were publishing a relative Continuous View with Start: *-10m to End: * and my goal publishing period were to be something like 08:40 to 08:50-- For the first, I envision this similar to interface scan class offsets. I'd like to schedule an offset so the View runs every ten minutes but must start at 00:00. This would help avoid accidentally clicking "Publish" and winding up with data that goes from 08:43 to 08:53 instead of the desired 08:40 to 08:50 and generally allow for more consistency for publishing times. For the second, I envision this like Asset Analytics offsets. So if I schedule an offset so the View runs every ten minutes but must start at 03:00 to stagger the publishing of Views, I could apply a relative timestamp of *-3m so I still get the desired 08:40 to 08:50 period.
  • ADMIN RESPONSE
    Aug 16, 2022
    Thanks for sharing your feedback on the PI Integrator. After review, we have decided to decline this idea for now, as our current engineering efforts are focused on cementing product stability and reliability, and we don't expect that we'll be able to prioritize this idea in a reasonable time period. You may have recently noticed that a number of ideas on our feedback site have been marked as “Declined”. While many of these ideas are great and valuable suggestions, we need to be more diligent about recognizing our development priorities and communicating back to those users when we realize we won't be able to act on something. We are currently working through a large effort to clean our feedback forums up and provide "Declined" statuses where we recognize that we won't be working on an idea in a reasonable timeframe. This effort spans across all of our products and will help us improve the transparency, usability, and sustainability of our feedback forums. If an idea that was declined is critical for your operations, please let us know by adding a comment on the idea.
  • Attach files
  • Jeff_Watkins
    Jun 23, 2026

    Kelsey described the issue perfectly. As we at Salt River Project use the Integrator for Business Analytics more and more to send sampled data to Snowflake for our Data Scientists and Data Analysts to use, in cases where they expect evenly distributed data that starts on the correct interval and timestamps with no straying due to the Integrator doing it's own thing, we vote to re-open this. I consider this to be, in fact, related to as you put it "product stability and reliability." If we can't expect the timestamp on the rows to be stable and reliable, then that is a fault of the product design.

    Reply