Why Value Streams, Capabilities, and Processes Are Not a Hierarchy: The Mapping Relationship Explained

Business Architecture Is Multi‑Perspective, Not a Single Model

BIZBOK, TOGAF, and OMG BACM all treat business architecture as a structured expression from multiple viewpoints. Value streams describe how an enterprise creates and delivers value to stakeholders; business capabilities describe the abilities required to realize that value; business processes describe how the business actually runs. These are complementary lenses, not layers of a single hierarchy.

OMG BACM Defines Mapping, Not Parent‑Child Relationships

Value Stream ↔ Business Capability

BACM states: Capability supports ValueStreamStage . A value‑stream stage requires certain capabilities (e.g., “Order‑to‑Delivery” needs order management, planning, inventory, logistics). This is a support mapping, not a decomposition of the stage into capabilities.

Value Stream ↔ Business Process

BACM states: Process / Activity implements ValueStream / ValueStreamStage . Processes and activities realize the value flow; one value‑stream stage can map to multiple processes.

Business Capability ↔ Business Process

BACM explicitly says: “Process and capability models of a business are complementary perspectives on the business.” They are not hierarchical; a capability is not a specific process level, nor is a process a further breakdown of a capability.

The relationship among the three is first and foremost a mapping relationship , not a parent‑child relationship .

Why Enterprises Still Draw Them as a Line: Huawei’s Engineering View

Huawei defines business architecture as comprising value streams, business capabilities, and process architecture, where process architecture “carries” (承载) value streams and capabilities —not “decomposes” them. Huawei maintains separate layering for each:

Value Stream → Value Stream Stage

Business Capability Category → Capability Group → Capability → Business Service

Process Category → Process Group → Process → Activity → Task

These three independent hierarchies are then related within a unified architecture platform. This aligns with BACM’s mapping concept.

The Illusion of Unified Levels

When all three models share the same L1/L2/L3 labels in a single repository or report, a visual illusion arises: L2 value‑stream stage appears to be the parent of L2 process group, L3 capability equals L3 process. In reality, identical level numbers only indicate depth within each model, not cross‑model hierarchy. They can be mapped, but not equated.

Three Models in Theory, One Architecture in Practice

The goal is not to merge them into one tree but to establish stable cross‑model relationships: value streams pull value creation, capabilities provide support, processes execute operations . The common “value stream → capability → six‑level process” chain is better understood as an architecture integration pattern , not a decomposition chain.

Answering the Frequent Question

“Which process level (L3, L4, L5) does a business capability correspond to?”

There is no fixed answer because capabilities and processes belong to different models. The right question is: Which value‑stream stages does a capability support? In which processes is it invoked and executed? That is the mapping business architecture must capture.

Final synthesis: Three models in theory, one architecture in practice; independent in modeling, connected in business.

References

[1] Object Management Group, Business Architecture Core Metamodel (BACM) Version 1.0 , 2024.

[2] Business Architecture Guild, Similar Yet Different: Value Streams and Business Processes — The Business Architecture Perspective .

[3] Huawei EAMap Docs.