 So leding up to the break, I'm going to try to run through the open group is doing. And if I finish earlier that's a great thing because I'm going to run through it very quickly because you're going to get it to read and a lot of it is readable stuff. This is basically the forum highlights the forum road maps and where they are going. But to start with just a couple of things about where the open group is at the moment, we now have 488 organisations have signed memberships with us over 40 different countries that are listed there and we continue to get a new country every now and again every quarter. Thank you, Dawn. Safe travels. I've pressed the wrong one again, didn't I? I'll get this right in a minute. In 2014, these were just where the new membership agreements came from. So it's fairly well spread. That's just in 2014. 93 new membership agreements signed. Hopefully you can recognise your country on one of those lists. And they came in various forums. So you've got the Archimate Forum, Gay New Members, the Architecture Forum did. IT for IT was brand new in 2014, so obviously that was. The Open Trusted Technology Forum, OTTF. The Security Forum, the Young Group Security Forum, Gay New Members. And Open Platform, 3.0. The Convergence Platform. And then the Health Care Forum, the Vertical there. Gay New Members as did the other vertical, which is the Exploration Mining Metals and Minerals. The Open Group Phase Consortium gained a lot of new members. And we also had a number of Gold Memberships that took on a lot of those. And of course, Cap Gemini returned as a Platinum Member. So I'm going to run through the forums fairly quickly. There's a lot of information here, so I don't want to put you to sleep. The Archimate Forum, obviously the two key things there are the Archimate Specification. But also, I want to draw your attention to the tool, the Architool, which is a free open source tool that we are now sponsoring. And it is also the case that we've got the tools interoperability work going on that I'll get into. And Archie does that so that the idea is that if you start with the free tool, you can then move up to a commercial tool later. So here's the roadmap. They're working on Archimate 3. So in the first quarter of this year, this quarter, what they're working on is reviewing it, developing it, reviewing it, developing it. Harmonisation, constant work to bring Togaf and Archimate closer together. Work on that. Capability based planning is there. And the model exchange file format, that's the interoperability part. So that work is critical and they're hoping to finish that up this quarter. Also, there's white paper on enterprise risk and security modelling and analysis. And that fits in well with the security forum work on risk analysis, the risk framework, and all of the fair certification and relating Archimate and BPMN working together. There's a number of publications, the model exchange file format. Again, there's a snapshot of that, so that's worth taking a look at already. The risk and manageability. All of those things you can take a look at and go to the publication site when they're there. The architecture forum. The architecture forum has been struggling with what we're going to do to evolve Togaf to a next version. And it's an ongoing discussion. Whenever we have a standard, we try to improve it and develop it and so on. So far, Togaf 9 has got more than 40,000 certifications against it. There were 75,000 downloads of Togaf in 2014, over 166 different countries, and the book sales were about 11,000. So one of the critical things in evolving Togaf is making sure that we can move everyone along together. We've got to make sure that we preserve everyone's investment in architecture, so there's not going to be a revolution, it has to be an evolution. And that we are in so many countries means that there's a huge translation activity around the standard, around the examinations, around certification, we have to bring all that together. So this isn't something that's going to happen quickly, but it's something that's an ongoing discussion. Constantly looking at that, we don't know, we don't have a publication date for it. But we've recently surveyed more than 40,000 architects on, and it's a pretty decent survey. Has anyone seen it? Anyone here seen the survey? It went to AEA members, there's a few hands. If you want to see more about that, we've had more than 500 responses, and the results are going to be discussed this week in the architecture forum. So that'll be interesting. So there's a lot of things going on in the architecture forum around the evolution, whatever that is, or the next version release, and some of the parts. The idea is break it down into parts, perhaps, and then evolve the parts. There's a part two set of activities there. Can you read this? There's a thumbs up from the back. Capability improvement, a lot of things around capabilities. So tomorrow I'm going to talk about, from an open group CEO perspective, what I think about business architecture. In actual fact, it's called what I don't need from business architecture. Maybe what I do. There's a lot of things that people are talking about business architecture, and in fact a lot of it is going on here or already exists. So there's a number of publications, framework and archimate modelling language, right paper, so that will be something that you've also seen on the other one. Ecosystem is very important to TOGAF. So work on how that extends. It should be important to all of the standards, but in TOGAF it's been a key part of why it's been so successful. And then Norwegian glossary and a Danish glossary. We've got glossaries all over the place. DirectNet, not many people will know about DirectNet. I did mention it briefly talking to Dawn just now. So this is around mesh communications networks. So it's a task force that enables effective and affordable solutions through a collaborative government industry environment. And I'll let you read the rest. But as I said earlier, their standard has got the capability of linking airplanes that already fly around the world as nodes in an internet in the sky, in this waveform mesh network. It's got a lot of interest from the government here and a lot of participations, but it's one of those things that goes on quietly in the open group. Here's some of the things that they're working on. So developing... They've already got some standards out there in the waveform and the link layer. They've taken them on forwards. If you're interested in that kind of stuff, it's worth a look around their site. The Enterprise Management Forum has been very quiet lately, but they're working on manageability and manageability infrastructure that we can use. And it's not only specification standards, but also open source technologies. One thing that they worked on some years ago, and still is very popular, is Open Pegasus. Open Pegasus came around because we tried for years to have specifications that enabled interoperability between management systems. And we never got there because no one could agree on it. And another consortia, the DMTF, developed a specification, but it required an implementation in order to do it. And they were not able to do it under their charter, so we partnered with them and we hosted the Open Pegasus thing. And now interoperability using Open Pegasus is enabled. And that's been amazingly successful. So manageability is their big thing. The things that they're working on right now are there, the common manageability programming interface, and the OS management interface technical standard. The vertical exploration mining metals and minerals, which is the first organisation within the Open Group, did a very detailed reference architecture. If you want to look at what reference architectures look like and how detailed they are for an industry-wide architecture, it's certainly worth looking at their site. It may not be relevant to your industry, but it gives a lot of pointers of what that is and how that is. And we're quite interested in doing that for other industries as well. So here we've got mining organisations. Part of this was coming out of South Africa. The mining organisations there, Anglo-Platinum, were involved, Datamine, Rio Tinto is a member. And one of the challenges, of course, is that without standards their health and safety records were not that good. So one of these things is it reduces the risk and operational cost in the mines. One of the things that we had to do though was you're not just selling to the concept of these standards. It's not just going to the people that are developing the architectures or the IT guys. You've got to sell it to the mine manager. And the mine manager is only worried about two things as far as I can gather. How much he's got out of the ground that day and how many people have died, hopefully none, unless they go on strike, then you shoot them. And so we had to sell this idea to the mine managers and they got it, which is great. So this is what they're working on. They're working on, obviously, they have a very, very good reference architectural ready. So the information model they're working on, the applications map, updating the charter. And they got some publications coming out in the second and third quarters. The only group phase consortium. This is all about federal aviation. So anything that flies, whether it's manned, unmanned, got wings, hasn't got wings, got engines, doesn't have engines, anything that's got the dials in, the avionics in. The problem there was that the government was enforcing something called sequestration, which is cutting everyone's budgets because they got fed up of asking people to cut their budgets so they just said we're taking 15% off everything. So as a result of that, Government departments, and in this case it was led by Navair, we're looking at how they could actually save money. And with the avionics in aircraft, they're all hardwired together. They're all stuck together. So very expensive to maintain, update and integrate these things. Wouldn't it be great if we could have almost a plug and play, almost like a smartphone and have portability between these things. And we could actually save some money. So they got together with all of the vendors. There's about 86 member organisations of the phase consortium now. And they've developed a portability standard for this. And hopefully at some stage we'll have a certification programme as well. So they're looking at how they can develop those kind of things. Interesting stuff. And then these are the things that they're working on. Now the phase specifications, there's two levels of them really. What we publish and what I'm allowed to see are the things that are publicly available and able to be discussed globally. The members themselves have got much more detail and things that are covered by export control as well. So more of that. The conformance launch is on hold right now, largely due to concerns about liability and so on in the vendor organisations. And more processes, the technical environment and procurement. Again that's on hold because really what we want to procure against is certified product. Until we've got certified product there's nothing to procure. They're publications, they're quite prolific. So they're doing a lot in the first quarter and the second. The health care forum. Now here we're looking at bringing boundaries information flow to the health care industry. What they've worked on recently is commenting on a paper by the federal health authority around federal health information management, the FIM. And we've got a very good relationship with them now. And we've done a first round of submission to them that's been very, very well accepted. So we're having an impact in health care. And also we will look at reference architectures and standards and so on messaging. All of the things that the open group does and try and bring them together for the benefits of health care. Is there a roadmap? So there's the presentations to the FHA board and the film evaluation. And there you've got the publications coming forward. So the evaluation briefing was published at the end of last year. And we've got more coming through this year. IT for IT, brand new last year. We've got a whole presentation on that. If you'd like to know more about it, you can check with us. We've also got some members from IT for IT sitting right here. And I'm sure they would be delighted to fill you in more on that area. But really this is new to us. It's not new completely. They've been working on it for some time. Inspired by Carol Van Seeland at Shell. Who said that we are, we for a long time have been running IT for the business. But we now need to manage the business of IT. So for the customers, the IT for IT forum provides a vendor neutral place. So organisations like Shell and BP and the many others that have joined already. Have a place where they can gain knowledge, lead the development of the reference architecture for IT management product portfolio. I've shown one of the artifacts that they've got. There's a lot more that can be seen. And they would welcome other IT organisations to join with them. Because I'm sure that many of you have got the same problem. The thing is that they're vast organisations. You've all got large organisations with large amounts of IT assets. Whether you know all of the assets you have or not is a question. Whether you know the total cost of ownership of them is a question. Whether they're optimised to how they're operating is a question. How you can get best value from running the business of IT is a question. And this is something that this group is setting out to try and work on and solve. And they would welcome other organisations to join with them. The roadmap. So in this quarter we're looking at publishing white papers. A technical standard will start the development and more guides and work white papers. Very interesting area for our people. Open trusted technology forum. You heard me reference with Dawn some of the work on OTTF. And in fact the provider accreditation. So if you were head of a telco, head of supply chain in a telco. These are the sort of things that you would benefit from by mandating that any product supplied to you were accredited under the open trusted technology forum. The technology provider standard. So you get risk reduction and you get innovation enablement. The risk reduction comes through brand degradation, customer information loss of revenue, regulatory non-compliance. All of those things can be reduced. Innovation enablement because you've freed up time to focus on innovation because you've got this. You can differentiate your products. Drive revenue and have geographic flexibility in what you're doing. Their roadmap. So OTTPS has gone through the ISO or is going through the ISO process to be adopted by ISO. As so many of other other standards have, especially in the SOA area. And I can see Heather over there who's worked tirelessly on, on behalf of ISO on SOA. And those all got adopted and recently they've taken large parts of our cloud standards to include with the ISO standards. So now we're looking at a past submission for the provider standard and that will make it an international standard. So that will be kind of fun. Translation into simplified Chinese. The issue with China in this particular context is that I met with the, or I was taken to meet the folk that are here from the ICCC, the IT Security Certification Conformance Council. Which is a government agency in China. And we were talking through all of the standards and things that the open group does and mostly focusing on architecture and so on. And I happened to mention OTTPS. And the question I was asked was what impact would that have on the Chinese, on our Chinese market. And I misunderstood the question. I said, well, it could help some of your companies like Huawei export to the US. And they said, no, no, no, you don't understand. You've explained to us that the problem is that in the US, for example, there are problems where you have product that is delivered. That somewhere along a complex global supply chain, malware or counterfeit products are introduced. I said, yeah. But we have the same problem. So now we want to know how we can use that standard to certify products coming into China. Additional publications. All there. Open Platform 3.0. This is what some organisations call the Nexus. It's the convergence of social mobile cloud with data internet of things. Standard best practices and knowledge sharing. So it's bringing these things together. So it's kind of in and kind of out. It still retains its own work group. Cloud still does it. So this is a forum comprising a number of work groups that can take their own work and then come back. Bring it together. They have published a snapshot of what the standards might look like and what their thinking is. And we would welcome anyone to take a read of that and provide feedback to them. You don't have to be a member of that group to provide feedback. It's anyone can provide feedback to a snapshot. And we'd welcome that because we want to know if their thinking is on track. We're looking at a further snapshot coming up in this quarter. And a version of the standard perhaps in the third quarter. The top two here I mentioned to Dawn. These are the two standards that together can do for the internet of things or HTTP and HTML do for internet messaging. Pretty serious stuff. And then we've got this scenario that came out in the fourth quarter. UDF we're hoping to relaunch UDF in the third quarter. That's been reworked quite substantially. And then cloud computing governance big data and internet things life cycle. Dear old Unix which continues to be ever present. I can see a number of Unix certified products around the desk here. Charlie you've got one. Sally's got one. Lauren's got one. Anyone with an Apple laptop. It's got a Unix certified product that they're working on. So they're working on the base specification issue seven technical core agenda. And we've got some publications coming out there. Everyone talks about Linux which a lot of people are using. The problem I have with Linux is it's not as secure as Unix. It's a bigger footprint and it's not stable. The standard itself isn't stable. It's not a standard. It keeps changing. And the products themselves are all different versions. With Unix everyone conforms to the same specification. Which is 5000 odd APIs. You know what you're getting. You know that you can have portability. Real time embedded systems forum. This is largely focused on high assurance now. And what they're working on in all areas is areas around safety critical mission critical. And the people working in that are getting a lot of information education sharing of knowledge around all of this area. And they've got a quite a lot of high assurance things that they're working on. Mills multiple independent levels of security. They're working on updating those APIs. They're working to develop standards for high assurance common criteria. Multi-core update. Common application environment for dependability. And dependability through assurance. Now dependability through assurance I'm convinced is a way that you would architect in security. And risk mitigation from the outset. And it should be a real part of everyone's considerations when developing large complex systems. The security forum. This is a forum where vendors and customers can come together. And we've just picked out CISOs. Chief Information Security Officers. For them. There is a peer group opportunity. Networking. Focusing on risk management. Security architecture. Where they can steer the program. Demonstrate leadership. And it's a peer group on critical subject areas. The aim group security forum. Working on. TNSP I think stands for Tograff next security. Or something. And there's no such thing as Tograff next by the way. But it's all related to integrating more security. Getting tighter security into the Tograff guidance. And at the bottom we've got more security and risk and risk certification. And then. Carrying on risk certification. X-DAS is. A very old standard. For distributed audit services I believe. India. A lot of activity going on with the. The organizations in India. And. ISM three. Which is the. The way of identifying the vulnerabilities in your organization. And. Having a framework for addressing those vulnerabilities. You know that's that's a two part problem. Many organizations can understand vulnerabilities. But actually having a framework that takes you all the way through to. Addressing them and. Eliminating them is the other part. Data security principle security automation. Platform. And here's some of their publications. I think I finished. That's a relief. I think I finished. That's a relief wasn't it.