How to model the Client Software's being modelled in ServiceNow CSDM

perumalselvam · ‎02-11-2025

Anyone has a best practice used for this modelling with the usage of CSDM with different classes

Business application

Application services

Software Model

Software installation

Installed devices (Computer/Infra)

Jonathan Schnei · ‎02-17-2025

In CSDM 4.0, there is not 'relationship' path between the Business App and the SW Model/Installation (nor does there need to be). Importantly, only use relationships between CI classes (in line with CSDM).

You can relate the records above that are CI's (Business App, App Service, Infra CI) like so: Business App consumes App Service runs on Infra CI (server, device, etc). At the same time, you have the other records (SW models, SW Installs, Infra) which use references like so: SW Install references SW Discovery Model references SW Model; and SW Install references Infra CI (the device it was discovered on). An important distinction needs to be kept in mind for those Infra CI's - for client SW the, the Infra CI's for the Business App (ie the Server an App runs on) is not the same Infra CI that the SW install was discovered on (ex/ end user devices like laptops). In this way, you are not connecting Business Apps to client SW models via a relationship, and that is OK since the records are used for very different purposes. And you can connect infra SW to BA's via TPM within Enterprise Architecture - but that is to understand technical risk to your BA's from the infrastructure HW/SW product lifecycle, not to connect BA's to SW models.

However, there is a different connection point you can consider - the Contract. A contract (in the CI's covered related list) references all CI's it covers (like Business Apps). It also has an Assets Covered related list to reference the SW licenses and Entitlements it covers. Therefore, the contract can be the connective tissue between Business Apps and SW models. In this way, the BA can be used for Enterprise Architect to align with organization strategy & capabilities and understand the supporting operational infrastructure, while the SW models can be used by SAM owner to track and manage SW licensing, entitlements, & compliance. And then EA and SAM meet in the middle at the Contract that covers the App/SW.

View solution in original post

Dr Atul G- LNG · ‎02-11-2025

Hi @perumalselvam

My knowledge says CSDM is only used for Services, and these software are like helping to provide these services, I might be wrong but need to follow the thread.

@John Zhang1 inputs please.

*************************************************************************************************************
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.

Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]

****************************************************************************************************************

John Zhang1 · ‎02-11-2025

Business Application form have both Application type and Architecture type field, which are used for any type of application/software modelling.

Jonathan Schnei · ‎02-17-2025

In CSDM 4.0, there is not 'relationship' path between the Business App and the SW Model/Installation (nor does there need to be). Importantly, only use relationships between CI classes (in line with CSDM).

You can relate the records above that are CI's (Business App, App Service, Infra CI) like so: Business App consumes App Service runs on Infra CI (server, device, etc). At the same time, you have the other records (SW models, SW Installs, Infra) which use references like so: SW Install references SW Discovery Model references SW Model; and SW Install references Infra CI (the device it was discovered on). An important distinction needs to be kept in mind for those Infra CI's - for client SW the, the Infra CI's for the Business App (ie the Server an App runs on) is not the same Infra CI that the SW install was discovered on (ex/ end user devices like laptops). In this way, you are not connecting Business Apps to client SW models via a relationship, and that is OK since the records are used for very different purposes. And you can connect infra SW to BA's via TPM within Enterprise Architecture - but that is to understand technical risk to your BA's from the infrastructure HW/SW product lifecycle, not to connect BA's to SW models.

However, there is a different connection point you can consider - the Contract. A contract (in the CI's covered related list) references all CI's it covers (like Business Apps). It also has an Assets Covered related list to reference the SW licenses and Entitlements it covers. Therefore, the contract can be the connective tissue between Business Apps and SW models. In this way, the BA can be used for Enterprise Architect to align with organization strategy & capabilities and understand the supporting operational infrastructure, while the SW models can be used by SAM owner to track and manage SW licensing, entitlements, & compliance. And then EA and SAM meet in the middle at the Contract that covers the App/SW.

perumalselvam · ‎02-19-2025

Thank you for your detailed insight @Jonathan Schnei. Let me try this and comeback if needed.