Business Application with “Consumes::Consumed By” Relationship to Application Services Get Well Playbook Application Service with 'Consumes::Consumed By' Relationship to Business Application A step-by-step guide to analyze and remediate CMDB data Table of Contents Summary. 3 Audience3 Problem Overview.. 3 Executive Summary. 3 How this playbook can help you achieve your business outcome. 3 How this playbook is structured. 3 Problem Analysis 5 Upstream Causes5 Downstream consequences 5 Impact on Your Business5 Engagement Questions6 Remediation Plays 7 Summary. 7 Play 1: Analysis 8 Play 2: Fix Play – Populate Correct Relationship. 9 Data Governance. 11 Summary Goal for this Playbook To help identify and correct relationships from Application Service to Business Application tables that are not 'Consumes::Consumed By' Author Scott LemmDate 08/14/2020Addresses HSD # HSD0008108Applicable ServiceNow Releases All ReleasesPrerequisites CMDB and CSDM Data Foundations DashboardsTime required Approximately 1 to 8 hours Audience Configuration Manager or Configuration Management teamServiceNow AdminApplication OwnerTechnical Service Owner Problem Overview Application Portfolio Management (APM) uses relationships to provide value such as identifying risk to deployed instances, Application Services, related to publisher and manufacturer end-of-life (EOL) dates. A deployed application that will no longer be supported by a publisher may be a critical security and operational risk. APM requires the relationship between a business application and application service use 'consumes::consumed by'. If the relationships between Application Services and Business Applications are not 'consumes::consumed by' APM will not be able to provide Technology Portfolio Management capability. This playbook helps you identify those Application Services without 'consumed::consumed by' relationships to Business Application instances. Executive Summary How this playbook can help you achieve your business outcome Application Services, with 'consumes::consumed by' relationships to Business Applications, provide capability to mitigate risk, improve MTTR, reduce costs and rationalize application use. How this playbook is structured This Playbook will guide you through 3 plays. Play 1 (an analysis play) helps you identify which Application Service CIs in your CMDB do not have 'consumes::consumed by' relationship(s) to Business Applications.Play 2 (a fix play) tells you how to replace a relationship to 'consumes::consumed by' on an Application Service from the form viewPlay 3 (a Data Governance play) lists the guidelines and processes for relationship management between Application Service and Business Application. Use these guidelines to maintain effective data in your CMDB. Problem Analysis Upstream Causes Transforms are loading Application Services and relationships but not the 'consumes::consumed by' relationship type3rd party tags are not providing the correct relationship.You may not be aware that relationships between Application Services and Business Application should be 'consumes::consumed by'. Downstream consequences Data Consequence Data will not be populated despite a relationship presentBusiness decisions made based on incorrect data Operation Consequence Erodes trust in the accuracy of the CMDB. Results in a poor user-experienceProcesses that rely on CI relationship 'consumes::consumed by' will be unable to process dataReporting will lack correct data, unable to associate Design Domain and Manage Technical Services Domain elements as expectedApplication owners may be unaware of operational applications are end-of-life, without publisher support Application Consequence Application costing data will be inaccurateApplication rationalization will not functionRisk is unable to identify where sensitive data may be deployed Impact on Your Business Missing relationships from Application Service to Business Application affect the following areas of your business A poor User Experience (internal & external) making Work harder than it needs to beErosion of CMDB trust accompanied with a general lack of adoption and enthusiasmSecurity - Unable to display knowledge of deployed applications without publisher supportAudit compliance - Unable to show total costs Engagement Questions Consider answers to these questions: What are the major sources of application service CIs in your CMDB?Are 3rd party integrations populating your business application to application service relationships?Do you import data manually? If so, what process do you use? Does your process include populating relationships? Remediation Plays Summary Play Name Play 1: Analysis What is this play about Identify which Application Service CIs in your CMDB do not have 'consumes::consumed by" relationship(s) to Business Application Play Steps Run report to help identify target CIs Play 2: Fix Existing Data What is this play about Populate correct relationship Play Steps Add correct relationship and remove bad relationship to a Application Service from the form view Play 3: Data Governance What is this play about Helps you establish standard operating procedures, as well as periodic data certification Play Steps Provides detailed advice, best practices and data audit instructions Play 1: Analysis What this Play is about Identify which Application Service CIs in your CMDB do not have 'consumes::consumed by' relationship(s) to Business Application Required tasks Install CMDB and CSDM Data Foundations Dashboard from the ServiceNow App StoreNavigate to the CSDM Data Foundations Dashboard module in the left navigation menuSelect the Crawl tabSelect the App Service to Business App Relationship not Consumed By report to view a list of application services CIs that are missing 'consumes::consumed by' relationships to business application. Play 2: Fix Play – Populate Correct Relationship What this Play is about This play tells you how to add 'consumes::consumed by' relationship while removing incorrect relationship on an existing application service CI using the form view of an application service. Required tasks Open an application service from the App Service to Business App Relationship not Consumed By report Scroll down to Related items on the form and view the results. In the Related items section, select the + button, which says Add CI Relationship when you hover over it. Add a new CMDB relationship The CMDB relationship editor opens. Scroll down to Relationships. A list of existing relationships will be displayed. Check the box of the Business Application relationship(s) you wish to delete (1) then the trash can sign (2) to remove the Relationship(s) from the list. Now add the correct relationship. Ensure Consumed by (child) is the Suggested relationship type. Set Class to filter by Business Application (1) and select Run Filter (2) to view only the Business Application CI types. In the Configuration Items list check the box of the Business Application(s) you wish to create a relationship to (1) then the + sign (2) to add the Relationship(s) to the list below (scroll down to view new relationship). Now hit Save and Exit. A confirmation pop-up will want to confirm your change to the CMDB, choose OK. Data Governance What this Play is about This play lists the best practices and processes for application service relationships using 'consumes::consumed by' Required tasks Periodically review the CSDM Data Foundation dashboard report to see if there are any application services missing relationships to business application. Congratulations You have completed this Get Well Playbook.