PIVision user to associate event frames with each other (Root cause and effect)

Event frames are often correlated with one another. "This caused that." One event was the cause for another. These associations are valuable human input, actually they represent discovery of latent issues and growth. To capture the leading edge in the PI historian is a good upselling feature of advanced PI.

Example, consider an OEE tracking system in PI, OEE detects a production loss for a unit and creates an event frame. Minutes earlier a valve in the same unit moved very slowly and created an event frame for poor valve health (failed to Open). Our customers (operations teams in this example) want to associate the valve event with the OEE loss event. These scenarios play out several times a day every day in a large facility. Figuring out and documenting the root causes of loss or poor quality is core to our customer's success. Over time, these event frame associations in a large dataset can pareto bad-actor equipment and set priorities for spending. Very common use of PI.

PI AF supports the necessary user action here with event frame references. PIvision does not. PIvision needs to allow its users to enter event frame references. Similarly, PIVision should allow manual event frame creation and multiple element references creation per event frame. With these advancements customers have deeper tools and reason to invest resources in creating more mature PI event frames.