Business Capabilities association

[TaylorJ78]

I am mapping business capabilities to both business applicaiton and business services.  When I attempt to build the relationship, I am also finding mapped application service class records in my search (see example 1).  The search criteria states Business Application and Business Service only.  

My questions are: 1. If the service started as a Business Service but was converted to an application service (csdm 3.0) is it still technically considered a business service even though the class has been modified to an Application Service?
2. By moving all business services to the table, cmdb_ci_service_buisness (csdm 4.0) will this resolve the issue above for mapping business capabilities or is this a glitch in the system and we need to be careful when relating business capabilities?

[cassieb_]

You may want to check with the CI Class Manager to see if you have two Business Service classes, earlier releases had what is now "Service" as "Business Service". Otherwise you might change your "is a" to "is".

[EricDohr · Accepted solution]

@cassieb_ nailed it.  In many cases, if you have an instance that originally had the Services table [cmbd_ci_service] and then later introduced Business Services [cmdb_ci_service_business] you may see two tables with the name Business Service.  In newer instances, you can see the labels updated as seen below on the sys_db_object table.  I have seen customers update the label of cmdb_ci_service as a result of the new table to help avoid confusion.

Now if we look at the CI Class Manager and you look at the Business Capability record, you may see suggested relationships still to Service vs. Business Service.  If you leave it this way, you will see records that fall into tables that are extended by Service such as your Application Services. 

So back to your questions....

The Business Service table [cmdb_ci_service_business] is an extension fo the Service table [cmbd_ci_service].  As a result, records in lower tables will show in upstream tables.  Vice versa, if you looked only at the Business Service [cmdb_ci_service_business] table, you would not see tables upstream or in parallel that were extended by Service [cmdb_ci_service]  

For your second question, if you either adjust the existing query after your recommended relationship or you update the suggested relationship in the CI Class Heirarchy, that would potentially help.  Note, if you have not moved records into the new table though and you adjust the suggested relationship, you may not see records.

Hope this helps

[CMDB Whisperer]

All customers can and should change the Label of cmdb_ci_service to "Service" so that it matches what you will see in a fresh instance, to avoid further confusion.  I believe ServiceNow didn't include that change when they introduced the Business Service class, opting to leave it to customers to make this change on their own.