The integrator only includes EventFrames that are closed (have end time). That is not included in the documentation, so a major issue for me now.
The reasoning is that an open EF may not have all data or correct data. I would prefer to let the user decide on that and allow to include open eventframes. After all we can filter out the open ones using row filters.

I planned to use the integrator to get rid of OLEDB Enterprise. Now it turns out i cannot reach all my data. Looking seriously into returning the license.

The reasoning is

Customer would like to do Batch reports in BI Tool and Annotations contain important information, like Operator comments, reasons for changed values etc.

As an engineer using PI View or SQL writers for a report, I would like option to remove data older than a certain cutoff. For example, a continuous view is used to generate data for a report on the last 8 hours. Data older than that are no longer needed for the report and should be removed to avoid unnecessarily large tables.

One workaround with Text and Hadoop writers is the Append Timestamp option, but there's no ability to remove data from other targets.

As a user of PI Integrator for Business Analytics, I'd like to have it support high availability (HA).

We would like a better way to manage views in the Integrator User Interface. For example, we would like the views to be able to be sorted into a folder structure. With many views it is hard to properly manage them without something to sort them.

As an engineer looking to leverage hundreds of thousands of tags for BI, I would like to use a single integrator instance to publish all of the data rather than installing multiple instances on different nodes.

Currently, the PI Integrator for BA 2018 will add rows for event frames ending within the scheduled update time range. It would be better if the PI Integrator signed up for updates on the database and gets a list of all new or modified event frames to handle the cases where event frames are closed with an end time in the past that is not covered by the run period anymore.

Currently the PI Integrator for BA captures out-of-order data and edits of existing data in the archive through PI Integrator sync service. However, it does not capture late arriving data which may happen as a result of network outages between a PI Interface/Connector and the PI Data Archive. For these situations, the PI Integrator publishes null values unless a key column attribute is used to generate the timestamps. Ideally changes should be captured for late arriving data so that data is automatically updated from the PI Integrator when it eventually arrives.

When PI is used to gather equipment sensor information but Maximo is used for asset management, it would be helpful to have a simple way to get equipment information out of PI and into Maximo.  This would be useful for scheduling preventative maintenance, among other things.

Many partners we work with would like to be able to configure views and data output from PI Integrator for BA directly from within their Analytics tools. This could also allow for better integration with third party analytics tools and open an OEM/Reseller market for OSIsoft partners.

Support an end point for MQTT

The PI Integrator for Esri ArcGIS does not support SAML authentication through Portal. Support for SAML authentication would allow PI Integrator users to configure their own Identity Provider.

Customers who plan to have a significant number of views need a better way to manage the status of their views other than periodically checking the PI Integrator UI.

There should be a way to obtain view statuses through other programs (custom or PI), so that users can receive alerts if a view goes into an error status.

As an administrator for the PI Integrator for Esri ArcGIS 2017, I want to be able to change the SSL certificate bound to the application through an installer wizard. Currently, the only option is to uninstall and reinstall the application, or manually bind the certificate using the command line netsh.

There are automatic updates for PI data in Asset Views and Streaming Views, but not currently in Event Views which is what's used for Event Frames. This is important for propagating changes in EFs

Use case example: GADS classification. Data comes in and EFs are created. The integrator picks this up and sends the info along. Some time later (maybe a few days / maybe month end) data comes in re-classifying / updating the original data (ex. GADS code or attributes). In order to accommodate this manual intervention using the "Update Data" button is required.