 Welcome everybody. I'm Chris Harding, the forum director for Open Platform 3.0 with the Open Group. The Open Group is a vendor-neutral consortium that develops standards and best practices and is proud to present this webinar on SMAC and Open Platform 3.0. SMAC has become a recognized term for some new technologies, social, mobile, analytics and cloud. And Open Platform 3.0 is an open group initiative to help enterprises make use of these and other emerging technologies. We have three experts who will be presenting today. I will not be presenting content, but will be moderating the panel discussion. These are Aravind Ajad from WIPRO, Bhupesh Naik from Infotis and Gautam Bhatt from IBM. And they will be joined for the panel discussion by Mark Skelton, who is a professor at Warwick University in the UK and has been heavily involved, particularly in the business-related aspects of our Open Platform 3.0 work. Aravind and Bhupesh have not been involved in that work. They are independent thought leaders who will be presenting their ideas on how the industry is developing in this area. Generally, Gautam has been involved and is involved in the Open Platform 3.0 forum, and he will be talking about what we are doing to develop the platform. What is Open Platform 3.0? It is not a product, it is a standard platform that will help enterprises to use not only social, mobile, analytics and cloud, but also other emerging technologies, and particularly the internet of things. And it does not yet exist. It is in process of being defined by the Open Group, and Gautam will be talking more about that. Its purpose, however, is to help enterprises take advantage of these wonderful new technologies that everybody is talking about. So to say more about these technologies and their effect, I will hand over to the first of our three presenters, Aravind. So perhaps we can move to his next, his first slide. Okay, thanks Chris. Good morning everybody who is joining the webinar. My name is Aravind Azhar. I'm a lead architect and practice leader in emerging technologies at Vipro. So next few slides I'm going to cover what is the impact of SMAC and how do we look beyond the obvious within SMAC to understand the real impact of SMAC on the application architecture. So if you look at the application evolution so far, there always has been an influence of technology change on the application. Each computing error, as you can see in the diagram here, is defined by a technology disruption, and then that has resulted in how the applications are architected. So one of the things that currently we are seeing as we are calling it a SMAC, the social mobility analytics and flow, is one such computing error which is actually currently happening, which would have a lot of influence on how the applications are architected. So what is that influence or impact? If we have the question ourselves, that is what I'm going to, whether I'm trying to cover in the next few slides. So the most common way to look at impact of anything is to discuss about it and then look at various things. But most often the case, what I've seen with respect to SMAC is that there has been a lot of hype, buzzwords, so the discussion stops at the obvious. It doesn't go beyond the obvious. It doesn't go beyond those key words, social mobility, etc. So how do we move beyond the obvious? The real impact, in my view, is the long-term impact. The impact of not the big words, but the various ways and means in which this impact is trickling down in two applications is what I see is the ratio of the impact. So the real impact, the way I see it, is the user experience, the user thinking, the automation, the agility, which the SMAC brings to the application and the station. How I see the impact is coming. How I see the SMAC is influencing the application. So the first one I see is that not technology, but the influence of SMAC goes beyond technology, especially the social computing and the consumer internet that has influenced significantly what users expect from applications. So this is one of the manifestations of how SMAC is influencing the application architecture. So now the users expect that the applications are always on. They expect that the applications are available on all the screens they are using, whether it is a mobile phone or it's a personal computer or a tablet and so on. So users expect that the applications are very intuitive. The users expect that the applications are provided a natural means of interaction. On top of all, the users expect that the applications understand who the user is, what the intent of the user is using the application and what environment in which the user is accessing the application. In short, the users expect that the applications behave contextually to their needs. So this is one of the key manifestations how I see that user behavior is influencing the application architecture because of SMAC. The second such manifestation I see is the technology and how it is used. Traditions of technology is always a set of course monolithic technology stacks that are actually meant to solve different kinds of problems to be used in a vest style scenario. But the new thinking is that use the right technology for the use case. The technologies are no longer monolithic but they are agile, lightweight and then expected that we use best of the breed and then bring them together as opposed to have a monolithic stack. So these technologies you see these are driven by communities. These are coming from the various open source organizations and then these are adapted by the product vendors. So this is a thinking I call polyglot thinking. This has a tremendous impact on how the applications are architected. So how do I see the future applications? What kind of architectures that we can expect in future applications? So I define them by three characteristics. One is the client awareness that is about understanding the devices in which the applications are accessed, understanding the form factors, being able to deliver capabilities natively to the clients using these applications. The second chapter is the idea of context awareness. This is about understanding the intent of the user, understanding the environment in which the applications are used, understanding the history, how the users have interacted in the past and then what they have done area and then behave accordingly. The third characteristic I see which is the most important one is what I call intelligence. The application has to be scaled automatically. They have to heal by themselves. They are dynamic, agile and self-configurable. So what is needed to deliver this kind of future application architectures in this era of, you know, smack and beyond? What makes these future application architectures? So I define six essential capabilities that are required to deliver such future application architectures. The first one is continuous availability, continuously available architectures which are always available, listening always. Smarter clients are delivering capabilities and then delivering rich experience to the user, close to the user. Contextual delivery which we just discussed is about how do we deliver relevant information and relevant services by understanding the context of the user. Elastic architecture, scaling the applications as needed and be elastic and be efficient in handling resources. Adaptive process which is basically having the ability to have highest flexibility within the process and being agile and then ability to change these processes as needed. And then intelligence and data sizes which is the most important of all is about delivering intelligence from the data, wherever the data is, whenever we need such intelligence. So all these capabilities if we look at independent, each of these capabilities require tremendous amounts of experience and thinking in order to deliver such capabilities within applications. So is it fair to expect that, you know, every application will be able to bring such capabilities, you know, to the table probably not. So that's where the platform thinking comes in. Platform thinking is all about how do we deliver these capabilities in a standardized way so that the applications can leverage these capabilities and deliver the future application architectures. So that ends my talk. Over to you, Bhupesh. Thank you. Thank you, Arvind and thank you for that great discussion as well. My name is Bhupesh Naik and I'm from the process and from the digital process integration unit and work as a lead architect within the organization. After Arvind has taken you through the application impact on the kind of SMAC influence that has been brought on, what I will discuss is a set of ideas and a set of influence points that in Internet of Things would actually see where the platform 3.0 also converge. We just have a quick look at what and where these social mobility analytics and clouds come in. We all know that there is a certain set of innovations happen within the enterprise while there is a certain set of innovations do happen for the consumers as well in the industry. And there is a there is a convergent point here where we see that the enterprise are kind of pressured or kind of influence to use the consumer innovation capabilities to drive their enterprises in the way they work in the way they operate. And this is where we see a lot of digital convergence coming into picture where we see a lot of enterprise app, you know enterprise organizations going towards the consumer great ecosystem wherein we see that the social mobility analytics of cloud, you know, which are more closer to the consumer driven, you know, innovations are being considered and are kind of used in certain enterprise to deliver their own operations to deliver new business model. Having said that, there is a particular set of consumer, you know, focus that has been coming up. We need to have again a small look at what the consumer focus does really mean. When we say consumers, it is not a mean that it has only detailed customers. It can be employees, your staff, your field officers and your trading partners, whoever are your touch points inside your business and who are kind of influencing your profitability. Now, each of the consumers does really interact with the business to experience a set of operations, you know, that can be, you know, doing some actions, collaborating, analyzing, but finally, actually having to decide on set of actions that a consumer will take, you know, while interacting with a set of business capability. Now, this experience obviously comes through interactions that can be through visual sense, voice, contextual capabilities and these interactions are to be enabled via certain set of platforms which can be through digital information enabled platforms, analytics platforms and these platforms are then requiring a set of technology to kind of enable them through the top environment that I'm talking about. So as you see that it is more of a consumer focus that we bring in and because we are influencing the experiences on the consumers, we are kind of trying to converse the consumer and the enterprise innovations together to meet at a point where the experiences are transformed and the business innovations does really continue. Having said that, it is very important that we also look at when we speak about social mobility analytics and cloud in silos, we do understand that they have a particular set of importance in the ecosystem that we are talking about. But if you look at the Internet of everything, you know, I call it everything because, you know, there is not a limit to a thing that we talk about. We have physical entities, you know, which are assets which doesn't not exactly a machine, but we have people collaborating, you have machine, you know, interacting with people and that is through a set of networks which are again interoperable. For example, you may have 3D available or 4G available or it can be a Wi-Fi and then you have a set of gateways that are basically built upon using these different objects, you know, interacting and then these gateways are particularly a vertical set of gateways which are, you know, related to a certain set of, you know, functional capabilities which is energy transport medical. Just to give you an example that AD&D does really have come up with a digital life ecosystem which is more on the home security and it is based on the similar, you know, principles of how your different things, you know, different collaboration happens using social mobility analytics and clouds. For example, you may have a local analytics where a machine is interacting with, you know, the person on a variable device to interact with the person who is, you know, who is kind of giving a set of instructions to it and it has a local analytics to detect, process, gather and act upon it and then feedback to the, you know, the person or the user who is using it. So analytics would be, you know, only present in this particular ecosystem. Cloud will be only present to create on-demand gateways or create those applications and social will be only present for the people to interact and kind of interact not just with the people to people but also people to machine. So it is not, and this interaction is what the open platform will create a standard across and create a view in terms of how these interactions does really happen in an ecosystem viewpoint. So it is very key to understand that social mobility analytics and cloud, though they are key terms and can be individually be enabled and used, but it is more important that the conversions are more stronger and give result into a very stronger ecosystem like the net of everything. Having said that, it is also important to look at the influence on the enterprise architecture that we bring in. So while we know that the enterprise architecture does have a certain set of views that we generally follow, which is information, the process, the rules, integration, security, it is giving us a challenge and that that is something that the platform 3.0 will also address is that when cloud social mobility big data analytics and only channel experiences do come in, how are these particular viewpoints are going to change and impact the stakeholder viewpoints, right? So that is more important for us, while we say that we are going to use these technologies, while we say that we are going to use a conversion ecosystem, it is important to kind of give also a perspective to the different stakeholders of how a particular set of traditional viewpoints are going to change in the newer capabilities that we bring in. With that, I think I will close my session. Okay, thank you very much Chris, Arvind and Bhupesh for setting up a firm foundation on what SMAC is all about and its correlation with Open Platform 3.0. I believe that everyone can hear me really well. So keeping this in mind on what SMAC is and how that is part of Open Platform 3.0 as we saw in one of the preliminary slides. For the next few minutes, we will look into the work that has been done so far by the work streaming the open group in the context of Open Platform 3.0. So the work began with an identification and preparation of a list of business use cases as revealed on slide number 16. We see a total of 22 use cases which were developed throughout the study of the platform Open Platform 3.0. These 22 use cases spans across multiple industries, business processes, technologies and business domains with their sole intent to investigate and analyze the requirement characteristics of what an Open Platform 3.0 should be all about. On the right-hand side of the slide, we have provided a white paper link just led by Mark Scurton. It's part of the Open Group project and this is published by Open Group last month around 20th of March. So it covers every minor details of all the 22 use cases that we have been showing up on slide number 16. And a snippet of one of those use cases we would as well see in one of the subsequent slides as we proceed. So you might be wondering on what are the different components that are going to do and what is the relevance that each of it has in this context. So the systems that have been shown up on slide number 17 are derived from the use cases, the 22 use cases that we spoke of in the previous slide. And as you know in an object oriented paradigm, the interesting components are termed as objects and in order to link that concept, this diagram shows objects of different kind as you see. So we have the human objects, we have the utility objects, we have the moving objects and so on. So this particular slide 17 is to show the communication that flows among the different technologies in a business driven world with the help of 22 use cases. So the use cases have been further subdivided into what we call as a functional and non-functional aspect. We have the industry sectors to which it belongs to. And in this case we are talking about healthcare in specific and we are also covering on what are the functionalities served by this use case. So in this case, this use case is serving a functionality related to monitoring the health condition of the patient. The next one is on what are the business values derived out of it. And in this case it's all about improving the quality of life of the patient is what has been derived from this use case. So the next key aspect was with respect to understanding what are the business functions which helps drive the business functionality that we just looked into a while back. And finally about the actors who enable or influence the flow of information. And again from this use case we have categorized the actors into two. One is human actors and another one is machine actors. So again to go back to the first slide that we spoke of as part of the session in the form of the white paper. So the white paper has details about each of these use cases and slide number 80 is just an impact of what we have actually covered in detail in the white paper. So as the last while deriving the use cases, we ensure that we work on the raw data, the construct of the raw data as such and list the technologies from each of these use cases. So we were looking at that from an enterprise architecture standpoint, business standpoint and then derived from a technology viewpoint on how the raw data and the business use cases will proceed. Then we looked into a list of the standards collected which were circulated to each of those technologies. For example, we have in case of healthcare, we know that we have a medical data of the technologies and that is based on several of the standards such as the ICD-10 or 11 or the health level 7, which is from an independent organization and so on. So we respected the standards associated with each of the technologies which should compare to open platform 3 and then we are trying to correlate on how that has an impact on deriving an open platform 3.0 as an architecture or a standard in itself. And finally we mapped the technologies to each of the business use cases and that was the final step as part of the overall study. So as of now, what has been done so far is a musical component compared to the perceived goal or vision of open platform 3.0. And on slide number 19, if you can take a look at, it highlights the major activities which are still in pipeline. So the continued effort on further breaking up and analyzing the use cases by setting up the individual workgroups for cloud, Internet of Things, mobile and social in the context of ROGAP as an enterprise architecture is being seriously worked upon at this point. As we know that any project activity is incomplete without work products or deliverables. So with respect to what we have been talking about SMAC and open platform 3.0, the workgroup and the open group has a few deliverables as described on slide number 20. So one of them was the white paper that we spoke of a couple of times. The second one is with respect to the snapshot release that is still under preparation and due for release sometime next month. And what does the snapshot contain? It contains what has been thought about as a platform 3.0, I mean, just a standpoint based on the analysis of use cases. And the representation of snapshots is being performed using an archimage language, which again belongs to the open group. And followed by this we will have several other snapshots being published as we progress and as our group gets more and more matured with what open platform 3.0 should be all about. And finally, we can all expect a standard for standard release of open platform 3.0 sometime in the early 2015. So that is in a nutshell on what has been done in the workgroup at the open group and this is what I wanted to cover as part of the session. And I believe I can hand over the call back to Chris and thank you very much. Okay, thanks very much. So we now move to the Q&A session and we have a number of questions coming in. I think probably the first one which I will ask all the presenters and also Mark to comment on is a fairly crucial one. And I suspect we may get slightly different answers from certain different people because the definition of open platform 3.0 is still being worked out. But what does open platform 3.0 mean? What is open platform 3.0? So can we start with that one? I'm sure Chris, thanks. Very good presentation and very interesting. Yeah, it's a digital platform for what we call digital ecosystems. So today we have enterprise architecture and we have SMAC which is some social mobility cloud and big data technologies. And what we're finding today is that the combination of those four technologies plus the internet of things and other technologies now are creating new value. And the challenge of putting together a SMAC solution which may be driven by mobility requirements or through social engineering requirements or through data analytic requirements is having a joined up story. And the critical thing about the open platform 3.0 initiative is to create a joined up value proposition as Gutan was saying with the use cases. We talk about vertical ecosystems of vertical supply chains of joining up the end to end supply of say automotive products or retail products using these technologies or a horizontal digital value chain or digital ecosystem where you have say a home which is made up of buildings, rooms, different consumer and products, TV, digital radio or carpets or chairs or food and other things. And what we're talking about now is the next generation of enterprise architecture moving into ecosystem architecture and the open platform 3.0 is an architecture initiative to help you drive that value. The way I look at it earlier in my slide I've talked about platform thinking, right. So I strongly feel that the platform thinking is key to deliver what SMAC promised and what is going to come beyond SMAC. So I think that open platform 3.0 will be one such platform or maybe the platform which can provide such capabilities to the applications. This includes standards, this includes standardization, this includes interoperability and many such capabilities which can be helping application architectures to deliver the capabilities which I think SMAC offered today. We have a long way to go here on the open platform and the key aspect that obviously all of the audiences will be looking at open platform is from my side as well as the convergence standards that we bring in similar to what Mark has mentioned. When we talk about the new capabilities like social mobility analytics in the cloud and how they interact each other to kind of give and derive a particular function solution or an ecosystem and standards of how this ecosystem will work in this particular convergent environment is, you know, we would see the lot coming in from the platform 3.0 discussions for them. Okay, yeah, thank you very much Chris and yes, this is the interesting topic and also on the fact that we have been looking at the traditional IT world infrastructure which exists even now most of the environments. And we are also looking from the platform 3 on how would that be. So if you look at the traditional world and if you make comparative study between what has been existing and what has been envisioned, I think that would bridge a very good gap on where we want to actually go. So in the past or even now most of the times we see that the environment that we work on is basically the infrastructure. And as maybe you say that it has a traditional world of, you know, the storage world, it has a modern system in place and it has education and learning and executed and we serve to the business functionality. But as we see with the major four technologies coming to play in the form of SMAC, we see that the environment has a mixture of all these different technologies residing or coexisting simultaneously, which means that at some point in time, there should be a very good communication or flow of information that has to happen if we have to deal with this network of forces. And this is something which you can reveal in the white paper that he spoke of. So this platform 3 is something which would address the growing needs of the technology advancement and how these four major technologies and others would coexist in an environment and how to deal with that. So that is about in a nutshell. And again on the snapshot I searched, yes, it talks about the various aspects that we have discussed in this webinar so far. And it also contains what is being thought about at this point and where this is going to head to us. So I think that is exactly what I wanted to cover as part of this. So that was a fairly fundamental question. And I think the answer is the definition of open platform 3.0 is emerging and you've heard the number of the considerations as to what it should look like and what it is looking like. I'm going to, if I may, not go to the specific questions of what it will contain at this point. But I would like to go to a question from Ceri, which is another very basic question. The key success factors to stick all different technology to work seamlessly together. So what do we think are the key factors that will make it all work? And maybe I can ask people in replying to this, perhaps to comment specifically on something that Paul Simmons raised in the chat, which is the question of identity. As something that people's identity needing to be understood by components of the platform. So I think it's a it's a it's a it's a very good question because as what Mark described earlier as well that when we talk about the digital ecosystems coming up and obviously you it is more focused on the consumer experiences. We talk about the evolution of innovations is from the consumers for a certain set of capabilities in debate right now. So it does really is important that the digital native as we call it right for the consumers, you know, and and their digital identity being a focused, you know, and focused area in this ecosystem. And the way it works is today, if I, you know, example, if I have an identity within a Facebook social ecosystem, I do have an identity within LinkedIn, and I do have an identity within multiple others so far. So this identity also has a certain set of attributes attached to it, which is my hobby is what I do what my transactions are. You know how do I, you know, behave in a particular situation for for a responses that I given what my dates are, and all of these digital, you know, profile attributes and the native digital native attributes and the characteristics will drive a lot of this ecosystem experiences for the consumer. And obviously it is key in a way that the profiles distributed profiles of digital native will have to kind of convert at a point where it can be used and available for different, you know, application capabilities as well as position capabilities that we built in to give a more focused experiences as we as we see in my slide of the pyramid that we have, you know, seen is that the experiences that we drive in terms of how the consumer really decides act and see is through the complete digital ecosystems and yes, the digital native, you know, capability will really be a key to be a success factor in this particular ecosystem. Yeah, Chris is smart. I think just very quickly, I think in terms of individual identity, what I'm finding with other research projects is the need for privacy and trust and security over the over the technologies, not just mobile or social. And I think a critical success factor is having a strong method for calibrating or measuring your individual value or individual security for a service, which could be from these from these different systems. And so I would see an open platform three providing a way of federated identity, not open ID or Facebook ID or one of those is just part of the elements but actually orchestrating or choreographing your identity between different participants in the ecosystem. So there's an efficiency and a value for the individual for the platform provider, you know, Amazon or IBM or HP or Oracle, so on and so forth, and, and the individual. And so there's today, there's many IDs, many accounts you have to log into. And I think this whole there is security for the individual needs to be really sorted out. So very critical point a very good point back to you. My answer to said he was no question is that, you know, the technology is working together requires, you know, that you know the bluing happens at different levels. One is, you know, a technology working with another technology in a seamless way. That's where I was talking earlier about political thinking of technology. So that's I think that is a common representation of you know how exchange how do we exchange information across technologies. So this is where I think a lot of focus on you know what could be the common way of representing information that can be exchanged between these various technologies. So Jason being one and excellent being, you know, the existing popular, you know, format that is out there already. So I think that is one level where I see a common format which is playing a role which can actually bind these technologies together. At the next level, I see even the location of services that happen across these technologies. That's where I think open API comes in. That's where I think there is some amount of standardization on how these APIs are defined and what could be the model behind these APIs which help these technologies to, you know, work with each other. That's where that's coming. So the other angle that I see to this is that, you know, not always the things will be, you know, a technology calling one another technology and so on so forth. It can go more than that. So the other way I see that, you know, there is an ability that's where I see the platform coming in as in how these technologies work together to a common bus sort of, you know, which can actually bring and do these technologies together. So I think the answer to your question study is that, you know, you had already covered some of the answers, but I think above and beyond that I see this a common way of representing information. And then the platform playing the role which can actually bring these technologies together. Yeah. So it's basically a continuation of what we heard from Mark and Dukesh Narvind is basically the mode of communication and there are already standards which have been defined and each of those standards are something which may be specific to an industry. And what we're talking about is how this open platform can address the challenging situation where in we have some data flowing in from across industries, across technologies, across actors and still maintain a common language which can be considered through the flow of event or the data from its source of origination until it reaches the back end. So that is something which is a challenging situation and which is being partly addressed in the snapshot which is being released later in the month of April. And but again that's not the end of it means and there are further studies going on in order to see what really what really is that we are going to emission and if that's exactly what we intend to achieve at the end of the day. Okay, thanks. Thanks, Gautam. And I like to move to a question from Pradeep. How do you see enterprises using consuming up platform 3.0? Is there a model defined for this so far? And perhaps when answering that we might think specifically because there's a question asked by Tapan relating to multi channel banking, omnichannel banking, whether the platform will enable new models of take up in particular industries and particularly perhaps in the banking industry. So that's a big question about the take up of the platform. Yeah, please. Maybe if you can just break this question into two, if you can repeat the first part of it please. Maybe that would be easy to start off with. I think I just lost on the first part of the question. Let's break it into two and the fundamental question is how do you see enterprises using slash consume open platform 3.0? Is there a model defined so far? So the question, the basic question is about the use of the platform. Yeah, it's a difference of understanding building a analytics database with a portal on the front of it, which I see a lot of the consultants is selling to clients today or selling an orchestration of hardware story or a social media mobile service. These are just point solutions and they are creating islands of value in large and small enterprises. I think the way that the open platform 3 will create a new type of service for customers is it will answer the customer value. What is the sort of service they need for their jobs? What do they need to do every day through mobile or social? And it's creating this digital value consuming it through a set of services which are geared towards what the individual, the consumer wants. I think it's the difference as you saw with some of the slides earlier. And so it's a different mindset. It's not creating a solution as we may do in the past but creating a business system value with a marketplace and a continuous improvement cycle, which is different. So I would argue that we're not there yet. And I think with the open platform 3, we will create a new type of consumer interface, an open API, a kind of new marketplace, a new set of services which are, as Chris was saying earlier, just to finish off with the security services which today are fragmented. This will be bringing this together into the next generation of integrated services. Back to you. Yeah, Chris, just to add on to what Mark just stated out, that with respect to these particular aspects, we have the model approach in the sense that we have this cloud, mobile, social, and internet of things, pretty wide, dispersed technologies in itself. They still exist and there is an architecture around each of these. That is one aspect of it. If you look at individual component perspective. And secondly, we have for each of those industries, we have an industry-specific framework or an enterprise architecture. So now the question that is being asked is pretty interesting. The question, if I'm not wrong, is whether there is a standard architecture which defines or covers all of these technologies into one under the umbrella of open platform 3.0. So in continuation to what Mark stated, that's something which needs to be worked upon. Although we have architecture existing in place for an industry, we have architecture for each of the technologies as such, which varies from one extremity to other extremities. But the only major challenge is how do we develop an architecture around all of these that we can claim as an open platform 3.0. And as we saw in one of those slides, this is something which is the next level of study that the open group workstream is involved in. So I could see the growth or the perspective of open platform 3.0 from the Togess aspect of enterprise framework. Sorry, it's Mark Skelton again. I certainly agree that we're doing more work. And I think just to repeat again, when we talk about connected cars, smart cities, smart buildings, smart retail and other connected workspaces, what we're talking about is the way that the open platform 3.0 will be consumed is you'll be consuming it in a digital workplace, a digital work of a combined surface of technologies, buildings, appliances. And the thinking that we're trying to introduce is a completely different way of looking at technology. It's part of your job, part of your work. So we need to get away from the idea that it's a portal, it's an engineered solution. It's something that will become integrated multidisciplinary into the car, into the building, into your workplace, the very place where you're listening now. It'll become part of the integrated fabric of the organization going forward in the supply chains around it. Thanks for that. Unless anyone has further points on that, I'd like to move on. One thing I'd like to do is briefly make comments on some of the questions that have been asked. Couldn't please share any links to get a good insight on open platform 3.0. The link that I posted on the chat, I think, earlier and which I'll post in the Q&A shortly is the best place to start for open platform 3.0. Would the convergence means a more standardized interfaces contributed by key industrial tech leaders? Would those big market players be willing to converge at the expense of their research and development? And that could be a huge discussion point. And I think the brief answer to that is we very much hope that that is how it will work. There's a few questions on the relation of open platform 3.0 to TOGAP. And a point generally to make on those is that open platform 3.0 is a separate forum in the open group to the architecture forum. Basically, TOGAP is about how you do architecture. Open platform 3.0 is more about the kind of architecture that you do for these new technologies. But the relation between open platform 3.0 and TOGAP is still really to be worked out in detail. So having got those very quick things off, I'd like to ask the panelists to comment on another question that's come in now, which is a very interesting one, which is how can we handle a huge volume unstructured data stream from the smack by using the open platform architecture? That's from Pravat. So that is a very interesting technical question. And I'd like to ask our panelists to comment on that. The answer to that is obviously the one, the capability that is pretty interesting and very core to the platform 3.0 is also the big data. And we look at the data to be the most critical or one of the most critical area in platform 3.0, which would handle a certain set of information in terms of structure and unstructured and also based on the velocity of that information. Having said that, obviously we'll also see a lot of changes in the integration middleware or the traditional integration middleware being transitioned into, which is the ESB architectures and the messaging architectures will move on to. There is already a set of standards if you have seen in the industry, which is MQTT, which takes care of a large set of data transitions between machine to machine capabilities. We have a certain set of standards coming out from different telco organizations like Telinor, introducing open objects, which is more to deal with how different things would behave and share the information effectively again over the network and over the wire with the little data connection or we can have a bandwidth. So convergence of obviously big data and certain transitions of ESBs into the newer ecosystem where you can see API based capabilities also coming up. We have a lot of API management technologies introducing in the digital ecosystem because a lot of thought laying monitoring for the particular information exchange. So I think there is a certain set of awareness in the particular industry to take care of this and the convergence of certain set of standards plus big data would really take care of that. Yes, just to add to what Rukesh is telling, this is Garvin. So I don't know specifically what open platform being available, but the unstructured data and handling streams of unstructured data, that is one of the emerging problems and I think it is more and more going to be very common that we need to handle these streams of data coming in. So back in general, I think in specific with respect to how big data is to handle data is good files a lot for its ability to do things real time. I think stream processing is one of them which actually requires a real time processing of data, especially the volumes of data that is coming in. So more and more I think there is a lot of interest in how big data technology is evolving to adapt to this new paradigm which is about processing data streams in real time. I think that is where Hadoop has a lot of efforts that are done in Hadoop 2.0 where in bringing real time data processing as one of the key components of it. Apart from Hadoop I think Spark and Storm and many other open source technologies which are actually trying to bring in the way in which the data streams can be processed in real time in a concurrent way, in a high volume way. I think it is going to be more and more common and I also see that there will be a lot more convergence that would happen between all these efforts, between Hadoop and Storm and Spark and many other technologies like ACA and so on and so forth. I would like at this point to say a very big thank you to our three presenters, Aravind Bhupesh and Gautam and Sima who joined us for the panel. And also a big thank you to everybody who participated in this webinar who asked some excellent questions. I see some great responses and discussion going on even now on the chat. So thanks everyone for this. If I can point you to the link, hcdps colon slash slash collaboration dot open group dot org slash platform three slash for further information and that's where the presentation that we use will be posted. So thanks to everybody for participating from myself and on behalf of the open group and I wish you all a pleasant rest of today.