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 14 of 5194

    Migration from interface to connector

    Would like a way to migrate from interface to connector as easily as possible.
    Guest over 3 years ago in PI Connectors / PI Connector for BACnet 2 No status

    Add failover capability for the BACnet Connector.

    Failover similar to the UFO available for UNIint interfaces.  Warm failover would be sufficient, although I'm sure there are some who would like cold and hot as well.
    Chris Wozniak over 3 years ago in PI Connectors / PI Connector for BACnet 1 No status

    BACnet SC/SuperConnect Support

    Support for the BACnet SC/SuperConnect protocol for the PI Adapter, PI Connector, or PI Interface.
    Connor Hawkins almost 2 years ago in PI Connectors / PI Connector for BACnet 4 No status

    trend log objects (BACnet object type 20) available from the connector

    BACnet trendlog object present the opportunity to buffer at the edge where the data is collected and to gracefully recover from comms outages if data collection has been impacted. I would suspect the trendlog object could be handled similarly to ...
    Guest over 3 years ago in PI Connectors / PI Connector for BACnet 0 No status

    Support System States for the Adapter for Azure Event Hubs

    The data passed through the Adapter for Azure Event Hubs can be very dynamic in its configuration. It would be useful to be able to send system states to indicate bad data, and possibly the nature of that bad data. In the same way that interfaces ...
    Mike Horrocks almost 2 years ago in AVEVA™ Adapters / AVEVA Adapter for Azure Event Hubs 2 No status

    Make the connector a BACnet Device (get a BTL listing)

    Some devices can only send COV notifications to other BACnet devices. Since the Connector is not a device and does not respond to who-is messages (and does not listen on port 47808), the connector is unable to utilize COV subscriptions for these d...
    Paul Kim over 3 years ago in PI Connectors / PI Connector for BACnet 0 No status

    Suppress the creation of "Status Flag" PI Points

    The end-user would like to suppress the creation of the "Status Flag" PI Points, as they wish to keep their point count to a minimum due to the license-enforced point limit.
    Guest over 3 years ago in PI Connectors / PI Connector for BACnet 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 about 1 year ago in AVEVA™ Adapters / AVEVA Adapter for Azure Event Hubs 0 No status

    Program objects (BACnet object type 16) also bought through by the connector

    The program object description is often very useful to understand what the various object instances relate to. At our site the description holds the Asset designation and that would allow correct assignment of the analogue and binary object instan...
    Guest over 3 years ago in PI Connectors / PI Connector for BACnet 0 No status

    Log device information when the Connector receives errors from a device

    Currently the Connector logs when it receives errors, but does not print information that can be used to determine which device is reporting the errors. We currently need to perform a wireshark trace to look at the individual packets to determine...
    Guest over 3 years ago in PI Connectors / PI Connector for BACnet 0 No status