With respect to CATIA/ENOVIA, is there a best practice in the AEC industry for structuring the product tree?

There are couple use cases that are making me question how to best define a product structure in CATIA.

BOM reports - By Domain, by Storey

Clash analysis - some Domains cross multiple Storey

Open data - by Storey, by Domain, using filters or configuration, again components can cross over multiple Storey

Large number of Components - Opening a complete digital twin is getting impractical for the web client user. Thinking if filtering and/or configurations are needed to make the web client user productive.

The image is showing a play building where I am trying to resolve a product structure based on several uses cases.

------

I have documented 2 scenarios. There must be additional methodologies. Please add on :-)

Looking forward to the pros and cons.