In our TBSM template modelling approach our idea is to use specialized templates which describe a special aspect of the behaviour of a service instance. The idea is to use a primary template with the main goal to assign an icon and a type description and secondary templates with a specific behaviour, e.g. handling of incoming events (like the SCR_ServiceComponentRawStatusTemplate), the association of incidents registered against this service instance (affectem item/CI), etc.).
However, when visualising the service instances, we now notice that it is possible to select an icon with specific labels and attributes, but the only attributes available for associating with this view type are the attributes available for this template. Hence, we miss the opportunity to present attributes, e.g. the number of incidents or the number of events, which are part of the secondary templates.
So, we are wondering now whether we need to step away from the template specialization to allow for visualizing secondary template information. From a TBSM design approach it seems we would need something like a container template relationship in which the "container" template determines the icon etc. and the "contained" (sub) templates add specialized behaviour.
But maybe there are other options to allow for the visualization we need. I understand that we could achieve this at the service instance level, but we're looking for a way to achieve this at the service template level.