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

    User rights for viewing analytics

    In many cases analytics should not be visible to everyone having right to view an AF-Database. Should be possible to direct whom should have view access to analytics. This is an extension to the obivious right to change analytics :)
    Guest over 3 years ago in AVEVA™ PI Server / Security 2 No status

    Security tool that allows management of PI Data Archive, Vision, and AF security settings

    PI System Administrators would benefit from a client or PI SMT extension that supports auditing and modifying user access. This includes mapping Active Directory roles to PI Identities, managing PI Database and Point access, managing AF Database a...
    Guest over 3 years ago in AVEVA™ PI Server / Security 0 No status

    Maximum security should be the default for the PI Data Archive and PI System Management Tools

    Maximum security by default would help encourage security best practices by: Making the best decision for customers that do not know or care about security "Rewarding" security-conscious customers with not having to expend effort to maximize secur...
    Kenneth Barber over 3 years ago in AVEVA™ PI Server / Security 0 No status

    IEC61850 encryption

    Implement TLS encryption between the IEC61850 Connector and the target IED(s) as per TS 62351.
    Gabriel Verreault over 3 years ago in PI Connectors / Other specific PI Connector 0 No status

    Discrimnate meta data changes of source items picked by PI Connector for IEC 60870-5-104

    We would like to discrimnate when the meta data around the data item changes on the source. The digital states related to it, the description, etc. If these change, the connector will change them on our PI server. Currently PI Data Archive.does n...
    Guest over 3 years ago in PI Connectors / Other specific PI Connector 0 No status

    Failover for e-terrahabitat

    I would like to be able to configure two identical instances of the e-terrahabitat connector on different computers, only one of which collects data from habitat at any given time. In the event that the primary instance or the machine that hosts i...
    Allison Muraski over 3 years ago in PI Connectors / Other specific PI Connector 1 No status

    PI Connector for MQTT - Support Backwards Compatibility

    Need the ability for PI Connector for MQTT Sparkplug to support MQTT brokers/servers that are < v3.1.1, specifically v3.1
    Guest over 3 years ago in PI Connectors / Other specific PI Connector 0 Declined

    PI Connector for HART-IP: Remove UoM from being added to PI point "descriptor" attribute

    Currently, the connector applies the UoM to the PI point "descriptor" attribute. If I want to write in a custom descriptor, every time I restart the connector, I then need to re-edit all of the points.
    Guest over 3 years ago in PI Connectors / Other specific PI Connector 2 No status

    The MQTT Connector should be able to connect to MQTT Brokers that requires Client SSL Certificate.

    Currently the MQTT Connector only supports username/password authentication. This is great for local brokers/servers, but very unpractical when connecting to cloud brokers like AWS IoT Core. Adding support for Client SSL authentication will make i...
    Guest over 3 years ago in PI Connectors / Other specific PI Connector 0 No status

    OIDC authentication with federated accounts (through CONNECT) requires too many steps

    Currently, it is a 5-step process to get authenticated. After the first authentication, it is only a 3-step process, but still clunky.
    Laurie Dieffenbach about 1 year ago in AVEVA™ PI Server / Security 0 No status