Skip to main content

Business Architecture With ArchiMate

Business Architecture With ArchiMate

Sep 28, 2025 - Marc Lankhorst - Enterprise Architecture
business architecture with archimate

Business architecture is becoming a critical discipline for organizations that need to adapt quickly to market volatility, regulatory pressure, and digital disruption. By using ArchiMate for business architecture, enterprises can bridge the gap between high-level strategy and operational execution. This modeling language provides a common framework to connect business models, capabilities, value streams, and outcomes with the supporting IT landscape. In this article, we explore how to apply business architecture with ArchiMate, supported by practical examples such as stakeholder analysis, ecosystem mapping, capability maps, and business outcome journey maps.

Why Business Architecture Matters in a Changing Environment

Today, organizations need to move at speed and adapt their business to a volatile environment, while at the same time dealing with many inside and outside stakeholders and influences, ranging from customers and partners in the ecosystem to regulators, competitors, and the uncertain effects of politics (viz. Brexit or the US-China trade war). 

Summary

Business architecture with ArchiMate provides a structured way to connect strategy, capabilities, and operations. By using models such as capability maps, business model canvases, stakeholder views, and value streams, organizations can align business goals with execution and maintain agility in a volatile environment. ArchiMate not only ensures consistency and traceability across the enterprise but also enables clear communication with both business and IT stakeholders. Leveraging these models helps enterprises innovate, manage change, and deliver sustainable value.

FAQs

Business architecture defines how an organization creates and delivers value by connecting strategy to execution. It focuses on capabilities, value streams, processes, and stakeholders.

ArchiMate provides a standardized modeling language that helps architects design, analyze, and communicate business architecture models, ensuring consistency and alignment with IT and operations.

Examples include capability maps, business model canvases, stakeholder analysis, ecosystem maps, and business outcome journey maps—all traceable to enterprise goals.

Business stakeholders are often not familiar with technical diagrams. ArchiMate allows for stakeholder-oriented views, ensuring that business and IT teams share the same understanding.

 

Step by Step How to Develop Enterprise Architecture Services

Step by Step How to Develop Enterprise Architecture Services

Sep 26, 2025 - Marc Lankhorst - Enterprise Architecture
Step by step how to develop enterprise architecture services

Enterprise Architecture Services turn architecture practices into repeatable, value-driven offerings that support business strategy, investment planning, and technology adoption. Instead of seeing EA as abstract diagrams, services package people, processes, and tools into clear deliverables with measurable outcomes. In this article, we walk you step by step through how to define, measure, and manage enterprise architecture services, and show how tools like Bizzdesign Horizzon can accelerate the journey.

Summary

Bizzdesign Horizzon allows you to efficiently define and refine your practice as a service-oriented organization. You can bypass traditional methods like spreadsheets and documents, offering a more integrated and dynamic way to manage services. Within our enterprise architecture tool, you can design your services and develop metrics to evaluate their effectiveness. 

This enables strategic decisions about where to invest and how to secure additional funding to enhance these services and their foundational capabilities. By using our enterprise architecture tool, you don’t have to be an expert in creating services, your only concern will be whether there is a demand for the services and for it to create value. Bizzdesign Horizzon can manage enterprise architecture capabilities based on people, processes, and technology. To find out more about how you can create Enterprise Architecture Services in Bizzdesign Horizzon, book a demo.

 

An Approach How to Assess Business Capabilities

An Approach How to Assess Business Capabilities

Sep 25, 2025 - Marc Lankhorst - Enterprise Architecture
Step by step how to develop enterprise architecture services

Business capabilities are at the core of successful enterprise transformation. Capability-Based Planning (CBP) provides a structured way to align strategy with execution by mapping, assessing, planning, and controlling capabilities across the organization.

In this article, we focus on the Assess phase, where organizations evaluate their business capabilities to understand their strategic importance, maturity, and adaptability. 

This step is crucial to identify which capabilities require investment, where improvements are needed, and how adaptable the enterprise is to change. By applying heatmapping techniques and structured assessments, leaders can make smarter investment decisions and strengthen alignment with long-term goals.

The Capability-Based Planning Cycle

Capability-Based Planning activities are structured in a cycle: Map, assess, plan, and control. It shows us where to begin and the next steps to gradually increase the impact on the organization. 

Summary

Capability-based planning ensures that enterprises focus on the right investments, improve weak areas, and remain adaptable in a changing environment. By assessing capabilities across strategic importance, maturity, and adaptability, organizations gain clear insights into where to prioritize resources.

With the right tools, such as Bizzdesign Horizzon, you can visualize these assessments, identify gaps, and continuously align business capabilities with strategy. Ultimately, this approach empowers decision-makers to drive transformation more effectively and ensure long-term success.

FAQs

Capability-Based Planning (CBP) is a structured approach to align enterprise strategy with execution by mapping, assessing, and managing business capabilities.

Assessing business capabilities helps organizations identify critical areas for investment, measure maturity, and ensure alignment with strategic objectives.

Capabilities are assessed across strategic importance, maturity (people, processes, technology, information), and adaptability to ensure resilience and performance.

Adaptability shows how easily a capability can respond to external pressures, customer needs, and changing demand. It is vital for long-term enterprise resilience.

Tools like Bizzdesign Horizzon help organizations visualize, measure, and monitor capabilities, enabling smarter investment decisions and continuous alignment.

 

The Value of Reference Architectures

The Value of Reference Architectures

Sep 27, 2025 - Marc Lankhorst - Enterprise Architecture
the value of reference architectures

Reference architectures provide organizations with standardized blueprints to structure business, data, application, and technology practices. They offer a shared vocabulary, reusable patterns, and proven industry standards that reduce complexity and accelerate transformation. Instead of reinventing the wheel, enterprises can rely on these models to improve efficiency, ensure interoperability, and comply with regulations. In this article, we explore what reference architectures are, why they matter, and how they can support enterprise architecture and strategic planning.

What are reference architectures?

Reference architectures are standardized architectures that provide a frame of reference for a particular domain, sector or field of interest. Reference models or architectures provide a common vocabulary, reusable designs and industry best practices.

They are not solution architectures, i.e. they are not implemented directly. Rather, they are used as a constraint for more concrete architectures. 

Summary

Reference architectures deliver significant value by offering a common foundation of principles, standards, and best practices. They reduce inefficiencies, simplify system integration, and improve collaboration across industries. From compliance and benchmarking to mergers and innovation, these frameworks enable organizations to focus their creativity on areas of true competitive advantage. By adopting and governing reference architectures effectively, enterprises can accelerate digital transformation and strengthen their enterprise architecture practice.

FAQs

A reference architecture provides a standardized blueprint that helps organizations design and align their systems, processes, and data. Its main purpose is to ensure consistency, improve efficiency, and enable interoperability across business and IT landscapes.

A reference architecture is not implemented directly—it defines principles, standards, and reusable patterns. A solution architecture, on the other hand, applies these guidelines to address a specific organizational need or project.

Reference architectures are used across many domains, including banking (BIAN), insurance (ACORD), telecommunications (eTOM), government (NORA, FEAF), defense (NAF, DODAF, MoDAF), and manufacturing (ISA-95, SCOR).

Adopting reference architectures saves time, reduces design inefficiencies, improves compliance, and supports integration with partners and vendors. They also help organizations benchmark performance and streamline transformation projects.

No—reference architectures provide a foundation for non-differentiating processes. This allows enterprises to focus innovation on areas that drive competitive advantage, such as customer experience, product offerings, or new business models.

 

An Overview of the Levels of Abstraction in Enterprise Architecture

An Overview of the Levels of Abstraction in Enterprise Architecture

Sep 25, 2025 - Marc Lankhorst - Enterprise Architecture
An overview of the levels of abstraction in enterprise architecture

Levels of abstraction in enterprise architecture play a crucial role in how organizations design, analyze, and communicate transformation. With rapid change and agile adoption, documenting every detail is impractical—but a structured approach to abstraction ensures clarity and relevance. The ArchiMate® standard supports modeling across strategy, business, application, information, and technology layers, each at varying degrees of detail. In this article, we provide an overview of the different levels of abstraction in EA, showing how they help organizations balance high-level design with detailed documentation.

The Role of Abstraction in Enterprise Architecture

Organizations today are facing a rapidly increasing pace of change. They adopt agile methods that impact the entire enterprise to drive faster transformation.

Summary

Using ArchiMate across different levels of abstraction in enterprise architecture helps organizations find the right balance between strategic overviews and detailed documentation. By distinguishing between design-level and deployment-level elements, enterprises can standardize communication, improve efficiency in transformation projects, and manage complexity more effectively. The key is to choose the right abstraction level for your purpose—whether that’s strategy alignment, solution design, or IT portfolio management. With the right approach and tool support, such as Bizzdesign Horizzon, enterprises can connect every layer of abstraction into a unified and actionable architecture.

FAQs

They are layers of detail (from strategy to deployment) that help describe an enterprise at different granularities, making EA models easier to analyze and maintain.

They prevent information overload, ensure communication is tailored to stakeholders, and allow architects to focus on relevant details at each stage.

ArchiMate allows modeling of solution-agnostic, solution-specific, and deployment-specific views across business, application, and technology layers.

Yes, but not all should be. The scope depends on the enterprise’s purpose: high-level designs for transformation vs. deployment-level details for portfolio management.

 

Relating Capabilities to Strategy and Business Model

Relating Capabilities to Strategy and Business Model

Sep 25, 2025 - Marc Lankhorst - Enterprise Architecture
relating capabilities to strategy and business model

In our ongoing blog series on Capabilities and Capability-based Planning, we’ve mainly concentrated on the capability concept itself. We’ve discussed why capabilities are useful as a concept, how to define them, and how to structure Capability Maps. We’ve also looked at how you can use Capability Maps to support business challenges such as investment decision-making, to name a few. 

In this blog, we want to cast a wider net and look at the relationships between capabilities, and share best practices for your business and strategic planning.

Relating Business Strategy and Capabilities

The relationship between business strategy and capabilities is a two-way street. On the one hand, the strategy of an enterprise is a way of configuring its capabilities and resources to achieve certain goals. This may entail improving some capabilities, developing or acquiring completely new ones, or even divesting some non-core, non-strategic capabilities. 

Summary

Relating capabilities to strategy and business models enables organizations to move from abstract planning to actionable insights. By aligning capabilities with resources, value streams, and investment priorities, enterprises can ensure that strategy translates into measurable outcomes. This integrated perspective allows business architects to better guide transformation initiatives, support decision-making, and create long-term business value.

FAQs

Business strategy configures capabilities and resources to achieve goals, while existing capabilities can open opportunities for new ventures.

The Business Model Canvas highlights key capabilities needed for value creation, making strategy and investment planning more concrete.

Capabilities represent potential, while value streams represent value creation in motion. Cross-mapping them shows how capabilities support each stage of value delivery.

 

Using ArchiMate® to Visualize the TOGAF® Enterprise Continuum

Using ArchiMate® to Visualize the TOGAF® Enterprise Continuum

Sep 24, 2025 - Bernd Ihnen - Enterprise Architecture
using archimate to visualize the togaf enterprise continuum

The TOGAF® Enterprise Continuum is a cornerstone of enterprise architecture, providing a structured way to classify and organize architectural descriptions across different levels of abstraction. When combined with the ArchiMate® modeling language, organizations gain a clear and standardized notation to visualize Architecture Building Blocks (ABBs), Solution Building Blocks (SBBs), and deployed solutions. 

Understanding the TOGAF Enterprise Continuum

Previously, I have written about the use of a modeling language and the practical usage of the TOGAF Enterprise Continuum to classify architectural descriptions along different levels of abstraction.

Summary

Visualizing the TOGAF Enterprise Continuum with ArchiMate helps enterprise architects bridge the gap between conceptual architecture and real-world solutions. By applying ArchiMate’s flexible notation to ABBs, SBBs, and deployed solutions, organizations can ensure traceability, consistency, and clarity across different levels of abstraction. Whether developing new architectures, adding application services, or creating separate models, the key is to choose the approach that best fits the scope of your project while avoiding unnecessary modeling complexity. This synergy between TOGAF and ArchiMate provides a strong foundation for strategic planning and architecture governance.

FAQs

It is a classification system that organizes architectural artifacts across different abstraction levels, including Architecture Building Blocks (ABBs), Solution Building Blocks (SBBs), and deployed solutions.

ArchiMate provides a standardized modeling language that allows ABBs, SBBs, and their relationships to be visualized consistently, making enterprise architectures easier to understand and communicate.

The choice depends on context: the first approach works well for new architectures, the second adds an additional layer with artifacts, and the third allows separate logical and physical models.

 

Business Architecture Redefined: Mapping BIZBOK® to ArchiMate®

Business Architecture Redefined: Mapping BIZBOK® to ArchiMate®

Sep 24, 2025 - Marc Lankhorst - Bernd Ihnen - Enterprise Architecture
map BIZBOK® to the ArchiMate® modeling language

The Business Architecture Body of Knowledge (BIZBOK®) has become a widely used reference for business architects worldwide. ArchiMate®, in parallel, provides an open standard to represent enterprise architecture with a clear, consistent notation.

Mapping BIZBOK to ArchiMate bridges these two approaches, enabling architects to connect business architecture concepts to the broader scope of enterprise architecture. This mapping helps teams align definitions, avoid concept drift, and keep business architecture directly connected to planning, change, and investment decisions.

In this article, we explain how BIZBOK® can be expressed in ArchiMate®, highlight key mapping examples, and show why this integration strengthens both strategic and operational modeling.

What is BIZBOK®?

Since the foundation of the Business Architecture Guild and publishing version 1 of Business Architecture Body of Knowledge (BIZBOK®) in 2011, the best practices have become a popular set of guidelines and techniques for practicing business architects.

FAQs

BIZBOK® provides a core set of concepts, guidelines, and techniques for expressing business architecture as defined by the Business Architecture Guild. Its metamodel outlines key elements such as capabilities, value streams, stakeholders, value propositions, and organizational structures, offering a structured way for business architects to describe how the business creates and delivers value. 

ArchiMate® supports BIZBOK® concepts by offering a standardized modeling language and notation that can express those same business architecture elements within a broader enterprise architecture context. It includes motivation, strategy, business, implementation, and migration elements that correspond to many of the BIZBOK® metamodel concepts. It also allows for hierarchical modeling, making it possible to represent different levels of detail—such as capabilities, value streams, and organizational units—in a consistent way. 

Mapping BIZBOK® to ArchiMate® makes business architecture easier to connect to the rest of enterprise architecture. It ensures that abstract concepts like capabilities and value streams can be linked to more concrete elements such as processes, applications, and roles. This helps architects avoid business architecture becoming a stand-alone discipline, improves understanding for non-architects, and provides a clearer line of sight from strategic intent to operational models and implementation. 

 

Use Our Business Process Maturity Model to Measure Progress

Use Our Business Process Maturity Model to Measure Progress

Sep 27, 2025 - Bizzdesign - Enterprise Architecture
use our business process maturity model to measure progress

Business process maturity model provides a structured framework to measure the current state, identify strengths and weaknesses, and define a roadmap for improvement.

With more than 23 years of experience in enterprise architecture and BPM, Bizzdesign has developed an easy-to-use business process maturity model. This model helps organizations assess their BPM practices, prioritize improvement initiatives, and build a scalable foundation for continuous process optimization. 

What is a Business Process Maturity Model?

Business Process Management focuses on how the enterprise operates and delivers the results, i.e., products and services to external and internal customers. 

A business process maturity model is a structured framework to assess your organization’s level of maturity in managing and optimizing business processes. 

Summary

Whether you are just starting with BPM or looking to optimize advanced processes, using this model ensures your improvement efforts are targeted, structured, and aligned with business goals. With the right insights and tools, you can transform BPM from isolated initiatives into a driver of sustainable enterprise-wide performance.

 

Expressing the BIAN Reference Model for the Banking Industry in the ArchiMate Modeling Language

Expressing the BIAN Reference Model for the Banking Industry in the ArchiMate Modeling Language

Sep 25, 2025 - Marc Lankhorst - Enterprise Architecture
expressing the bian reference model

Reference models play a crucial role in enterprise architecture, providing standardized blueprints that align technology and business strategy. For the financial sector, the Banking Industry Architecture Network (BIAN) offers a comprehensive framework of business capabilities, service domains, and business objects. Expressed in the ArchiMate® modeling language, this reference model helps financial institutions improve interoperability, streamline processes, and strengthen governance. In this article, we explore how the BIAN model is represented in ArchiMate and present a case study that illustrates its practical application.

Break-down of the BIAN reference model

It stands to reason that such a standard reference model should be expressed in a standard notation, to foster its adoption, and BIAN recognized this need. BIAN version 13.0 has therefore been expressed in the ArchiMate 3 modeling language. The core of the BIAN reference model is its Service Landscape. 

Summary

The BIAN® reference model expressed in the ArchiMate® modeling language demonstrates how industry standards can accelerate digital transformation in financial services. By combining BIAN’s structured service domains with ArchiMate’s modeling capabilities, financial institutions gain a common language to improve interoperability, streamline processes, and strengthen governance. This alignment not only supports compliance and efficiency but also provides a solid foundation for innovation in the evolving financial landscape.