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 45

    Native MQTT Publishing (Egress) to Support Unified Namespace (UNS) Architectures

    Description & Use Case: As the manufacturing industry shifts toward Industry 4.0 and Unified Namespace (UNS) architectures, data must flow seamlessly between all systems in a publish/subscribe model. The AVEVA PI System is exceptional at inges...
    Mandeep Sidhu 5 days ago in AVEVA™ Adapters / AVEVA Adapter for MQTT 0 No status

    Allow session persistence to support true QoS 2 data collection and backfill of events after a data source disconnection

    It appears that regarding Session Persistence (persistent vs clean session), the Adapter hardcodes setting the Clean Session Flag for the generic data source (Sparkplug doesn’t QoS 2 nor session persistence) to true. This should be a user-defined ...
    Daniel Lopez 3 days ago in AVEVA™ Adapters / AVEVA Adapter for MQTT 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

    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

    Allow PI Adapter for MQTT (Generic) to process non-json payloads

    Some MQTT devices do not send json payloads; for example, some devices send a single value as the payload for a specific topic. It would be beneficial for the adapter to be able to handle this rather than to convert these payloads into json befo...
    Guest over 3 years ago in AVEVA™ Adapters / AVEVA Adapter for MQTT 3 In development

    Configurable Hostname/IP Identifier for OMF Health Egress

    The health tags and AF structure is created with the following naming pattern by default: <machine hostname>.<adapter type> To support modern containerized deployment models, please consider adding a configurable field that allows cust...
    Bharat Rawat about 1 month ago in AVEVA™ Adapters / AVEVA Adapter for MQTT 0 No status

    Enable OmfEgress component to be configurable by instance (by component)

    In our process we wish to send a different set of data to different PI environments. For instance we would like all data to egress to the PROD environment while only egress a subset of data to the DEV environment, in which we don't need all the da...
    Guest over 3 years ago in AVEVA™ Adapters / General 7 Future consideration