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 Declined
Product AVEVA™ PI Server
Categories Asset Framework (AF)
Created by Guest
Created on Aug 19, 2022

RELATED IDEAS

AF XML Export and Import Should Be Version Aware

XML export and import should get the possibility to export and import all or any versions of an element, not only the actual one.
  • ADMIN RESPONSE
    Aug 19, 2022
    Thank you very much for sharing your feedback on the PI Server. After further evaluation, we have decided to decline this item, as we are not planning on implementing it in the near future due to other high priority items across the PI System. Thank you for your feedback, and know that we are listening and reviewing every item that gets submitted!
  • Attach files
  • Guest
    Reply
    |     Aug 19, 2022
    Import/export never takes versions into account. It sounds like you have a use case for using versions, and it would be good to know what it is. Almost none of our modern client products actually take versioning into account when displaying data, so our understanding of why people need/want it is somewhat limited. This is one of those features that is often argued as a bug by some and a feature by others. Some customers have said that they use import/export to "delete" old versions, while others want it preserved.
  • Guest
    Reply
    |     Aug 19, 2022
    We often have to build assets and analytics that have to to be recalculated (backfilled) for several years. There are often config or tag changes in this period that we handle with versions. Most time we first create sample assets in a test database. If they work fine we move them to a productive database with xml export and import. Unfortunately we now can only transfer the latest version. I think xml export/import should only optionally use all or specific versions. Default could still be the latest version.
  • Guest
    Reply
    |     Aug 19, 2022
    I also need this feature
  • Guest
    Reply
    |     Aug 19, 2022
    We need to have versioning for accurate reporting. One of the problems versioning solves quite elegantly is when a site is off-line for a long period of time (say 2-6 months) for maintenance. Instead of using the primary sensor, back up sensors can be used for reporting in their place through versioning. Once the primary sensor is back in action, versioning can let us, easily swap it back in. Touching a production server without testing is a recipe for disaster (and in the devops world we are moving to, not even allowed). Not being able to configure a version in a test environment and then be able to deploy that change to the production environment exactly how you configured it in the first place is a serious problem. Being able to deploy the full version of an asset would be very useful. Being able to deploy a subset of the version history (cherry pick?) could be useful as well, but understandably be more difficult to implement.
  • Andy
    Reply
    |     Aug 19, 2022
    We also need this feature