Skip to Main Content
AVEVA™ PI System™ Feedback Portal

Welcome to our feedback site!


We created this site to hear your enhancement ideas, suggestions and feedback about AVEVA products and services. All of the feedback you share here is monitored and reviewed by the AVEVA product managers.

To start, take a look at the ideas in the list below and VOTE for your favorite ideas submitted by other users. POST your own idea if it hasn’t been suggested yet. Include COMMENTS and share relevant business case details that will help our product team get more information on the suggestion. Please note that your ideas and comments are visible to all other users.


This page is for feedback specifically for AVEVA PI System. For links to our other feedback portals, please see the tab RESOURCES below.

ADD A NEW IDEA

Search results: PI Interfaces

Showing 18 of 94

PI BACnet interface doesn't say which PI point caused the device to return Error 31

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" H...
Guest almost 3 years ago in PI Interfaces / General 0 Completed

Log bad timestamps for the PI RDBMS Interface

When the PI RDBMS Interface gets a bad timestamp from the source RDB that it cannot coerce into a PI Timestamp, the actual bad timestamp received from the RDB should be logged as part of the error message. This would coincide with the following e...
Guest almost 3 years ago in PI Interfaces / PI Interface for RDBMS 0 Future consideration

Allow PI-ICU to Create/Edit Stored Credentials in Credential Manager

An issue we run into often is that most of the accounts that are used to run our interfaces (mostly OPC DA) are different from accounts we use to configure the interfaces. Because these interfaces run on different domains, we have to store an acco...
Brian Rock almost 3 years ago in PI Interfaces / PI Interface Configuration Utility (PI ICU) 4 No status

Improve collection of Event Viewer logs in PI Interface for Microsoft Windows Event Log

The PI Interface for Microsoft Windows Event Log can capture Event Viewer Logs. Some of the logs in sub-folders cannot be captured by the interface. This includes logs that store PI information, such as PI Vision with the log: OSIsoft-PIVisualizat...
Ted Birky 9 months ago in PI Interfaces / Other Interfaces 0 No status

Add functionality to the interface to adjust timestamps by a configurable amount

This enhancement would add the ability to adjust timestamps to the PI to PI Interface (Beyond the included options for clock drift and subseconds). Potentially, a setting could be supplied to change the timestamps on all data transferred by a spec...
Guest almost 3 years ago in PI Interfaces / PI to PI Interface 1 No status

PItoPI should switch from COLD to WARM failover instead of exiting

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, older versions supported COLD failover. In the case of upgrading the interfaces, ...
Guest almost 3 years ago in PI Interfaces / PI to PI Interface 2 No status

Enhance Visibility of Event Frame Generator/Batch Interface History Recovery Status

Currently when running any event frame generator interface (EFGen, PIFTBatch, etc.) in history recovery mode, there is no way to monitor progress of the actual history recovery. The only way to determine status is to check message logs periodicall...
Guest almost 3 years ago in PI Interfaces / Batch Interfaces 0 No status

Enable logging of 5.x batch interface messages to the local PI message log again

Message logs for 5.X Batch interfaces and Connectors are written to Windows Event Viewer instead of PI Message Logs as in previous versions. The Windows Event Log is extremely slow compared to viewing PI message logs, the filtering is worse, the m...
Guest about 2 years ago in PI Interfaces / Batch Interfaces 2 Declined

Enhance how batch interfaces write to the message logs

Batch interfaces should write their messages to the message logs using the Source1 and Source2 fields just like UniInt based interfaces. Currently, batch interfaces leave these 2 fields blank. Source1 should contain the process name or similar and...
Guest almost 3 years ago in PI Interfaces / Batch Interfaces 0 No status

When Citect Interface loses connection to a device, throttle errors relating to failed tag reads

OSI PI Citect Interface The interface will log an entry to the message log for every tag that it can't source data for. This is fine for a small number of tags that have not been able to read data from Citect. However, when a Citect Unit (eg PLC)...
Guest almost 3 years ago in PI Interfaces / Other Interfaces 0 No status