>> Live from San Francisco, California, it's the theCUBE, covering the IBM Chief Data Officer Summit, brought to you by IBM. >> Welcome back to San Francisco everybody. You're watching theCUBE, the leader in live tech coverage. We go out to the events, we extract the signal from the noise and we're here at the IBM Chief Data Officer Summit, 10th anniversary. Seth Dobrin is here, he's the Vice President and Chief Data Officer of the IBM Analytics Group. Seth, always a pleasure to have you on. Good to see you again. >> Yeah, thanks for having me back Dave. >> You're very welcome. So I love these events you get a chance to interact with chief data officers, guys like yourself. We've been talking a lot today about IBM's internal transformation, how IBM itself is operationalizing AI and maybe we can talk about that, but I'm most interested in how you're pointing that at customers. What have you learned from your internal experiences and what are you bringing to customers? >> Yeah, so, you know, I was hired at IBM to lead part of our internal transformation, so I spent a lot of time doing that. >> Right. >> I've also, you know, when I came over to IBM I had just left Monsanto where I led part of their transformation. So I spent the better part of the first year or so at IBM not only focusing on our internal efforts, but helping our clients transform. And out of that I found that many of our clients needed help and guidance on how to do this. And so I started a team we call, The Data Science an AI Elite Team, and really what we do is we sit down with clients, we share not only our experience, but the methodology that we use internally at IBM so leveraging things like design thinking, DevOps, Agile, and how you implement that in the context of data science and AI. >> I've got a question, so Monsanto, obviously completely different business than IBM-- >> Yeah. >> But when we talk about digital transformation and then talk about the difference between a business and a digital business, it comes down to the data. And you've seen a lot of examples where you see companies traversing industries which never used to happen before. You know, Apple getting into music, there are many, many examples, and the theory is, well, it's 'cause it's data. So when you think about your experiences of a completely different industry bringing now the expertise to IBM, were there similarities that you're able to draw upon, or was it a completely different experience? >> No, I think there's tons of similarities which is, which is part of why I was excited about this and I think IBM was excited to have me. >> Because the chances for success were quite high in your mind? >> Yeah, yeah, because the chance for success were quite high, and also, you know, if you think about it there's on the, how you implement, how you execute, the differences are really cultural more than they're anything to do with the business, right? So it's, the whole role of a Chief Data Officer, or Chief Digital Officer, or a Chief Analytics Officer, is to drive fundamental change in the business, right? So it's how do you manage that cultural change, how do you build bridges, how do you make people, how do you make people a little uncomfortable, but at the same time get them excited about how to leverage things like data, and analytics, and AI, to change how they do business. And really this concept of a digital transformation is about moving away from traditional products and services, more towards outcome-based services and not selling things, but selling, as a Service, right? And it's the same whether it's IBM, you know, moving away from fully transactional to Cloud and subscription-based offerings. Or it's a bank reimagining how they interact with their customers, or it's oil and gas company, or it's a company like Monsanto really thinking about how do we provide outcomes. >> But how do you make sure that every, as a Service, is not a snowflake and it can scale so that you can actually, you know, make it a business? >> So underneath the, as a Service, is a few things. One is, data, one is, machine learning and AI, the other is really understanding your customer, right, because truly digital companies do everything through the eyes of their customer and so every company has many, many versions of their customer until they go through an exercise of creating a single version, right, a customer or a Client 360, if you will, and we went through that exercise at IBM. And those are all very consistent things, right? They're all pieces that kind of happen the same way in every company regardless of the industry and then you get into understanding what the desires of your customer are to do business with you differently. >> So you were talking before about the Chief Digital Officer, a Chief Data Officer, Chief Analytics Officer, as a change agent making people feel a little bit uncomfortable, explore that a little bit what's that, asking them questions that intuitively they, they know they need to have the answer to, but they don't through data? What did you mean by that? >> Yeah so here's the conversations that usually happen, right? You go and you talk to you peers in the organization and you start having conversations with them about what decisions are they trying to make, right? And you're the Chief Data Officer, you're responsible for that, and inevitably the conversation goes something like this, and I'm going to paraphrase. Give me the data I need to support my preconceived notions. >> (laughing) Yeah. >> Right? >> Right. >> And that's what they want to (voice covers voice). >> Here's the answer give me the data that-- >> That's right. So I want a Dashboard that helps me support this. And the uncomfortableness comes in a couple of things in that. It's getting them to let go of that and allow the data to provide some inkling of things that they didn't know were going on, that's one piece. The other is, then you start leveraging machine learning, or AI, to actually help start driving some decisions, so limiting the scope from infinity down to two or three things and surfacing those two or three things and telling people in your business your choices are one of these three things, right? That starts to make people feel uncomfortable and really is a challenge for that cultural change getting people used to trusting the machine, or in some instances even, trusting the machine to make the decision for you, or part of the decision for you. >> That's got to be one of the biggest cultural challenges because you've got somebody who's, let's say they run a big business, it's a profitable business, it's the engine of cashflow at the company, and you're saying, well, that's not what the data says. And you're, say okay, here's a future path-- >> Yeah. >> For success, but it's going to be disruptive, there's going to be a change and I can see people not wanting to go there. >> Yeah, and if you look at, to the point about, even businesses that are making the most money, or parts of a business that are making the most money, if you look at what the business journals say you start leveraging data and AI, you get double-digit increases in your productivity, in your, you know, in differentiation from your competitors. That happens inside of businesses too. So the conversation even with the most profitable parts of the business, or highly, contributing the most revenue is really what we could do better, right? You could get better margins on this revenue you're driving, you could, you know, that's the whole point is to get better leveraging data and AI to increase your margins, increase your revenue, all through data and AI. And then things like moving to, as a Service, from single point to transaction, that's a whole different business model and that leads from once every two or three or five years, getting revenue, to you get revenue every month, right? That's highly profitable for companies because you don't have to go in and send your sales force in every time to sell something, they buy something once, and they continue to pay as long as you keep 'em happy. >> But I can see that scaring people because if the incentives don't shift to go from a, you know, pay all up front, right, there's so many parts of the organization that have to align with that in order for that culture to actually occur. So can you give some examples of how you've, I mean obviously you ran through that at IBM, you saw-- >> Yeah. >> I'm sure a lot of that, got a lot of learnings and then took that to clients. Maybe some examples of client successes that you've had, or even not so successes that you've learned from. >> Yeah, so in terms of client success, I think many of our clients are just beginning this journey, certainly the ones I work with are beginning their journey so it's hard for me to say, client X has successfully done this. But I can certainly talk about how we've gone in, and some of the use cases we've done-- >> Great. >> With certain clients to think about how they transformed their business. So maybe the biggest bang for the buck one is in the oil and gas industry. So ExxonMobile was on stage with me at, Think, talking about-- >> Great. >> Some of the work that we've done with them in their upstream business, right? So every time they drop a well it costs them not thousands of dollars, but hundreds of millions of dollars. And in the oil and gas industry you're talking massive data, right, tens or hundreds of petabytes of data that constantly changes. And no one in that industry really had a data platform that could handle this dynamically. And it takes them months to get, to even start to be able to make a decision. So they really want us to help them figure out, well, how do we build a data platform on this massive scale that enables us to be able to make decisions more rapidly? And so the aim was really to cut this down from 90 days to less than a month. And through leveraging some of our tools, as well as some open-source technology, and teaching them new ways of working, we were able to lay down this foundation. Now this is before, we haven't even started thinking about helping them with AI, oil and gas industry has been doing this type of thing for decades, but they really were struggling with this platform. So that's a big success where, at least for the pilot, which was a small subset of their fields, we were able to help them reduce that timeframe by a lot to be able to start making a decision. >> So an example of a decision might be where to drill next? >> That's exactly the decision they're trying to make. >> Because for years, in that industry, it was boop, oh, no oil, boop, oh, no oil. >> Yeah, well. >> And they got more sophisticated, they started to use data, but I think what you're saying is, the time it took for that analysis was quite long. >> So the time it took to even overlay things like seismic data, topography data, what's happened in wells, and core as they've drilled around that, was really protracted just to pull the data together, right? And then once they got the data together there were some really, really smart people looking at it going, well, my experience says here, and it was driven by the data, but it was not driven by an algorithm. >> A little bit of art. >> True, a lot of art, right, and it still is. So now they want some AI, or some machine learning, to help guide those geophysicists to help determine where, based on the data, they should be dropping wells. And these are hundred million and billion dollar decisions they're making so it's really about how do we help them. >> And that's just one example, I mean-- >> Yeah. >> Every industry has it's own use cases, or-- >> Yeah, and so that's on the front end, right, about the data foundation, and then if you go to a company that was really advanced in leveraging analytics, or machine learning, JPMorgan Chase, in their, they have a division, and also they were on stage with me at, Think, that they had, basically everything is driven by a model, so they give traders a series of models and they make decisions. And now they need to monitor those models, those hundreds of models they have for misuse of those models, right? And so they needed to build a series of models to manage, to monitor their models. >> Right. >> And this was a tremendous deep-learning use case and they had just bought a power AI box from us so they wanted to start leveraging GPUs. And we really helped them figure out how do you navigate and what's the difference between building a model leveraging GPUs, compared to CPUs? How do you use it to accelerate the output, and again, this was really a cost-avoidance play because if people misuse these models they can get in a lot of trouble. But they also need to make these decisions very quickly because a trader goes to make a trade they need to make a decision, was this used properly or not before that trade is kicked off and milliseconds make a difference in the stock market so they needed a model. And one of the things about, you know, when you start leveraging GPUs and deep learning is sometimes you need these GPUs to do training and sometimes you need 'em to do training and scoring. And this was a case where you need to also build a pipeline that can leverage the GPUs for scoring as well which is actually quite complicated and not as straight forward as you might think. In near real time, in real time. >> Pretty close to real time. >> You can't get much more real time then those things, potentially to stop a trade before it occurs to protect the firm. >> Yeah. >> Right, or RELug it. >> Yeah, and don't quote, I think this is right, I think they actually don't do trades until it's confirmed and so-- >> Right. >> Or that's the desire as to not (voice covers voice). >> Well, and then now you're in a competitive situation where, you know. >> Yeah, I mean people put these trading floors as close to the stock exchange as they can-- >> Physically. >> Physically to (voice covers voice)-- >> To the speed of light right? >> Right, so every millisecond counts. >> Yeah, read Flash Boys-- >> Right, yeah. >> So, what's the biggest challenge you're finding, both at IBM and in your clients, in terms of operationalizing AI. Is it technology? Is it culture? Is it process? Is it-- >> Yeah, so culture is always hard, but I think as we start getting to really think about integrating AI and data into our operations, right? As you look at what software development did with this whole concept of DevOps, right, and really rapidly iterating, but getting things into a production-ready pipeline, looking at continuous integration, continuous development, what does that mean for data and AI? And these concept of DataOps and AIOps, right? And I think DataOps is very similar to DevOps in that things don't change that rapidly, right? You build your data pipeline, you build your data assets, you integrate them. They may change on the weeks, or months timeframe, but they're not changing on the hours, or days timeframe. As you get into some of these AI models some of them need to be retrained within a day, right, because the data changes, they fall out of parameters, or the parameters are very narrow and you need to keep 'em in there, what does that mean? How do you integrate this for your, into your CI/CD pipeline? How do you know when you need to do regression testing on the whole thing again? Does your data science and AI pipeline even allow for you to integrate into your current CI/CD pipeline? So this is actually an IBM-wide effort that my team is leading to start thinking about, how do we incorporate what we're doing into people's CI/CD pipeline so we can enable AIOps, if you will, or MLOps, and really, really IBM is the only company that's positioned to do that for so many reasons. One is, we're the only one with an end-to-end toolchain. So we do everything from data, feature development, feature engineering, generating models, whether selecting models, whether it's auto AI, or hand coding or visual modeling into things like trust and transparency. And so we're the only one with that entire toolchain. Secondly, we've got IBM research, we've got decades of industry experience, we've got our IBM Services Organization, all of us have been tackling with this with large enterprises so we're uniquely positioned to really be able to tackle this in a very enterprised-grade manner. >> Well, and the leverage that you can get within IBM and for your customers. >> And leveraging our clients, right? >> It's off the charts. >> We have six clients that are our most advanced clients that are working with us on this so it's not just us in a box, it's us with our clients working on this. >> So what are you hoping to have happen today? We're just about to get started with the keynotes. >> Yeah. >> We're going to take a break and then come back after the keynotes and we've got some great guests, but what are you hoping to get out of today? >> Yeah, so I've been with IBM for 2 1/2 years and I, and this is my eighth CEO Summit, so I've been to many more of these than I've been at IBM. And I went to these religiously before I joined IBM really for two reasons. One, there's no sales pitch, right, it's not a trade show. The second is it's the only place where I get the opportunity to listen to my peers and really have open and candid conversations about the challenges they're facing and how they're addressing them and really giving me insights into what other industries are doing and being able to benchmark me and my organization against the leading edge of what's going on in this space. >> I love it and that's why I love coming to these events. It's practitioners talking to practitioners. Seth Dobrin thanks so much for coming to theCUBE. >> Yeah, thanks always, Dave. >> Always a pleasure. All right, keep it right there everybody we'll be right back right after this short break. You're watching, theCUBE, live from San Francisco. Be right back.

>> live from Boston, Massachusetts. It's the Cube covering IBM Chief Data Officer Strategy Summit brought to you by IBM. Now here are your hosts. Day villain Day >> and stew Minimum. We're back. Welcome to Boston, Everybody. This is the IBM Chief Data Officer Summit. This is the Cube, the worldwide leader in live tech coverage. Inderpal. Bhandari is here. He's the newly appointed chief data officer at IBM. He's joined, but joined by Bob Picciano who is the senior vice president of IBM Analytics Group. Bob. Great to see again Inderpal. Welcome. Thank you. Thank you. So good event, Bob, Let's start with you. Um, you guys have been on the chief data officer kicked for several years now. You ahead of the curve. What, are you trying to achieve it? That this event? Yes. So, >> Dave, thanks again for having us here. And thanks for being here is well, tto help your audience share in what we're doing here. We've always appreciated that your commitment to help in the the masses understand all the important pulses that are going on the industry. What we're doing here is we're really moderating form between chief date officers on. We started this really on the curve. As you said 2014, where the conference was pretty small, there were some people who were actually examining the role, thinking about becoming a chief did officer. We probably had a few formal cheap date officers we're talking about, you know, maybe 100 or so people who are participating in the very 1st 1 Now you can see it's not, You know, it's it's grown much larger. We have hundreds of people, and we're doing it multiple times a year in multiple cities. But what we're really doing is bringing together a moderated form, Um, and it's a privilege to be able to do this. Uh, this is not about selling anything to anybody. This is about exchanging ideas, understanding. You know what, the challenges of the role of the opportunities which changing about the role, what's changing about the market and the landscape, what new risks might be on the horizon? What new opportunities might be on the horizon on we you know, we really liketo listen very closely to what's going on so we can, you know, maybe build better approach is to help their mother. That's through the services we provide or whether that's through the cloud capabilities were offering or whether that's new products and services that need to be developed. And so it gives us a great understanding. And we're really fortunate to have our chief data officer here, Interpol, who's doing a great job in IBM and in helping us on our mission around really becoming a cognitive enterprise and making analytics and insight on data really be central to that transformation. >> So, Dr Bhandari, new, uh, new to the chief date officer role, not nude. IBM. You worked here and came back. I was first exposed to roll maybe 45 years ago with the chief Data officer event. OK, so you come in is the chief data officer in December. Where do you start? >> So, you know, I've had the fortune of being in this role for a long time. I was one of the earliest created, the role for healthcare in two thousand six. Then I have honed that roll over three different Steve Data officer appointments at health care companies. And now I'm at IBM. So I do have, you know, I do view with the job as a craft. So it's a practitioner job and there's a craft to it. And do I answer your question? There are five things that you have to do to get moving on the job, and three of those have to be non sequentially and to must be done and powerful but everything else. So the five alarm. The first thing is you've got to develop a data strategy and data strategy is around, is focused around having an understanding ofthe how the company monetize is or plans to monetize itself. You know, what is the strategic monetization part of the company? Not so much how it monetize is data. But what is it trying to do? How is it going to make money in the future? So in the case of IBM, it's all around cognition. It's around enabling customers to become cognitive businesses. So my data strategy or our data strategy, I should say, is focused on enabling cognition becoming a cauldron of enterprise. You know, we've now realized that impacto prerequisite for cognition. So that's the data strategy piece. And that's the very first thing that needs to be done because once you understand that, then you understand what data is critical for the company, so you don't boil the ocean instead, what you do is you begin to govern exactly what's necessary and make sure it's fit for purpose. And then you can also create trusted data sources around those critical data assets that are critical for the for the monetization strategy of the company's. Those three have to go in sequence because if you don't know what you can do to adequately kind of three, and they're also significant pitfalls if you don't follow that sequence because you can end up pointing the ocean and the other two activities that must be done concurrently. One is in terms ofthe establishing deep partnerships with the other areas of the company the key business units, the key functional units because that's how you end up understanding what that data strategy ought to be. You know, if you don't have that knowledge of the company by making that effort that due diligence, that it's very difficult to get the data strategy right, so you've got to establish those partnerships and then the 5th 1 is because this is a space where you do require very significant talent. You have to start developing that talent and that all the organizational capability right from day one. >> So, Bob, you said that, uh, data is the new middle manager. You can't have an effective middle manager come unless you at least have some framework that was just described. >> Yeah, absolutely. So, you know, when Interpol talks about that fourth initiative about the engagement with the business units and making sure that we're in alignment on how the company's monetizing its value to its clients, his involvement with our team goes way beyond how he thinks about what date it is that we're collecting in the products that you're offering and what we might understand about our customers or about the marketplace. His involvement goes also into how we're curating the right user experience for who we want to win power with our products and offerings. Sometimes that's the role of the chief date officer. Sometimes that's the role of a data engineer. Sometimes it's the role of a data scientist. You mentioned data becoming the new middle management middle manager. We think the citizen analyst is ushering in that from from their seat, But we also need to be able to, from a perspective, to help them eliminate the long tail and and get transparency, the information. And sometimes it's the application developer. So we, uh, we collaborate on a very frequent basis, where, when we think about offering new capabilities to those roles, well, what's the data implication of that? What's the governance implication of that? How do we make it a seamless experience? So as people start to move down the path of igniting all of the innovation across those roles, there is a continuum to the information to using To be able to do that, how it's serving the enterprise, how it leads to that transformation to be a cognitive enterprise on DH. That's a very, very close collaboration >> we're moving from. You said you talked the process era to what I just inserted to an insight era. Yeah, um, and I have a question around that I'm not sure exactly how to formulate it, but maybe you can help. In the process, era technology was unknown. The process was very well, Don't know. Well known, but technology was mysterious. But with IBM and said help today it seems as though process is unknown. The technology's pretty known look at what uber airbnb you're doing the grabbing different technologies and putting them together. But the process is his new first of all, is that a reasonable observation? And if so, what does that mean for chief data officers? >> So the process is, you know, is new in the sense that in terms ofthe making it a cognitive process, it's going to end up being new, right? So the memorization that you >> never done it before, but it's never been done before, right >> in that sense. But it's different from process automation in the past. This is much more about knowledge, being able to scale knowledge, not just, you know, across one process, but across all the process cities that make up a company. And so in there. That goes also to the comment about data being the middle manager. I mean, if you've essentially got the ability to scale and manage knowledge, not just data but knowledge in terms of the insights that the people who are working these processes are coming up in conjunction with these data and intelligent capabilities, that that that that that of the hub right, it's the intelligence system that's had the Hubble this that's enabling all that so that That's really what leads Teo leads to the so called civilization >> way had dates to another >> important aspect of this is the process is dramatically different in the sense that it's ongoing. It's it's continuous, right, the process and your intimacy with uber and the trust that you're developing. A brand doesn't start and stop with one transaction and actually, you know branches into many different things. So your expectations, a CZ that relationships have all changed. So what they need to understand about you, what they need to protect about you, how they need to protect you in their transformation, the richness of their service needs to continue to evolve. So how they perform that task on the abundance of information they have available to perform that task. But the difficulty of being able to really consume it and make use of it is is a change. The other thing is, it's a lot more conversational, right? So the process isn't a deterministic set of steps that someone at a desk can really formulate in a business rule or a static process. It's conversationally changes. It needs to be dis ambiguity, and it needs to introduce new information during the process of disintegration. And that really, really calls upon the capabilities of a cognitive system that is rich and its ability to understand and interact with natural language to potentially introduce other sources of rich information. Because you might take a picture about what you're experiencing and all those things change that that notion from process to the conversational element. >> Dr. Bhandari, you've got an interesting role. Companies like IBM I think about the Theo with the CDO. Not only do you have your internal role, but you're also you know, a model for people going out there. You come too. Events like this. You're trying to help people in the role you've been a CDO. It's, um, health care organization to tell Yu know what's different about being kind of internal role of IBM. What kind of things? IBM Obviously, you know, strong technology culture, But tell us a little bit inside. You've learned what anything surprise you. You know, in your time that you've been doing it. >> Oh, you know, over the course ofthe time that I've been doing the roll across four different organizations, >> I guess specifically at IBM. But what's different there? >> You know, I mean IBM, for one thing, is a the The environment has tremendous scale. And if you're essentially talking about taking cognition to the enterprise, that gives us a tremendous A desperate to try out all the capabilities that were basically offering to our to our customers and to home that in the context of our own enterprise, you know, to build our own cognitive enterprise. And that's the journey that way, sharing with our with our customers and so forth. So that's that's different in in in in it. That wasn't the case in the previous previous rules that I had. And I think the other aspect that's different is the complexity of the organisation. This is a large global organization that wasn't true off the previous roles as well. They were Muchmore, not America century, you know, organizations. And so there's a There's an aspect there that also then that's complexity of the role in terms ofthe having to deal with different countries, different languages, different regulations, it just becomes much more complex. >> You first became a CDO in two thousand six, You said two thousand six, which was the same year as the Federal Rules of Civil Procedure came out and the emails became smoking guns. And then it was data viewed as a liability, and now it's completely viewed as an asset. But traditionally the CDO role was financial services and health care and government and highly regulated businesses. And it's clearly now seeping into new industries. What's driving that? Is that that value? >> Well, it is. I mean, it's, I think, that understanding that. You know, there's a tremendous natural resource in in the information in the data. But there is, you know, very much you know, union Yang around that notion of being responsible. I mean, one of the things that we're very proud of is the type of trust that we established over 105 year journey with our clients in the types of interactions we have with one another, the level of intimacy that we have in their business and very foundation away, that we serve them on. So we can never, ever do anything to compromise that you know. So the focus on really providing the ability to do the necessary governance and to do the necessary data providence and lineage in cyber security while not stifling innovation and being able to push into the next horizon. Interpol mentioned the fact that IBM, in and of itself, we think of ourselves as a laboratory, a laboratory for cognitive information innovation, a laboratory for design and innovation, which is so necessary in the digital era. And I think we've done a really good job in the spaces, but we're constantly pushing the envelope. A good example of that is blockchain, a technology that you know sometimes people think about and nefarious circumstances about, You know, what it meant to the ability to launch a Silk Road or something of that nature. We looked at the innovation understanding quite a lot about it being one of the core interview innovators around it, and saw great promise in being able to transform the way people thought about, you know, clearing multiparty transactions and applied it to our own IBM credit organization To think about a very transparent hyper ledger, we could bring those multiple parties together. People could have transparency and the transactions have a great deal of access into that space, and in a very, very rapid amount of time, we're able to take our very sizable IBM credit organization and implement that hyper ledger. Also, while thinking about the data regulation, the data government's implications. I think that's a really >> That's absolutely right. I mean, I think you know, Bob mentioned the example about the IBM credit organizer Asian, but there is. There are implications far beyond that. Their applications far beyond that in the data space. You know, it affords us now the opportunity to bring together identity management. You know, the profiles that people create from data of security aspects and essentially combined all of these aspects into what will then really become a trusted source ofthe data. You know, by trusted by me, I don't mean internally, but trusted by the consumers off the data. The subject's off the data because you'll be able to do that much in a way that's absolutely appropriate, not just fit for business purpose, but also very, very respectful of the consent on DH. Those aspects the privacy aspect ofthe data. So Blockchain really is a critical technology. >> Hype alleges a great example. We're IBM edge this week. >> You're gonna be a world of Watson. >> We will be a world Watson. We had the CEO of ever ledger on and they basically brought 1,000,000 diamonds and bringing transparency for the diamond industry. It's it's fraught with, with fraud and theft and counterfeiting and >> helping preserve integrity, the industry and eliminating the blood diamonds. And they right. >> It's fascinating to see how you know this bitcoin. You know, when so many people disparaged it is a currency, but not just the currency. You know, you guys IBM saw that early on and obviously participated in the open source. Be, You know, the old saying follow the money with us is like follow the data. So if I understand correctly, your job, a CDO is to sort of super charge of the business lines with the data strategy. And then, Bob, you're job is the line of business managers the supercharge your customers, businesses with the data strategy. Is that right? Is that the right value >> chain? I think you nailed it. Yeah, that's >> one of the things people are struggling with these days is, you know, if they can get their own data in house, then they've also gotta deal with third party. That industry did everything like that. IBM's role in that data chain is really interesting. You talked this morning about kind of the Weather Channel and kind of the data play there. Yeah, you know what? What's IBM is rolling. They're going forward. >> It's one of the most exciting things. I think about how we've evolved our strategy. And, you know, we're very fortunate to have Jimmy at the helm. Who really understands, You know, that transformational landscape on DH, how partnerships really change the ability to innovate for the companies we serve on? It was very obvious in understanding our client's problems that while they had a wealth of information that we were dealing with internally, there was great promise and being able to introduce these outside signals. If you will insights from other sources of data, Sometimes I call them vectors of information that could really transform the way they were thinking about solving their customer problem. So, you know, why wouldn't you ever want to understand that customers sentiment about your brand or about the product or service? And as a consequence to that, you know, capabilities that are there on Twitter or we chat or line are essential to that, depending on where your brand is operating in your branch, probably operating in a multinational space anyway, so you have to listen to all those signals and they're all in multiple language and sentiment is very, very bespoke. It's a different language, so you have to apply sophisticated machine learning. We've invented new algorithms to understand how to glean the signal at all that white noise. You use the weather example as well. You know, we think about the economic impact of climate atmosphere, whether on business and its profound. It's 1/2 trillion dollars, you know, in each calendar year that are, you know, lost information, lost assets, lost opportunity, misplaced inventory, you know, un delivered inventory. And we think we can do a better job of helping our clients take the weather excuses out of business in a variety of different industries. And so we've focused our initiatives on that information integration, governance, understanding new analytics toe to introduce those outside signals directly in the heart and want to place it on the desk of the chief data officer of those who are innovating around information and data. >> My my joke last Columbus. If they was Dell's buying DMC, IBM is buying the weather company. What does What does that say? My question is Interpol. When when Emma happens. And Bob, when you go out and purchase companies that are data driven, what role does the chief data officer play in both em in a pre and post. >> So, you know, I think the one that there being a cop, just gonna touch on a couple of points that Bob Major and I'll address your question directly as well. Uh, in terms of the role of the chief data officer, I think you're giving me that question before how that's he walled. The one very interesting thing that's happening now with what IBM is doing is previously the chief data officer. All at least with regard to the data, Not so much the strategy, but the data itself was internal focused. You know, you kind of worried about the data you had in house or the data you're bringing in now you've gotta worry as much about the exogenous status and because, you know, that's so That's one way that that role has changed considerably and is changing and evolving, and it's creating new opportunities for us. The other is again. In the past, the chief state officer all was around creating a warehouse for analytics and separated out from the operational processes. That's changing, too, because now we've got to transform these processes themselves. So that's, you know, that's that's another expanded role to come back to. Acquisitions emanate. I mean, I view that as essentially another process that, you know, company has. And so the chief data officer role is pretty key in terms of enabling that world in terms ofthe data, but also in terms ofthe giving, you know, guidance and advice. If, for instance, the acquisition isn't that problem itself, then you know, then we would be more closely involved. But if it's beyond that in terms of being able to get the right data, do that process as well as then once you've acquired the company in being able to integrate back the critical data assets those out of the key aspect, it's an ongoing role. >> So you've got the simplest level. You've got data sources and all the things associated with that. And then you've got your algorithms and your machine learning, and we're moving beyond sort of do tow cut costs into this new era. But so hot Oh cos adjudicate. And I guess you got to do both. You've got to get new data sources and you've got to improve this continuous process. By that you talked about how do you guide your customers as to where they put their resource? No. And that's >> really Davis. You have, you know, touching out again. That's really the benefit of this sort of a forum. In this sort of a conference, it's sharing the best practices of how the top experts in the world are really wrestling with that and identifying. I think you know Interpol's framework. What do you do sequentially to build the disciplines, to build a solid corn foundation, to make the connections that are lined with the business strategy? And then what do you do concurrently along that model to continue to operate? And how do you How do you manage and make sure your stakeholders understand what's being done? What they need to continue to do to evolve the innovation and come join us here and we'll go through that in detail. But, you know, he deposited a greatjob sharing his framers of success, and I think in the other room, other CEOs are doing that now. >> Yeah, I just wanted to quickly add to Bob's comment. The framework that I described right? It has a check and balance built into it because if you are all about governance, then the Sirio role becomes very defensive in nature. It's all about making sure you within the hour, you know, within the guard rails and so forth. But you're not really moving forward in a strategic way to help the company. And and that's why you know, setting it up by driving it from the strategy don't just makes it easier to strike that plus >> clerical and more about innovation here. We talked about the D and CDO today meaning data, but really, I think about it is being a great crucible for for disruption in information because you've disruption off. I called the Chief Disruption Office under Sheriff you >> incident in Data's digitalis data. So there's that piece of Ava's Well, we have to go. I don't want to go. So that way one last question for each of you. So Interpol, uh, thinking about and you just kind of just touched on it. He's not just playing defense, you know, thinking more offense this role. Where do you want to take it. What do your you know, sort of mid term, long term goals with this role? >> It's the specific role in IBM or just in general specifically. Well, I think in the case of I B M, we have the data strategy pretty well defined. Now it's all about being able to enable a cognitive enterprise. And so in, You know, in my mind and 2 to 3 years, we'll have completely established how that ought to be done, you know, as a prescription. And we'll also have our clients essentially sharing in that in that journey so that they can go off and create cognitive enterprises themselves. So that's pretty well set. You know, I have a pretty short window to three years to make that make that happen, And I think it's it's doable. And I think it will be, you know, just just a tremendous transformation. >> Well, we're excited to be to be watching and documenting that Bob, I have to ask you a world of washing coming up. New name for new conference. We're trying to get Pepper on, trying to get Jimmy on. Say, what should we expect? Maybe could. Although it was >> coming, and I think this year we're sort of blowing the roof off on literally were getting so big that we had to move the venue. It is very much still in its core that multiple practitioner, that multiple industry event that you experienced with insight, right? So whether or not you're thinking about this and the auspices of managing your traditional environments and what you need to do to bring them into the future and how you tie these things together, that's there for you. All those great industry tracks around the product agendas and what's coming out are are there. But the level of inspiration and involvement around this cognitive innovation space is going to be front and center. We're joined by Ginny Rometty herself, who's going to be very special. Key note. We have, I think, an unprecedented lineup of industry leaders who were going to come and talk about disruption and about disruption in the cognitive era on then. And as always, the most valuable thing is the journeys that our clients are partners sharing with us about how we're leading this inflection point transformation, the industry. So I'm very much excited to see their and I hope that your audience joins us as well. >> Great. We'll Interpol. Congratulations on the new roll. Thank you. Get a couple could plug, block post out of your comments today, so I really appreciate that, Bob. Always a pleasure. Thanks so much for having us here. Really? Appreciate. >> Thanks for having us. >> Alright. Keep right, everybody, this is the Cube will be back. This is the IBM Chief Data Officer Summit. We're live from Boston. You're back. My name is Dave Volante on DH. I'm along.