Allow a different naming pattern for the child event frames. End result would have the long, uniquely named EFs in the Parent EF as usual, but the Child EFs could have a simplified name, like the level of an alarm that is pulled from an attribute value (capable as of AF 2017 R2).

As an AF administrator. I want a simple way to generate a complete list of all analyses in error for an entire AF Server. Currently, the only way to retrieve analyses in error is in PI System Explorer which is restricted to a single database and there is no way to export the list.

At times I have event frames that generate late for various reasons that trigger a notification. Since it was late we have no need to get the notification. I would like a way to not have a notification trigger if it is late.

As for now, automatic recalculation is not triggered by changes on snapshot (KB01790), which means auto-recalculation does not work with snapshots values.
The idea of it doing otherwise is to help users that mistakenly added a wrong new event to a manual data entry tag to fix it and all related analyses.

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.

As a user, I would like to configure my rollups to display a value only if the quality of my inputs reaches a minimum % good (configurable). Currently, it's not clear which inputs are used in the rollup calculation- even if some inputs have bad values, the rollup calculates and appears normal.

On a highly loaded system with thousands of analysis i have one analysis that is misbehaving, missing executions but no skipped count, etc. Currently tracing enables tracing for ALL analysis creating an ocean of logging to plough through for that one event every few days.

As an AF administrator i would like to turn on Tracing for one or more individual analysis to investigate rare issues that happen over time, without logging ALL analysis evaluations as 99.9999% runs fine.

Ability to link Event Frames coming in from different sources (batch & mes interfaces, EFgen, PI Analytics, custom, etc.) together based on rules and monitoring an EF attribute SO THAT it's easier to associate time frame context and data that is related together but come from different sources.

Some organizations do not provide admin accounts with write permission to the root C:\ directory. The install kits of most PI products copy the setup.ini to C:\pisetup.ini, and then write the logs to C:\ before moving them to %pipc%\dat, both of which require write permission to C:. The only workaround for now is to find someone with that permission to run the kit (typically an IT member).

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

Currently notifications are not triggered (send) by events that are more than 72 hours in the past. For me it is necessary to get notifications from events in the (endless) past. Ideally I would like to configure for each notification separately the time range (from now on backwards) in which the notification should be triggered.

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 an AF administrator, I  would like to send in an attachment of a Notification files that are specified by file path in AF attributes. I currently do this by specifying the value at start time of an AF attribute that contains the changing file paths,  in the body of the email. I would like to have this as an attachment instead.

Currently analysis runtime information can be accessed programmatically using the AFSDK (AFAnalysisService.RuntimeInformationFields - https://techsupport.osisoft.com/Documentation/PI-AF-SDK/html/P_OSIsoft_AF_Analysis_AFAnalysisService_RuntimeInformationFields.htm). However, there are no fields which can be specified corresponding to backfilling/recalculation status of an analysis.

Adding a field for the aforementioned property or introducing a new method which could expose backfilling/recalculation status would be helpful for finding backfilling/recalculation errors programmatically. This approach should be much faster than finding analyses with backfilling errors in PSE.

It would be useful if Analysis Service would set the name of the Event Frame on close rather than open.

The use case is customer wants to dynamically set the name by a value of an EF attribute (possibly an EF output attribute) - for example, if a value changes while the event frame is opened, the customer wants to output the status of whether it has changed or not to an EF attribute and use that value such as  "<Event Frame name> - changed" instead of just "<Event Frame name>"

Currently, AF search results can only be sorted by a single field. It would be useful to have the capability to specify 2 (or more) SortField values so that the order of results can be guaranteed in the result of a tie.

For example, being able to sort Event Frame Search Results by both StartTime and EndTime.