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

    AVEVA Adapter for WITSML

    We need an Adapter for WITSML to get data from drilling, completions, and interventions of oil wells to CONNECT data services, so the data can be shared between multiple stakeholders.
    Guest about 2 years ago in AVEVA™ Adapters / New Connectivity 0 No status

    change Http code 101 message from "No Content" to "Switching Protocols" on PI Web API

    Hi AVEVA Team we found the issue about PI Web API. Once a client making connection to PIWebAPI over websocket (open chanel), PiWebAPI response with "HTTP code 101 No Content" instead of "HTTP code 101 Switching Protocols" Can we change response me...
    Guest over 2 years ago in Developer Resources / PI Web API Samples 0 No status

    PI Manual Logger Web でのエラー境界線のカスタマイズ

    グリッド ビューでは、オペレーターは制限列の薄い黄色のエラー境界線を確認するのが困難です。何かが制限違反であることを簡単に確認できるように、エラー境界線の太さと色をカスタマイズする方法を希望します。
    Guest over 2 years ago in AVEVA™ PI Vision™ / Manual Data Entry / PI Manual Logger 0 No status

    PI マニュアル ロガーWebのツアー スケジュール設定

    PI Manual Logger PC では、スケジュールに従ってツアーを実行するように設定できます。これにより、アプリケーションがツアーを最も近い時間で実行するのではなく、ツアーの実行時間を設定することができます。 PI Manual Logger Web では、ツアー スケジュール設定は考慮されません。定期的なツアー スケジュールに従って、PI Manual Logger Web にツアー実行の機能を追加を希望します。
    Guest over 2 years ago in AVEVA™ PI Vision™ / Manual Data Entry / PI Manual Logger 0 No status

    Allow the BACnet Adapter to handle responses with an LVT that does not match the request

    Currently the BACnet Adapter expects devices to respond with the same "Length Value, and Type" (LVT) value as the request. When this occurs the BACnet Adapter cannot parse the data in the response. For example: Request from Adapter, LVT=1 Response...
    Nico Cha over 2 years ago in AVEVA™ Adapters / AVEVA Adapter for BACnet 0 No status

    Addition of substitution parameters in DefaultStreamIdPattern -> specify a ValueField for it to read from

    People wanting to use a single EventHub and Container holding events from many sources with common attribute naming. Want to be able to differentiate the naming of the pi tags based on source. Being able to substitute a unique source identifier (s...
    Guest over 2 years ago in AVEVA™ Adapters / AVEVA Adapter for Azure Event Hubs 0 No status

    Error message should be generated for the Modbus request time out

    After request time out, Modbus adapter should generate an error as time out after specified duration set by user.
    Guest over 2 years ago in AVEVA™ Adapters / AVEVA Adapter for Modbus TCP 0 No status

    PI Adapters should not overwrite parameters configured in the stream in ADH

    When we change any override parameters for a stream in ADH an adapter restart will overwrite what we configure in the stream. One example is changing the interpolation method for a stream in ADH because we want to see the trend as step. Every time...
    Fabio Dani about 3 years ago in AVEVA™ Adapters / General 0 No status

    Don't change product version information response structure

    The design of the /productinformation response has changed between EDS 2020 and EDS 2023 Patch 1. Our application missed the new position of the version string so I had to change code to catch it. I know the product has shipped so there is nothing...
    Guest over 3 years ago in Edge Data Store / General 1 Declined

    Accept HEX numbers for Register offsets in data selection

    Most modbus equipment providers provide information using registers in Hex format i.e. 0x0000 ~ 0xFFFF. It would be nice if the offset could accept this to avoid error in conversions HEX to DEC. Would make things alot more seamless/easier.
    Matthew Kishe over 3 years ago in AVEVA™ Adapters / AVEVA Adapter for Modbus TCP 0 Future consideration