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

General

    Have the option to discover new data streams, auto-select them, and save data retrieved for them, all with a single query to the data source, similar to PI Connectors

    Background + problem When PI Connector tries to save data for a tag that does not already exist (e.g. data for a new piece of equipment), it will create that tag automatically. This is very convenient, but it sometimes led to issues where data tha...
    Kenneth Barber about 3 hours ago in AVEVA™ Adapters / General 0 No status

    For PI Points created by AVEVA Adapters, use the point class "base" instead of "classic" if the PI Point does not use "classic"-specific PI Point attributes

    When an AVEVA Adapter creates a new PI Point, it always uses the point class "classic", even if none of the attributes that are specific to this point class are ever used. Instead, AVEVA Adapters should create PI Points using the point class "base...
    Kenneth Barber 5 days ago in AVEVA™ Adapters / General 0 No status

    Be able to save, name, and easily reuse query strings for data discoveries

    Currently, the query string of a data discovery is part of the data discovery, and once a data discovery is run, it cannot be rerun since part what identifies a discovery is the time at which it ran. This is not a flaw, but rather a part of the de...
    Kenneth Barber 12 days ago in AVEVA™ Adapters / General 0 No status

    Allow multiple instances of an AVEVA Adapter to exist on the same server without using Docker

    Currently, there can be only 1 instance of a specific AVEVA Adapter on each server if Docker is not used. However, within that instance, multiple components and data sources can be configured. This is convenient, but then the service account for t...
    Kenneth Barber about 1 month ago in AVEVA™ Adapters / General 0 No status

    Rename services to reflect the renaming of the product

    AVEVA Adapters were previously called "PI Adapters", but the name of any AVEVA Adapter service begins with "PIAdapter". The PI To CONNECT Agent was previously called the "PI To Data Hub Agent", but the service name is still "PIToDataHubAgent". I'm...
    Kenneth Barber 18 days 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 over 1 year ago in AVEVA™ Adapters / General 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 9 months 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 about 4 years ago in AVEVA™ Adapters / General 4 Future consideration

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

    Support https instead of http only

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