Service to Service Offering - CI relationship or no?

[David A2]

We are starting to build out our Service portfolio from the ground up and have a little quandary around building CI relationships between Services and Service Offerings.

CSDM 3.0 seems to infer there should no be a prescribed relationship between a Service and Service Offering, but instead you use a reference field - https://docs.servicenow.com/bundle/rome-servicenow-platform/page/product/csdm-implementation/concept/ci-relationships.html

I came across this success guide that seem to show you should be using a "Contains" relationship - https://www.servicenow.com/content/dam/servicenow-assets/public/en-us/doc-type/success/quick-answer/services-service-offerings.pdf

Do we have any indication on what CSDM 4.0 might be pointing us to on this?

[Stig Brandt]

Hi

The main reason to use a cmdb relationship between service and service offering was to be able to show it on the dependency map, though this is not really needed, as you can just use "map related items".

[Barry Kant]

Hi David,

Stig is right on the dependency view capability.

The other part is the Impacted Service capability.

If you have a reference then it will not be part of the Impacted Service output. 
If you also make a CI relations then it will be part of the Impacted Services output.

So depending on the use case you might want it or not.

For CSDM 4.0 there are no changes on this level.

BR,

Barry

[David A2]

Thank you both for the responses. So we will be utilizing Service Owner Workspace and will be expected to be tracking Service health, SLA's, etc. I assumed using the reference would be sufficient in providing the service owners with relevant information about their Service health data and outages affecting a service offering would translate to the service, but Barry's comment is making me think creating a CI relationship might be required to show Service health and outage information. Am I misunderstanding? 

[Barry Kant]

Good morning David,

you are right about the Service Owner capabilities , this will have a successor capability Digital Product Management in time.

Regarding the data as output of the Impacted Services:

that depends on what data (level) is expected and for what purpose. 
ootb the outages are shown in portal on service level (service status view). 

I think it makes more sense to do that on Service Offering level, as subscriptions are done on Service Offering level. 

So it is pretty much depending on the purpose. 

My personal view is that I would expect it in the impacted service table. Technically that can be done in 2 ways:

1 - add a relation between service and service offering.

2 - modify the impacted service logic to lookup the parent when the class == service offering.

BR,

Barry