WEBVTT 00:00.840 --> 00:02.951 Ladies and gentlemen , welcome to the 00:02.951 --> 00:05.340 Final Warriors Corner presentation 00:05.360 --> 00:08.280 titled Seeing Over the Horizon Intel . 00:08.280 --> 00:10.680 Electronic warfare for deep sensing , 00:10.710 --> 00:12.950 integrated fires , experimentation A . 00:12.950 --> 00:15.770 D . A with presenters . Mr Mark kits . 00:15.780 --> 00:18.520 Brigadier general john rafferty , Mr 00:18.520 --> 00:21.000 Willie nelson , Major General bryan 00:21.000 --> 00:23.330 Gibson and Lieutenant Colonel Andrew 00:23.330 --> 00:24.050 Evans . 00:50.540 --> 00:52.596 Hey , good afternoon everyone . Hope 00:52.596 --> 00:55.190 everyone is having a fantastic A . U . 00:55.190 --> 00:58.100 S . A . Thank you very much for 00:58.110 --> 01:00.221 sticking with us for the last warrior 01:00.221 --> 01:02.970 corner here we promise we will well 01:02.980 --> 01:06.470 well make it worth your time here . Um , 01:06.480 --> 01:08.536 First I want to say thank you to our 01:08.536 --> 01:10.536 panel members for joining me . Very 01:10.536 --> 01:12.702 much appreciated and and thank you all 01:12.702 --> 01:14.869 for again sticking around for the last 01:14.869 --> 01:17.410 panel here . The title of the panel 01:17.410 --> 01:20.750 Seeing Over the Horizon is that long 01:20.750 --> 01:23.620 range sensing is my portfolio and 01:23.630 --> 01:27.250 enabling the capabilities that the CFT 01:27.250 --> 01:29.306 directors and I start task force are 01:29.306 --> 01:31.250 going to talk about it's really my 01:31.250 --> 01:34.330 mission as a P . O . W . S . General 01:34.330 --> 01:36.850 Murray has talked about sensing deep 01:36.890 --> 01:39.500 and assessing deep and that is the 01:39.500 --> 01:41.389 portfolio that I am attempting to 01:41.389 --> 01:43.333 enable that we're going to deliver 01:43.340 --> 01:45.340 through our tactical intelligence , 01:45.340 --> 01:47.451 targeting access . Note are tightened 01:47.451 --> 01:49.562 capability through our investments in 01:49.562 --> 01:51.930 electronic warfare and through our 01:51.930 --> 01:53.930 multi domain sensing system and our 01:53.930 --> 01:55.708 investments in our intelligence 01:55.708 --> 01:58.350 portfolio to sense deep . So I'm really 01:58.350 --> 02:00.461 excited to be a part of of this panel 02:00.461 --> 02:02.710 but really excited that we have this 02:02.710 --> 02:05.880 opportunity to make these investments 02:05.890 --> 02:08.970 in both are sensing for deep and are 02:08.970 --> 02:11.780 assessing for deep . Lastly , I I do 02:11.780 --> 02:13.947 want to talk a little bit about my P . 02:13.947 --> 02:15.613 O . Uh while we have a direct 02:15.613 --> 02:17.836 relationship with Mr NElson for R . P . 02:17.836 --> 02:19.891 And T . Portfolio , we're sort of at 02:19.891 --> 02:21.724 this unique relationship to army 02:21.724 --> 02:24.230 modernization . I'm not delivering 02:24.240 --> 02:26.420 directly the next generation combat 02:26.420 --> 02:28.540 vehicle , I'm not delivering directly 02:28.550 --> 02:30.990 uh , the future vertical lift portfolio , 02:31.000 --> 02:33.111 but the sensors and capabilities that 02:33.111 --> 02:35.278 I'm investing in that we are investing 02:35.278 --> 02:38.200 across our portfolio is enabling future 02:38.200 --> 02:40.520 vertical lift to operate survive a ble 02:40.770 --> 02:42.860 is enabling the sensor to shooter 02:42.860 --> 02:46.180 architectures by seeing deep and that's 02:46.180 --> 02:48.124 really what we're gonna talk about 02:48.124 --> 02:50.291 today . I'm really excited that all of 02:50.291 --> 02:52.458 our panel members will be able to give 02:52.458 --> 02:54.680 you insight as to how these investments 02:54.680 --> 02:56.847 in my portfolio are enabling , how the 02:56.847 --> 02:59.124 army is going to operate in the future . 02:59.124 --> 03:01.347 And so with that , I'm going to hand it 03:01.347 --> 03:03.569 over to General rafferty are long range 03:03.569 --> 03:05.402 precision fire safety director . 03:07.440 --> 03:09.496 So , uh , good afternoon everybody . 03:09.496 --> 03:11.496 I'm uh john rafferty from Fort sill 03:11.496 --> 03:14.320 Oklahoma . And I've been the cross 03:14.320 --> 03:16.431 functional team director for the last 03:16.431 --> 03:18.542 three years . And and so I've been on 03:18.542 --> 03:20.960 this campaign of learning for for for 03:20.960 --> 03:23.016 sensor to shooter along with with Mr 03:23.016 --> 03:25.450 NElson under his his leadership . Uh 03:25.460 --> 03:27.293 and we've been expanding our our 03:27.293 --> 03:30.420 partnerships and and team beyond what 03:30.420 --> 03:32.253 you might think . We're narrowly 03:32.253 --> 03:34.490 focused on our rpm and and uh and def 03:34.490 --> 03:36.800 con partners for the extended range 03:36.800 --> 03:39.022 cannon artillery system and the and the 03:39.022 --> 03:41.022 ammo that goes with that are on the 03:41.022 --> 03:43.300 precision strike missile with with P O . 03:43.300 --> 03:45.522 Missiles and space and the aviation and 03:45.522 --> 03:47.744 missile center where equally is focused 03:47.744 --> 03:49.800 on the end to end approach to this . 03:49.800 --> 03:51.856 And we know that we've got to see as 03:51.856 --> 03:53.911 far as we can shoot and we've got to 03:53.911 --> 03:56.022 find targets in an enormous amount of 03:56.022 --> 03:58.133 data . And so are we believe that our 03:58.340 --> 04:01.780 targeting methodology of decide detect 04:01.790 --> 04:03.930 to deliver and assess has been the 04:03.930 --> 04:06.520 perfect approach for us as a big team 04:06.530 --> 04:10.480 across across multiple pOS multiple CFT 04:10.480 --> 04:13.130 s uh and engaged with the the user 04:13.130 --> 04:15.690 community . And so in the in the decide 04:15.690 --> 04:17.801 phase , that's when we that's when we 04:17.801 --> 04:19.968 set up the high payoff target list for 04:19.968 --> 04:22.079 what what targets we want to attack . 04:22.079 --> 04:23.968 Right ? And and those high payoff 04:23.968 --> 04:26.134 targets are essential to achieving the 04:26.134 --> 04:25.940 commander's objectives and and 04:25.940 --> 04:28.107 achieving the objectives in the scheme 04:28.107 --> 04:30.107 of maneuver . Uh And so that really 04:30.107 --> 04:32.273 kind of sets the requirements for deep 04:32.273 --> 04:34.384 sensing is what are those targets and 04:34.384 --> 04:36.551 where what range bans , what degree of 04:36.551 --> 04:38.551 fidelity do we need to find them in 04:38.551 --> 04:40.384 order to engage with the weapons 04:40.384 --> 04:42.551 systems that were developing . So it's 04:42.551 --> 04:44.773 uh so it's equally as important just we 04:44.773 --> 04:46.829 like to say it's you know , concepts 04:46.829 --> 04:49.051 informing technology and the the ignite 04:49.051 --> 04:51.329 idea in the futures and Concept center . 04:51.329 --> 04:53.440 It's kind of the same here uh in that 04:53.440 --> 04:55.607 and that we need to uh we need to have 04:55.607 --> 04:57.718 the technology that that's coming out 04:57.718 --> 04:59.884 of the sensing community uh inform how 04:59.884 --> 05:01.996 we're developing our munitions in our 05:01.996 --> 05:04.051 concepts for employing them . So the 05:04.051 --> 05:05.996 team work here has been absolutely 05:05.996 --> 05:08.218 essential uh and then we go down to the 05:08.218 --> 05:10.440 to the detect phase and and we're happy 05:10.440 --> 05:12.607 to be a part of the team that's that's 05:12.607 --> 05:16.270 developing the uh the detect uh systems 05:16.270 --> 05:18.437 that are going to provide us with this 05:18.437 --> 05:20.603 information . But really we're focused 05:20.603 --> 05:20.420 on what are we going to do with the 05:20.420 --> 05:22.660 data that they're going to deliver . Uh 05:22.670 --> 05:25.880 And and Mark talked about titan , which 05:25.880 --> 05:27.936 we are totally reliant on titan as a 05:27.936 --> 05:30.047 ground station . That's going to give 05:30.047 --> 05:32.158 us the data to find our targets . And 05:32.158 --> 05:34.380 then we've been working across multiple 05:34.380 --> 05:36.547 organizations to develop uh to develop 05:36.547 --> 05:38.269 the synchronized high up tempo 05:38.269 --> 05:40.047 targeting tool which will be an 05:40.047 --> 05:42.158 application on titan that follows the 05:42.158 --> 05:44.269 high payoff target list . It's driven 05:44.269 --> 05:46.491 by the target selection standards . And 05:46.491 --> 05:49.060 then and then it follows the commands 05:49.060 --> 05:51.227 that are in the attack guidance matrix 05:51.227 --> 05:53.560 to generate calls for fire uh and uh 05:53.570 --> 05:55.292 and make the sensor to shooter 05:55.292 --> 05:57.403 timelines that we know we're going to 05:57.403 --> 05:59.626 have to for uh for the demands of large 05:59.626 --> 06:01.848 scale combat . And then if we just take 06:01.848 --> 06:03.848 it down to the deliver . I talked a 06:03.848 --> 06:05.959 little bit about that we need to make 06:05.959 --> 06:08.070 sure our munitions are capable enough 06:08.070 --> 06:07.920 to take advantage of the of the data 06:07.920 --> 06:09.864 and the targeting information that 06:09.864 --> 06:12.087 we're going to get in our platforms and 06:12.087 --> 06:13.809 our R . C . Two systems uh for 06:13.809 --> 06:16.800 controlling uh integrating fires are 06:16.800 --> 06:18.750 ready to be able to deal with the 06:18.750 --> 06:21.330 volume of targets and to be agile 06:21.330 --> 06:24.500 enough uh to to deal with the the best 06:24.500 --> 06:26.611 shooter ? Not necessarily the shooter 06:26.611 --> 06:28.556 that we had we had in mind . Uh so 06:28.556 --> 06:30.556 we've got to develop that degree of 06:30.556 --> 06:32.444 agility in there and then finally 06:32.444 --> 06:34.667 assess , I mean marketed , we've got to 06:34.667 --> 06:36.833 be able to get a sense deep and assess 06:36.833 --> 06:36.690 deep . Uh and that traditionally has 06:36.690 --> 06:38.746 been one of the weaknesses in our in 06:38.746 --> 06:40.830 our D three A process is we have 06:40.830 --> 06:42.941 trouble with the assessment phase and 06:42.941 --> 06:45.108 that's I'm glad that that's a that's a 06:45.108 --> 06:47.330 focus for all of us . This intelligence 06:47.330 --> 06:49.441 and targeting relationship has always 06:49.441 --> 06:48.890 been , you know , kind of a love hate 06:48.890 --> 06:51.260 relationship , but but the fact that 06:51.260 --> 06:53.316 we're working together early in this 06:53.316 --> 06:55.427 and not just trying to figure out how 06:55.427 --> 06:57.538 to make our systems work once they're 06:57.538 --> 06:59.538 in the field is a pretty remarkable 06:59.538 --> 06:59.530 development and at least in in my 06:59.530 --> 07:02.260 experience and then last 07:02.740 --> 07:05.250 the three approaches that we take to 07:05.250 --> 07:07.472 all the things that we're developing is 07:07.472 --> 07:09.694 is first is should we do it right . And 07:09.694 --> 07:11.806 so does our operation analysis showed 07:11.806 --> 07:14.083 that this investment , this technology , 07:14.083 --> 07:16.250 this capability is critical to helping 07:16.250 --> 07:18.361 us achieve our objectives against the 07:18.361 --> 07:20.583 near pier threat in the future . And we 07:20.583 --> 07:22.694 believe that all the investments here 07:22.694 --> 07:22.390 based on our operation analysis are 07:22.390 --> 07:25.750 absolutely relevant and needed . 07:26.240 --> 07:28.480 And then the second thing is can we do 07:28.480 --> 07:30.940 it right , So are we technically able 07:30.940 --> 07:33.950 to deliver these systems and we know by , 07:34.540 --> 07:36.429 by the way in which we've , we've 07:36.429 --> 07:38.651 approached these science and technology 07:38.651 --> 07:40.570 investments and uh , the careful 07:40.570 --> 07:42.681 transition planning that we have from 07:42.681 --> 07:44.292 the S and T community to the 07:44.292 --> 07:46.237 acquisition community . So we , we 07:46.237 --> 07:48.181 bridge that valley of death across 07:48.181 --> 07:50.237 these programs that we can do this . 07:50.237 --> 07:52.514 We're meeting our technical milestones , 07:52.514 --> 07:54.681 we're on schedule , we can do , we can 07:54.681 --> 07:56.570 do these things . And then lastly 07:56.570 --> 07:58.681 though , it's how will we do it ? Not 07:58.681 --> 08:00.737 just the user , not just the soldier 08:00.737 --> 08:02.959 touchpoints in terms of like how should 08:02.959 --> 08:02.740 we configure this ? What's the best 08:02.750 --> 08:05.950 interface ? Is it intuitive , but it's , 08:05.960 --> 08:08.182 but it's how are we going to fight with 08:08.182 --> 08:10.349 these capabilities ? And that's what , 08:10.349 --> 08:12.460 you know , Willie nelson's leadership 08:12.460 --> 08:14.627 on the campaign of learning for sensor 08:14.627 --> 08:16.793 to shooter has been very important and 08:16.793 --> 08:18.960 it's all been risk reduction for , for 08:18.960 --> 08:20.960 project convergence . Uh especially 08:20.960 --> 08:20.580 what we're going to learn during 08:20.580 --> 08:23.010 project convergence , 21 is going to be 08:23.010 --> 08:25.121 all about how we're going to fight as 08:25.121 --> 08:27.177 an army team as a combined arms team 08:27.177 --> 08:29.399 and as a joint team , take advantage of 08:29.399 --> 08:31.510 deep sensing , attacking targets with 08:31.510 --> 08:34.400 ranges that we haven't before And an 08:34.400 --> 08:36.622 agile C2 and command relationships that 08:36.622 --> 08:38.789 we haven't really explored before . So 08:38.789 --> 08:40.900 we're pretty excited about the future 08:40.900 --> 08:43.067 and with that , I will look forward to 08:43.067 --> 08:45.178 your questions and turn it over to Mr 08:45.178 --> 08:47.710 nelson ? Well , good afternoon , it's 08:47.710 --> 08:49.877 always exciting to be the last briefer 08:49.877 --> 08:51.988 or briefing team of the day I guess . 08:51.988 --> 08:54.210 Uh but again , um for those who weren't 08:54.210 --> 08:56.432 here earlier , good afternoon . My name 08:56.432 --> 08:56.240 is Willie nelson . I'm the safety , the 08:56.240 --> 08:58.030 assured P and T . And Space CFT 08:58.030 --> 09:00.141 director headquartered at register an 09:00.141 --> 09:03.000 arsenal in Huntsville Alabama . Um so a 09:03.010 --> 09:06.420 good uh segue into some of you may have 09:06.420 --> 09:08.253 heard of what we refer to as the 09:08.253 --> 09:10.420 campaign of learning and in some cases 09:10.420 --> 09:12.420 that proceeds project convergence a 09:12.420 --> 09:14.531 little bit . But it's what we what we 09:14.531 --> 09:16.587 did about two years ago as we said , 09:16.587 --> 09:18.753 we've got all these new this new kid , 09:18.753 --> 09:20.976 all these new capabilities , individual 09:20.976 --> 09:20.630 capabilities , we've got guns that can 09:20.630 --> 09:22.297 shoot farther , We've got a I 09:22.297 --> 09:24.519 capabilities that Alex is gonna talk to 09:24.519 --> 09:26.463 a little bit about . We've got all 09:26.463 --> 09:26.160 these things that are coming together , 09:26.640 --> 09:28.473 we need to sit down with the war 09:28.473 --> 09:30.696 fighters in both europe and the pacific 09:30.696 --> 09:32.862 and figure out new T . T . P . S . And 09:32.862 --> 09:34.973 conduct and how do we integrate these 09:34.973 --> 09:34.860 these systems . And so what we did is 09:34.860 --> 09:36.960 we brought literally the communities 09:36.960 --> 09:39.930 from europe , from , from user pack , 09:39.940 --> 09:42.162 our fires community , our intel group , 09:42.162 --> 09:44.384 our network teams and we had an initial 09:44.384 --> 09:46.329 meeting about two years ago to say 09:46.329 --> 09:48.384 listen , we're going to be accessing 09:48.384 --> 09:50.496 sensors at higher altitudes , peter , 09:50.496 --> 09:50.290 high altitude space whatever . And 09:50.290 --> 09:52.512 we've got to be able to integrate those 09:52.512 --> 09:54.401 in into our system and be able to 09:54.401 --> 09:56.570 rapidly decrease our decision time and 09:56.570 --> 09:58.626 are executing time with all of these 09:58.626 --> 10:00.792 new weapons and so from that new TTP s 10:00.792 --> 10:02.848 and contacts were developed and then 10:02.848 --> 10:05.014 the beauty of the campaign of learning 10:05.014 --> 10:07.181 is when we go back to the field and so 10:07.181 --> 10:09.237 we went back into europe and we went 10:09.237 --> 10:09.190 back into the pacific this last year , 10:09.200 --> 10:11.200 even through Covid , we were mildly 10:11.200 --> 10:13.311 successful in europe , and then we go 10:13.311 --> 10:14.978 ahead and actually set up the 10:14.978 --> 10:17.089 experimentation again , bringing data 10:17.089 --> 10:19.144 down from sensors , integrating that 10:19.144 --> 10:21.256 through the , through the platforms . 10:21.256 --> 10:23.144 You're going to hear today on the 10:23.144 --> 10:25.144 operational architecture in theater 10:25.144 --> 10:27.256 with the weapons systems and soldiers 10:27.256 --> 10:27.060 manning , manning the weapons and so 10:27.060 --> 10:28.893 from that you get really you get 10:28.893 --> 10:31.116 validated input and requirements out of 10:31.116 --> 10:33.227 that in terms of how well it worked . 10:33.227 --> 10:35.449 Uh data formats , we found that in many 10:35.449 --> 10:37.449 cases the data formats maybe didn't 10:37.449 --> 10:39.560 work like we thought , so you're able 10:39.560 --> 10:41.727 to work those out . And again to bring 10:41.727 --> 10:43.727 the ape in discussion earlier , the 10:43.727 --> 10:43.360 more that we can do that stuff in the 10:43.360 --> 10:45.710 lab early and then go take it and put 10:45.710 --> 10:47.950 it in the operational field with with 10:47.950 --> 10:50.240 our soldiers and war fighters . Um then 10:50.250 --> 10:52.306 then again we're able to really turn 10:52.306 --> 10:54.330 that maturity of these systems much 10:54.330 --> 10:56.663 better . And so again we were in europe , 10:56.663 --> 10:58.886 we did some a series of tests in europe 10:58.886 --> 11:01.052 two years ago because of Covid , we're 11:01.052 --> 11:03.274 not in the pacific , but this last year 11:03.274 --> 11:05.441 we were in both europe the pacific and 11:05.441 --> 11:05.350 again , bringing those sensor to 11:05.350 --> 11:07.517 shooter timelines down integrating the 11:07.517 --> 11:09.683 feedback and the requirements that are 11:09.683 --> 11:11.628 developed by our soldiers into our 11:11.628 --> 11:13.850 weapons systems to be able to uh mature 11:13.850 --> 11:15.906 systems . And again , all that is in 11:15.906 --> 11:18.017 preparation then for the main event , 11:18.017 --> 11:17.930 which will be project convergence as 11:17.930 --> 11:19.986 you all are well tracking and so I'm 11:19.986 --> 11:21.874 here , I'll be here to answer any 11:21.874 --> 11:21.230 questions . But we thought we'd at 11:21.230 --> 11:23.341 least just kind of mentioned with the 11:23.341 --> 11:25.341 Campaign of learning is so that you 11:25.341 --> 11:27.119 know what that is and if you're 11:27.119 --> 11:29.063 involved in that we're starting to 11:29.063 --> 11:31.286 engage our coalition partners in the 22 11:31.286 --> 11:33.452 timeframe , again keeping in sync with 11:33.452 --> 11:35.674 our project convergence mantra . Uh and 11:35.674 --> 11:35.150 we'll be doing more and more that next 11:35.150 --> 11:37.261 year . So the kickoff program for the 11:37.261 --> 11:39.370 kick off for 22 planning will be in 11:39.370 --> 11:41.481 December . Uh and then we'll we'll be 11:41.481 --> 11:43.703 kicking that off then the next calendar 11:43.703 --> 11:45.870 year . So I'll uh leave it at that and 11:45.870 --> 11:45.730 again respond your questions if you 11:45.730 --> 11:48.540 have any alternate over to the air 11:48.540 --> 11:52.520 Missile Defense CFT Director . Okay , 11:52.520 --> 11:54.880 thanks Willy , I'm brian Gibson , the 11:54.890 --> 11:56.890 john rafferty's counterpart at fort 11:56.890 --> 11:59.057 sill . We've been there about the same 11:59.057 --> 12:01.279 amount of time and various jobs , but I 12:01.279 --> 12:03.223 get the privilege of leading their 12:03.223 --> 12:05.334 missile defense cross functional team 12:05.334 --> 12:07.557 and I think before I go into details on 12:07.557 --> 12:07.180 their missile defense . If you look at 12:07.190 --> 12:10.140 who's on this stage from a P E 02 CFT 12:10.140 --> 12:13.540 directors to headquarters DEA and other 12:13.640 --> 12:16.860 staff elements expert . It's a good 12:16.860 --> 12:19.500 fundamental representation of of the 12:19.500 --> 12:21.722 team work that it takes to do something 12:21.722 --> 12:23.944 fundamentally different . And you might 12:23.944 --> 12:26.056 think of why is their defense on this 12:26.056 --> 12:28.520 panel ? I heard about long range fires . 12:28.520 --> 12:31.210 I hear about intelligence here about 12:31.220 --> 12:33.340 the need for space . There is an 12:33.350 --> 12:35.820 inextricable link between space 12:35.820 --> 12:38.042 intelligence and the conduct of air and 12:38.042 --> 12:39.987 missile defense and whether that's 12:39.987 --> 12:41.931 inside of service lines or whether 12:41.931 --> 12:44.250 that's in support of our joint force , 12:44.740 --> 12:47.370 the tighter that we make the coupling 12:47.370 --> 12:49.203 of those three domains and those 12:49.203 --> 12:51.314 capabilities , the better the options 12:51.314 --> 12:53.370 we provide for our war fighters . So 12:53.370 --> 12:55.592 it's it's great to be on this panel . I 12:55.592 --> 12:57.537 appreciate it . It's a it's a good 12:57.537 --> 12:59.703 approach I think to systems of systems 12:59.703 --> 13:01.592 oftentimes is not well understood 13:01.592 --> 13:04.310 because it's hard , it's complex and 13:04.310 --> 13:06.970 many times it is approached with 13:06.970 --> 13:09.137 success from a lot of different people 13:09.137 --> 13:10.914 who make it successful a lot of 13:10.914 --> 13:13.230 different things but it's all about the 13:13.230 --> 13:15.397 right information at the right place , 13:15.397 --> 13:17.452 at the right place to the right user 13:17.452 --> 13:19.563 inside of air missile defense . There 13:19.563 --> 13:21.563 are some obvious things that it's a 13:21.563 --> 13:23.508 benefit for us when we create this 13:23.508 --> 13:25.508 tighter coupling of those different 13:25.508 --> 13:28.010 connections . One , the sooner we can 13:28.020 --> 13:30.390 tell a threat is coming to us , the 13:30.390 --> 13:33.120 more reaction time we have and the 13:33.120 --> 13:35.510 sooner if we have to take a kinetic 13:35.510 --> 13:37.600 shot , the better off we potentially 13:37.600 --> 13:40.450 will be And much of that is tied to 13:40.450 --> 13:42.730 deep sensing and much of that is tied 13:42.730 --> 13:45.200 directly to left of before syncing the 13:45.200 --> 13:47.830 intelligence and the information being 13:47.830 --> 13:50.140 provided to our operators . The other 13:50.140 --> 13:53.070 thing equally important that this idea 13:53.070 --> 13:54.848 of deep sensing and coupling of 13:54.848 --> 13:57.430 intelligence does for our forces , it 13:57.430 --> 14:00.350 allows us the ability to only 14:00.740 --> 14:04.580 radiate when we must to allow 14:04.590 --> 14:07.260 us to retain the advantage and to not 14:07.260 --> 14:09.316 give away our positions just for the 14:09.316 --> 14:11.538 function of having to take a shot if we 14:11.538 --> 14:14.370 have to . So the better opportunities 14:14.370 --> 14:17.160 we provide to intentionally 14:17.160 --> 14:20.850 unintentionally but also control our 14:20.850 --> 14:23.170 emissions . The better off we preserve 14:23.170 --> 14:25.337 the flexibility for the success of the 14:25.337 --> 14:27.114 fight . So that's an incredible 14:27.114 --> 14:29.059 important part that oftentimes get 14:29.059 --> 14:31.170 overlooked that it's about taking the 14:31.170 --> 14:33.392 shot and put a missile down range . But 14:33.392 --> 14:35.392 equally important , I think left of 14:35.392 --> 14:37.503 that is provide for the protection of 14:37.503 --> 14:39.670 not ourselves , not only ourselves but 14:39.670 --> 14:42.510 others . And then lastly it's all about 14:42.510 --> 14:44.810 contested environments and when we 14:44.810 --> 14:47.130 established the coupling of being able 14:47.130 --> 14:50.530 to sense , understand , decide and then 14:50.540 --> 14:52.596 act differently because of different 14:52.596 --> 14:54.707 connections that we're establishing . 14:54.840 --> 14:56.451 The better off . We have the 14:56.451 --> 14:58.507 opportunity to operate and contested 14:58.507 --> 15:00.673 environments and still provide options 15:00.673 --> 15:02.896 to our war fighters . So I'm incredibly 15:02.896 --> 15:05.118 excited to be on the panel . Thanks for 15:05.118 --> 15:07.173 allowing me to be here . The four of 15:07.173 --> 15:10.580 you oftentimes . Um , it goes without 15:10.580 --> 15:12.850 saying , but this is an army together , 15:12.850 --> 15:14.906 fighting and to joint together fight 15:14.940 --> 15:16.996 and it's all about getting different 15:16.996 --> 15:18.773 outcomes . So with that I'll be 15:18.773 --> 15:20.940 followed by Alex miller to finish this 15:20.940 --> 15:24.760 up . Thanks . Hey , thank you . I'm 15:24.760 --> 15:26.927 gonna do something live . Um I brought 15:26.927 --> 15:29.149 technology sitting in that chair is not 15:29.149 --> 15:31.371 gonna do some success . So I'm going to 15:31.371 --> 15:33.371 change the concept and I'm actually 15:33.371 --> 15:33.220 gonna come up here for a minute . Um 15:33.230 --> 15:35.380 and thanks Mark . And it's important 15:35.390 --> 15:37.668 because this is what this is all about . 15:37.668 --> 15:39.834 It's about thinking through what we're 15:39.834 --> 15:39.660 gonna do and why we're going to do it . 15:40.040 --> 15:41.929 So you've heard about some of our 15:41.929 --> 15:44.760 signature efforts titan in DSS the 15:44.760 --> 15:46.880 terrestrial air system . That's not 15:46.880 --> 15:48.824 what this is about . This is about 15:48.824 --> 15:52.480 thinking through how and why so why we 15:52.480 --> 15:55.400 know in the future all of the threats 15:55.400 --> 15:59.060 are layered across every domain across 15:59.060 --> 16:00.910 the space . Air , terrestrial , 16:00.910 --> 16:02.854 integrated air , missile defense , 16:02.854 --> 16:05.077 cyber human , it's all layered , that's 16:05.077 --> 16:07.220 why we're doing these things . And as 16:07.220 --> 16:09.220 we think through how we're going to 16:09.220 --> 16:11.387 employ technology . It is really about 16:11.387 --> 16:13.442 thinking through the indian into end 16:13.442 --> 16:15.331 architecture . It is really about 16:15.331 --> 16:17.164 thinking through how we maintain 16:17.164 --> 16:19.387 architectural agility and architectural 16:19.387 --> 16:21.553 flexibility because architecture's our 16:21.553 --> 16:23.609 conceptual infrastructure is a thing 16:23.609 --> 16:25.720 when we start buying infrastructure , 16:25.720 --> 16:27.887 we have locked ourselves in . So being 16:27.887 --> 16:30.220 able to think through that is important . 16:30.220 --> 16:29.490 But let me , let me just rattle off 16:29.490 --> 16:31.490 some of the other things that we're 16:31.490 --> 16:33.712 thinking about because this isn't about 16:33.712 --> 16:35.850 us , this is about us and thinking 16:35.850 --> 16:37.906 through how we do this together . So 16:37.906 --> 16:40.017 the network . General Ray the network 16:40.017 --> 16:42.128 cross functional team , collaborative 16:42.128 --> 16:44.350 sensing . How we do this with the other 16:44.350 --> 16:46.183 services across all domains that 16:46.183 --> 16:48.350 normally don't talk to each other . We 16:48.350 --> 16:50.517 normally don't do air plus ground plus 16:50.517 --> 16:52.739 space sensing . That's a new thing that 16:52.739 --> 16:54.794 we're getting into edge processing . 16:54.794 --> 16:56.406 I've seen really commendable 16:56.406 --> 16:58.406 improvements in edge processing but 16:58.406 --> 17:00.406 also edge power management for that 17:00.406 --> 17:02.572 processing because we know we can nerd 17:02.572 --> 17:04.628 out a little bit throwing gps at the 17:04.628 --> 17:06.794 problem at the edge doesn't work right 17:06.794 --> 17:08.961 to power hungry . Too hot . Like no no 17:08.961 --> 17:11.183 soldier once a gpu in their backpack it 17:11.183 --> 17:13.128 will burn them . It's not fun . Um 17:13.128 --> 17:15.072 signature management and signature 17:15.072 --> 17:16.961 control to do manned and unmanned 17:16.961 --> 17:18.739 teaming . I love A . I . I am a 17:18.739 --> 17:20.906 computer scientist by trade A . I . Is 17:20.906 --> 17:23.128 what I get really excited about but the 17:23.128 --> 17:23.000 foundations of A . I . R . What's 17:23.000 --> 17:25.060 really compelling as we move forward 17:26.140 --> 17:28.251 considering how we're going to employ 17:28.251 --> 17:30.510 technology . Getting away from A . I . 17:30.510 --> 17:32.621 As a cognitive prosthetic . Something 17:32.621 --> 17:34.788 that just makes us a little bit better 17:34.788 --> 17:37.010 and things were already doing to really 17:37.010 --> 17:39.066 empowering machines to augment human 17:39.066 --> 17:41.288 decision making . I look forward to the 17:41.288 --> 17:43.510 day when our budget analysts don't have 17:43.510 --> 17:45.454 to look at excel because there are 17:45.454 --> 17:47.566 already tools that are doing this for 17:47.566 --> 17:49.677 them . So that is augmenting decision 17:49.677 --> 17:51.343 making . Not just a cognitive 17:51.343 --> 17:53.343 prosthetic . All of these represent 17:53.343 --> 17:55.510 changes to our operating model and our 17:55.510 --> 17:57.566 business models because they are not 17:57.566 --> 17:59.732 the same And we have to modernize both 17:59.732 --> 18:01.454 of them not only how we employ 18:01.454 --> 18:03.454 technology but how we do technology 18:03.454 --> 18:05.621 from the ground up . And it means that 18:05.621 --> 18:07.677 we can't buy something that requires 18:07.677 --> 18:07.440 modernized infrastructure . We haven't 18:07.450 --> 18:09.617 also modernize the infrastructure . So 18:09.617 --> 18:11.672 let me go through some of the things 18:11.672 --> 18:13.839 that we are doing because nobody wants 18:13.839 --> 18:13.370 to hear that we solve these problems 18:13.370 --> 18:15.203 because we haven't we're working 18:15.203 --> 18:17.426 through them sensing deeper . How do we 18:17.426 --> 18:19.537 do mandate and mandating , unattended 18:19.537 --> 18:21.537 sensing and robotics platform based 18:21.537 --> 18:23.850 sensing . So tying together the G vsc 18:23.860 --> 18:25.749 general Kaufman's nick generation 18:25.749 --> 18:27.860 combat vehicle . How do we turn those 18:27.860 --> 18:30.027 into sensor mules ? How do we leverage 18:30.027 --> 18:32.138 the air launched effects to get after 18:32.138 --> 18:34.249 seeing over the horizon because I can 18:34.249 --> 18:36.471 see anywhere making sense of what we're 18:36.471 --> 18:38.582 seeing . That's the compelling part . 18:38.582 --> 18:38.550 That's where we have a lot of problems 18:38.560 --> 18:41.050 because pixels are awesome for people 18:41.060 --> 18:43.282 when we look at maps that is forensic , 18:43.282 --> 18:45.449 we are looking at those pixels because 18:45.449 --> 18:47.671 we've already collected them but making 18:47.671 --> 18:49.727 decisions off of that in real time . 18:49.727 --> 18:51.560 Really compelling processing and 18:51.560 --> 18:54.370 analyzing . So analysts have to think 18:54.380 --> 18:56.590 in depth and over the last three days 18:56.590 --> 18:59.060 I've it's been a masterclass walking 18:59.060 --> 19:01.250 around with my leadership to think 19:01.250 --> 19:03.361 through . Are we really talking about 19:03.361 --> 19:05.361 detail on the right way disrupted ? 19:05.361 --> 19:07.250 Denied integrate intermittent and 19:07.250 --> 19:09.472 limited columns . Are we really talking 19:09.472 --> 19:11.583 about it as a binary switch . Is that 19:11.583 --> 19:11.560 honor ? Is it off or is it temporal ? 19:12.140 --> 19:14.362 Is our communication should we treat it 19:14.362 --> 19:16.529 from the get go is ephemeral that it's 19:16.529 --> 19:18.251 not always going to be there . 19:18.251 --> 19:17.930 Therefore we have to have methods for 19:17.930 --> 19:20.097 synchronizing and replicating data and 19:20.097 --> 19:21.819 moving that through and making 19:21.819 --> 19:24.160 decisions on sparse data and loading 19:24.160 --> 19:26.920 human intuition into machines . That's 19:26.920 --> 19:28.976 what we're thinking about analysis . 19:28.976 --> 19:31.087 How do we leverage advanced analytics 19:31.087 --> 19:33.309 and that's an amorphous term . I know , 19:33.309 --> 19:35.198 but getting past just very simple 19:35.198 --> 19:37.309 rudimentary rudimentary analytics and 19:37.309 --> 19:39.253 empowering machines to augment our 19:39.253 --> 19:41.476 decision making so that we can actually 19:41.476 --> 19:43.642 get after machine intelligence because 19:43.642 --> 19:45.753 I love all of our Ai scholars because 19:45.753 --> 19:45.500 they are doing they are doing 19:45.500 --> 19:47.940 foundational work but we have got to 19:47.940 --> 19:50.107 empower them , Get them to tools , get 19:50.107 --> 19:52.780 them to processes , working through all 19:52.780 --> 19:54.502 of the edge processing because 19:54.502 --> 19:56.724 ultimately and I missed the term and so 19:56.724 --> 19:58.724 I know we changed it but getting to 19:58.724 --> 20:00.613 that digital quarterback that can 20:00.613 --> 20:02.724 actually help us work through all the 20:02.724 --> 20:04.669 jet ski to continue . Um uh that's 20:04.669 --> 20:06.724 that's what we're going through . So 20:06.724 --> 20:08.947 automation augmentation allowing humans 20:08.947 --> 20:10.724 to imbue machine and view their 20:10.724 --> 20:12.669 decision making processes into the 20:12.669 --> 20:14.440 architecture . That is where 20:14.450 --> 20:16.810 convergence is trying to get to so with 20:16.810 --> 20:19.320 that I'll yield back to to the team for 20:19.330 --> 20:22.370 for questions . Yeah , thanks thanks 20:22.370 --> 20:26.290 Alex um before sorry , before we get to 20:26.290 --> 20:28.234 questions I do want to amplify one 20:28.234 --> 20:30.810 point that was thematic in in the in 20:30.810 --> 20:34.580 the panel here and and the theme is 20:34.590 --> 20:36.630 that we are not alone , right ? We 20:36.630 --> 20:38.519 could have in order to enable the 20:38.519 --> 20:40.519 sensor to shooter architecture . It 20:40.519 --> 20:42.830 would take all of us and many , many 20:42.830 --> 20:44.386 more on this panel that are 20:44.386 --> 20:46.480 contributing to that conceptual 20:46.480 --> 20:49.290 architecture . It also involves 20:49.300 --> 20:51.880 industry , we will fail if industry 20:51.880 --> 20:55.760 cannot deliver in an open way that most 20:55.760 --> 20:58.140 importantly , understands that in order 20:58.140 --> 21:00.600 to do deep sense and deep assess the 21:00.600 --> 21:03.090 army cannot do it alone . And so we've 21:03.090 --> 21:05.980 got to be able to leverage all sources 21:05.990 --> 21:08.560 of sensing and all sources of our 21:08.560 --> 21:11.740 ability to make uh , determinations on 21:11.740 --> 21:13.684 that sensor capability in order to 21:13.684 --> 21:15.851 deliver that over the horizon , sensor 21:15.851 --> 21:18.073 to shooter architecture that we're that 21:18.073 --> 21:20.240 we are all striving towards . So thank 21:20.240 --> 21:22.462 you all very much and uh , I will yield 21:22.462 --> 21:23.684 to questions please . 21:28.740 --> 21:30.573 Good afternoon gentlemen , Jamal 21:30.573 --> 21:32.630 Williams Joint staff . Uh sir , it 21:32.630 --> 21:35.430 seems like a lot of the platforms that 21:35.430 --> 21:37.486 we're looking at a large or national 21:37.486 --> 21:39.790 assets . Uh , is there a place for the 21:39.790 --> 21:41.901 dismounted joint fires warfighter and 21:41.901 --> 21:43.901 if so , what capabilities are being 21:43.901 --> 21:45.846 looked at ? Uh , the C F . T S for 21:45.846 --> 21:47.901 those individuals like the J tax and 21:47.901 --> 21:51.200 afford observers as well , George , do 21:51.200 --> 21:54.990 you want to start us off ? Sure , 21:55.000 --> 21:57.960 I am . Well , obviously that's outside 21:57.960 --> 22:00.730 of outside of our CFT platform or 22:00.730 --> 22:03.570 portfolio . Um , I think you might have 22:03.570 --> 22:05.570 tried to slide this question into a 22:05.570 --> 22:08.460 panel earlier in the week . Sounds 22:08.460 --> 22:10.670 familiar , but uh , but but I'd say 22:10.670 --> 22:12.726 that , you know , we're the army and 22:12.726 --> 22:14.726 and the under the leadership of the 22:14.726 --> 22:16.670 Fire Center of Excellence is still 22:16.670 --> 22:18.830 pushing out jets as in a really 22:18.830 --> 22:20.886 important modernization tool for our 22:20.886 --> 22:22.910 our light and dismounted uh fire 22:22.910 --> 22:26.220 supporters . And so that modernization 22:26.220 --> 22:29.180 ever will continue . Uh the uh 22:29.190 --> 22:31.246 experimentation we're doing with the 22:31.246 --> 22:33.301 attack device during some of the use 22:33.301 --> 22:35.360 cases in the project converges . 21 22:35.360 --> 22:38.720 will also prove what's possible uh 22:38.730 --> 22:42.460 for connectivity for uh 22:44.440 --> 22:46.740 Uh innovative ways to uh to connect 22:46.740 --> 22:49.000 sensors . uh and uh and shooters . 22:49.010 --> 22:51.066 We're going to learn more about that 22:51.066 --> 22:53.177 project convergence 21 too . So so we 22:53.177 --> 22:55.343 certainly we have not walked away from 22:55.343 --> 22:57.566 the close fight and that's that's often 22:57.566 --> 22:59.677 a misconception that uh that that I'm 22:59.677 --> 23:01.677 glad you gave me the opportunity to 23:01.677 --> 23:03.677 challenge a little bit . But what's 23:03.677 --> 23:05.788 more important about what we're doing 23:05.788 --> 23:07.788 in terms of connecting , you know , 23:07.788 --> 23:09.732 deep sensing , improved , improved 23:09.732 --> 23:12.820 processes , uh more precision and then 23:12.830 --> 23:14.997 and then longer range and lethality is 23:14.997 --> 23:17.210 we're changing the close fight . So 23:17.210 --> 23:19.377 when I when I set up front , the first 23:19.377 --> 23:21.488 thing we ask is should we do this and 23:21.488 --> 23:23.543 will it make a difference and all of 23:23.543 --> 23:23.380 our operational analysis when it comes 23:23.380 --> 23:25.602 to the integration of , you know , more 23:25.602 --> 23:27.824 lethality and range , especially at the 23:27.824 --> 23:29.991 division and brigade combat team fight 23:29.991 --> 23:32.158 is that it totally changes the brigade 23:32.158 --> 23:34.380 combat team fight . We make it unfair . 23:34.380 --> 23:36.269 Uh and and so I think in that way 23:36.269 --> 23:38.324 that's when we start to win in these 23:38.324 --> 23:40.436 very challenging scenarios and that's 23:40.436 --> 23:42.547 when we make the best contribution we 23:42.547 --> 23:44.680 can to the light and dismounted 23:44.690 --> 23:46.912 observation community is maybe they got 23:46.912 --> 23:49.550 fewer targets to worry about because 23:49.560 --> 23:52.020 because we will have been able to 23:52.030 --> 23:55.990 engage and defeat armored targets . Uh 23:56.000 --> 23:58.200 It ranges we can't now with totality 23:58.200 --> 24:00.367 that we that we that we don't have now 24:00.367 --> 24:02.870 uh before they deploy while they're 24:02.870 --> 24:04.981 still in assembly areas . So we think 24:04.981 --> 24:07.314 we make all the difference in the world . 24:07.314 --> 24:09.426 So that's kind of a comprehensive way 24:09.426 --> 24:08.480 in which we are addressing the close 24:08.480 --> 24:11.650 fight . So I want to jump on that 24:11.660 --> 24:13.660 because I've been thinking about it 24:13.660 --> 24:15.716 since yesterday because I was a hard 24:15.716 --> 24:17.827 question to answer yesterday too . Um 24:17.827 --> 24:19.993 It's okay if we say we don't know what 24:19.993 --> 24:22.900 the right thing is . What we do know is 24:22.910 --> 24:25.150 giving a J . Attack or an O . D . A . 24:25.160 --> 24:28.170 Or a small unconventional warfare 24:28.170 --> 24:30.170 element a bunch of stuff and asking 24:30.170 --> 24:32.392 them to report everything through pipes 24:32.392 --> 24:34.670 that don't work . Not the right answer . 24:34.670 --> 24:36.837 So we might not know what works but we 24:36.837 --> 24:38.948 know 10,000 ways that don't work . So 24:38.948 --> 24:41.170 we can start calling it down to the kit 24:41.170 --> 24:43.337 and the concepts and the TTP s and the 24:43.337 --> 24:45.830 architecture that do work and then test 24:45.830 --> 24:47.997 it out because I know that are soft is 24:47.997 --> 24:50.219 working through that thought process as 24:50.219 --> 24:52.330 well . Oh just one more thing and one 24:52.330 --> 24:54.441 thing we are doing for the dismounted 24:54.441 --> 24:56.330 soldier is to be able to make the 24:56.330 --> 24:58.441 provide them some resiliency and some 24:58.441 --> 25:00.552 assurances and their P and T solution 25:00.570 --> 25:02.737 and their positioning , navigation and 25:02.737 --> 25:04.959 timing . And so the DATs are dismounted 25:04.959 --> 25:07.070 assured PMT system managed through MR 25:07.070 --> 25:09.520 MR kits , P E . O . That is 11 program 25:09.520 --> 25:11.687 that the army is putting forward to be 25:11.687 --> 25:13.964 able to provide again that assuredness , 25:13.964 --> 25:15.909 that reliability and resistance in 25:15.909 --> 25:18.020 resilience in terms of timing in many 25:18.020 --> 25:19.964 cases to keep the networks going , 25:19.964 --> 25:21.798 that's gonna that's gonna enable 25:21.798 --> 25:23.909 everything you're saying here as well 25:23.909 --> 25:26.020 as other position aiding capabilities 25:26.020 --> 25:28.242 to include GPS but other other types of 25:28.242 --> 25:29.964 capability . Again down to the 25:29.964 --> 25:29.580 dismounted soldiers so I just want to 25:29.590 --> 25:31.812 put a plug in for that program but also 25:31.812 --> 25:33.923 to know that it's in a direct support 25:33.923 --> 25:36.090 because we are going to be fighting in 25:36.090 --> 25:35.890 a challenging environment . We know 25:35.890 --> 25:38.001 that and so we ought to be able to do 25:38.001 --> 25:39.001 that seamlessly . 25:58.040 --> 26:00.096 Being being the last panel I guess . 26:00.096 --> 26:02.900 Has it has any other questions for the 26:02.900 --> 26:05.860 panel ? Dead sir , 26:07.340 --> 26:09.396 we're doing things differently . Are 26:09.396 --> 26:11.562 you looking at different formations or 26:11.562 --> 26:13.690 how you can leverage joint assets to 26:13.700 --> 26:15.756 squeeze the time of the kill chain ? 26:17.040 --> 26:19.040 Yeah , I'll get it started and then 26:19.050 --> 26:21.161 General Gibson will jump in here . So 26:21.161 --> 26:23.390 uh I would say absolutely . When we 26:23.390 --> 26:26.120 look at our sensor portfolio , it's not 26:26.120 --> 26:28.630 just an army portfolio . It's also not 26:28.630 --> 26:30.797 just the defence portfolio . How do we 26:30.797 --> 26:33.170 ingest the data that we need . So we 26:33.170 --> 26:35.337 can make those assessments and deliver 26:35.440 --> 26:38.480 our solution or the uh , the product at 26:38.480 --> 26:40.591 the right time to either a shooter or 26:40.591 --> 26:42.869 or our intelligence professionals . So , 26:42.869 --> 26:45.091 so we see it as a holistic architecture 26:45.091 --> 26:48.200 which as Mr Miller mentioned is a 26:48.200 --> 26:50.640 complicated environment and so building 26:50.640 --> 26:53.050 sort of a core open system is is really 26:53.050 --> 26:55.390 a key tenant for us so that we can 26:55.390 --> 26:58.510 ingest sensors and operate in a very 26:58.510 --> 27:01.280 diverse environment of sensing . Dad , 27:01.280 --> 27:03.910 john Gibson , sir . Okay , thanks . A 27:03.920 --> 27:06.720 really good question . Um , you know , 27:06.720 --> 27:09.850 it's not only about making our current 27:09.860 --> 27:12.920 kill chains better , it's about 27:12.920 --> 27:15.070 establishing new options and new kill 27:15.070 --> 27:18.690 change that we don't have today . So as 27:18.690 --> 27:20.640 you heard with , with networks and 27:20.640 --> 27:22.696 architecture and standardization and 27:22.696 --> 27:25.420 all those things , it's not just inside 27:25.420 --> 27:27.587 of the defensive fires , it's just not 27:27.587 --> 27:29.642 inside of the offensive fires . It's 27:29.642 --> 27:31.809 just not inside of the tactical or the 27:31.809 --> 27:33.864 strategic it's providing and looking 27:33.864 --> 27:35.976 for and exercising and learning about 27:35.976 --> 27:38.930 how can we do it differently to provide 27:38.930 --> 27:41.900 different capabilities . So it's a two . 27:41.910 --> 27:43.799 It's a two pronged attack . Do it 27:43.799 --> 27:46.450 better and do it differently . Thanks . 27:49.540 --> 27:51.540 Hi Colin clark . Breaking defense . 27:51.680 --> 27:54.510 Hopefully we can get something specific 27:54.510 --> 27:57.680 here . Um , what is the single 27:57.690 --> 28:01.120 hardest problem you are all grappling 28:01.120 --> 28:03.460 with right now and how are you fixing 28:03.460 --> 28:07.060 it ? So 28:07.070 --> 28:08.959 um , in this sense of the shooter 28:08.959 --> 28:11.126 architecture , we are taking sort of a 28:11.126 --> 28:13.530 deliberative approach in how we 28:13.530 --> 28:15.308 experiment as Mr nelson sort of 28:15.308 --> 28:18.880 mentioned and for me , my focus being 28:18.880 --> 28:21.350 sort of the material provider here is 28:21.470 --> 28:23.850 really doing it in a way that's open , 28:24.240 --> 28:27.540 that prepares us for this in uncertain 28:27.540 --> 28:29.540 environment in terms of our sensing 28:29.540 --> 28:31.850 capability . Right ? So that , that 28:31.850 --> 28:34.183 sounds easy , right ? We can talk about , 28:34.183 --> 28:36.183 hey , we've got to build a solution 28:36.183 --> 28:38.930 that integrates sensors and processes 28:38.930 --> 28:41.270 data , but we don't necessarily know 28:41.270 --> 28:43.326 what those sensors of the future are 28:43.326 --> 28:45.381 going to look like . We've got to be 28:45.381 --> 28:47.548 able to do it in a joint environment . 28:47.548 --> 28:49.770 And so so I think the biggest challenge 28:49.770 --> 28:51.950 for me is enabling that open system so 28:51.950 --> 28:53.950 that we can have the many different 28:53.950 --> 28:56.228 sensory modalities and sensor types to , 28:56.228 --> 28:57.950 to feed that sensor to shooter 28:57.950 --> 29:00.061 architecture and john rafferty , I'll 29:00.061 --> 29:02.283 throw it over to the next Yeah , thanks 29:02.283 --> 29:04.394 Colin Kahl . It's a , it's a , it's a 29:04.394 --> 29:06.660 great question . Uh for me , I'm I'm 29:06.660 --> 29:08.716 extremely competent that we've got , 29:08.716 --> 29:10.882 you know , world class team working on 29:10.882 --> 29:13.049 the technical end of this ? Uh and for 29:13.049 --> 29:15.271 my end , it's , it's absolutely how are 29:15.271 --> 29:17.271 we going to fight this ? How are we 29:17.271 --> 29:18.993 gonna be ready to exploit this 29:18.993 --> 29:21.049 capability when it's delivered ? Not 29:21.049 --> 29:23.160 just figure it out then . And so it's 29:23.160 --> 29:22.400 got to be a little bit of a leap of 29:22.400 --> 29:25.170 faith for all of us to recognize that 29:25.170 --> 29:27.337 this capability is going to be there . 29:27.337 --> 29:29.614 Uh and and begin to imagine , you know , 29:29.614 --> 29:31.837 what , what could be and that's kind of 29:31.837 --> 29:33.726 the that's the idea behind behind 29:33.726 --> 29:36.059 project convergence . Uh , but you know , 29:36.059 --> 29:35.950 brian hinted at it when he , when he 29:35.960 --> 29:38.460 mentioned , you know , our our interest 29:38.460 --> 29:41.170 in exploring the advantages of 29:41.180 --> 29:43.180 integrating offensive and defensive 29:43.180 --> 29:45.480 fires in certain scenarios to address a 29:45.480 --> 29:48.030 fire centric enemy one that's built 29:48.030 --> 29:50.252 around the fires , warfighting function 29:50.252 --> 29:52.419 of long range artillery protected by , 29:52.419 --> 29:54.530 by integrated air defenses . It's a , 29:54.530 --> 29:56.710 it's purpose built to offset our 29:56.710 --> 29:59.390 advantages . Uh , and so we're never 29:59.390 --> 30:01.279 going to match up one for one and 30:01.279 --> 30:03.279 cannon for canon or interceptors or 30:03.279 --> 30:05.510 anything . What we need to do is is 30:05.510 --> 30:08.320 fight smarter and uh , and , and , and , 30:08.330 --> 30:10.700 and have the , you know , defeat the 30:10.700 --> 30:13.200 arrow killed the archer approach of 30:13.200 --> 30:15.670 integrated fires . The problem is how 30:16.440 --> 30:18.496 I'm convinced now we can do it now . 30:18.496 --> 30:20.770 We've integrated our systems in ways 30:20.770 --> 30:23.070 that we didn't know we could and we 30:23.070 --> 30:25.237 know we're gonna have more sensors and 30:25.237 --> 30:27.237 more shooters just inside the fires 30:27.237 --> 30:29.459 were fighting function . But how are we 30:29.459 --> 30:31.514 going to see to it at what level ? I 30:31.514 --> 30:31.300 mean , gentleman over here mentioned 30:31.300 --> 30:33.356 are we organized , we have the right 30:33.356 --> 30:35.356 right units , right organizations , 30:35.356 --> 30:37.578 modernizations about more than just the 30:37.578 --> 30:39.800 M domain are . We've got to , we've got 30:39.800 --> 30:41.522 to really think hard about our 30:41.522 --> 30:43.467 organizations in the future . What 30:43.467 --> 30:45.689 level do we want to see to this ? Who's 30:45.689 --> 30:47.967 in charge of it and that kind of thing . 30:47.967 --> 30:47.200 That will be the really hard part and 30:47.200 --> 30:49.478 that's what I think about overwhelming , 30:50.340 --> 30:52.451 so from , I guess I would say from my 30:52.451 --> 30:54.784 foxhole , from a safety standpoint . Um , 30:54.784 --> 30:56.840 you know , we have the sayings , all 30:56.840 --> 30:58.951 sensors , best shooters , things like 30:58.951 --> 31:00.896 that from my , from my perspective 31:00.896 --> 31:03.062 right now it's the all sensors is kind 31:03.062 --> 31:05.229 of my problem set . We've got a ton of 31:05.229 --> 31:07.451 legacy systems that are gonna be around 31:07.451 --> 31:07.370 for a long time and they were built on 31:07.370 --> 31:09.730 sometimes unique architectures that 31:09.730 --> 31:11.786 aren't changing and and they must be 31:11.786 --> 31:13.786 incorporated and you continue to be 31:13.786 --> 31:15.620 used . We've got new innovative 31:15.630 --> 31:17.574 capabilities , a lot of commercial 31:17.574 --> 31:19.630 capabilities that are also coming on 31:19.630 --> 31:21.686 that are just phenomenal . But we've 31:21.686 --> 31:23.630 got to find a way to integrate all 31:23.630 --> 31:25.852 those . There is no single best message 31:25.852 --> 31:28.019 format , open , we use terms like open 31:28.019 --> 31:30.241 system formats and that's exactly where 31:30.241 --> 31:32.352 we need to go . But again , it's it's 31:32.352 --> 31:34.297 the integration of all sensors and 31:34.297 --> 31:36.352 again , space high altitude aviation 31:36.352 --> 31:38.574 platforms , you name it soldiers on the 31:38.574 --> 31:40.297 ground . It's that fundamental 31:40.297 --> 31:42.408 integration of that . Then , as as as 31:42.408 --> 31:44.297 Alex mentioned then there's other 31:44.297 --> 31:46.519 processes and challenges of what you do 31:46.519 --> 31:48.574 with the data . But for me right now 31:48.574 --> 31:50.686 it's it's that coalition of that data 31:50.686 --> 31:52.852 and bringing it into a meaningful type 31:52.852 --> 31:54.963 of compute environment that we can do 31:54.963 --> 31:57.130 something meaningful from it . And and 31:57.130 --> 31:56.240 of course all that has to be done 31:56.240 --> 31:58.407 rapidly . But that's a whole , another 31:58.407 --> 32:00.684 problem . But I think that would be my , 32:00.684 --> 32:00.170 that would be my answer your question . 32:01.140 --> 32:03.710 Okay , thanks . So I'm convinced . Like 32:03.720 --> 32:05.720 what john said and will , he said , 32:05.720 --> 32:07.831 we're gonna get the ones and zeros to 32:07.831 --> 32:09.942 work . All right , We're going to get 32:09.942 --> 32:11.870 things to communicate . Talk and 32:11.870 --> 32:13.926 architecture is that we designed for 32:13.926 --> 32:16.259 all the right reasons in the right ways . 32:16.259 --> 32:18.481 As john alluded to thinking a lot about 32:19.040 --> 32:21.040 what's that mean to the operational 32:21.040 --> 32:23.207 force and how we organize and decide . 32:23.207 --> 32:25.373 I think for me , especially the decide 32:25.373 --> 32:27.484 part when we establish new joint kill 32:27.484 --> 32:30.710 chains , we provide new options to our 32:30.710 --> 32:33.670 warfighters . How do , how do we decide 32:33.670 --> 32:36.610 which option to execute that today ? We 32:36.610 --> 32:38.800 don't have in our architectures that 32:38.800 --> 32:41.720 today may have multiple paths in which 32:41.720 --> 32:43.942 to execute that option . So I think the 32:43.942 --> 32:46.930 deciding piece is where fundamentally 32:46.940 --> 32:49.300 um , I spent a lot of my time and 32:49.300 --> 32:51.467 trying to think through , along with , 32:51.467 --> 32:53.633 as john described , what's it mean for 32:53.633 --> 32:55.967 the organizational side as well , where , 32:55.967 --> 32:58.133 where I think that's the hardest thing 32:58.133 --> 33:01.240 in front of us . Thanks . I'm Gonna 33:01.240 --> 33:04.950 Give You two . Um , we have the hardest , 33:05.340 --> 33:08.060 most important mission in the world 33:08.740 --> 33:12.270 period and we have a talent shortfall 33:12.940 --> 33:15.840 for high tech skills that is going to 33:15.840 --> 33:18.040 cripple us if we don't solve it . So 33:18.040 --> 33:19.984 when general Donahue says I need a 33:19.984 --> 33:22.096 single pane of glass for these things 33:22.096 --> 33:24.096 and we have to scramble to find the 33:24.096 --> 33:26.500 people that's a hard problem . The 2nd 33:26.500 --> 33:29.190 1 is , how do we protect your 33:29.190 --> 33:32.780 intellectual capital ? Been in a trade 33:32.780 --> 33:35.002 show for three days , How do we protect 33:35.002 --> 33:37.113 your intellectual capital . so we can 33:37.113 --> 33:39.224 protect our modernization . Those are 33:39.224 --> 33:41.430 hard problems and again I will say it 33:41.430 --> 33:43.652 and I will repeat it and this is a hill 33:43.652 --> 33:45.708 worth dying on . We have the hardest 33:45.708 --> 33:47.819 most important mission in the world . 33:53.140 --> 33:55.270 Any other questions for the panel . 34:03.640 --> 34:05.807 Thank you . Good morning and thank you 34:05.807 --> 34:08.140 for your time jim nickel from Microsoft . 34:08.640 --> 34:10.807 When you think about your charter as a 34:10.807 --> 34:14.150 CFT under a F . C . Is there an easy 34:14.150 --> 34:16.317 way to think about how you divide your 34:16.317 --> 34:20.280 focus between addressing identified in 34:20.280 --> 34:23.350 known gaps in national defense strategy 34:23.840 --> 34:27.710 20 2035 Plans vs the experimentation 34:27.710 --> 34:30.060 side of what's possible and could 34:30.070 --> 34:32.040 influence changes in different 34:32.040 --> 34:34.470 approaches to future warfare . 34:36.440 --> 34:39.580 Yeah , I'll start then I give my allies 34:39.580 --> 34:41.802 here a chance to take a crack at it . I 34:41.802 --> 34:43.858 think for me it's it's fundamentally 34:43.858 --> 34:46.080 because we're all different right ? You 34:46.080 --> 34:47.747 look at the portfolios of the 34:47.747 --> 34:49.858 priorities for which were established 34:49.858 --> 34:52.080 and to trying to get different outcomes 34:52.080 --> 34:54.302 for our army . Um , there are different 34:54.302 --> 34:56.136 capacities and capabilities that 34:56.136 --> 34:58.358 underpin our current stance and each of 34:58.358 --> 35:00.580 those different each of those different 35:00.580 --> 35:02.191 silos . So I think it's more 35:02.191 --> 35:05.540 importantly the the partition of work 35:05.550 --> 35:08.730 between current and future and whether 35:08.730 --> 35:11.880 that is on the acquisition side , 35:11.880 --> 35:13.991 experimentation side , the conceptual 35:13.991 --> 35:17.260 side or you pick the side , it's 35:17.260 --> 35:19.427 important to think through all of it . 35:19.427 --> 35:21.649 But it's important inside of what we do 35:21.649 --> 35:23.816 for cross functional teams is to do it 35:23.816 --> 35:25.982 together and to do it differently than 35:25.982 --> 35:28.860 how we got to this point . So for me , 35:28.870 --> 35:31.850 um inside of what I'm charged with , I 35:31.850 --> 35:35.580 think it's a balance between both given 35:35.580 --> 35:39.480 the stance inside of the branch I'll 35:39.490 --> 35:41.768 just tag on . It's certainly a balance , 35:41.768 --> 35:43.934 you know , again as he mentioned , our 35:43.934 --> 35:46.790 portfolios are unique to to what we're 35:46.790 --> 35:49.160 doing . I think from from my 35:49.160 --> 35:51.327 perspective it's really the challenges 35:51.327 --> 35:53.750 is developing or understanding and 35:53.760 --> 35:55.593 teasing out those new integrated 35:55.593 --> 35:57.790 capabilities . We tend to use 35:57.800 --> 35:59.578 interoperability and integrated 35:59.578 --> 36:01.744 incorrectly . You know , interoperable 36:01.744 --> 36:03.967 is one thing to things that can operate 36:03.967 --> 36:06.133 and perform together . But how do what 36:06.133 --> 36:08.356 happens when I put a new type of sensor 36:08.356 --> 36:10.578 with a different type of weapon and you 36:10.578 --> 36:12.744 have a fundamentally different and new 36:12.744 --> 36:14.633 capability that derives from that 36:14.633 --> 36:16.689 combination that's integration . And 36:16.689 --> 36:16.360 really that I think that's where we're 36:16.360 --> 36:19.540 trying to find working again . And it's 36:19.540 --> 36:21.651 a , it's an absolute partnership with 36:21.651 --> 36:23.873 assault I think , you know , and that's 36:23.873 --> 36:26.096 why I'm thrilled to death that assaults 36:26.096 --> 36:28.262 leading this panel to show you that we 36:28.262 --> 36:30.207 it's we mean it and we can't do it 36:30.207 --> 36:32.429 without the PM's . They've got the area 36:32.429 --> 36:34.707 of the expertise to be able to do that . 36:34.707 --> 36:34.540 We've got the laboratories and the 36:34.550 --> 36:36.772 scientists that are performing that and 36:36.772 --> 36:38.828 it's really that synchronization and 36:38.828 --> 36:41.030 integration of of those resources uh 36:41.040 --> 36:43.151 and talent that helps bring out those 36:43.151 --> 36:45.373 new capabilities . I think that's how I 36:45.373 --> 36:47.151 would address it anybody else , 36:50.630 --> 36:52.686 this is something that might keep me 36:52.686 --> 36:54.574 awake tonight . Thank you because 36:54.574 --> 36:56.686 because what I keep trying to wrap my 36:56.686 --> 36:58.630 head around is is uh is you know , 36:58.630 --> 37:00.797 reading that charter , you know , when 37:00.797 --> 37:02.797 I first got to fort sill and uh and 37:02.797 --> 37:05.019 sometimes I go back and look at some of 37:05.019 --> 37:07.019 my notebooks from you know , almost 37:07.019 --> 37:09.241 three years ago and I look at the , you 37:09.241 --> 37:08.590 know , how I was describing what we 37:08.590 --> 37:10.757 were doing and how we were approaching 37:10.757 --> 37:12.923 things and it looks childish . So like 37:12.923 --> 37:14.979 what I what I know now versus what I 37:14.979 --> 37:17.201 knew then uh I'm not sure how I would , 37:17.201 --> 37:19.423 how I would redo the charter . But what 37:19.423 --> 37:21.479 I might add in there is , don't stop 37:21.479 --> 37:23.646 thinking about the problem , don't get 37:23.646 --> 37:25.757 laser focused on the solution and the 37:25.757 --> 37:29.030 path that we're on and ah Don't , you 37:29.030 --> 37:31.197 know , is the chief told us during our 37:31.197 --> 37:33.308 last update to them is keep your foot 37:33.308 --> 37:32.780 on the gas . Right ? So what we're 37:32.780 --> 37:34.947 delivering in 23 is really important . 37:34.947 --> 37:37.169 But thinking about how we spiral in the 37:37.169 --> 37:39.002 improvements after that is uh is 37:39.002 --> 37:41.058 something that uh that if I could go 37:41.058 --> 37:43.280 back and rewrite the charter , it would 37:43.280 --> 37:45.502 probably be something like that because 37:45.502 --> 37:45.440 you're going to learn a lot along the 37:45.440 --> 37:48.620 way and the enemy is going to do things 37:48.630 --> 37:50.741 and we're going to learn how to fight 37:50.741 --> 37:52.741 as a combined arms team a whole lot 37:52.741 --> 37:54.741 better to uh and that's what that's 37:54.741 --> 37:56.741 what we do best and better than any 37:56.741 --> 37:56.330 army in the world . So it's probably 37:56.330 --> 37:59.970 this thinking aspect of it well , and 37:59.970 --> 38:02.137 you didn't ask me , but I'm gonna jump 38:02.137 --> 38:04.137 in here and say , you know , from a 38:04.137 --> 38:06.303 material side like general , we've got 38:06.303 --> 38:08.526 to do it differently . And my job is to 38:08.526 --> 38:10.637 provide them the options so that they 38:10.637 --> 38:12.026 can make decisions about 38:12.026 --> 38:14.248 experimentation , future capability and 38:14.248 --> 38:16.414 delivering it now right in our P and T 38:16.414 --> 38:18.581 portfolio we've we're delivering now , 38:18.581 --> 38:20.637 but we're also experimenting options 38:20.637 --> 38:22.692 for 10 , 15 years from now partnered 38:22.692 --> 38:24.692 with partnered with our R . S and T 38:24.692 --> 38:26.748 partners . So , so as an acquisition 38:26.748 --> 38:28.581 professional , I've got to do it 38:28.581 --> 38:30.803 differently in order to give them those 38:30.803 --> 38:32.859 options so that they can drive those 38:32.859 --> 38:34.581 priorities for the acquisition 38:34.581 --> 38:36.914 community . But thanks for the question . 38:36.914 --> 38:39.920 I appreciate it . Right . I think I 38:39.920 --> 38:42.220 think we're concluding here , I just 38:42.220 --> 38:44.220 want to say thank you very much the 38:44.220 --> 38:46.164 panel for for joining us . A great 38:46.164 --> 38:48.220 discussion , appreciate , appreciate 38:48.220 --> 38:48.060 that . And thank you for joining , 38:48.060 --> 38:48.640 appreciate it .