WEBVTT 00:02.990 --> 00:05.157 Good morning , everyone and welcome to 00:05.157 --> 00:07.379 day two of the dous conference . I hope 00:07.379 --> 00:09.601 everyone enjoyed the socials last night 00:09.601 --> 00:11.712 and you're ready for another exciting 00:11.712 --> 00:13.546 day today as a reminder , please 00:13.546 --> 00:15.768 silence your cell phones at this time . 00:15.768 --> 00:17.879 Also , if everyone could please check 00:17.879 --> 00:19.879 your pockets for your cat card . If 00:19.879 --> 00:21.490 it's not there , it's at the 00:21.490 --> 00:23.850 registration desk downstairs . Kicking 00:23.860 --> 00:26.450 off day two , we have a fireside chat 00:26.459 --> 00:28.180 with the National Geospatial 00:28.190 --> 00:30.530 Intelligence Agency , Director , Vice 00:30.540 --> 00:33.159 Admiral Frank Whitworth and the DIA 00:33.169 --> 00:35.840 Chief Information Officer Mr Casa . 00:36.169 --> 00:38.280 Please welcome Vice Admiral Whitworth 00:38.280 --> 00:39.780 and Mr Casa to the stage . 00:57.400 --> 01:00.259 Right . Ok . Thank you everyone for 01:00.270 --> 01:02.381 joining us again this morning for our 01:02.381 --> 01:04.548 fireside chat to kick off day two . We 01:04.548 --> 01:06.714 are with Admiral Whitworth and just by 01:06.720 --> 01:08.831 way of background , Admiral Whitworth 01:08.831 --> 01:10.998 is the eighth director of the National 01:10.998 --> 01:12.998 Geospatial Intelligence Agency . Uh 01:12.998 --> 01:15.190 started that role in June of 2022 . 01:15.199 --> 01:17.459 Right . Right . And you've had several 01:17.470 --> 01:19.889 roles within the IC and dod previously 01:19.900 --> 01:22.699 for joining NGA . Uh you were the joint 01:22.709 --> 01:26.680 staff J two . Yeah , and uh spent also 01:26.690 --> 01:28.912 uh a significant amount of time working 01:28.912 --> 01:30.746 at combatant commands to include 01:30.746 --> 01:33.650 Centcom Jsoc Africom , uh and various 01:33.660 --> 01:35.900 roles throughout your career , even as 01:35.910 --> 01:38.110 a White House intelligence uh desk 01:38.120 --> 01:40.120 officer , which is fascinating . So 01:40.120 --> 01:42.342 quite , quite an extensive career . But 01:42.342 --> 01:44.398 in your current role in NGA , uh the 01:44.398 --> 01:46.564 the mission has changed over time when 01:46.564 --> 01:48.620 II I , my first job in the IC was 01:48.629 --> 01:50.851 actually at NGA . And I was telling you 01:50.851 --> 01:52.962 yesterday , I was uh I was a database 01:52.962 --> 01:55.073 administrator and this was post 911 . 01:55.073 --> 01:57.351 So this was in the early two thousands . 01:57.351 --> 01:59.351 So our focus was really rock Middle 01:59.351 --> 02:01.573 East . That was , that's where , that's 02:01.573 --> 02:03.740 where all of our emphasis was , that's 02:03.740 --> 02:05.573 changed over time . And that was 02:05.573 --> 02:07.685 actually with Nema . So the focus was 02:07.685 --> 02:09.907 on i at the time Imagery Intelligence , 02:09.907 --> 02:12.129 uh obviously , with the stand up of NGA 02:12.129 --> 02:14.018 expanded into GON uh and then the 02:14.018 --> 02:16.240 mission also changed . Uh So let's just 02:16.240 --> 02:18.351 start there for today . Tell us about 02:18.351 --> 02:20.629 how uh how NGA S focus has changed and , 02:20.629 --> 02:22.740 and where that operational uh mission 02:22.740 --> 02:24.796 as as assessment function is where , 02:24.796 --> 02:27.018 where are those emphasis areas ? Thanks 02:27.018 --> 02:29.185 Doug . Um First off , it's great to be 02:29.185 --> 02:30.962 here . I have actually , if you 02:30.962 --> 02:33.296 calculate over the course of the career , 02:33.296 --> 02:35.518 the amount of time I've spent either in 02:35.518 --> 02:38.619 Gio or with Dia um it's a substantial 02:38.630 --> 02:40.630 number about two thirds or so of my 02:40.630 --> 02:42.889 career has been , you know , with your 02:42.899 --> 02:46.399 organization . And so it feels right to 02:46.410 --> 02:49.059 be here right now now , on behalf of 02:49.070 --> 02:52.610 the 16,000 people of NGA , and I'm 02:52.619 --> 02:54.841 really proud of them . And , you know , 02:54.841 --> 02:56.841 I chose that music uh intentionally 02:57.789 --> 03:00.020 because the idea here , you know , we 03:00.029 --> 03:02.490 have , we have Ln Os all over the place . 03:02.500 --> 03:05.279 We have what we call NGA support teams 03:05.289 --> 03:07.940 at all of the co coms and services , a 03:07.970 --> 03:10.839 lot of other agencies and we're all 03:10.850 --> 03:13.500 over the place and if you're a decision 03:13.509 --> 03:16.360 maker or if you're a trigger puller or 03:16.369 --> 03:18.591 some sort of an operator out there with 03:18.591 --> 03:21.679 the joint force , or if you're a first 03:21.690 --> 03:23.746 responder trying to do some homeland 03:23.746 --> 03:25.809 security or doing some homeland 03:25.820 --> 03:27.949 response , everything's gonna be all 03:27.960 --> 03:30.127 right , if you've got NGA on your side 03:30.127 --> 03:32.940 and you know , I've had this 03:32.949 --> 03:35.410 conversation with the navy recently , 03:35.419 --> 03:39.220 we pay for one rider uh from NGA to 03:39.229 --> 03:42.720 be on the carrier strike groups , we 03:42.729 --> 03:45.399 choose to pay for that . Uh Because the 03:45.410 --> 03:47.729 image that I want uh at least for those 03:47.740 --> 03:50.490 7000 , you only have 7000 people within 03:50.500 --> 03:52.500 a carrier strike group is that they 03:52.500 --> 03:54.556 just inherited by virtue of that one 03:54.556 --> 03:57.029 ship rider , they just inherited the 03:57.039 --> 04:00.199 talents and the time and the energy of 04:00.210 --> 04:03.250 16,000 . And that's the way in my 04:03.259 --> 04:04.981 discussions with some of those 04:04.981 --> 04:07.203 commanders , that's the way they feel . 04:07.203 --> 04:09.250 So when you think about operational 04:09.339 --> 04:11.339 focus , which is the nature of your 04:11.339 --> 04:13.339 question , I could go any number of 04:13.339 --> 04:15.395 places . Of course , I have to go to 04:15.395 --> 04:17.617 the pacing challenge that the Secretary 04:17.617 --> 04:19.672 of Defense has identified , which is 04:19.672 --> 04:21.839 China and I'm really proud of the team 04:21.839 --> 04:23.839 over the past year and the way that 04:23.839 --> 04:25.728 we've stayed ahead of some of the 04:25.730 --> 04:28.989 occurrences in the South Pacific and 04:29.000 --> 04:32.769 South China Sea . And uh in our support 04:32.779 --> 04:34.859 of some of the great alliances that 04:34.869 --> 04:36.925 occur there , especially in maritime 04:36.925 --> 04:40.309 Domain awareness . And , you know , we 04:40.320 --> 04:42.589 have worked on a tool called Enhanced 04:42.600 --> 04:44.720 Domain awareness , which helps us 04:44.730 --> 04:47.670 monitor uh some of the behavior related 04:47.679 --> 04:49.735 unregulated fishing . That is a real 04:49.735 --> 04:51.623 problem for some really important 04:51.623 --> 04:55.250 countries out there . And so of course , 04:55.260 --> 04:57.709 I have to just begin with keeping pace 04:57.720 --> 05:00.149 with that pacing challenge . Russia , 05:00.160 --> 05:02.769 Ukraine has been a staple for us for a 05:02.779 --> 05:06.329 long time and it's been over two years . 05:06.589 --> 05:08.700 I'm really impressed with the ability 05:08.700 --> 05:10.367 of the team to keep pace with 05:10.367 --> 05:12.478 monitoring day to day tactical at the 05:12.478 --> 05:15.660 same time , keep tabs on strategic . Uh 05:15.670 --> 05:18.570 And then I saw a new gear within our 05:18.579 --> 05:22.420 workforce on October 7th a year ago , 05:23.670 --> 05:26.489 uh when we had what occurred in the 05:26.500 --> 05:29.630 horrors of the Hamas 05:30.829 --> 05:32.996 operation against the Israelis , where 05:32.996 --> 05:35.218 we were called upon by the president to 05:35.218 --> 05:37.769 ensure that Israel could defend itself 05:37.910 --> 05:39.966 against Hamas and regional threats . 05:39.966 --> 05:42.200 And we've lived up to that and I'm 05:42.209 --> 05:44.042 really proud of the team also in 05:44.042 --> 05:45.987 keeping that operational focus and 05:45.987 --> 05:48.153 ensuring that we tell the entire story 05:48.153 --> 05:50.290 so that if there are things to know 05:50.299 --> 05:52.410 about the environment , to understand 05:52.410 --> 05:54.577 the environment in Gaza or elsewhere , 05:54.577 --> 05:56.632 as it may relate to the humanitarian 05:56.632 --> 05:58.743 situation and the amount of damage or 05:58.743 --> 06:00.799 destruction we're telling the entire 06:00.799 --> 06:02.910 story . There's no shaping at NGA . I 06:02.910 --> 06:04.910 could offer the same thing with our 06:04.910 --> 06:07.021 operational focus in terms of telling 06:07.021 --> 06:09.021 the tale of and being predictive on 06:09.021 --> 06:11.077 North Korea and some of the launches 06:11.077 --> 06:13.510 that they've had recently uh ensuring 06:13.519 --> 06:16.309 that we also keep an eye on this very 06:16.320 --> 06:18.209 important access of supply that's 06:18.209 --> 06:20.431 occurring , that involves both Iran and 06:20.431 --> 06:23.380 North Korea in some cases , having an 06:23.390 --> 06:25.929 instrumental role in exposing that 06:25.940 --> 06:28.799 activity and ensuring that our decision 06:28.809 --> 06:30.753 makers have what they know to talk 06:30.753 --> 06:34.130 about it and respond to that . So , uh 06:34.140 --> 06:36.084 you know , the last thing that I'm 06:36.084 --> 06:38.140 gonna mention and it kind of goes to 06:38.140 --> 06:40.251 that music again . Everything's gonna 06:40.251 --> 06:42.251 be all right . That's kind of the , 06:42.251 --> 06:44.418 that's the visual and the audio that I 06:44.418 --> 06:46.540 have with our deploys who are called 06:46.549 --> 06:49.859 upon by a lawful request from FEMA at a 06:49.890 --> 06:52.929 time that some assistance needs to be 06:52.940 --> 06:56.700 made to Americans . And in the case of 06:57.790 --> 07:00.170 Milton and Helene , these two 07:00.179 --> 07:02.512 hurricanes that had devastating effects . 07:02.512 --> 07:04.623 We got the call at one point , we had 07:04.623 --> 07:07.589 20 people on the ground with 07:08.429 --> 07:10.651 one of our trailers that we have that's 07:10.651 --> 07:14.390 already prewired for communications and 07:14.399 --> 07:16.121 for printers and of course our 07:16.121 --> 07:18.010 exploitation equipment for lawful 07:18.010 --> 07:21.500 collect through commercial and they 07:21.510 --> 07:23.910 made a difference in identifying grid 07:23.920 --> 07:26.549 reference maps and waterproof maps and 07:26.559 --> 07:28.670 that kind of thing that go out to all 07:28.670 --> 07:30.615 the searchers and allowing them to 07:30.615 --> 07:32.670 organize themselves . And there was 07:32.679 --> 07:35.160 even an unprecedented use and lawful 07:35.170 --> 07:37.529 use of really carefully controlled uh 07:37.540 --> 07:40.619 you know , uh entity for some drone 07:40.630 --> 07:43.029 technology to go in places that humans 07:43.040 --> 07:44.873 just couldn't get was completely 07:44.873 --> 07:47.600 impassable . And then we also had up 07:47.609 --> 07:49.600 upwards of 25 people working this 07:49.609 --> 07:51.869 mission remotely , they didn't have to 07:51.880 --> 07:54.102 be there . They were just working on it 07:54.102 --> 07:56.213 remotely again through commercial and 07:56.213 --> 07:58.547 unclassified uh visual imagery analysis . 07:58.547 --> 08:01.160 And so I uh I , you know , I think uh 08:01.170 --> 08:03.170 your question is exactly right . We 08:03.170 --> 08:05.226 could spend 30 minutes talking about 08:05.226 --> 08:07.448 the operational focus of NGA . So thank 08:07.448 --> 08:10.019 you for that . So in all of those 08:10.029 --> 08:12.260 operations , NGA obviously collects and 08:12.269 --> 08:14.380 processes , a lot of data makes sense 08:14.380 --> 08:16.380 of it disseminates it to those that 08:16.380 --> 08:18.760 need it . Um W when I , when I was , 08:18.769 --> 08:20.880 when I was there in Nema , uh someone 08:20.880 --> 08:22.880 told me most of what we do hits the 08:22.880 --> 08:24.936 cutting room floor and as a database 08:24.936 --> 08:27.102 administrator , I would always get the 08:27.102 --> 08:26.799 request because I did the visualization 08:26.809 --> 08:29.040 and everything else as well of , you 08:29.049 --> 08:31.216 know , that Amazon thing where it says 08:31.216 --> 08:33.327 if you , if you like this , you might 08:33.327 --> 08:35.438 also like this . Everyone wanted that 08:35.438 --> 08:37.716 of tell me what I should be looking at . 08:37.716 --> 08:39.660 And so now , obviously , almost 20 08:39.660 --> 08:41.938 years later , more than 20 years later , 08:41.938 --> 08:41.609 we're talking about A I and the 08:41.619 --> 08:43.730 opportunities with A I . Can you talk 08:43.730 --> 08:46.250 about that and what G UN A I is , is uh 08:46.260 --> 08:48.371 advancing towards as your time as the 08:48.371 --> 08:50.482 director . Yeah , the preface to your 08:50.482 --> 08:52.649 question was about scale . And I think 08:52.649 --> 08:54.704 that uh this is a story of scale and 08:54.704 --> 08:56.871 it's appropriate that uh we've , we've 08:56.871 --> 08:59.469 inherited uh this responsibility for 08:59.479 --> 09:02.669 Gona I because Gon has a scale like 09:02.679 --> 09:04.679 none other . If you think about the 09:04.679 --> 09:06.512 number of ones and zeros that we 09:06.512 --> 09:09.059 transport across this globe , it's , 09:09.070 --> 09:11.840 it's , it's without peer in , in the 09:11.849 --> 09:13.738 agencies , at least of the United 09:13.738 --> 09:16.099 States . And so uh going for the 09:16.109 --> 09:18.919 hardest thing first addressing A I for 09:18.929 --> 09:20.873 that hardest thing , which is this 09:20.873 --> 09:22.820 massive network I think is uh is 09:22.830 --> 09:25.380 correct . So to answer your question , 09:25.390 --> 09:27.390 it's been a banner year . I'm gonna 09:27.390 --> 09:30.010 address tradecraft and standards and 09:30.020 --> 09:32.242 then talk a little bit about the future 09:32.559 --> 09:34.781 and let's talk about tradecraft because 09:34.781 --> 09:36.726 we have to baseline what everybody 09:36.726 --> 09:38.948 knows about the way A I applies to GE . 09:40.809 --> 09:43.619 So typically a human will go through an 09:43.630 --> 09:46.219 image which is a file which is data in 09:46.229 --> 09:48.451 and of itself , it's ones and zeros and 09:48.451 --> 09:50.673 it's very dense . Anybody who's taken a 09:50.673 --> 09:52.840 picture on Hi res accidentally and you 09:52.840 --> 09:54.896 try to send it and just chokes , you 09:54.896 --> 09:54.890 know , the deal that's us times 09:54.900 --> 09:57.909 gazillions , right ? So 09:59.450 --> 10:03.440 the human is looking for an object 10:03.450 --> 10:05.919 or a behavior that is really , really 10:05.929 --> 10:08.096 small relative to that field of view . 10:08.096 --> 10:10.280 And to give you some idea , most 10:10.289 --> 10:12.345 everybody in this room , if you came 10:12.345 --> 10:14.979 through an airport was treated to the 10:14.989 --> 10:18.049 marvels of computer vision . So your 10:18.059 --> 10:20.619 mug was up on a sensor either at TS a 10:20.630 --> 10:22.686 global entry , something like that . 10:22.686 --> 10:24.797 And you marveled at how it identified 10:24.797 --> 10:27.019 that's you . And you can pass , right ? 10:27.400 --> 10:31.159 Uh If it were only so easy in our work 10:31.169 --> 10:34.479 because your mug is about 80% of that 10:34.489 --> 10:37.909 field of view . What we're looking for , 10:37.919 --> 10:40.989 unique behaviors , anomalous things , 10:41.000 --> 10:44.070 objects , et cetera is about 2 , 100 10:44.080 --> 10:47.340 1000th of a percent of that field of 10:47.349 --> 10:49.679 view . So I think you have an idea of 10:49.690 --> 10:53.030 the challenge here . So how do you do 10:53.039 --> 10:55.760 it ? You , you run as much data and and 10:55.770 --> 10:57.603 that's where the coffers that we 10:57.603 --> 10:59.826 already have become so powerful because 10:59.826 --> 11:01.992 you run as much data through a process 11:01.992 --> 11:04.489 that involves also data labeling , 11:04.619 --> 11:08.039 identifying what that object is and 11:08.049 --> 11:11.869 then ultimately creating a model . So 11:11.880 --> 11:13.991 that then when that data runs through 11:13.991 --> 11:16.102 the model , it's it goes through what 11:16.102 --> 11:18.299 we call running inference which then 11:18.309 --> 11:22.020 runs into detections that we as humans 11:22.030 --> 11:25.859 can use . It accelerates and 11:25.869 --> 11:28.590 add scale to this otherwise very 11:28.599 --> 11:32.030 tedious process , right ? So there are 11:32.039 --> 11:35.070 some now that we have like hit the just 11:35.080 --> 11:37.080 the trade craft itself . Let's talk 11:37.080 --> 11:39.247 about some of the tools that have made 11:39.247 --> 11:41.358 some advancements over the year . Nga 11:41.358 --> 11:43.469 Maven is now a program of record . It 11:43.469 --> 11:46.679 is being employed by real world 11:46.690 --> 11:49.090 combatant commanders and there are at 11:49.099 --> 11:51.210 least four now who have it and I want 11:51.210 --> 11:53.321 it to be more and I know the CD O and 11:53.321 --> 11:55.599 the Department of Defense does as well . 11:55.599 --> 11:57.543 And we're working on that for real 11:57.543 --> 11:59.599 world operations . And that's very , 11:59.599 --> 12:02.020 very significant . Nga Maven is 12:02.030 --> 12:05.549 effectively a , a process that involves 12:05.559 --> 12:08.059 what I just described in Gona I and 12:08.070 --> 12:11.020 identifying opportunities and where it 12:11.030 --> 12:13.270 has made its mark here recently is in 12:13.280 --> 12:15.280 the combination also of a graphical 12:15.280 --> 12:18.510 user interface that is very agile where 12:18.520 --> 12:20.840 a commander can say I want , I , I've 12:20.849 --> 12:22.940 treasured knowing the confidence of 12:22.950 --> 12:24.561 what's out there in terms of 12:24.561 --> 12:27.809 opportunities . But I also want to have 12:27.820 --> 12:29.764 a little bit more in the targeting 12:29.764 --> 12:31.876 cycle . So it's applied mainly to the 12:31.876 --> 12:34.098 targeting cycle . And for us , we we're 12:34.098 --> 12:36.098 really into target development . So 12:36.098 --> 12:37.987 it's very helpful in the scale of 12:37.987 --> 12:40.209 target development in identifying those 12:40.209 --> 12:42.209 opportunities . But it , it also is 12:42.209 --> 12:44.289 attractive to the J threes and the J 12:44.299 --> 12:46.909 four s of the world and the commanders 12:46.919 --> 12:49.150 of the world because they can add other 12:49.159 --> 12:51.500 aspects of that cycle 12:53.130 --> 12:55.429 and our detections to answer the 12:55.440 --> 12:57.607 question of how you doing . Now in NGA 12:57.607 --> 12:59.829 Maven , our detections are way up . I'm 12:59.829 --> 13:01.940 not gonna go into how high they are , 13:01.940 --> 13:03.884 but they're way way up compared to 13:03.884 --> 13:06.107 where they were . When we inherited the 13:06.107 --> 13:08.219 program over a year ago , the models 13:08.229 --> 13:10.340 are way up . I was asked the question 13:10.340 --> 13:12.451 when I first inherited , do you think 13:12.451 --> 13:14.618 you'll just stick with one model ? And 13:14.618 --> 13:16.507 it's not that uh we have a lot of 13:16.507 --> 13:18.618 models because models can be tailored 13:18.618 --> 13:20.729 to different situations and different 13:20.729 --> 13:22.729 uh pieces of ground . So that's Nga 13:22.729 --> 13:25.719 Maven and that's targeting another 13:25.729 --> 13:28.020 concentration area for us warning , 13:29.059 --> 13:31.030 this is the big industrial geo 13:31.210 --> 13:33.409 targeting is rather acute campaign 13:33.419 --> 13:37.059 based warning is global . This is where 13:37.070 --> 13:40.219 you're establishing a baseline of 13:40.229 --> 13:42.451 objects and behaviors out there and you 13:42.451 --> 13:44.673 want some queuing that something is out 13:44.673 --> 13:46.785 of place , you want some queuing that 13:46.785 --> 13:49.007 there is something anomalous . And this 13:49.007 --> 13:51.173 is what the professionals of NGA spend 13:51.173 --> 13:53.479 most of their time and energy on . We 13:53.489 --> 13:55.989 want to prevent surprise . There is a 13:56.000 --> 13:59.460 program known as Aspen that is 13:59.469 --> 14:02.510 attempting to use A I and really good 14:02.520 --> 14:05.739 modeling to that end . And it's about , 14:05.750 --> 14:07.972 it's not just about detections and it's 14:07.972 --> 14:09.972 not just about infer it's about the 14:09.972 --> 14:12.219 entirety of keeping your stuff 14:12.229 --> 14:16.020 organized in workflow to include GIS 14:16.030 --> 14:19.580 data to include NAV data . Uh And with 14:19.590 --> 14:21.739 accuracy , GEOS spatially , we're 14:21.750 --> 14:23.806 really into geospatial accuracy . If 14:23.806 --> 14:25.861 there's one thing you take from this 14:25.861 --> 14:27.972 morning , it it needs to be , you can 14:27.972 --> 14:30.139 detect all you want . But if you don't 14:30.139 --> 14:29.700 know where on the earth it is with 14:29.710 --> 14:31.654 precision and accuracy , you got a 14:31.654 --> 14:34.450 problem . Yeah , then there's 14:34.460 --> 14:37.739 navigation and what I would like to 14:37.750 --> 14:41.270 identify as kind of fire and ice uh is 14:41.280 --> 14:43.640 an application of A I in very real 14:43.650 --> 14:45.817 terms . For instance , ice flows up in 14:45.817 --> 14:48.140 the Arctic . We have an A I model that 14:48.150 --> 14:50.317 actually helps us stay ahead of that , 14:50.317 --> 14:51.983 which is really important for 14:51.983 --> 14:54.119 navigation on fire . We have a model 14:54.130 --> 14:56.340 that helps the National Guard identify 14:56.349 --> 14:58.700 flash points that are occurring across 14:58.710 --> 15:01.849 this nation at least . So , um , you 15:01.859 --> 15:04.081 know , we have a responsibility for the 15:04.081 --> 15:05.803 safety of navigation that many 15:05.803 --> 15:08.109 Americans don't recognize or realize . 15:08.119 --> 15:10.286 And that is , if a plane is going into 15:10.286 --> 15:12.286 an airport , I'm talking especially 15:12.286 --> 15:14.580 about a dod plane or leaving it , it 15:14.590 --> 15:17.479 needs to have reliable data of every 15:17.489 --> 15:20.200 obstruction and that does change . And 15:20.210 --> 15:21.969 that's why we drive so many 15:21.979 --> 15:23.979 requirements that aren't just about 15:23.979 --> 15:26.201 warning and aren't just about targeting 15:26.201 --> 15:28.146 safety and navigation can never be 15:28.146 --> 15:30.312 forgotten in this regard . Yeah , when 15:30.312 --> 15:32.423 I , when I was uh involved in this uh 15:32.423 --> 15:35.059 quite some time ago , it it was , it 15:35.070 --> 15:37.237 was the shift from Nema to Nga and the 15:37.237 --> 15:39.237 tagline was know the know the earth 15:39.237 --> 15:41.292 show the way , right ? Which was the 15:41.292 --> 15:43.403 the focus of the world and the way we 15:43.403 --> 15:45.459 define the world was only through 12 15:45.459 --> 15:47.681 scenarios ranging from counterterrorism 15:47.681 --> 15:49.903 to natural disasters . But if there was 15:49.903 --> 15:52.070 a problem that didn't fit within those 15:52.070 --> 15:54.181 12 scenarios of modern in the world , 15:54.181 --> 15:56.292 it just wasn't important , right ? It 15:56.292 --> 15:55.869 was outside the scope of what we were 15:55.880 --> 15:57.880 looking at because there's just too 15:57.880 --> 16:00.047 much to deal with too many scenarios , 16:00.047 --> 16:02.269 too many types of data , too many types 16:02.269 --> 16:04.491 of missions . So I I've heard about NGA 16:04.491 --> 16:06.436 S Digital Twin effort to develop a 16:06.436 --> 16:08.658 living model of the world to try to get 16:08.658 --> 16:10.713 a handle on that . Can you , can you 16:10.713 --> 16:10.469 explain what that is ? Yeah . And so 16:10.479 --> 16:12.701 now you're moving into the future and I 16:12.701 --> 16:14.757 forgot on your last question to move 16:14.757 --> 16:17.090 into the future very quickly on A I and , 16:17.090 --> 16:19.729 and , and in one word , multimodal . So 16:19.739 --> 16:21.961 what I've been describing thus far on A 16:21.961 --> 16:24.183 I has largely been advances in computer 16:24.183 --> 16:26.406 vision and we've been doing in computer 16:26.406 --> 16:28.239 vision for a long time , but the 16:28.239 --> 16:30.461 advancements are now accelerating as as 16:30.461 --> 16:32.572 frankly the models and uh and some of 16:32.572 --> 16:35.090 the um tradecraft is improving 16:36.530 --> 16:40.390 now how to combine text and images 16:40.739 --> 16:42.906 and that's multimodal and that's where 16:42.906 --> 16:46.109 we're , we're literally um very excited 16:46.119 --> 16:48.549 about this . We , we want to ask 16:48.559 --> 16:51.349 questions about geospatial environments 16:51.580 --> 16:54.390 and get answers that are multimodal in , 16:54.400 --> 16:57.570 in context . And we have actually gone 16:57.580 --> 17:00.830 with an R and D foundational contract 17:00.840 --> 17:02.710 with Microsoft to come up with 17:02.719 --> 17:04.886 something like that . And that will be 17:04.886 --> 17:06.886 the beginning . The , the the world 17:06.886 --> 17:08.886 will be our oyster in that regard . 17:08.886 --> 17:10.886 Back to your question on Foundation 17:10.886 --> 17:13.449 Digital Twin . This gets to the 17:13.459 --> 17:15.570 navigation mission that I was talking 17:15.570 --> 17:17.709 about before . And there's a 17:17.719 --> 17:19.941 progression really , if you think about 17:19.941 --> 17:22.689 this over time , started with maps , 17:22.699 --> 17:24.699 good old fashioned , like literally 17:24.699 --> 17:26.866 just a two dimensional map that people 17:26.866 --> 17:28.900 would keep and hold and use to move 17:28.910 --> 17:31.449 from point A to point B safely . And we 17:31.459 --> 17:33.681 certainly had responsibility for that . 17:33.681 --> 17:35.737 Then it started then imagine a vault 17:35.737 --> 17:37.959 where you have tons of maps and you get 17:37.959 --> 17:40.126 into volumes for contingencies where , 17:40.126 --> 17:42.126 wherever you , if you're a deploy a 17:42.126 --> 17:44.348 military force , et cetera , you had to 17:44.348 --> 17:46.403 have a lot of maps . And we got into 17:46.403 --> 17:48.459 that and then we started recognizing 17:48.459 --> 17:50.570 that this is more efficient when it's 17:50.570 --> 17:52.792 done as a file . And so electronic maps 17:52.792 --> 17:55.015 have been uh really uh where we've been 17:55.015 --> 17:57.489 moving for the last decade or so . And 17:57.500 --> 17:59.667 so they're files , but again , they're 17:59.667 --> 18:01.939 individual files . The idea of 18:01.949 --> 18:04.116 foundational digital twin is to create 18:04.116 --> 18:06.560 a layer , a place where no matter where 18:06.569 --> 18:10.260 you are , you have foundational data of 18:10.270 --> 18:12.492 the earth that you can count on to move 18:12.492 --> 18:14.492 from point A to point B safely . So 18:14.492 --> 18:16.381 what's key to this and why are we 18:16.381 --> 18:18.430 making actually more progress today 18:18.439 --> 18:20.661 than ever ? It's largely because of the 18:20.661 --> 18:22.883 three dimension , the three dimensional 18:22.883 --> 18:25.050 piece of gon and the advancement we've 18:25.050 --> 18:27.640 had in the last year or two . Really . 18:28.000 --> 18:31.839 So precision and accuracy 18:31.849 --> 18:34.459 on a map is really , it's not just X 18:34.469 --> 18:36.580 and Y coordinates . People think it's 18:36.580 --> 18:38.959 just that long to be really , really 18:38.969 --> 18:41.469 precise . It's all about the Z , it's 18:41.479 --> 18:43.535 all about elevation . So when we say 18:43.535 --> 18:46.099 three dimensional geo is improving , 18:46.109 --> 18:49.170 therefore , foundational digital twin 18:49.180 --> 18:51.291 is improving . It's real . And I have 18:51.291 --> 18:53.349 metrics for this , our Office of 18:53.359 --> 18:56.699 Geography in the last year . So it's 18:56.709 --> 18:58.765 not even a full year yet in the last 18:58.765 --> 19:02.560 year has generated 60 years of 19:02.569 --> 19:05.650 products without some of this 3D 19:05.660 --> 19:07.827 technology , uh that they've been able 19:07.827 --> 19:11.599 to use and their responses to RFIS for 19:11.609 --> 19:13.942 products and , you know , spot products , 19:13.942 --> 19:15.998 et cetera . That's up like 50 or 60% 19:15.998 --> 19:17.998 compared to uh it , I think they're 19:17.998 --> 19:20.165 satisfying 50 to 60% of them when they 19:20.165 --> 19:22.630 used to average like 10% because these 19:22.640 --> 19:25.280 are really hard , so foundational 19:25.290 --> 19:27.569 digital twin , really important that , 19:27.579 --> 19:30.410 you know , if you are an aircraft or if 19:30.420 --> 19:32.642 you're a UAV technology or wherever you 19:32.642 --> 19:34.753 are on the globe , that there's going 19:34.753 --> 19:36.920 to be a layer that you can tap into at 19:36.920 --> 19:39.087 this rate . We believe that by the end 19:39.087 --> 19:41.569 of 2025 there should be a mesh of at 19:41.579 --> 19:44.750 least 2 m variety uh for the world . Uh 19:44.770 --> 19:47.020 that's a high bar to set , but given 19:47.030 --> 19:49.363 the acceleration we're seeing right now , 19:49.363 --> 19:52.989 we like where we stand . So Nro and 19:53.000 --> 19:56.229 NGA have collaborated for , for years 19:56.239 --> 19:59.069 on space overhead architecture and now 19:59.079 --> 20:01.190 Space Force is a component of that as 20:01.190 --> 20:02.857 well . Can you talk about the 20:02.857 --> 20:04.579 relationship between the three 20:04.579 --> 20:06.746 organizations ? What the benefit is of 20:06.746 --> 20:08.690 having those three organizations ? 20:08.690 --> 20:08.689 Because they don't , I don't think 20:08.699 --> 20:10.643 everyone understands the different 20:10.643 --> 20:12.699 components and disciplines that each 20:12.699 --> 20:14.477 bring to the table and then the 20:14.477 --> 20:16.699 opportunities to improve that support . 20:16.699 --> 20:18.810 It's so true . Uh I'll start with NRO 20:18.810 --> 20:21.032 and I've said this with Dr Scalise when 20:21.032 --> 20:23.143 he visits with us and he goes through 20:23.143 --> 20:25.199 our briefings and you know , and I , 20:25.199 --> 20:27.310 and I mean it publicly and , and just 20:27.310 --> 20:29.255 like I did privately , there is no 20:29.255 --> 20:31.143 organization with which NGA has a 20:31.143 --> 20:33.310 closer relationship than NRO . It is a 20:33.310 --> 20:35.199 sym , it is literally a symbiotic 20:35.199 --> 20:37.199 relationship . They can't get their 20:37.199 --> 20:39.366 mission done without us as an office . 20:39.366 --> 20:41.699 And in a world class acquisition office , 20:41.699 --> 20:43.866 we can't get our mission done as world 20:43.866 --> 20:45.921 class exploitation and dissemination 20:45.921 --> 20:48.143 without them . It's as simple as that . 20:48.143 --> 20:50.366 And so there are some other things that 20:50.366 --> 20:52.255 uh that I'll mention when I start 20:52.255 --> 20:54.477 talking about the space force that also 20:54.477 --> 20:56.366 involve NRO . And so it's kind of 20:56.366 --> 20:58.532 symbiotic between all of us . I really 20:58.532 --> 21:00.588 like the progress that we've made in 21:00.588 --> 21:02.810 our relationship with the United States 21:02.810 --> 21:04.866 Space Force really over the last six 21:04.866 --> 21:06.921 months or so I mentioned recently in 21:06.921 --> 21:09.088 another forum , it's been sort of like 21:09.088 --> 21:11.310 uh kind of a couple of months of eureka 21:11.310 --> 21:13.959 uh where the symbiotic relationship is 21:13.969 --> 21:16.219 becoming very clear . I like to think 21:16.229 --> 21:19.030 that it might be because of a uh an 21:19.040 --> 21:21.207 initiative that we launched called the 21:21.207 --> 21:23.318 Joint Mission Management Center JM MC 21:23.739 --> 21:26.180 because we've had similar episodes in 21:26.189 --> 21:28.300 the past . So what's going on here is 21:28.300 --> 21:30.522 the dod is buying its own constellation 21:30.522 --> 21:32.522 and that's gonna bring a tremendous 21:32.522 --> 21:35.369 amount of opportunity in the TP process . 21:35.380 --> 21:37.602 So for those of you who aren't familiar 21:37.602 --> 21:39.713 tasking , processing , exploitation , 21:39.713 --> 21:41.936 dissemination , we're talking about the 21:41.936 --> 21:43.991 tea here . This is all about the tea 21:43.991 --> 21:46.158 and things can get emotional about the 21:46.158 --> 21:48.380 tea because if you don't task it , it's 21:48.380 --> 21:50.491 not gonna get exploited , right . And 21:50.491 --> 21:52.602 so it matters to combatant commanders 21:52.602 --> 21:54.769 especially and anybody who cares about 21:54.769 --> 21:56.991 mission . So in the t when you're gonna 21:56.991 --> 21:59.158 have a constellation growing like that 21:59.158 --> 22:01.102 and especially with dod entities , 22:01.102 --> 22:03.324 we're a combat support agency , we care 22:03.324 --> 22:05.436 a lot about that . We wanna make sure 22:05.436 --> 22:07.658 we're complete . You gotta have a place 22:07.658 --> 22:09.936 for people to sit , look at each other , 22:09.936 --> 22:12.199 discuss priorities , set thresholds and 22:12.209 --> 22:14.320 then use really good technology . And 22:14.320 --> 22:16.320 we've got some good technology that 22:16.320 --> 22:17.876 combines opportunities with 22:17.876 --> 22:20.640 requirements . And these have literally 22:20.650 --> 22:23.099 been tested in some recent experiments , 22:23.109 --> 22:25.276 uh or not even experiments , they were 22:25.276 --> 22:28.479 true fledged exercises at end of paycom 22:28.939 --> 22:30.717 where you look at international 22:30.717 --> 22:32.883 opportunities , you look at commercial 22:32.883 --> 22:34.939 opportunities , you look at this new 22:34.939 --> 22:37.161 dod constellation opportunities and you 22:37.161 --> 22:39.050 look at your traditional national 22:39.050 --> 22:40.995 technical means and you know , the 22:40.995 --> 22:43.106 entire list of opportunities compared 22:43.106 --> 22:45.272 to the entire list of requirements and 22:45.272 --> 22:47.439 you can check them off . The idea here 22:47.439 --> 22:49.661 gets into stewardship , right ? Because 22:49.661 --> 22:49.660 as Americans , we're not interested in 22:49.670 --> 22:51.837 paying twice for the same point on the 22:51.837 --> 22:53.948 earth at the same point in time . And 22:53.948 --> 22:56.329 so this joint mission management center 22:56.770 --> 22:58.750 uh started as a great idea by our 22:58.760 --> 23:00.869 source director that we've been 23:00.880 --> 23:02.880 literally putting out there for 23:02.890 --> 23:05.489 comments and you know , a a complete 23:05.500 --> 23:08.199 concept of operations that you know 23:08.209 --> 23:10.153 we're really excited about . And I 23:10.153 --> 23:12.390 sense the same from the US space force 23:12.400 --> 23:14.780 because they helped us with it . This 23:14.790 --> 23:16.346 is a , this is something we 23:16.346 --> 23:18.457 collaborated on . NRO will be there . 23:18.457 --> 23:20.512 All the services the co coms are all 23:20.512 --> 23:22.568 invited . And of course , you know , 23:22.568 --> 23:24.780 since our people work at this every 23:24.790 --> 23:26.457 single night , they're called 23:26.457 --> 23:28.568 collection orchestrators , you know , 23:28.568 --> 23:30.401 combining the puzzle that is the 23:30.401 --> 23:32.650 weather and orbits and maintenance and 23:32.660 --> 23:34.438 priorities , which , you know , 23:34.438 --> 23:36.327 certainly we , we uh we were just 23:36.327 --> 23:39.030 talking about there's a place on the 23:39.040 --> 23:41.540 earth that does that . And we went IOC 23:41.550 --> 23:43.661 with this because we just simply , we 23:43.661 --> 23:45.717 took the same space where our people 23:45.717 --> 23:47.883 existed and do this for a living . And 23:47.883 --> 23:50.579 then we created desks and there and we 23:50.589 --> 23:52.645 already have NRO and we already have 23:52.645 --> 23:55.089 space force in that building . I'm 23:55.099 --> 23:57.210 sorry in that uh in that space of our 23:57.210 --> 23:59.130 building here in uh in Nga uh 23:59.140 --> 24:02.609 Washington . And it's exciting and the 24:02.619 --> 24:04.786 part that I don't talk as much about , 24:04.786 --> 24:06.897 but the reason we went IOC is because 24:06.897 --> 24:09.063 we actually wired it for sound for one 24:09.063 --> 24:11.008 of our allies because there's some 24:11.008 --> 24:12.952 investment there as well . I don't 24:12.952 --> 24:15.063 specify which one that's not needed , 24:15.063 --> 24:17.119 but just know that , you know , when 24:17.119 --> 24:19.119 you're looking at international dod 24:19.119 --> 24:21.452 commercial and national technical means , 24:21.452 --> 24:23.508 there's a place where that stuff can 24:23.508 --> 24:25.841 accumulate and people can talk about it . 24:25.841 --> 24:28.670 And that's the JM MC on commercial . 24:28.680 --> 24:31.013 And I know we're going to get into this . 24:31.013 --> 24:33.180 But the relationship that we have with 24:33.180 --> 24:35.291 NRO and the relationship that we have 24:35.291 --> 24:37.347 with the US Space Force is also very 24:37.347 --> 24:39.236 important . Uh If I could buy the 24:39.239 --> 24:41.420 pixels , I would . But my lot in life 24:41.430 --> 24:43.790 and I'm saying our really NGA lot in 24:43.800 --> 24:45.967 life is to buy analysis and we'll talk 24:45.967 --> 24:49.439 about that in a few minutes . But the 24:49.449 --> 24:51.505 US Space Force has this thing called 24:51.505 --> 24:54.790 tech S RT . And both the US Space Force 24:54.800 --> 24:56.967 and NGA have determined we're gonna be 24:56.967 --> 24:59.839 in lockstep on how the tech S RT and 25:00.479 --> 25:03.949 our analytics and Nr Os bought pixels . 25:04.180 --> 25:06.319 Uh all keep tabs on , you know , 25:06.329 --> 25:09.119 basically the needs versus the shots . 25:09.130 --> 25:11.130 OK . So that we're not shooting the 25:11.130 --> 25:13.130 same place on the earth and wasting 25:13.130 --> 25:15.910 taxpayer money . And uh I think that uh 25:15.920 --> 25:17.587 when you look at the whole of 25:17.587 --> 25:19.864 government approach here , uh you know , 25:19.864 --> 25:21.587 we represent a really powerful 25:21.587 --> 25:24.140 microcosm uh you know , as uh as your 25:24.150 --> 25:27.469 question suggests . So Doctor Stacey 25:27.479 --> 25:29.701 Dixon was here yesterday and one of the 25:29.701 --> 25:31.646 questions I asked her was cultural 25:31.646 --> 25:33.859 policy changes in the IC . What is , 25:33.869 --> 25:36.091 what is she observed as her time as PDD 25:36.091 --> 25:38.036 and I and , and her role in the IC 25:38.036 --> 25:40.258 throughout her career and she mentioned 25:40.258 --> 25:42.930 commercial imagery uh and how that 25:42.939 --> 25:45.449 really correct , created a mindset s 25:45.709 --> 25:47.859 mind shift change as well as a policy 25:47.869 --> 25:49.980 change . Can you , can you talk about 25:49.980 --> 25:52.036 NGA S role in commercial space going 25:52.036 --> 25:54.147 into the future , especially with the 25:54.147 --> 25:56.313 growing number of sensors in the sky ? 25:56.313 --> 25:58.536 Yes . Um and I gave you a little primer 25:58.536 --> 26:00.425 on this . Um and it , it involves 26:00.425 --> 26:02.949 analytics and this is where for a group 26:02.959 --> 26:05.181 like this and this is such an important 26:05.181 --> 26:07.859 team . Um I need to just articulate a 26:07.869 --> 26:10.290 few dollars , ok ? Because dollars 26:10.300 --> 26:14.180 count and um and as stewards uh of 26:14.189 --> 26:16.356 those dollars , I'm gonna go ahead and 26:16.356 --> 26:18.411 make sure , you know , they're being 26:18.411 --> 26:20.750 spent . Well , so our lot in life is to 26:20.760 --> 26:22.816 uh contract for commercial analytics 26:22.816 --> 26:25.038 and it's been a very , very busy year . 26:25.038 --> 26:27.260 Uh People may be aware of what's called 26:27.260 --> 26:29.260 Luna A and B . These are commercial 26:29.260 --> 26:31.371 analytics , largely driven by some of 26:31.371 --> 26:33.593 the requirements they received from the 26:33.593 --> 26:35.427 former Indo Paycom chief on some 26:35.427 --> 26:37.482 aspects of maritime domain awareness 26:37.482 --> 26:39.704 and to ensure that we had best of breed 26:39.704 --> 26:42.219 commercial analytics applying there and 26:42.290 --> 26:44.849 Luna A and B collectively , it's $500 26:44.859 --> 26:47.819 million . Luna A is an ID IQ for about 26:47.829 --> 26:51.349 290 uh with 10 vendors . OK . So 26:51.359 --> 26:53.415 spreading the load out there getting 26:53.415 --> 26:55.637 the best that we have from the American 26:55.637 --> 26:57.581 commercial industry . Uh Luna B is 26:57.581 --> 26:59.750 expected to be awarded in 2025 . 27:00.599 --> 27:02.849 Another exciting thing and this goes , 27:02.859 --> 27:04.581 this is where I'm gonna tie uh 27:04.581 --> 27:08.560 commercial with A I is 27:09.010 --> 27:11.229 uh a request for proposal that we made 27:11.239 --> 27:13.350 in September . You may have seen this 27:13.350 --> 27:16.300 for $700 million for data labeling . 27:17.380 --> 27:19.602 I would love for our people to have the 27:19.602 --> 27:22.420 time of the day to do all the data 27:22.430 --> 27:25.939 labeling needed for A A I and machine 27:25.949 --> 27:28.005 learning ess essentially for machine 27:28.005 --> 27:30.005 learning . And we talked about that 27:30.005 --> 27:32.227 process before , but that's actually an 27:32.227 --> 27:34.393 additional requirement on our people's 27:34.393 --> 27:37.390 time . So we need to pay for it . We're 27:37.400 --> 27:39.678 working towards the end where we won't . 27:39.678 --> 27:42.160 But for now , uh we have to pay $700 27:42.170 --> 27:44.359 million . That is a request for 27:44.369 --> 27:47.770 proposal called Sequoia . So again , 27:47.780 --> 27:51.560 the commercial sector for us uh is such 27:51.569 --> 27:54.180 an important teammate and I just want 27:54.189 --> 27:57.209 to underscore that and then the kind of 27:57.219 --> 28:00.489 the question why is this important when 28:00.500 --> 28:02.389 you get right down to mission and 28:02.389 --> 28:05.319 combining availability of commercial 28:05.329 --> 28:07.496 with your traditional NTM and what dod 28:07.496 --> 28:10.079 is building ? And I used to have a 28:10.089 --> 28:12.200 mentor who told me I just want it all 28:12.349 --> 28:15.290 and that's true . So coverage counts , 28:15.880 --> 28:17.880 resolution , of course counts , but 28:17.880 --> 28:21.430 coverage counts as well . And secondly , 28:21.599 --> 28:23.710 commercial brings the ability to tell 28:23.710 --> 28:25.766 the tale in forums where you weren't 28:25.766 --> 28:28.719 able to tell the tale before Ukraine is 28:28.729 --> 28:31.709 a great example of this . So there are 28:31.719 --> 28:35.479 over 400,000 users of a portal called 28:35.489 --> 28:38.380 GEGD . And that's a commercial portal 28:38.390 --> 28:41.280 that allows vetted members of that 28:41.290 --> 28:44.479 community to reach and get commercial 28:44.489 --> 28:47.560 data , commercial imagery . Immediately . 28:48.010 --> 28:50.920 There's no middle person who says 28:51.130 --> 28:53.130 you're gonna see that or you're not 28:53.130 --> 28:55.297 going to see this . Now , that doesn't 28:55.297 --> 28:57.408 happen if it's a commercial image and 28:57.408 --> 28:59.430 it's part of GGD , that means the 28:59.439 --> 29:01.650 Ukrainians will get it . Now , I'm not 29:01.660 --> 29:03.438 gonna fall prey to some sort of 29:03.438 --> 29:05.549 insinuation that that helped the Kirk 29:05.549 --> 29:07.660 initiative . I've heard this before . 29:07.660 --> 29:09.716 No , I'm gonna cite exactly what the 29:09.716 --> 29:11.810 Deputy of CIA said that Kirk was a 29:11.819 --> 29:14.770 surprise but in allowing Ukraine to 29:14.780 --> 29:16.930 defend themselves , make no mistake 29:16.939 --> 29:19.050 that that portal and the availability 29:19.050 --> 29:20.606 of commercial imagery , the 29:20.606 --> 29:22.439 availability to talk about it as 29:22.439 --> 29:24.272 opposed to some of our exquisite 29:24.272 --> 29:26.050 methods that's been very , very 29:26.050 --> 29:28.161 powerful . So we ended yesterday with 29:28.161 --> 29:30.890 Doctor Dixon and General Henry talking 29:30.900 --> 29:32.900 a lot about integration and efforts 29:32.900 --> 29:34.900 around the community , which is the 29:34.900 --> 29:37.067 definition and an engineering sense of 29:37.067 --> 29:39.233 integration is interrelated components 29:39.233 --> 29:38.609 working together towards a common 29:38.619 --> 29:40.869 objective part of testing that 29:40.880 --> 29:44.189 relationship is through exercises . So 29:44.199 --> 29:46.421 in our last minute or so here , can you 29:46.421 --> 29:48.930 talk about NGS role in Global Thunder ? 29:48.969 --> 29:50.747 Oh yeah , great way to finish , 29:50.747 --> 29:52.913 especially here at us Stratcom . And I 29:52.913 --> 29:55.025 just had a great meeting with members 29:55.025 --> 29:57.191 of the Stratcom staff culminating with 29:57.191 --> 29:59.247 uh General Cotton yesterday . And we 29:59.247 --> 30:01.469 promoted one of our seniors actually uh 30:01.469 --> 30:03.750 to uh to a really important post as he 30:03.760 --> 30:07.140 leads our NGA team here . So this is a 30:07.579 --> 30:10.040 strategic and in some cases , a field 30:10.050 --> 30:12.272 exercise that tests all of the elements 30:12.272 --> 30:14.689 of us of what us stratcom is all about . 30:15.180 --> 30:17.010 And it's very , I think it's 30:17.020 --> 30:19.020 appropriate for us given that we're 30:19.020 --> 30:21.030 embedded in all of the combatant 30:21.040 --> 30:23.151 commands . And this is testing almost 30:23.151 --> 30:25.310 every one of the plans that at least 30:25.319 --> 30:27.541 are integrated into the Unified Command 30:27.541 --> 30:31.420 uh plan . Um It tests our ability to 30:31.430 --> 30:33.652 do , targeting , it , tests our ability 30:33.652 --> 30:35.874 to do warning , it tests our ability to 30:35.874 --> 30:38.910 do safety of navigation on a global 30:38.920 --> 30:41.959 level . And so we have people who are 30:41.969 --> 30:44.025 at strategic levels with co coms and 30:44.025 --> 30:46.191 especially with General Cotton and his 30:46.191 --> 30:48.247 command element . And then we've got 30:48.247 --> 30:50.247 people who are out with the trigger 30:50.247 --> 30:52.191 pullers and out with those fielded 30:52.191 --> 30:54.080 forces and to finish it addresses 30:54.080 --> 30:56.413 something where we really cut our teeth . 30:56.413 --> 30:58.525 And that is strategic warning of some 30:58.525 --> 31:00.580 sort of vertical escalation . When I 31:00.580 --> 31:02.413 mention warning and I talk about 31:02.413 --> 31:04.747 baselining and saying this is anomalous . 31:04.747 --> 31:06.747 This is something you need to worry 31:06.747 --> 31:08.802 about . Make no mistake every single 31:08.802 --> 31:10.691 day when we have an ops and intel 31:10.691 --> 31:12.858 update , it begins with the chances of 31:12.858 --> 31:15.025 vertical escalation . It always begins 31:15.025 --> 31:16.969 in that nuclear realm . And I hope 31:16.969 --> 31:19.191 Americans feel better about that , that 31:19.191 --> 31:21.136 they've got . Again , everything's 31:21.136 --> 31:20.770 gonna be all right , if you got the NGA 31:20.780 --> 31:22.891 on your side , looking to ensure that 31:22.891 --> 31:25.002 you're not going to have some sort of 31:25.002 --> 31:27.113 vertical escalation , which of course 31:27.113 --> 31:26.560 is something we all want to avoid . 31:26.569 --> 31:28.625 This is the essence of deterrence is 31:28.625 --> 31:30.847 knowing that you might have a problem . 31:30.847 --> 31:33.013 Yeah . Well , thank you for that . And 31:33.013 --> 31:32.810 thanks for joining us today . I I think 31:32.819 --> 31:35.135 it highlights it's especially with NGA , 31:35.145 --> 31:37.367 the role of technology and how that not 31:37.367 --> 31:39.367 only supports the mission that your 31:39.367 --> 31:41.423 agency does and really the entire IC 31:41.423 --> 31:43.534 and dod , but it is the mission these 31:43.534 --> 31:45.756 days . So thank you so much for joining 31:45.756 --> 31:47.812 us today with teammates like Dia and 31:47.812 --> 31:49.867 the commercial sector . We can do no 31:49.867 --> 31:51.867 wrong . Thank you . Appreciate it . 31:51.867 --> 31:52.680 Thank you . Thanks .