Allow Calculation Wait Time to be set at the analysis rather than server level
The CalculationWaitTimeInSeconds applies to the entire server but different calculations will have differing requirements of promptness and accuracy (and accuracy can be mitigated with the Recalculation option)
Nathan Anderson
Apr 21, 2026
Use case: EF generating analytics, so no auto recalculation is available.
Analytics with multiple triggers must account for the latency for every data stream - otherwise EF's can and will end witn incorrect end times. If for example there are two tags of 60 second scan classes, we must add the two latency's together (in this case 2 minutes) then set the tuning parameter for the entire analytics engine CalculationWaitTimeInSeconds to be greater. This not feasible for built out systems, my system would require a 10 minute setting.
allowing a CalculationWaitTimeInSeconds setting per analytic or a collection delay timer per analytic would allow PI to properly collect all inputs.
My customer has a similar need. For what it's worth, this request appears to be similar to this one: https://feedback.osisoft.com/forums/555148-pi-server/suggestions/37048084-delayed-triggers-for-analytics
Use case: EF generating analytics, so no auto recalculation is available.
Analytics with multiple triggers must account for the latency for every data stream - otherwise EF's can and will end witn incorrect end times. If for example there are two tags of 60 second scan classes, we must add the two latency's together (in this case 2 minutes) then set the tuning parameter for the entire analytics engine CalculationWaitTimeInSeconds to be greater. This not feasible for built out systems, my system would require a 10 minute setting.
allowing a CalculationWaitTimeInSeconds setting per analytic or a collection delay timer per analytic would allow PI to properly collect all inputs.