Direct Answer: A business capability map is a stable, technology-agnostic inventory of what your organisation can do — not how it does it or what systems support it. In ArchiMate 3.x, the Capability element sits in the Strategy layer, not the Business layer. It is distinct from Business Function, which describes operational activity. In Sparx EA, you build a capability map by creating a hierarchy of Capability elements in a Strategy layer diagram, decomposing from Level 1 (enterprise-wide domains) to Level 2 and Level 3 (operational and enabling capabilities). Heatmapping is applied via tagged values and conditional formatting. Application realisation is modelled using the Realization connector between Application Component (Technology layer) and Capability (Strategy layer). This distinction matters: capability maps are strategic instruments. They should remain stable across technology changes. If your “capability map” changes every time a system is replaced, it is probably modelling functions, not capabilities.
Key Takeaways
- ArchiMate distinguishes Capability (Strategy layer, what the org can do) from Business Function (Business layer, how an activity is performed). Use Capability elements for strategic mapping.
- Level 1/2/3 decomposition provides the structural backbone; do not go below Level 3 in most enterprise-wide models.
- Heatmapping requires tagged values on Capability elements — maturity score, investment category, strategic importance — populated with governance discipline.
- Application realisation connects the technology layer (what systems support a capability) to the strategic layer, enabling portfolio rationalisation analysis.
- MDG governance of your Capability stereotype is the difference between a map you can query with AI and a diagram that ages badly.
Capability vs Business Function: The Distinction That Matters
This is the most common mistake in ArchiMate capability modelling, and it is worth addressing directly before getting to the mechanics.
Capability (ArchiMate Strategy layer) represents an ability that the organisation either has or does not have, at a level of abstraction that is independent of how the ability is delivered. “Customer Onboarding,” “Risk Assessment,” “Product Development,” “Regulatory Reporting” are capabilities. They do not change when the underlying process changes, when a system is replaced, or when a team is reorganised.
Business Function (ArchiMate Business layer) represents an operational activity performed by an organisational unit. “Process Loan Application,” “Generate Compliance Report,” “Manage Customer Data” are business functions. They describe operational reality — which is valuable, but different.
When you build a capability map with Business Function elements, you end up with a map that reflects your current operating model rather than your stable strategic inventory. Reorganisations invalidate it. System replacements change it. It becomes an operational model dressed up as a strategic one.
In Sparx EA, both element types are available in their respective ArchiMate packages. The Capability element is under ArchiMate 3 > Strategy > Capability. Do not substitute Business Function. The semantic difference is not cosmetic — it affects how EA GraphLink traverses the model and how AI tools interpret the relationship between capabilities and the rest of the architecture.
Structuring the Hierarchy: Level 1 to Level 3
A typical enterprise capability map has three levels of decomposition.
Level 1: Capability Domains. These are the broadest groupings — typically six to twelve for a mid-to-large enterprise. They represent the major areas of business activity at the highest level of abstraction: Customer Engagement, Operations, Finance, Risk and Compliance, Technology, and so on. Level 1 should be stable across five to ten years.
Level 2: Core Capabilities. Each domain decomposes into five to twelve core capabilities. These are the named abilities that strategy conversations reference directly: within Customer Engagement, Level 2 capabilities might include Customer Acquisition, Customer Onboarding, Customer Service, and Loyalty Management.
Level 3: Enabling Capabilities. Level 2 capabilities decompose further where analytical value warrants it. Not all capabilities need Level 3 — apply it where strategic differentiation or investment decisions operate at that granularity.
In Sparx EA, model the hierarchy using the Composition connector between Capability elements, or use package-level grouping. A dedicated Strategy layer diagram with nested Capability elements is the standard approach. Keep each level on its own diagram for readability; link diagrams via element cross-references.
A practical limit: Do not go beyond Level 3 at enterprise scope. At Level 4 and below, you are modelling processes or functions, not capabilities. The map becomes unwieldy and loses its strategic character. Deeper decomposition belongs in domain-specific or programme-level models.
Heatmapping: Capability Assessment in Sparx EA
A capability map without assessment data is a taxonomy. Assessment data — the heatmap — is what makes it a strategic planning instrument.
Common heatmap dimensions include:
- Capability maturity (1–5 scale, or Low/Medium/High)
- Strategic importance (Core Differentiator / Enabling / Commodity)
- Investment category (Invest / Maintain / Divest / Transform)
- Business pain level (stakeholder-assessed gap between current and required capability)
In Sparx EA, implement these as tagged values on the Capability stereotype in your MDG profile. Populate them through stakeholder assessment workshops — structured conversations where business domain owners rate their capabilities against each dimension.
Visual heatmapping in Sparx EA uses conditional formatting on diagram elements. Shape scripts or diagram filters can colour Capability elements based on tagged value contents. A Capability with MaturityLevel = 1 and StrategicImportance = Core Differentiator renders in red. A Capability with MaturityLevel = 4 and InvestmentCategory = Commodity renders in amber.
The heatmap is where the capability map starts generating strategic conversations. Investment committees, programme boards, and transformation leads engage with a heatmapped capability map in a way they simply do not engage with a plain hierarchy.
Connecting Capabilities to Applications
The capability-to-application relationship is the link between strategic intent and technology portfolio. In ArchiMate, the connector is Realization: an Application Component (or Application Service) realizes a Capability, meaning the technology enables the organisational ability.
In Sparx EA, this means drawing Realization connectors from Application Component elements (in your technology or application layer package) to Capability elements. A single Capability may be realised by multiple applications — a common finding that reveals application redundancy. A single Application may realise multiple capabilities — relevant for impact analysis when the application is under consideration for retirement.
This realisation layer is what powers portfolio rationalisation analysis. The questions it enables include:
- Which capabilities are supported by more applications than necessary?
- Which capabilities have no dedicated application support?
- If we retire Application X, which capabilities are impacted?
These are not just modelling questions. They are investment questions. And when the capability-to-application realisation layer is in the repository, EA GraphLink can surface these answers through AI query without requiring an architect to manually compile a spreadsheet.
Connecting Capabilities to Strategic Goals
The other critical connection is upward: from Capability to strategic goal or driver. ArchiMate models this using the Association or Influence connector from Capability to Goal (Strategy layer) or Outcome (Strategy layer).
When capabilities are connected to strategic goals, the model answers a question executives care about: “Is our technology investment aligned with our strategic priorities?” A capability that is rated low maturity AND connects directly to a top-three strategic goal is a prioritised investment case. A capability rated low maturity but with no strategic goal connection is a candidate for accept-and-tolerate.
This connection layer is also what enables AI-assisted strategic portfolio analysis. A Kernaro AI Hub query — “Which of our low-maturity capabilities are directly linked to this year’s strategic priorities?” — can only be answered if the capability-to-goal relationships are modelled and the tagged values are populated.
Sparx EA Implementation Notes
Element creation: Right-click in a Strategy layer diagram, select New Element, choose Capability from the ArchiMate 3 palette. Alternatively, drag from the toolbox panel.
MDG support: The ArchiMate 3 MDG Technology that ships with Sparx EA includes the Capability element. No custom MDG definition is needed for the element itself, but you will want to extend the Capability stereotype with your assessment tagged values (MaturityLevel, StrategicImportance, etc.) through a custom profile that extends the ArchiMate MDG.
Naming convention: Use noun phrases, not verb phrases. “Customer Onboarding” not “Onboard Customers.” Capabilities are things the organisation has, not things it does.
Package structure: Keep your capability model in a dedicated package, separate from process models and technology models. Capability maps need to be governed as strategic assets — ownership, review cadence, update process.
FAQ
What is the difference between a capability and a business function in ArchiMate? A Capability (Strategy layer) represents a stable, technology-agnostic ability the organisation has — what it can do. A Business Function (Business layer) represents an operational activity performed by an organisational unit — how work is done. Capabilities are stable across reorganisations and system changes. Business Functions change when operating models change. For strategic capability mapping, use Capability elements, not Business Functions.
How many capability levels should a capability map have? Typically three: Level 1 (domains, six to twelve), Level 2 (core capabilities, five to twelve per domain), and Level 3 (enabling capabilities, where strategic granularity warrants it). Going beyond Level 3 at enterprise scope tends to produce process models rather than capability models. Deeper decomposition is better handled in domain-specific or programme-level models.
How do I do heatmapping in Sparx EA? Implement assessment dimensions as tagged values on your Capability stereotype (MaturityLevel, StrategicImportance, InvestmentCategory, etc.). Populate them through stakeholder assessment workshops. Apply visual heatmapping using Sparx EA’s conditional formatting or shape scripts to colour Capability elements based on tagged value contents. The MDG profile for your Capability stereotype should define these tagged values with controlled vocabularies.
What connector type do I use to link capabilities to applications? Use the ArchiMate Realization connector, from Application Component (or Application Service) to Capability. This represents the technology enabling the organisational ability. In Sparx EA, this connector is available in the ArchiMate 3 connector palette. The direction matters: the application realises the capability, not the other way around.
Do I need a custom MDG profile for capability mapping? The ArchiMate 3 MDG that ships with Sparx EA includes the Capability element — no custom definition is needed for the element itself. However, you will want to extend the Capability stereotype with your assessment tagged values (maturity score, investment category, etc.) through a custom MDG profile that extends the built-in ArchiMate 3 profile. This is a standard MDG extension task, not a full custom MDG build.
How do capabilities connect to strategic goals in ArchiMate? Use Association or Influence connectors from Capability to Goal or Outcome elements (Strategy layer). This connection links your capability map to your strategic intent, enabling analysis of which capabilities are critical to strategic priorities and which are not. It is this connection layer that enables AI-assisted strategic portfolio analysis through EA GraphLink.
Build a Capability Map That Earns Its Place in Strategy Conversations
Sparx Services’ Amplify offering builds capability modelling into your EA practice — not just the ArchiMate structure, but the assessment methodology, the MDG governance, and the connection to your application portfolio and strategic goals.
A well-built capability map is one of the most durable and valuable artefacts an EA practice can produce. We help you build one that lasts.
