Currently, only INSTRUMENT_PARAMETRIC class and it's sub-classes will work with PANEL class to acquire panel properties during instrument placement. Defining I/O POINTS in the schema as a sub-class of instruments, and placing them from a cell library does not result in a relationship between the PANEL and the I/O POINT. On nearly every project, we place CONTROL PANELs on the P&ID, then place a DIGITAL CONTROLLER PANEL inside CONTROL PANEL with a relationship manually added between the two panels. Then we place I/O POINTS inside the DIGITAL CONTROLLER PANEL. We manually define a relationship between the I/O POINT and the DIGITAL CONTROLLER PANEL in order to extract both the CONTROL PANEL name and the DIGITAL CONTROLLER PANEL name as properties of the I/O POINT class. On a typical project we may have 3000 - 5000 I/O POINTs. It would save countless placement and back-checking hours if the I/O POINTs would be able to acquire the CONTROL PANEL and DIGITAL CONTROLLER PANEL data via an automatically defined relationship with the panel during placement as happens with INSTRUMENT_PARAMETRIC class.