 Welcome to the grid zero dot to release party part of the one of the major hyper ledger projects dedicated to supply chain solutions built on a distributed ledger. My name is Jack Pichniewski. I'm part of the grid team leading our community development and for the next 42 minutes. I and other members of the grid team will be hosting you on this release party. Very simple agenda for the next 42 minutes. Once I'm done with this little intro, I will turn it over to David Checkie, one of the key sponsors and thought leaders for the grid project. He's going to briefly explain the vision and the philosophy behind the overall digital supply chain platform and the hyper ledger grid project specifically. Once he's done with that, we're going to give the lion share of the time for this 40 minute session to Shannon T lander and myself and we're going to be doing a demo of the features that we've released as part of grid zero dot to. So right before I turn it over to David Checkie. I just want to note as a reminder that this is a public meeting by which I mean it is not affiliated with any specific company or business so we will not be discussing business interests during this session. This session is focused on the hyper ledger grid project and open source project for building integrated supply chain solutions on a distributed ledger that will be the focus of our time today. We're really glad that you all have taken some time out of your days to join. And with that, David Checkie the floor is yours. Jack, great, great kickoff and awesome music selections to ease us into what is truly a great milestone for the team and community, working on grid, couldn't be happier to be here to talk to this entire audience about where we're at with grid zero dot to release and to get into a demo. Let's just talk briefly I know what Jack even said brief on the slide here I will say I'm like personally I'm very excited about what we're doing with grid and I can talk at length about it and I will do my best to keep it brief again I'm Dave Checkie. I really try to guide the vision and strategy for grid as a product and evolution but that is a community effort and it is we're going to talk about how it's open open source, open governance and open standards as we get into this a little bit. I think Jack is driving here I'm going to have him go ahead and run on advanced right so just to set the stage, a little bit, really seeking to integrate our supply chains in digital ways. Looking at technology as an enabler to establish more effective supply chain connectivity is something that many, many organizations are doing, and many software products are seeking to to help enable this is a vision that I think is widely recognized and has been for some time as super opportunistic. With hyper ledger grid we're really seeking to do that in deliberate ways, taking advantage of modern technology and modern, modern platforms. We'll go ahead to the next next slide is well I want to set the stage a little bit more that this is a hyper ledger project. For those of you not familiar with hyper ledger hyper ledger is a Linux foundation. Umbrella project that is a great home, both in this picture metaphorically but also as a community for enterprise centric and or just general blockchain or distributed ledger based solutions. Hyper ledger grid you can see in this picture is aligned with a domain domain specific capabilities in particular around enabling supply chain integration in this in this family. So a little bit more background on grid then on the next slide here that's setting the stage as part of hyper ledger in the hyper ledger foundation so really what is grid grid is a platform for building supply chain solutions. Many of us talk a lot about the value of common process data and technology aligning those types of anchoring values across supply chains can drive meaningful efficiencies value and business outcomes. Different trading partners working with different data or working in different ways with different processes or using different types of technologies are the reality of our supply chains every day. And they create friction and unnecessary effort and costs. Doing things like reconciling invoices or or keeping aligned data about the products that we are exchanging in a supply chain. Are just exact common examples of the types of custom integration that we put up with in our in our supply chains in order to just operate and execute internally in many organizations we've sought to optimize, but we don't talk a lot about how to optimize process data and technology across our industries. Hyper ledger grid seeks to provide a platform and a framework for implementing common process data technology solutions across supply chains. We've anchored hyper ledger grid to existing industry standards. So we're not reinventing process data and technology. We are we are evolving and we are implementing in new ways. So as example of that is what we're seeing today with zero dot two's release is about establishing some common core data concepts in particular product data. Product data has a very well managed and governed set of standards in particular with GS one. GS one and G 10 and serializable G 10's and other dimensions of product data exists in our industries and and are obvious ways that we could start to seek alignment for collaboratively sharing and managing those important data assets. Other examples include GS one standards like GLN how we define locations in our supply chains really building out these core concepts location product customer kind of the essence of most business transactions. So we anchor those things to industry standards. In addition hyper ledger grid of course being a hyper ledger provides open source flexibility. This is not a a vendor solution. This is an open source project that is it is driven by the community. The team that's here has worked across organizations to deliver zero dot two and has been a great collaborative community effort and we welcome other contributions be they be they subject matter expertise ideas or technical contributions as well. Fundamentally we just we see grid as open standards open governance open source implementations of common process data and technology. It's a really really powerful set of capabilities. All right let's talk about the roadmap quickly and then we'll get into the demo. So where we at our short term focus is really anchored on like I talked about those big nouns pricing. I'm sorry pricing data location data product data some core workflow capabilities and we're already building purchasing and purchase order capabilities. You can see in that first bullet on the left side in the core that we're working that we just released zero dot two. That's why we're here in July and that we are already underway on zero dot three focusing on purchasing. Looking out you can imagine where we're going with the roadmap but we also spelled more of it out here things about thinking about quality specification. How do we collaborate more effectively on our product specifications in a supply chain. How do we resolve disputes more effectively and efficiently across parties. How do we handle invoicing and payment or evolve into more supplier managed purchasing or customer driven forecasting solutions getting into product catalogs and bill of lading. These are things that we in a supply chain collaborate on all the time today. We just think there are more effective digital ways to do this really driving a virtually vertically integrated orientation. Longer term features like integrated forecasting and planning really digging deeper into traceability and product journey is are all things that we think and talk a lot about. We're really tying the features to what we see users of this environment getting value out of. It's not necessarily purely aspirational. It's practical in the features that we're building. So again today we're here to celebrate to learn more and to talk about the grid zero dot two release and with that in particular about how we're managing product. Let's get to the demo. Right. Thank you. Thank you. Thank you. Are you able to hear me testing. Yes, just yes. Thank you very much. Thank you very much. All right. So for this next section which is going to take the rest of the time. Shannon T lander is joining me to do this demo Shannon. Are you able to share your screen. Yes, I certainly can. Thank you. Folks Shannon is also a key member of our team engineer extraordinaire manages project as well. Thank you Shannon I can see your screen. If if you can see Shannon screen please either say yes in the chat window thumbs up emoji you know whatever whatever your speed is. All right I'm getting some yeses getting some thumbs up cool we're going to go. So what are you looking at. We thought the best and most effective way to demo the grid zero dot two features was actually to simulate you know how they might work in concert for you know a real use case. And so the way we're going to play this out is you've got two organizations alpha and beta. Shannon is playing the part of alpha alpha is the orange box in the top right that will represent where alpha is interacting on grid and making commands. Alpha is a supplier. Alpha supplies many different types of products including absolutely delicious steaks with lots of marbling to many different customers. One of those customers is beta and I will be playing the beta organization. You can see beta in the white box in the bottom right and I'm a customer who I buy delicious steaks and many other things from alpha and I also buy lots of products from lots of other suppliers. So you know why are alpha and I and I talking here about grid well you know some of the challenges that I as a as a customer with many different suppliers have had have included. First of all very disparate experiences in having to log into many different supplier portals to interact and engage with those suppliers up to an including multiple different portals for a single supplier. In addition to that it's not just you know how we interact from a portal perspective but also when it actually comes to the information that we need to exchange to do business. It comes in many different forms many different manners and that's proved a challenge as well for me as a customer when it comes to reconciling all these different products that I'm buying across all these suppliers. And so in this simulation Shannon is the alpha organization is going to guide me beta through how we can to start with level set on the products that we share between each other using grid and specifically the zero dot two features. So then to help all of us here with seeing that come to life you'll see in the top left is kind of Archie cheat for the different commands and technical steps that will be running through. If you are someone who likes to see well what's the actual you know command line or code that we're running through it's all there for you to look at as we're going. And then in the bottom left are the specific features that we're going to be demoing in order so that as we're going through this you can track where we are in our journey. Our ultimate goal is that I as beta can see the products that I'm buying from alpha and they're able to supply the products and I'm able to make changes to those products to reflect how I want them to look. So with that we're going to get started. The first thing that alpha and beta need to do in order to transact on the grid distributed ledger is set up something called a splinter circuit Shannon. Yeah, so I am going to propose as the alpha organization that we create a splinter circuit and so what this is going to do is this is going to allow our organizations to privately communicate on the splinter network. And if in the future we want to add more trade partners. We can bring them into this splinter network and create different circuits with those people or with those organizations but this circuit that we're creating is just private between our two organizations. So first off I as the alpha organization, I'm going to propose that we create a splinter circuit. And so now it is up to the beta organization, they can see that circuit that I've just proposed for them. And if we go into the alpha organization, we should also be able to see that same circuit proposal that was submitted. And so now, as the alpha organization jack would you like to accept my circuit proposal. As the beta organization, I totally accept your proposal for a circuit, let's do business. Cool. All right, so now we should be able to see that circuit that we just created from both of our organizations. And so now, now that we have a grid circuit running, we will be able to perform grid transactions. Super great. So what types of transactions are we able to perform on the circuit that we have. Yeah, so we can check that out by looking at the preloaded smart contracts that grid offers. So I'm just going to quickly go into my splinter service CLI and I'm going to specify the circuit that my alpha organization is running just to tell it exactly which circuit I'm on. So now I can list all of the contracts that are available on that circuit that we just created so you can see that grid service ID is being used. And so we can see these are all of the smart contracts that are loaded onto our circuit. And so we can perform transactions that are defined by these smart contracts. Super great. So if I'm reading this correctly, the smart contracts on our private circuit between alpha and beta include location data. We'll get to pike later. We can do purchase orders. We can exchange product and schema information. Am I am I reading that correctly Shannon. Yeah, exactly. That's exactly right. So the schema smart contract. It enables us to define reusable and kind of standard product properties that we are transacting within grid. And then product enables us to share that GS one compatible product data in grid based on the GS one compatible schemas that we create. And then grid location offers an ability to share location master data between all the trade partners purchase order as you would assume has purchase order specific functionality and then grid pike. The final one is allows for permissioning across grid so you can allow certain agents and organizations to do specific tasks. Super great. Yeah. And if I just so I understand before we move on to milestone three. As our relationship is alpha and beta organizations evolve. We could add additional smart contracts to this circuit and that would be independent of any other circuits we have either of us with other organizations. Is that correct. Yes, that's exactly right. So grid zero dot to just allows these initial smart contracts to be loaded on to any grid circuit, but any changes that we want to make or additional smart contracts that we want to add to the circuit can definitely be added in the future. Okay, so now that we've created the circuit and we've seen our smart contracts. We have two additional pieces of setup to do before we start transacting on product. Right. Yes. So now that we have our splinter circuit set up between our organizations. We are going to make an organization. A grid representation of our organization so we're going to create a grid pike organization to represent both the alpha organization and the beta organization from our separate nodes here. So I'm going to go ahead and once again notify the my grid instance what circuit we are using. And so this tells it where to create that organization. And so I will create my alpha org. And go into the data is terminal and also create the data organization. Now after I create both of these organizations. We are able to view those organizations from both of these nodes, because we created these organizations on the same circuit. So if I call grid organization list I should be able to see both the alpha and the beta organization. And then, like I said before this is viewable from both nodes so both nodes can see the organizations that are created in the circuit. Super great super great so you just showed us also that from alpha and betas point of view in these two different command lines that we've got here orange and white. We're going to name a state of the data. Exactly. Right on, right on. So now that we've got these organizations there's one more step if I remember correctly before we start transacting. Yes. So now that we have our grid organization setup. We need to set the permission so that we can actually perform some grid transactions. So what I'm going to do so as the alpha organization, since I'm the one creating the products, I'm going to create a role called product owner. And so this will give me the ability to create schemas and products and delete them and update them. Basically, pretty inclusive permissions for dealing with products within grid. So now I've created that role for my. I've created that role for my organization. We can see now that the product owner role is added for my organization. So now I'm going to assign that role that I just created product owner to my agent. And so my agent is tied to my public key that I have so you'll see that it's pulling in my alpha agents, public key that I have stored. And now this agent is able to perform all of the transactions that are protected by these permissions. So specific schema permissions like can create can update. And then certain product permissions like can create can update and can delete product. And I think that important takeaway here too is that with these pike roles and these pike organizations, we can define all sorts of different relationships between participants on a circuit. In this particular case, right alpha being the supplier absolutely needs the capability to create products upload data about products and perhaps it wouldn't make as much sense in this particular relationship for beta. To have the ability to create products given that they're buying them, but they're not necessarily creating them. However, right in different relationships with different organizations. We can get very granular and specific in honoring the many different and diverse complex relationships between participants in a supply chain. And now that we've got you know all the all the infrastructure in our relationship setup within the grid ecosystem, like, we're here to we're here to look at some products right Shannon, can you create a product that you sell to me. Yeah, of course so I'm going to first create the schema for my GS one product. And so this basically just tells grid the kind of the format of this product that it's expecting. So it validates it. It validates the product that I create based on that schema that I just submitted. And as you can see, this is a GS one product that I'm creating. And so now I can go ahead and run that submission. And if I go ahead and list the products, we should be able to see that product that I just created. And once again, if we go over to the beta organization, you should also be able to see a product that I just created Jack. I would love to see it. Let's see it in the command line and then is there another way I can look at it to. Yes, of course there is. So we have a little UI for our product management and so I'm just signed in as an alpha agent. So what this allows us to do is see all of the products that I have access to across all of the different circuits that I am also a part of. And so I believe if I read. All right, and so we can see that that is the circuit that I created just a bit ago. And so if I go ahead and switch over to that circuit. We can see my test regulated product name product that I just created for you Jack is that is that what you expected. I mean, I definitely am glad to see that there's a product there. I will say that test regulated product name is not what what beta calls what we buy from alpha, you know we call it steak. Is there a way that can we update this so that it looks like what I'm buying from you. Yeah, so I think if you want to make those updates I as the alpha organization and go I'm going to go ahead and give you the permission to run that transaction yourself to make the updates to the product okay. I like that. Yeah, I can just do it myself that sounds great. Exactly. So I'm going to create an a role called beta product owner. Within my alpha organization. And so we can see that this role only has the can update product permission. So that means that an agent with this permission would not be able to create or delete a product they would not be able to create a product. And so now that I have created that role within the alpha organization, the beta organization can update the beta agent with that role. And so now, I believe you should be able to update that product Jack. I'm ready. I'm ready. All right. So we're uploading some fresh XML here. Let's see if that actually caused. All right, I think that was just a little bit of an error from the response, but I think that we should be able to see our stake. So here is the updated product. Jack. I'm looking. Ah, yeah, that's right. That's what that's what I buy that makes a lot of sense. All right. I think we just got a little bit of an invalid response there from the splinter Damon it looks like but the transaction went through and I can tell that because I just looked at my logs. And I can see that the grid Damon inserted one product which means that product was in fact updated. Just a little issue there with the response but there you go you see that you now have a specified what exactly this product is and the image. Right on. So, folks, that was that was the whole demo to recap real quick, we just showed. We had six different features within grid zero dot to we created that splinter circuit. We looked at the smart contracts that we had available within it. We set up our organizations within that circuit and defined what each of us was going to be able to do to reflect our relationship as alpha and beta. And then the product whose data aligned with open and industry standards that were enforced on entry into the system. And then we gave the customer in this case the ability to update the data around that product to better reflect what was meaningful information for the customer. The takeaways that I want to add from this demo for y'all to think about one. Even with the capabilities and grid zero dot to it's zero dot to it's early days right we have a long journey ahead of us as you as you saw with the roadmap but there's already a lot of power here to honor and represent the complex and individual relationships of participants throughout the supply chain from all the way to consumer facing whether retail or what have you. Second of all, what we did here with creating and updating some product data. Imagine extending that to other activities within the supply chain, take purchase order for an example. What if I as the bait organization want to delegate to my suppliers to log purchase orders on my behalf to cut out costs and complexity and how I do business with them. That's possible with these feature sets that you saw here. Third, the way that you saw the technology actually working right most of it was in the command line. We also very briefly demoed a simple user interface for grid. What I want to emphasize is that the way that we're building this platform. It is open and flexible for multiple ways for organizations to use and participate in this ecosystem. What do I mean by that. Well, the command line demonstration that we were showing, you know, you don't need a user interface if you're engaged in fully automated or autonomous transactions between businesses or organizations. We hypothesize that there's many cases where the grid ecosystem could be used to actually automate portions of relationships between supply chain participants. And in that case, you don't need a user interface. In circumstances where you do, like we demoed, we do have a simple one that a makes it easy for, you know, a supply chain planner or what have you right to navigate not just from one specific relationship of a supplier but actually from all of the different circuits that might be active in an organization. And also to within each of those circuits see what are all the different smart contracts things that I can do. What is the state of my relationship with this other person in the supply chain. Third, we aren't limited, excuse me, to that specific user interface as checkie noted in the chat. There are many circumstances and we imagine that many of the early adopters especially will be more interested in actually integrating the grid distributed ledger with existing interfaces that they have through ERP systems and other data management systems that are already being used in their organization. And that's absolutely possible as well. So, you know, to put it very simply, right, the grid distributed ledger can meet organizations where they are. With that, that's all we had to demo. We have 10 minutes left here in this release party. And we're going to open it up for if anyone has questions or comments, we have multiple members of the grid project team here to take your questions. There is no such thing as a dumb question wherever you're coming, whatever walk of life, we're happy to respond. If you want to unmute yourself and raise a question, go for it. If you want to type it in the chat window, I will look at that and moderate those as well. The floor is open. Thank you, Jack. Another here awesome demo. If somebody want to onboard on the technical side of contributing to this grid. What is the scripting language the person should know or what technical details the person should know to contribute? Yeah, it's a great question. And I know the like the, I think the whole engineering team from the community is probably on the call. Like there's a couple ways to just get involved quickly and hyper ledger has public chat rooms, the rocket chat based rooms that are a great way to reach out and learn more about specifically about the technology. Grid itself is written primarily in Rust. If you're looking to do core code contributions. A lot of it is the smart contracts are written in Rust. But there is also plenty of other things that can be engineered around grid, in particular the integration layer and some other things that would benefit from other types of skill sets as well. So again, like reaching out and engaging with the engineering community, the team that's building the code side of grid. Through that rocket chat channel is a great way to start. Thank you. Yeah. It's a really cool demo that showcases this distributed. Collaborative management of product data. As I talked about in the beginning. That same pattern of collaborating and working together. And transacting really submitting transactions updating a product, but that same transaction could be things like. You know, issuing a purchase order or collaborating on a dispute or. You know, even other more transformative things. We can imagine shared views of inventory shared views of plans and forecasts and collaborating and really more effective digital ways across supply chains. Then turning some of that into. Yeah, go ahead. Sorry. Sorry to interrupt you, David, but we do have a question in the chat. I'll read it out. It's coming from Riju. How does the grid integrate with existing ERP and master data management systems in, for example, the cargo ecosystem with regards to purchase orders in the RP's and product master data and product syndication tools. Yeah, great question. Great offers a, a set of event driven capabilities. So when things change in grid, it can publish events so that organizations that are running grid can capture those events in like a pub sub type way for example. And distribute them. Great is also like, of course, fully API enabled. And there's a lot of different ways to integrate to and from that. Lastly, we are working on an integration framework called griddle that will further ease enterprise integration scenarios between. The business transactions and processes that are running on grid and the back office systems that businesses run today. So a lot of capabilities, again, grounded in very practical implications for running these types of distributed solutions in a modern enterprise. Next question is coming from Eric, who asks, what would you say is the main difference is with fabric, another hyper ledger project, for example, which is already used in supply chain applications. Yeah, I want to talk about like why what grid is like what we see is great about grid. Comparing and contrasting with other solutions. Maybe a different conversation. I'd point out that grid is a open source implementation of supply chain capabilities. I'll clarify that fabric for those on the phone that don't know fabric is a distributed ledger. On this demo, we used a distributed application platform named splinter grid itself is a like more of a business application. Not, not just a infrastructure thing like splinter or fabric is grid is a business application that provides supply chain capabilities in open ways based on open standards, open governance, community driven and free and open source principles. And, you know, that stands in contrast to an entire industry full of vendor driven solutions that are commercially licensed and so on and so forth. So we really think it's important when we're building grid that it maintains that open collaborative community driven orientation. And this is Burnmore had a mall. I have a good opportunity to get a good chance to work with David and Jack. And I would just add on the grid on the first question on the earlier question from from you on the integration with existing ERPs. This is true for cargo. This is true for other and other companies as well. The key place to think of where the of where splinter of where grid lives is between companies. And so the opportunity to connect these the the in house back in systems inside a distributor or producer and and a customer is to is to remember that this grid is a form of glue. It's a form of interaction. It's a form of achieving agreement through processes between these companies. That's really the key between these companies is is the application where we see the most use. And also and that's just to build on what they were saying. And also on the question of being open open source what this means in practical terms who care you know who who what does this mean in practical terms. This means that when two partners are working together on one of those partners can turn and say to all of their other suppliers. Here's a great piece of software. There's no one charging you at the door. Find your best party to work with implementing this including your own developers and you can also be working with us. That's really the scalability the ability to to provide our sector away to drive forward is incredibly valuable and incredibly exciting to see. So thanks for thanks for let me jump in there guys. Right on right on. And with that, I think we're going to conclude the release party here. I want to thank you all for taking time out of your busy days to attend to get a little taste little show not tell about where grid is in its journey with zero dot to again if you'd like to learn more. I'm pasting into the chat window the hyper ledger grid website which includes the detailed roadmap and feature releases for zero dot one zero dot two and what's coming in zero dot three. It also includes a glossary of terms for those of you who are maybe newer to this space whether it's to how do supply chains work how does it distributed ledger work. And finally it has a links to our community spaces we have a rocket chat with direct access to the main project team in case you want to ask any questions about how the platform is built. And that's also the best way to to ask any other questions related to you know how do you want like learning more about actually using or testing out the platform within your space organization. So with that, again, thank you everyone. Have a great rest of your day. Be well be safe. Take care of yourself and those around you. Thank you.