AVEVA™ PI System™ Feedback Portal

Welcome to our new 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 Completed
Product AVEVA™ PI Server
Categories Data Archive
Created by Guest
Created on Aug 20, 2022

RELATED IDEAS

Add flag for offline archive reprocessing to honor archived digital state values

If a tag is edited to use a new digital state set, this set will be used for all future data even though the previous state set is still used for historical data.  If a historical archive (prior to editing the digital state set used by the point) is reprocessed, the events within the archive will be coerced to the new digital state set.  This can be very confusing if the archived data is intended to be the old digital state set.
  • ADMIN RESPONSE
    Aug 20, 2022
    This is now possible with the PI Server 2018 SP3 Patch 3 release.
  • Attach files
  • Guest
    Reply
    |     Aug 20, 2022
    This makes manageability very difficult whenever a customer wants to merge or split a large enterprise PI system. My customer wanted to split their centralized PI system into individual business unit systems due to many years of growth which led to decreasing performance. The issue is that reprocessing an archive honors the digital state set in the header of the archive file and doesn't honor any digital state set changes made along the way. The only way to avoid this is to only 'append' to the original digital state set and avoid any string replacements for a given integer value (eg - 1 = OPEN changed to 1 = CLOSED). This is a major issue as customers such as utilities go through their backend SCADA system upgrades which occur every 10 years or so. Often the SCADA vendor dictates these digital state sets which can vary wildly from previous sets.