When the PI RDBMS Interface gets a bad timestamp from the source RDB that it cannot coerce into a PI Timestamp, the interface attempts to use the current timestamp instead and logs the following error:

"pitm_settime() error - 15002. Using current time."

The interface should instead include an option that controls what to do in this situation. The potential options would be to either discard the event entirely after logging an appropriate error or to use the current timestamp of when the event was retrieved (Also logging an appropriate warning).

I had a case (794719) with a customer who would like to have SNMPTrap interface available on our live library so that he can browse online instead of downloading the user manual.
Thank you!

allow instruction level data to use batch level start time. Add an option to allow this. use case: the instruction level start time is the time when the DOT should be ramped up or down.  The batch start time is a few minutes before that timestamp.  To get the turbines adjusted in time, they need to use the batch start time.  This gives the operator enough time to adjust the set point and have the new target met by the instruction start time.

The new CSI UCOS API now supports a "bumpless download".

"CSI has recently added what they call a “bumpless download” feature to their UBrowser application that the interface uses to communicate with the database. What this does is allows the database to be updated without stopping the service. "

Please implement this feature.

Note: This was previously Enhancement 121741.

Create a new function indicating if the string can be turned into a number. For example, IsNumber() function could return 1 if the string can be turned into a number 0 if not.

OPC HDA Interface would be enhanced to use  switch '/outputsnaptime'.  For output tags, the interface would use the timestamp from the original event that triggered the output to timestamp the data.

Note: This was previously Enhancement 124754.

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.

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.

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 PI Interface for OPC XML-DA documents to the Live Library

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.

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.

There is no easy way to verify that historical data moved from one PI Server to another using the PI to PI Interface isn't missing data on the target PI Server.

As a PI System User, I would like to archive values for the VT_UI2 data type using the PI System.

Add the ability to create custom Performance tag names for the PI Batch Interfaces.

For systems with numerous batch interfaces the Performance tag naming convention does not intuitively distinguish between interface instances since the Interface ID is the only unique text in the tag name.