The current version of the PI Interface for OPC XML-DA seems to only support SOAP 1.1. All recent OPC XML-DA servers are developed following SOAP 1.2 standards, meaning the PI interface will not connect. Please enhance the interface to also support servers using the newer SOAP 1.2 standards.

This also relates to tech support case 00857284

As now it is just Source and Area event attributes that work for the instrument tag. It should be possible for any attribute to work as a filter in instrument tag. It is not every OPC AE server that supports Source and Area.

The PI Foxboro Interface should support the new Foxboro platform on Windows Server 2016 and I/A Version 9.4.

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.

Enhance the OPC XML DA Interface to store bad quality values from its OPC XML DA Server in PI, so that the values, timestamp and status from bad quality data are saved in PI.

Note: This is work item 21742OSI8 - Add support of data quality.

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.

Certain MIB files use dynamic indices which make dynamic OIDs. As the interface uses OIDs in the instrument tag manual action is needed to repair it should the OID change. This is particularly prevalent when using the HOST-RESOURCES-MIB, which uses process ID as its index.

Add an option to encrypt trafic between interfaces/connectors and the PI Data Archive

Add support for BACnet Setpoint objects in the PI BACnet interface.

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.

Add ping -i feature to the interface and allow for either the output of the ping time or destination in the PI tag.

Case: This will allow for IT to monitor the network path taken in communication from one site to another. If the route has changed in the communication of devices, we will be able to track it in PI and know exactly when the route changed.

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.

Smart Connector foo DeltaV should let user configure some default attributes for tags created:
- User should be able to define what the default point security should be
- User should be able to decide if tags should be created as Poll or Advise

The IEEE specification of the IEEE C37.118 protocol does not specify if analog data should be singed or unsigned for 16-bit integers. The currently the PI Interface for IEEE C37.118 represents these values as exclusively unsigned. Both types should be configurable in the interface

Currently, the interface does not have any means to convert timestamp values (i.e. not the actual timestamps corresponding to values), such as InstructionStart, to account for timezone differences.  Therefore, the timestamps have to be manually adjusted to account for timezone differences once it reaches the archives. 

Having to manually adjust the timestamp causes issues further down the line, such as with PItoPI, and creates unnecessary overhead in AF to do said conversion.

PI APS is now not able to rename a PI Point name. If the item name is changed on the Datasource side we wish that APS rename the Pi Point.