Release a new version of the interface where it does not depend on the 1.x version of log4j rather the most recent and secure version of log4j. This is to improve security.

Note: The Log4j 1.x version installed with the interface is not a part of the security vulnerabilities found in 2021.

Update PI Interface for GE HABConnect codebase to 64bit to make use of latest Habconnect API v5.11.

Up to PI EFGen 4.0, we were able to backfill OOO Event Frames by simply inputting the start and end time of the corresponding period. Since 4.1, this must be done in a per-event basis, since larger time ranges are modified so that RST matches the start of the latest active event and OOO EFs are missed.

PI Interfaces for Batch allow source batches to be merged into one merge batch and then store the source batch properties as extended properties on the event frame. There should be an option to show source batches of merged batches as child event frames rather than extended properties.

The interface can retrieves Report events [Event,value="Report"].
Within these events, [Descript] - parameter returning "category" from SQL database.
We could not retrieve "description" column contents from the SQL DB [BReportEvent] table.
See case 00902899.

Have the functionality to change the Point Type from the PSSS, because it cannot edit Point Type for existing PI Points.

We are in need of a PI Batch/AF Events Interface to store data from Honeywell Experion Batch or Honeywell Procedure Analyst into PI Asset Framework.

Add a feature that performs a verification check of the data in PI against data in the DeltaV Historian and provide a report of any missing or mismatched data.

Add a feature that performs a verification check of the data in PI against data in the DeltaV Historian and provide a report of any missing or mismatched data.

PI Interface for EnergyAxis to support REXU-EA meter types.

it would be useful to have an interface that can connect and retrieve data from OPC UA server. it will help to avoid using any additional software for "downgrading" the protocol to OPC at client side.

We see some value in getting a read/write interface with Itron's MV90 billing system database. Being able to see billing interval billing data in PI would be valuable as well as being able to transfer billing data between other partners via PI to PI interface would solve a rather complex data exchange issue going on in the utility space.

Add support for workgroups for PI Interface for Emerson DeltaV Syncade

Currently, UniInt-based interfaces will reload a tag if edits are detected on any of the PI Point attributes. This is not ideal as edits to non-key attributes (such as EngUnits) will still cause a tag to be reloaded, potentially leading to data source issues if large numbers of edits are made.

Requesting to add the option to filter out edits to PI Point attributes that are not used by the interface to avoid unnecessary reloads.

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

Add PI Interface for OPC XML-DA documents to the Live Library

The PI XMLTool that is bundled with the PI Interface for OPC XML-DA does not function with Windows Server 2019 even though the PI Interface for OPC XML-DA itself is documented to function. Can the client tool please be worked on so that it will function with the same operating systems that the interface does. This is a key component to aide in the troubleshooting of the interface as well as determining the correct instrumenttag field by the browsing the XML-DA tags on the server.