WEBVTT

00:00.439 --> 00:02.550
All right , welcome back , everyone .

00:02.550 --> 00:05.150
Uh as we get closer to the end of this

00:05.159 --> 00:09.090
conference , um I'd

00:09.100 --> 00:11.156
like to say thank you all for uh for

00:11.156 --> 00:13.378
attending . This has been fantastic for

00:13.378 --> 00:15.378
me . Uh Mr Costa said earlier in uh

00:15.378 --> 00:17.829
earlier this week , uh One of us was

00:17.840 --> 00:19.896
vol and told one of us volunteered ,

00:19.896 --> 00:22.007
right ? Uh Everybody's been asking me

00:22.007 --> 00:24.229
that question . Um Captain Whiteley has

00:24.229 --> 00:26.451
done a fantastic job as the MC . So I'd

00:26.451 --> 00:28.396
like to say , uh thank you Captain

00:28.396 --> 00:30.618
Whiteley for uh for , for , for helping

00:30.618 --> 00:32.840
out with this conference , uh and , and

00:32.840 --> 00:35.173
helping uh helping MC this year because ,

00:35.173 --> 00:37.340
uh you know , you get up here in front

00:37.340 --> 00:36.909
of these lime lights and it gets a

00:36.919 --> 00:39.086
little , you get a little sweaty , you

00:39.086 --> 00:41.252
can't really see the crowd . Um Well ,

00:41.252 --> 00:43.475
if you haven't made up your mind , I'll

00:43.475 --> 00:43.119
give you the answer to the , to , to

00:43.130 --> 00:46.319
that , right ? Uh I love to get up here

00:46.330 --> 00:48.386
in front of the crowd and I asked Mr

00:48.386 --> 00:50.386
Cost , I said , sir , can I , can I

00:50.386 --> 00:52.330
please MC this year for , for this

00:52.330 --> 00:54.441
year's notice ? Uh He said , you know

00:54.441 --> 00:56.663
what chief you got the job , right ? Um

00:56.663 --> 00:58.497
and I share a little bit of that

00:58.497 --> 01:00.608
wanting for the limelight with the uh

01:00.608 --> 01:02.774
with the moderator of our next panel .

01:02.774 --> 01:06.769
So , so next up ,

01:06.779 --> 01:09.400
we have our uh service intelligence cio

01:09.410 --> 01:12.370
panel uh who will be moderated by , by

01:12.379 --> 01:15.870
Dia S deputy Cio Mr Ep Matthews .

01:16.129 --> 01:18.550
Um I don't wanna steal any more of your

01:18.559 --> 01:20.448
limelight , sir . I know how much

01:20.448 --> 01:22.337
you're excited to get up here and

01:22.337 --> 01:24.392
really just be in front of , of this

01:24.392 --> 01:26.503
crowd . So , uh without further ado ,

01:26.503 --> 01:28.670
please , uh welcome Mr Ep Matthews and

01:28.670 --> 01:30.948
the rest of our panelists to the stage ,

01:31.129 --> 01:34.949
baby . This is what you came for .

01:36.010 --> 01:38.900
Name strikes every time she moves .

01:43.470 --> 01:45.610
God is watching her , but she's

02:00.989 --> 02:03.100
all right . Uh Thank you , Chief . Uh

02:03.100 --> 02:06.230
You definitely got me . Um , before we

02:06.239 --> 02:07.959
get started , you know , this

02:07.970 --> 02:09.803
conference would not be possible

02:09.803 --> 02:11.940
without multiple people helping out

02:11.949 --> 02:14.429
there is one person in Cio that is

02:14.440 --> 02:16.662
leaving us today . It's the last , last

02:16.662 --> 02:18.607
day . Um Someone who's worked very

02:18.607 --> 02:20.829
closely with us , it's Mark Zola . If I

02:20.829 --> 02:22.607
could just recognize him , he's

02:22.607 --> 02:24.384
responsible for setting up this

02:24.384 --> 02:26.440
conference , working with his team .

02:26.440 --> 02:26.289
Mark if you could stand up .

02:30.360 --> 02:31.360
Thank you .

02:34.539 --> 02:36.539
Ok . So the theme song , you know ,

02:36.539 --> 02:38.706
this is what you , this is what you're

02:38.706 --> 02:40.761
waiting for , right ? We know we had

02:40.761 --> 02:42.983
fillers for the last two days . This is

02:42.983 --> 02:45.150
what you're waiting for , right ? Ok .

02:45.150 --> 02:47.372
So let's start . Uh could you introduce

02:47.372 --> 02:49.595
yourself what organization you work and

02:49.595 --> 02:51.928
your favorite candy . My favorite candy .

02:51.928 --> 02:53.761
Well , thank you very much . I'm

02:53.761 --> 02:53.509
Christopher Page . I'm from the United

02:53.520 --> 02:55.631
States Navy . I'm the Deputy Director

02:55.631 --> 02:57.464
of Intelligence Capabilities and

02:57.464 --> 02:59.631
Systems for OP N A which is the Navy's

02:59.631 --> 03:01.687
headquarters staff . And my favorite

03:01.687 --> 03:03.798
candy . I'll go with baby Ruth . Ok .

03:03.910 --> 03:06.021
I'm Colonel Mike , Ma Jesse . I'm the

03:06.021 --> 03:08.132
Air Force Intelligence , CIO . And my

03:08.132 --> 03:11.330
favorite candy is Snickers . I'm Lisa

03:11.339 --> 03:14.649
Lee . I am the Marine Corps uh command

03:14.660 --> 03:16.216
information Officer for the

03:16.216 --> 03:18.271
Intelligence Division under the DC I

03:18.271 --> 03:20.382
and also the authorizing official and

03:20.382 --> 03:22.382
program manager for Skynet . And my

03:22.382 --> 03:24.327
favorite candy is little root beer

03:24.327 --> 03:28.220
barrels . I love them . Uh So I'm

03:28.229 --> 03:29.896
David Pierce . I'm the Army's

03:29.896 --> 03:32.062
Intelligence chief , data officer . So

03:32.062 --> 03:34.804
I'm not the cio but um I am on the

03:34.815 --> 03:36.871
panel here . I would say my favorite

03:36.871 --> 03:39.375
candy is uh let's see here Payday ,

03:39.384 --> 03:41.794
maybe that was yesterday . Uh But

03:41.804 --> 03:44.494
that's good . OK . OK . So let's get

03:44.505 --> 03:46.505
started . Uh Lisa , you're the only

03:46.505 --> 03:48.800
woman on this panel . Um There , there

03:48.809 --> 03:51.020
might be uh women who are sitting on

03:51.029 --> 03:53.140
that audience who , you know , 11 day

03:53.140 --> 03:55.251
would like to sit on the stage . What

03:55.251 --> 03:57.473
are some of the struggles that you went

03:57.473 --> 03:59.640
through ? Um you know , the challenges

03:59.640 --> 04:01.973
that , that you went through , you know ,

04:01.973 --> 04:01.770
as you went through your journey of

04:01.779 --> 04:03.835
this , of this career , what jobs do

04:03.835 --> 04:05.940
you take ? What did it cost you and

04:05.949 --> 04:08.227
what are you doing to help others ? Oh ,

04:08.270 --> 04:11.660
Lisa , let me help you with that . All

04:11.669 --> 04:13.669
right , relax . That was , that was

04:13.669 --> 04:15.270
planned . That was not Mike

04:15.279 --> 04:18.950
mansplaining . Go ahead . Well ,

04:18.959 --> 04:21.410
thank you , Colonel . Thanks for the

04:21.420 --> 04:24.190
question . Ep so I started my career um

04:24.200 --> 04:28.070
back in 1998 . Yeah , so 26 years ago

04:28.250 --> 04:31.700
as a transportation specialist intern .

04:31.709 --> 04:35.109
So uh I then morphed into a 2210

04:35.119 --> 04:38.250
position , which was it . And um so

04:38.260 --> 04:40.371
there are two challenges really , you

04:40.371 --> 04:42.593
know , back in the late nineties I came

04:42.593 --> 04:44.816
in , um , I , I was , of course a woman

04:44.816 --> 04:46.927
and then , uh , when I got moved into

04:46.927 --> 04:48.816
the , it , I found out that I was

04:48.816 --> 04:51.093
really uh a minority , right ? In that ,

04:51.093 --> 04:53.700
in that perspective . So , um , uh ,

04:53.709 --> 04:56.929
throughout my career , uh I um took

04:56.940 --> 05:00.359
advantage of listening to some of my

05:00.369 --> 05:02.425
mentors where they said , you know ,

05:02.425 --> 05:04.480
hey , you have to , you have to move

05:04.480 --> 05:06.591
around in order to get promoted . And

05:06.591 --> 05:08.536
of course , I started off as a GGS

05:08.536 --> 05:11.079
seven , right ? Um And , um , work my

05:11.089 --> 05:13.311
way up . In fact , we were just talking

05:13.311 --> 05:15.630
the other day , $12.98 an hour was ,

05:15.640 --> 05:17.807
was my hourly wage when I started back

05:17.807 --> 05:20.470
in 1998 which is crazy , right ? To

05:20.480 --> 05:24.000
think that , um , so I , I did those

05:24.010 --> 05:26.160
things , uh I , I did sacrifice , uh

05:26.170 --> 05:28.489
time with my family growing up with my

05:28.500 --> 05:31.820
three boys . Um in order to , um , you

05:31.829 --> 05:34.170
know , go , go through my career and I

05:34.179 --> 05:36.619
did it several times . Have to feel

05:36.630 --> 05:39.470
like I have had to prove myself to some

05:39.480 --> 05:41.980
of the workforce , uh , as a woman to

05:41.989 --> 05:43.980
say , you know , hey , I , I do

05:43.989 --> 05:46.267
understand it . I , I'm not , you know ,

05:46.267 --> 05:48.433
just a dumb blonde . Right . Because I

05:48.433 --> 05:50.489
think that's the kind of stigma that

05:50.489 --> 05:52.545
you get sometimes . Um , and , and I

05:52.545 --> 05:55.019
have found over the years that the , uh ,

05:55.029 --> 05:57.500
climate has changed dramatically and

05:57.510 --> 06:00.329
the evolution of , of , um , how , uh ,

06:00.339 --> 06:03.100
females are appreciated . They're given

06:03.380 --> 06:05.890
uh time off uh when they're having

06:05.899 --> 06:08.010
their Children and even the paternity

06:08.010 --> 06:09.843
leave that they're given for the

06:09.843 --> 06:12.010
husbands , it's making it easier . And

06:12.010 --> 06:13.955
there's this , this um family life

06:13.955 --> 06:15.788
balance that everyone is , is uh

06:15.788 --> 06:17.899
talking about now . And that's what I

06:17.899 --> 06:19.621
try to , to implement uh in my

06:19.621 --> 06:22.540
organization . And also uh for , for

06:22.549 --> 06:24.989
the the females that I have that wanna

06:25.000 --> 06:27.167
be me someday . You know , it's , it's

06:27.167 --> 06:29.630
not just doing one thing , right ? You

06:29.640 --> 06:31.709
have to know a little bit about

06:31.720 --> 06:34.630
everything to become a manager . You

06:34.640 --> 06:36.807
have to know budget , you have to know

06:36.807 --> 06:38.807
how to talk to people , you have to

06:38.807 --> 06:40.918
know how to talk in front of people .

06:40.918 --> 06:42.918
But you also have to understand the

06:42.918 --> 06:45.029
technology and you have to understand

06:45.029 --> 06:46.640
how to translate between the

06:46.640 --> 06:49.260
engineering community and the executive

06:49.269 --> 06:51.380
community , right ? And that's really

06:51.420 --> 06:54.279
uh an , an art , right ? And you have

06:54.290 --> 06:56.739
to learn that and , and get good at it .

06:56.750 --> 06:59.220
So um that's what I would , that's what

06:59.230 --> 07:02.369
I would say . Um For folks who wanna be

07:02.380 --> 07:05.510
me someday . Um diversify what you're

07:05.519 --> 07:09.420
doing from a , from a um uh area of

07:09.429 --> 07:12.000
specialty , right ? Acquisition . All

07:12.010 --> 07:14.869
that you have to know what and uh uh

07:14.880 --> 07:17.510
don't just stick with one thing and be

07:17.519 --> 07:20.549
flexible , but I do believe that um

07:20.809 --> 07:23.339
that the atmosphere is , is very much

07:23.350 --> 07:25.869
welcoming now to , to uh minority

07:25.880 --> 07:28.109
diverse , all that . It's great . OK ,

07:28.559 --> 07:30.709
Chris , uh when you were commissioned

07:31.000 --> 07:34.290
um Doug was just Born dota Conference

07:34.299 --> 07:36.859
didn't exist , Jay Wicks didn't exist .

07:37.299 --> 07:39.299
Um What are the challenges you face

07:39.299 --> 07:41.521
then that you don't face now ? And what

07:41.521 --> 07:43.688
are the some , what are the challenges

07:43.688 --> 07:45.799
that young people face today that you

07:45.799 --> 07:45.500
didn't have to face ? Well , thank you

07:45.510 --> 07:47.288
very much and thank you for the

07:47.288 --> 07:49.288
question . I , as I think about the

07:49.288 --> 07:51.529
navy that I joined and again , um

07:51.609 --> 07:54.350
signed up in 1984 commissioned in 88

07:54.410 --> 07:56.354
and at the time , what was the big

07:56.354 --> 07:58.243
challenge ? Well , we had a major

07:58.243 --> 08:01.010
communist power that uh was doing

08:01.019 --> 08:03.186
things that was a great concern to the

08:03.186 --> 08:05.186
United States . And so we were very

08:05.186 --> 08:07.820
interested in deterring the possibility

08:07.829 --> 08:09.940
of a thermonuclear war . But the same

08:09.940 --> 08:12.705
time , we were concerned about conflict

08:12.716 --> 08:14.605
below that level . And so we were

08:14.605 --> 08:16.716
spending a lot of time organizing and

08:16.716 --> 08:18.805
training and getting ourselves ready

08:18.816 --> 08:21.476
for the potential for conflict . At the

08:21.485 --> 08:23.596
same time , there were trouble in the

08:23.596 --> 08:25.485
Middle East and I found myself uh

08:25.485 --> 08:27.707
deployed quite quickly to what was then

08:27.707 --> 08:29.763
called the Persian Gulf dealing with

08:29.763 --> 08:31.818
troubles caused by Iran . If I think

08:31.818 --> 08:33.818
about all that , I , I realize that

08:33.818 --> 08:35.707
that old saying , the more things

08:35.707 --> 08:37.874
change , the more they stay the same ,

08:37.874 --> 08:39.929
very much applies . And even further

08:39.929 --> 08:42.096
when I think about what has stayed the

08:42.096 --> 08:44.152
same , it is still about bringing in

08:44.152 --> 08:46.263
the best and brightest from America ,

08:46.263 --> 08:48.429
bringing together a bunch of strangers

08:48.429 --> 08:50.596
and turning them into a crew , turning

08:50.596 --> 08:52.818
them into true brothers and sisters and

08:52.818 --> 08:54.763
getting them into uh doing the the

08:54.763 --> 08:56.929
adventure of a lifetime . Now , having

08:56.929 --> 08:56.702
said that a lot of things have changed .

08:56.711 --> 08:58.878
All right . So if I think about uh one

08:58.878 --> 09:01.481
example and Lisa tripped on that , the ,

09:01.919 --> 09:04.141
we thought we were diverse , we weren't

09:04.141 --> 09:06.252
even close . And if I think about the

09:06.252 --> 09:08.141
diversity that we've embraced the

09:08.141 --> 09:10.308
diversity , we still have to embrace ,

09:10.308 --> 09:12.308
you know , we recognize that that's

09:12.308 --> 09:14.419
where our strength as Americans comes

09:14.419 --> 09:14.229
from . And we're very much seeing that

09:14.239 --> 09:16.350
strength brought into the Navy . If I

09:16.350 --> 09:18.461
think about data , you know , it used

09:18.461 --> 09:20.406
to be that most of the information

09:20.406 --> 09:22.450
leaving the ship was the form of a

09:22.460 --> 09:24.440
narrative report at best , right ?

09:24.500 --> 09:27.150
Where now there's a lot more of a , of

09:27.159 --> 09:30.309
a desire to send out data and to make

09:30.320 --> 09:32.264
it actually meaningful and have it

09:32.264 --> 09:34.487
contribute to learning . I was in a , a

09:34.487 --> 09:36.653
session last week where I heard that a

09:36.653 --> 09:38.709
strike group that just got back from

09:38.709 --> 09:40.764
the Red Sea talking with great pride

09:40.764 --> 09:42.820
about the updates it was sending out

09:42.820 --> 09:45.042
mid deployment to the strike group that

09:45.042 --> 09:47.209
was gonna relieve it . And to see that

09:47.209 --> 09:48.931
that's sort of a dedication to

09:48.931 --> 09:51.042
continuous learning that wasn't there

09:51.042 --> 09:53.376
when I , when I was around the other is ,

09:53.376 --> 09:55.431
it's a lot quieter on the ship . And

09:55.431 --> 09:57.320
that the way we communicated both

09:57.320 --> 09:59.487
internally and externally is primarily

09:59.487 --> 10:01.542
through voice , voice radio . And if

10:01.542 --> 10:03.709
you walk into a ship now you can , you

10:03.709 --> 10:05.820
can hear the keyboard tapping away as

10:05.820 --> 10:07.876
people do a lot more with chat . And

10:07.876 --> 10:09.987
that has changed the culture in a lot

10:09.987 --> 10:12.209
of different ways . In some regards , I

10:12.209 --> 10:14.431
think it has helped the decision making

10:14.431 --> 10:16.487
process because it is quieter . It's

10:16.487 --> 10:18.209
also allowed a little bit more

10:18.209 --> 10:20.376
persistence in some of the information

10:20.376 --> 10:22.376
being exchanged . And I I find that

10:22.376 --> 10:24.542
pretty exciting deployment length . It

10:24.542 --> 10:26.764
used to be very unusual for us to spend

10:26.764 --> 10:28.931
more than six months on deployment . I

10:28.931 --> 10:30.987
did a seven month and it was seen as

10:30.987 --> 10:32.931
extraordinary nowadays , it is not

10:32.931 --> 10:34.820
unusual for ships to come back to

10:34.820 --> 10:36.931
having spent 9 , 1011 months at sea .

10:36.931 --> 10:39.042
And that has changed a lot within the

10:39.042 --> 10:41.289
crew . A the crew members grow a lot

10:41.299 --> 10:43.840
closer . And in fact , uh I think

10:43.849 --> 10:46.140
sometimes our biggest challenges with

10:46.150 --> 10:48.372
stress and with mental health come when

10:48.372 --> 10:50.679
the crew maybe gets off that deployment

10:50.690 --> 10:52.801
and starts to depressurize and spread

10:52.801 --> 10:54.746
out a little bit . But the biggest

10:54.746 --> 10:56.912
thing and I think it ties to that last

10:56.912 --> 10:59.079
point is connectedness . You know , if

10:59.079 --> 11:01.134
I consider , um , how we used to get

11:01.134 --> 11:03.929
word from home when I was at sea . Um ,

11:03.969 --> 11:06.270
you're lucky if you got mail , you're

11:06.280 --> 11:08.502
lucky . If it was only six weeks late ,

11:08.599 --> 11:10.809
I can remember . Um , you know ,

11:10.820 --> 11:13.609
learning about happy and sad family

11:13.619 --> 11:15.940
developments many months after they've

11:15.950 --> 11:17.894
already happened where now there's

11:17.894 --> 11:20.006
instantaneous communications and that

11:20.006 --> 11:22.172
could be both the morale booster and I

11:22.172 --> 11:24.283
encourage you if you happen to take a

11:24.283 --> 11:26.506
look at , at some of what got published

11:26.506 --> 11:28.506
just yesterday , they get off a Kry

11:28.506 --> 11:30.728
strike group too , but also a source of

11:30.728 --> 11:32.950
stress because now the things that used

11:32.950 --> 11:35.006
to be a little bit removed are right

11:35.006 --> 11:34.789
there in your face . There's nothing

11:34.799 --> 11:37.299
like suddenly getting uh uh a text or

11:37.309 --> 11:39.531
an email that says , hey , we're taking

11:39.531 --> 11:41.753
your kid to the emergency room and then

11:41.753 --> 11:44.087
you're wondering for the next two hours .

11:44.087 --> 11:46.198
Well , what happened where before you

11:46.198 --> 11:45.880
would probably get the story many ,

11:45.890 --> 11:47.950
many weeks later in the mail on

11:47.960 --> 11:50.182
something dropped off a helicopter . So

11:50.182 --> 11:52.293
those things have changed to me . The

11:52.293 --> 11:54.182
biggest takeaway is that not just

11:54.182 --> 11:56.293
connectivity , but that connectedness

11:56.293 --> 11:58.516
that just wasn't necessarily there when

11:58.516 --> 12:00.682
I was growing up in the Navy . David .

12:00.682 --> 12:03.520
Um I , I'll give you the dia example ,

12:03.530 --> 12:06.289
you know , Dia nominated his chief data

12:06.299 --> 12:08.410
officer this year earlier this year .

12:08.410 --> 12:10.521
You know , the CD O function or title

12:10.521 --> 12:12.521
didn't even exist a few years ago .

12:12.690 --> 12:15.000
Right when you came into your position

12:15.010 --> 12:17.177
in the army as the army , intel cd O ,

12:17.270 --> 12:19.103
what are some of the things that

12:19.103 --> 12:19.070
surprised you like ? What are the

12:19.080 --> 12:21.302
challenges that you thought you did not

12:21.302 --> 12:23.247
have to face that you are you were

12:23.247 --> 12:25.191
facing ? Yeah , that's right . The

12:25.191 --> 12:27.413
position didn't even exist . Um And you

12:27.413 --> 12:29.580
know , folks kind of recognize that we

12:29.580 --> 12:31.580
were moving to data Centricity . We

12:31.580 --> 12:33.802
wanted to get there somehow , we needed

12:33.802 --> 12:35.580
to figure out how to uh empower

12:35.580 --> 12:37.691
somebody to kind of uh right the ship

12:37.691 --> 12:39.691
uh and figure out how we were gonna

12:39.691 --> 12:41.913
transform a culture . And uh you know ,

12:41.913 --> 12:44.080
nobody was really taking a look at how

12:44.080 --> 12:46.191
uh our organization was plugging into

12:46.191 --> 12:48.030
the icy ecosystem and , and

12:48.039 --> 12:50.659
coordinating that across we're all one

12:50.669 --> 12:53.150
team . And I like to think of this as

12:53.159 --> 12:57.099
like uh having a , a whole set of

12:57.109 --> 12:59.590
capabilities available to you where you

12:59.599 --> 13:01.890
are also a part of that . And so often

13:01.900 --> 13:04.580
times um folks like to get insular and

13:04.590 --> 13:06.701
they look to look , they like to look

13:06.701 --> 13:09.539
inward at what they're delivering . Uh

13:09.549 --> 13:11.660
And I think it's helpful when we're ,

13:11.660 --> 13:14.280
you know , looking at data uh to also

13:14.289 --> 13:16.469
look outward and understand who are

13:16.479 --> 13:19.299
stakeholders and our customers are . Um

13:19.320 --> 13:21.376
And , and to be able to uh integrate

13:21.376 --> 13:24.419
across that ecosystem uh with a new CD

13:24.429 --> 13:27.770
O role , uh I ran into some significant

13:27.780 --> 13:30.070
challenges , you know , the first was ,

13:30.190 --> 13:32.849
what do you do , right ? What is the

13:32.859 --> 13:35.026
what is the actual thing that you need

13:35.026 --> 13:37.510
to do ? And often times a lot of those

13:37.520 --> 13:40.130
uh individual tasks are things that

13:40.140 --> 13:42.150
people are already doing other

13:42.159 --> 13:44.799
functional , you know , sections within

13:44.809 --> 13:47.031
our directorate already . We're already

13:47.031 --> 13:49.087
doing those things . So I think it's

13:49.087 --> 13:51.309
important for leaders to really kind of

13:51.309 --> 13:53.309
um carve out their space within the

13:53.309 --> 13:55.476
environment that they , they operate .

13:55.476 --> 13:57.420
Uh And really you need to get some

13:57.420 --> 13:59.531
credibility first . You know , people

13:59.531 --> 13:58.780
like to go out of the gate with a

13:58.789 --> 14:00.678
vision , right ? And start with a

14:00.678 --> 14:02.845
vision . But I think there was a quote

14:02.845 --> 14:05.320
John C Maxwell said , uh uh people

14:05.330 --> 14:07.580
don't buy in , people buy into the

14:07.590 --> 14:10.599
leader before they buy into the vision .

14:11.070 --> 14:13.292
So I think it's important that you need

14:13.292 --> 14:16.219
to establish trust first . Um There's a

14:16.229 --> 14:20.109
uh John Blakey who's a um a well known

14:20.119 --> 14:22.063
author . I think it was the ceo of

14:22.063 --> 14:24.950
Unilever said , uh ability , integrity

14:24.960 --> 14:27.219
and benevolence is the way to trust

14:27.229 --> 14:31.080
there . So ability can I do what I say ?

14:31.090 --> 14:34.679
I can do integrity . Will I actually

14:34.690 --> 14:37.739
do what I said ? And then benevolence

14:37.750 --> 14:39.900
is um you know , can I find common

14:39.909 --> 14:42.239
ground with folks and advocate for

14:42.250 --> 14:44.472
their share , for shared interests that

14:44.472 --> 14:46.361
we , that we have ? Uh So I think

14:46.361 --> 14:48.694
that's important first is to , you know ,

14:48.694 --> 14:50.806
get a lay of the land , understand uh

14:50.806 --> 14:52.861
what trust relationships you need to

14:52.861 --> 14:55.028
build and then that helps with getting

14:55.028 --> 14:57.669
the buy in and be beginning to know who

14:58.489 --> 15:00.600
that folks can trust , they can trust

15:00.600 --> 15:02.711
the CD O with some of these tasks and

15:02.711 --> 15:04.767
they can start to understand kind of

15:04.767 --> 15:06.822
what that , what that greater vision

15:06.822 --> 15:09.109
looks like . Um You're trying to create

15:09.119 --> 15:12.859
gravity around a new thing , right ? Um

15:12.869 --> 15:15.036
And so , you know , if you think about

15:15.036 --> 15:17.147
Centricity , you need gravity to kind

15:17.147 --> 15:19.258
of go around that , that data centric

15:19.258 --> 15:21.480
culture . So you have to start thinking

15:21.480 --> 15:23.702
about the initiatives that you're gonna

15:23.702 --> 15:25.702
build out and , and really start to

15:25.702 --> 15:27.909
articulate that vision and and how

15:27.919 --> 15:30.609
those things are going to work . Uh

15:30.619 --> 15:33.059
Right now , we're stuck kind of in this

15:33.070 --> 15:36.679
uh um uh transition period where we're

15:36.690 --> 15:38.940
going from a , a tool centric or

15:38.950 --> 15:42.780
application centric mindset . And we're

15:42.789 --> 15:45.679
moving to more of a um a data centric

15:45.690 --> 15:48.500
mindset where , you know , as I was

15:48.510 --> 15:51.330
saying before , folks looking inward on

15:51.340 --> 15:55.320
the platform , me and my platform , my

15:55.330 --> 15:59.190
users , my data to looking outward our

15:59.200 --> 16:03.150
data , our capabilities . How how is

16:03.159 --> 16:05.381
our data gonna be interoperable to move

16:05.381 --> 16:07.659
from , from this system to this system ?

16:07.659 --> 16:09.603
And how am I thinking about that ?

16:10.150 --> 16:12.369
Right . Uh And I think it starts with

16:12.380 --> 16:15.000
people , right ? And understanding um

16:16.090 --> 16:18.969
how that mindset needs to shift so that

16:18.979 --> 16:22.369
we're thinking more about um where our

16:22.380 --> 16:24.602
data is going to go and what it's going

16:24.602 --> 16:28.099
to be used for . OK , Mike , um

16:28.780 --> 16:30.780
you know , as you are the Air Force

16:30.780 --> 16:32.947
Intel Cio , what are some of the skill

16:32.947 --> 16:35.058
sets you have learned on the job that

16:35.058 --> 16:37.058
you wished you knew ahead of time ,

16:37.058 --> 16:39.419
right . Coming into the job . I mean ,

16:39.429 --> 16:41.640
so I think staying in touch with the

16:41.650 --> 16:43.872
culture , like , what a , what a Skibby

16:43.909 --> 16:46.076
question you have , I'm gonna eat that

16:46.076 --> 16:48.242
right now . Like , how do you , how do

16:48.242 --> 16:50.242
you relate to the , the , the , the

16:50.242 --> 16:52.353
workforce as it continues to change ?

16:52.353 --> 16:54.349
And so uh communicating with that

16:54.359 --> 16:57.205
workforce and relating and doing it in

16:57.216 --> 16:59.383
a manner in a medium that they're used

16:59.383 --> 17:01.105
to . And we also have a lot of

17:01.105 --> 17:02.994
questions about like , what about

17:02.994 --> 17:05.160
training ? You know , the applications

17:05.160 --> 17:07.383
are changing so fast and the , we can't

17:07.383 --> 17:09.549
keep up with the training . Well , you

17:09.549 --> 17:11.716
know , they're used to just , is there

17:11.716 --> 17:13.716
a youtube video on how to do this ?

17:13.716 --> 17:15.938
It's probably 10 providers of videos on

17:15.938 --> 17:17.952
that . They are just like , like

17:17.962 --> 17:20.184
they'll find it themselves if they have

17:20.184 --> 17:22.421
a question used to kind of more of a

17:22.432 --> 17:25.582
digital native environment . So they

17:25.592 --> 17:27.814
are used to like saying , well , let me

17:27.814 --> 17:29.925
download this app and , and figure it

17:29.925 --> 17:31.991
out and use it . Um But , you know ,

17:32.001 --> 17:34.112
presenting what's new on the app in a

17:34.112 --> 17:36.390
banner and like , that's your tutorial ,

17:36.390 --> 17:38.750
let me walk you through it . This is um

17:38.880 --> 17:41.449
not a traditional way . We're used to

17:41.459 --> 17:43.859
having like classes taught and ways of

17:43.869 --> 17:46.219
doing business . Um but being able to

17:46.229 --> 17:49.760
continue to relate and um and be

17:49.770 --> 17:53.150
flexible in how you approach uh the

17:53.160 --> 17:55.589
environment the problem and the culture

17:55.599 --> 17:58.160
as it is um in our , in our workforce

17:58.170 --> 18:00.392
has multiple generations in it . So you

18:00.392 --> 18:02.559
have to be kind of flexible in how you

18:02.559 --> 18:04.781
deal with what , who's comfortable with

18:04.781 --> 18:06.948
what and I can relate , you know , try

18:06.948 --> 18:09.170
to relate to my kids and see like , how

18:09.170 --> 18:11.226
are you doing this ? And um just the

18:11.226 --> 18:13.337
idea of that they're more comfortable

18:13.337 --> 18:15.559
doing things through a digital medium ,

18:15.559 --> 18:17.670
not interpersonal And that's probably

18:17.670 --> 18:19.979
not everybody but a lot of the , this

18:20.239 --> 18:22.619
um generation post COVID is used to

18:22.630 --> 18:26.020
remote uh and interacting with their

18:26.030 --> 18:28.869
friends via Discord . And you know ,

18:28.880 --> 18:31.047
even a card game will have a camera on

18:31.047 --> 18:33.047
the table and they're playing cards

18:33.047 --> 18:34.991
together from the different houses

18:34.991 --> 18:36.991
instead of like sitting at the same

18:36.991 --> 18:39.213
table and they're very comfortable with

18:39.213 --> 18:40.991
that . Um So , um just being um

18:41.000 --> 18:43.109
understanding like from a leadership

18:43.119 --> 18:46.430
perspective , how to work with

18:46.439 --> 18:49.170
multiple generations of technology and

18:49.180 --> 18:51.890
adoption . And , you know , I'm not in

18:51.900 --> 18:54.750
the , the new one either . And so uh

18:54.760 --> 18:57.150
how do I figure that out ? And there

18:57.160 --> 18:59.216
are things that I'm less comfortable

18:59.216 --> 19:01.327
with ? You know , I know my team will

19:01.327 --> 19:03.438
say , why don't you just edit this on

19:03.438 --> 19:05.549
teams with all of us at the same time

19:05.549 --> 19:05.260
instead of downloading it and sending

19:05.270 --> 19:07.910
it to me on email , like I get it . OK ,

19:07.920 --> 19:11.280
I need to do that . But

19:11.500 --> 19:13.989
there's , there's ways you've just

19:14.000 --> 19:16.979
traditionally done things . So for me ,

19:16.989 --> 19:19.211
I think for me . Um I like three things

19:19.211 --> 19:21.433
I learned in my job . Uh But Doug and I

19:21.433 --> 19:23.760
got the position on the same day . And

19:23.770 --> 19:25.826
the deal I made with Doug is , hey ,

19:25.826 --> 19:28.048
Doug , you do all the public speaking .

19:28.048 --> 19:28.000
I'll do all the things behind the ,

19:28.010 --> 19:29.954
behind the scenes . So I think the

19:29.954 --> 19:32.121
first thing for me , what I learned is

19:32.121 --> 19:34.288
in the position that I'm that I'm in ,

19:34.288 --> 19:36.454
I gotta do public speaking and I gotta

19:36.454 --> 19:38.510
learn that . Um And so for those who

19:38.510 --> 19:40.621
are aspiring to be on the stage , one

19:40.621 --> 19:42.732
day , you don't wanna learn it when I

19:42.732 --> 19:41.939
learned it . And that's when you get

19:41.949 --> 19:44.060
the job , you wanna learn it prior to

19:44.060 --> 19:46.171
that . I think number two , you wanna

19:46.171 --> 19:48.282
learn how to explain complex problems

19:48.282 --> 19:50.338
in a very simple manner . I remember

19:50.338 --> 19:52.505
one day our F five was down and that's

19:52.505 --> 19:54.449
exactly what I wrote to our deputy

19:54.449 --> 19:56.616
director . Hey , ma'am , the F five is

19:56.616 --> 19:58.782
down and she wrote back . Ep I , I'm ,

19:58.782 --> 20:00.893
I'm glad you think I'm an it person ,

20:00.893 --> 19:59.959
but I have no idea what this means ,

19:59.969 --> 20:02.369
right ? So I had to learn how to , how

20:02.380 --> 20:05.770
to speak um mission outcomes when

20:05.780 --> 20:07.891
system problems happen . And the last

20:07.891 --> 20:10.058
thing I've learned , you know , I used

20:10.058 --> 20:09.800
to be in my previous job , I used to be

20:09.810 --> 20:11.921
very detail oriented , going down and

20:11.921 --> 20:13.977
understanding down to the subsystems

20:13.977 --> 20:16.088
and components and the interactions .

20:16.088 --> 20:18.199
And at , at this level , I really had

20:18.199 --> 20:20.421
to keep it superficial . I need to know

20:20.421 --> 20:22.532
high level impacts and the ability to

20:22.532 --> 20:22.500
communicate and the impacts that it has

20:22.510 --> 20:24.621
to our our stakeholders . All right ,

20:24.621 --> 20:26.510
let's go to the next question and

20:26.510 --> 20:28.399
anyone can take this . There is a

20:28.399 --> 20:30.399
generational divide , right ? We're

20:30.399 --> 20:32.399
hiring the new officers of tomorrow

20:32.399 --> 20:34.579
that are digitally native . They come

20:34.589 --> 20:36.811
in , some of them are highly frustrated

20:37.069 --> 20:39.849
because Mike , as you alluded to , we

20:39.859 --> 20:41.915
do not know how to task them . We do

20:41.915 --> 20:43.748
not know how to talk to them and

20:43.748 --> 20:45.859
they're working on technology that is

20:45.859 --> 20:47.859
from , you know , 1995 . How do you

20:47.859 --> 20:51.339
deal with that challenge ? I , I think

20:51.349 --> 20:53.460
it's interesting that we used to take

20:53.460 --> 20:55.571
smoke or we need we , but people used

20:55.571 --> 20:57.627
to take smoke breaks and now they're

20:57.627 --> 20:59.849
taking social media breaks , like leave

20:59.849 --> 21:01.905
your phone at the door is so foreign

21:01.905 --> 21:04.016
and I'm disconnected and I'm jonesing

21:04.016 --> 21:07.489
for that data . And so I've got to know

21:07.500 --> 21:09.722
what's going on at any given time . And

21:09.722 --> 21:12.199
so we are in a tough situation because

21:12.209 --> 21:14.431
we're living in a skiff and it's harder

21:14.431 --> 21:16.431
to have that . But so you're seeing

21:16.431 --> 21:19.020
this like I gotta have my , my fix and ,

21:19.030 --> 21:22.609
and do that . Um And so

21:22.839 --> 21:25.209
catering to that vice , fighting with

21:25.219 --> 21:27.108
it is going to help you with this

21:27.108 --> 21:29.489
challenge of , of workforce retention

21:29.500 --> 21:31.770
and attraction for these kinds of jobs

21:31.780 --> 21:34.040
as well because this is where the

21:34.050 --> 21:37.300
culture has shifted to . Um And so

21:37.469 --> 21:39.699
yesterday's technology , tomorrow is

21:39.709 --> 21:41.765
true . Sometimes we're trying to get

21:41.765 --> 21:43.931
better and we are , we are doing a lot

21:43.931 --> 21:46.098
of things to do that . But in a lot of

21:46.098 --> 21:47.987
ways when you work in a skiff and

21:47.987 --> 21:50.209
you're not wireless and you're not able

21:50.209 --> 21:53.420
to use the latest presentation software

21:53.430 --> 21:55.880
to build your slides and all these

21:55.890 --> 21:57.946
capabilities , they're used to using

21:57.946 --> 22:00.057
for school work , you know , and then

22:00.057 --> 22:02.279
they come into the job and they can't ,

22:02.279 --> 22:04.446
it's back to , you know , powerpoint .

22:04.446 --> 22:08.250
Um And so it's tough . Um

22:08.260 --> 22:10.829
but I think we are getting better and

22:10.839 --> 22:14.099
uh we are addressing it . Um but it is

22:14.109 --> 22:16.489
not as fast as I think many would like .

22:17.280 --> 22:20.780
OK . Um Dave , I'll come to you , let's

22:20.790 --> 22:22.679
say , you know , if you go to the

22:22.679 --> 22:24.901
private sector , if you listen to the ,

22:24.901 --> 22:26.957
if you listen to the internet A I is

22:26.957 --> 22:29.012
all the rage . Although I noticed in

22:29.012 --> 22:31.179
the cio panel yesterday , not a single

22:31.179 --> 22:33.290
person mentioned the A I , right ? Um

22:33.550 --> 22:37.199
We deal on , I deal with uh a

22:37.209 --> 22:39.376
lot of people that say they come to me

22:39.376 --> 22:41.042
and say , hey , I need an A I

22:41.042 --> 22:43.209
capability and if I ask , what problem

22:43.209 --> 22:45.431
are you trying to solve ? They struggle

22:45.431 --> 22:45.310
to answer that . What data you need to

22:45.319 --> 22:47.589
train , they struggle to answer that .

22:47.599 --> 22:49.710
Where , where will you get the data ?

22:49.710 --> 22:51.810
They can answer that . Um How do you

22:51.819 --> 22:55.030
see the relevance of A IA I

22:55.040 --> 22:57.680
governance , its intersection with data

22:57.689 --> 22:59.829
governance and it's , you know , it's

22:59.839 --> 23:02.270
dependence on infrastructure governance

23:02.280 --> 23:04.502
all tying together . And how do you see

23:04.502 --> 23:06.558
your role in this community to solve

23:06.558 --> 23:08.869
this problem ? Awesome question . Um

23:08.880 --> 23:11.102
The urgency is now , obviously , you've

23:11.102 --> 23:13.349
heard um just about every panel ,

23:13.359 --> 23:15.689
almost every panel . Um and all the

23:15.699 --> 23:18.699
breakout sessions talk about A I

23:19.550 --> 23:21.883
people like to say that it's a buzzword .

23:21.883 --> 23:24.020
Uh But I would say that it's a , you

23:24.030 --> 23:27.459
know , cultural shift . Now again ,

23:27.839 --> 23:30.061
uh here we were going to a data centric

23:30.061 --> 23:32.061
culture and now we're talking about

23:32.061 --> 23:34.117
integrating A I capabilities . And I

23:34.117 --> 23:36.859
would say , um you know , to be able to ,

23:36.869 --> 23:38.925
to be able to do that , we need good

23:38.925 --> 23:41.290
quality data to be able to support that .

23:41.300 --> 23:43.467
We need a good foundation of data that

23:43.467 --> 23:45.522
enables us to accelerate that . So ,

23:46.050 --> 23:48.161
you know , uh just a couple of things

23:48.161 --> 23:50.609
to note , you know , um you know , the

23:50.619 --> 23:52.563
Federal Government Congress asking

23:52.563 --> 23:55.699
questions , why aren't we moving faster ?

23:56.609 --> 23:58.609
Right ? Um You know , then you have

23:58.609 --> 24:00.720
solution providers saying we're ready

24:01.510 --> 24:03.677
and then the government's there like ,

24:03.677 --> 24:07.260
OK , uh what do we do ? Um

24:07.439 --> 24:10.079
Well , where's the data ? Right ? Um

24:10.089 --> 24:12.270
And that's the question because good

24:12.280 --> 24:14.502
quality data accelerates A I adoption .

24:14.502 --> 24:17.369
So and improving that data quality

24:17.380 --> 24:19.380
starts , I think less with the

24:19.390 --> 24:21.619
technology than it does with people ,

24:22.489 --> 24:24.545
right ? Uh And that's , that's where

24:24.545 --> 24:26.750
this data culture stuff comes in is

24:26.760 --> 24:29.869
understanding how people are thinking

24:29.880 --> 24:32.609
about this issue because what I said

24:32.619 --> 24:34.786
before , we were looking inward at the

24:34.786 --> 24:36.952
platform and we weren't thinking about

24:36.952 --> 24:40.280
how we were sharing the data across and

24:40.290 --> 24:42.560
tailoring it to our stakeholder needs .

24:42.930 --> 24:45.041
You know , we're sitting there in the

24:45.041 --> 24:47.208
platform and going , how do we deliver

24:47.208 --> 24:49.339
through the platform ? But if we get

24:49.349 --> 24:52.810
this right , then we understand that we

24:52.819 --> 24:54.819
need to architect for flexibility .

24:54.819 --> 24:56.930
There's gonna be new things that come

24:56.930 --> 24:58.486
on board , new kinds of A I

24:58.486 --> 25:00.652
capabilities that come online . How do

25:00.652 --> 25:03.770
we support that uh and get left of that

25:03.780 --> 25:06.050
data issue ? Right . Uh I I like to

25:06.060 --> 25:08.770
think about this thing as uh um

25:09.060 --> 25:12.520
starting with the problem statement to

25:12.530 --> 25:14.530
include looking through the lens of

25:14.530 --> 25:17.540
data and thinking about what do we need

25:17.550 --> 25:20.550
that data to look like in order for the

25:20.560 --> 25:24.479
user to get distract value from it . Um

25:24.750 --> 25:27.640
And A A I is the same as potentially

25:27.650 --> 25:30.689
any other system data in munch munch

25:30.699 --> 25:34.290
munch data out . So what are we doing

25:34.300 --> 25:36.770
in the munch munch munch period to get

25:36.780 --> 25:38.891
that data into a place where somebody

25:38.891 --> 25:41.224
can make a decision off of that ? Right ?

25:41.224 --> 25:43.447
And if we can think about how that data

25:43.447 --> 25:44.836
needs to be packaged for

25:44.836 --> 25:46.891
interoperability and movement across

25:46.891 --> 25:48.891
the IC to be able to support us . I

25:48.891 --> 25:50.949
think that's where we get uh uh

25:50.959 --> 25:54.380
accelerated A I adoption from is we're

25:54.390 --> 25:56.501
able to use this data , we're able to

25:56.501 --> 25:58.959
contextualize that information now to

25:58.969 --> 26:01.136
get the value that we're looking for .

26:01.136 --> 26:03.358
Um So I'd say it starts there , there's

26:03.358 --> 26:05.479
another issue here , um clear problem

26:05.489 --> 26:08.780
statements about what , what problems

26:08.790 --> 26:10.846
we're trying to solve and then tying

26:10.846 --> 26:13.339
those problem statements to success

26:13.449 --> 26:16.819
metrics . What are we measuring ? And

26:16.829 --> 26:18.940
what's the value that we're expecting

26:18.940 --> 26:22.390
to see from any of the A I capabilities

26:22.400 --> 26:25.119
that we're thinking about adopting ? Uh

26:25.130 --> 26:27.449
and I challenge folks , you know , if

26:27.459 --> 26:30.880
uh people wanna uh start with uh um

26:30.930 --> 26:33.670
technology conversation , always back

26:33.680 --> 26:36.160
up and ask the questions about what is

26:36.170 --> 26:38.510
the problem statement ? What are we

26:38.520 --> 26:40.631
trying to address here and apply some

26:40.631 --> 26:43.430
rails ? OK . Within this , within these

26:43.439 --> 26:46.599
rails , how do we apply A I to get

26:46.609 --> 26:48.720
after the problem that's trying to be

26:48.720 --> 26:50.665
solved ? And I think that's really

26:50.665 --> 26:53.109
important . Um moving forward there .

26:53.119 --> 26:55.119
Uh There's the paradigm here though

26:55.609 --> 26:58.930
with A I , you have , um there's the

26:58.939 --> 27:01.900
problem that the A I can solve and then

27:01.910 --> 27:04.290
there's the problem that we want solved

27:05.310 --> 27:07.254
and often times those things don't

27:07.254 --> 27:09.489
match up quite right ? Because the A I

27:09.500 --> 27:12.439
can solve a lot more problems than the

27:12.449 --> 27:14.560
problem that's being solved , right ?

27:14.560 --> 27:16.739
So , uh we also have to think about

27:16.750 --> 27:19.329
that from two different directions ,

27:19.339 --> 27:22.160
you know , um sometimes we can maximize

27:22.170 --> 27:24.392
the value that we're getting from these

27:24.392 --> 27:26.930
models or these capabilities . Uh And

27:26.939 --> 27:29.272
we need to look for those opportunities ,

27:29.272 --> 27:31.383
but we need to make sure that we , we

27:31.383 --> 27:33.383
have , we have some controls around

27:33.383 --> 27:33.130
that . So we can , we can understand ,

27:33.420 --> 27:35.531
you know , scope schedule cost risk ,

27:35.531 --> 27:37.599
all those different things . Uh And

27:37.609 --> 27:40.500
that's important . Uh One last thing I

27:40.510 --> 27:42.788
don't wanna take up too much time here ,

27:42.788 --> 27:44.677
but data products . So here we're

27:44.677 --> 27:46.899
talking about data interoperability and

27:46.899 --> 27:49.121
all these different things . But if you

27:49.121 --> 27:51.343
think about data as a product and , and

27:51.343 --> 27:53.343
you know , Laurie Wade talked about

27:53.343 --> 27:56.380
this yesterday . Uh but what is a

27:56.390 --> 28:00.050
product , you know , a product is uh

28:00.510 --> 28:02.750
a thing that is the result of an action

28:02.760 --> 28:05.310
or process . And if we're thinking

28:05.319 --> 28:08.869
about this being the product , uh we

28:08.880 --> 28:11.390
need to uh we , we need to get an

28:11.400 --> 28:13.456
understanding that this is the thing

28:13.456 --> 28:15.939
that is the closest to the stakeholder

28:15.949 --> 28:18.116
that we're engaging with and using all

28:18.116 --> 28:20.689
these information systems for , we're

28:20.699 --> 28:23.770
setting up all the networks for . So if

28:23.780 --> 28:27.010
that's true , right ? This is the

28:27.020 --> 28:30.030
strategic asset , right ? And so if

28:30.040 --> 28:32.199
we're focusing on the data pro as a

28:32.209 --> 28:35.020
product , that should be the most

28:35.030 --> 28:38.550
important package or delivery that

28:38.560 --> 28:41.630
we're giving to a user . And if that's

28:41.640 --> 28:44.160
true , then , then we need to really

28:44.170 --> 28:46.439
talk to the people that are using it ,

28:46.680 --> 28:48.640
get the feedback and improve that

28:48.650 --> 28:50.750
product so that we can generate the

28:50.760 --> 28:52.871
value from it . And I , I think , you

28:52.871 --> 28:55.093
know , if people can focus in on that ,

28:56.439 --> 28:59.709
that , that , that product delivery and

28:59.719 --> 29:01.775
the feedback loop that's required to

29:01.775 --> 29:03.939
deliver that product , you know , the

29:03.949 --> 29:06.060
uh you know , the industry would tell

29:06.060 --> 29:08.171
you , you know , product market fit .

29:09.099 --> 29:11.321
And if you think about that from a data

29:11.321 --> 29:14.719
lens , that's where we need to deliver .

29:15.750 --> 29:18.890
Ok . Uh Ultimately , most of us here

29:18.900 --> 29:20.619
support targeting directly or

29:20.630 --> 29:22.852
indirectly . Right . Chris , I know you

29:22.852 --> 29:25.074
do yesterday when Laurie was speaking ,

29:25.074 --> 29:27.297
I felt like I was on Oprah and I was so

29:27.297 --> 29:26.849
disappointed there was nothing

29:26.859 --> 29:29.026
underneath my chair . I really thought

29:29.026 --> 29:31.192
I would , you know , you would get a A

29:31.192 --> 29:33.470
I model , I would get an A I model and ,

29:33.470 --> 29:33.229
you know , and , and ultimately , there

29:33.239 --> 29:35.461
was nothing there . Uh Chris , where do

29:35.461 --> 29:37.683
you think A I would make sense for us ?

29:38.270 --> 29:40.326
Right ? Where , because , you know ,

29:40.326 --> 29:42.492
ultimately some of these models are no

29:42.492 --> 29:42.170
better than the coin flip , but thank

29:42.180 --> 29:44.180
you very much and I'll uh build off

29:44.180 --> 29:46.402
what Dave talked about and that we need

29:46.402 --> 29:48.347
to think about all of the problems

29:48.347 --> 29:50.680
within that broad category of targeting .

29:50.750 --> 29:52.639
And so if you'll indulge me for a

29:52.639 --> 29:54.750
second , you think about where we are

29:54.750 --> 29:56.917
as a department right now , you know ,

29:56.917 --> 29:56.819
we've made some pretty significant

29:56.829 --> 29:59.162
investments over the past several years ,

29:59.162 --> 30:01.107
we got some more investments going

30:01.107 --> 30:03.162
forward that'll suddenly allow us to

30:03.162 --> 30:05.273
have many , many more sensor equipped

30:05.273 --> 30:07.983
platforms in all war fighting domains .

30:08.162 --> 30:10.384
And so one of the challenges we face as

30:10.384 --> 30:12.302
a community is to take the data

30:12.312 --> 30:14.312
streaming off all those platforms ,

30:14.312 --> 30:16.822
whether they're space , Air surface

30:16.833 --> 30:19.345
subs service shore cyber and to do

30:19.355 --> 30:21.299
something with it to contribute to

30:21.299 --> 30:23.633
targeting . So there's a volume problem .

30:23.633 --> 30:25.522
We've also got a bit of a variety

30:25.522 --> 30:27.355
problem and that we're no longer

30:27.355 --> 30:29.245
constrained to single discipline

30:29.255 --> 30:31.199
collection . We've got the ability

30:31.199 --> 30:33.255
through some of these sensor quipped

30:33.255 --> 30:35.735
platforms to deal with Gent and Sigint

30:35.745 --> 30:37.801
and Akin and all the other instances

30:37.801 --> 30:39.806
you could possibly imagine . And so

30:39.816 --> 30:42.066
there really is indeed a variety

30:42.076 --> 30:44.500
problem . There's a velocity issue and

30:44.510 --> 30:46.677
that the expectation of our commanders

30:46.680 --> 30:48.859
is that we're gonna be able to go from

30:48.869 --> 30:51.150
collection to actually having

30:51.160 --> 30:53.729
actionable intelligence in relatively

30:53.739 --> 30:55.709
short order . And so how do we now

30:55.719 --> 30:58.069
speed things along ? I'll call it a

30:58.079 --> 31:00.390
veracity issue which gets to precision .

31:00.489 --> 31:02.433
As Alma Wentworth talked about the

31:02.433 --> 31:04.211
other day , there's certainly a

31:04.211 --> 31:06.156
locational aspect . It , there's a

31:06.156 --> 31:08.100
movement aspect to it . There's an

31:08.100 --> 31:10.267
identity aspect to it . So obviously ,

31:10.267 --> 31:12.579
if we can pinpoint with a great deal of

31:12.589 --> 31:15.500
precision where a given adversary is

31:15.510 --> 31:18.300
where it's going and who it is , we can

31:18.310 --> 31:21.050
really do a lot to bring value to the

31:21.060 --> 31:23.060
targeting chain . And so we need to

31:23.060 --> 31:25.869
think about is where does A I best fit ,

31:25.880 --> 31:28.449
where are some of the problems , the

31:28.459 --> 31:30.681
more we can actually move the needle we

31:30.681 --> 31:32.681
can actually solve in such a manner

31:32.681 --> 31:34.903
that it's gonna make a difference . And

31:34.903 --> 31:36.848
right now , there's still a lot of

31:36.848 --> 31:36.780
uncertainty about that . We've had some

31:36.790 --> 31:39.229
nascent efforts to bring A I to bear

31:39.239 --> 31:41.750
along each of those different vs uh in

31:41.760 --> 31:45.000
some cases , some progress , I'm a

31:45.010 --> 31:47.177
little bit more concerned about really

31:47.177 --> 31:49.288
looking at F scores , really thinking

31:49.288 --> 31:51.599
about things like true positives and

31:51.609 --> 31:53.839
false positives because I need to think

31:53.849 --> 31:56.016
about , hey , what level of confidence

31:56.016 --> 31:58.238
to , I need to ascribe to the outputs .

31:58.238 --> 32:00.238
And I also need to think about as a

32:00.238 --> 32:02.182
programmer , what is the right and

32:02.182 --> 32:04.349
proper balance between the analyst and

32:04.349 --> 32:06.349
the analytic . And there's a lot of

32:06.349 --> 32:08.571
very hyperbolic dialogue right now that

32:08.571 --> 32:10.238
we need to get quantified and

32:10.238 --> 32:12.293
channelize . So we can actually make

32:12.293 --> 32:12.209
some good decisions about where and

32:12.219 --> 32:14.589
when and for what purpose to apply A I ?

32:14.880 --> 32:17.102
OK , Mike , do you have any comments on

32:17.102 --> 32:19.213
this ? Uh Yeah , I mean A I is a huge

32:19.213 --> 32:21.213
topic and I feel like it's almost a

32:21.213 --> 32:23.436
wildfire but we're trying to control it

32:23.436 --> 32:26.949
um in a responsible and secure way . We ,

32:27.310 --> 32:29.589
we have uh a group of people that we're

32:29.599 --> 32:31.989
uh investing in that is really hard to

32:32.000 --> 32:35.069
find like the talent for A I and we're

32:35.079 --> 32:37.390
focusing the people that want to get a

32:37.400 --> 32:39.344
little A I sprinkled into whatever

32:39.344 --> 32:41.739
they're doing to go to this entity that

32:41.750 --> 32:43.829
we can then ensure that whatever use

32:43.839 --> 32:46.006
case they're bringing is appropriate ,

32:46.006 --> 32:48.061
is done responsibly and securely and

32:48.061 --> 32:50.560
then help them through that journey to

32:50.569 --> 32:52.625
integrating that into whatever their

32:52.625 --> 32:54.736
workflow is and the , the application

32:54.736 --> 32:56.847
that they need to provide it in . And

32:56.847 --> 32:58.791
then um understand the differences

32:58.791 --> 33:00.958
between the ML that we've been working

33:00.958 --> 33:03.125
on for many years have got really good

33:03.125 --> 33:05.069
results on , on those discrete use

33:05.069 --> 33:06.910
cases to more of a generative uh

33:06.920 --> 33:09.550
multiple use case like what's the use

33:09.560 --> 33:11.671
case for Google search ? I mean , the

33:11.671 --> 33:13.949
same idea . It's like an answer engine ,

33:13.949 --> 33:15.727
right ? So , um that's a harder

33:15.727 --> 33:17.949
question . But how do we use , use that

33:17.949 --> 33:17.935
and control it ? What are the

33:17.944 --> 33:20.505
appropriate use cases um that we're

33:20.515 --> 33:22.404
going to allow for that kind of a

33:22.404 --> 33:24.805
technology to be used on ? And many

33:24.814 --> 33:27.036
times the customer doesn't realize it's

33:27.036 --> 33:29.147
just automation they're looking for .

33:29.147 --> 33:31.147
Not , you don't need all that . A I

33:31.147 --> 33:33.258
just automate whatever you're talking

33:33.258 --> 33:35.370
about . And that's more of a , like a

33:35.370 --> 33:37.481
calculator output every single time ,

33:37.481 --> 33:39.703
the same that you can trust . Um And so

33:39.703 --> 33:41.814
understanding what exactly is they're

33:41.814 --> 33:43.981
trying to get at apply the appropriate

33:43.981 --> 33:45.703
technology and then do it in a

33:45.703 --> 33:47.647
responsible way from a centralized

33:48.000 --> 33:49.722
group of people . We can focus

33:49.722 --> 33:51.680
resources on to give them that

33:51.689 --> 33:53.650
capability to have those inference

33:53.660 --> 33:56.150
engines and GP US and tools like

33:56.160 --> 33:59.280
pytorch to generate the , the thing

33:59.290 --> 34:01.739
that they're looking for . And then

34:01.750 --> 34:03.750
let's not do it over and over again

34:03.750 --> 34:05.972
because we didn't know someone else did

34:05.972 --> 34:08.028
it . Let's have a marketplace and in

34:08.028 --> 34:10.139
our marketplace then allows us to see

34:10.139 --> 34:12.361
what have we already bought and what we

34:12.361 --> 34:14.583
have . Some people already built that I

34:14.583 --> 34:16.583
don't have to do again , that I can

34:16.583 --> 34:18.583
just find and reutilize . So having

34:18.583 --> 34:20.889
that um is key , I think at the same

34:20.899 --> 34:23.121
time while we're trying to focus all of

34:23.121 --> 34:25.232
that , I think you'll be hard pressed

34:25.232 --> 34:27.455
to find an application vendor out there

34:27.455 --> 34:29.566
that doesn't say it's coming with A I

34:29.566 --> 34:31.677
already embedded . And so all of that

34:31.677 --> 34:33.899
work that we just did on the government

34:33.899 --> 34:36.540
side , we're just getting it in the

34:36.550 --> 34:39.399
applications we buy now and didn't have

34:39.409 --> 34:41.520
all that back end . What's this model

34:41.520 --> 34:43.687
doing ? How is it working ? What's the

34:43.687 --> 34:43.209
confidence score ? Where is it , you

34:43.219 --> 34:45.899
know , it just came in the app . OK .

34:46.000 --> 34:47.800
So from transitioning from that

34:47.810 --> 34:50.000
question specifically for you David ,

34:50.110 --> 34:51.777
if the A I is building in the

34:51.777 --> 34:53.721
application , why should I be data

34:53.721 --> 34:55.832
centric ? Why should I adopt the data

34:55.832 --> 34:58.054
reference architecture ? That's great .

34:58.054 --> 35:00.330
Um So I like to think about the

35:00.340 --> 35:03.179
stakeholder now shifting from

35:03.939 --> 35:06.360
being a human to also being a machine ,

35:07.179 --> 35:09.739
right ? So the data needs to be not

35:09.750 --> 35:11.806
just human readable but also machine

35:11.806 --> 35:14.649
readable to enable A I , right ? And if

35:14.659 --> 35:17.169
we're , if we're not thinking about how

35:17.179 --> 35:19.860
and what the um the requirements are

35:19.870 --> 35:22.120
for making machines , be able to

35:22.129 --> 35:25.090
understand the data we have uh we're

35:25.100 --> 35:27.267
we're not gonna be able to utilize the

35:27.267 --> 35:29.322
A I effectively . So um machines are

35:29.322 --> 35:31.267
dumb , right ? They don't know the

35:31.267 --> 35:33.600
context of one word versus another word ,

35:33.600 --> 35:35.711
we have to tell the machine what that

35:35.711 --> 35:38.110
means . So we have to uh to be able to

35:38.120 --> 35:40.489
understand how we can apply semantic

35:40.500 --> 35:43.050
meaning to that information , right ?

35:43.060 --> 35:45.620
To be able to enable A I to to enable

35:45.629 --> 35:48.340
us to accelerate right . So if we want

35:48.350 --> 35:51.280
the benefits of A I acceleration and

35:51.290 --> 35:54.239
being able to um to do things in a more

35:54.250 --> 35:57.739
rapid pace , um we need to be able

35:57.750 --> 36:00.709
to , to apply that , that semantic

36:00.719 --> 36:04.139
meaning . I think it's also um uh

36:04.149 --> 36:06.205
important just to highlight from the

36:06.205 --> 36:08.419
previous comment that the one team

36:09.169 --> 36:12.270
thing that I pulled on earlier . Yeah .

36:12.409 --> 36:15.489
Uh there are all these opportunities

36:15.500 --> 36:18.449
out there and different products , but

36:18.459 --> 36:20.689
there are leads in the intelligence

36:20.699 --> 36:22.699
community that are looking at these

36:22.699 --> 36:24.866
things by , by intelligence discipline

36:24.866 --> 36:26.477
and , and and other types of

36:26.477 --> 36:28.532
disciplines here . So what we do not

36:28.532 --> 36:31.489
wanna do is uh what they would say in

36:31.500 --> 36:33.750
the army is go off on our own FTX ,

36:34.139 --> 36:37.870
right ? With our own ideas without

36:37.879 --> 36:40.270
doing the cross talk and collaboration

36:40.280 --> 36:42.336
across the intelligence community to

36:42.336 --> 36:44.558
determine where is the right place that

36:44.558 --> 36:46.558
we were applying and building these

36:46.558 --> 36:49.330
things across the different IC elements .

36:49.860 --> 36:52.939
And then how are we integrating with

36:52.949 --> 36:54.838
those IC elements to , to see our

36:54.838 --> 36:56.893
requirements and improve an existing

36:56.893 --> 37:00.320
capability ? And then if there are gaps

37:00.719 --> 37:03.879
that we identify across the services ,

37:04.719 --> 37:07.080
we can look at opportunities to build

37:07.090 --> 37:09.479
things that are novel or unique to help

37:09.489 --> 37:12.750
us accelerate mission space . But I

37:12.760 --> 37:14.871
would say that I what , what we don't

37:14.871 --> 37:17.350
want to do is build things in silos

37:17.540 --> 37:19.762
because we think it's cool and we wanna

37:19.762 --> 37:21.873
get there faster than the next person

37:21.873 --> 37:23.762
we really need to , to , to cross

37:23.762 --> 37:26.290
collaborate and improve that um improve

37:26.300 --> 37:28.578
that cross stalk moving forward . Lisa ,

37:28.578 --> 37:30.969
let me come to you . Uh Gao did a study

37:30.979 --> 37:34.270
and said 90% of government it projects

37:34.280 --> 37:37.020
fail . So we are in that 10 , you know ,

37:37.030 --> 37:39.560
10% success rate , right ? Like the 90%

37:39.570 --> 37:42.139
fail . Uh 20 years ago , technologists

37:42.149 --> 37:45.669
did all the it today because everyone

37:45.679 --> 37:47.879
uses it a lot of digital natives , you

37:47.889 --> 37:50.439
know , it is done a lot of it or

37:50.449 --> 37:52.449
application it specifically is done

37:52.449 --> 37:55.949
outside of CIO . Um Usually they don't

37:55.959 --> 37:57.792
have infrastructure expertise or

37:57.792 --> 38:00.370
awareness or architectural . The CIO is

38:00.379 --> 38:02.490
not aware of the artist architectural

38:02.490 --> 38:05.040
pathway that is taken . I recall Steve

38:05.050 --> 38:07.229
Jobs said once , you know , from from

38:07.239 --> 38:09.560
an inception of an idea to actually

38:09.570 --> 38:11.737
implementation into production , there

38:11.737 --> 38:13.737
are thousands of decisions that are

38:13.737 --> 38:15.959
made , right ? And usually if it's done

38:15.959 --> 38:17.848
out outside , like the CIO is not

38:17.848 --> 38:19.959
typically aware , what are the things

38:19.959 --> 38:22.181
that you're doing and how do you handle

38:22.181 --> 38:24.181
the challenges um to make sure your

38:24.181 --> 38:26.403
success rate is greater than 10% of the

38:26.403 --> 38:28.570
projects that is done in it within you

38:28.570 --> 38:30.737
within the Marine Corps portfolio . So

38:30.737 --> 38:32.848
that , yeah , that's a , that's a big

38:32.848 --> 38:34.626
question , right ? So um I have

38:34.626 --> 38:37.260
multiple hats which may make it easier

38:37.350 --> 38:39.590
because I don't really have to worry

38:39.600 --> 38:41.211
about collaborating with the

38:41.211 --> 38:43.211
authorizing official or the program

38:43.211 --> 38:45.156
manager or the CIO because I'm all

38:45.156 --> 38:48.560
three , right ? But in in the rest of

38:48.570 --> 38:50.737
your cases , you absolutely do have to

38:50.737 --> 38:52.681
and there is a close collaboration

38:52.681 --> 38:54.629
that's needed between all of those

38:54.639 --> 38:56.472
folks , including your financial

38:56.472 --> 38:58.695
management people and everything else .

38:58.695 --> 39:00.590
But uh I've seen that , that the

39:00.600 --> 39:03.050
decisions that I've had to make um uh

39:03.060 --> 39:06.540
it , it , it helps to be aware of all

39:06.550 --> 39:09.855
of the uh nuances and , and all of the

39:09.865 --> 39:12.615
uh processes . Like I was getting back

39:12.625 --> 39:14.958
to the first question that you asked me .

39:14.958 --> 39:17.069
It's about knowing a little bit about

39:17.069 --> 39:18.958
everything , right ? So I have to

39:18.958 --> 39:21.181
understand the financial management , I

39:21.181 --> 39:20.476
have to understand the program

39:20.486 --> 39:22.597
management . I have to understand the

39:22.597 --> 39:24.764
acquisition processes . Plus I have to

39:24.764 --> 39:26.930
act uh understand the technical pieces

39:26.930 --> 39:28.930
of it in order to make decisions on

39:28.930 --> 39:30.930
what we're gonna buy . Does it make

39:30.930 --> 39:33.153
sense for us to buy it ? Do I do a cost

39:33.153 --> 39:35.208
analysis on that ? Right . And , and

39:35.208 --> 39:37.319
does it make business sense for us to

39:37.319 --> 39:39.153
do it ? And oh , by the way , if

39:39.153 --> 39:41.264
there's political pressures , how you

39:41.264 --> 39:43.597
go about juggling those as well ? So it ,

39:43.597 --> 39:45.708
it , it's a lot , it , it really is a

39:45.708 --> 39:47.819
lot . Yeah . So I'll uh thank you for

39:47.819 --> 39:50.097
the answer and I'll ask maybe uh Chris ,

39:50.097 --> 39:52.208
right in that scenario , if something

39:52.208 --> 39:54.330
goes wrong , right ? It's usually the

39:54.340 --> 39:56.562
CIO that gets called , even though it's

39:56.562 --> 39:58.830
not developed in Cio or Cio may not be

39:58.840 --> 40:01.209
aware of those architectural decisions

40:01.219 --> 40:05.149
that are taking place . Um How do

40:05.159 --> 40:07.239
you deal with the principle that a

40:07.439 --> 40:09.870
manufacturing error is usually meaning

40:09.879 --> 40:12.439
uh a design uh of an error is caught in

40:12.449 --> 40:14.560
the design phase . It's a lot cheaper

40:14.560 --> 40:16.727
than to fix it in a production error .

40:16.727 --> 40:18.338
Right ? Typically we see the

40:18.338 --> 40:20.671
intersection of this at , at a to , hey ,

40:20.671 --> 40:22.893
I need you to a to this and we see that

40:22.893 --> 40:25.005
the risk is just too great . And then

40:25.005 --> 40:27.171
you have a mission that is driving and

40:27.171 --> 40:29.338
saying , hey , I need this right ? And

40:29.338 --> 40:31.282
20 years ago , I would say mission

40:31.282 --> 40:33.449
drove it today , the risk of China and

40:33.449 --> 40:35.449
or the the the cyber threat and the

40:35.449 --> 40:37.393
risk that is driven by our foreign

40:37.393 --> 40:40.030
adversaries , you know , puts uh you

40:40.040 --> 40:42.979
know , puts the cio and ciso um having

40:42.989 --> 40:45.100
a seat and a voice at a table and how

40:45.100 --> 40:47.322
do you deal with that , you know , with

40:47.322 --> 40:49.378
that challenge ? No , thank you very

40:49.378 --> 40:51.433
much . I appreciate that . One thing

40:51.433 --> 40:53.489
that we've tried to do is to embrace

40:53.489 --> 40:55.711
still relatively new , but the adaptive

40:55.711 --> 40:57.822
acquisition framework that dod rolled

40:57.822 --> 40:59.767
out a couple of years ago . And so

40:59.767 --> 41:01.933
we've been able to move several of our

41:01.933 --> 41:03.933
acquisition programs over to one of

41:03.933 --> 41:06.149
those designated pathways , software

41:06.159 --> 41:08.699
acquisition pathway , for example , has

41:08.709 --> 41:10.969
really been pretty successful . Now ,

41:10.979 --> 41:13.090
some of the things I have seen that I

41:13.090 --> 41:15.035
think are very helpful in terms of

41:15.035 --> 41:17.257
addressing the risks you talked about .

41:17.257 --> 41:19.919
One is uh and really goes to governance

41:19.929 --> 41:22.096
in that , at least in the Navy , we've

41:22.096 --> 41:24.262
really decided there's kind of an iron

41:24.262 --> 41:26.485
triangle of governance . We need to get

41:26.485 --> 41:28.540
the fleet or the user activity , the

41:28.540 --> 41:30.540
acquisition community or the people

41:30.540 --> 41:32.596
actually building the capability and

41:32.596 --> 41:34.596
then the sponsor most often nev and

41:34.600 --> 41:37.669
meet frequently and deal with things in

41:37.679 --> 41:40.070
discrete units and have a very clear

41:40.080 --> 41:42.399
idea each step of the way what our kind

41:42.409 --> 41:44.550
of our bounding box is . And so it's

41:44.560 --> 41:46.989
things like in the past , we were doing

41:47.199 --> 41:49.088
major acquisitions , use the more

41:49.088 --> 41:51.310
traditional model , it might be several

41:51.310 --> 41:53.477
months or years , years or even longer

41:53.689 --> 41:57.110
to suddenly discover a design defect

41:57.120 --> 41:59.679
very early on . And now it is so late

41:59.689 --> 42:02.389
in the program , it may not be , you

42:02.399 --> 42:04.566
know , survivable , right ? And so for

42:04.566 --> 42:06.677
meeting every couple months , perhaps

42:06.677 --> 42:08.621
or even more frequently and having

42:08.621 --> 42:10.750
opportunities to do the cross check ,

42:10.760 --> 42:12.871
then I'm finding it's a lot easier to

42:12.871 --> 42:15.370
find and fix problems earlier in the

42:15.379 --> 42:18.469
process . We've also tried to really

42:18.479 --> 42:20.701
operationalize our approach to the risk

42:20.701 --> 42:23.030
management framework to again provide

42:23.040 --> 42:25.260
earlier and more frequent checks along

42:25.270 --> 42:28.100
the way . And um and I think we've had

42:28.110 --> 42:30.550
a lot of success in trying to use the

42:30.560 --> 42:33.429
high risk escalation process to be able

42:33.439 --> 42:35.439
not just to , you know , call out a

42:35.439 --> 42:37.439
specific program , but to help that

42:37.439 --> 42:39.606
program help itself . And so we've got

42:39.606 --> 42:41.661
a number of success stories over the

42:41.661 --> 42:43.717
past several months where we've been

42:43.717 --> 42:45.550
able to take a program high risk

42:45.550 --> 42:47.772
escalation back to the point where it's

42:47.772 --> 42:49.883
actually running straight and true in

42:49.883 --> 42:51.995
doing what we needed to do within the

42:51.995 --> 42:54.161
architecture . It's interesting that a

42:54.161 --> 42:56.272
lot of those levers really come to me

42:56.272 --> 42:58.439
from my role as a programmer , more so

42:58.439 --> 43:00.810
than my role as a CIO and the cio side ,

43:01.449 --> 43:03.709
the hardest thing I think has been to

43:03.719 --> 43:05.780
really define an enterprise

43:05.790 --> 43:08.790
architecture and then try to get people

43:08.800 --> 43:11.070
to operate within it . And so like in

43:11.080 --> 43:13.989
the 2017 time frame , we came up with

43:14.000 --> 43:16.222
an enterprise approach , we called NANT

43:16.222 --> 43:18.500
one , the Naval Intelligence operation ,

43:18.500 --> 43:20.500
networked enterprise and add one of

43:20.500 --> 43:22.667
those rare opportunities in government

43:22.667 --> 43:24.778
to be there at the beginning . And at

43:24.778 --> 43:26.722
the end , it's seven year planning

43:26.722 --> 43:28.667
period just wrapped up a couple of

43:28.667 --> 43:30.389
weeks ago . And uh normally in

43:30.389 --> 43:32.444
government , you get to start , then

43:32.444 --> 43:34.667
run away before it finishes . And so it

43:34.667 --> 43:34.469
was interesting to be able to kind of

43:34.479 --> 43:37.149
run a scorecard on our team on myself

43:37.159 --> 43:39.360
and say , OK , this is what we had set

43:39.370 --> 43:42.469
out to achieve in 2017 . Where did we

43:42.479 --> 43:44.701
succeed ? Where did we fail ? Where did

43:44.701 --> 43:46.812
we have some , you know , some things

43:46.812 --> 43:48.979
there in the middle , I give us a like

43:48.979 --> 43:51.146
an 85% which isn't really too terribly

43:51.146 --> 43:53.368
bad . But so I think to summarize to be

43:53.368 --> 43:55.701
able to have an enterprise architecture ,

43:55.701 --> 43:55.419
to be able to take advantage of the

43:55.429 --> 43:57.540
adaptive acquisition framework and to

43:57.540 --> 43:59.596
be able to really be skillful in the

43:59.596 --> 44:01.610
use of RMF . Those three lovers are

44:01.620 --> 44:05.179
very , very helpful . Uh Mike um

44:05.750 --> 44:07.861
you know , we have seen uh one of the

44:07.861 --> 44:10.083
things that , you know , uh we're doing

44:10.083 --> 44:12.330
on our side is if Kat's products exist

44:12.340 --> 44:14.284
again , going back to the original

44:14.284 --> 44:16.507
question that of Gao , right ? Saying ,

44:16.507 --> 44:18.879
hey , 90% of projects fail . Um If you

44:18.889 --> 44:21.111
see Kat's products that are available ,

44:21.111 --> 44:23.222
one of the things that we've tried to

44:23.222 --> 44:25.111
enforce is that if Kat's products

44:25.111 --> 44:27.222
available , we're not gonna customize

44:27.222 --> 44:29.222
it because if you do customize it ,

44:29.222 --> 44:31.333
right , you lose all the , you know ,

44:31.333 --> 44:33.333
sequential updates , right ? You ac

44:33.333 --> 44:35.445
accumulate technical debt and right ,

44:35.445 --> 44:37.611
you're , you're risking API S that are

44:37.611 --> 44:39.556
broken . In addition , what you're

44:39.556 --> 44:41.667
really saying to the vendor community

44:41.667 --> 44:43.667
who are like domain experts in that

44:43.667 --> 44:45.945
field that , you know , we know in our ,

44:45.945 --> 44:48.111
you know , within our small government

44:48.111 --> 44:50.222
organizations um of like , you know ,

44:50.222 --> 44:52.389
picking , pick whatever number 5000 to

44:52.389 --> 44:54.600
50,000 or 20,000 that we know better

44:54.610 --> 44:57.090
than what millions of users are using

44:57.100 --> 44:59.229
uh across the , you know , across

44:59.239 --> 45:01.879
across the globe . So if coats products

45:01.889 --> 45:04.770
exist , our goal is to adopt that ,

45:04.780 --> 45:07.002
right ? But what we're seeing now , the

45:07.002 --> 45:09.169
general trend is now SASS products are

45:09.169 --> 45:11.391
coming out , right ? That's the the the

45:11.391 --> 45:13.558
trend , right ? How do you deal with a

45:13.558 --> 45:15.558
Sass product ? And in Dia , we have

45:15.558 --> 45:17.558
about three SAS products that we're

45:17.558 --> 45:19.724
trying to build in and you know , into

45:19.724 --> 45:19.300
our environment . What are the

45:19.310 --> 45:21.366
challenges that you face in terms of

45:21.366 --> 45:23.088
building a SAS product that is

45:23.088 --> 45:25.310
commercially available towards bringing

45:25.310 --> 45:27.477
that in into a closed loop environment

45:27.477 --> 45:29.532
like ours on J Wicks . Yeah , S A is

45:29.532 --> 45:31.866
tough in an air gap network environment ,

45:31.866 --> 45:34.088
right ? So , well , today , if you want

45:34.088 --> 45:36.469
to have a SASS , we are running the

45:36.479 --> 45:38.709
SASS , not the vendor itself , which is

45:38.719 --> 45:42.149
I would say not true . S A if I want

45:42.159 --> 45:43.937
like we have enterprise license

45:43.937 --> 45:45.937
agreements and say I wanted to have

45:45.937 --> 45:48.048
service . Now , for example , I would

45:48.048 --> 45:50.270
then instantiate service . Now again in

45:50.270 --> 45:53.500
my classified environment and run that

45:53.570 --> 45:55.681
and probably get some people from the

45:55.681 --> 45:57.848
company that know that product to work

45:57.848 --> 45:59.792
for us to make that products as it

45:59.792 --> 46:03.610
should be . And um that's not SASS but

46:03.620 --> 46:05.620
to the customer , it is like to the

46:05.620 --> 46:07.731
user that's actually logging into the

46:07.731 --> 46:10.009
SAS , they don't know all the back end .

46:10.009 --> 46:12.120
So it's still sass to them . But from

46:12.120 --> 46:14.120
us , the capability deliverers , we

46:14.120 --> 46:16.120
know that the people that should be

46:16.120 --> 46:18.342
actually delivering that capability are

46:18.342 --> 46:17.459
the ones that build it and know it the

46:17.469 --> 46:20.580
best . And so why can't service now run

46:20.590 --> 46:22.969
it at all ? Three classifications and ,

46:23.149 --> 46:25.620
and we technologically can , we're

46:25.629 --> 46:27.899
blazing some trails with that . So if

46:27.909 --> 46:30.610
they can deliver the new updates in

46:30.620 --> 46:33.100
their containerized application through

46:33.110 --> 46:35.300
a pipeline at UN class with their

46:35.310 --> 46:37.620
workforce , we can move that up into

46:37.629 --> 46:40.270
production at secret NTS and parody and

46:40.280 --> 46:42.610
keep it , um keep it going and they had

46:42.620 --> 46:44.787
needed maybe a smaller workforce to be

46:44.787 --> 46:47.270
able to do the help desk activities and

46:47.280 --> 46:50.020
use us more as a front end to scale out

46:50.040 --> 46:52.620
the customers as needed . But the

46:52.629 --> 46:55.679
majority of the actual running of that

46:55.689 --> 46:58.179
S A is from the people that actually

46:58.270 --> 47:01.080
built the product and , uh their dev

47:01.179 --> 47:03.939
ops team is now running it versus , you

47:03.949 --> 47:05.899
know , us instantiating it again ,

47:05.909 --> 47:08.131
whether that and we've kind of got that

47:08.131 --> 47:11.100
with 365 but not even that because we

47:11.110 --> 47:13.054
asked for Microsoft to embed their

47:13.054 --> 47:15.221
employees into our units and we didn't

47:15.221 --> 47:17.332
really trust how they were doing it .

47:17.332 --> 47:19.499
It wasn't true as because we have this

47:19.499 --> 47:21.499
like we run email , we need to know

47:21.499 --> 47:23.721
what you're doing . And so we have this

47:23.721 --> 47:25.721
blended team now doing that . And I

47:25.721 --> 47:28.350
think true as is where the team that we

47:28.360 --> 47:30.600
asked to provide that is providing it .

47:30.820 --> 47:33.040
And uh we don't have to do that again

47:33.790 --> 47:35.846
to the customer . They're not know ,

47:35.846 --> 47:38.969
but we know , ok , let's go to , you

47:38.979 --> 47:40.979
know , you talked about cost rising

47:40.979 --> 47:43.090
enterprise cost for us is rising from

47:43.090 --> 47:46.090
our cheapest , our cheapest uh

47:46.100 --> 47:49.850
inflection point was 30% to almost 300% .

47:50.560 --> 47:53.350
Um So enterprise cost is exponentially

47:53.360 --> 47:56.739
rising . The cyber security threats are

47:56.750 --> 47:59.739
ever changing and evolving . Zero trust

47:59.750 --> 48:02.370
requirements are looming , especially

48:02.379 --> 48:04.379
compliant to connect and comply and

48:04.379 --> 48:07.310
compliance requirements . Uh Critical

48:07.320 --> 48:10.939
infrastructure is aging , the demands

48:10.949 --> 48:13.020
for shiny new toys , either

48:13.030 --> 48:16.530
applications um or A I ,

48:16.939 --> 48:19.510
right . Still , the customer is still

48:19.520 --> 48:22.000
pressing , how do you balance all these

48:22.010 --> 48:24.129
things against the backdrop of a flat

48:24.139 --> 48:26.479
budget or a declining budget , Lisa .

48:26.489 --> 48:29.159
I'll start with you . Wow . Yeah . So

48:29.169 --> 48:31.699
it's , it's a juggling act , right ? So ,

48:31.709 --> 48:33.820
and , and we in the Marine Corps , we

48:33.820 --> 48:35.987
have a very small budget to begin with

48:35.987 --> 48:37.765
and with all of these competing

48:37.765 --> 48:39.876
priorities that we have uh zero trust

48:39.876 --> 48:41.709
being , you know , first and for

48:41.709 --> 48:43.931
foremost , right now , how are we gonna

48:43.931 --> 48:46.439
integrate uh these , these requirements

48:46.449 --> 48:48.671
into our architecture ? Right ? And how

48:48.671 --> 48:50.727
much is that the cost and every time

48:50.727 --> 48:52.782
you go to look and see how much it's

48:52.782 --> 48:55.060
gonna cost , it's unaffordable , right ?

48:55.060 --> 48:56.893
So , so we need to be able to uh

48:56.893 --> 48:59.982
partner with some of our , our larger

49:00.212 --> 49:04.193
uh you know , uh IC partners uh to take

49:04.202 --> 49:06.742
advantage of a service , maybe that

49:06.752 --> 49:09.343
they can provide or licenses that they

49:09.353 --> 49:12.656
can , you know , help us uh a , a choir

49:12.756 --> 49:15.196
because it's , it's uh virtually

49:15.206 --> 49:18.726
impossible . We can't afford to give up

49:18.746 --> 49:20.913
what we're doing right now in order to

49:20.913 --> 49:23.496
get to the next thing , right ? So we

49:23.506 --> 49:25.728
wanna , we wanna be all in , in cloud ,

49:25.728 --> 49:27.839
we wanna be all in , in , in software

49:27.839 --> 49:30.006
as a service , but we can't because we

49:30.006 --> 49:32.228
can't afford it and I can't go back and

49:32.228 --> 49:34.284
ask for more money , right ? Because

49:34.284 --> 49:36.506
this is all we're gonna get and oh , by

49:36.506 --> 49:38.673
the way , that's getting cut next year

49:38.673 --> 49:38.489
and a little bit more the year after

49:38.500 --> 49:41.000
that . So , uh i it's a challenge . And

49:41.010 --> 49:44.070
we need really , we need uh help from

49:44.080 --> 49:46.320
the vendor community to try to try to

49:46.330 --> 49:49.500
synchronize and level set and , and uh

49:49.510 --> 49:52.639
try to lower the costs across the

49:52.649 --> 49:54.816
environment , right ? Either all IC or

49:54.816 --> 49:57.600
all dod or all government , right ? And ,

49:57.610 --> 50:00.260
and that I think would benefit all of

50:00.270 --> 50:03.129
us . OK , Chris , anything different ?

50:03.250 --> 50:05.709
Any thoughts from the programmer

50:05.719 --> 50:07.830
perspective ? One of the things where

50:07.830 --> 50:10.870
we really need to improve within dod is

50:10.879 --> 50:14.270
on cost estimation and working with

50:14.280 --> 50:16.610
fuel supplies , whatever it may be , I

50:16.620 --> 50:18.842
think programmers realize there's gonna

50:18.842 --> 50:21.860
be a range of potential outcomes . And

50:21.870 --> 50:24.037
so I think when people are approaching

50:24.037 --> 50:25.926
us , whether they want enterprise

50:25.926 --> 50:28.092
software licensing or anything else in

50:28.092 --> 50:29.926
that category is to give us that

50:29.926 --> 50:32.037
sensitivity analysis so that we don't

50:32.037 --> 50:34.500
end up undermining our own credibility .

50:34.510 --> 50:36.679
When the next year , the cost ends up

50:36.689 --> 50:38.800
being nothing like we'd predicted the

50:38.800 --> 50:41.022
time before . There's that part of it ,

50:41.022 --> 50:43.133
the other one . And this is just kind

50:43.133 --> 50:45.300
of the sad reality of how we do things

50:45.300 --> 50:47.356
in dod is that the O and M lines are

50:47.356 --> 50:49.467
normally the first things that we cut

50:49.467 --> 50:51.578
where we're trying to balance against

50:51.578 --> 50:53.689
our investment accounts , right ? And

50:53.689 --> 50:53.600
for some of these things , you know ,

50:53.610 --> 50:55.899
the mantra is , hey , we'll deal with

50:55.909 --> 50:58.131
it in the year of execution . And so we

50:58.131 --> 51:00.620
need to kind of as we do PB reform ,

51:00.629 --> 51:03.139
think about how do we now honor our O

51:03.149 --> 51:06.500
and M lines better there's a lot of

51:06.510 --> 51:08.510
legislative proposals of the things

51:08.510 --> 51:10.732
that are out there . But if we're going

51:10.732 --> 51:13.389
to be in a services construct , we need

51:13.399 --> 51:15.739
to really put the same level of rigor

51:15.750 --> 51:18.110
and discipline and focus in our O and M

51:18.120 --> 51:20.342
accounts as we do on our RDT and in our

51:20.342 --> 51:23.600
procurement , uh we have about 10

51:23.610 --> 51:26.090
minutes left . So what I like to do and

51:26.100 --> 51:28.322
so to answer your uh not to answer your

51:28.322 --> 51:30.489
question . But Lisa , I think in terms

51:30.489 --> 51:32.600
of , you know , how we can help you .

51:32.600 --> 51:34.767
Um especially on the zero trust side ,

51:34.767 --> 51:34.760
we're gonna build enterprise

51:34.770 --> 51:36.603
requirements . Um I don't know ,

51:36.603 --> 51:39.010
enterprise services uh that enterprise

51:39.020 --> 51:41.131
services is not just for dia but it's

51:41.131 --> 51:43.464
also for the service intel uh community .

51:43.464 --> 51:45.576
And we would love for you to leverage

51:45.576 --> 51:47.629
uh We want you to leverage our

51:47.639 --> 51:49.750
enterprise services as long as we can

51:49.750 --> 51:51.806
afford it . That's , that's , that's

51:51.806 --> 51:53.972
the big , the big issue . Yeah . Um So

51:53.972 --> 51:56.139
within the time left , I'll start from

51:56.139 --> 51:58.139
the end and walk down . If you were

51:58.139 --> 52:01.300
king for a day or queen per day ,

52:02.409 --> 52:06.110
what would you implement ? Excellent

52:06.120 --> 52:08.739
question . Really hard to answer . Um I

52:08.750 --> 52:11.600
would say uh if you wanna move data

52:11.610 --> 52:14.159
around the world and you wanna use A I

52:14.169 --> 52:16.550
capabilities , you need the pipes to be

52:16.560 --> 52:18.780
able to support doing that . And our

52:18.790 --> 52:21.139
networks are all over the place . I

52:21.149 --> 52:23.260
would say that uh you know , it would

52:23.260 --> 52:25.371
be , it sometimes it's easier to just

52:25.371 --> 52:29.169
start over , right . So if uh you know ,

52:29.590 --> 52:32.330
I work for a day and the decision had

52:32.340 --> 52:34.340
to be made and all the money in the

52:34.340 --> 52:36.284
world was available to do this . I

52:36.284 --> 52:38.173
would start over Greenfield on an

52:38.173 --> 52:40.118
entire network solution and employ

52:40.118 --> 52:42.659
federal level identity and access

52:42.669 --> 52:46.340
management um to support data

52:46.350 --> 52:48.572
applications , interfaces , et cetera .

52:48.899 --> 52:51.066
Uh I think that would be the right way

52:51.066 --> 52:54.889
to go . OK , Lisa , if I could be queen

52:54.899 --> 52:57.409
for a day in my position , I would want

52:57.419 --> 53:00.689
everything as a service , right ? I we

53:00.699 --> 53:02.921
need as government employees to be able

53:02.921 --> 53:04.977
to focus on what our real jobs are ,

53:04.977 --> 53:07.199
right ? And , and in order to do that ,

53:07.199 --> 53:09.421
we need to have the experts , which are

53:09.421 --> 53:11.643
the vendor community and the folks that

53:11.643 --> 53:13.588
do this and have all the technical

53:13.588 --> 53:15.588
expertise to do all these technical

53:15.588 --> 53:17.699
things for us , right ? So that would

53:17.699 --> 53:19.866
be great if I could just in affordable

53:19.866 --> 53:22.239
way to pay for everything and let the

53:22.250 --> 53:24.399
vendor community do it for us as a

53:24.409 --> 53:26.739
service would be , that would be a

53:26.750 --> 53:28.972
dream for me because then I could focus

53:28.972 --> 53:31.083
on being the cio and looking at , you

53:31.083 --> 53:33.306
know , how we're going to move into the

53:33.306 --> 53:35.306
next thing and start thinking about

53:35.306 --> 53:37.194
these things , whether instead of

53:37.194 --> 53:39.528
putting out the fire of the day , right ?

53:39.528 --> 53:41.639
My network's down or this this server

53:41.639 --> 53:43.694
went offline , right ? I don't wanna

53:43.694 --> 53:46.719
have to deal with that , Mike if I

53:46.729 --> 53:48.840
could be king for a day with infinite

53:48.840 --> 53:51.260
money and power . I would

53:52.469 --> 53:55.520
change how we do our , it workforce

53:55.530 --> 53:59.469
activities . I , I think that um we

53:59.479 --> 54:01.701
talk a lot about how do we retain an it

54:01.701 --> 54:04.209
workforce and , and , and all of that .

54:04.409 --> 54:06.465
I , I don't know that there is an it

54:06.465 --> 54:08.576
workforce out there that's coming out

54:08.576 --> 54:10.687
and saying I wanna work somewhere for

54:10.687 --> 54:13.080
20 years . Um And so how do we make it

54:13.090 --> 54:16.770
so that it is easier to come and go and

54:16.780 --> 54:18.891
that if we had that infinite budget ,

54:18.891 --> 54:21.300
it was a commensurate pay scale that

54:21.310 --> 54:23.143
would allow them to work on cool

54:23.143 --> 54:25.780
mission . But come and go into our

54:25.790 --> 54:28.012
community with a low barrier of entry .

54:28.012 --> 54:30.479
Not that it takes me another month to

54:30.760 --> 54:33.790
um get my accounts and my computer set

54:33.800 --> 54:35.689
up and I'm sitting around like it

54:35.689 --> 54:38.209
should be seamless to come and go as an

54:38.219 --> 54:40.419
employee in it because we're not

54:40.429 --> 54:42.429
generating , you know , the , we're

54:42.429 --> 54:44.485
generating the best fighter pilots ,

54:44.485 --> 54:46.262
we're generating the best intel

54:46.262 --> 54:48.373
officers , but it is not a military ,

54:48.373 --> 54:50.540
unique thing and we are not generating

54:50.540 --> 54:52.540
the best of that . So let's make it

54:52.540 --> 54:54.707
easy to come and go . And I have a , a

54:54.707 --> 54:56.929
lot of reservists and I think the , the

54:56.929 --> 54:59.096
model of that is great . I have people

54:59.096 --> 55:01.318
that work out in industry and then come

55:01.318 --> 55:03.151
on orders and work for us in the

55:03.151 --> 55:05.040
military , bring that expertise .

55:05.040 --> 55:07.040
They're sitting on this side of the

55:07.040 --> 55:08.929
table in this uniform and they're

55:08.929 --> 55:10.929
talking in an educated way to their

55:10.929 --> 55:10.750
counterparts out there and then they go

55:10.760 --> 55:13.919
back and it's , it's great with , I

55:13.929 --> 55:16.096
mean , it works really well . So if we

55:16.096 --> 55:18.262
could do that at a large scale and the

55:18.262 --> 55:20.485
it workforce is very different than the

55:20.485 --> 55:22.850
rest of them , it would be awesome . Ok ,

55:23.030 --> 55:25.709
Chris , if our king for day , what I

55:25.719 --> 55:27.719
would most want is for the American

55:27.719 --> 55:29.830
people to get to see what I see every

55:29.830 --> 55:31.997
day . And that's some incredible human

55:31.997 --> 55:33.997
beings who come together to do this

55:33.997 --> 55:36.669
work . Uh It barring that I would love

55:36.679 --> 55:38.901
it if the greater dod could see what we

55:38.901 --> 55:41.449
do often times intelligence is what I

55:41.459 --> 55:43.889
would call the big yellow arrow on the

55:43.899 --> 55:46.320
right side of the OB one diagram , it

55:46.330 --> 55:48.909
just appears and I want people to

55:48.919 --> 55:51.540
realize that it appears because of

55:51.550 --> 55:53.830
collectors and analysts and agents and

55:53.840 --> 55:55.909
enablers who are working around the

55:55.919 --> 55:58.149
world and around the clock to do this

55:58.159 --> 56:00.381
very important work . What I would wish

56:00.381 --> 56:02.659
if we had infinite money is we would

56:02.669 --> 56:04.502
transform the architecture to be

56:04.502 --> 56:07.100
oriented on them . We talk a lot about

56:07.120 --> 56:08.820
data Centricity , application

56:08.830 --> 56:11.052
Centricity network Centricity . I would

56:11.052 --> 56:14.060
love for us to be human center . And I

56:14.070 --> 56:16.229
think about um as we're sitting here

56:16.239 --> 56:18.560
right now , there's undoubtedly a petty

56:18.570 --> 56:21.530
officer on watch and some DDG in a Ford

56:21.540 --> 56:24.330
C area who was working way too hard to

56:24.340 --> 56:26.879
pull data together to try to answer

56:26.889 --> 56:28.945
questions for his or her commander .

56:28.945 --> 56:31.379
And I just think that our next big

56:31.389 --> 56:33.379
revolution is putting that petty

56:33.389 --> 56:35.500
officer at the center of our thinking

56:35.500 --> 56:37.556
and building the architecture around

56:37.556 --> 56:39.833
him or her . Thank you . Thank you all .

56:39.833 --> 56:42.100
I think if I working for the day , this

56:42.110 --> 56:44.277
is what I would want . I would want my

56:44.277 --> 56:46.959
experience on Saturday and Sunday to be

56:46.969 --> 56:50.409
the same from Monday through Friday

56:50.419 --> 56:52.870
today . It's not right . And there are

56:52.879 --> 56:55.389
really three simple things that this

56:55.780 --> 56:57.879
does , that we in the government do

56:57.889 --> 57:00.250
terribly right . Think of your most

57:00.260 --> 57:03.050
expensive app on your phone . What is

57:03.060 --> 57:05.227
it ? Think of the most expensive app ?

57:05.227 --> 57:07.560
Right . It's , it's few dollars a month .

57:07.560 --> 57:09.727
If it may be a subscription model , it

57:09.727 --> 57:11.949
might be a few dollars a year . Right .

57:11.949 --> 57:14.171
There are three things the , the iphone

57:14.171 --> 57:16.282
has . Right ? One , it has enterprise

57:16.282 --> 57:18.393
security services . So no matter what

57:18.393 --> 57:18.350
app you use , you can use your face

57:18.360 --> 57:20.527
recognition . That's security , that's

57:20.527 --> 57:22.749
an enterprise security services today .

57:22.749 --> 57:24.749
We don't do that , right . We allow

57:24.749 --> 57:26.971
customized security services within the

57:26.971 --> 57:28.860
application rate for the vendor .

57:28.860 --> 57:30.749
Terrible for the community and in

57:30.749 --> 57:32.916
terrible , in terms of cost , in terms

57:32.916 --> 57:34.860
of , you know , risk . I think the

57:34.860 --> 57:36.693
second thing they have is common

57:36.693 --> 57:38.860
infrastructure services . Right . So ,

57:38.860 --> 57:41.027
think of it . Um , how much do you pay

57:41.027 --> 57:43.193
for your phone ? You might , you might

57:43.193 --> 57:42.300
pay for your networks like , you know ,

57:42.310 --> 57:44.620
$50 a month . Right . That's about $600

57:44.629 --> 57:47.909
a year . You pay maybe $1000 for your

57:47.919 --> 57:50.159
phone and your apps . We pay a few

57:50.169 --> 57:53.050
dollars , right ? If any free . How do

57:53.060 --> 57:55.227
we do it in the government ? How do we

57:55.227 --> 57:57.338
do it in the IC ? We pay $100 million

57:57.338 --> 57:59.560
for the app . We're not gonna spend any

57:59.570 --> 58:01.792
money on infrastructure and we're gonna

58:01.792 --> 58:03.959
take risk on our local area networks .

58:03.959 --> 58:06.126
We have it backwards and we wonder why

58:06.126 --> 58:08.330
our experience is so different on

58:08.340 --> 58:10.229
Saturday and Sunday versus Monday

58:10.229 --> 58:12.173
through Friday . And you flip that

58:12.173 --> 58:14.173
around , we will be the standard of

58:14.173 --> 58:16.507
excellence by which everybody else will ,

58:16.507 --> 58:18.729
will follow . Thank you for your time ,

58:21.510 --> 58:25.449
baby . This is what you came for

58:27.139 --> 58:29.810
strikes every time she moans

58:33.280 --> 58:35.330
everybody is watching . All right .

58:35.340 --> 58:37.562
Thank you , Mr Matthews . Uh and to all

58:37.562 --> 58:40.239
of the panelists uh without further ado ,

58:40.250 --> 58:42.306
I'd like to turn it over uh one last

58:42.306 --> 58:44.979
time for this conference to uh Mr Casa

58:44.989 --> 58:47.959
to close us out uh for this absolutely

58:47.969 --> 58:50.229
fantastic dous worldwide conference

58:50.239 --> 58:52.729
that uh so many people have helped to

58:52.739 --> 58:55.500
uh to put on uh Mr Casa . The floor is

58:55.510 --> 58:55.979
yours .

59:05.239 --> 59:07.239
Microphone , check up swinging swat

59:07.280 --> 59:09.280
lecture , closing down the sector ,

59:09.280 --> 59:11.502
supreme neck protector . Better one can

59:11.502 --> 59:15.229
Mr meta pop pop with the pressure to

59:15.239 --> 59:17.739
the final day . Uh Thank you to that

59:17.750 --> 59:19.972
last panel . It was great . Uh They did

59:19.972 --> 59:21.917
a fantastic job . I thank them and

59:21.917 --> 59:23.972
every other panel that joined us , I

59:23.972 --> 59:26.028
think they're thankful that this was

59:26.028 --> 59:28.139
not an hr conference based on some of

59:28.139 --> 59:27.639
the comments that might result in swift

59:27.649 --> 59:31.510
action . Um I , I do

59:31.520 --> 59:33.742
wanna apologize to some of the others .

59:33.742 --> 59:35.909
Uh plenary speakers , I did say in the

59:35.909 --> 59:38.340
beginning that uh the intra music

59:38.350 --> 59:40.350
didn't have relevance to what we're

59:40.350 --> 59:42.770
doing here today . Um That music that

59:42.780 --> 59:44.891
you just heard was a collaboration by

59:44.891 --> 59:46.836
Red Man and Method Man that has no

59:46.836 --> 59:49.058
relevance on this conference or Omaha .

59:49.058 --> 59:51.169
Uh But it's my favorite collaboration

59:51.169 --> 59:53.224
of all artists and I celebrate their

59:53.224 --> 59:55.391
whole catalog . Uh But it doesn't mean

59:55.391 --> 59:57.770
that Omaha does not have its own famous

59:57.780 --> 01:00:00.709
musicians uh and celebrities . Uh In

01:00:00.719 --> 01:00:02.879
fact , you might be surprised to know

01:00:02.889 --> 01:00:05.000
uh well , many of , you know , Warren

01:00:05.000 --> 01:00:07.219
Buffett is from Omaha , right ? You

01:00:07.229 --> 01:00:09.800
might be surprised to know that Steve

01:00:09.810 --> 01:00:12.370
Borden is from Omaha . Anyone hear

01:00:12.379 --> 01:00:15.169
Steve Borden ? Yeah , that's right .

01:00:15.260 --> 01:00:18.780
Sting . The famous wwewwf wrestler

01:00:19.110 --> 01:00:21.350
actually battled uh Ric Flair in the

01:00:21.360 --> 01:00:24.080
final episode of Monday Nitro in March

01:00:24.090 --> 01:00:26.330
of 2001 right here from Omaha . That's

01:00:26.340 --> 01:00:29.729
right . And then Jojo Siwa who could

01:00:29.739 --> 01:00:33.500
forget her , a famous musician also on

01:00:33.510 --> 01:00:36.169
four episodes of or four seasons of

01:00:36.179 --> 01:00:39.090
dance moms . So all from Omaha . So I

01:00:39.100 --> 01:00:41.389
think we have a lot to uh recognize

01:00:41.399 --> 01:00:44.010
here today . Uh But anyway , Omaha ,

01:00:44.020 --> 01:00:46.242
you didn't come for those celebrities .

01:00:46.242 --> 01:00:48.242
Some of you may have , but you came

01:00:48.242 --> 01:00:50.409
because this location is home to a lot

01:00:50.409 --> 01:00:52.187
of innovation , right ? We have

01:00:52.187 --> 01:00:54.739
stratcom here and any time we have one

01:00:54.750 --> 01:00:56.790
of these notice conferences at a

01:00:56.800 --> 01:00:58.800
location where there is a combatant

01:00:58.800 --> 01:01:00.689
command . We always have a ton of

01:01:00.689 --> 01:01:02.689
participation . That's no different

01:01:02.689 --> 01:01:04.800
here today . 2018 was my first notice

01:01:04.800 --> 01:01:06.800
conference , as I mentioned . Uh at

01:01:06.800 --> 01:01:08.949
that time , we had 2600 participants

01:01:09.290 --> 01:01:11.229
here . This week was actually the

01:01:11.239 --> 01:01:13.295
second largest conference that we've

01:01:13.295 --> 01:01:15.406
had in the history of hosting Dodi as

01:01:15.406 --> 01:01:17.830
Jennifer Ron told us or taught us as

01:01:17.840 --> 01:01:21.600
the plural of dois is um we had

01:01:21.610 --> 01:01:25.399
4064 participants this week ,

01:01:25.409 --> 01:01:27.298
which is amazing . Again , second

01:01:27.298 --> 01:01:30.280
highest ever uh that was uh about 1500

01:01:30.290 --> 01:01:32.800
vendors alone uh that represented and ,

01:01:32.810 --> 01:01:34.921
and demonstrated their technologies ,

01:01:34.921 --> 01:01:36.810
technologies . Really a fantastic

01:01:36.810 --> 01:01:39.149
participation . You heard a lot this

01:01:39.159 --> 01:01:41.600
week , we heard from the J two panels

01:01:41.610 --> 01:01:43.689
which talked a lot about the uh

01:01:43.699 --> 01:01:45.939
challenges we have on the intelligence

01:01:45.949 --> 01:01:48.060
side , many of which we've dealt with

01:01:48.060 --> 01:01:50.227
since the beginning of time , but many

01:01:50.227 --> 01:01:52.171
new challenges that we have and uh

01:01:52.171 --> 01:01:54.338
emerging threats such as those uh from

01:01:54.338 --> 01:01:56.449
China . Uh but also enduring , like I

01:01:56.449 --> 01:01:58.616
say from Russia that , that we've been

01:01:58.616 --> 01:02:00.727
dealing with since the Cold War . You

01:02:00.727 --> 01:02:02.671
heard from the five I panel , they

01:02:02.671 --> 01:02:04.449
stressed the need for of course

01:02:04.449 --> 01:02:06.616
collaboration , especially on networks

01:02:06.616 --> 01:02:08.782
and data . Um We also talked about the

01:02:08.782 --> 01:02:10.782
challenges with identity management

01:02:10.782 --> 01:02:13.139
there . Um We also heard uh of course

01:02:13.149 --> 01:02:15.149
from the Ciso panel who spoke about

01:02:15.149 --> 01:02:17.316
Speedos and hot chocolate in a blanket

01:02:17.316 --> 01:02:19.371
uh reminding us of why they're under

01:02:19.371 --> 01:02:22.959
the leadership of CIO S . Uh but we

01:02:22.969 --> 01:02:25.191
heard a lot of common threads in all of

01:02:25.191 --> 01:02:27.136
those and , and one of the biggest

01:02:27.136 --> 01:02:29.191
common threads was on data , right ?

01:02:29.191 --> 01:02:31.358
And you heard that from the last panel

01:02:31.358 --> 01:02:33.191
of today , we're developing more

01:02:33.191 --> 01:02:35.413
systems than ever . Uh We are producing

01:02:35.413 --> 01:02:37.469
more data than ever in the history .

01:02:37.469 --> 01:02:39.689
And traditionally , it's really been

01:02:39.699 --> 01:02:41.921
divided into three phases . There's one

01:02:41.921 --> 01:02:43.921
collecting the data that's , that's

01:02:43.989 --> 01:02:46.560
been hard , but it's getting easier uh

01:02:46.570 --> 01:02:48.403
with the more systems that we're

01:02:48.403 --> 01:02:50.459
building . There's adding meaning to

01:02:50.459 --> 01:02:52.514
that data which has always been done

01:02:52.514 --> 01:02:54.626
through statistics , that's not new .

01:02:54.626 --> 01:02:56.848
But what is new is that data is getting

01:02:56.848 --> 01:02:59.070
in the hands of everyone all around the

01:02:59.070 --> 01:03:01.070
world . It's now proliferated which

01:03:01.070 --> 01:03:03.181
again is opportunities as I mentioned

01:03:03.181 --> 01:03:02.870
in the beginning of this , that's where

01:03:02.879 --> 01:03:04.935
a lot of innovation is coming from .

01:03:05.159 --> 01:03:07.550
But it's also the challenges where

01:03:07.620 --> 01:03:09.731
adding meaning to data has often been

01:03:09.731 --> 01:03:11.731
the prerogative and really the sole

01:03:11.731 --> 01:03:13.842
prerogative of governments around the

01:03:13.842 --> 01:03:16.009
world . That's no longer the case . We

01:03:16.009 --> 01:03:18.120
are now operating in a world of a lot

01:03:18.120 --> 01:03:19.898
of complexity . Uh and a lot of

01:03:19.898 --> 01:03:22.064
misinformation that as an intelligence

01:03:22.064 --> 01:03:24.342
community , as a department of defense ,

01:03:24.342 --> 01:03:26.453
we have to work through . And what we

01:03:26.453 --> 01:03:28.676
saw here today were opportunities to do

01:03:28.676 --> 01:03:30.398
that new tools that we we have

01:03:30.398 --> 01:03:32.398
available at our disposable to take

01:03:32.398 --> 01:03:34.398
advantage of new methods for adding

01:03:34.398 --> 01:03:36.342
meaning to that data , new ways to

01:03:36.342 --> 01:03:38.520
secure that data and new ways to get

01:03:38.530 --> 01:03:41.270
that from point A to point B , right .

01:03:41.280 --> 01:03:43.629
As cio S as technologists , we're

01:03:43.639 --> 01:03:45.639
operating the entire stack and this

01:03:45.639 --> 01:03:47.639
conference brings us all together .

01:03:47.639 --> 01:03:49.861
I've probably had as many of you a year

01:03:49.861 --> 01:03:51.972
worth of meetings over the past three

01:03:51.972 --> 01:03:53.917
days . Right . That's , that's the

01:03:53.917 --> 01:03:56.139
value of this conference . Not only are

01:03:56.139 --> 01:03:58.306
we being exposed to new technologies ,

01:03:58.306 --> 01:04:00.472
new methods of operating , but we're ,

01:04:00.472 --> 01:04:02.695
we're meeting with our colleagues , not

01:04:02.695 --> 01:04:05.189
just within the IC N dod , but a huge

01:04:05.199 --> 01:04:07.870
presence from industry and academia uh

01:04:07.879 --> 01:04:09.990
and other federal partners outside of

01:04:09.990 --> 01:04:12.212
our , our , our community . It's been a

01:04:12.212 --> 01:04:14.157
great conference this week again ,

01:04:14.157 --> 01:04:16.490
Omaha is my favorite location . Um Like ,

01:04:16.490 --> 01:04:18.657
like I experienced in 2018 when we had

01:04:18.657 --> 01:04:21.229
this first one this , this week proved

01:04:21.239 --> 01:04:24.050
the same that this is an excellent site

01:04:24.129 --> 01:04:26.185
and I , I have a few people to thank

01:04:26.185 --> 01:04:28.407
for hosting this conference . Um One is

01:04:28.407 --> 01:04:30.679
NC SI who is the vendor that helps put

01:04:30.689 --> 01:04:32.800
all of this together . There is a ton

01:04:32.800 --> 01:04:34.800
of work in managing a conference of

01:04:34.800 --> 01:04:36.949
4000 plus participants . Uh I wanna

01:04:36.959 --> 01:04:39.469
thank , of course , Captain Whiteley ,

01:04:39.479 --> 01:04:42.860
as well as Chief Kyle Peterson . Um

01:04:42.870 --> 01:04:45.179
They both did tremendous jobs as our M

01:04:45.189 --> 01:04:47.500
CS . Uh If you couldn't guess it was

01:04:47.510 --> 01:04:49.729
Amanda whose lifelong dream it was to

01:04:49.739 --> 01:04:52.780
come up here uh and moderate for us .

01:04:52.790 --> 01:04:54.957
Um So thank you both . Just a round of

01:04:54.957 --> 01:04:56.957
applause for them , both , please .

01:05:01.500 --> 01:05:03.611
And one final thank you . And it goes

01:05:03.611 --> 01:05:05.556
along with the theme of all of the

01:05:05.556 --> 01:05:07.667
speakers that you heard this week and

01:05:07.667 --> 01:05:09.889
that theme was integration , right ? As

01:05:09.889 --> 01:05:12.000
I , as I had mentioned , systems that

01:05:12.000 --> 01:05:14.222
work together are designed from the get

01:05:14.222 --> 01:05:16.278
go to integrate . You can't take two

01:05:16.278 --> 01:05:18.389
things that were developed and expect

01:05:18.389 --> 01:05:18.290
them to work seamlessly together . That

01:05:18.370 --> 01:05:20.592
just doesn't , it's not how engineering

01:05:20.592 --> 01:05:22.814
works , but part of integration is more

01:05:22.814 --> 01:05:25.037
than just integrating technology , it's

01:05:25.037 --> 01:05:27.259
integrating people , which as you heard

01:05:27.259 --> 01:05:29.370
from the last panel culture is really

01:05:29.370 --> 01:05:31.481
hard . I wanna thank one final person

01:05:31.481 --> 01:05:33.648
in this room and that's Mark Zola , if

01:05:33.648 --> 01:05:35.703
you could work your way to the stage

01:05:35.703 --> 01:05:37.703
while I , while I'm speaking . So ,

01:05:37.703 --> 01:05:39.814
Mark is our associate CIO , he's been

01:05:39.814 --> 01:05:42.219
with us for over a year . Uh Mark's

01:05:42.229 --> 01:05:45.679
responsibilities span far and wide and

01:05:45.689 --> 01:05:47.919
part of that responsibility is uh

01:05:47.929 --> 01:05:50.239
overseeing our communications team that

01:05:50.250 --> 01:05:52.250
helps coordinate this conference in

01:05:52.250 --> 01:05:54.649
collaboration with NC SI um But also

01:05:54.659 --> 01:05:57.429
Mark is in charge of all of our

01:05:57.439 --> 01:05:59.820
deployed forward , deployed CIO staff .

01:05:59.830 --> 01:06:02.052
So that's staff at all of the combatant

01:06:02.052 --> 01:06:03.941
commands that staff at all of the

01:06:03.941 --> 01:06:06.399
agencies we support both in the IC and

01:06:06.409 --> 01:06:08.810
dod . Uh But then also with our federal

01:06:08.820 --> 01:06:11.449
partners and that includes capabilities

01:06:11.459 --> 01:06:13.681
such as J Wick and our common operating

01:06:13.681 --> 01:06:15.792
environment . Mark is the linchpin of

01:06:15.792 --> 01:06:17.792
bringing all that together as their

01:06:17.792 --> 01:06:19.903
associate CIO . Today is his last day

01:06:19.903 --> 01:06:22.459
in Cio . He is moving on to be the

01:06:22.469 --> 01:06:25.159
Deputy J two of Transcom and I just

01:06:25.169 --> 01:06:27.225
wanna publicly thank Mark for all of

01:06:27.225 --> 01:06:29.280
the work that he's done to bring CIO

01:06:29.280 --> 01:06:31.391
together . We've had a lot of success

01:06:31.391 --> 01:06:33.058
over this past year under his

01:06:33.058 --> 01:06:35.225
leadership and he is a big part of our

01:06:35.225 --> 01:06:37.280
CIO family . He's a big part of this

01:06:37.280 --> 01:06:39.447
community . Uh Well , you may not have

01:06:39.447 --> 01:06:41.558
met Mark before . Hopefully , you did

01:06:41.558 --> 01:06:40.840
get a chance to meet him at this

01:06:40.850 --> 01:06:43.017
conference , but I assure you the work

01:06:43.017 --> 01:06:45.128
that he and his team does and what he

01:06:45.128 --> 01:06:47.294
leads impacts each of every one of you

01:06:47.294 --> 01:06:49.517
in this room and in this community . So

01:06:49.517 --> 01:06:49.110
just a couple of things to present to

01:06:49.120 --> 01:06:52.810
Mark one is a soccer ball . Mark

01:06:52.820 --> 01:06:55.169
loves soccer and this was signed by all

01:06:55.179 --> 01:06:57.679
of our CIO leads around the world . Um

01:06:57.689 --> 01:06:59.911
So they brought this for you and I just

01:06:59.911 --> 01:07:02.500
wanted to quickly present this . Thank

01:07:02.510 --> 01:07:05.520
you and finally our CIO coin .

01:07:06.229 --> 01:07:08.396
Thank you , Mark for all you've done .

01:07:16.159 --> 01:07:18.860
And then the final part of this closing

01:07:18.989 --> 01:07:21.100
and we're not gonna take the whole 30

01:07:21.100 --> 01:07:23.045
minutes here . I know , I know you

01:07:23.045 --> 01:07:22.919
wanna get out , I wanna get out

01:07:22.929 --> 01:07:26.129
probably more than you . Um But the

01:07:26.139 --> 01:07:28.139
final part that we do every year as

01:07:28.139 --> 01:07:30.139
part of our transition is a closing

01:07:30.139 --> 01:07:32.361
video that our team makes , that really

01:07:32.361 --> 01:07:34.417
captures the spirit of this week and

01:07:34.417 --> 01:07:33.909
the collaboration that you all have

01:07:33.919 --> 01:07:36.030
been a part of . I have not seen this

01:07:36.030 --> 01:07:38.363
closing video , so we're gonna see this ,

01:07:38.363 --> 01:07:40.308
this together at this time . Uh So

01:07:40.308 --> 01:07:42.419
without further ado , we will present

01:07:42.419 --> 01:07:44.530
the video which will officially close

01:07:44.530 --> 01:07:45.530
our conference ,

01:08:02.439 --> 01:08:04.540
the Dous conference in one word ,

01:08:04.830 --> 01:08:08.459
extraordinary insightful , influential

01:08:08.469 --> 01:08:12.100
partnership , innovation , opportunity ,

01:08:12.350 --> 01:08:15.889
collaboration required , inspiring

01:08:16.109 --> 01:08:18.790
game changing dope .

01:08:24.450 --> 01:08:26.172
The great thing about the Dous

01:08:26.172 --> 01:08:28.006
conference is it brings together

01:08:28.006 --> 01:08:29.950
academia , industry , government ,

01:08:29.950 --> 01:08:32.490
military legislation , defense and

01:08:32.500 --> 01:08:34.722
intelligence , as well as other federal

01:08:34.722 --> 01:08:36.611
partners outside of our immediate

01:08:36.611 --> 01:08:38.722
customer set . Really what that gives

01:08:38.722 --> 01:08:40.944
us the opportunity is to learn from the

01:08:40.944 --> 01:08:43.111
ideas of others . Their best practices

01:08:43.111 --> 01:08:45.222
and areas where they've succeeded are

01:08:45.222 --> 01:08:47.333
also fail and integrate that into our

01:08:47.333 --> 01:08:49.444
plan forward for how we make the best

01:08:49.444 --> 01:08:51.611
use of technology within the C and D .

01:08:51.611 --> 01:08:53.556
Dous is the premier conference for

01:08:53.556 --> 01:08:55.611
networking and for understanding new

01:08:55.611 --> 01:08:57.167
and emerging technology and

01:08:57.167 --> 01:08:59.389
capabilities . It's a great opportunity

01:08:59.389 --> 01:09:01.556
to see where the community is headed .

01:09:01.556 --> 01:09:03.611
You will leave here smarter than you

01:09:03.611 --> 01:09:05.833
arrived and with a slightly larger moex

01:09:05.833 --> 01:09:08.167
your network is there for , you need it ,

01:09:08.167 --> 01:09:10.222
whether it's crisis , whether it's a

01:09:10.222 --> 01:09:12.444
unique challenge that you haven't faced

01:09:12.444 --> 01:09:14.500
before , you can always rely on your

01:09:14.500 --> 01:09:16.500
network . And this has just been an

01:09:16.500 --> 01:09:18.667
amazing opportunity for the the agency

01:09:18.667 --> 01:09:20.833
to have better relationships with many

01:09:20.833 --> 01:09:22.944
of our private sector partners and IC

01:09:22.944 --> 01:09:24.667
partners as well . Stratcom is

01:09:24.667 --> 01:09:26.589
committed to taking charge and

01:09:26.600 --> 01:09:29.120
integrating it superiority into our

01:09:29.129 --> 01:09:30.296
deterrent strategy .

01:09:33.359 --> 01:09:35.500
What I was most looking forward to in

01:09:35.509 --> 01:09:37.410
this year's do conference was the

01:09:37.419 --> 01:09:40.169
plenary sessions . There's no way that

01:09:40.180 --> 01:09:42.899
we would be able to do what we do from

01:09:42.910 --> 01:09:45.629
AJ X perspective without the support of

01:09:45.640 --> 01:09:48.950
our service components and the IC

01:09:48.959 --> 01:09:51.709
community , General Anthony Cotton ,

01:09:51.720 --> 01:09:53.720
who was the United States strategic

01:09:53.720 --> 01:09:56.189
Commander . He's our four star general

01:09:56.200 --> 01:09:58.589
to grace our stage . And I was so

01:09:58.600 --> 01:10:00.544
thrilled to hear from him , the US

01:10:00.544 --> 01:10:02.322
nuclear command and control and

01:10:02.322 --> 01:10:04.489
communication system known as NC three

01:10:04.489 --> 01:10:06.711
is essential to the president's ability

01:10:06.711 --> 01:10:08.933
for command and control of the nation's

01:10:08.933 --> 01:10:09.910
nuclear forces .

01:10:12.799 --> 01:10:14.720
Everything we do is enabled by

01:10:14.729 --> 01:10:17.959
technology um and normally and when

01:10:17.970 --> 01:10:20.799
it's done properly , it's transparent

01:10:20.810 --> 01:10:23.299
to the user . It's seamlessly operating

01:10:23.310 --> 01:10:25.859
in the background . I'm very , very ,

01:10:25.870 --> 01:10:29.290
very interested in how we move the

01:10:29.299 --> 01:10:31.430
needle towards progress on . Uh

01:10:31.439 --> 01:10:33.810
ensuring that it is accessible across

01:10:33.819 --> 01:10:36.379
the board to all of our offices . We

01:10:36.390 --> 01:10:40.109
are continually looking for additional

01:10:40.120 --> 01:10:43.390
partnerships in industry to shore up

01:10:43.399 --> 01:10:47.100
our IT systems , our network for JW , a

01:10:47.109 --> 01:10:49.430
great example of dia s efforts is the

01:10:49.524 --> 01:10:51.468
ongoing development of the machine

01:10:51.468 --> 01:10:54.104
assisted analytical rapid repository or

01:10:54.115 --> 01:10:56.064
Mars program of record . These are

01:10:56.075 --> 01:10:57.797
going to be critical in how we

01:10:57.797 --> 01:11:00.834
implement our zero trust architecture

01:11:00.845 --> 01:11:03.654
as we move forward in securing our data

01:11:03.665 --> 01:11:06.625
on J zero trust is much more than a

01:11:06.634 --> 01:11:10.084
buzzword . It is a foundational change

01:11:10.095 --> 01:11:12.151
to the way that we operate our cyber

01:11:12.151 --> 01:11:14.384
security program . Data needs to be

01:11:14.395 --> 01:11:16.544
readily available at the speed of

01:11:16.555 --> 01:11:18.629
decisions within the Department of

01:11:18.640 --> 01:11:20.759
Defense . We need to transform into a

01:11:20.770 --> 01:11:24.419
data centric and A I enabled guarantor

01:11:24.430 --> 01:11:26.129
of strategic deterrence .

01:11:30.700 --> 01:11:33.720
The future for Dia and the IC is very

01:11:33.729 --> 01:11:36.229
challenging . Our adversaries in the

01:11:36.240 --> 01:11:38.839
nation state threat actors are

01:11:38.850 --> 01:11:41.072
increasing their capabilities and their

01:11:41.072 --> 01:11:43.120
speed at which they are operating

01:11:43.209 --> 01:11:45.660
conferences such as this that help us

01:11:45.819 --> 01:11:47.979
identify those partnerships , those

01:11:47.990 --> 01:11:49.990
force multipliers that will help us

01:11:49.990 --> 01:11:52.419
succeed in that mission . I see us as a

01:11:52.430 --> 01:11:55.669
leader , a leader in advancing it

01:11:55.680 --> 01:11:58.629
technologies . I think our role will be

01:11:58.640 --> 01:12:01.669
Trailblazer , the future for Dia within

01:12:01.680 --> 01:12:05.680
the IC . and Dod is us as the premier

01:12:05.689 --> 01:12:08.649
TSSC I service provider . Dia S role is

01:12:08.660 --> 01:12:10.827
the foundational military intelligence

01:12:10.827 --> 01:12:12.938
provider will put us front and center

01:12:12.938 --> 01:12:14.771
within both the Dod and the IC .

01:12:14.771 --> 01:12:16.438
Today's environment calls for

01:12:16.438 --> 01:12:18.493
leveraging the best practices of all

01:12:18.493 --> 01:12:20.549
agencies and together using the best

01:12:20.549 --> 01:12:22.604
practices that we have in leveraging

01:12:22.604 --> 01:12:22.265
each other's capabilities . We're

01:12:22.274 --> 01:12:24.274
creating one system for the broader

01:12:24.274 --> 01:12:26.385
community to meet our mission needs .

01:12:26.385 --> 01:12:28.441
The agency is leading edge , the men

01:12:28.441 --> 01:12:30.496
and women are talented and committed

01:12:30.496 --> 01:12:32.718
and dedicated to the mission . Dia will

01:12:32.718 --> 01:12:34.718
continue to be a leader and will be

01:12:34.718 --> 01:12:36.885
driving future capabilities across the

01:12:36.885 --> 01:12:38.552
Department of Defense and the

01:12:38.552 --> 01:12:40.774
intelligence community . It's not until

01:12:40.774 --> 01:12:42.552
you get together that you truly

01:12:42.552 --> 01:12:44.552
appreciate the breadth and depth of

01:12:44.552 --> 01:12:46.552
what everyone is working on and how

01:12:46.552 --> 01:12:46.390
that may apply to every one of our

01:12:46.399 --> 01:12:47.970
missions across the defense

01:12:47.979 --> 01:12:49.270
Intelligence agency .

01:12:53.140 --> 01:12:54.140
All right ,

01:12:59.799 --> 01:13:01.966
again , thank you everyone for joining

01:13:01.966 --> 01:13:04.021
us . It's been a fantastic week . We

01:13:04.021 --> 01:13:06.243
wish you a happy Halloween safe travels

01:13:06.243 --> 01:13:08.243
home and we will see you again next

01:13:08.243 --> 01:13:08.890
year . Thank you .