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 Declined
Product AVEVA™ PI Server
Categories PI Builder
Created by Kenneth Barber
Created on Aug 20, 2022

RELATED IDEAS

Use PI SQL Client OLEDB for PI Builder data imports

PI Builder has a few problems:

  • It is specific to Excel.

  • It does not store data in tables.

  • Imported data is static and can become outdated easily, which can lead to frequent imports, the need to publish PI Builder edits soon after import, and the reluctance to save the results of a PI Builder import.

These problems would be solved if PI SQL Client OLEDB could query the same data as PI Builder and if PI Builder used PI SQL Client OLEDB for data imports. This way, imported data would be stored in a query table. Query tables have all of the benefits of regular tables (data isolation, readable formulas, banded rows, etc.) and are also refreshable. Rather than just being an edit publisher, PI Builder would also act as a query generator, which is easier than trying to modify the sample queries in PI SQL Commander Lite. Lastly, by moving PI Builder's query functionality to PI SQL Client OLEDB, we reduce the amount of functionality that is specific to PI Builder. This should make it easier to make versions of PI Builder for other spreadsheet programs, such as LibreOffice Calc.

  • ADMIN RESPONSE
    Aug 20, 2022
    As the name implies, PI Builder was envisioned to be used for building AF objects. Its chief goal is not for querying data. We would rather not blur the line between a (primarily) configuration tool vs. a data tool (for example, PI DataLink).
  • Attach files
  • Kenneth Barber
    Reply
    |     Aug 20, 2022
    This suggestion would solve this one: https://feedback.osisoft.com/forums/555148-pi-server/suggestions/18668149-use-excel-tables-to-contain-pi-builder-data This suggestion is closely related to this one: https://feedback.osisoft.com/forums/555148-pi-server/suggestions/31708795-store-pi-data-archive-information-in-an-sql-server
  • Kenneth Barber
    Reply
    |     Aug 20, 2022
    I don't see what's wrong with blurring the line. Within OSIsoft, there are many cases of products being expanded beyond their original purpose, or being replaced with something more generalized. The best example is probably the entire PI system. PI (Plant Information) began as a way to manage process data, but now OSIsoft encourages customers to connect PI to financial data and record operator logs in PI. Would it have been different if I had suggested replacing PI Builder with a more generalized add-in (PIxel/PIXL?), or if I had suggested a new add-in entirely?