China Network Isolator interface does not support float64 point type, which is required by many customers in China. Right now, they have to change the point type to string first and then to float64 by analytics, this will consume two times of license number.

The interface instancesnames contain the plantsnames and I want to put the interfaces with the same plant name together in the list.

CA ISO is planning to upgrade its ADS (automated dispatch system) to version 8. This upgrade introduces breaking changes from the current system, API version 7.

The CA ISO interface should be updated to account for these changes.

When primary server is down, secondary server is accessed instead of primary server, which is good. However, in the case of output point with source tag, it stops working, then restarting the interface instance of interest is needed. Of course, if we set up UniInt Failover that backup instance keeps its session with secondary server, this issue can be prevented. But, it will be better if source tag is also switched to secondary server.

As a PI System Administrator, I would like to monitor the point count and other parameters for scan class 0 via Performance Counters. Currently, this is only exposed via the UniInt Health Tags.

Currently, AMI Interfaces require a rebuild of the AMI cache files when the PI Server is migrated to a new machine/hostname (Although to clarify if the hostname does not change during the PI Server migration the cache does not need to be rebuilt). This is undesirable for large AMI implementations as rebuilding the cache files can be a time consuming process.

It is requested that AMI Interfaces should be able to handle PI Server migrations with new hostnames without rebuilding the AMI cache files

PI AMI Itron Interface currently supports TLS1.1. Microsoft ended support for TLS1.1 in March 2020. To keep the PI AMI Itron Interface usable with latest browsers, please update to support TLS1.3.

Batch interfaces should follow a similar approach to UniInt based interfaces to retrieve the diagnostic tags. That is to say they should pull the diagnostic tags based on the PointSource, Location1, and ExDesc, not a hardcoded name based purely on EXE name and Location1. This would allow the PI admin to name tags to their organization's naming convention and also avoid naming conflicts between interface instances of the same type running on another interface node.

There are no current direct native interface connectivity to Hitachi ABB Mach systems.

Current suggestion is to investigate IEC 61850 or Modbus could be investigated as an option.

This affect to delay in Event\Trigger points. KCS: Delay in Event Points.

When using Event Points, we purposefully do have a delay (if excMax is > 2 s then 2 s else 0.9*excMax) for advise tags (Trigger Point) before they're sent to the PI Server if the event value has not changed since the last scan.

As an interfaces user, I would like to know which versions of iFIX and Windows Server OS are compatible with the PI Interface for GE iFix so that I can determine whether this interface is suitable for my use case.

The last update for this interface was in 2014, so there has been no testing on compatibility since iFIX 5.5, but I am looking to use versions 5.8, 5.9, and 6.0 and Windows Server 2016.

The PI Interface Configuration Utility install kit currently includes both the 2012 and the 2019 Microsoft Visual C++ Redistributables. Please upgrade the PI Interface Configuration Utility so that it requires only the Microsoft Visual C++ 2015-2019 Redistributable. This will reduce the size of the install kit and make it faster to download and install.

Even though PI Interfaces are slowly being phased out in favour of PI Connectors, OSIsoft is still releasing new PI Interfaces, and so the PI Interface Configuration Utility will still be around for a long time and it will still be worthwhile to optimize it.

The MAXSTOPTIME parameter for batch interfaces does not kill the interface process when the limit is exceeded, however the parameter does work for UniInt based interfaces. Please fix the batch interfaces so that the interface process is killed once the MAXSTOPTIME has elapsed.

Batch interfaces should write their messages to the message logs using the Source1 and Source2 fields just like UniInt based interfaces. Currently, batch interfaces leave these 2 fields blank. Source1 should contain the process name or similar and Source2 should contain a string in the format of "<PointSource> | <Location1/ID> | <FailoverID>". Having this will greatly help PI administrators filter the logs based on point source, especially when there are 20+ interfaces running on a server.

ABB 800xA offers a batch capture mode that is more flexible than ISA88 since it doesn't match all unit procedures to units, but rather acquires them at the beginning of the batch. Currently the interface is designed to only retrieve batches that follow the ISA88 model.