All ideas

Analyses can suffer from bad calculations due to bad events for a tag, such as system digital state events returned for a numerical tag. Although BadVal() can be implemented to avoid using bad events in these analyses, they add another layer of ...

It would be useful to trigger event-triggered rollup analyses upon adding new children. Currently rollup analyses are only triggered when rollup attributes are updated (and not triggered when rollup attributes are added). This would be particularl...

Created on behalf of a customer: In order to use fewer attributes in an element, a customer hoped to output analysis results to an attribute with a dynamic PI Point data reference. Unfortunately, with the use of substitution parameters or with str...

PI System Explorer Management Tab should have better search criteria. For example, select specific elements in which to rerun an Analysis. Maybe use Element = something OR/AND Element = something else. Or search by element path.

Data can be flagged as questionable, which should mean the value may or may not be valid. Asset Analytics seems to be rejecting the value as Bad. The function instead should evaluate the result, but flagging the result as questionable as well.

Feature of Notifications 2012 that was not carried forward - big mistake. Need the ability to customize the sender email on notifications.  Makes it easier for users to configure email rules to take actions such as file in certain folders, f...

Currently, the only way to acknowledge a notification in PI Notifications (2.X) is to acknowledge the event frame in PI Vision. Not all customer's have PI Vision. Therefore, the Acknoledgment Site from PI Notifications (1.X) should be upgraded t...

The Non-Repetition Interval in Notification Rules is currently only applied to Notifications sent at Event Start. I would like the Non-Repetition Interval to also be applied to Notifications sent at Event End.

It would be helpful to see if our PI system version is up to date and if not, what the latest released version is. This helps us with the upgrade planning.

Originally posted on PI Square at https://pisquare.osisoft.com/ideas/29295-individual-collective-members-health-data-matches-with-other-nodes We would like a way to know if a node in a collective is not receiving the same data as the other nodes....