What is your use case?
I am asking the question because we are using time aware modelling (TAM) to clone elements for 2 use cases that do not fit nicely with how I think TAM should be used.
I provide an example in the original post. Imagine that you design a network where multiple elements exchange information. Topology will be somewhat a snowflake - so ... you will have a hub and spokes, and then one of the spokes will lead to another hub with its own spokes. Now, there is no a priori knowledge of how many spokes (or children, if we use this reference) will a hub (parent) have. There is also a possibility that relationship is between hub and a nested element of a spoke. Easiest to model would be a pattern of one hub, one spoke (with nested elements), and then clone multiple spokes (children) as many times as needed because they will have the same communication characteristics with hub.
That's the simplest, but of course it might be that we have special spokes that are somehow related to hub and to nested elements of their own.
For now ... I simply use a pattern, then manually recreate relationships - which is a bit faster than cloning full structure for duplication, finding one of the nested elements, and creating relationship between it and the hub.
Best regards
Marcin