Ideas

Trigger analyses "On Any" but also allow for a MaxTime and trigger after MaxTime has passed. Helpful to keep the timestamp current.

Currently, if a variable is mapped to an attribute and the attribute's AF path changes, the variable must be remapped to the attribute. Instead of relying on the attribute's full path to identify the attribute, each attribute should be identified...

Normally AF function PrevEvent() returns the timestamp of the previous event for a specified timestamp. But if the previous event is system digital state "No Data" it does not return the timestamp but again system digital state "No Data". That is...

Currently it is only possible to specify one timestamp override per analysis.  I would like a way to set a conditional based timestamp override that way the output timestamp could vary based on the result of an analysis.

The traceability of cross-element analysis in the PI System Explorer would be greatly improved by using jump labels on relative or absolute paths in the expression or in the ConfigStrings. For example, you could jump to the referenced element or a...

As control engineer, i think it´s necesary to include some flow control functions, as for next, while, etc; and the capacity to do Iterative functions.

Create rate based Performance counters for analytics & Calculations instead of counts. For example counting the number of EFs created over time is not as helpful as knowing the rate at which i create EFs. The rate would allow me to catch spike...

At the moment recalculatuion order is only respected correctly if the referencing to attributes in other elements is done directly in the analysis, e.g.: '.\T22LBA12FT901 XJ50_BER|Value' And it is also possible to use filters, e.g.: '.\Elements...

As a troubleshooter, I use the Analysis Service Trace logging to determine why certain analyses are not returning the expected results. Currently, Analysis Service Evaluation Trace logging records the inputs and outputs for each analysis. It would...