 So, rhaid attacks y gallwch gynllunaf ar y cyfnod o'i ddweud o'r cwestiynau, ond, yn ymweld, y gallwch eu cyflwyno'n mynd i'w gweithio'r awgfyrdd yma sy'n mynd i'w ddifreson wedi'u bod 9.1 a 9.2 yn y dywed y dywan i'r Cymru? I can be very facetious and say that if you put the books side by side you need a magnifying glass to see the differences. However, first of all there's a difference in philosophy Roeddwn i'r wneud o'r rhanau cyfnodd maen nhw'n ffordd ar hyn o'r standard o monolethau, sy'n meddwl i'r ddifigol yn ddifigol yn ddifigol. Rwy'n ddifigol. Mae'r ddifigol yn ddifigol y 9.2 ymlaen yn y 9.1 ym mhwynt. Mae'n ddifigol yn ddifigol yn ddifigol, mae'n ddifigol yn ddifigol sy'n ddifigol yn ddifigol. Mae'n codiwch perl Dawyer yn y gallu myned photographer, mae'n gwirioneddol chi здесь i dda fo iawn am y gofyn wieldaeth delaw o'r mindd yn gwneud neigten nw, mwy farchig o fi ar elidwyaeth o'r identitykrwch mewn ymarferio, am bwysig yma i weld nesaf dyma. phil o'r defnyddio. Yn gyfnodion o'r cyfnodau ond ynghylch ar gyfer gwaith fod yn ei wneud, yn ymgyrch â'r rawr o'r material ar gyfer gweinol, oherwydd mae'n dod i'r rhan o'r gwaith, ac mae'r metr yn gweithio'r model. Felly, mae'n i'n gwybod, oherwydd mae'n gwybod, mae'n gwybod i'r model yw yn ei wych yn cael eu rhan o'r model. Felly yw y moddlaeth, oherwydd yn gwybod rhan o'r model yw'r 9.1, mae'r gwahodd tais o ddiddordeb gyda'r gwahodd o'r cyflaid? Mae'n gweithio o'r cyflaid. Rydyn ni'n adrodd yn llaw ar-gweithio, mae'n cyfeithio'r model mewn methu, mae'n adrodd yn y Gymru. Ac mae'r gynhyrch ar y cerddau gyda'r gynhyrch yma yn fawr yw ymlaid. Mae'n olygu'r gion iaith yma, mae'n gweithio'r gynhysgau cefnogi. mae'n cyflaid o'r cynnig o ddechrau'n argymdeithio. mae'n gwneud gwahanol amser, ac mae gwahanol amser yn gweinio'r gweithio ar gyfer oed ddweud yn y gwrthodod. Dyma'n gweithio'n gweithio'n gweithio. Rwyf ddim yn ddweud bod ni'n gweithio ar y dyna, ac mae'n gweithio'r gweithio ar y dyna'r concept o ddegawr bodi i bobl ac yn gweithio'n gweithio'r gweithio'r gweithio sy'n gweithio'r gweithio. Peithas chi'n gwneud yn gwneud hynny o gyfweithio'r Ddegw? front line ofFi canyon. We've now, as Mike mentioned, we've broken some of the break information out from the standard but also add much extended guidance into what we call the Toguff series guides. I think today there are seven published and there are three almost due to come out so if you look at the reference cards I think there's going to be a list of 10. Yesterday we delivered in the body of knowledge. I think there were over 30 deliverables which if you then add the Toguff series guides makes with Tog dub HTC Monarch 40 documents. Yn oedd y ffordd yma yw 100 oeddau gwahanol yw'r hynny i'w llyfrwydd yn ei airion o'i bwysig yw'r hynny i'w llyfrwydd yw'r gwahanol yw'r hynny i'w llyfrwydd yw Llyfraniaeth, a ddweud ym mwynhau a'r hynny, i'w ddweud ymwysig yw'r Hefyd, o'i ddweud yr Ffyrdd Toghath Rhaid, a yna'n fawr yn dweud o'i ddweud ar gyfer y mae'r gyda'r cymaint y cyfrifol o'r thysgau'r cyfrifol ymlaen. Mae'r cyfrifol y byddw i ddefnyddio i gyfrifol, ond maen nhw'n gwneud, ac yn ysgrifetigau Togurf Cymru yn ysgrifetigau, yn y sylfaen o'r cyfrifol. The other thing to realise is that the Togurf Cymru is going through the same consensus process as the standard itself, so there are very much consensus-based documents and have basically the same status as the standard. Therefore we can build things, a certification around those as well, So you will see, and we'll talk a little bit more about how the certification programs are being extended to sort of cover the TOCA series guides. Right. Right. The whole body of knowledge concept. The series, it's a good point you make about the series guide. They are, they go through pretty much the same rigorous process as the standards. Where there's a different track for white papers, but the guides if they're published in that series they've really been through the consensus process, which is important to note. Here we are, I've got some questions coming through. Mike, what's the impact... What is the... Can you say a little more about the TOGAPP library, please? Oh, yes. Any of you who have been involved in the Architecture Forum will know that I have been very keen on capturing the ecosystem around TOGAPP. I'n ddweud o diagran o'r sylwgr yn ymgyrchu, yn cael y rhai yma. Ynno? Mae'r cyfnod i'w ddiogel fod yn ysgrifennu'r cyffredin. Yn'r unrhyw yng Nghydrogyff yn ymgyrch, yn'r unrhyw yng Nghydrogyff ymgyrch yn awr. Yn ymgyrch yn ymgyrch, mae nid, yn ymgyrch yma, ar y cyfnod yma, ar y cyfnod. Mae'r gŵf yn ystafell oherwydd rôl ystod yn dîm ystafell â'r cystafell hwn. Mae'r ddweudhyn y gallwch yn gyflwyfiadau, ydych yn adwyd, ddwyllt, a'r ddwyllt yn ddwyllt yn ddwylltol benthau'r cyfanol ac efo'r ddwyllt. Byddwn i ni fydd ar duddangos, efo'r 40 oed, oedd ydwch yn ginden nhw'n cymdeithasol a fydd ystafell i'r dystafell ystafell. That means we actually have an architecture of resources. We've got dependencies. We've got relationships. So one of the things I've been very keen on is in documenting that, promoting it. The Togaf library is the thing which captures the components of that ecosystem. And we've done a lot of work in the last year in structuring that to make those documents much more visible. So if you're a telecommunications company, there is a document telling you how to use the Togaf standard in the telecommunications area. If you're in banking, if you're in mining, if you're in defence, all of those things exist. If you want to know how to apply project management to the Togaf process, it's all there. And it's making that visible, which is a major element of this release. The big value of this release that we've made this week is actually not Togaf 9.2. It's a Togaf standard version 9.2 trademark lawyers. It is making visible all of the work that many, many people have done over six or seven years in bringing that standard to life. Thank you, Mike. Next question, ideal for you, Andrew. What's the impact of the new version of the standard on Togaf 9 certification program? Okay. Well, what we did originally when we set out with Togaf 9 certification was actually to build in the capability to cope with Togaf 9, 9.1 and 9.2. The bottom line is that the program is all designed basically to absorb 9.2. There have been some updates to the program, but if you're already certified, you don't have to re-certify. Basically, we have a transition period, so courses have six months before they have to update to the new standard. If you're studying, you basically have 18 months because what will happen is we will switch. We will actually switch the exams right now so that the questions are actually sort of agnostic. They can work for both 9.1 and 9.2 and 18 months time. We may start asking 9.2 specific questions. Why do we pick 18 months? Well, the reason there is because there's a six-month period before courses have to overlap, but then you may have an exam voucher which lasts 12 months. That's why we allow that period. Basically, we've got that. It's a planned transition. It's the same as we did last time. If you're somebody who's been certified in the past to Togaf 9, there is actually now what we call a credential, which is something new that we're introducing in our certification program, which is basically a lighter weight, smaller amount of learning. In fact, in this case, it's a three-hour amount of learning that you can do to show that you actually got up-to-date knowledge of what's changed in the 9.2 standard and the ecosystem around it. In fact, we've got a course on them here tomorrow afternoon that Mike is running, which will actually be doing that training and delivering the credential. In fact, all of our trainers within the Togaf 9 certification program, they are required to have this credential in order to continue training because some of them may have been, in fact, some of them were certified originally back in, I think it was February 2009 when we started. Really, we wanted to make sure that our trainers do have the knowledge, the full understanding of all the changes that we put in place. We were pleased to see, in fact, yesterday and today, I think we're up to 57 of our trainers have now got the credential as of this morning. We're probably going to make about 100 before the end of the month of the trainers, so that's our target for a few people to straggle a bit, but some people are keen of another. That's basically the story with certification. It's a planned migration. It's evolution. Things like the study guides, they have been updated. Yesterday as part of the release, like I mentioned, I think there were about 30 core documents went out yesterday, but the study guides, the practice tests, these have all been updated and were delivered yesterday. The training materials at the open group licenses, they were also delivered yesterday updated to the 9.2 release. Okay, thank you. Mike, you mentioned metamodel earlier. Questions come in. Have there been any metamodel changes to accommodate security concepts, such as policy trust domains, threat opportunity, weakness strength and risk and control? Put very simply, within the core standard, no. That is because the core Toga standard has to be totally generic. It has to be applicable in every possible situation, and our policy is that if you want to have a style of architecture where you are applying it is constrained, you document that in a guide rather than in the core standard. We still believe, no, we don't believe, when we put the Toga standard together, we did not necessarily believe that security was a major concern for every company. So security was addressed as a free standing guide. It is still addressed as a free standing guide, which was refreshed about 18 months ago. A lot of the concepts that you referred to there are covered in detail in that guide, but not in the basic foundational metamodel within the Toga F9.2 standard. Okay, thank you. A couple of questions that are essentially the same. What's the plan for future development of Toga F9.2? Can I pick up on that? We discovered that having a content driven plan in a volunteer organisation with no assignable resources was non-deterministic, which is why it's taken us such a long time to get to version 9.2. What do I mean by that? I mean we say, well, we're not going to issue, we're not going to deliver a new version until we've done this, this, this and this. So just over a year ago, we decided we were going to go on to an annual cycle. We would capture changes, and it's important that we capture changes because we do need to keep the Toga F standard and the Toga F ecosystem up to date. But we would capture changes based on the willingness of people to work and contribute. Over 25 years, that's proved to be a really valuable filter about what is important to people. And so each year, we are thinking, our plan is that we will refresh the Toga F standard. Some of those changes may be very, very minor error correction. Some of them may be... I suppose we will call that maintenance, wouldn't we? Some of them may be minor, and the ones we put in this year are relatively minor. At some stage, we will have a major update, but we won't take a decision on that until we've seen what changes are put together. So we have initiated... I can use the old metaphor of painting the fourth bridge. When you get to one end, you go back and start again. Actually, that no longer works because they've invented new paint, which will last 50 years. However, yesterday morning, we launched Toga F version 9.2. Yesterday morning, we initiated the review cycle to move for the next 12-month period. At some stage, we will get to the point where we've got something which is substantially different. But we're moving to the point where we are recognising the fact that we do not have assignable resources and we are exploiting the willingness of people to work and contribute. Essentially, what we have is not just useful, but widely used in the market as is. Maybe one for you, Andrew. Are there any other standards of the open group cited within version 9.2? Yes, I think that was one of the things we did when we updated. For example, we've got a lot more references to the IT for IT reference architecture. That's one that springs to mind. I'm just trying to think what other ones there were explicitly mentioned. Can you think of any, Mike? Obviously, a lot of things are out in the guides now. Of course, there are. Yes, so things like SOA, that's out in its own guide. Of course, that one goes on. We were talking about adaptations to the content meta model. That has details of how you would adapt the meta model. We've got a lot of references to Archimate, but the detail about the relationship between the TOGA standard and Archimate is actually held in a series of companion guides. There are ongoing harmonisation activities. We would be looking for more guides to come out in those areas. That's where we're really looking for that sort of thing to be. Models to be developed and so on. Last question I have right now, and anyone's got a last minute one. I know we're going to hear more about this later when Brian Layle talks, but what are the most significant changes in the business architecture domain? Mike, is that one for you? In version nine of TOGAF, there were lots and lots of throwaway lines in the description of phase B. We talked about business capabilities. We talked about value chains. We talked about brief reference to operating models. It didn't mean a great deal because there was nothing behind it. Now there is because we've got a very active business architecture group within the architecture forum who are picking off these topics one by one. They have published a guide to business capabilities. They've published a guide to value streams. They're very close to publishing a guide on business models. They're working on that, and we've taken advantage of that to strengthen the descriptions. What is a value stream? What is the capability? How do you relate capabilities to value streams? Importantly, we put in information about how you actually relate this stuff to what the business actually wants to do. We had goals. We've now got an important concept called a course of action, which is what we're going to do to address a goal. A course of action means identifying how you build up the value, how you build up the ultimate value to stakeholders, to customers, a value stream, what business capabilities you need to enable that value stream. That's all built in now into the TOGAF standard and with the detail in the associated guides. As I said earlier, a very important step is actually stressing that the first versions of that stuff, the value stream diagram, the business capability descriptions, has to come before you get sign off for your architecture project because that's the context. It has to be done as part of the visioning. You don't leave that until you say, oh well, we're underway. Let's get some business architects in now. I have to be involved in the planning right up front. Those new concepts of course of action tie very well to the strategy part of the Archimate modelling language that we're talking with 301. Even though we didn't say explicitly ties with Archimate, obviously it does some of that, and some of it's gone a little bit ahead of Archimate because we've got value streams and stages and that will be coming soon in Archimate as well. It is all tying together. Great stuff. Thank you, gentlemen. Well, actually, there's a question just come in. There are still many differences between Archimate 3.0 and Toyota 9.2 in architecture type and meta model. Will they gradually converge in these two aspects? The answer is gradually converge. The question I have is, is it necessary for them to converge? The Togath Standard and Archimate were developed by different groups of people for different purposes. We do need to identify the implications of using the Togath Standard and Archimate together. We also need to recognise that they can be used separately. You don't have to use Archimate. We also have to recognise that the Togath Standard has an installed base. 65,000 individuals who've got Togath certification. Was that the figure you gave me yesterday, Andrew? 67,000. All right. That's close enough for me. What we don't need to do is to have artificial convergence that makes life difficult for 67,500 people if there is no real business benefit. That's the driver here. We're converging where we need to but not treating it as a religion. Thank you. General, we'll leave it there for questions. Just one last opportunity to plug the session this afternoon. The credentials. That's tomorrow afternoon. This afternoon we've got an architecture forum meeting. Welcome to come on. That is on credentials as well. The afternoon session today is for members particularly aimed at people who are accredited training providers because we believe that the Togath credentials programme offers a business opportunity and we'd like to engage people in the extension of the credentials programme. And then tomorrow afternoon we have training. Togath update training tomorrow afternoon which will lead for those people who are already Togath certified can actually be then entered into the essentials credential so it's a very lightweight assessment, very easy, gets you up to date with your knowledge and can get you one of our new shiny badges. That is very important because as Steve hinted earlier on of those, the people who've got Togath 9 certification there are those who did it in February 2009 and haven't come near Togath since and there are those who are actively taking effort to remain up to date. That credential enables you to put alongside your Togath 9 certification an indicator that you have taken the trouble to maintain your knowledge of Togath. Excellent. Denman, we'll leave it there. Thank you very much. Mike Lambert and Andrew Josie.