Cmdb And Csdm Data Foundations Dashboards – We work with data quality and management every day, so we’re constantly talking to people on their CSDM journeys who wonder how to know if you’re already crawling, walking, running or flying. Out of the box you get tools like the CSDM Data Foundation Dashboard, which are a good start but won’t take you all the way.
Let’s take a look at the CSDM Data Foundations dashboard and compare it to the Data Content Manager to see what the difference is and to get the right answer to the question. I will limit crawling in this article and then expand to walking and running.
Cmdb And Csdm Data Foundations Dashboards
The CSDM Data Foundations Dashboard is a free, scalable tool for tracking key data quality indicators at each stage of CSDM implementation. You can find it in the ServiceNow Store.
Servicenow Domain Expertise — Beniva Consulting Group
You will receive an actual score vs. a target (=100%) for these three things and a link to a playbook that describes what to do to improve your results.
However, compared to what the CSDM whitepaper (link to CSDM 4.0 draft) says about the drag phase, this dashboard only covers one relationship (in both directions) from the model of all creep phase data.
IT infrastructure under application services or the new SDLC component CI class? Or a business application, application service, SDLC component, or some specific attribute in technical CI classes such as server, application, or network equipment?
While the dashboard provides valuable metrics, it doesn’t feel complete. Having that one relationship is a good start, but that alone does not make you compliant with the CSDM crawl phase requirements.
Platform: Configuration Management Database (cmdb)…
Waiting for something that may or may not happen in the future is usually not a viable option. You need results now. So, let’s look at some of the challenges associated with adding more indicators to this dashboard:
In general, waiting or going the script route are unnecessarily complicated and time-consuming options. They cost money in time spent or licenses. Also, you will not get instant results.
Let’s see how you can overcome these limitations with a visual and intuitive tool like Data Content Manager:
First let’s make the dashboard OOB with DCM, creating two super-simple blueprints. The first one will check if all business applications have a CI relationship with the “consume::consume” application services. Someone else will check the same link in the opposite direction. They will look like this:
Live From New York Its Now Learning It Service Man…
The CSDM Foundation Dashboard makes both of these blueprints simple. They examine the “uses::consumption” relationship from both directions. They only take a few minutes to create when you install DCM.
As I mentioned earlier, the above does not make you compliant with the CSDM crawl. In real life, you may want to check other things. So let’s look at a plan that includes all the classes in the crawl phase and some important foundation data references that go beyond the minimum crawl requirement.
Effectively, if your data conforms to this plan, you are compliant with CSDM crawling from a data model perspective. Although it sounds complicated, this blueprint takes about 15 minutes to draw, and you can start with our free CSDM templates.
These blueprints are not just static images, but can include dynamic states based on the data you want to verify.
Cmdb Data Foundations Dashboard.mov On Vimeo
So, for example, you can define that the downstream connections from the application service to the application or server are only required for production environments. Or simply having an application or server under the application service.
In this case, the audited records are business applications, and you can easily see which ones deviate from the blueprint you used for the audit.
Collected from blueprint elements, you can get a quick overview of which areas of your data model (blueprint) are in good shape and where work needs to be done. For example, in this case you can immediately see that all your business applications have an IT application owner.
Detailed verification messages describe exactly what is correct and what is not. Here is an example of verification messages for one of the verified business applications called “Customer Portal”.
Create And Use Dashboards
This level of detail is available for any individual audit context. You can automatically create tasks based on this, and you can use the baseline to resolve deviations found by the audit.
DCM comes with advanced reporting capabilities and integrated dashboards. They are based on blueprints you define, not rules imposed by someone else. You don’t need case-specific scripting or reports. Just define your requirements in blueprints, let the audits run, and you will get results.
I believe the above audit dashboard gives you a complete picture of whether you are compliant with the CSDM crawl or not. The CSDM Data Foundations dashboard only gives you part of the big picture.
We’ve written about the difference between Data Content Manager and ServiceNow’s out-of-the-box tools in the past, and we’ll continue to do so in the future.
Steps To Get Business Applications Under Control
In my next article I will look at the CSDM word phase. I’ll show you how to take dashboards to a personal level for the people you depend on to keep your data up to date. Personalization is very powerful in creating a sense of ownership and data ownership.
Please contact us so you can demonstrate what we’ve described here along with many other things that help improve the quality of your data in ServiceNow. (This article was originally published in 2019, republished in 2021 and updated accordingly. For CSDM 4.0 in 2022)
ServiceNow published the Common Service Data Model three years ago. Since then, the ServiceNow community has been clamoring for examples of CSDM and more details on how to implement the model in the real world.
In February 2019, I wrote a blog post discussing the model from a service portfolio perspective to understand how to interpret the whitepaper in practice. I thought it would be a good time to rewrite that post and reflect on how the model has evolved and what the business services portfolio piece looks like today.
Everything You Need To Know About Servicenow
ServiceNow has updated their Common Service Data Model (CSDM) whitepaper a few times since its original publication in 2018:
In October 2020, we were pleased to co-present a webinar series on version 3.0 with Mark Bodman from ServiceNow. You can find our thoughts and a summary of the CSDM 3.0 Webinar Series here.
Again a year later, we received CMDB 4.0 examples for a Data Driven Portal webinar from ServiceNow with Venny McCarranen.
As of 2018, whitepaper updates continue to provide more detail and CSDM examples, while the overall concept and message remain the same. Here are some key messages from different versions of the whitepaper:
Implementing A Self Healing Servicenow Cmdb With High Quality Data
In the original post I talked about the lack of a true data model. The whitepaper provided only a very high-level conceptual model, a list of actual tables, the conceptual model, and a list of relationships to be used between the classes. So, I also provided some CSDM examples.
We’ll talk more about data models later, but here’s a quick blast from the past, the CSDM Conceptual Model v1.0:
Later versions of the CSDM included more detail in their still conceptual data model diagrams and, most importantly, differentiated between technical and business services. This evolves to a model where these records are managed in separate tables rather than using a service classification in a common service CI class.
Since CSDM 2.0, technical and business services belong to their own domains, each identifying different stakeholders. Version 4.0 introduced a new building domain, but the relationship with services through application services still remained the same.
Servicenow Csdm: Evolution & Csdm Examples
The figure below shows the service part for versions 2.0 and 3.0 equivalent to this part. The same applies to 4.0 as the building domain is optional between the Business Application and Application Service classes.
CSDM has a strong focus on applications. It has been heavily criticized. Different customers are eager to see more common examples of CSDM and use cases that do not involve business applications as proposed.
Personally I feel that “Application Service” can be replaced by “Configuration Object” where depending on the service, any CI can be directly related to service offerings in the Cell / Consume domain.
I left the design and construction of domains out of this CSDM example image on purpose, mainly to emphasize that services can exist without any connection to application services or business applications.
Importance Of Foundation Data With Examples
Think of end-user services, for example: a CI workstation must be directly linked to a business service offering that describes exactly how that work is delivered to a customer and the catalog items, levels of service, and other commitments associated with the service.
It also raises the question of the type of relationship between the business service offering and the application service: dependent. This is a type of logical relationship when a business service depends on an application (or any other CI) for its delivery.
Excel dashboards & data visualization, data quality dashboards, data dashboards for schools, data visualization dashboards, cmdb data model, foundations of data science, best data studio dashboards, data studio marketing dashboards, best data dashboards, data dashboards, cmdb csdm, cmdb data
