 There we go recorded. Got it. Shall we roll now. Whenever you're ready. Sure, Andrea, would you like to do the introductions or would you like me. Please, that's the stage Tom. Okay. Beautiful. Well, welcome everybody to Thursday was a March 24 2022. This is the supply chain and trade finance special interest group. Session today will have Rajat joining us here. Representing Moby today. We'll give him a second here because he has a day job. We'll let him talk about it. Dex freight a little bit here. His day job, but he's also a big part of Moby. He's been involved with it for a while. I contacted him when I saw some stuff about Dex freight and thought that he might, it might be an interest to hear about that. And it turns out the Dex freight isn't using hyper ledger, but Moby is. And so that's why Rajat has been to share with us. This EV battery pack traceability pilot at Moby. So. We're recording this session here. As is normal with the case with hyper ledger events. All our welcome and any antitrust thoughts. We don't have those part of the charts, but you know, this is an open session here. So please don't share anything that's competitive in nature. Conclusion or any of that kind of stuff. Let's see anything else here. And I was wrong when I put in the hyper ledger of the supply chain sig. So, email or blog yesterday that this was the first, this is actually the second of our events. So, Rajat, thanks for being the second now. And we have some more cooked up here coming forward that we'll tell you about. And Eric, do you want to say anything about the blog and our wiki and stuff like that, how that's coming along? Just for everyone has a little flavor there. So we're working behind the scenes to merge the old supply chain and the old trade finance wiki pages. So that's under underway on that. You'll find all the old resources, all the old meetings that we need to transfer over and the new stuff moving forward for sure. We'll also share the mailing list for those who are not yet on our mailing list. We also have a discord channel where we pop in from time to time and we'll be sharing that link on the wiki page. So stay tuned. Work in progress, lots of stuff to do and should be over soon. Okay. Beautiful. So with that, I'm going to turn it over to you here for your wisdom and thoughts and insights. So can you tell us whether you'd like questions to wait or whether you'd like questions to come along the way? Either way is fine. I guess come along the ways is better. So that way we're fresh with those questions and answers. Beautiful, beautiful. Okay. It's all yours. Okay, great. I do have to sign off like five minutes prior because I need to have, I need to go to another talk. Okay, with y'all. Absolutely. All right, then. Well, thank you, Tom and Andrea and the, and the SIG for the opportunity to come and talk to you, come and talk to y'all. And forgive me for, for not having pretty. Good looking slide decks. So they're pretty boring at this point. So I'm going to try my best to, to, to make a good point of, of what we're trying to do. And hopefully. We all learn something out of. Out of the, out of the work we're doing. So I'm going to talk about the EV battery pack trace ability pilot that Moby is doing. And. Okay, there you go. So today's agenda is. I'm going to talk about the pilot objectives and scope. Well, the scope is repeated there. And some architecture and some tech primitives. So this is where hyper ledger fabric comes in. Some next steps and early scaling challenges. The pilot is in the very early stage. So we've identified some scaling challenges. But I'm pretty sure we'll, we'll learn more as the pilot. Continues. For over, over time this year. And hopefully next. So about myself. Dr. in transportation 2005 New Jersey. I used to work for Texas A&M University as a research scientist. For over 13 something years. Had a privilege of working with several. Federal state and US and foreign entities, foreign governments in various V2X projects, transportation projects. I also published a book about blockchain last year. I'm also co-founder of Dextrate, which is a blockchain based logistics company. I also work with Moby as working groups lead in that capacity. I coordinate all the working groups slash committees at Moby. They're differentiated by various use cases and verticals. So one of the working groups that I. Lead is called supply chain working group. So about Moby, it's a, it's a global consortium of. Mobility companies. Started in 2018. So we have members, about 100 or plus members. Including. Top top 10 OEMs for GM Honda. Toyota Industries. BMW with tier one suppliers like Denso Hitachi. Tochu. And service providers like center. And infrastructure provider like AWS and, and. A lot of good folks. That are in mobility space. Contributing to Moby's core. The objective of creating various standards. With regards to using blockchain and associated technologies and. Mobility verticals. So, like I said, one of the working groups or committees is a supply chain working group. It's called shared by BMW and Ford. The objective of the group is, is develop data specifications and reference architectures. And other standards that'll prescribe interfaces, data structures on chain off chain storage. Those primitives as well as. Some governance regarding the use of blockchain in various supply chain use cases and supply chain, as you all know, it's quite complex. And. Before I was part of the working group. I had, I had no knowledge of the nuances of automotive supply chain, which, which turned out to be very, very complex. So, so when, when the working group was talking about the, so the working group went through phases so, and that's typical of all the working groups at Moby. The first task is, is to develop standards data schemas reference implementations. And then the second phase is to then sort of battle test those standards. Because we want to we want to learn, you know, what's, you know, if the standards are good enough for field work and actual implementation so the pilots. The pilots are a good way to sort of battle test those standards. So the working group decided, you know, through a consensus process that will do a parse traceability, high value parse traceability and supply chain physical tracking trace. And the first thing we decided was why do we need parse traceability or why do the stakeholders need parse traceability. And, and it kind of that need has sort of evolved over time. That's what I felt part of being the working group. Initially it was more about, you know, how to reduce the recall cost of those high value parts. Those high value parts are also called safety parts, because those parts are the one that they're heavily scrutinized under if there's a massive recall. And regulatory bodies like it's a NSTSA and other European regulatory bodies, you know, those look closely on those safety parts. And then for the last, I would say, five years, the big OEMs have all started talking about their sustainability goals, you know, they want to be carbon neutral by 10 years and reduce carbon emissions by X percent. So they've all made those, made those announcements so that now I guess they have to live with it. And the third point is interesting, which is the sustainability really regulations that's, that's slowly coming out, and one of them is EU battery directive. And I strongly recommend everybody to, if you're in supply chain world, you know, take a look at that directive. It's a proposed directive. That was crafted in 2019-2020. It's, it's, it was supposed to be enacted earlier this year, but because of the situation going in Europe, most likely it'll be delayed. But the battery directive is, is a very ambitious goal of the EU to basically physically track and trace batteries from its first life to second life to all the way to life. The goal is to minimize, maximize its use and minimize, minimize the instance when you have to start to throw the batteries in a landfill because batteries have a lot of hazardous materials, right. So that's the third point. The fourth point is reducing losses due to concrete parts. This is known. This is a, this could be a big problem. This has been a big problem for OEM, especially now that the OEMs are slowly moving into 3D, 3D printing and they've seen their, their, their 3D printing plans and files being stolen and all that stuff. The point is, was also interesting to me, when one of the OEMs mentioned that, you know, a lot of the tier end suppliers, the folks, the businesses were on the supply, basic materials and basic parts are mostly small businesses, you know, spread around the globe and they always have problem coordinating or integrating with bigger suppliers and, and, and so they, the working group felt like, you know, we need to have these reference implementation standards for, for, to reduce the barriers to entry for these small businesses. And finally, the whole idea of blockchain is horizontal collaboration, right. So we started, can I ask a quick question back in the previous chart. How much an after, aftermarket parts come into the discussion, or was it all really more the manufacturing kind of the, the plant, the car. Mostly the, the first market, not so much an aftermarket, but they do recognize that the whole counterfeit part has the potential where the aftermarket devices may not follow the spec of the original design and they could be added to the, to the vehicles and they have an issue of now, you know, what do we do with the warranties, right. So it was discussed but it's mostly that the whole the counterfeit part scope is, I think it includes the aftermarket parts as well. Okay. Good. Thank you. So as we, as we thought about the whole, you know, parts track and trace. So we, the first thing we did was we defined the scope and then we spent about a couple of months working on the workflow the actual workflow of how parts move upstream and downstream from, to your tier one suppliers all the way to the OEM to the dealers and all the way to the end user. And at the same time, we're also thinking about, okay, so if you do a physical track and trace, if you're able to do it, then what's next, you know, what can you do with it. You can typically realize that the physical custody track and trace of physical custody of parts that is essentially a foundational layer. And once you have that then you can add, you know, things like emissions tracking and sustainability tracking, all of those good things, even recycling recollection is actually built on the first track and trace the physical custody of parts. As they move upstream and downstream. So, so we say we call this a multi layer construct is, you know, first let's do the foundation, which is the physical custody of parts and then, and then we can start adding other applications on top. The, the complexity comes from, from, you know, one of these kind of realities of the automotive supply chain, which is, there are several tier tier one can provide parts to several OEMs. A tier end can provide materials and, you know, basic parts to several tier ones. But as you go down like from OEM to the OEM level. You know, so they get they obviously receive, you know, different kinds of parts based on their specs. Maybe from the same tier, same tier same company. And because the, because their relationship, even though the relationship is one on one, they're, they're getting materials and some, you know, core parts from, from different parts, different, different tier end suppliers. So the, the, the complexity of, you know, data, data being tossed around between different layers of, of the supply chain can get quite, quite complex. So, so one of the things we did was, you know, what is the essential component of physical track and trace. And so the general agreement was the hard part was identity, right. And creating almost a digital twin of this parts flow, all the way from tier end to, you know, OEM to dealer is, is to be able to number one, assign identities to different parts, making sure those identities are recognizable by, you know, plus one minus one stakeholders or your partners. And be able to assign those identities to, you know, common, common, you know, common documentations like delivery notes, delivery notes, advance shipment notifications, bill of aidings, those kind of things. And one of the things that they mentioned was like, a lot of times, the identity identity that's assigned by a tier tier tier one may not be recognizable by OEM, and so on and so forth. So the first thing that we wanted to do in this, in this parts provenance is, is to bring everybody into a same structure of identity. And, and, as you may know, Moby created the vehicle identity. And then we're now working on the battery identity. And also, you know, universal device identities. So our challenge was to, okay, you can create a new identity structure but it still needs to be. It still needs to encapsulate the existing identity structures that's assigned by, which are mostly serial numbers that's assigned by, you know, manufacturers. Okay, so that was a challenge. And then, if you want to do, you know, the provenance of parts through blockchain or DLT or what have you, then those identity structure has to be has to be has to be the same. So, so this is where the, the, the very public credentials and DIDs and the W3C standards come in and we're using that I'll go through that in just a moment. But the EV battery was chosen as a part in the pilot, mainly because the EV batteries are getting a lot of attention. And as you know, most of the OEMs have, have, have declared that they're going to, you know, either phase out the ICE vehicles internal combustion engine vehicles. And we all know that the EV battery, the, the market share of the batteries growing everywhere. And because of that, and then because of the EU battery directive, the EV batteries are obviously getting a lot of attention. So we decided, Hey, what part do we choose. And so everybody said, let's choose EV battery. So EV battery is the top level of EV battery is even called EV battery pack, which is, which has a bunch of modules. So if you look at the left side, these little boxes are the individual modules, typically in an EV like Tesla. You have 16 modules per pack. And, and, and one pack has other components like battery management systems and circuits and all that. But usually they have like 16 modules and each module has a bunch of cells. I think there's like 3648 cells, something like that. So, then the question was okay, you know, you want to track pack and you want to track modules. Why do you want to track the modules. And then what happens is when you, when you look at the, if you have a problem with the, the battery pack or the battery system. Typically, what they would do is they would look at the modules. And then if any of the modules is at fault, they swap out the modules. They don't, they being the dealers or service providers, maintenance service providers don't go up to the cell level it's very difficult for them at this point. So we decided let's not go to the cell level let's stick to the pack level and the module level. Just to keep things simple. So if we've categorized the pilot in two objectives, the business objectives and the technical objectives. The business objectives for from, from, you know, the movie member point of view is, you know, we want to, they want, you know, they want to be, they want to be prided with what's what are the lessons learned what are the challenges what are the solutions what are related to, to scaling this type of physical track and trace. Obviously we also want to be able to show, you know, how what happens when somebody wants to query, you know, who has the battery pack who has the battery module for first life second life use cases at any given time. Right. An example of that is that makes the recalls a lot easier be able to estimate time resources required to move battery packs. And so this is with regards to greenhouse gas emissions during the transportation process as you'll know transportation also creates a significant greenhouse gas emissions and and also carbon footprint. So one of the problems with their with the pilots that they've done before is that it's very difficult for them to get those numbers from the transportation companies because transportation is kind of a completely separate workflow from from the typical transportation manufacturing process. So it's a very research oriented pilot. And, and so the other technical objectives was to obviously to map out current workflow of parts movement upstream and downstream. It was quite a challenging exercise. We also the pilot obviously has to maintain the current workflow, right that the poems and suppliers typically use. And in terms of technical objectives we wanted to test how various DLT blockchain primitives work, including verifiable credential the IDs, zero knowledge proves. And also kind of battle test will be and other standards that's available out there, including movies, the ID and the season dates are W3C standards. There's new one that's coming up. 2020. So yeah, we kind of outlined these two major objectives of the pilot. There's not back there. Were you trying to track just that when the battery pack kind of gets formed or are you also trying to track all the parts and sub assemblies before it gets formed. The point the scope is the, the, the battery packs are and the modules are sent from the tier one suppliers. Okay, manufacturers to the, to the, to the OEM and OEM, then basically puts those packs to the vehicle. Right. And then those vehicles are sent to the dealers. The battery pack. Okay, got it. Thank you. Any other questions out there for a shot. Before he goes on. Give it three beats. 123. For shot continue please thank you. Okay, so just to continue on the current scope if you battery module physical track trace upstream and downstream. If you wanted to limit the suppliers to tier one, obviously there's made a multiple tiers, color tier and suppliers, just to keep things simple. So in the process of physical movement of those parts or packs. The logistics process is, is we want to simplify it. So we just assume there's one logistics provider. We're taking up parts from, let's say a supplier and, and from supplier and delivering it to an OEM. Obviously that's, that's not always the case. If you're sending a part, you know, cross border or international, then you have multiple as providers and multiple modes involved. So basically for the, for the sake of the pilot, given the time and time and time and resource we want to keep it simple so we assume there's one was provided was taking care of all the information. We're not doing any integrations with any legacy systems at this point. That would be a significant cost. So the pilot. We're also not working on any governance with regards to the layer zero operation. I'll talk about the layer zero and just a moment. For example, you know, who can be part of the part of the track and trace, you know who runs the notes and those kind of things so we're not taking care of not dealing with that. There's a separate, there's going to be a separate issue on the governance of those notes. So the, the flow that we have in the current scope is you have a tier one supplier to the left. And it creates the battery battery pack creates what we call a battery birth certificate, which is, which is, which is based on our vehicle birth certificate. It's based on the, the verify the credential schema that birth certificate is then transferred to the OEM. Obviously tier one supplier hires a logistics provider, then the logistics provider, you know, picks of the shipment delivers to the OEM. There's a trip start and, and, and certificates that's, you know, provided to provided to the logistics provider, which, which says, which provides credentials as to, you know, when did they, when did they start a trip and when did they end the trip. And if they were able to, they have all the documentations necessary to verify if the right right pack was delivered or not, based on the communication to tier one OEM. So it basically follows, follows that ways up to downstream, all the way to the owner. And then we also doing sort of an ups kind of reverse flow where an example is the owner reports that the battery pack battery pack has some issues takes it to the dealer. And the dealer looks at the pack, and dealer says, I think, you know, five out of the 16 modules are not working. And in that case, the dealer sends the pack back to the OEM. And the OEM then reports it to the supplier and then supplier says, Okay, we're going to replace the five of the modules, or, you know, we're going to replace the whole thing. But so this is a very, very simple kind of happy path of the physical tracking trace in, in actuality, there's much more nuances to it. For example, in the case of logistics, you may have warehouses involved may have, you know, customs involved if you're, if you're sending the pack, you know, across the border, you may have multiple tracking companies involved, multiple forwarders involved. And also, if you're sending, if the OEM is sending, OEM receives the faulty packs, and then OEM says, Okay, we can't send it to the supplier and supplier says, Okay, we can't fix it, we'll have to replace it. What they'll do is they'll send those faulty packs or modules to a, either to a recycler or, or where they just kind of trash it. So they will send it to some other companies to, for that matter. So all these certificates are essentially verified credentials using W3C standards. Okay, so one thing we've done is we've, we've created all these structures. And as Jason files and GitHub so any member who wants to run their own, you know, pilot they can just borrow all the certificates. And the scheme as associated with that. Another question there. So I'm Mr. question today. How are you physically identifying the individual battery packs or is that that not really a scope are using RFID are you do a scan of barcodes. What do you do? So, the, right now that all the battery packs come with a serial number. Okay, that's either put in by the supplier or the OEM itself. So what we're working on is a battery identification number which, which would look very similar to the vehicle identification number that we're all familiar with that's 17 digit code that you see on the windshield and at the door. So we're working on that so that, that anybody can look at it and kind of decode some basic information about the battery. There's another initiative that global battery alliances is working on in response to EU directive is to create a battery passport. And that includes RFID or QR code. You use the QR code and it will tell you the full history of the battery back. Okay. Yeah. All right, so the major components in the pilot. The obviously we need to take care of the IDs, right, the vehicle ID, the battery ID and the battery pack ID that's associated with the vehicle ID and all of that. So we're, we're, we're using W3C for that. There's a, there's a infrastructure that Moby is is is building. It's been tested right now with with our OEM members. It's called integrated trust network. It's essentially basically a federated network of us. It's implemented in hyper ledger fabric and AWS. The zero infrastructures is is the one that keeps track of the dates. The third component is the use case specific minimum set of attributes so for the pilot we've defined the attributes for, you know, documents like advancement notifications, the bill of ladings, the purchase orders, because, because the OEMs and the suppliers they do verification if they received the right part or not. So we have, we have defined attributes for that. We're borrowing some attributes from schema.org so that we don't have to create new attributes. The attributes are created by our Moby standards. So the, the fourth one. So those three are components are kind of a main base components. And so as the pilot progresses, we're, we're going to work more on the framework to share information between the companies. And what are the, what are the legal constraints and practical constraints of sharing different information between different stakeholders. So that's that with the, you know, blockchain DLT underneath so all that, all that framework. We still need to work on it. And obviously, like I said before the governance of those notes and layer zero infrastructure. Um, let me see. All right, so this is a kind of a high level architecture and not too technical on this stuff we have a technical team development team working on it. So we have the, the, the bottom layer zero infrastructure is federated notes. We call it integrated trust network because Moby is using that network for other use cases as well. The pilots that we're doing. And there's a bunch of our members are already running the notes and somewhere in the face somewhere in the states of testing those notes. There's a middle layer which is sort of an orchestration layer that issues the verifiable credentials. We call an orchestration layer. That's is slowly being built. And on top is obviously the application layer which is the track trace. And so there's the legacy system which we're not touching at this point, but we're creating the digital twin or the notes that connects their legacy systems of that stakeholder. And there. So we're providing some basic functionality to those nodes. And that basic functionality is the, you know, creating your debts and, and registering those debts to the, to the, to the, to the layer zero. And depending on the use case then, then those stakeholders can, you know, add multiple functionalities to the, to the, to the note. So in for our pilots since we're not connecting with any legacy systems, the, the all the data will be obviously be kind of simulated data at this point. All right. So the digital twin the node, the one that highlighted in red. So if you, if we kind of zoom in into that, there are several components. I'm not good at explaining all these components. So the digital twin essentially note that individual members run have bunch of components in there. They're included data vault universal wallet. They're sharing, you know, authentications and AVS service for endpoints that connects to their legacy systems and also connects to other other notes in that network, and with the, with the layer zero infrastructure. Let's see. All right, so there's a bunch of questions in the chat box Tom you want to take over those. See like five. All right. There was one around presentation being available here so we'll be able to share that that was one of the questions. Were there others. Let me see here. And we'll put the recording up on YouTube also. So I think that's what I see for questions right now. Maybe I'm missing some. Okay. I think that's it for it now. Say it again. I think that were that those were all of the questions for now. Okay, thank you. Thank you. So this is my, almost last slide so the way the pilots are structured at this point we do a three month feature release. And that's starting in April. So we've done all the screen designs, music, all those good things. And the next step is now discussing the next steps in the pilot. So once you have. So the current scope, whether we expand the scope horizontally include more suppliers upstream, or whether we add depth to the current workflow. So that means adding, you know, warehousing, transporting models changes. So we're working with the committees actually discussing that as we speak. So the scaling challenges that we've already kind of identified is, you know, we're, we're gradually understanding the scaling challenges, when, when our stakeholders want to do this kind of physical track and trace. And one of the biggest challenges that we see is that integration with their existing systems. Because they're the ones that originate data about parts, right, so that the digital twin, or the notes that we have designed is that they need to, you know, synchronize with their legacy systems. And that, that adds a bit of a burden and cost to the stakeholders. It may not be a significant challenge, but it's still could be a challenge if, if, you know, we're talking about tier and suppliers or, you know, a lot of them are small businesses. And, you know, we obviously we still need to work on the governance of those notes, because federated network. There's a possibility of sub network being formed different, depending on the use cases. And at this point, we don't, we don't exactly know how the governments will happen. And, and finally, the, the legal side of all this, right, because they're all, you know, most of the audience are publicly traded companies so they have to be careful about the, you know, trade secrets. All of those good stuff so we're still learning all of that. And obviously those could be, you know, legal side could be a significant challenge that we haven't even, we haven't even dealt with. And that concludes my presentation. If you want to get to me is this different ways to do that scan the QR code, get to my LinkedIn, connect me and LinkedIn, or send me an email. My book is also available in various sources. And that's it Tom. Thank you very much. Appreciate it here. I see one question in the chat box here, all the nodes spin up over cloud or native hardware nodes. I think you mentioned AWS and maybe that's the answer to the question but I'll let you answer that and folks, please get your questions up whether you want to raise your hand or hold the style open it up here and right after Richard finishes you can ask your next question. Right now the notes that we've spun up is AWS but other members are spinning up in different environment. And put that sounds like some of those might be their own dedicated hardware notes. Okay, got it. Okay. Good. I have one question. And then we'll go to the floor here. If you spend thinking about tokenizing any of this information at all, or it was like, not not even worthwhile at this point in time to have that discussion. No, we have not discussed tokens at this point. Movies position is, they don't want to touch tokens. We're talking about cryptocurrency tokens right. So you're talking about writer you know or some sort of digital twin and NFT that represents a battery pack. Maybe it could be something like that. Yeah. You know tokens were the movies position is not to talk about tokens because they're, you know, the members are all publicly traded companies and they want to be careful, not to get associated with a nonprofit like movie issuing tokens. So that's one with regards to NFTs we're, we're just exploring NFTs for some other use cases, but but not on this one. So this one, we feel up to this point, the disembarkable credentials will will just be fine. Yeah, good, good. Okay. Who else out there for questions you have for a shot. Anybody else. I see one thank you there in the chat for your resort. Welcome. Okay. So, I guess for a shot you did such a great job of answering everyone's questions. There's no questions, but I was the only person that questions out there and additional other person. So you see Rajat's book there. Oh, did somebody say something. Hi, can we have the Arctic diagram, if it is possible and the conference page or the any format of your books or anywhere, how the entire architecture has been built, like anchor pair how it's designed and notes are how it designed and fabrics activation it's how it's getting authorized. So I just wanted very curious to see architecture diagram. Um, I think the architecture diagrams in the movie website. You'll have to ping me and send me an email so I can connect you to the right source and provide you with that information. I requested a friend request or the LinkedIn so that I can give you my email ID so that I'll go through all the stuff. So I'm, I'm preparing for hyper lecture fabric administration examination. So this would be very useful study case for me to get the past. Yeah, we have we have a tech tech stack team. We can get in touch with you with them and you can ask really something really sounds great. Thank you. Okay, any any further questions out there. Okay, well with that, Rajat has shared lots of ways to get a hold of him there. So that's good to email address is a QR code LinkedIn, etc out there, or you can buy his book. So that that's good with that Rajat thank you very much for sharing. What you guys are doing there with mobile be glad you're using hyper ledger fabric there and it sounds like you're planning all the identity work, which is working itself right. Yeah, exactly. It is the challenge. All the things so for the folks who asked, Rajat, if you will be able to share your presentation on our wiki, and then this this presentation will go up on YouTube so people can watch it. And we'll put something out there so that there's a link and then we'll get that to you also Rajat. Okay, great. Thank you. Thank you. Thank you guys. Thanks everybody for joining. Enjoy. We'll look for additional sessions here and look for our wiki getting up and running here shortly. So thanks everybody enjoy the rest of the day, and we'll see you soon. Thank you. Okay, bye everybody.