>> Narrator: Live from Washington, D.C. It's the CUBE. Covering Boomi World 19. Brought to you by Boomi. >> Welcome to the CUBE, about the leader in live tech coverage. I am Lisa Martin with John Furrier. We're at Boomi World 19 in Washington, D.C. Please welcome one of Boomi's award winners to the program from Gilead Sciences we have the Director of IT, Murali Anakavur. Welcome Murali and congratulations on Gilead being the 2019 Change Agent Award winner for North America. >> Thank you so much Lisa. It's good to receive the award. Lot of efforts have been put in place by our folks. I'm very honored and privileged to receive this award. >> Fantastic. So give our audience an overview of Gilead Sciences. What you guys do and then we'll start getting into the IT infrastructure and all of the great things that you have done with Boomi. >> Definitely. Gilead has been in the forefront of meeting an aspect of medical needs of patients worldwide. Clearly, it's the company, if you recollect, solve the (mumbles) problem in the world. There were the cured from the cure for it that started the company originally to come up to where they are today. They are in the forefront of science and R and D and technology when putting therapeutics for inflammatory infectious, and recently in big cancer treatments and other treatments. So the world is opening up big time. Our focus is to resolve and make medical needs. The company is so focused and they want to provide the cure for all these and it's so passionately too. So all kinds of R and D going on. I'm so honored to be working for a company which is doing this great need for humanity, frankly. >> Absolutely. So the cure for Hepatitis C, that's huge. Whenever we talk about technology where it impacts every single person on this planet, infectious diseases, cancer as you mentioned, it's really... It's pulverizing people understand it. It's--there's a lot of gravity around it. Talk to us about what you needed to implement, from a technology infrastructure perspective, to connect all of these different data sources, so that the next cure for all these different diseases has a foundation from which providers can actually link data. >> Obviously. >> Talk about it. There are some backing sources company, any company needs, let's say ERP system, need some CRM system. Those are good. But our company has the complexity of manufacturing system that needs to make medicines. Company's complexity is the lab systems, R and D systems, product life cycle management systems where things originated in a little molecule for the compound they call it, and it expands into what they say clinical studies on a medicine. So you can imagine the plethora of system that make this happen. So what happens in this environment is now people bring up systems for what they need and ERP does what they need. All of the sudden, "I can't do without customer data." "I can't do without my patient data." "I can't do without my item data." "How do we get the data?" So it becomes--begs the question like, "Oh my gosh, okay we got all these complex systems in place, how are you going to share the data? Who's the master? Where's the source of truth? So all those sort of begging question is that, kind of start up the landscape of integration. So that's where we are. Launched that previous legacy systems for SOA that we have currently. Mostly call it the SD enterprise service. that shares data within the premises. Guess what today? They want, "Hey I've got this Cloud system that I'm accessing. I'm going to buy this sales force commercial systems that could enable me to launch my commerce market better. How do we deal with these guys? How do we reach out to those folks? How do I make my engagement app on the events for doctors? How do I connect with my patients? All these are big question that've been asked. There was a need for system that'll kind of take care of all these diverse platforms in the Cloud on Prim, connect them together, so the data sharing happens. That was the biggest challenge that we have kind of solve right now. And then with Boomi coming on to our platform since a couple of years from in the past, we have matured into a place where we're going to launch a lot of things on Boomi and we are looking forward to it eagerly to consolidate all those legacy innovation platforms into the Boomi world infrastructure. So i's exciting. >> Talk about the IT landscape in your company. What's going on there? How is the structure? What are some of the environment look like? Is it transforming the roles of the people? Stacking and wrecking, is it Cloud, Hybrid, what? Talk about your environment. >> Fantastic. I think the very question getting into our pillars or what we do in IT, right? Our pillars are very simple. First thing is core services, you've got to make it--keep the lights on you've got to sure things are working fine. The next thing we adhere to is people. Who do we need to make all this happen? ITs people, acknowledged management, retain people, the best talent, get the best talent. The third pillar we have is the enabling of technology. And that's where some of us come in to enables. How do we migrate Cloud? Let's say we have a big data platform on an infrastructure, adopt infrastructure, tear down infrastructure on-prem. And you what, it's a plan's base. So the data growth, it's enormous these days. So we are talking about Cloud. We are already have plans, we already have infrastructure in Cloud that we are moving to. So if you look at it, the company's so focused not only on technology which is required to, in this day and age, to talking about data, talking about expansion, elasticity and a computing power you need, yeah, here we are with opting we'll be multicloud recipient and beneficiary, but at the same time we're also focusing on people and the core services we provide as IT. IT is technical, non-technical-- >> So you have multiple Clouds right now? >> Exactly. >> Amazon, Azure. >> Yup, we will have a multi Cloud eventually. Not that everything is online and in perfection, but our plan is to have a multi Cloud strategy going forward because the amount of things that coming to our landscape. >> You're on classic hybrid right now, you've got it all on premises. >> Yes. >> Some Cloud going on. >> Absolutely, absolutely. >> So let's talk about business transformation, digital transformation. You did a great job of articulating the business challenge, the challenges that you needed to solve. From an IT perspective, you have all the hybrid multi Cloud environment. Where did the digital transformation initiative come from? Was it the business saying, "We have so much data and desperate systems. We want to be solving more real world problems. Hi, IT, help us build the foundation that allows that." >> It's fantastic. If you look at our company, our sheer full task is digital transformation. Not just IT or COO. CEO talks about our digital transformation. So everybody, in fact, it was questioned. "Hey, we want to be digital." What does it mean to be digital? Because thing comes up. So in the landscape of ITVR, we are going to be a digital-enabled company. We're going to define what it means. To me personally, digital-enabled means, "Hey, I need to share a piece of data across the landscape, whoever needs it, whenever they need it or where they need it." That's called the digital transformation if you ask me because that enables other systems to consume it, and then provide the care and attention it needs. Be at our customers. Customers are patients. Be at our hospitals that we work with. They're our customers. Employ our customers and turn that, it could be your portal. So we are attacking it from multiple points of view. You want to make sure the technology enablement moving forward in innovation. We care for all these areas of customers where we can really digitally enable them. So focus is not just one point of digitalization, it's customers and patients. How can we give them access? How can we get the feedback? All of them fall into 360 degrees of data enablement. It's so focused and we're so thrilled to have such (mumbles) that can pay a lot of attention to all these things. I think it'll be transforming our company a big time in the next few years with the digitalization that we're looking forward to. Mobile applications. All kinds of things are coming up. >> So why Boomi? Boomi is a Cloud native platform. We saw the video and if you saw that technical keynote this morning that the first videos started up with a few minutes of all the areas in which they were first. But they took this big bet back in 2007 when they were found that they are this single instance multi technic Cloud application. What differentiated Boomi when you guys were looking for the right partner with which is standardized? >> It's interesting because we like the Cloud part. Same time being (mumbles) country and industry, they said, " I can't (mumbles) put it on the Cloud." I mean this was about four years back. Remember, things were not really stable at that time. Or people are wondering, "What? Cloud?" "Where can I put my data?" We chose the Boomi hybrid model which is awesome because it gave us the benefit of both, of material that's in Cloud, I'm taking care of anything that you need to do material, I'm taking care of my processing on site. So that key was that bang say, "Oh wow, that's a fantastic option to have. It's a (mumbles) infrastructure. People can build things faster on Prim, run your case, data cases on Prim, but you have all Cloud metadatas protecting you (mumbles) Everything is easy, (mumbles) SHA. So all those were factors when we decided to go in to Boomi. But we see among others as full. But then the speed of market, less call framework, and also the roadmap they'll have for them. That's very important for us. I mean first thing in technology I want to go for next five years, ten years. Are you welcome with me in the technology? Are you making insights as we talked about today? (laughs) I'm just paraphrasing it. But those all things matter to us. In words, mine is protected. We don't end up with some debt, right? Like they model this platforms to be up to date. So those were our key factors in moving forward with Dell Boomi. >> And so let's talk about some of the business outcomes. You've mentioned a few. But let's look at them kind of categorically. If we look at kind of this over this polarizing industry, being able to study different aspect of man diseases and identify cures for them hopefully, what are some of the business outcomes that you guys are achieving so far with them. You're a Change Agent Award winner, so give us some of those really big wins that you've seen to dates? >> How to be proactive, right? It's a game, it's a data game these days. The more data you have aboard the decision you can make, you're going to differentiate in solving problems, and mean competitive as well. We are trying to see these aspects in the data that we can collect from all places. Now once you have the data, you need some kind of integration that needs to happen to process the data, to share the data to people who need them. That's why integration comes in. Obviously there are other areas where we do big data processing. We need to have some kind of a cluster to compute them and cue some analytics for scientist to see, "Hey, I've got this data. This was inference." And now we can introduce that integration to cue them all the data that they need. What does it take? In my opinion, days and months too can infer through these files and files of data, takes less than 10 minutes for people to now infer. >> Dramatic speed of (mumbles) here. Wow, elaborate on that a little bit. >> And what happens is when you get this huge epidemiology data on the world, you've got thousands and thousands tera bytes of data. Without proper computing and the resources and the modern platform, it's tough for you to count those data to come out with some analytic that people can use. You can ask queries like, "Hey, this disease happens in this area. Tell me the percentage that is relevant to this disease in this area that I need to concentrate on solving the problem." You want to solve big problems and you want to make sure the population benefits from that. So this kind of data gives you inferences that people can research on and say, "Hey, I'm going to focus on this area. It's very predominant." And let's say Africa nation, population is almost about 3 billion, 4 billion people in the world. So let's focus on that disease that gives some traction going on. And that's how you solve the world's problem, one by one, one step at a time. I'm so happy to be involved in that kind of enablement because I'm a very very minuscule part of the whole deal because we work with scientists who are fantastic, who are biologists, who are researchers. Our act in this helps them get to what they need to do. We are completely at their service for what they need and then we just want to enable things for them, make things faster, make the hope comes for them to an R and D, to be more clearer. So that's where we come in. It's more like a service, but industry aspect within the company, but then we are fully fortunate to work for a company that cures diseases and we are part of that journey that they're going through. >> You've just articulated beautifully why you guys won in the Change Agent category. Morally that was outstanding. Congratulations on what you've achieved so far. I'm sure, I'm excited to hear next year where the business goes. We appreciate your time. >> Thanks a lot, Lisa. Nice to talk to you guys today. >> Likewise, thank you. >> For John Furrier, I'm Lisa Martin. You're watching the CUBE from Boomi World 19. (lively music)

>> Live from San Francisco. It's theCUBE covering IBM Think 2019 brought to you by IBM. >> Welcome back everyone, this is the CUBE's live coverage in San Francisco at Moscone Center for IBM Think 2019. I'm John Furrier with Dave. Volante Dave it's been in AI, it's been cloud, it's been in data changing the game. We've got two great guests here Murali Nemani, CMO of ScienceLogic, your CEO has been on the CUBE before and Joe Damassa who is the VP of strategy and offerings for hybrid cloud service at IBM. Thanks for joining us. >> Welcome. >> Appreciate it. >> Thank you guys. >> Welcome to CUBE. So day four of four days coverage, yes, you can see the messaging settling the feedback settling, AI clearly front and center, role of data in that and then cloud scale across multiple capabilities. Obviously on premise multi cloud is existing already. Software's changing all this. >> Right. >> And so AI impacting operations is key. So how do you guys work together? What's the relationships in ScienceLogic and IBM? Could you just take a minute to explain that? >> I think I mean, clearly, as you talked about the hybrid nature of what we're dealing with, with the complexity of it, it's all going to be about the data. You know, software is great, but it's about software that collects the data, analyzes the data, and gives you the insights so you can actually automate and create value for our clients. So it's really this marriage, it's a technology but it's a technology that allows us to get access to the data so we can make change, it's all about the data. >> And so a lot of what IBM has been doing is building the analytics engines and Watson it's for them. Our partnership has been really building the data and the data lake and the real time aspects of collecting and preparing that data so that you can really get interesting outcomes out of it. So when you think about predictive models, when you think about the the way that data can be applied to doing things like anomaly detection that ultimately accelerate and automate operations. That's where the relationship really starts taking hold. >> So you guys are specialized in AIops and IT apparatus as that transforms with scale and data which you need machine running, you need a kind of gave it automation. >> Yes. >> And which is the devops use of operations is don't go down, right, up and running, high availability. >> Yeah. >> So on the cloud services side, talk about where the rubber is meeting the road from a customer standpoint, because the cultural shift from IT Service Management, IT operations has been this manual, some software here and there, but it's been a process. Older processes change a little bit, but this is a new game. Talk about how you guys are engaging the customers. >> Well, a part of it I mean, it's interesting when you step back and you stop breathing, you're on exhaust in terms of pushing what you're trying to sell and you listen to your customers what we're hearing is that they all understand the destination. They understand they're moving to the cloud, they understand the value that's going to bring, they're having a hard time getting started. It's how do I start the journey ? I've got all of this estate and traditional IT operations capabilities it's kind of move. How do I modernize it? How do I make it so it's portable across different environments. And so when you step back, you know, we basically said, hey, you need the portability of the platform. So what we're doing with Red Hat, what we're doing with IBM, cloud private, it creates that portable containerizing ability to take our existing workloads and start moving them, right. And then the other thing that the clients need are the services. Who's going to help me advise me on what workloads should move, which one shouldn't, most of the staff fails because you move the wrong things. How do you manage that? How do you build it? And then when you're done, and you've got this hybrid complex environment, how do we actually get insights to it and the data I need to operationalize it? How do I do IT apps, when I don't own everything within the four walls of my data set. >> Now, are you guys going to market together? You guys sell each other products, the relationship with ScienceLogic and IBM is it a partnership, is it a joint development? Can you explain a little bit more on how you guys work together? >> Well, we're one of the largest sort of services provider in the industry. So as we bring, our products, our technologies and our capabilities to market, we bring ScienceLogic into those deals, we use ScienceLogic in our services so that we can actually deliver the value to our clients. So it is sort of a co development, co joint partnership plus also our goal to market. >> So you use that as a tool to do discovery and identify the data that's in and the data that we're talking about is everything I need to know about my IT operations, my applications, the dependencies. Maybe you could describe a little bit more. >> Sure if you think about one of the things that Joe was mentioning is, today, the workloads are shifting, you're going from, let's say management performance monitoring and management platforms that you need to evolve from, to incorporate new technologies like containers and microservices and server-less architectures. That's one area of how did the tool sets fundamentally evolve to support the latest technologies that are being deployed? So think about that. Second is, how do you consolidate those set of tools now you're managing? Because you're adopting cloud based technologies or new capabilities, and so get consolidation there. And the third is, these workloads that are now migrating out of your private cloud or private data center into public clouds, right? And then that workload migration, I think it is Forrester level saying, about 20% of the total workloads are currently in some sort of a public cloud environments. So there's a lot of work to do in terms of getting to that tipping point of where workloads are now truly in a multi cloud hybrid cloud. So as IBM accelerates that transition and their core competencies in helping these large enterprises make that transition, you need a common manageable environment, that the common visibility across those workloads. So that's at the heart of what we're pulling, and then the data sets happened to be data sets that are coming either from the application layer, data coming from the log management systems, it could be data coming from a service desk in terms of the kind of CMDB based data sets, and we're building a data lake that ultimately allows you to see across these heterogeneous system. >> It could be service request to get that really touches the business process so you can now start to sort of map the value and how change is going to affect that value, right? >> Yeah, exactly. >> Yeah. >> I mean, what's interesting about ScienceLogic as a partner, it's the breadth of their platform in terms of the different things they can monitor, the depth, the ability to go into containers, and kind of understand what the applications are doing in them and the scale in terms of the types of devices. So when you think about, the types of devices, we're going to have to manage everything from, sensors in an Internet of Things, environment to routers, to sophisticated servers and applications that can be running anywhere, you need the flexibility of the platform that they have in order to be able to deliver that. >> And I think that's a key point when you talking about containers and Kubernetes, we heard your CEO Jeannie remitting mentioned Kubernetes, onstage like, that's great, good time(mumbles) I know no one like Kubernetes now it's mainstream. >> Yeah. >> So this is showing them what's going on the industry which is the on premise decomposition of on premise with cloud private, you guys have. >> Yes. >> Is giving them the ability to use containers to manage their existing stuff and do that work and then have the extension to cloud, public cloud or whatever public cloud. This gives them more mount modern capabilities. So the question is, this change the game we know that but how has it changed AIOps and what does it mean? So I guess the first question is, what is AIOps? And what is this new on premise with cloud private and full public cloud architecture look like in AIOps 2.0? >> So for me, it's a very simple definition. It's really using algorithmic mechanisms, right? Towards automating operations, right? It's a very simple way, simplistic way of looking at it. But ultimately, the end game is to automate operations because you need to move at the pace of business and machine speed. And if you want to go, move in machine speed, you can have, I mean, you can't throw enough humans at this problems, right? Because of the pace of change, the familiarity of the workloads spinning up and sitting down. We have a bank as a customer who turns up containers for every 90 seconds and then turn them down. Just can't keep that in that real time state of change and being able to understand the topological relationships between the application layer and the underlying infrastructure so that you can truly understand the service health because when an application degrades in performance, the biggest issue is a war room's scenario where everyone's saying, it's not me, it's not me and because everyone's green on their front, but it's now how do you get that connective tissue all the way running-- >> Well it's also not only the change, it's also the velocity of data coming off that exhaust or the changes and services is thrown off tons of data that you need machines now I mean, that's kind of the thing. >> Exactly, yeah. And I would add to that, I think part of the definition of AIOps is evolving. We know where we're coming from is more fit for purpose analytics, right? I have this problem, I'm the collect this data, I'm going to put these automations in place too address it. We need to kind of take it data Model approach that says, how do I ingest all of this data? You know, even at the start, when you're looking at which workloads and you're doing discovery and assessment of workloads, that data should go into a data lake that can be used later when you're actually doing the operations and management of those workloads. So what data do we collect at every stage of the migration and the transformation of it, and including the operational data? And then how do we put a form analytics on it, and then get the true insights? I think we're just scratching the surface of applying to AI, because it's all been very narrow cast, narrow focus, I have this problem, I collect this data, I can automate this server, it needs to move much beyond that to it... >> And services are turning up and on and off so fast as a non deterministic angle here, and you got state, non deterministic, I mean, those are hard technical computer science problems to solve >> Yeah. >> That's you don't just put a processor around say, oh, yeah. >> Well, let's back to the the scalability of the platform, the ability in real time to be monitoring and looking at that data and then doing something right. >> All right now, humans aren't completely removed from the equation, right? And so I'm interested in how the humans are digesting and visualizing all this data, especially at this speed there a visualization component? How does that all evolving? >> Yeah, I think that to me I mean, that's part of the biggest challenges. You humans are a, they have to be the ones that kind of analyze what's coming and say, what does this mean when you haven't already algorithmically built it into your automation technology, right? And then they also don't have to be the one to train, the system is doing to actually do it. So one of the things that were are that struggling with not struggling with, we're experimenting with is, how best to visualize this, right? We do some things now, we've got a hybrid cloud management platform, we're teaming with the product guys, and it's the ability to have four consoles. One from a consumption, how do I consume services from Amazon, IBM Cloud on premise, how do I deploy it? So in a Dev apps model, how do I fulfill that very quickly and operational councils, right, and then cost on asset management so you can actually have at glance say, oh, you know, I've got a big Hadoop cluster which been spun up, I'm paying $100,000 for it and it has zero utilization. So how do you visualize that so you can say oh, I'm need to put a rule in that if somebody's spinning something up on, you know, IBM Cloud and they're not using it, I either shut it down, or I sent messages out, right, for governance in top of it. So it's putting business rules and logic in terms, in addition to visualization to help automate. >> And Jeannie talked about this at our keynote efficiency versus innovation around how to manage and this is where the scale comes in. Because if you know that something's working, you want to to double down on it, you can then, kind of automate that away and then you just move someone, the humans to something else. This is where the AIOps I think it's going to be, I think, going to change the category. I mean, it's a Gartner Magic Quadrant for the IT operations. >> Right. >> AI potentially decimates that, I mean... >> Yeah, there's this argument that you know, you have these nice quadrants or let's say nicely defined market segments. You have the NPMD, the ITSM, the ITOM, you know, you have APM and so what's happening is in this world of AIOps, none of those D marks really fit anymore because you're seeing the convergence of that. And then the other transition that's happening is this movement from, you know, classic ops or Dev and a dev to Ops, Dev Ops and now dev sec Ops, you know, you're trying to get worlds to converge. And so when we talk about the data and being able to build data models, those data models need to converge across those domains. So a lot of the work we do is collect data sets from log management, from service desk and service management, from APM etc, and then build that data model in real time. So you can.... >> It kind of building an Uber or CMDB or I mean, right? (loud laughter) I mean, do most of your clients have a single CMDB? Probably not, right? >> Yeah. So this is sort of a new guidepost, isn't it? >> Yeah, a part of it is. There are these data puddles if you will, all right data exist in a lot of different places How do you bring them together so you can federate different data sources, different catalogs into a common platform because if a user is trying to decide, okay, should I spin this up on, you know, this environment or that one, you want the full catalog of capabilities that are on premise in your CMDB system with the legacy environment out of the catalogs that may exist on Amazon or Azure, etc and you want data across all that. >> It seems that everything's a data problem now. And datas are being embedded into the applications which are then the workflows are defining infrastructure, architecture, or are sole cloud, multi cloud, whatever the resource is, so we had JPMorgan Chase on top data geek on and she was talking about, we have models for the models and IBM has been talking about this concept of reasoning around the data. This is why I always like the cognition kind of angle of cognitive, because that's not just math, math is math, you do math on, you know, supervised machine learning and knowing processes to be efficient, but the cognition and the reasoning really helps get at that data set, right. So can you guys react to that? I mean, is everything a data problem? Is that how you should look at it and how does reasoning fit into all this? >> Well, I mean, that's back to your point about what is the humans role in this, right. So we're moving in a services business from primarily labor base with tools to make them more efficient to the technology doing the work. But the humans have to then say, when the technology get stumped, what does that mean? So should I build a new, how do I train it better? How do I, you know, take my domain expertise? How do I do the deep analytics to tell me all right, how do I solve those problems in the future? So the role changes I think Jenny talks about in terms of new collar workers. I mean, these are data scientists, these are people that understand the dynamics of the inner relationship of the different data, the data models that need to get built and they are guiding in effect the automation. >> I thought your CTO was on theCUBE talking about, Paul was talking about, you know, take the heavy and Rob Thomas was also on, the GM of the data plus AI team. I think he really nailed it. If you guys to take away the heavy lifting of the setup work then the data science who're actually there to do the reasoning or help assist in managing what's going on and putting guard rails around whatever business policy is. >> Today, I mean, we talked to in this about 79 percent I think it's a gardener stat of 79 percent of the data scientists. And these are these PhDs, they're highly valuable, spend their time collecting, preparing, cleansing those data models, right? So, you're now really applying that PhD level knowledge base towards solving a problem, you're just trying to make sense of the data. So one, do you have a holistic and a few? Two, is there a way to automate those things so you can then apply the human aspects towards the things that Joe was talking about. So that's a big part of what we're trying to come together in terms of the market for. >> Well guys thanks for the insight, thanks for coming on, great job. I think we talked for you know, an hour and on cultural shift because you mentioned the sets in here Ops and devs. It's a melting pot and it's a cultural shifts. I think that topic is worth following up on. But I'll let you guys just get a quick plug for you. I know you going to an event coming up and you got some work. You can talk about what you guys are doing. You got an event coming up, what your pitch, give a quick flag. >> Yeah, so we've got our symposium, which is our big user conference. It's in April. It's right in, it's on April 22 to 23rd to the 25th. It's in downtown Washington DC, Cherry Blossom festival season at the Ritz Carlton. And so a lot of that, we'll have theCUBE there as well. >> Yeah of course. >> So, we're looking forward to it. A lot of great energy to be carried over. >> We love going to the District. (laughs loudly) >> What don't we say, you guys are great, great to visit. So give the plugs with a service you're doing. Just give an update on what you guys are up to. >> Yeah, I think I mean, we're also we're investing the technology when we're full on board with the containerization, as we talked about, we're putting together a services portfolio. I think Jenny mentioned that we're taking a whole bunch of capability across IBM Global Technology Services, Global Business Services, and really coalescing into about, you know, 23 offerings to help customers advise on cloud, move to cloud build for cloud and manage on cloud and then you've seen the announcements here about what we're doing around the multi cloud management system. Those four console I talked about how do we help, you know, put a gearbox in place to manage the complexity of the hybrid nature that our customers are dealing with. >> It seems IBM got clear visibility on what's happening with cloud, cloud private, I think a really big announcement. I think it's not talked about in the show and I'll always kind of mentioned the key linchpin but you see cloud, multi cloud, hybrid cloud, you got AI and you got partnerships, ecosystem now its execution time, right? >> Yeah, exactly and, and frankly, that's the challenge, right? So we used to be able to manage it all on the four runs, right? Your SAP instances was in the data center, your servers were in the data center, your middleware is in the data center. Now I got my applications running in Salesforce.com often software as a service. I've got three or four different infrastructures of service providers. But I still have the legacy that I got to deal with. I mean the integration problems are just tremendous. >> Chairman VP of strategy at IBM hybrid cloud and Murali Nemani, CMO ScienceLogic, AI operations, bringing in hybrid clouds to theCUBE bringing all the coverage day four. I'm with Dave Volante, it's all about cloud AI developers all happening here in San Francisco this week. Stay with us from this short break. (upbeat music)

>> Narrator: Live from New York City, it's theCUBE. Covering IBM Data Science For All. Brought to you by IBM. >> Welcome back to New York here on theCUBE. Along with Dave Vellante, I'm John Walls. We're Data Science For All, IBM's two day event, and we'll be here all day long wrapping up again with that panel discussion from four to five here Eastern Time, so be sure to stick around all day here on theCUBE. Joining us now is Vikram Murali, who is a program director at IBM, and Vikram thank for joining us here on theCUBE. Good to see you. >> Good to see you too. Thanks for having me. >> You bet. So, among your primary responsibilities, The Data Science Experience. So first off, if you would, share with our viewers a little bit about that. You know, the primary mission. You've had two fairly significant announcements. Updates, if you will, here over the past month or so, so share some information about that too if you would. >> Sure, so my team, we build The Data Science Experience, and our goal is for us to enable data scientist, in their path, to gain insights into data using data science techniques, mission learning, the latest and greatest open source especially, and be able to do collaboration with fellow data scientist, with data engineers, business analyst, and it's all about freedom. Giving freedom to data scientist to pick the tool of their choice, and program and code in the language of their choice. So that's the mission of Data Science Experience, when we started this. The two releases, that you mentioned, that we had in the last 45 days. There was one in September and then there was one on October 30th. Both of these releases are very significant in the mission learning space especially. We now support Scikit-Learn, XGBoost, TensorFlow libraries in Data Science Experience. We have deep integration with Horton Data Platform, which is keymark of our partnership with Hortonworks. Something that we announced back in the summer, and this last release of Data Science Experience, two days back, specifically can do authentication with Technotes with Hadoop. So now our Hadoop customers, our Horton Data Platform customers, can leverage all the goodies that we have in Data Science Experience. It's more deeply integrated with our Hadoop based environments. >> A lot of people ask me, "Okay, when IBM announces a product like Data Science Experience... You know, IBM has a lot of products in its portfolio. Are they just sort of cobbling together? You know? So exulting older products, and putting a skin on them? Or are they developing them from scratch?" How can you help us understand that? >> That's a great question, and I hear that a lot from our customers as well. Data Science Experience started off as a design first methodology. And what I mean by that is we are using IBM design to lead the charge here along with the product and development. And we are actually talking to customers, to data scientist, to data engineers, to enterprises, and we are trying to find out what problems they have in data science today and how we can best address them. So it's not about taking older products and just re-skinning them, but Data Science Experience, for example, it started of as a brand new product: completely new slate with completely new code. Now, IBM has done data science and mission learning for a very long time. We have a lot of assets like SPSS Modeler and Stats, and digital optimization. And we are re-investing in those products, and we are investing in such a way, and doing product research in such a way, not to make the old fit with the new, but in a way where it fits into the realm of collaboration. How can data scientist leverage our existing products with open source, and how we can do collaboration. So it's not just re-skinning, but it's building ground up. >> So this is really important because you say architecturally it's built from the ground up. Because, you know, given enough time and enough money, you know, smart people, you can make anything work. So the reason why this is important is you mentioned, for instance, TensorFlow. You know that down the road there's going to be some other tooling, some other open source project that's going to take hold, and your customers are going to say, "I want that." You've got to then integrate that, or you have to choose whether or not to. If it's a super heavy lift, you might not be able to do it, or do it in time to hit the market. If you architected your system to be able to accommodate that. Future proof is the term everybody uses, so have you done? How have you done that? I'm sure API's are involved, but maybe you could add some color. >> Sure. So we are and our Data Science Experience and mission learning... It is a microservices based architecture, so we are completely dockerized, and we use Kubernetes under the covers for container dockerstration. And all these are tools that are used in The Valley, across different companies, and also in products across IBM as well. So some of these legacy products that you mentioned, we are actually using some of these newer methodologies to re-architect them, and we are dockerizing them, and the microservice architecture actually helps us address issues that we have today as well as be open to development and taking newer methodologies and frameworks into consideration that may not exist today. So the microservices architecture, for example, TensorFlow is something that you brought in. So we can just pin up a docker container just for TensorFlow and attach it to our existing Data Science Experience, and it just works. Same thing with other frameworks like XGBoost, and Kross, and Scikit-Learn, all these are frameworks and libraries that are coming up in open source within the last, I would say, a year, two years, three years timeframe. Previously, integrating them into our product would have been a nightmare. We would have had to re-architect our product every time something came, but now with the microservice architecture it is very easy for us to continue with those. >> We were just talking to Daniel Hernandez a little bit about the Hortonworks relationship at high level. One of the things that I've... I mean, I've been following Hortonworks since day one when Yahoo kind of spun them out. And know those guys pretty well. And they always make a big deal out of when they do partnerships, it's deep engineering integration. And so they're very proud of that, so I want to come on to test that a little bit. Can you share with our audience the kind of integrations you've done? What you've brought to the table? What Hortonworks brought to the table? >> Yes, so Data Science Experience today can work side by side with Horton Data Platform, HDP. And we could have actually made that work about two, three months back, but, as part of our partnership that was announced back in June, we set up drawing engineering teams. We have multiple touch points every day. We call it co-development, and they have put resources in. We have put resources in, and today, especially with the release that came out on October 30th, Data Science Experience can authenticate using secure notes. That I previously mentioned, and that was a direct example of our partnership with Hortonworks. So that is phase one. Phase two and phase three is going to be deeper integration, so we are planning on making Data Science Experience and a body management pact. And so a Hortonworks customer, if you have HDP already installed, you don't have to install DSX separately. It's going to be a management pack. You just spin it up. And the third phase is going to be... We're going to be using YARN for resource management. YARN is very good a resource management. And for infrastructure as a service for data scientist, we can actually delegate that work to YARN. So, Hortonworks, they are putting resources into YARN, doubling down actually. And they are making changes to YARN where it will act as the resource manager not only for the Hadoop and Spark workloads, but also for Data Science Experience workloads. So that is the level of deep engineering that we are engaged with Hortonworks. >> YARN stands for yet another resource negotiator. There you go for... >> John: Thank you. >> The trivia of the day. (laughing) Okay, so... But of course, Hortonworks are big on committers. And obviously a big committer to YARN. Probably wouldn't have YARN without Hortonworks. So you mentioned that's kind of what they're bringing to the table, and you guys primarily are focused on the integration as well as some other IBM IP? >> That is true as well as the notes piece that I mentioned. We have a notes commenter. We have multiple notes commenters on our side, and that helps us as well. So all the notes is part of the HDP package. We need knowledge on our side to work with Hortonworks developers to make sure that we are contributing and making end roads into Data Science Experience. That way the integration becomes a lot more easier. And from an IBM IP perspective... So Data Science Experience already comes with a lot of packages and libraries that are open source, but IBM research has worked on a lot of these libraries. I'll give you a few examples: Brunel and PixieDust is something that our developers love. These are visualization libraries that were actually cooked up by IBM research and the open sourced. And these are prepackaged into Data Science Experience, so there is IBM IP involved and there are a lot of algorithms, mission learning algorithms, that we put in there. So that comes right out of the package. >> And you guys, the development teams, are really both in The Valley? Is that right? Or are you really distributed around the world? >> Yeah, so we are. The Data Science Experience development team is in North America between The Valley and Toronto. The Hortonworks team, they are situated about eight miles from where we are in The Valley, so there's a lot of synergy. We work very closely with them, and that's what we see in the product. >> I mean, what impact does that have? Is it... You know, you hear today, "Oh, yeah. We're a virtual organization. We have people all over the world: Eastern Europe, Brazil." How much of an impact is that? To have people so physically proximate? >> I think it has major impact. I mean IBM is a global organization, so we do have teams around the world, and we work very well. With the invent of IP telephoning, and screen-shares, and so on, yes we work. But it really helps being in the same timezone, especially working with a partner just eight miles or ten miles a way. We have a lot of interaction with them and that really helps. >> Dave: Yeah. Body language? >> Yeah. >> Yeah. You talked about problems. You talked about issues. You know, customers. What are they now? Before it was like, "First off, I want to get more data." Now they've got more data. Is it figuring out what to do with it? Finding it? Having it available? Having it accessible? Making sense of it? I mean what's the barrier right now? >> The barrier, I think for data scientist... The number one barrier continues to be data. There's a lot of data out there. Lot of data being generated, and the data is dirty. It's not clean. So number one problem that data scientist have is how do I get to clean data, and how do I access data. There are so many data repositories, data lakes, and data swamps out there. Data scientist, they don't want to be in the business of finding out how do I access data. They want to have instant access to data, and-- >> Well if you would let me interrupt you. >> Yeah? >> You say it's dirty. Give me an example. >> So it's not structured data, so data scientist-- >> John: So unstructured versus structured? >> Unstructured versus structured. And if you look at all the social media feeds that are being generated, the amount of data that is being generated, it's all unstructured data. So we need to clean up the data, and the algorithms need structured data or data in a particular format. And data scientist don't want to spend too much time in cleaning up that data. And access to data, as I mentioned. And that's where Data Science Experience comes in. Out of the box we have so many connectors available. It's very easy for customers to bring in their own connectors as well, and you have instant access to data. And as part of our partnership with Hortonworks, you don't have to bring data into Data Science Experience. The data is becoming so big. You want to leave it where it is. Instead, push analytics down to where it is. And you can do that. We can connect to remote Spark. We can push analytics down through remote Spark. All of that is possible today with Data Science Experience. The second thing that I hear from data scientist is all the open source libraries. Every day there's a new one. It's a boon and a bane as well, and the problem with that is the open source community is very vibrant, and there a lot of data science competitions, mission learning competitions that are helping move this community forward. And it's a good thing. The bad thing is data scientist like to work in silos on their laptop. How do you, from an enterprise perspective... How do you take that, and how do you move it? Scale it to an enterprise level? And that's where Data Science Experience comes in because now we provide all the tools. The tools of your choice: open source or proprietary. You have it in here, and you can easily collaborate. You can do all the work that you need with open source packages, and libraries, bring your own, and as well as collaborate with other data scientist in the enterprise. >> So, you're talking about dirty data. I mean, with Hadoop and no schema on, right? We kind of knew this problem was coming. So technology sort of got us into this problem. Can technology help us get out of it? I mean, from an architectural standpoint. When you think about dirty data, can you architect things in to help? >> Yes. So, if you look at the mission learning pipeline, the pipeline starts with ingesting data and then cleansing or cleaning that data. And then you go into creating a model, training, picking a classifier, and so on. So we have tools built into Data Science Experience, and we're working on tools, that will be coming up and down our roadmap, which will help data scientist do that themselves. I mean, they don't have to be really in depth coders or developers to do that. Python is very powerful. You can do a lot of data wrangling in Python itself, so we are enabling data scientist to do that within the platform, within Data Science Experience. >> If I look at sort of the demographics of the development teams. We were talking about Hortonworks and you guys collaborating. What are they like? I mean people picture IBM, you know like this 100 plus year old company. What's the persona of the developers in your team? >> The persona? I would say we have a very young, agile development team, and by that I mean... So we've had six releases this year in Data Science Experience. Just for the on premises side of the product, and the cloud side of the product it's got huge delivery. We have releases coming out faster than we can code. And it's not just re-architecting it every time, but it's about adding features, giving features that our customers are asking for, and not making them wait for three months, six months, one year. So our releases are becoming a lot more frequent, and customers are loving it. And that is, in part, because of the team. The team is able to evolve. We are very agile, and we have an awesome team. That's all. It's an amazing team. >> But six releases in... >> Yes. We had immediate release in April, and since then we've had about five revisions of the release where we add lot more features to our existing releases. A lot more packages, libraries, functionality, and so on. >> So you know what monster you're creating now don't you? I mean, you know? (laughing) >> I know, we are setting expectation. >> You still have two months left in 2017. >> We do. >> We do not make frame release cycles. >> They are not, and that's the advantage of the microservices architecture. I mean, when you upgrade, a customer upgrades, right? They don't have to bring that entire system down to upgrade. You can target one particular part, one particular microservice. You componentize it, and just upgrade that particular microservice. It's become very simple, so... >> Well some of those microservices aren't so micro. >> Vikram: Yeah. Not. Yeah, so it's a balance. >> You're growing, but yeah. >> It's a balance you have to keep. Making sure that you componentize it in such a way that when you're doing an upgrade, it effects just one small piece of it, and you don't have to take everything down. >> Dave: Right. >> But, yeah, I agree with you. >> Well, it's been a busy year for you. To say the least, and I'm sure 2017-2018 is not going to slow down. So continue success. >> Vikram: Thank you. >> Wish you well with that. Vikram, thanks for being with us here on theCUBE. >> Thank you. Thanks for having me. >> You bet. >> Back with Data Science For All. Here in New York City, IBM. Coming up here on theCUBE right after this. >> Cameraman: You guys are clear. >> John: All right. That was great.