The DCM Blog

Connecting Discovery Data with CSDM

By Mikko Juola

April 22, 2020
Connecting Discovery Data with CSDM

“You cannot have a successful CMDB implementation without discovery tools” could be a quote from several articles describing the success factors for a CMDB initiative.

And sure enough, many companies get all the bells and whistles to populate their CMDB, but how do these technical components relate to more abstract entities such as Business Applications and Services? Or how to take ownership of these data records from an operational point-of-view?

“Discovery finds applications and devices on your network, and then updates the CMDB with the information it finds.”
What is ServiceNow Discovery?

The Common Service Data Model (CSDM), v2.0 published by ServiceNow in late 2019, describes the data model for these more abstract CMDB classes. But as mentioned in the whitepaper, the CSDM is not a product or a solution that would do anything for you. It is just a model, even though it is a very good one.

Some more sophisticated tools can even map application topologies (and call them service maps), but at least for now, there is always one or more parts of the big picture that cannot be modeled and managed without human input.

To sum up the problem:

  • You cannot succeed with the CMDB without discovery tools (according to multiple studies)
  • Discovery tools cannot manage all data within the CMDB
  • The Common Service Data Model provides a model but not the means to link discovered data into the abstract data classes
  • At least the Service Portfolio and other logical elements (like Business Applications) on top tiers and relationships to non-CMDB data (like users and organizations structures) are manually maintained.
  • You need to define and manage relationships between discovered and manually maintained data.
Discovery Meets Manual Data

Borderline between discovered and manually maintained data


In this blog, I will describe:

  • an example of discovery-populated data
  • a data model related to Discovery data
  • data models connecting discovery data to the Common Service Data Model and non-CMDB data
  • how to ensure that agreed models are being followed

Managing the Borderline

One way to manage the borderline between discovered and manually maintained CIs is first to define the links that connect the discovered CIs to the manually maintained CIs. And then start tracking that each record in those borderline classes has the required relationships. This is basically the same as tracking orphan CIs, but with an exact focus on particular use cases.

Let’s imagine that you have a ServiceNow Discovery and/or ServiceMapping products in use. These two can provide a detailed map of your application infrastructure, from Servers and their components to installed applications and their connections.

Example Discovery Data and Data Model

In this example, the Discovery tools have created following data into your CMDB for one of the application entry points.

Service Mapping data

Example data populated by discovery


These records belong to at least 7 different CI classes and if we simplify and generalize the related data model a bit, it could look like this:

Service Mapping Data Model

DCM Blueprint example for discovered data


If all this data is maintained by discovery tools, then modeling the relationships between discovered classes may not be that fruitful. What is more important, are the links that pass the borderline i.e. the links between discovered and manually maintained CIs and links between CIs and other data within the ServiceNow platform.

Good examples of other data are Users and Groups responsible for managing the services.

Examples to Connect Discovered Application Data to CSDM

In the real world, the topmost records in the previous example are related to business applications. Few words about them

  • Application Service class represents a logical application stack for a particular Business Application.
  • Application class often represents e.g., “middleware” or other installed applications on servers.

According to the CSDM, the Business Application class is part of the Design domain and is used mainly for Application Portfolio Management and Enterprise Architecture purposes. In most cases, the data in the Business Application class is manually maintained. Relationships to service portfolio should be done on the Application Service level, according to the CSDM.

Let’s draw another blueprint that defines the links between discovered application data and manually maintained Business Application and Service CIs.

In the following example, we connect the discovered application to manually maintained data. Starting from the Application Service class, we want to ensure it is connected to discovered Application records. More importantly, we ensure that all Application Services, also manually created ones, are related to Business Applications and Business Services.


Discovery to CSDM Model

DCM Blueprint example for connecting discovered application data to CSDM


But what should we do with the rest of the discovered data? Or what is important for all CIs?

Connecting all Discovery Data to Technical Services

To ensure that all CIs are connected to Technical Service Offerings as the CSDM requires, we can create a more abstract data model to define how this should be done. Discovery tools can populate a lot of data into different CI classes. And one thing to consider also is that some CIs are connected to services via other CIs. For example, discs and memory modules should be related to computers that are then connected to services.

All CIs to CSDM

Connecting all CIs to technical services

In this example, we can filter the Configuration Item class to select which CI classes should follow this model (or exclude the ones that should not). And for the Service Offering, we can also add a filter saying it should be of type Technical Service.

With these two blueprints above, we can ensure that:

  • All discovered applications are connected to business services and business applications.
  • All other discovered CIs are connected to Technical Service Offerings responsible for maintaining, supporting, and managing them.
  • All CIs have proper responsibilities in place as references to users and groups.

Running continuous audits against these blueprints will make sure that data will remain in good shape and people can focus on the most important parts of the data model to enable the wonderful capabilities provided by discovery, especially when connected to the new Common Service Data Model.

Data Content Manager can help to ensure quality data

With Data Content Manager (DCM), one can draw a blueprint matching the data models shown above and simply run an audit to check how accurate and up-to-date your current data is. Audit results can be shown per audited record (an application service, for example) or Blueprint element (“Depends on::Used by” link between an Application Service and a Service Offering, for example) to see which data to fix.


Audit Dashboard

DCM Audit Dashboard

Additional CSDM Resources

We have written a lot on aligning with the Common Service Data Model and how Data Content Manager can help ease the journey.

Here are some excellent places to start:

Please reach out to us if you have any questions!

Mikko Juola

Mikko Juola

Chied Product Officer at Qualdatrix


Built on now

Featured Posts

Can You Get A Whopping 1436% ROI by Improving CI Data Quality?

Can You Get A Whopping 1436% ROI by Improving CI Data Quality?

How do you calculate the Return On Investment (ROI) for Data Quality improvement? That’s a question we get asked almost every day. And every time, answering is painful since we’ve not come up with a magic formula that fits every scenario. Believe me, we’ve tried. So,...

5 Challenges to Address for Better CMDB Data Quality

5 Challenges to Address for Better CMDB Data Quality

Comprehending the impact of CMDB Data Quality, especially its absence, can be difficult. It is a big problem since poor data quality is often the main reason ITSM systems, like ServiceNow, don’t meet expectations. We are deeply involved with data quality daily. Our...

Video: Ensure You Can Do Root Cause Analysis

Video: Ensure You Can Do Root Cause Analysis

Root Cause & Impact Analysis in ServiceNow is essential, but it is sometimes not clear what you need to have in place to do it. This is especially true for Application Services since they are not self-evident for many ServiceNow users. Ensuring your Application...

How LapIT Improves CMDB Data Quality with DCM

How LapIT Improves CMDB Data Quality with DCM

LapIT designs and implements solutions for information and communication technology environment services in Northern Finland. Their customers are mainly municipal, public administration, and healthcare organizations. We interviewed Leena Broas, Development Manager at...

Video: How to Improve Foundation Data in ServiceNow and CSDM

Video: How to Improve Foundation Data in ServiceNow and CSDM

In this video, Pekka Korpi, CEO of Qualdatrix, and Mikko Juola, Product Owner of Data Content Manager, discuss the importance of Foundation data in ServiceNow and how it can be improved using Data Content Manager. Foundation Data in ServiceNow refers to the critical...

Build a Business Case for Data Quality Improvement

Build a Business Case for Data Quality Improvement

Accurate and reliable data is the backbone of any successful organization. Countless data quality improvement projects are started across organizations since poor data quality can lead to misinformed decisions, wasted resources, and lost opportunities. On the other...

How Metsä Group Improves Data Quality with DCM

How Metsä Group Improves Data Quality with DCM

Metsä Group uses Data Content Manager to improve data quality in their CMDB. We had a chance to interview Mika Lindström, the ICT Configuration Development Manager at Metsä Group. Thanks, Mika, for joining us. Metsä Group are an internationally operating frontrunner...

How to use CSDM to Improve Incident Management

How to use CSDM to Improve Incident Management

It’s been a while since this article was originally published, so I thought it would be time to update it to reflect changes to the CSDM model and our latest thinking. We published this article first in 2020 when ServiceNow’s Knowledge event included the first...

How to Get Started with CSDM in 5 Steps

How to Get Started with CSDM in 5 Steps

Getting started with CSDM is easier if you have a simple model for implementation. We think that the 5-Step Model we present here is helpful. It works well with any data model, and it works well with CSDM alignment and the CMDB. Maintaining high Data Quality in CMDB...

How CMDB Supports Regulatory Compliance at Danske Bank

How CMDB Supports Regulatory Compliance at Danske Bank

Data Content Manager improves data quality within an organization’s CMDB, reducing manual and disparate work for data quality maintenance. This increase in data transparency and ease of data management helps companies to achieve and maintain regulatory compliance,...

Get Started

Book a Call with us Now.


Explore how Data Content can enhance the quality of your data in ServiceNow. See how you can accelerate your CSDM journey and improve your CMDB or any data in your platform. All without the need for scripting, additional reports, or customizations.


Related Content You Might Like:


The Recipe For Success eBook

  • Establish Ownership & Roles
  • Manage Your Scope
  • Choose the Right Tools

We talk to people about CSDM alignment every day and constantly see organizations struggle with the same things over and over again. We wrote CSDM - The Recipe for Success to share our experiences.

It gives you hands-on guidance on some of the most important things you must address on your CSDM Journey, regardless of your maturity level.

CSDM The Recipe for Success eBook

Get Your Free eBook