Guidance for using IT Shared Services

chriswaters
Tera Contributor

How do "IT shared services" fit into the mix with the CSDM?

https://docs.servicenow.com/bundle/madrid-it-business-management/page/product/it-finance/concept/c_I...

I don't see how they apply in the model, and that makes me feel like the best approach would be to avoid them for now.

Thanks!

1 ACCEPTED SOLUTION

scott_lemm
ServiceNow Employee
ServiceNow Employee

Chris,

IT Shared Services are not an object in the CMDB and thus not a direct part of the CSDM. These IT Shared Services are ITFM objects utilized to create automated cost rollups for the business.

Within the CMDB we focus on providing a portfolio of Services and their relationships to other Services. 

It is important to have a definition of "Shared". That definition may or may not reflect a technical representation of relationships documenting what services consume the Shared Services.

Showing the "share":
The CSDM within the CMDB has the value proposition of showing where shared services are consumed by other services. Shared Services are not specifically "labeled" in the Common Service Data Model. They may be built out like any other service within the CMDB as either Technical Services, Application Services or Business Services that happen to be shared. Using relationships created through Service Mapping or manual effort you can see where your services depend on other services thus displaying a "shared" service. Showing the "share" then enables business to see where services are utilized and thus validate financial modeling.

 

It sounds like there may be value in identifying a Service in the CMDB as "shared".

Hope this helps.

View solution in original post

3 REPLIES 3

scott_lemm
ServiceNow Employee
ServiceNow Employee

Chris,

IT Shared Services are not an object in the CMDB and thus not a direct part of the CSDM. These IT Shared Services are ITFM objects utilized to create automated cost rollups for the business.

Within the CMDB we focus on providing a portfolio of Services and their relationships to other Services. 

It is important to have a definition of "Shared". That definition may or may not reflect a technical representation of relationships documenting what services consume the Shared Services.

Showing the "share":
The CSDM within the CMDB has the value proposition of showing where shared services are consumed by other services. Shared Services are not specifically "labeled" in the Common Service Data Model. They may be built out like any other service within the CMDB as either Technical Services, Application Services or Business Services that happen to be shared. Using relationships created through Service Mapping or manual effort you can see where your services depend on other services thus displaying a "shared" service. Showing the "share" then enables business to see where services are utilized and thus validate financial modeling.

 

It sounds like there may be value in identifying a Service in the CMDB as "shared".

Hope this helps.

We have used the Service Portfolio layers to identify shared services, sitting next to end user services (roughly following the TBM model).

GarLac
ServiceNow Employee
ServiceNow Employee

Does this answer still stand true in CSDM 4.0 or in San Diego?