WEBVTT 00:00.740 --> 00:02.851 Ladies and gentlemen , this is rusted 00:02.851 --> 00:04.796 OsD Public Affairs . Thank you for 00:04.796 --> 00:06.796 calling in . For today's brief . We 00:06.796 --> 00:08.851 have Lieutenant General Dennis crawl 00:08.851 --> 00:10.851 the director of command and control 00:10.851 --> 00:13.018 communications and computers and cyber 00:13.018 --> 00:14.851 as well as the Chief Information 00:14.851 --> 00:17.580 Officer . Joint Staff J six Here today 00:17.580 --> 00:19.524 to answer your questions about the 00:19.524 --> 00:22.530 Joint Jad C2 and its implementation 00:22.530 --> 00:25.570 plan . We have about 45 minutes today 00:25.570 --> 00:28.890 for this brief . I will call on the 00:28.890 --> 00:31.160 journalist as this continues . You'll 00:31.160 --> 00:33.216 get an opportunity to ask a question 00:33.400 --> 00:35.567 and then a follow up before we move on 00:35.567 --> 00:37.400 to the next one . After we cycle 00:37.400 --> 00:39.567 through the group , We'll go ahead and 00:39.567 --> 00:42.210 start again until we've either closed 00:42.210 --> 00:45.500 on the 45 minutes or we've 00:45.510 --> 00:47.900 all the questions are done and then 00:47.900 --> 00:49.956 general Colin have an opportunity to 00:49.956 --> 00:52.178 close out this session . So with that , 00:52.178 --> 00:54.400 I'm gonna turn it over to general crawl 00:54.400 --> 00:56.400 for an opening comment . Look , I I 00:56.400 --> 00:58.700 really appreciate the opportunity to 00:58.710 --> 01:01.860 explain just briefly where we are in 01:01.860 --> 01:04.380 the story on the department's efforts 01:04.380 --> 01:06.480 to deliver a true joint all domain 01:06.480 --> 01:09.310 command and control capability uh and 01:09.310 --> 01:11.477 rather than spending a long time in an 01:11.477 --> 01:13.699 opener , I really prefer to get to your 01:13.699 --> 01:16.640 questions to leave us plenty of time uh 01:16.650 --> 01:18.820 to give the best answer I can based on 01:18.820 --> 01:20.987 where we are in this journey . So what 01:20.987 --> 01:22.876 I'd like to do is just as a brief 01:22.876 --> 01:25.450 reminder , uh kind of walk back . This 01:25.450 --> 01:27.600 is the fourth artifact and the final 01:27.600 --> 01:29.610 artifact in the delivery of the 01:29.610 --> 01:32.310 planning for jazzy to delivery . This 01:32.310 --> 01:34.790 started some time ago when the Deputy 01:34.790 --> 01:37.290 secretary authored the cross functional 01:37.290 --> 01:40.220 team charter , which really provided 01:40.230 --> 01:44.070 the workspace . Place headspace for 01:44.080 --> 01:46.247 all the various efforts throughout all 01:46.247 --> 01:48.450 of D . O . D . On the OS decide the 01:48.450 --> 01:51.410 military side . And even in some of the 01:51.410 --> 01:54.240 supporting elements to come together . 01:54.250 --> 01:57.950 One to map where we were uh in the 01:57.950 --> 01:59.950 efforts that we've had , you know , 01:59.950 --> 02:02.006 knowing illuminating those areas and 02:02.006 --> 02:04.061 then starting to formulate where the 02:04.061 --> 02:06.520 department needed to go . There was a 02:06.530 --> 02:09.330 really a sincere effort to put that 02:09.330 --> 02:11.441 together and there was clearly a lack 02:11.441 --> 02:14.250 of structure and operational or 02:14.250 --> 02:16.710 organizational design on how we were to 02:16.710 --> 02:19.320 move forward . Uh I've said in the past , 02:19.330 --> 02:22.260 this effort to deliver a jazzy to 02:22.260 --> 02:24.540 capability is not novel . The 02:24.540 --> 02:26.762 department has been on this journey and 02:26.762 --> 02:28.818 several other attempts uh some which 02:28.818 --> 02:31.430 have been marginally successful uh and 02:31.430 --> 02:34.220 some which have failed altogether . And 02:34.220 --> 02:36.442 this was a different approach , quite a 02:36.442 --> 02:38.387 different approach in the starting 02:38.387 --> 02:40.442 point with that CFT Charter . One of 02:40.442 --> 02:42.498 the reasons this did not end up in a 02:42.498 --> 02:44.164 typical program office as the 02:44.164 --> 02:47.960 department has often done is speed . 02:48.640 --> 02:51.280 The Deputy Secretary and Vice Chairman 02:51.280 --> 02:53.502 of the Joint Chiefs wanted this to move 02:53.502 --> 02:56.110 quickly but smartly and also wanted to 02:56.110 --> 02:58.580 accept more risk than we take in 02:58.580 --> 03:00.770 traditional programs , meaning that we 03:00.770 --> 03:03.210 have an appetite and expect to fail 03:03.210 --> 03:07.170 fast and then fix and then scale and so 03:07.170 --> 03:09.226 this apparatus that was developed to 03:09.226 --> 03:11.281 define the problem and layout , that 03:11.281 --> 03:13.448 roadmap ahead and oversee the delivery 03:13.448 --> 03:15.337 of these . Uh these very specific 03:15.337 --> 03:17.560 elements was created that was about a 03:17.560 --> 03:19.790 year ago , maybe a little bit longer 03:19.790 --> 03:21.957 ago , maybe a year . And some change . 03:22.040 --> 03:24.207 The next document that came out really 03:24.207 --> 03:26.370 are seminal piece was the strategy 03:26.620 --> 03:29.160 signed by the secretary himself . And 03:29.160 --> 03:31.740 this was really important for us to 03:31.740 --> 03:34.810 determine the end state on where Jared 03:34.810 --> 03:37.040 C2 was heading to make sure that we 03:37.040 --> 03:40.120 could prepare ourselves for that fight 03:40.120 --> 03:42.320 that we expect not only today but also 03:42.320 --> 03:45.080 tomorrow . And in very simple terms , 03:45.090 --> 03:48.250 this was the recognition that data and 03:48.250 --> 03:50.840 data centric city was at the heart of 03:50.840 --> 03:53.130 success in our next war fight . We are 03:53.130 --> 03:56.210 awash and sensor data unable to keep up 03:56.210 --> 03:58.680 the really the human intensive labor 03:58.690 --> 04:00.690 and at the pace we were moving , we 04:00.690 --> 04:02.634 couldn't take advantage of it . We 04:02.634 --> 04:04.634 could not bring in machine learning 04:04.634 --> 04:07.990 artificial intelligence uh to to really 04:07.990 --> 04:10.110 look at the make sense aspect of the 04:10.110 --> 04:12.277 data that we were receiving much of it 04:12.277 --> 04:14.110 hit the cutting room floor . And 04:14.110 --> 04:16.277 finally we couldn't get to the act the 04:16.277 --> 04:18.620 most critical point of making sure that 04:18.620 --> 04:20.960 information was distilled so that war 04:20.960 --> 04:23.182 fighters and decision makers could make 04:23.182 --> 04:25.130 the best decision at the speed of 04:25.130 --> 04:26.990 relevance that was needed . That 04:26.990 --> 04:29.460 strategy laid out clear lines of effort , 04:30.140 --> 04:32.420 specifically what it was we needed to 04:32.420 --> 04:35.170 accomplish and really those large bins 04:35.170 --> 04:37.910 and buckets . Um while that document is 04:37.910 --> 04:40.021 classified for a host of reasons , we 04:40.021 --> 04:42.270 were able to recently release an 04:42.270 --> 04:45.000 unclassified version which at least 04:45.000 --> 04:47.420 provides a sense of those lines of 04:47.420 --> 04:49.364 effort and where the department is 04:49.364 --> 04:51.420 trying to go with them . So once you 04:51.420 --> 04:53.630 know where you want to go , the next 04:53.630 --> 04:55.852 document in that series was the posture 04:55.852 --> 04:58.090 review . And that really is simply 04:58.100 --> 05:00.500 looking at your gaps if you know where 05:00.500 --> 05:02.611 you want to go and there's some areas 05:02.611 --> 05:04.667 you can't go . You got to define why 05:04.667 --> 05:06.611 that posture review took a look at 05:06.611 --> 05:08.667 those gaps to find them very clearly 05:08.667 --> 05:11.170 and then prioritize them all with an 05:11.170 --> 05:13.420 eye toward funding and also those 05:13.420 --> 05:14.920 pieces that need to have a 05:14.920 --> 05:17.030 developmental priority both in the R 05:17.030 --> 05:18.808 and D and S and T communities . 05:19.040 --> 05:21.262 Sometimes we knew where we wanted to go 05:21.262 --> 05:23.540 but technology may not have been there . 05:23.540 --> 05:25.651 And so we took a look at what it took 05:25.651 --> 05:27.651 and how to prioritize those to fill 05:27.651 --> 05:29.960 those gaps . But the seminal document 05:30.440 --> 05:32.496 that we've been waiting for and it's 05:32.496 --> 05:34.440 been difficult for the reasons you 05:34.440 --> 05:36.607 might expect . It's so comprehensive . 05:36.607 --> 05:38.829 But the document that really that we've 05:38.829 --> 05:40.996 been waiting for is the implementation 05:40.996 --> 05:43.051 plan which the Deputy secretary just 05:43.051 --> 05:45.162 recently signed and the reason that's 05:45.162 --> 05:46.662 important . The department 05:46.662 --> 05:48.730 unfortunately has examples over the 05:48.730 --> 05:50.897 past couple of decades , at least that 05:50.897 --> 05:52.952 I'm aware of where we've got up to . 05:52.952 --> 05:54.897 That culmination point of defining 05:54.897 --> 05:56.952 where we want to go and those gaps . 05:56.952 --> 05:59.008 But the delivery mechanism , the how 05:59.008 --> 06:00.674 we're gonna get there ? Who's 06:00.674 --> 06:02.674 responsible , what order do you put 06:02.674 --> 06:04.786 these in ? What are the prerequisites 06:04.786 --> 06:06.452 to make sure that you have an 06:06.452 --> 06:08.619 actionable plan that can be executed . 06:08.619 --> 06:10.674 And finally , those milestones which 06:10.674 --> 06:12.897 include funding , if those are absent , 06:12.897 --> 06:15.008 what you end up with is a really neat 06:15.008 --> 06:17.170 story , a grand idea , but really 06:17.170 --> 06:19.170 nothing that comes off the conveyor 06:19.170 --> 06:21.337 belt at the other end and this is what 06:21.337 --> 06:24.120 the the I plan actually does for us is 06:24.120 --> 06:26.190 it takes a look very clearly at 06:26.190 --> 06:30.010 specific and prioritized plans . How 06:30.010 --> 06:32.010 are we going to accomplish the very 06:32.010 --> 06:34.720 things that we said again in what order ? 06:34.730 --> 06:37.140 How do you measure them ? How do we 06:37.140 --> 06:39.630 leverage the boards , bureaus , working 06:39.630 --> 06:41.852 groups , cells , committees that are in 06:41.852 --> 06:44.600 the building to empower them uh to move 06:44.600 --> 06:48.480 these to fruition . Um it does 06:48.490 --> 06:50.750 provide a sense of shared awareness . 06:51.740 --> 06:53.851 You don't always know what others are 06:53.851 --> 06:55.851 working on . So the I plan captures 06:55.851 --> 06:57.851 that in its fullest so you can look 06:57.851 --> 06:59.900 across your lane of expertise , be 06:59.900 --> 07:02.060 informed by some of the other efforts 07:02.070 --> 07:04.370 and maybe that provides opportunity to 07:04.370 --> 07:07.000 come up with a better way . Not all 07:07.000 --> 07:09.180 overlap is bad , but if your Venn 07:09.180 --> 07:11.690 diagram has too much vent in it , uh 07:11.700 --> 07:13.922 then you're really wasting resources at 07:13.922 --> 07:16.170 that point . So , increasing awareness 07:16.380 --> 07:19.910 with the I plan is also a residual 07:19.910 --> 07:22.290 benefit . The other thing it does is it 07:22.290 --> 07:24.457 allows us to to look at these emerging 07:24.457 --> 07:26.623 technologies and figure out where they 07:26.623 --> 07:29.120 fit in the process rather than simply 07:29.120 --> 07:32.200 focusing on what is directly in front 07:32.200 --> 07:34.820 of us , but anticipating that next need , 07:34.830 --> 07:37.300 anticipating the threat and how we can 07:37.300 --> 07:39.522 leverage what may not even be available 07:39.522 --> 07:42.120 today to meet that landing spot when it 07:42.120 --> 07:44.740 does become available . So very 07:44.740 --> 07:47.110 importantly in that implementation plan , 07:47.170 --> 07:49.170 the front end of it captures what I 07:49.170 --> 07:51.480 just described . The back end of it is 07:51.480 --> 07:53.810 going to remain electronic , meaning 07:53.810 --> 07:56.360 that there is some , it's a malleable 07:56.360 --> 07:59.120 docking that we can go in and again 07:59.130 --> 08:02.120 leverage what we learn on the fly and 08:02.120 --> 08:04.410 not lock ourselves into something that 08:04.410 --> 08:08.320 we can't move or advantage . So that 08:08.320 --> 08:10.264 piece really takes a look at who's 08:10.264 --> 08:12.730 responsible , the five Ws plus the H of 08:12.730 --> 08:15.360 how we get there are all captured in 08:15.360 --> 08:17.560 that implementation plan . So we can 08:17.560 --> 08:19.504 point to who has the lead , who is 08:19.504 --> 08:21.310 providing support and the most 08:21.310 --> 08:23.199 important aspect that I mentioned 08:23.199 --> 08:24.977 before are those milestones for 08:24.977 --> 08:27.120 delivery . Have we satisfied the 08:27.120 --> 08:29.342 prerequisites ? Have we even identified 08:29.342 --> 08:31.564 what they are ? Is this the right order 08:31.564 --> 08:34.110 of March ? Do we have a good funded 08:34.110 --> 08:36.332 delivery timetable ? That makes sense . 08:36.540 --> 08:38.762 Do we have a testing apparatus lined up 08:38.762 --> 08:40.929 with this so we can learn very quickly 08:41.040 --> 08:43.096 and most importantly , do we have an 08:43.096 --> 08:45.318 eye to the threat so that we don't lock 08:45.318 --> 08:47.484 ourselves into something that we would 08:47.484 --> 08:49.650 eventually deliver that will not meet 08:49.660 --> 08:52.020 success on the battlefield . That's why 08:52.020 --> 08:54.240 the implementation plan is so critical 08:54.350 --> 08:56.760 and important to what we do . Uh , it's 08:56.760 --> 08:59.190 classified for reasons you might expect . 08:59.200 --> 09:01.570 I can talk a little bit and provide 09:01.570 --> 09:04.460 even some examples of how this may come 09:04.460 --> 09:06.790 together , but one of the areas when 09:06.790 --> 09:08.957 you prioritize against vulnerabilities 09:08.957 --> 09:11.068 and threats , that's not something we 09:11.068 --> 09:13.170 would like to advertise to our 09:13.170 --> 09:15.990 adversaries . And also you might expect 09:15.990 --> 09:18.710 that as we partner with industry to 09:18.710 --> 09:21.270 assist us in moving forward . Many of 09:21.270 --> 09:23.640 these contracts have not been let uh 09:23.640 --> 09:26.220 and it's unwise to to reveal 09:26.230 --> 09:28.174 responsible parties and the orders 09:28.174 --> 09:30.341 which we might prosecute some of those 09:30.341 --> 09:32.563 before . We have the contractual pieces 09:32.563 --> 09:34.810 in place . Uh , so for those reasons 09:34.810 --> 09:36.643 and a few others , the documents 09:36.643 --> 09:38.866 classified , but the idea and sentiment 09:38.866 --> 09:41.088 that I gave you and the level of detail 09:41.088 --> 09:43.310 there in is real . I don't believe I've 09:43.310 --> 09:45.143 exaggerated any of it . The most 09:45.143 --> 09:47.950 crucial aspect is now in front of us . 09:47.950 --> 09:50.670 We have all four parts and we've talked 09:50.670 --> 09:52.503 some time ago and I've said very 09:52.503 --> 09:54.337 specifically this is the year of 09:54.337 --> 09:56.337 delivery and that's exactly what we 09:56.337 --> 09:58.690 intend to do . I think we've talked , 09:58.700 --> 10:00.890 we've studied , we've interacted , 10:00.930 --> 10:03.200 we've mapped its now time to put these 10:03.200 --> 10:06.370 together and learn by doing so with 10:06.370 --> 10:10.000 that . I welcome your questions . Thank 10:10.000 --> 10:12.800 you general . So media as a reminder . 10:12.810 --> 10:14.921 You get an opportunity for a question 10:14.921 --> 10:17.088 and then a follow up before we move on 10:17.088 --> 10:19.199 to the next question . First question 10:19.199 --> 10:21.254 goes to Brandi Vincent with Next gov 10:21.640 --> 10:23.751 thanks for us and thank you so much . 10:23.751 --> 10:26.029 Lieutenant General Karl for doing this . 10:26.029 --> 10:28.084 Um you sort of alluded to this , but 10:28.084 --> 10:29.918 there was a variety of different 10:29.918 --> 10:32.084 inspirations for Jared C . Two . There 10:32.084 --> 10:34.290 was also a D . O . D . Lead study on 10:34.300 --> 10:36.740 Russian new generation warfare a few 10:36.740 --> 10:39.330 years ago that found that multi domain 10:39.330 --> 10:41.720 battle is how Russia might be beaten in 10:41.720 --> 10:43.920 the next generation of war And in some 10:43.920 --> 10:46.600 parts , I think Jared C2 grew from that 10:46.600 --> 10:48.767 idea and that concept . Can you please 10:48.767 --> 10:50.989 elaborate a little bit on how important 10:50.989 --> 10:53.720 Jazzy to capabilities might be amid 10:53.720 --> 10:56.100 this ongoing and evolving conflict 10:56.100 --> 10:57.933 surrounding Russia's invasion of 10:57.933 --> 11:00.150 Ukraine and particularly if the US 11:00.150 --> 11:02.900 military becomes more involved . That's 11:02.910 --> 11:05.260 that's a great question . So I will say 11:05.270 --> 11:07.420 very clearly that I don't think it 11:07.420 --> 11:10.010 matters what we're pursuing , what 11:10.010 --> 11:13.150 conflict or what challenge we're facing . 11:13.540 --> 11:16.660 The speed of . You know , First of all , 11:16.660 --> 11:18.600 the volume of information is only 11:18.600 --> 11:21.490 growing exponentially . Uh and we have 11:21.490 --> 11:24.360 the ability with the sensors , hardly 11:24.360 --> 11:26.416 anything is private anymore . Almost 11:26.416 --> 11:28.470 the unblinking , all seeing eye is 11:28.470 --> 11:30.980 everywhere . So we're awash in sensor 11:30.980 --> 11:33.860 data . We also know that in order to 11:33.860 --> 11:36.193 take and make sense of that sensor data , 11:36.193 --> 11:38.416 we've got to be able to bring the human 11:38.416 --> 11:40.710 machine interface alive . We need to be 11:40.710 --> 11:43.090 aided to know what information is 11:43.090 --> 11:45.010 important and at what time it's 11:45.010 --> 11:47.288 important , You know , back , you know , 11:47.288 --> 11:49.066 20 or 30 years ago having human 11:49.066 --> 11:51.288 analysts wade through full motion video 11:51.288 --> 11:53.510 for example looking for that needle in 11:53.510 --> 11:55.677 a haystack , we're now looking for the 11:55.677 --> 11:57.788 needle in the needle stack . This has 11:57.788 --> 11:59.899 become even more challenging and most 11:59.899 --> 12:02.066 importantly at speed . So if you think 12:02.066 --> 12:04.232 about whether it's the Russian Ukraine 12:04.232 --> 12:06.454 conflict or any conflict or even how we 12:06.454 --> 12:08.566 spend our money in the department for 12:08.566 --> 12:10.800 exercising testing , uh , it's about 12:10.800 --> 12:14.110 making the smartest decision at speed 12:14.120 --> 12:16.064 and that's the difference . If the 12:16.064 --> 12:18.120 clock wasn't on us , this might be a 12:18.120 --> 12:20.470 different , a different pursuit meaning 12:20.470 --> 12:22.526 you could take your time , you could 12:22.526 --> 12:24.303 make a lot of mistakes , you'll 12:24.303 --> 12:26.470 eventually get to the answer and if it 12:26.470 --> 12:26.360 didn't matter when you got to the 12:26.360 --> 12:28.582 answer , uh , then I guess that process 12:28.582 --> 12:30.920 would be good enough , but a an answer 12:30.920 --> 12:32.753 good enough for a perfect answer 12:32.753 --> 12:34.920 delivered too late isn't good enough . 12:34.920 --> 12:37.100 And that's really our dilemma . So 12:37.100 --> 12:39.156 we've talked about , you know , in a 12:39.156 --> 12:41.267 lot of our war college , is this idea 12:41.267 --> 12:43.100 of Boyd's boogaloo being able to 12:43.100 --> 12:45.322 operate in a decision cycle faster than 12:45.322 --> 12:47.489 your adversary . What you described in 12:47.489 --> 12:50.080 that multi domain , multi battle , the 12:50.090 --> 12:52.090 power of information has never been 12:52.090 --> 12:53.990 stronger . The machine . Human 12:53.990 --> 12:55.990 interface , the need has never been 12:55.990 --> 12:58.250 greater and Jared C2 is attempting to 12:58.250 --> 13:00.306 leverage that so that we can deliver 13:00.306 --> 13:02.194 that the best decision to the war 13:02.194 --> 13:04.780 fighter in the fastest time . So I 13:04.780 --> 13:07.002 think it's as relevant as ever and will 13:07.002 --> 13:09.510 be more so going forward . Thank you so 13:09.510 --> 13:11.677 much for that . And then just a really 13:11.677 --> 13:13.930 quick follow up , we understand that 13:13.940 --> 13:17.050 the implementation plan um was on 13:17.060 --> 13:19.880 Deputy Secretary Hicks desk for at 13:19.880 --> 13:22.260 least a couple of weeks . The plan is 13:22.260 --> 13:24.810 classified , but can you speak at all 13:24.820 --> 13:27.900 to any of the revisions or additions 13:27.900 --> 13:30.930 that you or she contributed broadly to 13:30.930 --> 13:33.760 it ? I can I I think we can talk at 13:33.760 --> 13:36.330 least in some broad terms . Uh one this 13:36.330 --> 13:39.420 took a little bit of time because I'll 13:39.420 --> 13:41.587 be honest , I have never been involved 13:41.587 --> 13:44.520 in a product or a process in my 35 13:44.520 --> 13:46.910 years of commission service where I had 13:46.910 --> 13:49.490 so much leadership support and personal 13:49.490 --> 13:51.660 involvement and I will say that the 13:51.660 --> 13:55.030 Deputy Secretary dr hicks understands 13:55.030 --> 13:57.920 this extremely well . Uh She knows 13:57.920 --> 14:00.870 where she wants to go uh and know some 14:00.870 --> 14:03.092 of the pitfalls in the past of what has 14:03.092 --> 14:05.203 prevented us from getting there . She 14:05.203 --> 14:07.314 has partnered very well with the vice 14:07.314 --> 14:09.370 chairman , both the previous one and 14:09.370 --> 14:11.592 the current one and they are intimately 14:11.592 --> 14:13.703 involved in the details of delivery . 14:14.140 --> 14:16.530 So that takes a little bit of time and 14:16.530 --> 14:18.641 I'll tell you right now , I call that 14:18.641 --> 14:20.860 welcomed time , that's where your 14:20.860 --> 14:23.520 leadership rolls up sleeves and really 14:23.520 --> 14:25.970 works with you to ensure that there's a 14:25.970 --> 14:28.290 common understanding the challenge is 14:28.290 --> 14:30.910 properly scoped and set and I think , 14:30.910 --> 14:33.021 you know , if I look at what dr hicks 14:33.021 --> 14:35.132 was really looking at was making sure 14:35.132 --> 14:37.500 that the i plan uh really in that 14:37.500 --> 14:39.611 forensic decomposition of working our 14:39.611 --> 14:41.444 way from delivery all the way to 14:41.444 --> 14:43.500 assignments had all the pieces in it 14:43.740 --> 14:46.090 that we weren't overlooking a parts 14:46.090 --> 14:47.868 that would be critical again to 14:47.868 --> 14:49.812 informing how we prioritize how we 14:49.812 --> 14:52.500 budget , what policy , either , you 14:52.500 --> 14:55.470 know , limitations or empowerment were 14:55.470 --> 14:58.520 already in place . Uh So that was again 14:58.530 --> 15:01.710 uh phenomenally welcomed interaction 15:01.710 --> 15:03.877 with leadership to get there . And you 15:03.877 --> 15:05.877 think about the other aspect of the 15:05.877 --> 15:08.099 players involved in this . This isn't a 15:08.099 --> 15:10.043 single service . It's not just one 15:10.043 --> 15:12.321 program office , it's the entire D . O . 15:12.321 --> 15:15.560 D . Uh so that the vastness of this , 15:15.940 --> 15:17.830 we also have D . O . D . Efforts 15:17.840 --> 15:20.173 underway as I'm sure most of , you know , 15:20.540 --> 15:23.380 project Overmatch project convergence A 15:23.380 --> 15:26.270 BMS . They're all alive and well and 15:26.270 --> 15:28.492 while many of them are kind of in their 15:28.492 --> 15:30.492 nation areas and expertise and what 15:30.492 --> 15:33.160 they're looking for . Service and cocom 15:33.170 --> 15:35.750 acumen and prowess they feed into this . 15:35.760 --> 15:37.927 So that had to be considered as well . 15:37.927 --> 15:40.110 Not stopping those activities but 15:40.110 --> 15:42.410 harnessing their energy and direction 15:42.420 --> 15:44.698 but making sure that we're not getting , 15:44.698 --> 15:46.864 you know divergent or working at cross 15:46.864 --> 15:49.080 purposes . All of those culminated in 15:49.080 --> 15:51.247 taking just a little more time to make 15:51.247 --> 15:53.358 sure we got this right . And I'm also 15:53.358 --> 15:55.760 very reassured that by keeping the back 15:55.760 --> 15:57.700 half of this electronic we're not 15:57.700 --> 15:59.867 locked into what we knew on the day of 15:59.867 --> 16:02.100 signature . Thank you so much and 16:02.100 --> 16:04.770 thanks for us . Thank you general and 16:04.770 --> 16:06.881 thank you Brandy . Next question goes 16:06.881 --> 16:08.881 to angus with military technology . 16:09.940 --> 16:12.218 Hello . Thanks for us . Thanks general . 16:12.840 --> 16:14.730 I was struck reading the summary 16:14.730 --> 16:17.800 document that under line of effort to . 16:17.800 --> 16:21.720 There's a huge task there of education 16:21.720 --> 16:24.770 and training . It mentions educating 16:24.770 --> 16:28.680 leaders within defense and also the 16:28.690 --> 16:30.357 D . O . D . Workforce must be 16:30.357 --> 16:32.680 proficient in identifying institutional 16:32.680 --> 16:34.569 changes That you're gonna have to 16:34.569 --> 16:36.736 implement in order to get this through 16:36.970 --> 16:38.970 and working . But I'm also thinking 16:38.970 --> 16:41.026 that that it must go way beyond that 16:41.026 --> 16:42.803 because you've got intelligence 16:42.803 --> 16:45.026 agencies who we know have had their own 16:45.026 --> 16:47.390 journey over the last 20 years of 16:47.390 --> 16:49.390 whether they're sharing too much or 16:49.390 --> 16:51.557 whether they're not sharing enough and 16:51.557 --> 16:53.612 allies as well who have their own uh 16:53.612 --> 16:56.870 bespoke processes in place already . 16:56.880 --> 16:59.102 How are you going to make that all work 16:59.102 --> 17:00.658 together ? And what are the 17:00.658 --> 17:02.880 consequences of not getting everyone on 17:02.880 --> 17:04.713 the same page ? Well we live the 17:04.713 --> 17:06.936 consequences of not getting everyone on 17:06.936 --> 17:09.102 the same page . That's what status quo 17:09.102 --> 17:11.740 is . Uh So I think you know the risk is 17:11.750 --> 17:14.010 continuing the current trajectory apart 17:14.010 --> 17:16.260 from Jazzy too . That would be a risk . 17:16.640 --> 17:18.610 Uh This is actually designed as an 17:18.610 --> 17:21.660 attempt to bring those uh entities 17:21.660 --> 17:23.716 together so that we can look at this 17:23.716 --> 17:25.827 problem holistically . And the reason 17:25.827 --> 17:27.960 that line of effort is important is 17:27.960 --> 17:31.210 that we we say frequently that we are 17:31.210 --> 17:34.720 pursuing data centric city years ago , 17:34.720 --> 17:38.300 the idea was really network . In fact 17:38.300 --> 17:40.467 many of the writers in these technical 17:40.467 --> 17:42.580 forums have written a lot on network 17:42.580 --> 17:45.210 centric city and at the time that was 17:45.210 --> 17:47.210 really the buzzword . We were gonna 17:47.210 --> 17:49.432 mesh ourselves to make sure information 17:49.432 --> 17:51.680 had a pathway . And then we realized 17:51.690 --> 17:53.801 that really was an element was not an 17:53.801 --> 17:56.800 element on the periodic table of C . 17:56.800 --> 17:59.350 Two but more of a compound it had other 17:59.350 --> 18:01.572 parts you could break apart and then we 18:01.572 --> 18:03.920 started getting focused on application 18:04.120 --> 18:06.120 eccentricity , it was all about the 18:06.120 --> 18:08.287 application and that went on for a few 18:08.287 --> 18:10.453 years and we realized we gotta there's 18:10.453 --> 18:12.509 something else to this . And finally 18:12.509 --> 18:14.842 the latent discovery for us was uh data . 18:15.140 --> 18:17.362 Data is the element that we're pursuing 18:17.540 --> 18:19.651 And data centric city has three parts 18:19.651 --> 18:23.360 to it . The first really is people 18:24.240 --> 18:26.600 we hardly ever speak of this because 18:26.600 --> 18:28.840 we're so focused on the second tenant 18:28.850 --> 18:31.580 which is technology And then the 3rd 18:31.580 --> 18:35.270 piece is process or policy . If you 18:35.270 --> 18:37.381 want to capture data centric city you 18:37.381 --> 18:39.603 gotta line all three of those up . I am 18:39.603 --> 18:42.090 confident That we will solve the 18:42.090 --> 18:44.170 technical pieces of jazz c . two . 18:44.540 --> 18:47.210 There is a way to do this . I also 18:47.210 --> 18:49.850 believe that process and policy under 18:49.850 --> 18:51.940 the right pressures will form around 18:51.940 --> 18:54.162 the needs of the department and we will 18:54.162 --> 18:56.329 find ways to do things in an efficient 18:56.330 --> 18:59.550 and safe way . I am less optimistic 19:00.040 --> 19:02.300 on the people's side . If we don't take 19:02.300 --> 19:05.210 some some pretty strong action . It's 19:05.210 --> 19:07.140 really the people that are our 19:07.140 --> 19:10.460 strongest asset and really as a 19:10.460 --> 19:12.627 department as a government even beyond 19:12.627 --> 19:15.610 D . O . D . While there is value with 19:15.610 --> 19:17.610 our people we don't really have the 19:17.610 --> 19:19.680 best road map . We don't really know 19:19.680 --> 19:21.820 what it means to recruit the right 19:21.820 --> 19:23.931 market . We don't really know what it 19:23.931 --> 19:26.098 means to train and develop the kind of 19:26.098 --> 19:28.320 workforce we need not only today but in 19:28.320 --> 19:30.264 the future and for those who don't 19:30.264 --> 19:33.200 stick around this retention issue is 19:33.200 --> 19:35.367 one that we need to get a grasp of and 19:35.367 --> 19:37.320 figure out why . And we know that 19:37.320 --> 19:39.270 working in the government can be 19:39.270 --> 19:41.270 challenging things like on boarding 19:41.270 --> 19:43.960 delays , security clearances . Uh some 19:43.960 --> 19:46.016 of the educational requirements that 19:46.016 --> 19:48.238 are in place . Uh And you know that the 19:48.238 --> 19:50.460 pay in some cases where the pay may not 19:50.460 --> 19:52.460 be commensurate with industry . But 19:52.460 --> 19:54.349 I'll be honest the people that we 19:54.349 --> 19:56.571 talked to uh love to work in this field 19:56.571 --> 19:58.793 because they can do something that they 19:58.793 --> 20:00.738 can't do anywhere else and they're 20:00.738 --> 20:02.960 patriots at heart and they want to give 20:02.960 --> 20:05.071 back to their country still very much 20:05.071 --> 20:07.016 alive . So I really appreciate the 20:07.016 --> 20:09.238 question uh in the sense that we've got 20:09.238 --> 20:11.460 to take a look at people as strongly as 20:11.460 --> 20:13.349 we do technology . Otherwise this 20:13.349 --> 20:15.870 enterprise the jazzy to experiment that 20:15.870 --> 20:17.926 we're going through now in attempted 20:17.926 --> 20:20.037 delivery will not be successful . I'm 20:20.037 --> 20:22.600 encouraged that it made the cut and 20:22.600 --> 20:24.822 it's a it's got a strong voice in every 20:24.822 --> 20:26.920 form that were in front of . So I 20:26.920 --> 20:29.087 believe we've got it right . I believe 20:29.087 --> 20:31.142 there is clearly the right amount of 20:31.142 --> 20:33.364 attention to this but we haven't cashed 20:33.364 --> 20:35.587 that check yet . We now have to do what 20:35.587 --> 20:37.940 we've recognized our our shortfalls To 20:37.940 --> 20:40.107 the second part of your question . How 20:40.107 --> 20:42.110 do we bring in all the people to do 20:42.110 --> 20:44.480 this ? That's precisely what jazz C . 20:44.480 --> 20:46.840 two is leveraging . Not just for the U . 20:46.840 --> 20:49.300 S . Entities and not just for our 20:49.300 --> 20:51.133 letter agencies that support our 20:51.133 --> 20:53.356 efforts which we already have processes 20:53.356 --> 20:56.120 in place . We are re vigorous eating uh 20:56.130 --> 20:58.780 some of the forums we have with our our 20:58.780 --> 21:01.220 international partners . We know that 21:01.220 --> 21:03.387 five eyes sit at the table and many of 21:03.387 --> 21:05.442 these but the table is spread pretty 21:05.442 --> 21:07.590 wide with our coalition partners as 21:07.590 --> 21:09.930 well who have helped us develop the 21:09.940 --> 21:12.850 pieces that we can share . So inclusion 21:12.940 --> 21:16.080 is the solution to ensuring that we get 21:16.080 --> 21:18.191 a a better outcome and that we're not 21:18.191 --> 21:20.330 leaving some really good ideas out of 21:20.330 --> 21:21.330 the room . 21:24.640 --> 21:28.510 Angus did you have a follow up ? Um I 21:28.520 --> 21:30.576 sort of have like about seven follow 21:30.576 --> 21:32.631 ups but I'll just I'll just stick to 21:32.631 --> 21:34.970 one little little bit which is are you 21:34.970 --> 21:38.120 therefore saying that recruitment and 21:38.120 --> 21:41.270 retention will be in scope for judge C . 21:41.270 --> 21:45.010 Two line of effort to . Yes , I'm 21:45.010 --> 21:47.177 saying that exactly . We have a vested 21:47.177 --> 21:50.230 interest uh those opr . S . Those are 21:50.240 --> 21:52.790 the principles who will be responsible 21:52.790 --> 21:54.846 for that come from lots of different 21:54.846 --> 21:56.457 places but it's a collective 21:56.457 --> 21:58.510 responsibility to make sure that we 21:58.510 --> 22:00.590 look at our workforce . I mean I've 22:00.590 --> 22:02.701 talked about , I've even testified on 22:02.701 --> 22:04.950 this That our workforce needs are 22:04.950 --> 22:07.510 different than they were 15 or 20 years 22:07.510 --> 22:10.160 ago . The people that we really need as 22:10.160 --> 22:12.680 part of our organization , uh want a 22:12.680 --> 22:14.847 different work environment . They want 22:14.847 --> 22:16.958 a different structure . I don't think 22:16.958 --> 22:19.069 we'll have any problem recruiting the 22:19.069 --> 22:20.958 people we need , but we've got to 22:20.958 --> 22:22.902 listen to what their needs are and 22:22.902 --> 22:24.791 we've got to be flexible as in an 22:24.791 --> 22:26.930 organization that has historically 22:26.940 --> 22:29.230 functioned with a very firm and rigid 22:29.230 --> 22:31.790 hierarchy With a lot of people who get 22:31.790 --> 22:34.090 into this business of recent , like 22:34.100 --> 22:36.500 more shared space at the table where 22:36.500 --> 22:38.389 you don't have to work through 17 22:38.389 --> 22:40.770 layers of seniority to get an idea to 22:40.770 --> 22:43.270 the forefront . Uh they want to live 22:43.280 --> 22:45.580 where they want to live and work in 22:45.580 --> 22:47.747 those places they want to live . So is 22:47.747 --> 22:49.980 it necessary , for example , to have 22:49.980 --> 22:52.147 everyone live in a place that you know 22:52.147 --> 22:54.258 that it has cyber in front of it also 22:54.258 --> 22:56.202 has the word fort in front of it . 22:56.202 --> 22:58.369 Maybe you don't have to live on a ford 22:58.369 --> 23:00.424 in order to do some of the work that 23:00.424 --> 23:00.060 we're talking about . Maybe the 23:00.060 --> 23:02.227 educational requirements . It's better 23:02.227 --> 23:04.560 focused on your credentials and your 23:04.560 --> 23:07.250 competency rather than just formal 23:07.250 --> 23:09.194 courses etcetera . There's a whole 23:09.194 --> 23:11.250 smattering of things that we need to 23:11.250 --> 23:13.306 look at that would attract the right 23:13.306 --> 23:15.361 workforce . And recruitment is a key 23:15.361 --> 23:17.250 piece of this because it directly 23:17.250 --> 23:19.417 impacts our ability to execute . Jazzy 23:19.417 --> 23:22.120 too . That's brilliant , thank you very 23:22.120 --> 23:25.710 much . Thank you Agnes , let's move to 23:25.710 --> 23:27.950 Theresa Hitchens with Breaking Defense 23:28.440 --> 23:30.440 thanks for us and thank you General 23:30.440 --> 23:32.607 Carl , it's nice to see you again . Um 23:32.740 --> 23:35.920 Yeah , as we've learned in school 23:35.920 --> 23:38.830 strategy encompasses goals , ways and 23:38.830 --> 23:41.840 means I I take it it's fair to say that 23:41.840 --> 23:45.730 the strategy document um that that you 23:45.730 --> 23:48.130 just released a summary of is the goals , 23:48.190 --> 23:50.590 the implementation plan is the ways but 23:50.590 --> 23:52.940 the means the budget , those are 23:52.940 --> 23:55.162 actually in the hands of the services . 23:55.390 --> 23:58.830 So you said that this implementation 23:58.830 --> 24:00.840 plan has some funding , I guess 24:00.840 --> 24:03.590 guidance in it . Can you talk about 24:03.600 --> 24:06.630 what that is given that actually the 24:06.630 --> 24:08.463 joint staff doesn't have funding 24:09.140 --> 24:11.307 authority , that's in the hands of the 24:11.307 --> 24:13.420 services . So can you explain how you 24:13.420 --> 24:15.940 intend to match the means to the ways 24:15.940 --> 24:18.107 that are in this implementation plan ? 24:18.107 --> 24:20.218 You bet and this is the beauty of the 24:20.218 --> 24:22.350 organization because the cross 24:22.350 --> 24:24.560 functional team , even though it sits 24:24.940 --> 24:27.760 where it sits uh as you know , being 24:27.760 --> 24:30.190 executed or chaired with the joint 24:30.190 --> 24:32.520 staff J six , it's not a joint staff J 24:32.520 --> 24:35.670 six entity , we have two feeders right 24:35.670 --> 24:37.600 now that come out of that cross 24:37.600 --> 24:40.810 functional team and the power of the 24:40.810 --> 24:43.240 money that moves through that is 24:43.240 --> 24:45.300 married very well with the power of 24:45.300 --> 24:47.578 requirements , through the joint staff . 24:47.578 --> 24:49.800 So to answer your question directly and 24:49.800 --> 24:51.633 the reason that that partnership 24:51.633 --> 24:53.560 between the Vice chairman and the 24:53.560 --> 24:56.330 deputy secretary is so critical , you 24:56.330 --> 24:59.320 are right , the power of the purse in 24:59.320 --> 25:02.600 the in really . D O D flows through the 25:02.600 --> 25:05.380 D MAg from the Deputy Secretary . And 25:05.380 --> 25:07.760 that D MAG channel is very much alive 25:08.140 --> 25:10.307 in that cross functional team output . 25:10.540 --> 25:12.484 And it works hand in hand with the 25:12.484 --> 25:14.590 joint staff requirement of validated 25:14.590 --> 25:16.820 requirements through the J Rock . And 25:16.820 --> 25:18.653 those two things should never be 25:18.653 --> 25:20.542 separated . You don't want to put 25:20.542 --> 25:22.542 funding against things that are not 25:22.542 --> 25:25.020 valid requirements uh and you certainly 25:25.030 --> 25:26.974 don't have the power and the joint 25:26.974 --> 25:29.197 staff to direct service budgets . Never 25:29.197 --> 25:31.450 intended , nor is it being sought . So 25:31.450 --> 25:33.720 the way this machine actually functions 25:33.730 --> 25:36.880 uh is the Vice Chairman has really 25:36.890 --> 25:39.610 reinvigorated the J ROC and the J Rock 25:39.610 --> 25:41.920 community to make sure that when things 25:41.930 --> 25:44.380 are postured inside of that cross 25:44.380 --> 25:46.602 functional team , if they're already in 25:46.602 --> 25:48.550 play and it's a funding matter , a 25:48.550 --> 25:50.606 milestone matter , a timing matter , 25:50.640 --> 25:52.696 They get fed directly into the D MAG 25:52.940 --> 25:55.500 for direction from the Deputy Secretary 25:55.500 --> 25:57.590 to the services and if these are new 25:57.590 --> 25:59.730 start's good ideas , et cetera that 25:59.730 --> 26:01.786 need to have requirements associated 26:01.786 --> 26:04.008 with them first . Those collectives are 26:04.008 --> 26:06.063 gathered , brought through the J ROC 26:06.063 --> 26:09.190 validated and then pushed over to the D 26:09.190 --> 26:11.412 MAG and of course that , you know , the 26:11.412 --> 26:13.468 Deputy Secretary has a whole host of 26:13.468 --> 26:16.410 things of funding mechanisms to get 26:16.410 --> 26:18.950 after everything in near term through 26:18.950 --> 26:22.030 reprogramming all the way to out years 26:22.040 --> 26:24.410 of formal palming uh and then things 26:24.410 --> 26:26.577 like the rapid defense experimentation 26:26.577 --> 26:28.743 reserve a raider fund that allows some 26:28.743 --> 26:31.170 level of innovation uh to take place . 26:31.240 --> 26:33.184 So that's how we accomplished that 26:33.184 --> 26:35.940 balance between the requirements piece 26:35.950 --> 26:38.530 on the joint side and the true funding 26:38.530 --> 26:41.870 piece uh and the authorities that rest 26:41.870 --> 26:44.092 with the deputy secretary through the D 26:44.092 --> 26:47.130 max . Okay , can I follow up then ? Um 26:47.140 --> 26:49.480 you've been working on this for , as 26:49.480 --> 26:52.340 you said for about a year and you and 26:52.340 --> 26:54.507 general parker have in the past talked 26:54.507 --> 26:56.729 about minimum viable products . Can you 26:56.729 --> 26:58.896 talk about what the priorities are for 26:58.896 --> 27:02.030 actual delivery in this year , in this 27:02.030 --> 27:04.141 next coming year . Now that this this 27:04.141 --> 27:07.310 is a formal document and a formal um 27:07.310 --> 27:11.130 plan . Yes , I can . So , you know , to 27:11.130 --> 27:13.297 answer your question , you know , very 27:13.297 --> 27:15.352 bluntly and honestly , while we have 27:15.352 --> 27:17.630 seven mbps uh that are out there and 27:17.630 --> 27:19.780 they range from , you know , you can 27:19.780 --> 27:22.002 actually do the number account a little 27:22.002 --> 27:24.058 bit differently depending on how you 27:24.058 --> 27:26.113 aggregate them , but they're largely 27:26.113 --> 27:26.090 around identity credential and 27:26.090 --> 27:29.100 management , cloud , our transport 27:29.100 --> 27:32.480 layer zero Trust , Environment Mission , 27:32.480 --> 27:35.900 partner Environment dev SEc Ops , which 27:35.900 --> 27:37.900 could be broken up into a couple of 27:37.900 --> 27:40.011 different things , basically platform 27:40.011 --> 27:42.122 with large uh and things like cloud , 27:42.122 --> 27:44.178 you know , things like that . Uh and 27:44.178 --> 27:46.178 there's all work involved in all of 27:46.178 --> 27:48.067 those and in some cases there are 27:48.067 --> 27:50.390 statutory authorities that , you know , 27:50.390 --> 27:52.557 rest like with the C I . O for some of 27:52.557 --> 27:55.220 that selection with our data enterprise 27:55.220 --> 27:57.387 in the building and services have some 27:57.387 --> 27:59.331 roles in that . So not stepping on 27:59.331 --> 28:01.710 those toes at all . But there are two 28:01.710 --> 28:03.821 areas that we've picked of those that 28:03.821 --> 28:06.280 we are looking to accelerate and that 28:06.280 --> 28:08.510 it really are focused this year and I 28:08.510 --> 28:11.710 mean delivery soonest and the first one 28:11.720 --> 28:14.010 is Deb said cops and to give you the 28:14.010 --> 28:16.270 use case because we could spend a lot 28:16.270 --> 28:18.492 of time going through , you know , what 28:18.492 --> 28:20.270 is their benefit in selecting a 28:20.270 --> 28:22.492 platform ? What would the platform look 28:22.492 --> 28:24.603 like ? Don't we already have a couple 28:24.603 --> 28:26.770 of those platforms . Do you need to be 28:26.770 --> 28:28.826 so specific with big standards ? Are 28:28.826 --> 28:28.740 you gonna have a little standards ? How 28:28.740 --> 28:30.907 do you prevent so much divergence that 28:30.907 --> 28:32.962 they start working at cross purposes 28:32.962 --> 28:35.073 and no longer become affordable . All 28:35.073 --> 28:37.240 good questions . But what we're really 28:37.240 --> 28:40.610 focused on this year is a use case 28:40.620 --> 28:42.676 where I cannot recall the department 28:42.676 --> 28:44.898 doing this , I could be , I could stand 28:44.898 --> 28:47.009 corrected if someone comes up with an 28:47.009 --> 28:49.231 example but you know our teams that are 28:49.231 --> 28:51.453 working on this don't have one . And to 28:51.453 --> 28:53.676 some of you it may sound modest or even 28:53.676 --> 28:55.676 small but I want you to think about 28:55.676 --> 28:57.676 what hasn't existed before and what 28:57.676 --> 28:59.787 we're trying to accomplish that is to 28:59.787 --> 29:02.360 take an application since applications 29:02.370 --> 29:04.980 rule our environments and they crush us 29:04.980 --> 29:07.147 in budgets . They don't have a P I . S 29:07.147 --> 29:09.230 on the back side . I can't exchange 29:09.230 --> 29:11.600 data the way that I need to exchange 29:11.600 --> 29:13.933 data . They're locked up going in there , 29:13.933 --> 29:16.156 locked up coming out and they misbehave 29:16.156 --> 29:18.510 on the network . Almost impossible to 29:18.510 --> 29:20.960 manage on the network . Either chatty 29:20.970 --> 29:23.200 unsecure or I can't share them with 29:23.200 --> 29:25.311 others at a time that I need to share 29:25.311 --> 29:27.460 them and forget about patching . The 29:27.460 --> 29:30.270 patching protocol is so problematic 29:30.280 --> 29:32.502 that we don't do this in the times that 29:32.502 --> 29:34.447 are necessary . That's the present 29:34.447 --> 29:36.613 environment . So what we're attempting 29:36.613 --> 29:39.290 to do in depth sec ops this year is to 29:39.290 --> 29:41.430 take a series of applications . We've 29:41.430 --> 29:43.652 let the services come forward which the 29:43.652 --> 29:46.390 ones that they want to create first and 29:46.390 --> 29:48.940 this environment on a common platform 29:48.950 --> 29:51.320 with a common developers toolkit will 29:51.320 --> 29:54.200 create a secure application that comes 29:54.200 --> 29:56.100 directly out of the developmental 29:56.110 --> 29:58.440 environment environment with an 29:58.440 --> 30:00.830 authority to operate placed directly on 30:00.830 --> 30:02.663 the network with the Reciprocity 30:02.663 --> 30:04.552 agreement and shared by the other 30:04.552 --> 30:08.050 services literally in minutes and so we 30:08.050 --> 30:10.106 went out to customers and again , if 30:10.106 --> 30:12.161 you're an industry you would look at 30:12.161 --> 30:14.328 this and probably yawn and say do that 30:14.328 --> 30:16.439 every day . Right . Every Fortune 500 30:16.439 --> 30:18.661 company operates like this , you know , 30:18.661 --> 30:20.939 hundreds of ap I adjustments every day . 30:20.939 --> 30:24.160 We don't for a host of reasons so that 30:24.170 --> 30:27.860 from start to finish from developing to 30:27.860 --> 30:31.250 publishing to hosting to using and then 30:31.250 --> 30:33.780 real time patching to ensure that 30:33.780 --> 30:36.140 secure and then giving this homework 30:36.140 --> 30:38.810 between the services to let them test 30:38.810 --> 30:41.170 drive their developmental environments 30:41.380 --> 30:43.380 developed by others or degrade each 30:43.380 --> 30:45.324 other's homework will start soon . 30:45.324 --> 30:47.436 Pieces of that are already underway . 30:47.640 --> 30:49.860 That's kind of element number one , 30:50.340 --> 30:52.730 Element number two in depth . Sec ops 30:52.740 --> 30:55.760 is to take some of our most misbehaving 30:55.760 --> 30:57.982 applications in the environment , which 30:57.982 --> 31:00.149 I would prefer not to mention uh right 31:00.149 --> 31:02.930 now , uh and put them through the 31:02.930 --> 31:05.930 redevelopment gauntlet and have them 31:05.930 --> 31:09.460 reformatted into this viable uh 31:09.840 --> 31:11.900 application that I just described so 31:11.900 --> 31:13.844 that it can behave properly on the 31:13.844 --> 31:16.140 network and we can share data . This 31:16.140 --> 31:18.730 really came to light in some of the 31:18.740 --> 31:21.100 crisis actions that we went through for 31:21.100 --> 31:23.360 things like Afghanistan and even what 31:23.360 --> 31:25.582 we're seeing now in the Russian Ukraine 31:25.582 --> 31:27.582 conflict , looking at , just simply 31:27.582 --> 31:29.471 trying to pull information out of 31:29.471 --> 31:31.693 systems that just do not behave right , 31:31.693 --> 31:33.860 we can't live this way any longer . So 31:33.860 --> 31:36.510 dev sec ops as I've just described , it 31:36.520 --> 31:38.631 is really one of the areas that we're 31:38.631 --> 31:40.710 looking to accomplish this year and 31:40.710 --> 31:42.877 we've got a tremendous head start . We 31:42.877 --> 31:44.821 are not starting from cold steel , 31:44.821 --> 31:46.766 we've got lots of those elements . 31:46.766 --> 31:50.030 Every service has a viable means and we 31:50.030 --> 31:52.250 now have a bake off of sorts as they 31:52.250 --> 31:54.472 test drive each other's products and to 31:54.472 --> 31:56.639 be honest , I've never seen a level of 31:56.639 --> 31:58.861 cooperation between the services to get 31:58.861 --> 32:01.020 after what looks right break on the 32:01.020 --> 32:02.660 other side , mission partner 32:02.660 --> 32:04.827 environment is an area that we need to 32:04.827 --> 32:07.670 tame , This is more ethereal right now , 32:07.670 --> 32:10.280 meaning I don't have such a concrete 32:10.280 --> 32:12.169 example , but we've done a lot of 32:12.169 --> 32:14.640 testing with partners on data . 32:14.640 --> 32:16.780 Exchange what wave forms are best , 32:16.780 --> 32:18.930 what security elements where data is 32:18.930 --> 32:22.750 stored , how to do this in a austere or 32:22.750 --> 32:25.150 a denied environment and there hasn't 32:25.150 --> 32:27.370 been an order to what we've done . But 32:27.370 --> 32:29.600 what we're focused on right now are 32:29.600 --> 32:31.711 some of the challenges we have in our 32:31.711 --> 32:35.240 current fielded systems we've got at 32:35.240 --> 32:38.260 the secret level and below a very 32:38.740 --> 32:42.230 wonky problematic uh 32:42.240 --> 32:44.590 array right now with the way that we 32:44.590 --> 32:46.590 exchange data with our partners and 32:46.590 --> 32:48.812 it's not sustainable . It's expensive . 32:48.812 --> 32:51.034 It doesn't work well . And almost every 32:51.034 --> 32:53.400 country has some level of bespoke 32:53.410 --> 32:55.740 configuration that makes it really hard 32:55.740 --> 32:58.380 to manage . And so we're taking that on 32:58.390 --> 33:00.501 as to how do you take what you've got 33:00.501 --> 33:03.650 and put it in a repeatable , 33:03.650 --> 33:07.170 recognizable , affordable . Uh you no 33:07.180 --> 33:09.990 order and we have two combatant 33:09.990 --> 33:12.212 commands , Central command and indo pay 33:12.212 --> 33:14.750 calm command that have done phenomenal 33:14.750 --> 33:16.694 work to that end . And rather than 33:16.694 --> 33:19.170 creating all of that here in D . C . Uh 33:19.180 --> 33:21.347 we've turned to our combatant commands 33:21.347 --> 33:23.730 who have shown progress and we are 33:23.730 --> 33:26.330 helping them organize this in the cross 33:26.330 --> 33:28.390 functional team to see if we can 33:28.390 --> 33:31.270 replicate that as a standard . So those 33:31.270 --> 33:34.300 are the two areas that are receiving a 33:34.310 --> 33:36.950 disproportional amount of attention up 33:36.950 --> 33:39.360 front . Thank you so much . 33:40.640 --> 33:42.730 Thank you Teresa . Let's move on to 33:42.730 --> 33:44.674 Jared stab you with federal news . 33:45.740 --> 33:47.684 Thanks Russ and thanks general for 33:47.684 --> 33:49.907 doing this . Um , I apologize if you've 33:49.907 --> 33:52.129 addressed this , I had to step away for 33:52.129 --> 33:51.350 a second , but I was hoping you could 33:51.350 --> 33:53.572 elaborate a little bit more on the what 33:53.572 --> 33:55.739 you said is going to need to be strong 33:55.739 --> 33:57.628 action on the people's side . How 33:57.840 --> 34:00.380 detailed and specific does the 34:00.380 --> 34:02.960 implementation plan get on the concrete 34:02.960 --> 34:05.182 actions you need to take to handle some 34:05.182 --> 34:07.293 of the people issues . Are you mostly 34:07.293 --> 34:08.738 it's still at the problem 34:08.738 --> 34:10.738 identification stage or do you know 34:10.738 --> 34:12.738 what you need to do on the people's 34:12.738 --> 34:14.904 side ? Yeah , we're far more developed 34:14.904 --> 34:16.849 there . And unfortunately it's not 34:16.849 --> 34:18.904 because of our wisdom and somehow we 34:18.904 --> 34:21.071 dedicated more time to it . The reason 34:21.071 --> 34:23.238 that we're so developed on that end is 34:23.238 --> 34:23.140 we haven't , we've known about these 34:23.140 --> 34:25.196 problems for a long time and haven't 34:25.196 --> 34:27.350 fixed it . Uh So this is really 34:27.350 --> 34:29.810 something that we should have done 57 , 34:29.810 --> 34:32.020 10 years ago . Uh What the 34:32.020 --> 34:34.700 implementation plan finally does is 34:34.700 --> 34:37.800 really put that accountability and 34:37.800 --> 34:39.856 measurable steps against each one of 34:39.856 --> 34:41.970 those discrete parts that we've 34:41.970 --> 34:44.100 discovered . I've kind of outlined a 34:44.100 --> 34:46.322 little bit of that on what we're trying 34:46.322 --> 34:48.760 to tackle , but , you know , the 34:48.760 --> 34:52.000 workforce is evolving . Uh There's 34:52.000 --> 34:54.000 different needs , There's different 34:54.000 --> 34:55.889 skill sets . Uh there are certain 34:55.889 --> 34:58.056 people we actually need on staff to do 34:58.056 --> 35:00.310 the , the work belonging , you know , 35:00.310 --> 35:02.477 to us and there's others that could be 35:02.477 --> 35:04.754 contracted out to do that as a service . 35:04.754 --> 35:06.740 Uh but we've got to ensure , for 35:06.740 --> 35:08.684 example , I'll just give you a few 35:08.684 --> 35:10.907 examples that we've known about when it 35:10.907 --> 35:12.796 comes to recruitment . You know , 35:12.796 --> 35:14.907 people just don't fall out of the sky 35:14.907 --> 35:17.129 and decide I'm gonna come over and join 35:17.129 --> 35:19.184 the government . And it's tough to , 35:19.184 --> 35:21.518 it's tough to find where those jobs are . 35:21.518 --> 35:23.740 It's difficult to onboard . It's timely 35:23.740 --> 35:25.796 their security , you know , security 35:25.796 --> 35:27.684 concerns . I mean , we we make it 35:27.684 --> 35:30.080 difficult and in many cases , maybe 35:30.080 --> 35:32.136 it's necessary because we want to be 35:32.136 --> 35:34.358 thorough , but in many cases it's not , 35:34.358 --> 35:36.413 we've just got to get better at it . 35:36.413 --> 35:38.358 We've got to understand our market 35:38.358 --> 35:40.524 better . We've got to understand , you 35:40.524 --> 35:42.524 know , if you're part of the team , 35:42.524 --> 35:44.747 what's your developmental pathway ? One 35:44.747 --> 35:46.969 of the biggest disappointments I've had 35:46.969 --> 35:49.136 is that there are certain career paths 35:49.136 --> 35:51.136 in these technical fields that it's 35:51.136 --> 35:53.302 unclear how you advance , what schools 35:53.302 --> 35:55.358 you attend , how you progress , what 35:55.358 --> 35:57.191 the expectations are . These are 35:57.191 --> 35:59.413 reasonable things for people to want to 35:59.413 --> 36:01.580 know when they join an organization of 36:01.580 --> 36:03.524 our size . So what we have is well 36:03.524 --> 36:05.636 intentioned people who've got a laser 36:05.636 --> 36:07.580 focus on this . But now we've come 36:07.580 --> 36:10.140 together in a more holistic way and 36:10.140 --> 36:12.990 we've committed to fixing this . So I'm 36:13.000 --> 36:15.000 incredibly for everything that I've 36:15.000 --> 36:17.111 just said , that sounds pessimistic , 36:17.111 --> 36:19.111 is that were slow in doing it . I'm 36:19.111 --> 36:21.222 incredibly optimistic that we finally 36:21.222 --> 36:22.944 got a beat on it . Uh , and we 36:22.944 --> 36:25.111 understand what needs to be done . And 36:25.111 --> 36:27.278 I think the order of prosecution makes 36:27.278 --> 36:29.444 sense . And you know our leadership in 36:29.444 --> 36:31.667 the building from the secretary on down 36:31.667 --> 36:31.630 support from Congress . There's not a 36:31.630 --> 36:34.310 single entity that I interact with that 36:34.320 --> 36:36.540 isn't ahead of me right now , spurring 36:36.540 --> 36:39.460 me empowering us as an effort to get 36:39.460 --> 36:41.516 after this as our highest priority . 36:41.730 --> 36:45.080 People really are our strength and our 36:45.080 --> 36:47.450 leadership is really committed to 36:47.450 --> 36:50.370 fixing it . So yes we have a head start 36:50.380 --> 36:52.380 it's not nascent and I would expect 36:52.380 --> 36:54.730 some pretty recognizable changes to 36:54.730 --> 36:56.910 that in a few months ahead . And can 36:56.910 --> 36:58.854 you just say a little bit on which 36:58.854 --> 37:00.966 communities for lack of a better word 37:00.966 --> 37:03.188 are implicated by by the implementation 37:03.188 --> 37:05.299 plan ? I mean I'm guessing it extends 37:05.299 --> 37:07.466 pretty far beyond just the traditional 37:07.466 --> 37:09.688 I . T . Workforce . It does but I think 37:09.688 --> 37:11.854 it's manifest more right now we in the 37:11.854 --> 37:13.854 I . T . Workforce and really in the 37:13.854 --> 37:13.600 technical side of it not in the 37:13.600 --> 37:16.260 scientific and technology community 37:16.270 --> 37:18.437 there . They've always been able to go 37:18.437 --> 37:20.770 out and really get you know the experts , 37:20.770 --> 37:22.548 the data scientists , the chief 37:22.548 --> 37:24.480 technicians and the do test and 37:24.480 --> 37:26.591 analysis . They've always been really 37:26.591 --> 37:28.813 good at that . Uh I'm talking about the 37:28.813 --> 37:30.813 other organizations especially even 37:30.813 --> 37:33.150 within services in order for us to take 37:33.160 --> 37:35.840 our visions and implement them on day 37:35.840 --> 37:38.320 to day operations and how we do 37:38.320 --> 37:40.542 business . Uh that's really what's been 37:40.542 --> 37:42.764 lacking . So I think you'll see this at 37:42.764 --> 37:44.709 the service level . Uh Certainly I 37:44.709 --> 37:46.764 think you'll see this at the support 37:46.764 --> 37:48.987 level where this will be manifest . And 37:48.987 --> 37:51.042 the very first question I think or a 37:51.042 --> 37:52.931 question or two that opened up is 37:52.931 --> 37:55.042 related to this as well . In addition 37:55.042 --> 37:57.320 to the right workforce to work some of 37:57.320 --> 37:59.370 this , the training and education , 37:59.370 --> 38:02.620 responsibility for everybody uh needs 38:02.620 --> 38:04.787 to be raised and that's addressed here 38:04.787 --> 38:06.953 as well . So this is about raising the 38:06.953 --> 38:10.130 competency of the user Because you know , 38:10.130 --> 38:12.280 again , maybe 20 or 30 years ago , 38:12.290 --> 38:14.290 someone might say , you know what , 38:14.290 --> 38:16.568 that's someone else's problem to solve . 38:16.568 --> 38:18.679 But we're all dependent on technology 38:18.720 --> 38:20.553 and there's got to be a level of 38:20.553 --> 38:22.498 understanding . We understand it's 38:22.498 --> 38:24.664 clear for our security , right ? We do 38:24.664 --> 38:26.720 things and how we use the term cyber 38:26.720 --> 38:28.720 cyber hygiene , which is a terrible 38:28.720 --> 38:30.887 term . Uh And I know that we've talked 38:30.887 --> 38:33.109 before that you know , hygiene for some 38:33.109 --> 38:35.220 maybe is optional . Uh So maybe cyber 38:35.220 --> 38:37.442 hygiene is a bad way to look at it . Uh 38:37.442 --> 38:39.387 cybersecurity is not optional . So 38:39.387 --> 38:41.109 we've got to train and educate 38:41.109 --> 38:43.280 everybody who will use this space 38:43.280 --> 38:45.970 properly . So it even affects the 38:45.970 --> 38:49.910 nontechnical user of this . Uh So yes , 38:49.910 --> 38:51.799 I think you'll see this primarily 38:51.799 --> 38:54.210 focused on the professional cadre , we 38:54.210 --> 38:57.330 need uh in the non S and T 38:57.520 --> 39:00.250 community . Thank you sir . 39:01.220 --> 39:03.580 Thank you Jared . Um Next question goes 39:03.580 --> 39:05.750 to Brianna Riley with Inside Defense . 39:06.720 --> 39:08.831 Thanks so much for doing this back to 39:08.831 --> 39:10.942 Teresa's question on the MVPs mission 39:10.942 --> 39:12.942 partner environment has been in the 39:12.942 --> 39:15.164 works for years , I'm wondering is part 39:15.164 --> 39:17.220 of the reason you're prioritizing it 39:17.220 --> 39:19.331 now because of Russia's aggression in 39:19.331 --> 39:19.150 Ukraine or can you shed further light 39:19.150 --> 39:21.206 on why it ranks so highly among your 39:21.206 --> 39:23.094 priorities and then beyond that , 39:23.094 --> 39:24.983 what's the timeline look like for 39:24.983 --> 39:27.039 delivering capabilities here ? Thank 39:27.039 --> 39:29.206 you . Sure . Well , I would say that , 39:29.206 --> 39:31.150 you know , to answer your question 39:31.150 --> 39:33.372 directly . No , we didn't spur it on or 39:33.372 --> 39:35.372 elevated as a result of the Russian 39:35.372 --> 39:37.539 Ukraine conflict Mp as you said , it's 39:37.539 --> 39:39.539 been in the work along , you know , 39:39.539 --> 39:41.706 quite some time ago and we made this a 39:41.706 --> 39:43.983 priority uh , formally , uh , you know , 39:43.983 --> 39:46.150 in the strategy which was written over 39:46.150 --> 39:48.317 a year ago , it made the cut as a line 39:48.317 --> 39:50.650 of effort because of one real principle , 39:51.020 --> 39:52.964 we're never going to fight alone . 39:53.020 --> 39:55.298 We're always going to rely on partners . 39:55.298 --> 39:57.464 We need partners . Uh , there's not an 39:57.464 --> 39:59.464 operation or activity especially at 39:59.464 --> 40:01.687 scale that we can think of that . We'll 40:01.687 --> 40:03.742 we'll do this by ourselves . We need 40:03.742 --> 40:05.853 our partners and our allies and so we 40:05.853 --> 40:07.798 need to get better at it . You are 40:07.798 --> 40:09.798 correct . This has gone on for some 40:09.798 --> 40:12.440 time . There's been pockets of , of 40:12.440 --> 40:14.662 success in areas , but what was lacking 40:14.662 --> 40:16.930 to be fair is , you know , if you ask 40:16.930 --> 40:19.950 me the question five years ago , what's 40:19.950 --> 40:22.006 your operational design , Forget the 40:22.006 --> 40:24.228 priorities , where are you going ? What 40:24.228 --> 40:26.228 do you want to accomplish ? I don't 40:26.228 --> 40:28.228 think we could have , we could have 40:28.228 --> 40:30.283 said yet we were very busy , lots of 40:30.283 --> 40:32.172 action . Lots of testing a lot of 40:32.172 --> 40:34.394 sharing . But to what point ? This puts 40:34.394 --> 40:37.120 a fine point on delivery . And really 40:37.120 --> 40:39.453 since we're talking about data exchange , 40:39.453 --> 40:42.800 our number one MPE priority is in the 40:42.800 --> 40:45.550 system and systems that provide that 40:45.550 --> 40:48.280 information exchange at the cocom level , 40:48.290 --> 40:50.710 which is why I listed centcom and indo 40:50.710 --> 40:52.599 pay calm . They struggle in their 40:52.599 --> 40:54.377 environments like all combatant 40:54.377 --> 40:56.488 commands do to make sure that we have 40:56.488 --> 40:58.432 the right apparatus technically in 40:58.432 --> 41:00.870 place . Uh we can always put filters on , 41:00.880 --> 41:03.102 we know what information can and cannot 41:03.102 --> 41:05.213 be shared . But if you don't have the 41:05.213 --> 41:07.158 transport apparatus , if you can't 41:07.158 --> 41:09.047 share data , if there's no common 41:09.047 --> 41:11.158 repository , how do our partners do ? 41:11.158 --> 41:13.324 Jazzy too . Uh and how do they look at 41:13.324 --> 41:15.436 their own decision making cycle if we 41:15.436 --> 41:17.436 can't connect at the data level And 41:17.436 --> 41:19.602 that's really why mp is so important . 41:19.602 --> 41:21.713 Timelines was the second part of your 41:21.713 --> 41:23.880 question . This gets a little trickier 41:24.110 --> 41:26.670 right now . Not all the budget 41:26.670 --> 41:30.220 decisions have been made . Uh So I'm 41:30.220 --> 41:33.350 guessing as I look at this are asked , 41:33.360 --> 41:35.471 you know , the Deputy secretary has a 41:35.471 --> 41:37.670 very tough job ahead of her because 41:37.670 --> 41:40.230 we've asked for everything . I think 41:40.230 --> 41:42.720 we've prioritized fairly well . But if 41:42.720 --> 41:45.480 you add these up , I'm confident it's 41:45.480 --> 41:47.702 more money than we have to do all of it 41:47.702 --> 41:50.230 right now . So we have to make the case . 41:50.240 --> 41:52.462 What are the prerequisites that have to 41:52.462 --> 41:54.518 be in place to take that next step , 41:54.518 --> 41:56.629 Which things can be spread out , what 41:56.629 --> 41:58.851 things don't you want ? Maybe there's , 41:58.851 --> 42:00.907 you know , wisdom in not spending so 42:00.907 --> 42:03.129 much money in certain areas because you 42:03.129 --> 42:02.660 want to see how they play out and 42:02.660 --> 42:05.390 develop rather than over investing in 42:05.390 --> 42:08.370 an area . So we do need to make some 42:08.370 --> 42:10.510 tough choices in the department on 42:10.510 --> 42:12.621 which you know , which pieces of this 42:12.621 --> 42:14.732 get fielded at what , what points and 42:14.732 --> 42:17.760 we are prepared using the I plan to go 42:17.760 --> 42:19.593 through that D MAg and budgetary 42:19.593 --> 42:21.880 process . We also have a close eye on 42:21.880 --> 42:24.770 budget on continuous resolutions . You 42:24.770 --> 42:26.826 know , some of this , our new starts 42:26.826 --> 42:28.826 and I think all of us know that new 42:28.826 --> 42:31.000 starts can be challenging uh , in a cR 42:31.000 --> 42:33.650 environment . I'm not using that as an 42:33.650 --> 42:35.950 excuse . I'm not convinced that slowed 42:35.960 --> 42:38.430 where we have been right now , but in 42:38.430 --> 42:40.830 the future if that becomes a way of 42:40.840 --> 42:43.520 practice And it becomes more common 42:43.530 --> 42:45.197 delivery of certain aspects , 42:45.197 --> 42:47.620 especially new start aspects of Jazz C2 42:47.630 --> 42:50.170 will be hampered as other programs have 42:50.180 --> 42:53.550 been . Thank you . Quick follow up on 42:53.550 --> 42:55.920 the funding elements . Can you speak 42:55.920 --> 42:57.920 ballpark figures about the level of 42:57.920 --> 42:59.809 funding the I plan is recommended 42:59.809 --> 43:01.864 recommending and well , any of those 43:01.864 --> 43:04.087 funding recommendations , you know , be 43:04.087 --> 43:06.309 reflected in the Fy 23 budget request . 43:06.309 --> 43:08.476 Thanks , I can answer the latter . The 43:08.476 --> 43:10.460 answer is yes , very clearly we've 43:10.460 --> 43:12.738 already had placeholders in , you know , 43:12.738 --> 43:14.960 even though these this document , the I 43:14.960 --> 43:17.182 plan itself was recently signed . We've 43:17.182 --> 43:19.630 been in constant battle rhythm events 43:19.630 --> 43:21.630 with our leadership on where we saw 43:21.630 --> 43:24.110 this forming up . So it's not as though 43:24.110 --> 43:26.277 it was just dropped in the environment 43:26.277 --> 43:28.443 and we're now trying to take a look at 43:28.443 --> 43:30.388 this for the first time . We had a 43:30.388 --> 43:32.443 pretty strong understanding of where 43:32.443 --> 43:34.610 these would fall out . And so yes , we 43:34.610 --> 43:36.832 have a solid plan I think or at least a 43:36.832 --> 43:38.999 good a good recommendation maybe on on 43:38.999 --> 43:41.054 how that will land for 23 as for how 43:41.054 --> 43:43.780 much money overall , I don't think I , 43:43.790 --> 43:46.290 I fully have a , you know , reliable 43:46.290 --> 43:48.568 answer to give you . But even if I did , 43:48.568 --> 43:50.950 I probably wouldn't share it . I'm not 43:50.950 --> 43:53.228 keen to get out ahead of uh , you know , 43:53.228 --> 43:55.394 the Secretary and Deputy Secretaries , 43:55.394 --> 43:58.010 battlespace in that area . Thank you . 43:59.000 --> 44:01.610 Uh thank you , Brianna . Last question 44:01.610 --> 44:03.666 goes to sang Min lee with Radio Free 44:03.666 --> 44:06.380 Asia . Yes . Um , I have a question 44:06.380 --> 44:10.150 about how to jet to apply to korean 44:10.160 --> 44:13.640 peninsula . So , um , there is a 44:13.650 --> 44:15.817 discussion about the , you included in 44:15.817 --> 44:18.094 the ally , the United States to jet to . 44:18.094 --> 44:20.670 So you're thinking about the korean 44:20.680 --> 44:22.736 forces can be included in the jet to 44:22.736 --> 44:25.280 and also how to apply that uh , the 44:25.290 --> 44:27.568 north Korea threat in korean peninsula . 44:27.890 --> 44:30.001 No thanks . That's a , that's a great 44:30.001 --> 44:32.430 question . And the short answer is yes , 44:32.440 --> 44:34.950 completely included . Uh , and that's 44:34.950 --> 44:38.090 part of that uh combatant command roll 44:38.090 --> 44:41.380 up uh , that I described earlier . Uh , 44:41.380 --> 44:44.820 and you know specifically to uh the 44:44.820 --> 44:47.920 Republic of Korea , the centric Kay 44:48.090 --> 44:50.680 apparatus , you know , the very command 44:50.680 --> 44:53.070 and control system that it uses is one 44:53.070 --> 44:55.410 of many that are out there for all of 44:55.410 --> 44:57.610 our partners that we're trying to 44:57.620 --> 45:00.940 ensure stays modernized viable and and 45:00.940 --> 45:03.420 again meets the needs of war fighters 45:03.960 --> 45:06.127 in that theater and how the theater is 45:06.127 --> 45:08.630 fed with timely information . Uh that 45:08.630 --> 45:11.690 particular system itself is in the 45:11.690 --> 45:14.750 scope of jazzy to reformation , all 45:14.750 --> 45:17.140 designed to empower and increase that 45:17.140 --> 45:19.251 information , information sharing and 45:19.251 --> 45:20.973 state . So the answer is yes . 45:20.973 --> 45:24.400 Absolutely . Included My polio question . 45:24.400 --> 45:27.200 How about the jet related to the US 45:27.200 --> 45:29.144 versus Korea two against the North 45:29.144 --> 45:32.830 Korean threat . Yes . So I I look at , 45:32.840 --> 45:34.951 you know , all threats that combatant 45:34.951 --> 45:37.062 commands bring to the table are being 45:37.062 --> 45:40.070 tested against our jazz C2 model uh in 45:40.070 --> 45:42.800 very discrete parts . So yes , the 45:42.800 --> 45:45.180 threat on the korean peninsula gets the 45:45.180 --> 45:47.190 same treatment that we would get 45:47.190 --> 45:50.000 threats in other geographical areas . 45:50.010 --> 45:52.020 And what we're looking for in that 45:52.020 --> 45:55.160 analysis is where we come up short and 45:55.160 --> 45:57.271 and again , just being honest , there 45:57.271 --> 45:59.493 are many good ideas that are hatched in 45:59.493 --> 46:01.549 the CFT that when they're put to the 46:01.549 --> 46:04.000 test , we find out we have gaps . We 46:04.000 --> 46:05.944 might have been too focused on one 46:05.944 --> 46:08.590 particular threat stream or we've not 46:08.590 --> 46:10.312 leveraged what , you know , an 46:10.312 --> 46:12.257 adversary could bring bring to the 46:12.257 --> 46:15.230 table . But the the threat on the 46:15.230 --> 46:17.950 peninsula itself and the threat , you 46:17.950 --> 46:21.590 know regionally is considered uh , in 46:21.590 --> 46:23.812 that combatant command planning And its 46:23.812 --> 46:25.923 vetting and testing against Chad C2 . 46:26.480 --> 46:30.250 Okay , Thank you . Thank you sir . That 46:30.250 --> 46:32.330 concludes all the questions that we 46:32.330 --> 46:34.386 have . Let's turn it over to you for 46:34.386 --> 46:36.441 any closing comments . No , I I hope 46:36.441 --> 46:38.608 this is an ongoing dialogue . I really 46:38.608 --> 46:40.441 do appreciate the opportunity to 46:40.441 --> 46:42.497 interact . I think the questions are 46:42.497 --> 46:44.774 hard hitting . Uh , and they should be , 46:44.774 --> 46:46.997 I've given you the most honest answer I 46:46.997 --> 46:49.108 can on where I'm optimistic and where 46:49.108 --> 46:50.997 we have work to do this will be a 46:50.997 --> 46:53.108 journey for us . But a journey that I 46:53.108 --> 46:53.010 hope is different than we've had in the 46:53.010 --> 46:55.010 past , meaning that , you know , if 46:55.010 --> 46:57.232 this was a factory , we have a conveyor 46:57.232 --> 46:59.900 belt . We are now focused from , you 46:59.900 --> 47:02.122 know , our most senior leader on down , 47:02.180 --> 47:04.180 it's a delivery of a capability and 47:04.180 --> 47:06.236 we're gonna learn from it . It's not 47:06.236 --> 47:08.236 all going to be perfect , but we're 47:08.236 --> 47:10.347 going to learn by doing and that time 47:10.347 --> 47:10.030 has already started . I thank you for 47:10.030 --> 47:13.850 the opportunity . Thank you General 47:13.850 --> 47:15.683 and journalist . If you have any 47:15.683 --> 47:17.739 questions you need answered , please 47:17.739 --> 47:19.906 send them to me and I'll work with the 47:19.906 --> 47:22.128 joint staff on completing those . Thank 47:22.128 --> 47:24.294 you for calling in . Thank you General 47:24.294 --> 47:24.100 have a great day