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

    Documentation of EDS Modbus TCP Adapter needs to be updated on removed 32-bit register support for Modbus TCP Adapter

    Challenge: The current version of PI Adapter for Modbus TCP does not any longer support 32-bit Holding/Input registers as this is outside of the Modbus specifications. However, in some cases, 32-bit register values have to be read from 16-bit regi...
    Hans-Otto Weinhold over 2 years ago in Edge Data Store / Ingress 0 Planned

    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 over 1 year ago in AVEVA™ Adapters / New Connectivity 0 No status

    CONNECT Agent for AVEVA Plant SCADA (Citect)

    AVEVA Plant SCADA 2020r2 and newer, has an OPC UA Server, so the AVEVA Adaptor for OPC UA can be used to send data to CONNECT data services (AVEVA Data Hub). However native connectivity like the PI-to-CONNECT Agent or the System Platform Connector...
    Guest over 1 year ago in AVEVA™ Adapters / New Connectivity 0 No status

    Disable Meta data collection for the PI Connector for Wonderware Historian

    We would like to have a way to disable the PI Connector for Wonderware Historian's ability to  collect descriptions and engineering units in the historian.  These can be incorrect at times in the Wonderware Historian.
    Guest over 3 years ago in PI Connectors / PI Connector for Wonderware Historian 1 No status

    PI Connector for Cygnet - Historical Data Recovery

    The PI Connector for Cygnet is normally used for real-time data acquisition. But, some times it becomes necessary to migrate large volumes of historical data between Cygnet and PI. There is a back filling application that can be used to do this, ...
    Guest over 3 years ago in PI Connectors / PI Connector for Wonderware Historian 0 No status

    Do not bundle PI Adapters with EDS

    Reduce the footprint of EDS by not bundling adapters with EDS but instead have them be a separate installation so only the desired adapters end up being installed on the device. It will also allow easier for a clearer process when an adapter needs...
    Gabriel Verreault over 3 years ago in Edge Data Store / Installation 1 Future consideration

    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 almost 3 years ago in Edge Data Store / General 1 Declined

    Use Wonderware tags MinimumEUValue and MaximumEUValue to configure AF attributes limits/traits

    In addition to historian tags, the PI Connector for Wonderware Historian collects many metadata (see attached screen shot about a tank). Part of these are MinimumEUValue MaximumEUValue It could be really worth if connector could come with...
    David_CHATEL almost 3 years ago in PI Connectors / PI Connector for Wonderware Historian 0 No status

    Customer is seeking WW connector to collect data from WW historian but with same naming convention of existing tags

    Customer is seeking WW connector to collect data from WW historian but with same naming convention of existing tags. Existing tags were reading from "FxBias interfaces" and in need to let them read from WW historian thru WW connector. WW connect...
    Guest over 3 years ago in PI Connectors / PI Connector for Wonderware Historian 1 No status

    Optionally not include Galaxy name

    Add capability to include Galaxy name or not and include specific areas or not. In the current system I am working with, the primary and backup WW Galaxies are named differently. This causes the Connector to build separate trees in AF.
    Guest over 3 years ago in PI Connectors / PI Connector for Wonderware Historian 0 No status