CSDM and Asset Implementation

[Alberta]

I know we need to CSDM for CMDB implementation.  However, I read ServiceNow documentation regarding CSDM and Asset mgmt.

The doc mentioned CSDM is optional to Asset implementation.  

Can any CSDM expert answer my following questions?

1. Why CSDM is optional to Asset development?
2. When we need to use CSDM for Asset?
3. What are the benefits to use CSDM for asset
4. If we need CSDM for asset, can we use CSDM framework for both CMDB and Asset development together?

[Cassandra Kittl]

I am going to answer in a roundabout manner: CMDB and Asset is like twins with a money variance. I my research on Configuration Management practices, I often found CMDB and Asset management tied together. ITIL separates them as well as ServiceNow. As for CSDM for assets - think on the foundation layer with the locations, vendors, and even contracts. CSDM helps to ensure the different applications on the ServiceNow platform can speak the same language, so all the tables referenced (especially the foundation) should be consistent for the overlapping connections.

[Jeff Ernst1]

Hi Alberta,

Here are my thoughts. CMDB is focused on creating relationships between configuration items. The CSDM gives you a guide on what tables to use in ServiceNow and what relationships to use because ServiceNow is building functionality that leverages those tables and relationships. I do agree the foundation has to be followed no matter what module you are using inside of ServiceNow. If you are just using Asset Management, then you probably don't have to worry about creating the relationship between configuration items, but if you are going to use asset model management and asset tracking strategy to create CIs, I would suggest making sure you are aligning to the CSDM, so you don't have rework. For example, you aren't aligning asset models to create CIs in classes that aren't a part of the CSDM because ServiceNow discovery and service mapping is expecting to see them in completely different classes. If you aren't creating CIs for your assets, then I don't think you need to align to the CSDM outside of the foundation section.

-Jeff

[SebastianKunzke]

I will try to answer your question in sequence:

1. Why CSDM is optional to Asset development?
   It is optional, because many objects described within the CSDM are not used within the asset management. However I would suggest, that you have a look into the foundation data section of CSDM, because this will be important for all of your processes. In special please have a look into the lifecycle management, product models and groups.
2. When we need to use CSDM for Asset?
   OOTB you have some asset categories, that will create CIs within the CMDB. Also for Incident Management you will work with CIs and not with assets. Because of that it can be useful to have a look into technical services and their relation. Here you can use the synchronization feature to assign the correct support groups to the related CI. (It is optional and only needed, if you want to use this as a assignment rule)
3. What are the benefits to use CSDM for asset
   The benefit to consider CSDM from the beginning of your ServiceNow journey is a holistic and standardized view about your data. But based on your maturity it is just mind blowing and the focus on foundation data is the best.
4. If we need CSDM for asset, can we use CSDM framework for both CMDB and Asset development together?
   CSDM is a common service data model and designed to give you a guidance for the implementation and organization of core data objects within ServiceNow. So yes, you can use it for both. And you should, because asset and CMDB is tight together.

PS: Have a look into now-create or ask your implementation partner. ServiceNow created a nice presentation, that give guidance in how to start and also how to use it for your modules.

[yojan]

Hello Alberta, my 5 cents on this 🙂

Config manages the operational lifecycle of components, as CIs, meanwhile asset manages the financial lifecycle of those components. That two faces of the coin are closely tied, as a server CI, as example, has its model with the licenses and the financial lifecycle of that model...

All those CIs are in the lower part of the CSDM model, owned and supported by technical services and offerings and impacting application service(s) by "service impacted by", as if that component fails, the app service is degraded or even stopped.

So...

 1. CSDM is optional to asset as you can manage the operational lifecycle of the components but not the financial one

 2. asset, as attributes and relationships established with the CI component, uses CSDM as complementary info to those CIs

 3. and 4. the benefits I think are already explained in my 1st explanation

The image below somehow explains how we do the app services support 🙂

Best regards