How the mapping of Business capabilities with Business Services should be done?

[Suggy]

How the mapping of Business capabilities with Business Services should be done?

Ex - lets say we have a Service called 'EUC'

and lets say we have capabilities like :

1. Hardware support

2. Software support (this is parent) and it has child capabilities like '2.1 Software installation', '2.2 Software uninstallation'

Now question is, 

Q1 - If I map EUC with parent capability "Software support", I believe it also means it supports the other 2 child capabilities. In that case I open the EUC, it does not show the 2 child capabilities.

Is that expected behavior? should we explicitly map the 2 child capabilities?

[AJ-TechTrek]

Hi @Suggy ,

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.

Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.

Thanks

AJ

Linkedin Profile:- https://www.linkedin.com/in/ajay-kumar-66a91385/

[Suggy]

Hi @AJ-TechTrek Thanks for replying. I have asked specific pin pointed quesion. Your response is generic 🙂

[WayneOdom · Accepted solution]

I can't speak for ServiceNow, but as an Enterprise Architect, that would be expected behavior.   Generally speaking, in our company we don't define lower level capabilities or requirements until we have a business need to do so.    And business applications that enable a specific capability may not necessarily enable all the child capabilities.    So we would explicitly associate them with the business application in question.   

I would be cautious about over developing your capability model.   People tend to go too granular, too fast, and end up with a hard to manage capability model.    I would go look at example capability models out there posted in business architecture literature, or on the Open Group, and not go deeper than 3 levels of decomposition. 

[Suggy]

@WayneOdom Thank you for replying.

I see that once you add the capability to the BA, and if there are multiple child for this capabillity, ALL those child capability are automatically showing up on the Dependency map.

And thank you for sharing your inputs on the capability levels. I agree we need to be cautious here. ServiceNow allows to create upto 6 levels and our customer is going until that. I would talk to them on this 🙂