Summary: ArchiMate is the open standard modelling language for enterprise architecture, maintained by The Open Group (currently version 3.2, 2022). It provides one consistent notation for describing business, applications and technology in a single connected model rather than a folder of disconnected slides. Where TOGAF describes how you run architecture work, ArchiMate describes what you express it in. This article explains the layers, elements, relationships and viewpoints — and shows, from our experience in real Portamus client projects, how to adopt ArchiMate without drowning in your own model.
Key takeaways
- ArchiMate is a language, not a process and not a tool — the open standard from The Open Group.
- Its core has three layers: Business, Application, Technology, framed by Strategy, Physical, Implementation & Migration and the cross-cutting Motivation aspect.
- Every element belongs to one of three aspects: active structure (who or what acts), behaviour (what happens) and passive structure (what is acted upon).
- Viewpoints are where the value sits: audience-specific views onto one shared model — in line with ISO/IEC/IEEE 42010.
- ArchiMate complements TOGAF; “TOGAF or ArchiMate?” is the wrong question (see TOGAF vs. ArchiMate).
- The most common failure is not too little notation but too much model: scope beats usefulness.
What is ArchiMate?
ArchiMate is a standardised modelling language for enterprise architecture. It defines a fixed vocabulary of elements (business process, application component, node, …) and relationships (serving, realization, assignment, …) together with a graphical notation.
The decisive difference to free-form drawing: in ArchiMate every box and every arrow has a defined meaning. That sounds like formalism, but it has a very practical effect — models become queryable. Questions such as “which business processes depend on this database?” or “which departments does decommissioning this system affect?” can be answered from the model instead of being re-surveyed in every project.
ArchiMate originated in a Dutch research project from 2002 and was adopted as an open standard by The Open Group in 2008. The current release is ArchiMate 3.2 (October 2022).
The layers of ArchiMate
ArchiMate organises architecture into layers. The three core layers carry the weight; the others frame them.
| Layer | Models | Typical elements |
|---|---|---|
| Strategy | How the organisation creates value long-term | Capability, Resource, Course of Action, Value Stream |
| Business | What happens in business terms | Business Actor, Business Role, Business Process, Business Service, Business Object |
| Application | The application landscape | Application Component, Application Service, Application Interface, Data Object |
| Technology | The technical foundation | Node, Device, System Software, Technology Service, Artifact, Communication Network |
| Physical | Production and logistics | Equipment, Facility, Material, Distribution Network |
| Implementation & Migration | The path to the target architecture | Work Package, Deliverable, Plateau, Gap |
| Motivation (aspect) | The why behind the architecture | Stakeholder, Driver, Assessment, Goal, Outcome, Principle, Requirement |
The layers connect through serving and realization relationships: technology serves applications, applications serve business processes. That unbroken chain is what makes impact analysis possible — from a server decommissioning down to the affected customer process.
Elements and aspects: the logic behind the language
Learning ArchiMate as a symbol catalogue is exhausting. The language has a surprisingly simple internal logic: every layer is structured by the same three aspects.
- Active structure — who or what acts: Business Actor, Application Component, Node.
- Behaviour — what happens: Business Process, Application Service, Technology Function.
- Passive structure — what is acted upon: Business Object, Data Object, Artifact.
Almost every element falls out of that matrix. In our training sessions this grid is regularly the moment ArchiMate clicks: instead of memorising 60 symbols you learn three questions — who, what happens, on what?
Relationships: the underrated part
In ArchiMate the relationships carry the actual semantics. The ones that matter most:
| Relationship | Meaning | Typical use |
|---|---|---|
| Composition / Aggregation | Whole–part | A department consists of teams |
| Assignment | Active structure performs behaviour | A role performs a process step |
| Realization | Concrete realises abstract | An application component realises an application service |
| Serving | One element provides functionality to another | An application service serves a business process |
| Access | Behaviour accesses an object | A process reads/writes a business object |
| Triggering / Flow | Temporal sequence / flow of information | One process step triggers the next |
| Influence | Motivation elements affect each other | A principle influences a requirement |
Rule of thumb from practice: if a team gets stuck debating the correct relationship, the model is usually too fine-grained. Serving and realization carry most of the explanatory power in real projects.
Viewpoints: why ArchiMate is more than a notation
An ArchiMate model is not the same as an ArchiMate diagram. The model is the repository of all elements and relationships; a diagram is a view onto it, filtered for what a particular audience needs. The standard ships predefined viewpoints: Layered, Application Cooperation, Technology Usage, Goal Realization, Migration and more.
That principle — an architecture description consists of views addressing stakeholder concerns — comes from ISO/IEC/IEEE 42010, and ArchiMate implements it consistently. In practice: one model, many views. The CFO sees cost and capabilities, the operations team sees nodes and deployments — from the same underlying data. This is exactly where slide-based landscapes fail: ten pictures of one reality, none of them current.
ArchiMate and TOGAF: language meets method
Both standards come from The Open Group and are deliberately aligned:
- TOGAF provides the method — the ADM with phases A through H.
- ArchiMate provides the language — the notation for the outputs of those phases.
ADM phases B, C and D (business, information systems and technology architecture) map almost one-to-one onto ArchiMate’s core layers; phases E/F are expressed through the Implementation & Migration layer with plateaus and gaps; the motivation elements cover the vision and requirements work from phase A and ongoing requirements management. For a detailed comparison see TOGAF vs. ArchiMate.
Adopting ArchiMate: our approach
Across our EA design engagements one pragmatic sequence has proven itself:
- Purpose before notation. Which three decisions should the model improve? Without that answer you produce documentation without an audience.
- Minimal viable metamodel. We start with 12–15 element types and extend only on demonstrated need.
- Agree naming conventions. Models fail more often on inconsistent names than on wrong relationships.
- Define three to five viewpoints — one per audience, each with a named owner.
- Connect data sources. The application inventory comes from application portfolio management, not from manual typing.
- Anchor a maintenance trigger. A model without an update trigger (change, project approval, architecture review) is stale within months.
Common mistakes
- Trying to model everything. Completeness is not the goal; decision-making capability is.
- Buying the tool first. Purpose and metamodel first, tool second. Archi is enough to start with.
- Diagrams instead of a model. Exporting views and then abandoning the elements just yields expensive slides.
- No model governance. Without named owners and a maintenance trigger, every repository is abandoned.
- Playing ArchiMate off against BPMN or UML. They operate at different altitudes and complement each other.
Frequently asked questions about ArchiMate
What is ArchiMate in simple terms? ArchiMate is an open, standardised modelling language for enterprise architecture, maintained by The Open Group. It provides a fixed notation — elements, relationships and views — for describing business processes, applications and technology in one coherent model.
What are the layers of ArchiMate? Three core layers — Business, Application, Technology — framed by the Strategy Layer, the Physical Layer, the Implementation & Migration Layer and the cross-cutting Motivation aspect.
What is the difference between ArchiMate and TOGAF? TOGAF is a method (the ADM cycle); ArchiMate is a modelling language (the notation). Both come from The Open Group and are designed to be used together.
What is the difference between ArchiMate and UML or BPMN? ArchiMate models the enterprise as a whole; BPMN models a single process in executable detail; UML models software design. Use ArchiMate for the overview and link out at the edges.
Which ArchiMate version is current? ArchiMate 3.2, published by The Open Group in October 2022 — a backwards-compatible evolution of ArchiMate 3.1 (2019).
Which tools support ArchiMate? The language is tool-neutral. Common choices are the free Archi plus commercial suites such as BiZZdesign Horizzon, SAP LeanIX, Sparx Enterprise Architect, ADOIT or Software AG Alfabet.
Is an ArchiMate certification worth it? For modelling architects, yes — it secures shared notation and semantics. For organisations, a binding modelling convention is the bigger lever.
Is ArchiMate suitable for mid-sized companies? Yes, provided you use only a fraction of the language — typically 12 to 15 element types and a handful of viewpoints.
Conclusion
ArchiMate is the shared language of enterprise architecture: standardised, tool-neutral, aligned with TOGAF and — through viewpoints — connectable to what real stakeholders actually need. Its value comes not from completeness but from discipline: a deliberately small metamodel, clear conventions, and a maintenance process tied to real decisions. Our consistent experience: adopt ArchiMate lean and maintain it seriously, and within a few months you have an architecture that answers questions instead of an archive nobody opens.
Looking to adopt ArchiMate — or to make an existing model useful again? We support you from metamodel and conventions through to viewpoints your stakeholders actually read. → Explore Portamus enterprise architecture design
Sources
- The Open Group: ArchiMate 3.2 Specification (2022)
- The Open Group: TOGAF Standard, 10th Edition (2022)
- ISO/IEC/IEEE 42010:2022 — Software, systems and enterprise — Architecture description