All ideas

When having calculationWaitTimeInSeconds set to a large value in combination with an AF-SDK app triggering recalculations, it can happen that recalculation writes a value at timestamp x before this analysis is triggered to run in real-time for tim...

Having the ability to store analysis variable configuration (calculation) in an attribute value would help a lot in creating assets from template that have diverging analysis configuration. For example, an attribute named attribute1 with a strin...

Analysis templates are useless if one need to adapt the analysis for some elements, for example in my case I need to change the "True for" clause in an Event Frame Generation Analysis, but I can't because it is created by a template.

Leaving the default to Any Inputs for expression analytics can cause some performance issue as a calculation could end up triggering multiple times per second if there are several inputs. Since this is the default, some users may not take the time...

This suggestion is on how you manage the input tags into calculation that at some point it returned bad value (like I/O Timeout, Bad Input, Snapfix, etc...) or became questionable. These tags will make your calc at analysis become "Calc Failed". I...

If something I'll call lists are implemented following the model of categories (that is an element can belong to multiple, arbitrarily named entities) and rollup is extended to allow that as an option in addition to the parent element, this would ...

See the attached picture. The picture also reveals other parts of PI System Explorer that are not translated. The picture and the idea for this suggestion come from https://pisquare.osisoft.com/s/feed/0D58W00006XNrBuSAL.

Currently it's not possible to use attributes that are based on a PI Point Data Reference with RelativeTime or TimeRange settings as triggers for analyses with event-triggered scheduling. You get the "No valid triggering inputs found" error. The r...

When using the recorded values function in Analysis, Time weighted totals and averages assumes that the data is continuous and not discrete. This creates issues with data streams that are both discrete and require time weighting functions. Ideally...

Some Analytics fail due to a tag not existing. It is possible to test for a Bad value via the BadVal() function, however, this does not work if the tag does not exist. Consequently the equation will not run. This caused me many hours of debugging ...