Expose Event Frame Annotations in PI SQL DAS (RTQP Engine)

I have read from different users that indeed the annotations are essential to further track data in BI solutions.

Me and my colleagues are working on downtime tracking, QEHS events, ... that are being tracked and where operators and proces engineers are actively adding comments to the events. We need to use workarounds to get this data available.

It would make it alot easier for us to just be able to send the data via a supported PI technologie like DAS of PI integrator for BI

I used comments - > annotations in PIOLEDB Enterprise in a solution that we are trying move into RTQP and this is a roadblock. We have to have our event frame comments available in Power BI to implement full features. The loss in functionality is not good as we are recommended to use RTQP as a more efficient tool.

The IsAnnotated field available PI SQL Client is often useless because it is set to True as soon as a notification is sent based on the event frame.

To answer questions such as "how many event frames were annotated by actual human users ?", we need to access the details of annotations.

This function is necessary because PI sql client is an official recommended tool

we add comments to event frame annotations. Definitely would be nice to query off this.

This is a must!!!

This is PI SQL Client solution inconsistency

Event Frames are widely used for reporting and BI, comments/annotations are a part of the event frames that brings added value.

It is sad this has been declined. One obvious use case for event frames is tracking downtimes, which often come with operator comments (which we intended to use annotations for). In addition to supervisiors/engineers/managers analyzing those comments, a potential use case is to send those annotations to a natural language processing engine to uncover more insights. PI SQL Client doesn't have support for annotations (and neither does the PI Integrator for BA),which in my opinion makes Event Frames Annotations an incomplete feature when looked at from the perspective of the whole PI System data infrastructure

We also want to view the users comments. Not just a the reason code. I was surprise not to see and now I know why. You even went to trouble of telling us that it is Annotated, but you can't see it. Why bother setting a flag, when the data is not accessible? Like giving me an light indicator that I have gas in my tank, but you can't see the level?

We see an increasing number of use cases to include annotations in our event frames when publishing to PI SQL. It is frustrating that it is declines. Reason code is a good attribute to have published to SQL, but annotations works in conjunction with it to provide the most value.

Annotations & comments are the only way to provide a detail by manual entry. which is good to reflect on reports. It is a good option to add to the SQL DAS under eventframes.