As a PI Administrator, I need to determine the health of the PI Integrator. I wish to monitor the connection and inter-process behaviour between the integrator and multiple worker nodes. I would like to be able to determine when a worker node disconnects from the integrator framework/host, hangs or becomes unavailable as this will result in no data being published. By monitoring the health and performance of all components of the PI Integrator, I can take a proactive approach to system health and performance.

As a user who publishes to Oracle, I would like the PI Integrator to support the latest Oracle database and ODAC versions so that I can take advantage of Oracle bug fixes.

For example, the PI Integrator 2020 version supports only ODAC 12.1.0.2.4 , but nuisance messages due to the following were resolved in a later version of ODAC: ORA-03137: Malformed TTC Packet From Client Rejected.

Currently OSI has not tested web-based PI tools with Chromium-based version of Microsoft Edge.
It will be helpful to know if there are plans for it to become officially supported by a certain time, since eventually Chromium-based Edge will get pushed to all of end users

OAuth2 is the recommended security practice to authenticate users and applications by esri. This would also allow the PI Integrators to use Windows Active Directory Federated Services as organizations move to Office365.

It would be nice to have an option to specify PI INT to create sub folders within a 'view' folder in AWS S3 so that data files dumped in S3 folder could be automatically organized by the time period, example: subfolder for all files created for that day.

As an Azure IoT Administrator, I would like to only give the Integrator minimum permissions to my IoT hub in order to minimize security concerns and reduce management overhead for shared access keys. Currently I can specify a device ID in the Integrator's Admin > Targets page, but this still requires a connection string for the IoT hub as opposed to the individual IoT device. I instead want to be able to use the device-level connection string.

In PI Integrator for BA, to use filter on an attribute configured as Boolean Value Type, we can use Numeric filter. However, 'attribute' = 1 does not work because it filters out all the rows. We have to use 'attribute' = True. It is not intuitive that we can use string value in a numeric filter. Is there any way OSIsoft can improve the UI, like add a row filter option for Boolean?

I would like to get notified for Unique Output Streams Consumed or Remaining in PI Integrator Administration page under Licensing.

I would like to be able to publish data from the PI Integrator for Business Analytics to Apache Hive that is set up for only Kerberos authentication.

Support integration to non-Esri GIS systems such as GE Smallworld

We are using PI Integrator to write operator comments to a file target. The operator comments can include carriage returns which mess up the data written to file. Carriage returns and other bad characters should be replaced before writing to the target.

When publishing to a file, the file can get extremely large. There should be an option in the file target to specify the maximum file size before rolling over to a new file.

Please update testing to include support for ESRI Arc GIS 10.8.1 which was released in July 2020

When using PI Integrator for esri ArcGIS, logon to Enterprise portal or AGOL can fail. But the current UI does not provide why it failed.
As a user, I would like to know why my portal/AGOL login have failed so that I can either use alternate accounts or troubleshoot issue more promptly.

As a PI Integrator user, I would like to view the next run time of my scheduled view to ensure that I have configured it correctly.

PI Integrator creates tables in the destination database. I'd like to have PI Integrator publishes data to pre-defined tables.

PI Integrator supports SQL authentication to the backend SQL server. However, the install user is only authenticated to the SQL server by windows authentication, which makes using a non-domain SQL Server unfeasible. Please support a non-domain SQL server as the Integrator backend to allow more flexible architecture options.

To avoid confusion during certificate selection, please change the friendly name of the self-signed certificate from "PI Integrator for Business Analytics" to "PI Integrator for Business Analytics Self-signed Certificate"
PI SQL DAS self-signed certificate has the friendly name "PI SQL Data Access Server Self-signed Certificate", which is quite clear.