 I'm Mark Langhorst. I work with the business design as a managing consultant and chief technology evangelist But I'm mainly here because within the context of the open group. I lead the team that develops the argument language I have done so ever since it was just a research project in the Netherlands I was a project manager of that so we're talking about the argument 3.1 release the new features in there It's actually a relatively minor release. It's a dot release So it's not a major release like 3.0, but there are several useful improvements for end users The most visible one is the new value stream concept that can be used to express How an organization produces value for its stakeholders its customers etc. And so the the stages in which that value is created Another addition that might seem small, but it's very useful for practitioners is the use of an Association relation that has a direction. You can see a directed association rather than just an undirected one So this might seem minor, but it has lots of practical applications and there are many smaller improvements to things like definitions of concepts pictures of the metamodel and some technical details on the so-called derivation of relationships Archimedes started out in the first version as You could say just a language for modeling the core of how an enterprise operates But it has been extended over the years with a number of other concepts first in argument version 2 with concepts for expressing the motivation Behind the architectures how things like strategic goals to stakeholders then in version 3 it was extended with the strategy layer Which expresses things like capabilities and now value streams So the higher level perspective of the organization also a concept like course of action that expresses the strategy itself How are we going to use our capabilities and resources to achieve these strategic goals? That is then linked to this core of the architecture. How are things really operating? So you can really see this You have this line of sight from your strategic goals via these higher level concepts like capabilities and value streams to how that is Realized in practice. So you have this Full connection between these different elements Of course within organizations is just a matter of the architects working together And we have lots of large customers as busy design working with Archimedes But what's maybe even more interesting is to see that Archimedes now Explicitly used as a standard for expressing architectures between organizations and for reference architectures an example is in banking you have the Bayan standard, which is a standard for describing how banks operate. That's expressed in Archimedes Another example is in say higher education in the UK and in the Netherlands in other countries There are reference architectures for universities and other educational institutions expressed in Archimedes NATO has just the last year published a new version of the NATO architecture framework and one of the two Metamodels that you're allowed to use for expressing your architectures is Archimedes So various kinds of applications also beyond just the individual organization. An Archimedes is a relatively lean language It doesn't force you into details. So it is suitable for modeling Within an agile context the essentials rather than all the details Modeling used to be Something that you had to design all the details and and that's no longer viable in an agile context So you have to keep things to the minimum and as a language argument fits well with that So I would encourage everyone to have a look at the argument 3.1 standard the new version And if you have any ideas on future versions evolving the standard further Please contribute to the argument form of the OPEC group join that and be part of the community that Evolves the standard and makes it an even better tool for enterprise architects