Service offering - can they be related to multiple services and how?

[Chaz_]

We have a a requirement where assessments are completed at a service level which check the service health and resiliency etc. This generates a large number of assessments for service owners. The approach being taken is to setup a service offering which can relate to multiple services and then trigger the assessment from the service offering instead of the service. This should reduce the assessments and largely answers will apply to each service in that grouping.

Question - can they be related to multiple services and how? I've only experienced service offerings being linked to 1 service and I know a service can have multiple service offerings. How about the other way round? ie. 1 service offering related to multiple services.

[Barry Kant]

Hi Chaz, 

Service Offerings are parented by a single parent service. 
You can make underpinning relations like this:
Service Offering Depends On Service Offering
eg:
Many applications (business service offerings) are underpinned by a SSO solution (technical service offering). 
That way an (technical) authentication service can be (via-via) related to multiple business services.

Not sure if you have similar examples/expectations?

BR,
Barry

[Chaz_]

Thanks for clarifying that.

Maybe I should describe the problem a bit more. We send out resilience surveys to service owners based on services which check the service health. As this is driving a large number of surveys for people to maintain, we have noticed that there groupings where services can share similar characteristics.

Is there a way of targeting a survey against a group rather than the service level? The intention is to reduce the volume but also avoid detracting from the CSDM model which could cause tech debt later.

Many thanks.

[Stig Brandt]

Hi @Chaz_ 

Is there a way of targeting a survey against a group rather than the service level? The intention is to reduce the volume but also avoid detracting from the CSDM model which could cause tech debt later.

To group Services, maybe consider to use Service Portfolio's -> Taxonomy - Layers, here you group services into logical containers, her you also will have taxonomy - owners etc. I think that is the way to go.