We have encountered a situation where we were unable to write out-of-order data to PI through the buffer subsystem from an interface, apparently because the buffer subsystem was not yet fully initialized when the interface connected to it. Please implement an appropriate wait cycle at interface startup, to ensure that the buffer subsystem (on which the interface is dependent) is fully initialized and available before permitting the interface to complete its connection and initialization.

Note the case in question arose when the interface service was configured with a dependency on the PI Buffer Subsystem service.

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.

Ability to clamp or ignore values outside a threshold.
Example would be to clamp the low value to 'zero' attribute and/or a high value at 'span' - many xmtrs read erratically when at limit (e.g., an empty flow transmitter often reads negative)

Is there an option in DNP3 driver (In fact at TCP level) to make it listen on a certain (usually 20000 for DNP3)? In era of IoT devices, most devices are sleeping devices, they wake up usually once a day and push data to DNP3 Master (PI), however DNP3 PI collector doesn't support this model. As an enduser I would like to utilize this mode of operation at our plant. FYI, there are other products e.g. Citect SCADA and ClearSCADA use two separate ports for Inbound and outbound DNP3 traffic to use the both modes simultaneously.

While PI Connector for UFL supports FOREACH (CsvGetItem(__Message, char(13))) to allow using a Carriage Return as a delimiter, it does not support Serial input.
This leaves PI Interface for UFL the only option to work with Serial input. Please allow to use a hex value as a delimiter, which will allow to specify a Carriage Return (0x0D) as a delimiter.

There should be a way to configure the PI UFL interface to both discard duplicate events (same value at the same timestamp) and record multiple unique values for the same timestamp when these events come from multiple data files.

For example, if multiple data files contain the following entries:

(Timestamp)  (Value)
11:00:00      ABC
11:00:00      ABC
11:00:00      XYZ

The following data should be archived:

(Timestamp) (Value)
11:00:00 ABC
11:00:00 XYZ

As a PI System User I would like to archive and analyse VT_UI4 data using the PI System.

Allow the Event Frame Templates to be fully customizable. This will give the flexibility to remove attributes like Product from the PIBatch and Procedure, as it is represented in the lower levels of Event Frames.

Add a function that can be used in the UFL Configuration File to perform bitwise operations. For example, a function similar to the AND operator in Performance Equations and Asset Analytics.

CNI interface should support message 25. Currently, we do not support any message beyond 22.

When using the interface to gather data for hundreds of SNMP devices, managing the .pwd file becomes very burdensome due to an inability to format the file. Comments are helpful in sorting devices, but they are removed upon encryption. It would be nice to see a tool that helps with the management of passwords.

hen the primary Interface becomes available and healthy again, it becomes "back up". I need the primary Interface to become the "primary" whenever it is healthy.

https://pisquare.osisoft.com/thread/42591-revert-back-to-primary-data-collector

In PI Event Frames Interface Manager, there needs to be a 'Are you sure?' pop up after clicking "Remove Interface" button to prevent accidental deletion of interfaces.

When validating/troubleshooting data flow issues, it would be helpful to see metrics on which interfaces are actively sending data to the buffering subsystem via Buffering Manager. If an interface is in a bad state or stopped, it would be obvious which interface is having issues since the count would be zero. Currently the counts in the buffer queue are for all interfaces, so this only gives the user an idea on whether the buffer subsystem is forwarding data to the data archive, without knowing which interfaces this data is coming from.

PI ICU rejects options IGNORE5TH and IGNOREFLDMSEC at the same time. When modeling teams change MEAS fields often, IGNORE5TH is extremely useful to keep data history contiguous. When using field time that is stamped by the EMS, milliseconds are not useful.

Please remove the constraint on having both options.

Add OMF health function to Citect interface.