 So let's get on to the meat of the presentation. First of all, what does it provide? Well, this is, of course, familiar to any argument to a user or any argument to one user already. Archiment provides you a language with concepts to describe enterprise architectures. And it has its in-built framework for organizing these concepts. And I will show you how this framework has evolved over the years. Of course, Archiment provides a notation for these concepts. So it provides you with a way of graphically displaying your architecture. But it also has its vision and visualization of architecture for different stakeholders. So this notation is not the only way you can display these models. You might want to use other ways of doing that. And later on in my presentation, I will also patch upon that when we are going to talk about viewpoints. And finally, of course, it's an open standard maintained by the open group. But since you're attending an open group webinar, you will know about that. So why did we develop a new version of Archiment? Developers of the new version started about two years ago. And over the last few years, since version two came out, we saw an increasing demand for relating enterprise architecture to business strategy. More and more organizations have recognized that PA is not just an IT thing, but it's really a way of realizing your strategy of implementing a strategy. And vice versa also, a feedback mechanism up towards the strategy. So architecture should be connected better to the strategic world. Secondly, we see that there are a lot of technology innovations that mix IT and the physical world. Say, for example, the internet of things. In Archimate 2, it was possible to model the internet, but we didn't have any concept for the things. So the physical world is something we needed to add. And also in more traditional domains, like manufacturing or logistics or other, say, physically-based companies, we see increased usage of enterprise architecture. So we wanted to support those domains with concepts from modeling the physical world as well. Then of course, in applying a language like Archimate and Practice, you always discover some inconsistencies or things that could be improved or various areas in which we wanted to improve the usability and make it easier for people to understand the language. And finally, of course, the open group has more standards than just Archimate. And we wanted to improve the alignment between these standards. And of course, most importantly in the enterprise architecture domain is Toga. So there was already a project working on harmonization between Archimate and Toga for the last two years, looking at definitions, et cetera. So that's also been input to this new version. I won't read out all the definitions to you. Don't worry about that. But you can find in the standard the differences and see which definitions have been improved at. So first of all, the Archimate framework. Well, those of you who are familiar with Archimate know that its core is constructed of three different aspects, as we call them. We have the access structure aspect, which comprises the subjects of the sentence, if you want to put it in grammatical terms. In this case, John. We have the behavior, the verbs in the sentence. So in this case, John reads. And what does he read? He reads a book. And the book is object. So this active structure behavior, the passive structure, that's really the core of the structure of the language. That has been like this ever since the inception of Archimate. And in its first version, we have these three layers of business application and technology, which were, and perhaps still are, the most common layers you see in enterprise architecture approaches. Some people might say you want to have an information layer there as well, but it's very important to know that Archimate uses this passive structure column to position information architecture. So it's not a separate layer, but it's integrated across these three layers. So the information really resides in the passive structure aspect and not in a separate layer. So this was Archimate 1. This was where we started when Archimate was transferred to the open group. This was what was developed in the R&E project that I met between 2002 and 2004, as I've already mentioned. But then when people started working with Archimate, they discovered that it did cover the core of the architecture but it didn't cover the motivation behind the architecture, things like your goals and your principles and your requirements. So that's the first addition we made. And of course, you also want to describe how an architecture should be implemented, so which steps to take, plateaus, which work packages should implement parts of that. So those were the two main additions to Archimate in version two, demotivation and implementation and migration extensions, as they were then called. Later on, I will talk about the word extension. We're not going to use it anymore in Archimate 3, but I'll leave that for now. So where are we now? Well, first of all, like I mentioned at the start, people are increasingly using enterprise architecture in a more strategic context. And of course, many people ask for concepts in this area already for the last years and perhaps capability as a concept is the most prominent one. We'll talk about that later on. So we now have some more strategic concepts to link architecture to where the organization wants to go. And secondly, we have this layer of physical concepts. And as I already said in my introduction, this is tightly integrated with the IT world since we see that physical technology often is IT-based as well. The Internet of Things is just one example, but most equipment nowadays is computer control. So it's really tightly coupled to the technology layer. I will discuss it later on as well. So this is now the new framework for Archimate 3. So these different areas are now covered by the language and that's what we'll zoom in on in the rest of this talk.