Understanding Business Architecture: Models, Capabilities, and Operations

Business architecture is the primary architecture; all other architectures can be derived from it and should trace back to it.

Although any model is an abstraction of reality, business architecture should be the most concrete representation of reality in business terms . It provides the business rules and requirements for building all other architectures. This architectural layer maintains alignment with corporate strategy and keeps the entire enterprise focused ; in this way it offers an excellent feedback mechanism for additional business improvements and opportunities to build competitive advantage.

Business architecture defines the enterprise value chain (or flow) and its relationships with all internal and external business entities. It defines what the enterprise must produce and how to produce it to satisfy customers, compete in the market, deal with suppliers, maintain operations, and care for employees.

This business architecture can be described by three key models; these three models are often used interchangeably to describe business architecture, but in practice they are quite different. They provide different viewpoints of the business, sometimes overlapping:

Business Model describes how the enterprise operates; it focuses more on the external relationships and interactions among the company, partners, and customers.

Business Operating Model describes the set of integrated business processes and the level of data standardization required across the company’s internal components; it emphasizes internal relationships and interactions among departments and how they cooperate to run the business.

Capability Model describes the capabilities needed to implement the business and operating models.

The company’s business model is a simplified representation of its business logic, meaning it describes the fundamental principles of how the organization creates, delivers, and captures value; it defines how the enterprise delivers value to customers, attracts them to pay for that value, and converts those payments into profit.

Even though the term is used broadly to represent core aspects of the business (purpose, product, market, customers, …), the essence of the business model is that it describes the service the company provides to customers, how it interacts with them, through which resources, activities, and partners it achieves this, and ultimately how it makes money.

In the early history of business models, defining model types was typical, but those types usually described only one aspect of the business, often just the revenue model. Recent literature on business models therefore focuses on describing the model as a whole rather than a single element. Inspired by the “Business Model Canvas” framework, business model design should include descriptions of the following key elements:

“Target Customer Segments” defines the different groups of people or organizations the enterprise aims to reach and serve.

“Value Proposition” describes the bundle of products and services that create value for a specific customer segment.

“Channels” describes how the company communicates with and reaches its customer segments to deliver the value proposition.

“Customer Relationships” describes the type of relationship the company establishes with each customer segment.

“Key Resources” describes the most important assets required for the business model to function.

“Key Activities” describes the most important things the company must do for its business model to work.

“Key Partnerships” describes the network of suppliers and partners that enable the business model.

“Revenue Streams” represents the cash the company generates from each customer segment.

“Cost Structure” describes all costs incurred by operating the business model.

All of these elements of the business model should be mixed together in a value stream or value chain, which describes the sequence of steps that allow value creation within the organization; this will be described in the operating model.

The operating model describes how you want the business to run internally; it defines the main operational elements required to implement the business model and how each of them is linked and further designed as sub‑components. In this sense, the operating model is usually informed and derived from the business model; however, in some cases the operating model can become a source of competitive advantage and can inform the business model.

The operating model breaks the company’s organization into logical components and describes how the organization conducts business; it outlines the key areas of organizational structure, operating units, and trade partners, and provides a set of guidelines and technical infrastructure for business architecture, enabling the company to develop its business.

The operating model should answer internal operational questions such as “What is the organizational structure?”, “What processes does the organization use?”, and “What are the roles and responsibilities?”. The main components and relationships of the operating model framework are:

People components, including structure, organization, skills, knowledge culture, governance, rewards, procurement, and location.

Support infrastructure and facility components, including physical assets, facilities and locations, information and data assets, technology infrastructure, and applications (some of which are described in more detail in the IT architecture).

Process components, including overall processes, inputs, outputs, accountability (who does what), where, how, metrics, and the level of consistency.

Capability modeling is a technique that represents the internal aspects of an organization’s business independent of its structure, processes, people, or domains; it describes the full set of capabilities an organization needs to execute its business model or fulfill its mission.

A capability is a specific ability or competence that a company must possess to achieve a particular purpose or result. In this sense, capabilities abstract and encapsulate the organization, its people, and the roles, processes, procedures, and technology related to a given business function into simple blocks.

Capabilities in a capability model differ from processes in an operating model; capabilities answer the “what” the enterprise does to achieve the desired outcome, while processes describe “how” it is done. The benefit is that capability models tend to be more stable over time and more static across business units within the same department, making them better suited as design components on which IT architecture can be anchored.

Key distinguishing features of business capabilities that separate capability models from operating models are:

Each capability is unique and reusable. It is a fundamental element of the organization, distinct from other capabilities. A capability may be applied across the whole organization and can affect different results in different ways, but it remains a single capability.

Capabilities are stable. Well‑defined capabilities change rarely; compared with projects, processes, applications, or even strategy, they provide a more stable view of the organization. They only change when there is a major shift in the underlying business model or mission, such as during a transformation program or a merger/acquisition.

Capabilities are abstracted from the organization model. They are not merely a restatement of the enterprise organization model. They are organization‑neutral, meaning changes in organizational structure do not require changes in the capability model.

Business capabilities do not impose any constraints on how they are realized through IT systems or manual operations.

Capability models are multi‑level, but the number of levels varies by organization. Almost everyone has at least two levels, rarely more than five, with lower levels containing 10‑50 capabilities.

Figure 19 – Business Capability Model

At the higher levels (from level 1 to level 2), the capability model represents the organization’s 5‑10 major generic capabilities, which often overlap with high‑level process models or product groups. Levels below the third tier mainly serve to connect the model to processes and technology.

For more information on this topic, please follow the public account.