All ideas

In the DA collective there is a function called "Failback". The function is described as: << When the collective member which the client application was connected to becomes unavailable, the client connection starts monitoring when the memb...

The PrevVal function currently requires two parameters: an attribute and a timestamp. However, I find that 90% of the time that I use this function I am looking for the previous value with respect to the current time ('*'). The error which analyti...

Like Mathlab, Octave is a powerful free calculus software which is used commonly in machine learning. I think it could be a good idea to integrate this software with PI Analytics just for these purpouses and others like just make advance calculati...

As an analysis user, interested in implementing event detection for micro-grid and PMU deployments, given the model parameters, I would like to be able to compute ARMA (Auto Regressions Moving Average) model, so that I can easily identify events t...

AF templates only allow extensions for attributes. I want to be able to do element level adjustment for analyses.

Customer would like to have Brace/Parenthesis matching and adding comments (e.g. //) functions in Analysis Expression like programming languages.

Currently, users can select any of the event frame templates available on an AF database as the template for event-frames generated by an analysis/analysis template. There is no real way of restricting  which templates can be used, since EF T...

As an administrator of my analyses, I would like to be able to get better visibility into my Error details when many of my analyses are in error.

Because some functions in PI AF Analytics require an attribute reference (instead of a tag number or tag value), it would be useful to be able to retrieve an attribute reference using a String variable. This functionality would allow dependent att...

If an analysis with multiple trigger attributes is triggerred, it is difficult to assess which attribute produced the trigger. Hasvaluechanged has it's limitations, and comparing PrevEvent is also cumbersome. Instead of only receiving a timestamp...