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 111 of 5264

     Add OAuth 2.0 Token Exchange (RFC 8693) Support to PCS for PI

    Add native support for the OAuth 2.0 Token Exchange (RFC 8693) grant type in Platform Common Services (PCS) for PI when integrated with external identity providers such as Microsoft Entra ID. AIM must support exchanging externally issued access to...
    Lubos Mlcoch about 1 month ago in AVEVA™ PI Server / Security 8 No status

    Introduce compatibility between PCS AIM and Azure national cloud deployments

    Currently, Platform Common Services (PCS) for the PI System is incompatible with Azure national cloud deployments (e.g. A U.S. government Entra ID instance) due to limitations with Microsoft Graph global service, upon which PCS AVEVA Identity Mana...
    Ryan Biggins about 1 month ago in AVEVA™ PI Server / Security 0 No status

    Add option to view user's effective permissions or view CONNECT as user

    For data sharing with orgs that are not PI users, they would have to be added to the existing org's tenant. In this use case it is difficult to verify that a user has correct permissions and can only see data intended for them without using a test...
    Adam Bolin 28 days ago in PI to CONNECT / General 0 No status

    Allow AIM to directly authenticate users from other Identity Providers without CONNECT

    Currently, AIM can only use CONNECT or Microsoft Entra ID as the main Identity Provider. Configuring any other IDP requires federation through CONNECT. Allowing other IDPs to work directly with AIM without CONNECT would simplify the OIDC configura...
    Dan McGovern 3 months ago in AVEVA™ PI Server / Security 0 No status

    Allow mapping of OIDC clientcredential to multiple identities for Data archive

    Currently, when you create a mapping in PI Data archive for OIDC client credentals, you can only assign one identity.This severely limits the granularity and forces to add new identities to existing tags to grant extra permissions and is an easy s...
    Peter Speybrouck 3 months ago in AVEVA™ PI Server / Security 0 No status

    transfer element attribute description

    For example for PI Point Data Reference and String value types.
    Guest about 1 month ago in PI to CONNECT / General 0 No status

    Add configurable defaults for PI Point "Pointsecurity" and "Datasecurity"

    Read access to the PIPOINT table is required for most identities. Pointsecurity and Datasecurity currently use the settings on the PIPOINT table as the default. New points will generally give read access to most identities because of these default...
    Guest over 3 years ago in AVEVA™ PI Server / Security 2 No status

    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 4 months ago in PI to CONNECT / General 1 No status

    AIM (PCS) should have option to select a custom Alias name

    AVEVA Identity Manager app (PCS) should have option to select a custom DNS Alias name through the UI.
    Eduardo Miller 4 months ago in AVEVA™ PI Server / Security 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