Thank you for all coming and braving the weather. The clock is ticking. I have a little clock here staring me down. So what I'd like to talk to you today is not how to make a command line tool. Like, we all know how to do that. Go does it very well. What I'd like to talk about is how to design, intentionally design a command line tool that is easy for people to use, and people actually be willing to maintain and contribute to so that it's not just your problem to maintain for the rest of your life or whatever company or project you happen to work on. So when I talk about a tool that people love, what does that mean? Because it's not just touchy-feely. I want to make a command line tool that's predictable. I want a tool that, if I learn one command, or I already know how to use another tool within that ecosystem, I can guess. I don't need to go to the help text or the documentation. And I can probably figure out what the other commands look like, and I'm able to just use muscle memory and feel like an amazing person and just use the rest of the commands all by myself. Another design goal here that we're going to cover is I'd like to make task-oriented commands. I'd like to understand what it is that person who is using the CLI is doing and make that task easier, not just an HTTP put, post, patch, whatever, but a series of steps that may involve ugly things. For example, making key pairs and posting it somewhere and then signing something and doing all sorts of random things that you may need to do and turning that into one simple command. Another design goal that we're going to cover today is how to make a command friendly both to an interactive session where you're slowly, painfully typing and pressing back space a lot, and then also when you're automating something in a script. And then another thing is one of the things that I do, just in Women a Go and Open Source in general, is I work on command line tools pretty often, and I am always onboarding new contributors. And the reason why is because new contributors are really attracted to command line tools. Instead of jumping into, say, the control loop, which touches like 16 different things, and it's really gnarly, and the tests require a lot of knowledge, usually if you jump into a command line tool, you need to know how to talk to an HTTP server, and you need to know Go. So it's pretty easy for someone to get into. So if you do things, I'm going to say right, but whatever, you do things good enough, it's a great place to get new contributors into your project and then bring them into that ugly control loop that you may have. So that's what we're trying to do here. So I did say I did a lot of command line tools. Real quick, I'm going to be mentioning them and mentioning the names. So I just want to go over real quick what they are, so you know what I'm talking about. I wrote the Docker version manager. It's called DVM. You may have heard of DEP. I'm sorry. That was me. Kubernetes service catalog. The CLI for that is SVcat, a brand new one that I'm working on. It's related to Kubernetes and Cloud Native. I don't know what Cloud Native is, but it has to do with Cloud Native application bundles. And it's called Porter. And I made that wonderful little emoji icon there, and I'm so proud of it. And like Apple pie-summy, because I don't hear a lot of these emojis, but whatever. OK, so this is what I'm going to go over as far as what it takes to make a CLI. We're going to talk about command design, what frameworks I'm going to tell you to use, how to structure your packages, dirty word dependency injection. I hate using something like that. I feel like I'm Java, but whatever. We'll get through it. And then how to write tests. So the very first thing I want to talk about here is how to design your commands.  And you're going to have to argue for why you need to do it differently. And you're probably not going to win. Inertia wins over all other arguments. So don't let that be one of the arguments kind of on your pro-con list of why you want to change things. So one of the very first things I look at is selecting a grammar. So I'm actually from the US, from an English school. So I don't know what grammar is, but I'm going to try. OK? So again, native English. So subject, verb, noun is usually what I'm used to when I see a command line tool written by someone who knows English. So it may be like kubectl get services or helm list, something like that. That's what we're talking about when we're saying grammar. What's nice about having a grammar and picking it up front is that when you read it to yourself, it sounds like a sentence. You're reducing that cognitive overload or just that burden of going, repeating it to yourself over and over and over again so that you can remember it from going to the documentation to typing in the command line. Anything you can do to help someone reduce how often they're copying and pasting and actually learning these commands and being able to come up with them themselves is someone who's going to use that tool more and maybe like it a little bit more and not curse you out. So that's what I'm getting at with grammar right here. Another piece about grammar, though, is that when you're selecting these nouns and verbs, especially, is you want to be consistent. So I'm going to pick a helm because we're going to helm team now. So one, that's really cool. I just started this week. That's exciting. Is that you want to be consistent. Helm is not consistent. It's helm install. What is the command to remove something? It's helm delete, not uninstall. That messes me up every single time, and I have it aliased. That is an example of being inconsistent with your grammar. And that is something that is going to cause people trouble every single time they use your command line tool. So you make a decision about how am I going to make. You make a decision about how you're going to make decisions. So you can argue with your coworkers in PRs a month from now when they want to add a new command. You're not figuring out here all the commands that we may have in the future, but you're trying to figure out how are we as a team going to make these decisions. So it's easier to just make them quickly and justify them and move on so that as a whole as we add new things, it doesn't start looking like beautiful Katamari balls. If you don't know what that is, it's a really great video game and you should play it. So the other thing you're going to want to look at is understanding the ecosystem that you live in. Very few of us get to write a really cool new tool and then not have to worry about what other tools people are running alongside it. So for example, SVcat, which is a service catalog tool, always gets used next to Qubectl for Kubernetes. And I don't really get to pick and choose how that works. They made decisions. It looks like Qubectl get services. And they made decisions about what verbs are going to use, what they're called, what flags they're going to use. They use dash dash output, not dash dash format. This is what a printed output looks like, et cetera. I can't change something just because I disagree. I may have aesthetic differences or very held opinion, like strongly held opinions. No one cares how I feel about it because if I change it for change's sake, I've made your lives harder. So SVcat looks very similar to Qubectl for anything that's related to it. So for example, SVcat lets you list brokers. No one cares how brokers are. It doesn't matter. But the command is SVcat get brokers and it's guessable. It's predictable. Now, I have a couple of commands that look nothing like Qubectl. I have SVcat sink. And there's no noun after that. That's because sink means something very specific in my domain of service catalog. It doesn't matter what it is. But because people who are in my world of SVcat kind of understand that domain, it makes sense to them. Now, I was able to make that decision. It's additive. But I don't get to go back and change things underneath. I need like shared understanding. Cool. Now you all hate service catalog, just like me. So we can move on. So the Docker version manager, DVM, is a version manager. There's 12 version managers out there. Maybe who knows? So we copied the Node version manager, NVM. And because it kind of did the same thing, we reused all the same commands and patterns and how it sourced variables, et cetera, for the most part. Because we wanted to drive home how you would use it and it would look exactly the same. So most people are going, wait, jerks. It doesn't work at all like Glide. Why'd you do that? It's because it doesn't work at all like Glide under the hood. We didn't want people to assume that and think it. So we went out of our way to make sure that if you use the command line tool, we didn't accidentally encourage these biases of going, oh, yeah, it should probably work like Glide. All the commands are the same. Nope. So we went out of our way to make sure that we didn't use the same verbs, and nouns, and flags, and things like that. So that's enough talking. Let's have cute emojis. Actually, that's not an emoji. I learned this is an emoticon. It's a very important distinction. They're really hard to type, though. They look cool. That's a shrug. But I always have to go to Google. So I want a tool that helps me make these. So I'm going to make a tool called a moat. And I'm going to have a verb, add. And the noun will be a emoticon. So I'm going to add one called gopher. And I'm pretending that's gopher. It's probably not. You can tell me later it's not. That's fine. So I'm going to be able to add a gopher. And I'm going to be able to remove one. I'm obviously not going to remove gopher. So I'm going to remove anxiety about my talk. OK. And then I want to be able to add a repository. So here's a new noun that I'm introducing. I'm reusing that verb. I'm adding a noun, so I'm being consistent. And I also like to have a list of all my repositories. So one of the other tenants that we talked about a little bit earlier, though, was being nice to scripts.  So let's also add dash dash output JSON and let people be able to do this. This will just help as they try to automate my CLI. I'll probably have this on a bunch of my different commands, actually. So now I'm going to start doing something a little bit weird. And everyone's like, wait, Caroline, I want to tell you you're wrong. Just wait. You can tell me I'm wrong later. But I'm also going to have one called a moat list. And I'll list out all the different modicons I have. And I'm going to have one more. And this is the one I wanted the whole time, which was shrug, burp, hug, or whatever it is. It'll copy it to the clipboard so I don't have to know how to make these elaborate wonderful modicons. All right, now you get to help me. I broke with the grammar, the convention. You notice that for list and shrug, I dropped an noun. I dropped a noun and a verb. I just, what I do. And the reason why is I made a judgment call. And I said that it was more important to be true to my domain and the task that the user was trying to do, which is as quickly as possible, copy that darn a modicon to my clipboard and type something cool and then put it in Slack, which is really, that's all I would use this for. Then it is to follow some holy tenets of, I must use subject, noun, verb. What you could do is backfill and have those longer things. So for example, a moat list, a modicons. But the other thing to look at is look at the command that I'm using. It's a moat. The command almost kind of tells you, this is the domain I'm working with. Heck, I mean, you add a couple more characters. It is a modicon itself. A lot of people will get pretty quickly with that shorn in thing, what it is we're dealing with anyway. So again, it's something that you get to pick as a team what are the rules you want to break. So again, moving on though, one of the things you really want to do is you want to make tasks easier. All too often, I see people writing a CLI for the first time. And what they do is they wrap the HTTP commands calls that are there. And it basically looks like a CodeGen client.  Anyone can write CodeGen and go, we'll just do it for you. That's not helpful. We want to add that human layer to it and accomplish tasks for people because otherwise you're going to see 30 different artisanal forks that add in this stuff for you. And you've missed this opportunity to help everyone out. So let's just talk about frameworks real quick. There's a whole bunch of different ways to deal with command line tools. The most popular ones out there, though, are really easy to work with and are the most testable. I've worked with CodeGangster and a couple other ones, and they get the job done. Not saying they're bad, but some of these are way more testable. So I'll just thank Steve, and I recommend you use some of these. I'm not going to tell you how to use them because I've got nine minutes. So instead, I'm just going to call out what these frameworks are and what you would use each one for. So Cobra is the first one. And there's a whole bunch of code up there. The code that matters is that we're initializing a new Cobra command. And then in use, we're saying, what is the command that Cobra should be taking over and helping with? So in this case, the command that it's going to be defining is for Helm. And it's built out a bunch of different things. We define the help text. We're defining the description. So that's what short is. That's a short description. It gets printed out of your type Helm, and you give up, and you don't give it any other options. You can add in subcommands. So I'm defining Helm install and Helm list. Helm's huge. There's way more, but we just have a slide here. And then the other thing Cobra does is it basically takes over your main because it'll do things like print out the help text if people do things wrong, if people type in Helm, all the different commands, and then there's an error. It'll print it out. It'll handle printing out all the different output that came out of your command, any weird validation, et cetera. So this is what it looks like when you wire it up. Yeah, in Cobra, we trust. Cool. So Viper is the other one I really like. I like to go sting in the Viper. I don't know. It sounds cool. And Viper can do a whole bunch of different things, and you can totally use Viper in ways that make your life super hard. But what I always like to bust it out for is when people get in arguments about Toml versus JSON versus YAML versus HCL versus, I don't know, whatever, come out since then. And so what this lets you do and what this code snippet does is that I can have in a directory a configuration file for my app, and it can be a Toml file, JSON file, whatever, a huge list of whatever it wants to be. And I can give Viper just the first part of the file name. In this case, this is for duffel, which is another random CLI I work on. I'll just give it duffel. And it'll go through the directory and look for duffel.toml. It'll look for duffel.json, duffel.yaml, whatever. It'll go through all of them until it finds one. It knows how to parse. It'll load it up into memory. And then un-martial it onto a structure for me. Now, the next thing you may have noticed is that my structure looks a little funky. It doesn't say YAML or Toml or whatever. It doesn't have six different attributes on it. It just has one called map structure. And that's how it gets to handle all of them at once. So let's me write a tiny piece code and only decorate it in a generic way and then be able to handle anything. And then hopefully my team stops arguing about what type of code they want to use. I did say that you can totally shoot yourself on the foot with Viper, mostly from the standpoint of how you use it. So some people don't like the fact that you can read in your configuration environment from anywhere. You can do Viper.get and then read in random configuration options that came out of your config file from environment variable really deep within your code. And that means anyone who's using your code has to have Viper. You can get weird dependency things where anybody who uses your code needs Viper. So just be careful when you do that if you're a library, because people may come after you. They have me. Maybe let's just put that way. So it used to be that I just used Cobra. And then I was like, now I love Cobra and Viper. And now, as of three months ago, Affero, which I don't even think is a lizard or a snake. I'm not quite sure. Someone told me later why he picked that name. But what's cool about it is actually super subtle. It lets you stop using hard-coded IOU till and be able to swap out your dependency in the file system with something that you can mock out and hit something else entirely. So instead of doing always IOU till that read file or walking a directory tree or anything like that, I can swap it out with what you see as FS. It could be in memory database or in that database file system that I mocked out in one of my tests. It can actually hit more exciting things, like HTTP things, stuff like that. Doesn't matter. It's easy to swap out. And that's what I want to stress right now. When I look at tests, we'll see why this is fun. So all of this was setting up, how do we make this testable? We've made this nice for our users. How do we make this nice so that we're going to have to be the only person on the team who maintains this?  I'm saying make it least two. One, where all of your dependencies on Cobra and Viper and Affero live. And one, where all your logic lives. And it kind of maybe doesn't even look like a CLI. So wire in one place and write like it isn't even a CLI in the other. So under CMD, that's what your main is. Keep this as tiny as possible. Just a reminder, anything that's in main can't be exported, can't be reused. Usually it has funky, like anonymous functions, deeply connected to Cobra. And you have to know Cobra in order to test it. And it's not easy to test. No one can reuse it. And no one really wants to force everyone to take weird dependencies on CLI frameworks in order to use one cool utility function. So put all your cool stuff somewhere else. Dave Cheney would say not PKG. I don't care. Put it wherever. And what I suggest, either through structs or functions or whatever, do one-to-one mapping. If your CLI has a command called do the boogie woogie, I don't want to see a function called do the boogie woogie somewhere in package right here. And the reason why is because someone else who wants to reuse your command line tool and then do really cool things with it, extend it and bake it into their own, they shouldn't have to copy and paste your code and recreate it. They should be able to take one of your functions out of this package and be able to use it. Additionally, if I want to test things, I don't want to have to piece together what happened in that CMD package. I should just have one function inside of PKG with corresponding tests for it. It just makes it cleaner and easy to use. And just like Bob Ross says, happy little packages with happy little tests for everything. If you are doing code gen or you're doing band-aids and wrappers and hiding really how awful your API is designed, again, this is where it all goes. So yeah. So when I say we want to put wiring inside that CMD package, this is what it looks like. If you look at Porter, which is the latest command line tool that I wrote, everything looks like this. And it's very boring. There's very few tests because it's really hard to mess up this wiring. For the most part, they're just tests for validation. And it always calls out something else. So for the validation, you can see it's just calling out to the printer package. And for the implementation, again, it's calling out to the printer package. And then it's calling print mixins. So if I want to test something, all the tests are actually in those other packages. And all I need to do is make sure that in CMD, I wired it up. I'm going to go through really fast on this. But one of the things that's really important that I said earlier is that you want to be able to treat that second package that doesn't have all the wiring that has all just the logic for your CLI. You don't want to treat it like a CLI. And you want to just do the right test for it. Like you normally write tests for anything else. And one thing that really helps with that is to be able to inject things like the console. So you can capture the output and go walk out printed. Or be able to inject things like the file system. So you go, did I make things right? Did I put in a config file? Can I mock in standard in? Stuff like that. So I like to make something called contacts. And again, that's not the right name for it. I don't care. But that's what I call it. And I also like to do things that eventually turn out to making, I call it an SDK, whatever. It's essentially a structure that replicates my CLI. But doesn't have any of the CLI frameworks associated with it. So it's called Porter here. And it's got everything with it. And then you can just use it like your CLI, but 100% programmatically through code. And this is what it ends up looking like. And then you can write your tests.  I tried. Tried, everyone. Thank you all for your time. Appreciate it.


The hospitality industry is increasingly aware of the potential benefits of integrating nature-based solutions into their operations to reduce their environmental impact while maintaining or improving service levels. One such solution is constructed wetlands, CWs. These systems use natural processes to treat wastewater and have been shown to be effective at removing pollutants from wastewater streams. Studies on CWs have been conducted in Europe, Asia and South America and have demonstrated high removal rates for various contaminants. Additionally, CWs are compact and require less space than other wastewater treatment technologies, making them ideal for applications in the hospitality industry. This article was authored by Sarah Justino, Christina S. Cicale-Harrows, Paula ML Castro and others.


Hello, it's Waylon Chow. This is Secured Lending Module 5, Part B. In this part, we will look at secured loans and security interests, specifically nine different types of security interests. So we've already looked at the use of guarantees to make a loan safer for a creditor. Another common way of making a loan safer for a creditor is using a secured loan. So there would still be money that's lent from the creditor to the debtor, and the debtor is still making a promise to repay. But in addition to that, the debtor is providing a security interest to the creditor over assets that are owned by the debtor. So those assets are called collateral. There are many different ways of structuring a security interest in order to accommodate various legal, accounting, or practical business issues. We will look at nine different types. First, the pledge, a child mortgage, a real estate mortgage, a conditional sale, a consignment, a lease, an assignment of accounts receivable, a general security agreement, and a Section 427 Bank Act security interest. The simplest form of security interest is called a pledge. So let's go back to our simple example with me needing some lunch money. So may I borrow some money for lunch? And you say very kindly again, yes, sure, here's 20 bucks. So the 20 bucks goes over to me. And then I say, thanks, I promise to pay you back next week. You'll hear. I take my shoes in case I don't pay.  So I use the money to buy my lunch and I eat it. Then next week rolls around and I say, sorry, I can't pay you back. So now you say, okay, I'm selling your shoes on Craigslist. So you're able to sell them and you get money for them and you keep that money to pay off the money that I owe you. Now that seems to work fine, but you know, think though, what's wrong with this transaction? It's a practical issue here. What's wrong is I have no shoes to wear while the loan is outstanding. I have to walk around barefoot. So here's the general description of a pledge. So we have the debtor and the creditor. The debtor does not have use of the collateral during the loan because the collateral is given to the creditor who has possession of it until the loan is repaid. So the collateral is given by the debtor to the creditor in exchange for the loan money. And the collateral, the type of collateral that is used is personal property. So it's not real estate. It's some kind of personal property. And it could be something like stocks, bonds, jewelry, precious metals, or life insurance policy. And once the loan is fully repaid, that collateral is returned by the creditor to the debtor. And if there is a loan default, just like with my shoes, the creditor can sell the collateral and apply the proceeds against the debt that's owing. Now the key here is that this type of security interest, a pledge, works only if the debtor does not need the use or possession of the collateral during the loan. And that's a practical issue. That the collateral has to be something that the debtor does not need the use or possession of during the loan. So that's why giving my shoes as a pledge, practically speaking, does not really work. But if you use something like a stock that you own or a bond or jewelry or precious metals or life insurance policy, those are things that you own. But you don't need to have them in your possession to have use or enjoyment of them. So those types of personal property would work for use as collateral in a pledge. The second type of security interest is called a chattel mortgage. And the chattel mortgage can be used to solve that problem that we had in our example with the shoes where I don't have the use of the shoes. So let's go through that example, but this time using a chattel mortgage. So here, me and that's you. I'm asking to borrow money again. And you're willing to give me the $20. $20 goes over to me. And now I say thanks. I promise to pay you back next week. You can have a chattel mortgage over my shoes in case I don't pay. So instead of giving you possession of my shoes, instead I'm giving you a security interest called a chattel mortgage. So the money is used for my lunch. And then a week later I say I can't pay you back. So now what you do is you repossess my shoes. So you take my shoes. So when I'm in default, you take my shoes and then you go ahead and sell them on Craigslist. So you convert them into money to pay off the debt. So the key here with the chattel mortgage is that I still get to wear my shoes while the loan is outstanding. So we've solved that practical issue using a chattel mortgage instead of a pledge. Here's the general explanation of a chattel mortgage. So we still have a debtor and a creditor. So the title of the personal property that's being used as collateral is given by the debtor to the creditor in exchange for the money that's being loaned. And when the loan is fully repaid, that title is returned by the creditor to the debtor. If there's a loan default, the creditor can seize the collateral, or in other words a repo or a repossession, and sell it to repay the loan. Similar to a chattel mortgage is a real estate mortgage, except now the collateral is not a personal property or a chattel but is real estate. The type of real estate mortgage that we'll be describing is one that is under the Ontario land title system, which is the predominant system in Ontario. With a real estate mortgage, the debtor is also called the mortgageor, the creditor is also called the mortgagee. So a loan is made by the creditor, or the mortgagee to the mortgageor. In exchange for that loan, the mortgageor provides first a personal covenant promising to repay that loan. A personal covenant is just another way or a legal way of saying a contractual promise to repay that loan. What is also provided in exchange for the loan is what's called a charge that is registered on the title of real property. So the land title system in Ontario is a registration system where the ownership of property is registered, and in that registration system you can register a charge against the title of a piece of real estate. Arising from this real estate mortgage, the mortgageor, the debtor, has the right to retain possession and use of the real property that's being used as collateral during the term of the loan. The creditor, the mortgagee, has this charge, which we've mentioned, that is registered on the title of that property, and that charge is only removed or discharged once the loan is fully repaid. So the significance of that charge being registered on title is that anyone who looks up the registration of the property will see that that charge or that mortgage is there, and if anyone buys the property with that mortgage still registered against the property, with that charge still there, they will be taking that property still being subject to that mortgage. A conditional sale is often used where there is a sale of an asset by a seller to the purchaser with that seller providing financing for the transaction. So the creditor is also the seller and the debtor is also the purchaser in this situation. On the sale of the asset by the creditor to the debtor, the debtor will take possession of that asset and the creditor retains legal title of the asset. Once there is full payment of the purchase price or in other words, the debtor or the purchaser has made all of the necessary payments so they could be monthly payments after all the monthly payments are done, the title of the asset is transferred from the creditor to the debtor. If there is a default, for example, the debtor has missed one of the monthly payments, the creditor has a legal right to seize the collateral and sell it to repay the loan. One exception is if the debtor is a consumer and at least two thirds of the price has already been paid, in that situation the creditor cannot seize the collateral without a court order. So this protection is provided by the Ontario Consumer Protection Act. Let's say you have some old clothing that you want to sell at a secondhand clothing store. So what you do is you bring your clothes to the store and you can sign your clothes to the store. So what that means is that you give possession of your clothes, the goods, over to the store. The store we call the consignee and you are the consignor. You give possession but not the title of the goods. When the store, the consignee sells the goods to one of its customers. It gives a portion of the proceeds it receives to you, the consignor, and at the time of the sale, front by the consignee to the customer of the store, the title of the goods at that time is transferred from you, the consignee, to the buyer of the goods. And that's what we call a consignment. A lease of a car or any other type of vehicle is not as simple as many people think it is. It is not just making monthly rental payments in order to get the use of the vehicle. What it really is, it is a secured transaction which is used to finance the purchase of the vehicle.  So what a lease transaction is, it happens in a few steps. The first step is the seller of the car which is usually the auto dealership sells the car to a lease finance company. So if you're buying a Honda from a Honda dealership, the Honda dealership is selling the car not to you, the customer, but they're selling it to the lease financing company who we call the Les Sore. And it's the Les Sore that owns the title of the vehicle during the term of the lease. And then the lease agreement is between you, the customer, the Les E, and the lease financing company, the Les Sore. Under that lease agreement, the Les E is obligated to make regular payments, so they could be monthly payments, let's say, during the term of the lease. So if it's a three-year lease, you're making a monthly payment for a term of three years. And in exchange for those payments, you get to have possession and use of the vehicle. And then at the end of the term of the lease, so if it's a three-year lease after three years, you are given the option to purchase the title of the vehicle by making some kind of lump sum payment. Businesses that sell to its customers on credit will generate accounts receivables. Those accounts receivables are considered to be assets that have value. As such, they can be used as collateral for loans or lines of credit. The security interest that involves accounts receivables is called an assignment of accounts receivable. What that involves is that the creditor, which is usually a bank or some other kind of financing company, will provide a loan or a line of credit that is secured by having the accounts receivables of the debtor assigned over to the creditor. So while the loan or line of credit remains in good standing, in other words, as long as there's no default, it's business as usual. The debtor will collect its ARs in the usual course of its business. But if there is a default, the creditor takes over the collection of the ARs. A quick quiz question. Please pause this video so that you can read the question and consider the choices. Please feel free to look at a previous slide. Pharaohs carries on a wholesale electronics business. He sells to his customers on credit, giving them 20 days to pay. Pharaohs has applied for an operating line of credit and his bank has asked him to assign his accounts receivables to it as security. Which of the following is true? The answer is B. Pharaohs will be permitted to continue to collect his own receivables and carry on his business as usual unless he defaults on the line of credit. A general security agreement or GSA allows a creditor to take a security interest over all of the assets of a business. So the way it works is that the creditor provides a loan or it could also be a loan of credit to the debtor. And that loan or loan of credit is secured by a security interest that is attached to all of the debtor's current assets and also after acquired property. So assets that they acquire in the future will also be covered by this security interest. And the way the general security agreement is set up is that it still allows the debtor as long as there's no default to freely use, sell and buy assets in order to carry on its business. But if there is a default the creditor will have the legal ability to seize all the property owned by the debtor at that time. So since all the property is basically all the business the creditor has the ability on default essentially to take over the whole business. And that's what people typically call a receivership. The section 427 bank act security interest as the name suggests is only available to creditors who are banks that are regulated by the federal bank act. And also this type of security interest is also restricted as to the types of assets that it can apply to. It can apply to goods and retailers goods and wholesalers, goods and manufacturers and mining and forestry products. And then there are also goods or certain assets that this type of security interest cannot apply to. It cannot apply to consumers assets and assets of most businesses providing services. The main advantage of using a section 427 security interest is that the federal registration that's required can cover a debtor's assets wherever they are situated in Canada. In contrast, if we need to register under personal property security legislation it must be done in every province in which the debtor has secured assets. So if they have secured assets in ten provinces we need to do ten different provincial registrations. And this type of security interest is usually taken by a bank if it's possible to take it, if it's eligible in a particular situation, but they'll take it when they can in addition to other security interests namely the provincial personal property security interest which we will discuss in the next module.


This is the VOA Special English Agriculture Report. America is the world's largest food exporter. But the worst drought in half a century is hitting corn and wheat harvests. The drought across the Central United States adds to concerns about world food supplies and prices in the coming years. Experts say by 2050 the world will have to produce at least 60 percent more food to feed a population growing bigger and richer. China, a major food importer, is looking to producers around the world to guarantee future food supplies. China has invested in food production in Australia and New Zealand. A new source of supply is Ukraine. Ukraine was known as the bread basket of Europe because of rich corn and wheat harvests a century ago. Galina Kovtok is Chief Executive of Ukraine's largest agricultural business, ULF. She predicts that within a few months her company will be approved to export corn to China. That will make Ukraine the first country outside the Americas to do so. ULF will soon have almost 2 million tons of elevator storage capacity as it prepares for the Chinese market. Chinese money is financing the building of six grain elevators. But the company's equipment is largely American, including half-million-dollar John Deere combines to harvest wheat. ULF's grain production per hectare is now halfway between the Ukrainian average and the high yields of the American Midwest. But farming depends on the weather. Across the Black Sea area, in Ukraine, Russia and Kazakhstan, drought this year is pushing harvests down 15 to 20 percent. Traditionally, the Black Sea region is the main source of wheat for North Africa and the Middle East. But this year, on the supply side, Russia may have to suspend exports. And on the demand side, Africa and the Middle East are now competing with China. At the same time, a new report says large parts of Asia may face long periods of severe drought within 10 years. The report is from the British-based Center for Low-Carbon Futures, a network of universities. It says Northern China, India, Afghanistan, Mongolia and Pakistan will be especially hard hit. It says other parts of Asia are likely to face longer and wetter monsoon seasons because of climate change. Andrew McConville works for the agricultural technology company Singenta. He says a lack of new investment in technology to help farmers improve productivity has caused problems for agriculture. For VOA Special English, I'm Alex Villareal.


So, good morning, good afternoon, good evening to everyone wherever you are in the world. Just preparing to start the webinar for today. We just wait a minute or so for a few more people to join us. As you can see from the title. The webinar will be focused today on supply risk assessment and trying to give some case studies and examples of how we can use technology to make that a better process. There's a QR code on there you can use to make the session interactive. So please use your mobile phone cameras to scan and use that to participate in the polls, and also to give feedback and download any tools that we offer during the webinar. I think at that point I think we'll start the session. So, my name is Neil Marshall X Coca Cola for 20 plus years too many years to remember for myself. For the last year I've been working as a consultant for my own company, working with select partners across the globe mainly in Europe in the US. I'm delighted to say I also have my friend college and the CTO and founding partner agronome. Yanis notice, who will also take us through this webinar and give some case study examples, and do a bit of a live demo. Towards the end will also do some interaction if possible and if there's time to do some question and answers as we get to the end. So let's talk about Yanis, as well as being the chief technology officer and partner. He has over 15 years experience working in this field, particularly around risk monitoring assessment using AI and data intelligence to help build technology solutions to support food manufacturers retailers, food service operators, etc. Improve their insights into the business and prevent issues occurring. He leads the team responsible for the food archive platform, which is available through links but it's also www.agronome.com backslash food archive you can also find that I'm sure if you search for it, which is the premium food risk technology platform for the industry. Eponomol, which is my bad attempt at Greek to me next slide so we're being ably assisted by a couple of people in the background. And so I go for today and the webinar is to focus on how technology can help us really look at the supply risk ranking. How can we use that to assess our suppliers to minimize the recalls and use some of that data that's out there everywhere to try and focus in and holding on managing those suppliers and assessing their performance. We know there's so much data out there these days, it's difficult to select which data to use. We're limited, particularly with the pandemic and covered for access to that data and information. So technology is an obvious answer to support your teams and support that process to evaluate suppliers. So let's make that decision and start today so. Yes, next slide so some of the background information I think people have seen that before just go by one year sorry. The continued background of noise in the industry. What what the people trust or not you know people have probably seen this information before this slide reviews the previous webinars, and it's scary to believe that you know these are the three main sources where people get their information around food companies, particularly for consumers from the internet Google searching and scanning etc from the food companies, but also they rely heavily on the data from the governments and the regulators, and that one that the governments and the regulators are generally the most trusted for the But transition and also across into the audit space. Most big companies now have had to move to and smaller companies have had to move to the use of remote audits. So remote audits to replace physical assessment where people have had to rely again on technology to make those assessment of the suppliers using Google glasses and other solutions to look inside the suppliers operation. To assess those risks, look at the document share it, and in some ways it's made it more effective and more efficient, because obviously there's a time saving from people traveling. There's a cost saving from people not having to fly and drive around visiting suppliers, but sometimes the data can't be as easily accessible, or in some cases, there's a lack of trust around that data. So using technology again remote audits have been a good way to gain insights, particularly in the pandemic, and beyond I'm sure it'll stay for getting insights into suppliers performance. But we can also use that data to feed into our supplier risk models. So, Epimo please. Next slide. So some of that data and risk ranking means that there's trust in the food safety data. It's time consuming for companies, people's quality teams to look through that data, looking at the new suppliers evaluating that historical data. And there's a need to make a quicker, a simpler way of accessing that data, because it's often time consuming, it takes a lot of time to access the data. It's a lot of time to then correlate the data, analyze, review the data. And often a lot of companies are still using manual systems and Excel sheets to review that data and consolidate between systems that they're using the companies and this can lead to errors. People can make mistakes. And it's not effective. It's not a good process. And it's not efficient to do it that way. Next slide please. So what are we going to try to do today is look at how you use your process and offer some solutions through some examples that Yanis will show, but also then show you the food archive platform and how it can help you automate your process. So for you now and the people on the call and the people will listen in later. How automated is your process. How often do you update it. How do you make sure you get an early warning or indication of any change, particularly from the suppliers and if I think about my career and going back over 2030 years. Most of the issues and recalls have occurred when it's been from a supplier and sometimes a supplier. I call it the tier two supplier so the suppliers is a supplier so they make a change in their process to change an ingredient the change of manufacturing process, which has a knock on implication for the tier one supplier. And then leading into the manufacturer or the retailer later because they've changed something that you weren't aware of. There are other files that needs to be captured when you're assessing the risks from your suppliers. And next slide please. So we now want to transition into a poll to try to make this as interactive as we can. And these are the four questions that are now coming up if you can. Please answer will give it a minute or so to capture the results. And then we'll transition through to the next slide. I think one of the things that just while you're filling in one of the things that people have noticed is the amount of data that's out there is difficult. There's a lot of data. So how do you keep that simple, easy and effective and how do you manage that date. Okay, there we go so the results are in. I've manually updated of Excel documents being the biggest one probably no surprise. The second biggest one. Some people are already using a third party software to try to automate their processes, and then a tie between lack of systems and using in house software. I think that's probably fairly, fairly reflective of what we've seen so far and I'm sure Yanis can comment as well. Thank you for your presentation, but that's probably no surprise to me. Next slide please. So transitioning now to some case studies and over to Yanis to take us forward for the next session. Thank you. Thank you, Neil. Good morning, good afternoon and good evening to all. Thank you very much for your interest in this webinar. So I'm getting started this time with agronome so if we can go to the next slide. In agronome our mission is to empower the people ensuring that everyone has access to shape and healthy food. And this mission is for that keep us keeps us excited every morning that we wake up, because we are helping and supporting people that are doing such important work that are responsible to keep food safe for all of us, including others and our families. And when people are asking us when and how companies tend to put that guy, they tend to agronome sorry, in order to use a platform like for that guy. The answer is that this happens when the companies have to deal with a large amount of data that they have or external data that they need to manage and to to have at their fingertips, because they want to prioritize risk measures, and they need to be early informed about external risks that may affect their suppliers. So this is how a collaboration with food companies starts for us. We work in the, in the area that we call food risk intelligence. And in this area we have identified three key pillars for risk prevention. And these are the pillars that in which we are trying to help the companies. The one pillar has to do with risk monitoring, and we are helping food companies in the scanning investigating in the reporting incidents that are announced globally, and they are very relevant for the supply chain. The second pillar is the risk assessment. And this has to do with calculating risk indicators for thousands of ingredients and suppliers using different data types, which is one of the challenges that we have also mentioned in the first part, as Neil mentioned in the first part of this webinar. And the third pillar is the risk prevention, is how we can prioritize risk mitigation actions, mitigation actions like the lab testing program, the supplier package program, and how we can prioritize them and make them to focus on the high risk areas in order to help us to prevent incidents and help the companies to prevent incidents. Next slide please. And working with several, with many companies and hundreds of safety experts, we have identified that in these three pillars, there are three categories of people, three categories of companies that are the ones that are a bit skeptical about adopting a digital solution, and they are right because they feel very well with the current tools and the current practices that they are using. And there are others that they are following the trends in these three pillars, they are, they have started using digital tools, or they have, they are using a third party solution for that. And they have also the ones that they want to be the first, the first in adopting the digital solution that believes very much that the digital solution for risk prevention can improve and can transform, of course, to the better, to a better direction, the current practices for risk prevention. And based on the data that we have speaking to so many people, the current status of the industry in these three areas and in these three categories is that in the first in the risk monitoring pillar, we see that the people has already and the companies have already adopted a solution or they are doing this even manually, but with the help of some of the tools. In the risk assessment, there are a lot of mainly Excel based tools that are used. They are also, the companies are also adopting digital solutions in this area and the risk assessment area. And in the third pillar, the risk prevention pillar, mainly the companies are changing the preventive measures only when there is a major issue announced. There are no tools used right now by the industry and by the most companies and of course there are no solutions that are developed internally in order to prevent and predict risk. Next slide please. So, Neil, we want the input of the people here again. Yeah, very interesting where you're just putting forward the Yannis particularly the three areas. And I think it's, you know, if you reflect back on people we speak to and where they are. I don't think anyone will say they're really far to the right on everything I think that's probably unlikely, but it would be good to see where our audience stands today so if you can also scan the QR code again with your phone, and give us the feedback. There's also an opportunity to download the tool as well that's been provided by Agrono from this solution so I think everybody wants to be a leader. But I think people are somewhere between the three boxes, they may be leading in one area but they're down to the left and the others. You know I can only speak from my own experience. It'd be great to be always on the right and I think the other thing to mention here is, you know with the platform that you're developing and developed to this point. Everything's connected into this tool. So this is why it's really useful for doing the risk assessment you have the hazards connected in you have the ingredient assessments, the supplier information, which helps you get a really connected picture for the risk and I think that's critical as well. Right, I think you're going to take us through some use cases Marianas. Yeah. So the, what we will try to do here in this part of the webinar is that we will focus on one very important case on how we can perform a risk ranking supplier is cranking something that is widely done as a practice in the industry by estimating the risk, a risk score for each supplier using different parameters. And we have to actually there are two sub cases the one case is that we may want to start working with a new supplier and this happens a lot as also Neil mentioned during the pandemic period because due to the issues with availability of the materials, there is a need to change a supplier so you need to engage a new supplier. And there we what specifically a manufacturer needs to do is that he needs to check the history of the supplier regarding food safety incidents, like, which are the food recalls and border rejections linked to the specific company, but also which are the inspections and the outcomes of these inspections that have been done by the authorities and have been reported on the by the authorities on their website in different, like globally in different regions so how may I know about all these issues about the incidents and the inspections. And this is actually something that is also required by the latest food safety regulation and also by food safety standards so knowing which is the food safety category of the company that you are about to work with is a very important step in the evaluation. And the other sub case and the other cases, if we go to the next slide slide is that also for the existing suppliers that the manufacturer at the food company has a needs to identify which of the suppliers is potentially at high risk. So this requires in the next slide with, we are making this more specific so this requires to be able to identify which suppliers may potentially be at risk because one of the materials of the or the ingredients that they are using is affected by an emerging Chris. And this also means that we want also to be aligned with the suppliers and ensure that they have the mitigation measures in place that they have put the mitigation measures in place. And the second thing that is very important is to be able to identify which are the challenges for the suppliers and to collaborate with them in order to adopt a more proactive approach. And discussing with companies we see that this builds visibility and transparency in the collaboration with suppliers, because you know, as a buyer or as in this collaboration or as a supplier you know which are the challenges you need to to deal with and to address. And since this is an open thing and this is transparent, we can collaborate and we can make sure that these challenges and this energy increase will be addressed through a very good mitigation plan. So, this is the current status and now it's very important to see how AI but also data can help in to automate this kind of processes to address these challenges of managing the different types of information that you may have internally but also information that you need to collect from external sources about the risks. And we will we will present these three through use cases for these three for these two use cases that we mentioned the one on how you can evaluate a new supplier and the other on how you can identify with suppliers are at high risk because they are affected by an risk issue in the supply chain. So, starting with the, with the case of evaluating new supplier, the digital solution like to the guy if we go to the next slide. Is collecting all the information about the food safety incidents either these are recalls, border rejections, important fuselage announced in different regions, and provides you the ability to perform a very good and very accurate search. And to find out for a specific supplier if historically there are incidents or inspections or warning letters that have been announced for the specific supplier. And this can be done only through search. And the real cases here from from the discussions that we have with companies. They are saying to us that although we have very good search engines global search engines. The idea is that in some cases, this information is hidden behind Excel files or scant documents or web pages in different languages. So still, they are, it's a true story that they are searching for a specific company in the global searches in the global web search engines, and they are saying to us that there's nothing for this company. Can we try to do it also in a good search engine specifically for the suppliers that you have in for that guy and when we do that. They are surprised because they are many things that have been reported by the national authorities, but they are not visible to the global search engines that are there. And if we go to the next slide after searching and finding all the issues that have been reported, the digital solution can consolidate this in a library profile, where you have the option to see all the incidents, not only for the company, but also for subsidiaries or for specifics facilities of the company so this is consolidated. And in some cases you may still want to be very specific and go to a specific subsidiary and not the parent organizations or this is also visible. And study which were the inspections results inspection outcomes, and based on all the frequency and the severity of the incidents that have been reported for the origin of the supplier you can have also a risk for the specific region. So in this way, only with a simple search in the digital solution in a solution they put a guy, and by getting such a supplier risk profile, you may have all the food safety history and the regulatory history of this company at your hands. With no manual work on searching on the web in order to find specific incidents in different websites in different locations in different regions. So if we go to the part of how we can identify which suppliers are at high risk. Then the digital solution that put a guy can help. First of all, through the very good risk monitoring. So in the next slide. If we go to a specific use case of the manufacturing of products if we assume that we have a manufacturer of bakery products are ready to eat products, then using a very good monitoring service. We can get an early notification, like we are showing here about an increasing risk for with a specific percentage of increase for a chemical like for instance the ETO. And since he has this early notification, he can go and study this in depth so he can go to the supplier dashboard where all the suppliers that all the companies that he's working with are listed. And for each company, he can see which is the level of the risk, either in a numerical way, like we are showing here. Or there is also visual heat map that can present to the to the manufacturer, and he can identify which are the suppliers that are at the high, medium or low risk. So in the specific case, he will see that the main supplier for his sesame seeds, the supplier a in this case has an increased ingredient risks. And the end he needs to investigate this further. So this means if we go to the next slide this means that, first of all, he can see this whole show, there is a heat map that highlights, which are the suppliers that we need to pay attention because they have. They are in a high risk region based on the ingredients and the incidents that have been reported for this supplier. And if we go to the next slide. And we can see that the based on different drivers of the risk we can have an overall score for the specific company and for all the companies and using this overall score, we can run these companies from the ones with the highest risk or the lowest. And so, in this way we can design very important mitigation measures like for instance to ask for a certificates of analysis for the specific ingredient that the supplier is managing or is producing. And we can use also additional parameters like the recalls that this company had the border rejections the inspections the warning letters, and using all these parameters we can have an overall score for for the companies. And what we hear also from the companies is that, yes, in this case we would like also to adjust. If we go to the next slide slide that the companies are asking us if they can also adjust the different parameters the weight of the different parameters in the overall score. So there is also the possibility in the solution to adjust the parameters so to give different way or to disable completely some of these risk weights and focus only on the ones that are according to your your risk assessment model for suppliers. And it's also very important that if a company if a manufacturer would like to include one new and additional parameter like for instance the audit score. He can do it by including the parameter and by attaching also by uploading the data for this parameter so if we have the risk score for the companies for which I want to perform the risk ranking. This will be added as a new column here as a new parameter and can be used in the risk ranking of these companies and in this way we can identify very easily, which are the companies that are at high risk. And this is an automated process because any new incident any new inspection is automatically collected in this risk assessment approach in this matrix. And this used to recalculate the risk so if there are many new in your incidents reported for the ingredient of a specific supplier supplier sorry. This will increase the risk of the ingredients and this will be automatically reflected in this dashboard in this risk models. Next slide please. So, Neil, now that you see this approach that the manufacturer can follow using the digital solution which do you believe that are the benefits for the manufacturer before I get to the benefits I just want to just reemphasize I guess some of the points you just made Yes, I think people need to understand really through the platform you can pull out hidden data that's on the on the Internet in the reporting by the regulators you're gathering that information. I think the search engine within food archive helps that a lot particularly to give you a really good picture around the supplier. It allows you to connect all that data as you just explained into one place. But it also allows you to make a bespoke system that suits your individual company so the platform around this risk assessment is still flexible enough to add in like you just mentioned the supplier audit or the individual data as well. I think that also makes the platform unique. And it's really really very flexible. That's that's extra items. In addition to the benefits we're saying or we're just going to mention because that global perspective to be able to find trends look for trends connected to the horizon scan and the other way we connect. And again as we talk about many times, trying to look forward to predict or give us insights for what future trends could be. That's also really important. And I think the whole piece around managing your suppliers, looking at the risks from the suppliers and managing what potentially they can problems that can cause you allows you to mitigate against that in advance. And the critical piece that's still not going away that's still important for everyone is that visibility back up your supply chain to look at your suppliers. I mentioned earlier about the pain in the neck for me always was around tier two and even tier three suppliers so you're not always talking about just the first level supplier to you as a manufacturer or user. It can be two and three steps backwards as well. So it could be IP or confidential to that supplier, you're buying from, but how do you get the insights into those suppliers beyond that as well. And I know we've talked about Yanis, how you can use the platform to do that as well. Getting insights not only on your direct supplier, but the ones beyond that because that's usually where the issues come from. And that all points around personalizing the alerts through the platform around changes to suppliers. If there's a recall with that specific supplier, and you've got it in your profile in the platform, it will give you an award. I think they're really important benefits for people to use the platform and realize how we can help them to automate and make it easier in their day to day operation. I think with that we're going to step forward because I want to talk too much and take too much of the time, but move forward to the demo because I know me and you can talk about this forever but let's try and look at the live demo. Yeah, but your point is very valid and very important, especially the thing about the tier one and tier two suppliers. That's why with the companies that we are working together. We are always suggesting of involving also suppliers tier one suppliers in the in the platform because in this way they can, they will make sure that also tier two suppliers will be monitored. So if you have a very good traceability information, then you can directly as a company include both tier one but also tier two. So, now I will focus more we have covered very important things about the supplier assessment the supplier ranking the monitoring of the suppliers. Now I will focus more on how I will share my screen so I hope that everyone can see my screen on how we can monitor the ingredients and we can assess the risk of the ingredients and we can even prevent and we can predict incidents and risk of the ingredients so how we can leverage all this data and the AI technology in order to automate also this process of risk monitoring risk assessment and the risk prevention of the level of ingredients so suppose that you have a supplier that is providing to you to you to make powder. So how such platform can help you show this level at the level of the ingredients that the supplier has and this supplier is providing to you is managing. And we want to go very deep in the supply chain and we don't want only to be at the tier one, we want to go on tier two and even at the raw material part. So, in this case, the platform will help us because, first of all, it gives you all this power of risk monitoring the dynamic risk monitoring. So for the, for the ingredients monitoring, in the case of a specific ingredient like ground to Mary, it will highlight to us that there is a very important increasing trend for ground to Mary. If we compare the last year issues with the current year issues, there's a huge increase, and directly, we can go and perform a hazard analysis for this specific ingredient, and we can identify which were the cause, which was the root cause of this high increasing trend. So, you can do that very easily in such platform you just click on the specific ingredient and you can see all the data, all show organized very well in the different types of hazards. So, for instance, we can see that during the last 12 months, there is a very big important increase of incidents. And there are mainly incidents for turmeric powder coming from India, but originated from India. And the main reason of this, the main reasons for this increasing trend are two are the chemicals that were found in the turmeric powder and also fraud cases and specifically maybe other direction cases so if you click because we have the information very well organized and it's very accurate and this curated by also the experts, you can be very, you can go very deep and you can drill down to specific hazards. So, for instance, we see here that the main issue is the presence of pesticides that are exceeding the limits and if you click on the best sites, you can see that the main reason was the use of ETO in Kurkuma, so it was not only the sesame seeds that was affected by the ETO, but there are several and many other ingredients that have been affected. And you can see also other chemicals that were found in turmeric powder during the last two years. And if you click on the risk on the list, you can see specifically which are these incidents and go and study details about this specific incident. And the same you can do for other types of hazards like if I want to see what was the problem, what was the fraudulent practices that were identified. And this has to do mainly with, and also with the use of unauthorized ingredients and with adulteration cases and if you click for instance on adulteration cases, you can go deeply and you can see that this has to do with addition of some enhancers and neutralizers and you can be even, and you can see specifically what this was, what this happened and which were the cases. So knowing which are the specific hazards is very important because you know if the mitigation measures that you have in place are enough in order to prevent an incident. So if there is a large increase of incidents and a trend for ETO or if there is a new risk and emergency increase, you want to know it and you want to include this as a parameter in your lab testing and also ask for a specific certificate of analysis from the supplier. And you can extend this analysis also in the risk assessment part so you can perform a risk ranking for all the hazards that have been reported for Grand Turmeric. So you can see here that biological issue like Salmonella is one of the highest risks in Turmeric Grand Turmeric. There are also cases with lead that are frequent and there are ranked high and there are also new issues like for instance the ETO that we have already discussed that are highlighted in this risk assessment as a new issues. So you may know which are the increasing but also the new emerging issues and of course if you want to make this very specific only to chemical issues to have the risk ranking only to chemical for chemical issues you can select only the chemical parameters and have this risk assessment only for chemical parameters. But what one of the very important questions that we get also from the companies that we are working together is that since we have all this information for the incidents that go historically back many years and we know about the their frequency. Why we cannot apply predictive analytics technology in order to predict which will be the trend of the incidents within the next 12 months or which will be the hazards that are likely to increase which are the emerging issues, which will be the issues in the next few months. This is something like for instance the weather prediction that you are getting every day so how we can know how we know which will be the trend of the incidents for a specific ingredient. So, for this reason, we have applied AI technology and we have built prediction models specifically for each ingredient taking into consideration all the incidents that have been reported for this ingredient so far. And using this information, this data, we are forecasting, we are creating a forecast of the incidents, but also of the specific causes. So in the case for instance of the ground turmeric, we see that based on the prediction on the results of the prediction model, there will be there is not expected a very important increase of the incidents in the number of the incidents. And there are some countries that it seems that we will have more incidents. But still, there are some hazards that are likely to increase for the ground turmeric. Like for instance Salmonella will have an increasing trend and also will have issues with heavy metals like lead that seems to be increasing. And based on the analysis of the past, we are also highlighting here which are the emerging hazards that are present, that may be present in the ground turmeric, in kukuma. And you can see that, for instance, there are cases with Sudan one with a color like that was designed. So, you may be, you may want to include this parameters to include this kind of emerging risks in your preventive measures so to make sure that you have all the measures in place in order to prevent an incident. All to make sure that you have the materials and the ingredients that are authentic, that are very safe and that you are getting what you have been promised to get. And also using the information about the predicted incidents and the hazards, we may have also a heat map of the risks that we have right now, so the actual heat map of the risk but also the predicted heat map of the risk. So how the risk heat map will change within the next few months and the system knowing which are the suppliers from which you are getting the kukuma or which are using in the product that they are providing to you. The kukuma, you may be notified and you may know which is specifically the supplier, this supplier and why this supplier is at a higher risk. So, we talked about how the digital solution that uses data and AI technology can transform the way that you are performing the supplier risk ranking. And also we go deeper here in how such a technology can be used also to go deep in the analysis of all the hazards and all the risks for a specific ingredient and also how knowing all these emerging risks for the specific ingredient, you know which supplier or which suppliers are affected. So with that, I will go back to you. Thank you, Yanis. Very interesting. I think the whole thing there, hopefully it comes across from your demonstration there is that flexibility. You know, you are showing as easily how you jump around in the platform. But I think for some of the people on the call and people listening in, you know, they would have that ability if they also subscribe to the platform, they can also go in there and move around like you did.  I think from the business value angle. We've been through some examples there from the case studies and also through your demo, which really tried to help you to save time for yourself. Everyone's so busy these days, no one's got time to do anything. We've got less resources, less budget, less time. So automating a process, making it consistent, really assessing your suppliers and having those insights feeding into the platform makes it much easier to do that supplier risk assessment. I think the second point is around optimization, trying to optimize your current programs, your audits, your data, your information. So it again feeds into one solution. I think that's really important. And then the thing that we just touched on there about trying to do prediction to prevent incidents occur and you mean the last thing you is an issue or a recall or foodborne illness from your company but this is trying to help you be proactive to prepare and try and prevent that from happening so you're not doing the five o'clock on a Friday and a weekend, trying to resolve the issue. And the whole thing about automating the process means it takes away some of that manual effort, particularly if you've lost people or you're struggling to hire people in the current climate. We know that's difficulty for many people in many countries where resources and people are not so available. By automating away from a manual system of collecting that data and processing, it means you'll have a better, more robust system in place for assessing your suppliers. So flexibility and personalization with food archive help tremendous. I think our next slide please. Going on to the maps to show where you can go and give you some indication. I think Yanis talked several times about where people are and where you think your company is on that journey from skeptic to leader. I mentioned earlier, it was a QR code and a tool, which we'll provide now so again apologies I saw somebody said they're on the phone and we can't scan but I'm sure the team will share the information later, but there is a free tool there to help you assess where you are in your own personal and company digital journey, and you can use that to give an assessment and follow up back to the customer success team at Agra now who can help you and follow up with a more detailed discussion and webinar discussion demo demo if needed. Okay, next slide please I think we're going to now try to go to or maybe we'll leave that slide on. We're going to try to go through some of the questions that we've received. So I'm going to put in the hard questions to you. Let me just try and scan through the questions. Is there any that you already want to talk about? Yeah, I have already studied the questions and they are beautiful and very interesting. So I will start answering them live but also feel free to jump in and to compliment. Sure, well let's just go from the top. Yeah, I will start with the question about new companies or suppliers of novel ingredients. We rely on the information that is announced out there. So this is a limitation. Yeah, this is true. So if there is a very new company, or if a company has changed brand, and there is no connection to the previous company. We will not have historical information for this company. So this is true novel ingredients. Of course, they are monitored continuously. But yeah, limited data will be there for the very new companies. But usually the very important suppliers of the industry are also getting inside the novel ingredients space. So at least we can have a very good food safety history of these companies and we can have a good idea of the food safety culture of this company. This is very important. This is what we are discussing with many of the companies that we are working with. It's not only important to know the very specific thing that was reported for the company, but the profile of the company gives a very good idea of the food safety culture of the company. Yeah, and I think that you already mentioned it. We've been through examples with some clients customers where the names are sometimes different and it's not always easy to identify the suppliers. But you know, like everything, you've got to work with that and identify the information and feed it in because it's only as good as the data that's provided. I think that's the critical piece. I think there's another question about the trade supplier in Greece. The traceability. This is, this is a well known problem. So thank you very much Julia for pointing this out. There is, there is the lack of traceability of information in several cases. That's why what we are always suggesting to the companies that we are working with is to add all the ingredients and all the materials that are used in the products, even if you don't know the specific supplier, the tier one supplier because you are referring to this very critical thing that Neil mentioned. Even if you don't know it, please do not close your eyes to the emerging issues of specific ingredients and materials. You cannot close your eyes in an emerging issue for a spice. Even if this comes from finally not from India but it comes from Egypt, for instance, you need to know about it because in many cases they are transferred through Egypt, but they are originally produced in India. So it's, we are always suggesting tracing and monitoring of monitoring all the ingredients. A very good point about the correlation between kill step, like for Salmonella like the use of a chemical and the Salmonella. So what we have identified and what we have observed is that there is a very good correlation with the latency, of course, that first in the sesame seed we had an increasing trend of Salmonella, suddenly this trend stopped because they started to use a chemical to stop this trend because this was reported very much by the companies. And now that they stopped, it seems that the Salmonella is going up again for some of the seeds and spices. So this is very true, this is a very good point. And yes, we have identified such a correlation, such this kind of causality. Okay, that's the question from John Carter, yeah, but there's another one about how can suppliers be assessed in the tool from abroad, I guess we've already covered that one. Suppliers are covered from all countries and all locations. So there's no specific border just to Greece or just to Europe, globally suppliers can be included. Yeah, of course, of course, there is no limitation. And it makes sense to include global because we are not scanning only the very developed regions. We are also scanning the border rejections where many companies from other regions, like from Asia from Africa. They have been reported during the border control. So we are not focusing, you can find companies from everywhere, the database. Yeah, in terms of publishing information, the authorities are in some, in some, they are not in only regions, they are mainly in some regions, but we have a good coverage of the origin of the suppliers a very good one. Now you say if it's not reported in the country of origin, one of the other countries probably in Europe or US or in Asia will probably pick it up. That's, that's the way to look at it. I think there's a question, I know we don't have time, but the question about, is there an Excel or in-house tool that contains data for suppliers can be used to feed in the customized section and be included in the tool. Now you add in individual company data, Janice, I think we mentioned that already, but just want to confirm that. It's a possibility of importing all the suppliers list that you may have with their ingredients, all these things into the risk matrix that I presented, and automatically the risk will be estimated. So there is a possibility of importing an Excel file and also in many places of the platform, there is a possibility of exporting the risk results and exporting all these risk estimations in Excel file. So you can continue and you can integrate it also in the other process. Yeah, and that just made me think of another point. Obviously within the platform, there's the whole reporting process as well where you can export for reports and gather data and share it then within your own people who don't necessarily have access to the food archive but you can share it in your own business. And I always found that a very, very useful way of sharing data around those risks as well. Over time. Yeah, you want to any other question. We will also answer some of the questions that we did not manage to discuss, we will also answer it through email later. But I would like to thank you again for your interest in this webinar and for your attention. It was a pleasure as always to share experiences and our thoughts about it. And the same for me so thank you to everybody who's joined today. Hope that was useful and insightful. The recording and the materials will be available, and the customer success team will share that. Please remember to use the QR code where you can to download the free tool. And thanks again for your time today. Thank you.