Create a utility/script that will output the PI products installed, their versions and the most recent version of the product on the machine it is run on. This would help with installations and to manage the current software that is installed.

Extend the capability of PI SQL Client to connect directly to PI Data Archive Server

The PI Web API exposes a "CanBeAcknowledged" property when reading Event Frames. However, this property is read-only: it cannot be supplied when creating a new Event Frame or updating an existing Event Frame. I would like the ability to include this parameter when creating an Event Frame.

In OLEDB Enterprise, we could find element references by type.  Currently, this information is not exposed in RTQP.  It would be helpful to be able to identify which type of reference an element is using.  One use case is for PI Admin's to generate reports on element hierarchy to ensure the proper reference is being used by builders of the AF DB.  This is especially helpful in AF DBs where element references are used to build multiple "views" using the same elements and the reference type could be used in conjunction with the new IsPrimaryPath column for reporting.

My client is interested in writing annotations to Stream (time series) data via the PI Web API. I know it's possible to pull this data via the ?associations=annotations query parameters but the write feature is missing.

PercentTrue is missing in the WebAPI. Would you consider adding it? For some context, I come from here:

https://pisquare.osisoft.com/message/115587-re-calculation-percenttrue-is-missing-on-the-webapi

Allow PI OLEDB Enterprise access to AF Tables.  The current workaround is to have the table live on a SQL database and then link to them from AF.

The channel/websocket feature of PI Web API would be more useful if it was possible to subscribe/unsubscribe to attributes on an existing channel connection. Currently you have to open the connection with all the WebIds you want in the resource URL. If you want to change which values you are receiving, you would have to close the connection and open a new one. Adding this new feature would also solve issues with maximum URL length limitations.

In verifying the OPC DA server DCOM setting you need to use the OPCclient to check PI tags values. In the OPC DA server 2017 you need the latest version of OPCclient (was not in OCP client tools) to allow to connect correctly to the OPC DA server 2017. If the OPCclient was in the OPC DA server 2017 I would not had needed to go down load OPC Tools kit.

Add functionality to annotate AF Elements using Web API.

Support Type updates on PI Web API OMF ingress

I would like to be able to setup the PI Web API OMF endpoint to point to multiple PI Systems, so that way it is easy to send from this single instance to different production systems or to our development and production environments concurrently

Today PI OPC DA can only expose tags from DA.
To have the option to expose information from AF.
Both the AF structure and attributes.

We are using AF for everything so why not in PI OPC DA.

In the https://pivision-us.oxy.com/piwebapi/admin/search/database.html page the Rebuild Index button does not work. It should allow the pi vision administrator to immediate re-indexing of individual AF database at the time without affecting the usability of the others.

A user tries to retrieve date with timestamp 03-Nov-2018 23:59:59 (1 second before Daylight Saving Time beginning) in PI SMT, but the returned event has a timestamp of 04-Nov-2018 00:59:59. This is because PISDK timezone design is such that it can only transition DST on minute granularity, and the Windows TZ info for Brazil says the transition is at 23:59:59 so PISDK truncates the seconds for the transition rule.

Currently the PIPointQuery cannot contain a filter condition with same filter name twice per AND condition of the query string.

PointId:>5 AND PointId:<10.

This would cause an error.

Therefore filtering for a certain range is annoying as both result lists then have to be compared for common elements, workaround for the AND in above condition.

Enhancement:

Introduce a "BETWEEN" operator for the filter condition.

Allow multiple use of filter names in the same AND condition.

As a Web API developer, I would like to be able to use time PE functions in the Web API using the streams/streamsets controller to allow for complex time queries.

'Time Zone = Server' is available in PI OLEDB Provider, but has not been added to 'PI OLEDB Enterprise'.
We have PI Data Archives in multiple time zones and require the ability to select the data in the server time zone.

The UpdateValues method does not implement by itself the exception mechanism. Exception is applied on the client side, for instance by UniInt interfaces.

As a developer,  I would like this fact to be mentioned in the documentation to avoid confusion:
https://techsupport.osisoft.com/Documentation/PI-AF-SDK/html/MOSIsoftAFDataAFDataUpdateValues1.htm