Analytics & Calculations

It'd be nice to dynamically set the Event Frame category within Asset Analytics. Preferably have this as an option for each 'Start Trigger'. This would be advantageous since 'category' is on the top level object and thus much more efficient to q...

While it is possible to manually calculate Process Capability Statistics, such as Cpk and Ppk, using AF Asset Analytics, it would be much more convenient to have a built in function to calculate these values, specifically in relation to the SQC We...

When working with arrays in PI Analysis it would be nice to be able to compare a current value against the previous or next value. I have figured out that I can use PrevVal in the MapData function, however it appears that this goes back to data ar...

Currently you can only run a single PI Analytics instance at a time. We have two VMs running PI Analytics in a failover situation, but this means that one of the VMs is sitting idle 99% of the time. We are starting to hit the limits of scaling w...

Our process is writing an array of strings into an AF attribute of the same type. This AF attribute may receive information of different size (index) in time. We need to extract all the information contained in the string array (all the items) an...

The TriggeredOn() function would return true if the inserted attribute was the reason for the expression analysis to trigger/evaluate. I have multiple attributes in the same analysis but only want each line to have an output when its corresponding...

I'd like better diagnostic information around why event frames are not create by AF Analytics so that my solutions are of high quality and my users have confidence in their EF data.

It should be possible to map variables in event frame analysis to element attributes.

For our technical account we have to do recalulations on a daily basis, because of late arriving data. Auto-recalculation is not an option, because late arriving data that arrives after we have published the results, should not(!) be respected any...

We had a few issues with key-users creating inefficient AF Analysis and starting a backfill over a longer time period. This resulted in a CPU load of 100% (caused by the PIRecalculationprocessor). The whole PI System got not responsive incl. PI Sy...