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 Subscribe
Status No status
Product PI Connectors
Categories General
Created by Nico Cha
Created on Aug 20, 2022

RELATED IDEAS

Enable Relay/DCM to allow control over the data streams and destination PI Systems

Currently the Relay will send all data streams to all routed destination. This does not allow customers to have control over what data streams go to a specific destination. The only workaround is to have independent Connector/Relay pairs with specific configurations, which does not scale up if there are several Connectors since only one specific Connector/Relay can exist on a single node. For example: Let's say there are two Connectors (A and B), routed to a Relay with two destinations (1 and 2). The current implementation of the Relay will send both Connector A and B data to both Destinations 1 and 2. The request here is to allow end users to be able to configure Connector A to only send data to Destination 1 and Connector B to only send data to Destination 2 in the DCM. In addition, if a Connector has multiple data sources, end users should be able to select the destination for any given data source. For example: Let's say a Connector has two data sources (A and B) and is routed to a Relay with two destinations (1 and 2). The end users should be able to configure data source A to only send data to destination 1 and data source B to only send data to destination 2. This is similar to Enhancement Request: Support for more than one data source (https://feedback.osisoft.com/forums/555139-pi-connectors/suggestions/39122209-support-for-more-than-one-data-source) except this referenced enhancement request is specifically for the PI System Connector while this enhancement request is for all Relay-enabled Connectors.
  • Attach files
  • Alex123
    Reply
    |     Aug 20, 2022
    Hello, i can fully support the need to be able to send data to a dedicated PI collective. The current possibilities makes it not possible for us to use connectors (except v2 with different relays). We are in qualified environment (pharmacutical) and have different servers collectives for testing, qualification and promotion purposes. If we would connect new sources for test purposes, the data would are automatically be also deployed to the promotion system, which causes incompliance.