 So Andres is the vice president and CTO for IBM US Federal and responsible for IBM's industry solution technology strategy In support of the US federal customer Andres has been appointed an IBM distinguished engineer Some time ago now. Yeah, he represents the IBM software group on the governing board of the open group and his vice chair of the open trusted technology forum, and he also chairs the open CA standard program and Welcome Andres. Let's have a have a seat You meant the open trusted technology provider standard OTTF the well the forum your chair your vice chair of the forum on here. I'm vice chair of the open CA You open CA. Yes, the open CA standard. Yeah, okay. Well, take a take a seat I just don't want to have Peter get you know come off come off. I haven't get upset No, no, okay. So the reason the reason I've asked Andres up here and and to kick off the theme for this morning is Andres has has Raised several times over the last few meetings at the governing board of the open group We should be considering doing executable standards in the open group It we do we do great stuff with the way we do standards, but there are other there are other things going on outside and We should be thinking about how that relates to the open groups approach to things and what we should do so Can you just introduce the concept without going into? Specific details maybe but what's the idea of when you when you brought this to us and said okay? There's other stuff going on other ways of doing standards basically based on code What's the concept? well, the concept of executable standards is that we've gone through an evolution of You know are thinking about how to standardize over a 20 25 year period maybe even a little longer and and today you're seeing this convergence between The creation of open source and and standardization to create a foundation for innovation Whereas previously we really thought about standardization from a really hardcore Paper or specification perspective at least that's how we started off right. Yeah. Yeah, and I mean different types of standards and some of them have verification programs that go along with them and testing some don't so What does the executable approach bring that the the more traditional approach there call them paper standards for one of a better Description well, maybe a little history might not be a bad idea. So when we first started with standards we we talked about standardization and Standards really started You know if we think about the open group with with the open group and the and the two bodies that you know were the Constituted the open group X open and the open applications. Oh, it's that oh, it's that So what were they trying to achieve? They were trying to achieve interoperability Right and create a set of technologies that you could ensure interoperability and standardization across the industry and it was really based on a Very concerted after the industry at that time to write the specification and write the standard In fact, if we really think about this the we started off with executable standards as a concept We kind of got away from that if you think about Korba Mm-hmm. That was really more of a paper chase And Korba ended up not being so successful because we would sit down. We would spend hours and hours You know working with some of the most premier minds in the industry coming up with a specification And everybody would go off in their own corner and go implement And they would come back and it really wouldn't interoperate in the way that we thought it would so we really Realized that our original approach, which was the foundation for what we did here in the open group was the right approach and then you see that and the convergence of or the the Emergence shall I say of open source? and You then began to see this idea of well if we created a foundation a code base that can be a foundation for innovation we can ensure interoperability and Standardization, you know becomes more effective over a period of time. So yes, you definitely have specifications Especially for API's in their operability. You do have certifications especially to ensure that The integrity of interoperability and the implementations, but then you can actually layer on Your value-added capabilities as a vendor or a customer On on these interoperability layers based on open source and you've got a real Environment that has a tremendous amount of support in the industry Everybody understands that piece of code because it's open source And we all understand that it's where the the rough edges and the and the value is in the implementation and a lot more value and and time to market is decreased So effectively the code the code provides the platform From which innovation occurs and and it's self-documenting in a way, right? So you don't have to write the light, you know the the mini books on on the specification of standard itself The code is the standard. So we kind of gone from You know standardizing to innovate To innovation to standardization So we were creating code that becomes the standard becomes the foundation for that innovation So in and so this is things like examples like open-stack cloud foundry things like that that are They're providing a platform Now I know there's some dispute as to whether they're standards or not But yeah, it's that kind of thing that you're talking about We're forgetting that we had a few charts too, but we don't know if they want to if we want to show Why don't we why don't we go forward? Yeah, so, you know, that's a really great point. So we have a just a huge number of Foundations and universities and vendors that are working together To create, you know, the new cloud platforms and the new tools and DevOps platforms that are Going to be important for the future execution environment And I think it's really important for us to to be part of that and to realize that when we come up with a concept We need to potentially ground that in connectivity to some of these other groups or Implement our own open source so it becomes a foundation for innovation Okay, so in an open group in open groups history, we've done we've been involved in things like Plug fests and unplugged fests before is is that a similar thing or is this Is this different in some way that plug fester really, you know under the covers gorilla marketing What it does is it gets people to you know play with technology that somebody else came up with And extend it and it gets the millenials interested in it What's really different, you know in today's world with executable standards is that you are trying to achieve some level of interoperability some in you know a piece of innovation and you're coming up with a common code base And and that common code base defines the layer on which you actually, you know continue to add value and New ideas that aren't part of that original but extend it and add value to it Maybe even are somewhat, you know Kind of what we call if you hit the next chart Open plus right so you can you know you can be your own You know open source vendor if you want to and you know a symbol open source And that can be challenging by itself, you know because you're not really focusing on your core competency or you can go proprietary Which has its own, you know upside and downside You know one of them being vendor lock-in or you can go this route of open plus where you're actually using the open source and the standardization to create interoperability between different implementations of of the standard and using that foundational code base and different vendors and different organizations can extend it and you can Use it in any way that you would like and then sometimes these extensions become part of the standard I love the vendor lock-in assured. It's all it's like a certification program, isn't it? Still have you can still have a certification program. So, you know certifications are done it to ensure that people are are Following the standard or using it or know how to use it in some cases and that ensures interoperability, too So when it came up at the the governing board that the the initial area that we thought Was was most most natural fit For trying this out in the open group was the open platform 3.0 forum. Yeah, they're looking at building a Building what the third platform should be and defining that and that's that's where we've kind of put our toes in the water On it so far. Yeah. Yeah, if you go to next chart a Lot of those standards are are really focused on creating that whole software-defined data center and You know, you can't do that unless you actually ensure interoperability. So that's you know, a large focus of the industry today around standardization And this is essentially the sweet spot for open platform 3 And some of the work that we're doing there And I think we have a fantastic opportunity to make an impact in the industry in this particular area Are there any are there any areas that you've heard the forum discussing that are of of particular interest or where this this approach of Developing the standard the executable standards would would lend themselves nicely or most obviously Yeah, the Internet of Things is a wide open area. We actually have a fairly decent Foundation of standardization here in the open group and And you know, we're an authority in this area. I think to a certain degree, right? It's a growing area. We I think a little more energy in the Internet of Things would be fantastic And it would be a great place to add value there big data And you know big big data management the interoperability layer That the team has been talking about The other big one to me is a cloud brokering You know, how do you actually manage? You're definitely going to be Integrating multiple cloud providers. You're not going to just send ride one cloud provider horse Whether it be infrastructure or platform as a service and you're going to have to have you know That brokering layer that allows you to actually, you know interoperate with these Platforms some standardization there would be good because customers are beginning to ask about that layer Okay, okay So as we do this what have we got to look out for have where have you seen it successful and less successful or what are the kind of Things that we have to ensure to make it mean one of the one of the initial things I've heard is that maybe this is a different set of individuals. Yeah, then Typically participate in an open group Meeting and an open group. There's a place for everybody, right? But if you hit the next chart You know if you look at these Current standardization efforts that are foundation for innovation based on open source You got them, you know in pretty much every single category around where technology is heading today and You have to be able to code I think you have to understand the technology Because really you're writing the standard by writing some code and implementation So proof of concepts are going to be really important The other thing is that if we take some of this work that's already been done We can't just simply start from scratch. That's not what I'm suggesting, right? Let's take some of this Some of our major members and and build on top of them and and use them You know because that's really what standardization is about it's about a layering of different technologies to advance Innovation you don't simply start from scratch every time. You don't rebuild the operating system, right? No, you obviously use You know what you've got out there to create something new and that's really what we got to do here So we're gonna, you know, you know look to our major Board members and vendors to be able to help facilitate The donation of some of these environments on which we can actually build some of these these new capabilities and interoperability specifications Yeah So we as I say we're gonna well we we have started putting our toes in the water in the open platform 3.0 forum and We'll see how that goes. There may be other Other parts of the open group other forums where this kind of approach might be attractive to so Those of you in the room who are members Do think about whether whether this lends itself to to your particular area of interest or what it is that we might do so from We will we will you know, this is happening out there and and if this can help us Initially in open platform 3.0 and maybe in other places then There's something worth having a yeah, even if we just think of the open group I mean, and this is not true certainly But if we just think of the open group as toga for you know, some people do because they don't really know understand what we do We still need to pay attention You know to what it means to implement enterprise architecture in the context of these new technologies and techniques but that aside we have a vast number of You know expertise but also forums that should also be looking to you know, bring in new Millennial blood that would be you know interested in in doing the foundational coding for some of these ideas that we're coming up with and And that that will grow our membership and grow our Opportunities right as we continue to influence these areas, and I think that you know our our success in the past Is is an indicator of how important it is for us to be involved in this current, you know a set of initiatives Yeah, I don't know you you mentioned enterprise architecture specifically and to what extent Does an enterprise architect need to know about these things and the answer is almost certainly yes They do one of the one of the things that we've we've heard a lot of a lot about is what does This kind of approach mean for the more structured approach that enterprise architecture requires and you know the The realization I think in the acceptance that that architects need to know About these about these technologies and how they might go about integrating them and The use of standards when you're putting things together like that is is going to be key so the other thing too is that the industry is really looking to take some of these enterprise architecture best practices and codify them, you know in code and Make them And enable them to be Automated so that you don't simply have to do all of the work by hand And that the expertise lives in some of the code and that allows you to actually then step up You know it's kind of like that innovation piece that we talked about and and focus on something new So it for it is another great place Automation yeah, where we could take that expertise. I think we've got the expertise We've got it all codified very well, but now we actually have to distill it into a layer that We can reuse across the vendor and customer World in order to actually automate the implementation of that expertise Well, I hope that provides a little intro to to what we're what we're talking about We didn't plan on opening up for for questions necessarily on this But if anyone had a burning one we'd be happy to to take it, but if not, I think we've got a Panel session that Dave's going to lead going to lead shortly. So we'd probably leave it there for now. So Thank you for your attention and and on this. Thank you for sharing it. Absolutely