As a quality engineer, I need the ability to calculate Six Sigma SQC statitistics for key quality attirbutes. 

Cp, Cpu, Cpl, Pp, Ppk

As an engineer, I want to execute analyses when I get a new future data value, so that any forecasts (either via Analysis or via a 3rd party system or via a PI Point update) can trigger analyses.

As a user of PI AF and Notifications Service, I would like to send emails, with contents whose color will be changing according to the condition, like a Multistate Symbol on PI Processbook. I would like to avoid creating a number of email formats with the personalized contents.

Use case: User wants to trend Analysis Data Reference in client tools (Processbook, Coresight). User doesn’t want to create a PI tag for this output. Currently, the AnalysisDR ignores step, even if it’s input attributes are step.

It would be nice if there were an "Output at start" option to output values at the start of an event frame. Currently there is an "Outputs at close" option for Event Frames.

I would like to have monthly and yearly periodic trigger for Analysis-Expression and Event Frame Generation. Currently I have to use the daily trigger and check in the analysis if the month or the year changed. In case of “false” there is no output. In the case of “true” there is an output. This works but it is circuitous.

As a user, I want to be able to import/export AF tables using PI Builder, so that I can make changes as needed.

As a user of analyses, I would like to have a Percentile function so that I can filter out atypical events when doing summary calls. The function would look like this: Percentile('attribute', 'timerange', value). This is related to enhancement request WI 44140.

We currently have Event Frames generating for machine faults, with child event frames then tracking things such as maintenance team response time etc.
Leveraging this data in excel reports is proving difficult however due to the Child Event Frames having the same template and naming convention as the parent.
If Child Event Frames could have custom naming or different templates it would be extremely valuable

Currently PI Analysis Service has a built-in Statistics tool in PI System Explorer.

It is able to show statistics regarding Evaluation and Calculation Lag as well as Skipped Evaluations and some other important information.

PI System Explorer could run these statistics periodically and notify the user (in the Management tab or in the Analysis tab itself) whenever a PI Analysis has its parameters out of certain values (could cause a bad performance)

So that the users could avoid performance issues more easily.

It would be useful to add a feature to list notifications by user. This feature would be helpful in managing the list of notifications as more notifications are created and as users change job roles.

As a user of Asset Analytics I would like to manipulate data quality related flags (such as quastionable, substituted, etc) from my analysis so that I can set the flag when there is a problem with input value statuses.

I would like to have the possibility of automatically recapturing values for event frames, so if the lab data comes in after the events are generated the late values could be recaptured automatically and in bulk. This will save the time and effort to manually identify and recapture values for each of those event frames using PI System Explorer.

As a PI Administrator, I need to trust that the data is identical between my collective members. Currently, there is no way for me to be sure it is the same unless I do a side by side comparison. Data can be missing, or slightly off, and I have no easy way to understand this right now.

Recovering a PI tag that was deleted accidently is extremly annoying.
Why do I have to create a new tag and reprocess all historical archives to convert the old tag to the new tag in the archives? (https://techsupport.osisoft.com/Troubleshooting/KB/2651OSI8/)

It should be quite easy to just recreate the original tag if you have the pointid and recno. Maybe when deleting a tag you should only mark the tag as deleted instead of removing it from the pi point table.

As an analysis user I would like to define what should happen if multiple triggers occur with the same timestamp.
Currently AF analysis are using "Replace" mode when writing to the archive (meaning if multiple triggers have the same timestamp, the last one will overwrite all previous ones). AF SDK supports using "Insert" mode (which allows for multiple values having the same timestamp). I would like to have an option to select the write mode for each analysis.