Analytics & Calculations

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

Add support to import AspenTech functions into Asset Framework to use with Analysis.