ArchiMate 3.0.1 metamodel PDF

I’ve created a PDF that  you can print two sided (and laminate if you like) to have easy access to the ArchiMate 3.0.1 metamodel. (Last updated: 9 Aug 2017)

On the front it contains the Core meta-model. It is depicted in the Mastering ArchiMate colour scheme (this link gets you to a depiction of the ArchiMate 1 metamodel, which also illustrates how much ArchiMate has grown over the years), which shows both differences between the layers and the aspects (active structure, behaviour, passive structure). I use that colour scheme because it tends to be easier to grasp diagrams if the different aspects are shown in different colours. It also helps in explaining the language. There is a simple layered-colour version as well, see below.ArchiMate_3_0 Core-Metamodel_Selection_9Colours

I have expanded any non-usable element (Technology Object, which is an abstraction in the meta-model that cannot be used directly, only its subtypes Artifact and Material can) and replicated the relations that come from it so the sheet only shows real meta-model elements that you can use in models (and their direct relations, except the always allowed Composition/Aggregation from an element type to itself). I’ve used a bit of colour coding and labeling of the relations. It also shows all the cross-layer direct relations.

I’ve also left out all Collaborations and Interactions. Most can now be expressed by using Junctions on relations and using just the above set.

On the second page (back), the other domains of ArchiMate are shown. First Motivation:

ArchiMate_3_0 Motivation


Again, except for refering to the rest of the meta-model, I only show real element types. I’ve left out all the possible Influence relations (though they are mentioned) and again the always allowed Composition/Aggregation from an element type to itself. “Any Structural of Behavioural Element” is a reference to the meta-meta-model. It is assumed the reader knows what this means (in Core, Strategy and Implementation & Migration domains).

Then Strategy:

ArchiMate_3_0 Strategy in Context


I’ve used my Core colour coding to signal which parts of the Core meta-model can Realise which element of the Strategy domain (which the standard calls a ‘layer’).

And Implementation and Migration:

ArchiMate_3_0 Implementation and Migration Overview


Here, I used a grey diamond on relations to signal they may either be a Composition or an Aggregation. Again, self-referenced Composition and Aggregation are not shown.

Finally, the Composite Elements are shown:

ArchiMate_3_0 Composite Elements


The PDF is fully vector, so it can scale to unlimited size without becoming pixelated. Print it on a banner the size of a house and drape it in your conference venue 🙂

And for those that like the layered colour view that doesn’t differentiate between the core aspects. Here is a link to a PDF that shows the ArchiMate 3.0.1 metamodel in the ‘simple layered’ colour scheme. The front side looks like this:

ArchiMate_3_0 Core-Metamodel_Selection in Simple Layered Colours


[Updated on 10 Sep 2016. A few labels were fixed.]

[Updated on 25 Sep 2016. Main changes: Left-to-Right orientation, several relations fixed, changed colouring on relations, better explanation of Specialisation.]

[Updated to ArchiMate 3.0.1 (ArchiMate 3.0 Technical Corrigendum 1) on 9 Aug 2017.]

This entry was posted in Mastering ArchiMate, Using ArchiMate and tagged . Bookmark the permalink.

18 Responses to ArchiMate 3.0.1 metamodel PDF

  1. Marc Lankhorst says:

    Good work! I’d like to have the model source so I can create a version in the original color scheme of the standard itself, would that be possible?


    • gctwnl says:

      Even better: I created it for you. There is now also a version in the layered-colour scheme. See the text of the post (the link and how it looks is at the end). I also removed the colours from the ‘Strategy in Context’ diagram and changed the Implementation one, so I think I did not miss anything. I also improved the text and checked if the transformation did not change anything (as a bit of trickery is going on in the model to make the diagrams look as they do).


  2. Fantastic work – thanks so much – will be printing this off and putting on my desk at work!


  3. sergebouwens says:



  4. Thanks a lot for the metamodel. It’s really appreciated


  5. gctwnl says:

    Note to all: the PDF’s have been updated in a non-minor fashion. There were still a few omissions in the existing PDFs and on popular request, I’ve changed the orientation Left-to-Right.


  6. Ben Heideveld says:

    Prachtig Gerben!


  7. Daron Townsend says:

    Excellent resource, Thanks for putting the time into this


  8. Jeff says:

    Thanks very much for taking the time to do this. Much appreciated!


  9. fabio castiglioni says:

    Rem tene verba (in this case drawing) sequentur… You are always the Master Gerben!


  10. Pingback: Crossing the EA Chasm: Graphitization of ArchiMate 3.0 | - digital intelligence

  11. smileham says:

    I keep coming back and referring to this PDF while building models, it’s incredibly useful, but I also just wanted to point out that the link from the “tiered” colour scheme diagram is a little broken.


  12. Pingback: ArchiMate 3.0.1 | Mastering ArchiMate

  13. Barnet says:

    How do I show relationships between two or more concepts when drawing a model?


  14. Philipp says:

    Any way I can’t understand what’s different Archimate 3.0.1 vs 3.0…


    • gctwnl says:

      Not very much in the core metamodel. Here are some:

      • Triggers and Flows between events and services were added
      • Triggers and Flows from service to service were added
      • Assignment from Device to Artifact was moved back to Node to Artifact as it was in ArchiMate 2.1
      • Material can Realise Business Object
      • Technology internal behaviour (e.g. Technology Function) can Realise Business behavior

      The derivation mechanism was much improved in the standard. And the full table of all possible relations (core and derived) has been improved immensely as a result (it contained hundreds if not thousands of errors making it impossible for any tool to be both ArchiMate compliant and usable at the same time…)


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s