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?

[edkester]

as an FYI ... you can add 'references' to you dependency mapping:

   >  navigate to:  Dependency Views  >    Map related Items

   >  create a new record in this table to allow 'dependency view' to show relationships

[KKrabbenhoft]

All of this is very helpful. We are in the crawl stages of CSDM and CMDB. I am trying to gain as much knowledge to ensure a successful beginning. 

[LC-303]

What relationship type is best for Service :: Offering?

[EricDohr]

An Offering references a Service versus having a CO relationship. One Service could have many offerings. An Offering can only babe one service. 

[baig]

Contains::Contained BY