AVEVA™ PI System™ Feedback Portal

Welcome to our 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 Planned
Product PI Interfaces
Categories Batch Interfaces
Created by Bethany Jewett
Created on Mar 21, 2024

RELATED IDEAS

PI EMDVB Interface should not use the STARTUP.dat to determine recovery start time when configured in Failover and running in RealTime mode.

Currently when the PI Interface for Emerson DeltaV Batch (EMDVB) is configured for failover and running in RealTime mode, the interface will use a recovery start time (RST) based on the last time the interface was active.

This results in the interface performing history recovery for an excessive time interval in the scenario where one of the failover instances is idle for a long period of time and then becomes active because of a failover.

Instead, the interface should look at the failover tag to determine when either interface instance was last active and adjust the RST accordingly.

  • Attach files
  • Admin
    Ellery Murdock
    Reply
    |     Oct 8, 2024

    This is planned for a Jan 2025 release. As this fix is in the batch framework, all batch interfaces released after Jan 2025 will natively include this enhancement.

    As suggested, the secondary interface will use the failover tag to determine the history recovery timeline.

  • jeff_denz
    Reply
    |     Oct 2, 2024

    While I think this is obvious based on the explanation already given, an example of how this is problematic is during monthly patching. If the goal is to be as seamless as possible during patching activities, we do not wish to attempt recovery of 1 month worth of batch data during every patch. This can take hours in our case. Because of this, we have had to set the backup services to manual, only to be used in extreme circumstances. Therefore, the redundancy is nearly useless to us until this issue resolved. Please give serious consideration to updating this behavior.


    Hours vs seconds of recovery time during failovers is the difference.