Skip to Main Content
AVEVA Product Feedback


Status No Status
Created by Guest
Created on Aug 20, 2022

Trigger automatic recalculation for snapshot changed values

As for now, automatic recalculation is not triggered by changes on snapshot (KB01790), which means auto-recalculation does not work with snapshots values. The idea of it doing otherwise is to help users that mistakenly added a wrong new event to a manual data entry tag to fix it and all related analyses.
  • Attach files
  • Guest
    Reply
    |
    Aug 20, 2022
    Customer use case: The customer explained 2 types of analyses she has a desire for the automatic recalculation feature: 1.) An analysis where the input attributes are PI Point data references that are updated via manual input. These PI points are manually updated by a non-PI application. This type of analysis is configured to trigger naturally based on one of the input attributes. 2.) An analysis where the input attributes are PI point data references that are updated via a PI interface (exact interface was not documented). This type of analysis is configured to trigger periodically every 24 hours. With both of these types, the customer has scenarios where the input attributes were updated with events that have an incorrect value. To resolve the situation they need to send a new event to the input tag that uses the same timestamp, but with a different value. When this new event is sent, the customer wants the corresponding analysis to trigger a recalculation automatically. Currently, customers have to manually initiate a backfill when they find out the input tags had to be updated. This customer anticipated using the automatic recalculation feature that is now a part of the PI Analysis Service product would meet their need to have the recalculation automatically triggered, however currently that is not the case. This customer still has to manually backfill analyses when they run into either of the scenarios above.
  • Guest
    Reply
    |
    Aug 20, 2022
    This automatic recalculation is critical for us since is a mandatory step for our ACE-AF calculations migration. We appreciate your effort in helping us with this issue!. Juan Gutiérrez OT Manager at Ence