 Great. So, we can chat amongst ourselves here looks like we still got a few people coming in. And then for those of you listed on the recording you'll want to go forward a minute or two. We start. I don't know if Patrick you want to put it in a slideshow mode. Now. Yes, I thought it was. I'm seeing all the different charts. I'm not seeing just one. Are you seeing it now. Not yet. I'll stop sharing and then I'll reshare it. Okay. It's still in. Okay. We'll figure it out real quick. We will. There's always something. There's always something. There we go. That looks good. Okay. Cool. It is full screen. Beautiful blue background. Okay. Why don't we, why don't we get rolling here since it's a four after the hour here. So thanks everybody for joining either today live. Thursday or on the recording here. This is something at the end of the year. We're glad to have the folks from a beta. I just wanted to just say one thing. I just wanted to thank you guys for joining. You're joining us here in the transport alliance. Joining us to share their thoughts and. And what their plans are for 2021. Is a key player in standards. They also provide a lot of thought leadership on the supply chain world. So that's why we asked them to come on and share. A little bit of what again, what their thoughts are. What their plans are. speaking with us. Patrick is the president of BIDA, so he's involved with lots of different things. And Patrick and Ben, I'll let you also add on anything else that you'd like to introduce your introduction. And Ben, I know Ben from the shipment working group, Ben has been the massive leader. He's really kept us all rock and roll on here in 2020. And I found out that Ben's also doing a lot more work with BIDA. So between them, they can answer a lot of questions as well as provide a lot of insight as to what's going on with blockchain transport alliance and standard specifically, ask them to focus on. So with that, Patrick, I'll turn it over to you. And we can get rock and roll in. Yeah, awesome. Thanks so much for having me, Tom. I'm sorry, Marco wasn't going to be able to join us today. But I do see a number of familiar names, if not faces across the participants list. This is the second time I've been privileged enough to be invited to present to the hyperledger supply chain special interest groups. So thank you guys so much for having me back. We're going to dive into some more of the technical details this time around. And as Tom said, I'm excited to invite Ben to talk through some of those specifics. So just going to make sure you guys can still see my screen. We can see your screen. Perfect. Well, then I'm going to kick things off. At least I can see your screen. How's there you go. And so, like my previous presentation, I still try to frame all of this up around the digitization of freight and transportation. And so, as everyone knows, there's probably never been a time where supply chain has been more relevant than 2020. It's really come home to roost how interconnected the world has become and how dependent we are on the orchestration of lots of stakeholders to provide for everything from essentials like toilet paper, all the way to the the massive undertaking around the COVID-19 vaccine distribution plans, which are coming together really swiftly. And so we're really excited about the work we're doing a bit of because it's taking all of these legacy and analog processes and basically allowing for really high fidelity data elements to provide for these transformational business model shifts, really allowing for that multi-party collaborative arrangements that are that are driving the unlocking of sometimes hidden or obscured value opportunities. So blockchain has a lot of things to a lot of different people, but I think that's really the important part. It's around that multi-party collaborative arrangements and how that's unlocking new opportunities. So as I said, there's kind of two dirty dewards digitization and disruption. And as we move from these analog and legacy processes, we think that there's going to be industry-wide benefits. But that also is going to shake up incumbent stakeholders. And I don't think that it's going to be a destruction of the middlemen that was kind of the common thread around how blockchain technology or DLT more broadly was going to impact different stakeholders when the technology really started spinning up. I do think that it's going to bring about new value propositions in shifting of stakeholders' roles. So that's that being said, you know, Bitta came together in the summer of 2017, really kicked off its standards efforts in 2018 as a member driven community focused on education evangelism and working towards open source and royalty free data standards that we think are going to power this blockchain enabled ecosystem, particularly around supply chain and transportation business processes. So the Bitta community is far and wide. Since its inception, you know, we've had well over 2000 companies from around the globe submit inquiries around membership. Actual actual members and contributors to the standards development work have ranged from small academics and researchers all the way up to the world's biggest technology providers and actual physical asset owners, the transportation providers that actually move the atoms and not just bits. So it's really exciting to bring together such a diverse community, representing every transport mode in stakeholders from around the globe to collaboratively build out these solutions that we see coming much faster than I think everybody really realized they'd be be here. So like I said, that has kind of got two sides of the community. We've got kind of the community that's focused on evangelism and networking and education and then the meat of the situation is really around the production of these open source and royalty free data standards. And you know, we do this as a community, focused on inclusion and transparency to build that trust in our work products that we think will allow it to really be globally adopted. So all of the work around the standards committee is governed by one of two technical committees. To date, all of the work has been governed by the data formats technical committee that reports up to the board, the board of directors which ratifies and publishes out all of the specifications under an Apache 2.0 open source license structure. This new implementation technical committee, I'm really excited about it's going to for the first time push us into trying to address the really hard questions about, you know, what data goes on chain? What are the right best practices around reference architecture? And I think we've set this up in a really exciting way that's going to maintain the technology agnostic stance that bit is always really strived for. So I'm excited about where that's going. And that's going to be the real exciting work in 2021. That's going to allow us to leverage the power of our community to flesh out use cases and see the use of these data elements that have been produced to date in action, really driving time to value in allowing for that orchestration of identities in supply chain information for different types of stakeholders, whether those are the end users, consumers or asset providers that are actually allowing for the movement of the goods or different service providers, whether those are financial institutions, insurers, or regulatory bodies like customs agencies, DHS, DBP, etc. So I'm excited about where it's going. Everybody wants standards to happen. You can really only move at the pace of the community. So I'm really excited about what the groundwork we've laid over the past two years that's going to see us move into this next chapter. So the working groups that have been building out specifications include tracking documentation, location, party, shipment, and all of that kind of works towards these work products around a bill elating. We also have a standards review working group that helps us figure out what other standards are out there that we need to make sure that we're aware of and help thrive collaborative conversations with leading standards bodies. We don't want to boil the ocean. We know this isn't something that we can do independently. Collaboration is absolutely essential to drive this work, particularly because it's global in nature and is responsible for multi transport mode work. The handoff between different types of stakeholders I think is really becoming apparent as the consumerization visibility technology has gotten down to our iPhones. Everybody wants to have the same type of visibility that we now have through Uber or Lyft delivering our late night snack that we want around an ocean container or a rail car or a parcel that now has a sensor inside of it. So we're really excited about where it's going. We've outlined a number of work groups that we are planning to either spin up shortly or are working on the chartering of them. One of the ones I'm really excited around is this purchase order for the Consonant. I've had some really exciting conversations with outside organizations like the International Chamber of Commerce around the need for this and I think that it's really going to help capture those genesis data blocks that help waterfall all of our other data elements providing for the answers that we're looking for in these solutions. So this is kind of an early model around how we were looking at the different classes of data, how they would come together to address that question, where is my stuff? You know the foundational supply chain visibility questions and that's what we really honed in on in 2018 as we spun up these work groups to address traditional track and trace visibility functions. And this work has spurred us down a number of different developments and it's definitely been an iterative process and evolution that's got us to this point. You know the standards development process is particularly challenging. We leveraged this idea around co-opetition where we're bringing together stakeholders that are sometimes fierce competitors that would otherwise not want to be working in the same room with one another sharing insights about how they're approaching their data structures, how they're working with other stakeholders as they move goods between a point of production and consumption and sometimes even in reverse logistics situations. The points to take away is what I was saying. You can only move as fast as the community. There's challenges that we have identified and we've been working through between the actual consumables of what we're trying to produce the personas of those consumers, whether they're business role type professionals or whether they're more technical professionals and that also drives the contribution to this standards development efforts. And it's really been enlightening because I think it's really important to bring together both of those personas. You can have a world-class architect but if it's not addressing the crucial business need in a way that actually can get a budgetary sign-off, it's really kind of spinning our tires. So I think it's really been powerful the community we've brought together but it's also illuminated some real challenges and opportunities in the marketplace to develop new solutions. And one of those areas that's really been brought to light is the need for multi-role multi-work group collaborative platforms to drive this work forward effectively. And I think most people would be familiar with the platform like GitHub and GitHub is incredible in the way that it is democratized the ability for developers around the world to gain access to world-class thought leadership and also contribute to that. But there are challenges with on-the-market solutions and I'm really excited and happy that I've been here today to talk about how we're working to implement a solution that I think is really going to accelerate and drive participation and engagement not only from internal stakeholders from across the bit of community but also with external standards bodies and other industry participants and regulators from around the world that are really going to need to have an understanding of what we're working on and participate as we move forward. So with that I'm going to hand it over to the questionnaire real fast. Yeah yeah please. Some folks that work at big companies some folks that work at small companies since you're talking about the standards process and can you talk a little bit about hey are we looking for folks with only big company experience are we looking for startups to help with the standards process? Thanks for that question Tom. No it's really we want as many excited folks that have talent in understanding of these pain points to contribute to the solutions and that's a really important part of my role and it's been an expanding part of my role is making sure that we are having the right conversations with the right stakeholders from around the globe and I see a number of those stakeholders actually in the participant list today so I'm excited that we are working together to try to address this but everybody from I've had high schoolers reach out that have been interested in trying to solve some of these challenges all the way to C level executives at some of the world's largest enterprises there's a real excitement right now and I think we're at an inflection point where the technology is meeting a use case and I'm not going to dive too much into it because I really want to spend some time allowing Ben to kind of work through our work but I really think that the technology is getting to a point where it's not the biggest hurdle right now there's a real need to make sure that we proper properly educate and illuminate the solutions and capabilities that are out there to regulators because I think there's this regulatory uncertainty not only in the United States but at a global level that is slowing down the ability to really take this to an ecosystem level and so I'm excited and encouraged by number of projects that are out there where you're starting to see cross border applications of this technology driving real time to value so I'm excited about that but I'm going to hand it over to Ben Ben do you want me to stop sharing my screen so you can take over thank you Patrick yes if you could please okay I'm going to stop sharing and you go and we can see your slide 15 yeah perfect all right so good morning good afternoon everybody I'm Ben Patari basically I'm entrepreneur at heart this is my third venture acuise and we've been involved with bidas from the day one even before bidas itself was conceived as a name and what I'll do is I'll quickly go through some of the work that has happened what you saw was more a high level setup but I'm going to get a little bit more into the the nitty gritty of it so you kind of get a flavor of what what it looks like to develop standards within bidas work group so having said that essentially we have been involved in multiple work groups so the very first work group that came out of bidas was the the one on the tracking document work group we have a sort of a quasi standard already published and it's available on the bidas studio site if you want to download and review it I'm currently working and sharing the shipment work group that's where the I would say the the focal point is right now and then we have also been deeply involved in in the location party and below leading work groups as well so essentially when we started looking at I mean supply chain is a very broad topic and within that broad topic itself you have even if we just talk about logistics and transportation that in and of itself is a fairly broad topic so really we kind of started looking into it what are the use cases or the areas that we feel we want to start focusing on first so essentially that basically what led us to into building sort of this as a model that we are after right so what you have on the very left are the orders um that are coming in those orders obviously get combined with all kinds of master data in terms of location parties equipment and then you obviously have the routes and itineraries and the service rates and and and essentially when you plan and optimize what you get out of it is a shipment and this is where we're focusing on um right now in this work group but there are additional work groups working on location and party and and equipment is will be spun by itself and essentially trying to do a track and trace across that entire transportation logistics chain is really where our focus is in terms of um as Patrick mentioned you know bill of leading or or trackable events um that's what we're really after so that's where our involvement is now um what we have released so far when we first initially started out uh we actually started out doing the traditional way of how things were done like uh majority of our documentation was basically a word document with tabular structures with uml diagrams and and and you know the the data formats defined in uml and so on then we we would communicate through the slack channels and our information will be kept in github or some of it on swagger hub and we very quickly realize that when we're working in a multi work group and in a multi role collaborative scenario um that type of a paradigm doesn't really scale well especially if you're dealing with people from varying different scales from technical to business from executives to pretty much anybody in between so essentially what we ended up doing was while we were also innovating on the standard side we actually also built a platform which is what I'm going to uh demo right now and as you're seeing the platform you'll also see what the standards look like and those standards are completely all um open api v3 uh compliance standards now um we started out early on uh with looking at a lot of different formats but that's what really we standardize on and pretty much everybody is moving over this way so I don't think this would come as any surprise to anyone so having said that let me just just to be clear this is across all of bid is going to open api that is correct yeah so we had a lot of discussions and debate what is the best way to represent our standards and formats is it json tld is it xml xsds uml you name it right but this is what we have standardized on as being our mechanism going forward across all the groups thank you thank you tom so essentially what i'm going to demo now is we'll solve both those purposes right you will actually see some of the standards in action then you'll also see what that collaborative process looks like so um I'm actually on the acui side and just make sure I'm logged in and as you can see we have various different work groups that are defined and if you look at the location one this is by far the one which is being uh talked about the most because this is the very first one that we released right so essentially if you look at the model essentially this is what a specification I'm giving you a complete example of what a specification really looks like right it's got a introduction scope acknowledgments that type of section but if you really look at the model itself the entire model location is defined within the uml format I'm sorry in the uml format up here but the actual model itself is the open api specification so what you see here is the actual open api specification this is nothing proprietary what I mean by that is uh what you're seeing here is the actual specification but behind the specification you would see is the actual yaml file so those of you technically this is you can literally take this yaml file download it um and you can start implementing uh your location model if you would like um using this component right here so essentially it's a platform that allows you to build uh uh your your models and your specifications in in a highly visual and an open api v3 format and as you go and edit these models um you can you can go and commit your changes and those changes are then stored in the github repository so essentially what this is giving us is a platform for us to be able to collaborate um as Patrick and Tom were mentioning across a wide variety of audiences because if I show somebody who comes from operations or somebody who comes from a non-technical background this type of syntax it becomes very difficult for them to understand really what's happening but if I switch over and we start talking in terms of really what the data attributes are what the use cases what the requirements are they're able to comprehend and contribute much much better and they do not have to be that's the key point I'm trying to stress they do not have to be technical at all to be able to contribute uh but what we get the end product out of it is 100-person open api compliance so essentially anybody who wants to take it and implement it is then able to do that so um so that's that's the key um sort of direction we're heading and the reason we invested time and energy in this platform even though we know there's swagger hub and there's a bunch of other stuff out there but they all tend to be in technical domain and what we're trying to do at bidaz and this is a very very key point because we're actually working very closely with tradelands we also have a few interaction with with gs1 and we're trying to see whatever is already out there and make sense let's not try to reinvent the wheel whether it is the uncfx standards mmt standards um or other standards so like for example if I were to give you a glimpse of what the actual uh tradelands model looks like so this is the actual tradelands model right and so if you look in the tradelands model they actually also have address defined this is how they define address this is their definition of address uh within the tradelands model um and essentially now there's no reason for us to reinvent this wheel if we can just reuse this right there so essentially what when we invented when we created location we obviously had a location but we did a little bit um more in terms of location in the sense that we do uh have the same address components but for us location is also about creating a geo hierarchy or you actually we capture the information like latitude longitudes and altitude plus location is a recursive structure by itself and what I mean by that is location is an array of location itself um and so so this is more hierarchical but when it comes to the actual address attributes we just did as a reference as a uh to to that data model so you can start kind of getting a glimpse of what we are trying to do we're not trying to reinvent everything if something already exists it's good it's out there we would leverage it but then we will extend it in a manner so that uh we can have as much compatibility as possible across the already existing standards or in some cases just adopt them verbatim there's no reason to reinvent them so hopefully that kind of gives you a little bit of flavor of the type of work um that we're doing as at bidda so I can go more into a specific specifications so like for example this is our location party we have defined a complete common vocabulary and a data model as well in terms of the very common uh components that are needed across all the work groups when we talk about you know the the climate measurement or dimension measurement or hazardous material or or seals and signatures trackable entities weight measures these are components that are leveraged and used across pretty much all the different work groups that are out there so they're they're kind of becoming part of our common vocabulary and um these components are not necessarily even just tied down to a logistic domain for example these can be used across a wide variety of use cases and and domains um because they are common uh data structures that can be leveraged and referenced so so that that would be an example of that good Ben are you okay for a question right now from Brett yeah absolutely Brett go ahead hi my name is Brett Carpenter and I'm in um Rochester Michigan and what we're proving up in our in our technology platform has to do with map nodes and parse trees is there any consideration with regards to your location um treatments and methods in your engineering pursuits about map nodes and connecting the real world to you know to to the location itself so i mean we have talked location from the point of view of you know like um addressability and geocoordinates and and split um codes from from railroad station those type of things but specifically map nodes no um we we did have conversations around mapping polygons of locations as well but this would be an example where you know someone like you could come in provide that type of input and then we can see how it really impacts the location standard or what the next rev of definitely definitely to extend it yep yeah thanks Brett I'd love to follow up with you figure out how we can learn a little bit more about that absolutely absolutely good Brett man where do you want to take us next um so i think that's pretty much what i had to share obviously uh uh you're you're interested um you know please join us in these work groups if you have questions you can go through the forum section and post questions or if you have any other ideas that you would want to talk about you can go and submit your ideas um and they can be taken upon as additional work groups either to be spawned or maybe facilitated within the existing work groups i think there's there's a lot more work needs to be done so more we can get and involve the better it is so that's pretty much all i had to share for now but uh i'm open to q&a if you'd like and so i have one quick question here was there a link in the charts where somebody could go to open api and see what standards are already out there published um i mean it's certainly on recording here but is there some place we could rattle off for folks yeah so um beta.studio is the main site right and if you go in first you can we we have only released uh uh one one standard which was the this one right here and then what we are working on is this track and trace one right here but this is this is how we were doing things in the older ways but now all of our standards again this is a tbd early next year it'll be released out but all our standards will now be available online in the format uh that i just talked about or showed on the online platform itself and you would be able to download all the yaml files and what have you um from that platform so that is that is coming um as we speak but essentially watch the space go to bit watch beta.studio yeah you you can register and you can start looking at some of the stuff that's in here so you would just go in here click on register and there are there are two ways you can register you could just use your existing facebook or twitter or gmail id and just log right in now you may not have all the permissions but if you send the permissions certain word groups you will get those or you can fill this form and provide your interest in some of the word groups that you're interested in and we can we can get that information that way as well so but this is yet to be fully released we're transitioning like i said more from a old style of doing things where we would just create a bunch of word documents and put them on google drive or communicate via slack or github we're moving away from that and we're kind of creating this a a a a collaborative platform so to speak for us to be able to um do things a little bit more efficiently in in in a global setup but you're welcome to join and you're welcome to like i said provide your feedback your comments those all sections and that's definitely is a direction we're moving towards great thanks ben and i think ben hit upon a really important point you know saying that it's really a global community and so by moving to that open api v3 documentation that has the human readable element and then the underlying yaml file it removes the fuzziness around understanding what we're saying so that particularly when when you have consumers in a global environment there's not multiple multiple translations of the underlying data elements because what's documented there in in english at the moment has that underlying yaml structure that can be consumed machine to machine that's great because we have a lot of members who are outside the us who will probably listen to this on recording so that's that's good to point out thanks patrick yeah awesome okay any questions out there from the audience other thoughts so we got a question coming in from senali it says can you elaborate on ai enabled projects for secured supply chain ben do you want to talk a little bit about about your thoughts on that topic i know i know you've had a lot of time to consider the implications there yes so no that's that's a very broad topic right so essentially like i said when we started out we really started out looking at problems from the point of view of transportation and logistics and even to get kind of to the next level of it different modes of transportation right marine and air and railroad and what have you and then trying to build a is sort of a architecture around what would that multimodal architecture look like and what are some of the standards that we can develop around that architecture to even solve simple problems of you know end to end visibility or track or trace and and or even chain of custody type scenarios right but once you have that platform once you have that underlying layer available to you there are a lot of different ai use cases that can be enabled ai use cases as in trying to figure out or predicting where might be risk or delays within my network for goods to be moved to end destination building productive models around that or for example if you're dealing with more around machineries or equipment trying to figure out their maintenance schedules and being able to do predict then you can use that equipment data standard and then kind of use that as a component to build your ai ML models on top of those so as of right now we do not we haven't built any I guess we're building the I guess the underlying plumbing so to speak we haven't really built the ai models itself but the fact that if there is a standard because my background is actually ai I can I can talk at a length in a separate conversation but when we started looking at blockchain and ai and and some of the other technologies almost two three years ago for it to all make sense there was a need for standardization of underlying layer underlying plumbing if you if you will right in terms of what are those components that are needed in terms of equipment in terms of location in terms of party in terms of shipment ship units handling units those are the building blocks that are needed either obviously that you can do the traditional approach which is try to build an integration into 2030 40 different systems in a in a end to end fashion or you could agree on some form of standardization and that standardization then kind of becomes as your input building block into building your your your machine learning models right predictive models and so on so essentially what I'm seeing is list of the key drivers that are needed for for you to be able to whether it's multivariate or single-variate those components no longer have to be proprietary those components can be derived off of these models great thank you thanks Ben Patrick you want to talk with maybe a little bit about futures and what's coming in 2021 and how people can start actually using some of the standards and all the great work that's happening yeah Ben do you want to stop sharing your screen and I'll go back to the deck and I'll just run through that because it covers a couple of the different topics sorry I opened the wrong thing again here we go I'm seeing I've seen full screen here okay can you see it now oh maybe I just lost it can y'all see this here we go despite initial lux and reluctance yep okay so I love to use this slide and it's it's it's kind of the the needle popping the the bubble this was this was done in 2017 by the IBM Institute for Business Value Analysis and I think what it demonstrates is the expectation around the speed of implementation versus the challenges when the rubber hits the road and you really start seeing what are what it takes to get there and so this is showing first wave industries expectations around the adoption of this technology over a time period of four years between 2017 and 2021 with with half of that first wave industries that's defined somewhere else saying that by 2019 you know half the marketplace would be working on that when you overlay or overlay the transportation industry by 2020 and we're getting towards the end of this bell curve going into 2021 they were expecting you know based off of their survey results that most of the marketplace within the transportation industry would not only be experimenting with this technology but would have embraced it and started to leverage it and anecdotally I think that there's some really exciting projects out there but you know when when you look at the real facts we're a far away away from any any sort of adoption of production level projects particularly at an industry and ecosystem level so you know all of that being said you know when you step back and kind of look at the space station view of what all this means you know we're in the early stages of this it was trying to figure out you know how to educate industry participants outside of just the implications for cryptocurrency initially figuring out where are standards that can be leveraged that currently exist what standards need to be derived and then starting to build those collaborative relationships not only with other standards organizations but with stakeholders within supply chain and transportation operations and you know that's something that the BIDA is really excelled at is bringing together that global community everybody from BP to Salesforce who's looking at how to leverage this technology to move forward I think that this kind of final point right here on regulatory authorities developing auditing and compliance practices that's still really fuzzy I mean in the U.S. the SEC is doing some interesting things DHS and Homeland Security more broadly has some really interesting initiatives that I hope will see the actual fruit of it's certainly a great technology to leverage there but I think we're really just getting into this growth phase now where you're going to see these meaningful projects starting to roll out that showcase the value of innovative data governance models that are allowing for these business model transformations and that's really going to drive that growth around this space but slower than what most people think and there's certainly a marketplace for insight reports and consulting projects but it's really challenging but exciting when you start getting the people that hold the budgetary strings of these global organizations that are looking at how to implement this technology over in a series of kind of order of operations conversations to get there and so I think we'll see meaningful global projects emerge over the next three to five years in a very serious way and you're starting to see that now and so from 2017 to 2019 there was a real focus around the technology the spoke integrations going live there was trying to figure out what standards are out there and of course the way the IoT was going to play into everything standards around IoT still you know we're there's some work there 2020 is around now and I think it's not so much about the technology you know there was a real challenge around interoperability and interoperability I think with projects like Polkadot you're starting to see that interoperability challenge starting to be solved for in a really exciting way so this is allowing for real business use cases to bubble up to the surface and one of the exciting things about the work that we've done a bit is that it's stretching that visibility backwards into the supply chain in a way that just previously hasn't been widely available and so I'm excited about where that's going but you know global organizations are certainly meaningfully implementing projects at a production level these are just projects that have been highlighted over the second half of 2020 you know global organizations that are really excited about what this means and are taking a proactive step to make sure that they are building out the technology stacks and the professional capabilities within their organizations to serve their constituents moving forward you know everybody from Alibaba and and financial Cisco Salesforce the class one railroads the automakers there's a seemingly endless supply of really exciting applications for this technology that are as I alluded to at the beginning kind of unlocking these obscure areas where value can be recaptured and I think that's kind of the underlying point is that when you can recapture that value from inefficiencies you can put it towards much more exciting and you know frankly fun kind of projects and that's where you know people can get excited but the the standards component remains a crucial piece number of great organizations are doing really powerful work just this past week the digital container shipping association pushed out a standard around electronic bill of lading in the maritime space the interwork alliance has been doing some great work with two tokens that's connecting the port of Singapore and I think it's the port of Rotterdam I always confuse it and I apologize for anybody you got it project and that's been really exciting work around bill of lading as well but it reinforces the regulatory challenges that exist in different geographies in Singapore where you know they can work with a very progressive all by controlled power structure when something works really well they can adopt it but when those physical atoms get to the other side of that supply chain move after you know two weeks on the ocean and they land in Rotterdam there's you know 2000 years of trade precedent and six layers of administration that this system has to work for and so it's exciting but it's certainly illuminating certain challenges that are going to need to be solved for and that can only really be done by bringing together the right people to have those conversations with and then when you're having those conversations using a shared ontology or a shared language about what this means this was something that was and I didn't realize would be such an issue but when the standards efforts really started kicking off just defining what location would mean or what shipment means and making sure that that's a very clear definition that can be utilized around the globe for every transport mode is really really important and so all of that you know being said we're working really hard I'm having really exciting conversations with the leadership and standards organizations around the globe to make sure that we are framing up the next steps in a really powerful and effective I think maybe more crucially in an effective way so that we can have these globally meaningful conversations it's great to have you know one-on-one conversations with your congressman or representatives in congress but you know this is a global situation we're talking you know the world trade organization the world customs organization everybody is going to need to at least have a very solid understanding if not buy-in to these types of systems and you know stepping back that's quite an audacious role to take on but I think that there's there's a real value proposition to seeing this through but it's not going to be a tour a three-year project this is going to be an ongoing iterative project that's going to take the contributions of everybody from individual researchers to governmental entities and so you know as Ben said certainly invite all of y'all to to reach out get involved ask the executives at your company what are y'all thinking about this technology and how it can can play a role for your organizations a path forward and we'd love to have the conversations with y'all and get y'all involved particularly as we're moving into the implementation phase the expertise of professionals that have worked on the hyperledger platforms are really important they're being really they're well adopted there's a large body of work that we can learn from and we'd like to make sure that we utilize that knowledge set moving forward so all of that kind of being said I know we're running up about 10 minutes left you know just maybe open it back up for conversation points or discussions Tom I'll let you take it great thanks Patrick thanks Ben for things any other questions out there from the crowd maybe one question to kind of set something up but you see a lot of work around supply chain around control towers um maybe if you could distinguish where you think the work that Ben is leading could help or maybe compliment what's going on with control towers or maybe could be something that is kind of a better future than control towers yeah I think that's a great point and something that Ben alluded to and maybe I'll let Ben talk a little bit more about it but I guess my my point is is that BIDA is not going to build a product BIDA is really building that orchestration layer for the data elements that are going to power these types of applications and solutions on top of it we want to make sure that you know as Ben said the plumbing for global trade that's dependent on the movement of you know physical atoms the underlying bytes those high fidelity data elements can be shared and moved around systems in an effective way and so Ben do you want to elaborate on that point at all yeah absolutely right so whether you have control towers or you have IoT devices sensors what have you essentially what what they are helping is making who when what we're more visible right and when I say visible I don't mean visible between two companies or two parties or just end to end visible globally right so what we have done as part of our again we're not building a specific use case or a specific scenario what we're building is the underlying sort of really there's no the way to describe it but the plumbing in terms of figuring out this information who when why what and where type information so obviously where would be a location what would be a transaction like a shipment you know who would be a party so so what we're doing is we're defining standards around those and we're defining in such a way that they're not specific to a specific set of parties or specific set of mode or a specific set of rules but in a way that they can be universally used across various groups that is not to say that that work does not exist actually a lot of it exists and it becomes an issue even to figure out which one to use but I think we're adding value is looking at that work whether it exists in U.N. or whether it exists in you know some of the earlier standards and so so forth and trying to see what of it is actually public shareable and what of it still remains off chain in your respective ERP systems or control system so to speak so essentially sorry long answer the way we view control tower would be no different than a send a sensor or a party or for that matter any ERP ERTMS or WMS or anything like that yes yes as long as it's any any of those entities as long as it's sending data in terms of who and what we're we're um type information and if that information needs to be shared across a a group of participants not just within an enterprise or within two enterprise but a consortium of participants then then those are the type of stand standards is what we're building as far as bidders goes that is not to say that as you get involved and out of those discussions come up with some real use cases and and subgroups or even private groups are formed and you can go out and implement them using those standards that's that's entirely up to you but we're we're not doing anything specific solving a specific use case right now other than track and trick and visibility so so it's really a harmonization if I use that word harmonization of what everything means from a data perspective so that I'm not having to figure it out in my unique situation yep right yeah I think that's a really good way to say it you know the one of the you know when I first started thinking about the application of blockchain technology around supply chain and transportation you know the pain point that kept coming up was around EDI communications and it's great what EDI is enabled in terms of you know connecting the world but the unidirectional nature of how that data moves is is one challenge but the way that EDI is you know has been modified or iterated on over and over and over again for four decades has left you know global trade in a translation conundrum and so we have this opportunity to bring together other standards bodies that have done great work over the last four years as we've moved towards the digitization of commerce and create these open source and royalty free data standards that are geographic and technology agnostic so that we can you know solve for some of those those underlying communication fundamental issues great great so let's let's wrap up here since we're almost at the top of the hour Patrick Ben thank you very much for sharing folks who joined live or listened to recording thank you for joining in listening in clearly there's a lot of great work going on it sounds like to my ears here that on 2021 there's going to be more beyond location coming out of beta and you can actually start using some of that work at the open API specification in your work whatever your project is whether it's a startup or whether it's something within your organization and I guess the other point I heard was the the work I use harmonization again here the work with the other standards bodies out there so that you don't have to pick and choose and try to make make what seems like a mess into something for yourself because the standard bodies are actually working on that so with that happy holidays to everybody again Patrick Ben thanks for sharing here and look forward to talk to you with everybody at our next call which will be in 2021 thanks again for joining bye thank you thank you happy holidays happy holidays bye everybody bye bye Patrick bye Ben bye