AVEVA™ PI System™ Feedback Portal

Welcome to our new 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 Subscribe
Status Completed
Product AVEVA™ PI System Access (PSA)
Categories PI OPC DA & HDA Servers
Created by Guest
Created on Aug 23, 2022

RELATED IDEAS

Whitelist/Blacklist KST Members

As a user, I would like to restrict connections from the PI OPC Server to only some members of the KST by either implementing a whitelist or a blacklist.
  • ADMIN RESPONSE
    Aug 23, 2022
    This work has been completed with the release of PI OPC DA Server 2018. Please see documentation at livelibrary.osisoft.com for more details
  • Attach files
  • Guest
    Reply
    |     Aug 23, 2022
    I have a use case where the customer is running a data export-/import-server in DMZ. This server has both PI-to-PI, and PI-OPC-Server. This means the OPC-server is loading connections to all third party servers configured for PI-to-PI exports, and that is just plain wrong. :-)
  • Guest
    Reply
    |     Aug 23, 2022
    In our envornment, there are multiple PI Servers in the KST. The PI OPC Server is only allowed to access a subgroup of PI Servers. This result in failing login attempt every 20s on all PI Servers from the KST, where access is not deisred. So, we need the possibility to configure the PI Servers to be connected from the PI OPC Server.