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

AVEVA™ Adapters

    Showing 75

    Add the option "Ignore Bad_WaitingForInitialData Status"

    In the connectors there was the option "Ignore Bad_WaitingForInitialData Status", as described here. For gen 1 there was a need to edit the config files directly, and in gen 2 the option was integrated into the UI. Instead for the adapter I recent...
    sahilp over 2 years ago in AVEVA™ Adapters / AVEVA Adapter for OPC UA 0 No status

    Allow MQTT adapter to parse timestamps in local time without specifying a timezone suffix to each timestamp

    We would like the MQTT Adapter to be able to interpret timestamps in local time without needing to explicitly state the timezone or UTC offset in each timestamp, but for the adapter to always interpret the timestamps as being in a specific timezon...
    Guest over 3 years ago in AVEVA™ Adapters / AVEVA Adapter for MQTT 0 No status

    Allow default settings (eg. disable compression) for tags created by Adapters

    We would like to be able to specify default settings for tags created by the adapters. This would include things such as disabling compression for tags on this adapter (without disabling it as the default for all new tags on the Data Archive). Thi...
    Guest over 3 years ago in AVEVA™ Adapters / General 0 No status

    More control on MQTT parameters on the AVEVA Adapter for MQTT

    It would be nice to have more control on additional MQTT parameters for the AVEVA Adapter for MQTT. We are especially interested in having control on the QoS of the subscription. Setting this would give us more control in buffering, especially whe...
    Tombayu Hidayat about 1 year ago in AVEVA™ Adapters / AVEVA Adapter for MQTT 0 No status

    Defining "Scan Class" and "Poll" Capabilities in Aveva Adapter for Azure Event Hubs

    Define the "Scan Class" and "Poll" capabilities in the Aveva Adapter for Azure Event Hubs, similar to the functionality available in the Interface. Ensure the ability to manually select a "Scan Class" for PI Points and define it as "Poll".
    Guest over 1 year ago in AVEVA™ Adapters / AVEVA Adapter for Azure Event Hubs 0 No status

    Simplify the security configuration for OPC UA

    The newer OPC UA protocols have stricter security standards, which is good, but that makes configuring connections more difficult, especially with regard to the need to put in tunneling and open ports. It should be easier to establish a secure con...
    Laurie Dieffenbach over 1 year ago in AVEVA™ Adapters / AVEVA Adapter for OPC UA 0 No status

    Permit non-protected references

    The secrets references is a very useful addition but they are only permitted for "protected" parameters. It would be useful to also create references for non-protected parameters. Using references for non-protected parameters would help with creat...
    Mike Horrocks over 2 years ago in AVEVA™ Adapters / General 0 No status

    Support Kerberos for adapters on Linux

    Adapters are supported on Ubuntu, which also provides support for Kerberos (https://documentation.ubuntu.com/server/explanation/intro-to/kerberos/) Adding Kerberos support would increase the options for deploying adapters securely.
    Mike Horrocks 8 months ago in AVEVA™ Adapters / General 0 No status

    Include information from Json body in the stream name created by the MQTT Adapter

    As a system admin I would like to send mqtt messages from multiple devices to a single topic on an mqtt broker. Each message would contain data for the device along with a field to say which device the data has come from. Then I would like to use ...
    Guest over 3 years ago in AVEVA™ Adapters / AVEVA Adapter for MQTT 0 No status

    Adapters using Text parser be able to dynamically generate the stream name or ID based on fields of the text parsed

    This could be a good feature for any adapters that uses the text parser. MQTT, SDF, Azure Event Hubs. When using JsonPath or Xpath to parse a file or payload the stream name and stream id have to be hardcoded their value cannot be based on a the v...
    Randy Giguere over 2 years ago in AVEVA™ Adapters / General 0 No status