WEBVTT 00:00.700 --> 00:03.283 (techno music) 00:09.154 --> 00:11.351 ^- AFRL Commander's Challenge is a unique opportunity 00:11.351 --> 00:14.561 ^for young engineers, and not just engineers 00:14.561 --> 00:17.093 but the young workforce as a whole. 00:17.093 --> 00:20.139 The teams are constructed regionally by a base, 00:20.139 --> 00:21.801 a base identifies that they wanna try 00:21.801 --> 00:23.433 to compete in this year's challenge. 00:23.433 --> 00:24.476 We have psychologists on the teams, 00:24.476 --> 00:25.981 we have program managers, 00:25.981 --> 00:28.576 we have security forces personnel, 00:28.576 --> 00:30.392 we have maintenance personnel, 00:30.392 --> 00:32.026 we have some people that are on the team 00:32.026 --> 00:34.343 not really because they have any engineering background 00:34.343 --> 00:36.222 whatsoever, but they understand a certain aspect 00:36.222 --> 00:38.389 of the particular problem. 00:39.015 --> 00:43.175 ^- The problem is, is that UAS, unmanned aircraft systems, 00:43.175 --> 00:46.493 ^have always been around but they are proliferating 00:46.493 --> 00:49.675 at a rate right now which is comparable 00:49.675 --> 00:52.816 to the same as smart phones have in the past. 00:52.816 --> 00:56.733 It's a really easy trend, commercial trend line 00:57.715 --> 01:00.048 for people who wanna do harm 01:00.128 --> 01:02.795 to the US or to other countries, 01:02.857 --> 01:05.706 to basically leverage those commercial trends 01:05.706 --> 01:07.789 and cause harm with them. 01:08.495 --> 01:11.328 (engine whirring) 01:11.715 --> 01:13.458 ^- For the teams, we really wanted to instill in them 01:13.458 --> 01:17.625 ^first of all that motivation, that intrinsic reason 01:17.632 --> 01:20.132 why they joined this challenge 01:20.349 --> 01:23.493 and then build on it with characteristics, 01:23.493 --> 01:27.660 with principles, with tools, and process for innovation. 01:28.573 --> 01:31.101 ^- If you ask the infrastructure 01:31.101 --> 01:33.723 ^that we always used to solve problems 01:33.723 --> 01:36.409 ^you're gonna get the same answers all the time. 01:36.409 --> 01:38.830 If you ask people who haven't been presented 01:38.830 --> 01:41.933 with that problem or are new you're gonna get fresh ideas. 01:41.933 --> 01:44.989 - I saw it as basically a once in a lifetime opportunity, 01:44.989 --> 01:46.832 especially this early on in my career. 01:46.832 --> 01:49.581 ^With the whole rapid prototyping, designing, 01:49.581 --> 01:51.633 ^kinda going off on your own as a team, 01:51.633 --> 01:53.257 ^I thought it'd be a good opportunity, 01:53.257 --> 01:55.038 one to fashion my teamwork skills 01:55.038 --> 01:57.243 but also hopefully find some sort of solution 01:57.243 --> 02:00.445 or begin to find a solution for a real-world problem 02:00.445 --> 02:01.903 that's affecting the Air Force 02:01.903 --> 02:03.891 and a lot of other services today. 02:03.891 --> 02:07.095 - And the beautiful thing is that older guys, 02:07.095 --> 02:10.280 kinda like myself, we look at a problem a certain way 02:10.280 --> 02:12.868 and the younger generation says, 02:12.868 --> 02:14.358 "Hey, what if we use social media? 02:14.358 --> 02:15.787 "Or what if we used our smart phones?" 02:15.787 --> 02:18.042 Things that someone who didn't grow up with it, 02:18.042 --> 02:21.542 as I did not, might not have thought about 02:21.586 --> 02:24.312 and that young, fresh perspective 02:24.312 --> 02:27.858 yields solutions that we might not have otherwise found. 02:27.858 --> 02:29.355 - I'm hoping they come up with something 02:29.355 --> 02:31.081 I've never thought of and the people that I work for 02:31.081 --> 02:32.705 have never thought of. 02:32.705 --> 02:35.561 We take a look at what was great about every single one 02:35.561 --> 02:37.649 of the projects and what's valuable, 02:37.649 --> 02:39.039 what can be taken away. 02:39.039 --> 02:40.741 Then the Air Force, once we're ready, 02:40.741 --> 02:42.961 can figure out how we're gonna implement that 02:42.961 --> 02:44.794 back into our process. 02:46.794 --> 02:48.201 ^- In June we were given that incredibly broad 02:48.201 --> 02:49.692 ^problem statement, right? 02:49.692 --> 02:51.631 Detect and defend US military locations 02:51.631 --> 02:53.735 from unmanned air vehicle threats. 02:53.735 --> 02:55.140 - When you look at security, 02:55.140 --> 02:56.628 when you look at defeating threats, 02:56.628 --> 02:58.853 security is always slightly delayed 02:58.853 --> 03:01.420 from when threats actually develop 03:01.420 --> 03:03.535 ^'cause you can't counter, you can't guess 03:03.535 --> 03:05.579 ^and play the what if game in security 03:05.579 --> 03:08.354 ^so once a threat develops, that's when you start 03:08.354 --> 03:12.521 ^developing your counter measures to defeat that threat. 03:14.796 --> 03:16.737 - We basically threw a bunch of darts on the board. 03:16.737 --> 03:19.268 ^People had these random ideas for, 03:19.268 --> 03:20.920 ^not even just mitigation at that point, 03:20.920 --> 03:24.139 ^but attack, track, identify, and then mitigate. 03:24.139 --> 03:26.414 - When we realized that we weren't just trying 03:26.414 --> 03:29.997 ^to defeat one model of UAV that you can buy 03:30.451 --> 03:33.823 ^from Walmart that's gonna come in so we couldn't build 03:33.823 --> 03:36.846 a system that was specific to one type of drone 03:36.846 --> 03:39.490 and so we started with this architecture, 03:39.490 --> 03:41.366 saying, "We need to connect multiple things, 03:41.366 --> 03:44.116 "now where can we be innovative?" 03:48.518 --> 03:51.108 ^- Our concept, we wanted to give a multilayered approach. 03:51.108 --> 03:53.606 ^So instead of concentrating on a specific solution 03:53.606 --> 03:57.523 ^for one threat or scenario we wanted to be able 03:57.574 --> 03:59.652 to cover a couple different scenarios 03:59.652 --> 04:01.187 so we had a multilayered approach. 04:01.187 --> 04:05.270 ^- We came up with using a radar and camera system 04:06.124 --> 04:08.357 to detect and identify the drones 04:08.357 --> 04:11.136 and then we engaged them using a jammer 04:11.136 --> 04:14.926 and so once it's jammed it might land or hover 04:14.926 --> 04:16.698 and once it goes into that mode 04:16.698 --> 04:19.508 we can hit it with a net gun to safely capture it, 04:19.508 --> 04:20.993 retrieve it for forensic use later. 04:20.993 --> 04:22.316 ^- As far as engaging a UAS 04:22.316 --> 04:24.550 ^we primarily opted with electronic warfare. 04:24.550 --> 04:28.681 In particular we developed a software-defined radio platform 04:28.681 --> 04:31.094 where we can selectively disrupt signals 04:31.094 --> 04:34.613 to take down enemy UASes without necessarily 04:34.613 --> 04:36.569 disrupting our own communications. 04:36.569 --> 04:38.398 - We have two different ways of detecting 04:38.398 --> 04:42.021 both their GPS coordinates and with the sounds 04:42.021 --> 04:44.992 ^that they make and then for taking them down 04:44.992 --> 04:48.807 ^we use a long-range jammer and a hunter killer drone 04:48.807 --> 04:52.854 ^that has a mounted shotgun on it, 12-gauge shotgun. 04:52.854 --> 04:54.851 ^- Our overall concept is called the SPIDR 04:54.851 --> 04:57.301 ^and that stands for sense, predict, 04:57.301 --> 04:59.718 intercept, deny, and recover. 04:59.955 --> 05:02.535 And it's a two-part system, there's a ground component 05:02.535 --> 05:05.167 and an airborne platform and so the ground component, 05:05.167 --> 05:08.448 it's a series of electrical optical cameras 05:08.448 --> 05:10.815 and a laser designator on a gimbal, 05:10.815 --> 05:14.302 and that picks up the initial detection of an intruder. 05:14.302 --> 05:18.032 And once a intruder has been identified and tracked 05:18.032 --> 05:21.628 it passed it over to, we have a blue force UAV, 05:21.628 --> 05:25.795 a net system that takes off and goes after and captures it. 05:30.995 --> 05:32.559 ^- We're foaming at the mouth for this 05:32.559 --> 05:34.164 ^because we know what it can do 05:34.164 --> 05:36.393 ^and we're excited to show it off 05:36.393 --> 05:39.140 ^and we wanna get the reactions, you know. 05:39.140 --> 05:41.256 Everybody wants to hear the oohs and ahs. 05:41.256 --> 05:43.479 With wanna hear those reactions from the judges 05:43.479 --> 05:45.651 and we're ready to win this, 05:45.651 --> 05:48.488 let's go where the rubber meets the road, let's get it done. 05:48.488 --> 05:51.292 - Our solution is probably very different than the others 05:51.292 --> 05:54.904 in that we've established the building blocks 05:54.904 --> 05:57.483 on which the best parts of the other solutions 05:57.483 --> 05:59.171 should be able to plug and play. 05:59.171 --> 06:01.072 - What distinguishes team Smarthawk Solution 06:01.072 --> 06:03.864 is its multilayered, we have multiple methods of detection, 06:03.864 --> 06:06.915 multiple layers of alert, multiple methodologies 06:06.915 --> 06:08.686 for take down or mitigation. 06:08.686 --> 06:11.900 - I think we're in a very good position 06:11.900 --> 06:15.483 because our solution, it's not only capable 06:15.898 --> 06:19.398 but it's very flexible and it's adaptable. 06:20.478 --> 06:24.043 - One of the big things we look for is innovation 06:24.043 --> 06:27.385 ^and we kinda judge how they saw the problem 06:27.385 --> 06:28.565 ^and how they tackled the problem. 06:28.565 --> 06:30.807 ^It's really more an education piece 06:30.807 --> 06:34.253 ^for the young officer civilians than it is 06:34.253 --> 06:36.346 the actual solution piece that we're getting out of it. 06:36.346 --> 06:39.545 ^- Just seeing all the various ideas that are presented 06:39.545 --> 06:41.700 ^and how different approaches that are used 06:41.700 --> 06:43.977 because one approach isn't gonna solve all problems 06:43.977 --> 06:45.831 so this is kind of a nice way of doing it. 06:45.831 --> 06:47.750 - As a judge I'm looking for innovation. 06:47.750 --> 06:49.781 I'm not looking for somebody just to take 06:49.781 --> 06:52.599 ^and repackage an existing solution. 06:52.599 --> 06:54.658 ^That's lazy, we're looking for the people 06:54.658 --> 06:56.597 ^that are gonna go the hard route, 06:56.597 --> 06:58.009 that are gonna find an idea 06:58.009 --> 07:02.176 or try and innovate in a new space to solve this problem. 07:02.285 --> 07:03.569 - And then it'll move into 07:03.569 --> 07:05.612 and descend to 50 meters altitude. 07:05.612 --> 07:07.095 - So this particular exercise 07:07.095 --> 07:09.392 is for countering UAS operations 07:09.392 --> 07:13.309 ^so we've got a red side, you know, the bad guys 07:13.676 --> 07:16.907 with platforms, the multirotors and the fixed wing platforms 07:16.907 --> 07:20.065 that are simulated threats to a forward 07:20.065 --> 07:21.888 operating-based type of scenario. 07:21.888 --> 07:25.508 ^- Right now my favorite one to fly is the FPV racing quad, 07:25.508 --> 07:27.855 ^so it's a small 250-size quad rotor. 07:27.855 --> 07:30.124 It's fast, it's agile, and I get to fly it. 07:30.124 --> 07:32.619 It's all RC so I get to pretty much make it up, 07:32.619 --> 07:34.817 little freelancing, I get to go fast, I get to go high, 07:34.817 --> 07:37.018 low, and slow and I feel pretty confident 07:37.018 --> 07:38.286 against the other teams, 07:38.286 --> 07:39.533 I don't think they'll be able to catch me. 07:39.533 --> 07:41.875 ^- We've got a variety of different scenarios 07:41.875 --> 07:44.458 ^that involve a number of RCMAs, 07:44.832 --> 07:47.054 remotely-controlled model aircraft, 07:47.054 --> 07:51.221 and also small UAS, or automated aerial system vehicles. 07:54.207 --> 07:57.399 ^- I think it went good, I think we're a little disappointed, 07:57.399 --> 07:59.257 ^you know, we couldn't take down 07:59.257 --> 08:01.182 ^another UAV with our hack sound 08:01.182 --> 08:04.017 ^but once again, we still kinda are just showing 08:04.017 --> 08:07.017 a prototype and a concept so I think 08:07.159 --> 08:08.958 it was still cool to see it flying 08:08.958 --> 08:11.053 and yeah, there's a little disappointment there 08:11.053 --> 08:13.776 but I still think, I feel a sense of accomplishment 08:13.776 --> 08:15.593 and I think the rest of the team does, too. 08:15.593 --> 08:18.663 - We actually got the jammer working for the judges 08:18.663 --> 08:21.817 ^and we were able to do a longer-range test 08:21.817 --> 08:25.114 ^that was a little off plan, just to show 'em 08:25.114 --> 08:28.697 how well our jammer works at longer ranges. 08:30.249 --> 08:32.216 - We responded to some UAV threats 08:32.216 --> 08:33.358 ^that would happen in the area. 08:33.358 --> 08:34.680 ^We picked 'em up on our radar, 08:34.680 --> 08:37.759 ^our operator was able to pick up the drones 08:37.759 --> 08:41.842 and therefore alert the simulated security forces 08:43.133 --> 08:46.727 that would generally come out to respond to the situation. 08:46.727 --> 08:49.885 ^- I think we had a successful end result. 08:49.885 --> 08:52.501 I mean, we were able to jam pretty much 08:52.501 --> 08:56.251 every drone or everything they kinda put out. 08:56.990 --> 08:58.420 ^- Yes, we do have some successes. 08:58.420 --> 09:01.450 ^Flying fully autonomously with the drone 09:01.450 --> 09:03.701 ^just thinking for itself didn't work so well 09:03.701 --> 09:05.139 but switching back over for it 09:05.139 --> 09:09.306 to receive stuff from like the pilot, that was fine, 09:09.313 --> 09:11.748 we can still get coordinates, we can still pass over, 09:11.748 --> 09:13.428 so all that was fine it was just letting the drone 09:13.428 --> 09:15.490 think for itself that became a problem. 09:15.490 --> 09:16.969 - We got to knock some stuff out of the air, 09:16.969 --> 09:19.219 ^so to me that was a success 09:20.035 --> 09:22.979 ^and getting the detect and tracking kinda going 09:22.979 --> 09:25.613 was a big success, those was our first time 09:25.613 --> 09:27.742 being able to track with the water can 09:27.742 --> 09:29.364 and with the drone flying in the air. 09:29.364 --> 09:32.320 ^- Every team has had a certain amount of success, 09:32.320 --> 09:35.017 ^every team has had a certain amount of failure, 09:35.017 --> 09:37.265 and every team has had a certain amount 09:37.265 --> 09:40.201 of missed opportunity and it's interesting to hear them talk 09:40.201 --> 09:41.815 and look over at the guy sitting next to them 09:41.815 --> 09:43.300 during the event and say, 09:43.300 --> 09:44.999 "Wow, if I would have thought of that, 09:44.999 --> 09:48.660 "put it into mind I might've been able to do this or that." 09:48.660 --> 09:51.355 And it's a whole nother level of excitement 09:51.355 --> 09:53.087 because now they're getting to the end 09:53.087 --> 09:54.463 and they're stressed and frustrated 09:54.463 --> 09:56.946 and then it's a rebirth of that excitement 09:56.946 --> 09:58.730 of the experience, to see that. 09:58.730 --> 10:00.330 - One of the big thins I learned as well, 10:00.330 --> 10:01.933 I've worked at the Air Force research lab 10:01.933 --> 10:04.269 for about five years, I always worked 10:04.269 --> 10:06.021 sort of in a tight-knit little area 10:06.021 --> 10:08.028 where it was just sort of, 10:08.028 --> 10:10.643 the people I work with directly in my lab 10:10.643 --> 10:13.133 and then a couple other labs working with similar systems. 10:13.133 --> 10:15.760 But with this project we went and we talked to 10:15.760 --> 10:18.427 directorates all throughout AFRL 10:18.646 --> 10:21.657 asking them, "Hey, what have you guys done 10:21.657 --> 10:25.182 "with either counter UAV systems or something similar?" 10:25.182 --> 10:28.406 Maybe they just track missiles or they track mortar fire, 10:28.406 --> 10:30.295 well that's still something very small and fast 10:30.295 --> 10:32.403 so if they can do that then maybe we can implement it 10:32.403 --> 10:34.247 for what we're doing and what we found 10:34.247 --> 10:36.091 is everyone is super helpful. 10:36.091 --> 10:38.849 - I didn't really realize, I kind of expected coming in 10:38.849 --> 10:42.009 that this was gonna be a sheerly tactical challenge. 10:42.009 --> 10:44.933 ^In my career field we were focused on tactical challenges, 10:44.933 --> 10:47.342 ^that's our thing, you give us a problem 10:47.342 --> 10:50.081 ^and say, it's kinda like a square peg in a round hole, 10:50.081 --> 10:52.982 ^like, "This is what we got, this is where we need to go." 10:52.982 --> 10:56.118 Try to take in all those personnel challenges 10:56.118 --> 10:58.701 and learn how to manage a team, 10:59.282 --> 11:02.472 how to keep everybody in good spirits and even just down to, 11:02.472 --> 11:04.630 like when we were on the range yesterday 11:04.630 --> 11:06.806 you could take your time and slowly get things set up 11:06.806 --> 11:08.661 but keep that morale drive and say, 11:08.661 --> 11:10.422 "All right guys, we're gonna get out there, 11:10.422 --> 11:12.130 "get unloaded faster than everybody else, 11:12.130 --> 11:13.787 "we're gonna get set up and we're gonna be 11:13.787 --> 11:15.159 "sitting there calibrating 11:15.159 --> 11:16.950 "while everybody else is still wrenching on parts." 11:16.950 --> 11:19.367 - I'm a student of leadership 11:20.280 --> 11:24.132 and this provided an awesome leadership laboratory for me. 11:24.132 --> 11:27.799 I learned that leading a group of civilians, 11:29.013 --> 11:33.180 especially civilian engineers, is a challenging task. 11:34.053 --> 11:38.220 Once you're able to mold a team into a cohesive unit 11:39.394 --> 11:41.477 it really comes together. 11:42.080 --> 11:44.663 (upbeat music)