This request applies to seemingly all user persona of Digital Twin systems. I will highlight an Operations Team Conected Worker scenario where we have an AVEVA Digital Twin build in place.
The Connected Worker (CW) is having lots of SCADA alarms on a asset. It's causing production interuptions. The worker knows from experiece and from live SCADA the equip number of the asset, G-123.
The CW wants to see what data and events have been captured in the past on this asset in PI. In short, "Hello PI System, show me all you know about G-123".
The CW would go to PIVision and enter the equipment number and find the root element. They CW would be allowed then to (...here is what is lacking...) to set the context of the current display to the chosen asset. From here, G-123 info would be delivered to the dispaly for the CW.
** In PI AF assets are organized asset in very structured architecure to support this fast access and drilliiing into content. URI Attributes in AF and PIVIsion collections facilitate the drilling action for the CW user.
** What we lack is for the client tool to let the user search any element and set context on the display to the chosen element. This will allow then a pivision designer to build the screen elements to expose attribtutes and events of the root element. Also, they see the child elements under the root. This will provide the CW user the UX pathway to drill down into each child element to reveal "all that PI has for this asset."