Skip to Main Content
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.

Status No Status
Categories General
Created by Guest
Created on Aug 20, 2022

Revise Perfmon counter for PIBufss - Point Count

We are trying to use this perfmon counter as a diagnostic aid to catch issues with a third party interface, but it could be used with PI interfaces. We are checking to see if the point configuration for their interface matches across the four possible servers the interface could be sending from. I opened a case (00825139) and was given this response by the engineer: These two numbers are not expected to be the same. PIbufss point count is simply the number of points that it knows about - someone has sent data to these points, maybe far in the past. The numbers that piartool -bfs reports is the number of points that this pibufss happens to own now. Ownership of a point meaning that this pibufss is currently writing to the the snapshot for that point. The current behavior of that counter renders it basically worthless - to anyone. I am requesting that this counter always reflects what would be reported by piartool -bfs.
  • Attach files