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.

For the PI BACnet interface, the following error can be returned from the device for a particular request and then written into the message logs:

" >> BACnet error packet received. Error Code: 31; Error Desc: Unknown Object; InvokeID: 0"

However, this log message does not include which request caused the error. This error message should include which PI point resulted in this error so that the customer can easily find the relevant point and either correct the configuration or investigate why the device cannot find the object.

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.

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 support for BACnet Setpoint objects in the PI BACnet 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.

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

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.

This is for SNMP version 1.6.3.0, the following message is printed every scan frequency:

"Scan class <scan class number> for device <IP address> will be skipped due to previous pending requests"

And this needs to be throttled as the logs may be get filled up quickly with this type of messages.

Note: This was previously Enhancement 124938.

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

Add functionality to treat the data as "bad" and send a digital state instead, when status flags are sent with the event and status bits are set to TRUE. Right now, the data is sent to PI and marked as "questionable".

Note: This was previously Enhancement 125605.

There needs to be a 64-bit version of the CatGH5 interface that is capable of parallel processing in order to efficiently process an quantity of data/files (that the 32-bit version is not up to the task of handling well).

Currently only POINT/ANALOG fields support COUNT. This request would be to enhance the interface to additionally support the COUNT field.

We would like the PI CAISO interface to parse through the .XML files and exclude XMLs that contain certain specified <Batch Types>. Only certain batch types contain valid data for consumption.

If the RTU provides a timestamp of 0 when using RTU provided timestamps, which does not conform to the DNP3 spec, allow the option to timestamp the event with PI time or drop the event altogether.

Note: This was previously Enhancement 123208.

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.