Skip to Main Content
AVEVA™ PI System™ Feedback Portal

Welcome to our new 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

PI Interface for RDBMS

Showing 12 of 4804

RDBMS - Failover delay for specific situation when the interface encounters a ODBC failure/disconnect

RDBMS - Failover delay for specific situation when the interface encounters a ODBC failure/disconnect
AlexMeade over 1 year ago in PI Interfaces / PI Interface for RDBMS 0 No Status

RDBMS Interface version that support the failovertime > 20s (UFO_Interval)

If you have a query that lasts longer than 40s and a phase2 failover configuration is used. The interfaces switch constantly from primary to secondary and viceversa. With the parameter "UFO interval" you can control this behavior. However, this pa...
MiguelPalomo almost 2 years ago in PI Interfaces / PI Interface for RDBMS 1 Declined

New start-up parameter /SYNC_TIME defining a floating-window during which the interface will keep a RDB table in sync with PI data archive

The new RDBMSPI param:  /SYNC_TIME=rel_start_time,rel_end_time   for instance /SYNC_TIME=*-6h,*+1h When set, the interface: - after each execution of a query, which shall have the same "floating" window in its WHERE clause; for instance: SE...
Guest almost 2 years ago in PI Interfaces / PI Interface for RDBMS 1 No Status

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 2 years ago in PI Interfaces / PI Interface for RDBMS 0 Future Consideration

Add option to select interface behavior for bad timestamps (PI RDBMS)

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...
Guest almost 2 years ago in PI Interfaces / PI Interface for RDBMS 0 No Status

Accept weeks and years in the relative time syntax for history recovery start and end times

For whatever reason, times such as *-1w or *-1y are not accepted, but times such as *-1mo and *-1d are OK. Please make the PI Interface for RDBMS accept the same relative times that other PI programs accept.
Kenneth Barber almost 2 years ago in PI Interfaces / PI Interface for RDBMS 0 No Status

Accept the dd-mmm-yyyy format in the absolute time syntax for history recovery start and end times

The PI Interface for RDBMS currently accepts the format dd-mmm-yy but not the format dd-mmm-yyyy for history recovery start and end times. The former format lacks the century, so the year is ambiguous. The latter format solves this problem and so...
Kenneth Barber almost 2 years ago in PI Interfaces / PI Interface for RDBMS 0 No Status

History recovery from multiple tags with one output tag

I have a scan-based output point writing multiple PI values to the relational database as described here: https://livelibrary.osisoft.com/LiveLibrary/content/en/int-rdbms-v4/GUID-1A194D2B-388B-4FD7-8B82-D85EDDBBC572 I would like to perform histo...
Guest almost 2 years ago in PI Interfaces / PI Interface for RDBMS 0 No Status

Alert user when the interface discards values

Example:  When using a distribution tag, the number of tags returned and number of values sent to PI can be mismatched, due to missing aliases or data that does not need to be collected. It would be helpful to identify what values are dropped or ...
Guest almost 2 years ago in PI Interfaces / PI Interface for RDBMS 0 No Status

RDBMS time stamp precision

Currently the ODBC connection is configured with a SQL date time parameter when retrieving the TS parameter (snapshot time stamp). Due to the fact lots of sources system having more precision in their time stamps, it makes it hard to compair sour...
meierke1 almost 2 years ago in PI Interfaces / PI Interface for RDBMS 0 No Status