How to structure Technical Services and Service Offerings

[Erick18]

We have a very complex company structure. We have a Parent company with child companies who offer the same Technology Services. We also have Vendors that provide the same services. For example in the case of Windows Server and Linux Server Hosting, we have several teams who perform the same services as well as within the same company different teams that support different locations. 

Should we break out the company/vendor at the technology service or the technology service offering? Is there any benefit to separating out the services or is it better to keep the services simple and breakout the service offerings?

Service: Enterprise Server Hosting

Service Offering:  Enterprise Windows Servers - Team 1

Service Offering: Enterprise Linux Servers - Team 2

Service: Company A Server Hosting

Service Offering: Company A  Windows Servers Americas - Team 3

Service Offering: Company A Windows Servers Emea - Team 4

Service Offering: Company A Linux Servers - Team 5

Service: Company B Server Hosting 

Service Offering: Company B Windows Servers - Team 6

Service Offering: Company B Linux Servers - Team 7

Service: Vendor Server Hosting

Service Offering:  Vendor Windows Servers - Team 8

Service Offering:  Vendor Linux Servers - Team 9

OR

Service:  Server Hosting

Service Offering: Company A Windows Servers Americas - Team 3

Service Offering: Company A Windows Servers EMEA - Team 4

Service Offering: Company A Linux Servers - Team 5

Service Offering: Company B Windows Servers - Team 6

Service Offering: Company B Linux Servers - Team 7

Service Offering: Vendor Windows Servers - Team 8

Service Offering: Vendor Windows Servers - Team 9

Thanks, 

Erick

[Barry Kant]

Hi Erick,

The breakdown of the Service Offerings is the most important part, as that links to Dynamic CI Groups to the individual CIs. The Service layer (and maybe an upper IT Portfolio level) depends more ion the IT taxonomy in the company. So what is managed on Service level, and who is responsible for this. Reporting requirements perhaps. 
Most of it will happen on TSO level (OLAs, or UCs).

The portfolio structure can be inherited from TBM , which is a common sense data model for IT Services. 
In TBM there is not a breakdown per party, within SN CSDM that is only needed on TSO level. 

I would start simple, unless there is a need to manage it on Technical Service level.

Cheers,

Barry

[Phil Scherry]

Based upon @Barry Kant 's response, I would tend to lead towards a single Service and multiple Service Offerings.  Please let me know if I interpreted that incorrectly.

[Barry Kant]

Yes, that would be the easiest. 
Unless there is a need to make it more distinctive due to IT Organization Mgmt, or Existing Service Taxonomies that do exist (in company).

Have a good week,

Barry