This chapter defines the Business dimension of the base model. The base model defines a set of generic maturity indicators and attributes that can be used to assess an organization’s SOA maturity level against the OSIMM maturity matrix. Additional maturity indicators, assessment questions, and attribute mappings can be added by vendors or user organizations to extend the base OSIMM model.
The assessment questions that follow help elicit how an organization formally defines and documents their business drivers and processes, which ranges from isolated business line-driven to making business capabilities available via context-aware services.

OSIMM Business Dimension
The base OSIMM model provides one of many possible maturity indicators per dimension. Organizations, vendors, and consultants can provide additional maturity indicators, assessment questions, and attribute mappings to provide additional guidance necessary for the maturation of an organization’s SOA.
The following Business dimension maturity indicator is provided as part of the base OSIMM specification:
The following assessment questions help elicit information on how an organization formally defines and documents their business drivers and processes. By gathering information using these assessment questions, an assessor can map a maturity indicator to the associated maturity attributes, thereby determining the Business dimension maturity level.
The following are the base set of maturity indicators for the OSIMM Business dimension. Each maturity indicator is associated with a set of maturity attributes. Maturity attributes are those observed characteristics of a maturity indicator for each maturity level. The assessment questions are used to survey an organization’s Business dimension. Survey data obtained through the Business dimension assessment questions is used to determine the maturity level by assessing the data and matching to the maturity attributes that best fit the information obtained. The maturity weighting is used to determine an average maturity score across multiple maturity indicators. The model can be extended by adding additional maturity indicators and assigning weighting to the indicator by maturity level according to the value placed on the maturity indicator by the assessing organization.
Maturity Indicators for the Business Dimension
Maturity Level |
Maturity Indicator |
Maturity Attributes |
Maturity Weighting |
Assessment Question Mapping |
Silo Isolated Business Line-driven |
Formal definition and documentation of the organization’s business drivers and processes. |
Low or nonexistent Enterprise architecture is not an element of the IT or Enterprise strategy. Business processes are not formally defined and documented. Limited to how specific applications must behave; IT-specific. |
10 |
2, 15 3 1, 9, 17, 18 |
Integrated Business Process Integration |
Formal definition and documentation of the organization’s business drivers and processes. |
Limited No formal enterprise architecture. Limited to LOB objectives and need for information from other organizations. |
20 |
15 1, 2, 3, 4, 6, 9, 17, 18, 19 |
Componentized Componentized Business |
Formal definition and documentation of the organization’s business drivers and processes. |
Cross-organizational Some formal enterprise architecture constructs exist. Organization’s business drivers are documented as cross-organizational business objectives. |
30 |
15, 16 1, 2, 9, 17, 18, 19 |
Services Componentized Business Provides and Consumes Services |
Formal definition and documentation of the organization’s business drivers and processes. |
Enterprise-wide Formal use of enterprise architecture. Organization’s business drivers are documented as elements of the enterprise mission and business architecture. |
40 |
3, 15, 16 1, 2, 3, 8, 9, 10, 11, 17, 18, 19 |
Composite Services Processes Provided and Consumed via Composite Business Services |
Formal definition and documentation of the organization’s business drivers and processes. |
Integrated Enterprise-wide Formal use of enterprise architecture and Business Process Management (BPM). Organization’s business drivers are documented as elements of the enterprise mission and business architecture. |
50 |
3, 4, 5, 6, 10, 11, 15, 16 1, 2, 3, 8, 9, 10, 11, 17, 18, 19 |
Virtualized Services Outsourced Services, BPM, and BAM |
Formal definition and documentation of the organization’s business drivers and processes. |
Integrated across the enterprise and externally between business partners. Well-defined enterprise architecture that details both internal process flows as well as outsourced processes with and between business partner services. Strong use of Business Activity Monitoring (BAM). |
60 |
4, 5 ,6, 7, 9, 11, 12, 13, 14, 15, 19 |
Dynamically Re-Configurable Services Mix-and-match Business Capabilities via Context-aware Services |
Formal definition and documentation of the organization’s business drivers and processes. |
Enterprise services on demand. Well-defined enterprise architecture that includes a formal end-to-end definition of business process flow. Business Process Management (BPM) is used to define and test process flows necessary to meet well-defined SLAs. |
70 |
5, 6, 13, 15, 16 6, 13, 14 |