Application Services with Business Service Offering Relationship Get Well Playbook Application Service with Business Service Offering Relationship A step-by-step guide to analyze and remediate CMDB data 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: Analysis Play 2: Fix Play - Populate Missing Relationship Data Governance Summary Goal of this Playbook Goal of the Playbook Details about this playbook Author Scott LemmDate 08/19/2020Addresses HSD # HSD0007986Applicable ServiceNow Releases All ReleasesPrerequisites CMDB and CSDM Data Foundations DashboardsTime required Approximately 1 to 4 hours Audience Configuration Manager or Configuration Management teamServiceNow AdminService OwnerTechnical Service Owner Problem Overview Application Service is a service type that is a logical representation of a deployed application stack. It is a unique deployed instance of a Business Application. These Application Services often impact the business. The business is represented as Business Service Offerings with relationship from Application Service to Business Service Offering in the CMDB. Together these CIs provide a complimentary summary of the technology provided for the business to consume. If the relationships between Application Services and Business Service Offering are missing (unpopulated) then an Application Services will lack the ability to show and relay impact to the business. This playbook helps you identify those Application Services without relationships to Business Service Offerings. Executive Summary How this playbook can help you achieve business goals Application Services, with relationships to Business Service Offerings, provide a view into the potential and active impact technology has on the business. Business Services that depend on technology need to know when those services may be impacted in addition to providing rapid MTTR for any incidents that arise. The Application Service to Business Service Offering relationship is critical to maintaining business services. 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 relationship(s) to Business Service OfferingsPlay 2 (a fix play) tells you how to add a relationship to 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 Service Offerings. Use these guidelines to maintain effective data in your CMDB Problem Analysis Upstream Causes CI relationships are not enabled on the Application Service form viewTransforms are loading Application Services but not relationshipsServiceMapping is auto generating Application Services but relationships to Business Service Offerings are not discoverable3rd party tags are not providing the Business Service OfferingYou may not be aware that relationships between Application Services and Business Service Offerings are necessary Downstream Consequences Data Consequence Unable to share data between related CIsData silos will occur that can lead to unwelcome customizations Operation Consequence Erodes trust in the accuracy of the CMDB. Results in a poor user-experienceProcesses that rely on CI relationship hierarchy will be unable to process dataReporting will lack data, unable to associate technology to the business that sells or consumes said technologyActive impact of Application Services to the business is unknown to the help desk App Consequence Incident Management MTTR increases due to a lack of rapid identification into the cause of business impact from an Application ServiceIncident and Change criticality is unaware of business impact from Application ServicesITOM Health is unable to support service impact without a relationship to the Business Service OfferingsService Owner Workspace is unable to track and remediate outages caused by Application Services or elements of an Application ServiceService Owner Workspace is unable to document total costService Owner Workspace is unable to show accurate service status Impact on Your Business Missing relationships from Application Service to Business Application affect the following areas of your business A poor User Experience (internal and external) making Work harder than it needs to beErosion of CMDB trust accompanied with a general lack of adoption and enthusiasmSecurity - Unable to identify impact to servicesAudit compliance - Unable to show complete ownership and impactIncreased MTTR - Without relationships support teams will struggle to identify design details about a deployed application Engagement Questions: Consider the answers to these questions: What are the major sources of application service CIs in your CMDB?Do you know what your Application Services do for the business?Do you import data manually? If so, what process do you use? Does your process include populating relationships? Remediation Plays Summary The table below lists and summarizes each of the remediation plays in the playbook. Details are included later. Play Name Play 1: Analysis What this play is about Identify which Application Service CIs in your CMDB do not have relationship(s) to Business Service Offerings Required tasks Run report to help identify target CIs Play 2: Fix Existing Data What this play is about Populate missing relationship Required tasks Add a relationship to a Service Application from the form view Data Governance What this play is about Helps you establish standard operating procedures, as well as periodic data certification Required tasks 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 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 Run tabSelect the App Service Missing Business Service Offering Relationship report to view a list of application services CIs that are missing relationships to business service offerings. If you see a count of zero then this playbook is not applicable to you. Play 2: Fix Play - Populate Missing Relationships What this Play is about This play tells you how to add a relationship to an existing application service CI using the form view of an application service Required tasks Open an application service from the App Service Missing Business Service Offering Relationship report Scroll down to Related items on the form and view the resultsIn the Related items section, select the + button, which says Add CI Relationship when you hover over it. Add a new CMDB relationshipThe CMDB relationship editor opens. Ensure Used by (child) is the Suggested relationship type. Set Class to filter by Service Offering (1) and select Run Filter (2) to view only the Business Application CI typesIn 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 relationshipNow hit Save and Exit. A confirmation pop-up will want to confirm your change to the CMDB, choose OK Data Governance What is this Play about? This play lists the best practices and processes for application service relationships Required tasks Periodically review the CSDM Data Foundation dashboard report to see if there are any application services missing relationships to business service offerings Congratulations You have completed this Get Well Playbook.