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 71

    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 2 months ago in AVEVA™ PI Server / Security 0 No status

     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 2 months ago in AVEVA™ PI Server / Security 8 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

    Start/stop components to be retained on restart

    Currently it is possible to stop a component for a running adapter. However, if the adapter is restarted the component will automatically start up. It would allow for extra control during commissioning, downtime, incidents, etc. to be able to disa...
    Mike Horrocks 4 months ago in AVEVA™ Adapters / General 0 No status

    Support for additional Complex Data Types for all Adapters

    Request to enhance the Adapters to support more complex data types, specifically value/quality pairs. While some Adapters currently support geolocation and coordinate complex data types, they do not all support value/quality data types. In industr...
    Derek Wong about 1 year ago in AVEVA™ Adapters / General 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 4 months ago in AVEVA™ PI Server / Security 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

    Include buffering metrics in adapter health

    In the OmfEgress component in adapter health the metrics are limited to DeviceStatus, and IO rate. Another key metric for this component is the buffering state. To keep it simple it would be useful to have the number of events in the buffer. This ...
    Mike Horrocks about 1 year ago in AVEVA™ Adapters / General 0 No status

    Allow remote configuration

    Adapters are currently only listening on localhost (127.0.0.1) causing them to be only accessible locally. For docker containers, they can only be accessed from within the container or directly on the host (with the --network host switch which res...
    Gabriel Verreault over 3 years ago in AVEVA™ Adapters / General 3 Future consideration

    Support https instead of http only

    No description provided
    Gabriel Verreault over 3 years ago in AVEVA™ Adapters / General 2 Future consideration