Ability to create child Events (EFs)
As a power user or admin, I would like the ability to create child events (EFs) or sub events within AF Analytics SO THAT I can migrate EFGen configurations to something that can be applied to a template and not configured by tags and SO THAT my users can analyze finer time periods of events.
Most common trigger behaviors for a child event are:
* Pulse: values are 0/1 or ON/OFF
* Step: values change and upon each transition, current in-progress event is closed and a new one is created
* Step Continuous: An event is also captured in the OFF/0 state.
* A trigger expression.
The Name of the child event can come from:
* Active (trigger) tag value
* A Static name
* Another tag value at the time of creation (or delayed)
I would like to echo Marc Fortin, for users of RtReports, this functionality is vital if we want to migrate from PIBatch to AF. EventGen does not seem to have received a lot of attention, so it is really important that this can be handled in AF Event analyses.
The normal batch use case has four levels of nesting - batch, unit batch, phase and phase step. However this could increase due to sub-phases or sub steps. There may be a requirement to have simultaneous operations, so it would be important to be able to overlap child events.
For me, the two most important bits of fuctionality would be 1) to be able to specify a parent event template in an event template and 2) specify a keying mechanism. I would suggest two way to do this. Firstly, key by process unit which would equate to the parent AF element, or secondly, key by a common attribute (such as batch ID) between the parent and child events.
Best thing would be to have the option that parent and child can be from different templates. See also this idea:
This has not been scheduled.
Do you have any updates on this item? Has it been scheduled?
In response to Stephen Kwan, "Ok, in that case, the request is to exec..."
Sorry for the late response, yes i believe the analysis would just run when the event frame is open.
In response to Calvin La, "Hi Stephen, I think the customer wanted ..."
Ok, in that case, the request is to execute additional analyses "within" the event frame time duration in a streaming fashion. That also means these analyses would need some kind of a triggering/scheduling and I would assume these analyses would only "run" when an event frame is open?
Hi Stephen, I think the customer wanted to utilizes these properties after the Event Frame is created. Perhaps in the analysis or End Trigger condition.
For example, querying a TagVal of an attribute at the StartTime of the Event Frame to ensure an attribute it meets specific condition in relation to the queried attribute
This is a chicken/egg situation. The event frame analysis StartTrigger is executed to determine whether an event frame should be created. Before the EF is created, there is no StartTime. In short, there is no EF StartTime until the EF is created, thus it doesn't make sense to use an EF StartTime to determine whether the EF analysis should create an EF or not.
If I have misundertood the intent of this request, please provide more details.
Support analyses on event frames by allowing accessing event frame properties such as StartTime of the event frame as an input to the event frame analysis.
when developing this solution, please also keep in mind the following post:
it's important to define the child event frames as flexible as possible (e.g. also from a different AF Database,..).
This is currently in our backlog but has not been scheduled yet.
I would be interested in the current Status of this request. We are also facing a Project where we would like to define child Event Frames in AF Analysis as this is much more userfriendly for plant Operators than PIEfGen.
Also we would need an option to define a stepped start signal for Analysis.
Our options right now are to continue using a complex configuration of PI ACE (>150K lines of custom code) or have this child event frame capability within PI Analytics.
PI Analytics would be much more practical from a customer standpoint. Also, it seems that PI ACE is no longer under development which implies we should look elsewhere or risk LCM issues down the road.
We are collecting requirements for this. Please provide your needs in terms of how many levels of child event frames you would need, whether you need to reference other event frames, etc. Please describe your use cases.
Wondering if anyone from OSI can comment on this enhancement. There is a great interest in this.
Sounds simple and is definitiv required.
Brian Harclerode commented
This functionality is essential for Upstream Oil and Gas Drilling companies. We are currently using event frame generator to generate child events but rolling this out to hundreds of wells/rigs is cumbersome without templates. Also, we need to add the ability to roll up event frame attributes at the parent element level.
Colin Moore commented
As we look more and more into migrating from PI Batch to Event Frames we would prefer using templates. This ensures consistency of configuration and ease of roll out/testing.
I have a project whereby I am generating Event Frames during an equipment fault. This equipment can have more than 1 fault at a time, so I would like to have a parent "Equipment Fault" event frame with child event frames per specific fault. Once all specific faults return to normal and their event frame closed, the parent fault would also close.
Marc Fortin commented
To be able to convert 100% of Bagen to Event-Frame, this functionality is mandatory. With AF we can use attribute like start trigger and we use the powerful of templates.