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
Categories Data Archive
Created by Kenneth Barber
Created on Sep 20, 2026

Be able to configure the time range (the "shifting period") of future archives

Currently, each future archive corresponds to a single calendar month (source: https://docs.aveva.com/bundle/pi-server-s-da-admin/page/1019087.html). Please allow this time range to be configured, perhaps through a tuning parameter or through a setting in a file. For example, we might want the future archives to shift every year or every day. Examples of cases where this would be useful:

  • Currently, if you have very little future data, then you end up having an excessive number of future archives, and you must do extra work if you want to combine these archives. In this case, it would be good to configure a longer period of time for each future archive.

  • Currently, if you have a lot of future data, then your future archives will be huge, and so it might help if you could create more future archives that each cover a smaller time range.

  • If you have a data retention policy that applies to all future data, then it would help to have more future archives that cover a smaller time range so that you can delete entire archives and obey the retention policy as closely as possible without complicating the setup. If the archive files cover a long period of time (i.e. 1 month), then you need to choose between keeping some data past its retention period or deleting some future data prematurely when you rely only on deleting entire archive files, or you need to implement 2 different scheduled scripts: one that deletes the data within the archive files to enforce the retention policy, and another that unregisters and deletes the archive files whose time ranges are past the retention period.

  • Attach files