From a CSDM perspective, there is not a direct relationship between a Technical Service and Business Service.
- From a business service standpoint, you could have a Service with various offerings such as by platform/channel. For Example, if you had Microsoft Outlook as a Business Applicaiton, you may have different offerings given Office 365 - Web Based, Mobile, and the Outlook client. Each offering may have different support, commitments and more
- From a technical services standpoint, you could consider what are the various care and feed of the Exchange services
- Both Technical Service Offerings and Business Service Offerings have a CI relationship with the Application Service environments.
CSDM relationships and references to consider
- Technical Services have a reference to one or many Service Offerings (not a CI Relationship).
- Technical Service Offerings can have a relationship to Dynamic CI group(s) and/or Application Service(s)
- Business Services can have a CI relationship with one or more Business Capabilities
- Business Services have a reference to one or many Service Offerings (not a CI Relationship).
- Business Service Offerings can have a relationship to Application Service(s)
- A Service Offering cannot reference more than one Technical Service or Business Service. (Thanks
@Peter Kindbom for the correction!)
In a scenario like an Exchange Server were to go down, you would want to have that impacted services visibility to both Business Services Offerings and Technical Services Offering. For instance, availabilty commitments, response, resolution, etc.
One Technical Service Offering could have a relationship with multiple Application Services which then could lead to multiple Business Service Offerings.
Here is a really good set of examples you want to check out. Here is one specific example that may be applicable
