It is difficult to find all the analyses from template to backfill/recalculate after making changes in Analysis Template.  Currently one has to navigate to the Management plug-in, do some sort of search/filter, then queue the analyses.  This is a multi-step process.  Consider providing a better user experience.

When i create a derived Element Template, i would like to be able to override an inherited analysis. Now i am severly limited in the re-use of templates due to this limitation. I cannot extend nor exclude functionality in a derived template if this is used in an analysis, because i cannot adapt the inherited analysis.

This is similar to https://feedback.osisoft.com/forums/555148-pi-server/suggestions/17865355-exclude-analysis-function
but the two would complement each other quite well

Add the capability to perform scheduled backfills for a specific time frame, for analyses created on PI System Explorer.

For recursive Analyses such as below :
PrevVal(tagA,'*') + 'TagB' → output : tagA

When the PI Analysis Service is down (or the node needs to be restarted), the current calculation needs to be halted until the Backfilling reaches up to the start up time. Or else the value will not be as expected.

While no customers have asked for this directly, I have seen many customers ask how to check a tag for being stale. The solution to date assumes all tags have the same staleness timeout, which really is not the case most of the time.

This new "StaleTimeout" point attribute would be a duration (time span) customizable for each tag. There could also be a new PIPoint property called "IsStale" which could bounce the current value's timestamp off the "StaleTimeout".

As a user of Asset Analytics I would like to have more flexibility in including elements in my rollup calculation so that I would not need to build large hierarchies just for the purpose of rollup analyses.

Currently, in PSE there is no way to display attribute values greater than or equal to 1000 with commas for the thousands separators. Ex: 1,234,456 instead of 123456. This option exists in other PI Clients (i.e. PI Vision) and should be available in all PI Clients.

I would like to be able to configure outputs in an analysis to write at multiple time points (which are defined by the result of an array function).

My use case is to:

1. Configure an attribute as a Time Series Table Lookup
2. Create an analysis that retrieves the values of this attribute as an array, e.g. using RecordedValues
3. Transform the data using MapData
4. Write the result back to another attribute that is configured as a PI Point

Using the Max Rollup function - I would like to know which element provided the maximum value and output this as well so I can historize the information.

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 complexity the expression.

The addition of a "Use Good Data" only option in the analysis tab in PSE that applies BadVal handling on top of an analysis would help simplify expressions.

In AF please provide a way to suppress time zone and/or to format the timestamp in AF Events, particularity, Notifications. For example, in the message format in e-mail notification I do not need to indicate the time zone it was triggered in.
Please make this available in the AF SDK as well as in PI System Explorer.

Currently, the "Management" tab in PSE only allows you to view and manage analyses for the current AF database. Requesting the ability to select and manage analyses for multiple databases or an entire AF server without having to switch between databases.

As a PI Administrator of a PI System with complex security requirements, I need to set up different default permissions for various users so they can create tags that automatically have the proper security instead of having to rely on a process/procedure to correct security after the tags are built.

As an user, I want to be able to retrieve results of event frame searches and summaries and store them as AF attributes so that I can view event frame data in an AF attribute.

As an user, I want to be able to treat event frame like time series data, such as number of active event frames, sum of an attribute, so that I can continuously monitor the evolution of event frames over time.

As a PI System Explorer user I want to be able to see when was the creation date and last changed date of an AF object without enabling the Audit Trail, similar to the PI SMT feature which is easily accessible and works by default.

When editing PI Points, PI Builder does not return any error if one of the headers is wrong or misspelled. Simply, nothing is edited for that header and you  only find out at a later time when looking at the PI point. It would be useful if PI Builder could inform you when one of the headers does not match any PI Point attributes.