Solving Supply Chain's Big Problems Webinar - Value Chain Visibility & Demand Matching

Captions as YouTube publishes them, usually machine-generated, so names such as Daml and Canton can be misheard.

1. 0:00

   good afternoon everyone thank you very much for joining us and hope all of you are keeping safe this is Manish Grover your host with digital asset and I've got Rakesh Prasad a VP of digital at innovate with me here you know often everybody is Ritesh and also I have Alban Rao Enterprise Architect from innovate digital with us with us on the webinar today everyone yeah so we've got a very nice webinar in store for you

2. 0:31

   today we're talking about supply chains big problems so show you how we can achieve value chain visibility across the network using smart contracts and blockchain and also touch upon a little bit of their supply to demand matching problem that we are facing so first you know we are going to take you through some of the key supply chain challenges and overview of those touch upon the agility problem that we have responsiveness and visibility when it

3. 1:03

   comes to demand and supply matching then we also will take you through a live app that in no way has built an end-to-end app that was actually developed to track and handle the healthcare PPE equipment for during the covert 19 pandemic so as you know the entire supply chains got disrupted it was very difficult to procure items you know and there was a lot of a lot of lot of procurement challenges so you know we built out a

4. 1:34

   app to show how we can bring multiple sellers and buyers onto the same network and how we can track an item end-to-end making procurement pretty easy actually so they're going to talk about a little bit on that show you you know what the smart contract layer looks like and then actually give you a demo of how it works so just a couple of quick things before we start I am recording this session so we will share a recording and also the

5. 2:00

   presentation with you after the webinar so if by any chance you need to drop off feel free to do that you should receive the recording data tomorrow and obviously feel free to you know put your questions in the chat box we want to keep it as interactive as possible so you know place your questions either in the Q&A section of the webinar or in the chat box and we I'll keep looking at them and I'll and I'll bring them up for discussion at the right time so with that

6. 2:30

   rakesh why don't you kick off by introducing innovate and then we can begin to the overview of the supply chain challenges absolutely thank you finish and good afternoon everybody right so it's great to be on this interesting webinar with digital assets right so you know and is a partner for digital asset and you know as an organization we are recording Atlanta one of the key thing that I definitely wanted to highlight for for us as an

7. 2:54

   organization right one of the core values and on the core focus areas for us is leveraging technology to solve a very pertinent and a very pressing customer problem right so for us being a digital analytics firm our focus has always been around how do we solve the custom problem right it's not about just doing technology for the sake of technology and that's where this whole opportunity was working with this classic was very exciting because we figured out a very very pertinent

8. 3:20

   problem that was existing today in the industry which was further I would say amplified with co19 coming in and you know creating this kind of a scenario that we are in right and we took it head-on and it was great working with this class as an organization I think from a focused and point supply chain visibility process digitization and digital transformation are some of the core focus areas for us from a service

9. 3:46

   offering perspective right but if we can move on yeah thank you very much okay so now you know let's get into some typical challenges that that we often face in the in supply chain so I will bring up the whole slide obviously you know as we know there are multiple stakeholders you know right from the buyer to the seller sellers have probably multiple suppliers you know there's international shipping

10. 4:11

    and all of that involved and obviously you know it leads to several you know value chain visibility and you know data silos silo problems so Rakesh you know in your view what are some of the what are some of the challenge that you see in the market the clients face and you know touch upon a little bit on the root causes as well sure money sharing see what we see if you look at what are some of the you know patterns or something issues that symptoms that you see right I think one of the biggest gaps that we have seen is

11. 4:43

    the pace at which the decision making happens right and I think that is one of the big gaps that we have seen as the supply chain starts getting more and more global and more and more spread the pace of decision-making starts taking a hit right and organizations need to start thinking how do they keep up with that right second big impact is always been around what the customer experience is going to be based on how you are kind of adhering to all the commitments that

12. 5:09

    you are making from a delivery standpoint and we have all heard about the perfect order fulfillment scores making sure you are delivering the right product the right time the right quantity right so the overall customer experience is one of the big gaps that we have started seeing as the supply chain starts to not behave in the client manner right and then of course that leads to a financial impact around the overall organization's operations right on a revenue standpoint when you start

13. 5:34

    going out of stock or on the power standpoint when you start to curing to fulfill some pike in demands and you have to go outside the preferred network of suppliers right and then overall then it comes down to also being how responsive is your supply chain to not just take care of what you have planned for but also be you know flexible enough to get ready for anything that comes in which we all it's very hard for us to

14. 5:57

    anticipate right so I think those are some of the gladsome tools that we see right which happens from a talent standpoint but if you were to kind of take it a level deeper and and try and understand where these challenges really come from and I think what the biggest thing is from a visibility standpoint it becomes very challenging to get an end-to-end visibility that larger organizations are investing so heavily in trying to integrate across different

15. 6:23

    parties that is involved right but still to ask the amount of visibility you have from an end-to-end supply chain perspective that is limited primarily because every stakeholder tends to operate in its own silo of operation right and if you have a manufacturer they are operating in their world if you have a three PL and a shipper they are operating their world and if you have a buyer they're operating in their world so I think that itself picks a big visibility

16. 6:47

    issue and there is a lot of investment that is happening and trying to how do we build that whole visibility aspect right and with that what it leads to Manisha and others on the call is the fact that you start having a lot of data inconsistency issue because the way a manufacturer versus the shipper versus a you know so you know actual buyer they are kind of looking at their data they

17. 7:09

    while they are looking the same set the granularity varies the definitions vary at what frequency you want to look at that variant that starts creating a lot of data inconsistency issues right and finally most of the supply chain that is built today is always built based on historical trends yes AI and machine learning is kind of changing the game but majority still is based on historical trends of what you've seen in

18. 7:34

    the past and how you have planned for it right which then it gives you a place where exception handling becomes a challenge right and to manage exceptions typically it is always extra cost that goes into magnetic stick exceptions and come along and how do we fulfill that right those are some of the big things that we've seen from a supply chain arena standpoint right which is driving these challenges that exist today yeah

19. 7:57

    and a couple of points I wanted to make so on the financial impact side at least on the cost side that and responsiveness is sort of linked together because in order to be more responsive if you don't have a good supply chain you know like a demand sensing mechanism then you tend to keep more inventory you know carry more inventory which obviously leads to leads to higher costs as well there are things that that you know there are

20. 8:22

    initiatives that are going on in the industry such as retailer links so big retailers such as Walmart for example are building dedicated retailer links for their suppliers essentially telling the suppliers that hey here's our inventory here that demand patterns you figure out and make sure that we don't have a stock out or you carry the inventory in the right places so a lot of those initiatives are underway but

21. 8:46

    then again each of those are operating they are you know excellent initiatives leading to a I you know demand sensing you know techniques that are being put in retailer links that a data sharing is happening but then obviously like Rakesh mentioned on the left-hand side of the bottom you know all of those stakeholders are operating across application Islands and across company Islands as well so while Walmart may be sharing it you know not all suppliers may be geared to

22. 9:11

    access the same data in the same fashion so there's a lot of investment that is needed so with that let's move on to the demand supply matching impacts so we built out a very simplistic flow you know on the left hand side you have a retailer and this could be any point of sale of course retailers or even hospitals in our case when we get into the demo then we get into suppliers and

23. 9:38

    manufacturers they could be multiple even a chain of suppliers and manufacturers sometimes and then obviously there's fulfillment and distribution and there's latency everywhere so Rakesh do you want to talk a little bit about the about the various kind of issues we face in such a value chain Shawn I think this is a very classic example of what we are seeing in the industry today right so essentially your demand signals today which means

24. 10:02

    knowing exactly how much your retailers need and how much products you are going to sell is always based on a pattern and as I said there is always a delay in getting the real demand coming through right and what then suppliers and manufacturers are trying to do to fulfill that is based on their planning and based on the historic data they are able they're creating some sort of I would say invent to your flexibility to continuously adjust to the way the

25. 10:28

    demand is going to fluctuate it's not that it has been done randomly here the industry is matured a lot and now everything is based on a demand signal that is as real-time as potentially can be but still if you look at the actual execution of this it still works on at least four to six weeks of planning or seven weeks of planning that needs to be put together for every manufacturer or supplier to kind of fulfill the demand

26. 10:54

    that they are looking for right and based on that they are planning the inventories that they carry either at the distribution center or at their manufacturing location and that's a cost that they are carrying right and then they are trying to make sure that the inventory is optimized maximum for some sort of outlier scenarios right and all of this is done primarily because it's very hard in the end-to-end supply chain

27. 11:16

    to get real-time visibility into a demand that is potentially coming up and so that the supply chain can be built in a way that it can fulfill it right so since they're always dependent on I would say a handshake happening and that handshake leads to everybody planning for contingency and that contingency then leads to inventory cost and then of course also from a distribution and

28. 11:39

    fulfillment channel it becomes very difficult to figure out at which DC or at which area where you want to kind of keep what stock is there right you and all the organizations are trying to use a lot of data and analytics and machine learning is definitely taking this a notch up for the organizations to kind of make it more I would say real-time as much as possible and more realistic to the scenario that is on the ground but

29. 12:02

    covert 19 was a classic example right because what it through you nobody was prepared for it right and that is where the fact is that nobody since you're not seeing the real-time rise in the demand you're not able to respond real-time into how do you fulfill it right and how do you expand your supply chain to maybe fulfill that in mind right and I think that brings us to what we wanted to kind of cover it this was I think who 19 who

30. 12:25

    whatever it was I know it was a challenging time for all the organizations going through but I think it was also a very good eye-opener for a lot of us in this industry to say that how are we get up today and what do we need right and if you look at the purpose of why we are here today the demand of PPE just went through the roof right and the pp demands are was varying depend on which state which country at

31. 12:48

    what point in time of this whole you know covert cycle as we call it flatten the curve that they were on the demand was fluctuate fluctuating so high that the traditional supply chain was not able to manage it right and when we got started talking to couple of you know VC firms here and a couple of buyers in New York City they were struggling to match up the demand to the supply because it

32. 13:11

    was not that there were no suppliers out there that could provision the PPE requirement that was there it was just that they were outside the traditional chain awful and that is their right and to be able to bring them on board and to make sure how quickly can they be in the ecosystem that itself was throwing up a challenge where all of these transactions then started happening on the phone and spreadsheet right and the demand started becoming so high that was very hard to

33. 13:35

    kind of manage it and then be in a place where you can build in some transparency and visibility across for everybody right and that's where this became a very very exciting problem for us to take on as part of a new technology or a new solution that wanted to try out right yeah so there is a question from Steven and Steven I'll address that question in the next couple of slides it's essentially you know he's asking

34. 14:00

    changes do not flow from one system to the other so whose responsibility is it for communicating the changes to the shared data and who has responsibility that the system with out-of-date information gets the latest accurate data so that's obviously you know that's obviously the bulk of what we are doing today you know reconciling between systems and I just wanted to touch upon the demand

35. 14:24

    and supply matching angle that Rakesh pointed out is that on this slide if we if we go back to that flow chart that we had you know routing plans and you know who you know what to supply to which location is pretty much defined here and then obviously it is carried out but then because there is you know because there is obviously a lag between the time demand signals are processed and the orders are placed and then the

36. 14:55

    shipment is initiated there is very little flexibility here in case demand patterns change to change the change how you're supplying items so in the case of kovat for example depending on the number of test cases that were coming up and the number of hospitalizations that were happening the demand was fluctuating widely say for example between New Jersey and New York if there is a set of P P bound for New York and you know that suddenly the demand has

37. 15:25

    changed and it's required more in New Jersey at the last minute is it possible to quickly change that change that pattern and and move into the you know move that the inventory first to New Jersey and then fulfill fulfill New York and Whitney if I may right just to add one point to what Stephen was asking right so from a responsibility standpoint I think that's another fascinating point

38. 15:49

    that based on who is more powerful in the ecosystem he sets the demand he says the rules of the game right so if you are engaging Walmart or Amazon's of the world they set the rule of the game and you have to play with their game they will tell you where which DC what procurement and what is the product how is it right and everybody has to follow what they are trying to define as their supply chain

39. 16:13

    and their process right with limited flexibility that you will have from your side and there you have to optimize based on what the big retailers need right and if you now come to small retailers they typically are relying on manufacturers to be able to have that visibility and plan so that their outlets are not going to get out of stock right so I think the roles and responsibilities change based on where

40. 16:36

    you are engaging in which party has the more control in that equation right and it's very subjective to each of the relationship that you carry yeah so that brings us to steepen I think this would answer your question so generally what we are doing here is you know traditionally there are silos as we've already covered between different applications as well as different companies and the responsibility is the

41. 17:03

    you know the responsibility of making sure that the data is updated is is the process of reconciliation every application every company is trying to sync up with the with the counterpart on what is the what is the latest you know status of the inventory and you know of the of the orders of the demand and of the supply and obviously because of this constant reconciliation it leads to a lot of latency you know between between organizations and there are obviously a

42. 17:34

    lot of process breaks you know technology fails sometimes you know so sending the data may take say eight hours you consolidate and send it to someone and they might need some more time to make sense of the data process said run it through the logarithms you know send it to their send to their procurement systems and all that stuff so there's a constant reconciliation that is happening and the idea for what

43. 17:57

    we want to discuss today is this right so how do we enable a common source of truth within and between enterprises while maintaining privacy and confidentiality requirements and regulatory and compliance requirements and that's that's that's the purpose of of what digital asset is building so we've built out this built out demel which is a smart contract language which runs on you know different types of block chains and the purpose is this you

44. 18:28

    know how do we help clients tap into a single golden source of information while maintaining privacy and it's in in a sense everybody sharing a common mutual business process versus having to break that business process as soon as organizational boundaries are are crossed and the technology is currently in use at many in a large organization system Italy consequential organizations you see the Australian Securities Exchange at the bottom that's not a supply chain organization but you know

45. 19:01

    they are replacing their entire post trade equity settlement platform with a smart contract based application which is allowing you know all of the different participating banks and ASX itself to provide a common golden source of information to everyone versus having to rely on messaging and back-and-forth transmission of information similarly in the healthcare space there's a prototype

46. 19:25

    that was built for change healthcare which is obviously one of the largest exchanges in the u.s. they you know when you have a claim at a at a provider say a doctor your claim needs to go back all the way to the insurer sometimes there are multiple claims multiple providers have engaged with you as they rendered their treatment to you all of those different claims have to be consolidated sent to the insurer insurer has to make sure you know you're eligible then they

47. 19:48

    make the payments you as a consumer have very little idea and as also the provider is a very little idea of what's happening with that claim and what is the status so change is trying to change that essentially this is what the technology looks like it's a smart contracts run time it's open source so there's no cost to it you have a smart contract enabled application on the top that automatically runs on multiple

48. 20:13

    distributed ledger so you can either run it on a distributed ledger or you can run it on a traditional database like PostgreSQL Amazon Aurora you know or the even the Amazon AWS qldd that came out recently and the beauty of this platform is that each of these different networks can also be connected with each other and that's what we are calling the content protocol so if one of the ecosystems is running on say hi pillager

49. 20:42

    sawtooth or fabric there's another ecosystem that is running on coda or freeze coda platform and there's another enterprise which is processing their internal transactions using plain old database like AWS or aura or PostgreSQL each of them will be able to have you know economic transactions across across the networks so what does it allow essentially we'll cover that as we go through the demo in a couple of minutes

50. 21:12

    you know no duplicate party onboarding so as you know as you'll see in the demo in the covert 19 demo there are multiple buyers multiple sellers and every buyer has to take care of onboarding their own sellers even though that same seller may be furnishing the same information to multiple buyers each of the buyers have their own seller list you know and there's very little potential for reuse similarly the concept of inventory as a digital asset so we are used to dealing

51. 21:42

    with data records instead of dealing with an inventory so if there's a piece of inventory say a package say a ventilator in The Cove in nineteen case that twenty later should be tracked all the way from Cote request to providing a quotation to being shipped to being delivered and we should be able to track that one ventilator and take actions on it versus creating it as a data row and

52. 22:05

    then obviously you know there's a single version okay and one of the things I wanted to point out was much better regulatory compliance as well as you will see in the demo because there is a golden source of information which is completely confidential to the party that is ex that is living on the network you could define a regulatory body for example which would get a snapshot of certain amount of information through every transaction so who's procuring you know what kind of

53. 22:30

    equipment you know from which country you know you know and customs information FDA related information all of that can easily be funneled through to the regulatory body which can also be on the network so it makes the job of compliance you know the cost of compliance very low and Maurice if I may right this is Rakesh so I think these were when we started out thinking about building this whole solution right I think one of the biggest reasons that we chose to go with digital asset and use their demo platform was primarily around

54. 23:01

    teas right because if you were to kind of build an app which was going to cross boundaries of each organization or each parties that are going to play we did not have time to build something required for massive data integration to kind of set the trust on the data and make sure everybody is agreeing to what they're seeing right and that's where one of the big and that was everything

55. 23:24

    thing the co-driver for us to look at a platform of a distributed ledger platform and then work with the slicer to build it on their daemul platform right because it's open source and it is very flexible in terms of how the app can be written and how easily the app can be integrated to the dama layer right so I think there's some are experiences of maybe the reasons why we chose distributed laser first and then

56. 23:48

    of course using download to build that out other than any other platform exactly yeah I think data domicile was also an important consideration so there are parties from different geographies in this case say you've got a supplier in China and then you've got a you know buyer in in the US and there could be an intermediary in another location you know typically govern you know regulations don't permit your data to be shared across international boundaries

57. 24:12

    and you have to put you know several mechanisms in place to enable that to do that with the legacy technology would have taken an inordinate amount of time with demel smart contracts and deploying it on a blockchain network it makes it very easy because now you can share you can define data sharing and privacy at a granular level so that makes it much easier so with that and then let me see

58. 24:39

    if there are any questions I think there's one from Steven which we answered Steven hopefully hopefully that hopefully that answered your question if there are any other questions feel free to feel free to post in either the chat or in or in the Q&A section okay yeah steven is saying yes good we're done okay great so now what I would like to do is I'd like to welcome our win who's

59. 25:05

    going to take us through take us through the application how they built it and also show us a live demo of how it works Thank You nation hi everyone so I can see this is the application that we built which is fork over 19 we have got multiple parties that interact in the whole supply chain in our case or in a typical supply chain you have a buyer or a seller buyer could be for

60. 25:33

    example like CVS a seller could be 3m or GE bio typically has a buyer agent which will be a rep from the company who is responsible for making sure that the order and everything all the documentation and everything is correct typically you have a shipper which could be like a UPS or FedEx which is once the goods are each stateside in the US they kind of send it over to the final

61. 25:56

    destination which could be in hospital and in our business flow that's when the order is completed so the buyer creates basically the order he selects everything seller accepts it creates an RFQ creates a code buyer agents approves everything that everything has been all the documentation there would be a clearance customs clearance and everything has been done the shipper receives it the hospital also receives at once and that's when the order is

62. 26:20

    completed so Manish if you can make me the host I will share the screen yeah and we can get into the demo yeah let me do that and also just wanted to point out so this even though this is a you know typical procurement end-to-end procurement application which can be you know sort of thought about similar to a track and trace application but you know because the way it is if you remember we touched upon demand sensing you know in the beginning so each of these items when they are being delivered there's an angle of demand

63. 26:52

    which is you know how many test cases how many you know there are how many positive test cases which region has a higher traffic etc there are applications I know and there are a couple of attendees on this webinar as well which are creating those applications those applications created in demel will automatically interoperate with this application so now you could take the demand side of the you know of

64. 27:15

    the equation and marry it with this you know procurement end-to-end procurement of the PPE side of the equation and now you could have an end-to-end solution which sort of automatically takes the demand you know and most of it is going to be automated in algorithmic but it takes the demand makes the decisions using AI techniques and then it automatically routes your orders and accordingly so that's what I wanted to

65. 27:37

    point out and oh yeah we need yeah we needed to be a touch about this side also so this is what kind of our demos smart contract looks like as you can see everything is declared in the model itself you can have the contracts which are the legal documents or the the processes that particular user does parties are typically the people who can act on those all the access for what a

66. 28:04

    document is what the contract is and all the authorizations which is who which party can do what that is also declared in the Demel itself if you see in the first line 525 526 the buyer can create the code request but the controller who is the seller only he can do these actions which I only the seller can accept it or reject it and the buyer again at 5:36 he can cancel a quote

67. 28:27

    request so the access as well as the role based authorization everything is declaratively declared inside the demel itself so there is no extra overhead of setting up hook into what what are the permissions on each particular page or what are the functions all those all that is handled with demel itself and this makes development much easier because we are basically focusing on the business flow and not setting up the

68. 28:52

    backend or the overhead and those kind of things yeah and I really I think you were able to document the entire preliminary business process I think within a few days I think you were able to test out a rudimentary version of the process flow yeah definitely this definitely helped us and time to market the speed and everything was phenomenal once the business flow was defined we could basically knock out knock it out all the

69. 29:17

    flow and everything in diamond within a few days and the beauty of this is beauty of Damelin the runtime is we define the business flow everything the runtime exposes everything through red tape guys we use react Jas has the front end but you can use multiple front ends whichever you're comfortable with everything is through REST API is the authentication handling and everything is handled by demel itself so that makes

70. 29:41

    development really really smooth the code 19 app that we developed we've created using tamil we've deployed it on project dabble which is the cloud version the cloud platform for Dammann provided by additional asset itself reactor Jas was a front-end the platform that we chose for making this application so if and I think project double for a second so for anybody who's looking to develop Dan'l applications project double provides an excellent target environment for you to you know compile your ml model basically which

71. 30:21

    and then deploy it on posi devil and automatically you get everything that you would get from a managed platform so for example you don't have to worry about authentication don't worry about infrastructure scaling security and all of that your applications are you know our life automatically everything is managed in the backend with positive and it's free to use so if anybody is thinking of developing a demo application definitely give it a look

72. 30:46

    it's on project double com ok so I'm going to stop sharing and I'll give you the access now short let me see I think there's one more question let me make you the presenter okay go ahead I mean I think you should be able to share now yeah yeah please let me know if you can see the screen yeah we can so this is a project deployed on project Apple if you see covert 19 app this is basically the admin and these are like all the internal exchanges basically all the metadata and everything that for this

73. 31:34

    application is stored the way that the application works is you log in on a project Babel it creates a user and then you assign the permissions to the user and after that it is locked down so even the admin if you see I logged in as Arvin raw but there are multiple uses that are logged in the buyer buyer agent Hospital and seller even the admin doesn't have access to what the permissions or what the buyer is doing

74. 31:58

    so he has no visibility so that helps a lot in the data security as well as integrity of the data exchange is kind of it keeps track of everything that's happening in the system so you can see there are multiple buyer agents there are buyers or a shippers all the products are defined here exchange is what gives you the economies of scale so you don't have to onboard the same supplier and the same product twice once you know that a product has FDA approval for example you know that product is

75. 32:31

    available and obviously that can we configure it so sellers might make it visible in some geographies they may not want to make it visible in some geographies and stuff like that is definitely up to the seller but then you have to do all of that onboarding just once so supplier sellers are on-boarded ones products are on-boarded ones and then they are available for use as as defined and just to add all these actions that you're seeing at buy a ride

76. 32:55

    ship but this is all defined in the tamil so no extra work was done everything is handled by project double automatically this is the application this is the front end of application we can login with apple which ties into SSO so right now we are using Google accounts login as a buyer once set authenticates logs into your application these are some of the completed orders that have been completed previously and previously demos and missing the product catalog

77. 33:40

    these are the three products that we have set up for this application so you can see you have gloves you have respirators in create you can create the cat we can create the orders of what the orders are this is for creating the coat request you can select the sellers so these sellers are again tied for each buyer each buyer can onboard his own sellers of this creates this avoids

78. 34:08

    redundancy and duplication the due date when the coats are do we can select it up once you select that it places it in the queue if I log in as a seller actually okay again those log in as a seller I see on the coat request I can see that this is the coat request that I received if you see the buyer had selected to code to sellers this is one of the sellers arrogancy once it receives it he received this is the quantity whether he can accept it once he accepted he can say ok I'm going to

79. 34:56

    sell it to you for $3,000 quick question sellers will not be able to see each other's coats and could request wait correct so if you see right now the coat requests he can see only the one that he has been assigned to nothing else he cannot see the product catalog he cannot see the coats he cannot see anything else cargo initiated all the cargo which is handled by the shipper or the buyer agent or the hospital delivery he cannot see anything else he is he gets access to only the

80. 35:27

    action that he can do yeah and for everybody wondering I think the UI has been made using just to speed up development we used an existing react template that was customized which is open source and available on the Demel dot-com marketplace but obviously this front-end can be customized a lot in fact in no way has customized it by showing all of these products and making sellers visible to the buyer etc so there's definitely customization but it allows you to get off the ground much faster yeah definitely

81. 36:00

    so once the seller can create a code he can submit it the buyer can actually receive the code and you see that it received the code from on the seller or whether he can accept it or reject it I can accept it and he can assign the buyer agent a buyer agent is the representative who will take care of making sure that all the documentation and everything is correct once he accepted then the seller can see it as purchase order and then he can accept it

82. 36:32

    so when he accepts it this creates a purchase order into an order so if so if we go back to the workflow which is the buyer created the products I'm not sure which screen the showings give me one second here we were looking at the flowchart okay I'll just shorten this instead of being a slideshow so yeah so the buyer created the products it went to the created a code requires the seller it sent RFQ to the seller and the seller accepted it created a coat he sent a coat the buyer again accepted the code

83. 37:24

    had created a purchase order and the seller then accepted the purchase order which created an order the rest of the flow due to limitation of time we can skip those but typically the buyer agent will get a notification he can acts once it clears every in customs approval he can add it just for the sake this project we this application we just made the buyer agent do their BN customs but in real life you can have separate parties the parties can be on bordered

84. 37:55

    as many as we want depending on the business case for every we can have a different party the customs could be a different party if there's a state approval that could be a different party and we can just tie those into the workflow and make them authorized and access River once the shipper in hospital then it creates a orders completed so we can just look at yeah and this is a quick thing so during this process obviously once the product is shipped you could also use your

85. 38:26

    application can also use REST API and connect with a third-party shipper for example to get the latest status of the shipment so it doesn't have to be manually acted right thank you so as part of v2 of this application that's what we have planned right some of the key shippers and all where we have the API is available we plan to integrate that and make sure some of these processes may not be manual right and

86. 38:50

    you know be manual they will get automatically updated with notifications going that the status has changed exactly and I think you've got some AI algorithms running which will automatically place the orders depending on the inventory level and all that stuff so that's yes and that's another so even to choose the sellers based on their typical time in the past and those kind of performances those are the

87. 39:13

    enhancement that are planned on the app right because as a buyer you like if you have 10 suppliers you like to make sure you're placing the order of the supplier which has higher performance parameter or whatever right it based on the algorithm that we put to recommend it recommend the suppliers right so those are the added on capabilities that will that we plan to bring into the platform right as we go along

88. 39:38

    so right now this is again logged in as a buyer typically the flow is if you don't look at the party is the purchase order cargo when the seller sends out the goods for example he's based out of China and he/she puts it on a ship that's when the cargo gets initiated he'll get a notification that's when the buyer agent will receive a notification that the goes every stateside he'll clear the cargo and the FDA clearances and everything is done

89. 40:02

    shipment delivery is when we put it on to like FedEx or UPS when it needs to go stateside for the local transport once you receive it then the hospital delivery will be when the hospital actually receives and they've received the goods and gets a clearance and basically that ends up with the completed order so if a completed order it keeps track of the whole workflow the whole order history everything is

90. 40:26

    tracked the other good thing about Damelin a distributed ledger is because everything is tracked and everything gets archived so there's an audit trail for every transaction that's happening and sits since it's on a distributed ledger which is basically a block check in functionality it's more tamper proof because it's distributed on multiple systems so you can see this is not the current order that we created but a previous order everything is unique the

91. 40:53

    reference ID system generated the ledger this all the unique party IDs who can manipulate on them what the price was when what is ship who the shipper was like FedEx or UPS and which was a hospital what the quantity is the price and everything so this is in the non in a nutshell what the application does as you said it's fully customizable to enhance it to make any changes add more parties add more products anything it's

92. 41:18

    very easy to do it using demo awesome yeah thank you very much I will so this is great and obviously just for the benefit of everyone so I mean they'll just start sharing again so just for the benefit of everyone you can see that when we were here on this slide this this application this demo application has been deployed on project double for simplicity but obviously you could take the same application without any changes at all and deploy it on a block chain of your choice so if you are using fabric for example or Sawtooth you

93. 42:03

    could deploy the same application on fabric and and sawtooth or any other application and so that's that's what we mean by Rimmel photo and you know you don't typically have to choose your blockchain and the target platform before you develop your application so in this case in a way was initially going to deploy it on sawtooth for example but then we decided to deploy it on project level to make it easier to manage and to easier to demo and prototype with with the buyers and the sellers and the next step is to

94. 42:34

    depending on what the choice of technology is and obviously many other considerations that go into choosing a platform you know it can be deployed without any changes to to another network as well and rakesh do you want to touch upon quickly the analytics portion of it the AI angle that I want to kind of bring that up as one of the key things right so keep the this application that we have built right it

95. 43:05

    is taking care of making sure the process and the process aspect of it and all the parties and the compliance aspect of it all that is taken care right but there is another angle of how do you make it available to the users to get a status get to know where it is what's happening what are the delays and make it more conversational rather than trying to go and run multiple reports

96. 43:29

    right and that's where we are in a version 2 of this app we implant to integrate this app with our own conversationally eye solution we call it saya and that is nothing but think of it for lack of a better term as elixir or a voice assistant for your business right it's a amazing solution that we have built that can put data from or pull data from any other underlying applications and this application could build one a fret and then renders the inside as a way of asking a question like all of us are getting used to with

97. 44:03

    all the voice enabled solutions that we have on home right so that's the solution we plan to indicate where then it will start giving every party a clear visibility into where exactly the product is right now if it's delayed what is happening if it's reaching on time it's reaching on time which all final locations is going to be delivered to what's the et and all that good stuff right so their integration with our SIA

98. 44:28

    solution is planned and you can go to our website and over comm to take a look at this I application itself yeah I'll send out some of these in there in the follow-up email and obviously aggregated information is very important so how many orders have been placed how many were delayed you know what seems like the trend you know what kind of products are being are in demand recently etc so some of those aggregated bi related requirements can also image yeah and the idea is then that becomes

99. 44:58

    longer this app kind of then completely covers the I will say the full visibility aspect of your supply chain so that's where visibility starts coming into play so things yeah so I think with that we also answered a few other questions that had come up around portability and business intelligence so I'm hoping well nobody should have we have one question on the chat yeah let me see okay great

100. 45:31

     you were saying Salesforce and as your integration is already been announced or are you teasing them with this slide yeah I think those are in progress you know I we can share information offline URI yeah and India it looks like Indra had a question but I don't see your question in there are you do you still have it or nope I think I think Indra is good then so great so I think yeah that brings us to that brings us to the end of the end of the

101. 46:09

     presentation hopefully this was useful so we tackled upon some of the key supply chain challenges including visibility and demand matching which I hope everyone got a clear idea of how to do that using a using a smart contract based platform deployed on either a distributed ledger or even a database and how do we allow for how do we bridge multiple application and data silos without requiring continuous

102. 46:32

     reconciliation yeah and you know in the follow-up email I'm I'm gonna send you a recording the addition as well as some other interesting links to the science solution the brackish mentioned as well as a couple of other open-source apps including the open source daemul react template that was used for this application so with that thank you very much Rakesh any closing thoughts yeah I think

103. 46:55

     I just I was looking in the chat window right so in there I still has a question so I just requested her to type the question in there are you on mute so we not you'll not be able to speak up the question so if you can type your question we can address that right so that way we can absolutely answer the question right and it's we have time right so we are not running away so please go ahead and type your question and we will address it you can either use the chat window that you used is

104. 47:23

     this a marketplace or yes so if you know the idea and money let me take care another so in this question is a marketplace for procurement of medical supplies so the answer is we have not yet made it the objective of this app was purpose-built for all the medical supplies that we were requiring fork over 19 right so our goal is to put it on my marketplace and make it enable for

105. 47:46

     anybody to use for any kind of procurement right so we don't want to restrict it to medical supplies right the objective was starting from there but the way app is designed in the way that we have chosen the technology this can be extended to procuring any products in your supply chain is not restricted Oh sort of a sort of a solution accelerator which you can use to create your you can create your own marketplace using this application supplier quality qualifying MD

106. 48:17

     onboarding so money if you want to talk about the FDA onboarding that we were anyways discussing yeah yeah so obviously there's a workflow that goes into play when you onboard a supplier and obviously their products so all of those you know are are easily addressable in the solution so that's part of the onboarding process so when you onboard a supplier you know you can request the right information from them validate they validate that and then

107. 48:42

     permit the supplier on the on the network and also you could have you know periodic qualification requirements or review requirement so whether it's six months or one year or when something changes you could obviously put those triggers in place you know that also brings up a very interesting advantage with such a solution is that each of these FDA certifications and onboarding is

108. 49:06

     automatically visible to all of the buyers so you know that saves a lot of operational overhead for that same process to be done by multiple buyers as in the current cycle and you know yeah and the smart contract business rules typically you know the ecosystems are ecosystems are so this question let me repeat the question how is the smart contracts business rules governed in this ecosystem with multiple multi-party collaboration so the idea is that each

109. 49:36

     of the parties who are on the network are agreeing to the business rules that have been defined in the workflow including all of the supplier onboarding you know order placement you know how do we assign a buyer's agent how do we get a PA you know clearance etcetera all of that is automatically defined and if there are any changes that need to be made then multiple parties obviously have to agree to that change one simple

110. 50:00

     way that most of the ecosystems are addressing that is by creating a central party for example like a consortium or designating a neutral party to take care of some of those things so you know requests for changes go into that party that party does the collaboration and you know and the and the coordination between multiple parties and changes or country X to the system yeah and demel

111. 50:25

     is the protocol for interoperability demel defines the standard the smart contracts and then there is a separate protocol called the cantle protocol which actually does the interoperability between multiple family works so that was the final question from Indra Indra does that help yeah okay great so cool so thank you very much we are almost out of time now so be on the lookout for the recording and the presentation that I'll send out after this session maybe you'll

112. 51:01

     receive it I think sometime tomorrow and then thank you very much for attending safe and if you have any questions definitely reach out to me or to Rakesh and Irwin who were on the webinar and then you know yep good luck and thank you so much for attending thank you all have a good day thank you