Hi all, I'm having some trouble with the triggers of an Event Frame Generation Analysis. It seems like it lost some random trigger, but the strangest thing is that it seems that it lost only ending triggers.

Hi Michele

In general, when ever I encounter a situation where the Preview differs from the actual output, I'll restart the Analysis Service.

The difference between a Preview and normal operation or a Backfill operation is that the Preview is generated by your PI System Explorer client, while the normal/Backfill operations are done in the Analysis Service. The two should produce the same outputs, so either your client has a problem or the service.

Since both EF's are closed at midnight, I would lean towards the explicit end trigger not being interpreted properly by the Analysis Service. 'Irr_alm' probably resets to 0 at midnight, which would make the StartTrigger false, and thus close the EF.

Hi Asle,

thanks for the answer. The situation is not so simple, I can't just restart the Analysis Service, I won't go into too much detail, but there are multiple systems intersecting in this project, and the AF events generated here are just a part of the project, I can't just regenerate them or stop the service at a moment's notice.

Regarding your explanation about the closing of the event, the 'Irr_alm' is not going to 0 at midnight, but at sunset (let's say at around 8 pm). But also if this is the case the irr_alm going to 0 is not an end condition for the event. The closure at midnight is defintely triggered by the DailyTrigger.

Anyway, this situation happened just for some days, from August till now the events are being generated correctly and no changed has been made to the analysis. I just don't get how this situation could possible arise. Even I have no idea how to recreate the issue on my local system for debug for example.

"The closure at midnight is defintely triggered by the DailyTrigger."

So, as Rick_Davin_3.0​ says, the analysis is being evaluated any time DailyTrigger receives a new value, but whether it receives 0, 1 or 1000 is irrelevant. It's just there to invoke the analysis to evaluate the conditions.

Your start trigger relies on Mode_Calculated and Irr_alm, and the latter is irrelevant for the closing of the EF. Mode_Calculated is definitely evaluated to 0 on midnight between 2 and 3rd of August, so you're right about the DailyTrigger being the triggering event for evaluating the analysis at that time.

So that leaves us with the conclusion that Mode_Calculated did NOT trigger the calculation at 2-Aug 18:34:50, nor at 18:42:53 or 19:31:14. My best guess is that there's something wrong with the way the Analysis Service interprets which tags to trigger from (i.e. Mode_Calculated isn't set as a trigger), and that this bug is best resolved by restarting the Analysis Service.

• You could try recreating the analysis in a test environment, or just by creating a duplicate setup to see if that resolves this.
• I interpret your answer so that you haven't tried backfilling the analysis, only previewing the results. Often we see that the normal run fails to trigger on some events, but the backfill works great. There could be a difference since normal runs trigger from the snapshot values, while backfilling works directly on archive values
• You could try your luck with AVEVA's techsupport here, but I'm almost sure they'll conclude with the same recommendation. What versions are you running, btw?

"The closure at midnight is defintely triggered by the DailyTrigger."

So, as Rick_Davin_3.0​ says, the analysis is being evaluated any time DailyTrigger receives a new value, but whether it receives 0, 1 or 1000 is irrelevant. It's just there to invoke the analysis to evaluate the conditions.

Your start trigger relies on Mode_Calculated and Irr_alm, and the latter is irrelevant for the closing of the EF. Mode_Calculated is definitely evaluated to 0 on midnight between 2 and 3rd of August, so you're right about the DailyTrigger being the triggering event for evaluating the analysis at that time.

So that leaves us with the conclusion that Mode_Calculated did NOT trigger the calculation at 2-Aug 18:34:50, nor at 18:42:53 or 19:31:14. My best guess is that there's something wrong with the way the Analysis Service interprets which tags to trigger from (i.e. Mode_Calculated isn't set as a trigger), and that this bug is best resolved by restarting the Analysis Service.

• You could try recreating the analysis in a test environment, or just by creating a duplicate setup to see if that resolves this.
• I interpret your answer so that you haven't tried backfilling the analysis, only previewing the results. Often we see that the normal run fails to trigger on some events, but the backfill works great. There could be a difference since normal runs trigger from the snapshot values, while backfilling works directly on archive values
• You could try your luck with AVEVA's techsupport here, but I'm almost sure they'll conclude with the same recommendation. What versions are you running, btw?