Guy Acciai

My feedback

  1. 4 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Developer Technologies » PI Web API  ·  Flag idea as inappropriate…  ·  Admin →
    Guy Acciai supported this idea  · 
  2. 3 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  OSIsoft Learning » YouTube Learning Channel  ·  Flag idea as inappropriate…  ·  Admin →
    Guy Acciai supported this idea  · 
  3. 4 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Cloud Connect  ·  Flag idea as inappropriate…  ·  Admin →
    Guy Acciai supported this idea  · 
  4. 3 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Guy Acciai supported this idea  · 
  5. 17 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  PI Server » Data Archive  ·  Flag idea as inappropriate…  ·  Admin →
    Guy Acciai supported this idea  · 
  6. 213 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    39 comments  ·  PI Server » Analytics & Calculations  ·  Flag idea as inappropriate…  ·  Admin →
    Guy Acciai supported this idea  · 
  7. 8 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Manageability » General  ·  Flag idea as inappropriate…  ·  Admin →
    Guy Acciai supported this idea  · 
  8. 4 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Guy Acciai supported this idea  · 
  9. 3 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Guy Acciai shared this idea  · 
  10. 33 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Guy Acciai supported this idea  · 
  11. 8 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  PI Interfaces » UFL Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
    Guy Acciai supported this idea  · 
  12. 4 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Vision » Installation & Upgrading  ·  Flag idea as inappropriate…  ·  Admin →
    Guy Acciai supported this idea  · 
  13. 4 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Guy Acciai supported this idea  · 
  14. 3 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Guy Acciai supported this idea  · 
  15. 2 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Guy Acciai shared this idea  · 
  16. 18 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    An error occurred while saving the comment
    Guy Acciai commented  · 

    To: cbambury

    Can you elaborate a bit more on your view construction sitting on the LogEntries table? - I'll familiar with that table, and I'm curious if you joined the ScanID back to the individual views in the IntegratorStats database to sort out the View name and the execution time?

    Additionally, how did you deal with the "Stats" column, as it looks to be using some sort of compression - We tried a GZIP decoder, but didn't get very far -

    Any hints on how to decode LogEnteries.Stats column, or the Stats column in the various view tables stored within the IntegratorStats DB?

    Sharing some SQL code (or T-SQL if needed) on your view definition would be much appreciated.

    An error occurred while saving the comment
    Guy Acciai commented  · 

    Totally agree with the need for more visibility into view status, and my recommendation would be to push some of this (as well as last run statistics) into Perfmon, along with other Pi4BA performance data (CPU, Reads/Writes, Memory, Execution Time, per worker process). -

    This allows me to trend run time into PI with Perfmon interfaces, do notifications via PiNotifications, etc. - Versus building a separate dashboard for view tool, just expose (RO) alot of what's stored in the PI4BA PiView AF Configuration DB into Perfmon

    Bottom line, if Pi4BA is to become an enterprise tool, then it needs to expose more of it's operational status, and facilitate better monitoring, etc.

    Guy Acciai supported this idea  · 
  17. 18 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Guy Acciai shared this idea  · 
  18. 3 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Guy Acciai supported this idea  · 
  19. 31 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Correction to earlier comment by Matt Ziegler: This idea was not fulfilled in PI Integrator for Business Analytics 2018 release. This idea is currently not planned for a future release. If you have a use case and desired behavior for a particular writer and want to discuss further, please comment below or email me. Thank you!

    Guy Acciai supported this idea  · 
    An error occurred while saving the comment
    Guy Acciai commented  · 

    IMHO, this applies to any SQL target, aka Oracle or SQL server - I can somewhat understand the need for this to be an optional setting, either associated with the specific target (Like a drop table when deleting a view checkbox), or possible even making this an option during the View creation itself (for a SQL based sort of target), but the status-quo is a mess for DB users.

    We did give some of our power users access to create their own PI4BA views, which in turn, creates DB tables for them. We typically give these folks RO access to the underlying DB server, to then pull their data.

    Obviously, the owners can delete their own PI4BA views, but the resultant DB table remains (as Pi4BA created it for them, it seems that this should be deleted, when the view that created it, is also deleted. At

    Bottom line, this is definitely confusing for our users, and can leave "orphaned" data out in the DB server, that requires manual effort to sort out, what's still a valid table, compared to the views still exist in PI4BA

    Either build this into the product, or release a separate utility (or stored procedure?) than can query AF, find the meta data about what views should be in the DB, and compare this to the actual tables in the DB, with an option to delete DB tables to get things back in sync.

  20. 270 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    36 comments  ·  PI Server » Analytics & Calculations  ·  Flag idea as inappropriate…  ·  Admin →
    Guy Acciai supported this idea  · 
← Previous 1

Feedback and Knowledge Base

Posted ideas will have one of the following statuses.
Full definition of these statuses can be found on the Home Page.
No status
NEEDS MORE DISCUSSION
RESEARCHING/EVALUATING
DECLINED
PLANNED
STARTED/IN DEVELOPMENT
IN BETA/PREVIEW
COMPLETED