As an administrator, I need to ability to configure the life span of my PI data, so that data are kept or deleted accordingly. For example, data that should be deleted based on corporate mandates and data that should be kept forever are handled accordingly.
Note: This was previously Enhancement 25774OSI8.
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.