Simple Diagram explaining CSDM Layers

[Passion_of_SNOW]

I have joined an organization recently and they are still on the crawling phrase of CMDB and has not applied any service mapping yet. I am tasked with establishing the service mapping as per CSDM v5 framework. 

For now, I need to explain the service layers to service managers/owners in simple terms. This is what I have come up with  so far - 

But i am not sure if it represents the layers correctly. Any suggestion or advise using examples/definition would be appreciated. 

[AndersBGS]

Hi @Passion_of_SNOW ,

 have you looked at the CSDM white pair mm paper? You could take DPM into consideration, as this will give clear overview to service owners.

[TheJoeDC]

yeah, I find the the "Relationships in CSDM" section in the CSDM white paper very useful for understanding the layers. 

[Geri1]

There are a number of correct mappings you could do, based on the needs of the organization. I came up with this general diagram (color coded to match the domains in the CSDM 5 white paper) to explain the elements in a non-technical manner:

[glenn_pinto · Accepted solution]

I am working on some CSDM hands on content that will be made available when the CSDM Fundamentals course is updated next month. In the lab we model the CSDM elements and they display in this manner on a map. 

Also with v5, Application Service is now called a Service Instance of type Application Service to allow for different types that are non app based. Also Technical Service is called Technology Management Service and Technical Service Offering is called Technology Management Service Offering. 

We also view this model in the labs within DPM. As a service owner, you can view the service portfolio all the way down to the service and offering and see any KPIs you configure to view on any element or rolled up to a higher element like the service portfolio.