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 No Status
Product AVEVA™ PI Server
Categories Data Archive
Created by vasanth51
Created on Aug 20, 2022

RELATED IDEAS

Separate priority setting for Data Read and Data Write

Data Read and Date Write (Buffering) from/to PI Data Archive is based on the priority settings in PI SDK and PSE. We have a architecture of 6 member PI collective and all the source data is not buffered to the individual collective. Hence for other applications like PI Analysis or any other 3rd party applications data read should from couple of collective members and data write should be to 4 collective members. As per the current setup, if we enable the priority for 2 members in collective, data read and write is happening only for those members (Default behavior). But we need separate priority to control the data Read and data Write Operations separately. This feature will help us in resolving many business critical issues and other applications to leverage the features of PI.
  • Attach files
  • Guest
    Reply
    |     Aug 20, 2022
    Hi, I'm trying to understand a bit more of what you're trying to do. You have a 6 member PI Collective which by design should have the same data fanned by BufSS. But you're describing a situation where Asset Analytics would be writing to 4 of those members, rather than all 6. Did I get that right? In that case, you would have different data in the collective members, which is very unusual. How would your clients be accessing the data? Would you configure the clients to connect to only specific collective members? This is very unusual. If you're trying to load balance, perhaps what you need are two different collectives, each with the necessary number of collective members. You can then read from one collective and write to the other collective.
  • vasanth51
    Reply
    |     Aug 20, 2022
    As per our architecture, PI data Archive is 6 member collective (1 primary & 5 secondary). All the facility data is available in Business LAN DA members (2 servers) of collective and other members only have respective facility data. During monthly MS patching, we have noticed the issue that PI Analysis service trying to connect different collective member which is expected when the primary server goes down. However calculations results getting impacted because if it is connecting to facility DA members other than BLAN colective member, set of calculations is getting affected. Ex: If it is connected to Onshore DA member, all the Offshore calculations are getting affected as Onshore server doesn't have data for Offshore tags.