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

RELATED IDEAS

Enable Data Fanning for PI Collectives through PI System Management Tools

Currently, PI System Management Tools supports buffering but not data fanning (does not send data to all collective members). When using a PI Collective, customers would like to make changes to PI Point values in Archive Editor in the Primary Data Archive and see those changes replicated to the Secondary Data Archive when buffering is enabled.
  • Attach files
  • Guest
    Reply
    |     Aug 20, 2022
    Enabling data fanning from SMT archive editor matters for our PI implementation. Certain PI tags are used to keep historical records of logical setpoints, such as those used within AF and analysis, but not initiated by AF or by an Interface or Connector based source. These setpoints need to be replicated across collectives. Currently, the secondary member of the collective will not even accept data from directly from Archive Editor, with Archive Editor Error: "Error -2147219568: Writing, editing, or removing time series data on this collective member is disabled.". I suspect the same would be true if I used the command based PI archive tools to try to do the same thing. Related to this, when adding data via PI SMT archive editor, it is necessary to type the value first, then the timestamp in order to insert data. If the opposite order of entry is used, then a casting exception is provided by PI SMT. Rather than displaying this PI SMT Data Archive casting error to customers, why not publish a tip that indicates that the value must be added before the timestamp? It could be context specific, popping up if the customer did this in the opposite order than supported by SMT. The supported order of data entry is something that is only learned by trial and error, as far as I can tell at this point. See this OSIsoft Aveva link: https://customers.osisoft.com/s/knowledgearticle?knowledgeArticleUrl=751AF279-0964-800F-ACC2-D861D56F655B