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

Clear

Ideas

    Showing 31 of 5221

    Ability to log PI DataLink function usage

    A centralized place to log PI DataLink usage, including the following information, The formula of the function Search requests made by PI DataLink The client/user information
    Jeccie Qiu about 3 years ago in AVEVA™ PI DataLink™ / Settings 1 No status

    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 over 3 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 over 3 years ago in PI Interfaces / PI Interface for RDBMS 0 No status

    RDBMS Interface - Full Sync and Annotations

    The PI SDK writes required for setting annotation values with the exdesc and RDBMS interface are not compatible with Full Synchronization. Make this compatible.
    Matt Voll over 3 years ago in PI Interfaces / PI Interface for RDBMS 0 No status

    Setting for Update Interval That Can Be Specified at the Excel Workbook Level

    The customer would like to see an Update interval that can be specified at the Excel workbook level. The use case is that they run multiple Excel spreadsheets at the same time but need different update intervals for each. Workaround: use VBA to ac...
    Guest over 3 years ago in AVEVA™ PI DataLink™ / Settings 0 Declined

    Only include the worksheet in a formula if a sheet other than the one the formula resides is referenced

    Copying formulas from one sheet to another is tedious because you must replace the sheet that Datalink forces in with the sheet you paste into even if all referenced cells are all on the same sheet. Please make the behavior similar to how Excel do...
    Sublette-Sanofi over 3 years ago in AVEVA™ PI DataLink™ / Settings 0 No status

    Restrict the "Root path" field on the "Current Value" menu to only display PI Data Archive servers previously connected to this machine.

    We have 12 PI Data Archive Servers and another 12 PI AF Systems. I currently have to sort through a list of 124 "servers" when I setup to collect some PI data. Many of the 124 "servers" are old servers no longer in use or databases under PI AF Sys...
    DavidMFairchild over 3 years ago in AVEVA™ PI DataLink™ / Settings 0 No status

    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 insta...
    Guest over 3 years ago in PI Interfaces / PI Interface for RDBMS 1 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 over 3 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 over 3 years ago in PI Interfaces / PI Interface for RDBMS 0 No status