WEBVTT 00:00.640 --> 00:02.060 - [Announcer] Ladies and gentlemen, 00:02.060 --> 00:05.280 ladies and gentlemen please welcome to the stage 00:05.280 --> 00:10.280 AFA's National Director, East Area, Major Tyler Johnson. 00:11.545 --> 00:14.462 (triumphant music) 00:15.719 --> 00:17.969 (applause) 00:19.260 --> 00:21.500 - Good morning and thank you. 00:21.500 --> 00:22.960 The topic of our next session is 00:22.960 --> 00:25.463 Global Operational Perspectives on MDO. 00:26.300 --> 00:28.660 To fight and win against peer enemy advance threats, 00:28.660 --> 00:30.740 our airmen must rapidly and reliably 00:30.740 --> 00:32.940 integrate and employ MDO capabilities 00:32.940 --> 00:34.230 from the heart of our homeland 00:34.230 --> 00:36.543 to any battle space, anywhere on the planet. 00:37.730 --> 00:39.590 If our airmen engaged in airspace 00:39.590 --> 00:41.290 and cyber multi-domain operations 00:41.290 --> 00:44.180 can depend upon real-time fused situational awareness, 00:44.180 --> 00:45.710 our adversaries will be forced to contend 00:45.710 --> 00:47.783 with overwhelming violence and lethality. 00:48.950 --> 00:51.300 The Department of Defense should lead the world 00:51.300 --> 00:52.310 in situational awareness 00:52.310 --> 00:54.823 and fusion capabilities, but it isn't. 00:56.210 --> 00:58.560 Even commercial enterprises have more robust capabilities 00:58.560 --> 01:01.610 to track assets and operations worldwide. 01:01.610 --> 01:03.300 No doubt that in the incredible partnership 01:03.300 --> 01:05.460 between our enemy, our, excuse me, 01:05.460 --> 01:06.780 our airmen and industry, 01:06.780 --> 01:08.470 we can and will develop and field 01:08.470 --> 01:12.110 the C2 and Decision systems that our war fighters must have. 01:12.110 --> 01:14.060 Our panel this morning will address 01:14.060 --> 01:15.920 the joint all-domain command and control requirements 01:15.920 --> 01:18.020 and systems needed to dominate our enemies 01:18.020 --> 01:19.573 across our combatant commands. 01:20.410 --> 01:21.950 Our panel includes 01:21.950 --> 01:24.440 General Terrence J. O'Shaughnessy, Commander, 01:24.440 --> 01:26.350 North American Aerospace Defense Command 01:26.350 --> 01:27.650 and U.S. Northern Command. 01:28.730 --> 01:30.770 General Charles Q. Brown Jr., Commander, 01:30.770 --> 01:32.310 Pacific Air Forces. 01:32.310 --> 01:35.110 And finally, General Jeffrey L. Harrigian, Commander, 01:35.110 --> 01:37.490 U.S. Air Forces in Europe. 01:37.490 --> 01:40.070 Copies of their bios are in your program. 01:40.070 --> 01:41.400 I will now turn over the podium 01:41.400 --> 01:43.070 to AFA's President Orville Wright 01:43.070 --> 01:45.520 to begin the panel and moderate the Q and A. 01:45.520 --> 01:48.260 To submit questions, please go to slido.com 01:48.260 --> 01:51.330 and enter the code AWS20 on the website 01:51.330 --> 01:53.120 where you can submit your questions. 01:53.120 --> 01:54.358 General Wright, over to you, sir. 01:54.358 --> 01:55.191 - Thanks, Tyler. 01:55.191 --> 01:57.441 (applause) 02:01.460 --> 02:03.290 Well special thanks to Tyler. 02:03.290 --> 02:06.260 As you might see, this group's getting a bit older 02:06.260 --> 02:08.650 and the future of our Air Force Association, 02:08.650 --> 02:10.529 in fact you just met one of our board members, 02:10.529 --> 02:13.920 Tyler Johnson, is in the hands of great leaders like Tyler. 02:13.920 --> 02:17.040 So with that, let's kick it of with General O'Shaughnessy, 02:17.040 --> 02:18.390 General Brown, General Harrigian. 02:18.390 --> 02:20.290 Thanks so much for being here, checks. 02:25.300 --> 02:26.460 - So, first check the technology. 02:26.460 --> 02:27.830 Okay, we're good. 02:27.830 --> 02:29.790 So let me just start by talking about it 02:29.790 --> 02:31.340 from the Homeland Defense perspective 02:31.340 --> 02:33.580 as the Commander of NORTHCOM and NORAD, 02:33.580 --> 02:37.060 we're focused like a laser on defending our great nations. 02:37.060 --> 02:39.067 And I'll start there talking about it 02:39.067 --> 02:42.190 from the aspect that it's no longer a sanctuary. 02:42.190 --> 02:44.340 And many of us grew up in our entire careers 02:44.340 --> 02:47.060 without worrying too much about what happens at home 02:47.060 --> 02:48.630 as we've brought the fight 02:48.630 --> 02:52.220 all over the world very successfully. 02:52.220 --> 02:53.840 But now as we look at our adversaries, 02:53.840 --> 02:56.500 we look at their peer adversaries that have the ability 02:56.500 --> 02:59.540 to bring the fight back to us at home, 02:59.540 --> 03:01.460 it becomes more and more important that we're thinking 03:01.460 --> 03:04.390 about war fighting at home as much as we're thinking 03:04.390 --> 03:06.950 about it all across the globe. 03:06.950 --> 03:09.450 And so from our perspective, as the NDS tells us, 03:09.450 --> 03:12.030 we need to make sure that we understand 03:12.030 --> 03:15.590 and we take a clear-eyed assessment of our adversaries 03:15.590 --> 03:18.720 and we look at our ability to defend ourselves at home. 03:18.720 --> 03:20.540 A key part of that is the integration 03:20.540 --> 03:23.370 across the globe and under Chairman Dunford 03:23.370 --> 03:25.170 and now Chairman Milley, we've been doing a series 03:25.170 --> 03:28.810 of exercises called the Globally Integrated Exercises, 03:28.810 --> 03:31.400 where we no longer just do an exercise, say, 03:31.400 --> 03:34.350 in C.Q.'s domain up in the Pacific 03:34.350 --> 03:37.790 or Cobra's domain over in EUCOM in Europe, 03:37.790 --> 03:40.870 but we actually look at it from the global aspect. 03:40.870 --> 03:42.980 And one of the things we're finding as we do that 03:42.980 --> 03:46.300 is regional fights are no longer regional. 03:46.300 --> 03:50.000 There's an aspect of a fight in Europe 03:50.000 --> 03:52.680 that will very much impact us at home. 03:52.680 --> 03:55.170 There's an aspect of a fight in Asia Pacific 03:55.170 --> 03:57.820 that will very much impact us at home. 03:57.820 --> 04:01.190 And so that integration between what we're doing away 04:01.190 --> 04:04.510 and what we're doing at home becomes even more critical. 04:04.510 --> 04:06.150 And so we look at how do we do that 04:06.150 --> 04:08.500 and how do we bring it all together from us in the homeland 04:08.500 --> 04:10.320 and focus on the homeland. 04:10.320 --> 04:14.060 We're starting by looking at what is it that the threats are 04:14.060 --> 04:16.130 and what is it specifically we need to do about them 04:16.130 --> 04:17.340 and what we find is these threats 04:17.340 --> 04:18.750 are not single-domain threats 04:18.750 --> 04:20.560 like we might've had in the past. 04:20.560 --> 04:22.620 These are multi-domain threats. 04:22.620 --> 04:23.890 And we have, just as we heard 04:23.890 --> 04:25.440 from DT Thompson earlier today, 04:25.440 --> 04:27.440 we have threats that start in space 04:27.440 --> 04:29.690 and they go all the way down to the undersea 04:29.690 --> 04:31.370 and everything in between. 04:31.370 --> 04:32.280 And so we have to be able 04:32.280 --> 04:33.890 to bring our war fighting capability 04:33.890 --> 04:36.030 across all of those domains together, 04:36.030 --> 04:39.180 even at home as we posture ourselves to defend the homeland. 04:39.180 --> 04:41.570 And so we're looking at developing a capability 04:41.570 --> 04:43.042 that has all-domain awareness. 04:43.042 --> 04:45.000 Domain awareness from the undersea 04:45.000 --> 04:47.350 all the way through space to include cyber. 04:47.350 --> 04:49.326 We're looking at how does that all come together 04:49.326 --> 04:52.580 and that's JADC2 and we'll come back to that. 04:52.580 --> 04:54.410 And then we have to have defeat mechanisms 04:54.410 --> 04:56.160 that can defeat all the threats 04:56.160 --> 04:58.740 that we see in all those domains. 04:58.740 --> 05:00.700 So the key and core aspect 05:00.700 --> 05:03.420 of bringing it together is the JADC2. 05:03.420 --> 05:06.030 So NORTHCOM is partnered with the United States Air Force 05:06.030 --> 05:08.960 in a series of experiments. 05:08.960 --> 05:11.360 And starting with ABS is experiment number one that we did 05:11.360 --> 05:13.960 in December, and one coming up in April, 05:13.960 --> 05:16.360 we're trying to put the J in some of the work, 05:16.360 --> 05:18.163 the J being the Joint, and some of the work 05:18.163 --> 05:20.540 that the Air Force has been doing 05:20.540 --> 05:23.890 to bring and connect that joint force. 05:23.890 --> 05:25.640 And so what we've been doing is trying to see 05:25.640 --> 05:28.750 how is it that we can actually bring that force together, 05:28.750 --> 05:30.260 not in a de-conflicted way, 05:30.260 --> 05:33.075 but in a truly integrated fashion. 05:33.075 --> 05:35.980 In order to do so, you have to be able to not only fuse 05:35.980 --> 05:37.720 all the information, but then you have to be able 05:37.720 --> 05:39.540 to command and control it. 05:39.540 --> 05:41.750 And it's not just good enough anymore 05:41.750 --> 05:45.040 to just get the situational awareness of where we are today, 05:45.040 --> 05:47.650 you then have to take that information and turn it into data 05:47.650 --> 05:50.410 that you can actually use to predict the future. 05:50.410 --> 05:52.880 And you can have that predictive analysis that can help you 05:52.880 --> 05:53.970 with the courses of action 05:53.970 --> 05:56.630 that you might have going into the future. 05:56.630 --> 05:58.910 And so when we look at this multi-domain operations, 05:58.910 --> 06:02.540 we look at it from the homeland defense lands, we see JADC2 06:02.540 --> 06:05.580 as core to that, and that what we need to do 06:05.580 --> 06:07.696 is be able to connect that joint force 06:07.696 --> 06:09.364 and they're really excited about 06:09.364 --> 06:11.553 some of the work that the Air Force is doing or do that, 06:11.553 --> 06:13.410 and I'm really excited about the tracks that we're getting 06:13.410 --> 06:17.070 within the joint force to take JADC2 and bring it into 06:17.070 --> 06:19.260 the future, and I look forward to talking more about that. 06:19.260 --> 06:20.093 Thank you. 06:21.850 --> 06:23.030 - General Brown, thank you. 06:23.030 --> 06:25.190 - Good morning, it's a real pleasure to be here 06:25.190 --> 06:27.730 and I'll just share with you three things I think about 06:27.730 --> 06:30.200 or three truths as we look at JADC2 06:30.200 --> 06:32.321 in multi-domain operations. 06:32.321 --> 06:36.200 The first is that we often talk particularly in the Pacific 06:36.200 --> 06:38.370 about the first island chain and the threats 06:38.370 --> 06:39.577 inside of the first island chain 06:39.577 --> 06:41.380 and to build on what Shags just said is 06:41.380 --> 06:43.310 when you look at multi-domain operations, 06:43.310 --> 06:44.990 there are no safe havens. 06:44.990 --> 06:48.700 And we're all in some sort, form or fashion, 06:48.700 --> 06:49.930 inside the first island chain, 06:49.930 --> 06:52.330 depending on the man you talk about. 06:52.330 --> 06:56.100 I also think about the aspect of, we cannot buy ourselves 06:56.100 --> 07:00.700 out of the threat where we're completely risk free. 07:00.700 --> 07:02.190 And so you've got to think about all the domains, 07:02.190 --> 07:06.570 whether it's air, land, maritime, space, cyber, 07:06.570 --> 07:08.200 but also the supporting capabilities. 07:08.200 --> 07:11.140 I think a lot about logistics based on the size of the AOR 07:11.140 --> 07:13.840 I think about information and how we push information 07:13.840 --> 07:16.823 and how that all kinda lines into JADC2. 07:18.160 --> 07:20.210 But I also believe we have an asymmetric advantage 07:20.210 --> 07:22.540 and that advantage really lies in our allies and partners 07:22.540 --> 07:25.110 'cause our adversaries do not have the allies and partners 07:25.110 --> 07:28.330 that we have and how we operate with them is important 07:28.330 --> 07:30.470 in how we share information. 07:30.470 --> 07:33.180 And so, all that being said, we're really re-thinking 07:33.180 --> 07:35.430 a few areas where we can't continue to do things 07:35.430 --> 07:37.200 the way we've always done them. 07:37.200 --> 07:39.620 One of the areas that I'm really thinking about is logistics 07:39.620 --> 07:42.490 I had to assist in Guam here, about 10 days ago, 07:42.490 --> 07:45.217 looking at some of our war reserve material 07:45.217 --> 07:49.050 and having talked to Arnie Bunch earlier this week, 07:49.050 --> 07:50.900 I'm re-thinking about how we do that. 07:51.990 --> 07:53.753 Right now I think we look at our WRM, 07:53.753 --> 07:55.882 it's like going to Costco. 07:55.882 --> 07:59.725 It's all in bulk, it sits in a certain location. 07:59.725 --> 08:02.630 I think we need to have smaller tailored packages 08:02.630 --> 08:05.750 that we can move around the region, ready to go 08:05.750 --> 08:08.450 and integrated into a form and fashion. 08:08.450 --> 08:10.710 And also being able to push logistics. 08:10.710 --> 08:14.320 I think about Amazon Prime, where you sign up 08:14.320 --> 08:17.510 for a subscription, it keeps delivering stuff to you 08:17.510 --> 08:18.820 because it knows you're gonna use it, 08:18.820 --> 08:21.830 you can adjust that subscription, you can cancel at any time 08:21.830 --> 08:24.380 if need be, but you adjust that subscription 08:24.380 --> 08:25.430 based on the environment. 08:25.430 --> 08:28.490 With all the data we have and using AI, I think there's ways 08:28.490 --> 08:30.470 for us to be able to do that. 08:30.470 --> 08:31.950 And so that's an approach for we're thinking about 08:31.950 --> 08:33.303 as we move forward. 08:34.169 --> 08:37.050 I'm also thinking about how we do Command and Control. 08:37.050 --> 08:41.770 And what I've talked in various forums with our staff is, 08:41.770 --> 08:44.730 with JADC2 the goal is to connect 08:44.730 --> 08:47.170 every sensor to every shooter. 08:47.170 --> 08:49.780 Okay, that's a great goal, but right now I wanna make sure 08:49.780 --> 08:52.550 we can connect the right sensors to the right shooter 08:52.550 --> 08:55.450 as we're getting on the path to connecting all. 08:55.450 --> 08:58.400 Because we've gotta be able to fight today, next week, 08:58.400 --> 09:00.810 next month, next year, next decade. 09:00.810 --> 09:02.460 And it's gonna take us a while to get to every sensor, 09:02.460 --> 09:03.600 every shooter, but we've got to get 09:03.600 --> 09:05.453 the right ones started now. 09:06.570 --> 09:08.700 The other aspect of that is I know our communications 09:08.700 --> 09:12.040 will be contested and I think, and I told my staff 09:12.040 --> 09:15.590 is our primary plan ought to be that we're disconnected. 09:15.590 --> 09:16.660 And that our communications 09:16.660 --> 09:19.050 are gonna be vulnerable to attack. 09:19.050 --> 09:20.450 Our contingency plan will be 09:20.450 --> 09:22.630 that we're all completely connected. 09:22.630 --> 09:25.690 And if we're completely connected, we ought to be surprised 09:25.690 --> 09:28.360 and you've gotta be suspect that we're being spoofed. 09:28.360 --> 09:29.573 And we've gotta think about it from that aspect 09:29.573 --> 09:32.370 if we will not be fully connected and how we look 09:32.370 --> 09:35.820 at advance METL management system in the various clouds, 09:35.820 --> 09:38.210 I look at the big cloud that we have data that's coming out 09:38.210 --> 09:40.390 of the ERA operations center and the cloud 09:40.390 --> 09:43.170 at the forward edge where we're pushing information. 09:43.170 --> 09:45.440 And with enough information far enough in advance 09:45.440 --> 09:48.496 that our folks, our airmen, our drawing team, 09:48.496 --> 09:50.596 with our partners will be able to operate. 09:51.600 --> 09:53.530 And so that part of the concept we're working through 09:53.530 --> 09:56.920 we just exercise it in one of our exercises 09:56.920 --> 09:59.150 with INDOPACOM is how do we do 09:59.150 --> 10:01.373 a multi-day air-tasking order? 10:02.320 --> 10:04.830 It's not so much that we do a multi-day air-task course, 10:04.830 --> 10:06.730 it's a thought process that would've required us 10:06.730 --> 10:10.050 to pull information together so you can lay out information 10:10.050 --> 10:13.190 and execution orders several days in advance 10:13.190 --> 10:16.050 in case someone is disconnected at the forward edge, 10:16.050 --> 10:17.874 they have enough information to continue to operate 10:17.874 --> 10:20.260 not waiting for guidance from me, 10:20.260 --> 10:22.200 or from our air operations center. 10:22.200 --> 10:23.720 And so it's a different thought process, 10:23.720 --> 10:27.260 that we've gotta think of longer, further in advance 10:27.260 --> 10:30.060 and that's incumbent on me and leaders like myself 10:30.060 --> 10:32.837 to think about commanders intent and how we operate 10:32.837 --> 10:36.420 and how we position capability around the region. 10:36.420 --> 10:38.180 The last is agile combat employment 10:38.180 --> 10:40.270 and I really do appreciate the work that they, 10:40.270 --> 10:42.450 all the match coms are doing as we work 10:42.450 --> 10:45.350 at agile combat employment and how we'll get lighter, 10:45.350 --> 10:47.904 leaner as we move forward. 10:47.904 --> 10:51.270 I say right now, we are, as an air force, 10:51.270 --> 10:54.365 we're going glamping, we either forgot to go camping, 10:54.365 --> 10:57.770 how to get really light and lean and move forward 10:57.770 --> 10:59.460 and trust our airmen and empower them 10:59.460 --> 11:02.370 to actually go do things that they're trained to do 11:02.370 --> 11:05.160 without the, a lot of oversight and asking for permission 11:05.160 --> 11:06.740 from a higher level. 11:06.740 --> 11:08.310 It's a different thought process and I think 11:08.310 --> 11:10.920 we were on the right path and I appreciate the support 11:10.920 --> 11:12.680 that everybody's bringing along. 11:12.680 --> 11:13.950 Thanks. 11:13.950 --> 11:15.030 - Thank you Sir. 11:15.030 --> 11:16.670 - Okay, thanks, we're rolling again, 11:16.670 --> 11:21.440 thanks for an opportunity to talk about joint all-domain ops 11:21.440 --> 11:23.540 and where we're going with that, particularly as it relates 11:23.540 --> 11:25.373 to USAFE in Africa. 11:26.710 --> 11:30.050 Three upfront points from my perspective. 11:30.050 --> 11:34.630 Number one, I'd offer we need to continue to work 11:34.630 --> 11:37.030 on our understanding of the problem statement 11:37.030 --> 11:41.140 and what we're trying to solve as we go forward on this. 11:41.140 --> 11:44.050 Number two, I know teams have been working this, 11:44.050 --> 11:46.130 but as we look at the road map, 11:46.130 --> 11:48.730 we've gotta develop a road map that's executable 11:48.730 --> 11:52.680 in terms of delivering capabilities to the war fighters, 11:52.680 --> 11:55.900 in particular the joint soldiers, sailors, airmen, marines 11:55.900 --> 11:58.680 that're out there that're going to have to execute this. 11:58.680 --> 12:03.180 And then three, I would offer, we gotta find the right mix 12:03.180 --> 12:06.240 between the top down innovation 12:06.240 --> 12:07.880 and the bottom up innovation. 12:07.880 --> 12:11.470 And how we mix those together, to get the appropriate 12:11.470 --> 12:13.550 buy-in moving forward here. 12:13.550 --> 12:15.030 So if I go back to the first one 12:15.030 --> 12:15.900 of understanding the problem, 12:15.900 --> 12:17.560 I thought General O'Shaughnessy hit it well 12:17.560 --> 12:19.330 in terms of the threats. 12:19.330 --> 12:22.370 I think we all recognize we have some commonalities 12:22.370 --> 12:25.160 as we look across the globe that drive us to 12:26.100 --> 12:28.410 look for capabilities that would help us compete 12:28.410 --> 12:29.650 in that environment. 12:29.650 --> 12:33.950 There's others, as you look across Europe, Africa, 12:33.950 --> 12:37.030 you get into INDOPACOM, they're back in the homeland, 12:37.030 --> 12:39.210 that will drive specific capabilities 12:39.210 --> 12:40.820 that we're gonna need to have moving forward, 12:40.820 --> 12:45.350 particularly from not just a capability off a weapon system 12:45.350 --> 12:47.350 but from a C2 perspective. 12:47.350 --> 12:49.150 You know, as I look at Africa, 12:49.150 --> 12:52.680 that problem is a clearly challenging environment 12:52.680 --> 12:55.540 for us to make sure that we've got the sensors to connect 12:55.540 --> 13:00.100 to the right nodes as we look across that environment. 13:00.100 --> 13:03.780 Importantly as we look at that operating environment, 13:03.780 --> 13:06.310 I think General Brown hit it well. 13:06.310 --> 13:07.890 We gotta work with NATO. 13:07.890 --> 13:11.460 We gotta figure out how they will be a key contributor 13:11.460 --> 13:15.450 to this broader idea that we're talking about right now 13:15.450 --> 13:16.980 and how we incorporate partners, 13:16.980 --> 13:20.340 recognizing that we're gonna have technical challenges, 13:20.340 --> 13:23.350 we're gonna have policy challenges, information sharing 13:23.350 --> 13:27.090 though, will be key to our success if we're gonna make this 13:27.090 --> 13:29.660 a valid concept moving forward. 13:29.660 --> 13:32.560 I think importantly embedded in that problem 13:32.560 --> 13:35.220 is fundamentally acknowledging 13:35.220 --> 13:38.630 that we're gonna have to take on a culture change 13:38.630 --> 13:40.030 in how we approach this. 13:40.030 --> 13:42.960 Having said that, I think everybody sitting out here 13:42.960 --> 13:46.640 has been involved in an all-domain operation. 13:46.640 --> 13:48.980 I mean, we do that to a certain extent. 13:48.980 --> 13:50.580 Do we do it at the speed and pace 13:50.580 --> 13:51.950 that we would like, right now? 13:51.950 --> 13:53.210 No. 13:53.210 --> 13:55.590 But this ought not be looked at as something 13:55.590 --> 13:59.110 as we're completely breaking open a whole new idea here 13:59.110 --> 14:02.200 that's gonna be different to the things that our airmen 14:02.200 --> 14:03.750 are doing in the field right now. 14:03.750 --> 14:05.980 We will be able to do it, with better capabilities 14:05.980 --> 14:09.010 and at better speed, but we also need to recognize 14:09.010 --> 14:12.380 that mentality is resident in our force right now. 14:12.380 --> 14:14.160 Second, as I high-lighted there as we talk 14:14.160 --> 14:17.440 about an executable road map, what I've seen, 14:17.440 --> 14:18.850 and General O'Shaughnessy, your team 14:18.850 --> 14:21.170 has been leading on this with the experiments, 14:21.170 --> 14:24.840 incredibly important in that it demonstrates 14:24.840 --> 14:26.040 the capabilities that're out there, 14:26.040 --> 14:28.460 but what I want to challenge all of us is, 14:28.460 --> 14:30.500 we've got to leave behind capabilities 14:30.500 --> 14:32.850 that we put in the hands of our airmen. 14:32.850 --> 14:35.870 We've got to get the buy-in at that level, 14:35.870 --> 14:36.757 that this is where we're going, 14:36.757 --> 14:38.840 and this is how we're gonna do it. 14:38.840 --> 14:41.920 And we can't expect this to happen in a big bang, 14:41.920 --> 14:43.920 and I think everybody acknowledges that, 14:43.920 --> 14:47.280 but providing those capabilities in incremental fashion 14:47.280 --> 14:50.130 that gets buy-in across the joint force with our partners 14:50.130 --> 14:52.800 will be important to how we move forward on this. 14:52.800 --> 14:54.870 And those quick wins and those capabilities 14:54.870 --> 14:56.140 that we can get to them, 14:56.140 --> 15:00.020 and I would offer in the developmental ops way of thinking, 15:00.020 --> 15:03.060 is really where we need to go as we implement this. 15:03.060 --> 15:07.110 And then, finally, and General Brown and I brought this up 15:07.110 --> 15:09.360 back at our Command and Control summit, 15:09.360 --> 15:12.470 it really is getting the right integration and discussion 15:12.470 --> 15:16.200 between, I'll use the term that the theater war fighters 15:16.200 --> 15:19.010 and those that are generating these innovative ideas 15:19.010 --> 15:20.650 that are coming from the top down, 15:20.650 --> 15:22.580 we've gotta latch that up. 15:22.580 --> 15:25.920 If we do that, that will drive great synergy 15:25.920 --> 15:30.210 and bring great capabilities at speed to our war fighters. 15:30.210 --> 15:32.300 So I think those three things are things we can think about 15:32.300 --> 15:34.650 as we go forward here, look forward to any questions. 15:34.650 --> 15:35.483 Thank you. 15:35.483 --> 15:38.393 - Thanks, so we'll start with the questions, great start. 15:39.640 --> 15:43.930 For the three of you, and for your industry partners, 15:43.930 --> 15:46.890 you're up close and personal everyday with the threats 15:46.890 --> 15:49.630 specific to your AORs. 15:49.630 --> 15:51.250 Certainly, for General Harrigian 15:51.250 --> 15:53.450 in support of General Walters, the Russians. 15:54.600 --> 15:58.620 For General Brown, it's the Chinese and the North Koreans. 15:58.620 --> 16:02.210 And certainly, for General O'Shaugnessy, it's the Chinese 16:02.210 --> 16:04.793 and the Russians from New York to Omaha to L.A. 16:05.880 --> 16:09.820 So, again, for your industry partners, could you just offer 16:09.820 --> 16:11.930 a few words starting with General O'Shaughnessy 16:11.930 --> 16:14.863 on how you see the reality of the threat. 16:16.410 --> 16:17.560 - Well, thanks for the question 16:17.560 --> 16:21.280 and I do wanna be very clear here, the threats that we face 16:21.280 --> 16:24.380 in the homeland are real, and they're advanced. 16:24.380 --> 16:26.270 And so we need to work with our industry partners 16:26.270 --> 16:27.720 but we need to do it in different ways 16:27.720 --> 16:29.980 and so what we've done at NORTHCOM and NORAD 16:29.980 --> 16:32.480 is, instead of going out and saying we need a widget, 16:32.480 --> 16:35.000 a widget that does this, this and this, 16:35.000 --> 16:37.810 we're being much more strategic in our dialogue 16:37.810 --> 16:39.730 with industry and what we're doing, 16:39.730 --> 16:41.630 is we're bringing them the challenges and we're saying, 16:41.630 --> 16:43.970 we face challenges all the way from the undersea activity 16:43.970 --> 16:46.770 that we see from the maritime threats, from the air-domain 16:46.770 --> 16:49.750 threats that we see, all the way to space and cyber, 16:49.750 --> 16:52.000 and we bring that into an overall ecosystem 16:52.000 --> 16:54.700 of what we're trying to do to defend our great nation. 16:54.700 --> 16:57.380 But as we do so, we're trying to be very open 16:57.380 --> 17:00.200 in that we have an over-arching architecture 17:00.200 --> 17:02.110 of which we're trying to plug into 17:02.110 --> 17:05.870 but we wanna just give our challenges to industry 17:05.870 --> 17:08.010 both the defense industry and commercial industry 17:08.010 --> 17:10.300 because there's advantages to both of those. 17:10.300 --> 17:13.670 But we do so in a way that allows them to look to see 17:13.670 --> 17:17.170 how do they fit into solving some of these challenges. 17:17.170 --> 17:19.940 So instead of asking for a specific capability, 17:19.940 --> 17:22.820 we gave them insight into the challenges that we face 17:22.820 --> 17:26.350 and we give them insight in the broad level understanding 17:26.350 --> 17:29.070 of how we're gonna solve that and we've already been amazed 17:29.070 --> 17:31.750 by what they've come back with by doing it that way 17:31.750 --> 17:34.930 to see that we can open up, maybe the opportunity 17:34.930 --> 17:38.120 to see what is it that individual companies can bring. 17:38.120 --> 17:42.380 They tend to come back with a much more advanced, 17:42.380 --> 17:46.890 a much more thought-out ability to bring capability 17:46.890 --> 17:49.010 that will ultimately tie in both in the near term 17:49.010 --> 17:51.170 and the long term as was highlighted 17:51.170 --> 17:52.730 by both my partners here, 17:52.730 --> 17:55.330 is that there's a time piece of this 17:55.330 --> 17:57.380 and so we can't just be determining things 17:57.380 --> 17:58.810 that are gonna be great in 10 years, 17:58.810 --> 18:01.190 we gotta start bringing in that capability soon. 18:01.190 --> 18:03.210 And so by having that dialogue with industry, 18:03.210 --> 18:06.100 we're finding we're able to bring things left in time, 18:06.100 --> 18:08.110 bring capability to bear soon, 18:08.110 --> 18:09.840 and then bring more advanced capability 18:09.840 --> 18:12.880 that will help solve some of our toughest challenges. 18:12.880 --> 18:13.713 Thanks. 18:13.713 --> 18:16.750 - General Brown, the threat in your INDOPACOM theater. 18:16.750 --> 18:18.050 - Well, I think the thing that I look at 18:18.050 --> 18:21.710 for the threat we face, particularly less so from DPRK 18:21.710 --> 18:23.710 but more so from China is the fact 18:23.710 --> 18:26.310 that there's a lot of activity that goes on 18:26.310 --> 18:29.910 kinda below the radar that doesn't naturally make the press. 18:29.910 --> 18:32.080 And so we're at a competition all the time. 18:32.080 --> 18:35.980 And part of that is we can't wait eight to 10 years 18:35.980 --> 18:38.750 for something to leverage as like Shags has described. 18:38.750 --> 18:42.135 But it's how do we actually get the ball moving faster. 18:42.135 --> 18:45.210 The one area that I think we're, when I work with industry 18:45.210 --> 18:46.720 and talk, is the fact that 18:46.720 --> 18:49.130 verses not wanting any specific requirements, 18:49.130 --> 18:52.000 we're kinda talking about the concept and the vision 18:52.000 --> 18:55.240 and let industry see themselves in that concept and vision. 18:55.240 --> 18:57.997 And then, the way I think about it, they'll come back to me 18:57.997 --> 18:59.847 and go, "We have an app for that. 18:59.847 --> 19:02.497 "We have an approach that can actually solve the challenge 19:02.497 --> 19:04.652 "you're up against." verses me providing 19:04.652 --> 19:06.400 this very specific requirement, 19:06.400 --> 19:09.910 I get a very specific answer back that may've, 19:09.910 --> 19:12.300 by the time that it delivers, may not meet our requirements 19:12.300 --> 19:15.250 because the facts and assumptions all change. 19:15.250 --> 19:17.731 And so, I think there's good dialogue going forward 19:17.731 --> 19:20.540 as Shags described, we're, I think, collectively, 19:20.540 --> 19:24.150 all moving faster, but we still gotta pick up the pace. 19:24.150 --> 19:25.200 - [Orville Wright] Terrific. 19:25.200 --> 19:29.010 - And that's great, and clearly we are very much along, 19:29.010 --> 19:32.510 in that General Walters level is well with respect to you, 19:32.510 --> 19:35.573 here's the broader problems as we see them. 19:36.430 --> 19:39.720 I think industry and we'll hear more about this 19:39.720 --> 19:42.500 over the next couple of days is collectively understanding 19:42.500 --> 19:45.650 the vision but then to General Browns' points, 19:45.650 --> 19:49.201 sorting out how they can tailor to our needs based on 19:49.201 --> 19:52.090 our environments and that's where I, 19:52.090 --> 19:54.100 I think it's critically important and we've been trying 19:54.100 --> 19:55.810 to work this with support from General Walters 19:55.810 --> 19:59.030 to bring them to the AOR so that they can actually see it 19:59.030 --> 20:02.440 and understand it, so that then we can work together 20:02.440 --> 20:06.300 to kinda developmentally bring these capabilities 20:06.300 --> 20:09.400 that they offer to help solve the problems. 20:09.400 --> 20:12.100 I guess the other one that I just feel is important 20:12.100 --> 20:13.530 to bring up, particularly where I live, is, 20:13.530 --> 20:16.543 while we are clearly zeroed in on Russia, 20:17.490 --> 20:19.920 the threats we face in Africa, 20:19.920 --> 20:21.950 particularly from a competition perspective, 20:21.950 --> 20:24.450 both against the Chinese and Russian 20:24.450 --> 20:26.690 cannot be lost in this discussion. 20:26.690 --> 20:28.600 And so while we're looking to compete with them 20:28.600 --> 20:30.300 in a myriad of different manners, we're also, 20:30.300 --> 20:34.340 at the same time, focused on force-protecting as we recall 20:34.340 --> 20:38.480 back in January we lost three Americans at Manda Bay 20:38.480 --> 20:40.760 and those capabilities that we're talking about here, 20:40.760 --> 20:42.320 I would offer, will help us 20:42.320 --> 20:44.570 in that challenging environment as well. 20:44.570 --> 20:45.500 - Great. 20:45.500 --> 20:47.240 Thanks, well, lots of great questions 20:47.240 --> 20:49.770 coming from the audience, the system's working. 20:49.770 --> 20:53.990 Most of the questions come from someone called Anonymous. 20:53.990 --> 20:58.240 However, I have a question from Colonel Melissa Stone. 20:58.240 --> 21:02.300 And, she was good enough to identify herself, 21:02.300 --> 21:06.013 and from Colonel Stone, "Sirs, we've heard about work," 21:06.013 --> 21:08.487 this is a neat question, "We've heard about work in tech 21:08.487 --> 21:10.577 "and systems needed for MDO, 21:10.577 --> 21:13.187 "from a cognitive domain perspective, 21:13.187 --> 21:14.237 "what should we be doing 21:14.237 --> 21:16.797 "to prepare our human weapon systems?" 21:19.030 --> 21:20.320 - Well, we're looking for good people 21:20.320 --> 21:21.997 at NORTHCOM and NORAD so-- 21:23.290 --> 21:24.570 - [Gen. Harrigian] Germany as well. 21:24.570 --> 21:25.403 (laughs) 21:25.403 --> 21:27.573 - So I'm gonna have to find Melissa Stone. 21:28.710 --> 21:30.970 A couple things I mentioned, first off, 21:30.970 --> 21:33.053 I think we have to think about who it is 21:33.053 --> 21:35.170 that we're bringing on to the teams. 21:35.170 --> 21:39.240 I'll use a quick example, at NORTHCOM and NORAD is, 21:39.240 --> 21:41.907 as we were trying to go down this path of, how do we get 21:41.907 --> 21:44.100 to JADC2, how do we get to the technology 21:44.100 --> 21:45.110 that's available out there, 21:45.110 --> 21:47.810 and how do apply it in different ways, 21:47.810 --> 21:49.604 we're trying to transform, 21:49.604 --> 21:53.400 getting kind of a digital transformation within our command. 21:53.400 --> 21:57.580 And as we did that, we found we, when I looked at the folks 21:57.580 --> 22:01.520 that we are hiring, the average age of the individuals 22:01.520 --> 22:04.730 that we are hiring was 49 years old. 22:04.730 --> 22:08.730 So, if I bring in the average 49 year old person in, 22:08.730 --> 22:10.870 they're gonna think a lot like I think. 22:10.870 --> 22:12.380 Right, they're gonna think a lot like folks 22:12.380 --> 22:13.557 that have been around for a long time 22:13.557 --> 22:15.500 and have great experience perhaps, but nonetheless, 22:15.500 --> 22:17.920 they're not necessarily the different generation 22:17.920 --> 22:20.320 that might be able to bring some innovative thoughts, 22:20.320 --> 22:22.010 some different way of looking at our problems, 22:22.010 --> 22:24.018 so I think part of this cognitive aspect is, 22:24.018 --> 22:26.561 we have to embrace what we have as society 22:26.561 --> 22:29.010 and we have to be able to bring in different people 22:29.010 --> 22:31.730 into our organizations. 22:31.730 --> 22:34.710 And so part of that is we look at our digital transformation 22:34.710 --> 22:37.330 within the NORTHCOM piece, it really showed us 22:37.330 --> 22:40.660 that from an aspect we have to hire different people, 22:40.660 --> 22:42.560 and then we have to train folks, 22:42.560 --> 22:45.470 and the example I use is, even with myself, 22:45.470 --> 22:49.580 where you have to, in this dynamic that we live in today, 22:49.580 --> 22:50.900 it doesn't matter whether you're commercial world 22:50.900 --> 22:52.990 or you're in the Department of Defense, 22:52.990 --> 22:55.040 you have to continually learn. 22:55.040 --> 22:58.420 And so I'm literally on Amazon web services taking courses 22:58.420 --> 23:01.200 on AWS so that I can keep pace 23:01.200 --> 23:03.000 with all of the changing dynamic 23:03.000 --> 23:05.970 that we have and things that are available to us. 23:05.970 --> 23:08.630 And so we need to be able to bring that to our entire force 23:08.630 --> 23:12.690 and encourage and enable that continuous learning 23:12.690 --> 23:14.910 that our force needs to have and then we need 23:14.910 --> 23:18.240 to be able to bring in folks that have different experiences 23:18.240 --> 23:19.480 than what you might have 23:19.480 --> 23:22.370 from a traditional military background. 23:22.370 --> 23:23.700 - Terrific. 23:23.700 --> 23:25.700 And another not anonymous question 23:25.700 --> 23:26.951 of the many anonymous questions 23:26.951 --> 23:29.260 and I probably won't pronounce this name right, 23:29.260 --> 23:31.633 but Master Sergeant Kuykendall, 23:34.329 --> 23:35.162 this is a good one I think 23:35.162 --> 23:37.770 for General Harrigian given the operations 23:37.770 --> 23:39.187 in Iraq and Africa. 23:39.187 --> 23:41.617 "What does multi-domain operations look like 23:41.617 --> 23:44.327 "at the tactical unit level? 23:44.327 --> 23:45.647 "While the air force developed 23:45.647 --> 23:49.437 "career specific tactics techniques and procedures, 23:49.437 --> 23:51.167 "to integrate into the joint war effort 23:51.167 --> 23:52.687 "again at the tactical level." 23:53.720 --> 23:55.998 - So I believe we'll get there over time. 23:55.998 --> 24:00.550 At the end of the day, how we integrate these capabilities 24:00.550 --> 24:02.270 because, as General O'Shaughnessy said, 24:02.270 --> 24:04.290 there's a cognitive piece to this. 24:04.290 --> 24:07.730 I think we have raised ourselves, 24:07.730 --> 24:09.900 particularly with the wars we've fought 24:09.900 --> 24:11.610 for the last 20 years to 24:13.360 --> 24:17.290 expect a lot of air force to air force 24:17.290 --> 24:21.740 inside of our ways of doing business, 24:21.740 --> 24:24.740 whereas we move forward at that tactical level, 24:24.740 --> 24:27.000 we've gotta move to the point where you don't care 24:27.000 --> 24:28.083 where it comes from. 24:28.920 --> 24:31.010 You're comfortable with that, and you trust it 24:31.010 --> 24:33.070 and then you execute your part, 24:33.070 --> 24:35.130 if I can call it, of the kill chain, 24:35.130 --> 24:37.643 to ensure we're achieving the effects 24:37.643 --> 24:39.422 that are desired there. 24:39.422 --> 24:43.230 And I think, as we work through the experiments 24:43.230 --> 24:46.140 and our understanding of how this concept 24:46.140 --> 24:50.000 actually turns into operations, it'll give us opportunities 24:50.000 --> 24:53.350 to build the trust and confidence in this system 24:53.350 --> 24:56.477 that will drive, potentially some different TTPs 24:56.477 --> 25:00.600 and how you accept that information, 'cause the key will be 25:00.600 --> 25:03.257 to all of us to have that, 25:03.257 --> 25:05.160 and all I think is a bit of an overstatement, 25:05.160 --> 25:08.030 but the right people have the right understanding 25:08.030 --> 25:11.810 to be able to then execute at speed, which will be required 25:11.810 --> 25:13.050 for this enemy. 25:13.050 --> 25:14.640 - Yes, sir. 25:14.640 --> 25:17.780 And for General Brown, you're in a very joint theater. 25:17.780 --> 25:22.780 Certainly, Navy Combatant Commander, a big area, 25:23.160 --> 25:24.053 as you call it, 25:24.970 --> 25:27.730 so, how bought in do you think, 25:27.730 --> 25:30.250 or collaboratively, bar the other services 25:30.250 --> 25:31.800 in your joint theater, 25:31.800 --> 25:35.720 in sort of fulfilling the expectations 25:35.720 --> 25:36.800 of the operational objectives 25:36.800 --> 25:38.620 as joint all-domain command and control 25:38.620 --> 25:40.610 as you work with the other services? 25:40.610 --> 25:42.763 - Yeah, I think they're fairly plugged in. 25:43.830 --> 25:47.260 But we also all understand the problem as well. 25:47.260 --> 25:49.460 And when I look at that is the fact that all of us 25:49.460 --> 25:54.050 have long range weapons capability and if everybody's, 25:54.050 --> 25:57.698 you know, each one of us is either pulling a lanyard 25:57.698 --> 26:01.150 hitting a pickle button, activating a strike, 26:01.150 --> 26:02.570 it's how we pull all that together. 26:02.570 --> 26:05.683 And we understand the challenges associated with that. 26:05.683 --> 26:08.800 So, I think we've acknowledged that there is a problem, 26:08.800 --> 26:10.750 that we gotta actually solve. 26:10.750 --> 26:12.990 But how we come together as the various services 26:12.990 --> 26:14.800 and that's why I think it's a key part of us 26:14.800 --> 26:18.750 as we look at this, is, what are the right, right systems 26:18.750 --> 26:21.012 and sensors we gotta connect now 26:21.012 --> 26:24.287 between the different services, so we can all buy in 26:24.287 --> 26:25.700 and continue to move down the path 26:25.700 --> 26:28.780 for every sensor, every shooter. 26:28.780 --> 26:30.950 But I think we've all acknowledged it. 26:30.950 --> 26:34.860 Good dialogue between the components for various exercises. 26:34.860 --> 26:36.520 We also realize there's a lot of work to do, 26:36.520 --> 26:38.240 to get us where we need to be. 26:38.240 --> 26:39.870 - Again, for your industry partners, 26:39.870 --> 26:41.840 do you see more and more of a role 26:41.840 --> 26:44.567 for industry actual participation 26:44.567 --> 26:45.850 and increased level of knowledge 26:45.850 --> 26:48.050 associated with your exercises? 26:48.050 --> 26:49.150 - I do. 26:49.150 --> 26:51.050 And part of that is actually some of the things we're doing 26:51.050 --> 26:54.970 with some of the experimentation is for them to be there 26:54.970 --> 26:58.200 to actually observe, to watch us in action, 26:58.200 --> 26:59.510 'cause the more they're able to watch us 26:59.510 --> 27:02.080 be able to do things, they'll be able to understand 27:02.080 --> 27:04.780 how they may be able to design something 27:04.780 --> 27:06.830 or put something in place that actually will help us 27:06.830 --> 27:08.090 do what we need to do. 27:08.090 --> 27:08.923 - Great. 27:08.923 --> 27:10.210 - If I can peek back to that for just a minute, 27:10.210 --> 27:12.960 both something that both General Brown and General Harrigian 27:12.960 --> 27:16.140 mentioned and that is the participation of the exercise 27:16.140 --> 27:17.930 but also the DevOps mindset. 27:17.930 --> 27:21.840 I think we have to embrace that, and it's fairly routine 27:21.840 --> 27:23.920 in a commercial world, but as we see that, 27:23.920 --> 27:28.920 we see the advancement of their ability to meet our needs, 27:28.970 --> 27:31.610 exponentially, if we allow them to do that, 27:31.610 --> 27:36.070 we provide them the opportunity to enter in an environment 27:36.070 --> 27:38.520 that is relevant, bring in their team, 27:38.520 --> 27:40.880 what they can accomplish in literally days, 27:40.880 --> 27:44.100 might would have taken six months or a year to accomplish 27:44.100 --> 27:45.830 with that DevOps mindset. 27:45.830 --> 27:47.140 - Terrific. 27:47.140 --> 27:49.390 This question from the four 12th S. Wings, 27:49.390 --> 27:50.950 so thanks for being here and joining us 27:50.950 --> 27:52.663 at your Air Warfare Symposium. 27:53.700 --> 27:56.250 This is probably good for anyone who wants to volunteer, 27:56.250 --> 27:57.767 but, "What do you see the biggest hurdle 27:57.767 --> 28:00.487 "to executing real time joint all-domain command and control 28:00.487 --> 28:02.427 "in a Five Eyes environment?" 28:04.220 --> 28:05.270 - Our policies. 28:05.270 --> 28:06.640 (laughs) 28:06.640 --> 28:08.290 Our ability to share. 28:08.290 --> 28:10.600 It's the culture of not so much policy, 28:10.600 --> 28:13.110 I think in some cases, and it's not just Five Eye. 28:13.110 --> 28:15.340 Because all of my partners that I work with 28:15.340 --> 28:18.070 are not just part of the Five Eye consortium, 28:18.070 --> 28:19.750 so we actually have to look how broadly 28:19.750 --> 28:22.270 we can actually share information with our partners, 28:22.270 --> 28:23.850 the partners that need to know, 28:23.850 --> 28:26.640 in order to be able to operate, so it's a little bit 28:26.640 --> 28:30.430 of a culture piece, and there's also a little bit of policy. 28:30.430 --> 28:34.180 We've gotta be able to move at the speed that's required 28:34.180 --> 28:37.000 with some of our policies, I had a need, 28:37.000 --> 28:40.106 so we're ready to go if a contingency or conflict 28:40.106 --> 28:41.463 starts to evolve. 28:43.040 --> 28:47.020 - Let me just add, since I've been vocal on this. 28:47.020 --> 28:50.170 I think there's a policy piece in this, 28:50.170 --> 28:52.647 the other part that we spent a lot of time talking about is, 28:52.647 --> 28:56.440 who actually buys the risk in this scenario? 28:56.440 --> 28:59.840 If you're protecting sources and methods 28:59.840 --> 29:02.890 and you just wanna get it to the right people, 29:02.890 --> 29:06.270 then we need to be thoughtful about who buys the risk, 29:06.270 --> 29:09.460 and who we delegate that authority to, to manage it, 29:09.460 --> 29:12.410 whether it be at the tactical level, the operational level. 29:13.970 --> 29:18.220 Unfortunately, it appears to me that it takes a war 29:18.220 --> 29:22.547 or a critical event to happen before we say, "Okay, 29:22.547 --> 29:23.920 "I guess we should have done that." 29:23.920 --> 29:27.470 And so, we know that now, we've talked about it 29:27.470 --> 29:30.280 time and time again, and now's the time to fix it 29:30.280 --> 29:33.830 in competition and work through that and allow commanders 29:33.830 --> 29:36.080 to be commanders and make smart risk decisions 29:36.080 --> 29:38.730 based on the environment they're operating in. 29:38.730 --> 29:39.563 - Yes sir. 29:40.830 --> 29:44.487 Again, back to General Brown, a very specific question, 29:44.487 --> 29:48.110 "When will PakAf start maximizing use of the surface 29:48.110 --> 29:50.850 and sea domain for storage and distribution, 29:50.850 --> 29:52.907 small vessels and not large vessels?" 29:55.230 --> 29:57.320 - Ah, that's a good question, I don't know, 29:57.320 --> 29:59.030 it's part of working the joint requirements 29:59.030 --> 30:00.250 associated with this. 30:00.250 --> 30:02.030 I mean, there's a lot of good discussion 30:02.030 --> 30:03.990 and I think there's a lot of things, 30:03.990 --> 30:06.380 we talk about innovation to be able to use the other domains 30:06.380 --> 30:09.720 about how you move and support logistics. 30:09.720 --> 30:12.040 One of the things we're talking about with INDOPACOM is, 30:12.040 --> 30:14.303 do we have a logistics component commander? 30:15.730 --> 30:17.200 Just based on the size of the region 30:17.200 --> 30:19.640 and all the things that you're gonna have to move, 30:19.640 --> 30:22.593 should someone be sitting in charge of complete logistics. 30:23.500 --> 30:26.180 And I think there's an aspect to that will help PakAf, 30:26.180 --> 30:28.480 Pak fleet and the other components, 30:28.480 --> 30:31.930 think through how we're gonna use the limited resources 30:31.930 --> 30:33.950 to move capability. 30:33.950 --> 30:36.740 But I also believe we need to pre-position capability 30:36.740 --> 30:40.020 so you're not waiting to try to execute TPFDD 30:40.020 --> 30:42.070 so we can move at the pace we gonna need to move forward 30:42.070 --> 30:44.287 so, I think there's plenty opportunities there 30:44.287 --> 30:46.780 and the other aspect, last thing I'd actually add that, 30:46.780 --> 30:49.700 for all of us, is, we're talking about joint domain, 30:49.700 --> 30:53.940 all JADC2, we also been thinking about how we solve problems 30:53.940 --> 30:57.560 jointly verses trying to just use air capabilities 30:57.560 --> 31:02.560 to support logistics, so that means leaning on maritime 31:03.240 --> 31:06.250 or armory watercraft for example or other opportunities 31:06.250 --> 31:08.370 that we need to start taking advantage of. 31:08.370 --> 31:09.500 - Great. 31:09.500 --> 31:12.010 Back to General O'Shaughnessy, 31:12.010 --> 31:16.959 as you look at the cyber threat to the homeland, 31:16.959 --> 31:20.969 are you collaborating closely with CyberCom day to day, 31:20.969 --> 31:24.360 obviously between NORTHCOM and Cybercom with a situational 31:24.360 --> 31:28.400 learn as you need to collaborate to defend the homeland 31:28.400 --> 31:31.975 against a range of cyber threats from all over the world? 31:31.975 --> 31:33.980 - Yeah, clearly there's significant threats to the homeland 31:33.980 --> 31:37.510 from in the cyber domain, and I would say currently 31:37.510 --> 31:39.350 we are partnering very closely 31:39.350 --> 31:42.630 and do on a literally daily basis with cyber command, 31:42.630 --> 31:44.560 but I will say it's bigger than that and as you look at it 31:44.560 --> 31:46.190 from our national critical infrastructure, 31:46.190 --> 31:49.100 not just our D-O-D critical infrastructure, 31:49.100 --> 31:50.010 we're also partnered with 31:50.010 --> 31:52.030 the Department of Homeland Security. 31:52.030 --> 31:54.180 And as they've advanced their capability 31:54.180 --> 31:55.530 and they've stood up CISA, 31:55.530 --> 31:58.139 the Cyber Security and Infrastructure Security Agency, 31:58.139 --> 32:01.280 that is specifically tasked with defending 32:01.280 --> 32:03.786 our critical infrastructure from the cyber domain 32:03.786 --> 32:08.450 across our nation, they are also incredibly collaborative 32:08.450 --> 32:09.570 and great partners. 32:09.570 --> 32:10.860 But what we find is that we all have 32:10.860 --> 32:12.137 a little bit different role within that 32:12.137 --> 32:15.370 and how do define that and how do we further advance that 32:15.370 --> 32:17.730 and continuing to look at the threats, 32:17.730 --> 32:20.700 and I'll just use an example of the elections in 2018, 32:22.213 --> 32:24.500 the NORTHCOM and CyberCom participated 32:24.500 --> 32:26.510 in some of the election security. 32:26.510 --> 32:28.360 One of the ways that we're able to do that 32:28.360 --> 32:31.590 was taking full advantage of our guard. 32:31.590 --> 32:33.160 Our National Guard are great partners 32:33.160 --> 32:35.410 in all of the missions we do within NORTHCOM 32:35.410 --> 32:37.560 but we also found they're great partners 32:37.560 --> 32:39.900 in the cyber security as well, because if you think about 32:39.900 --> 32:42.580 our electoral system, it's really run by the States 32:42.580 --> 32:44.820 and then brought up to the federal piece of that. 32:44.820 --> 32:46.557 And so we applied this same model that we have 32:46.557 --> 32:49.620 and at DISCA, the Defense Support Civil Authorities, 32:49.620 --> 32:51.150 that we do for say, a hurricane, 32:51.150 --> 32:53.120 and we applied that to cyber security. 32:53.120 --> 32:56.680 And so we NORTHCOM don't have specific cyber capability 32:56.680 --> 32:58.080 or expertise necessarily beyond 32:58.080 --> 32:59.760 what any combatant command of, 32:59.760 --> 33:02.600 but what we do is we're able to take Paul Nakasone's team 33:02.600 --> 33:04.710 and funnel it through NORTHCOM 33:04.710 --> 33:07.870 and then be able to apply that in a DISCA type model, 33:07.870 --> 33:10.630 federal capability down to a state level. 33:10.630 --> 33:12.170 We had Paul Nakasone came in, 33:12.170 --> 33:13.784 the Department of Homeland Security came in, 33:13.784 --> 33:18.310 and all the TAGS came in to a conference that we held 33:18.310 --> 33:21.900 twice now within NORTHCOM in preparation for these elections 33:21.900 --> 33:24.910 to coordinate the level, to share intel, to bring it up 33:24.910 --> 33:26.240 to the highest classification level, 33:26.240 --> 33:29.110 so the TAGS at the state level have their say, 33:29.110 --> 33:31.690 and then they are able to put in sensors and in that 33:31.690 --> 33:34.050 they know that they can send up the red star cluster. 33:34.050 --> 33:36.420 When they need help at the state level from the federal, 33:36.420 --> 33:39.280 whether that be from DHS or Cyber Command or NORTHCOM, 33:39.280 --> 33:41.670 we now have the forums of which to do that. 33:41.670 --> 33:43.870 But this is a threat going into the future, 33:43.870 --> 33:45.380 not just for election security, 33:45.380 --> 33:47.310 but for our critical infrastructure 33:47.310 --> 33:49.223 that will remain incredibly important. 33:50.080 --> 33:51.920 - It's sure-- - If I could just, 33:51.920 --> 33:54.880 a little shout out for our 16th Air Force brothers 33:54.880 --> 33:58.780 and sisters, their alignment with General Walters 33:58.780 --> 34:03.300 priorities inside of EUCOM to get after his priorities 34:03.300 --> 34:07.910 along that cyber line of effort, has really, 34:07.910 --> 34:11.150 in a very short period of time, proved huge dividends 34:11.150 --> 34:12.650 for the collective force. 34:12.650 --> 34:14.650 And not only understanding 34:14.650 --> 34:17.790 and clarifying where we needed help, 34:17.790 --> 34:20.330 or where they were perceiving threats 34:20.330 --> 34:23.570 from an INW perspective, but then offering solutions 34:23.570 --> 34:25.050 that were quickly implemented 34:25.050 --> 34:27.230 because they had the right authorities. 34:27.230 --> 34:32.230 And I would offer to you over time, the power of that ISR 34:32.330 --> 34:35.060 cyber connection and the authorities that they have 34:35.060 --> 34:37.500 are very helpful to the combatant commands 34:37.500 --> 34:39.360 and one I would think as time moves on, 34:39.360 --> 34:41.860 will be one shared across the force. 34:41.860 --> 34:42.940 - Great. 34:42.940 --> 34:44.257 General Brown, back to you have, 34:44.257 --> 34:48.330 you've got some specific examples that could be, in fact, 34:48.330 --> 34:49.770 used as a template for industry, 34:49.770 --> 34:54.080 where you've had very successful interaction in your theater 34:54.080 --> 34:57.220 with industry, including innovation opportunities 34:57.220 --> 34:58.940 or just solving hard problems, 34:58.940 --> 35:01.183 Command and Control problems, or other problems? 35:02.020 --> 35:02.853 - Well, one of the things is, 35:02.853 --> 35:06.720 we have a science and technology and information exchange 35:06.720 --> 35:10.550 and we had it here back in November. 35:10.550 --> 35:12.640 And it's a great opportunity for us to bring industry in 35:12.640 --> 35:15.010 and kinda walk 'em through the concepts 35:15.010 --> 35:18.470 that we're working on, and again, it's kind of how we just, 35:18.470 --> 35:20.840 you know, we have our capabilities list, 35:20.840 --> 35:23.670 capability gaps list, but I told my team, 35:23.670 --> 35:25.770 we gotta top just, 'cause otherwise we just give them 35:25.770 --> 35:27.820 the gaps list, they'll solve that gap, 35:27.820 --> 35:29.650 but it may not solve the problem. 35:29.650 --> 35:31.670 And so the dialogue that we're able to have with them 35:31.670 --> 35:34.156 to talk through how we'd work our old plan, 35:34.156 --> 35:37.290 aspects of the old plan, aspects of our strategy 35:37.290 --> 35:39.810 has been very helpful with the industry 35:39.810 --> 35:43.510 and I kinda see it coming back, as I talk to industry, 35:43.510 --> 35:44.860 some of the things we're talking about, 35:44.860 --> 35:47.623 they're providing us solutions and opportunities. 35:48.500 --> 35:51.720 Our challenge is, how do we get that into our system 35:51.720 --> 35:53.400 to actually be able to fund some of those things, 35:53.400 --> 35:54.450 to move the ball forward. 35:54.450 --> 35:55.520 - Yes, sir. 35:55.520 --> 35:58.310 A lot of questions from the audience on the Arctic. 35:58.310 --> 36:01.610 Implications for melting ice cap and what's going on 36:01.610 --> 36:05.270 in the Arctic obviously Russians very active in that area, 36:05.270 --> 36:08.770 so, take it away, whoever will go on, start with the Arctic, 36:08.770 --> 36:10.920 it's certainly of interest to our audience. 36:10.920 --> 36:13.870 - Yeah, I'll start and the way that we look at the Arctic is 36:13.870 --> 36:16.800 it's an avenue of approach to the homeland. 36:16.800 --> 36:20.080 And so we used to look at that as a buffer zone, 36:20.080 --> 36:22.110 much like the oceans used to be moats, 36:22.110 --> 36:25.920 and now it's an attack convector and we currently see Russia 36:25.920 --> 36:29.060 advancing their capability and capacity to operate there. 36:29.060 --> 36:31.750 Now, some of that makes sense, based on a large percentage 36:31.750 --> 36:34.380 of their GDP is based on the economics of what they 36:34.380 --> 36:36.080 garden from the Arctic. 36:36.080 --> 36:37.290 But some of the development 36:37.290 --> 36:40.140 clearly appears to be going well beyond that. 36:40.140 --> 36:42.770 And so, buying, one of the roles that we have 36:42.770 --> 36:44.900 is within our unified command plant for NORTHCOM 36:44.900 --> 36:47.880 is we are the Arctic advocates, so we are, 36:47.880 --> 36:50.900 despite that we share with both PACOM and EUCOM, 36:50.900 --> 36:53.240 the Arctic battle space if you will, 36:53.240 --> 36:55.600 we are designators who are navigating 36:55.600 --> 36:57.660 for our capability and capacity. 36:57.660 --> 37:00.500 And so one of the things that we're really focused on is, 37:00.500 --> 37:03.380 how do we make sure the force is able to operate 37:03.380 --> 37:05.340 in that very difficult environment, 37:05.340 --> 37:08.230 I'll bring two things to mind here. 37:08.230 --> 37:11.300 One is, you can deploy a force, say to the Middle East 37:11.300 --> 37:12.860 or other areas all over the globe, 37:12.860 --> 37:15.070 that hasn't necessarily been there before. 37:15.070 --> 37:16.940 And they can be quite effective. 37:16.940 --> 37:18.730 But you can't do that in the Arctic. 37:18.730 --> 37:21.160 If you have not trained, if you don't have the right kit, 37:21.160 --> 37:22.940 you don't have the right gear, 37:22.940 --> 37:25.490 you will not be able to operate effectively in the Arctic, 37:25.490 --> 37:27.740 and so more and more it's about how do we get the services 37:27.740 --> 37:29.870 to include our great United States Air Force 37:29.870 --> 37:32.600 to increase the exposure that we give our airmen 37:32.600 --> 37:35.180 to the Arctic conditions, and we have a great range 37:35.180 --> 37:37.320 in the JPARC range up in Alaska, 37:37.320 --> 37:39.700 that couriers great opportunity to do that, 37:39.700 --> 37:42.540 so continuing to expose our force there, 37:42.540 --> 37:44.030 develop the capability to operate 37:44.030 --> 37:45.860 in the Arctic is critically important. 37:45.860 --> 37:46.950 And the second piece of it is, 37:46.950 --> 37:49.270 we need to be able to communicate in the Arctic. 37:49.270 --> 37:50.940 And one of the things we find is leveraging 37:50.940 --> 37:53.380 with commercial industry, is gonna help us 37:53.380 --> 37:56.550 advance our capability to get that communication there 37:56.550 --> 37:59.180 and partnering with folks that have similar challenges 37:59.180 --> 38:03.310 for example the oil industry, some of the Alaska Federation 38:03.310 --> 38:06.730 and natives in the indigenous people have similar challenges 38:06.730 --> 38:07.880 of lacking that communication, 38:07.880 --> 38:09.940 so how can we partner with them to make a business scape 38:09.940 --> 38:12.657 to get the commercial world to provide those services. 38:12.657 --> 38:15.893 And so we're working with things like Starlink, OneWeb 38:15.893 --> 38:19.720 are great examples, where if you could get communication 38:19.720 --> 38:21.310 at the level that you have in your home 38:21.310 --> 38:23.630 and broadband connectivity throughout the Arctic, 38:23.630 --> 38:26.020 that would completely change our ability to operate there, 38:26.020 --> 38:28.350 where some of our satellites don't have the ability 38:28.350 --> 38:30.140 to fully connect there. 38:30.140 --> 38:33.210 And those endeavors that we're doing with those companies 38:33.210 --> 38:34.900 I think are gonna change the way 38:34.900 --> 38:36.520 that we will be able to operate in the Arctic 38:36.520 --> 38:39.210 to connect the force once they're trained 38:39.210 --> 38:42.185 and able to operate there in a much more robust fashion. 38:42.185 --> 38:45.720 - What I'd add is, we do kinda pay attention to 38:45.720 --> 38:49.330 or everybody else will pay attention to the Antarctic. 38:49.330 --> 38:52.100 Because what happens in the Arctic is a precursor 38:52.100 --> 38:54.860 what could potentially occur in the Antarctic. 38:54.860 --> 38:57.523 And the Antarctic treaty is up for review in 2048, 38:58.410 --> 39:00.920 there is actually great power competition on the ice 39:00.920 --> 39:05.336 down there with the Russians and the PRC, 39:05.336 --> 39:06.760 and I think we just gotta be paying attention to it 39:06.760 --> 39:10.340 so it doesn't go down a path where you're not doing 39:11.463 --> 39:13.880 doing more than research, and that's an aspect 39:13.880 --> 39:15.549 we're paying attention to and learning some things 39:15.549 --> 39:17.410 about what's going on in the Arctic, 39:17.410 --> 39:19.890 when we start talking about capabilities. 39:19.890 --> 39:22.490 'Cause you'll have the same capabilities 39:22.490 --> 39:23.970 down at the South Pole. 39:23.970 --> 39:25.278 - [Orville Wright] Sure, yes, sir. 39:25.278 --> 39:28.958 - I'll just add as General O'Shaughnessy said, 39:28.958 --> 39:33.100 we've had opportunities with our partners 39:33.100 --> 39:36.000 to leverage the Arctic also as an opportunity 39:36.000 --> 39:39.200 for ourselves to create a dilemma for the Russians. 39:39.200 --> 39:41.220 Recognizing what we've been able to do 39:41.220 --> 39:45.300 with Bomber Taskforce support from some of the nations 39:45.300 --> 39:47.176 that clearly have interests up there, 39:47.176 --> 39:49.360 we've been able to leverage that to learn 39:49.360 --> 39:51.320 about some of the challenges that we have up there 39:51.320 --> 39:54.900 when it comes to communications to being able to operate. 39:54.900 --> 39:57.930 But also at the same time, provide us the insight 39:57.930 --> 39:59.370 to how we could better compete 39:59.370 --> 40:02.100 as global integrators in the Arctic. 40:02.100 --> 40:04.630 Now, we've got work to do, but I think 40:04.630 --> 40:08.290 just the connective tissue we have to have across 40:08.290 --> 40:11.200 the combatant commands to be able to do that 40:11.200 --> 40:15.080 is frankly something the Russians recognize we're doing 40:15.080 --> 40:16.470 and it's gonna drive them 40:16.470 --> 40:19.810 to either dedicate resources toward, or at least, 40:19.810 --> 40:22.340 think through how they would manage to protect that 40:22.340 --> 40:25.343 should we use that as an access for entry into Russia. 40:26.630 --> 40:28.640 - Okay, last round of questions, again, 40:28.640 --> 40:32.330 thanks to Major Balentine, you all have gotten into this 40:32.330 --> 40:35.890 somewhat already, but what, given the benefits, 40:35.890 --> 40:39.510 potential benefits of multi-domain operations 40:39.510 --> 40:42.350 and joining all the main command control to fuse 40:42.350 --> 40:43.570 and integrate those operations 40:43.570 --> 40:45.360 in a common operational picture. 40:45.360 --> 40:48.380 What are some of the challenges, even threats that you see? 40:48.380 --> 40:50.319 We've talked about the electronic threat, 40:50.319 --> 40:51.591 you've addressed somewhat 40:51.591 --> 40:53.693 command and control at too high a level, 40:55.200 --> 40:58.410 that would impact the ability of our forces to operate, 40:58.410 --> 41:01.070 so, let's just wind it up with MDO, 41:01.070 --> 41:02.620 the good, the bad and the ugly. 41:04.030 --> 41:05.610 - Well, I'll start and just look 41:05.610 --> 41:07.166 at the threats that we're faced to the homeland, 41:07.166 --> 41:09.650 we used to be able to look at these very stoke pipe, right, 41:09.650 --> 41:10.997 you look at it from ballistic missile defense, 41:10.997 --> 41:13.340 you have a system that's designed to give you 41:13.340 --> 41:16.540 that initial warning and then be able to actually defeat 41:16.540 --> 41:19.210 threats from say, a rogue nation, like North Korea, 41:19.210 --> 41:22.400 you have the ability to operate against air threats 41:22.400 --> 41:24.830 in, say, Russia, long range aviation. 41:24.830 --> 41:26.970 But now if you look at the advanced threat where we have it 41:26.970 --> 41:29.940 literally from the undersea threats that we face, 41:29.940 --> 41:32.390 the maritime threats that we face, the air domain threats 41:32.390 --> 41:35.160 we face and the space threats as DT Thompson talked about 41:35.160 --> 41:37.150 to include it as well as a cyber. 41:37.150 --> 41:39.390 We can't approach those in a stoke pipe manner. 41:39.390 --> 41:42.347 We have to look at this from the overall multi-domain aspect 41:42.347 --> 41:44.430 of that and all domain aspect of that 41:44.430 --> 41:46.010 if we're going to be able to put 41:46.010 --> 41:48.170 an affordable system forward. 41:48.170 --> 41:50.349 So we are looking at this from the ground up, 41:50.349 --> 41:52.420 to build this, what we're calling 41:52.420 --> 41:55.860 the Strategic Homeland Integrate Ecosystem for Layer Defense 41:55.860 --> 41:58.260 that is truly multi-domain from the start. 41:58.260 --> 42:00.660 And that way, you can plug in different capabilities 42:00.660 --> 42:04.252 but they contribute across multiple domains. 42:04.252 --> 42:07.040 That going forward, I think, given the advanced nature 42:07.040 --> 42:09.010 of the threats, given for example, hypersonics 42:09.010 --> 42:11.280 that you can no longer take a ballistic missile 42:11.280 --> 42:13.640 that you can just have a radar on for a short time, 42:13.640 --> 42:16.130 but because it's ballistic, you now know where it's going. 42:16.130 --> 42:17.680 You now need to maintain custody 42:17.680 --> 42:19.770 of that threat the entire time. 42:19.770 --> 42:21.440 Those advanced threats drive us 42:21.440 --> 42:23.240 to this multi-domain look at this, 42:23.240 --> 42:25.900 and so I think all the things we build going into the future 42:25.900 --> 42:28.450 need to plug in to the broader multi-domain capability, 42:28.450 --> 42:31.390 if we're going to be able to afford all the systems 42:31.390 --> 42:33.140 to put 'em together. 42:33.140 --> 42:33.973 - General Brown. 42:33.973 --> 42:36.760 - I think the good part is that there's good dialogue, 42:36.760 --> 42:39.047 when you look at JADC2 multi-domain operations 42:39.047 --> 42:42.200 and it forces us to be more joint and coaliltion focused, 42:42.200 --> 42:44.284 so that's the good part. 42:44.284 --> 42:45.970 I think some of the challenges, I wouldn't call it bad 42:45.970 --> 42:49.200 or ugly, but the, I think some of the challenges 42:49.200 --> 42:50.470 we're gonna have in the future is 42:50.470 --> 42:52.550 how we're, with all that information, 42:52.550 --> 42:54.720 connecting every sensor to every shooter, 42:54.720 --> 42:56.830 how we divvy that up across the joint force 42:56.830 --> 43:00.060 so we can put the effects, both kinetic and non-kinetic 43:00.060 --> 43:03.230 in place to make things happen, so we don't all show up 43:03.230 --> 43:06.940 at the same place, all trying to put capability 43:08.206 --> 43:10.728 on the threat, or we leave a gap. 43:10.728 --> 43:12.050 And those are my concerns. 43:12.050 --> 43:13.400 And then the last piece is, 43:14.940 --> 43:16.550 the concern I have is our ability 43:16.550 --> 43:19.530 to actually trust each other to be able to do things 43:19.530 --> 43:22.840 and allow at the lower level for our joint 43:22.840 --> 43:25.420 or coalition partner to take action. 43:25.420 --> 43:28.110 So we can move at the speed that's required. 43:28.110 --> 43:30.393 If we've gotta check the checker, 43:31.565 --> 43:33.810 it's gonna take us a while to get to where we need to be. 43:33.810 --> 43:36.910 So, we gotta be able to delegate down to our lower level 43:36.910 --> 43:39.160 and trust Shirdy to do their job. 43:39.160 --> 43:40.350 - And to wind up, General Harrigian. 43:40.350 --> 43:41.350 - Thank you so much. 43:42.360 --> 43:44.373 So, here's my analogy on this. 43:45.290 --> 43:47.460 Everybody's been out in the joint command, 43:47.460 --> 43:49.090 you got the planners, 43:49.090 --> 43:52.400 the J5 comes up with a great idea, right? 43:52.400 --> 43:54.870 They lay this idea out and then they look at you 43:54.870 --> 43:58.700 in the three in ops and go, "Get after it." 43:58.700 --> 44:02.320 And you're like "Whoa! Hey, this is not that easy." 44:02.320 --> 44:04.470 That's right, fan man, you're the guy in the five 44:04.470 --> 44:05.604 giving it to the three. 44:05.604 --> 44:06.940 (laughing) 44:06.940 --> 44:11.190 And so now we gotta turn power point into action. 44:11.190 --> 44:14.880 And like each one of us said, we gotta do things now 44:14.880 --> 44:17.970 to set us up to win the fight that I believe 44:17.970 --> 44:20.630 incrementally we can build these capabilities 44:20.630 --> 44:22.310 with the right people, cognitively 44:22.310 --> 44:24.130 with the right capabilities with the support 44:24.130 --> 44:26.190 from our partners, from the defense industry 44:26.190 --> 44:27.860 to get where we need to go. 44:27.860 --> 44:30.070 But we gotta make sure we keep thinking all the way 44:30.070 --> 44:32.120 through this, to make sure we're solving the right problem. 44:32.120 --> 44:33.170 And I'll leave it at that. 44:33.170 --> 44:34.003 Thanks. 44:34.003 --> 44:35.575 - Well, you all have been awesome, thank you so very much. 44:35.575 --> 44:37.825 (applause)