Ideas

The documentation for the IN function is somewhat unclear. The function definition shows examples such as: IN(number x, number y1, ... yn) and IN(number x, y1...yn) Whereas it's usage is: x IN (y1, ... yn) and x IN (y1...yn) respectively This is...

Analysis Management Plugin should ignore\ not allow backfill of non-history Analyses.  This will improve manageability. In the management pane, one can select analyses and then  queue for backfill, even if the analyses have no PIPoint D...

If there are no zeroth state needed for this type of operation then I don't see the need for the triggering input to be tied to a Digital State Set.

As a PI admin I would like to manage my tag configuration in bulk to efficiently carry out my role. PI Builder and excel provide a good way to do this for medium tag counts, however, the limitation of 100,000 tags makes it difficult to do this for...

When exporting Analysis Templates to excel with PI Builder, the AnalysisRuleVariableMapping and the AnalysisRuleConfigString normally includes uniqueid and GUID of the input and output attributes. It would be nice to have the possibility to filte...

As an analysis user, I would like to be able to specify the path for an AF attribute and use it for my calculation logic at all places that expect an attribute input.

Currently the analysis function "EventFrame" supports parameters "StartTime", "EndTime" and "Duration". I would like to see additional parameters "StartTriggerName" and maybe also "StartTriggerExpression". That could be useful for creating diffe...

As a PI Admin would like the ability to create or modify analyses using the PI Builder Excel plug in. Currently results vary and it is not supported by OSIsoft.

As a user of Asset Analytics I would like to reference parent element attributes, name, and other context information in Expression and Event Frame Generation analyses, even when it is not known during configuration time what the parent element wi...

Would be good to have one screen to manage the periodic scheduling for  all analyses in a given AF database.  This way, you can standardize where it makes sense to, and look for outliers (analyses that may have been scheduled incorrectly).