CMDB Health Dashboard Disabled <!-- .SOKMKBArticle div.margin { padding: 10px 40px 40px 30px; color: #283d40; font-family: Century Gothic, Verdana, Helvetica, Arial, sans-serif; font-size: 10pt; } .SOKMKBArticle div.fed{ background-color: #f5f8fa; border: 1px solid; border-color: #bfbfbf; padding: 10px; } .SOKMKBArticle .FedRestricted{ background-color: #c00000; color: #ffffff; padding: 10px; margin-top: 10px; text-align: center; font-size: 14pt; font-weight: bold; } .SOKMKBArticle .CustRestricted{ background-color: #ff0000; color: #ffffff; padding: 10px; margin-top: 10px; text-align: center; font-size: 14pt; font-weight: bold; } .SOKMKBArticle .SNRestricted{ background-color: #ea700d; color: #ffffff; padding: 10px; margin-top: 10px; text-align: center; font-size: 14pt; font-weight: bold; } .SOKMKBArticle .SNConfidential{ background-color: #ffc000; color: #ffffff; padding: 10px; margin-top: 10px; text-align: center; font-size: 14pt; font-weight: bold; } .SOKMKBArticle .Public{ background-color: #00b050; color: #ffffff; padding: 10px; margin-top: 10px; text-align: center; font-size: 14pt; font-weight: bold; } .SOKMKBArticle table.tocTable { border: 1px solid; border-color: #f2f2f2; background-color: #f2f2f2; padding-top: .6em; padding-bottom: .6em; padding-left: .9em; padding-right: .6em; } .SOKMKBArticle table.noteTable { align: left; border: none; border-color: #81b5a1; background-color: #f2f2f2; width: 100%; border-spacing: 2; font-size: 11px; } .SOKMKBArticle table.internalTable { border-top: 1px solid; border-left: 1px solid; border-color: #81b5a1; width: 100%; border-spacing: 1px; } .SOKMKBArticle .sp td { border-bottom: 1px solid; border-right: 1px solid; border-color: #81b5a1; background-color: #ffffff; height: 20px; padding-top: .5em; padding-bottom: .5em; padding-left: .5em; padding-right: .5em; } .SOKMKBArticle .sphr td { border-right: 1px solid; border-bottom: 1px solid; border-color: #81b5a1; background-color: rgb(245, 245, 245); padding-top: .5em; padding-bottom: .5em; padding-left: .5em; padding-right: .5em; height: 20px; } .SOKMKBArticle .sh td { border-bottom: 1px solid; border-right: 1px solid; border-color: #81b5a1; background-color: #81b5a1; color: #ffffff; height: 20px; padding-top: .5em; padding-bottom: .5em; padding-left: .5em; padding-right: .5em; } .SOKMKBArticle th { padding-top: .5em; padding-bottom: .5em; padding-left: .5em; padding-right: .5em; border-bottom: 1px solid; border-right: 1px solid; border-color: #646464; background: #646464; font-family: Century Gothic, Verdana, Helvetica, Arial, sans-serif; font-size: 10pt; color: white !important; height: 20px; } .SOKMKBArticle td { border-color: #646464; margin: 5px 5px 5px 5px; padding: 5px 5px 5px 5px; font-family: Century Gothic, Verdana, Helvetica, Arial, sans-serif; font-size: 10pt; color: #283d40; } .SOKMKBArticle p { color: #283d40; font-family: Century Gothic, Verdana, Helvetica, Arial, sans-serif; } .SOKMKBArticle li { color: #283d40; font-family: Century Gothic, Verdana, Helvetica, Arial, sans-serif; font-size: 10pt; line-height: 1.5; } .SOKMKBArticle pre { font-family: Courier New; } .SOKMKBArticle div { font-family: Century Gothic, Verdana, Helvetica, Arial, sans-serif; } .SOKMKBArticle hr { border-top-width: 1px; border-top-style: solid; border-top-color: #81b5a1; } .SOKMKBArticle a { color: #81b5a1; } .SOKMKBArticle a.two:link { padding: 15px 45px 15px 45px; margin-top: 20px; color: #ffffff; text-align: center; background-color: #1F8476; border: 1px solid; border-color: #1F8476; } .SOKMKBArticle a.two:visited { padding: 15px 45px 15px 45px; margin-top: 20px; color: #ffffff; text-align: center; background-color: #1F8476; border: 1px solid; border-color: #1F8476; } .SOKMKBArticle a.two:hover { color: #ffffff; background-color: #259b8a; } .SOKMKBArticle .button { padding: 15px 45px 15px 45px; margin-top: 20px; color: #ffffff; text-align: center; background-color: #1F8476; border: 1px solid; border-color: #1F8476; } .SOKMKBArticle .title { font-family: Century Gothic, Verdana, Helvetica, Arial, sans-serif; color: #81b5a1; font-size: 30pt; } .SOKMKBArticle .hd1 { font-family: Century Gothic, Verdana, Helvetica, Arial, sans-serif; color: #283d40; font-size: 20pt; border-bottom: 1px solid; border-bottom-color: #81b5a1; text-decoration: none; } .SOKMKBArticle h1 { font-family: Century Gothic, Verdana, Helvetica, Arial, sans-serif; color: #283d40; font-size: 20pt; font-weight: normal; border-bottom: 1px solid; border-bottom-color: #81b5a1; text-decoration: none; } .SOKMKBArticle .hd2 { font-family: Century Gothic, Verdana, Helvetica, Arial, sans-serif; color: #68a1af; font-weight: bold; font-size: 16pt; text-decoration: none; } .SOKMKBArticle h2 { font-family: Century Gothic, Verdana, Helvetica, Arial, sans-serif; color: #68a1af; font-weight: bold; font-size: 16pt; font-weight: normal; text-decoration: none; } .SOKMKBArticle .hd3 { font-family: Century Gothic, Verdana, Helvetica, Arial, sans-serif; color: #283d40; font-weight: normal; font-size: 14pt; text-decoration: none; } .SOKMKBArticle h3 { font-family: Century Gothic, Verdana, Helvetica, Arial, sans-serif; color: #283d40; font-weight: normal; font-size: 14pt; text-decoration: none; } .SOKMKBArticle .hd4 { font-family: Century Gothic, Verdana, Helvetica, Arial, sans-serif; color: #283d40; font-weight: normal; font-size: 12pt; text-decoration: none; } .SOKMKBArticle h4 { font-family: Century Gothic, Verdana, Helvetica, Arial, sans-serif; color: #283d40; font-weight: normal; font-size: 12pt; text-decoration: none; } .SOKMKBArticle .hd5 { font-family: Century Gothic, Verdana, Helvetica, Arial, sans-serif; color: #283d40; font-weight: bold; font-size: 10pt; text-decoration: bold; } .SOKMKBArticle h5 { font-family: Century Gothic, Verdana, Helvetica, Arial, sans-serif; color: #283d40; font-weight: bold; font-size: 10pt; text-decoration: bold; } .SOKMKBArticle .hd6 { font-family: Century Gothic, Verdana, Helvetica, Arial, sans-serif; color: #283d40; font-weight: normal; font-size: 10pt; text-decoration: underline; } .SOKMKBArticle h6 { font-family: Century Gothic, Verdana, Helvetica, Arial, sans-serif; color: #283d40; font-weight: normal; font-size: 10pt; text-decoration: underline; } .SOKMKBArticle details { font-size: 10pt; } .SOKMKBArticle details[open] summary ~ * { animation: sweep .5s; margin-top: 0; padding-top: 10px; } @keyframes sweep { 0% {opacity: 0; margin-top: -10px} 100% {opacity: 1; margin-top: 0px} } .SOKMKBArticle summary { cursor: pointer; outline: none; margin-bottom: 3px; } .SOKMKBArticle .summary { background-color: #81b5a1; font-size: 10px; color: white; cursor: pointer; padding: 5px; width: 100%; border: none; text-align: left; outline: none; vertical-align: top; } --> Get Well Playbook CMDB Health Dashboard Disabled A Step by Step Guide to enable the dashboard Table of Contents Summary Goal of this Playbook Audience Problem Overview Executive Summary How this playbook can help you achieve business goals How this playbook is structured Problem Analysis Upstream Causes Downstream Consequences Impact on Your Business Engagement Questions Remediation Plays Summary Play 1: Analyze your current state Play 2: Fix Play Data Governance Summary Goal of this Playbook The goal of this playbook is to identify and enable the CMDB Health Dashboard jobs. Details about this playbook AuthorJohn Walker (Johnny)Date08/10/2020Addresses HSD #HSD0001712Applicable ServiceNow ReleasesAll ReleasesTime requiredless than 1 hour Audience Configuration Manager or Configuration Management team - (admin role required)ServiceNow Admin or Discovery Admin Problem Overview If the CMDB Health Jobs are not enabled, the provided dashboard for CMDB Health will lack all information related to correctness, completeness and compliance. Without this vital tool for Data Governance, your CMDB will struggle to support all of the platform applications which depend on it. Executive Summary How this playbook can help you achieve business goals Accuracy within the CMDB will directly contribute to success and value in the many applications making use of it (which is most of them)Data Governance for the CMDB is provided by this built-in dashboard and the data gathering jobs which enable itProcess alignment can be measured by knowing where the gaps are within your CMDB classesAny plans to implement ITOM Visibility, Optimization or Health should all begin with this simple playbook to enable the CMDB Health DashboardMany other CMDB Get Well Playbooks will reference making use of this dashboard How this playbook is structured This Playbook is structured to guide you through four plays. The first play is to validate if any of the CMDB Health Jobs are not enabled(optional – choose one) The second play guides you through manually enabling the CMDB Health jobs(optional – choose one) The third play is a script to enable the CMDB Health jobsThe fourth play is related to governance Problem Analysis Upstream Causes Lack of a clearly designated Owner for the CMDBLack of awareness about the value provided by the CMDB Health DashboardThe CMDB Health jobs are disabled by default so that metrics are not actively collected until the CMDB is considered “live”Someone may have decided that there are so many outstanding issues within the CMDB that the dashboard “wasn’t showing a positive message”While the CMDB Dashboard was providing insight as to what was missing, incomplete or incorrect within the CMDB, where was not adequate time allocated to do anything about itLack of step-by-step directions to remediate issues within the CMDB led to a decision to disable the CMDB Health Dashboard Downstream Consequences Data Consequence If the CMDB Health Dashboard is not enabled, the three main areas of concern, Completeness, Correctness and Compliance, are all data issues within the CMDB going without governance Operation Consequence Without the CMDB Health Dashboard, the configuration management team might spend unnecessary time creating, maintaining and working customized processes to validate, maintain and support their CMDB App Consequence Without the CMDB Health Dashboard to govern issues such as lack of Completeness, Correctness and Compliance, there can be many inconsistent behaviors within Discovery, Service Mapping, Event Management, Asset Management, Hardware Lifecycle, Portfolio Management, Incident, Problem, Change, Vulnerability Response and others Impact on Your Business Lower MTTR Data Validation and Completeness When teams like the Service Desk aren’t dealing with inaccurate data, the time and effort required to triage and resolve Incidents will be lower Increase Operational Visibility Service Awareness The governance provided by the CMDB Health Dashboard will ensure that accurate information is always just a click away from the decision makersA healthy CMDB will lend itself directly to the ability to manage events taking place within your infrastructure, events which impact delivery of services across the board Audit / Compliance Data Governance The CMDB Health Dashboard is the source of record for Data Governance within your CMDBThere are certification filters available within the compliance area of the dashboard which will enable you to define a desired state for configuration items within a given class Process Gap Detection The CMDB Health Dashboard plays a vital role in ensuring compliance with any process related to Asset Management, Procurement, software licensing and more System Integrity Accuracy within all the records of the CMDB will contribute strongly to ensuring that all platform applications can function within normal, expected parameters Process Automation Digital Workflows Attempts to make use of digital workflows to support daily operations will be far simpler when foundational health has been restored to the CMDB Better User Experience Platform Awareness & Adoption Users will accept and adopt the CMDB (as well as the platform as a whole) when they know they can trust the quality of data they are presented with during daily operations Engagement Questions: Consider the answers to these questions: Is there an Owner defined for the CMDB?Are there any Configuration Management analysts working with the CMDB Owner to ensure Correctness, Completeness and Compliance within the CMDB?Have the CMDB Health jobs ever been enabled? If so, why were they later disabled?Has anyone worked with your configuration management team to help them understand the value of CMDB Health Dashboard? Remediation Plays Summary The table below lists and summarizes each of the remediation plays in the playbook. Details are included later. Play Name Analyze Play What this play is about Query to determine which CMDB Health Dashboard jobs are disabled Required tasks Run query script Fix Plays What this play is about Manually enable CMDB Health jobs Required tasks Navigate to the jobs and set them active Data Governance What this play is about Helps you establish standard operating procedures, as well as periodic data certification Required tasks Guidance related to using the CMDB Health Dashboard Play 1 - Analyze your current state What this Play is about Determine if any of the CMDB Health Jobs are disabled Required tasks Navigate to System Definition > Scheduled Jobs and search for Name starts with 'CMDB Health Dashboard'.Example:Note any of the five jobs here where Active is not set to 'true'.Proceed to the next play to remediate. Play 2: Fix Play What this Play is about All five CMDB Health Dashboard jobs need to be enabled for your CMDB Dashboard to be fully populated. Required tasks (Optional – choose one) To manually enable and later configure the CMDB Health Dashboard jobs, follow the instructions on this page or (Optional – choose one) Use this Fix Script to automatically enable all of the jobs. Data Governance What is this Play about? Guidance for CMDB Health Dashboard usage to ensure CMDB health Guidance Use ServiceNow out-of-the-box as much as possibleAvoid adding custom fields within the CMDB without a compelling business reason to do soBe careful when setting CMDB fields to Mandatory as this can prevent users from performing record updates - instead consider using recommended for fields like 'Assigned to' and 'Location'Whenever possible, make use of Discovery to populate the CMDBWhen integrating with third party discovery sources, be sure to leverage the Identification and Reconciliation EngineIf key identification criteria on records (like Serial Number) is missing, care should be taken to get that information collected and input as soon as possible Congratulations You have completed this Get Well Playbook.