Ideas

Substitution variables are only supported in datareferences. I want to use these directly in Analytics expressions. Now i need to create a attribute to resolve the substitution variable (formula, stringbuilder, etc.), and use that in my analysis....

Improve version control mechanism to consider also PI AF Analysis & Notifications Elements: Background: When adding or removing an attribute to an Element in PI AF, the element's revision number is incremented (as expected) which makes the re...

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...

New functions are needed for most problems in our fileds process and quality: * countif (count with conditions over specified horizon) * for loop (even it might be hard to implementate)

As a PI server Administrator I would like to have a way to decide the PI DA collective member Analysis server should connect. This will allow us to manage better the load on PI DA

Currently, BadVal() in Asset Analytics can handle situations like BadVal(1/0) without throwing a divide by zero error, but the badval() function in the Formula DR cannot. The request is to make them equivalent so that behavior is consistent across...

If I want to create an analysis that generates an event frame in PI System Explorer, often times it's useful to check the values of variables to make sure that a calculation is being done as expected to mitigate error on my end, and make sure I am...

The analysis tab in PSE can take quite some time to load if there are thousands of elements being referenced in the input attributes. This is rare for Expression, Event Frame and SQC analyses, but not as rare for Rollups. Ideally the tab should lo...

Please add PI FrequencyGT and PI FrequencyLT functions in AF analysis, like PI TimeGT and PI TimeLT, which find the frequency (number of times) within a range when an attribute value is greater or less than a given value.

PostProcessing stage of the transformation (if using ParantID and ElementID) should use paging (or another approach) for a better performance, it should also be better logged and display number of objects processed, a number of objects in the list...