(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)

>> I've got Madhav Mekala here with me, commerce architect at PepsiCo Madhav welcome to the program. >> Thank you Lisa. >> So we're going to be talking about the solution that you implemented that helped with the global supply chain. So let's talk first about your role, commerce architect. Help me understand that a little bit better. >> So Frito-Lay PepsiCo is pretty big. It's a conglomerate of multiple product lines. So I worked for Frito-Lay, which is basically all the salty snacks and then we have a Quaker products as well in our portfolio. So I oversee all the architecture for all the commercial IoT solutions in the FNA portfolio. >> Got it all the commercial lines. So we all know the last 18 months major challenges with the global supply chain component shortages, we've seen a huge increase in the cost of raw materials, limited labor, but you guys actually started to tackle this challenge before the pandemic happened. So talk to me about the catalyst that PepsiCo, what you saw to modernize field service and supply chain application. >> Yeah, so we have a pretty old system that our field force, our frontline users are using. So we have a world-class supply chain system where we go into the stores and place orders and deliver products throughout the U.S. And then we penetrate, I think, more than 95% of the households with our products. So we need to have a robust supply chain as well as a good frontline sales application, to be able to manage the orders, and be able to deliver the products, right? So the system that we have is almost 20 year old system running on a very outdated technology. We've been trying to replace that for a while now. And finally, we started this early last year to completely replace the solution with a brand new IPhone based app. And then that gives our frontline the ability to go place orders, do deliveries to retail execution in the store like check-in check-out, bill displays. There are so much functionality that our RSRs or frontline users do in the stores and this app enables them to do much more efficiently. >> And we're going to break into that, but you mentioned you had a 20 year old technology. Talk to me about some of the challenges that that likely presented to those frontline workers. >> Yeah. I mean, there are multiple challenges for one, we cannot enable new business models. So business wants to come up with new ideas for, to be able to implement in the field, but with our system being so old, it's so hard to implement anything on that one. And then even the physical device is not scaling. We had a lot of memory issues, so it's time for it to kind of retire, but also the technology we use the 3G technology is retiring pretty soon at the next year. So we were definitely need to move to a new solution. And this is one of the must things we have to do right away. So that's where we started the project and we are in pilot phase right now. >> What would have been some of those negative consequences, had you not undertaken the effort? I imagine from a competitive perspective, knowing how much competition is out there, what would some of those challenges have been if this had persisted? >> Yeah, so one is the stability of the application, right? So the frontline users have to spend more time because the app is not stable, the current one. So that reduces the efficiency of our Salesforce. Right? And then on the other hand, we also not able to put new features or new business models enable new business models on top of the existing ones. So we are losing out on some of them because of our outdated system. So that's one thing we want to solve with the new one. >> So this is really critical to really evolve PepsiCo's business at, at its baseline, right? >> That's true. Yeah. It is very critical application that we are building and this will enable us to do a lot more things in future. And we can come up with new ideas, including like virtual reality or connecting to multiple systems. There are so many new ideas that we want to enable once we have this in place. >> Awesome. Talk to me about why Couchbase and then tell us more about, you started to talk a little bit about the solution, but let's go ahead and dig in and unpack the actual solution that you implemented. >> Yeah. So this is, eh, we call it an ERP and a mobile device because it has so much functionality as a company Frito-Lay, we have been over a hundred years in this business, right? We have so many optimized process that we have that kind of led to some digility in the system because we want to do in a particular way, because that's the best way to do it as part of our business process. So what we're trying to do here is take that business process and also provide an app that will enhance it and then connect to more, more systems. So that's what we are trying to do here. And then on top of that one, we will replace all the existing peripherals that we use with the new technology, like Bluetooth and all so that, they are much more faster and they slot more productive for our frontline force. >> Sounds like a lot of sales folks are going to to be a lot more productive. Talk to me about where Couchbase is as an integral component to this new system. >> Yeah. So one of the key requirements for this app is offline mode. What that means is one of our other salesforce who go from our system from our DC to other stores, should be able to run the whole day without any major disruption, even if they're not connected, let's say because when they go into big stores, typically there's no connection there all metal boxes. So the cellular reception is not there, but most of our work that we do from our frontline is within the store. So it has to be a full offline where we have to have all the data within the device and we should be able to place orders, create inventory that records or adjust inventory, and then create invoices. All the majority of the things that we do are in the store and they should be able to do without the connection. So that's where we explored multiple options and kind of zeroed in on Couchbase where we bring all the data into Couchbase database on the device and then sync it when there is connection, but there's no connection, we still have all the data on the device and we can go do all of our duties in the stores without any issues, even if it is not connected. >> So the sales folks can be in the stores with their mobile device, doing all the transactions that they need to do with the stores, regardless of if there's connectivity. Talk to me about what happens when they get back to connectivity in that and the Couchbase database sync. >> Yeah. And the other big thing we want is instant connect. I mean, when there's connectivity, we want instant sync with the backend, right? If there's new data that comes, we need that in the device. At the same time, if I place an order, I want to send it back immediately to our backend systems so that our fulfillment starts for those. So that's very critical when we have a lot of cutoff times for our orders. So we need order as soon as we've placed to be going into the backend systems. So what happens when it gets connected, as soon as the sales folks come out of the store or when, within the story they could connectivity the Couchbased technology that we are using using the sync gateway immediately syncs the data back and forth if there's any new data that's available. So that is key for us in this particular app. >> So our transactions happening in real time or near real time. >> Yeah. So the data flow happens in real time when there's connectivity, but when it is not connected still, it doesn't have any issue with the actual transactions with the RSR that can go complete anything that. >> Got it. Okay. So there's no impediment there. In fact, it's a productivity enhancer. It sounds like for all of those sales folks out on the frontline. Tell us so millions of documents go through the system, tens of billions of dollars. Talk to me about the volume of data and the actual monetary value that's traversing the system. >> Yeah. It's huge, again, this is kind of the lifeline of the company. The sales are always the life of any company, right? So most of the sales for Frito-Lay goes through our system and we're talking anywhere between hundreds of thousands of documents that flow through back and forth between the Couch between the device and the server. So there's a lot of master data that comes like products price from customers, all that information that comes from the backend to the device and all the orders inventory and everything that gets created on the device gets flown sync back to the server. So yeah, I mean, it's, it's a very complex system. And also from the volume perspective, it's huge. So we had to build a massive infrastructure on the backend to be able to handle all this. One of the key feature is again, we have this massive data that we need to sync to the devices, but each device should only get the portion of the data that they want because a particular Salesforce only goes to a small set of 20 stores, let's say. So the data that we sync to that device is only for those 20 stores. So that's the key here. So Couchbase allows us to do that. The Couchbase sync, where we can subset the data into different portions and only send the data that is relevant for a particular device. >> So then from a, from a latency perspective, it must be pretty low latency, pretty fast to be able to get this data back to the device and to the sales person that is in the middle of a transaction. >> Yes. I mean, it's pretty, the sink is very fast. The Couchbase sync, especially user's web sockets. And we do continuous replicators where if I complete an order, the next instant it's on the server. So it's, it's we observed the speeds improved a lot. So the technology that we are using uses syncs for a long, long time compared to Couchbase, and that's another productivity gain for our Salesforce. >> What were some of the differentials? You mentioned some of the technology requirements that PepsiCo had in rearchitecting, the infrastructure, but what were some of the key technology differentiators that really made Couchbase stand out as the obvious choice? >> Yeah, so we, when we started this project, we all know the sink is the key for this whole project, because we thought the data going back and forth, we cannot really build a robust offline app. So we looked at multiple options, other providers that are doing the sync. And we also looked at building our own sink, in-house using APIs, but then we did lots of performance testing across all the options that we had at that time. And then Couchbase came above all of them pretty handily. So obviously we can coach base takes care of the sync, and then we can focus on our business process. So we can go build all the business process and not worry about how to build the syncing engine. And then that is itself a big effort. So that's what Couchbase provided us saying a instant sync engine. And then we were able to focus more on our, the app applicants, the frontline application, the sensor application. >> And those business processes. Let's talk about some of the business outcomes. We've mentioned a few already in our conversation, increased in productivity, the sales forces increased in that as well. But I imagine there's a lot of benefits for the end-user customer in terms of being able to get the transactions completed faster. What are some of those positive business outcomes that PepsiCo is seeing as a result of implementing Couchbase? >> Yeah. So you hit on a couple of them that the sync times are definitely a big factor where that will directly give more time for the sales folks to go either go to most stores, or even if they go to the existing stores, they can do more, spend more time with the customer merchandising and making sure everything is correct. So that's one, also the new app users connect with a lot of new peripherals that are not available on the previous platform. Also, the, our folks are very enthusiastic about using a new app, right? So it's like coming into the 21st century for them using such an old lab for a long time. So a lot of things that they see, they can see the images of the bags while ordering, which was not a feature earlier. Some of them are small, but they make a huge impact on our users. So, yeah, I mean, and then this is just a start that we are doing. And then once we are able to completely implement this one, we have a lot more going into, in future. I was just talking about, we can do virtual reality or show them how to sell using virtual reality. We can show a display to a store manager saying, 'Hey, I want to put a display here. And this is how it looks,' they can show it on the phone directly, than just explaining and showing some paper images. So there's a lot of possibilities. >> A lot of improvements to the customer experience. It sounds like, it sounds like adoption is quite high for your folks who are used to 20 year old technology, probably being very excited that they have a modern app. But talk to me a little bit about the appetite of the organization to continue modernizing the application infrastructure and presuming going from older technology to that 21st century, like you talked about. >> Yeah. So in other parts, we are already modernized some of these. So we have been on the journey for the last four, five years building multiple digital platforms. So one of the examples I can give is when COVID hit, there's a lot of disruption for everybody, for the consumers, so they are not able to find the products in the stores, a lot people are afraid to go to the stores to even buy products. So we reacted very quickly and opened a consumer website called snacks.com, which Pepsi never sold it to consumer directly. We always go through our stores, but the first time we open the consumer channel and Couchbase powered some of it for the backend purpose. So this is not a mobile app, it's just a desktop app, but we already have been on the digital transmission journey, even before we quickly turn into COVID for the snacks.com. And similarly, we are, doing this for our retail execution, portion of it using this project. So, and then we'll be continuing to do this going forward to enable a lot of functionality for I mean, for all of our sales, as well as supply chain and other systems, so that we can be more efficient. We can be more elastic saying if there is more demand, our backend should be able to handle all that, which was not the case before. So now we've built a state of the art backend system on cloud. So there's a lot of transmission, digital transmission going on within PepsiCo. And I'm really proud to be part of this project so that we took this to the next level. And then this is just a start. We can do a lot more. >> Right? This is just the beginning. That sounds like a great transformation for a historied company that we all, everybody knows PepsiCo and all of its products. But it sounds like when the pandemic hit, you had the infrastructure in place to be able to pivot quickly to launch that direct to consumer, which of course consumers, patience has been quite thin in the last year and a half. Talk to me a little bit about the impact to the overall organization as a result of being able to, to get more direct with those consumers. >> Yeah. So till now, again, we are the business model is we sell to the stores and then go customer. So we'd never get a direct sense of what consumer liking is. I mean, we get through some surveys and stuff, but we don't have a direct channel to the consumer, which this particular project enabled us snacks.com. So we know the consumer behavior, how they buying patterns, browsing patterns, which ones they like and including with geography and all so we learned a lot from the consumer behavior point of view for the project. And then we kept on enhancing. So one new thing we introduced was called Multipack where the consumers can come and pick, make their own Multipacks basically. They can say, okay, I need these many of this particular product, this particular product and make their Multipack and we ship them the customized Multipack. And it was, such a huge hit that we are not able to even fulfill them so much demand was there for that one, so we had to revamp and then get back. And now it's a huge thing on all the snacks.com platform. So all of this is possible because we had a digital platform underneath that supports this kind of innovation. So the new business models are just coming to life in within weeks or even few months and that's what we will be trying to do with the new platform that we're building for this app as well, where we'll bring in lot of new business models on top of we have already. >> Excellent, a lot of transformation it sounds like at PepsiCo in the last couple of years, I love the customization, that personalization route that you're going and I think that's going to be a huge hit for consumers. And as you said, there's a lot of demand , Madhav thank you for joining me today, talking about how you are modernizing the field service and supply chain application, the impact it's making for end users for your customers and for the sales folks. We appreciate your time. >> Thank you so much Lisa. >> From McCalla. I'm Lisa Martin. You're watching this Cube conversation.

>>I've got Mada Mykola here with me, commerce architect at PepsiCo Mada. Welcome to the program, >>Lisa. >>So we're going to be talking about the solution that you implemented, um, that helped with the global supply chain. So let's talk though, first about your role commerce architect. Help me understand that a little bit better. >>So Frito, uh, PepsiCo is pretty big. It's a conglomerate of multiple product lines. So I worked for Frito-Lay, which is basically all the salty snacks. And then we have, uh, the Quaker products as well in our portfolio. So I oversee all the architecture for all the commercial IOT solutions, uh, in the CFNA portfolio. >>Got it all the commercial lines. So we all know the last 18 months major challenges with the global supply chain component shortages. We've seen a huge increase in the cost of raw materials, um, limited labor, but you guys actually started to tackle this challenge before the pandemic happened. So talk to me about the catalyst that PepsiCo, what you saw to modernize field service and supply chain application. >>Yeah, so we have a pretty old system that our field force, our frontline users are using. So we have a world-class supply chain system where we go into the stores and place orders and deliver products, the us, and then we penetrate, I think, more than 95% of the households with our products. So we need to have a robust supply chain as well as a good frontline sales application, to be able to manage the orders and be able to deliver the products. Right? So the system that we have is almost 20 year old system running on a video data technology. There've been trying to replace that for a while now. And finally, we started this, uh, early last year to completely replace the solution with a brand new iPhone based app. Uh, and then that gives our frontline the ability to go place orders, do deliveries to retail execution in the store, like checking checkout, build displays. There are so much functionality that our RSRs or Franklin users do in the stores and this app enables them to do much more efficient. >>And we're going to break into that, but you mentioned you had a 20 year old technology. Talk to me about some of the challenges that that likely presented to those frontline workers. >>Yeah. I mean, there are multiple challenges for one, we cannot enable new business models. So business wants to come up with new ideas for, um, to be able to implement in the field, but with our system being so old, it's so hard to implement anything on that one. And then even the physical device is not scaling. We had a lot of memory issues, so it's time for it to kind of retire. And also the technology we use the 3g technologies retiring pretty soon at the next year. So we were definitely need to move to a new solution. And this is one of the most things we have to do, but right away. So that's where we started the project and we are in pilot phase right now. >>What would have been some of those negative consequences? Had you not undertaken the effort? I imagine from a competitive perspective, knowing how much competition is out there, what would some of those challenges have been if this had persisted? >>Yeah. So one is the stability of the application, right? So, uh, the frontline users have to spend more time because the app is not stable, the current one. So that reduces the efficiency of our Salesforce. Right? And then on the other hand, we also not able to put new features or new business models enable new business models on top of the existing ones. So we are losing out on some of them because of our outdated system. So that's one thing we want to solve with the new one. >>So this is really critical to really evolve PepsiCo's business at, at its baseline. Right? >>That's true. Yeah. It is very critical application that we're building and this will enable us to do a lot more things in future. And we can come up with new ideas, including like virtual reality or connecting to multiple systems. There are so many new ideas that we want to enable once we have this in place. >>Awesome. Talk to me about why Couchbase, and then tell us more about, you started to talk a little bit about the solution, but let's go ahead and dig in and unpack the actual solution that you implemented. >>Yeah. So this is, eh, we call it an ERP and a mobile device because it has so much functionality as a company three. Totally. We have been, uh, over a hundred years, uh, in this business, right. We have so many, uh, optimized process, uh, that we have that kind of led to some digital in the system because we want to do in a particular way, because that's the best way to do it as part of our business process. So what we're trying to do here is take that business process and also provide an app that will enhance it and then connect to more, more systems. So that's what we're trying to do here. And then on top of that one, we will replace all the existing peripherals that we use with the new technology, like Bluetooth and also, so that, uh, the, they are much more faster, and it's a lot more productive for our frontline force. >>Sounds like a lot of sales folks are going to be a lot more productive. Talk to me about where Couchbase is as an integral component to this new system. >>Yeah. So one of the key requirements for this app is an offline mode. What that means is, uh, one of our Salesforce who go from our system, uh, from our DC to all the stores, should be able to run the whole day without any, uh, major disruption, even if they're not connected, let's say because when they go into big stores, typically there's no connection. There are metal boxes. So the cellular reception is not there, but most of our work that we do from our frontline is within the store. So it has to be a full offline where we have to have all the data within the device, and we should be able to place artists create inventory that records or adjust inventory, and then create invoices. All the majority of the things that we do are in the store and they should be able to do without, um, the kind of connection. So that's where we explored multiple options and kind of zeroed in on Couchbase where we bring all the data into Couchbase based database on the device, and then sync it when there is connection, but there's no connection. We still have all the data on the device and we can go do all of our duties in the stores without any issues, even if it is not connected. >>So the sales folks can be in the stores with their mobile device, doing all the transactions that they need to do with the stores, regardless of if there's connectivity. Talk to me about what happens when they get back to connectivity in that and the Couchbase database sync. >>Yeah. And, uh, the other big thing we want is instant connect. I mean, when there's connectivity, we want instant sync with the backend, right? If there's new data that comes, we'll need that in the device at the same time, if I place an order, I want to send it back immediately to our backend systems for that our fulfillment stacks for those. So that's very critical when we have a lot of cutoff times for our artists. So we need artists as soon as we've placed to be going to the backend systems. So what happens when it gets connected, as soon as the sales folks come out of the store, or when within the store, they got connectivity, these codebase technology that we are using using the sync gateway immediately syncs the data back and forth. Uh, if there is any new data that's available. So that is key for us in this particular app. >>So our transactions happening in, in real time or near real time. >>Yeah. So the data flow happens in real time when this kind of gritty, but when it is not connected still, it doesn't have any issue with the actual transactions with the artists that can go complete anything that they would >>Got it. Okay. So there's no impediment there. In fact, it's a productivity enhancer. It sounds like for all of those sales folks out on the frontline TA. So, so millions of documents go through the system, tens of billions of dollars. Talk to me about the volume of data and the actual monetary value. That's traversing the system. >>Yeah. It's huge. Again, this is kind of weak. It's the lifeline of the company. The seals are always the life of any company, right? So most of the goes through our system. And, um, we're talking anywhere between hundreds of thousands of dollars that flow through back and forth, uh, between, uh, between the device and the server. So there's a lot of master data that comes like products place from customers, all that information that comes from the backend to the device and all the orders, inventory, and everything that gets created on the device gets flown back to the subtler. So yeah, I mean, it's, it's a very complex system. And also from the volume perspective, it's huge. So we had to build a massive infrastructure on the backend to be able to handle all this. One of the key feature is again, we have this massive data that we need to sync to the devices, but each device should only get the portion of the data that they want because a particular Salesforce only goes to a small set of 20 stores, let's say. So the data that we seem to that device is only for those 20 stores. So that's the key here. So Couchbase allows us to do that. The codebase sync, where we can subset the data into different portions and only send the data that is relevant for a particular device. >>So then from a, from a latency perspective, it must be pretty low latency, pretty fast to be able to get this data back to the device and to the sales person that is in the middle of a transaction. >>Yes. Uh, I mean, it's pretty, the sink is very fast. The Cosby's sink, especially user's web sockets. And we do continuous replicators where if I complete an order, the next instant it's on the stairwell. So it's, it's we observed the speeds improve a lot. So the technology that we are using users are things for a long, long time compared to code based. And that's another productivity gain for our Salesforce. >>What were some of the differentials? You mentioned some of the technology requirements that PepsiCo had in rearchitecting, the infrastructure, but what were some of the key technology differentiators that really made Couchbase stand out as the obvious choice? >>Yeah, so we, when we started this project, we all know the sink is the key for this whole project, because we thought that data going back and forth, we cannot really build a robust, um, uh, offline app. So we looked at multiple, uh, options, other providers that are doing the sink. And we also looked at building our own sink. Uh, in-house using API APIs, but then we did lots of, uh, performance testing across all the, uh, options that we had at that time. And then Ottawa cost base came above. All of them are pretty handle it. So obviously we can coach base takes care of the sink, and then we can focus on our business process. So we can go build all the business process and not worry about how we build a single. And then that is itself a big effort. So that's what caught me is prior to seeing instant sync engine. And then we were able to focus more on our, uh, the app application, the frontline application, the sales application, >>And those business processes. Let's talk about some of the business outcomes. We've mentioned a few already in our conversation, increased in productivity. The sales forces increased in that as well, but I imagine there's a lot of benefits for the end-user customer in terms of being able to get the transactions completed faster. What are some of those positive business outcomes that PepsiCo is seeing as a result of implementing Couchbase? >>Yeah. So you hit on a couple of them when the sink times are definitely a big factor with that will directly give more time for the sales folks to go either go to most stores or even they go to the existing stores, they can do more, spend more time with the customer merchandising and making sure everything is correct. So that's one also the new app users, uh, connect with a lot of new peripherals that are not available on the previous platform. Um, also the, uh, our folks are very, uh, enthusiastic about using a new app, right? So it's like coming into the 21st century for them using such an old lab for a long time. So a lot of things that they see, they can see the images of the bags while ordering, which was not a feature earlier. Some of them are small, but they make a huge impact on our users. >>Um, so yeah, I mean, and then this is just a start that we are doing. And then once we are able to completely implement this one, we have a lot more going into, in future. I was just talking about, we can do virtual reality or show them how to sell using what filter do. We can show a display to a store manager saying, Hey, I want to put a display here. And this is how it looks. They can show it on the phone that Dan just explaining and showing some paper images. So there's a lot of possibilities, >>A lot of improvements to the customer experience. It sounds like, it sounds like adoption is quite high for your folks who are used to 20 year old technology, probably being very, uh, excited that they have a modern app. But talk to me a little bit about the appetite of the organization to continue modernizing the application infrastructure and presuming going from older technology to that 21st century, like you talked about. >>Yeah. So in other parts, we are already modernized some of these. So we have been on the journey for the last four or five years building multiple digital platforms. So one of the example I can give is when COVID hit, there's a lot of disruption for everybody, for the consumers. So they are not able to find the products in the stores, but people are afraid to go to the stores to even buy products. So we reacted very quickly and opened a consumer of a website called snacks or calm, which Pepsi never sold it to the directly. We always go through our stores, but the first time we open the consumer channel and base powered some of it for the backend purpose. So this is not a mobile app, it's just a desktop app, but we already have been on the district has mission journey even before we quickly turned into COVID for the snacks.com. >>And similarly, we are, you are doing this for our retail execution portion of it, um, using this product. So, and then we'll be continuing to do this going forward, or to enable a lot of functionality for, uh, I mean, for all of our sales, as well as, uh, supply chain and other systems, so that we can be more efficient. We can be more elastic saying if there is more demand, our backend should be able to handle all that, uh, which was not the case before extra. Now we built a state of the art backend system on cloud. So there's a lot of transmission, digital transmission going on within PepsiCo. And I'm really proud to be part of this project so that we took this to the next level. And then this is just a start. We can do a lot more, >>Right? This is just the beginning. That sounds like a great transformation for a history company that we all, everybody knows PepsiCo and all of its products. But it sounds like when the pandemic hit, you had the infrastructure in place to be able to pivot quickly to launch that direct to consumer, which of course consumers, patients has been quite thin in the last year and a half. Talk to me a little bit about the impact to the overall organization as a result of being able to, to get more direct with those consumers. >>Yeah. So till now, again, we are, the business model is we sell to the stores and then go to the customer. So we'd never get a direct, uh, sense of what consumer, uh, liking is. I mean, we get through some surveys and stuff, but we don't have a direct channel with the consumer, which this particular product enabled us next.com. So we know the consumer behavior, how they, um, buying patterns, browsing patterns, which ones they like and including with geography. And also we learned a lot from a consumer behavior point of view for the project. And then we kept on enhancing. So one new thing we introduced was called multipack where the consumers can come and make their own market practices. They can say, okay, I need this many of this particular product, this product per I can make that multipack. And we ship them the customized market back. >>And it was such a huge hit that we are not able to even fulfill them so much demand was there for that one. So we had to revamp and then get back. And now it's a huge thing on our snacks that complex. So all of this is possible because we had a digital platform underneath that supports this kind of innovation. So the new business models are just coming to life in within weeks or even few months. And that's what we will be trying to do with the new platform that could billing for this app as well, where we'll bring in a lot of new business models. We have >>Excellent, a lot of, uh, transformation. It sounds like at PepsiCo in the last couple of years, I'd love the customization, that personalization route that you're going. I think that's going to be a huge hit for consumers. And as you said, there's a lot of demand letter. Thank you for joining me today, talking about how you are modernizing the field service and supply chain application, the impact it's making for end users for your customers and for the sales folks. We appreciate your time. >>Thank you so much >>From out of McCullough. I'm Lisa Martin. You're watching this cube conversation.

>> Narrator: From theCUBE studios in Palo Alto and Boston, it's the theCUBE covering IBM Think. Brought to you by IBM. >> Hi everybody, this is Dave Valanti and welcome back to the IBM Think 2020 digital event experience. This is the afterglow, the after thoughts, the post halo effect. Mani Dasgupta is here. She's the Vice President of Brand and Product Marketing at IBM. Great to see you again, thanks for coming back on Mani. >> Thank you Dave, it's fantastic to be here after Think which has been super successful for us, so excited to have this chat. >> You know it's really nice, one of the silver linings of these digital events is you can actually have these kinds of conversations in an afterglow, so I want to get right into it. Mark Foster kind of set things up for the division and the service, he talked about a lot of customers. He talked about the cognitive enterprise, and he gave really three sort of arcs of his content discussion. One was the market making platforms, the second was intelligent work flows, and the third is the whole enterprise experience in humanity and he tied it in to the whole COVID-19 pandemic. I wonder if you could give us your thoughts, and maybe an example? >> Sure, absolutely, sure can. You know the cognitive enterprise is a framework that businesses can adapt as they go on forward with their business transformation journey. The market making platform is in simple terms, its how do you put yourself in the route for growth? Do you need to look for new customers, do you need to look for new markets? What's your competitive advantage? Build a platform, or create a platform which signifies competitive advantage for you. So that's the first piece of it. The second piece of it pertains to the operations of the company. How well are you run? How efficient are you? How effective are your processes? How have you been able to apply the latest and greatest in technologies? Edge, 5G, automation, artificial intelligence. How are you able to apply those technologies to make your processes work better for you? So that's the second big piece. And the third piece is keeping your customers at the core of whatever you do. So the experience of the customers, the updated and newer demands of the customers. How do you address that with the human at the center of it, right? The empathy that I was talking about when we spoke last, before and during Think. It's truly important especially in these times, every company is trying to figure out, in this scenario, how do they keep their business on the growth track? And the cognitive enterprise framework helps them on this journey. >> Was there an example that came out of Think that you can point to that is reflective of this? >> Absolutely, there were actually three great case studies that clients and colleagues who joined us during Think, we had the CEO of Yara, we had Shell and we had Frito Lay. A quick example is Frito Lay, and I bring them up because this is a brand that everybody recognizes, in fact they are now in 94% of all US households. And these are name brands like your chips, especially when we are all stuck at home during this pandemic they are a name that quite often comes to mind, Frito Lay. So a good example of what they are having to deal with. They haven't changed their transformation trajectory, they have sped it up. They have just become way more agile, teams that were in different locations are now all near shore. If you think about this scenario right now, everybody is working on Webex, everybody is getting distributed agile to work, so everybody, nobody is at a disadvantage because they are somewhere in India or they are somewhere in Mexico, or they are somewhere in the US, they are all together right now working together on the same digital platform. So actually everybody's near shore. So they have sped up their direct to consumer channel, in the past one month they have been able to quickly pivot and bring snacks.com to people, everybody across the US, that's a very good example of how you can apply the changes around you to your advantage, and make sure that this contributes to the growth and success of their business, and we had Frito join us live during Think, if you want to see it you can go live to our, now on our on demand platform and watch them. >> One of the things that Mark Foster mentioned in his remarks was that a lot of executives might have been thinking prior to COVID that they wanted to shake things up a little bit. But it's risky, you know they're kind of reticent to do that well, things have been shaken up. And now they've got you know the perfect reason to disrupt their own business. And organizations have been very tactical, focus on the customer, really trying to keep the lights on, managing cash, et cetera, but as we start to come out of this, they're beginning to think of the more midterm impacts, they're rethinking the ideal customer profile, and the value proposition in this new reality. So how should customers think about getting started on this journey of the cognitive enterprise if they haven't started already? >> You know it's, the good thing is the technology right now is available to us, even if people want to get started they can do it right now. One of the ways that we have been advising our clients to get started who haven't get started this journey, is to come together in a distributed agile framework, what we call the IBM Garage our Co-Creation Workshop, put the customer at the center of it and create an empathy map. Around what is the problem that we are trying to solve? What's the most important thing that that particular business is trying to solve? And for every business it may be a different answer, right? And so it's not prescriptive, its a place where you can come and lay out the cards on the table and figure out what's the right next step for your business, and then we can use the same model to unpack the problem into solvable components and apply technology to very quickly show results. The beauty of this is not just an MVP, this is actually solving real world problems, and it is doing it at global scale. That's the beauty of it and I think that's where we should start. >> You know a lot of these big events, the big physical events, of course we love them it's something theCUBE has been doing for 10 years, but the disappointing thing is oftentimes after the event everybody disappears, they go back to work and it's sort of forgotten. The great thing about these digital events is you can kind of continue the discussion, not unlike what we're doing now, but also you have these Think Summits, and you're going to be connecting the dots in the thread from Think all the way through until this thing ends and even beyond I would predict, that digital is here to stay, at least an event standpoint, and a hybrid, and other businesses. So give us the update on the Think Summits, how do we get more information, what are they all about? >> Absolutely, for more information is always available on our on demand platforms, so you can go onto IBM.com/think, but what you said Dave is so important. That this is not a one and done, we want to keep the conversations running, we want to keep engaging with everybody who has come last week to have an engaging discussion with us, we will continue this in June, in Europe, in different cities we have a number of Think Summits. This will be followed with other Think Summits across the globe. Now as IBM we feel we have a responsibility not just that we create content and thought leadership that is consumed by millions of people across the globe, we do it in a way that is global. So we want to make sure that you and I today are talking in English, that we are able to have our colleagues in China are able to have the same conversation in the language that they prefer, and so in Japan and so on and so forth, IBM being the truly global company that we are, we want to make sure that the conversations also have nuances that are impacting these countries in real time, in the situation that we are in, not all companies are in the same space in the curve, some are recovering, some are bouncing back, some are just getting into this scenario that's all around us. So the remedy and the routes that business will take, is also slightly different. So we want to make sure we are very customized, we want to make sure we are really very relevant to that audience. So follow us on the Think Summits across the globe, as the new dates are keeping on newer dates are getting announced on the Think platform, so that's ready to go. The one last thing I would also say Dave, is that at this time what's very important is that not all tech is created equal, and not all companies are created equal. What's the cost of bad advice and so I think it's very important to be mindful of who you engage with. And make sure that we are not taken advantage of in these kind of scenarios. Be very mindful of how how well your partner understands your business, how well your partner understands what could go wrong. And plan for it, and not just show but be there with your clients, with your customers throughout the journey, and take them back to the path of growth. >> Yeah that whole notion of business resilience and not only as a defensive move, but also something that you can lean into, really try to grow your business, there's a lot of learning going on, a lot of great content on the IBM Think Digital Experience site. Of course theCUBE.net. Mani, thanks so much for coming back on, and breaking down IBM Think, and giving us a forward look to the Think Summits. Great to have you. >> Absolutely my pleasure Dave, thank you. >> And thank you for watching everybody, this is Dave Valanti for theCUBE and we'll see you next time. (upbeat instrumental music)