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 Future Consideration
Product AVEVA™ Adapters
Categories General
Created by Guest
Created on Aug 16, 2022

RELATED IDEAS

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 data. By removing a PItoPI link between PROD and DEV, this would largely reduce the complexity of the setup (especially when you have > 50 sites) while keeping a lower more manageable volume of data for development purposes. Currently when we setup PI Adapters, the OmfEgress component is configured for all instances on the host and sends all the data to all configured egress endpoints. We would like to see this OmfEgress component configured as part of the instance component instead.
  • Attach files
  • sahilp
    Reply
    |     Oct 20, 2023

    This could also be used as a cheap trick to improve the throughput and utilisation of available bandwidth.


    If we have a large tag DB e.g. 20k tags and/or a high latency but high bandwidth link to the webAPI, then a workaround could be to split in two instances and each with a separate (but identical) egress endpoints. Right now high latency, high bandwidth connections are under-utilised.