Ideas

Currently we do not have functionality to calculate a median over a set of tag archive values. For example a function such as TagMed('sinusoid', '*-2h', '*-30m') to return the median of that set of archive values.

Currently you have to type the attribute you wish to rollup by hand. Some of our customers have expressed interest in being able to select one attribute with the mouse rather than typing anything. Wildcard characters do work but some customers who...

Currently, if you want to store predictions for 1 day, 2 days, 3 days, etc. into the future, you must create a different PI tag for each distance into the future. Future data tags should support 2 timestamps: the timestamp that the predicted valu...

Users have requested to have Event Frames split up based on a time range to more easily visualize the data and make reports. For example, if an Event Frame is triggered Monday at 4pm and closed on Wednesday at 6pm it would be nice to have 1 even...

It's important to have Anaconda python with Af to perform machine learning and it will be easy to implement those models to have maximum benifits combined with pi and machine learning

As an AF Asset Analytics user, I would like there to be an option to output a value rather than 'Calc Failed' if an analysis fails to evaluate.  I have several aggregate analyses which are dependent on other analyses (which will occasionally ...

Hi team, I’m glad to hear the PI SDK is backwards compatible, but I’m equally surprised and sad to see PI ACE is no longer supported going forward, especially with the uncertainty of whether PI ACE can run on the latest Windows Server OS’s (curr...

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

PI DA Server should allow for more flexibility in terms of the format of archived data. A big advantage would be if PI could archive two timestamps per event. One timestamp will come from whatever the data source is (PI Interfaces, fiels devices, ...

It would be nice to have threshold attributes for pi points. Then we could configure that values received from the source outside this limits would be ignored (not stored), substituted by the respective threshold value or even by an "Over\Under Ra...