WEBVTT 00:00.371 --> 00:04.204 - [Announcer] Lieutenant General Dave Deptula. 00:09.234 --> 00:10.770 - I thank you very much, 00:10.770 --> 00:13.079 and good afternoon, ladies and gentlemen. 00:13.079 --> 00:15.391 And welcome to our seminar session on 00:15.391 --> 00:18.474 Global Reach in a Fusion Environment. 00:19.297 --> 00:21.939 And I put this topic in context, 00:21.939 --> 00:23.675 it's critical to acknowledge 00:23.675 --> 00:25.905 that information and its management 00:25.905 --> 00:28.301 is just as important today as are 00:28.301 --> 00:30.159 traditional tools of how we 00:30.159 --> 00:33.492 project military power around the world. 00:33.678 --> 00:35.790 Information and data is the force involving 00:35.790 --> 00:37.457 all these tools from 00:37.708 --> 00:39.919 individual military instruments-- 00:39.919 --> 00:43.683 satellites, airlifters, fighters, bombers, ICBMs-- 00:43.683 --> 00:46.650 into a highly integrated enterprise with the exchange 00:46.650 --> 00:48.869 of information and data will determine 00:48.869 --> 00:51.952 success or failure in future warfare. 00:53.914 --> 00:57.421 You heard the Chief talk about the importance 00:57.421 --> 01:00.504 of this topic just a few minutes ago. 01:00.695 --> 01:03.362 Now this means we need not only, 01:03.541 --> 01:06.745 we have to not only get serious about faster 01:06.745 --> 01:08.354 and more capable networks, 01:08.354 --> 01:10.433 but we've gotta fundamentally change the paradigm 01:10.433 --> 01:12.833 of how we fight because information is now 01:12.833 --> 01:16.000 the dominant factor in modern warfare. 01:17.012 --> 01:19.262 Desired effects in projecting power through 01:19.262 --> 01:21.335 global reach will increasingly be attained 01:21.335 --> 01:23.899 though the interaction of multiple systems, 01:23.899 --> 01:26.379 each one sharing information and empowering 01:26.379 --> 01:28.751 one another for a common purpose. 01:28.751 --> 01:32.334 It means treating each platform as a sensor 01:32.677 --> 01:34.594 as well as an effector. 01:35.746 --> 01:38.293 It will require a command and control paradigm 01:38.293 --> 01:40.084 that enables automatic linking 01:40.084 --> 01:43.084 as does cell phone technology today. 01:43.461 --> 01:47.022 It will also need to transfer data seamlessly 01:47.022 --> 01:49.242 without need for human interaction between 01:49.242 --> 01:51.159 the Combat Cloud nodes. 01:51.333 --> 01:55.500 Plus, it has to be reliable, secure, and jam-proof. 01:56.662 --> 01:58.668 Creating the reality of a Combat Cloud 01:58.668 --> 02:00.255 that conducts Fusion Warfare 02:00.255 --> 02:02.088 has major implications 02:02.203 --> 02:05.203 for how we think about global reach. 02:05.492 --> 02:07.353 So we have a distinguished panel 02:07.353 --> 02:09.332 to address these implications. 02:09.332 --> 02:11.329 And following their brief opening remarks, 02:11.329 --> 02:14.496 we'll engage them with your questions. 02:14.712 --> 02:16.814 Copies of their bios are in your program, 02:16.814 --> 02:18.366 and this afternoon, 02:18.366 --> 02:19.344 we're privileged to have, 02:19.344 --> 02:20.574 from left to right, 02:20.574 --> 02:23.558 General Robin Wren, Commander Global Strike Command; 02:23.558 --> 02:27.078 General Dewey Everhart, Commander Air Mobility Command; 02:27.078 --> 02:30.288 General Jay Raymond, Commander Air Force Space Command; 02:30.288 --> 02:33.736 Lieutenant General Dash Jamieson, Deputy Chief of Staff 02:33.736 --> 02:35.971 for Intelligence, Surveillance, and Reconnaissance; 02:35.971 --> 02:38.591 Paul Tronsor, Vice President, Global Ops Control 02:38.591 --> 02:41.674 and Service Quality Assurance, FedEx; 02:42.107 --> 02:44.683 and Retired Colonel Mark Valentine, 02:44.683 --> 02:47.503 Air Force Strategic Programs, Microsoft Corporation. 02:47.503 --> 02:49.915 So General Rand, over to you. 02:49.915 --> 02:51.332 - Thank you, sir. 02:51.563 --> 02:53.242 I appreciate the opportunity to be here. 02:53.242 --> 02:54.455 Chief, thank you. 02:54.455 --> 02:56.122 I thought your speech was perfect, 02:56.122 --> 02:57.183 and it really, 02:57.183 --> 02:58.763 anything that, that I 02:58.763 --> 03:00.096 would have said, 03:00.354 --> 03:02.173 just listen to what the Chief said 03:02.173 --> 03:03.691 'cause that's what we're dealing with 03:03.691 --> 03:05.315 in Air Force Global Strike. 03:05.315 --> 03:06.482 Global Strike. 03:07.797 --> 03:11.115 And how do we do that with this fusion environment 03:11.115 --> 03:13.437 as things are changing in the speed of the battle field? 03:13.437 --> 03:16.036 So our biggest challenge right now is 03:16.036 --> 03:19.606 we've gotta upgrade our current platforms that we have 03:19.606 --> 03:22.523 so they can be persistent and work. 03:22.676 --> 03:23.913 I always talk about, people, 03:23.913 --> 03:25.740 the beauty of this command 03:25.740 --> 03:29.740 is that we can do not in days, weeks, or months, 03:30.385 --> 03:31.326 but in hours, 03:31.326 --> 03:32.305 we can hold, 03:32.305 --> 03:33.722 with his support, 03:33.985 --> 03:35.568 with Jay's support, 03:35.735 --> 03:38.998 we can hold any target in a plan at risk. 03:38.998 --> 03:42.195 And that's a powerful capability to have. 03:42.195 --> 03:43.531 But if we're gonna be able to do that 03:43.531 --> 03:44.577 five years from now, 03:44.577 --> 03:45.803 10 years from now, there's things 03:45.803 --> 03:48.646 we've gotta do to our existing platforms. 03:48.646 --> 03:50.556 And that's where the challenge lies 03:50.556 --> 03:52.606 as we prepare, so the Chief said, 03:52.606 --> 03:54.004 "They rolled the marble to us." 03:54.004 --> 03:54.927 We're ready. 03:54.927 --> 03:56.412 We're identifying what those needs 03:56.412 --> 03:57.901 and requirements are, 03:57.901 --> 03:59.759 and we're gonna get after it. 03:59.759 --> 04:01.963 Not just with the new B-21 comin' onboard. 04:01.963 --> 04:04.036 Because we're gonna need to continue 04:04.036 --> 04:07.102 to operate with our systems that we have. 04:07.102 --> 04:08.943 I wanna just tell you one quick war story, 04:08.943 --> 04:10.199 and then I'll pass the mike, 04:10.199 --> 04:11.282 about fusion. 04:12.030 --> 04:16.197 I know you all read about the neat thing that happened 04:16.511 --> 04:19.761 a few weeks ago in Libya with our B-2s. 04:20.335 --> 04:23.946 In 36 hours, the young men and women at Whiteman 04:23.946 --> 04:25.845 generated five airplanes, 04:25.845 --> 04:27.345 built 400 weapons, 04:28.454 --> 04:30.037 loaded 400 weapons. 04:30.796 --> 04:33.546 Then they were ready in 36 hours, 04:34.186 --> 04:37.518 which we were given 96 to be ready to go. 04:37.518 --> 04:38.601 Taxied three. 04:39.061 --> 04:40.217 Took off three. 04:40.217 --> 04:41.736 Air refueled with three. 04:41.736 --> 04:42.903 Sent one home. 04:43.463 --> 04:46.213 Delivered over a hundred weapons, 04:47.447 --> 04:49.364 near time simultaneous. 04:49.728 --> 04:51.371 While they were en route, 04:51.371 --> 04:54.049 they got updated target coordinates. 04:54.049 --> 04:55.216 That's fusion. 04:58.751 --> 05:00.060 Dropped their weapons. 05:00.060 --> 05:01.227 Went and held. 05:01.678 --> 05:03.210 Got called from the ground forces 05:03.210 --> 05:04.850 and say you can go home now. 05:04.850 --> 05:06.600 There's nothing left. 05:06.872 --> 05:08.390 They returned back home, 05:08.390 --> 05:11.140 landed after 32 and a half hours, 05:11.556 --> 05:12.389 and the next morning, 05:12.389 --> 05:14.613 we resumed normal operations. 05:14.613 --> 05:15.890 The very next day, 05:15.890 --> 05:16.723 our B-52, 05:18.160 --> 05:19.577 a 1961-built B-52 05:21.638 --> 05:24.055 with the new connect onboard, 05:25.005 --> 05:27.672 was able to get a dynamic target 05:28.031 --> 05:30.531 from flew 40 minutes from Iraq 05:32.283 --> 05:34.950 into Western Syria and delivered 05:35.026 --> 05:38.609 a bunch of whoop ass on some really, really 05:40.060 --> 05:42.393 bad guys to the tune of 110. 05:43.694 --> 05:44.861 That's fusion. 05:45.017 --> 05:46.948 And that's a capability that we now 05:46.948 --> 05:49.610 have and we just gotta continue to evolve 05:49.610 --> 05:51.693 so we're able to do that. 05:53.346 --> 05:54.560 - So Chief, thank you. 05:54.560 --> 05:56.258 Thank you for allowing me, 05:56.258 --> 05:58.246 and Bobbo, thank you for that. 05:58.246 --> 06:00.712 One of the things you'll notice about that scenario 06:00.712 --> 06:03.056 is that radio technology and the fusion of the data 06:03.056 --> 06:06.361 that we have is a big challenge for the equities 06:06.361 --> 06:08.432 that we have in Air Mobility Command. 06:08.432 --> 06:10.278 And the reason why I say that is because 06:10.278 --> 06:12.406 what we have on board our airplane to increase 06:12.406 --> 06:14.239 the fusion of the data 06:15.284 --> 06:16.951 is the Mark I radio. 06:17.402 --> 06:18.712 So that challenges us 06:18.712 --> 06:19.773 each and every day 06:19.773 --> 06:20.608 of what we have, 06:20.608 --> 06:23.050 what we lengthen into an A2 AD environment. 06:23.050 --> 06:25.459 We have Fifth Gen aircraft that are being 06:25.459 --> 06:28.126 supported by a One Gen platform. 06:29.209 --> 06:30.799 And that's our refueling. 06:30.799 --> 06:32.265 So our challenges comin' up to us 06:32.265 --> 06:34.108 as in our projection models 06:34.108 --> 06:35.160 of the air refueling 06:35.160 --> 06:37.372 and also in the forward basing. 06:37.372 --> 06:40.371 And I will tell you that our air refuelers 06:40.371 --> 06:43.121 and our Mobility aircraft provide 06:43.134 --> 06:44.967 a huge agile response, 06:46.405 --> 06:48.729 enable a huge agile response 06:48.729 --> 06:50.614 and for our strike aircraft in the near future. 06:50.614 --> 06:52.156 And so there's two ways we're gettin' after this, 06:52.156 --> 06:54.428 and we're lookin' at our investment in different areas. 06:54.428 --> 06:56.135 One is in the defensive systems. 06:56.135 --> 06:57.588 This is not only in air refuelers, 06:57.588 --> 06:59.035 but also in our Mobility aircraft 06:59.035 --> 07:00.264 to be able to survive, 07:00.264 --> 07:04.431 to project those power platforms further on down the line. 07:04.442 --> 07:06.691 Also we're looking at our survivability. 07:06.691 --> 07:08.328 Because as I've talked to Dash 07:08.328 --> 07:09.688 and you've brought up many times, 07:09.688 --> 07:13.855 we have a lotta capability that we can onboard data 07:14.050 --> 07:15.569 through our Mobility platforms that 07:15.569 --> 07:16.635 are already out there, 07:16.635 --> 07:18.958 and off-board data to get it to where it needs to go 07:18.958 --> 07:20.369 through to the decision makers to execute 07:20.369 --> 07:22.369 against the next target. 07:23.737 --> 07:24.904 That is power. 07:26.447 --> 07:29.314 That is air power at the tip of the spear 07:29.314 --> 07:30.194 at the moment's notice. 07:30.194 --> 07:33.942 At the fused data and increases the survivability 07:33.942 --> 07:35.359 across the board. 07:36.177 --> 07:38.355 So we're looking at resilience of 07:38.355 --> 07:41.353 our Mobility platforms and our layered response 07:41.353 --> 07:44.663 and have them also be an alternate path. 07:44.663 --> 07:46.645 They may not be the primary, 07:46.645 --> 07:50.133 but it could be the alternate path to relay that data. 07:50.133 --> 07:52.050 We call this enclaving, 07:52.123 --> 07:54.559 is what we call it in a Mobility world. 07:54.559 --> 07:56.829 The KC-46 has capable systems. 07:56.829 --> 07:59.824 It's bringing on a lot of capability. 07:59.824 --> 08:01.997 However, there's better ways we can get after this. 08:01.997 --> 08:03.124 Better ways we can fuse. 08:03.124 --> 08:04.729 Better way we can use data 08:04.729 --> 08:08.896 in systems, and we're studying those things right now. 08:09.767 --> 08:13.279 I believe that our tankers will be able to continue 08:13.279 --> 08:16.434 to support and enable and be key enablers 08:16.434 --> 08:18.604 in support of this fused data. 08:18.604 --> 08:20.397 And I think that is one of the key assets, 08:20.397 --> 08:21.773 and then that will branch and sequel 08:21.773 --> 08:23.297 over to our Mobility Forces. 08:23.297 --> 08:25.301 But we cannot do it at all 08:25.301 --> 08:27.608 if it's not in conjunction with our space partners 08:27.608 --> 08:29.949 in the equities and the assets that Jay Raymond 08:29.949 --> 08:31.032 brings to us. 08:31.442 --> 08:32.376 - Thank you, sir. 08:32.376 --> 08:33.567 I'd like to, first of all, 08:33.567 --> 08:34.769 thank the Chief for the opportunity. 08:34.769 --> 08:36.073 I'd also would like to thank 08:36.073 --> 08:37.218 the Air Force Association 08:37.218 --> 08:38.966 for hosting this conference. 08:38.966 --> 08:39.987 It's great to be here, 08:39.987 --> 08:41.230 and it's great to get the chance 08:41.230 --> 08:43.601 to interact with the professionals 08:43.601 --> 08:45.725 that are in the audience today. 08:45.725 --> 08:48.182 You know, as I read the title of this panel, 08:48.182 --> 08:50.375 I started thinking about the capabilities 08:50.375 --> 08:52.491 that I bring to the Space capabilities 08:52.491 --> 08:53.612 and the Cyber capabilities 08:53.612 --> 08:55.278 that the airmen of Air Force Space Command 08:55.278 --> 08:56.903 bring and really what they bring is 08:56.903 --> 08:58.403 the DNA of fusion. 08:58.794 --> 09:00.692 And if you think about it, 09:00.692 --> 09:02.626 none of what General Rand talked about, 09:02.626 --> 09:04.223 whether it's the B-2 mission, 09:04.223 --> 09:07.152 whether what General, or Chief talked about (mumbles) 09:07.152 --> 09:08.612 on the personal recovery. 09:08.612 --> 09:10.241 None of that happens if you can't have the ability to fuse. 09:10.241 --> 09:13.325 And none of that happens without Space and Cyber. 09:13.325 --> 09:16.047 I would challenge anybody in this room to come up with 09:16.047 --> 09:18.317 anything that we do today as a Joint Force 09:18.317 --> 09:21.542 that isn't enabled by the fusion capability that 09:21.542 --> 09:23.959 Space and Cyber brings to it. 09:24.381 --> 09:25.548 And you can't. 09:25.846 --> 09:27.397 There's nothing we do as a Joint Force, 09:27.397 --> 09:29.763 absolutely nothing that we do as a Joint Force, 09:29.763 --> 09:32.756 that isn't enabled by that Space and Cyber. 09:32.756 --> 09:34.358 Our challenge in Air Force Space Command 09:34.358 --> 09:37.783 is that, as we've worked largely since Desert Storm 09:37.783 --> 09:41.128 to integrate those Space and now Cyber capabilities 09:41.128 --> 09:43.550 into the fight, our potential adversaries, 09:43.550 --> 09:46.145 our strategic competitors have had a front row seat, 09:46.145 --> 09:47.458 and they've been watchin' us. 09:47.458 --> 09:49.659 And they understand the power that we get by 09:49.659 --> 09:53.826 fusing, by using Space and Cyber to fuse this together. 09:54.172 --> 09:57.384 And they're actively developing capabilities to keep us 09:57.384 --> 09:59.813 from being able to access those Space capabilities 09:59.813 --> 10:00.829 to our advantage. 10:00.829 --> 10:02.662 So it, not only is it. 10:02.852 --> 10:04.333 It's not only good enough today to be able 10:04.333 --> 10:06.408 to integrate Space and Cyber capabilities in the fight, 10:06.408 --> 10:08.269 we must be able to protect and defend. 10:08.269 --> 10:09.979 That's the focus of Air Force Space Command today. 10:09.979 --> 10:13.014 Chief talked about it being a Joint Warfighting domain, 10:13.014 --> 10:15.431 just like air, land, and sea. 10:16.772 --> 10:18.831 And we will do our best to make sure 10:18.831 --> 10:20.765 that when the light switch is turned on 10:20.765 --> 10:23.116 that Space capabilities are always there 10:23.116 --> 10:26.949 because DNA fuels our American way of warfare. 10:27.363 --> 10:28.439 I would ask, I think there are some airmen here 10:28.439 --> 10:29.938 from Patrick Air Force Base. 10:29.938 --> 10:32.521 Stand up, please, if you would. 10:32.534 --> 10:34.645 So these airmen right here are from Patrick. 10:34.645 --> 10:37.355 Next Wednesday, they're gonna launch a WGS satellite, 10:37.355 --> 10:40.473 and they'll launch it perfectly like they always do. 10:40.473 --> 10:42.531 And that's why I'm glad you're here. 10:42.531 --> 10:43.402 As the Chief said, 10:43.402 --> 10:45.366 this is a perfect professional development conference, 10:45.366 --> 10:48.146 'cause now you get to see exactly why your role 10:48.146 --> 10:50.555 in launching these capabilities into space 10:50.555 --> 10:53.731 so our warfighters have those capabilities at their 10:53.731 --> 10:54.919 fingertips that are so important. 10:54.919 --> 10:56.710 Thanks for being here. 10:56.710 --> 10:58.960 (applause) 11:02.999 --> 11:05.126 - Chief, thank you so much for letting me speak 11:05.126 --> 11:07.436 here with this august command group 11:07.436 --> 11:08.702 that I'm sitting with. 11:08.702 --> 11:10.161 AFA General Spencer, 11:10.161 --> 11:11.301 thank you so much. 11:11.301 --> 11:12.134 I gotta say, 11:12.134 --> 11:13.936 I, too, really scratch my head 11:13.936 --> 11:17.220 as to why I was asked to be on this panel. 11:17.220 --> 11:18.959 And I thought, perhaps, 11:18.959 --> 11:21.042 it's because at the time, 11:21.317 --> 11:24.006 Lieutenant Colonel Mo Calabrese and I wrote a paper 11:24.006 --> 11:27.006 and it was titled, "Fusion Warfare," 11:28.748 --> 11:31.137 and I wanna just take a couple seconds 11:31.137 --> 11:32.637 to talk about that 11:32.802 --> 11:34.950 and how did we come up with the title 11:34.950 --> 11:37.783 and the concept of Fusion Warfare. 11:37.992 --> 11:40.258 And I can look at you all and say, 11:40.258 --> 11:41.258 "We didn't." 11:42.655 --> 11:44.072 I went to Nellis, 11:44.194 --> 11:47.642 and talked to about 60 ISR professional airmen, 11:47.642 --> 11:51.392 from Senior Airmen up to Lieutenant Colonels. 11:52.492 --> 11:55.104 And we talked about 5th Generation. 11:55.104 --> 11:59.271 And the capabilities of networks and system of systems. 12:00.038 --> 12:02.559 And I kept callin' it 5th Generation. 12:02.559 --> 12:06.053 And after about three hours and we took a couple breaks, 12:06.053 --> 12:08.201 couple airmen came up to me and said, 12:08.201 --> 12:10.837 "Ma'am, with all due respect, what was 12:10.837 --> 12:13.794 "First, Second, and Third Generation? 12:13.794 --> 12:15.447 "'Cause we know what Fourth Generation is. 12:15.447 --> 12:17.320 "You all talk about it. 12:17.320 --> 12:19.218 "And I get where you're goin' with Fifth Gen. 12:19.218 --> 12:23.257 "But when we're colonels, it'll be Seventh and Eighth Gen, 12:23.257 --> 12:26.257 "and Fifth Gen won't mean anything." 12:26.285 --> 12:28.185 And I said, "You guys are brilliant 12:28.185 --> 12:30.059 "as airmen always are," 12:30.059 --> 12:31.220 So we took a break. 12:31.220 --> 12:33.026 When we came back the next day, 12:33.026 --> 12:36.224 and there was a very brave Major Tabby Turner, 12:36.224 --> 12:38.701 Air Force Reserve on active duty. 12:38.701 --> 12:40.626 She said, "Ma'am, we all huddled last night, 12:40.626 --> 12:42.157 "and drank some beers after you left 12:42.157 --> 12:43.876 "when we could really think." 12:43.876 --> 12:44.709 Of course. 12:45.382 --> 12:48.044 And she said, "What do you think about the concept 12:48.044 --> 12:49.961 "called Fusion Warfare? 12:50.045 --> 12:53.128 "Because we believe it is truly about 12:53.542 --> 12:57.375 "the integration of data to decision UDU loops 12:57.912 --> 13:01.162 "across multiple domains at laser speed 13:03.442 --> 13:06.696 "in exacting lethality against our adversaries 13:06.696 --> 13:09.499 "at a time and place of our choosing." 13:09.499 --> 13:10.416 And I said, 13:10.471 --> 13:13.270 "That is exactly why I am proud to be an airman 13:13.270 --> 13:16.045 "because not only do you take the complex 13:16.045 --> 13:19.912 "and difficult, think about it, make it simple; 13:19.912 --> 13:23.079 "you are going to change the Air Force 13:23.454 --> 13:25.454 "and the way it thinks." 13:25.454 --> 13:28.037 And it's about multiple domains 13:28.160 --> 13:29.414 and multiple capabilities, 13:29.414 --> 13:33.331 and they don't think anything but Space, Cyber, 13:34.642 --> 13:36.142 Strike, Air, Lift. 13:36.723 --> 13:39.759 They think about all those capabilities. 13:39.759 --> 13:41.141 They're just brilliant. 13:41.141 --> 13:44.065 So I'm looking forward to the questions that come. 13:44.065 --> 13:46.623 One of the things I'll end with is 13:46.623 --> 13:49.123 when I looked at Global Reach, 13:49.332 --> 13:51.842 I didn't have to go too far to get a fantastic 13:51.842 --> 13:53.425 vignette of airmen. 13:53.958 --> 13:58.125 The 621st Airmen that is a Contingency Response Wing 14:00.248 --> 14:03.559 called in to assist the Iraqi Special Forces, 14:03.559 --> 14:07.726 Security Forces in opening up Qayyarah West Airfield 14:08.456 --> 14:10.789 prior to the fight in Mosul. 14:10.858 --> 14:13.701 And their team deployed forward and they are 14:13.701 --> 14:17.396 what I call the forward node of Fusion Warfare 14:17.396 --> 14:20.519 going into a bare base with no information, 14:20.519 --> 14:22.436 no cop, no information. 14:22.777 --> 14:24.860 They provided everything, 14:25.221 --> 14:27.345 not just to the Iraqi's but to our combat 14:27.345 --> 14:31.512 Air Forces, our Mobility Forces, and everyone else. 14:32.282 --> 14:34.904 Every airman is a part of Fusion Warfare, 14:34.904 --> 14:37.451 and I look forward to advancing it, 14:37.451 --> 14:40.149 and maintaining not just the tactical edge, 14:40.149 --> 14:42.995 but operational insights and the strategic 14:42.995 --> 14:44.792 advantage that it will bring. 14:44.792 --> 14:45.625 Thank you. 14:48.200 --> 14:49.617 - Good afternoon. 14:50.007 --> 14:52.073 AFA, thank you so much for having FedEx 14:52.073 --> 14:53.241 participate today. 14:53.241 --> 14:54.328 I'm honored to be here, 14:54.328 --> 14:56.137 and Chief, I enjoyed the remarks very much. 14:56.137 --> 14:58.054 Fascinating discussion. 14:58.186 --> 14:59.682 Thank you for that. 14:59.682 --> 15:02.077 Let me introduce FedEx to ya real quick 15:02.077 --> 15:04.222 before we go any further and may be 15:04.222 --> 15:06.673 wondering why FedEx is on the panel. 15:06.673 --> 15:09.814 We take many of the concepts of fusion 15:09.814 --> 15:11.656 and put it in the commercial side, 15:11.656 --> 15:13.135 on the industry side. 15:13.135 --> 15:14.626 Those of you may not know, 15:14.626 --> 15:17.128 FedEx is been around for 43 years. 15:17.128 --> 15:19.114 We were founded in Memphis, Tennessee. 15:19.114 --> 15:22.927 About 35,000 individuals in Memphis work for FedEx. 15:22.927 --> 15:25.831 And we have over 400,000 team members around the globe. 15:25.831 --> 15:27.748 We're in 220 countries, 15:28.064 --> 15:30.231 and we pick up and deliver 15:30.714 --> 15:32.683 about 12 million shipments a year. 15:32.683 --> 15:33.657 In terms of cyber, 15:33.657 --> 15:36.329 we have about 50 million inquiries 15:36.329 --> 15:39.496 into our IT systems daily from outside 15:40.355 --> 15:41.688 about shipments. 15:41.949 --> 15:45.652 We operate more than 650 aircraft around the globe 15:45.652 --> 15:46.985 at 375 airports. 15:47.846 --> 15:50.556 We have more than 150,000 ground vehicles 15:50.556 --> 15:52.723 deployed around the world, 15:53.120 --> 15:55.803 and we have to take these concepts of fusion 15:55.803 --> 15:58.932 and command and control into our business as well. 15:58.932 --> 16:01.971 Our business was built on reliability. 16:01.971 --> 16:03.886 People come to expect that from FedEx and 16:03.886 --> 16:08.053 we ship for both individual, commercial, and military 16:08.590 --> 16:11.895 as well, so it matters that we have a functioning, 16:11.895 --> 16:14.432 well-oiled command and control system 16:14.432 --> 16:16.784 that operates in a global environment. 16:16.784 --> 16:18.744 We have a very centralized command and control 16:18.744 --> 16:20.429 system in Memphis, but we push down 16:20.429 --> 16:22.270 that operations authority down to the lowest 16:22.270 --> 16:25.695 possible level on decision making in the local 16:25.695 --> 16:29.563 and regional perspective to allow us to react to 16:29.563 --> 16:31.955 those activities that would take place. 16:31.955 --> 16:35.205 Many, many opportunities during the day 16:35.356 --> 16:39.356 as we operate around the globe for our adjusting 16:39.575 --> 16:41.305 our network and making sure that we can deliver 16:41.305 --> 16:43.293 on that promise, whether it be military equipment 16:43.293 --> 16:45.906 we're carrying on our airplanes or heart valves. 16:45.906 --> 16:49.615 So we have studied fusion and how to take all 16:49.615 --> 16:52.942 that information into our control center so that 16:52.942 --> 16:56.442 we can manage opportunity when opportunity 16:56.532 --> 16:58.474 presents itself to make those rapid 16:58.474 --> 17:00.369 and reliable decisions so that we can 17:00.369 --> 17:02.373 again deliver on that commitment. 17:02.373 --> 17:04.061 So I'm honored to be here and look forward 17:04.061 --> 17:05.052 to the questions. 17:05.052 --> 17:05.885 Thank you. 17:07.701 --> 17:08.534 - All right. 17:08.534 --> 17:09.367 Thank you. 17:09.370 --> 17:10.203 Good afternoon, everyone. 17:10.203 --> 17:12.656 Mark Valentine from Microsoft Corporation. 17:12.656 --> 17:14.077 You probably heard of us. 17:14.077 --> 17:16.457 Little tech company out in the West. 17:16.457 --> 17:17.616 And if you take nothing else 17:17.616 --> 17:19.162 away from this conversation today, 17:19.162 --> 17:20.435 please understand that we do more than 17:20.435 --> 17:21.978 Office and Windows. 17:21.978 --> 17:25.590 I have no idea how I got invited to this panel either. 17:25.590 --> 17:28.598 General Deptula and General Goldfein, 17:28.598 --> 17:30.073 thank you for the opportunity. 17:30.073 --> 17:32.486 And I want to reiterate something the Chief said 17:32.486 --> 17:33.607 during his discussion. 17:33.607 --> 17:34.524 And that is 17:34.798 --> 17:36.553 the United States Air Force, 17:36.553 --> 17:37.920 and I still use the pronoun "we," 17:37.920 --> 17:39.431 so apologize me if I do that. 17:39.431 --> 17:42.067 We do not have a problem with data. 17:42.067 --> 17:43.984 We have plenty of data. 17:44.684 --> 17:46.851 What we lack are insights. 17:47.005 --> 17:48.255 So to that end, 17:48.668 --> 17:50.456 and ma'am, I understand that the name 17:50.456 --> 17:53.344 "Fusion Warfare" was created on a bar napkin at Nellis, 17:53.344 --> 17:55.784 and I have a lot of those to my credit as well, 17:55.784 --> 17:57.951 but I don't like the term. 17:58.803 --> 18:00.451 And it's not that it's a horrible term, 18:00.451 --> 18:02.485 but I think when we say Fusion Warfare, 18:02.485 --> 18:05.958 it makes us think that it's somehow different. 18:05.958 --> 18:09.180 And that it somehow changes the principles of war, 18:09.180 --> 18:10.972 which I do not think that it does. 18:10.972 --> 18:12.775 Just as General Haiden says that there 18:12.775 --> 18:14.705 is no war in space; there's just war. 18:14.705 --> 18:16.899 I think the same thing when we start talking 18:16.899 --> 18:18.142 about this environment. 18:18.142 --> 18:20.195 But more importantly, when we say Fusion Warfare, 18:20.195 --> 18:24.195 I think it limits our understanding of the types 18:24.207 --> 18:27.352 of sensors that we could use in this network. 18:27.352 --> 18:29.580 So therefore, I prefer the term 18:29.580 --> 18:32.700 an Internet of Combat Things, if you will, 18:32.700 --> 18:35.232 or I guess to state it even more clearly, 18:35.232 --> 18:39.399 it's using the insights created from networks of things 18:39.623 --> 18:42.040 to accomplish combat effects. 18:42.195 --> 18:44.277 So I wanna ask a question of the audience. 18:44.277 --> 18:47.928 Has anyone in here heard of an individual named 18:47.928 --> 18:50.497 Roy Uemera, and if you were at the Cyberspace Symposium 18:50.497 --> 18:52.298 a couple weeks ago, you can't answer 18:52.298 --> 18:54.191 because I introduced him there. 18:54.191 --> 18:55.024 All right. 18:55.092 --> 18:58.425 Dr. Roy Uemera is a Ph.D. from Stanford. 18:58.661 --> 19:00.285 He was one of the first people 19:00.285 --> 19:02.119 to carry the term, futurist, 19:02.119 --> 19:03.724 which I know sounds crazy now 19:03.724 --> 19:05.185 'cause everyone on the Internet and Twitter 19:05.185 --> 19:06.798 says they're a futurist and a technologist, 19:06.798 --> 19:08.504 but this individual really was. 19:08.504 --> 19:09.683 And he's no longer with us, 19:09.683 --> 19:11.591 but he created a statement 19:11.591 --> 19:13.282 which has turned into kind of a law 19:13.282 --> 19:14.723 to tech geeks around the world. 19:14.723 --> 19:16.238 And it's called Uemera's Law. 19:16.238 --> 19:17.368 And very simply, 19:17.368 --> 19:20.119 it states that we tend to overestimate 19:20.119 --> 19:22.506 the effect of a technology in the short run, 19:22.506 --> 19:25.589 but underestimate it in the long run. 19:26.265 --> 19:27.848 So if that is true, 19:28.780 --> 19:30.047 and we take it at face value, 19:30.047 --> 19:32.624 maybe this whole Fusion Warfare thing 19:32.624 --> 19:33.580 we're talking about, 19:33.580 --> 19:35.701 or Combat Cloud or Internet of Combat Things, 19:35.701 --> 19:37.951 maybe we're over-hyping it. 19:41.002 --> 19:42.919 But when was Time Zero? 19:44.891 --> 19:46.600 I just read last night, 19:46.600 --> 19:48.543 just doin' a quick search on the Internet, 19:48.543 --> 19:50.710 I found a report from 2001 19:50.900 --> 19:53.629 written from the Department of Defense to Congress. 19:53.629 --> 19:56.399 And it was entitled, "Net-Centric Warfare." 19:56.399 --> 19:58.232 That was 16 years ago. 19:59.708 --> 20:01.343 If you actually look at the footnotes, 20:01.343 --> 20:03.418 and I encourage you to look at footnotes these days, 20:03.418 --> 20:05.772 you will find the primary source information 20:05.772 --> 20:09.355 in that document mostly comes from the 80s. 20:11.187 --> 20:15.354 So we've been talking about this for 30 years, at least. 20:16.004 --> 20:16.920 And I'm willing to bet, 20:16.920 --> 20:18.606 someone can go out and find a Sun Tzu reference 20:18.606 --> 20:21.576 where even Sun Tzu talked about Fusion Warfare. 20:21.576 --> 20:23.987 So we've been talkin' about it for a long time. 20:23.987 --> 20:26.966 And notwithstanding some of great videos we saw 20:26.966 --> 20:28.826 that the Chief put together and some of the 20:28.826 --> 20:30.958 outstanding things that I got to see as an airman, 20:30.958 --> 20:32.377 and the airmen are still doing, 20:32.377 --> 20:35.627 we haven't done that much in this area. 20:35.680 --> 20:38.347 And I hope that General Deptula, 20:38.634 --> 20:41.532 we get to the why during the rest of the questions. 20:41.532 --> 20:43.532 So thanks for your time. 20:44.281 --> 20:47.093 - Well, thanks very much, lady and gentlemen. 20:47.093 --> 20:50.819 We'll now get on to hear what's on the audience's mind. 20:50.819 --> 20:53.158 First question, General Rand. 20:53.158 --> 20:56.753 Given that Fusion Warfare and the Combat Cloud 20:56.753 --> 20:59.166 will involve more than kinetic strike, 20:59.166 --> 21:00.834 how do you envision integrating 21:00.834 --> 21:03.698 offensive cyber operations with aircraft 21:03.698 --> 21:06.865 conducting long range strike missions? 21:09.726 --> 21:11.540 - I think the best way to answer that 21:11.540 --> 21:15.623 is that, um, I think the ability to be on station 21:16.390 --> 21:18.246 with the bombers for a long time, 21:18.246 --> 21:22.164 it gives us the ability to do a lot of ISR kind of work. 21:22.164 --> 21:24.718 And that's what's so critical now 21:24.718 --> 21:28.513 with the new radar we're gonna get in the B-52, 21:28.513 --> 21:30.372 the advanced targeting pod. 21:30.372 --> 21:32.329 The ability to collect that information 21:32.329 --> 21:35.638 and then pass it either to other airborne platforms 21:35.638 --> 21:38.393 or back to ground forces or wherever we need 21:38.393 --> 21:39.855 to get it, and I think that's the 21:39.855 --> 21:41.688 hugely positive thing. 21:43.227 --> 21:45.345 I tell our guys already as they're 21:45.345 --> 21:46.883 preparin' to go down range, 21:46.883 --> 21:48.430 I said, you know, frankly, 21:48.430 --> 21:50.552 the least important thing you might do 21:50.552 --> 21:51.802 is drop a bomb. 21:53.377 --> 21:54.961 The most important thing you might do 21:54.961 --> 21:56.961 is provide a critical piece of ISR 21:56.961 --> 21:59.654 that's gonna save someone's life. 21:59.654 --> 22:00.611 - Very good. 22:00.611 --> 22:03.542 It's back to that sensor-shooter thing. 22:03.542 --> 22:06.709 General Everhart, what is AMC doing to 22:07.039 --> 22:09.472 ensure Mobility Platforms can survive 22:09.472 --> 22:11.389 in contested air space, 22:11.957 --> 22:14.755 and integrate with Fifth Generation fighters and bombers 22:14.755 --> 22:17.255 in a Combat Cloud environment? 22:19.155 --> 22:21.202 - I've got the team right now takin' a look 22:21.202 --> 22:23.313 at a whole host of things. 22:23.313 --> 22:24.887 First of all, gotta be able to communicate 22:24.887 --> 22:27.893 when that aircraft needs to communicate back to us. 22:27.893 --> 22:29.680 Then what do I do with that data? 22:29.680 --> 22:31.742 What do I do with that communication? 22:31.742 --> 22:33.679 Oftentimes, I talk to folks and I say, 22:33.679 --> 22:35.767 you know, I've got a persistent platform 22:35.767 --> 22:37.566 that's out there that's got to be able 22:37.566 --> 22:38.899 to deliver fuel. 22:39.401 --> 22:43.568 So while it's in this pattern while the F-35 or the F-22 22:43.720 --> 22:47.017 or the B-1, B-2, the B-21, that's gonna go 22:47.017 --> 22:48.989 and service its target, while we're out there 22:48.989 --> 22:51.322 what is that platform doing? 22:51.979 --> 22:53.813 So what are the systems that I can put onboard 22:53.813 --> 22:56.116 to either gather that data up, 22:56.116 --> 22:59.949 or off-board that data back to the satellites, 23:00.550 --> 23:02.684 back to the National Command Authorities 23:02.684 --> 23:05.184 where they have decision space 23:05.524 --> 23:07.991 in a rapid changing environment? 23:07.991 --> 23:10.158 So using the F-35 example. 23:10.409 --> 23:12.492 F-35 services the target. 23:12.601 --> 23:14.692 Its cache is full of data. 23:14.692 --> 23:16.316 It's just not only data, 23:16.316 --> 23:17.915 but what you do with it. 23:17.915 --> 23:19.294 It comes up to the platform 23:19.294 --> 23:20.627 called a tanker. 23:20.642 --> 23:22.424 The tanker takes that data. 23:22.424 --> 23:23.943 Unbeknownst to anyone in the cockpit. 23:23.943 --> 23:25.854 Unbeknownst to the pilot in the F-35. 23:25.854 --> 23:27.788 It off-boards, frees up the cache, 23:27.788 --> 23:30.455 so now you can re-load it again, 23:30.707 --> 23:32.412 so that can be another decision-making, 23:32.412 --> 23:34.783 just a little bit down the line. 23:34.783 --> 23:35.786 They get their gas. 23:35.786 --> 23:36.697 They service the gas. 23:36.697 --> 23:37.954 That data gets off-boarded. 23:37.954 --> 23:39.538 And unbeknownst to anybody it's done 23:39.538 --> 23:41.558 back to command authorities where it needs to be, 23:41.558 --> 23:43.471 or back to the pilot in the F-35 so he can 23:43.471 --> 23:45.362 make decisions as that example 23:45.362 --> 23:49.529 as General Goldfein gave us in that fight tonight. 23:49.616 --> 23:52.162 That's hugely, hugely important. 23:52.162 --> 23:55.503 We're working toward an agile combat, or a 23:55.503 --> 23:57.902 agile command and control network 23:57.902 --> 23:59.135 because I will tell you right now 23:59.135 --> 24:01.363 that also the ATOs we produce 24:01.363 --> 24:03.824 is not gonna survive the first contact. 24:03.824 --> 24:05.516 So how do you get that data? 24:05.516 --> 24:07.241 How do you fuse that data 24:07.241 --> 24:08.794 to get what's the next set of orders 24:08.794 --> 24:10.026 that are comin' to ya to survive? 24:10.026 --> 24:12.910 What's that next set of orders is comin' to ya 24:12.910 --> 24:15.967 to service the next target to defeat the enemy, 24:15.967 --> 24:18.235 to get inside their UDU loop. 24:18.235 --> 24:20.321 So those are the things that we're looking at right now. 24:20.321 --> 24:23.863 We've got, I've got 1164 airplanes out there. 24:23.863 --> 24:26.336 And they could all being used at one time. 24:26.336 --> 24:29.336 Why not use them as relay platforms? 24:29.602 --> 24:30.946 I can use conformal antennas. 24:30.946 --> 24:32.684 I can use other method; 24:32.684 --> 24:34.193 they can still do their mission. 24:34.193 --> 24:35.545 But if it's a Mobility, 24:35.545 --> 24:37.642 if it's a C-17 collecting data 24:37.642 --> 24:40.936 just like an F-35 does when it goes to remote airfield, 24:40.936 --> 24:43.394 and oh by the way, it was picking up radar signatures 24:43.394 --> 24:45.781 on the way, I can relay that out to tell 24:45.781 --> 24:46.952 my friends up top, 24:46.952 --> 24:49.952 "Hey, go kill that so I come in another day." 24:49.952 --> 24:51.090 That is hugely important. 24:51.090 --> 24:52.348 That is part of this fusion. 24:52.348 --> 24:53.934 That is part of this integration that's 24:53.934 --> 24:56.246 gonna make us really get after this thing, I believe. 24:56.246 --> 24:57.746 So thank you, sir. 24:58.165 --> 24:59.159 - Thanks very much for that answer. 24:59.159 --> 25:01.742 If I may, it's viewing aircraft 25:03.654 --> 25:06.154 not just as individual pieces, 25:06.711 --> 25:10.711 but as data nodes inside a much large ISR strike 25:12.616 --> 25:14.597 maneuver sustainment complex. 25:14.597 --> 25:15.680 - Absolutely. 25:15.864 --> 25:16.754 - Very good. 25:16.754 --> 25:17.697 General Raymond. 25:17.697 --> 25:18.954 The notion of fully integrated warfare 25:18.954 --> 25:22.246 as envisioned by establishing a Combat Cloud 25:22.246 --> 25:24.958 will be highly dependent on the capabilities 25:24.958 --> 25:27.348 provided by our space assets. 25:27.348 --> 25:29.073 What is Space Command doing 25:29.073 --> 25:32.921 to insure the resilience, redundancy, and robustness 25:32.921 --> 25:34.971 of our space architecture? 25:34.971 --> 25:35.946 - That's a great question. 25:35.946 --> 25:36.779 Thank you. 25:36.892 --> 25:37.797 We're doing a lot. 25:37.797 --> 25:38.728 First of all, 25:38.728 --> 25:40.720 it starts with the concept of operations, 25:40.720 --> 25:42.562 so we've developed a Joint Warfighting Con-ops 25:42.562 --> 25:45.298 in partnership with the National Reconnaissance Office 25:45.298 --> 25:47.381 to drive at exactly that. 25:48.221 --> 25:51.698 How do you go about switching from a relatively 25:51.698 --> 25:53.170 benign domain to being able 25:53.170 --> 25:55.870 to operate in a contested warfaring domain 25:55.870 --> 25:58.875 just like the other domains that we operate in? 25:58.875 --> 26:01.446 Foundational to being able to operate 26:01.446 --> 26:03.537 in any operational domain, 26:03.537 --> 26:04.968 you have to have two must have's. 26:04.968 --> 26:06.875 You have to have the ability to command and control 26:06.875 --> 26:08.841 in that domain, and you have to have the ability 26:08.841 --> 26:10.920 to have situational awareness in that domain. 26:10.920 --> 26:12.912 And so we're working very hard on developing 26:12.912 --> 26:15.212 a battle management command and control capability, 26:15.212 --> 26:17.246 and as the Chief said earlier in his remarks, 26:17.246 --> 26:18.891 that isn't us alone, 26:18.891 --> 26:21.058 that's us all in this room 26:22.129 --> 26:25.171 in getting the best out of industry to help us 26:25.171 --> 26:26.254 achieve that. 26:26.883 --> 26:30.496 On the space situational awareness business, 26:30.496 --> 26:32.706 largely the way we've done that business in the past 26:32.706 --> 26:34.829 has been focused on having a catalog in space. 26:34.829 --> 26:36.483 In a benign environment, 26:36.483 --> 26:40.568 knowing where something is in space is good enough. 26:40.568 --> 26:42.044 In a contested environment, 26:42.044 --> 26:43.578 it falls woefully short, 26:43.578 --> 26:46.250 so we're evolving our SSA capabilities 26:46.250 --> 26:49.929 to be able to have more than just a location in space. 26:49.929 --> 26:52.140 We're working our architectures in doing 26:52.140 --> 26:53.866 the analysis to determine what 26:53.866 --> 26:55.041 kind of architectures you have to have 26:55.041 --> 26:56.914 to have a space architecture that again is 26:56.914 --> 26:58.997 resilient and defendable. 26:59.292 --> 27:02.025 We've overhauled our training programs. 27:02.025 --> 27:04.172 We've come up with what's called 27:04.172 --> 27:05.450 the Space Mission Force, 27:05.450 --> 27:06.536 which allows our operators 27:06.536 --> 27:08.472 rather than to just do basic levels of training, 27:08.472 --> 27:09.777 but allows our operators 27:09.777 --> 27:11.310 to do the advanced training again 27:11.310 --> 27:14.007 needed to operate in this domain. 27:14.007 --> 27:15.864 And then, finally, we're working very hard 27:15.864 --> 27:17.885 in developing the tactics, techniques, 27:17.885 --> 27:19.694 and procedures that are required to be able 27:19.694 --> 27:21.020 to operate in this domain. 27:21.020 --> 27:22.755 So I'm really excited about the work that's going on. 27:22.755 --> 27:25.072 We are completely shifting the focus of our 27:25.072 --> 27:27.652 command both in Space and in Cyber 27:27.652 --> 27:30.819 to a warfighting command in developing 27:31.556 --> 27:33.472 the Joint Warfighters we need to be able to operate 27:33.472 --> 27:35.992 in these, in both of these domains. 27:35.992 --> 27:36.825 Thank you. 27:37.634 --> 27:38.634 - Very good. 27:38.920 --> 27:42.236 General Jameison, in the Mitchell Institute Fusion Warfare 27:42.236 --> 27:45.873 paper that you authored, it calls for the integration 27:45.873 --> 27:49.181 of multiple UDU loops across multiple command 27:49.181 --> 27:51.622 and control nodes and domains. 27:51.622 --> 27:53.307 Where does the priority need to be 27:53.307 --> 27:56.307 for moving this integration forward? 27:58.625 --> 27:59.458 - Thank you. 27:59.458 --> 28:01.107 That's a great question. 28:01.107 --> 28:03.774 And I'll start out by describing 28:04.488 --> 28:07.321 for Mr. Valentine how I do believe 28:08.339 --> 28:10.696 that you're absolutely right. 28:10.696 --> 28:13.417 The nature of warfare is not changing, 28:13.417 --> 28:14.653 and it doesn't change. 28:14.653 --> 28:17.570 However, Fusion Warfare and the why 28:17.916 --> 28:20.249 of multiple UDU loops across 28:20.344 --> 28:23.414 multiple domains to affect decision=making 28:23.414 --> 28:25.077 to create the desired effects at a 28:25.077 --> 28:27.577 time and place of our choosing 28:28.027 --> 28:30.115 while the adversary if fumbling because 28:30.115 --> 28:33.161 he cannot match the speed and the exacting 28:33.161 --> 28:36.078 lethality is because we are talking 28:36.995 --> 28:40.662 about the advancing of the character of war, 28:41.229 --> 28:44.396 and those multiple UDU loops are a way 28:45.578 --> 28:48.911 from Dr. Boyd's paper on decision-making 28:50.069 --> 28:52.937 on how do we think through our problems 28:52.937 --> 28:57.020 and how do we take complexities and simplify them 28:57.164 --> 29:00.599 so that we actually understand what is our 29:00.599 --> 29:02.897 in-state that we're driving through. 29:02.897 --> 29:05.217 What technology has given us is the means to 29:05.217 --> 29:08.550 integrate the multi-domain capabilities. 29:09.596 --> 29:11.954 What our airmen have given us through 29:11.954 --> 29:15.372 critical thinking is the advancement and speed 29:15.372 --> 29:17.371 of decision making from the data passed through, by, 29:17.371 --> 29:21.204 and which all of those domains to every single 29:22.687 --> 29:26.104 capability in the United States Air Force 29:26.577 --> 29:29.827 and in the Joint Warfighting community. 29:29.881 --> 29:33.243 When General Everhart talks about his Airlift, 29:33.243 --> 29:36.274 his tankers, there's not a single operational 29:36.274 --> 29:39.842 mission today that does not rely on those assets. 29:39.842 --> 29:43.259 The power harnessed from the capabilities 29:44.026 --> 29:47.943 that they can ingest by feeding those insights, 29:47.991 --> 29:51.908 live and in real time, to our B-2 strike assets 29:52.255 --> 29:53.505 are incredible. 29:53.867 --> 29:55.760 When we look at how is that done, 29:55.760 --> 29:57.482 as General Raymond talked about, 29:57.482 --> 29:59.643 it's through our Space Enterprise that we're 29:59.643 --> 30:00.976 able to do that. 30:01.261 --> 30:04.042 As I recall from that centric papers, 30:04.042 --> 30:06.088 because I did research those 30:06.088 --> 30:07.564 when we wrote our paper, 30:07.564 --> 30:08.966 it was a little more about 30:08.966 --> 30:11.549 individual stove pipes passing. 30:12.164 --> 30:13.873 It was not about a synthesized 30:13.873 --> 30:17.693 collaborative environment that is evolving into 30:17.693 --> 30:19.800 a contested or in a contested environment. 30:19.800 --> 30:23.133 So, sir, that's how I believe we address 30:23.358 --> 30:26.358 the multiple UDU loops, multi-domain 30:26.695 --> 30:28.445 in where we're going. 30:28.526 --> 30:30.443 This is really thought. 30:31.013 --> 30:32.655 It's thought provoking. 30:32.655 --> 30:34.838 It's how do we take what we have today 30:34.838 --> 30:38.588 and advance at a speed of which our adversary 30:40.181 --> 30:41.264 cannot match. 30:41.722 --> 30:43.677 Not because they don't have technology. 30:43.677 --> 30:45.925 They probably will be at parity with us 30:45.925 --> 30:48.592 or even exceed us in many areas. 30:48.773 --> 30:50.866 But it is about the innovation, 30:50.866 --> 30:52.683 as General Raymond talked about. 30:52.683 --> 30:55.784 It's about our tactics, techniques, and procedures, 30:55.784 --> 30:58.284 not just at the tactical edge, 30:58.768 --> 31:01.765 but concentrated throughout our multi-domain 31:01.765 --> 31:05.104 command centers giving us operational insights 31:05.104 --> 31:08.072 and giving us, then, strategic advantage. 31:08.072 --> 31:09.739 - Thanks, very much. 31:10.063 --> 31:13.813 In other words, this is really much more than 31:15.240 --> 31:16.635 just net-centric warfare. 31:16.635 --> 31:19.343 This is a complete paradigm shift in the way 31:19.343 --> 31:23.121 we think about integration of what used to be, 31:23.121 --> 31:25.371 and to a degree, still are, 31:25.601 --> 31:27.127 a variety of stove pipes, 31:27.127 --> 31:29.269 but integrating all the parts and pieces 31:29.269 --> 31:33.436 to ubiquitously share seamlessly information across 31:33.917 --> 31:35.084 all the parts. 31:35.178 --> 31:36.011 Okay. 31:36.282 --> 31:37.282 Mr. Tronser. 31:38.420 --> 31:41.365 The founder and Chairman of FedEx, Fred Smith, 31:41.365 --> 31:42.948 is a former Marine. 31:42.949 --> 31:45.414 And many of your command and control concepts mirror 31:45.414 --> 31:47.356 those of the Armed Forces. 31:47.356 --> 31:49.156 Could you talk a little bit 31:49.156 --> 31:51.142 about how you deal with the uncertainty 31:51.142 --> 31:53.055 that you experience in your network? 31:53.055 --> 31:53.888 - Sure. 31:53.888 --> 31:54.721 Thanks very much. 31:54.721 --> 31:55.554 Great question. 31:55.554 --> 31:58.719 So I mentioned breadth and scope of FedEx 31:58.719 --> 31:59.886 a bit earlier. 31:59.886 --> 32:03.103 The fact that there's not a minute that goes by 32:03.103 --> 32:05.597 of any day of the year that there's not a FedEx jet 32:05.597 --> 32:06.612 in the sky somewhere. 32:06.612 --> 32:08.439 And we're faced with the uncertainty. 32:08.439 --> 32:10.558 Now, certainly, ours is on the commercial side 32:10.558 --> 32:14.391 and it matters not what the cargo is we carry. 32:14.583 --> 32:18.127 Our mission is to complete every one of those missions. 32:18.127 --> 32:19.475 So in the environment, 32:19.475 --> 32:21.092 in the global environment in which we operate, 32:21.092 --> 32:22.591 we face many of the same things 32:22.591 --> 32:26.070 that the Air Force faces in terms of impediments, 32:26.070 --> 32:28.086 whether it be weather or civil disruption 32:28.086 --> 32:30.081 or even military disruption, 32:30.081 --> 32:32.498 so the challenge for Express, 32:32.891 --> 32:35.027 uh, for FedEx is to integrate 32:35.027 --> 32:37.944 those information channels into our 32:37.983 --> 32:39.348 present control centers. 32:39.348 --> 32:41.625 By the way we have five different commands 32:41.625 --> 32:44.498 around the globe that roll up to a global 32:44.498 --> 32:45.888 operations control center in Memphis that I head. 32:45.888 --> 32:48.517 We have European command, looks over 32:48.517 --> 32:49.815 the European network. 32:49.815 --> 32:51.533 We have a Asia-Pacific command that works 32:51.533 --> 32:55.450 over the Asia flying and inter-European flying. 32:56.043 --> 32:57.582 We do a Middle East and we have Latin America. 32:57.582 --> 33:01.166 And those roll back up to the global operations 33:01.166 --> 33:03.318 control center, and our challenge really 33:03.318 --> 33:06.392 is to integrate the information that comes in 33:06.392 --> 33:09.291 and then, and we've talked about it a fair amount. 33:09.291 --> 33:12.240 What do you do with the information that comes in? 33:12.240 --> 33:14.115 Our command structure is set up for 33:14.115 --> 33:15.828 rapid decision making. 33:15.828 --> 33:19.078 Our aircraft probably don't fly as fast 33:19.776 --> 33:21.411 as Air Force aircraft. 33:21.411 --> 33:23.303 We're in the 500 miles per hour range. 33:23.303 --> 33:26.188 But you do need to make decisions rather rapidly 33:26.188 --> 33:27.855 in that environment. 33:28.013 --> 33:31.014 And so what we've learned in our 43 years of history 33:31.014 --> 33:32.013 is that you need to have, 33:32.013 --> 33:34.408 as the Chief pointed out earlier, 33:34.408 --> 33:36.241 one person in command. 33:36.247 --> 33:38.340 And our command structure's based on that. 33:38.340 --> 33:40.499 But we also push down that command authority 33:40.499 --> 33:41.717 I mentioned earlier, 33:41.717 --> 33:42.837 down to the lowest level possible 33:42.837 --> 33:44.170 down to the regional 33:44.170 --> 33:45.706 and the local level to allow 33:45.706 --> 33:46.902 for decision makers. 33:46.902 --> 33:49.993 So it's that uncertainty that the global 33:49.993 --> 33:52.414 environment introduces to us that we struggle with 33:52.414 --> 33:54.272 and that we have to maintain this firm 33:54.272 --> 33:55.617 command and control. 33:55.617 --> 33:58.034 We're available in our operations center 24/7, 33:58.034 --> 33:59.867 and our team is there. 34:00.578 --> 34:02.411 The strength of FedEx, 34:02.815 --> 34:04.005 very much like the Air Force 34:04.005 --> 34:04.838 is in our, 34:04.838 --> 34:06.026 the power of our people, 34:06.026 --> 34:08.193 and we train, train, train our team 34:08.193 --> 34:10.286 to be rapid decision makers 34:10.286 --> 34:11.958 and be able to communicate as well 34:11.958 --> 34:13.977 because in a command and control environment, 34:13.977 --> 34:16.283 communication, we think, is key. 34:16.283 --> 34:17.866 - Thanks very much. 34:17.898 --> 34:19.731 Drifter, you're lucky. 34:20.514 --> 34:22.333 This is the last question. 34:22.333 --> 34:24.333 In your opening remarks, 34:24.502 --> 34:26.678 you mentioned how long we've been theorizing 34:26.678 --> 34:30.178 about Fusion Warfare with limited results. 34:30.239 --> 34:33.148 You also mentioned that the supporting technology's 34:33.148 --> 34:36.481 available, but we've been slow to adopt. 34:37.101 --> 34:39.479 Could you expand a little bit on why? 34:39.479 --> 34:40.979 - Roger that, sir. 34:41.757 --> 34:45.590 I've been thinkin' about this for a long time. 34:46.687 --> 34:48.603 I just made the jump over to the private sector 34:48.603 --> 34:49.693 not too long ago, 34:49.693 --> 34:52.485 and there's a mismatch between how we used technology 34:52.485 --> 34:54.265 when I was in the Air Force 34:54.265 --> 34:57.074 and how I watch technology being used today. 34:57.074 --> 34:58.775 And there are a couple of things, 34:58.775 --> 35:00.615 but I'll just focus on one, 35:00.615 --> 35:01.591 General Deptula. 35:01.591 --> 35:02.508 And that's, 35:03.005 --> 35:04.836 I see that there's a fundamental misunderstanding 35:04.836 --> 35:07.175 of this concept of digital transformation. 35:07.175 --> 35:08.698 Using information to gain insight. 35:08.698 --> 35:09.752 Finding correlations, causation, and then 35:09.752 --> 35:12.655 getting to the quanta to be able to predict. 35:12.655 --> 35:14.808 We call it digital transformation 35:14.808 --> 35:16.021 on the private sector side, 35:16.021 --> 35:16.909 but you know, I think, 35:16.909 --> 35:18.361 we're calling here Fusion Warfare, 35:18.361 --> 35:21.291 and ma'am, your points are well taken. 35:21.291 --> 35:23.246 Internet of Combat Things or even Third Offset. 35:23.246 --> 35:25.402 And I think it comes from a paradigm. 35:25.402 --> 35:28.045 It's almost our own little innovators dilemma, 35:28.045 --> 35:31.562 where we were so successful in our first two offsets 35:31.562 --> 35:32.891 that we've take those lessons 35:32.891 --> 35:35.808 that we're applying them to this new generation. 35:35.808 --> 35:38.255 So in the first offset, we made a strategic choice 35:38.255 --> 35:40.401 to invest in nuclear weapons. 35:40.401 --> 35:41.708 And then the second. 35:41.708 --> 35:44.015 We can argue whether it was PGMs or stealth technology. 35:44.015 --> 35:46.060 But we made that strategic choice to invest 35:46.060 --> 35:47.873 in that technology over something else. 35:47.873 --> 35:50.000 And now we find ourselves in this 35:50.000 --> 35:52.096 third offset where we're trying to harness 35:52.096 --> 35:54.538 the power of information technology, 35:54.538 --> 35:58.188 but I think we're trying to apply what we learned 35:58.188 --> 35:59.946 from the first two offsets to this. 35:59.946 --> 36:02.311 And that is, in the first two offset strategies, 36:02.311 --> 36:04.478 the things were important. 36:06.169 --> 36:08.526 The things were the source of our advantage. 36:08.526 --> 36:10.977 So if we lost the plans for the nuclear weapon, 36:10.977 --> 36:12.784 we lost our advantage. 36:12.784 --> 36:14.077 Fast forward to stealth. 36:14.077 --> 36:15.705 If we lost those plans, 36:15.705 --> 36:17.827 then we could easily be overcome. 36:17.827 --> 36:21.310 But when you enter a digital transformation world, 36:21.310 --> 36:24.769 oftentimes the things aren't that important. 36:24.769 --> 36:27.374 And we've talked about here, you know, 36:27.374 --> 36:28.239 airplanes as being things. 36:28.239 --> 36:29.072 But when I see things, 36:29.072 --> 36:31.475 I mean individual components on airplanes 36:31.475 --> 36:33.258 or on ships or on spacecraft. 36:33.258 --> 36:35.578 Sometimes, they're not that important, 36:35.578 --> 36:37.912 because, quite frankly, they're almost 36:37.912 --> 36:39.579 gonna be ubiquitous. 36:39.667 --> 36:41.286 They're gonna be undifferentiated in many cases, 36:41.286 --> 36:42.805 and they'll be commercially available. 36:42.805 --> 36:44.755 So it's an interesting thought experiment, 36:44.755 --> 36:48.838 but imagine sharing the exact same sensor network 36:50.130 --> 36:51.797 with your adversary. 36:53.053 --> 36:55.092 So the only source of advantage in that environment 36:55.092 --> 36:57.600 is going to be how you array those sensors 36:57.600 --> 36:59.330 and how quickly you can gain insight. 36:59.330 --> 37:00.613 And the Chief spoke about it earlier, 37:00.613 --> 37:03.395 but it implies that need for speed. 37:03.395 --> 37:07.296 And so instead of focusing on securing the thing, 37:07.296 --> 37:09.721 which has, I think, taken a lot of our resources right now, 37:09.721 --> 37:12.205 I think if we focused on maintaining resilient 37:12.205 --> 37:14.038 access to the insight. 37:14.568 --> 37:16.263 Not necessarily even the data. 37:16.263 --> 37:18.279 But maintaining resilient access to the insight, 37:18.279 --> 37:21.025 I think we could narrow that gap, 37:21.025 --> 37:22.617 which is what we're seeing in the private sector 37:22.617 --> 37:24.122 and the public sector. 37:24.122 --> 37:25.617 And there are some different strategies for doin' that, 37:25.617 --> 37:27.706 but go read some biology books and think 37:27.706 --> 37:29.360 about redundancy and symbiosis, 37:29.360 --> 37:31.395 and I think we're pretty close there. 37:31.395 --> 37:32.917 - Well, that's a great way to finish up, 37:32.917 --> 37:35.477 by focusing on the way we think 37:35.477 --> 37:39.644 as opposed to the things that help us enable that, 37:39.907 --> 37:43.216 although the things are very important as well. 37:43.216 --> 37:45.115 Well, thank you ladies and gentlemen for joining 37:45.115 --> 37:48.710 us this afternoon for this insightful discussion. 37:48.710 --> 37:52.418 Next event on the calendar is a coffee break. 37:52.418 --> 37:54.875 Please be back in your seats at 3:10, 37:54.875 --> 37:57.014 and meanwhile, please join me in thanking.