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 No Status
Product PI Interfaces
Categories PI Interface for UFL
Created by Heather Boehler
Created on Aug 17, 2022

RELATED IDEAS

Allow the UFL interface to delete PI tag data or provide some other supported automated method of deleting PI data from a collective.

There is no way to easily delete data in a time range if you want the changes to occur on both the primary and secondary data archive. It seems the UFL interface would be good to use to do this. You could provide it a tag name and time range and then buffer the delete to both collectives, so the data does not exist on either.
  • Attach files
  • ehoffman
    Reply
    |     Aug 17, 2022
    Since the collective prefers data to be sent through buffer subsystem in order for it to be written to all collective members what if buffer subsystem could also handle delete requests as well? I feel having buffer subsystem handle this would really help keep servers in sync when writing and deleting data to tags. We have a lot of manual entry process where we are always writing and deleting and or correcting data. It would be nice to have a OSI supported producted that could handle this vs creating custom VBA code or other methods to handle deleting data on collectives.
  • sjohnson
    Reply
    |     Aug 17, 2022
    There is definitely an opportunity to streamline deleting data in a collective environment. Currently, we have to jump through programming hoops to ensure data gets deleted from each server in the collective. It would be much preferred to have buffering or other technology handle deletes automatically, as it does for data sending.
  • Guest
    Reply
    |     Aug 17, 2022
    This would be nice to add on as an option to have handled by something in a programmatic fashion, especially if the buffer subsystem would allow for it.