Relating Applications to Application Services - Strategy

[marcglaza]

Hi - I'm wrestling with the best way to get value from my organization's service maps to be used by Incident, Problem, and Change and make this easiest for my IT user base as well as maintenance and accuracy of records.

Currently, the organization is using records application records that are manually created and maintained for Affected CI/Services.  There is no current relationship to any corresponding Application Services.  The applications in many cases are defined at a component level (think apis, cfg files, microservices, jboss, angular, etc..)  The applications in this case are home grown, some possible discovered components but assume manual.   

What is the best way to correlate the application-to-application service?   Should I relate the component CIs to the corresponding application services?  OR should I create similar application records matching my application services and then relate all the components to the new application (parent) records, thereby creating a 1:1 relationship between my application and application service and a 1:m relationship between my application parent and its children component CIs?    Or is there another best practice here that I should consider?  

[Miklos Palfi]

Hi Marc,

there are great recordings from previous Digital Service Forum sessions here:

https://www.youtube.com/playlist?list=PLkGSnjw5y2U5bshRSZTQKElcOupZFDwNp

One which could help you is this one:

Configuring ServiceNow in CSDM Recorded September 14th 2023

https://youtu.be/vepYCDhe1oY?feature=shared

The term "Application" is a bit ambiguous: we call like that the different installed applications (like databases, middlewares etc.) which are tightly related to servers and should be grouped together into application services. But we call the business applications also applications which are grouping together the different (prod/test/dev) application service instances. Which of these two do you mean by application in your terms?