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 51 of 5194

    Securing the PI System

    As an ICS systems engineer, I need to understand and easily configure Authentication and Authorization settings to secure the PI System from the point of data collection to data access and remote display viewing.
    Guest over 3 years ago in AVEVA™ PI Server / Security 0 Declined

    Allow security to be set at AFAttribute level

    I want to give access to only some attributes on some elements to some users. Currently, the smallest granularity in AF Security is at the element, not attribute level. Sure there are some workarounds like creating derived templates, but it would ...
    Guest over 3 years ago in AVEVA™ PI Server / Security 0 Declined

    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

    PI AF Security - More Granularity Needed

    It would be helpful if AF's security model was more granular. For example (and please correct me if I am wrong), the same settings that allow someone to add/modify UOMs in AF is the same setting that allow someone to change the AF Sever name. This...
    Guest over 3 years ago in AVEVA™ PI Server / Security 1 Declined

    Support for data classification

    As a PI admin, I need to ensure that my data access and handling complies with classifications or levels of sensitivity. Background Regulations and compliance regimes require different controls for data based on the classification of data. Relat...
    Guest over 3 years ago in AVEVA™ PI Server / Security 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