Allow different naming for Parent and Child Event Frames
Allow a different naming pattern for the child event frames. End result would have the long, uniquely named EFs in the Parent EF as usual, but the Child EFs could have a simplified name, like the level of an alarm that is pulled from an attribute value (capable as of AF 2017 R2).
AdminJeff Resnick
(Admin, OSIsoft)
shared this idea
6 comments
-
Bruce C. McCamant
commented
I would like to suggest that in addition to different naming patterns for child event frames, that you also expose start trigger names to be used in the naming pattern.
-
Bradley Rinehart
commented
We use event frames to track status within our production systems. We name the child event frames using the trigger name. It can be confusing when the parent event frame name matches the first statistical trigger name. It would be beneficial if the parent frame name reflected the production line element name and date while the child event frame names reflected the production line status.
I would also like to include attributes in the parent event frame that are not the same as those in the child event frame. Also include trigger specific attributes in the child event frames.
-
DaveGreene
commented
I can't believe this only has 9 votes.
https://pisquare.osisoft.com/thread/38841-naming-parent-and-child-events
-
MarkusKoschorreck
commented
Best thing would be to have the option that parent and child can be from different template.
-
Jason Bray
commented
This would be extremely useful for identifying event frames from different stages of a process, or for visualizing specific types of events in PI Vision. Ideally, one could also specify unique EF templates for child events (created automatically using AF analysis with different severity triggers), but unique naming would be a good workaround in the meantime.
-
Are you generating the EF's using analytics?
