 I'm Steve Nunn, President and CEO of the Open Group. Welcome to Toolkit Tuesday, where we highlight the various components and leading experts of the Architects Toolkit, a collated portfolio of the most pertinent technology standards for enterprise architects. During the series, I'll be calling on a number of recognized experts who will bring their particular insights on how to most effectively use the various tools in the Architects Toolkit. We'll have a mix of interviews, panel sessions, and pre-recorded presentations along the way. While all standards of the Open Group are designed so they can be adopted independently of one another, the greatest value for an organization can be derived when they're used in unison, that some of the parts should be greater than the whole. In the Architects Toolkit, we have collated a portfolio of the most pertinent ones for architects, together, all in one place. For most of these tools, certification from the Open Group is also available, so practitioners can demonstrate that they have the skills required, and recruiters can take the guesswork out of the recruitment process all backed up by our Open Badges program. So there it is, second time around. Tomorrow it's going to be first time. I know it is, I know it is. But I would forgive you if you were a little slow after last night. Those of you who were at the castle, wasn't that a great night? Fantastic. Great, great location. Great food. Great company, of course. The networking and what a band. ACDC hip hop and bagpipes in one song. Never thought I'd say that. But yeah, fantastic. But those of you who weren't there, sorry you missed it, but it was great. And welcome to those of you who are joining us today. Mind showing, putting a brief show of hands. Those of you who weren't here yesterday and are today. Good, good. And those of you who weren't here yesterday and aren't today. Yeah, there you go, I knew there'd be some. Yeah, good, good, good. So we've, welcome to the Toga Fuser group. That's what this session is. And we will be live streaming, we're recording the whole event this morning. And we will be live streaming the first two presentations this morning, because that's going to be going out as our episode of Toolkit Tuesday, which we do every two weeks, a 30 minute segment every two weeks of broadcast. And this week we get to be, well this two weeks we get to be live from Edinburgh. So be aware of that. So I will, after the initial intros, I will just say a few words of welcome to those who'll be joining us remotely. But those of you here, let's see. The Wi-Fi, it's around somewhere, it will be on slides and whatever, but the Wi-Fi is, SSID is delegate with a capital D, delegate, and the password is haymarket, all lowercase. And the way we do questions, and please do get some questions, we do have a panel session at the end today. So I think we're going to be holding questions for the panel session. But please don't wait until that point to put them in. As the speaker is talking, please put the questions in and then we can get a more organized panel hopefully for you later. We've got a number of quickfire presentations this morning, relatively short, but lots to get through. So get on with it, Steve. Coffee breaks will be outside, outside the doors you just came in, make it real simple for you today, and lunch will be on this level as well, Lennox One Room. You won't be able to miss it. We are having a drinks reception this evening. I'll say more about the tracks that we go into later before we break for lunch, but there will be a networking reception for everybody. Everybody welcome, 5.30 in the concourse area outside here. So we're making it really simple, you just need to be here on this level. Thank you to our sponsors for their support for this event. It is important and you'll see some of them have exhibit tables outside. Please do take the time to visit them. They'd love to see you. Sponsors this week are Bumi, Konexium, Dell Technologies, Mega International, the Association of Enterprise Architects, and VanHaren Publishing. So thank you to them. Right, pausing. So welcome to our viewers, our attendees for Toolkit Tuesday. You join us live in Edinburgh this week at part of the Open Group event, and we are having a Togaf user group here at the EICC in Edinburgh. Fantastic venue. We've got some great presentations coming up. Some people in the room, so the speakers will be aware that they are addressing both you online as you're joining us remotely and the people in the room. So welcome. We've got a great lineup today, and I want to keep us on track so that you have the full time allotted for each of our speakers, so I'm going to move right into it. But I do hope wherever you are in the world you're keeping well, and we appreciate you taking the time out of your day, night, whatever it may be to join us. So our first speaker today is Chris Ford, who is the General Manager Asia Pacific Region and the Vice President of Enterprise Architecture at the Open Group. It's always good to introduce a colleague, so welcome, Chris. He's based in Shanghai, and as General Manager of Asia Pacific, Chris is responsible for the business functions in that area. As the Vice President of Enterprise Architecture, he is responsible for the Enterprise Architecture portfolio in the Open Group including the Togaf and Arcumate Standards among other things. And Chris is also the CEO of the Association of Enterprise Architects, one of our sponsors here today. And today Chris is going to give a brief overview of the Togaf Standard 10th Edition. So a warm welcome from the Open Group event and Toolkit Tuesday for Chris Ford. Thanks, Steve. Well, good morning everybody. Steve said the topic for the presentation today is the Togaf Standard 10th Edition, which we launched at our London event in April of 2022. So what's new in this edition? What's new is an increasingly modular structure, expanded context specific content. The expanded content includes, for example, domain specific materials. The updated document structure and expanded content delivers on what we've heard from practitioners, what they told us they wanted, more, better and topical guidance on how to deliver the best Enterprise Architecture that supports their stakeholders and their organizations. How do we make the Togaf Standard or, you know, for that matter, any standard that the Open Group produces? All of our activities at the Open Group are member-driven, leveraging the experience of subject matter experts and developed in an open and consensus-based manner through the Open Group Standards process. The Togaf Standard is developed by EA practitioners whose organizations are members of the Architecture Forum. When appropriate, the Architecture Forum and other members collaborate across lines of specialty through what we call working groups. They collaborate with other SMEs in other areas. Now, for examples of these are the current Government EA Working Group and the Ecosystems Working Group, which Phil will talk about shortly. And those working groups are open to all members. Those two examples. Currently, we have many Togaf-specific pipeline activities underway. Those activities are in addition to the 20 series guides that we delivered in April. And I mean many activities. To paraphrase Mick Adams, who's one of the two current co-chairs, along with Celine, who spoke yesterday of the Architecture Forum, this is the busiest, most consequential and most productive period he has seen during his involvement with the Open Group and with Togaf. That's saying a lot, because I've been around this organization 15 years and I think Mick's been around it about the same amount of time. So what is the Togaf Standard? It's an enterprise architecture framework containing a methodology. It's developed by and for EA practitioners to architect based on best practices. It's used by the world's leading organizations to simultaneously transform their business models and improve operational efficiency. So what's interesting about this is it's good in good times and it's good in bad times. It's comprehensive, modular and configurable. And a key point is that its vendor and technology neutral are agnostic. Now regarding the modular structure in the top right of this slide is a partial representation of the Open Group Library which contains multiple standards and materials such as Togaf, Open Angelo architecture, Archimate, Security, Healthcare, Commercial Aviation, Banking, Process Automation, Trusted Technology, IT for IT, that's just a partial list of the materials available to you through the Open Group Library. Now all of those materials are available from the Open Group's homepage. You just go up there, click on the library component. But today our focus is in the center of the slide on the representation of the Togaf Library within the Open Group Library and specifically the Togaf Standard 10th Edition. Now there are two major chunks of the 10th Edition, the six-part fundamental content and the 20 Togaf Series Guides I referred to that are actually grouped in here in summary groupings. The fundamental content should be relatively stable and enduring. The Series Guides are more dynamic and more fluid in terms of frequency of changes and in the delivery of additional topical content over time. Now on the right side of the slide, also in the Togaf Library, related to but outside of the standard, you will find additional guidance, white papers, tools and other materials available to you in multiple formats. This area of the library is actually quite important and I'll illustrate why with a specific example shortly. The Togaf Standard 10th Edition is currently available in multiple formats, three in particular here, HTML, PDF and printed books. And as I said before, you can go to the library via our homepage to access and order these formats. Now it's easy to get lost in the new messages so I just wanted to comment on continuity because the core character of the Togaf Standard is retained within the 10th Edition. So for example, you will still find catalogs, diagrams of matrices, the ADM, the Architecture Development Method and enterprise segment and capability partitioning referenced in the standards. In terms of impactful change, the fundamental content is revised and reorganized. In the center of the diagram here are the six parts of the Togaf Standard fundamental content, the introduction and core concepts, the ADM, ADM techniques, applying the ADM, architecture content, enterprise architecture capability and governance. Now if you're interested in statistics in terms of words, for this segment of the standard, 58% of it is unchanged, 12% is updated and 30% is relatively new. For example, we put anchors into that segment of the standard for the series guides. As I said, we expect the fundamental content to be relatively stable and enduring. Now continuing with impactful change, this list of 20 Togaf series guides is total about 1,089 pages. So if you reflect back to version 9.2, if you took out the front matter and the appendices, you'd be dealing with about 760, 700 pages worth of stuff. Here we're talking about 1,089 pages in the series guides, excuse me, and about 550 pages in the fundamental content. So it's a lot of material. The Togaf series guides offer how-to and domain-specific guidance for practitioners on applying the Togaf standard across a range of topics and contexts. And this list will continue to grow and be revised over time. Now let's look at the list of series guides in another way. In groups of related content such as general how-to, here we have the practitioner's approach to developing enterprise architecture using the Togaf ADM, digital technology adoption, a guide to readiness assessment and road mapping, using the Togaf standard in the digital enterprise, domain specifics. We have six guides on business architecture, covering business models, capabilities, value streams, information mapping, and organizational mapping. A guide for integrating risk and security with the Togaf enterprise architecture. A guide for customer master data management. And two guides relative to agile methods at the moment, enabling enterprise agility and applying the Togaf ADM using agile sprints. Continuing with the groupings, reference models and methods, digital business reference models, government reference model, architecture maturity models, architecture project management, and architecture skills framework. Now for capability owners and sponsors of EA, there's a leader's guide to establishing and evolving an EA capability. So I keep on emphasizing the new stuff and how much there is and everybody's going, whoa, whoa, what the heck? How do I figure out where to start? Well, here's where you should look to orient yourself on the 10th edition. This white paper is your starting point. It's titled an introduction to the Togaf Standard 10th edition. The content is written for three audiences. Enterprise architecture practitioners, leaders of enterprise architecture teams, and sponsors of enterprise architecture. Stakeholders, implementers, planners, and other consumers of EA are rarely directly involved in your customized implementation of the Togaf Standard. Instead, consumers of EA are typically interested in using the outputs of EA to provide options and recommendations to guide their decisions and to govern the direction of those decisions in implementation. Change control, management. That's to say they're interested in the outcomes, not in the sausage making of architecture or customizations of it. Now, this white paper contains an explanation on the motivation for and the substance of the revisions and the new additions to the Togaf Standard 10th edition. It includes recommendations on how to start using the standard and also, in Appendix A, gives you a detailed set of release notes on changes to the fundamental content. I referenced earlier multiple formats. This is the Digital HTML edition. And in this material, which is available online, it's linked, navigable, and searchable from this landing page. You can hopefully see the URL at the bottom here. This will be repeated at the end of the presentation. In the first column on the left, the navigation graphic shows links to the getting started and what's new content. In the second column begins specific content practitioner guidance, organizing EA content, domain specifics, and so on. This digital edition brings together the fundamental content and Togaf series guides, and our intent is to make it easier to navigate and search the fundamental and extended content together and comprehensively. We expect to evolve this continuously as we expand and refresh the content of the standard and receive feedback from you on usability and relevance. You can, of course, download the PDF and buy the books. And actually, you know, the intent here is to help you use the material in the way you want to consume it in terms of those formats. One of the newer features here with the digital edition, which is quite important in my view, is the ability to provide feedback in real time to any part of the Togaf standard. So when you go down through that navigation path, you'll find an itemized list in the left side about what content is available, but also a little icon at the top for comments and bugs. And if you click on that, you're going to launch a form which you can fill out in context and submit comments or bug reports about things that are a problem with the standard. So, for example, in one of the meetings yesterday, excuse me, a lady from the MOD was saying, I found consistency issues with terminology or language, and how are you going to deal with that? Well, we can't catch all of that necessarily in the editorial process, but as you see it, you can tell us and we can try and deal with it. So how does that occur? Feedback through these forms are triaged by our editorial team and it's appropriate if it's not just an editorial issue, it's routed to the architecture forum directors on my team and it's addressed and prioritized by the product team and by the forum members for disposition. So I really encourage you, whether you choose to interact with the PDF material or the books or digitally online with us through the HTML and you find an issue or you like or dislike something that's going on, please use this feature to comment and let us know what your impressions and what needs to be corrected. Now, earlier I mentioned that I'd provide an example of other important content in the library. Here, this guide document titled How to Use the Archimete Modeling Language to Support the Togoff Standard was actually published simultaneously with the 10th edition, but you wouldn't know it because it wasn't part of the standard and wasn't advertised as such. It's in the Togoff Library I'll be done soon. It's in the Togoff Library but it's not a part of the certification program. So why should you pay attention to it? The document was a collaborative effort between the Archimete Forum and the Architecture Forum and it proposes example models using Archimete Notation and I've extracted here the Enterprise Continuum and the ADDM represented in Archimete. There's also a textual comparative analysis of the relevant components of the standards. Beyond the text the models in Archimete Notation are available for you to use and customize for your own organization. You can access them through the Open Group Archimete Exchange file format and import them to any EA tool to provide to support that exchange file format. There are many other examples of useful materials for you in the Open Group Library in general and the Togoff Library specifically for you to leverage in your architecture endeavors. The main point being that the library is a source of multiple resources for architecting and accelerating architecture delivery and time to value. The main point being that the library I'm sorry is that now Mark Lancoste will be covering this material in more depth later in the session today. So looking ahead for content what's our intent? More Togoff series guides in development more EA supporting content such as guides on white papers like I just referenced more frequent updates to the Togoff standard and innovative ways to access and adapt the content. As I said earlier actually there are currently 20 pipeline activities underway related just to the Togoff standard in our enterprise architecture portfolio of products. So we delivered 22U in the market in April and we got 20 in the pipeline. Looking ahead for Togoff certification yesterday during the plenary session of the Edinburgh event Andrew Josie our VP of standards and certifications at the Open Group and Dave Hornford a partner at Conexium announced the Togoff certification portfolio following a successful beta. Andrew will do a deeper dive on Togoff certification later but here's a brief reference. The Togoff certification portfolio includes the Togoff 9 certifications Togoff enterprise architecture certification Togoff business architecture certification and Togoff certification credentials. New learning paths have been developed that include direct paths from Togoff 9 foundation and upwards and recognition of Togoff 9 certification with a bridge path to the new materials. Now here's a list of staff emails of folks who can be contact points for you and to our URLs for access to the current materials. And that's basically what I had to cover for you today. Thank you for joining us here at the Togoff user group session in Edinburgh and the Toolkit Tuesday broadcast. Steve, back to you. Thank you. And as a reminder we will be doing questions on the panel session that follows later which I realise for those of you joining us remotely on Toolkit Tuesday means you won't be able to hear them live but you can still submit questions and we will be having this whole session will be available on the Open Group YouTube channel next week so even if you can't see them on Toolkit Tuesday today if you do submit a question we'll hopefully get to it on the panel and you'll be able to see how it was answered then. I started talking about questions earlier so to submit questions please go to slido.com slido.com and enter the hashtag o-g-e-d-i small o-g capital D, capital I and then you'll be able to submit your questions you don't need to download anything just any connected device will get you there just a reminder on that. Thank you Chris for the great introduction our next speaker is Phil Tetlow who is the CTO at Data Ecosystems with IBM for the past 21 years Phil has worked for IBM as a technical architect and he's also the Academy of Technology Vice President Emerging Technology where he helps top 100 companies build really big data and analytics at analytics IT systems in this session Phil will look at Ecosystems architecture which is a new era of network of systems working towards shared goals often above enterprise level so a warm welcome from the open group and Toolkit Tuesday please for Phil Tetlow Thank you very much Clickers on there Thank you Good morning everybody good afternoon, good evening for those watching on YouTube thank you very much for giving me this opportunity to speak I want to talk to you about a challenge but more a huge opportunity that we have as a global community of architects and if I do this properly I might be telling you where we're all about to head I thought about how I wanted to present this morning and I decided I could do it one or two ways either I could tell you about some things that a growing community of architects have been doing or I thought I could tell you a story about a whole series of meetings and coincidences and realizations and I decided it was probably best to do it the informal way and tell you a story so where to start I was a young technician dare I say a young architect I can remember being in a taxi I had a long taxi ride with a very very senior internationally recognized software engineer and I was talking to him about the nuances of architecture and practice and technical challenges and so on and so forth and he stopped me after about 20 minutes and he said Phil, Phil, Phil that's great he said but you need to understand something about the two things that we get better at as we increase our understanding of technology he said the first thing is we learn how to scale he said we build bigger, better, faster stronger things he said that's always been the history of technology it doesn't matter whether we're talking about silicon you can be talking about stone or metal or bronze or that's what we do as a species and he said the second thing is generally as we build bigger as we scale out we tend to increase the complexity that we build as we build bigger bridges we need to introduce new and different techniques and technologies for handling the spans that we aspire to cross handling the loads that we expect those spans to be able to hold and he said but there's a flip side to scale and that's complexity and he said the thing is that the human brain isn't particularly good at handling increased levels of complexity we were built to throw spears and stones at Buffalo and Rhino on the plains not to build bridges and steam engines he said to compensate what the human brain does is we abstract we move away from the problem so that we can handle more and more stuff inside the limited capacity of the human brain and I remember learning from that session and thinking I'll carry that forward and if you relate to those two ideas or if you if you look at the history of technology and specifically architecture, IT architecture through the lens of complexity through the lens of scale and complexity then this is probably the way that our profession or our industry has played out or has played out so in the early years of the IT industry we worried about bits and bytes then eventually we scaled out to dare to worry about units that we used to refer to as being programs then we became even more ambitious we started to talk about objects and components and eventually we became so adventurous we started to talk about systems and then eventually we got to the point where today we talk about systems of systems and when we talk about systems of systems we generally give the systems of systems to refer to those collections of systems to be enterprises and we talk about enterprise architecture but there's a problem with the term enterprise and there's a grand challenge with the idea of enterprise architecture and the reason for that is that around the architecture profession the industry hasn't stood still we've scaled out even further and we've abstracted even further what I mean by that is that if we look at the definition of an enterprise today the definition that we use in forums like this I would suggest is no longer relevant and applicable why? that's the big question well when we as professionals refer to the idea of an enterprise what we're essentially talking about is a closed box we think about companies as if they're a container and inside that container we build other containers or components and we link those components together into networks of capability ultimately for the benefit of either the individuals or the organization itself or the business units the individuals or the organization itself that's what we do, that's how we earn our money however in this age of highly connected systems particularly with technologies like the internet and the worldwide web most organizations do not live with inside a closed or confined context today most of the architectures that we build actually arc out beyond the barriers the edges of what we used to consider the classical enterprise often the domains that we probably find hard to define not only do we find that the tendrils of our IT systems are flowing beyond the barriers of the classical enterprise but they're also doing it in a way that is increasingly beyond the control of the individual architect or architecture teams today in the world of technology or the world the world of technology in which we live it's perfectly acceptable to talk in terms of almost organic evolution systems talk to systems those systems talk to other systems and eventually we produce the global network of connectivity that actually we're all bathed in how do we apply professional practice in that open context what are the new challenges that we need to think about as architects how do we apply rigor how do we get to the point where we can apply or we can work to all the professional standards that we hold so dear that was the challenge that we started to think about first of all inside IBM and ultimately we took that up to IBM's Academy of Technology which is the elite team of technical experts at the very top of IBM and inside the Academy of Technology we started the eco systems architecture team and surprise surprise that was an exciting adventure so the first question we asked was if we talk about this network of networks or evolving systems of subsystems with no boundaries no closure what are we talking about and we spent two or three years actually vigorously debating the definition of what an eco system should be from that we eventually established a starting point if you like a ground zero a set of base standards where we could at least start to discuss formally the type of challenges that we felt we were facing in there we say enterprise age and here we have them here you see them before us so this is the seven plus one keys of viable eco systems I'm not going to read the slide out you can read it for yourself but it contains elements that some of which will be obvious some of which are embedded in very classical ideas of architecture some of which are not so classical and some of which might seem rather daring so ideas like number four must support instrumentation and observation of both participating element and group levels this includes implicit awareness of its environment given that this can be considered as both a unit and group participant in an eco system so how how do we apply the idea of context at varying levels of scale and abstraction how do we make that recursive or almost a fractal type structure and how do we apply it across multiple domains multiple dimensions for different reasons of different times and different colors in different ways and the particular slide that you're looking at here it did take us about 18 months to put together where did we travel next so relatively recently we tried to pull seven plus one principles into a very loose framework to direct future progress the name isn't precious we decided on the acronym Viper because we thought it was familiar it would be appealing this comes out with some work that my esteemed colleague Paul Holman has applied with many clients and many very successfully delivered projects and Paul and I came together and took the work that he'd done in and around this esteemed community and with his clients inside IBM and I tried to infuse the thinking here with the ideas that I'd primed and some work from a number of colleagues elsewhere inside IBM and at the moment we're now opening that up to the global community inside the open group hopefully for wide and vigorous a challenge so again I'm not going to read the slide but hopefully you'll see some elements of good practice here so viability, integrity, probability the fact that components agents, nodes in a network may or may not participate inside the network or network of networks and that their participation may not be directly in the control of an architect the point that we're trying where we're trying to head next with this working group is we want to move on beyond definitions and base understandings what we're trying to do is push forward into a phase where we can openly ascribe to a set of recognisable tools that we can apply on top of standards like TOGAF where are the challenges with regards to actual practice well if you look at the de facto in modelling today this slide essentially says that in order to fit inside I'm going to digress slightly again I was at a conference once and there was a very erudite technical speaker who was on the stage and he posed a question to the audience in fact that's what I'll do today so he asked the audience and he said could anybody here today give me the unit of measure a unit of measure for length so does anybody in the audience want to venture a unit of measure for length yeah millimetres, meters, inches, centimetres yeah furlong, good, yeah great whatever unit of measure for capacitance I thought it was coulombs, could be wrong maybe whatever so here's the killer question what's the unit of measure for complexity the answer is we don't have one anyway this guy volunteered and he said I think we do he said I think the unit of measure should be the head fold if you can't get a problem inside your head then by definition it's complex it should measure complexity in head folds the reason that we use the schematics that we use today is that they're familiar with the human experience what this slide is essentially trying to say is that for years from the very very start of the architecture profession the weapons of the architect the chosen weapons for architects have typically been the spear and the shield so lines and boxes we do everything with boxology but every single one of these diagrams you can distill it even further essentially what we're talking about is just nodes and connections they're all graphs but the problem with the type of schematics or the underlying principles of the architectural methods we use today is one of context they're all good at describing specific context and applying specific types of closure but what happens when you actually need to smash different types of diagram or different types of thinking together and that happens in an ecosystems world when you can't describe accurately what you want to describe how could you smash together a data model with a component model how could you smash together a flow any type of flow with a probabilistic representation of nodes or I'm making this up as I'm going along and the conclusion that we came to inside the group was essentially what we've got to do is we've got to work out we've got to move away from two-dimensional thinking to end-dimensional thinking we've got to be able to co-represent different contexts within the same grander context and when we started to think about that problem about how do we deliberately get an overlap an intersection between different types of thought methods or approaches or methodologies what does that mean and you would think that it actually speaks to a train crash but we stood back a little bit further and we looked at the problem from a distance and what we actually found was that if you go out to other formal disciplines then this problem has been and has been solved many, many times before so if you go out into fields like biology or physics especially physics what you'll find is that the physicists have had to handle problems exactly like this where you're dealing with different phenomena and you have to be able to combine said phenomena into a unified method describing a situation let me give you an example from history I've just done some I've just finished writing a book on actually the history of information but as part of that I had to do some pretty deep research into the work of Alan Turing during World War II and I was privileged to work with the historians at Bletchley Park let me tell you some lesser known facts about Alan's work during World War II most people think that he was predominantly focused on cracking the enigma code he was but later on in World War II he also became interested or worked within a team who were trying to crack a code so the enigma cipher was the code that was used by field commanders to send instructions to the troops out in the field the Lorenz cipher was the cipher that was used to send instructions from Hitler's High Command to the field commanders it was a much more complex heavyweight code and Turing worked alongside a guy called Bill Tut Turing's contribution it was actually Tut that cracked the Lorenz cipher not Turing Turing's contribution he worked in the field of Bayesian probability Bayesian mathematics Bill Tut and I think this is a crime because Bill's almost been written out of history simply because of the success and secrecy of his work Bill Tut was one of the founding fathers of graph theory in my mind he was one of the first systems architects to come out and link together ideas and his predominant work on cracking the Lorenz cipher was actually linking symbols using graph theory what Alan Turing did was he brought together the idea of probabilistic linking so that you could work across complex networks and reason when individual symbols were due to come together again what's lesser known the historians at Bletchley believe that the work that was done on the Lorenz code was later remapped to not predict enemy positions prior to the D-day landings in World War II and again if you speak to the historians that's the reason why the Allies knew to a level of almost certainty where the major threat points were when they invaded the beaches if you take forward that work so if you look at probabilistic linking of graphs and dare I use I'm going to use a big word here inside architecture as traditionalist we like to use words like hierarchy there are better words to describe the coming together of networks and the ugly word that I like to use is an ontological approach towards architecture and the difference between a hierarchy or a network the difference between a hierarchy and an ontology is that a hierarchy has a single single entry point and has a root an ontology has multiple entry points for multiple reasons at multiple times in multiple colours and if you would apply probability over the top of an ontological view of networks you can replace the term network with architecture at any level of abstraction be that at systems or enterprise or ecosystem level then you stand a reasonable chance of modelling anything and that's how you can successfully crush together multiple different patterns of understanding anyway that's the point we got to I'm doing some work inside IBM with colleagues who are interested in quantum computing and the thing about quantum, the quantum world and I'm very very hopeful about where we're going to be going with quantum computing is that in the quantum world it is absolutely open up to that type of scenario where you're dealing with very high scale very connected very probabilistic networks of interaction so maybe in 10 or 15 years time if I'm still around and there's an invite we might have a session on quantum architecture wouldn't that be a thing anyway sorry I'm going to end there that's essentially the journey we've been on the point we're at now as I said we've got the brace principles in place we know what we're talking about we know some mathematical tools and techniques that we can apply so probabilistic network theory Bayesian techniques as it were there are mathematical techniques like homology to actually look at gaps in architecture to figure out whether or not we need to pay attention in areas that we're not we're looking for able and noble individuals to help us on that quest if you're interested please speak to me later on today if you're not interested please speak to me later on today rather lonely I'm looking forward to lunch that was a pleasure ladies and gentlemen thank you very much for your time thank job and I will remember at some point in the future an erudite speaker talking about a head full of complexity fantastic job thank you so that concludes Toolkit Tuesday for this episode thank you to our speakers Chris Ford and Phil Tetlow and thank you all for joining us there will be as I say the whole session here in Edinburgh will be available on the open-vip YouTube channel sometime towards the end of next week I think so if you have questions you've submitted questions then look out for how they are answered next time on Toolkit Tuesday will be November the 1st and we'll be talking about the value of zero trust architecture my colleague John Linford and one of our members, Nikhil Kumar will be talking about that on November 1st so join us then for Toolkit Tuesday thank you very much for joining us this time around