Actions

Difference between revisions of "Business Capability Modeling"

m
Line 2: Line 2:
  
 
In other words, business capability modeling is graphically representing the abilities of the company, as well as its potential. When business architects and analysts engage in business capability modeling, their work results in the creation of a capability model. This forms the core of business capability mapping, which enables adaptive, sleek architectures that can respond quickly to changes in today's competitive business landscape. The first stage of the mapping [[process]] is identifying the highest-level [[Business Capability|capabilities of the business]]. Typically, these are oriented towards the operational side. After they’re all documented you can start decomposing these top-level capabilities into lower-level capabilities. At this point you may choose to create an exhaustive model and keep every single sub-capability. Alternatively, you could discard all but the ones most relevant to the achievement of [[Business Goals|business goals]]. This doesn’t automatically entail negative consequences. Keeping your eyes on the whole business landscape is laudable during this process but capabilities that aren’t critical may safely be omitted during the mapping process. This of course also depends to a large degree on the timeframe of the project and the number of allotted personnel. Once you have an agreed upon capability model, you and your team should start listing attributes for each individual capability and [[service]] level expectation. These may differ from company to company, but usually what you’ll be looking at are things such as performance requirements, capability owner, customers, inputs and outputs, as well as general information on the elements that compose it – people, processes, and technology. All this knowledge captured as part of the [[Business Architecture|business architecture]] will later help you derive the exact requirements for the [[IT Infrastructure|IT infrastructure]]. The goal of this practice is to model the business around its most stable elements. This is because although the way in which a company powers its abilities may change dramatically with time (the How), the actual abilities are usually unfluctuating even on long time scales (the What). For instance, it’s very plausible for a [[manufacturing]] company to have had a capability called Deliver [[Product]] for the past century. The way in which this capability might have been fulfilled throughout the years however will have varied immensely (i.e. horse-drawn carriage, train, truck etc.). The main benefit of having a model based on the most resilient elements of the business is its longevity. Changes to how capabilities are implemented don’t necessarily alter the base model. What’s more, with a stable business model the IT infrastructure of the enterprise is more likely to actually support the business instead of constantly showing up as an ongoing cost. Consequently, business capability mapping promotes a strong connection between the [[Business Model|business model]] and the infrastructure supporting the [[Business Requirements|business requirements]]. This also means that when professionals model business capabilities they are helping to bring together business and IT figures. As part of your [[Business Transformation|business transformation]] effort you will undoubtedly need to engage in business capability mapping. So, in esence, modeling business capabilities is about defining your organization’s ability to execute.<ref>Explaining Business Capability Modeling [https://www.orbussoftware.com/us/business-architecture/business-capability-modeling/# ObusSoftware]</ref>
 
In other words, business capability modeling is graphically representing the abilities of the company, as well as its potential. When business architects and analysts engage in business capability modeling, their work results in the creation of a capability model. This forms the core of business capability mapping, which enables adaptive, sleek architectures that can respond quickly to changes in today's competitive business landscape. The first stage of the mapping [[process]] is identifying the highest-level [[Business Capability|capabilities of the business]]. Typically, these are oriented towards the operational side. After they’re all documented you can start decomposing these top-level capabilities into lower-level capabilities. At this point you may choose to create an exhaustive model and keep every single sub-capability. Alternatively, you could discard all but the ones most relevant to the achievement of [[Business Goals|business goals]]. This doesn’t automatically entail negative consequences. Keeping your eyes on the whole business landscape is laudable during this process but capabilities that aren’t critical may safely be omitted during the mapping process. This of course also depends to a large degree on the timeframe of the project and the number of allotted personnel. Once you have an agreed upon capability model, you and your team should start listing attributes for each individual capability and [[service]] level expectation. These may differ from company to company, but usually what you’ll be looking at are things such as performance requirements, capability owner, customers, inputs and outputs, as well as general information on the elements that compose it – people, processes, and technology. All this knowledge captured as part of the [[Business Architecture|business architecture]] will later help you derive the exact requirements for the [[IT Infrastructure|IT infrastructure]]. The goal of this practice is to model the business around its most stable elements. This is because although the way in which a company powers its abilities may change dramatically with time (the How), the actual abilities are usually unfluctuating even on long time scales (the What). For instance, it’s very plausible for a [[manufacturing]] company to have had a capability called Deliver [[Product]] for the past century. The way in which this capability might have been fulfilled throughout the years however will have varied immensely (i.e. horse-drawn carriage, train, truck etc.). The main benefit of having a model based on the most resilient elements of the business is its longevity. Changes to how capabilities are implemented don’t necessarily alter the base model. What’s more, with a stable business model the IT infrastructure of the enterprise is more likely to actually support the business instead of constantly showing up as an ongoing cost. Consequently, business capability mapping promotes a strong connection between the [[Business Model|business model]] and the infrastructure supporting the [[Business Requirements|business requirements]]. This also means that when professionals model business capabilities they are helping to bring together business and IT figures. As part of your [[Business Transformation|business transformation]] effort you will undoubtedly need to engage in business capability mapping. So, in esence, modeling business capabilities is about defining your organization’s ability to execute.<ref>Explaining Business Capability Modeling [https://www.orbussoftware.com/us/business-architecture/business-capability-modeling/# ObusSoftware]</ref>
 +
 +
 +
== See Also ==
 +
<div style="column-count:2;-moz-column-count:3;-webkit-column-count:3">
 +
[[Business]]<br />
 +
[[Business-to-Business (B2B)]]<br />
 +
[[Business Application]]<br />
 +
[[Business-Driven Development (BDD)]]<br />
 +
[[Business-to-Business Gateway]]<br />
 +
[[Business-to-Consumer (B2C)]]<br />
 +
[[Business Accelerator]]<br />
 +
[[Business Activity Monitoring (BAM)]]<br />
 +
[[Business Analysis]]<br />
 +
[[Business Analytics]]<br />
 +
[[Business Application]]<br />
 +
[[Business Application Programming Interface (BAPI)]]<br />
 +
[[Business Architecture]]<br />
 +
[[Business Asset]]<br />
 +
[[Business Capability]]<br />
 +
[[Business Capability Modeling]]<br />
 +
[[Business Ethics]]<br />
 +
[[Business Case]]<br />
 +
[[Business Centric Methodology (BCM)]]<br />
 +
[[Business Continuity Management (BCM)]]<br />
 +
[[Business Continuity Plan (BCP)]]<br />
 +
[[Business Continuity Planning (BCP)]]<br />
 +
[[Business Cycle]]<br />
 +
[[Business Diversification]]<br />
 +
[[Business Driven Technology]]<br />
 +
[[Business Drivers]]<br />
 +
[[Business Ecosystem]]<br />
 +
[[Business Environment and Internal Control Factors (BEICF)]]<br />
 +
[[Business Excellence]]<br />
 +
[[Business Expansion]]<br />
 +
[[Business Function]]<br />
 +
[[Business Function Model]]<br />
 +
[[Business IT Alignment]]<br />
 +
[[Business Impact Analysis (BIA)]]<br />
 +
[[Business Incubator]]<br />
 +
[[Business Insurance]]<br />
 +
[[Business Integration]]<br />
 +
[[Business Intelligence]]<br />
 +
[[Business Interruption Insurance]]<br />
 +
[[Business Life Cycle]]<br />
 +
[[Business Logic]]<br />
 +
[[Business Management System (BMS)]]<br />
 +
[[Business Model Innovation (BMI)]]<br />
 +
[[Business Model for Information Security (BMIS)]]<br />
 +
[[Business Motivation Model (BMM)]]<br />
 +
[[Business Objects]]<br />
 +
[[Business Operations]]<br />
 +
[[Business Oriented Architecture (BOA)]]<br />
 +
[[Business Mission]]<br />
 +
[[Business Vision]]<br />
 +
[[Business Model]]<br />
 +
[[Business Goals]]<br />
 +
[[Business Objective]]<br />
 +
[[Corporate Structure]]<br />
 +
[[Corporate Social Responsibility (CSR)]]<br />
 +
[[Chief Executive Officer (CEO)]]<br />
 +
[[IT Strategy (Information Technology Strategy)]]<br />
 +
[[IT Governance]]<br />
 +
[[Enterprise Architecture]]<br />
 +
[[IT Sourcing (Information Technology Sourcing)]]<br />
 +
[[IT Operations (Information Technology Operations)]]<br />
 +
</div>
 +
 +
 +
===References===
 +
<references />

Revision as of 13:30, 11 June 2021

Business capability modeling is a technique for the representation of an organization’s business anchor model, independent of the organization’s structure, processes, people or domains.[1]

In other words, business capability modeling is graphically representing the abilities of the company, as well as its potential. When business architects and analysts engage in business capability modeling, their work results in the creation of a capability model. This forms the core of business capability mapping, which enables adaptive, sleek architectures that can respond quickly to changes in today's competitive business landscape. The first stage of the mapping process is identifying the highest-level capabilities of the business. Typically, these are oriented towards the operational side. After they’re all documented you can start decomposing these top-level capabilities into lower-level capabilities. At this point you may choose to create an exhaustive model and keep every single sub-capability. Alternatively, you could discard all but the ones most relevant to the achievement of business goals. This doesn’t automatically entail negative consequences. Keeping your eyes on the whole business landscape is laudable during this process but capabilities that aren’t critical may safely be omitted during the mapping process. This of course also depends to a large degree on the timeframe of the project and the number of allotted personnel. Once you have an agreed upon capability model, you and your team should start listing attributes for each individual capability and service level expectation. These may differ from company to company, but usually what you’ll be looking at are things such as performance requirements, capability owner, customers, inputs and outputs, as well as general information on the elements that compose it – people, processes, and technology. All this knowledge captured as part of the business architecture will later help you derive the exact requirements for the IT infrastructure. The goal of this practice is to model the business around its most stable elements. This is because although the way in which a company powers its abilities may change dramatically with time (the How), the actual abilities are usually unfluctuating even on long time scales (the What). For instance, it’s very plausible for a manufacturing company to have had a capability called Deliver Product for the past century. The way in which this capability might have been fulfilled throughout the years however will have varied immensely (i.e. horse-drawn carriage, train, truck etc.). The main benefit of having a model based on the most resilient elements of the business is its longevity. Changes to how capabilities are implemented don’t necessarily alter the base model. What’s more, with a stable business model the IT infrastructure of the enterprise is more likely to actually support the business instead of constantly showing up as an ongoing cost. Consequently, business capability mapping promotes a strong connection between the business model and the infrastructure supporting the business requirements. This also means that when professionals model business capabilities they are helping to bring together business and IT figures. As part of your business transformation effort you will undoubtedly need to engage in business capability mapping. So, in esence, modeling business capabilities is about defining your organization’s ability to execute.[2]


See Also

Business
Business-to-Business (B2B)
Business Application
Business-Driven Development (BDD)
Business-to-Business Gateway
Business-to-Consumer (B2C)
Business Accelerator
Business Activity Monitoring (BAM)
Business Analysis
Business Analytics
Business Application
Business Application Programming Interface (BAPI)
Business Architecture
Business Asset
Business Capability
Business Capability Modeling
Business Ethics
Business Case
Business Centric Methodology (BCM)
Business Continuity Management (BCM)
Business Continuity Plan (BCP)
Business Continuity Planning (BCP)
Business Cycle
Business Diversification
Business Driven Technology
Business Drivers
Business Ecosystem
Business Environment and Internal Control Factors (BEICF)
Business Excellence
Business Expansion
Business Function
Business Function Model
Business IT Alignment
Business Impact Analysis (BIA)
Business Incubator
Business Insurance
Business Integration
Business Intelligence
Business Interruption Insurance
Business Life Cycle
Business Logic
Business Management System (BMS)
Business Model Innovation (BMI)
Business Model for Information Security (BMIS)
Business Motivation Model (BMM)
Business Objects
Business Operations
Business Oriented Architecture (BOA)
Business Mission
Business Vision
Business Model
Business Goals
Business Objective
Corporate Structure
Corporate Social Responsibility (CSR)
Chief Executive Officer (CEO)
IT Strategy (Information Technology Strategy)
IT Governance
Enterprise Architecture
IT Sourcing (Information Technology Sourcing)
IT Operations (Information Technology Operations)


References

  1. Definition: What does Business Capability Modeling Mean? Gartner
  2. Explaining Business Capability Modeling ObusSoftware