Skip to Main Content
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.

Status No Status
Product PI Interfaces
Categories Batch Interfaces
Created by Guest
Created on Apr 8, 2024

Batch interfaces keeping merged child operation EventFrames open until the parent Operation EventFrame has been closed.

Currently for batch interfaces using the /MUP parameter, child operation event frames might be reopened and closed multiple times until the last operation event frame closes and the child event frame is closed for good.

For example with UnitProcedures, if a subsequent UnitProcedure has to be merged, the previously closed UnitProcedure will be opened, updated with the end time of the subsequent UnitProcedure and closed again.

It would be good to update the interface with an option where child operation EventFrames that should be merged can be kept open until the parent Operation EventFrame has been closed.

For the case of UnitProcedures, merging UnitProcedures would then only close if the parent Procedure EventFrame has been closed.

For the case of Operations, merging Operations would then only close if the parent UnitProcedure EventFrame has been closed.

And the same procedure should be followed for all other sub EventFrames.

  • Attach files