is business application mandatory as per CSDM?

[mehak1890]

Hi Dear All,

I'm bit confused about CSDM between business application and Technical Service. We are validating the business application in our organization, but most of the cases business application is not there. They are saying that all the applications or product they use are mainly used by Technical teams , not Business users. If they change the class of Technical Service to Business Application then how we will be able distinguish between technical Applications or Business Applications.

But as per Application owners, they are saying that why Business Application is mandatory if Technical Service already there in ServiceNow. Yes this is Technical Service not business application, they help in dataflow between multiple applications. 

Can anyone help on this? Do we really need business application as per CSDM 4.0 if its not there in ServiceNow? if yes then why?

Its very important for me to understand the CSDM process.

Thanks ,

Mehak

[Holger Buchner]

Dear Mehak,

Business Applications, Business Capabilities and Information Objects are entities in the CSDM that are mainly used to model the purpose of deployed it components and technical services. A Business Application describes an abstract object that is used to clarify ownerships (business owner), the purpose (what business capabilities does it enable).
The bridge to the deployed configuration items is the applcation service CI that is related to the business application. 
You are usually making use of business applications, if you want to document your current state or future state of enterprise architecture as an additional or new facete to application portfolio management.

For Risk management, it might be usefull to collect the assessments on business application level too, instead of managing all the related underlying CIs individually.
I hope, that helps,
Holger

[Geoff Lamb]

Not from a CSDM point of view, but we have made it mandatory from a business process point of view. 

We track costs, risks, vulnerabilities, ownership, DR compliance, information assets etc at the rolled up Business Application. Every widget can roll up to a Business Application so we know who owns it and is responsible for it, otherwise you have a bunch of orphaned CI's. It means that we have a bunch of 'bucket' Business Applications like 'Network Management' or 'Unix Management.' 

[AustinN]

I would see some of the 'bucket' applications to be Technical Services/Offerings.

[Geoff Lamb]

They are also services/offerings. But we need every widget to roll up to a Business Application, because that is how we do our accounting and ownership responsibilities (patching, lifecycle.) In our organisation, the Business Application is the 'primary key' or building blocks. We tag every widget with a APM Business App ID.

It works for us - I am not saying everyone should do it this way, and it is not prescribed by SN.