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.
This enhancement would be particularly valuable for PI points receiving data from OPC AE (Alarms & Events). These tags typically store textual event information that cannot be effectively trended or analysed within the PI System itself and are often forwarded to downstream systems for reporting, analytics, or long-term processing. Applying shorter retention periods to this type of data would help reduce unnecessary storage consumption while retaining the information for the period it is operationally useful. As text-based event data generally requires significantly more storage than numeric time-series data, the ability to define different retention policies could result in substantial storage savings and improved overall PI Data Archive management.
records retention policies are useful to have. to retain long term data differently than transient data, or to store AF Analytic ouput differently than DCS data
Another advantage to archive sets would be the ability to have an archive set for your continous data from a control system where the archives are set to read only after a month but then have an archive set for your data that comes from analytics set for longer. this would allow for your bigger archive sets to be read only while allowing you the ability to backfill older analytical data on an archive that is older.
A way to do this would be the ability to have different archive sets that you could assign a tag to. You could have 1 archive set rolled over every year and another one that never did.