>> Narrator: Live from Munich Germany, it's theCUBE, covering IBM, Fast Track Your Data. Brought to you by IBM. >> We're back. This is Dave Vellante with Jim Kobielus, and this is theCUBE, the leader in live tech coverage. We go out to the events. We extract the signal from the noise. We are here covering special presentation of IBM's Fast Track your Data, and we're in Munich Germany. It's been a day-long session. We started this morning with a panel discussion with five senior level data scientists that Jim and I hosted. Then we did CUBE interviews in the morning. We cut away to the main tent. Kate Silverton did a very choreographed scripted, but very well done, main keynote set of presentations. IBM made a couple of announcements today, and then we finished up theCUBE interviews. Jim and I are here to wrap. We're actually running on IBMgo.com. We're running live. Hilary Mason talking about what she's doing in data science, and also we got a session on GDPR. You got to log in to see those sessions. So go ahead to IBMgo.com, and you'll find those. Hit the schedule and go to the Hilary Mason and GDP our channels, and check that out, but we're going to wrap now. Jim two main announcements today. I hesitate to call them big announcements. I mean they were you know just kind of ... I think the word you used last night was perfunctory. You know I mean they're okay, but they're not game changing. So what did you mean? >> Well first of all, when you look at ... Though IBM is not calling this a signature event, it's essentially a signature event. They do these every June or so. You know in the past several years, the signature events have had like a one track theme, whether it be IBM announcing their investing deeply in Spark, or IBM announcing that they're focusing on investing in R as the core language for data science development. This year at this event in Munich, it's really a three track event, in terms of the broad themes, and I mean they're all important tracks, but none of them is like game-changing. Perhaps IBM doesn't intend them to be it seems like. One of which is obviously Europe. We're holding this in Munich. And a couple of things of importance to European customers, first and foremost GDPR. The deadline next year, in terms of compliance, is approaching. So sound the alarm as it were. And IBM has rolled out compliance or governance tools. Download and the go from the information catalog, governance catalog and so forth. Now announcing the consortium with Hortonworks to build governance on top of Apache Atlas, but also IBM announcing that they've opened up a DSX center in England and a machine-learning hub here in Germany, to help their European clients, in those countries especially, to get deeper down into data science and machine learning, in terms of developing those applicants. That's important for the audience, the regional audience here. The second track, which is also important, and I alluded to it. It's governance. In all of its manifestations you need a master catalog of all the assets for building and maintaining and controlling your data applications and your data science applications. The catalog, the consortium, the various offerings at IBM is announced and discussed in great detail. They've brought in customers and partners like Northern Trust, talk about the importance of governance, not just as a compliance mandate, but also the potential strategy for monetizing your data. That's important. Number three is what I call cloud native data applications and how the state of the art in developing data applications is moving towards containerized and orchestrated environments that involve things like Docker and Kubernetes. The IBM DB2 developer community edition. Been in the market for a few years. The latest version they announced today includes kubernetes support. Includes support for JSON. So it's geared towards new generation of cloud and data apps. What I'm getting at ... Those three core themes are Europe governance and cloud native data application development. Each of them is individually important, but none of them is game changer. And one last thing. Data science and machine learning, is one of the overarching envelope themes of this event. They've had Hilary Mason. A lot of discussion there. My sense I was a little bit disappointed because there wasn't any significant new announcements related to IBM evolving their machine learning portfolio into deep learning or artificial intelligence in an environment where their direct competitors like Microsoft and Google and Amazon are making a huge push in AI, in terms of their investments. There's a bit of a discussion, and Rob Thomas got to it this morning, about DSX. Working with power AI, the IBM platform, I would like to hear more going forward about IBM investments in these areas. So I thought it was an interesting bunch of announcements. I'll backtrack on perfunctory. I'll just say it was good that they had this for a lot of reasons, but like I said, none of these individual announcements is really changing the game. In fact like I said, I think I'm waiting for the fall, to see where IBM goes in terms of doing something that's actually differentiating and innovative. >> Well I think that the event itself is great. You've got a bunch of partners here, a bunch of customers. I mean it's active. IBM knows how to throw a party. They've always have. >> And the sessions are really individually awesome. I mean terms of what you learn. >> The content is very good. I would agree. The two announcements that were sort of you know DB2, sort of what I call community edition. Simpler, easier to download. Even Dave can download DB2. I really don't want to download DB2, but I could, and play with it I guess. You know I'm not database guy, but those of you out there that are, go check it out. And the other one was the sort of unified data governance. They tried to tie it in. I think they actually did a really good job of tying it into GDPR. We're going to hear over the next, you know 11 months, just a ton of GDPR readiness fear, uncertainty and doubt, from the vendor community, kind of like we heard with Y2K. We'll see what kind of impact GDPR has. I mean it looks like it's the real deal Jim. I mean it looks like you know this 4% of turnover penalty. The penalties are much more onerous than any other sort of you know, regulation that we've seen in the past, where you could just sort of fluff it off. Say yeah just pay the fine. I think you're going to see a lot of, well pay the lawyers to delay this thing and battle it. >> And one of our people in theCUBE that we interviewed, said it exactly right. It's like the GDPR is like the inverse of Y2K. In Y2K everybody was freaking out. It was actually nothing when it came down to it. Where nobody on the street is really buzzing. I mean the average person is not buzzing about GDPR, but it's hugely important. And like you said, I mean some serious penalties may be in the works for companies that are not complying, companies not just in Europe, but all around the world who do business with European customers. >> Right okay so now bring it back to sort of machine learning, deep learning. You basically said to Rob Thomas, I see machine learning here. I don't see a lot of the deep learning stuff quite yet. He said stay tuned. You know you were talking about TensorFlow and things like that. >> Yeah they supported that ... >> Explain. >> So Rob indicated that IBM very much, like with power AI and DSX, provides an open framework or toolkit for plugging in your, you the developers, preferred machine learning or deep learning toolkit of an open source nature. And there's a growing range of open source deep learning toolkits beyond you know TensorFlow, including Theano and MXNet and so forth, that IBM is supporting within the overall ESX framework, but also within the power AI framework. In other words they've got those capabilities. They're sort of burying that message under a bushel basket, at least in terms of this event. Also one of the things that ... I said this too Mena Scoyal. Watson data platform, which they launched last fall, very important product. Very important platform for collaboration among data science professionals, in terms of the machine learning development pipeline. I wish there was more about the Watson data platform here, about where they're taking it, what the customers are doing with it. Like I said a couple of times, I see Watson data platform as very much a DevOps tool for the new generation of developers that are building machine learning models directly into their applications. I'd like to see IBM, going forward turn Watson data platform into a true DevOps platform, in terms of continuous integration of machine learning and deep learning another statistical models. Continuous training, continuous deployment, iteration. I believe that's where they're going, or probably she will be going. I'd like to see more. I'm expecting more along those lines going forward. What I just described about DevOps for data science is a big theme that we're focusing on at Wikibon, in terms where the industry is going. >> Yeah, yeah. And I want to come back to that again, and get an update on what you're doing within your team, and talk about the research. Before we do that, I mean one of the things we talked about on theCUBE, in the early days of Hadoop is that the guys are going to make the money in this big data business of the practitioners. They're not going to see, you know these multi-hundred billion dollar valuations come out of the Hadoop world. And so far that prediction has held up well. It's the Airbnbs and the Ubers and the Spotifys and the Facebooks and the Googles, the practitioners who are applying big data, that are crushing it and making all the money. You see Amazon now buying Whole Foods. That in our view is a data play, but who's winning here, in either the vendor or the practitioner community? >> Who's winning are the startups with a hot new idea that's changing, that's disrupting some industry, or set of industries with machine learning, deep learning, big data, etc. For example everybody's, with bated breath, waiting for you know self-driving vehicles. And the ecosystem as it develops somebody's going to clean up. And one or more companies, companies we probably never heard of, leveraging everything we're describing here today, data science and containerized distributed applications that involve you know deep learning for you know image analysis and sensor analyst and so forth. Putting it all together in some new fabric that changes the way we live on this planet, but as you said the platforms themselves, whether they be Hadoop or Spark or TensorFlow, whatever, they're open source. You know and the fact is, by it's very nature, open source based solutions, in terms of profit margins on selling those, inexorably migrate to zero. So you're not going to make any money as a tool vendor, or a platform vendor. You got to make money ... If you're going to make money, you make money, for example from providing an ecosystem, within which innovation can happen. >> Okay we have a few minutes left. Let's talk about the research that you're working on. What's exciting you these days? >> Right, right. So I think a lot of people know I've been around the analyst space for a long long time. I've joined the SiliconANGLE Wikibon team just recently. I used to work for a very large solution provider, and what I do here for Wikibon is I focus on data science as the core of next generation application development. When I say next-generation application development, it's the development of AI, deep learning machine learning, and the deployment of those data-driven statistical assets into all manner of application. And you look at the hot stuff, like chatbots for example. Transforming the experience in e-commerce on mobile devices. Siri and Alexa and so forth. Hugely important. So what we're doing is we're focusing on AI and everything. We're focusing on containerization and building of AI micro-services and the ecosystem of the pipelines and the tools that allow you to do that. DevOps for data science, distributed training, federated training of statistical models, so forth. We are also very much focusing on the whole distributed containerized ecosystem, Docker, Kubernetes and so forth. Where that's going, in terms of changing the state of the art, in terms of application development. Focusing on the API economy. All of those things that you need to wrap around the payload of AI to deliver it into every ... >> So you're focused on that intersection between AI and the related topics and the developer. Who is winning in that developer community? Obviously Amazon's winning. You got Microsoft doing a good job there. Google, Apple, who else? I mean how's IBM doing for example? Maybe name some names. Who do you who impresses you in the developer community? But specifically let's start with IBM. How is IBM doing in that space? >> IBM's doing really well. IBM has been for quite a while, been very good about engaging with new generation of developers, using spark and R and Hadoop and so forth to build applications rapidly and deploy them rapidly into all manner of applications. So IBM has very much reached out to, in the last several years, the Millennials for whom all of this, these new tools, have been their core repertoire from the very start. And I think in many ways, like today like developer edition of the DB2 developer community edition is very much geared to that market. Saying you know to the cloud native application developer, take a second look at DB2. There's a lot in DB2 that you might bring into your next application development initiative, alongside your spark toolkit and so forth. So IBM has startup envy. They're a big old company. Been around more than a hundred years. And they're trying to, very much bootstrap and restart their brand in this new context, in the 21st century. I think they're making a good effort at doing it. In terms of community engagement, they have a really good community engagement program, all around the world, in terms of hackathons and developer days, you know meetups here and there. And they get lots of turnout and very loyal customers and IBM's got to broadest portfolio. >> So you still bleed a little bit of blue. So I got to squeeze it out of you now here. So let me push a little bit on what you're saying. So DB2 is the emphasis here, trying to position DB2 as appealing for developers, but why not some of the other you know acquisitions that they've made? I mean you don't hear that much about Cloudant, Dash TV, and things of that nature. You would think that that would be more appealing to some of the developer communities than DB2. Or am I mistaken? Is it IBM sort of going after the core, trying to evolve that core you know constituency? >> No they've done a lot of strategic acquisitions like Cloudant, and like they've acquired Agrath Databases and brought them into their platform. IBM has every type of database or file system that you might need for web or social or Internet of Things. And so with all of the development challenges, IBM has got a really high-quality, fit-the-purpose, best-of-breed platform, underlying data platform for it. They've got huge amounts of developers energized all around the world working on this platform. DB2, in the last several years they've taken all of their platforms, their legacy ... That's the wrong word. All their existing mature platforms, like DB2 and brought them into the IBM cloud. >> I think legacy is the right word. >> Yeah, yeah. >> These things have been around for 30 years. >> And they're not going away because they're field-proven and ... >> They are evolving. >> And customers have implemented them everywhere. And they're evolving. If you look at how IBM has evolved DB2 in the last several years into ... For example they responded to the challenge from SAP HANA. We brought BLU Acceleration technology in memory technology into DB2 to make it screamingly fast and so forth. IBM has done a really good job of turning around these product groups and the product architecture is making them cloud first. And then reaching out to a new generation of cloud application developers. Like I said today, things like DB2 developer community edition, it's just the next chapter in this ongoing saga of IBM turning itself around. Like I said, each of the individual announcements today is like okay that's interesting. I'm glad to see IBM showing progress. None of them is individually disruptive. I think the last week though, I think Hortonworks was disruptive in the sense that IBM recognized that BigInsights didn't really have a lot of traction in the Hadoop spaces, not as much as they would have wished. Hortonworks very much does, and IBM has cast its lot to work with HDP, but HDP and Hortonworks recognizes they haven't achieved any traction with data scientists, therefore DSX makes sense, as part of the Hortonworks portfolio. Likewise a big sequel makes perfect sense as the sequel front end to the HDP. I think the teaming of IBM and Hortonworks is propitious of further things that they'll be doing in the future, not just governance, but really putting together a broader cloud portfolio for the next generation of data scientists doing work in the cloud. >> Do you think Hortonworks is a legitimate acquisition target for IBM. >> Of course they are. >> Why would IBM ... You know educate us. Why would IBM want to acquire Hortonworks? What does that give IBM? Open source mojo, obviously. >> Yeah mojo. >> What else? >> Strong loyalty with the Hadoop market with developers. >> The developer angle would supercharge the developer angle, and maybe make it more relevant outside of some of those legacy systems. Is that it? >> Yeah, but also remember that Hortonworks came from Yahoo, the team that developed much of what became Hadoop. They've got an excellent team. Strategic team. So in many ways, you can look at Hortonworks as one part aqui-hire if they ever do that and one part really substantial and growing solution portfolio that in many ways is complementary to IBM. Hortonworks is really deep on the governance of Hadoop. IBM has gone there, but I think Hortonworks is even deeper, in terms of their their laser focus. >> Ecosystem expansion, and it actually really wouldn't be that expensive of an acquisition. I mean it's you know north of ... Maybe a billion dollars might get it done. >> Yeah. >> You know so would you pay a billion dollars for Hortonworks? >> Not out of my own pocket. >> No, I mean if you're IBM. You think that would deliver that kind of value? I mean you know how IBM thinks about about acquisitions. They're good at acquisitions. They look at the IRR. They have their formula. They blue-wash the companies and they generally do very well with acquisitions. Do you think Hortonworks would fit profile, that monetization profile? >> I wouldn't say that Hortonworks, in terms of monetization potential, would match say what IBM has achieved by acquiring the Netezza. >> Cognos. >> Or SPSS. I mean SPSS has been an extraordinarily successful ... >> Well the day IBM acquired SPSS they tripled the license fees. As a customer I know, ouch, it worked. It was incredibly successful. >> Well, yeah. Cognos was. Netezza was. And SPSS. Those three acquisitions in the last ten years have been extraordinarily pivotal and successful for IBM to build what they now have, which is really the most comprehensive portfolio of fit-to-purpose data platform. So in other words all those acquisitions prepared IBM to duke it out now with their primary competitors in this new field, which are Microsoft, who's newly resurgent, and Amazon Web Services. In other words, the two Seattle vendors, Seattle has come on strong, in a way that almost Seattle now in big data in the cloud is eclipsing Silicon Valley, in terms of where you know ... It's like the locus of innovation and really of customer adoption in the cloud space. >> Quite amazing. Well Google still hanging in there. >> Oh yeah. >> Alright, Jim. Really a pleasure working with you today. Thanks so much. Really appreciate it. >> Thanks for bringing me on your team. >> And Munich crew, you guys did a great job. Really well done. Chuck, Alex, Patrick wherever he is, and our great makeup lady. Thanks a lot. Everybody back home. We're out. This is Fast Track Your Data. Go to IBMgo.com for all the replays. Youtube.com/SiliconANGLE for all the shows. TheCUBE.net is where we tell you where theCUBE's going to be. Go to wikibon.com for all the research. Thanks for watching everybody. This is Dave Vellante with Jim Kobielus. We're out.

>> Announcer: Live from Munich, Germany, it's theCUBE. Covering IBM, Fast Track Your Data, brought to you by IBM. >> We're back in Munich, Germany this is Fast Track Your Data and this is theCUBE, the leader in live tech coverage, we go out to the events. We extract a signal from the noise my name is Dave Vellante and I'm here with my co-host Jim Kobielus. We just came off of the main stage. IBM had a very choreographed, really beautiful, Kate Silverton was there of BBC Fame talking to various folks within the IBM community. IBM executives, practitioners, and quite a main stage production Jim. IBM always knows how to do it right. Manish Goyal here, he's the Director of Product Management for the Watson Data Platform. Something we covered on theCUBE extensively, that announcement last year in New York City. Manish welcome to theCUBE. >> Thank you for having me. >> Dave: So this is, it really was your signature moment back in last fall at Strata in New York City. We covered that, big announcement, lot of customers there. You guys demonstrated sort of the next generation of platform that you guys are announcing. >> Manish: That's right. >> So take us, bring us up to date. How's it going, where are we at, and what are you guys doing here? >> So, again thank you for having me. >> Dave: You're welcome. >> Let me take a minute to just let all the viewers know what is alternate about form. So the Watson Data Platform is our cloud analytics platform, and it's really three things. It's a set of composable data services, for ingest, analyze, processed. It's a set of tailor-made experiences for the different personas. Whether you are a data engineer, a business analyst, data scientist, or the steward. And connecting all of these, both of these is a set of data fabric, which is really the secret sauce. And think of this as being the governance layer that ensures that everything that we're doing, that everything that is being done by any of these personas is working on trusted data, and that the insights that are being generated can be trusted by the risk folks, the business folks, as they put the analytics into production. >> Dave: So just to review for our audience, there are a number of components to the Watson Data Platform. >> That's right, yep. >> Dave: There's the governance components you mentioned, there's the visualization, there's analytics. Now, many people criticized Watson Data Platform, they said oh it's just IBM putting a bunch of despaired products together, some acquisitions and then wrapping some services around it. When we talked to you guys in October, you said no, no, that's not the case. But can you affirm that? >> That is exactly right, that is not the case. It's not just us putting stuff together and calling it a new name, and think oh that's the platform, just a set of despaired services. That is absolutely not, and that's why I was emphasizing this common data fabric, right. I've got a couple of, let me sort of dive a little bit deeper into it. >> Sure, great. >> Manish: So the biggest problem that customers and data users in general complain about is, extremely hard to find data, right. The tools that they're working with are all siloed. So even if, you know, you and I are working on, you know our analytics projects, very hard for me to share what I'm working on with you, the environment that I am running on with you, et cetera. And this... The third piece is, a real issue with is the data that I'm working with trusted? Like can I actually believe that this is the best data that I can use, so that when I put something into production when I create my machine learning models I put them into my production environment. The risk guys are going to be fine with it, I'm going to be fine with it, I see the results that I'm getting. And so, getting this data fabric which is addressing these issues. One, it's addressing it first and foremost with a data catalog, a governance layer. So that it's very clear, irrespective, whether you're a data engineer, business analyst, data scientist or the data steward, from the CDO's office, you're all working off the same version of the truth, right. >> Jim: Manish is that something a DevOps platform, is it like DevOps for data science or for machine learning development or is it... How would you describe... Does that make sense? The automated release pipeline that's-- >> Manish: In a way yes. >> With the governance baked in? >> Yes, in a way that's one way to describe it. So that's one aspect right? Making sure that you're working with the trusted data, making it very easy to find the data, so that's sort of the governance aspect. The second piece that sort of really makes this a platform is that you're working off the same notion of a workspace, we call it a project. So, you may start out as a data engineer being asked yourself, take all these different data sources that are coming in and create and publish a data set that can be consumed for dashboarding, for data analysis whatever. And you're working on that in a project, now if you have a data science team that needs to be working on the same thing, you can just invite them to the same project. So they're working on the same thing, similarly to a business analyst, et cetera. And all of these results, and when we talk about governance it's not about just data sets, it's all analytical products. So it is the model that you're creating are being put back into the catalog and governed. Data flows-- >> It's model governance. >> Jim: Model governance, it's model governance? >> Exactly. >> And aiding governance. >> Manish: So it's a huge problem that customers have. I was just talking to a large insurance company yesterday, and they're question was, "What are you doing to make sure that I don't have to spend an enormous amount of time that I have to with the risk group, before I can put a model into production." Because they want complete lineage all the way back, saying "Okay you created this model, you're going to put it into production, whether it's for allowing credit card insurance, whatever your product is that you're selling. How do you make sure that there's no bias in the model that is created, can you show me the data set on which you trained it? And then when you re-trained it can you show me that data set?" So in case they're audited, that there's complete way to go back from the production model all the way back to the data set that was created. And which goes even further back from all the different data sources. Where it was cleansed, et cetera, the ETL, where it was published, and then picked up by data science team. So all of these things, putting it together with this data fabric. Governance being a huge, huge portion of that that goes across everything that we're doing. Giving these tailor-made experiences for the different business personas, oh sorry, the data personas, and just making it extremely simple for generating insights that can be trusted. So that is what we are trying to do with the Watson Data Platform. As, since last fall when we announced it, we have had a huge update on our data science experience, you heard a lot about that in the presentation this morning. As well as, all of our other cloud data services and the governance put forth. >> Dave: And that data science experience is embedded fundamental to the platform. >> It is, it is. >> Dave: You know I want to ask you about that. Because I don't know if you remember Jim and Manish, a few years ago, several years ago, Pivotal announced this thing called Chorus and it went, it was a collaboration platform and it really went nowhere. Now part of the reason it went nowhere was because it was early days, but also there wasn't the analytics solution underneath it. But a lot of people questioned, "Well do we really need to collaborate across those personas?" Again maybe they were immature at the time. So convince me that there's a need for that and that this is actually getting used in the world. >> There was an example, probably you've always seen the venn diagram or for data scientist, right? With all the different skills that they need, they are a unicorn, and there are no unicorns. It's extremely hard for our customers, in fact just finding really good data scientist is extremely hard. It's a very limited supply of that talent. So that's one thing right. So you can't find enough of these folks to scale out the level of analytics that is needed, if you want to use data for a comparative advantage. So that's one aspect right, of talent being a huge issue. The second aspect of it is you really do need specialized skill in data engineer. You don't want your PhD data scientist spending 60% of their time finding cleansing data. You have folks who really do that well and you want to enable them to work closely with the data science team. And you really do need business analyst who are the key to sort of understanding the business problem that needs to be solved, because that's where you always want to start any analytics product. What is it that you're trying to improve, or reduce cost on, or whatever your problem is that you're addressing. And so you really need, it is a team sport. You can't just do it without. Now if it is a team sport, how are these folks going to collaborate, right? And that is why, in all of our interactions with our customers and their data science teams. They absolutely love the collaboration features that we have put in, and we have put in a lot of effort in data science experience and the same collaboration features are actually going to extend across the portfolio of these experiences on the data platform. >> And the whole notion of personas is so fundamental to Watson Data Platform. And I'm wondering, is IBM evolving the range and variety of personas for which you're providing these experiences? And what I mean by that is, examples, we see more and more data science application development projects focusing on for example, chat bots. That involves human conversation, you need a bit more, possibly a persona, a computational linguist. Or cognitive IoT, like Watson, you know IoT, that's sensors, that's hardware devices maybe hardware engineers, hardware engineering experiences. You see what I'm getting at is that data science centric projects are increasingly moving from the totally virtual world, to being very much embedding in the physical world and the world of human guided, machine learning guided conversation. What are your thoughts about evolving the personas mix? >> So application, application developers, or the persona I actually missed when I was talking about this before, it's absolutely central because almost anything that the data science team is doing is going to create, at the end of the day, sort of create models. But the hope is that it's going to put into production system. And that job typically is the role of an application developer. Now, Jim you mentioned sort of, there's a lot of emphasis these days on conversational chat bots. And again, at the end of the day with data science projects you are in many ways, trying to improve the experience that you're giving your customers. Or personalizing the experience that you're giving your customers. A celebrity experience that Rob talked about this morning. And there are other personas involved in that sense, so to get a chat bot right, I mean there is data that you can obviously harvest and use to create that flow, an intelligence in chat bot. But there are elements where you do need a subject matter expert to curate that. To make sure that it doesn't seem robotic, that it does feel genuine. And so there is a role for a subject matter expert, we sort of collaborate with a business analyst role, or persona. But yes, all of these roles play an important part in sort of putting together the entire package. It just feels seamless, and that's why I sort of come back to saying that it is a team sport and if you do not enable the teams to work closely together, and enhance their productivity, you can go after all the data that's being generated and all the opportunity that data is presenting. And the prize is to gain a competitive advantage. >> Dave: One of the things Manish, you demonstrated last fall was this sort of, it was sort of a recommendation engine and very personalized. And it was quite a nice demo and it wasn't a fake demo from what I understood, it was real data. Can you share with us in the time we have remaining, just some of your favorite examples of how people are applying the Watson Data Platform and affecting business? >> Manish: Sure yeah so, I'll tell you a couple of examples. So I was actually in London earlier this week, meeting with a customer and they are using DSX, our data science experience, with a couple of utility companies. One is a water company, water utility company. And the problem that they're trying to solve is, they're supplying water in a hilly area and they want to optimize the power that they use to power the pumps to pump out water. Because it can be very expensive if the pumps are running all the time, et cetera. And so they're using data science experience to optimize when and how, and how long the pumps need to run to enable that the customers are happy with the level of water supply that they're getting and the force that they're getting it with. While the utility company is optimizing the expense in actually powering these things. So that's just a recent example that comes to mind. There are others, there's a logistics, huge logistics in transportation company who's using data science experience to optimize how the refrigeration of the storage units that are going all across the globe for transporting sort of food and other articles like that. How they can optimize the temperature of the goods that they're transporting, again to make sure that there's absolutely the minimum amount of wastage that occurs in the transportation process. But at the same time optimizing the cost that they incur, because all of that sort of shows up in the end product that you and I buy from retailers. >> Dave: And is there instrumentation in the field involved in that? Is that kind of a semi-IoT example? >> Absolutely, right, so in this case, actually both of these cases, in one case there are smart meters that are throwing out data every 15 minutes. In the other example of the logistics one, it is data that is almost streaming coming in. So in one case you can use batch processing, even though it's coming in at a 15 minute intervals, to predict out what you want to do. In the other case it's streaming data, which you want to analyze as it streams. >> Excellent, alright well exciting times here for you and your group. >> Absolutely >> Dave: Congratulations on getting the product out and getting it adopted. >> Thank you. >> Glad to see that. And thanks for coming on theCUBE. >> Manish: Thank you. Thanks for having me. >> Alright! >> Dave: Keep it right there everybody. Jim and I will be back, we're live from Munich, Germany, unscripted, bringing theCUBE to you. Bringing Fast Track Your Data. We'll be right back. (techno music)