In the previous postings of this series we have introduced the (history of) the ArchiMate language, its underlying framework, the core concepts as well as its extensions. This should give you a good overview of the language. On the one hand it may seem complex (many concepts, many different types of relations). On the other: there’s a lot of structure and symmetry to the language, making it fairly easy to learn. Still, it is a good practice to tailor the language for use in your own organization. This posting is all about that: how do we customize ArchiMate for use in our organization?