Analytics & Calculations

It would be useful to trigger event-triggered rollup analyses upon adding new children. Currently rollup analyses are only triggered when rollup attributes are updated (and not triggered when rollup attributes are added). This would be particularl...

Created on behalf of a customer: In order to use fewer attributes in an element, a customer hoped to output analysis results to an attribute with a dynamic PI Point data reference. Unfortunately, with the use of substitution parameters or with str...

PI System Explorer Management Tab should have better search criteria. For example, select specific elements in which to rerun an Analysis. Maybe use Element = something OR/AND Element = something else. Or search by element path.

Data can be flagged as questionable, which should mean the value may or may not be valid. Asset Analytics seems to be rejecting the value as Bad. The function instead should evaluate the result, but flagging the result as questionable as well.

A way to specify within the analyses if input values should be retrieved from the Data Archive or the PIAF Cache. Thereby preventing different results during real-time calculation and for instance backfills and decreasing the execution time of ana...

As an analysis user in a multi-national corporation with data from different time zones, I want to be able to designate a time zone per input when configuring analyses so that any relative time used in the analysis refers to the correct data.

I would like there to be a way to output the results of a rollup analysis to an Analysis Data Reference, so that I can view a trend without having to write to a PI point. Currently, there is no option to have a rollup analysis that does not write ...

It is difficult to find all the analyses from template to backfill/recalculate after making changes in Analysis Template.  Currently one has to navigate to the Management plug-in, do some sort of search/filter, then queue the analyses.  ...

When a failover occur or at service startup, ALL analysis configured for backfilling executes based on the last configured backfill/recalculate timerange. There is actually no feature to manually remove a configured backfill on a specific analysis.

Currently we have an analysis with the output timestamp set to be a variable within the analysis. If I map that variable to an output, it includes the subseconds, but the output time for the analysis is truncated to the second. The output time for...