WEBVTT - Creating more resilient supply chains by decoupling labor from location: Elliot Katz and Shai Magzimof of Phantom Auto 0:00:03.920 --> 0:00:10.120 Technology d couples Labor from location. We remove the geographic 0:00:10.360 --> 0:00:15.240 restriction to hiring, because with remotely operated forklifts you can 0:00:15.280 --> 0:00:18.520 have someone doing that exact same work in the exact 0:00:18.600 --> 0:00:24.000 same warehouse but be sitting thousands of miles away. So 0:00:24.480 --> 0:00:29.600 our customers are using our remote operation platform to connect 0:00:29.680 --> 0:00:32.520 people all around the country who want need to work 0:00:33.280 --> 0:00:37.960 with the hundreds of thousands of essential jobs that must 0:00:38.000 --> 0:00:44.680 be filled to keep our supply chain intact. Welcome to 0:00:44.720 --> 0:00:48.279 the restless ones. I'm Jonathan Strickland. As you may know, 0:00:48.479 --> 0:00:52.040 I've spent the last fifteen years covering technology and learning 0:00:52.040 --> 0:00:56.600 how it works, demystifying everything from massive parallel processing to 0:00:56.720 --> 0:01:02.560 advanced robotics and everything in between. Yet it's the conversations 0:01:02.720 --> 0:01:05.600 with some of the most forward thinking leaders, those at 0:01:05.600 --> 0:01:09.560 the intersection of technology and business, that fascinate me the most. 0:01:11.400 --> 0:01:14.119 Elliott cats and shy Magsimov are working at Phantom auto 0:01:14.240 --> 0:01:19.200 on some really tricky challenges related to autonomous vehicles. Phantom 0:01:19.280 --> 0:01:23.319 Auto's mission is to provide solutions that address gaps in 0:01:23.400 --> 0:01:27.200 autonomous vehicle capabilities, and one way you can look at 0:01:27.240 --> 0:01:30.800 that is how machines are very good at dealing with 0:01:30.920 --> 0:01:35.240 a limited number of variables, but as you add more 0:01:35.360 --> 0:01:39.039 and more variables and you make a system increasingly dynamic, 0:01:39.680 --> 0:01:43.240 machines can struggle to keep up. Situations that a human 0:01:43.280 --> 0:01:47.319 could handle by drawing on similar experiences or using free 0:01:47.319 --> 0:01:52.400 association or trial and error are beyond machine capabilities, at 0:01:52.440 --> 0:01:55.520 least for now anyway. And when it comes to driving 0:01:55.520 --> 0:01:59.960 a vehicle, dynamic situations are the norm. Under controlled can 0:02:00.080 --> 0:02:04.200 editions and autonomous system can excel, but the world is 0:02:04.320 --> 0:02:08.400 rarely organized into such standard scenarios, and that's one area 0:02:08.480 --> 0:02:12.640 where Phantom auto can help. The company creates solutions in 0:02:12.680 --> 0:02:15.880 which a human operator can control a vehicle, such as 0:02:15.880 --> 0:02:19.360 a forklift in a warehouse from a remote location in 0:02:19.440 --> 0:02:24.040 real time. Using a combination of cameras, sensors, actuators and 0:02:24.080 --> 0:02:27.720 wireless connectivity, the operator can control the vehicle as if 0:02:27.760 --> 0:02:31.240 they were sitting in the driver's seat. I was beyond 0:02:31.320 --> 0:02:35.000 excited to talk about that technology, but first I wanted 0:02:35.000 --> 0:02:37.800 to learn more about Elliott cats, whose vision is all 0:02:37.840 --> 0:02:40.400 about leveraging tech to make a difference in the world, 0:02:40.720 --> 0:02:44.760 and shy Maximov, who builds solutions that make those ideas possible. 0:02:48.520 --> 0:02:52.960 I am so excited today to have this conversation. We're 0:02:52.960 --> 0:02:55.239 going to be talking about a lot of things that 0:02:55.520 --> 0:02:59.560 I find absolutely fascinating and I want to welcome both 0:02:59.639 --> 0:03:03.440 shy and Elliott to the restless ones. Welcome to the show. 0:03:03.919 --> 0:03:08.160 Thank you, Ji. Thank you, thanks for having us so. First, Elliott, 0:03:08.200 --> 0:03:10.480 I was wondering if you could start us off by 0:03:10.480 --> 0:03:13.520 telling me a bit about how you first got interested 0:03:13.680 --> 0:03:18.880 in technology. Yeah, absolutely so. I grew up in Silicon Valley, 0:03:19.040 --> 0:03:21.840 really before it was silicon valley, but I kind of 0:03:22.040 --> 0:03:25.440 came of edge during the first dot com boom. So 0:03:25.520 --> 0:03:29.680 I saw from a relatively young age how quickly and 0:03:29.880 --> 0:03:36.200 broadly technology can be adopted by society, and that's when 0:03:36.240 --> 0:03:39.280 I really got interested, and and not so much in 0:03:39.560 --> 0:03:45.200 technology for technology's sake, but really technology that could help 0:03:45.440 --> 0:03:52.920 make broad, sweeping positive societal change. So I'm mainly attracted 0:03:52.920 --> 0:03:57.680 to technology that I believe can create material net positive change, 0:03:58.320 --> 0:04:02.560 enhancing people's safe the or their health or just the 0:04:02.640 --> 0:04:06.040 general quality of their day to day lives. Yes, and 0:04:06.240 --> 0:04:09.760 that DOT COM boom, that's also a time of learning, 0:04:09.800 --> 0:04:13.320 lots of lessons. You know what is working in that 0:04:13.880 --> 0:04:16.920 realm of technology that can make positive change in the 0:04:16.960 --> 0:04:20.960 world versus technology that, without the proper planning, can end 0:04:21.040 --> 0:04:24.479 up falling apart. Shy, I'm also curious about you. When 0:04:24.480 --> 0:04:27.279 did you first start getting interested in tech? Yeah, I 0:04:27.279 --> 0:04:29.720 got a slightly different story than Eliot I. I grew 0:04:29.800 --> 0:04:32.840 up in Jerusalem, in Israel, so pretty far away from 0:04:32.839 --> 0:04:35.880 Silicon Valley. I remember when I was six seven years old, 0:04:36.120 --> 0:04:37.960 I used to wake up at night and see my 0:04:38.040 --> 0:04:40.360 dad playing video games. So my dad was a video 0:04:40.360 --> 0:04:42.400 game addict. So I saw that growing up and I 0:04:42.440 --> 0:04:47.000 got into computers, playing within real time multiplayer on the computer, 0:04:47.120 --> 0:04:49.480 connecting land and and things like that. So that's how 0:04:49.480 --> 0:04:52.320 I got, you know, my my initial passion to computers. 0:04:52.480 --> 0:04:55.719 I started to learn about networking communication and had a 0:04:55.760 --> 0:04:59.920 deep passion for wireless connectivity and built on communications. Later 0:05:00.120 --> 0:05:03.800 on I got to white combinator and went to Silicon 0:05:03.839 --> 0:05:06.360 Valley for the first time. I barely spoke the language 0:05:06.400 --> 0:05:09.000 at the time and that came in and presented the company. 0:05:09.080 --> 0:05:11.240 We were doing at the time, some e commerce social 0:05:11.320 --> 0:05:13.480 website that turned into a search engine that later got 0:05:13.480 --> 0:05:16.800 acquired by Apple. So it was an interesting journey there. 0:05:17.080 --> 0:05:19.200 But I would say, you know, for me, technology is always, 0:05:19.279 --> 0:05:22.360 you know, something that is fascinating just seeing it and 0:05:22.400 --> 0:05:24.880 what it could change in this world. What the things 0:05:24.880 --> 0:05:27.640 that you can create and build makes you so excited 0:05:27.960 --> 0:05:30.840 to do something that really matters. Shall you touched on 0:05:30.880 --> 0:05:33.440 something I definitely wanted to ask you about, because having 0:05:33.480 --> 0:05:36.479 someone who is a serial founder of companies is really 0:05:36.520 --> 0:05:39.520 exciting for me. What is it that motivates you when 0:05:39.520 --> 0:05:41.960 you're founding these companies? Is it just that you you 0:05:42.000 --> 0:05:43.880 have a spark of an idea and you have to 0:05:43.880 --> 0:05:46.720 see it to fruition? For me, it's a deep passion 0:05:46.760 --> 0:05:49.520 for technology. You know, I was inspired by the Steve 0:05:49.600 --> 0:05:51.760 Jobs and the Mark Zuckerberg of the world when I was, 0:05:51.839 --> 0:05:54.600 you know, a teenager already, and you know then there's 0:05:54.600 --> 0:05:57.120 solving big problems, changing the world as the results and 0:05:57.160 --> 0:06:00.960 doing something that matters and leading teams building something that 0:06:01.120 --> 0:06:04.040 can really, technologically speaking, make a leap in in our 0:06:04.120 --> 0:06:06.280 day to day and how we used to do stuff. 0:06:06.680 --> 0:06:09.719 Just a be passion for technology. Elliott, we're going to 0:06:09.720 --> 0:06:11.960 be talking about things that have kind of a then 0:06:12.040 --> 0:06:17.240 diagram overlap of autonomous vehicles. Did you become interested in 0:06:17.440 --> 0:06:20.800 autonomous vehicles, partly because this is a technology that is 0:06:20.920 --> 0:06:25.039 poised to have a tremendous positive impact if we get 0:06:25.040 --> 0:06:28.800 the technology right. Yeah, that's exactly right. You know, as 0:06:28.839 --> 0:06:32.599 I said before, I'm attracted to technology that I believe 0:06:32.720 --> 0:06:36.880 can create material net positive change. And when it comes 0:06:36.920 --> 0:06:42.000 to our current status quo with passenger vehicles, for example, 0:06:42.680 --> 0:06:47.640 more than one point three million people die from traffic 0:06:47.680 --> 0:06:51.960 accidents every year worldwide and, to put that into a 0:06:52.040 --> 0:06:57.839 pretty sobering perspective, that death toll is equivalent to nearly 0:06:58.040 --> 0:07:02.920 eight fully loaded, seven forty seven airplanes crashing every single 0:07:03.040 --> 0:07:06.400 day in a given year in killing everyone on board. 0:07:06.920 --> 0:07:09.240 So you know, if that amount of planes fell out 0:07:09.240 --> 0:07:12.119 of the sky for even a week, we would likely 0:07:12.160 --> 0:07:16.080 shut down aviation as we know it. But for whatever 0:07:16.120 --> 0:07:19.680 reason we've kind of just accepted the fact that a 0:07:19.720 --> 0:07:22.480 certain amount of people are going to die each year 0:07:22.600 --> 0:07:26.320 driving on our roads. And I really am a true 0:07:26.360 --> 0:07:32.400 believer that autonomous vehicles can and eventually will change that. 0:07:32.560 --> 0:07:35.680 It's going to take a lot of time and a 0:07:35.720 --> 0:07:39.840 lot of hard work, obviously, to make that change, but 0:07:39.960 --> 0:07:43.480 I think that, you know, given that factual backdrop, our 0:07:43.520 --> 0:07:48.280 current status quo, it's a very worthwhile pursuit. And Elliott, 0:07:48.280 --> 0:07:50.760 you've tapped into something that I think really helps define 0:07:50.800 --> 0:07:54.040 restless ones, this idea of just because things are this 0:07:54.080 --> 0:07:56.400 way now doesn't mean that's how they have to be 0:07:57.000 --> 0:08:00.080 and that, through the application of technology, we can and 0:08:00.440 --> 0:08:05.200 envision and make that change. So Elliott, the Society of 0:08:05.240 --> 0:08:10.160 automotive engineers a while back define levels of autonomy from 0:08:10.280 --> 0:08:13.200 zero to five. Zero being there are no real driver 0:08:13.280 --> 0:08:16.119 assist features to speak of in the vehicle. Five being 0:08:16.720 --> 0:08:19.760 the vehicle does everything and there's no need for human 0:08:20.400 --> 0:08:22.880 oversight at all. When I talk to people I say 0:08:22.880 --> 0:08:26.440 we're probably to maybe on the cusp of three, but 0:08:26.560 --> 0:08:31.200 as that being too cynical, too pessimistic. Listen, we definitely 0:08:31.240 --> 0:08:34.440 have level two vehicles out on the road today and 0:08:34.480 --> 0:08:39.080 that's that's basically advanced driver assistance right. An easy example 0:08:39.200 --> 0:08:42.920 is Tesla auto pilot. But when we're talking about, you know, 0:08:42.960 --> 0:08:47.320 what I would call truly autonomous vehicles, we do have 0:08:47.400 --> 0:08:54.120 an extremely small volume of level four vehicles that exists today. 0:08:54.120 --> 0:08:59.160 A level four meaning the vehicles are truly autonomous. You 0:08:59.200 --> 0:09:01.360 can be sitting in the back seat of the car 0:09:01.520 --> 0:09:03.800 with no one sitting in the passenger seat or up 0:09:03.800 --> 0:09:05.960 front at all, but you can only do so in 0:09:06.080 --> 0:09:12.400 certain very specific operational design domains, which means the vehicles 0:09:12.440 --> 0:09:15.640 can only travel at certain times a day in very 0:09:15.720 --> 0:09:21.280 limited weather conditions and in very limited geographic areas. So 0:09:21.800 --> 0:09:27.120 to expand to more vehicles operating in larger geographic areas, 0:09:27.160 --> 0:09:30.120 in in areas where there may be rain or even 0:09:30.200 --> 0:09:34.960 snow that is going to be very, very difficult. And 0:09:35.040 --> 0:09:39.680 the issue is just how hard this problem is to solve, 0:09:39.720 --> 0:09:43.040 because if you think about it, if every day today, 0:09:43.120 --> 0:09:45.960 when you drive to work, you have to make an 0:09:46.040 --> 0:09:49.360 unprotected left hand turn, you know that you, the driver 0:09:49.559 --> 0:09:53.239 in the car, are very, very likely going to successfully 0:09:53.240 --> 0:09:56.800 make that unprotected left turn a hundred percent of the time. 0:09:57.160 --> 0:09:59.720 And for an autonomous vehicle it has to be the 0:09:59.760 --> 0:10:02.960 same right and if an autonomous vehicle makes that turn 0:10:03.040 --> 0:10:08.280 successfully nine times in a row but crashes on the 0:10:08.480 --> 0:10:14.720 thousandth attempt, that's arguably the worst automotive grade product in history. 0:10:15.080 --> 0:10:19.439 So it's an extremely high safety bar that the autonomous 0:10:19.480 --> 0:10:22.640 vehicle players need to hit and again, it's going to 0:10:22.679 --> 0:10:26.360 take a very long time to get there, but I 0:10:26.640 --> 0:10:30.280 do believe that it's a very worthwhile pursuit. Yeah, shy, 0:10:30.480 --> 0:10:32.760 can you talk a little bit about the guiding principle 0:10:32.800 --> 0:10:35.880 early on with Phantom motto. Yeah, it comes from my 0:10:35.920 --> 0:10:39.200 experience with wireless connectivity and Communication. You know, as we're 0:10:39.240 --> 0:10:41.840 talking right now, we can be in different places at 0:10:41.840 --> 0:10:44.600 the different times and still hear each other, see each 0:10:44.600 --> 0:10:47.079 other and help each other. Right. And when it comes 0:10:47.120 --> 0:10:49.520 to the future of technologies, when you look at the 0:10:49.640 --> 0:10:51.800 four g even and then five g and sixty in 0:10:51.800 --> 0:10:54.480 the future we're going to have more and more wireless 0:10:54.640 --> 0:10:58.600 connectivity and infrastructure and also technologies that would allow us 0:10:58.640 --> 0:11:02.000 to almost be in a different place in real time. 0:11:02.160 --> 0:11:04.760 You're not actually going to be there physically, but you 0:11:04.760 --> 0:11:07.880 will be able to help out. And we're looking at AI. 0:11:07.960 --> 0:11:10.520 You know, I remember when it started Phantom, before I 0:11:10.559 --> 0:11:12.880 came up with the idea, I started working on autonomous 0:11:12.920 --> 0:11:16.760 system and I built my first AI application. And getting 0:11:17.120 --> 0:11:21.400 a data set online gets you of accuracy, and then 0:11:21.480 --> 0:11:24.040 everything else is getting more and more difficult as you 0:11:24.080 --> 0:11:27.200 continue to develop your software and machine learning and practice 0:11:27.280 --> 0:11:29.840 more data. But it doesn't just get more difficult linear, 0:11:29.920 --> 0:11:32.439 it gets more exponential as you go towards the top. 0:11:32.480 --> 0:11:35.479 Once you're a ninet, you need trillions of data sets. 0:11:35.480 --> 0:11:38.240 So when we're looking at the technologies they're there. The 0:11:38.280 --> 0:11:41.480 problem is they can't cover the entire all the use cases, 0:11:41.520 --> 0:11:43.679 all the edge cases. And then I thought what if, 0:11:43.840 --> 0:11:48.120 with low latency communication, somebody can help out? It doesn't 0:11:48.120 --> 0:11:50.080 mean that they can jump in in the middle of driving, 0:11:50.400 --> 0:11:52.760 but if the vehicle recognized it as a problem and 0:11:52.800 --> 0:11:55.520 then it can slow down and stop in place, wait 0:11:55.600 --> 0:11:59.240 until someone remotely connects to it to figure out whether 0:11:59.280 --> 0:12:01.920 they need to to the sideway of the world or 0:12:02.080 --> 0:12:04.840 continue to do something around an object that is an 0:12:04.880 --> 0:12:07.800 obstacle that's in front of it. Broad construction areas, right, 0:12:07.800 --> 0:12:10.080 whether conditions. So that's when I thought, you know what 0:12:10.160 --> 0:12:12.320 if we have that human capability? So I started working 0:12:12.400 --> 0:12:16.040 on an engine for a video communication and data that 0:12:16.080 --> 0:12:18.600 allows you basically to see what's going on from the 0:12:18.640 --> 0:12:22.280 sensors like human, not like a machine. Right then be 0:12:22.360 --> 0:12:24.839 able to send commands back to the vehicle, assist the 0:12:24.920 --> 0:12:28.480 vehicle or remotely driving in certain cases that are very limited, 0:12:28.520 --> 0:12:32.959 at the speed, limited the constraints, and that basically resulted 0:12:32.960 --> 0:12:34.679 in the idea of a human in the loop. Right. 0:12:34.720 --> 0:12:37.720 So think about someone that can be sitting far away 0:12:37.760 --> 0:12:40.120 from where the vehicle is and getting a request. Hey 0:12:40.160 --> 0:12:42.440 know there's a vehicle in trouble here, can you help out? 0:12:42.480 --> 0:12:45.040 They assess the situation and, depends on the conditions, they 0:12:45.040 --> 0:12:47.199 can help out in different paths. Right some would be 0:12:47.200 --> 0:12:50.720 a bit more involved than others. That was the general idea. 0:12:50.840 --> 0:12:53.960 But more than that, something that we keep forgetting is 0:12:54.160 --> 0:12:56.640 computers have been out there now for forty or fifty 0:12:56.720 --> 0:12:59.760 years and there's still not perfect. There's no single computer 0:12:59.800 --> 0:13:01.679 syst them that you can say hey, no, that can 0:13:01.720 --> 0:13:05.320 never fail. It's a hundred percent secure from anything in 0:13:05.440 --> 0:13:08.480 any bugs, any edge cases, and I think that combination 0:13:08.520 --> 0:13:11.479 of machines and human at the same time is the strongest. 0:13:11.640 --> 0:13:15.400 If we can work together to accomplish autonomy, it's going 0:13:15.440 --> 0:13:17.080 to be much better and it's not this kind of 0:13:17.160 --> 0:13:20.520 a vivid idea of like a rosy picture of people 0:13:20.559 --> 0:13:23.000 and computers. I think we practice it every day when 0:13:23.040 --> 0:13:25.400 we're working on our computers and we see that there's 0:13:25.440 --> 0:13:27.559 certain things that we still gotta do, and I believe 0:13:27.559 --> 0:13:29.040 it that and I think that's not going to change. 0:13:29.040 --> 0:13:30.640 I think that's going to be the next couple of 0:13:30.640 --> 0:13:32.520 decades to come. We're still going to need to have 0:13:32.760 --> 0:13:36.280 human in the loop in every computer system, especially mission 0:13:36.280 --> 0:13:39.000 critical systems that we all depended on and we need 0:13:39.000 --> 0:13:40.800 that for our psychology and we need that to make 0:13:40.800 --> 0:13:42.800 them work and we need that to really deploy autonomous 0:13:42.840 --> 0:13:46.320 vehicles at scale. That's it must have. Yeah, you've touched 0:13:46.360 --> 0:13:48.280 on so much that I love to talk about on 0:13:48.360 --> 0:13:51.640 this show, like I love the idea of Ai being 0:13:51.679 --> 0:13:56.160 more about augmented intelligence, where the AI and the humans 0:13:56.640 --> 0:14:00.040 are working together so that the AI is an a 0:14:00.080 --> 0:14:03.200 willing people to do their jobs better than they could before, 0:14:03.360 --> 0:14:06.840 as opposed to the AI has stepped in and humans 0:14:06.840 --> 0:14:10.800 have become unnecessary. I find it phenomenal that the convergence 0:14:10.840 --> 0:14:15.200 and technologies have enabled this approach, largely in the sense 0:14:15.240 --> 0:14:18.560 of of that low latency, because that was, I think, 0:14:18.600 --> 0:14:22.080 a huge hurdle for us to overcome, and we're entering 0:14:22.120 --> 0:14:24.920 into a world where we're getting that same sort of 0:14:24.960 --> 0:14:29.440 low latency, high throughput capability, but now we're not constrained 0:14:29.480 --> 0:14:32.240 by tethers, which obviously, in the in the case of 0:14:32.800 --> 0:14:37.880 being able to potentially control a car remotely, is absolutely critical. Right. 0:14:37.920 --> 0:14:40.560 You can't have any latency there. When you're talking about 0:14:40.600 --> 0:14:43.720 moving a vehicle that has some form of cargo in it, 0:14:43.800 --> 0:14:46.640 whether it's people or products or whatever, and there are 0:14:46.680 --> 0:14:49.440 other vehicles on that road as well. There are real 0:14:49.520 --> 0:14:51.480 time events that are happening, so you have to be 0:14:51.520 --> 0:14:54.320 able to see and react in that real time as 0:14:54.360 --> 0:14:56.560 if you were physically behind the wheel of the car. 0:14:57.000 --> 0:15:01.520 I'm very curious about what your approach was to ensure 0:15:02.000 --> 0:15:07.200 that low latency, to enable this technology. Right. So we 0:15:07.240 --> 0:15:09.480 can talk about the approach of specifically how we solve 0:15:09.560 --> 0:15:12.760 for low latency and communication, but before we get there, 0:15:12.800 --> 0:15:15.560 I think just taking a look at the history, right. 0:15:15.560 --> 0:15:17.800 So we started a couple of decades ago. I think 0:15:18.080 --> 0:15:19.960 even when I was a child, like ten years ago, 0:15:20.160 --> 0:15:22.360 video communication like the one we're having now, you know, 0:15:22.440 --> 0:15:24.720 that didn't exist at the time, and let alone like 0:15:24.760 --> 0:15:27.080 twenty years ago, when it was only just giant phones, 0:15:27.160 --> 0:15:28.840 when I don't even have to make a phone call 0:15:28.880 --> 0:15:30.800 and you barely can hear the other person, you know. 0:15:30.840 --> 0:15:33.640 So you can see that there's progress and evolution around 0:15:33.800 --> 0:15:36.720 communication that is definitely trending in the right direction to 0:15:37.120 --> 0:15:40.480 enable things like that. If you read online about five 0:15:40.560 --> 0:15:43.920 g low latency capabilities and and in the future of 0:15:43.960 --> 0:15:46.920 things like six G, everything points that we're working on 0:15:47.000 --> 0:15:50.520 getting low latency communication. So first of all places or 0:15:50.560 --> 0:15:52.480 areas where it may not be the case yet, it 0:15:52.520 --> 0:15:55.040 will happen eventually and we're a big believer in that. 0:15:55.200 --> 0:15:57.400 So that's number one. Number two is the design of 0:15:57.440 --> 0:16:01.760 the vehicle. We believe that the vehicle safety sensor system 0:16:01.960 --> 0:16:05.760 must be intact in order for a remote operator to 0:16:05.800 --> 0:16:08.480 get in. So meaning if the safety system is disabled 0:16:08.600 --> 0:16:10.960 or not working or as a problem that dissevered with 0:16:10.960 --> 0:16:13.680 the vehicle, the human operator will not intervene with the vehicle. 0:16:13.800 --> 0:16:16.560 They can guide, they can give some information, some logs 0:16:16.600 --> 0:16:18.880 and pointing a direction to the vehicle, but they can't 0:16:18.880 --> 0:16:20.680 really drive it. They can only drive it when the 0:16:20.720 --> 0:16:23.640 safety system is working, and the safety system is the 0:16:23.680 --> 0:16:26.480 baseline protection of the vehicle. That's how we should think 0:16:26.520 --> 0:16:28.440 about it, almost like a guardian. Think about like a 0:16:28.480 --> 0:16:31.480 circle around the vehicle, like your Aida System Today, and 0:16:31.560 --> 0:16:35.480 the idea is that the remote operator can communicate with 0:16:35.520 --> 0:16:38.080 that system and say, Hey, you know, you're now detecting 0:16:38.080 --> 0:16:41.240 an object, but listen, if you reduce that distance from 0:16:41.280 --> 0:16:44.000 an object but another a couple of inches backwards, closer 0:16:44.040 --> 0:16:47.840 to the vehicle, then you will be allowed to proceed. Right. 0:16:47.960 --> 0:16:50.320 So that that's a huge idea. Now it's all within 0:16:50.840 --> 0:16:54.640 predefined area of operation. So again we have a guardian 0:16:54.680 --> 0:16:56.320 for the vehicle, and this is one of the reasons 0:16:56.520 --> 0:16:59.720 why we are not working with forklifts in warehouses, where 0:17:00.120 --> 0:17:02.440 you don't have that same problem like auton was vehicles, 0:17:02.480 --> 0:17:05.280 where their safety systems are just not not there yet. 0:17:05.320 --> 0:17:08.440 You know, they're overly conservative. You can't really adjust them 0:17:08.480 --> 0:17:10.720 because there's too much risk on the table. And we're 0:17:10.760 --> 0:17:13.320 looking at the forklift in the warehouse. The speed is 0:17:13.400 --> 0:17:15.600 much lower, so you're allowed to work together with the 0:17:15.600 --> 0:17:17.920 safety system to achieve the task, which is to drive 0:17:17.960 --> 0:17:20.440 to somewhere, pick up a palette, places on the racks 0:17:20.520 --> 0:17:22.880 or load the truck and so on. Some places really 0:17:23.000 --> 0:17:26.280 have a bad network right as five g continues to 0:17:26.520 --> 0:17:29.679 roll out in different places all around the country. We 0:17:30.000 --> 0:17:32.320 have a niche today that we're very successful at and 0:17:32.359 --> 0:17:35.439 we're proud that we're making impact in the labor and 0:17:35.480 --> 0:17:38.760 logistics where the market really needs Phantom today, and that's 0:17:38.800 --> 0:17:41.000 in closed environment. Right. So in the closed environment, when 0:17:41.000 --> 0:17:45.200 you have a warehouse or the yard operation areas where 0:17:45.240 --> 0:17:47.639 you can actually install better network conditions, you know if 0:17:47.640 --> 0:17:49.280 you have an issue with the networking, you know, you 0:17:49.320 --> 0:17:51.640 map the network, you see that there's not enough bandwidth 0:17:51.680 --> 0:17:55.040 for upload or download and and basically your request to 0:17:55.080 --> 0:17:57.639 get a better network conditions in this specific area. And 0:17:57.680 --> 0:18:00.159 there we go. So that's the infrastructure side. Now the 0:18:00.200 --> 0:18:03.440 text site. We have the ability to bond multiple networks. 0:18:03.520 --> 0:18:05.000 You can think of it as it can be a 0:18:05.000 --> 0:18:09.119 couple of networks together. Each packet of our software is 0:18:09.160 --> 0:18:12.159 being sent to the best network available, right. So you 0:18:12.160 --> 0:18:15.919 have basically packets routing and each package that its own criticality. Right. 0:18:15.960 --> 0:18:18.000 So if you have a data channel versus a video 0:18:18.040 --> 0:18:20.040 channel and the data is to break system, so you 0:18:20.119 --> 0:18:22.280 have to have that over all the channels, to have 0:18:22.359 --> 0:18:25.840 multiple redundancy layers where you know something that is less important. Right. 0:18:25.880 --> 0:18:28.120 So we have some prioritization and bonding systems that would 0:18:28.119 --> 0:18:31.000 build some deep technology and I P that. You know, 0:18:31.080 --> 0:18:33.280 we spent a lot of time with money working on 0:18:33.320 --> 0:18:35.040 the first couple of years of the company. That same 0:18:35.040 --> 0:18:38.600 technology works for cars, for trucks, for forklifts, for you know, 0:18:38.680 --> 0:18:41.639 delivery robots, and we believe again, as the future and 0:18:41.680 --> 0:18:44.240 infrastructure continuous to evolve, that's going to apply there as well. 0:18:45.119 --> 0:18:48.679 And I definitely want to talk more about the forklifts 0:18:48.680 --> 0:18:51.520 in particular. Can you talk a bit about some of 0:18:52.240 --> 0:18:55.560 the challenges that this remote operation helps solve? I know 0:18:55.640 --> 0:18:59.600 that like labor shortage being a huge one, obviously. So, 0:19:00.040 --> 0:19:04.199 first of all, we are squarely in the logistics sector. 0:19:04.600 --> 0:19:08.679 Our hottest application right now is remotely operated forklifts. We 0:19:08.760 --> 0:19:12.879 also do work with yard trucks and distribution center yards and, 0:19:13.080 --> 0:19:16.200 first and last, mild delivery with robots. But when you're 0:19:16.200 --> 0:19:18.639 talking about the logistics space, you hit the nail on 0:19:18.680 --> 0:19:21.719 the head right. There's been a labor shortage in the 0:19:21.760 --> 0:19:26.000 sector for decades. That's become much more acute in the 0:19:26.040 --> 0:19:29.879 past couple of years, in which many believe, for a 0:19:30.000 --> 0:19:34.960 myriad of factors, is our new status quo. And our 0:19:35.000 --> 0:19:40.560 customers have traditionally had to hire, for example, forklift operators 0:19:40.600 --> 0:19:46.120 that are in commuting distance of their facilities. But our 0:19:46.240 --> 0:19:52.199 Technology d couples Labor from location right we remove the 0:19:52.280 --> 0:19:57.919 geographic restriction to hiring because with remotely operated forklifts you 0:19:57.960 --> 0:20:01.119 can have someone doing that exact same work in the 0:20:01.160 --> 0:20:04.359 exact same warehouse but be sitting, you know, up to 0:20:04.600 --> 0:20:08.840 thousands of miles away. So instead of having to hire 0:20:08.960 --> 0:20:13.800 people only within commuting distance of the facility. We're turning 0:20:13.880 --> 0:20:19.080 that Labor pool into literally anyone located pretty much anywhere. 0:20:19.960 --> 0:20:25.040 So our customers are using our remote operation platform to 0:20:25.800 --> 0:20:28.800 connect people all around the country who want need to 0:20:28.840 --> 0:20:32.320 work right especially coming out of the pandemic, with the 0:20:32.440 --> 0:20:37.240 hundreds of thousands of essential jobs that must be filled 0:20:37.560 --> 0:20:42.960 to keep our supply chain intact. Labor is the key 0:20:43.160 --> 0:20:46.840 top line problem right now for our customer base. Yeah, 0:20:46.920 --> 0:20:49.720 I didn't have a deep appreciation for how delicate the 0:20:49.760 --> 0:20:53.119 supply chain was until the pandemic and we saw the 0:20:53.160 --> 0:20:56.720 disruption of the supply chain acted out on a global scale, 0:20:57.160 --> 0:21:02.080 affecting every industry, particular lead computer and Electronics Industries, as 0:21:02.119 --> 0:21:08.120 the semiconductor shortage exacerbated that problem, and I realized that 0:21:08.200 --> 0:21:10.760 you could think of the supply chain operating almost like 0:21:10.880 --> 0:21:16.320 an electric utility and that it's frequently operating near Max 0:21:16.400 --> 0:21:20.160 capacity and that anything that would push it beyond that. 0:21:20.240 --> 0:21:24.040 Suddenly you realize how delicate the system was and when 0:21:24.080 --> 0:21:27.080 you pair that also with this growing trend of a 0:21:27.119 --> 0:21:31.560 desire to work remotely, which is happening both in white 0:21:31.560 --> 0:21:35.120 color and blue color jobs, you realize that this is 0:21:35.240 --> 0:21:37.800 also a solution for that as well, where it enables 0:21:37.840 --> 0:21:40.440 people to have that kind of life where they are 0:21:40.480 --> 0:21:45.040 able to work remotely. If covid taught us anything, it's that, 0:21:45.640 --> 0:21:48.360 you know, remote work is probably here to stay. Right 0:21:48.440 --> 0:21:51.760 the face of work, I believe, has changed forever, but 0:21:52.040 --> 0:21:55.639 times like Covid have taught us that there are times 0:21:55.720 --> 0:21:58.679 when remote work isn't just a nice to have, it 0:21:58.800 --> 0:22:02.280 is a half to have. And what we're doing is 0:22:02.400 --> 0:22:08.480 we're providing warehouse workers that same privilege to work remotely. Right, 0:22:09.000 --> 0:22:14.320 I think that we have an ability to positively impact 0:22:14.760 --> 0:22:18.840 the lives of, you know, the backbone of our supply chain, 0:22:18.960 --> 0:22:22.879 these warehouse workers, while at the same time providing a 0:22:23.000 --> 0:22:28.240 technology to their employers that is solving one of their 0:22:28.280 --> 0:22:33.399 major challenges, which is not only finding labor but retaining 0:22:33.440 --> 0:22:36.040 that Labor right, because a lot of times working in 0:22:36.080 --> 0:22:40.080 a warehouse is really hard work in a pretty tough environment, 0:22:40.240 --> 0:22:43.240 and their safety issues. To write. One in ten forklifts 0:22:43.280 --> 0:22:46.240 are involved in a in an accident each year which 0:22:46.280 --> 0:22:51.120 can cause, you know, serious injury, sometimes even death, unfortunately. 0:22:51.520 --> 0:22:55.040 So if you can remove those operators out of that 0:22:55.359 --> 0:23:01.359 potentially hazardous and definitely uncomfortable environment in put them into 0:23:01.800 --> 0:23:05.000 an office environment where they're sitting with other colleagues and 0:23:05.040 --> 0:23:07.640 they're doing the exact same job, but you know, it's 0:23:07.680 --> 0:23:09.960 seventy degrees and they can have a cup of coffee 0:23:09.960 --> 0:23:14.040 while doing that. We strongly believe that that is going 0:23:14.080 --> 0:23:17.359 to be preferred by both sides, meaning the employers, the 0:23:17.400 --> 0:23:25.760 companies and also their workforce. Conventional Thinking says you have 0:23:25.880 --> 0:23:28.360