Relationship for business capability

Brian Lancaster · ‎06-15-2023

I'm trying to figure out what relationship to use for Business Capability. I found this post that says Business Capability should be related to Services based on the suggested relationship. However, for some reason in my instance Business Capability has no suggested relationships. I decided to look at my PDI but suggested relationship is not with Services instead it is with "uses" Unique Certificate.

Edit: I just had my manager setup a PDI that had nothing installed. There are no suggested relationships in the PDI either. It appears the one in my PDI is because I had installed some of the store apps that expand the CMDB.

So I have three questions.

1. What should the relationship should you use for Business Capability?

2. What CI should it be related to?

3. What if I have parent child relationship between Business Capabilities?

MaggieT · ‎06-19-2023

Hi Brian,

1. The CSDM has that a Business Application can be directly related to:

Other Business Applications (parent - child)
Business Capability (Provides - Provided By)
Application Service (Consumes - Consumed By)
Information Objects (Uses - Used By)

2. Your CIs should be related to an application service and then the application service relates to Business Application.

3. It is possible to have parent - child relationship between Business Capabilities. The top Parent Business Capability should be set at level 0 then child capability set at level 1 and so on. You will then be able to view all related business capabilities in the dependency view of the Business Application.

Have you tried to manual add a relationship to a Business Application record? If you try to manually add relationships, the suggested relationship is available OOTB.

Hope this helps.

Cheers,

MaggieT

View solution in original post

Tomas Lozano · ‎06-16-2023

Hi Brian

You can relate capabilities to the business applications the capabilities themselves depend on using the CI relation Provided by::Provides.

Re: Parent/Child relation

You can map to business applications at any capability level so there is no right or wrong. My personal recommendation would be to consider using certain levels as "taxonomy nodes" and only link to business applications at the lowest level.

Thanks,

Tomas

jeevitha gopi · ‎11-16-2024

can we map the business application to a taxonomy nodes in a bulk way instead mapping each business application seperately? in a business application table can we update in a bulk in alist view or something?

Riya Verma · ‎06-16-2023

Hi @Brian Lancaster ,

Hope you are doing great.

What should the relationship be for Business Capability?: the recommended relationship for Business Capability is typically established with Services..
What CI should Business Capability be related to?the Business Capability should ideally be related to Configuration Items (CIs) that represent the Services being provided. By establishing this relationship, you can associate the Business Capability with the relevant CIs, enabling better visibility and management of the Service dependencies. The exact CI type would depend on your specific ServiceNow configuration and the nature of the Services you are working with.
What if there is a parent-child relationship between Business Capabilities? If you have OOB parent child relatinship the you can use them.To establish the parent-child relationship between Business Capabilities, you can utilize a reference field that refers to another Business Capability record. This reference field would be configured to point to the parent Business Capability record, thus establishing the hierarchical connection.

Please mark the appropriate response as correct answer and helpful, This may help other community users to follow correct solution.
Regards,
Riya Verma

Brian Lancaster · ‎06-16-2023

We did that for number 3 but then there is no relationship when it comes to looking at the dependence view.