The OPC landscape is shifting away from DA/HDA and towards UA servers. A significant number of OPC client tools are being created that connect to OPC UA servers, and none of these are compatible with PI without the use of a third party UA wrapper since we only provide DA and HDA servers.

Add auditing or a view of statistics for the calls or requests done by each individual application. Allow a PI Admin to see which user or application is making a specific call and see how long it takes to complete to monitor performance and potentially resource intensive Web API calls.

As a PI Web API user I want to know exactly what kind of Body Parameters (their defaults and description) are supported by PI Web API methods. The current sample requests are not sufficient because they do not describe the values for body parameter, though many parameters have unique restrictions.

Here is an example of desired content:
https://developers.jivesoftware.com/api/v3/cloud/rest/StreamEntity.html

Add methods to retrieve messages from the local and remote PI Message Logs where remote can refer a PI Data Archive node or any remote PINS.

Because the EventLog Class in .NET Framework provides access to local and remote Event Logs, offering the AF (Server) Event Log through PI AF SDK is not necesarry.

As of now, we can get PINetMgr statistics via PowerShell command Get-PIConnectionStatistics. # of users familiar with AF SDK are more than with PowerShell.
It will be nice feature addition in AF SDK, and usability will also increased.

The ability to backfill an analysis using an end time in the future. This would read data from future inputs and write the results as future values.

When any time related functions need to be performed against timestamp columns in PI SQL Commander, one needs to utilize a significant amount of conversions to make this work. For example, if one needs to round timestamps to the nearest minute or the nearest hour, a CASE statement with multiple CASTs needs to be done to get this to work.

If T-SQL DATEADD and DATEDIFF commands were implemented, this would simplify the query by a significant amount. Similarly, in PL/SQL, the ROUND function is able to round the datetime value directly, which would fit perfectly to this scenario.

I would like the RTQP Engine to be able to read annotations.
My use case is the following :
I have user that enter manual values into PI along with these values the operator will specify the reason for this manual input.

The comment is stored in an annotations, there is currently no way to retrieve this information.

Retrieving a string would be sufficient for my needs.

I would like the ability to access event frame annotations using PI SQL Client, in the same way as in PI OLEDB Enterprise.

When the crawler fails on an incremental crawl, the index search must perform a complete rebuild of the index. It would be beneficial for there to be a way to revert to a previous built index just prior to the failed incremental crawl so that the index file is available. This is particularly useful for large data sources that take hours or days to crawl before they're usable again.

The OPC DA Server service uses %PIPC%\PI_OPCDA2\Data\SavedNamespace.xml to load the tags and does not update the  cache until  the service is stopped and started again. If any new tag is added to the PI Server, it is not picked by the OPC DA Server. The service should periodically update its cache from the PI Server after the initial start.

As a PI Web API user, I would like a simple method to perform bulk deletes of a particular attribute or PI tag. Currently, a bulk delete requires 2 calls. One to retrieve the event I wish to delete and another to delete it.

I would like the ability to pass response values from one request into the body of a dependent request using the batch controller to avoid making 2 calls to the PI Web API.

Currently,  I can only use Parameters in subsequent URLs, but not bodies.

As a developer of custom applications that use the PI  AF SDK, I'd like to be able to easily determine if an attribute based of an attribute template is configured for tag creation. Currently the AF Attribute Template class does not have this property. The current work around is to look at the configuration string which is less efficient.

As an end-user, I want to be able to see to which PI Collective member I am connecting to. I also want to be able to toggle programmatically from one PI Collective member to the other so I can make sure the informaiton I am seeing is aligned and in synch accross all PI Collective members without going into thick PI clients or through log files.

As a PI SQL Client OLEDB user, I would like to have the TIME(), DATE(), LOCALDATE() and TOLOCALDATE() functions available in order to construct datetimes for my queries.

These functions were available in PI OLEDB Enterprise, but are not available in PI SQL Client OLEDB.

If PI OLEDB Provider is not going to be further developed, allow PI OLEDB Enterprise to connect directly to a PI Data Archive.
There are times when an SQL type query is needed, but the data structure has not been mapped to an AF server yet.

The ProgID of the 2015 PI OPC DA Server is OSISoft.OPCDA2.DA.1, while the ProgID of the 2010 PI OPC DA Server is OPC.DA.1.

Existing client tools that pointed to the 2010 PI OPC DA server will need to be reconfigured to point to the new ProgID after the PI OPC DA server is upgraded to 2015.

While this is done because of an architecture change between the 2010 and 2015 servers, potentially necessitating changes to be made to the client application, it is still desirable in some cases to point it to the new server without changing the ProgID.

https://pisquare.osisoft.com/message/116957-pi-sql-commander-and-ssrs-how-to-retrieve-multiple-values-with-the-same-timstamp

In the current implementation of the transpose archive in OLEDBEnt, a user is unable to retrieve data that may exist at the same timestamp as  another piece of data. This is because the time column is treated as the primary key of the transpose table. I would like to be able to retrieve all data using the archive transpose function regardless if timestamps are duplicated.