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

Cp, Cpu, Cpl, Pp, Ppk

On high latency networks, it can take ICU many minutes to start because every interface on the PI Data Archive is checked. Minimize startup time by caching a node's registered interfaces.

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.

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.

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

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.

Offer a free Community Edition of PI. Limit the point count, but let us geeks monitor our IOT hobbies with PI. This will encourage business buy in and increase general knowledge of OSIsoft throughout the geek community.

As an user, I want to be able to have a localized element and attribute name in addition to the base language, so that my users do not have to learn a different language.

If you have a PI Point attribute with auto tag creation and you want the attribute UOM and PI Point engunits to match, you have to define it twice; once in the attribute UOM field and a second in the attribute configuration string, e.g. engunits=m3. If there was a substitution parameter for the attribute's UOM, you could use it in the attribute configuration string, e.g. engunits=%AttributeUOM%.

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 an administrator, I want to use SQL Azure as the database backend for my PI AF databases, so that I can offload the SQL adminstrative tasks to Azure.

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.

Our company is progressively superseding the deployment of hosts with SQL Server installed, while moving towards the usage of SQL Server instances provided by AWS' Relational Database Service as the DB backend. Although currently OSISoft does not officially support the usage of RDS instances as backends for AF and PI Vision, we performed some internal tests with both AF and Vision and they seem to be promising. We would like OSISoft to study this kind of solution and, if there are no major obstructions, provide official support for such scenarios.

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.

To have an email acknowledgement system where recipients can reply to the email and have the notification acknowledged