Business Service Offerings - Relationships to other CI

[Richard W]

Hi, when I look at the CSDM 4 whitepaper it explains that Business Service Offerings should depend on Application Services. That makes sense, however, when I look at the online documentation about creating a Business Service Offering using Service Builder it mentions the "depends on" relationship to an application service but it also mentions creating a relationship between the Business Service Offering and other Business Service Offerings. Why is that not in the CSDM relationships table diagram as an option?

My reason for asking this is that so far I have built many application services prior to offerings being a type of CI and I have related application services to other application services to show where there is dependency. If we assume I create a business service offerings that depend on an application service should I be considering migrating the existing relationships between application services up to relationships between business service offerings? 

I notice that the agent workspace and service owner workspace shows offerings and specifically has a widget showing offerings that this offering depends on as well as application services that this offering depends on but it only goes one level down so any 2nd or 3rd level dependencies do not show in the workspace. Is this a reason to change the relationship types as mentioned in the paragraph above?

[Barry Kant]

Hi Joel,

the depends on services (offerings) is more the supply chain look of the business service. So a decomposition of the service.
Applictions service relate to application services . For interfacing dependencies etc. 
So as example:
ServiceNow - Prod depends on OKTA SSO  is application service to application service relation, but also ServiceNow BSO depends on OKTA TSO (as example).

BR,
Barry

[Community Alums]

there have been several observations of mismatched documentations , demo data provided and various threads of CSDM in community. E.g. many documentations of ServiceNow including slide decks of CSDM show 'Contains' relationship of SERVICE OFFERING & SERVICE, but all over SERVICENOW Provided DEMO DATA shows 'Depends On' relationship.

[Steve_Norman]

Hi all - I'd like to add in a question here around how to best model the flow of data from one application to another, and more importantly how to represent this flow from a service (and service level tracking) perspective.  Should one avoid modeling a dependency from one BSO to another, and rely on app svc to app svc relationships only? Several options are described below, and I would appreciate any input if one of these rises above the rest, or if another view would be more appropriate. From a business perspective, the mechanism of the data transfers are not important and the TSO layer is abstracted out. Thank you in advance for you input