(upbeat music) >> Okay, welcome back everyone to theCUBE's coverage here at re:MARS. I'm John Furrier, host of theCUBE. It's the event where it's part of the "re:" series: re:MARS, re:Inforce, re:Invent. MARS stands for machine learning, automation, robotics, and space. And a lot of conversation is all about AI machine learning. This one's about AI and business transformation. We've got Stepan Pushkarev CTO, CEO, Co-Founder of Provectus. Welcome to theCUBE. And Russ Lamb, eCommerce Retail Data Engineering Lead at PepsiCo, customer story. Gentlemen, thanks for coming on theCUBE. >> Great to be here, John. >> Yeah, thanks for having us. >> I love the practical customer stories because it brings everything to life. This show is about the future, but it's got all the things we want, we love: machine learning, robotics, automation. If you're in DevOps, or you're in data engineering, this is the world of automation. So what's the relationship? You guys, you're a customer. Talk about the relationship between you guys. >> Sure, sure. Provectus as a whole is a professional services firm, premier, a AWS partner, specializing in machine learning, data, DevOps. PepsiCo is our customer, our marquee customer, lovely customer. So happy to jointly present at this re:Invent, sorry, re:MARS. Anyway, Russ... >> I made that mistake earlier, by the way, 'cause re:Invent's always on the tip of my tongue and re:MARS is just, I'm not used to it yet, but I'm getting there. Talk about what are you guys working together on? >> Well, I mean, we work with Provectus in a lot of ways. They really helped us get started within our e-commerce division with AWS, provided a lot of expertise in that regard and, you know, just hands-on experience. >> We were talking before we came on camera, you guys just had another talk and how it's all future and kind of get back to reality, Earth. >> Russ: Get back to Earth. >> If we're on earth still. We're not on Mars yet, or the moon. You know, AI's kind of got a future, but it does give a tell sign to what's coming, industrial change, full transformation, 'cause cloud does the back office. You got data centers. Now you've got cloud going to the edge with industrial spaces, the ultimate poster child of edge and automation safety. But at the end of the day, we're still in the real world. Now people got to run businesses. And I think, you know, having you here is interesting. So I have to ask you, you know, as you look at the technology, you got to see AI everywhere. And the theme here, to me, that I see is the inflection point driving all this future robotics change, that everyone's been waiting for by the way, but it's like been in movies and in novels, is the machine learning and AI as the tipping point. This is key. And now you're here integrating AI into your company. Tell us your story. >> Well, I think that every enterprise is going to need more machine learning, more, you know, AI or data science. And that's the journey that we're on right now. And we've come a long way in the past six years, particularly with our e-commerce division, it's a really data rich environment. So, you know, going from brick and mortar, you know, delivering to restaurants, vending machines and stuff, it's a whole different world when you're, people are ordering on Amazon every couple minutes, or seconds even, our products. But they, being able to track all that... >> Can you scope the problem statement and the opportunity? Because if I just kind of just, again, I'm not, you're in, it's your company, you're in the weeds, you're at the data, you're everything, But it just seems me, the world's now more integration, more different data sources. You've got suppliers, they have their different IT back ends. Some are in the cloud, some aren't in the cloud. This is, like, a hard problem when you want to bring data together. I mean, API certainly help, but can you scope the problem, and, like, what we're talking about here? >> Well, we've got so many different sources of data now, right? So we used to be relying on a couple of aggregators who would pull all this data for us and hand us an aggregated view of things. But now we're able to partner with different retailers and get detail, granular information about transactions, orders. And it's just changed the game, changed the landscape from just, like, getting a rough view, to seeing the nuts and bolts and, like, all the moving parts. >> Yeah, and you see in data engineering much more tied into like cloud scale. Then you got the data scientists, more the democratization application and enablement. So I got to ask, how did you guys connect? What was the problem statement? How did you guys, did you have smoke and fire? You came in solved the problem? Was it a growth thing? How did this, how did you guys connect as a customer with Provectus? >> Yeah, I can elaborate on that. So we were in the very beginning of that journey when there was, like, just a few people in this new startup, let's call it startup within PepsiCo. >> John: Yeah. >> Calling like a, it's not only e-commerce, it was a huge belief from the top management that it's going to bring tremendous value to the enterprise. So there was no single use case, "Hey, do this and you're going to get that." So it's a huge belief that e-commerce is the future. Some industry trends like from brand-centric to consumer-centric. So brand, product-centric. Amazon has the mission to build the most customer-centric customer company. And I believe that success, it gets a lot of enterprises are being influenced by that success. So I remember that time, PepsiCo had a huge belief. We started building just from scratch, figuring out what does the business need? What are the business use cases? We have not started with the IT. We have not started with this very complicated migrations, modernizations. >> John: So clean sheet of paper. >> Yeah. >> From scratch. >> From scratch. >> And so you got the green light. >> Yeah. >> And the leadership threw the holy water on that and said, "Hey, we'll do this."? >> That's exactly what happened. It was from the top down. The CEO kind of set aside the e-commerce vision as kind of being able to, in a rapidly evolving business place like e-commerce, it's a growing field. Not everybody's figured it out yet, but to be able to change quickly, right? The business needs to change quickly. The technology needs to change quickly. And that's what we're doing here. >> So this is interesting. A lot of companies don't have that, actually, luxury. I mean, it's still more fun because the tools are available now that all the hyper scales built on their own. I mean, back in the day, 10 years ago, they had to build it all, Facebook. You didn't know, I had people on here from Pinterest and other companies. They had to build all of that from scratch. Now cloud's here. So how did you guys do this? What was the playbook? Take us through the AI because it sounds like the AI is core, you know, belief principle of the whole entire system. What did you guys do? Take me through the journey there. >> Yeah. Beyond management decisions, strategic decisions that has been made as a separate startup, whatever- >> John: That's great. >> So some practical, tactical. So it may sound like a cliche, but it's a huge thing because I work with many enterprises and this, like, "center of excellence" that does a nice technology stuff and then looks for the budget on the different business units. It just doesn't go anywhere. It could take you forever to modernize. >> We call that the Game of Thrones environment. >> Yes. >> Yeah. Nothing ever gets done 'till it blows up at the end. >> Here, these guys, and I have to admit, I don't want to steal their thunder. I just want to emphasize it as an external person. These guys just made it so differently. >> John: Yeah. >> They even physically sat in a different office in a WeWork co-working and built that business from scratch. >> That's what Andy Jackson talked about two years ago. And if you look at some of the big successes on AWS, Capital One, all the big, Goldman Sachs. The leadership, real commitment, not like BS, like total commitment says, "Go." But enough rope to give you some room, right? >> Yeah. I think that's the thing is, there was always an IT presence, right, overseeing what we were doing within e-commerce, but we had a lot of freedoms to make design choices, technology choices, and really accelerate the business, focus on those use cases where we could make a big impact with a technology choice. >> Take me through the stages of the AI transformation. What are some of the use cases and specific tactics you guys executed on? >> Well, I think that the supply chain, which I think is a hot topic right now, but that was one use case where we're using, like, data real time, real time data to inform our sales projections and delivery logistics. But also our marketing return on investment, I feel like that was a really interesting, complex problem to solve using machine learning, Because there's so much data that we needed to process in terms of countries, territories, products, like where do you spend your limited marketing budget when you have so many choices, and, using machine learning, boil that all down to, you know, this is the optimal choice, right now. >> What were some of the challenges and how did you overcome them in the early days to get things set up, 'cause it takes a lot of energy to get it going, to get the models. What were some of the challenges and how did you overcome them? >> Well, I think some of it was expertise, right? Like having a partner like Provectus and Stepan really helped because they could guide us, Stepan could guide us, give his expertise and what he knows in terms of what he's seen to our budding and growing business. >> And what were the things that you guys saw that you contributed on? And was there anything new that you had to do together? >> Yeah, so yeah. First of all, just a very practical tip. Yes, start with the use cases. Clearly talk to the business and say, "Hey, these are the list of the use cases" and prioritize them. So not with IT, not with technology, not with the migration thing. Don't touch anything on legacy systems. Second, get data in. So you may have your legacy systems or some other third party systems that you work with. There's no AI without data. Get all the pipelines, get data. Quickly boat strap the data lake house. Put all the pipelines, all the governance in place. And yeah, literally took us three months to get up and running. And we started delivering first analytical reports. It's just to have something back to business and keep going. >> By the way, that's huge, speed. I mean, this is speed. You go back and had that baggage of IT and the old antiquated systems, you'd be dragging probably months. Right? >> It's years, years. Imagine you should migrate SAP to the cloud first. No, you don't do don't need to do that. >> Pipeline. >> Just get data. I need data. >> Stream that data. All right, where are we now? When did you guys start? I want to get just going to timeline my head 'cause I heard three months. Where are we now? You guys threw it. Now you have impact. You have, you have results. >> Yeah. I mean that for our marketing ROI engine, we've built it and it's developed within e-commerce, but we've started to spread it throughout the organization now. So it's not just about the digital and the e-commerce space. We're deploying it to, you know, regionally to other, to Europe, to Latin America, other divisions within PepsiCo. And it's just grown exponentially. >> So you have scale to it right now? >> Yeah. Well- >> How far are you in now? What, how many years, months, days? >> E-commerce, the division was created six years ago, which is, so we've had some time to develop this, our machine learning capabilities and this use case particular, but it's increasingly relevant and expansion is happening as we speak. >> What are you most proud of? You look back at the impact. What are you most proud of? >> I think the relationship we built with the people, you know, who use our technology, right. Just seeing the impact is what makes me proud. >> Can you give an example without revealing any confidential information? >> Yeah. Yeah. I mean, there was an example from my talk about, I was approached recently by our sales team. They were having difficulty with supply chain, monitoring our fill rate of our top brands with these retailers. And they come up to me, they have this problem. They're like, "How do we solve it?" So we work together to find a data source, just start getting that data in the hands of people who can use it within days. You know, not talking like a long time. Bring that data into our data warehouse, and then surface the data in a tool they can use, you know, within a matter of a week or two. >> I mean, the transformation is just incredible. In fact, we were talking on theCUBE earlier today around, you know, data warehouses in the cloud, data meshes of different pros and cons. And the theme that came out of that conversation was data's a product now. >> Yes. >> Yes. >> And what you're kind of describing is, just gimme the product or find it. >> Russ: Right. >> And bring it in with everything else. And there's some, you know, cleaning and stuff people do if they have issues with that. But, if not, it's just bring it in, right? It's a product. >> Well, especially with the data exchanges now. AWS has a data exchange and this, I think, is the future of data and what's possible with data because you don't have to start from, okay, I've got this Excel file somebody's been working with on their desktop. This is a, someone's taken that file, put it into a warehouse or a data model, and then they can share it with you. >> John: So are you happy with these guys? >> Absolutely, yeah. >> You're actually telling the story. What was the biggest impact that they did? Was it partnering? Was it writing code, bringing development in, counseling, all the above, managed services? What? >> I think the biggest impact was the idea, you know, like being able to bring ideas to the table and not just, you know, ask us what we want, right? Like I think Provectus is a true partner and was able to share that sort of expertise with us. >> You know, Andy Jackson, whenever I interview on theCUBE, he's now in charge of all Amazon. But when he was at (inaudible). He always had to use their learnings, get the learnings out. What was the learnings you look back now and say, Hey, those were tough times. We overcome them. We stopped, we started, we iterated, we kept moving forward. What was the big learning as you look back, some of the key success points, maybe some failures that you overcome. What was the big learnings that you could share with folks out there now that are in the same situation where they're saying, "Hey, I'd rather start from scratch and do a reset." >> Yeah. So with that in particular, yes, we started this like sort of startup within the enterprise, but now we've got to integrate, right? It's been six years and e-commerce is now sharing our data with the rest of the organization. How do we do that, right? There's an enterprise solution, and we've got this scrappy or, I mean, not scrappy anymore, but we've got our own, you know, way of doing. >> Kind of boot strap. I mean, you were kind of given charter. It's a start up within a big company, I mean- >> But our data platform now is robust, and it's one of the best I've seen. But how do we now get those systems to talk? And I think Provectus has came to us with, "Here, there's this idea called data mesh, where you can, you know, have these two independent platforms, but share the data in a centralized way. >> So you guys are obviously have a data mesh in place, big part of the architecture? >> So it is in progress, but we know the next step. So we know the next step. We know the next two steps, what we're going to do, what we need to do to make it really, to have that common method, data layer. between different data products within organization, different locations, different business units. So they can start talking to each other through the data and have specific escalates on the data. And yeah. >> It's smart because I think one of the things that people, I think, I'd love to get your reaction to this is that we've been telling the story for many, many years, you have horizontally scalable cloud and vertically specialized domain solutions, you need machine learning that's smart, but you need a lot of data to help it. And that's not, a new architecture, that's a data plane, it's control plane, but now everyone goes, "Okay, let's do silos." And they forget the scale side. And then they go, "Wait a minute." You know, "I'm not going to share it." And so you have this new debate of, and I want to own my own data. So the data layer becomes an interesting conversation. >> Yeah, yes. Meta data. >> Yeah. So what, how do you guys see that? Because this becomes a super important kind of decision point architecturally. >> I mean, my take is that there has to be some, there will always be domains, right? Everyone, like there's only so much that you can find commonality across, like in industry, for example. But there will always be a data owner. And, you know, kind of like what happened with rush to APIs, how that enabled microservices within applications and being sharing in a standardized way, I think something like that has to happen in the data space. So it's not a monolithic data warehouse, it's- >> You know, the other thing I want to ask you guys both, if you don't mind commenting while I got you here, 'cause you're both experts. >> We just did a showcase on data programmability. Kind of a radical idea, but like data as code, we called it. >> Oh yeah. >> And so if data's a product and you're acting on, you've got an architecture and system set up, you got to might code it's programmable. You need you're coding with data. Data becomes like a part of the development process. What do you guys think of when you hear data as code and data being programmable? >> Yeah, it's a interesting, so yeah, first of all, I think Russ can elaborate on that, Data engineering is also software engineering. Machine learning engineering is a software. At the end of the day, it's all product. So we can use different terms and buzz words for that but this is what we have at the end of the day. So having the data, well I will use another buzz word, but in terms of the headless architecture- >> Yes. >> When you have a nice SDK, nice API, but you can manipulate with the data as your programming object to build reach applications for your users, and give it, and share not as just a table in Redshift or a bunch of CSV files in S3 bucket, but share it as a programmable thing that you can work with. >> Data as code. >> Yeah. This is- >> Infrastructure code was a revolution for DevOps, but it's not AI Ops so it's something different. It's really it's data engineering. It's programming. >> Yeah. This is the way to deliver data to your consumers. So there are different ways you can show it on a dashboard. You can show it, you can expose it as an API, or you can give it as an object, programmable interface. >> So now you're set up with a data architecture that's extensible 'cause that's the goal. You don't want to foreclose. You must think about that must keep you up at night. What's going to foreclose that benefit? 'Cause there's more coming. Right? >> Absolutely. There's always more coming. And I think that's why it's important to have that robust data platform to work from. And yeah, as Stepan mentioned, I'm a big believer in data engineering as software engineering. It's not some like it's not completely separate. You have to follow the best practices software engineers practice. And, you know, really think about maintainability and scalability. >> You know, we were riffing about how cloud had the SRE managing all those servers. One person, data engineering has a many, a one to many relationships too. You got a lot going on. It's not managing a database. It's millions of data points and data opportunity. So gentlemen, thanks for coming on theCUBE. I really appreciate it. And thanks for telling the story of Pepsi. >> Of course, >> And great conversation. Congratulations on this great customer. And thanks for >> coming on theCUBE. >> Thanks, thank you. Thanks, Russ, would you like to wrap it up with the pantry shops story? >> Oh, yeah! I think it will just be a super relevant evidence of the agility and speed and some real world applicable >> Let's go. Close us out. >> So when, when the pandemic happened and there were lockdowns everywhere, people started buying things online. And we noticed this and got a challenge from our direct to consumer team saying, "Look, we need a storefront to be able to sell to our consumers, and we've got 30 days to do it." We need to be able to work fast. And so we built not just a website, but like everything that behind it, the logistics of supply chain aspects, the data platform. And we didn't just build one. We built two. We got pantry shop.com and snacks.com, within 30 days. >> Good domains! >> The domain broker was happy on that one. Well continue the story. >> Yeah, yeah. So I feel like that the agility that's required for that kind of thing and the like the planning to be able to scale from just, you know, an idea to something that people can use every day. And, and that's, I think.- >> And you know, that's a great point too, that shows if you're in the cloud, you're doing the work you're prepared for anything. The pandemic was the true test for who was ready because it was unforeseen force majeure. It was just like here it comes and the people who were in the cloud had that set up, could move quickly. The ones that couldn't. >> Exactly. >> We know what happened. >> And I would like to echo this. So they have built not just a website, they have built the whole business line within, and launched that successfully to production. That includes sales, marketing, supply chain, e-commerce, aside within 30 days. And that's just a role model that could be used by other enterprises. >> Yeah. And it was not possible without, first of all, right culture. And second, without cloud Amazon elasticity and all the tools that we have in place. >> Well, the right architecture allows for scale. That's the whole, I mean, you did everything right at the architecture that's scale. I mean, you're scaling. >> And we empower our engineers to make those choices, right. We're not, like, super bureaucratic where every decision has to be approved by the manager or the managers manager. The engineers have the power to just make good decisions, and that's how we move fast. >> That's exactly the future right there. And this is what it's all about. Reliability, scale agility, the ability to react and have applications roll out on top of it without long timeframes. Congratulations. Thanks for being on theCUBE. Appreciate it. All right. >> Thank you. >> Okay, you're watching theCUBE here at re:MARS 2020, I'm John Furrier. Stay tuned. We've got more coverage coming after this short break. (upbeat music)