Glossary
ArchiMate
ArchiMate is an open and independent modeling language for enterprise architecture, published as a standard by The Open Group. It provides element types, relationships and a graphical notation to describe an organization, its applications and its infrastructure in a single model.
Updated
What is ArchiMate?
ArchiMate is a modeling language for IT architecture and, more broadly, enterprise architecture. The Open Group, which publishes it, defines it as an open and independent modeling language supported by different tool vendors and consulting firms. The specification is developed by The Open Group ArchiMate Forum.
The current version is ArchiMate 4, published on April 27, 2026. It follows ArchiMate 3.2, published on October 19, 2022, which the published exchange format still targets.
A modeling language is not a drawing tool. ArchiMate fixes a vocabulary (a process, an application component, a node), the relationships allowed between those elements, and a symbol for each. Two architects who have never met then read the same diagram the same way. In a tool that implements the language, an element exists once in the model and appears in as many views as needed. Rename an application and it is renamed everywhere.
The language targets the architecture level: which applications serve which activity, on which infrastructure. It does not try to describe the inside of a piece of software or the detail of a process.
How is the language structured: layers and aspects?
Up to version 3.2, ArchiMate is presented as a grid that crosses layers with aspects.
The core has three layers: Business, Application and Technology. Around it, the language adds motivation elements (stakeholder, goal, requirement, principle), strategy elements (capability, resource, value stream), physical elements (equipment, facility) and implementation and migration elements (work package, deliverable, plateau). That last group describes the path from one state to the next.
Aspects separate what acts, what is done and what is acted upon. Active structure covers actors, application components and nodes. Behavior covers processes, functions and services. Passive structure covers the objects being handled: business object, data object, artifact. You can read them as the subject, verb and object of a sentence.
An ArchiMate model example fits in a few elements. A business actor, Sales Department, is assigned to the process Order Entry. That process is served by an application service, Order Capture, which is realized by the application component ERP. The component is in turn realized by an artifact deployed on a node, a virtual machine for instance. One line of reading shows what depends on what, from the business down to the machine.
The schema of the 3.1 exchange format lists eleven relationship types, among them composition, aggregation, assignment, realization, serving, access, flow and triggering.
What does ArchiMate 4 change?
ArchiMate 4 is a major revision, presented by The Open Group as a cleanup and simplification meant to make the language easier to adopt.
The most visible change concerns behavior elements. Version 3 had a business process, an application process and a technology process, and the same for functions, services and events. Version 4 keeps a single set: service, process, function and event. The collaborations of the three layers are merged into one element, and the business role becomes a generic role. Several elements are removed: the interactions, constraint, contract, gap and representation. In an interview published on The Open Group blog, the Forum describes a reduction of about 30% in the number of concepts, from a little more than 60 element types down to 40.
The vocabulary changes too. The term layer is replaced by the more generic term domain, and the matrix of aspects and layers gives way to a concentric layered hexagon diagram. Relationships can now carry a multiplicity.
The Open Group announces strong user-level compatibility so that practitioners can move from earlier versions without disruption. In May 2026 the Forum said it was still working on the certification programs and on the conformance requirement for tools. Before migrating a repository, check which version your tool supports.
ArchiMate vs UML: what is the difference?
The difference is one of level. UML (Unified Modeling Language) is a specification of the Object Management Group (OMG), at version 2.5.1 since December 2017. OMG describes it as a graphical language for visualizing, specifying, constructing and documenting the artifacts of distributed object systems. UML is used to design software: classes, call sequences, states, the deployment of one application.
ArchiMate sits above that. It describes a set of applications in their business and technical context without going inside each one. The introductory guide published by The Open Group's ArchiMate community puts it this way: details rely on domain-specific languages, UML for software design and BPMN for process modeling.
In practice the languages coexist. The enterprise architect models in ArchiMate that the ERP exchanges orders with the logistics system. The development team describes the internal structure of the connector in UML. The business analyst describes the steps of the order process in BPMN.
The common mistake is to push a language outside its ground: a class diagram to present an application landscape to an executive committee, or an ArchiMate model taken down to database tables. If the intended reader is a developer, use UML. If the reader has to decide the fate of an application, use ArchiMate.
What is the ArchiMate exchange file format?
An ArchiMate model lives in a tool, and each tool has its own storage format. To move from one tool to another, The Open Group publishes a separate standard: the ArchiMate Model Exchange File Format, an XML file format defined by XSD schemas.
The published edition, dated November 15, 2019, is aligned with ArchiMate 3.1. The Open Group's FAQ states that it applies to both the 3.1 and 3.2 versions of the language. The format is divided into three schemas: model exchange (elements, relationships, properties), view exchange and diagram exchange.
The Open Group also states its limit. The format is a mechanism to convey data from one tool to another. It is not intended as a persistent file format for the model itself, and the file is meant to be processed by a tool that knows ArchiMate.
In a project, the file is useful in several situations. You can change tools without re-entering the repository, receive a model from a supplier who uses different software, or feed an architecture tool from another source, for example an application map built from the inventory. Before choosing a tool, test the round trip on one of your own models, and look in particular at what happens to the diagrams.
Which tools can you use to model in ArchiMate?
Dedicated modeling tools implement the language: element types, allowed relationships, views. Archi is an open source example. Its site presents it as an open source modeling toolkit for creating ArchiMate models and sketches. It is distributed under the MIT license, runs on Windows, macOS and Linux, and can import and export The Open Group's exchange format. At the date of consultation, version 5.11 supports ArchiMate 3.2. It is a sound choice for learning the language, for a single architect or for a small team.
Commercial enterprise architecture tools add what a local file does not give you: a shared repository, access rights by scope, multi-user editing, portfolio analysis. The Open Group keeps a register of certified ArchiMate tools, useful for checking what a vendor announces.
General-purpose drawing tools often ship a library of ArchiMate shapes. They produce a decent picture for a presentation. They do not produce a model: nothing stops you from drawing a relationship the language forbids, and an element drawn on two diagrams exists twice.
The choice depends less on the language than on your organization. Who will keep the model current, how many people edit it, and where does the as-is data come from? A model entered by hand needs to be checked against the as-is, like an architecture document.
What Uncia brings, and what it does not do
Uncia reads the sources of your IT estate in read-only mode (connectors to clouds, hypervisors, CMDB, firewalls and scanners; dropped-in files such as an RVTools export, a flow matrix or an architecture document), reconciles them in a knowledge base and generates Architecture, Infrastructure and Network maps from it. That knowledge can be exported as an ArchiMate file in The Open Group's exchange format, valid against the published schema, so it travels back into your architecture tools. The other exports (draw.io, PNG, SVG) are described on the IT estate mapping page.
Uncia is not an ArchiMate modeling tool. You do not draw views or design a target in it: it complements your enterprise architecture tool and does not replace it. The export follows the exchange format published for ArchiMate 3.1 and 3.2, not ArchiMate 4. It also reflects what your sources contained at the latest collection.
Sources
- The Open Group Library, ArchiMate 4 Specification (C260), April 27, 2026: description and changes since version 3.2, accessed
- The Open Group, announcement of the ArchiMate 4 Specification, accessed
- The Open Group Blog, "Discussing the Release of the ArchiMate 4 Specification", May 20, 2026, accessed
- The Open Group Library, ArchiMate 3.2 Specification (C226), October 19, 2022, accessed
- The Open Group, ArchiMate Forum, accessed
- The Open Group, license terms for the ArchiMate Specification, accessed
- The Open Group, ArchiMate overview (link to the register of certified tools), accessed
- The Open Group, ArchiMate Model Exchange File Format: overview and FAQ, accessed
- The Open Group Library, ArchiMate Model Exchange File Format for the ArchiMate Modeling Language, Version 3.1 (C19C), November 15, 2019, accessed
- The Open Group, XSD schema of the 3.1 exchange format (element and relationship types), accessed
- The Open Group ArchiMate community, "ArchiMate 101: A Practical Introduction", accessed
- Object Management Group, UML 2.5.1 specification, accessed
- Archi, official site and download page (version 5.11, ArchiMate 3.2), accessed
- Archi, source code repository (MIT license), accessed
- Archi, exchange format plug-in (Open Exchange File import and export commands), accessed
Frequently asked questions
Who maintains ArchiMate?
The Open Group. The ArchiMate Specification is a standard of The Open Group, developed by its ArchiMate Forum.
What is the latest version of ArchiMate?
ArchiMate 4, published by The Open Group on April 27, 2026. The previous version, ArchiMate 3.2, dates from October 19, 2022.
Is ArchiMate free to use?
The specification is downloaded from The Open Group under license. For ArchiMate 4, non-members register for a 90-day evaluation license, then move to a free, perpetual non-commercial license or an annual commercial license. On the tooling side, Archi is open source under the MIT license.
Do I have to choose between ArchiMate and UML?
No, they do not describe the same thing. ArchiMate models the overall architecture, from business to infrastructure. UML, an OMG specification, is used to design software in detail. Many teams use both, each at its own level.
Can the ArchiMate exchange format be used to store a model?
That is not its purpose. The Open Group states that the exchange format conveys data from one tool to another and is not intended as a persistent file format for the model itself. Keep the model in your tool's own format and use the exchange file to transfer it.