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 134 of 5222

    PI to Connect Agent instance Failover

    on behalf of customer: We would like to see agent failover added to PI to Connect. The PI System already provides high availability, and extending this capability into PI to Connect would deliver a resilient hybrid infrastructure end-to-end. Histo...
    omar alomari 2 months ago in PI to CONNECT / General 1 No status

    PI to Connect agent needs to be collective aware

    The PI to Connect agent is not collective aware. Instead, only a single archive can be mapped to the agent. Please allow the PI to Connect agent to utilize collectives. This increases the system's overall resiliency.
    Devin over 3 years ago in PI to CONNECT / General 2 In development

    PI to CONNECT should have a verification tool to make sure there are no gaps in the data

    When using PI to CONNECT there might be errors in the transfer due to disconnections or other network issues. Ideally PI to CONNECT would have a tool to verify if the data was properly transferred by checking the data.
    Fabio Dani 6 months ago in PI to CONNECT / General 0 No status

    Support security baselining

    As a PI administrator, I need to baseline the security configuration of my PI System to ensure OSIsoft security best practices are followed. Below is a list of requested features. Baseline verification (read-only) for PI Data Archive: - PI Data ...
    Guest over 3 years ago in Developer Resources / PI System Deployment Tests 2 No status

    Allow Multiple Data Archives per PI to CONNECT Agent

    Allowing data transfer for tags from multiple PI Data Archives with one agent will help to cut down on the number of agent services, and therefore machines, that need to be involved to send data from PI to CONNECT.
    Guest over 3 years ago in PI to CONNECT 0 In development

    Root Element should be added to the transfer

    When we create a transfer from PI AF there is a way to select a Root Element to start the search. However the root element from where we start the search is not added to the transfer. Ideally we would be able to add the root element into the trans...
    Fabio Dani about 1 month ago in PI to CONNECT / General 0 No status

    Monitor PI to CONNECT connection

    Sometimes, the PI to CONNECT agent seems to have some interruption in replicating data from a PI Data Archive into CONNECT data services. It would be beneficial to have some more monitoring options (in addition to what is available through the CON...
    Guest over 3 years ago in PI to CONNECT 1 In development

    Add ability to uncheck or remove attributes from existing transfer

    Transfers are initially added by searching and then selecting elements then attributes to add. When we want to edit the transfer, we are only able to remove entire elements, not by attributes. This became an issue when we later found that we had a...
    Guest about 1 year ago in PI to CONNECT / General 0 No status

    Allow selective AF Database indexing

    The PI to CONNECT agent will index the whole AF server. On big ones, this is tedious (one took more than 12 hours) - would prefer to have the ability to choose either on the agent or from CONNECT which AF databases to index.
    Guest almost 3 years ago in PI to CONNECT / General 1 No status

    Remove installation kits' dependency on write permission to root C:\.

    Some organizations do not provide admin accounts with write permission to the root C:\ directory. The install kits of most PI products copy the setup.ini to C:\pisetup.ini, and then write the logs to C:\ before moving them to %pipc%\dat, both of w...
    Guest over 3 years ago in AVEVA™ PI Server / Installation 4 No status