Automatic Recalculation of Event Frame in PI Analysis
As a user, I would like to have the option to automatic recalculation of event frame for out-of-order input events in AF analysis. The option is available for expression analysis in PI Analysis 2017 R2 but not for event frame generation analysis.
The inability for the system to auto recalculate EF based analysis is a significant hurdle when dealing with qualified systems. After dealing with multiple deviations because of OOO data not triggering the generation of EF's that are used in integrations with validated MES systems, we're left with few options - abandoning event frames seems likely for this use case since we cannot reliably maintain a qualified data stream.
One of my big customers has many intermittent connections, so there is much out-of-order data, upon which they need to generate event frames for reporting.
Customer had Out-Of-Order values for inputs on an EF Analysis. This resulted in either No Event Frames being created, or Event Frames opened for a long time. Customer was backfilling the Analysis regularly but is very repetitive. This feature would definitely saving the customers some effort.
We have the same situation where events sometimes arrive out-of-order of tags that are input of an expression analysis with Recalculate analysis for out-of-order input events. As this output is used for an end trigger of an Event Frame, the event does not get closed sometimes. A manual recalc/backfill of the Event Frame analysis or a recapture of the created event frame manually fixes it.
So if the same option for recalculation for out-of-order(and for relative analysis) was available for Event Frame analysis, problem solved. ;)
I think this is the same as;
https://feedback.osisoft.com/forums/555148-pi-server/suggestions/34695688-automatic-recalculation-of-event-frame-in-pi-analy
This could be an optional value a per event frame that could be configurable as a Boolean. If enable kick the automatic recalculation if any attribute change.
We have a situation where lab data may be delayed in being passed into PI. Therefore, it's imperative that either simultaneous event frames need to happen (which is not a current option) or automatic backfill needs to occur. One of these options is a must have!
Create event frames that did not exist before the OOO events came in. Flag them as OOO to make clear why they did not trigger notifications at the time.
For event frames that would not have been created if the OOO events had come in at the time, rather than deleting them, flag them as ‘obsolete’ or ‘superseded’
As as PI Admin I want that a EF is automatically changed if for example the Trigger Tag is changing in the archived values from my PI system.
It could happen that we completly remove the start end trigger for a specific event in the archive. Correspontenly the EF should also removed automaticaly.
This is at least affecting the EF Generator
As a user, I also would like to have this feature of PI Analysis. I am using a PI Connector to gather data with a specific past timestamp , and I need to trigger an EF based on those new coming data with old timestamps, but if the timestamp is too old, I cannot do trigger the EF based on the function HasValueChanged.
We found other ways to do it, but with an automatic recalculation, it would be easier.
It's a critical limitation for EF. The automatic recalculation of EF in case of OOO shoud act on EF modifying them where necessary, saving the existing ID
In addition to normal out of order data cases for EF triggers, this is also critical for late arriving data that has timestamps prior to the last Analysis Service restart.
Due to the LastExecutionTime being set to the current time when the Analysis Service is restarted, any input events with timestamps that are the most recent for that data but are prior the Analysis Service restart time will not trigger EF generation. That data is considered out of order even though it actually might not be technically be out of order.
This has become a necessity for us. We need a scheduling feature to trigger back filling on Analysis tab for elements in OSI PI. We are using a RDBMS interface to load data from SQL database. Partially some data arrives late and can only be reconciled through back filling. We have several equipment for which, doing this manually is almost impossible every day. So this is critical.
The inability for the system to auto recalculate EF based analysis is a significant hurdle when dealing with qualified systems. After dealing with multiple deviations because of OOO data not triggering the generation of EF's that are used in integrations with validated MES systems, we're left with few options - abandoning event frames seems likely for this use case since we cannot reliably maintain a qualified data stream.