Currently the integrator takes the Unit-of-Measure Class of the first element found that matches the asset shape, and uses that for all elements. This causes UoM conversion problems if other elements have units from a different class.

I want the UoM conversion to be optional, as only at design time one can determine if the current set of elements, AND the future set of elements returned by the asset shape would support any UoM conversion or not.
There are no technical means to ascertain the UoM class for future elements returned by the asset shape would match the current class.

This request applies to any OSIsoft product that requires a web browser: If certain browsers or browser versions are not supported by an OSIsoft product, the browser version should be detected and an error message shown to the user so they know to use a different browser or version.

During View import process, have the option to preserve or change the View's GUID. This comes into play if multiple Integrators share the same SQL backend; there will be a GUID collision. Use case: split a large view among Integrators (for performance reasons) by using the Export/Import option.

The Integrator application server should have a status page ("OK" or "Running") so that clients or load balancers can easily determine whether the site is up or not.  This should be implemented when the Integrator eventually supports high availability.

We are planning to represent the PI real time data in AWS Cloud (in any suitable format) using some weblink or any other way.

We trying to build a Dashboard kind of thing (using Dimensional modelling) to pull equipment data based on Several filter condition on AWS Cloud Solution.  I am not actually trying to put PI Server on AWS Cloud,

Going forward we need the ability to display the AF data related to equipment.

Will any PI Integrator help me to achieve my goals?

My users want to see the PI Point names in their views and not just the attribute name. I would like to be able to add the attribute configuration string as a column in my view.

The actual version just allows to create a text file output. It would be nice to be able to manage the format of the columns in that target

SAP recommends using compression on column store databases to conserve RAM and disk space resources (https://blogs.sap.com/2016/08/12/how-and-why-to-do-compression-of-column-store-tables-in-sap-hana/). Since date+time values are typically unique and compression in SAP HANA is column-based, compression of timeseries data like the data published by the Integrator is more effective if date and time are in separate columns as opposed to a single time column containing both date and time.

Native ArcGIS Feature Services allow for features to be updated by performing a POST to the REST endpoint to "Apply Updates".  It would be good to be able to record new values to the PI Data Archive by "Applying Edits" to the features / Elements made available for read access by the Integrator Hosted Time Enabled Feature Services.

I wish that the start time of a continuous view update cycle could precede the end time of the last cycle.

For example every day query the last 30 days of data and replace rows that have already been written to the target table with the most recent data. This would be a straightforward way to ensure that data in PI and the integrator View are the same for the last 30 days. Manual corrections up to 30 days old could then be captured automatically.

As a system administrator, I need a mechanism to backup and restore system configurations. The ability to export and import all or selected views is something that would help us maintain our system.

Update the naming convention used to create ArcGIS feature services and layers to use names that more accurately reflect the services and layers stored on the Integrator side. Customer Issue: The current convention is to use numbers instead of the layer names which causes confusion when trying to locate published items in ArcGIS Online or Portal for ArcGIS.

I would like if the quality attribute was available for PI Integrator. Some of my data comes into PI flagged as questionable. When I export data using PI Integrator, I would like include the quality attribute so I can easily remove any questionable data from the analyses.

As a PI Administrator for a power company I am asked twice a month to verify that none of the products I support have had a security patch released. Any such products in a NERC zone need to be patched within the next 12 days.

It used to be fairly easy to look at updates to all PI Client tools to find released security patches. So far I haven't been able to find out if any have been patched. This would also include interfaces which are prone to being run in a NERC environment.

To execute a view with the same parameters, it is actually mandatory to edit the view to be able to execute it again.
It would be nice to be able to force its execution using a right clic on it for example

When applying a filter when building a shape, the Integrator displays a limited amount of matching elements which is fine.
It would be useful do display the number of element matches as an additional info

As a data science user, I would like to be able to include additional PI/AF tag information such as is Questionable so that I may filter out data down stream easier.

The PI Integrator should validate any link entered in the endpoint section (PI Vision, Portal, GeoEvent). It should warn the user of any certificate issues or port that are not opened.

Support for element references within PI Integrator for Esri ArcGIS.