 Beautiful. Hello everybody. Welcome to today's Hyperledger Supply Chain Special Interest Goupa webinar here the second for 2020. Today we have Marina and Luca from SurgeTech over in Italy right? You'll tell us where in Italy you are you guys work probably virtually like the rest of us here. They're gonna present their solution based on Hyperledger here for the fashion industry. So with that I shared with Marina and Luca that we go an hour and 20-30 minutes of presentation. She'll probably say she's open for questions along the way so you're welcome to do that. You good with that Marina? Yes absolutely. Okay beautiful. So Marina, well we'll turn it over to you and you and Luca and let's roll. Beautiful. Thank you. Thank you Tom. Thank you Hyperledger for this beautiful opportunity. We're so excited to be part of Hyperledger community and I will present myself shortly. My name is Marina and I'm a co-founder of Surge company. Today with me I have Luca Ferrari and his owner. Let's start our presentation. I already shared my screen so we can just start. I'll start saying a few words about our company. So company is based in Bologna. It's Italy town, beautiful town anyway. I think that's where the oldest university in the world is right? Bologna? Yes. There you go, claim to fame. Great Tom. We created this company in 2018. Just from the beginning we started working remotely so we can say that our company is absolutely COVID resilient and so the fortune was the idea to bring an international team based mostly in Europe working everybody like remotely from from just from the start and we use Hyperledger Fabric to create an enterprise solution. Our main client is Keating Iwer. This company works in field of luxury goods and our product is running. What's the name of the company? The main client? Keating. They are producing, they are designing and retailing Iwer. Okay, so they be a competitor to Laxativa? Yes. I think that's everything like Gucci sunglasses. Good, that's good. We're very interested in real life stories so that's great that you have a client that's using it. Yes this is a complete real life story with up and downs but with beautiful end. So many companies are using our solutions and because of our solution we had great support of our investors so we are really happy to see that more than 20 companies are using this solution. What was the point? Looking at today's supply chains we can see that they are quite complex and there are a lot of requirements, compliance and regulatory, I think nightmare of everybody working on supply chains and the main problem is the fact that companies are keeping their data separated, isolated from other players in supply chains. So from the other side there is a blockchain technology which gives huge opportunities for different ways to collaborate and looking at this our idea was the possibility to enrich blockchain technology and to make a solution which can help the companies to collaborate in a new way. So our solution is front software and it's all about collaboration, connection and integration. So for the first time thanks to distributed ledger these companies had the opportunity to share their data. Obviously as people used to say blockchain is not a solo flight. So first we need to create a consortium but then just starting with three companies, one which is producing lands, another assets and the third one certification institute. We started studying their processes, business processes and changed them by different workflows which gave them more efficient collaboration. And then surge is putting blockchain technology as a layer between companies and blockchains. So it's possible to make the source of true inside the blockchain and by building that in the end we are able to have a digital passport of a product. So product came in the first place in the center and this is the result of our of this collaboration because every single company has his own front and our solution is like blockchain as a service. So it's running on cloud and subscription. It doesn't need any implementation. So the fact is that every company is giving their part of data and certificates or they can upload tones of documents there. So that's the main goal. That's the main result and why? First of all because we live in the world where consumers are more like say yes. And the second thing is that companies they can really communicate their values, their effort and their social responsibility. For example, Kerring, thanks to Front, this year could calculate their environmental profit and loss monitor value because they are really sensitive about these things. So for them, for the first time it was possible to have some informations about their eyewear. They couldn't have in different way without mapping this supply chain. So by mapping the supply chain, changing workflows and process, a business process and by helping companies to collaborate. In the end, we have the possibility to have every possible document certificate and let's say asset that we need for analysis, for giving some messages as a company and it's really a nice story. So this is from my side. I hope that I was clear. Just I'm here if you want to ask me something more about this case study. We will proceed with more technical details about solutions. Okay, so thank you. Thank you, Marina. And let me say that as Marina said, we have this idea, this vision of putting the product at the center. Okay, so our core idea is let's put the product at the center and let's ask everybody involved in the supply chain to collaborate. And what happens is that by this idea, we can implement different solutions. So most of the companies now are doing POCs, pilots for track and trace. This is one of the things we may do, but it's in reality is much wider what we can achieve with this kind of solution. The first thing is the one that Marina was mentioning. So creating this digital ID, digital passport of a product, a very sophisticated one, managing data and documents for every type of merchandise, thanks to collaboration through the supply chain. So all companies who collaborate across several tiers of the supply chain can provide their data, their documents, their information, which gets aggregated in one single place. Another example is a simple track and trace. And I won't comment too much about that because I mean, there are probably one million case studies over the internet. And another type of business solution is the one Marina was mentioning, compliance and sustainability. So we can ask companies to provide any type of information, such as composition of a specific product. And through this, we can have information such as the country of origin of components of things that are maybe just part of what we sell to the market. So suppose it's packaging, we can have the provenance of the of the carton that was used to make the packaging or of any other animal fiber or so on, or like that. Or even asking compliance, compliance, things like, for example, certificates. And so this is a this is type of business solutions we have implemented and we can do with our solution. Mari, if you can move to the next slide, please. Thank you. And what are the benefits we expect? The first one is to reduce time to market. What happens in most supply chains is that information has to go when you release a new product through several tiers of supply chain. So maybe you sell the product to the market, but you have a supplier that is doing something. And this supplier is working with their suppliers and those suppliers are working with different companies providing raw materials, components and so on. And many times when the new design is made, unless you are Airbus or Boeing or a super large multinational, you don't have such a system, such a very powerful PLM where all the different tiers of the supply chain are collaborating. And so what happens is that at the end of the day, because of versioning, because of changes in the design of the product and the supply chain may end up in a situation of a lack of alignment. So someone may be on version one, while others are maybe on version three at the end of the day, when the final assembly happens, simply components do not fit. And asking everybody to collaborate, we can be sure that products at the end of the day are more compliant. We can also reduce really cost because it's much easier to put together information and documents about a specific product and also improve margins because companies across the supply chain become more efficient so they can save time they were spending just to upload and download Excel files, PDF documents, images, making sure certifications were there because they just have to go point and click and find the document. Then we have also a screenshot of how the application looks like and how easy it is to retrieve the information. Mari, next slide, please. So this is an example of a thing that we have done in reality. This is for traceability of Iwer, as Marina was saying. So we have moved across several layers of the supply chain moving from the product itself to the companies that were actually manufactured to the suppliers of raw materials and components and to certification authorities. And this enables at the end of the day the distributor to have in one place all the information be technical data, be documents and so on. Next slide, please. Another example was a study we did for track and trace for leather for leather goods. This is something probably everybody, everybody has is quite familiar with. So it's not different. What is different is the way we implemented that we are going to see in a second. Next slide, please. And this is just a graphical explanation of how logically the solution may work. So suppose you have an wholesaler or a retailer working with three tiers of a supply chain, we can enable workflows and data and data processes, data exchange, document exchange across all those tiers. We can also enable thanks clearly to blockchain technologies, workflows with a second base, workflows which which end up end up being exclusively of, for example, tier two and tier three, which do not involve, for example, the final wholesaler. So companies get enabled and they can also do things which are not connected to the to the final product or to the final to the final merchandise. Luca, can I ask a question here on this? Sure. So what you're saying and I'm going back a couple of charts, it sounds like either you can have folks directly put data into this solution, or if it's already in some existing environment, some with database, whatever, or set of systems, TMS or WMS, etc. You can you can pull it out of there should should the yes. Okay, the exactly this is exactly what we do. So every company has information in their systems, as you were saying, we can take it from there, put it in the solution, it gets aggregated in one single place, which at the end of the day, gets aggregated to the final product in a standard scenario. And then it is available for the final for the final distributor or retailer. And the additional benefit is that all the companies involved in the supply chain get a benefit from this, because they have access to the system, and they can clearly see the data they are allowed to see. So it's there is a strong security implemented. But suppose there is something that is relevant for a company that is in tier two that it comes from a company that that is in tier three, they can get it right away, because everybody has access. So let me ask you a different question here, I mentioned earlier, I'm a big fan of standards. We have some folks on the line here also big fans of standards. Do you use a standard method? Or do you normalize it within your environment? Or how do you get everybody on a similar page of a data model? And then okay, I do my ideal world, I'd love a process model. Yeah, this is an excellent question. This this goes directly back to data and the worldwide standards that we have in 2021. So if there is something like UPC provided by GSI, just one, yes, we use it. If there is an ISO standard like for country, for country codes, yes, we use it same for currencies and and so on. Then there are some business domains, which are very, very, very specific to the industry. And in that case, we need to do data modeling, because there are some things that we end up finding out that do not even have any kind of taxonomy in the business. So we need to do that. So to get back to the point. Yes, whenever there is a standard, there is a global standard, we use it like we will see it in a second. The way the code that we use to basically present I where is the UPC or EAN depends on the way the companies want to use the layout of their screens of their of their dashboards. It's about the cases we're not that lucky. And we have to do data modeling because international standards are not there. And in addition to this, whenever there is something which we cannot directly refer to an international standard, like a unit of measure, as we were saying, or a country code or a currency, then what we do is in the product, we have a data layer which does conversion. So we define what is the gold standard for the specific for that specific industry. And everything gets converted to that to that gold standard that becomes the standard of everybody when working in the system. Okay, so thank you for the question, by the way. So this is a very simply out how the final result looks like. So it's a very simple dashboard. It's a web web web web interface. What the users get is a this super rich dashboard where as we were saying, the typical implementation is the final product is actually an aggregator of all the information that is provided by every company. So in production, like for this specific dashboard, I don't know how many columns we are managing. I don't know, it could be even more than 100. There is there are there is very sophisticated management of the aggregation of columns and of sections of the product because because clearly the information as as you go up the supply chain and you integrate layers and layers gets very, very, very rich and and that ends up also in a bill of material concepts and so on. But for the user, then it's so easy. So they need a specific certificate for that specific product, they just put a filter, go to the specific column, click a link and they can get the document in a very simple way. Or if they need data, they can quickly export it to Excel. We are also integrated with business objects for for for a data analysis. And Mari, if you can go to the next slide, please. We also what we also do is document management. So there is very strict interconnection between the product and the documents related to it. And we also in some cases, do some sophisticated document management with versioning and expiration dates depends on the type of document and and on the business and on the business requirement. But what I want to what I want to convey is basically this message of this ability to use blockchain and our technology as a very big way to aggregate information and put it in a synergistic way and presented in a synergistic way to the to the to the final user and to the customer. And I mean, sometimes being a lie, let's say, clearly, using a big example, but I think it's it's good to use big examples. I try to give the message that this is a bit the Salesforce. What we want to do is the Salesforce of products. Okay, so as Salesforce has the message of customer centricity, we give the message of product centricity, but product centricity centricity is more complex. It's more complex because the product data is a result of a collaboration of many, many companies. And so I think blockchain has enabled this this concept and we are trying really to achieve that and to go in that direction. Mari, if you can move to the next slide. Yes, absolutely. I would just like to add that we apply this solution to our industry, luxury industry, but it's absolutely easy to apply it to other type of industries like automotive or food and beverage. So that's also the the opportunity to use this solution everywhere in every industry where there are complex supply chains, complex process, something to change and to make possible a different way to collaborate. Thank you. Let's move on to the next page. I think that we're going to have also some technology at some point if I remember the presentation. Okay, yes. Okay, before we go there, before they go there, Luca, let's just give folks an opportunity if they want to buzz in here, we'll give them 15 seconds and see what questions they might have on the business solution side. I have one question. Can you hear me? So the mapping, what are your solutions to mapping? Yeah, basically, what we do as I was mentioning before is that we have an integrated mapping layer, which does basically the following. Whenever there is an international standard, we take data from the systems of the different companies and we map it to the international standard. Suppose someone is using a country code that is not compliant with the ISO format, we map it and we map it in our, let's say, integration layer, which is very light middleware. While, if there is no international standard that we can use, then we do mapping across against our libraries. There is a very powerful business concept in the system that is the library concept that is like the jargon, the vocabulary of the application for every field that is structured. So that is not a comment, for example. So we use, we have this powerful business tool that we call libraries and in the integration layer, what we do is we map every data against the library. So every company working inside the system for a specific field will always work with the library item. Right, so you have the library in a database and you shape files, you shape files to drive the technology. Yeah, geospatial. Correct. Yeah, just let me, since you said something, and I want just to give you a little bit more precise, what we do not keep libraries in a database. This, our solution has no database, apart from the blockchain and for caching. So what we do is we keep it in GitHub. And we have read this to do like the caching and the integration. The reason for this is that because we don't want to have anything persistent in our, in our software. So whatever data that is a business data is stored inside hyper ledger, whatever is like functional to the application stays in GitHub, just to be more precise. Okay. Private GitHub. Yeah, it's always private data, but is managed differently. So if it is, if it is technical to the application, like a library, it stays in GitHub. If it is business data, like, like data about the frame or weight or anything like that, it stays in hyper ledger. Right. Yes, it just for people who doesn't know this concept with me from very beginning, we saw this problem because if you think only about colors, every company is calling colors in different way. For me, maybe three is red for other companies like Rosso or maybe at X or something like that. So just for the colors, it wasn't so, so simple. So we started thinking immediately about, okay, how we can fix this. So the fact is that they're continuing putting their documents, their data, as they ever, as they always did, in the same way. And then our system is Is there a decompression? Yeah, is there to change this? So they don't need to change their way to work. And that's that's a great thing for for companies, because because they don't want to change their way to do their business. Good. Anybody else out there with any questions? Hi, yes. This is Alicia. I have a question. What you said earlier, Marina, you mentioned that the client can calculate the environmental profit and loss. Can you speak a little bit more to how they're doing that? Yeah, maybe, maybe, that side of caring, you can see how they calculate like how it's possible to calculate all the the monetary value of of profit and loss. But the fact is that for some components for some items, they're using like paper, which is recycled. Okay. Yes, sorry, I don't have or no. And so or maybe plastic, or they want to make sure that for some acetate, they use less water than past four years. So that's the way by mapping supply chain, you can see on certificates, you can see on documents how they make this product, because otherwise you can't have this information from your suppliers, you can even ask them, I mean, like, how many how many liter of use of water you use for doing that? Like, I don't know, I don't care. So in this way, it's possible to consult all these materials and to prove their effort is not just a word. We are green company. No, we can show that by seeing what our suppliers and their suppliers do. Is there a third party? Is there anyone going in third party to audit to confirm the data that those third party suppliers? Yeah, yeah, yeah. Yes, the the yes, the internal sustainability department of carrying is checking all that information. And to be even even more precise about about what we do. It gets a bit technical. But when you want to do the environmental profit and loss, you have to go at the very bottom of the product. So that's what we do. So we break down the structure of the product up to the raw material. And if it is cardboard, what we ask the suppliers that are there, let's say the manufacturer of the cardboard, because is directly involved to provide is the weight of the cardboard used for that specific product, the country of origin, and all the other technical aspect, which may be useful to do the calculation of the environmental profit and loss. Thank you for explaining that. That's very useful. Thank you. Good. Maybe also they're very good questions, folks. Yeah, thank you for those for those questions. Clearly, I don't want to I don't want to give you a wrong impression. So it is not it is not immediate. So it takes a lot of work to get there. So it's a lot of implementation and a lot of analysis, because clearly, you have to break it down really to the bottom. So, so bad at the end of the day is feasible and it's achievable. I could believe that Luca is yesterday, if anyone's familiar with green biz, they have a series of news letters, Lisa, you may be familiar since you asked that question. They have a new newsletter, basically, Green Finn, I think it's called, they just started yesterday. And one of the two things that they pointed out as the top storylines are going to follow is in green business, a big sustainability media organization, the two things are, they're two top storylines were around standards and to around data collection. And exactly the kind of things that you guys are talking about, and Alicia, you asked about in the difficulties associated with that. So it's actually something for those of you out there, I'm near and dear to my heart, and I'm happy to talk about it. So with that, let's go back here to Luca Marina here. Yeah, yeah, yeah. So I will click quickly move on to the technical side. So from the beginning, our, let's say there is one big concept that is behind our technology is that we did not build a gigantic system that is on top of a distributed system. So there is there is no beam off, but there is a different technological concept that is a distributed application. So from the beginning, what we wanted to do was a conceptually light application that is given to every player. So suppose we have 10 companies, 15 companies collaborating, they will have their hyper ledger peers, maybe not all of them, depending on the size of the company. Because we also enable sharing peers, which is a concept that maybe we can, we can discuss separately. Luca, just wait, when you when you mentioned a hyper ledger ledger, could you specify what parts of hyper ledger you're using? Yeah, we use fabric. We, we used to use in the very beginning. Also, you made you may remember that composer that we use as a rest server. But we later we dismissed that and we developed our own technology also in that area. So basically, we use fabric. Okay, great. Thank you. Thank you. Do you use any of the other projects out of hyper ledger is everything fabric? No, we are using only fabric at this point in time. We are also looking into the other into the other projects at this moment. But the only one that we are using in production is fabric. And that's quite fine. Thank you. Just so everyone has it is clear in their mind what we're talking about here. Okay, thank you. And so, Katie, I was to create those, those applications, distributed application that we we give to we provide to every company. And those applications do many things like they do user management, they do caching, they do they manage notifications, they manage the data data mapping, the data mapping layer, they manage imports and exports, they manage rest API's and and so on. So you can think about this as a fully packaged front end and back end application, which is able to speak at the same time with fabric, and with customers providing a web interface or webbooks or, or APIs, and at the same time, connect to GitHub for libraries and clearly for the code repository, which is I think quite basic, but also to Amazon and Asia, where we store the off chain off chain files, which are clearly asked and say when we save the ash in the blockchain, but we keep the we keep the file outside, we integrate with we integrate this with, for example, with Azure Active Directory for user management, and also for the Key Vault and and so on. So, so in the nutshell, this is our technology. So is a new concept of business application that is not that is not a single large piece of software is a lean software that is provided to each to each company. Also, the configuration of each application changes depending on the profile of the company. So depending on what kind of company they are, we divide them into, let's say, sets or buckets of companies depending on the typology, they will get we'll also get different, different, different functionalities and clearly each company has its own configuration for the for the data layer. Okay, Mari. In detail, this is this is what our software, which we call front does. So it's basically, as I was saying, identity management, the user and machine interface, it integrates with a fabric does all the data layer manages the security, which is super sophisticated is completely proprietary. It's, it's based, it's completely written in chain code. And it's interesting. I mean, we don't have enough time today, but maybe there is another location we can talk in detail about how we implemented security, which is not at organization level. It is at user level. So it's quite, quite sophisticated actually. We it also manages notifications. Because clearly when you have cross company workloads, you need to let them let people know that something is happening because clearly it is a lot of things happening to the blockchain. And we also so we capture the events and we route them to the appropriate companies, depending on on some settings. And it does dashboarding and the cash in there was I was mentioning, for the staging part of the data, which is a part of our processes. And next slide. Next slide. So just to make you understand our business model works, or maybe, okay, I can go on with that, Mari, if you're okay with that. Okay, I think she's basically this is a this is Yeah, this is the way we work on the business on the business side. So there is a cloud subscription for the software. Nothing is companies and cannot to install anything, even if we support the hybrid scenario. So if if someone is is very eager to have his software in the data center, it is it is possible. We provide professional services, clearly for developing the business case, and the business scenario design for process design and so on. We provide support, which is very important, because because as we see that when the networks tend to extend, users need a lot of a lot of assistance. Just just maybe for how to use or for small bug fixing and so on. And another thing that we do is is run the applications, because what we saw is that most of the companies really do not want so much to run to run hyper ledger or to run our instance of the system. So we help them run running those, those systems in their cloud or in their cloud, in their cloud subscriptions. And just to say about cloud subscription that cost depends on how, how big the company is why this because we wanted to allow also small companies to be part of this supply chain revolution. And it's obvious that they don't have the same wallet for ITA projects as big multinational companies. So that's why this cost depends on on on how big the company is in supply chain. Yep. And so just so I will. So almost the end of the presentation. So a few, a few remarks. Next slide. So why we think I mean, we have a good value proposition. First of all, I mean, this is not the custom, custom development. So we have created a product that we enhance, improve and evolve on a daily basis. So I think there is a lot of value with this. So companies know that they are not embarking into something that would become very difficult to maintain in time because the software is constantly managed and improved by us. We we also help companies manage their risk because we have success stories. So we know how to help small and big companies managing this type of this type of situation. And also we also we think we can also avoid dead ends because we have seen many situations where there are complexities which may lead to project failures. Like mentioning I would like to mention a few of them like reasonable UI and UX. So the application has to be usable as to be fast. You need to provide the tools that the users need to work on a daily basis like Excel integration that is so important like filtering like sorting like being able to personalize the dashboards in the way that that are convenient for them like security, which is a super important as to be super, super detailed so that everybody can see only what they are allowed to see performance, which is at the same time very important. So we have developed an entire proprietary layer so that when we provide data so when our application reads data it does not read directly from from fabric but is reading from a cache stage from a cache layer which is helping a lot in terms of performance and is also floating the blockchain from workload that is not necessary. Like also studying but this is clearly I think a pretty pretty understandable for everybody doing a good design of the blockchain or the architecture so making it making it reasonable and making sure that the software is stable and that integration works that the vocabulary is is is clear for everybody and also because our company is reliable we've been pretty successful so far and we have investors who have trusted us and have provided the funds to be sure that we can we can be resilient over time and we can also be resilient for for our customers. Okay our presentation is finished. Thank you a lot for your attention for being here and seeing our solution and our ideas. Great Marina and Luca thank you this was very good. Appreciate you sharing also some of the ideas here. I have a quick question here maybe if you could describe let's take the carry examples that you talked about that. How did it was this kind of a top-down they kind of said hey suppliers you need to get on board with this or was it more of a holistic type of let's work together type of thing and then that kind of gets into the question how many nodes are there how are they doing the governance of but it's had a change there. Yeah okay I will give you the first part of okay good thanks. I think that is really unrealistic to think that people like 15 companies will say oh let's work together it's romantic. I could dream can't I? Yeah yes but things can start also slowly easily just with a couple companies and then that's the power of this of this solution that it's so flexible so you can you can in every moment you can add other companies add other suppliers so it's not necessary to start together. Actually maybe it's more efficient to start one by one just adding one reality after after other and it just changed some processes but it's it's so easy easy to add or to to just cut some some of these companies. Okay so it kind of started started from caring and then it kind of expanded out is what you're saying. Yes okay maybe maybe Luca will be better. Yeah that's good. Yeah yeah I mean this is this is this is exactly the good explanation it started from caring and then it spread out and clearly smaller companies in the beginning were having let's say more and more time understanding the benefits but then they they gradually understood in the course of action because they were they were actually understanding that their own let's say internal systems and processes were not so let's say robust and that that was a great opportunity to implement to improve them. Some of them are also using the solution as a document management system because some smaller companies didn't have any any of that so it's so simple now for that. Suppose you have a supplier uploading a catalog of metal components like I don't know something in metal like screws or anything like that it becomes very easy to use the system to aggregate all the all the documents and the information for that. And then Tom I apologize but I forgot what was the second part of the question. Number of nodes in the implementation. Yes this is a great question so now we're running with five nodes of fabric so there are three nodes for the most important companies one is for the certification authority and one is a shared node and we use this concept of shared nodes because because clearly we have implemented a very strong security layer in our application on top of that that is as I was saying is anyway written into the blockchain so it's not it's not easy to let's say go around it because all the rules are written into the into the chain code and so we use the concept of shared nodes so in order to let's say avoid a growth of the network that is too costly for the companies. Okay good thanks. Luca you mentioned certification first about like a plus for a company for example we have DICE in this consortium and they are producing lands okay you can imagine what what it means for a company to have the possibility to ask a certification for every single land land just on there or on our system without PDF without meals without you know because a lot of times as info for for example for American for American market market market yes they need to provide this bullet test this is a special testing where the metal bullet is falling on land yes on lands and if this lands remains whole they can sell this this hardware in America so many many times they they needed to to make another test because they lost that that certification or they don't remember who managed that or sometimes there is no anymore the person who worked on that type of certification and you lose all the documentation so for them they understood that there are a lot of plus for them that's why companies wanted to to be part of this of this measuring system good thank you what other questions out there folks from we're coming we're coming to the top of the hour so get your questions in anybody okay well hearing none I think we'll we'll stop here a little bit beforehand but that that's great Rena and Luca thank you very much for presentation I I see Kevin's thoughts I see Ben's thoughts here in the chat that like the session here said great session so thank you everybody thanks for sharing with us the folks that are on the phone here please take a look at my email from a little bit earlier to the to the to the SIG email server basically hey we're still looking for input on where do we focus this group here for the new year here 2021 that was the subject of the last call and Mark and I are looking for your input to decide where we're going to go in addition to doing webinars like this one here so with that thanks everybody enjoy the rest of your day whatever it looks like otherwise in your place and I look forward to seeing you again a couple weeks from now thanks everybody thank you thank you thank you thank you buddy thank you have a nice day you also share