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

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.

Allow for monthly scan intervals for scan classes. i.e. "scan monthly on the first hour of the first day of every month".

(Posted on behalf of our customer)

It can reduce the chance of startup failure because of the connection to PI Data Archive time-out. It's also helpful if interface can reduce time to get PI point information from PI Data Archive.

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

1. Having the capability of acknowledging the message in the PI Buffer GUI and removing the "red flag" when messages acknoledged.
2. Having the Buffer updated automatically when a tag is renamed, without having to restart the buffer.

We use the Phoenix Contact Firewall with the OPC Inspector. When the OPC server restarts or breaks the connection for a few seconds, the firewall blocks all ports except port 135. After initial connection through this port, new firewall rules are dynamically established for DCOM connections. If connection break to OPC Server we have to restart interface manually.

As a PI System Admin, I would like to see a confirmation window (acceptation pop-up message), when deleting Interface instances in PI Event Frames Interface Manager. This would minimize the deletion of the instances by error.

I would like the PI UFL Interface to be able to directly read from input files that are in non-UNC paths such as Azure File share, so I do not need to periodically copy the input files into another path.

When an interface fails writing to a DCS system, the interface writes a failure status to the output tag and goes on.  User has requested an option to have an output tag retry after write failure. It would be good to have this functionality in all uniint interfaces as they are recompiled, starting with the OPC DA interface, also to have this added to PI Connectors. Retries could stop after x retries of 1 minute retries, or when a new output value comes in. Or some other policy could be worked out.

PI-SNMPTrap interface currently only has support for SNMPv1 and SNMPv2C trap. Feature request for PI-SNMPTrap interface to include support for SNMPv3 trap.

Monitoring of snmp traps originating from CISCO switch devices require support for SNMPv3 trap.

There are some performance counters that are Date and Time based.

PI PerfMon tags have to be configured as Float32 or Int32 and at PI AF it has to be converted by using PI Analysis or Formulas. Would be easier to configure, maintenance and to build reports if there is a direct way.

Create an option to allow the PI Interface for UFL to delete files with the read-only attribute.

As of version 3.8.1 COLD failover is no longer supported by the PI to PI Interface (https://techsupport.osisoft.com/Troubleshooting/Enhancements/19255OSI8). However, the PI Interface configuration utility still allows COLD failover to be selected. This leads to an invalid configuration and the interface refuses to start.

PI ICU should not allow the selection of COLD failover as it does not allow HOT failover, both of which are not supported by the interface.

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.

PI Interface for CA ISO ADS can extract data from XML fields. Under the Instruction Detail field, there are multiple MW, serviceType, and segNo fields. Presently, retrieving those values in a PI tag (for example, instrument tag "MW,ResID") returns values for all of the particular field under that resource ID.

It would be beneficial to be able to extract MW values for only one segNo or serviceType under the particular Resource ID, as getting all of the values at once does not make sense in a PI tag.

We currently use the Cybectec interface to relay information into our PI system. It is our understanding that the latest certified OS is Windows Server 2012 R2. We are currently going through a upgrade of our PI system and our standard OS for deployment is Windows 2019. We would like to request that the Cybectec interface is certified with Windows 2019 (or at least 2016) to ensure that we are supported in our environment. Using Windows Server 2012 R2 will require us to complete another upgrade (server) in 2023 as the OS will be end of life.

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.