(upbeat techno music) >> Collibra is a company that was founded in 2008 right before the so-called modern big data era kicked into high gear. The company was one of the first to focus its business on data governance. Now, historically, data governance and data quality initiatives, they were back office functions, and they were largely confined to regulated industries that had to comply with public policy mandates. But as the cloud went mainstream the tech giants showed us how valuable data could become, and the value proposition for data quality and trust, it evolved from primarily a compliance driven issue, to becoming a linchpin of competitive advantage. But, data in the decade of the 2010s was largely about getting the technology to work. You had these highly centralized technical teams that were formed and they had hyper-specialized skills, to develop data architectures and processes, to serve the myriad data needs of organizations. And it resulted in a lot of frustration, with data initiatives for most organizations, that didn't have the resources of the cloud guys and the social media giants, to really attack their data problems and turn data into gold. This is why today, for example, there's quite a bit of momentum to re-thinking monolithic data architectures. You see, you hear about initiatives like Data Mesh and the idea of data as a product. They're gaining traction as a way to better serve the the data needs of decentralized business users. You hear a lot about data democratization. So these decentralization efforts around data, they're great, but they create a new set of problems. Specifically, how do you deliver, like a self-service infrastructure to business users and domain experts? Now the cloud is definitely helping with that but also, how do you automate governance? This becomes especially tricky as protecting data privacy has become more and more important. In other words, while it's enticing to experiment, and run fast and loose with data initiatives, kind of like the Wild West, to find new veins of gold, it has to be done responsibly. As such, the idea of data governance has had to evolve to become more automated and intelligent. Governance and data lineage is still fundamental to ensuring trust as data. It moves like water through an organization. No one is going to use data that is entrusted. Metadata has become increasingly important for data discovery and data classification. As data flows through an organization, the continuously ability to check for data flaws and automating that data quality, they become a functional requirement of any modern data management platform. And finally, data privacy has become a critical adjacency to cyber security. So you can see how data governance has evolved into a much richer set of capabilities than it was 10 or 15 years ago. Hello and welcome to theCUBE's coverage of Data Citizens made possible by Collibra, a leader in so-called Data intelligence and the host of Data Citizens 2022, which is taking place in San Diego. My name is Dave Vellante and I'm one of the hosts of our program which is running in parallel to Data Citizens. Now at theCUBE we like to say we extract the signal from the noise, and over the next couple of days we're going to feature some of the themes from the keynote speakers at Data Citizens, and we'll hear from several of the executives. Felix Van de Maele, who is the co-founder and CEO of Collibra, will join us. Along with one of the other founders of Collibra, Stan Christiaens, who's going to join my colleague Lisa Martin. I'm going to also sit down with Laura Sellers, she's the Chief Product Officer at Collibra. We'll talk about some of the the announcements and innovations they're making at the event, and then we'll dig in further to data quality with Kirk Haslbeck. He's the Vice President of Data Quality at Collibra. He's an amazingly smart dude who founded Owl DQ, a company that he sold to Collibra last year. Now, many companies they didn't make it through the Hadoop era, you know they missed the industry waves and they became driftwood. Collibra, on the other hand, has evolved its business, they've leveraged the cloud, expanded its product portfolio and leaned in heavily to some major partnerships with cloud providers as well as receiving a strategic investment from Snowflake, earlier this year. So, it's a really interesting story that we're thrilled to be sharing with you. Thanks for watching and I hope you enjoy the program. (upbeat rock music) Last year theCUBE covered Data Citizens, Collibra's customer event, and the premise that we put forth prior to that event was that despite all the innovation that's gone on over the last decade or more with data, you know starting with the Hadoop movement, we had Data lakes, we had Spark, the ascendancy of programming languages like Python, the introduction of frameworks like Tensorflow, the rise of AI, Low Code, No Code, et cetera. Businesses still find it's too difficult to get more value from their data initiatives, and we said at the time, you know maybe it's time to rethink data innovation. While a lot of the effort has been focused on, you more efficiently storing and processing data, perhaps more energy needs to go into thinking about the people and the process side of the equation. Meaning, making it easier for domain experts to both gain insights from data, trust the data, and begin to use that data in new ways, fueling data products, monetization, and insights. Data Citizens 2022 is back and we're pleased to have Felix Van de Maele who is the founder and CEO of Collibra. He's on theCUBE. We're excited to have you Felix. Good to see you again. >> Likewise Dave. Thanks for having me again. >> You bet. All right, we're going to get the update from Felix on the current data landscape, how he sees it why data intelligence is more important now than ever, and get current on what Collibra has been up to over the past year, and what's changed since Data citizens 2021, and we may even touch on some of the product news. So Felix, we're living in a very different world today with businesses and consumers. They're struggling with things like supply chains, uncertain economic trends and we're not just snapping back to the 2010s, that's clear, and that's really true as well in the world of data. So what's different in your mind, in the data landscape of the 2020s, from the previous decade, and what challenges does that bring for your customers? >> Yeah, absolutely, and and I think you said it well, Dave and the intro that, that rising complexity and fragmentation, in the broader data landscape, that hasn't gotten any better over the last couple of years. When when we talk to our customers, that level of fragmentation, the complexity, how do we find data that we can trust, that we know we can use, has only gotten more more difficult. So that trend that's continuing, I think what is changing is that trend has become much more acute. Well, the other thing we've seen over the last couple of years is that the level of scrutiny that organizations are under, respect to data, as data becomes more mission critical, as data becomes more impactful than important, the level of scrutiny with respect to privacy, security, regulatory compliance, as only increasing as well. Which again, is really difficult in this environment of continuous innovation, continuous change, continuous growing complexity, and fragmentation. So, it's become much more acute. And to your earlier point, we do live in a different world and and the past couple of years we could probably just kind of brute force it, right? We could focus on, on the top line, there was enough kind of investments to be, to be had. I think nowadays organizations are focused or are, are, are are, are, are in a very different environment where there's much more focus on cost control, productivity, efficiency, how do we truly get the value from that data? So again, I think it just another incentive for organization to now truly look at data and to scale with data, not just from a a technology and infrastructure perspective, but how do we actually scale data from an organizational perspective, right? You said at the, the people and process, how do we do that at scale? And that's only, only, only becoming much more important, and we do believe that the, the economic environment that we find ourselves in today is going to be catalyst for organizations to really take that more seriously if, if, if you will, than they maybe have in the have in the past. >> You know, I don't know when you guys founded Collibra, if you had a sense as to how complicated it was going to get, but you've been on a mission to really address these problems from the beginning. How would you describe your, your, your mission and what are you doing to address these challenges? >> Yeah, absolutely. We, we started Collibra in 2008. So, in some sense and the, the last kind of financial crisis and that was really the, the start of Collibra, where we found product market fit, working with large financial institutions to help them cope with the increasing compliance requirements that they were faced with because of the, of the financial crisis. And kind of here we are again, in a very different environment of course 15 years, almost 15 years later, but data only becoming more important. But our mission to deliver trusted data for every user, every use case and across every source, frankly, has only become more important. So, what has been an incredible journey over the last 14, 15 years, I think we're still relatively early in our mission to again, be able to provide everyone, and that's why we call it Data Citizens, we truly believe that everyone in the organization should be able to use trusted data in an easy, easy matter. That mission is is only becoming more important, more relevant. We definitely have a lot more work ahead of us because we still relatively early in that, in that journey. >> Well that's interesting, because you know, in my observation it takes 7 to 10 years to actually build a company, and then the fact that you're still in the early days is kind of interesting. I mean, you, Collibra's had a good 12 months or so since we last spoke at Data Citizens. Give us the latest update on your business. What do people need to know about your current momentum? >> Yeah, absolutely. Again, there's a lot of tailwind organizations that are only maturing their data practices and we've seen that kind of transform or influence a lot of our business growth that we've seen, broader adoption of the platform. We work at some of the largest organizations in the world with its Adobe, Heineken, Bank of America and many more. We have now over 600 enterprise customers, all industry leaders and every single vertical. So it's, it's really exciting to see that and continue to partner with those organizations. On the partnership side, again, a lot of momentum in the org in the, in the market with some of the cloud partners like Google, Amazon, Snowflake, Data Breaks, and and others, right? As those kind of new modern data infrastructures, modern data architectures, are definitely all moving to the cloud. A great opportunity for us, our partners, and of course our customers, to help them kind of transition to the cloud even faster. And so we see a lot of excitement and momentum there. We did an acquisition about 18 months ago around data quality, data observability, which we believe is an enormous opportunity. Of course data quality isn't new but I think there's a lot of reasons why we're so excited about quality and observability now. One, is around leveraging AI machine learning again to drive more automation. And a second is that those data pipelines, that are now being created in the cloud, in these modern data architecture, architectures, they've become mission critical. They've become real time. And so monitoring, observing those data pipelines continuously, has become absolutely critical so that they're really excited about, about that as well. And on the organizational side, I'm sure you've heard the term around kind of data mesh, something that's gaining a lot of momentum, rightfully so. It's really the type of governance that we always believed in. Federated, focused on domains, giving a lot of ownership to different teams. I think that's the way to scale data organizations, and so that aligns really well with our vision and from a product perspective, we've seen a lot of momentum with our customers there as well. >> Yeah, you know, a couple things there. I mean, the acquisition of OwlDQ, you know Kirk Haslbeck and, and their team. It's interesting, you know the whole data quality used to be this back office function and and really confined to highly regulated industries. It's come to the front office, it's top of mind for Chief Data Officers. Data mesh, you mentioned you guys are a connective tissue for all these different nodes on the data mesh. That's key. And of course we see you at all the shows. You're, you're a critical part of many ecosystems and you're developing your own ecosystem. So, let's chat a little bit about the, the products. We're going to go deeper into products later on, at Data Citizens 22, but we know you're debuting some, some new innovations, you know, whether it's, you know, the the under the covers in security, sort of making data more accessible for people, just dealing with workflows and processes, as you talked about earlier. Tell us a little bit about what you're introducing. >> Yeah, absolutely. We we're super excited, a ton of innovation. And if we think about the big theme and like, like I said, we're still relatively early in this, in this journey towards kind of that mission of data intelligence that really bolts and compelling mission. Either customers are still start, are just starting on that, on that journey. We want to make it as easy as possible for the, for organization to actually get started, because we know that's important that they do. And for our organization and customers, that have been with us for some time, there's still a tremendous amount of opportunity to kind of expand the platform further. And again to make it easier for, really to, to accomplish that mission and vision around that Data Citizen, that everyone has access to trustworthy data in a very easy, easy way. So that's really the theme of a lot of the innovation that we're driving, a lot of kind of ease of adoption, ease of use, but also then, how do we make sure that, as clear becomes this kind of mission critical enterprise platform, from a security performance, architecture scale supportability, that we're truly able to deliver that kind of an enterprise mission critical platform. And so that's the big theme. From an innovation perspective, from a product perspective, a lot of new innovation that we're really excited about. A couple of highlights. One, is around data marketplace. Again, a lot of our customers have plans in that direction, How to make it easy? How do we make How do we make available to true kind of shopping experience? So that anybody in the organization can, in a very easy search first way, find the right data product, find the right dataset, that they can then consume. Usage analytics, how do you, how do we help organizations drive adoption? Tell them where they're working really well and where they have opportunities. Homepages again to, to make things easy for, for people, for anyone in your organization, to kind of get started with Collibra. You mentioned Workflow Designer, again, we have a very powerful enterprise platform, one of our key differentiators is the ability to really drive a lot of automation through workflows. And now we provided a, a new Low-Code, No-Code kind of workflow designer experience. So, so really customers can take it to the next level. There's a lot more new product around Collibra protect, which in partnership with Snowflake, which has been a strategic investor in Collibra, focused on how do we make access governance easier? How do we, how do we, how are we able to make sure that as you move to the cloud, things like access management, masking around sensitive data, PIA data, is managed as a much more effective, effective rate. Really excited about that product. There's more around data quality. Again, how do we, how do we get that deployed as easily, and quickly, and widely as we can? Moving that to the cloud has been a big part of our strategy. So, we launch our data quality cloud product, as well as making use of those, those native compute capabilities and platforms, like Snowflake, Databricks, Google, Amazon, and others. And so we are bettering a capability, a capability that we call push down, so we're actually pushing down the computer and data quality, to monitoring into the underlying platform, which again from a scale performance and ease of use perspective, is going to make a massive difference. And then more broadly, we talked a little bit about the ecosystem. Again, integrations, we talk about being able to connect to every source. Integrations are absolutely critical, and we're really excited to deliver new integrations with Snowflake, Azure and Google Cloud storage as well. So that's a lot coming out, the team has been work, at work really hard, and we are really really excited about what we are coming, what we're bringing to market. >> Yeah, a lot going on there. I wonder if you could give us your, your closing thoughts. I mean, you you talked about, you know, the marketplace, you know you think about Data Mesh, you think of data as product, one of the key principles, you think about monetization. This is really different than what we've been used to in data, which is just getting the technology to work has been, been so hard. So, how do you see sort of the future and, you know give us the, your closing thoughts please? >> Yeah, absolutely. And, and I think we we're really at a pivotal moment and I think you said it well. We, we all know the constraint and the challenges with data, how to actually do data at scale. And while we've seen a ton of innovation on the infrastructure side, we fundamentally believe that just getting a faster database is important, but it's not going to fully solve the challenges and truly kind of deliver on the opportunity. And that's why now is really the time to, deliver this data intelligence vision, this data intelligence platform. We are still early, making it as easy as we can, as kind of our, as our mission. And so I'm really, really excited to see what we, what we are going to, how the marks are going to evolve over the next, next few quarters and years. I think the trend is clearly there. We talked about Data Mesh, this kind of federated approach focus on data products, is just another signal that we believe, that a lot of our organization are now at the time, they're understanding need to go beyond just the technology. I really, really think about how to actually scale data as a business function, just like we've done with IT, with HR, with sales and marketing, with finance. That's how we need to think about data. I think now is the time, given the economic environment that we are in, much more focus on control, much more focus on productivity, efficiency, and now is the time we need to look beyond just the technology and infrastructure to think of how to scale data, how to manage data at scale. >> Yeah, it's a new era. The next 10 years of data won't be like the last, as I always say. Felix, thanks so much. Good luck in, in San Diego. I know you're going to crush it out there. >> Thank you Dave. >> Yeah, it's a great spot for an in-person event and and of course the content post-event is going to be available at collibra.com and you can of course catch theCUBE coverage at theCUBE.net and all the news at siliconangle.com. This is Dave Vellante for theCUBE, your leader in enterprise and emerging tech coverage. (upbeat techno music)

(atmospheric music) >> Welcome to theCUBE Coverage of Data Citizens 2022 Collibra's Customer event. My name is Dave Vellante. With us is Kirk Haslbeck, who's the Vice President of Data Quality of Collibra. Kirk, good to see you, welcome. >> Thanks for having me, Dave. Excited to be here. >> You bet. Okay, we're going to discuss data quality, observability. It's a hot trend right now. You founded a data quality company, OwlDQ, and it was acquired by Collibra last year. Congratulations. And now you lead data quality at Collibra. So we're hearing a lot about data quality right now. Why is it such a priority? Take us through your thoughts on that. >> Yeah, absolutely. It's definitely exciting times for data quality which you're right, has been around for a long time. So why now? And why is it so much more exciting than it used to be? I think it's a bit stale, but we all know that companies use more data than ever before, and the variety has changed and the volume has grown. And while I think that remains true there are a couple other hidden factors at play that everyone's so interested in as to why this is becoming so important now. And I guess you could kind of break this down simply and think about if Dave you and I were going to build a new healthcare application and monitor the heartbeat of individuals, imagine if we get that wrong, what the ramifications could be, what those incidents would look like. Or maybe better yet, we try to build a new trading algorithm with a crossover strategy where the 50 day crosses the 10 day average. And imagine if the data underlying the inputs to that is incorrect. We will probably have major financial ramifications in that sense. So, kind of starts there, where everybody's realizing that we're all data companies, and if we are using bad data we're likely making incorrect business decisions. But I think there's kind of two other things at play. I bought a car not too long ago and my dad called and said, "How many cylinders does it have?" And I realized in that moment, I might have failed him cause I didn't know. And I used to ask those types of questions about any lock breaks and cylinders, and if it's manual or automatic. And I realized, I now just buy a car that I hope works. And it's so complicated with all the computer chips. I really don't know that much about it. And that's what's happening with data. We're just loading so much of it. And it's so complex that the way companies consume them in the IT function is that they bring in a lot of data and then they syndicate it out to the business. And it turns out that the individuals loading and consuming all of this data for the company actually may not know that much about the data itself and that's not even their job anymore. So, we'll talk more about that in a minute, but that's really what's setting the foreground for this observability play and why everybody's so interested. It's because we're becoming less close to the intricacies of the data and we just expect it to always be there and be correct. >> You know, the other thing too about data quality, and for years we did the MIT, CDO, IQ event. We didn't do it last year at COVID, messed everything up. But the observation I would make there, your thoughts is, data quality used to be information quality, used to be this back office function, and then it became sort of front office with financial services, and government and healthcare, these highly regulated industries. And then the whole chief data officer thing happened and people were realizing, well they sort of flipped the bit from sort of a data as a risk to data as an asset. And now as we say, we're going to talk about observability. And so it's really become front and center, just the whole quality issue because data's so fundamental, hasn't it? >> Yeah, absolutely. I mean, let's imagine we pull up our phones right now and I go to my favorite stock ticker app, and I check out the Nasdaq market cap. I really have no idea if that's the correct number. I know it's a number, it looks large, it's in a numeric field. And that's kind of what's going on. There's so many numbers and they're coming from all of these different sources, and data providers, and they're getting consumed and passed along. But there isn't really a way to tactically put controls on every number and metric across every field we plan to monitor, but with the scale that we've achieved in early days, even before Collibra. And what's been so exciting is, we have these types of observation techniques, these data monitors that can actually track past performance of every field at scale. And why that's so interesting, and why I think the CDO is listening right intently nowadays to this topic is, so maybe we could surface all of these problems with the right solution of data observability and with the right scale, and then just be alerted on breaking trends. So we're sort of shifting away from this world of must write a condition and then when that condition breaks that was always known as a break record. But what about breaking trends and root cause analysis? And is it possible to do that with less human intervention? And so I think most people are seeing now that it's going to have to be a software tool and a computer system. It's not ever going to be based on one or two domain experts anymore. >> So how does data observability relate to data quality? Are they sort of two sides of the same coin? Are they cousins? What's your perspective on that? >> Yeah, it's super interesting. It's an emerging market. So the language is changing, a lot of the topic and areas changing. The way that I like to say it or break it down because the lingo is constantly moving, as a target on the space is really breaking records versus breaking trends. And I could write a condition when this thing happens it's wrong, and when it doesn't it's correct. Or I could look for a trend and I'll give you a good example. Everybody's talking about fresh data and stale data, and why would that matter? Well, if your data never arrived, or only part of it arrived, or didn't arrive on time, it's likely stale, and there will not be a condition that you could write that would show you all the good and the bads. That was kind of your traditional approach of data quality break records. But your modern day approach is you lost a significant portion of your data, or it did not arrive on time to make that decision accurately on time. And that's a hidden concern. Some people call this freshness, we call it stale data. But it all points to the same idea of the thing that you're observing may not be a data quality condition anymore. It may be a breakdown in the data pipeline. And with thousands of data pipelines in play for every company out there, there's more than a couple of these happening every day. >> So what's the Collibra angle on all this stuff? Made the acquisition, you got data quality, observability coming together. You guys have a lot of expertise in this area, but you hear providence of data. You just talked about stale data, the whole trend toward realtime. How is Collibra approaching the problem and what's unique about your approach? >> Well I think where we're fortunate is with our background. Myself and team, we sort of lived this problem for a long time in the Wall Street days about a decade ago. And we saw it from many different angles. And what we came up with, before it was called data observability or reliability, was basically the underpinnings of that. So we're a little bit ahead of the curve there when most people evaluate our solution. It's more advanced than some of the observation techniques that currently exist. But we've also always covered data quality and we believe that people want to know more, they need more insights. And they want to see break records and breaking trends together, so they can correlate the root cause. And we hear that all the time. "I have so many things going wrong just show me the big picture. Help me find the thing that if I were to fix it today would make the most impact." So we're really focused on root cause analysis, business impact, connecting it with lineage and catalog metadata. And as that grows you can actually achieve total data governance. At this point with the acquisition of what was a Lineage company years ago, and then my company OwlDQ, now Collibra Data Quality. Collibra may be the best positioned for total data governance and intelligence in the space. >> Well, you mentioned financial services a couple of times and some examples, remember the flash crash in 2010. Nobody had any idea what that was. They would just say, "Oh, it's a glitch." So they didn't understand the root cause of it. So this is a really interesting topic to me. So we know at Data Citizens 22 that you're announcing, you got to announce new products, right? It is your yearly event. What's new? Give us a sense as to what products are coming out but specifically around data quality and observability. >> Absolutely. There's this, there's always a next thing on the forefront. And the one right now is these hyperscalers in the cloud. So you have databases like Snowflake and BigQuery, and Databricks, Delta Lake and SQL Pushdown. And ultimately what that means is a lot of people are storing in loading data even faster in a SaaS like model. And we've started to hook into these databases, and while we've always worked with the same databases in the past they're supported today. We're doing something called Native Database pushdown, where the entire compute and data activity happens in the database. And why that is so interesting and powerful now? Is everyone's concerned with something called Egress. Did my data that I've spent all this time and money with my security team securing ever leave my hands, did it ever leave my secure VPC as they call it? And with these native integrations that we're building and about to unveil here as kind of a sneak peak for next week at Data Citizens, we're now doing all compute and data operations in databases like Snowflake. And what that means is with no install and no configuration you could log into the Collibra data quality app and have all of your data quality running inside the database that you've probably already picked as your go forward team selection secured database of choice. So we're really excited about that. And I think if you look at the whole landscape of network cost, egress cost, data storage and compute, what people are realizing is it's extremely efficient to do it in the way that we're about to release here next week. >> So this is interesting because what you just described, you mentioned Snowflake, you mentioned Google, oh actually you mentioned yeah, Databricks. You know, Snowflake has the data cloud. If you put everything in the data cloud, okay, you're cool. But then Google's got the open data cloud. If you heard, Google next. And now Databricks doesn't call it the data cloud, but they have like the open source data cloud. So you have all these different approaches and there's really no way, up until now I'm hearing, to really understand the relationships between all those and have confidence across, it's like yamarket AMI, you should just be a note on the mesh. I don't care if it's a data warehouse or a data lake, or where it comes from, but it's a point on that mesh and I need tooling to be able to have confidence that my data is governed and has the proper lineage, providence. And that's what you're bringing to the table. Is that right? Did I get that right? >> Yeah, that's right. And it's, for us, it's not that we haven't been working with those great cloud databases, but it's the fact that we can send them the instructions now we can send them the operating ability to crunch all of the calculations, the governance, the quality, and get the answers. And what that's doing, it's basically zero network cost, zero egress cost, zero latency of time. And so when you were to log into BigQuery tomorrow using our tool, or say Snowflake for example, you have instant data quality metrics, instant profiling, instant lineage in access, privacy controls, things of that nature that just become less onerous. What we're seeing is there's so much technology out there just like all of the major brands that you mentioned but how do we make it easier? The future is about less clicks, faster time to value, faster scale, and eventually lower cost. And we think that this positions us to be the leader there. >> I love this example because, we've got talks about well the cloud guys you're going to own the world. And of course now we're seeing that the ecosystem is finding so much white space to add value connect across cloud. Sometimes we call it super cloud and so, or inter clouding. Alright, Kirk, give us your final thoughts on the trends that we've talked about and data Citizens 22. >> Absolutely. Well I think, one big trend is discovery and classification. Seeing that across the board, people used to know it was a zip code and nowadays with the amount of data that's out there they want to know where everything is, where their sensitive data is, if it's redundant, tell me everything inside of three to five seconds. And with that comes, they want to know in all of these hyperscale databases how fast they can get controls and insights out of their tools. So I think we're going to see more one click solutions, more SaaS based solutions, and solutions that hopefully prove faster time to value on all of these modern cloud platforms. >> Excellent. All right, Kirk Haslbeck, thanks so much for coming on theCUBE and previewing Data Citizens 22. Appreciate it. >> Thanks for having me, Dave. >> You're welcome. All right. And thank you for watching. Keep it right there for more coverage from theCUBE. (atmospheric music)

(bright upbeat music) >> Welcome to theCUBE's Coverage of Data Citizens 2022 Collibra's Customer event. My name is Dave Vellante. With us is Kirk Hasselbeck, who's the Vice President of Data Quality of Collibra. Kirk, good to see you. Welcome. >> Thanks for having me, Dave. Excited to be here. >> You bet. Okay, we're going to discuss data quality, observability. It's a hot trend right now. You founded a data quality company, OwlDQ and it was acquired by Collibra last year. Congratulations! And now you lead data quality at Collibra. So we're hearing a lot about data quality right now. Why is it such a priority? Take us through your thoughts on that. >> Yeah, absolutely. It's definitely exciting times for data quality which you're right, has been around for a long time. So why now, and why is it so much more exciting than it used to be? I think it's a bit stale, but we all know that companies use more data than ever before and the variety has changed and the volume has grown. And while I think that remains true, there are a couple other hidden factors at play that everyone's so interested in as to why this is becoming so important now. And I guess you could kind of break this down simply and think about if Dave, you and I were going to build, you know a new healthcare application and monitor the heartbeat of individuals, imagine if we get that wrong, what the ramifications could be? What those incidents would look like? Or maybe better yet, we try to build a new trading algorithm with a crossover strategy where the 50 day crosses the 10 day average. And imagine if the data underlying the inputs to that is incorrect. We'll probably have major financial ramifications in that sense. So, it kind of starts there where everybody's realizing that we're all data companies and if we are using bad data, we're likely making incorrect business decisions. But I think there's kind of two other things at play. I bought a car not too long ago and my dad called and said, "How many cylinders does it have?" And I realized in that moment, I might have failed him because 'cause I didn't know. And I used to ask those types of questions about any lock brakes and cylinders and if it's manual or automatic and I realized I now just buy a car that I hope works. And it's so complicated with all the computer chips. I really don't know that much about it. And that's what's happening with data. We're just loading so much of it. And it's so complex that the way companies consume them in the IT function is that they bring in a lot of data and then they syndicate it out to the business. And it turns out that the individuals loading and consuming all of this data for the company actually may not know that much about the data itself and that's not even their job anymore. So, we'll talk more about that in a minute but that's really what's setting the foreground for this observability play and why everybody's so interested, it's because we're becoming less close to the intricacies of the data and we just expect it to always be there and be correct. >> You know, the other thing too about data quality and for years we did the MIT CDOIQ event we didn't do it last year at COVID, messed everything up. But the observation I would make there love thoughts is it data quality used to be information quality used to be this back office function, and then it became sort of front office with financial services and government and healthcare, these highly regulated industries. And then the whole chief data officer thing happened and people were realizing, well, they sort of flipped the bit from sort of a data as a a risk to data as an asset. And now, as we say, we're going to talk about observability. And so it's really become front and center, just the whole quality issue because data's fundamental, hasn't it? >> Yeah, absolutely. I mean, let's imagine we pull up our phones right now and I go to my favorite stock ticker app and I check out the NASDAQ market cap. I really have no idea if that's the correct number. I know it's a number, it looks large, it's in a numeric field. And that's kind of what's going on. There's so many numbers and they're coming from all of these different sources and data providers and they're getting consumed and passed along. But there isn't really a way to tactically put controls on every number and metric across every field we plan to monitor. But with the scale that we've achieved in early days, even before Collibra. And what's been so exciting is we have these types of observation techniques, these data monitors that can actually track past performance of every field at scale. And why that's so interesting and why I think the CDO is listening right intently nowadays to this topic is so maybe we could surface all of these problems with the right solution of data observability and with the right scale and then just be alerted on breaking trends. So we're sort of shifting away from this world of must write a condition and then when that condition breaks, that was always known as a break record. But what about breaking trends and root cause analysis? And is it possible to do that, with less human intervention? And so I think most people are seeing now that it's going to have to be a software tool and a computer system. It's not ever going to be based on one or two domain experts anymore. >> So, how does data observability relate to data quality? Are they sort of two sides of the same coin? Are they cousins? What's your perspective on that? >> Yeah, it's super interesting. It's an emerging market. So the language is changing a lot of the topic and areas changing the way that I like to say it or break it down because the lingo is constantly moving as a target on this space is really breaking records versus breaking trends. And I could write a condition when this thing happens it's wrong and when it doesn't, it's correct. Or I could look for a trend and I'll give you a good example. Everybody's talking about fresh data and stale data and why would that matter? Well, if your data never arrived or only part of it arrived or didn't arrive on time, it's likely stale and there will not be a condition that you could write that would show you all the good and the bads. That was kind of your traditional approach of data quality break records. But your modern day approach is you lost a significant portion of your data, or it did not arrive on time to make that decision accurately on time. And that's a hidden concern. Some people call this freshness, we call it stale data but it all points to the same idea of the thing that you're observing may not be a data quality condition anymore. It may be a breakdown in the data pipeline. And with thousands of data pipelines in play for every company out there there, there's more than a couple of these happening every day. >> So what's the Collibra angle on all this stuff made the acquisition you got data quality observability coming together, you guys have a lot of expertise in this area but you hear providence of data you just talked about stale data, the whole trend toward real time. How is Collibra approaching the problem and what's unique about your approach? >> Well, I think where we're fortunate is with our background, myself and team we sort of lived this problem for a long time in the Wall Street days about a decade ago. And we saw it from many different angles. And what we came up with before it was called data observability or reliability was basically the underpinnings of that. So we're a little bit ahead of the curve there when most people evaluate our solution. It's more advanced than some of the observation techniques that currently exist. But we've also always covered data quality and we believe that people want to know more, they need more insights and they want to see break records and breaking trends together so they can correlate the root cause. And we hear that all the time. I have so many things going wrong just show me the big picture. Help me find the thing that if I were to fix it today would make the most impact. So we're really focused on root cause analysis, business impact connecting it with lineage and catalog, metadata. And as that grows, you can actually achieve total data governance. At this point, with the acquisition of what was a lineage company years ago and then my company OwlDQ, now Collibra Data Quality, Collibra may be the best positioned for total data governance and intelligence in the space. >> Well, you mentioned financial services a couple of times and some examples, remember the flash crash in 2010. Nobody had any idea what that was, they just said, "Oh, it's a glitch." So they didn't understand the root cause of it. So this is a really interesting topic to me. So we know at Data Citizens '22 that you're announcing you got to announce new products, right? Your yearly event, what's new? Give us a sense as to what products are coming out but specifically around data quality and observability. >> Absolutely. There's always a next thing on the forefront. And the one right now is these hyperscalers in the cloud. So you have databases like Snowflake and Big Query and Data Bricks, Delta Lake and SQL Pushdown. And ultimately what that means is a lot of people are storing in loading data even faster in a salike model. And we've started to hook in to these databases. And while we've always worked with the same databases in the past they're supported today we're doing something called Native Database pushdown, where the entire compute and data activity happens in the database. And why that is so interesting and powerful now is everyone's concerned with something called Egress. Did my data that I've spent all this time and money with my security team securing ever leave my hands? Did it ever leave my secure VPC as they call it? And with these native integrations that we're building and about to unveil here as kind of a sneak peek for next week at Data Citizens, we're now doing all compute and data operations in databases like Snowflake. And what that means is with no install and no configuration you could log into the Collibra Data Quality app and have all of your data quality running inside the database that you've probably already picked as your your go forward team selection secured database of choice. So we're really excited about that. And I think if you look at the whole landscape of network cost, egress cost, data storage and compute, what people are realizing is it's extremely efficient to do it in the way that we're about to release here next week. >> So this is interesting because what you just described you mentioned Snowflake, you mentioned Google, oh actually you mentioned yeah, the Data Bricks. Snowflake has the data cloud. If you put everything in the data cloud, okay, you're cool but then Google's got the open data cloud. If you heard Google Nest and now Data Bricks doesn't call it the data cloud but they have like the open source data cloud. So you have all these different approaches and there's really no way up until now I'm hearing to really understand the relationships between all those and have confidence across, it's like (indistinct) you should just be a note on the mesh. And I don't care if it's a data warehouse or a data lake or where it comes from, but it's a point on that mesh and I need tooling to be able to have confidence that my data is governed and has the proper lineage, providence. And that's what you're bringing to the table. Is that right? Did I get that right? >> Yeah, that's right. And for us, it's not that we haven't been working with those great cloud databases, but it's the fact that we can send them the instructions now we can send them the operating ability to crunch all of the calculations, the governance, the quality and get the answers. And what that's doing, it's basically zero network cost, zero egress cost, zero latency of time. And so when you were to log into Big BigQuery tomorrow using our tool or let or say Snowflake, for example, you have instant data quality metrics, instant profiling, instant lineage and access privacy controls things of that nature that just become less onerous. What we're seeing is there's so much technology out there just like all of the major brands that you mentioned but how do we make it easier? The future is about less clicks, faster time to value faster scale, and eventually lower cost. And we think that this positions us to be the leader there. >> I love this example because every talks about wow the cloud guys are going to own the world and of course now we're seeing that the ecosystem is finding so much white space to add value, connect across cloud. Sometimes we call it super cloud and so, or inter clouding. Alright, Kirk, give us your final thoughts and on the trends that we've talked about and Data Citizens '22. >> Absolutely. Well I think, one big trend is discovery and classification. Seeing that across the board people used to know it was a zip code and nowadays with the amount of data that's out there, they want to know where everything is where their sensitive data is. If it's redundant, tell me everything inside of three to five seconds. And with that comes, they want to know in all of these hyperscale databases, how fast they can get controls and insights out of their tools. So I think we're going to see more one click solutions, more SAS-based solutions and solutions that hopefully prove faster time to value on all of these modern cloud platforms. >> Excellent, all right. Kurt Hasselbeck, thanks so much for coming on theCUBE and previewing Data Citizens '22. Appreciate it. >> Thanks for having me, Dave. >> You're welcome. All right, and thank you for watching. Keep it right there for more coverage from theCUBE.

(upbeat music) >> Welcome back to theCUBE's continuing coverage of Snowflake Summit '22 live from Caesar's Forum in Las Vegas. I'm Lisa Martin, my cohost Dave Vellante, we've been here the last day and a half unpacking a lot of news, a lot of announcements, talking with customers and partners, and we have another great session coming for you next. We've got a customer and a partner talking tech and data mash. Please welcome Mitesh Shah, VP in market strategy at Elation. >> Great to be here. >> and Ash Naseer great, to have you, senior director of data engineering at Warner Brothers Discovery. Welcome guys. >> Thank you for having me. >> It's great to be back in person and to be able to really get to see and feel and touch this technology, isn't it? >> Yeah, it is. I mean two years or so. Yeah. Great to feel the energy in the conference center. >> Yeah. >> Snowflake was virtual, I think for two years and now it's great to kind of see the excitement firsthand. So it's wonderful. >> Th excitement, but also the boom and the number of customers and partners and people attending. They were saying the first, or the summit in 2019 had about 1900 attendees. And this is around 10,000. So a huge jump in a short time period. Talk a little bit about the Elation-Snowflake partnership and probably some of the acceleration that you guys have been experiencing as a Snowflake partner. >> Yeah. As a snowflake partner. I mean, Snowflake is an investor of us in Elation early last year, and we've been a partner for, for longer than that. And good news. We have been awarded Snowflake partner of the year for data governance, just earlier this week. And that's in fact, our second year in a row for winning that award. So, great news on that front as well. >> Repeat, congratulations. >> Repeat. Absolutely. And we're going to hope to make it a three-peat as well. And we've also been awarded industry competency badges in five different industries, those being financial services, healthcare, retail technology, and Median Telcom. >> Excellent. Okay. Going to right get into it. Data mesh. You guys actually have a data mesh and you've presented at the conference. So, take us back to the beginning. Why did you decide that you needed to implement something like data mesh? What was the impetus? >> Yeah. So when people think of Warner brothers, you always think of like the movie studio, but we're more than that, right? I mean, you think of HBO, you think of TNT, you think of CNN, we have 30 plus brands in our portfolio and each have their own needs. So the idea of a data mesh really helps us because what we can do is we can federate access across the company so that, you know, CNN can work at their own pace. You know, when there's election season, they can ingest their own data and they don't have to, you know, bump up against as an example, HBO, if Game of Thrones is going on. >> So, okay. So the, the impetus was to serve those lines of business better. Actually, given that you've got these different brands, it was probably easier than most companies. Cause if you're, let's say you're a big financial services company, and now you have to decide who owns what. CNN owns its own data products, HBO. Now, do they decide within those different brands, how to distribute even further? Or is it really, how deep have you gone in that decentralization? >> That's a great question. It's a very close partnership, because there are a number of data sets, which are used by all the brands, right? You think about people browsing websites, right? You know, CNN has a website, Warner brothers has a website. So for us to ingest that data for each of the brands to ingest that data separately, that means five different ways of doing things and you know, a big environment, right? So that is where our team comes into play. We ingest a lot of the common data sets, but like I said, any unique data sets, data sets regarding theatrical as an example, you know, Warner brothers does it themselves, you know, for streaming, HBO Max, does it themselves. So we kind of operate in partnership. >> So do you have a centralized data team and also decentralized data teams, right? >> That's right. >> So I love this conversation because that was heresy 10 years ago, five years ago, even, cause that's inefficient. But you've, I presume you've found that it's actually more productive in terms of the business output, explain that dynamic. >> You know, you bring up such a good point. So I, you know, I consider myself as one of the dinosaurs who started like 20 plus years ago in this industry. And back then, we were all taught to think of the data warehouse as like a monolithic thing. And the reason for that is the technology wasn't there. The technology didn't catch up. Now, 20 years later, the technology is way ahead, right? But like, our mindset's still the same because we think of data warehouses and data platforms still as a monolithic thing. But if you really sort of remove that sort of mental barrier, if you will, and if you start thinking about, well, how do I sort of, you know, federate everything and make sure that you let folks who are building, or are closest to the customer or are building their products, let them own that data and have a partnership. The results have been amazing. And if we were only sort of doing it as a centralized team, we would not be able to do a 10th of what we do today. So it's that massive scale in, in our company as well. >> And I should have clarified, when we talk about data mesh are we talking about the implementing in practice, the octagon sort of framework, or is this sort of your own sort of terminology? >> Well, so the interesting part is four years ago, we didn't have- >> It didn't exist. >> Yeah. It didn't exist. And, and so we, our principle was very simple, right? When we started out, we said, we want to make sure that our brands are able to operate independently with some oversight and guidance from our technology teams, right? That's what we set out to do. We did that with Snowflake by design because Snowflake allows us to, you know, separate those, those brands into different accounts. So that was done by design. And then the, the magic, I think, is the Snowflake data sharing where, which allows us to sort of bring data in here once, and then share it with whoever needs it. So think about HBO Max. On HBO Max, You not only have HBO Max content, but content from CNN, from Cartoon Network, from Warner Brothers, right? All the movies, right? So to see how The Batman movie did in theaters and then on streaming, you don't need, you know, Warner brothers doesn't need to ingest the same streaming data. HBO Max does it. HBO Max shares it with Warner brothers, you know, store once, share many times, and everyone works at their own pace. >> So they're building data products. Those data products are discoverable APIs, I presume, or I guess maybe just, I guess the Snowflake cloud, but very importantly, they're governed. And that's correct, where Elation comes in? >> That's precisely where Elation comes in, is where sort of this central flexible foundation for data governance. You know, you mentioned data mesh. I think what's interesting is that it's really an answer to the bottlenecks created by centralized IT, right? There's this notion of decentralizing that the data engineers and making the data domain owners, the people that know the data the best, have them be in control of publishing the data to the data consumers. There are other popular concepts actually happening right now, as we speak, around modern data stack. Around data fabric that are also in many ways underpinned by this notion of decentralization, right? These are concepts that are underpinned by decentralization and as the pendulum swings, sort of between decentralization and centralization, as we go back and forth in the world of IT and data, there are certain constants that need to be centralized over time. And one of those I believe is very much a centralized platform for data governance. And that's certainly, I think where we come in. Would love to hear more about how you use Elation. >> Yeah. So, I mean, elation helps us sort of, as you guys say, sort of, map, the treasure map of the data, right? So for consumers to find where their data is, that's where Elation helps us. It helps us with the data cataloging, you know, storing all the metadata and, you know, users can go in, they can sort of find, you know, the data that they need and they can also find how others are using data. So it's, there's a little bit of a crowdsourcing aspect that Elation helps us to do whereby you know, you can see, okay, my peer in the other group, well, that's how they use this piece of data. So I'm not going to spend hours trying to figure this out. You're going to use the query that they use. So yeah. >> So you have a master catalog, I presume. And then each of the brands has their own sub catalogs, is that correct? >> Well, for the most part, we have that master catalog and then the brands sort of use it, you know, separately themselves. The key here is all that catalog, that catalog isn't maintained by a centralized group as well, right? It's again, maintained by the individual teams and not only in the individual teams, but the folks that are responsible for the data, right? So I talked about the concept of crowdsourcing, whoever sort of puts the data in, has to make sure that they update the catalog and make sure that the definitions are there and everything sort of in line. >> So HBO, CNN, and each have their own, sort of access to their catalog, but they feed into the master catalog. Is that the right way to think about it? >> Yeah. >> Okay. And they have their own virtual data warehouses, right? They have ownership over that? They can spin 'em up, spin 'em down as they see fit? Right? And they're governed. >> They're governed. And what's interesting is it's not just governed, right? Governance is a, is a big word. It's a bit nebulous, but what's really being enabled here is this notion of self-service as well, right? There's two big sort of rockets that need to happen at the same time in any given organization. There's this notion that you want to put trustworthy data in the hands of data consumers, while at the same time mitigating risk. And that's precisely what Elation does. >> So I want to clarify this for the audience. So there's four principles of database. This came after you guys did it. And I wonder how it aligns. Domain ownership, give data, as you were saying to the, to the domain owners who have context, data as product, you guys are building data products, and that creates two problems. How do you give people self-service infrastructure and how do you automate governance? So the first two, great. But then it creates these other problems. Does that align with your philosophy? Where's alignment? What's different? >> Yeah. Data products is exactly where we're going. And that sort of, that domain based design, that's really key as well. In our business, you think about who the customer is, as an example, right? Depending on who you ask, it's going to be, the answer might be different, you know, to the movie business, it's probably going to be the person who watches a movie in a theater. To the streaming business, to HBO Max, it's the streamer, right? To others, someone watching live CNN on their TV, right? There's yet another group. Think about all the franchising we do. So you see Batman action figures and T-shirts, and Warner brothers branded stuff in stores, that's yet another business unit. But at the end of the day, it's not a different person, it's you and me, right? We do all these things. So the domain concept, make sure that you ingest data and you bring data relevant to the context, however, not sort of making it so stringent where it cannot integrate, and then you integrate it at a higher level to create that 360. >> And it's discoverable. So the point is, I don't have to go tap Ash on the shoulder, say, how do I get this data? Is it governed? Do I have access to it? Give me the rules of it. Just, I go grab it, right? And the system computationally automates whether or not I have access to it. And it's, as you say, self-service. >> In this case, exactly right. It enables people to just search for data and know that when they find the data, whether it's trustworthy or not, through trust flags, and the like, it's doing both of those things at the same time. >> How is it an enabler of solving some of the big challenges that the media and entertainment industry is going through? We've seen so much change the last couple of years. The rising consumer expectations aren't going to go back down. They're only going to come up. We want you to serve us up content that's relevant, that's personalized, that makes sense. I'd love to understand from your perspective, Mitesh, from an industry challenges perspective, how does this technology help customers like Warner Brothers Discovery, meet business customers, where they are and reduce the volume on those challenges? >> It's a great question. And as I mentioned earlier, we had five industry competency badges that were awarded to us by Snowflake. And one of those four, Median Telcom. And the reason for that is we're helping media companies understand their audiences better, and ultimately serve up better experiences for their audiences. But we've got Ash right here that can tell us how that's happening in practice. >> Yeah, tell us. >> So I'll share a story. I always like to tell stories, right? Once once upon a time before we had Elation in place, it was like, who you knew was how you got access to the data. So if I knew you and I knew you had access to a certain kind of data and your access to the right kind of data was based on the network you had at the company- >> I had to trust you. >> Yeah. >> I might not want to give up my data. >> That's it. And so that's where Elation sort of helps us democratize it, but, you know, puts the governance and controls, right? There are certain sensitive things as well, such as viewership, such as subscriber accounts, which are very important. So making sure that the right people have access to it, that's the other problem that Elation helps us solve. >> That's precisely part of our integration with Snowflake in particular, being able to define and manage policies within Elation. Saying, you know, certain people should have access to certain rows, doing column level masking. And having those policies actually enforced at the Snowflake data layer is precisely part of our value product. >> And that's automated. >> And all that's automated. Exactly. >> Right. So I don't have to think about it. I don't have to go through the tap on their shoulder. What has been the impact, Ash, on data quality as you've pushed it down into the domains? >> That's a great question. So it has definitely improved, but data quality is a very interesting subject, because back to my example of, you know, when we started doing things, we, you know, the centralized IT team always said, well, it has to be like this, Right? And if it doesn't fit in this, then it's bad quality. Well, sometimes context changes. Businesses change, right? You have to be able to react to it quickly. So making sure that a lot of that quality is managed at the decentralized level, at the place where you have that business context, that ensures you have the most up to date quality. We're talking about media industry changing so quickly. I mean, would we have thought three years ago that people would watch a lot of these major movies on streaming services? But here's the reality, right? You have to react and, you know, having it at that level just helps you react faster. >> So data, if I play that back, data quality is not a static framework. It's flexible based on the business context and the business owners can make those adjustments, cause they own the data. >> That's it. That's exactly it. >> That's awesome. Wow. That's amazing progress that you guys have made. >> In quality, if I could just add, it also just changes depending on where you are in your data pipeline stage, right? Data, quality data observability, this is a very fast evolving space at the moment, and if I look to my left right now, I bet you I can probably see a half-dozen quality observability vendors right now. And so given that and given the fact that Elation still is sort of a central hub to find trustworthy data, we've actually announced an open data quality initiative, allowing for best-of-breed data quality vendors to integrate with the platform. So whoever they are, whatever tool folks want to use, they can use that particular tool of choice. >> And this all runs in the cloud, or is it a hybrid sort of? >> Everything is in the cloud. We're all in the cloud. And you know, again, helps us go faster. >> Let me ask you a question. I could go on forever in this topic. One of the concepts that was put forth is whether it's a Snowflake data warehouse or a data bricks, data lake, or an Oracle data warehouse, they should all be inclusive. They should just be a node on the mesh. Like, wow, that sounds good. But I haven't seen it yet. Right? I'm guessing that Snowflake and Elation enable all the self-serve, all this automated governance, and that including those other items, it's got to be a one-off at this point in time. Do you ever see you expanding that scope or is it better off to just kind of leave it into the, the Snowflake data cloud? >> It's a good question. You know, I feel like where we're at today, especially in terms of sort of technology giving us so many options, I don't think there's a one size fits all. Right? Even though we are very heavily invested in Snowflake and we use Snowflake consistently across the organization, but you could, theoretically, could have an architecture that blends those two, right? Have different types of data platforms like a teradata or an Oracle and sort of bring it all together today. We have the technology, you know, that and all sorts of things that can make sure that you query on different databases. So I don't think the technology is the problem, I think it's the organizational mindset. I think that that's what gets in the way. >> Oh, interesting. So I was going to ask you, will hybrid tables help you solve that problem? And, maybe not, what you're saying, it's the organization that owns the Oracle database saying, Hey, we have our system. It processes, it works, you know, go away. >> Yeah. Well, you know, hybrid tables I think, is a great sort of next step in Snowflake's evolution. I think it's, in my opinion, I, think it's a game changer, but yeah. I mean, they can still exist. You could do hybrid tables right on Snowflake, or you could, you know, you could kind of coexist as well. >> Yeah. But, do you have a thought on this? >> Yeah, I do. I mean, we're always going to live in a time where you've got data distributed in throughout the organization and around the globe. And that could be even if you're all in on Snowflake, you could have data in Snowflake here, you could have data in Snowflake in EMEA and Europe somewhere. It could be anywhere. By the same token you might be using. Every organization is using on-premises systems. They have data, they naturally have data everywhere. And so, you know, this one solution to this is really centralizing, as I mentioned, not just governance, but also metadata about all of the data in your organization so that you can enable people to search and find and discover trustworthy data no matter where it is in your organization. >> Yeah. That's a great point. I mean, if you have the data about the data, then you can, you can treat these independent nodes. That's just that. Right? And maybe there's some advantages of putting it all in the Snowflake cloud, but to your point, organizationally, that's just not feasible. The whole, unfortunately, sorry, Snowflake, all the world's data is not going to go into Snowflake, but they play a key role in accelerating, what I'm hearing, your vision of data mesh. >> Yeah, absolutely. I think going forward in the future, we have to start thinking about data platforms as just one place where you sort of dump all the data. That's where the mesh concept comes in. It is going to be a mesh. It's going to be distributed and organizations have to be okay with that. And they have to embrace the tools. I mean, you know, Facebook developed a tool called Presto many years ago that that helps them solve exactly the same problem. So I think the technology is there. I think the organizational mindset needs to evolve. >> Yeah. Definitely. >> Culture. Culture is one of the hardest things to change. >> Exactly. >> Guys, this was a masterclass in data mesh, I think. Thank you so much for coming on talking. >> We appreciate it. Thank you so much. >> Of course. What Elation is doing with Snowflake and with Warner Brothers Discovery, Keep that content coming. I got a lot of stuff I got to catch up on watching. >> Sounds good. Thank you for having us. >> Thanks guys. >> Thanks, you guys. >> For Dave Vellante, I'm Lisa Martin. You're watching theCUBE live from Snowflake Summit '22. We'll be back after a short break. (upbeat music)

(upbeat music) >> Welcome back to theCUBE's continuing coverage of Snowflake Summit '22 live from Caesar's Forum in Las Vegas. I'm Lisa Martin, my cohost Dave Vellante, we've been here the last day and a half unpacking a lot of news, a lot of announcements, talking with customers and partners, and we have another great session coming for you next. We've got a customer and a partner talking tech and data mash. Please welcome Mitesh Shah, VP in market strategy at Elation. >> Great to be here. >> and Ash Naseer great, to have you, senior director of data engineering at Warner Brothers Discovery. Welcome guys. >> Thank you for having me. >> It's great to be back in person and to be able to really get to see and feel and touch this technology, isn't it? >> Yeah, it is. I mean two years or so. Yeah. Great to feel the energy in the conference center. >> Yeah. >> Snowflake was virtual, I think for two years and now it's great to kind of see the excitement firsthand. So it's wonderful. >> Th excitement, but also the boom and the number of customers and partners and people attending. They were saying the first, or the summit in 2019 had about 1900 attendees. And this is around 10,000. So a huge jump in a short time period. Talk a little bit about the Elation-Snowflake partnership and probably some of the acceleration that you guys have been experiencing as a Snowflake partner. >> Yeah. As a snowflake partner. I mean, Snowflake is an investor of us in Elation early last year, and we've been a partner for, for longer than that. And good news. We have been awarded Snowflake partner of the year for data governance, just earlier this week. And that's in fact, our second year in a row for winning that award. So, great news on that front as well. >> Repeat, congratulations. >> Repeat. Absolutely. And we're going to hope to make it a three-peat as well. And we've also been awarded industry competency badges in five different industries, those being financial services, healthcare, retail technology, and Median Telcom. >> Excellent. Okay. Going to right get into it. Data mesh. You guys actually have a data mesh and you've presented at the conference. So, take us back to the beginning. Why did you decide that you needed to implement something like data mesh? What was the impetus? >> Yeah. So when people think of Warner brothers, you always think of like the movie studio, but we're more than that, right? I mean, you think of HBO, you think of TNT, you think of CNN, we have 30 plus brands in our portfolio and each have their own needs. So the idea of a data mesh really helps us because what we can do is we can federate access across the company so that, you know, CNN can work at their own pace. You know, when there's election season, they can ingest their own data and they don't have to, you know, bump up against as an example, HBO, if Game of Thrones is going on. >> So, okay. So the, the impetus was to serve those lines of business better. Actually, given that you've got these different brands, it was probably easier than most companies. Cause if you're, let's say you're a big financial services company, and now you have to decide who owns what. CNN owns its own data products, HBO. Now, do they decide within those different brands, how to distribute even further? Or is it really, how deep have you gone in that decentralization? >> That's a great question. It's a very close partnership, because there are a number of data sets, which are used by all the brands, right? You think about people browsing websites, right? You know, CNN has a website, Warner brothers has a website. So for us to ingest that data for each of the brands to ingest that data separately, that means five different ways of doing things and you know, a big environment, right? So that is where our team comes into play. We ingest a lot of the common data sets, but like I said, any unique data sets, data sets regarding theatrical as an example, you know, Warner brothers does it themselves, you know, for streaming, HBO Max, does it themselves. So we kind of operate in partnership. >> So do you have a centralized data team and also decentralized data teams, right? >> That's right. >> So I love this conversation because that was heresy 10 years ago, five years ago, even, cause that's inefficient. But you've, I presume you've found that it's actually more productive in terms of the business output, explain that dynamic. >> You know, you bring up such a good point. So I, you know, I consider myself as one of the dinosaurs who started like 20 plus years ago in this industry. And back then, we were all taught to think of the data warehouse as like a monolithic thing. And the reason for that is the technology wasn't there. The technology didn't catch up. Now, 20 years later, the technology is way ahead, right? But like, our mindset's still the same because we think of data warehouses and data platforms still as a monolithic thing. But if you really sort of remove that sort of mental barrier, if you will, and if you start thinking about, well, how do I sort of, you know, federate everything and make sure that you let folks who are building, or are closest to the customer or are building their products, let them own that data and have a partnership. The results have been amazing. And if we were only sort of doing it as a centralized team, we would not be able to do a 10th of what we do today. So it's that massive scale in, in our company as well. >> And I should have clarified, when we talk about data mesh are we talking about the implementing in practice, the octagon sort of framework, or is this sort of your own sort of terminology? >> Well, so the interesting part is four years ago, we didn't have- >> It didn't exist. >> Yeah. It didn't exist. And, and so we, our principle was very simple, right? When we started out, we said, we want to make sure that our brands are able to operate independently with some oversight and guidance from our technology teams, right? That's what we set out to do. We did that with Snowflake by design because Snowflake allows us to, you know, separate those, those brands into different accounts. So that was done by design. And then the, the magic, I think, is the Snowflake data sharing where, which allows us to sort of bring data in here once, and then share it with whoever needs it. So think about HBO Max. On HBO Max, You not only have HBO Max content, but content from CNN, from Cartoon Network, from Warner Brothers, right? All the movies, right? So to see how The Batman movie did in theaters and then on streaming, you don't need, you know, Warner brothers doesn't need to ingest the same streaming data. HBO Max does it. HBO Max shares it with Warner brothers, you know, store once, share many times, and everyone works at their own pace. >> So they're building data products. Those data products are discoverable APIs, I presume, or I guess maybe just, I guess the Snowflake cloud, but very importantly, they're governed. And that's correct, where Elation comes in? >> That's precisely where Elation comes in, is where sort of this central flexible foundation for data governance. You know, you mentioned data mesh. I think what's interesting is that it's really an answer to the bottlenecks created by centralized IT, right? There's this notion of decentralizing that the data engineers and making the data domain owners, the people that know the data the best, have them be in control of publishing the data to the data consumers. There are other popular concepts actually happening right now, as we speak, around modern data stack. Around data fabric that are also in many ways underpinned by this notion of decentralization, right? These are concepts that are underpinned by decentralization and as the pendulum swings, sort of between decentralization and centralization, as we go back and forth in the world of IT and data, there are certain constants that need to be centralized over time. And one of those I believe is very much a centralized platform for data governance. And that's certainly, I think where we come in. Would love to hear more about how you use Elation. >> Yeah. So, I mean, elation helps us sort of, as you guys say, sort of, map, the treasure map of the data, right? So for consumers to find where their data is, that's where Elation helps us. It helps us with the data cataloging, you know, storing all the metadata and, you know, users can go in, they can sort of find, you know, the data that they need and they can also find how others are using data. So it's, there's a little bit of a crowdsourcing aspect that Elation helps us to do whereby you know, you can see, okay, my peer in the other group, well, that's how they use this piece of data. So I'm not going to spend hours trying to figure this out. You're going to use the query that they use. So yeah. >> So you have a master catalog, I presume. And then each of the brands has their own sub catalogs, is that correct? >> Well, for the most part, we have that master catalog and then the brands sort of use it, you know, separately themselves. The key here is all that catalog, that catalog isn't maintained by a centralized group as well, right? It's again, maintained by the individual teams and not only in the individual teams, but the folks that are responsible for the data, right? So I talked about the concept of crowdsourcing, whoever sort of puts the data in, has to make sure that they update the catalog and make sure that the definitions are there and everything sort of in line. >> So HBO, CNN, and each have their own, sort of access to their catalog, but they feed into the master catalog. Is that the right way to think about it? >> Yeah. >> Okay. And they have their own virtual data warehouses, right? They have ownership over that? They can spin 'em up, spin 'em down as they see fit? Right? And they're governed. >> They're governed. And what's interesting is it's not just governed, right? Governance is a, is a big word. It's a bit nebulous, but what's really being enabled here is this notion of self-service as well, right? There's two big sort of rockets that need to happen at the same time in any given organization. There's this notion that you want to put trustworthy data in the hands of data consumers, while at the same time mitigating risk. And that's precisely what Elation does. >> So I want to clarify this for the audience. So there's four principles of database. This came after you guys did it. And I wonder how it aligns. Domain ownership, give data, as you were saying to the, to the domain owners who have context, data as product, you guys are building data products, and that creates two problems. How do you give people self-service infrastructure and how do you automate governance? So the first two, great. But then it creates these other problems. Does that align with your philosophy? Where's alignment? What's different? >> Yeah. Data products is exactly where we're going. And that sort of, that domain based design, that's really key as well. In our business, you think about who the customer is, as an example, right? Depending on who you ask, it's going to be, the answer might be different, you know, to the movie business, it's probably going to be the person who watches a movie in a theater. To the streaming business, to HBO Max, it's the streamer, right? To others, someone watching live CNN on their TV, right? There's yet another group. Think about all the franchising we do. So you see Batman action figures and T-shirts, and Warner brothers branded stuff in stores, that's yet another business unit. But at the end of the day, it's not a different person, it's you and me, right? We do all these things. So the domain concept, make sure that you ingest data and you bring data relevant to the context, however, not sort of making it so stringent where it cannot integrate, and then you integrate it at a higher level to create that 360. >> And it's discoverable. So the point is, I don't have to go tap Ash on the shoulder, say, how do I get this data? Is it governed? Do I have access to it? Give me the rules of it. Just, I go grab it, right? And the system computationally automates whether or not I have access to it. And it's, as you say, self-service. >> In this case, exactly right. It enables people to just search for data and know that when they find the data, whether it's trustworthy or not, through trust flags, and the like, it's doing both of those things at the same time. >> How is it an enabler of solving some of the big challenges that the media and entertainment industry is going through? We've seen so much change the last couple of years. The rising consumer expectations aren't going to go back down. They're only going to come up. We want you to serve us up content that's relevant, that's personalized, that makes sense. I'd love to understand from your perspective, Mitesh, from an industry challenges perspective, how does this technology help customers like Warner Brothers Discovery, meet business customers, where they are and reduce the volume on those challenges? >> It's a great question. And as I mentioned earlier, we had five industry competency badges that were awarded to us by Snowflake. And one of those four, Median Telcom. And the reason for that is we're helping media companies understand their audiences better, and ultimately serve up better experiences for their audiences. But we've got Ash right here that can tell us how that's happening in practice. >> Yeah, tell us. >> So I'll share a story. I always like to tell stories, right? Once once upon a time before we had Elation in place, it was like, who you knew was how you got access to the data. So if I knew you and I knew you had access to a certain kind of data and your access to the right kind of data was based on the network you had at the company- >> I had to trust you. >> Yeah. >> I might not want to give up my data. >> That's it. And so that's where Elation sort of helps us democratize it, but, you know, puts the governance and controls, right? There are certain sensitive things as well, such as viewership, such as subscriber accounts, which are very important. So making sure that the right people have access to it, that's the other problem that Elation helps us solve. >> That's precisely part of our integration with Snowflake in particular, being able to define and manage policies within Elation. Saying, you know, certain people should have access to certain rows, doing column level masking. And having those policies actually enforced at the Snowflake data layer is precisely part of our value product. >> And that's automated. >> And all that's automated. Exactly. >> Right. So I don't have to think about it. I don't have to go through the tap on their shoulder. What has been the impact, Ash, on data quality as you've pushed it down into the domains? >> That's a great question. So it has definitely improved, but data quality is a very interesting subject, because back to my example of, you know, when we started doing things, we, you know, the centralized IT team always said, well, it has to be like this, Right? And if it doesn't fit in this, then it's bad quality. Well, sometimes context changes. Businesses change, right? You have to be able to react to it quickly. So making sure that a lot of that quality is managed at the decentralized level, at the place where you have that business context, that ensures you have the most up to date quality. We're talking about media industry changing so quickly. I mean, would we have thought three years ago that people would watch a lot of these major movies on streaming services? But here's the reality, right? You have to react and, you know, having it at that level just helps you react faster. >> So data, if I play that back, data quality is not a static framework. It's flexible based on the business context and the business owners can make those adjustments, cause they own the data. >> That's it. That's exactly it. >> That's awesome. Wow. That's amazing progress that you guys have made. >> In quality, if I could just add, it also just changes depending on where you are in your data pipeline stage, right? Data, quality data observability, this is a very fast evolving space at the moment, and if I look to my left right now, I bet you I can probably see a half-dozen quality observability vendors right now. And so given that and given the fact that Elation still is sort of a central hub to find trustworthy data, we've actually announced an open data quality initiative, allowing for best-of-breed data quality vendors to integrate with the platform. So whoever they are, whatever tool folks want to use, they can use that particular tool of choice. >> And this all runs in the cloud, or is it a hybrid sort of? >> Everything is in the cloud. We're all in the cloud. And you know, again, helps us go faster. >> Let me ask you a question. I could go on forever in this topic. One of the concepts that was put forth is whether it's a Snowflake data warehouse or a data bricks, data lake, or an Oracle data warehouse, they should all be inclusive. They should just be a node on the mesh. Like, wow, that sounds good. But I haven't seen it yet. Right? I'm guessing that Snowflake and Elation enable all the self-serve, all this automated governance, and that including those other items, it's got to be a one-off at this point in time. Do you ever see you expanding that scope or is it better off to just kind of leave it into the, the Snowflake data cloud? >> It's a good question. You know, I feel like where we're at today, especially in terms of sort of technology giving us so many options, I don't think there's a one size fits all. Right? Even though we are very heavily invested in Snowflake and we use Snowflake consistently across the organization, but you could, theoretically, could have an architecture that blends those two, right? Have different types of data platforms like a teradata or an Oracle and sort of bring it all together today. We have the technology, you know, that and all sorts of things that can make sure that you query on different databases. So I don't think the technology is the problem, I think it's the organizational mindset. I think that that's what gets in the way. >> Oh, interesting. So I was going to ask you, will hybrid tables help you solve that problem? And, maybe not, what you're saying, it's the organization that owns the Oracle database saying, Hey, we have our system. It processes, it works, you know, go away. >> Yeah. Well, you know, hybrid tables I think, is a great sort of next step in Snowflake's evolution. I think it's, in my opinion, I, think it's a game changer, but yeah. I mean, they can still exist. You could do hybrid tables right on Snowflake, or you could, you know, you could kind of coexist as well. >> Yeah. But, do you have a thought on this? >> Yeah, I do. I mean, we're always going to live in a time where you've got data distributed in throughout the organization and around the globe. And that could be even if you're all in on Snowflake, you could have data in Snowflake here, you could have data in Snowflake in EMEA and Europe somewhere. It could be anywhere. By the same token you might be using. Every organization is using on-premises systems. They have data, they naturally have data everywhere. And so, you know, this one solution to this is really centralizing, as I mentioned, not just governance, but also metadata about all of the data in your organization so that you can enable people to search and find and discover trustworthy data no matter where it is in your organization. >> Yeah. That's a great point. I mean, if you have the data about the data, then you can, you can treat these independent nodes. That's just that. Right? And maybe there's some advantages of putting it all in the Snowflake cloud, but to your point, organizationally, that's just not feasible. The whole, unfortunately, sorry, Snowflake, all the world's data is not going to go into Snowflake, but they play a key role in accelerating, what I'm hearing, your vision of data mesh. >> Yeah, absolutely. I think going forward in the future, we have to start thinking about data platforms as just one place where you sort of dump all the data. That's where the mesh concept comes in. It is going to be a mesh. It's going to be distributed and organizations have to be okay with that. And they have to embrace the tools. I mean, you know, Facebook developed a tool called Presto many years ago that that helps them solve exactly the same problem. So I think the technology is there. I think the organizational mindset needs to evolve. >> Yeah. Definitely. >> Culture. Culture is one of the hardest things to change. >> Exactly. >> Guys, this was a masterclass in data mesh, I think. Thank you so much for coming on talking. >> We appreciate it. Thank you so much. >> Of course. What Elation is doing with Snowflake and with Warner Brothers Discovery, Keep that content coming. I got a lot of stuff I got to catch up on watching. >> Sounds good. Thank you for having us. >> Thanks guys. >> Thanks, you guys. >> For Dave Vellante, I'm Lisa Martin. You're watching theCUBE live from Snowflake Summit '22. We'll be back after a short break. (upbeat music)

>>Welcome everyone to this cube conversation featuring unit Q. I'm your host, Lisa Martin. And we are excited to be joined by Christian Vickle, the founder and CEO of unit Q Christian. Thank you so much for joining me today. >>Thank you so much, Lisa pleasure to be here. >>Let's talk a little bit about unit Q. You guys were founded in 2018, so pretty recent. What is it that unit Q does. And what were some of the gaps in the market that led you to founding the company? >>Yep. So me and my co-founder Nick, we're actually doing our second company now is the unit Q is number two, and our first company was called scout years ago. We were back ES wicks and it was very different from unit Q. It's a social network for meeting people. And it was really during that experience where we saw the impact that quality of the experience quality of the product can have on your growth trajectory and the challenges we faced. How do we test everything before we ship it? And in reality, a modern company will have, let's say, 20 languages supported you support Android, Iowas, web big screen, small screen, you have 20 plus integrations and you have lots of different devices out there that might run your binary a little differently. So who is the ultimate test group of all of these different permutation and that's the end user. >>And we, we saw the, the big gap in the market, sort of the dream platform for us was unit queue. So if, if this would've existed back in the day, we would've been a, a happy purchaser and customer, and it really comes down to how do we, how do we harness the power of user feedback? You know, the end user, that's testing your product every single day in all different configurations. And then they're telling you that, Hey, something didn't work for me. I got double build or the passive recent link didn't work, or I couldn't, you know, when music, when the ad is finished playing on, on my app, the music doesn't resume. So how do we capture those signals into something that the company and different teams can align on? So that's where, you know, unit Q the, the vision here is to build a quality company, to help other companies build higher quality products. >>So really empowering companies to take a data driven approach to product quality. I was looking on your website and noticed that Pandora is one of your customers, but talk to me a little bit about a customer example that you think really articulates the value of what Q unit he was delivering. >>Right? So maybe we should just go back one little step and talk about what is quality. And I think quality is something that is, is a bit subjective. It's something that we live and breathe every day. It's something that can be formed in an instant first impressions. Last it's something that can be built over time that, Hey, I'm using this product and it's just not working for me. Maybe it's missing features. Maybe there are performance related bots. Maybe there is there's even fulfillment related issues. Like we work with Uber and hello, fresh and, and other types of more hybrid type companies in addition to the Pandoras and, and Pinterest and, and Spotify, and these more digital, only products, but the, the end users I'm producing this data, the reporting, what is working and not working out there in many different channels. So they will leave app produce. >>They will write into support. They might engage with a chat support bot. They will post stuff on Reddit on Twitter. They will comment on Facebook ads. So like this data is dispersed everywhere. The end user is not gonna fill out a perfect bug report in a form somewhere that gets filed into gr like they're, they're producing this content everywhere in different languages. So the first value of what we do is to just ingest all of that data. So all the entire surface area of use of feedback, we ingest into a machine and then we clean the data. We normalize it, and then we translate everything into English. And it was actually a surprise to us when we started this company, that there are quite a few companies out there that they're only looking at feedback in English. So what about my Spanish speaking users? What about my French speaking users? >>And when, when, when that is done, like when all of that data is, is need to organized, we extract signals from that around what is impacting the user experience right now. So we break these, all of this data down into something called quality monitors. So quality monitor is basically a topic which can be again, passive reset, link noting, or really anything that that's impacting the end user. And the important part here is that we need to have specific actionable data. For instance, if I tell you, Hey, Lisa music stops playing is a growing trend that our users are reporting. You will tell me, well, what can I do with that? Like what specifically is breaking? So we deploy up to 1500 unique quality monitors per customer. So we can then alert different teams inside of the organization of like, Hey, something broke and you should take a look at it. >>So it's really breaking down data silos within the company. It aligns cross-functional teams to agree on what should be fixed next. Cause there's typically a lot of confusion, you know, marketing, they might say, Hey, we want this fixed engineering. They're like, well, I can't reproduce, or that's not a high priority for us. The support teams might also have stuff that they want to get fixed. And what we've seen is that these teams, they struggle to communicate. So how do we align them around the single source of truth? And I think that's for unit two is early identification of stuff. That's not working in production and it's also aligning the teams so they can quickly triage and say, yes, we gotta fix this right before it snowballs into something. We say, you know, we wanna, we wanna cap catch issues before you go into crisis PR mode, right? So we want to get this, we wanna address it early in the cycle. >>Talk to me about when you're in customer conversations, Christian, the MarTech landscape is competitive. There's nearly 10,000 different solutions out there, and it's growing really quickly quality monitors that you just described is that one of the key things that, that you talk to customers about, that's a differentiator for unit Q. >>Yeah. So I mean, it, it, it comes down to, as you're building your product, right, you, you have, you have a few different options. One is to build new features and we need to build new features and innovate and, and, and that's all great. We also need to make sure that the foundation of the product is working and that we keep improving quality and what, what we see with, with basically every customer that we work with, that, that when quality goes up, it's supercharges the growth machine. So quality goes up, you're gonna see less support tickets. You're gonna see less one star reviews, less one star reviews is of course good for making the store front convert better. You know, I, I want install a 4.5 star app, not a 3.9 star app. We also see that sentiment. So for those who are interested in getting that NPS score up for the next time we measure it, we see that quality is of course a very important piece of that. >>And maybe even more importantly, so sort of inside of the product machine, the different conversion steps, let's say sign up to activate it to coming back in second day, 30 day, 90 day, and so forth. We see a dramatic impact on how quality sort of moves that up and down the retention function, if you will. So it, it really, if you think about a modern company, like the product is sort of the center of the existence of the company, and if the product performs really well, then you can spend more money in marketing because it converts really good. You can hire more engineers, you can hire, you can hire more support people and so forth. So it's, it's really cool to see that when quality improves its supercharges, everything else I think for marketing it's how do you know if you're spending into a broken product or not? >>And I, and I, I feel like marketing has, they have their insights, but it's, it's not deep enough where they can go to engineering and say, Hey, these 10 issues are impacting my MPS score and they're impacting my conversion and I would love for you to fix it. And when you can bring tangible impact, when you can bring real data to, to engineering and product, they move on it cause they also wanna help build the company. And, and so I think that's, that's how we stand out from the more traditional MarTech, because we need to fix the core of, of sort of this growth engine, which is the quality of the product >>Quality of the product. And obviously that's directly related to the customer experience. And we know these days, one of the things I think that's been in short supply the last couple of years is patience. We know when customers are unhappy with the product or service, and you talked about it a minute ago, they're gonna go right to, to Reddit or other sources to complain about that. So being able to, for uniq, to help companies to improve the customer experience, isn't I think table stakes for businesses it's mission critical these days. Yeah, >>It is mission critical. So if you look at the, let's say that we were gonna start a, a music app. Okay. So how do we, how do we compete as a music app? Well, if you, if you were to analyze all different music apps out there, they have more or less the same features app. Like they, the feature differentiation is minimal. And, and if you launch a new cool feature than your competitor will probably copy that pretty quickly as well. So competing with features is really hard. What about content? Well, I'm gonna get the same content on Spotify as apple SD. So competing with content is also really hard. What about price? So it turns out you'll pay 9 99 a month for music, but there's no, there's no 1 99. It's gonna be 9 99. So quality of the experience is one of the like last vectors or areas where you can actually compete. >>And we see consistently that if you' beating your competition on quality, you will do better. Like the best companies out there also have the highest quality experience. So it's, it's been, you know, for us at our last company, measuring quality was something that was very hard. How do we talk about it? And when we started this company, I went out and talked to a bunch of CEOs and product leaders and board members. And I said, how do you talk about quality in a board meeting? And they were, they said, well, we don't, we don't have any metrics. So actually the first thing we did was to define a metrics. We have, we have this thing called this unit Q score, which is on our website as well, where we can base it's like the credit score. So you can see your score between zero and a hundred. >>And if your score is 100, it means that we're finding no quality issues in the public domain. If your score is 90, it means that 10% of the data we look at refers to a quality issue. And the definition of a quality issue is quite simple. It is when the user experience doesn't match the user expectation. There is a gap in between, and we've actually indexed the 5,000 largest apps out there. So we're then looking at all the public review. So on our website, you can go in and, and look up the unit Q score for the 5,000 largest products. And we republish these every night. So it's an operational metric that changes all the time. >>Hugely impactful. Christian, thank you so much for joining me today, talking to the audience about unit Q, how you're turning qualitative feedback into pretty significant product improvements for your customers. We appreciate your insights. >>Thank you, Lisa, have a great day. >>You as well, per Christian Lin, I'm Lisa Martin. You're watching a cube conversation.

>>From around the globe. It's the cube with digital coverage of AWS reinvent 2020 sponsored by Intel, AWS, and our community partners. >>Hi, everyone. Welcome back to the cubes. Live coverage of AWS reinvent 2020 I'm John Farrow, your hosts. We've got the cube virtual. We're not there in person with remote this year, and we're excited to cover three weeks of wall-to-wall coverage. It's virtual events, so they don't over three weeks. We're in week three, day two. Um, and if you're watching this live on the platform tomorrow, Thursday at two o'clock Andy Jassy, we'll be live here on the cube with one-on-one with me to address all the hard questions, but here we're doing a day two of week three analysis with Jeremy Burton industry legend entrepreneur. Now the CEO of observe Inc, um, formerly the CMO of Dell technologies before that EMC has done a variety of ventures, seeing many ways of innovation, friend of the cube. Jeremy, thank you for coming on. >>Yeah, my pleasure. Great. Always great to be on the cube. >>Uh, great to have you on in particularly because, um, yesterday Verner, Vogel's talked a lot about observability and I noticed you got your observed shirt on, uh, observe Inc is your company's name, which is one of the many, uh, hot startups around observability, where you're making a business out of basically what he talked about yesterday. Um, and today's keynote. You had the extended cloud, uh, edge applications. You had bill Vass who leads up both edge and quantum. And then you had Rudy Valdez who, who talked a lot about, uh, evolution of cloud architecture. And of course you finally had, um, David Richardson, who is the VP of serverless. So you got edge. Quantum serverless architecture speaks to the sea change, Jeremy, and you have a good read on these big waves. When you look at serverless and then quantum, you look at, uh, edge, which is data, and you look at, um, all this coming together and on their architecture, Verner's keynote yesterday kind of makes sense. It's a systems architecture and this new observability trend, isn't like a point product. It's a broader concepts. You have a complete rethinking of distributed computing in the cloud. This is kinda what this Amazon feels like. What's your, what's your take? >>Yeah, it's a, it's a good observation. You know, the, the, the, the sort of punchline is, is that people are building applications differently. Um, so the, the, the, the, the technologies that people are using to build apps are different, um, the way in which they build applications is different. Um, the way folks released codes into production is different, and it stands to reason. Therefore, you're going to need a different approach, uh, when you want to troubleshoot these applications. So, uh, when you find, uh, you know, w w what is show when you want to find out what issues customers are having? So what, what we fell a couple of three years ago when we started to observe was that, um, uh, a new approach was required, what you're going to need to monitor your application. And, you know, 2020 is not the same as what you needed in 2015 or 2010. >>And we felt very strongly that this new wave was, was going to be called observability. It, it brings a tear to my eye to hear a Verner, talk about it, because as much as we observe, you know, believe that we can do big things in future. It's the big vendors today that can move markets. And so the Amazon and vulnerable particular talk about observability, I think it lends more credence to the topic. Um, we think that organizations should have observability teams. We think there should be a head of observability. And again, you know, Amazon and Dawson this, uh, I think means that there's a much stronger chance that that's going to happen. And they're going to start, start to shine a light on, I think, a topic that almost everybody needs to pay attention to as they build their next generation of applications. >>When you guys, I know you guys are launched and you have couple of campaign customers now and growing rapidly, um, well-funded, um, uh, get some great investors have found that the investors of snowflake also, um, invested in you guys. So they see this cloud trend LC snowflake when public, and I know you're on the board of snowflake as well. So, uh, you, you, you know, a little bit about what's going on with Amazon and the opportunity when you look at observability, okay, you're building a business around it. And again, you think about head of observability. That's not like a small thing when you make, put someone in charge of something. So why do you say that? I mean, what, I mean, you know, some would say, you know, Hey, it's a feature, not a company. I mean, this is two mindsets that are different. How do you address that? >>Yeah, the, the, the, the thing I'd say is, look, the number one job in America is, um, is a software engineer is writing code. The number two job is fixing it. And so, you know, th th the job think about that for a second. The job of fixing our applications is almost as big as the job of creating our applications. Uh, something has to change, right? I know the job of fixing cars is not as big as the auto industry. Why, because over time that industry has matured and there are better tools to diagnose cars. Uh, and so they're, they, they become easy to fix over time. We've, we've not made that leap with our applications. Um, the tools that the engineering team use to debug and troubleshoot their application are often still very different to what the dev ops team is using, um, which is very different to what maybe the SRE team is using. >>And so it's a huge problem in our industry. Um, really not being able to diagnose troubleshoot issues when they arise. It, it costs the industry, a fortune, it costs, you know, sort of in indirect wasted productivity of development teams, but it also costs in terms of customer experience. Um, I mean, you know, you and I both know is, look, if we're, if we're having a bad experience with maybe a new service that we're trying out online, w w we're probably going to go somewhere else. And so the there's never been like a more important time for people to invest in observing the entire environment, the entire customer experience, not only will you have happier customers, you might actually reduce the costs and improve the productivity in your engineering team as well. So I feel like the opportunity there is, is, is, is, is vast. Um, I also think longer term, um, it doesn't just apply to troubleshooting distributed applications. >>Um, I think the security systems are very related to the way we build software. Um, I mean, I think in, in, in the news in recent days, we've, we've come attuned, uh, uh, to, to software defects, um, or malware in software causing breaches and government agencies. Um, Hey, that, that could be anybody's software right there. Yeah. And so security has got a role to play in observability and the customer experience. It doesn't stop when they have a bad experience on the website. What if they complain? You know, what if a help desk ticket get, how do you track that? >>Yeah, I'm going to, I have a lot of questions for chassis tomorrow. One of them I'm going to ask him, and I want to get your thoughts on it. Cause you brought that up. And I think it's a key point, you know, building applications and supporting them and fixing them. It kind of reminds me of the old adage of, um, you know, you know, you gotta run it running the operation, 70% of the budget using to running it. If you look at what's happening and if you talk to customers and this is what I'm going to ask chassis tomorrow, Verner actually talked about, I on day two operations in his keynote. Yeah. I mean, this is Amazon they're, they're targeting builders. And so I talked to, um, a few other entrepreneurs, um, who were growing companies and some CIA CIOs and CEOs and the basic enterprises. >>They don't want to be building things like they, that's not their DNA. They don't build things like, that's not what they do. I mean, first of all, I love the builder mentality and with Amazon. Um, but they might be at a time where there might not be enough builders, Jeremy right out there. So you've got skill shortages and then ultimately are enterprises really builders. Yeah. They'll build something, but then they just run it it's. So, so at what point do they stop building or they build their own thing in the cloud and then they got to run it. So I think Amazon is going to shift quickly to day two operations, get bill, bill, bill run, run, run. >>Yeah. That's a great topic of conversation. I think what you sort of poking out is, is sort of the maturation of this digital age in the state that we're at. Um, I mean, if you, if you go back, you, you know, to, you know, 10, 10, 20 years, um, I mean, look at the mid nineties, um, there were a lot of people building custom applications, right? I mean, you know, it was innovation, it was all about building custom apps. And I think that golden era of application development whack that now, um, and, and customers in order to get competitive advantage, they are building their own applications. When you talk about digital transformation, what does that mean? Well, it means, you know, often a traditional company building a new digital experience for services that they've potentially offered in a physical way, uh, in the past. So make no mistake, P people are builders or they are writing code, they are becoming digital. >>I think what you'll find at some point as the industry's mature, some of these digital experience is become packaged. And so you can buy those off the shelf. And so there's less building required. But I think as we sit today, um, that there's probably more code been written in anger by more organizations that at any point in the last 30 years. And, and I think this is another reason why observability is so important, um, as you're building that code and as you're developing that customer experience, you want to be able to understand, um, where the issues are and, and, um, uh, like along the way, you don't want to wait until there's a, a big customer disaster on the day of you roll that, something to production before you start investigate. And you want to do that as you go. >>Yeah. And I think that's a kill. I do agree with you, by the way. I think the, there is a builder mentality, but it's probably right. But remember those days back in it, if you want to put our, our time machine hat on and go through the time machine is, you know, that was during the mainframe client server transition. And it was called spaghetti code. You know, it's like the monoliths were built and then it had to be supported and that became legacy. So I kind of see that happening today, where, um, people are moving to the cloud, they are building, but at some point you got to build your thing in the cloud. If I'm a company. And again, this isn't some dots trying to connect in real time. I got serverless, which is totally cool. I'm gonna have quantum has headroom for compute. >>I'm going to have, um, kind of a S a SOA service oriented architecture with web services, with observability. I'm gonna have all these modern apps great that, or run them. And I'm now I'm gonna shift them. Multiple clouds is so, you know, maybe the private cloud waves coming back, you're seeing telco clouds. You start to see these new tier. I won't say tier two clouds, but I mean, people will build their own cloud environment. There's no doubt as going to the cloud. And Steve Malania, Aviatrix kind of made this point yesterday in his analysis where he's like, he thinks private cloud will be back. I was just, it'll just be public cloud. People will build their own clouds and run them. >>Yeah. I feel well, what happens over time is, is the, the sort of line above which you would add value rises. So I kind of feel like, look, cloud is just going to the infrastructure. We can debate, you know, private cloud, public cloud. Is it a public cloud, or is it a private cloud served up by a public cloud provider? My view is, is look, all of that is, is, um, just going to be commodity, right? Um, it's going to be served up for an ever decreasing cost. And so then it's incumbent on organizations to innovate above that line. And, you know, 20 years ago, you know, we, we built our own data centers. Um, and now increasingly that, that seeming like a crazy idea. Um, and you know, now you can get almost all of your infrastructure from the cloud. The great thing is, I mean, look at observe. >>We have no people running data center operations, none, right? We have no people building a database, non, you know, we use snowflake in the cloud. It runs on AWS. We have, we have one dev ops, uh, engineer. And so all the people in the company right now, we're focused on adding value, helping people understand and analyze data, uh, above that line. And we just pay for a service level and, and look, uh, as time goes by, there's going to be more and more services and that line's going to rise. And so, you know, what, what I care about and what I think a lot of CEOs care about is are most of my resources innovating above that sort of value creation line, um, because that's what people are going to pay for in our business. And I think that's, what's going to represent you, you know, sort of value add for you, you know, organizations big and small. >>Yeah. That's a good point. I want to shift to the next topic and then we'll get into some observability questions I have for you and update on your company. Um, complexity has been a big theme. That's come out of all the conversations with analysts that have come on the cube, as you hear it with Amazon, a lot of undifferentiated, heavy lifting, being extracted away to your point about value layers and competing on value. Amazon continues to do that all great stuff, but some are saying, and we had said on the cube, yes, two days ago you put them complexity behind the curtain. It's still complexity, right? So, so complexity with the edge is highlighted. Uh, even though they got green, uh, I, um, edge core Greengrass, which has core thing, IOT core, a lot of cool things happening, but it's still not yet super easy. So complexity tends to slow things down became striction, what's your view on this? Because taming, the complexity seems to be a post COVID pandemic mandate for cloud journeys. What's your thing. >>Yeah, I totally agree. I think, I think in certainly you look organizations that have been in existence, but you know, 30, 40 years, or maybe even 10 years look at there's an amount of technical debt and complexity that you build up over time. Um, but even newer companies, um, the way that people are building modern distributed applications and in some respects is, is more complex than in days gone by, you know, microservices. Um, some of which maybe you own some of which maybe you don't, and what you've gotta be able to do is, is see the big picture, you know, w w when, when there's something in my code, but then when am I making a call out to maybe a third party microservice and, and that microservices bailing out on me, like people have got to see the big picture. And I think what hasn't been available as people have changed the architecture and their applications, there hasn't been an equivalent set of innovation or evolution in the tools that they use to manage that environment. And so you, you, you, you've got this sort of dichotomy of, uh, a better way for software developers to write code and deploy it into production microservices. But at the same time, you don't have good information and good tools to make sense of that complexity. >>That's great stuff. Jeremy Burton is here. He's the CEO of observe Inc cube, alumni, VIP cube alumni, by the way, has been on the cube every year, since the Q has been around 2010, when he took the new job as the CMO of EMC prior to being bought by Dell, Jeremy, you're a legend in the industry, certainly on as an executive and a marketer. And as an entrepreneur, um, I gotta ask you observe Inc, your company now, um, you're right in the middle of all this, you, you got a big bet going on. Could you share, in your opinion, your words, what is the big bet that you're making with observing? Uh, what are you betting on? How do you see the preferred future unfolding and where are you guys going to capture that value? >>Yes, I I'll big bat. Hey, uh, really is to take a new approach, um, in, in, in, in terms of enabling people to observe their systems, that the term observability actually goes back, uh, to a guy in control systems theory in the sixties. And then it's got quite a simple definition, which is, you know, being able to determine the, uh, I've been able to diagnose a system by the telemetry data that it emits. So let's look at the external outputs. And then based on that, can I determine the internal state of the application? And so from the get-go, we felt like observability was not about building another tool, right? We're not, you know, it's not about building another monitoring tool, a logging tool. Um, it's about analyzing data. And I, I was struck many years ago. Uh, I spent a bit of time with, with Andy McAfee, uh, from the sea sail lab at MIT. >>And he made a statement that I thought at the time was quite profound, which he said, look, everything's a matter of data. If you have enough data, you can solve any problem. And that stuck with me for a long time. And, um, you know, observe really what we do is we ingest vast quantities of telemetry data. We treat everything as events and we try and make sense of it. And the economics of the infrastructure now is such, that is you truly can ingest all the Alltel telemetry data and it's affordable, right? I mean, one of the wonderful things that Amazon has done is they've brought you, you know, very cheap, affordable storage. You can ingest all your data and keep it forever. Um, but, but now can you make sense of it? Well, you know, compute is pretty cheap these days and you've got amazing processing engines like snowflake. >>And so I was sense was that if we could allow folks to ingest all of this telemetry data process, that data and help people easily analyze that data, then they could find almost any problem that existed, uh, in their applications or in their infrastructure. So we really set out to create a data company, which I think is fundamentally different to, to really what everybody else is doing. And today we're troubleshooting distributed applications, but I think in future, we, my hope is that we can, we can help people analyze almost anything around their applications or infrastructure. >>And what's the use case problem statement that you're entering the market on? Is it just making sure microservices can be deployed as a Kubernetes? Is it managing containers? Is there a specific, um, customer adoption use case that you're focused on right now? >>Yeah, we've tried to target our ideal customer if you like has been the three or 4,000, uh, uh, SAS companies. Uh, we're, we're really focused on the U S right now, but three to 5,000 SAS companies, um, predominantly, uh, obviously running on AWS often, uh, Kubernetes infrastructure, but, you know, people who, uh, having a hard time, uh, understanding the complexity of the application that they've created, and they're having a hard time understanding, uh, the experience that their customers are having and tracking that back to root cause. So, you know, really helping those SAS companies troubleshoot their applications and having a better customer experience that's where the early customers are. And if we can do a good job in that area, I think we can, you know, over time, you know, start to take on some of the bigger companies and maybe some of the more established companies that are moving in this, this digital direction. >>Jeremy, thanks for sharing that. And I got one last set of questions for you around the industry, but before I get there, give a quick plug for observe. What are you guys looking to do hire, I mean, give a quick, uh, a PSA on what's going on with observed. >>Yeah, so we're, uh, the company is now what a rough and tough. About three years old, we got about 40 people. Uh we're well-funded by sort of Hill ventures. Uh, they were the original investors in, in snowflake. Um, and, um, yeah, I mean, we we've, we've well, more than doubled in size since the COVID lockdown began. We had about 15 people when that began. We've got almost 40 now. Um, and I would anticipate in the next year we're, we're probably going to double in size again, but, um, yeah, really the core focus in the company is, is understanding and analyzing vast quantities of data. And so anybody who is interested in, uh, that space look us up >>Mainly any areas, obviously engineering and the other areas okay. >>Near in all over. I mean, we, you know, w w w as you'll see, if you go to observing.com, we've got a pretty slick front end. Uh, we invested very early on in design and UX design. So we believe that you are, can be a differentiator. So we've got some amazing engineers on the front end. Uh, so going to can always do with the help there, but obviously, um, you know, there's a data processing platform here as well. Um, we, uh, we do run on top of snowflake. We, we do have a number of folks here who are very familiar, uh, you know, with the snowflake database and, and how to write efficiency equals. So, so front and backend. Um, we very soon, I think we'll be starting to expand the sales team. Um, we're really starting to get our initial set of customers and the feedback loop rule in rolling into engineering. And my hope would be, you know, probably early part of next year, we re we really start to nail the product market fit. Um, and we've got a huge release coming in the early part of next year where that the metrics and alerting functionality will be in the product. So, yeah, it's, it's sort of all systems go right now. >>Congratulations. Love to see the entrepreneurial journey. We'll keep an eye out for you and you're in a hot space. So we'll be riding, you'll be riding that wave, uh, question for you on the, um, just kind of the industry, uh, you're in the heart of Silicon Valley. Like I am honestly, I'm fellow Alto, you're up in the Hillsborough area. Um, I think you're in Hillsborough, right? That's where you, where you live. Um, San Francisco, the Valley, the pandemic pretty hard hit right now. People are sheltering in place, but still a lot of activity. Um, what are you hearing in, um, in, in the VC circles, startup circles, as everyone looks at coming out of the pandemic and you look at Amazon and you look at what snowflake has done. I mean, snowflake was built on top of Amazon competing against Redshift. Um, okay. They were hugely successful at doing that. So there's kind of this new playbook emerging. What are, what are people talking about? What's the scuttlebutt. >>Yeah. I mean, clearly TAC has done very well throughout what has been, you know, like just a terrible environment. Um, I think both kind of socially and economically, and I think what's going on in the stock market right now is probably not reflective of the, of the economic situation. And I think a lot of the indices are dominated by tech companies. So you, if you're not careful, you can get a little bit of a false read. Um, but look, what is undisputed is, is that the world is going to become more digital, more tech centric than, than less. Um, so I think there is a very, very bright future, you know, for tech, um, that there is certainly plenty of VC money, um, available. Um, you know, that is not really changed materially in the last year. Um, so if you have a good idea, if you're on one of these major trends, I think that there is a very good chance that you can get the company funded. >>Um, and you know, our, our expectation is that, you know, next year, obviously industries are going to return to work that have been dominant maybe for the last six, nine months. And so some parts of the economy should pick up again, but I would also tell you, I think certain, uh, sort of habits are not going to die. I mean, I think more things are going to be done online and we've gotten used to that way of working and, and you know, what, not, some of it is measurable. I don't know about cocktails over zoom, but working with customers, um, in some respects is easier because they're not traveling, we're not traveling. So we both have more time. Uh, it's sometimes easy to get meetings with people that you would never get. Now. Now, can you do an efficient sales process, education proof of concept? You know, those processes maybe have to grow up a little bit to be taken online, but I think the certain parts of the last, maybe six to nine months that we don't want to throw away and go back to the way we were doing it, because I think, you know, maybe this way of doing it is, is more efficient. >>What do you think about the, uh, entrepreneurial journeys out there? Obviously, um, Amazon we're here covering re-invent is really kind of, you know, building a massive compute engine. They've got higher level services and, you know, I've been speculating for years. I think snowflake is the first kind of big sign. That points to kind of what I said five years ago, which is there's going to be an opportunity for these other clouds as specialty clouds. I called them might be the wrong word, but snowflake basically built on top of Amazon, you know, most valuable company ever on wall street, uh, IPO on someone else's cloud. So is that a playbook? I mean, is that a move? I mean, this is kind of like a new thing. >>Yeah. I mean, that's, I mean, I, I feel like on databases, I've got a lot of history on management, Oracle almost 10 years. And you know, what snowflake does they did was they, they rearchitected the database explicitly for the cloud. I mean, you can run Oracle on the cloud, but, but it, but it doesn't do things the way that snowflake does it. Right. I mean, snowflake uses commodity storage. It uses S3 it's elastic. And so when you're not using it, you're not paying it. And these things sound very simple and very obvious now, which is I think what, what, what the genius of the founders, you know, Ben Warren and Tre, uh, work, and, and I think there will be other costs, you know, categories of infrastructure that will get rearchitected and reinvented for the cloud. And, you know, I've got equally big opportunities. Um, and so, yeah, I mean, I think the model, I believe firmly that the model is if you're a startup, you don't need to waste a lot of time, like reinventing the wheel on data center, infrastructure and databases, and a lot of the services that you would use to construct an application. >>You, you, you can start, you know, if, if the building that you're trying to build is like 12 floors, you can start at the eighth or ninth floor. Um, you know, I've, I've got like what three or 400 quality engineers at snowflake that are building our database. I don't, I don't need to do that. I can just piggyback on top of what they've done and add value. And, you know, the, the, the beautiful thing, you know, now, if you're a business out there thinking of, of, of, of becoming digital and reinventing yourself, or you're a startup just getting going, there's a lot of stuff you just don't have to build anymore. You just don't even have to think about it. >>Yeah. This is the new program of bull internet. It's internet, truly 2.0 or 3.0, whatever 4.0, a complete reset of online. And I think the pandemic, as you pointed out on many cube interviews and Andy Jassy send his keynote is on full display right now. And I think the smart money and smart entrepreneurs are going to see the opportunities. Okay. >>Yeah. It comes back to ideas and a great, I mean, I've always been a product person. Um, but look at great idea, a great product idea and a great product idea that, that capitalizes on the big trends in the industry. I think there's always going to be funding for those kinds of things. I don't know a lot about the consumer world I've always worked in, in B2B, but, um, you know, the kind of things that you're going to be able to do in future. I mean, think about it. If storage is essentially free and compute is essentially free. Just imagine what you could do, right. Jeremy, >>This is the new consumer. Get out. Let's understand that. Finally, B2B is the new consumer enterprise is hot. I was, again, it was riffing on this all week. All the things going on in enterprise is complex is now the new consumers now all connected. It's all one thing. The consumerization of it, the condition of computing has happened. It's going on. So you're a leader. Thank you for coming on. Great to see you as always, um, say hi to your family and stay safe. >>Yeah, you too. Thanks for the invite. Always, always a pleasure. >>Jeremy Burton breaking down the analysis of day two of week three of re-invent coverage. I'm John furry with the cube virtual. We're not in person anymore. Virtualization has allowed us to do more interviews over 110 interviews so far for re-invent and tomorrow, Thursday at two o'clock, Andy Jassy will spend 30 minutes with me here on the cube, looking back at re-invent the highs, the lows, and what's next for Amazon web services. I'm chef Aria. Thanks for watching.

>> Announcer: From around the globe, it's theCube with digital coverage of MIT, Chief Data Officer and Information Quality Symposium brought to you by Silicon Angle Media. >> Hi, I'm Stu Miniman and this is the seventh year of theCubes coverage of the MIT, Chief Data Officer and Information Quality Symposium. We love getting to talk to these chief data officers and the people in this ecosystem, the importance of data, driving data-driven cultures, and really happy to welcome to the program, first time guests Eileen Vitrine, Eileen is the Chief Data Officer for the United States Air Force, Eileen, thank you so much for joining us. >> Thank you Stu really excited about being here today. >> All right, so the United States Air Force, I believe had it first CDO office in 2017, you were put in the CDO role in June of 2018. If you could, bring us back, give us how that was formed inside the Air force and how you came to be in that role. >> Well, Stu I like to say that we are a startup organization and a really mature organization, so it's really about culture change and it began by bringing a group of amazing citizen airman reservists back to the Air Force to bring their skills from industry and bring them into the Air Force. So, I like to say that we're a total force because we have active and reservists working with civilians on a daily basis and one of the first things we did in June was we stood up a data lab, that's based in the Jones building on Andrews Air Force Base. And there, we actually take small use cases that have enterprise focus, and we really try to dig deep to try to drive data insights, to inform senior leaders across the department on really important, what I would call enterprise focused challenges, it's pretty exciting. >> Yeah, it's been fascinating when we've dug into this ecosystem, of course while the data itself is very sensitive and I'm sure for the Air Force, there are some very highest level of security, the practices that are done as to how to leverage data, the line between public and private blurs, because you have people that have come from industry that go into government and people that are from government that have leveraged their experiences there. So, if you could give us a little bit of your background and what it is that your charter has been and what you're looking to build out, as you mentioned that culture of change. >> Well, I like to say I began my data leadership journey as an active duty soldier in the army, and I was originally a transportation officer, today we would use the title condition based maintenance, but back then, it was really about running the numbers so that I could optimize my truck fleet on the road each and every day, so that my soldiers were driving safely. Data has always been part of my leadership journey and so I like to say that one of our challenges is really to make sure that data is part of every airmans core DNA, so that they're using the right data at the right level to drive insights, whether it's tactical, operational or strategic. And so it's really about empowering each and every airman, which I think is pretty exciting. >> There's so many pieces of that data, you talk about data quality, there's obviously the data life cycle. I know your presentation that you're given here at the CDO, IQ talks about the data platform that your team has built, could you explain that? What are the key tenants and what maybe differentiates it from what other organizations might have done? >> So, when we first took the challenge to build our data lab, we really wanted to really come up. Our goal was to have a cross domain solution where we could solve data problems at the appropriate classification level. And so we built the VAULT data platform, VAULT stands for visible, accessible, understandable, linked, and trustworthy. And if you look at the DOD data strategy, they will also add the tenants of interoperability and secure. So, the first steps that we have really focused on is making data visible and accessible to airmen, to empower them, to drive insights from available data to solve their problems. So, it's really about that data empowerment, we like to use the hashtag built by airmen because it's really about each and every airman being part of the solution. And I think it's really an exciting time to be in the Air Force because any airman can solve a really hard challenge and it can very quickly wrap it up rapidly, escalate up with great velocity to senior leadership, to be an enterprise solution. >> Is there some basic training that goes on from a data standpoint? For any of those that have lived in data, oftentimes you can get lost in numbers, you have to have context, you need to understand how do I separate good from bad data, or when is data still valid? So, how does someone in the Air Force get some of that beta data competency? >> Well, we have taken a multitenant approach because each and every airman has different needs. So, we have quite a few pathfinders across the Air Force today, to help what I call, upscale our total force. And so I developed a partnership with the Air Force Institute of Technology and they now have a online graduate level data science certificate program. So, individuals studying at AFIT or remotely have the opportunity to really focus on building up their data touchpoints. Just recently, we have been working on a pathfinder to allow our data officers to get their ICCP Federal Data Sector Governance Certificate Program. So, we've been running what I would call short boot camps to prep data officers to be ready for that. And I think the one that I'm most excited about is that this year, this fall, new cadets at the U.S Air Force Academy will be able to have an undergraduate degree in data science and so it's not about a one prong approach, it's about having short courses as well as academe solutions to up skill our total force moving forward. >> Well, information absolutely is such an important differentiator(laughs) in general business and absolutely the military aspects are there. You mentioned the DOD talks about interoperability in their platform, can you speak a little bit to how you make sure that data is secure? Yet, I'm sure there's opportunities for other organizations, for there to be collaboration between them. >> Well, I like to say, that we don't fight alone. So, I work on a daily basis with my peers, Tom Cecila at the Department of Navy and Greg Garcia at the Department of Army, as well as Mr. David Berg in the DOD level. It's really important that we have an integrated approach moving forward and in the DOD we partner with our security experts, so it's not about us doing security individually, it's really about, in the Air Force we use a term called digital air force, and it's about optimizing and building a trusted partnership with our CIO colleagues, as well as our chief management colleagues because it's really about that trusted partnership to make sure that we're working collaboratively across the enterprise and whatever we do in the department, we also have to reach across our services so that we're all working together. >> Eileen, I'm curious if there's been much impact from the global pandemic. When I talk to enterprise companies, that they had to rapidly make sure that while they needed to protect data, when it was in their four walls and maybe for VPN, now everyone is accessing data, much more work from home and the like. I have to imagine some of those security measures you've already taken, but have there anything along those lines or anything else that this shift in where people are, and a little bit more dispersed has impacted your work? >> Well, the story that I like to say is, that this has given us velocity. So, prior to COVID, we built our VAULT data platform as a multitenancy platform that is also cross-domain solution, so it allows people to develop and do their problem solving in an appropriate classification level. And it allows us to connect or pushup if we need to into higher classification levels. The other thing that it has helped us really work smart because we do as much as we can in that unclassified environment and then using our cloud based solution in our gateways, it allows us to bring people in at a very scheduled component so that we maximize, or we optimize their time on site. And so I really think that it's really given us great velocity because it has really allowed people to work on the right problem set, on the right class of patient level at a specific time. And plus the other pieces, we look at what we're doing is that the problem set that we've had has really allowed people to become more data focused. I think that it's personal for folks moving forward, so it has increased understanding in terms of the need for data insights, as we move forward to drive decision making. It's not that data makes the decision, but it's using the insight to make the decision. >> And one of the interesting conversations we've been having about how to get to those data insights is the use of things like machine learning, artificial intelligence, anything you can share about, how you're looking at that journey, where you are along that discovery. >> Well, I love to say that in order to do AI and machine learning, you have to have great volumes of high quality data. And so really step one was visible, accessible data, but we in the Department of the Air Force stood up an accelerator at MIT. And so we have a group of amazing airmen that are actually working with MIT on a daily basis to solve some of those, what I would call opportunities for us to move forward. My office collaborates with them on a consistent basis, because they're doing additional use cases in that academic environment, which I'm pretty excited about because I think it gives us access to some of the smartest minds. >> All right, Eileen also I understand it's your first year doing the event. Unfortunately, we don't get, all come together in Cambridge, walking those hallways and being able to listen to some of those conversations and follow up is something we've very much enjoyed over the years. What excites you about being interact with your peers and participating in the event this year? >> Well, I really think it's about helping each other leverage the amazing lessons learned. I think that if we look collaboratively, both across industry and in the federal sector, there have been amazing lessons learned and it gives us a great forum for us to really share and leverage those lessons learned as we move forward so that we're not hitting the reboot button, but we actually are starting faster. So, it comes back to the velocity component, it all helps us go faster and at a higher quality level and I think that's really exciting. >> So, final question I have for you, we've talked for years about digital transformation, we've really said that having that data strategy and that culture of leveraging data is one of the most critical pieces of having gone through that transformation. For people that are maybe early on their journey, any advice that you'd give them, having worked through a couple of years of this and the experience you've had with your peers. >> I think that the first thing is that you have to really start with a blank slate and really look at the art of the possible. Don't think about what you've always done, think about where you want to go because there are many different paths to get there. And if you look at what the target goal is, it's really about making sure that you do that backward tracking to get to that goal. And the other piece that I tell my colleagues is celebrate the wins. My team of airmen, they are amazing, it's an honor to serve them and the reality is that they are doing great things and sometimes you want more. And it's really important to celebrate the victories because it's a very long journey and we keep moving the goalposts because we're always striving for excellence. >> Absolutely, it is always a journey that we're on, it's not about the destination. Eileen, thank you so much for sharing all that you've learned and glad you could participate. >> Thank you, STU, I appreciate being included today. Have a great day. >> Thanks and thank you for watching theCube. I'm Stu Miniman stay tuned for more from the MIT, CDO IQ event. (lively upbeat music)

>> Announcer: From around the globe, it's theCUBE with digital coverage of MIT Chief Data Officer and Information Quality symposium brought to you by SiliconANGLE Media. >> Hi everybody. This is Dave Vellante and welcome back to theCUBE's coverage of the MIT CDOIQ 2020 event. Of course, it's gone virtual. We wish we were all together in Cambridge. They were going to move into a new building this year for years they've done this event at the Tang Center, moving into a new facility, but unfortunately going to have to wait at least a year, we'll see, But we've got a great guest. Nonetheless, Doug Laney is here. He's a Business Value Strategist, the bestselling author, an analyst, consultant then a long time CUBE friend. Doug, great to see you again. Thanks so much for coming on. >> Dave, great to be with you again as well. So can I ask you? You have been an advocate for obviously measuring the value of data, the CDO role. I don't take this the wrong way, but I feel like the last 150 days have done more to accelerate people's attention on the importance of data and the value of data than all the great work that you've done. What do you think? (laughing) >> It's always great when organizations, actually take advantage of some of these concepts of data value. You may be speaking specifically about the situation with United Airlines and American Airlines, where they have basically collateralized their customer loyalty data, their customer loyalty programs to the tunes of several billion dollars each. And one of the things that's very interesting about that is that the third party valuations of their customer loyalty data, resulted in numbers that were larger than the companies themselves. So basically the value of their data, which is as we've discussed previously off balance sheet is more valuable than the market cap of those companies themselves, which is just incredibly fascinating. >> Well, and of course, all you have to do is look to the Trillionaire's Club. And now of course, Apple pushing two trillion to really see the value that the market places on data. But the other thing is of course, COVID, everybody talks about the COVID acceleration. How have you seen it impact the awareness of the importance of data, whether it applies to business resiliency or even new monetization models? If you're not digital, you can't do business. And digital is all about data. >> I think the major challenge that most organizations are seeing from a data and analytics perspective due to COVID is that their traditional trend based forecast models are broken. If you're a company that's only forecasting based on your own historical data and not taking into consideration, or even identifying what are the leading indicators of your business, then COVID and the economic shutdown have entirely broken those models. So it's raised the awareness of companies to say, "Hey, how can we predict our business now? We can't do it based on our own historical data. We need to look externally at what are those external, maybe global indicators or other kinds of markets that proceed our own forecasts or our own activity." And so the conversion from trend based forecast models to what we call driver based forecast models, isn't easy for a lot of organizations to do. And one of the more difficult parts is identifying what are those external data factors from suppliers, from customers, from partners, from competitors, from complimentary products and services that are leading indicators of your business. And then recasting those models and executing on them. >> And that's a great point. If you think about COVID and how it's changed things, everything's changed, right? The ideal customer profile has changed, your value proposition to those customers has completely changed. You got to rethink that. And of course, it's very hard to predict even when this thing eventually comes back, some kind of hybrid mode, you used to be selling to people in an office environment. That's obviously changed. There's a lot that's permanent there. And data is potentially at least the forward indicator, the canary in the coal mine. >> Right. It also is the product and service. So not only can it help you and improve your forecasting models, but it can become a product or service that you're offering. Look at us right now, we would generally be face to face and person to person, but we're using video technology to transfer this content. And then one of the things that I... It took me awhile to realize, but a couple of months after the COVID shutdown, it occurred to me that even as a consulting organization, Caserta focuses on North America. But the reality is that every consultancy is now a global consultancy because we're all doing business remotely. There are no particular or real strong localization issues for doing consulting today. >> So we talked a lot over the years about the role of the CDO, how it's evolved, how it's changed the course of the early... The pre-title days it was coming out of a data quality world. And it's still vital. Of course, as we heard today from the Keynote, it's much more public, much more exposed, different public data sources, but the role has certainly evolved initially into regulated industries like financial, healthcare and government, but now, many, many more organizations have a CDO. My understanding is that you're giving a talk in the business case for the CDO. Help us understand that. >> Yeah. So one of the things that we've been doing here for the last couple of years is a running an ongoing study of how organizations are impacted by the role of the CDO. And really it's more of a correlation and looking at what are some of the qualities of organizations that have a CDO or don't have a CDO. So some of the things we found is that organizations with a CDO nearly twice as often, mention the importance of data and analytics in their annual report organizations with a C level CDO, meaning a true executive are four times more often likely to be using data, to transform the business. And when we're talking about using data and advanced analytics, we found that organizations with a CIO, not a CDO responsible for their data assets are only half as likely to be doing advanced analytics in any way. So there are a number of interesting things that we found about companies that have a CDO and how they operate a bit differently. >> I want to ask you about that. You mentioned the CIO and we're increasingly seeing lines of reporting and peer reporting alter shift. The sands are shifting a little bit. In the early days the CDO and still predominantly I think is an independent organization. We've seen a few cases and increasingly number where they're reporting into the CIO, we've seen the same thing by the way with the chief Information Security Officer, which used to be considered the fox watching the hen house. So we're seeing those shifts. We've also seen the CDO become more aligned with a technical role and sometimes even emerging out of that technical role. >> Yeah. I think the... I don't know, what I've seen more is that the CDOs are emerging from the business, companies are realizing that data is a business asset. It's not an IT asset. There was a time when data was tightly coupled with applications of technologies, but today data is very easily decoupled from those applications and usable in a wider variety of contexts. And for that reason, as data gets recognized as a business, not an IT asset, you want somebody from the business responsible for overseeing that asset. Yes, a lot of CDOs still report to the CIO, but increasingly more CDOs you're seeing and I think you'll see some other surveys from other organizations this week where the CDOs are more frequently reporting up to the CEO level, meaning they're true executives. Along I advocated for the bifurcation of the IT organization into separate I and T organizations. Again, there's no reason other than for historical purposes to keep the data and technology sides of the organizations so intertwined. >> Well, it makes sense that the Chief Data Officer would have an affinity with the lines of business. And you're seeing a lot of organizations, really trying to streamline their data pipeline, their data life cycles, bringing that together, infuse intelligence into that, but also take a systems view and really have the business be intimately involved, if not even owned into the data. You see a lot of emphasis on self-serve, what are you seeing in terms of that data pipeline or the data life cycle, if you will, that used to be wonky, hard core techies, but now it really involving a lot more constituent. >> Yeah. Well, the data life cycle used to be somewhat short. The data life cycles, they're longer and they're more a data networks than a life cycle and or a supply chain. And the reason is that companies are finding alternative uses for their data, not just using it for a single operational purpose or perhaps reporting purpose, but finding that there are new value streams that can be generated from data. There are value streams that can be generated internally. There are a variety of value streams that can be generated externally. So we work with companies to identify what are those variety of value streams? And then test their feasibility, are they ethically feasible? Are they legally feasible? Are they economically feasible? Can they scale? Do you have the technology capabilities? And so we'll run through a process of assessing the ideas that are generated. But the bottom line is that companies are realizing that data is an asset. It needs to be not just measured as one and managed as one, but also monetized as an asset. And as we've talked about previously, data has these unique qualities that it can be used over and over again, and it generate more data when you use it. And it can be used simultaneously for multiple purposes. So companies like, you mentioned, Apple and others have built business models, based on these unique qualities of data. But I think it's really incumbent upon any organization today to do so as well. >> But when you observed those companies that we talk about all the time, data is at the center of their organization. They maybe put people around that data. That's got to be one of the challenge for many of the incumbents is if we talked about the data silos, the different standards, different data quality, that's got to be fairly major blocker for people becoming a "Data-driven organization." >> It is because some organizations were developed as people driven product, driven brand driven, or other things to try to convert. To becoming data-driven, takes a high degree of data literacy or fluency. And I think there'll be a lot of talk about that this week. I'll certainly mention it as well. And so getting the organization to become data fluent and appreciate data as an asset and understand its possibilities and the art of the possible with data, it's a long road. So the culture change that goes along with it is really difficult. And so we're working with 150 year old consumer brand right now that wants to become more data-driven and they're very product driven. And we hear the CIO say, "We want people to understand that we're a data company that just happens to produce this product. We're not a product company that generates data." And once we realized that and started behaving in that fashion, then we'll be able to really win and thrive in our marketplace. >> So one of the key roles of a Chief Data Officers to understand how data affects the monetization of an organization. Obviously there are four profit companies of your healthcare organization saving lives, obviously being profitable as well, or at least staying within the budget, depending upon the structure of the organization. But a lot of people I think oftentimes misunderstand that it's like, "Okay, do I have to become a data broker? Am I selling data directly?" But I think, you pointed out many times and you just did that unlike oil, that's why we don't like that data as a new oil analogy, because it's so much more valuable and can be use, it doesn't fall because of its scarcity. But what are you finding just in terms of people's application of that notion of monetization? Cutting costs, increasing revenue, what are you seeing in the field? What's that spectrum look like? >> So one of the things I've done over the years is compile a library of hundreds and hundreds of examples of how organizations are using data and analytics in innovative ways. And I have a book in process that hopefully will be out this fall. I'm sharing a number of those inspirational examples. So that's the thing that organizations need to understand is that there are a variety of great examples out there, and they shouldn't just necessarily look to their own industry. There are inspirational examples from other industries as well, many clients come to me and they ask, "What are others in my industry doing?" And my flippant response to that is, "Why do you want to be in second place or third place? Why not take an idea from another industry, perhaps a digital product company and apply that to your own business." But like you mentioned, there are a variety of ways to monetize data. It doesn't involve necessarily selling it. You can deliver analytics, you can report on it, you can use it internally to generate improved business process performance. And as long as you're measuring how data's being applied and what its impact is, then you're in a position to claim that you're monetizing it. But if you're not measuring the impact of data on business processes or on customer relationships or partner supplier relationships or anything else, then it's difficult to claim that you're monetizing it. But one of the more interesting ways that we've been working with organizations to monetize their data, certainly in light of GDPR and the California consumer privacy act where I can't sell you my data anymore, but we've identified ways to monetize your customer data in a couple of ways. One is to synthesize the data, create synthetic data sets that retain the original statistical anomalies in the data or features of the data, but don't share actually any PII. But another interesting way that we've been working with organizations to monetize their data is what I call, Inverted data monetization, where again, I can't share my customer data with you, but I can share information about your products and services with my customers. And take a referral fee or a commission, based on that. So let's say I'm a hospital and I can't sell you my patient data, of course, due to variety of regulations, but I know who my diabetes patients are, and I can introduce them to your healthy meal plans, to your gym memberships, to your at home glucose monitoring kits. And again, take a referral fee or a cut of that action. So we're working with customers and the financial services firm industry and in the healthcare industry on just those kinds of examples. So we've identified hundreds of millions of dollars of incremental value for organizations that from their data that we're just sitting on. >> Interesting. Doug because you're a business value strategist at the top, where in the S curve do you see you're able to have the biggest impact. I doubt that you enter organizations where you say, "Oh, they've got it all figured out. They can't use my advice." But as well, sometimes in the early stages, you may not be able to have as big of an impact because there's not top down support or whatever, there's too much technical data, et cetera, where are you finding you can have the biggest impact, Doug? >> Generally we don't come in and run those kinds of data monetization or information innovation exercises, unless there's some degree of executive support. I've never done that at a lower level, but certainly there are lower level more immediate and vocational opportunities for data to deliver value through, to simply analytics. One of the simple examples I give is, I sold a home recently and when you put your house on the market, everybody comes out of the woodwork, the fly by night, mortgage companies, the moving companies, the box companies, the painters, the landscapers, all know you're moving because your data is in the U.S. and the MLS directory. And it was interesting. The only company that didn't reach out to me was my own bank, and so they lost the opportunity to introduce me to a Mortgage they'd retain me as a client, introduce me to my new branch, print me new checks, move the stuff in my safe deposit box, all of that. They missed a simple opportunity. And I'm thinking, this doesn't require rocket science to figure out which of your customers are moving, the MLS database or you can harvest it from Zillow or other sites is basically public domain data. And I was just thinking, how stupid simple would it have been for them to hire a high school programmer, give him a can of red bull and say, "Listen match our customer database to the MLS database to let us know who's moving on a daily or weekly basis." Some of these solutions are pretty simple. >> So is that part of what you do, come in with just hardcore tactical ideas like that? Are you also doing strategy? Tell me more about how you're spending your time. >> I trying to think more of a broader approach where we look at the data itself and again, people have said, "If you tortured enough, what would you tell us? We're just take that angle." We look at examples of how other organizations have monetized data and think about how to apply those and adapt those ideas to the company's own business. We look at key business drivers, internally and externally. We look at edge cases for their customers' businesses. We run through hypothesis generating activities. There are a variety of different kinds of activities that we do to generate ideas. And most of the time when we run these workshops, which last a week or two, we'll end up generating anywhere from 35 to 50 pretty solid ideas for generating new value streams from data. So when we talk about monetizing data, that's what we mean, generating new value streams. But like I said, then the next step is to go through that feasibility assessment and determining which of these ideas you actually want to pursue. >> So you're of course the longtime industry watcher as well, as a former Gartner Analyst, you have to be. My question is, if I think back... I've been around a while. If I think back at the peak of Microsoft's prominence in the PC era, it was like windows 95 and you felt like, "Wow, Microsoft is just so strong." And then of course the Linux comes along and a lot of open source changes and low and behold, a whole new set of leaders emerges. And you see the same thing today with the Trillionaire's Club and you feel like, "Wow, even COVID has been a tailwind for them." But you think about, "Okay, where could the disruption come to these large players that own huge clouds, they have all the data." Is data potentially a disruptor for what appear to be insurmountable odds against the newbies" >> There's always people coming up with new ways to leverage data or new sources of data to capture. So yeah, there's certainly not going to be around for forever, but it's been really fascinating to see the transformation of some companies I think nobody really exemplifies it more than IBM where they emerged from originally selling meat slicers. The Dayton Meat Slicer was their original product. And then they evolved into Manual Business Machines and then Electronic Business Machines. And then they dominated that. Then they dominated the mainframe software industry. Then they dominated the PC industry. Then they dominated the services industry to some degree. And so they're starting to get into data. And I think following that trajectory is something that really any organization should be looking at. When do you actually become a data company? Not just a product company or a service company or top. >> We have Inderpal Bhandari is one of our huge guests here. He's a Chief-- >> Sure. >> Data Officer of IBM, you know him well. And he talks about the journey that he's undertaken to transform the company into a data company. I think a lot of people don't really realize what's actually going on behind the scenes, whether it's financially oriented or revenue opportunities. But one of the things he stressed to me in our interview was that they're on average, they're reducing the end to end cycle time from raw data to insights by 70%, that's on average. And that's just an enormous, for a company that size, it's just enormous cost savings or revenue generating opportunity. >> There's no doubt that the technology behind data pipelines is improving and the process from moving data from those pipelines directly into predictive or diagnostic or prescriptive output is a lot more accelerated than the early days of data warehousing. >> Is the skills barrier is acute? It seems like it's lessened somewhat, the early Hadoop days you needed... Even data scientist... Is it still just a massive skill shortage, or we're starting to attack that. >> Well, I think companies are figuring out a way around the skill shortage by doing things like self service analytics and focusing on more easy to use mainstream type AI or advanced analytics technologies. But there's still very much a need for data scientists and organizations and the difficulty in finding people that are true data scientists. There's no real certification. And so really anybody can call themselves a data scientist but I think companies are getting good at interviewing and determining whether somebody's got the goods or not. But there are other types of skills that we don't really focus on, like the data engineering skills, there's still a huge need for data engineering. Data doesn't self-organize. There are some augmented analytics technologies that will automatically generate analytic output, but there really aren't technologies that automatically self-organize data. And so there's a huge need for data engineers. And then as we talked about, there's a large interest in external data and harvesting that and then ingesting it and even identifying what external data is out there. So one of the emerging roles that we're seeing, if not the sexiest role of the 21st century is the role of the Data Curator, somebody who acts as a librarian, identifying external data assets that are potentially valuable, testing them, evaluating them, negotiating and then figuring out how to ingest that data. So I think that's a really important role for an organization to have. Most companies have an entire department that procures office supplies, but they don't have anybody who's procuring data supplies. And when you think about which is more valuable to an organization? How do you not have somebody who's dedicated to identifying the world of external data assets that are out there? There are 10 million data sets published by government, organizations and NGOs. There are thousands and thousands of data brokers aggregating and sharing data. There's a web content that can be harvested, there's data from your partners and suppliers, there's data from social media. So to not have somebody who's on top of all that it demonstrates gross negligence by the organization. >> That is such an enlightening point, Doug. My last question is, I wonder how... If you can share with us how the pandemic has effected your business personally. As a consultant, you're on the road a lot, obviously not on the road so much, you're doing a lot of chalk talks, et cetera. How have you managed through this and how have you been able to maintain your efficacy with your clients? >> Most of our clients, given that they're in the digital world a bit already, made the switch pretty quick. Some of them took a month or two, some things went on hold but we're still seeing the same level of enthusiasm for data and doing things with data. In fact some companies have taken our (mumbles) that data to be their best defense in a crisis like this. It's affected our business and it's enabled us to do much more international work more easily than we used to. And I probably spend a lot less time on planes. So it gives me more time for writing and speaking and actually doing consulting. So that's been nice as well. >> Yeah, there's that bonus. Obviously theCUBE yes, we're not doing physical events anymore, but hey, we've got two studios operating. And Doug Laney, really appreciate you coming on. (Dough mumbles) Always a great guest and sharing your insights and have a great MIT CDOIQ. >> Thanks, you too, Dave, take care. (mumbles) >> Thanks Doug. All right. And thank you everybody for watching. This is Dave Vellante for theCUBE, our continuous coverage of the MIT Chief Data Officer conference, MIT CDOIQ, will be right back, right after this short break. (bright music)

>>from around the globe If the cube with digital coverage of M I t. Chief data officer and Information quality symposium brought to you by Silicon Angle Media >>Hello, everyone. This is Day Volonte and welcome back to our continuing coverage of the M I t. Chief Data Officer CDO I Q event Interpol Bhandari is here. He's a leading voice in the CDO community and a longtime Cubillan Interpol. Great to see you. Thanks for coming on for this. Especially >>program. My pleasure. >>So when you you and I first met, you laid out what I thought was, you know, one of the most cogent frameworks to understand what a CDO is job was where the priority should be. And one of those was really understanding how, how, how data contributes to the monetization of station aligning with lines of business, a number of other things. And that was several years ago. A lot of change since then. You know, we've been doing this conference since probably twenty thirteen and back then, you know, Hadoop was coming on strong. A lot of CEOs didn't want to go near the technology that's beginning to change. CDOs and cto Zehr becoming much more aligned at the hip. The reporting organizations have changed. But I love your perspective on what you've observed as changing in the CDO roll over the last half decade or so. >>Well, did you know that I became chief data officer in two thousand six? December two thousand and six And I have done this job four times four major overnight have created of the organization from scratch each time. Now, in December of two thousand six, when I became chief data officer, there were only four. Chief Data Officer, uh, boom and I was the first in health care, and there were three, three others, you know, one of the Internet one and credit guns one and banking. And I think I'm the only one actually left standing still doing this job. That's a good thing or a bad thing. But like, you know, it certainly has allowed me to love the craft and then also scripted down to the level that, you know, I actually do think of it purely as a craft. That is. I know, going into a mutual what I'm gonna do. They were on the central second. No, the interesting things that have unfolded. Obviously, the professions taken off There are literally thousands off chief data officers now, and there are plenty off changes. I think the main change, but the job is it's, I think, a little less daunting in terms off convincing the senior leadership that it's need it because I think the awareness at the CEO level is much, much, much better than what it waas in two thousand six. Across the world. Now, having said that, I think it is still only awareness and don't think that there's really a deep understanding of those levels. And so there's a lot off infusion, which is why you will. You kind of think this is my period. But you saw all these professions take off with C titles, right? Chief Data officer, chief analytics officer, chief digital officer and chief technology officer. See, I off course is being there for a long time. And but I think these newer see positions. They're all very, very related, and they all kind of went to the same need which had to do with enterprise transformation, digital transformation, that enterprises chief digital officer, that's another and and people were all trying to essentially feel the elephants and they could only see part of it at the senior levels, and they came up with which have a role you know, seemed most meaningful to them. But really, all of us are trying to do the same job, which is to accelerate digital transformation in the enterprise. Your comment about you kind of see that the seat eels and sea deals now, uh, partnering up much more than in the past, and I think that's in available the major driving force full. That is, in my view, anyway. It's is artificial intelligence as people try to infuse artificial intelligence. Well, then it's very technical field. Still, it's not something that you know you can just hand over to somebody who has the business jobs, but not the deep technical chops to pull that off. And so, in the case off chief data officers that do have the technical jobs, you'll see them also pretty much heading up the I effort in total and you know, as I do for the IBM case, will be building the Data and AI Enablement internal platform for for IBM. But I think in other cases you you've got Chief date officers who are coming in from a different angle. You know, they built Marghera but the CTO now, because they have to. Otherwise you cannot get a I infused into the organization. >>So there were a lot of other priorities, obviously certainly digital transformation. We've been talking about it for years, but still in many organisations, there was a sense of, well, not on my watch, maybe a sense of complacency or maybe just other priorities. Cove. It obviously has changed that now one hundred percent of the companies that we talked to are really putting this digital transformation on the front burner. So how has that changed the role of CDO? Has it just been interpolate an acceleration of that reality, or has it also somewhat altered the swim lanes? >>I think I think it's It's It's Bolt actually, so I have a way of looking at this in my mind, the CDO role. But if you look at it from a business perspective, they're looking for three things. The CEO is looking for three things from the CDO. One is you know this person is going to help with the revenue off the company by enabling the production of new products, new products of resulting in new revenue and so forth. That's kind of one aspect of the monetization. Another aspect is the CEO is going to help with the efficiency within the organization by making data a lot more accessible, as well as enabling insights that reduce into and cycle time for major processes. And so that's another way that they have monitor. And the last one is a risk reduction that they're going to reduce the risk, you know, as regulations. And as you have cybersecurity exposure on incidents that you know just keep keep accelerating as well. You're gonna have to also step in and help with that. So every CDO, the way their senior leadership looks at them is some mix off three. And in some cases, one has given more importance than the other, and so far, but that's how they are essentially looking at it now. I think what digital transformation has done is it's managed to accelerate, accelerate all three off these outcomes because you need to attend to all three as you move forward. But I think that the individual balance that's struck for individuals reveals really depends on their ah, their company, their situation, who their peers are, who is actually leading the transformation and so >>forth, you know, in the value pie. A lot of the early activity around CDO sort of emanated from the quality portions of the organization. It was sort of a compliance waited roll, not necessarily when you started your own journey here. Obviously been focused on monetization how data contributes to that. But But you saw that generally, organizations, even if they didn't have a CDO, they had this sort of back office alliance thing that has totally changed the the in the value equation. It's really much more about insights, as you mentioned. So one of the big changes we've seen in the organization is that data pipeline you mentioned and and cycle time. And I'd like to dig into that a little bit because you and I have talked about this. This is one of the ways that a chief data officer and the related organizations can add the most value reduction in that cycle time. That's really where the business value comes from. So I wonder if we could talk about that a little bit and how that the constituents in the stakeholders in that in that life cycle across that data pipeline have changed. >>That's a very good question. Very insightful questions. So if you look at ah, company like idea, you know, my role in totally within IBM is to enable Ibn itself to become an AI enterprise. So infuse a on into all our major business processes. You know, things like our supply chain lead to cash well, process, you know, our finance processes like accounts receivable and procurement that soulful every major process that you can think off is using Watson mouth. So that's the That's the That's the vision that's essentially what we've implemented. And that's how we are using that now as a showcase for clients and customers. One of the things that be realized is the data and Ai enablement spots off business. You know, the work that I do also has processes. Now that's the pipeline you refer to. You know, we're setting up the data pipeline. We're setting up the machine learning pipeline, deep learning blank like we're always setting up these pipelines, And so now you have the opportunity to actually turn the so called EI ladder on its head because the Islander has to do with a first You collected data, then you curated. You make sure that it's high quality, etcetera, etcetera, fit for EI. And then eventually you get to applying, you know, ai and then infusing it into business processes. And so far, But once you recognize that the very first the earliest creases of work with the data those themselves are essentially processes. You can infuse AI into those processes, and that's what's made the cycle time reduction. And although things that I'm talking about possible because it just makes it much, much easier for somebody to then implement ai within a lot enterprise, I mean, AI requires specialized knowledge. There are pieces of a I like deep learning, but there are, you know, typically a company's gonna have, like a handful of people who even understand what that is, how to apply it. You know how models drift when they need to be refreshed, etcetera, etcetera, and so that's difficult. You can't possibly expect every business process, every business area to have that expertise, and so you've then got to rely on some core group which is going to enable them to do so. But that group can't do it manually because I get otherwise. That doesn't scale again. So then you come down to these pipelines and you've got to actually infuse AI into these data and ai enablement processes so that it becomes much, much easier to scale across another. >>Some of the CEOs, maybe they don't have the reporting structure that you do, or or maybe it's more of a far flung organization. Not that IBM is not far flung, but they may not have the ability to sort of inject AI. Maybe they can advocate for it. Do you see that as a challenge for some CEOs? And how do they so to get through that, what's what's the way in which they should be working with their constituents across the organization to successfully infuse ai? >>Yeah, that's it's. In fact, you get a very good point. I mean, when I joined IBM, one of the first observations I made and I in fact made it to a senior leadership, is that I didn't think that from a business standpoint, people really understood what a I met. So when we talked about a cognitive enterprise on the I enterprise a zaydi em. You know, our clients don't really understand what that meant, which is why it became really important to enable IBM itself to be any I enterprise. You know that. That's my data strategy. Your you kind of alluded to the fact that I have this approach. There are these five steps, while the very first step is to come up with the data strategy that enables a business strategy that the company's on. And in my case, it was, Hey, I'm going to enable the company because it wants to become a cloud and cognitive company. I'm going to enable that. And so we essentially are data strategy became one off making IBM. It's something I enterprise, but the reason for doing that the reason why that was so important was because then we could use it as a showcase for clients and customers. And so But I'm talking with our clients and customers. That's my role. I'm really the only role I'm playing is what I call an experiential selling there. I'm saying, Forget about you know, the fact that we're selling this particular product or that particular product that you got GPU servers. We've got you know what's an open scale or whatever? It doesn't really matter. Why don't you come and see what we've done internally at scale? And then we'll also lay out for you all the different pain points that we have to work through using our products so that you can kind of make the same case when you when you when you apply it internally and same common with regard to the benefit, you know the cycle, time reduction, some of the cycle time reductions that we've seen in my process is itself, you know, like this. Think about metadata business metadata generating that is so difficult. And it's again, something that's critical if you want to scale your data because you know you can't really have a good catalogue of data if you don't have good business, meditate. Eso. Anybody looking at what's in your catalog won't understand what it is. They won't be able to use it etcetera. And so we've essentially automated business metadata generation using AI and the cycle time reduction that was like ninety five percent, you know, haven't actually argue. It's more than that, because in the past, most people would not. For many many data sets, the pragmatic approach would be. Don't even bother with the business matter data. Then it becomes just put somewhere in the are, you know, data architecture somewhere in your data leg or whatever, you have data warehouse, and then it becomes the data swamp because nobody understands it now with regard to our experience applying AI, infusing it across all our major business processes are average cycle time reduction is seventy percent, so just a tremendous amount of gains are there. But to your point, unless you're able to point to some application at scale within the enterprise, you know that's meaningful for the enterprise, Which is kind of what the what the role I play in terms of bringing it forward to our clients and customers. It's harder to argue. I'll make a case or investment into A I would then be enterprise without actually being able to point to those types of use cases that have been scaled where you can demonstrate the value. So that's extremely important part of the equation. To make sure that that happens on a regular basis with our clients and customers, I will say that you know your point is vomited a lot off. Our clients and customers come back and say, Tell me when they're having a conversation. I was having a conversation just last week with major major financial service of all nations, and I got the same point saying, If you're coming out of regulation, how do I convince my leadership about the value of a I and you know, I basically responded. He asked me about the scale use cases You can show that. But perhaps the biggest point that you can make as a CDO after the senior readership is can we afford to be left up? That is the I think the biggest, you know, point that the leadership has to appreciate. Can you afford to be left up? >>I want to come back to this notion of seventy percent on average, the cycle time reduction. That's astounding. And I want to make sure people understand the potential impacts. And, I would say suspected many CEOs, if not most understand sort of system thinking. It's obviously something that you're big on but often times within organisations. You might see them trying to optimize one little portion of the data lifecycle and you know having. Okay, hey, celebrate that success. But unless you can take that systems view and reduce that overall cycle time, that's really where the business value is. And I guess my we're real question around. This is Every organization has some kind of Northstar, many about profit, and you can increase revenue are cut costs, and you can do that with data. It might be saving lives, but ultimately to drive this data culture, you've got to get people thinking about getting insights that help you with that North Star, that mission of the company, but then taking a systems view and that's seventy percent cycle time reduction is just the enormous business value that that drives, I think, sometimes gets lost on people. And these air telephone numbers in the business case aren't >>yes, No, absolutely. It's, you know, there's just a tremendous amount of potential on, and it's it's not an easy, easy thing to do by any means. So we've been always very transparent about the Dave. As you know, we put forward this this blueprint right, the cognitive enterprise blueprint, how you get to it, and I kind of have these four major pillars for the blueprint. There's obviously does this data and you're getting the data ready for the consummation that you want to do but also things like training data sets. How do you kind of run hundreds of thousands of experiments on a regular basis, which kind of review to the other pillar, which is techology? But then the last two pillars are business process, change and the culture organizational culture, you know, managing organizational considerations, that culture. If you don't keep all four in lockstep, the transformation is usually not successful at an end to end level, then it becomes much more what you pointed out, which is you have kind of point solutions and the role, you know, the CEO role doesn't make the kind of strategic impact that otherwise it could do so and this also comes back to some of the only appointee of you to do. If you think about how do you keep those four pillars and lock sync? It means you've gotta have the data leader. You also gotta have the technology, and in some cases they might be the same people. Hey, just for the moment, sake of argument, let's say they're all different people and many, many times. They are so the data leader of the technology of you and the operations leaders because the other ones own the business processes as well as the organizational years. You know, they've got it all worked together to make it an effective conservation. And so the organization structure that you talked about that in some cases my peers may not have that. You know, that's that. That is true. If the if the senior leadership is not thinking overall digital transformation, it's going to be difficult for them to them go out that >>you've also seen that culturally, historically, when it comes to data and analytics, a lot of times that the lines of business you know their their first response is to attack the quality of the data because the data may not support their agenda. So there's this idea of a data culture on, and I want to ask you how self serve fits into that. I mean, to the degree that the business feels as though they actually have some kind of ownership in the data, and it's largely, you know, their responsibility as opposed to a lot of the finger pointing that has historically gone on. Whether it's been decision support or enterprise data, warehousing or even, you know, Data Lakes. They've sort of failed toe live up to that. That promise, particularly from a cultural standpoint, it and so I wonder, How have you guys done in that regard? How did you get there? Many Any other observations you could make in that regard? >>Yeah. So, you know, I think culture is probably the hardest nut to crack all of those four pillars that I back up and you've got You've got to address that, Uh, not, you know, not just stop down, but also bottom up as well. As you know, period. Appear I'll give you some some examples based on our experience, that idea. So the way my organization is set up is there is a obviously a technology on the other. People who are doing all the data engineering were kind of laying out the foundational technical elements or the transformation. You know, the the AI enabled one be planning networks, and so so that are those people. And then there is another senior leader who reports directly to me, and his organization is all around adoptions. He's responsible for essentially taking what's available in the technology and then working with the business areas to move forward and make this make and infuse. A. I do the processes that the business and he is looking. It's done in a bottom upwards, deliberately set up, designed it to be bottom up. So what I mean by that is the team on my side is fully empowered to move forward. Why did they find a like minded team on the other side and go ahead and do it? They don't have to come back for funding they don't have, You know, they just go ahead and do it. They're basically empowered to do that. And that particular set up enabled enabled us in a couple of years to have one hundred thousand internal users on our Central data and AI enabled platform. And when I mean hundred thousand users, I mean users who were using it on a monthly basis. We company, you know, So if you haven't used it in a month, we won't come. So there it's over one hundred thousand, even very rapidly to that. That's kind of the enterprise wide storm. That's kind of the bottom up direction. The top down direction Waas the strategic element that I talked with you about what I said, Hey, be our data strategy is going to be to create, make IBM itself into any I enterprise and then use that as a showcase for plants and customers That kind of and be reiterated back. And I worked the senior leadership on that view all the time talking to customers, the central and our senior leaders. And so that's kind of the air cover to do this, you know, that mix gives you, gives you that possibility. I think from a peer to peer standpoint, but you get to these lot scale and to end processes, and that there, a couple of ways I worked that one way is we've kind of looked at our enterprise data and said, Okay, therefore, major pillars off data that we want to go after data, tomato plants, data about our offerings, data about financial data, that s and then our work full student and then within that there are obviously some pillars, like some sales data that comes in and, you know, been workforce. You could have contractors. Was his employees a center But I think for the moment, about these four major pillars off data. And so let me map that to end to end large business processes within the company. You know, the really large ones, like Enterprise Performance Management, into a or lead to cash generation into and risk insides across our full supply chain and to and things like that. And we've kind of tied these four major data pillars to those major into and processes Well, well, yes, that there's a mechanism they're obviously in terms off facilitating, and to some extent one might argue, even forcing some interaction between teams that are the way they talk. But it also brings me and my peers much closer together when you set it up that way. And that means, you know, people from the HR side people from the operation side, the data side technology side, all coming together to really move things forward. So all three tracks being hit very, very hard to move the culture fall. >>Am I also correct that you have, uh, chief data officers that reporting to you whether it's a matrix or direct within the division's? Is that right? >>Yeah, so? So I mean, you know, for in terms off our structure, as you know, way our global company, we're also far flung company. We have many different products in business units and so forth. And so, uh, one of the things that I realized early on waas we are going to need data officers, each of those business units and the business units. There's obviously the enterprise objective. And, you know, you could think of the enterprise objectives in terms of some examples based on what I said in the past, which is so enterprise objective would be We've gotta have a data foundation by essentially making data along these four pillars. I talked about clients offerings, etcetera, you know, very accessible self service. You have mentioned south, so thank you. This is where the South seven speaks. Comes it right. So you can you can get at that data quickly and appropriately, right? You want to make sure that the access control, all that stuff is designed out and you're able to change your policies and you'd swap manual. But, you know, those things got implemented very rapidly and quickly. And so you've got you've got that piece off off the off the puzzle due to go after. And then I think the other aspect off off. This is, though, when you recognize that every business unit also has its own objectives and they are looking at some of those things somewhat differently. So I'll give you an example. We've got data any our product units. Now, those CEOs right there, concern is going to be a lot more around the products themselves And how were monetizing those box and so they're not per se concerned with, You know, how you reduce the enter and cycle time off IBM in total supply chain so that this is my point. So they but they're gonna have substantial considerations and objectives that they want to accomplish. And so I recognize that early on, and we came up with this notion off a data officer council and I helped staff the council s. So this is why that's the Matrix to reporting that we talked about. But I selected some of the key Blair's that we have in those units, and I also made sure they were funded by the unit. So they report into the units because their paycheck is actually determined. Pilot unit and which makes them than aligned with the objectives off the unit, but also obviously part of my central approach so that I can disseminate it out to the organization. It comes in very, very handy when you are trying to do things across the company as well. So when we you know GDP our way, we have to get the company ready for Judy PR, I would say that this mechanism became a key key aspect of what enabled us to move forward and do it rapidly. Trouble them >>be because you had the structure that perhaps the lines of business weren't. Maybe is concerned about GDP are, but you had to be concerned with it overall. And this allowed you to sort of hiding their importance, >>right? Because think of in the case of Jeannie PR, they have to be a company wide policy and implementation, right? And if he did not have that structure already in place, it would have made it that much harder. Do you get that uniformity and consistency across the company, right, You know, So you will have to in the weapon that structure, but we already have it because way said Hey, this is around for data. We're gonna have these types of considerations that they are. And so we have this thing regular. You know, this man network that meat meets regularly every month, actually, and you know, when things like GDP are much more frequently than that, >>right? So that makes sense. We're out of time. But I wonder if we could just close if you could address the M I t CDO audience that probably this is the largest audience, Believe or not, now that it's that's virtual definitely expanded the audience, but it's still a very elite group. And the reason why I was so pleased that you agreed to do this is because you've got one of the more complex organizations out there and you've succeeded. And, ah, a lot of the hard, hard work. So what? What message would you leave the M I t CDO audience Interpol? >>So I would say that you know, it's it's this particular professional. Receiving a profession is, uh, if I have to pick one trait of let me pick two traits, I think what is your A change agent? So you have to be really comfortable with change things are going to change, the organization is going to look to you to make those changes. And so that's what aspect off your job, you know, may or may not be part of me immediately. But the those particular set of skills and characteristics and something that you know, one has to, uh one has to develop or time, And I think the other thing I would say is it's a continuous looming jaw. So you continue sexism and things keep changing around you and changing rapidly. And, you know, if you just even think just in terms off the subject areas, I mean this Syria today you've got to understand technology. Obviously, you've gotta understand data you've got to understand in a I and data science. You've got to understand cybersecurity. You've gotta understand the regulatory framework, and you've got to keep all that in mind, and you've got to distill it down to certain trends. That's that's happening, right? I mean, so this is an example of that is that there's a trend towards more regulation around privacy and also in terms off individual ownership of data, which is very different from what's before the that's kind of weather. Bucket's going and so you've got to be on top off all those things. And so the you know, the characteristic of being a continual learner, I think is a is a key aspect off this job. One other thing I would add. And this is All Star Coleman nineteen, you know, prik over nineteen in terms of those four pillars that we talked about, you know, which had to do with the data technology, business process and organization and culture. From a CDO perspective, the data and technology will obviously from consent, I would say most covert nineteen most the civil unrest. And so far, you know, the other two aspects are going to be critical as we move forward. And so the people aspect of the job has never bean, you know, more important down it's today, right? That's something that I find myself regularly doing the stalking at all levels of the organization, one on a one, which is something that we never really did before. But now we find time to do it so obviously is doable. I don't think it's just it's a change that's here to stay, and it ships >>well to your to your point about change if you were in your comfort zone before twenty twenty two things years certainly taking you out of it into Parliament. All right, thanks so much for coming back in. The Cuban addressing the M I t CDO audience really appreciate it. >>Thank you for having me. That my pleasant >>You're very welcome. And thank you for watching everybody. This is Dave a lot. They will be right back after this short >>break. You're watching the queue.

>> Narrator: From theCUBE studios in Palo Alto in Boston, connecting with thought leaders all around the world, this is a cube conversation. >> Everyone welcome to this cube conversation here in the Palo Alto cube studios. I'm John Furrier your host of theCUBE, with a great guest here, Shanthi Vigneshwaran, who is with the Office of Strategic programs in the Center for Drug Evaluation and Research within the US Food and Drug Administration, FDA, is the Informatica Intelligent Disrupter of the Year award. Congratulations, Shanthi welcome to this cube conversation. Thanks for joining me. >> Thank you for having me. >> Congratulations on being the Informatica Intelligent Disrupter of the year award. Tell us more about the organization. I see FDA everyone's probably concerned these days making sure things going faster and faster, more complex, more things are happening. Tell us about your organization and what you work on. >> FDA is huge, our organization is Center for Drug Evaluation research. And its core mission is to promote public health by ensuring the availability of safety and effective drugs. For example any drugs you go and buy it in the pharmacy today, Our administration helps in trying to approve them and make sure it's so in term of quality and integrity of the marketed products in the industry. My office is specifically Office of strategic programs whose mission is to transform the drug regulatory operations with the customer focus through analytics and informatics. They work towards the advancement for the CDERs public health mission. >> What are some of the objectives that you guys have? What are some things you guys have as your core top objectives of the CDER, the drug research group? >> The core objectives is we wanted to make sure that we are promoting a safe use of the marketed drugs. We want to make sure there's the availability of the drugs that are going to the patients are effective. And also the quality of the drugs that are being marketed are able to protect public health. >> What are some of the challenges that you guys have to take in managing the pharmaceutical safety, because I can only imagine certainly now that supply chains, tracing, monitoring, drug efficacy, safety, all these things are happening. What are some of the challenges in doing all this? >> In our office there are challenges in three different areas. One is the drug regulation challenges because as drugs are being more advanced and as there are more increasingly complex products, and there are challenging in the development area of the drugs, we wanted to make sure here we have a regulation that supports any advancement in science and technology. The other thing is also Congress is actually given new authorities and roles for the FDA to act. For example the Drug Quality and Security Act, which means any drug that's they want to track and trace all the drugs that goes to the public is they know who are the distributors, who are the manufacturers. Then you have the 21st Century Cures Act, and also the CARES Act package which was recently assigned, which also has a lot of the OTC drug regulatory modernization. Then there's also the area of globalization because just as disease don't have any borders, Product safety and quality are no longer on one country. It's basically a lot of the drugs that are being manufactured are overseas and as a result we wanted to make sure there are 300 US ports. And we want to make sure the FDA regulated shipments are coming through correctly to proper venues and everything is done correctly. Those are some the challenges we have to deal with. >> So much going on a lot of moving purchase as people say, there's always drug shortages, always demand, knowing that and tracking it. I can only imagine the world you're living in because you got to be innovative, got to be fast, got to be cutting edge, got to get the quality right. Data is super critical. And can you share take a minute to explain some of the data challenges you have to address and how you did that. Because I mean I could almost just my mind's blown just thinking about how you live it every day. Can you just share some of those challenges that you had to address and how did you do? >> Some of the key challenges we actually see is we have roughly 170,000 regulatory submissions per year. There are roughly 88,000 firm registration and product listing that comes to us, and then there are more than 2 million adverse event reports. So with all these data submissions and organization as such as us we need it, we have multiple systems where this data is acquired and each has its own criteria for validating the data. Adding to it are internal and external stakeholders also want certain rules and the way the data is being identified. So we wanted to make sure there is a robust MDM framework to make sure to cleanse and enrich and standardize the data. So that it basically make sure the trust and the availability and the consistent of the data, is being supplied to published to the CDER regulatory data users. >> You guys are dealing with- >> Otherwise like it's almost to give them a 360 degree view of the drug development lifecycle. Through each of the different phases, both pre market which is before the drug hits the market, and then after it hits the market. We still want to make sure the data we receive still supports a regulatory review and decision making process. >> Yeah, and you got to deliver a consumer product to get people at the right time. All these things have to happen, and you can see it clearly the impacts everyday life. I got to ask you that the database question 'cause the database geek inside of me is just going okay. I can only imagine the silos and the different systems and the codes, because data silos is big document. We've been reporting on this on theCUBE for a long time around, making data available automation. All these things have to happen if there's data availability. Can you just take one more minute talk about some of the challenges there because you got to break down the silos at the same time you really can't replace them. >> That's true. What we did was we did leave it more of us I mean, step back like seven years ago, when we did the data management. We had like a lot of silo systems as well. And we wanted to look at we wanted to establish a, we knew we wanted to establish a master data management. So we took a little bit more of a strategic vision. And so what we ended up saying is identifying what are the key areas of the domain that will give us some kind of a relationship. What are the key areas that will give us the 360 degree lifecycle? So that's what we did. We identified the domains. And then we took a step back and said and then we looked at what is the first domain we wanted to tackle. Because we know what are these domains are going to be. And then we were like, okay, let's take a step back and say which is the domain we do it first that will give us the most return on investment, which will make people actually look at it and say, hey, this makes sense. This data is good. So that's what we ended up looking at. We looked at it as at both ends. One is from a end user perspective. Which is the one they get the benefit out of and also from a data silo perspective which is the one data domains that are common, where there's duplication that we can consolidate. >> So that's good. You did the work up front. That's critical knowing what you want to do and get out of it. What were some of the benefits you guys got out of it. From an IT standpoint, how does that translate to the business benefits? And what was achieved? >> I think the benefits we got from the IT standpoint was a lot of the deduplication was not theirs. Which basically means like a lot of the legacy systems and all of the manual data quality work we had to do we automated it. We had bots, we also had other automation process that we actually put into work with Informatica, that actually helped us to make sure it's the cost of it actually went for us considerably. For example it used to take us three days to process submissions. Now it takes us less than 24 hours to do it, for the users to see the data. So it was a little bit more, we saw the, we wanted to look at what are the low hanging fruits where it's labor intensive and how can we improve it. That's how we acted there. >> What are some of the things that you're experiencing? I mean, like, we look back at what it was before, where it is now? Is it more agility, you more responsive to the changes? Was it an aspirin? Was it a complete transformation? Was some pain reduced? Can you share just some color commentary on kind of before the way it was before and then what you're experiencing now? >> So for us, I think before, we didn't know where the for us, I mean, I wouldn't say we didn't know it, when we have the data, we looked at product and it was just product. We looked at manufactured they were all in separate silos. But when we did the MDM domain, we were able to look at the relationship. And it was very interesting to see the relationship because we now are able to say is. for example, if there is a drug shortage during due to hurricane, with the data we have, we can narrow down and say, Hey, this area is going to be affected which means these are the manufacturing facilities in that area , that are going to be not be able to function or impacted by it. We can get to the place where the hurricane tracks we use the National Weather Service data, but it helps us to narrow down some of the challenges and we can able to predict where the next risk is going to be. >> And then before the old model, there was either a blind spot or you were ad hoc, probably right? Probably didn't have that with you. >> Yeah, before you were either blind or you're doing in a more of a reactionary not proactively. Now we are able to do a little bit more proactively. And even with I mean drug shortages and drug supply chain are the biggest benefit we saw with this model. Because, for us the drug supply chain means linking the pre and post market phases that lets us know if there's a trigger and the adverse events, we actually can go back to the pre market side and see where the traceability is who's at that truck. What are all the different things that was going on. >> This is one of the common threats I see in innovation where people look at the business model and data and look at it as a competitive advantage, in this case proactivity on using data to make decisions before things happen, less reactivity. So that increases time. I mean, that would probably you're saying, and you get there faster, if you can see it, understand it, and impact the workflows involved. This is a major part of the data innovation that's going on and you starting to see new kinds of data whereas has come out. So again, starting to see a real new changeover to scaling up this kind of concept almost foundationally. What's your thoughts just as someone who's a practitioner in the industry as you start to get this kind of feelings and seeing the benefits? What's next, what do you see happening because you haven't success. How do you scale it? What how do you guys look at that? >> I think our next is we have the domains and we actually have the practices that we work. We look at it as it's basically data always just changes. So we look at is like what are some of the ways that we can improve the data? How can we take it to the next level. Because now they talk about power. They are also warehouse data lakes. So we want to see is how can we take these domains and get that relationship or get that linkages when there is a bigger set of data that's available for us. What can we use that and it actually we think there are other use cases we wanted to explore and see what is the benefit that we can get a little bit more on the predictability to do like post market surveillance or like to look at like safety signals and other things to see what are the quick things that we can use for the business operations. >> It's really a lot more fun. You're in there using the data. You're seeing the benefits and real. This is what clouds all about the data clouds here. It's scaling. Super fun to talk about and excited. When you see the impacts in real time, not waiting for later. So congratulations. You guys have been selected and you receive recognition from Informatica as the 2020, Intelligent Disrupter of the year. congratulations. What does that mean for your organization? >> I think we were super excited about it. But one thing I can say is when we embarked on this work, like seven years ago, or so, problem was like we were trying to identify and develop new scientific methods to improve the quality of our drugs to get that 360 degree view of the drug development lifecycle. The program today enables FDA CDER to capture all the granular details of data we need for the regulatory data. It helps us to support the informed decisions that we have to make in real time sometimes or and also to make sure when there's an emergency, we are able to respond with a quick look at the data to say like, hey this is what we need to do. It also helps the teams. It recognizes all the hard work. And the hours we put into establishing the program and it helped to build the awareness within FDA and also with the industry of our political master data management is. >> It's a great reward to see the fruits of the labor and good decision making I'm sure it was a lot of hard work. For folks out there watching, who are also kind of grinding away in some cases, some cases moving faster. You guys are epitome of a supply chain that's super critical. And speed is critical. Quality is critical. A lot of days critical. A lot of businesses are starting to feel this as part of an integrated data strategy. And I'm a big proponent. I think you guys have have a great example of this. What advice would you have for other practitioners because you got data scientists, but yet data engineers now who are trying to architect and create scale, and programmability, and automation, and you got the scientists in the the front lines coming together and they all feed into applications. So it's kind of a new things go on. Your advice to folks out there, on how to do this, how to do it right, the learnings, share. >> I think the key thing I, at least for my learning experience was, it's not within one year you're going to accomplish it, It's kind of we have to be very patient. And it's a long road. If you make mistakes, you will have to go back and reassess. Even with us, with all the work we did, we almost went back a couple of the domains because we thought like, hey, there are additional use cases how this can be helpful. There are additional, for example, we went with the supply chain, but then now we go back and look at it and say like, hy, there may be other things that we can use with the supply chain not just with this data, can we expand it? How can we look at the study data or other information so that's what we try to do. It's not like you're done with MDM and that is it. Your domain is complete. It's almost like you look at it and it creates a web and you need to look at each domain and you want to come back to it and see how it is you have to go. But the starting point is you need to establish what are your key domains. That will actually drive your vision for the next four or five years. You can't just do bottom up, it's more of like a top down approach. >> That's great. That's great the insight. And again, it's never done. I mean, it's data is coming. It's not going away. It's going to be integrated. It's going to be shared. You got to scale it up. A lot of hard work. >> Yeah. >> Shanthi thank you so much for the insight. Congratulations on your receiving the Disrupter of the Year Award winner for Informatica. congratulations. Intelligence >> Yeah, thank you very much for having me. Thank you. >> Thank you for sharing, Shanthi Vigneshswaran is here, Office of Strategic programs at the Center for Drug Evaluation and Research with the US FDA. Thanks for joining us, I'm John Furrier for theCUBE. Thanks for watching. (soft music)

>>Bly from Boston, Massachusetts. It's the cube covering ifs world conference 2019 brought to you by ifs. >>Okay. We're back in Boston, Massachusetts ifs world day one. You walked into cube Dave Vellante with Paul Gillen boss Devoss is here. He's the director of ISF I F S labs and Bob Dico who's the vice president of AI and RPA at ifs jets. Welcome. Good to see you again. Good morning bossy. We're on last year. I'm talking about innovation ifs labs. First of all, tell us about ifs labs and what you've been up to in the last 12 months. Well, I have has Lapsis a functioning as the new technology incubator. Fire Fest writes over continuously looking at opportunities to bring innovation into, into product and help our customers take advantage of all the new things out there to yeah. To, to create better businesses. And one of the things I talked about last year is how we want to be close to our customers. And I think, uh, that's what we have been doing over the pasta pasta year. Really be close to our customers. So Bob, you got, you got the cool title, AI, RPA, all the hot cool topics. So help us understand what role you guys play as ifs. As a software developer, are you building AI? Are you building RPA? Are you integrating it? Yes, yes. Get your paint. >>I mean, our value to our customers comes from wrapping up the technology, the AI, the RPA, the IOT into product in a way that it's going to help their business. So it's going to be easy to use. They're not going to need to be a technical specialist to take advantage of it. It's going to be embedded in the product in a way they can take advantage of very easily that that's the key for us as a software developer. We don't want to offer them a platform that they can just go and do their own thing. We want to sort of control it, make it easier for them. >>So I presume it's not a coincidence that you guys are on together. So this stuff starts in the labs and then your job is to commercialize it. Right? So, so take machine intelligence for example. I mean it can be so many things to so many different people. Take us back to sort of, you know, the starting point, you know, within reason of your work on machine intelligence, what you were thinking at the time, maybe some of the experiments that you did and how it ends up in the product. Oh, very good question. Right? So I think we start at a, Oh, well first of all, I think ifs has been using a machine learning at, at various points in our products for many, many years of Trumbull in our dynamic scheduling engine. We have been using neural networks to optimize fuel serve scheduling for quite some many years. >>But I think, um, if we go back like two years, what we sold is that, uh, there, there's a real potential, um, in our products that if you will take machine learning algorithms inside of the product to actually, um, help ultimately certain decisions in there, um, that could potentially help our business quite a bit. And the role of ifs lapse back in the day as that we just started experimenting, right? So we went out to different customers. Uh, we started engaging with them to see, okay, what kind of data do we have, what kind of use cases are there? And basically based on that, we sort of developed a vision around AI and a division back in the day was based on on three important aspects, human machine interaction optimization and automation. And that kind of really lended well with our customer use case. We talked quite a bit about that or the previous world conference. >>So at that point we basically decided, okay, you know what, we need to make serious work of this, uh, experimenting as boots. But at a certain point you have to conclude that the experiments were successful, which we did. And at that point we decided to look at, okay, how can we make this into a product and how to normally go system. We started engaging with them more intensively and starting to hand over in this guys, we decided the most also a good moment to bring somebody on board that actually has even more experience and knowledge in AI and what we already had as hive as labs. But that could basically take over the Baton. And say, okay, now I am going to run with it and actually start commercializing and productizing that still in collaboration with IVIS laps. But yeah, taking that next step in the road and then then Bob came onboard. >>Christian Pedersen made the point during the keynote this morning that you have to avoid the, the appeal of technology for technology's sake. You have to have it. I start with the business use case. You are both very technology, very deep into the technology. How do you keep disciplined to avoid letting the technology lead your, your activities? >>Well, both. Yeah. So, so I think a good example is what we see this world's going fronts as well. It is staying closer to customer and, and, and accepting and realizing that there is no, um, there's no use in just creating technology for sake of technology as you say yourself. So what we did here for example, is that we showcase collaboration projects with, with customers. So, for example, we show showcase a woman chair pack, which um, as a, as a manufacturing of spouting pouches down here in Massachusetts actually, uh, and they wanted to invest in robotics to get our widows. So what we basically did is actually wind into their factory literally on the factory floor and start innovating there. So instead of just thinking about, okay, how do robotics and AI for subrogations or one of our older products work together, we set, let's experiment on the shop floor off a customer instead of inside of the ivory towers. Sometimes our competitors to them, they'll start to answer your question. >>Sure. I can pick up a little, a little feasible. Yeah. Well, so in, I think the really important thing, and again, Christian touched on it this morning is not the individual technologies themselves. It's how they work together. Um, we see a lot of the underlying technologies becoming more commoditized. That's not where companies are really starting to differentiate algorithms after a while become algorithms. There's a good way of doing things. They might evolve slightly over time, but effectively you can open source a lot of these things. You can take advantage, the value comes from that next layer up. How you take those technologies together, how you can create end to end processes. So if we take something like predictive, we would have an asset. We would have sensors on that asset that would be providing real time data, uh, to an IOT system. We can combine that with historical maintenance data stored within a classic ERP system. >>We can pull that together, use machine learning on it to make a prediction for when that machine is gonna break down. And based on that prediction, we can raise a work order and if we do that over enough assets, we can then optimize our technicians. So instead of having to wait for it to break down, we can know in advance, we can plan for people to be in the right the right place. It's that end to end process where the value is. We have to bring that together in a way that we can offer it to our customers. There's certainly, you know, a lot of talk in the press about machines replacing humans. Machine of all machines have always replaced humans. But for the first time in history, it's with cognitive functions. Now it's, people get freaked out. A little bit about that. I'm hearing a theme of, of augmentation, you know, at this event. >>But I wonder if you could share your thoughts with regard to things like AI automation, robotic process automation. How are customers, you know, adopting them? Is there sort of concern up front? I mean we've talked to a number of RPA customers that, you know, initially maybe are hesitant but then say, wow, I'm automating all those tasks that I hate and sort of lean in. But at the same time, you know, it's clear that this could have an effect on people's jobs and lives. What are your thoughts? Sure. Do you want to kick off on them? Yeah, I'll know. Yeah, absolutely. That's fine. So I think in terms of the, the automation, the low level tasks, as you say, that can free up people to focus on higher value activities. Something like RPA, those bots, they can work 24, seven, they can do it error free. >>Um, it's often doing work that people don't enjoy anyway. So that tends to actually raise morale, raise productivity, and allow you to do tasks faster. And the augmentation, I think is where it gets very interesting because you need to, you often don't want to automate all your decisions. You want people to have the final say, but you want to provide them more information, better, more pertinent ways of making that decision. And so it's very important. If you can do that, then you've got to build the trust with them. If you're going to give them an AI decision that's just out of a black box and just say, there's a 70% chance of this happening. And what I founded in my career is that people don't tend to believe that or they start questioning it and that's where you have difficulty. So this is where explainable AI comes in. >>I do to be able to state clearly why that prediction is being made, what are the key drivers going into it? Or if that's not possible, at least giving them the confidence to see, well, you're not sure about this prediction. You can play around with it. You can see I'm right, but I'm going to make you more comfortable and then hopefully you're going to understand and, and sort of move with it. And then it starts sort of finding its way more naturally into the workplace. So that's, I think the key to building up successful open sexually. What it is is it's sort of giving a human the, the, the parameters the and saying, okay, now you can make the call as to whether or not you want to place that bet or make a different decision or hold off and get more data. Is that right? >>Uh, yeah. I think a lot of it is about setting the threshold and the parameters with within which you want to operate. Often if a model is very confident, either you know, a yes or a no, you probably be quite happy to let it automate. Take that three, it's the borderline decision where it gets interesting. You probably would still want someone to look over it, but you want them to do it consistently. You want them to do it using all the information to hand and say that's what you do. You're presented to them. And to add to that, um, I think we also should not forget they said a lot of our customers, a lot of companies are, are actually struggling finding quality stuff, right? I mean aging of the workforce riots, we're, we're old. I'm retiring eventually. Right? So aging of the workforce is a potential issue. >>Funding, lack of quality. Stop. So if I go back to the chair pack example I was just talking about, um, and, and, and some of the benefits they get out of that robotics projects, um, um, is of course they're saving money right there. They're saving about one point $5 million a year on money on that project, but their most important benefits for them, it's actually the fact that I have been able to move the people from the work floor doing that into higher scope positions, effectively countering the labor shortage today. They were limited in their operations, but in fact, I had two few quality stuff. And by putting the robots in, they were able to reposition those people and that's for them the most important benefits. So I think there's always a little bit of a balance. Um, but I also think we eventually need robots. >>We need ultimation to also keep up with the work that needs to be done. Maybe you can speak to Bobby, you can speak to software robots. We've, Pete with people think of robots, they tend to think of machines, but in fact software robots are, where are the a, the real growth is right now, the greatest growth is right now. How pervasive will software robots be in the workplace do you think in the three to five years? >> I think the software robots as they are now within the RPA space, um, they fulfill a sort of part of the Avril automation picture, but they're never going to be the whole thing. I see them very much as bringing different systems together, moving data between systems, allowing them to interact more effectively. But, um, within systems themselves, uh, you know, the bots can only really scratched the surface. >>They're interacting with software in the same way a human would on the whole by clicking buttons going through, et cetera, beneath the surface. Uh, you know, for example, within the ifs products we have got data understanding how people interact with our products. We can use machine learning on that data to learn, to make recommendations to do things that our software but wouldn't be able to see. So I think it's a combination. There's software bots, they're kind of on the outside looking in, but they're very good at bringing things together. And then insight you've got that sort of deeper automation to take real advantage of the individual pieces of software. >> This may be a little out there, but you guys >>are, you guys are deep into, into the next generation lot to talk right now about quantum and how we could see workable quantum computers within the next two to two to three years. How, what do you think the, the outlook is there? How is that going to shake things up? So >>let me answer this. We were actually a having an active project and I for slabs currently could looking at quantum computing, right? Um, there's a lot of promise in it. Uh, there's also a lot of unfilled, unfulfilled problems in that, right? But if you look at the, the potential, I think where it really starts playing, um, into, uh, into benefits is if the larger the, the, the optimization problems, the larger the algorithms are that we have to run, the more benefits it actually starts bringing us. So if you're asking me for an for an outlook, I say there is potential definitely, especially in optimization problems. Right. Um, but I also think that the realistic outlook is quite far out. Uh, yes, we're all experimenting it and I think it's our responsibility as ifs or ciphers laps to also look on what it could potentially mean for applications as we FSI Fs. >>But my personal opinion is the odd Lucas. Yeah. So what comes five to 10 years out? What comes first? Quantum computing or fully autonomous driverless vehicles? Oh, that's a tricky question. I mean, I would say in terms of the practical commercial application, it's going to be the latter in that much so that's quite a ways off. Yeah, I think so. Of course. Question back on on RPA, what are you guys exactly doing on RPA? Are you developing your own robotic process automation software or are you integrating, doing both say within the products? We, you know, if we think of RPA as, as this means of interacting with the graphical user interface in a way that a human would within the product. Um, we, we're thinking more in terms of automating processes using the machine learning as I mentioned, to learn from experience, et cetera. Uh, in a way that will take advantage of things like our API eighth, an API APIs that are discussed on main stage today. >>RPA is very much our way of interacting with other systems, allowing other systems when trapped with ifs, allowing us to, to send messages out. So we need to make it as easy as possible for those bots to call us. Uh, you know, that can be by making our screens nice and accessible and easy to use. But I think the way that RPA is going, a lot of the major vendors are becoming orchestrators really. They're creating these, these studios where you can drag and drop different components into to do ACR, provide cognitive services and you know, elements that you could drag and drop in would be to say, ah, take data from a file and load it into ifs and put it in a purchase order. And you can just drag that in and then it doesn't really matter how it connects to YFS. It can do that via the API. And I think it probably will say it's creating the ability to talk to ifs. That's the most important thing for us. So you're making your products a RPA ready, friendly >>you, it sounds like you're using it for your own purposes, but you're not an RPA vendor per se. You know what I'm saying? Okay. Here's how you do an automation. You're gonna integrate that with other RPA leadership product. I think we would really take a more firm partner approach to it. Right? So if a customer, I mean, there's different ways of integrating systems to get our RPA as a Google on there. There's other ways as well, right? That if a customer actually, um, wants to integrate the systems together using RPA, very good choice, we make sure that our products are as ready as much for that as possible. Of course we will look at the partner ecosystem to make sure that we have sufficient and the right partners in there that a customer has as a choice in what we recommends. But basically we say where we want to be agnostic to what kind of RPA feminists sits in there that was standing there was obviously a lot of geopolitical stuff going on with tariffs and the like. >>So not withstanding that, do you feel as though things like automation, RPA, AI will swing the pendulum back to onshore manufacturing, whether it's Europe or, or U S or is the costs still so dramatically advantageous to, you know, manufacture in China? Well, that pendulum swing in your opinion as a result of automation? Um, I have a good, good question. Um, I'm not sure it's will completely swing, but it will definitely be influenced. Right. One of the examples I've seen in the RPA space ride wire a company before we would actually have an outsourcing project in India where people would just type over D uh, DDD, the purchase orders right now. Now in RPA bolts scans. I didn't, so they don't need the Indian North shore anymore. But it's always a balance between, you know, what's the benefit of what's the cost of developing technology and that's, and it's, and, and it's almost like a macro economical sort of discussion. >>One of the discussions I had with my colleagues in Sri Lanka, um, and, and maybe completely off topic example, we were talking about carwash, right? So us in the, in the Western world we have car wash where you drive your car through, right? They don't have them in Sri Lankan. All the car washes are by hands. But the difference is because labor is cheaper there that it's actually cheaper to have people washing your car while we'd also in the us for example, that's more expensive than actually having a machine doing it. Right. So it is a, it's a macro economical sort of question that is quite interesting to see how that develops over the next couple of years. All right, Jess. Well thanks very much for coming on the cube. Great discussion. Really appreciate it. Thank you very much. You're welcome. All right. I'll keep it right there, but he gave a latte. Paul Gillen moved back. Ifs world from Boston. You watch in the queue.

>> From Cambridge, Massachusetts it's theCUBE, covering MIT Chief Data Officer and Information Quality Symposium 2019. Brought to you by, SiliconANGLE Media. >> Welcome back to Cambridge, Massachusetts, everybody. You're watching theCUBE, the leader in live tech coverage. I'm Dave Vellante with my co-host, Paul Gillan. Chris Lynch, good friend is here CEO, newly minted CEO and AtScale and legend. Good to see you. >> In my own mind. >> In mine too. >> It's great to be here. >> It's awesome, thank you for taking time. I know how busy you are, you're running around like crazy your next big thing. I was excited to hear that you got back into it. I predicted it a while ago you were a very successful venture capitalists but at heart, you're startup guy, aren't ya? >> Yeah 100%, 100%. I couldn't be more thrilled, I feel invigorated. I think I've told you many times, when you've interviewed me and asked me about the transition from being an entrepreneur to being a VC and since it's a PG show, I've got a different analog than the one I usually give you. I used to be a movie star and now I'm an executive producer of movies. Now am back to being a movie star, hopefully. >> yeah well, so you told me when you first became a VC you said, I look for startups that have a 10X impact either 10X value, 10X cost reduction. What was it that attracted you to AtScale? What's the 10X? >> AtScale, addresses $150 billion market problem which is basically bringing traditional BI to the cloud. >> That's the other thing you told me, big markets. >> Yeah, so that's the first thing massive market opportunity. The second is, the innovation component and where the 10X comes we're uniquely qualified to virtualize data into the pipeline and out. So I like to say that we're the bridge between BI and AI and back. We make every BI user, a citizen data scientist and that's a game changer. And that's sort of the new futuristic component of what we do. So one part is steeped in, that $150 billion BI marketplace in a traditional analytics platforms and then the second piece is into you delivering the data, into these BI excuse me, these AI machine learning platforms. >> Do you see that ultimately getting integrated into some kind of larger, data pipeline framework. I mean, maybe it lives in the cloud or maybe on prem, how do you see that evolving over time? >> So I believe that, with AtScale as one single pane of glass, we basically are providing an API, to the data and to the user, one single API. The reason that today we haven't seen the delivery of the promise of big data is because we don't have big data. Fortunate 2000 companies don't have big data. They have lots of data but to me big data means you can have one logical view of that data and get the best data pumped into these models in these tools, and today that's not the case. They're constricted by location they're constricted by vendor they're constricted by whether it's in the cloud or on prem. We eliminate those restrictions. >> The single API, I think is important actually. Because when you look at some of these guys what they're doing with their data pipeline they might have 10 or 15 unique API's that they're trying to manage. So there's a simplification aspect to, I suppose. >> One of the knocks on traditional BI has always been the need for extract databases and all the ETL that goes that's involved in that. Do you guys avoid that stage? You go to the production data directly or what's the-- >> It's a great question. The way I put it is, we bring Moses to the mountain the mountain being the data, Moses being the user. Traditionally, what people have been trying to do is bring the mountain to Moses, doesn't scale. At AtScale, we provide an abstraction a logical distraction between the data and the BI user. >> You don't touch, you don't move the data. >> We don't move the data. Which is what's unique and that's what's delivering I think, way more than a 10X delivery in value. >> Because you leave the data in place you bring that value to wherever the data is. Which is the original concept of Hadoop, by the way. That was what was profound about Hadoop everybody craps on it now, but that was the game changer and if you could take advantage of that that's how you tap your 10X. >> To the difference is, we're not, to your point we're not moving the data. Hadoop, in my humble opinion why it plateaued is because to get the value, you had to ask the user to bring and put data in yet another platform. And the reason that we're not delivering on big data as an industry, I believe is because we've too many data sources, too many platforms too many consumers of data and too many producers. As we build all these islands of data, with no connectivity. The idea is, we'll create this big data lake and we're going to physically put everything in there. Guess what? Someday turned out to be never. Because people aren't going to deal with the business disruption. We move thousands of users from a platform like Teradata to a platform like Snowflake or Google BigQuery, we don't care. We're a multi-cloud and we're a hybrid cloud. But we do it without any disruption. You're using Excel, you just continue and use it. You just see the results are faster. You use Tableau, same difference. >> So we had all the vertical rock stars in here. So we had Colin in yesterday, we had Stonebraker around earlier. Andy Palmer just came on and Chris here with the CEO who ultimately sold the company to HP. That really didn't do anything with it and then spun it off and now it's back. Aaron was, he had a spring in his step yesterday. So when you think about, Vertica. The technology behind Vertica go back 10 years and where we come now give us a little journey of, your data journey. >> So I think it plays into the, the original assertion is that, vertical is a best-in-class platform for analytics but it was yet another platform. The analog I give now, is now we have Snowflake and six months, 12 months from now we're going to have another one. And that creates a set of problems if you have to live in the physical world. Because you've all these islands of data and I believe, it's about the data not about the models, it's about the data. You can't get optimal results if you don't have an optimal access to the pertinent data. I believe that having that Universal API is going to make the next platform that more valuable. You're not going to be making the trade-off is, okay we have this platform that has some neat capability but the trade-off is from an enterprise architecture perspective we're never going to be able to connect all this stuff. That's how all of these things proliferated. My view is, in a world where you have that single pane of glass, that abstraction layer between the user and the data. Then innovation can be spawned quicker and you can use these tools effectively 'cause you're not compromising being able to get a logical view of the data and get access to it as a user. >> What's your issue with Snowflake you mentioned them, Mugli's company-- >> No issue, they're a great partner of ours. We eliminate the friction between the user going from an on-prem solution to the cloud. >> Slootman just took over there. So you know where that's going. >> Yep (laughing) >> Frank's got the magic touch. Okay good, you say they're a partner yours how are you guys partnering? >> They refer us into customers that, if you want to buy Snowflake now the next issue is, how do i migrate? You don't. You put our virtualization layer in and then we allow you access to Snowflake in a non-disruptive way, versus having to move data into their system or into a particular cloud which creates sales friction. >> Moving data is just, you want to avoid it at all cost. >> I do want to ask you because I met with your predecessors, Dave Mariani last year and I know he was kind of a reluctant CEO he didn't really want to be CEO but wanted to be CTO, which is what he is now. How did that come about, that they found you that you connected with them and decided this was the right opportunity. >> That's a great question. I actually looked at the company at the seed stage when I was in venture, but I had this thing as you know that, I wanted to move companies to Boston and they're about my vintage age-wise and he's married with four kids so that wasn't in the cards. I said look, it doesn't make sense for me to seed this company 'cause I can't give you the time you're out in California everything I'm instrumenting is around Boston. We parted friends. And I was skeptical whether he could build this 'cause people have been talking about building a heterogeneous universal semantic layer, for years and it's never come to fruition. And then he read in Fortune or Forbes that I was leaving Accomplice and that I was looking for one more company to operate. He reached out and he told me what they were doing that hey, we really built it but we need help and I don't want to run this. It's not right for the company and the opportunity So he said, "I'll come and I'll consult to you." I put together a plan and I had my Vertica and data robot. NekTony guys do the technical diligence to make sure that the architecture wasn't wedded to the dupe, like all the other ones were and when I saw it wasn't then I knew the market opportunity was to take that, rifle and point it at that legacy $150 billion BI market not at the billion dollar market of Hadoop. And when we did that, we've been growing at 162% quarter-over-quarter. We've built development centers in Bulgaria. We've moved all operations, non-technical to Boston here down in our South Station. We've been on fire and we are the partner of choice of every cloud manner, because we eliminate the sales friction, for customers being able to take advantage of movement to the cloud and we're able through our intelligent pipeline and capability. We're able to reduce the cost significantly of queries because we understand and we were able to intelligently cash those queries. >> Sales ops is here, all-- >> Sales marketing, customer support, customer success and we're building a machine learning team here at Dev team here. >> Where are you in that sort of Boston build-out? >> We have an office on 711 Atlantic that we opened in the fall. We're actually moving from 4,000 square feet to 10,000 this month. In less than six months and we'll house by the first year, 100 employees in Boston 100 in Bulgaria and about that same hundred in San Mateo. >> Are you going after net new business mainly? Or there's a lot of legacy BI out there are you more displacing those products? >> A couple of things. What we find is that, customers want to evolve into the cloud, they don't want a revolution they want a evolution. So we allow them, because we support hybrid cloud to keep some data behind the firewall and then experiment with moving other data to the cloud platform of choice but we're still providing that one logical view. I would say most of our customers are looking to reap platform, off of Teradata or something onto a, another platform like Snowflake. And then we have a set of customers that see that as part of the solution but not the whole solution. They're more true hybrids but I would say that 80% of our customers are traditional BI customers that are trying to contemporize their environments and be able to take advantage of tabular support and multidimensional, the things that we do in addition to the cube world. >> They can keep whatever they're using. >> Correct, that's the key. >> Did you do the series D, you did, right? >> Yes, Morgan Stanely led. >> So you're not actively but you're good for now, It was like $50 million >> Yeah we raised $50 million. >> You're good for a bit. Who's in the Chris Lynch target? (laughs) Who's the enemy? Vertica, I could say it was the traditional database guys. Who's the? >> We're in a unique position, we're almost Switzerland so we could be friend to foe, of anybody in that ecosystem because we can, non-disruptively re-platform customers between legacy platforms or from legacy platforms to the cloud. We're an interesting position. >> So similar to the file sharing. File virtualization company >> The Copier. >> Copier yeah. >> It puts us in an interesting position. They need to be friends with us and at the same time I'm sure that they're concerned about the capabilities we have but we have a number of retail customers for instance that have asked us to move down from Amazon to Google BigQuery, which we accommodate and because we can do that non-disruptively. The cost and the ability to move is eliminated. It gives customers true freedom of choice. >> How worried are you, that AWS tries to replicate what you guys do. You're in their sights. >> I think there are technical, legal and structural barriers to them doing that. The technical is, this team has been at it for six and a half years. So to do what we do, they'll have to do what we've done. Structurally from a business perspective if they could, I'm not sure they want to. The way to think about Amazon is, they're no different than Teradata, except for they want the same vendor lock-in except they want it to be the Amazon Cloud when Teradata wanted it to be, their data warehouse. >> They don't promote multi-cloud versus-- >> Yeah, they don't want multi-cloud they don't want >> On Prem >> Customers to have a freedom of choice. Would they really enable a heterogeneous abstraction layer, I don't think they would nor do I think any of the big guys would. They all claim to have this capability for their system. It's like the old IBM adage I'm in prison but the food's going to get three squares a day, I get cable TV but I'm in prison. (laughing) >> Awesome, all right, parting thoughts. >> Parting thoughts, oh geez you got to give me a question I'm not that creative. >> What's next, for you guys? What should we be paying attention to? >> I think you're going to see some significant announcements in September regarding the company and relationships that I think will validate the impact we're having in the market. >> Give you some leverage >> Yeah, will give us, better channel leverage. We have a major technical announcement that I think will be significant to the marketplace and what will be highly disruptive to some of the people you just mentioned. In terms of really raising the bar for customers to be able to have the freedom of choice without any sort of vendor lock-in. And I think that that will create some counter strike which we'll be ready for. (laughing) >> If you've never heard of AtScale before trust me you're going to in the next 18 months. Chris Lynch, thanks so much for coming on theCUBE. >> It's my pleasure. >> Great to see you. All right, keep it right there everybody we're back with our next guest, right after this short break you're watching theCUBE from MIT, right back. (upbeat music)

(techno music) >> From Cambridge, Massachusetts, it's theCUBE. Covering MIT Chief Data Officer and Information Quality Symposium 2019. Brought to you by SiliconANGLE Media. >> Welcome back to Cambridge, Massachusetts everybody, we're here with theCUBE at the MIT Chief Data Officer Information Quality Conference. I'm Dave Vellante with my co-host Paul Gillin. Susan Wilson is here, she's the vice president of data governance and she's the leader at Informatica. Blake Anders is the corporate vice president of data governance at New York Life. Folks, welcome to theCUBE, thanks for coming on. >> Thank you. >> Thank you. >> So, Susan, interesting title; VP, data governance leader, Informatica. So, what are you leading at Informatica? >> We're helping our customers realize their business outcomes and objectives. Prior to joining Informatica about 7 years ago, I was actually a customer myself, and so often times I'm working with our customers to understand where they are, where they going, and how to best help them; because we recognize data governance is more than just a tool, it's a capability that represents people, the processes, the culture, as well as the technology. >> Yeah so you've walked the walk, and you can empathize with what your customers are going through. And Blake, your role, as the corporate VP, but more specifically the data governance lead. >> Right, so I lead the data governance capabilities and execution group at New York Life. We're focused on providing skills and tools that enable government's activities across the enterprise at the company. >> How long has that function been in place? >> We've been in place for about two and half years now. >> So, I don't know if you guys heard Mark Ramsey this morning, the key-note, but basically he said, okay, we started with enterprise data warehouse, we went to master data management, then we kind of did this top-down enterprise data model; that all failed. So we said, all right, let's pump the governance. Here you go guys, you fix our corporate data problem. Now, right tool for the right job but, and so, we were sort of joking, did data governance fail? No, you always have to have data governance. It's like brushing your teeth. But so, like I said, I don't know if you heard that, but what are your thoughts on that sort of evolution that he described? As sort of, failures of things like EDW to live up to expectations and then, okay guys over to you. Is that a common theme? >> It is a common theme, and what we're finding with many of our customers is that they had tried many of the, if you will, the methodologies around data governance, right? Around policies and structures. And we describe this as the Data 1.0 journey, which was more application-centric reporting to Data 2.0 to data warehousing. And a lot of the failed attempts, if you will, at centralizing, if you will, all of your data, to now Data 3.0, where we look at the explosion of data, the volumes of data, the number of data consumers, the expectations of the chief data officer to solve business outcomes; crushing under the scale of, I can't fit all of this into a centralized data at repository, I need something that will help me scale and to become more agile. And so, that message does resonate with us, but we're not saying data warehouses don't exist. They absolutely do for trusted data sources, but the ability to be agile and to address many of your organizations needs and to be able to service multiple consumers is top-of-mind for many of our customers. >> And the mind set from 1.0 to 2.0 to 3.0 has changed. From, you know, data as a liability, to now data as this massive asset. It's sort of-- >> Value, yeah. >> Yeah, and the pendulum is swung. It's almost like a see-saw. Where, and I'm not sure it's ever going to flip back, but it is to a certain extent; people are starting to realize, wow, we have to be careful about what we do with our data. But still, it's go, go, go. But, what's the experience at New York Life? I mean, you know. A company that's been around for a long time, conservative, wants to make sure risk averse, obviously. >> Right. >> But at the same time, you want to keep moving as the market moves. >> Right, and we look at data governance as really an enabler and a value-add activity. We're not a governance practice for the sake of governance. We're not there to create a lot of policies and restrictions. We're there to add value and to enable innovation in our business and really drive that execution, that efficiency. >> So how do you do that? Square that circle for me, because a lot of people think, when people think security and governance and compliance they think, oh, that stifles innovation. How do you make governance an engine of innovation? >> You provide transparency around your data. So, it's transparency around, what does the data mean? What data assets do we have? Where can I find that? Where are my most trusted sources of data? What does the quality of that data look like? So all those things together really enable your data consumers to take that information and create new value for the company. So it's really about enabling your value creators throughout the organization. >> So data is an ingredient. I can tell you where it is, I can give you some kind of rating as to the quality of that data and it's usefulness. And then you can take it and do what you need to do with it in your specific line of business. >> That's right. >> Now you said you've been at this two and half years, so what stages have you gone through since you first began the data governance initiative. >> Sure, so our first year, year and half was really focused on building the foundations, establishing the playbook for data governance and building our processes and understanding how data governance needed to be implemented to fit New York Life in the culture of the company. The last twelve months or so has really been focused on operationalizing governance. So we've got the foundations in place, now it's about implementing tools to further augment those capabilities and help assist our data stewards and give them a better skill set and a better tool set to do their jobs. >> Are you, sort of, crowdsourcing the process? I mean, you have a defined set of people who are responsible for governance, or is everyone taking a role? >> So, it is a two-pronged approach, we do have dedicated data stewards. There's approximately 15 across various lines of business throughout the company. But, we are building towards a data democratization aspect. So, we want people to be self-sufficient in finding the data that they need and understanding the data. And then, when they have questions, relying on our stewards as a network of subject matter experts who also have some authorizations to make changes and adapt the data as needed. >> Susan, one of the challenges that we see is that the chief data officers often times are not involved in some of these skunkworks AI projects. They're sort of either hidden, maybe not even hidden, but they're in the line of business, they're moving. You know, there's a mentality of move fast and break things. The challenge with AI is, if you start operationalizing AI and you're breaking things without data quality, without data governance, you can really affect lives. We've seen it. In one of these unintended consequences. I mean, Facebook is the obvious example and there are many, many others. But, are you seeing that? How are you seeing organizations dealing with that problem? >> As Blake was mentioning often times what it is about, you've got to start with transparency, and you got to start with collaborating across your lines of businesses, including the data scientists, and including in terms of what they are doing. And actually provide that level of transparency, provide a level of collaboration. And a lot of that is through the use of our technology enablers to basically go out and find where the data is and what people are using and to be able to provide a mechanism for them to collaborate in terms of, hey, how do I get access to that? I didn't realize you were the SME for that particular component. And then also, did you realize that there is a policy associated to the data that you're managing and it can't be shared externally or with certain consumer data sets. So, the objective really is around how to create a platform to ensure that any one in your organization, whether I'm in the line of business, that I don't have a technical background, or someone who does have a technical background, they can come and access and understand that information and connect with their peers. >> So you're helping them to discover the data. What do you do at that stage? >> What we do at that stage is, creating insights for anyone in the organization to understand it from an impact analysis perspective. So, for example, if I'm going to make changes, to as well as discovery. Where exactly is my information? And so we have-- >> Right. How do you help your customers discover that data? >> Through machine learning and artificial intelligence capabilities of our, specifically, our data catalog, that allows us to do that. So we use such things like similarity based matching which help us to identify. It doesn't have to be named, in miscellaneous text one, it could be named in that particular column name. But, in our ability to scan and discover we can identify in that column what is potentially social security number. It might have resided over years of having this data, but you may not realize that it's still stored there. Our ability to identify that and report that out to the data stewards as well as the data analysts, as well as to the privacy individuals is critical. So, with that being said, then they can actually identify the appropriate policies that need to be adhered to, alongside with it in terms of quality, in terms of, is there something that we need to archive. So that's where we're helping our customers in that aspect. >> So you can infer from the data, the meta data, and then, with a fair degree of accuracy, categorize it and automate that. >> Exactly. We've got a customer that actually ran this and they said that, you know, we took three people, three months to actually physically tag where all this information existed across something like 7,000 critical data elements. And, basically, after the set up and the scanning procedures, within seconds we were able to get within 90% precision. Because, again, we've dealt a lot with meta data. It's core to our artificial intelligence and machine learning. And it's core to how we built out our platforms to share that meta data, to do something with that meta data. It's not just about sharing the glossary and the definition information. We also want to automate and reduce the manual burden. Because we recognize with that scale, manual documentation, manual cataloging and tagging just, >> It doesn't work. >> It doesn't work. It doesn't scale. >> Humans are bad at it. >> They're horrible at it. >> So I presume you have a chief data officer at New York Life, is that correct? >> We have a chief data and analytics officer, yes. >> Okay, and you work within that group? >> Yes, that is correct. >> Do you report it to that? >> Yes, so-- >> And that individual, yeah, describe the organization. >> So that sits in our lines of business. Originally, our data governance office sat in technology. And then, our early 2018 we actually re-orged into the business under the chief data and analytics officer when that role was formed. So we sit under that group along with a data solutions and governance team that includes several of our data stewards and also some others, some data engineer-type roles. And then, our center for data science and analytics as well that contains a lot of our data science teams in that type of work. >> So in thinking about some of these, I was describing to Susan, as these skunkworks projects, is the data team, the chief data officer's team involved in those projects or is it sort of a, go run water through the pipes, get an MVP and then you guys come in. How does that all work? >> We're working to try to centralize that function as much as we can, because we do believe there's value in the left hand knowing what the right hand is doing in those types of things. So we're trying to build those communications channels and build that network of data consumers across the organization. >> It's hard right? >> It is. >> Because the line of business wants to move fast, and you're saying, hey, we can help. And they think you're going to slow them down, but in fact, you got to make the case and show the success because you're actually not going to slow them down to terms of the ultimate outcome. I think that's the case that you're trying to make, right? >> And that's one of the things that we try to really focus on and I think that's one of the advantages to us being embedded in the business under the CDAO role, is that we can then say our objectives are your objectives. We are here to add value and to align with what you're working on. We're not trying to slow you down or hinder you, we're really trying to bring more to the table and augment what you're already trying to achieve. >> Sometimes getting that organization right means everything, as we've seen. >> Absolutely. >> That's right. >> How are you applying governance discipline to unstructured data? >> That's actually something that's a little bit further down our road map, but one of the things that we have started doing is looking at our taxonomy's for structured data and aligning those with the taxonomy's that we're using to classify unstructured data. So, that's something we're in the early stages with, so that when we get to that process of looking at more of our unstructured content, we can, we already have a good feel for there's alignment between the way that we think about and organize those concepts. >> Have you identified automation tools that can help to bring structure to that unstructured data? >> Yes, we have. And there are several tools out there that we're continuing to investigate and look at. But, that's one of the key things that we're trying to achieve through this process is bringing structure to unstructured content. >> So, the conference. First year at the conference. >> Yes. >> Kind of key take aways, things that interesting to you, learnings? >> Oh, yes, well the number of CDO's that are here and what's top of mind for them. I mean, it ranges from, how do I stand up my operating model? We just had a session just about 30 minutes ago. A lot of questions around, how do I set up my organization structure? How do I stand up my operating model so that I could be flexible? To, right, the data scientists, to the folks that are more traditional in structured and trusted data. So, still these things are top-of-mind and because they're recognizing the market is also changing too. And the growing amount of expectations, not only solving business outcomes, but also regulatory compliance, privacy is also top-of-mind for a lot of customers. In terms of, how would I get started? And what's the appropriate structure and mechanism for doing so? So we're getting a lot of those types of questions as well. So, the good thing is many of us have had years of experience in this phase and the convergence of us being able to support our customers, not only in our principles around how we implement the framework, but also the technology is really coming together very nicely. >> Anything you'd add, Blake? >> I think it's really impressive to see the level of engagement with thought leaders and decision makers in the data space. You know, as Susan mentioned, we just got out of our session and really, by the end of it, it turned into more of an open discussion. There was just this kind of back and forth between the participants. And so it's really engaging to see that level of passion from such a distinguished group of individuals who are all kind of here to share thoughts and ideas. >> Well anytime you come to a conference, it's sort of any open forum like this, you learn a lot. When you're at MIT, it's like super-charged. With the big brains. >> Exactly, you feel it when you come on the campus. >> You feel smarter when you walk out of here. >> Exactly, I know. >> Well, guys, thanks so much for coming to theCUBE. It was great to have you. >> Thank you for having us. We appreciate it, thank you. >> You're welcome. All right, keep it right there everybody. Paul and I will be back with our next guest. You're watching theCUBE from MIT in Cambridge. We'll be right back. (techno music)