WEBVTT

00:00.483 --> 00:03.150
(feet thudding)

00:04.837 --> 00:07.254
- [Drill Sargent] Halt, halt.

00:09.630 --> 00:10.713
Present arms.

00:14.891 --> 00:19.340
♪ Oh, say can you see ♪

00:19.340 --> 00:23.127
♪ By the dawn's early light ♪

00:23.127 --> 00:27.312
♪ What so proudly we hailed ♪

00:27.312 --> 00:30.852
♪ At the twilight's last gleaming ♪

00:30.852 --> 00:34.675
♪ Whose broad stripes and bright stars ♪

00:34.675 --> 00:38.579
♪ Through the perilous fight, ♪

00:38.579 --> 00:42.606
♪ O'er the ramparts we watched ♪

00:42.606 --> 00:46.281
♪ Were so gallantly streaming ♪

00:46.281 --> 00:50.154
♪ And the rocket's red glare, ♪

00:50.154 --> 00:53.928
♪ The bombs bursting in air, ♪

00:53.928 --> 00:57.643
♪ Gave proof through the night ♪

00:57.643 --> 01:01.404
♪ That our flag was still there. ♪

01:01.404 --> 01:06.404
♪ Oh, say does that
star-spangled banner yet wave ♪

01:10.156 --> 01:15.156
♪ O'er the land of the free ♪

01:15.331 --> 01:18.998
♪ And the home of the brave ♪

01:22.962 --> 01:25.379
- [Drill Sargent] Order arms.

01:28.963 --> 01:31.657
Company, quarter turn, march.

01:32.547 --> 01:35.214
(feet thudding)

01:53.520 --> 01:55.170
- Good morning, please be seated.

01:59.830 --> 02:03.540
Hi, everyone, welcome to Tampa.

02:03.540 --> 02:05.450
My name is Elissa Wykoff,

02:05.450 --> 02:07.920
I am senior vice-president
National Conference Services.

02:07.920 --> 02:10.773
Yes, I am the one sending
you all the emails.

02:11.630 --> 02:13.410
It's nice to see that you all read them,

02:13.410 --> 02:16.030
and you were here promptly
at 8:45 this morning,

02:16.030 --> 02:18.062
so thank you very much.

02:18.062 --> 02:19.968
(audience claps)

02:19.968 --> 02:22.618
(laughs) Yes, you get a
round of applause for that.

02:22.618 --> 02:24.960
I have a few administrative
announcements to make,

02:24.960 --> 02:28.120
and then we're gonna get the
program rolling this morning.

02:28.120 --> 02:30.660
First off, there is a slight change

02:30.660 --> 02:33.160
to a breakout session for this afternoon,

02:33.160 --> 02:36.620
the Insider Threat session in room 21

02:36.620 --> 02:39.580
that was marked Government
Only on the app,

02:39.580 --> 02:41.810
and on the addendum, and
on the program guide,

02:41.810 --> 02:43.610
is now open to all attendees.

02:43.610 --> 02:46.590
So if you really wanted
to go to that session

02:46.590 --> 02:48.300
and originally were not permitted to,

02:48.300 --> 02:49.850
you may now go to that session.

02:51.650 --> 02:54.053
In addition, just a few reminders,

02:54.970 --> 02:56.900
the mobile app is available to download

02:56.900 --> 02:58.080
if you have an iPhone.

02:58.080 --> 03:00.630
Sorry if you have an Android,

03:00.630 --> 03:02.240
hopefully, the work-around

03:02.240 --> 03:04.240
I sent you all last
night has been working.

03:04.240 --> 03:06.670
You're gonna get a web-based
version of the app,

03:06.670 --> 03:08.420
you're still gonna get
the same information,

03:08.420 --> 03:10.730
you should be able to
see the notifications.

03:10.730 --> 03:11.880
We're working with Guidebook

03:11.880 --> 03:15.430
to hopefully get the
app back up and running

03:15.430 --> 03:16.560
on the Google Play Store,

03:16.560 --> 03:18.690
so I do apologize for any inconvenience,

03:18.690 --> 03:20.530
but hopefully the work-around is good,

03:20.530 --> 03:23.100
and you can also access the app.

03:23.100 --> 03:26.310
The app is gonna be your
most up-to-date version

03:26.310 --> 03:29.280
of the agenda, we are also
keeping the NCSI web site,

03:29.280 --> 03:30.700
the DoDIIS web site up-to-date,

03:30.700 --> 03:32.230
so you can check either place.

03:32.230 --> 03:34.610
And you all should have
received an addendum

03:34.610 --> 03:36.745
at registration, there's
been a lot of changes

03:36.745 --> 03:39.480
thanks to some of the things in the news,

03:39.480 --> 03:42.730
so please double-check
the addendum and the app,

03:42.730 --> 03:44.970
before going, choosing what
sessions you want to attend

03:44.970 --> 03:47.110
for the rest of the week.

03:47.110 --> 03:49.843
In addition, there is
a social this evening

03:49.843 --> 03:52.090
you were all told about at registration.

03:52.090 --> 03:55.250
The All-Hands on Deck Networking Social.

03:55.250 --> 03:57.480
Please be sure to bring your ticket

03:57.480 --> 03:58.980
that you received at registration,

03:58.980 --> 04:01.460
that is your entry into the social.

04:01.460 --> 04:04.120
It's at American Social,
right across the bridge,

04:04.120 --> 04:05.230
over by the Weston,

04:05.230 --> 04:07.530
and we hope to see you
all there this evening.

04:08.620 --> 04:10.750
Finally, please make
sure to take some time

04:10.750 --> 04:11.920
to go to the Exhibit Hall,

04:11.920 --> 04:14.227
we have well over 200 companies up there,

04:14.227 --> 04:17.100
our largest Exhibit Hall since 2012,

04:17.100 --> 04:18.610
so please take some time to go up there

04:18.610 --> 04:19.940
and visit with the vendors,

04:19.940 --> 04:22.090
check out their cool
tech, spend some time,

04:22.090 --> 04:23.870
we've allotted a lot of time on the agenda

04:23.870 --> 04:25.570
for you to be able to do that.

04:25.570 --> 04:27.114
If at any time you have any questions,

04:27.114 --> 04:28.950
you guys can always find me.

04:28.950 --> 04:30.300
Go to the registration desk,

04:30.300 --> 04:31.550
we're all here to help.

04:31.550 --> 04:34.100
So thank you very much and
have a great conference.

04:39.251 --> 04:42.001
(dramatic music)

05:12.497 --> 05:14.997
(tense music)

05:28.125 --> 05:29.340
(rocket blasting)

05:29.340 --> 05:31.083
- Our nation is at a crossroads.

05:32.300 --> 05:34.610
The threats we face, evolving.

05:34.610 --> 05:37.433
The competitive military
advantage we've had, eroding.

05:41.070 --> 05:43.070
The operational environment has shifted.

05:45.139 --> 05:46.050
And the ability to develop

05:46.050 --> 05:48.063
asymmetric capabilities is paramount.

05:49.080 --> 05:50.463
The technology that we provide will be

05:50.463 --> 05:52.813
the lethality we need on the battlefield.

05:54.120 --> 05:55.910
The world is continuously changing,

05:55.910 --> 05:57.400
and the global competition we face

05:57.400 --> 05:59.190
is quickly maturing.

05:59.190 --> 06:01.620
We must meet our asymmetric
challenges head on,

06:01.620 --> 06:03.720
with increased speed to mission.

06:03.720 --> 06:07.220
By being resilient in the face
of current, evolving threats,

06:07.220 --> 06:09.940
being redundant in our ability
to continue the mission

06:09.940 --> 06:11.650
in any operating environment,

06:11.650 --> 06:12.770
and above all,

06:12.770 --> 06:15.233
by securing our assets
from malicious intrusions.

06:16.090 --> 06:17.720
We cannot rely on the status quo,

06:17.720 --> 06:19.460
we must respond.

06:19.460 --> 06:21.720
The arena of warfare has changed.

06:21.720 --> 06:24.033
It's shifted from terrestrial to cyber.

06:26.710 --> 06:29.120
It's time for us to create new advantages,

06:29.120 --> 06:30.660
to utilize every innovation,

06:30.660 --> 06:32.930
and drive technological supremacy.

06:32.930 --> 06:35.160
Whether that be through
Big Data analytics,

06:35.160 --> 06:37.690
artificial intelligence, or robotics,

06:37.690 --> 06:39.813
to engage in current and future conflicts.

06:40.770 --> 06:42.230
America is a target.

06:42.230 --> 06:43.988
Whether through terrorists

06:43.988 --> 06:45.560
seeking to attack our way of life,

06:45.560 --> 06:48.140
or vicious cyber-activity
against our infrastructure,

06:48.140 --> 06:49.983
or political information subversion.

06:50.870 --> 06:52.440
We must initiate a response

06:52.440 --> 06:54.690
and execute against the
challenges presented.

06:55.720 --> 06:57.180
We cannot do this alone.

06:57.180 --> 06:59.900
We must stand shoulder to
shoulder with our allied partners

06:59.900 --> 07:00.733
and vendor community,

07:00.733 --> 07:03.020
in order to protect our way of life.

07:03.020 --> 07:04.660
The threats we face are universal

07:04.660 --> 07:07.150
and the landscape is constantly shifting.

07:07.150 --> 07:09.870
Yet, together we can
do something about it.

07:09.870 --> 07:12.480
We must be resilient,
committed, and focused

07:12.480 --> 07:14.030
on every potential opportunity.

07:15.040 --> 07:16.540
This is our advantage.

07:16.540 --> 07:19.160
To meet these challenges,
respond to the threats,

07:19.160 --> 07:21.310
shield and protect
against our adversaries.

07:22.230 --> 07:23.460
This is why we're here.

07:24.628 --> 07:27.378
(dramatic music)

07:32.142 --> 07:32.975
Ladies and gentlemen,

07:32.975 --> 07:35.323
welcome to the 2019 DoDIIS
Worldwide Conference.

07:39.930 --> 07:40.910
- [Announcer] Ladies and gentlemen,

07:40.910 --> 07:42.350
please welcome to the stage

07:42.350 --> 07:43.890
the Chief Information Officer

07:43.890 --> 07:47.847
of the Defense Intelligence
Agency, Mr. Jack Gumtow.

07:49.037 --> 07:52.287
(audience applauding)

07:56.230 --> 07:59.170
- Good morning, just real quick,

07:59.170 --> 08:01.550
yesterday, when I saw this video,

08:01.550 --> 08:04.320
and we were running
through the preps on that,

08:04.320 --> 08:05.607
I was pretty impressed with that,

08:05.607 --> 08:08.540
and more so impressed because usually,

08:08.540 --> 08:10.300
NCSI generates that for us,

08:10.300 --> 08:11.760
this year we did it in-house,

08:11.760 --> 08:14.281
they did a phenomenal job, so thank you.

08:14.281 --> 08:17.448
(audience applauding)

08:18.940 --> 08:21.490
So once again, good morning,
and welcome to Tampa

08:21.490 --> 08:25.410
for the start of the 2019
DoDIIS Worldwide Conference.

08:25.410 --> 08:28.570
For those who don't yet
know me, I'm Jack Gumtow,

08:28.570 --> 08:30.273
I'm the DIA/CIO.

08:31.410 --> 08:35.850
This conference, it marks
my second as the CIO,

08:35.850 --> 08:37.660
and it's a tremendous honor

08:37.660 --> 08:39.410
that I get to host this conference,

08:39.410 --> 08:41.570
which is the largest IT conference

08:41.570 --> 08:43.057
in the intel community.

08:44.414 --> 08:46.540
I want to thank the city of Tampa,

08:46.540 --> 08:48.330
the Tampa Convention Center,

08:48.330 --> 08:51.820
and the Tampa Bay Police
Department for their support.

08:51.820 --> 08:54.410
I can't overstate how important it is

08:54.410 --> 08:56.140
to have these kind of partners

08:56.140 --> 08:59.533
when we organize an
event of this magnitude.

09:00.988 --> 09:03.810
I also want to express my
appreciation to my boss,

09:03.810 --> 09:06.293
DIA Director, Lieutenant
General Bob Ashley,

09:08.040 --> 09:09.930
for his continued support.

09:09.930 --> 09:12.250
So in that support,

09:12.250 --> 09:14.360
it stems from a deep understanding

09:14.360 --> 09:17.960
of the valued proposition
that this conference provides,

09:17.960 --> 09:21.490
both to DIA, and to you as our partners.

09:21.490 --> 09:22.363
Sir, thank you.

09:26.007 --> 09:29.050
I also want to express
my sincere appreciation

09:29.050 --> 09:31.550
to Miss Katelyn Ostrowski,

09:31.550 --> 09:33.810
and the Eastlake High School
Performing Arts Academy

09:33.810 --> 09:35.560
for this morning's National Anthem.

09:37.026 --> 09:37.870
(audience applauding)
I think she's gone,

09:37.870 --> 09:38.870
but yeah, thank you.

09:44.370 --> 09:45.903
As a high school student,

09:47.730 --> 09:50.100
as an individual, she
did a phenomenal job,

09:50.100 --> 09:51.960
let alone she's in high school,

09:51.960 --> 09:53.440
standing in front of this crowd,

09:53.440 --> 09:57.840
bringing me to that this is
our second largest conference

09:57.840 --> 10:01.470
in 14 or 16 years, and as of this morning

10:01.470 --> 10:04.174
we had about 3,700 people in attendance,

10:04.174 --> 10:06.453
so it's fairly large.

10:07.720 --> 10:09.250
So let me give you a little background

10:09.250 --> 10:10.490
in what we have in store for you

10:10.490 --> 10:11.853
over the next few days.

10:12.960 --> 10:15.790
We have an agenda that
offers distinguished line-up

10:15.790 --> 10:17.960
of military and government experts,

10:17.960 --> 10:20.060
and industry leaders to provide insights

10:20.060 --> 10:21.883
on a variety of relevant topics.

10:22.820 --> 10:25.760
Our goal is to generate conversations,

10:25.760 --> 10:28.040
surrounding the collective set of issues

10:28.040 --> 10:30.100
that we are facing as we continue

10:30.100 --> 10:33.390
our digital journey and
our digital evolution.

10:33.390 --> 10:35.250
I have no doubt our
speakers will bring a wealth

10:35.250 --> 10:37.150
of knowledge and experience

10:37.150 --> 10:39.313
which will create a rewarding three days.

10:41.590 --> 10:43.900
This brings me to this
years conference theme,

10:43.900 --> 10:47.230
resiliency, redundancy, and security,

10:47.230 --> 10:50.020
adapting to asymmetric threats.

10:50.020 --> 10:53.333
Everything is digitally connected.

10:54.370 --> 10:57.700
And everything is
vulnerable and exploitable.

10:57.700 --> 10:59.260
And at the same time,

10:59.260 --> 11:01.363
it offers us numerous opportunities.

11:03.090 --> 11:07.620
Collectively, we must be
prepared to rapidly adapt

11:07.620 --> 11:09.510
to the demands of the changing strategic

11:09.510 --> 11:11.173
and tactical digital environment.

11:12.170 --> 11:14.500
Over the course of the next three days,

11:14.500 --> 11:18.120
we have a unique opportunity
to network face-to-face,

11:18.120 --> 11:20.483
and access innovative technologies.

11:21.690 --> 11:23.350
To this end,

11:23.350 --> 11:26.020
we have designed a line-up
of breakout sessions

11:26.020 --> 11:28.813
lead by a variety of government
and industry experts.

11:29.730 --> 11:32.870
If you've been to the DoDIIS
conference previously,

11:32.870 --> 11:35.850
you understand that the
intrinsic value of being here

11:35.850 --> 11:38.810
is the ability to capitalize
on the direct engagement

11:38.810 --> 11:40.463
with subject matter experts.

11:41.420 --> 11:43.803
Please take advantage
of these opportunities.

11:45.960 --> 11:47.980
So where is DIA heading?

11:47.980 --> 11:50.370
And how is the DIA/CIO
addressing the goals

11:50.370 --> 11:52.753
of the agency, the IC and DOD?

11:55.100 --> 11:58.750
Within the CIO there's an undeniable need

11:58.750 --> 12:00.800
to enhance our capabilities,

12:00.800 --> 12:03.890
and become an
all-encompassing, data-centric,

12:03.890 --> 12:07.890
information and communications
technology service provider

12:07.890 --> 12:08.993
for our partners.

12:10.450 --> 12:12.430
To achieve this end-state,

12:12.430 --> 12:15.120
we have embarked on a deliver process.

12:15.120 --> 12:18.290
To crystallize our vision, objectives

12:18.290 --> 12:20.590
and the means to achieve
the collective goals

12:20.590 --> 12:22.773
of DIA, the IC, and DOD.

12:24.060 --> 12:25.820
This effort is underway,

12:25.820 --> 12:29.453
and I call it the DIA/CIO Modernization.

12:31.710 --> 12:36.563
To do this, we establish the
CIO vision, it's published.

12:38.280 --> 12:41.560
We follow that with the DIA/CIO strategy,

12:41.560 --> 12:43.963
outlining four goals and 19 objectives.

12:44.990 --> 12:48.070
This document is
published and is available

12:48.070 --> 12:50.050
at the DI booth in the exhibit hall.

12:50.050 --> 12:51.550
It's an unclassified document.

12:53.920 --> 12:55.080
We are close to publishing

12:55.080 --> 12:57.264
an annual DIA/CIO planning guidance,

12:57.264 --> 13:01.390
which outlines where we are
prioritizing our investments,

13:01.390 --> 13:03.020
where we are disinvesting

13:03.020 --> 13:06.570
in order to generate
capacity and resources,

13:06.570 --> 13:08.670
and to achieve the goals
and objectives laid out

13:08.670 --> 13:09.513
in the strategy.

13:12.870 --> 13:15.010
The approach we're
taking allows us to shift

13:15.010 --> 13:17.803
towards being an enabling
mission and business partner,

13:19.290 --> 13:21.320
while focusing on what we do well

13:21.320 --> 13:23.120
and allowing our partners the latitude

13:23.120 --> 13:24.470
to rapidly move forward

13:24.470 --> 13:26.533
using our foundational capabilities.

13:27.530 --> 13:31.330
I don't believe my CIO
organization function unilaterally,

13:31.330 --> 13:33.753
or can own all aspects of the IT staff,

13:34.800 --> 13:37.503
which heretofore, has
been the predominant view.

13:38.900 --> 13:41.760
Rather, we are focusing
on our core strengths

13:41.760 --> 13:45.243
in transport, infrastructure,
and platform services,

13:46.210 --> 13:49.010
while jointly developing
applications with our partners.

13:50.010 --> 13:53.210
It's okay if others build capabilities,

13:53.210 --> 13:54.640
as long as they are building them

13:54.640 --> 13:57.100
on our foundational core we're providing

13:57.100 --> 14:00.440
and use the standards and
guidance we are publishing.

14:00.440 --> 14:02.140
And more on that in just a moment.

14:04.150 --> 14:08.150
At the top of my stack, up on the screen,

14:08.150 --> 14:09.983
are analytics and visualization.

14:11.240 --> 14:13.683
I see that as our
partners' responsibility.

14:14.690 --> 14:16.750
Why is it theirs?

14:16.750 --> 14:18.083
That's a great question.

14:19.490 --> 14:21.740
It's because I don't live in those spaces.

14:21.740 --> 14:24.290
I don't live in those mission spaces.

14:24.290 --> 14:26.080
And when we have attempted

14:26.080 --> 14:27.910
to deliver at that layer,

14:27.910 --> 14:30.140
we end up delivering pizza,

14:30.140 --> 14:32.040
when what they really wanted was beer.

14:32.941 --> 14:34.590
(audience quietly laughing)

14:34.590 --> 14:36.950
We will be there to help,

14:36.950 --> 14:39.320
but what I am doing today
is setting the stage

14:39.320 --> 14:42.363
for our partners to be able to
easily do this on their own.

14:43.990 --> 14:46.350
I've empowered my CTO to stand up

14:46.350 --> 14:47.900
a technical leadership council,

14:47.900 --> 14:49.760
to develop technical standards,

14:49.760 --> 14:53.063
guidance, and strategic
technical direction.

14:54.200 --> 14:56.020
These are routinely published

14:56.020 --> 14:58.453
and made available to
the community at large.

14:59.400 --> 15:01.193
I encourage you to meet with my CTO

15:01.193 --> 15:03.590
to discuss these standards,

15:03.590 --> 15:07.159
as they impact everyone
that interacts with DIA,

15:07.159 --> 15:09.940
the defense intelligence enterprise,

15:09.940 --> 15:11.733
from an IT perspective.

15:13.760 --> 15:15.920
So to achieve the goals I've listed,

15:15.920 --> 15:18.140
and to ensure we meet
mission requirements,

15:18.140 --> 15:19.083
I need your help.

15:20.220 --> 15:21.920
I need increased collaboration

15:21.920 --> 15:24.440
and transparency with our partners.

15:24.440 --> 15:25.480
Paying special attention

15:25.480 --> 15:28.173
to providing foundational
services ahead of demand.

15:29.980 --> 15:32.530
I need proactive collaboration
with our partners

15:32.530 --> 15:34.266
so we can align their requirements

15:34.266 --> 15:36.690
with emergent technologies,

15:36.690 --> 15:38.723
determine our key investment areas,

15:39.710 --> 15:43.533
and as importantly, identify
areas where I can take risk.

15:46.370 --> 15:49.350
We need to enhance and support
our foundational environment

15:49.350 --> 15:52.450
so that our partners can
build and deploy capabilities,

15:52.450 --> 15:56.980
at mission-mandated speeds,
not at bureaucracy speeds,

15:56.980 --> 15:59.370
and provide connectivity to our partners

15:59.370 --> 16:01.620
that's not limited by the constraints

16:01.620 --> 16:03.993
of geography or a desk.

16:06.760 --> 16:08.313
The IACO is changing.

16:09.460 --> 16:12.793
We're focusing on partner
support and partner service.

16:13.850 --> 16:14.823
This is a journey.

16:16.010 --> 16:17.190
We're moving forward

16:17.190 --> 16:19.220
and are actively implementing the tenets

16:19.220 --> 16:20.653
that I've spoken about.

16:21.490 --> 16:24.823
I need you, as my partners
and my colleagues,

16:25.880 --> 16:29.230
to help me and therefore help
our collective communities,

16:29.230 --> 16:30.690
achieve mission success.

16:32.960 --> 16:36.203
At this time, I'm happy
to welcome my boss,

16:37.120 --> 16:41.303
DIA's 21st Director,
Lieutenant General Bob Ashley.

16:42.230 --> 16:43.420
I think you're gonna find

16:43.420 --> 16:46.793
that he is engaging,
grounded and pragmatic.

16:48.010 --> 16:50.790
And if you have an opportunity
to engage him offline,

16:50.790 --> 16:51.820
I think you're gonna discover

16:51.820 --> 16:54.150
that he's a pretty good musician as well.

16:54.150 --> 16:56.416
Sir?
- All right, thank you.

16:56.416 --> 16:59.583
(audience applauding)

17:04.250 --> 17:06.889
Jack, I want pizza and beer.

17:06.889 --> 17:08.936
(audience laughing)

17:08.936 --> 17:10.990
It's not enough just to have one.

17:10.990 --> 17:13.150
Hey, I just wanted to point out also that,

17:13.150 --> 17:15.260
as you saw, those senior
non-commissioned officers

17:15.260 --> 17:18.010
walking the off stage,
Katelyn was in step,

17:18.010 --> 17:19.881
so that was well done.

17:19.881 --> 17:23.048
(audience applauding)

17:24.810 --> 17:27.560
I have this urge to turn
around and see how my hair is.

17:28.910 --> 17:31.520
Nope, doesn't work, it
just shows the bald spot.

17:31.520 --> 17:33.623
Hey, thanks for coming out today.

17:34.480 --> 17:36.007
This is incredibly important,

17:36.007 --> 17:38.640
and excuse me if I cough a little bit,

17:38.640 --> 17:41.580
Saturday morning I landed
back from Afghanistan,

17:41.580 --> 17:44.230
I'm still getting the
dust out of my throat.

17:44.230 --> 17:47.010
I would like to point out that we have the

17:47.010 --> 17:49.410
20th Director of the
Defense Intelligence Agency

17:49.410 --> 17:51.140
sitting in row three,

17:51.140 --> 17:53.710
and you also have a former Sen Comm J2,

17:53.710 --> 17:55.970
and they look incredibly rested

17:55.970 --> 17:57.580
now that they've gone into retirement.

17:57.580 --> 18:00.210
Although I think Vince and Mark are

18:00.210 --> 18:01.820
both staying pretty busy.

18:01.820 --> 18:03.370
Demetri, you look tired, buddy.

18:04.690 --> 18:06.560
Got the Sen Comm J2 in
the front row with us,

18:06.560 --> 18:09.270
and so, I know you have an
incredibly busy schedule,

18:09.270 --> 18:11.570
and thanks for spending time with us.

18:11.570 --> 18:12.420
So thanks for being here.

18:12.420 --> 18:13.380
Thanks for the CIO,

18:13.380 --> 18:14.710
thanks for the Tampa community.

18:14.710 --> 18:17.375
Everybody that brings
this community together,

18:17.375 --> 18:20.930
and we talk about the
challenges we have to face,

18:20.930 --> 18:22.440
and it's kinda good timing,

18:22.440 --> 18:23.450
that even though Saturday morning,

18:23.450 --> 18:26.600
I literally just got off
a plane from Afghanistan

18:26.600 --> 18:28.973
as we started this session,

18:30.350 --> 18:32.850
it was very illustrative
of one of our challenges,

18:34.020 --> 18:35.380
and I'm not a technologist,

18:35.380 --> 18:36.530
but for some reason,

18:36.530 --> 18:40.633
Samsung and Apple don't
talk to one another.

18:42.300 --> 18:43.893
That's a huge issue.

18:44.730 --> 18:45.820
And so one of the things I'd ask you

18:45.820 --> 18:48.930
to think about is the
idea of interoperability,

18:48.930 --> 18:51.520
as we go through the next couple of days.

18:51.520 --> 18:53.710
Because everybody that's
sitting in this audience

18:53.710 --> 18:58.250
that represents a unique
industry capability,

18:58.250 --> 19:00.250
you gotta be able to talk to each other.

19:01.110 --> 19:03.260
You have got to be able
to talk to each other.

19:03.260 --> 19:06.890
So as Jack has laid out,
it's a good time to engage,

19:06.890 --> 19:09.570
meet somebody, don't go with
your normal circle of friends,

19:09.570 --> 19:11.890
expand that out a little bit.

19:11.890 --> 19:14.410
And how do we create new solutions?

19:14.410 --> 19:15.520
You know, in my talking points

19:15.520 --> 19:16.530
we highlighted the fact

19:16.530 --> 19:19.060
that things like Post-it, Super Glue,

19:19.060 --> 19:21.573
and duct tape were not built by design,

19:22.410 --> 19:24.380
they were built by mistake,
they were accidents,

19:24.380 --> 19:28.453
they were opportunities
to leverage a capability,

19:30.200 --> 19:32.840
but that's not where they started.

19:32.840 --> 19:36.420
And so we have to think
about how we innovate,

19:36.420 --> 19:38.970
and I am thoroughly convinced
that there is nobody

19:38.970 --> 19:41.613
that innovates like America.

19:42.980 --> 19:46.550
And I saw that in the field
with our special operators,

19:46.550 --> 19:49.670
with industry, with the guys
teaming with the task force,

19:49.670 --> 19:52.163
when I just left Bagram
a couple of days ago.

19:55.380 --> 20:00.000
Data interoperability, so with
all the unique capabilities,

20:00.000 --> 20:02.320
the designs that you bring

20:02.320 --> 20:04.410
to the Department of Defense,

20:04.410 --> 20:07.293
everything has to talk to everything else,

20:08.800 --> 20:11.920
otherwise, we will be sub-optimized

20:11.920 --> 20:14.280
and we will miss opportunities.

20:14.280 --> 20:16.370
And the opportunities
that are presenting to us

20:16.370 --> 20:18.450
in terms of technology,

20:18.450 --> 20:21.193
many of those are duel-use
and they come with threats.

20:22.260 --> 20:24.760
In some cases, things we
may not have anticipated.

20:27.710 --> 20:29.753
So a little bit of a spoiler this week is,

20:29.753 --> 20:32.120
that Jack said,

20:32.120 --> 20:33.897
It's about redundancy,
it's about resiliency,

20:33.897 --> 20:37.637
"it's about security, it's
about how we move data."

20:40.820 --> 20:42.163
And it is complicated.

20:43.466 --> 20:46.127
And in many ways we can solve problems,

20:46.127 --> 20:48.673
and we can solve problems at speed,

20:51.040 --> 20:53.463
our challenge is to solve
the problem at scale.

20:55.350 --> 20:57.370
I can come up with a unique capability

20:57.370 --> 20:59.350
for a battalion, a brigade,

20:59.350 --> 21:02.860
where they can operate at
speed within that brigade,

21:02.860 --> 21:05.360
but can they talk to every other brigade?

21:05.360 --> 21:07.300
Can they talk to other services?

21:07.300 --> 21:09.253
Can they talk to other nations?

21:11.700 --> 21:14.120
I don't know if we have
as much a speed problem,

21:14.120 --> 21:15.833
as we have a scale problem.

21:16.970 --> 21:18.700
And buried within that scale problem

21:18.700 --> 21:20.550
is the challenge of interoperability,

21:21.760 --> 21:24.200
and data is one of the
fastest-growing industries,

21:24.200 --> 21:27.200
and it has a laser-focus of a couple

21:27.200 --> 21:29.500
of our key competitors,
both China and Russia.

21:30.830 --> 21:32.560
And if you've not seen
the Defense White Paper

21:32.560 --> 21:34.220
that China just published,

21:34.220 --> 21:36.140
I'd actually take a look at that.

21:36.140 --> 21:37.420
They realize the understanding

21:37.420 --> 21:39.840
of their ability to leverage
data is part of what it means

21:39.840 --> 21:40.973
to be a great power.

21:41.960 --> 21:44.660
And Putin has been on
record to say that really,

21:44.660 --> 21:45.680
the people that can leverage

21:45.680 --> 21:47.920
and understand that, will dominate.

21:47.920 --> 21:50.360
And information is how
China plans to dominate

21:50.360 --> 21:52.870
in the future, that is their strategy.

21:52.870 --> 21:57.083
That is their strategy to get
behind decision advantage.

21:58.240 --> 22:00.950
And so just think of all the
information that's out there.

22:00.950 --> 22:04.463
2.5 quintillion bytes of
data created every day.

22:07.830 --> 22:11.463
In a market that's gonna go
over 100 billion by 2022.

22:13.064 --> 22:16.423
And so I think about that in
context and I go back to 1993.

22:17.640 --> 22:20.553
So 1993, Barbara and I are
walking into Circuit City,

22:22.093 --> 22:23.870
(audience laughing)

22:23.870 --> 22:26.253
young captain, two kids,
not a lot of money.

22:28.500 --> 22:31.290
And so we're looking at the Dell computer,

22:31.290 --> 22:32.780
and the debate we're having is whether

22:32.780 --> 22:34.910
we get the four or the
eight meg hard drive,

22:34.910 --> 22:35.950
because I'm not sure

22:35.950 --> 22:38.348
we'll ever fill up the
eight meg hard drive.

22:38.348 --> 22:40.691
(audience laughing)

22:40.691 --> 22:42.591
and that thing was still, like $1,200.

22:44.750 --> 22:46.550
We did go with the 8 meg hard drive.

22:47.860 --> 22:50.600
I can create a single
PowerPoint slide now that has,

22:50.600 --> 22:52.008
that's eight megs.

22:52.008 --> 22:54.570
(audience laughing)

22:54.570 --> 22:56.093
But just think about the technology,

22:56.093 --> 23:00.070
everything that we see,
between smart-houses,

23:00.070 --> 23:03.323
everything that can control your life.

23:04.920 --> 23:08.050
And then look at the
context of a smart city.

23:08.050 --> 23:11.533
A safe city, that China's
building on a global scale.

23:14.390 --> 23:17.930
For what could be, you know, a
safe city, better regulation,

23:17.930 --> 23:19.760
how do you do industrial control systems?

23:19.760 --> 23:21.130
How do you regulate lights?

23:21.130 --> 23:25.000
Infrastructure, industrial systems?

23:25.000 --> 23:27.070
Or smart cities for how
you can tag virtually

23:27.070 --> 23:28.933
everybody that's walking on the street.

23:30.690 --> 23:32.810
And where is that data going,

23:32.810 --> 23:34.060
and who's controlling it?

23:35.150 --> 23:37.670
So it's not just about the
internet of things for consumers,

23:37.670 --> 23:41.530
it's other risks that
lie out there in data,

23:41.530 --> 23:43.760
and our inability to leverage it.

23:43.760 --> 23:47.180
Terrorist networks,
misinformation, deep fakes,

23:47.180 --> 23:50.083
confusion, distrust in institutions.

23:51.380 --> 23:53.350
And then what's our job?

23:53.350 --> 23:54.770
As a combat support agency,

23:54.770 --> 23:56.190
we have to supply the warfighters

23:56.190 --> 24:00.530
with information that is
accurate, and that is trusted,

24:00.530 --> 24:04.903
in an environment where
misinformation exists.

24:05.820 --> 24:07.480
So how do we find that
relevant information?

24:07.480 --> 24:09.870
How do we find accurate information?

24:09.870 --> 24:12.840
And as Neil Wiley says,
it's that secret sauce,

24:12.840 --> 24:15.130
our ability to take publicly
available information

24:15.130 --> 24:18.780
and integrate it with the
pristine collection that we have.

24:18.780 --> 24:23.780
But as Jack alluded to,
we have to do it at speed.

24:24.580 --> 24:26.680
It has to be fast enough to be actionable.

24:30.240 --> 24:33.450
And the policy that underpins the process,

24:33.450 --> 24:37.200
that allows you to integrate
that into our systems,

24:37.200 --> 24:38.710
in so many ways, and I saw this

24:38.710 --> 24:40.300
in Afghanistan over the last week,

24:40.300 --> 24:43.150
are industrial policies
that are not informed

24:43.150 --> 24:45.200
by the requirements of a digital age.

24:45.200 --> 24:47.720
But we're working our way through that.

24:47.720 --> 24:51.330
Challenges of acquisition,
how do we address risk,

24:51.330 --> 24:54.660
as Jack talked about, and
how do we mitigate that risk?

24:54.660 --> 24:56.610
How do we take a commercial application

24:56.610 --> 24:58.490
and integrate it in near realtime,

24:58.490 --> 25:01.490
and update it without having to go through

25:01.490 --> 25:06.490
this laborious process to
bring it on our networks.

25:09.420 --> 25:10.930
So if you ask me my vision,

25:10.930 --> 25:13.964
to kind of complement what
Jack has already talked about,

25:13.964 --> 25:17.890
it's the workforce, it's
highly-professional individuals,

25:17.890 --> 25:19.290
it's leading-edge technology,

25:19.290 --> 25:20.850
and how we discover information,

25:20.850 --> 25:22.900
how we create knowledge,

25:22.900 --> 25:24.480
how we provide warning

25:25.850 --> 25:27.150
and identify opportunities,

25:27.150 --> 25:30.150
so that we can overwhelmingly
have an advantage

25:30.150 --> 25:31.807
over our adversaries for our warfighters

25:31.807 --> 25:33.363
and our policy makers.

25:34.600 --> 25:36.900
And there's a lot of
things in that to unpack.

25:41.090 --> 25:43.180
So it means an analyst that
can work through large data,

25:43.180 --> 25:44.660
can see connections in minutes

25:44.660 --> 25:48.380
that used to take us hours to days.

25:48.380 --> 25:50.630
It means leveraging
constantly emerging tools,

25:50.630 --> 25:51.760
and this is part of what we saw

25:51.760 --> 25:53.010
with the task force in theater,

25:53.010 --> 25:56.520
the ability to leverage tools in realtime

25:56.520 --> 25:59.680
that are being built, and
bring them into the network.

25:59.680 --> 26:01.420
And to be able to take that data,

26:01.420 --> 26:03.480
with a degree of trust
and risk-mitigation,

26:03.480 --> 26:06.740
and move it from
unclassified to a collateral,

26:06.740 --> 26:10.500
to a TS, to enrich that analysis,

26:10.500 --> 26:13.700
extract insights and
then move it back down,

26:13.700 --> 26:16.000
because your ability to
share with a partner,

26:16.000 --> 26:19.620
a coalition partner, may
not be on a classified,

26:19.620 --> 26:21.780
but it has to be on a secure network.

26:21.780 --> 26:23.480
Those are challenges that we have.

26:25.310 --> 26:26.640
When you design this technology,

26:26.640 --> 26:30.390
and I saw some of this over
the week, the past week,

26:30.390 --> 26:32.550
I would ask you to take
the words proprietary

26:32.550 --> 26:34.500
and NOFORN out of your lexicon.

26:34.500 --> 26:35.603
We cannot do that.

26:36.780 --> 26:39.220
We have got to be able to share

26:39.220 --> 26:40.053
with our allies and partners.

26:40.053 --> 26:41.900
If you go back to
national defense strategy,

26:41.900 --> 26:43.040
that is a line of effort, too.

26:43.040 --> 26:45.330
It is allies and partners.

26:45.330 --> 26:46.500
The door is open for us

26:46.500 --> 26:49.223
to push hard on our ability to share.

26:50.270 --> 26:53.083
Let me give you a good example
that dates back to 1941.

26:56.140 --> 26:59.050
So there's two navy and two army officers

26:59.050 --> 27:01.550
that work cryptology,
and they jump on a ship

27:01.550 --> 27:03.000
and they're headed to the UK.

27:04.210 --> 27:06.500
They have solved Purple.

27:06.500 --> 27:09.020
They have solved the Japanese
diplomatic communications,

27:09.020 --> 27:09.853
they have broken it.

27:09.853 --> 27:12.190
It is something the Brits
have been working on.

27:13.200 --> 27:14.583
So they arrive.

27:17.060 --> 27:18.610
The Brits have broken Enigma.

27:18.610 --> 27:20.740
They've broken the German communications,

27:20.740 --> 27:22.180
but Churchill's given them guidance

27:22.180 --> 27:24.230
that you will not share that information.

27:25.490 --> 27:26.900
But the U.S. comes forward and says,

27:26.900 --> 27:27.910
hey, we've broken Purple,

27:27.910 --> 27:29.260
I know you guys have been working on it,

27:29.260 --> 27:30.360
this is how it worked.

27:32.553 --> 27:33.386
And the guy that's the head

27:33.386 --> 27:36.700
of the Secret Intelligence Service,

27:36.700 --> 27:39.490
Stewart Menzies, which if
you're a James Bond fan,

27:39.490 --> 27:41.193
you would recognize him as M,

27:42.300 --> 27:44.360
although his moniker is actually C,

27:44.360 --> 27:45.783
which stands for Chief.

27:46.770 --> 27:48.730
So they have the conversation,

27:48.730 --> 27:51.340
the Americans say we've broken Purple,

27:51.340 --> 27:54.737
Menzies sends a note
to Churchill and says,

27:54.737 --> 27:56.900
"Can we share Enigma?"

27:56.900 --> 27:58.100
Churchill says, "Do it."

27:59.790 --> 28:04.790
It should not take an act of
war, or the Prime Minister,

28:05.760 --> 28:08.460
to get the authority to
share that information.

28:08.460 --> 28:10.220
What was the outcome?

28:10.220 --> 28:11.880
It was estimated that our understanding

28:11.880 --> 28:14.520
of both Purple and Enigma codes

28:14.520 --> 28:17.033
probably shortened the war by two years.

28:19.100 --> 28:20.723
But we have to do that now.

28:21.650 --> 28:23.010
That's the framework and mindset

28:23.010 --> 28:25.730
that we've gotta take
for our senior leaders,

28:25.730 --> 28:27.220
our decision makers,

28:27.220 --> 28:30.313
is why are you waiting for
the first shot to be fired?

28:32.199 --> 28:34.300
And we can start building those insights.

28:34.300 --> 28:38.460
And those insights, not just
about, during a conflict,

28:38.460 --> 28:40.283
it's about deterring a conflict.

28:43.590 --> 28:47.330
So for our focus, there's
three key areas to talk about.

28:47.330 --> 28:49.033
Open-source intelligence,

28:50.260 --> 28:53.510
our Machine-Assisted Analytic
Rapid-Repository System,

28:53.510 --> 28:56.170
or MARS, which I think that
everybody's heard about.

28:56.170 --> 28:57.110
And obviously,

28:57.110 --> 29:00.420
the flagship communications
program we have JWICS.

29:00.420 --> 29:01.700
And it's very important that

29:01.700 --> 29:03.550
when we talk about
open-source intelligence,

29:03.550 --> 29:06.500
we set that aside from
publicly available information.

29:06.500 --> 29:11.210
That is an outcome of PAI,

29:11.210 --> 29:12.380
because if you're a logistician,

29:12.380 --> 29:13.870
you want publicly available information,

29:13.870 --> 29:15.080
and if you are a planner,

29:15.080 --> 29:17.533
if you're in admin, you name it.

29:19.400 --> 29:21.580
And for too long I think we've conflated

29:21.580 --> 29:23.490
the two of those together.

29:23.490 --> 29:24.830
And for us in the OSIN forum,

29:24.830 --> 29:26.240
it means we've got to
be able to understand

29:26.240 --> 29:27.903
how to collect and process that.

29:28.898 --> 29:30.590
And so we made the decision this year

29:31.880 --> 29:33.260
that is a additive curve field

29:33.260 --> 29:35.050
that we're gonna build at DIA.

29:35.050 --> 29:37.140
To understand how to collect
and process that information,

29:37.140 --> 29:38.950
because we've kinda
made it a pick-up game,

29:38.950 --> 29:42.600
more ad hoc, for other specialties
over the last few years,

29:42.600 --> 29:44.050
and we can no longer do that.

29:45.440 --> 29:47.560
As far as large complex data sets,

29:47.560 --> 29:50.620
DIA's been doing that
for a couple of decades.

29:50.620 --> 29:52.430
But they're not all in the same place.

29:52.430 --> 29:54.263
They do not all talk to one another,

29:55.350 --> 29:56.600
and we've gotta fix that.

29:57.874 --> 30:00.663
We gotta figure out how we
aggregate information together.

30:01.660 --> 30:06.660
And it gets back to the core
of why this agency exists,

30:06.690 --> 30:09.000
is to provide foundational intelligence

30:09.000 --> 30:12.163
on foreign militaries, and
the operational environment.

30:13.410 --> 30:15.720
And since it is football season,

30:15.720 --> 30:20.720
my rough analogy is this
is the scouting report

30:20.750 --> 30:22.250
on the team you're gonna play.

30:23.450 --> 30:27.240
And we update the scouting
report every single day.

30:27.240 --> 30:28.073
And not only that,

30:28.073 --> 30:29.560
we're gonna tell you the
good restaurants to go,

30:29.560 --> 30:30.810
where to avoid traffic,

30:30.810 --> 30:33.260
as we tell you about the
operational environment.

30:35.900 --> 30:37.720
Best way to describe it is a vision

30:37.720 --> 30:40.000
as we create the best that we can

30:40.000 --> 30:44.620
to replicate a virtual
model of our adversaries

30:46.626 --> 30:47.663
and our competitors.

30:49.680 --> 30:54.540
And MARS is our attempt to
start building that baseline.

30:54.540 --> 30:56.430
It is not MIDB,

30:56.430 --> 30:58.480
it is not the Modern Integrated Data Base,

30:58.480 --> 31:01.250
it is an information environment.

31:01.250 --> 31:04.773
It is dynamic and we cannot
build it without you.

31:09.930 --> 31:11.480
So think about the Arab Spring.

31:13.654 --> 31:15.167
And this is kinda where Big Data comes in,

31:15.167 --> 31:18.490
and what was taking place in
the northern tiers of Africa.

31:18.490 --> 31:19.980
The communication that was taking place,

31:19.980 --> 31:23.170
the revolutionary
conversations, the protests,

31:23.170 --> 31:26.023
everything was evolving, the conditions,

31:26.870 --> 31:29.150
and the IC saw those conditions,

31:29.150 --> 31:30.850
but from an indications
warning standpoint,

31:30.850 --> 31:33.593
we didn't necessarily see the when.

31:34.790 --> 31:36.513
When this was gonna all kick off.

31:38.020 --> 31:38.890
And when I think about that,

31:38.890 --> 31:41.000
I think about conversations
I've had with senior leaders

31:41.000 --> 31:46.000
about August of 1914,
"The Guns of August."

31:47.190 --> 31:50.780
If we had MARS, if we had
Big Data, if we had AI, NO,

31:50.780 --> 31:52.990
and everything that we had now,

31:52.990 --> 31:55.020
would we have walked into World War I?

31:58.668 --> 32:00.153
It's a question I can't answer.

32:03.370 --> 32:06.623
But imagine, as the
Arab Spring kicked off,

32:07.470 --> 32:08.870
if you were the Sen Comm J2.

32:10.490 --> 32:12.193
What was possible to know?

32:13.220 --> 32:15.603
What insights might you have had,

32:16.540 --> 32:21.540
to see what was about to evolve,

32:22.020 --> 32:23.910
that was sparked by Mohamed Bouazizi,

32:23.910 --> 32:25.210
the Tunisian vegetable vendor

32:25.210 --> 32:27.763
that engaged in an act of self-immolation?

32:31.550 --> 32:32.893
And I ask that question,

32:34.300 --> 32:36.350
because when the Arab Spring unfolded,

32:36.350 --> 32:37.973
I was that Sen Comm J2.

32:42.970 --> 32:45.180
But with all the data, all
the stuff that comes out,

32:45.180 --> 32:46.580
there is also a big piece of this

32:46.580 --> 32:49.930
that speaks to traditional
analysis and good tradecraft,

32:49.930 --> 32:51.217
because you can't just say,

32:51.217 --> 32:53.307
"The box told me the following."

32:54.190 --> 32:57.077
And so we're already
working our way though that,

32:57.077 --> 32:59.730
and building analytic data teams,

32:59.730 --> 33:01.920
where we take a tool developer,

33:01.920 --> 33:04.500
a methodologist, an all-source analyst,

33:04.500 --> 33:07.710
and a data scientist, and
we kluge them together

33:09.300 --> 33:11.140
to look at how we deal with information,

33:11.140 --> 33:14.690
and then we train those
algorithms with good tradecraft,

33:14.690 --> 33:16.550
where I can tell you we
have a high probability,

33:16.550 --> 33:18.690
because of the way I've
trained that algorithm,

33:18.690 --> 33:22.573
that what I am telling you is accurate.

33:25.440 --> 33:27.960
And then the last piece is JWICS,

33:27.960 --> 33:30.140
our flagship for how we communicate,

33:30.140 --> 33:32.077
and we have to do this,
and it has to be resilient,

33:32.077 --> 33:35.360
and it has to be redundant,
and it has to be secure.

33:35.360 --> 33:36.480
More importantly, it's gonna have

33:36.480 --> 33:38.270
to increase in capacity,

33:38.270 --> 33:41.510
we're gonna have to make
sure that we get the funding,

33:41.510 --> 33:43.753
that it stays cutting-edge,

33:45.160 --> 33:46.950
and that we're able to
have high-speed links

33:46.950 --> 33:48.180
to deal with the volume

33:48.180 --> 33:50.330
of information that's
coming in the future.

33:52.120 --> 33:53.400
And even as we talk about JWICS

33:53.400 --> 33:54.760
so there's secure communications,

33:54.760 --> 33:59.180
we think about quantum.

33:59.180 --> 34:00.870
Quantum encryption,
quantum communications,

34:00.870 --> 34:02.830
and are we going toward a point where,

34:02.830 --> 34:04.020
not only is it JWICS,

34:04.020 --> 34:06.880
but it's we're leveraging
commercial networks

34:06.880 --> 34:09.490
in realtime to be able to communicate

34:09.490 --> 34:12.450
with partners globally,
where those networks

34:12.450 --> 34:15.363
that the Defense Department
builds do not exist.

34:17.450 --> 34:20.867
So that's the kind of innovation
we have to think about.

34:20.867 --> 34:21.880
And think about the chairman's intent

34:21.880 --> 34:23.700
for global integration.

34:23.700 --> 34:26.790
And we have combatant
commands represented here.

34:26.790 --> 34:29.323
That goes back to my scale issue,

34:31.580 --> 34:33.840
because the tyranny of
combatant command boundaries

34:33.840 --> 34:36.570
will not bound our adversaries,

34:36.570 --> 34:39.163
our competitors, in
great power competition.

34:40.620 --> 34:41.970
And so we have to think about how

34:41.970 --> 34:44.530
we are interoperable
across combatant commands,

34:44.530 --> 34:48.590
across the J2s in our core functions,

34:48.590 --> 34:50.850
and how we do foundational,
how we do targeting,

34:50.850 --> 34:52.650
how we do collection management,

34:52.650 --> 34:56.560
how we bring in intel mission
data to feed that F-35.

34:56.560 --> 34:59.250
How we do acquisition,
and most importantly,

34:59.250 --> 35:01.143
across combatant commands,

35:02.000 --> 35:03.800
how do I do indications and warning?

35:04.680 --> 35:05.940
How to optimize that,

35:05.940 --> 35:09.540
because if I'm not interoperable
with data and understanding

35:09.540 --> 35:12.353
and tools that speak to one another,

35:13.330 --> 35:16.593
I will be sub-optimized,
and I will miss something.

35:17.770 --> 35:19.970
And that's how we get
to decision authority.

35:21.690 --> 35:24.050
And as you saw the quote from Eisenhower,

35:24.050 --> 35:28.750
to share another comment from Neil Wiley,

35:28.750 --> 35:32.900
where he says, "Our job
is to support Plan A."

35:32.900 --> 35:34.253
Plan A is diplomacy.

35:37.210 --> 35:38.160
But if Plan A fails,

35:38.160 --> 35:39.850
we gotta be ready to execute Plan B.

35:39.850 --> 35:42.380
And in great power competition,

35:42.380 --> 35:44.580
you gotta bring your A game on day one,

35:44.580 --> 35:47.373
because if you don't, you
may not get a day two.

35:48.390 --> 35:49.430
So we gotta be postured

35:49.430 --> 35:52.900
to provide unparalleled support
to those decision makers,

35:52.900 --> 35:55.260
and as Jack talked about,
it's not just data.

35:55.260 --> 35:58.420
It's visualization, it's
artificial intelligence,

35:58.420 --> 36:01.810
it's computer vision,
it's machine learning.

36:01.810 --> 36:05.599
And those capabilities
will evolve over time,

36:05.599 --> 36:07.680
and our competitors and
adversaries are dedicating

36:07.680 --> 36:10.340
a great deal of time
and effort to do that.

36:10.340 --> 36:11.670
So rather than have a conversation

36:11.670 --> 36:13.990
about who's ahead or who's behind,

36:13.990 --> 36:16.350
in the next decade
everybody's gonna have it.

36:16.350 --> 36:18.500
So how are you gonna
operate in that space.

36:19.630 --> 36:21.227
Another quote from President
Eisenhower, he said,

36:21.227 --> 36:23.890
"The only way to win World
War III is to prevent it."

36:23.890 --> 36:27.600
Which for us is how do
we create that knowledge,

36:27.600 --> 36:29.320
how do we create situation understanding,

36:29.320 --> 36:33.090
and how do we create decision
advantage for our leaders?

36:33.090 --> 36:36.560
Because while they're working
on warfighting concepts,

36:36.560 --> 36:39.193
their expectation is we
are solving these problems.

36:41.540 --> 36:44.380
So let me close with one
last quote from Churchill,

36:44.380 --> 36:46.690
and I think it's illustrative of a phrase

36:46.690 --> 36:47.690
that everybody already says,

36:47.690 --> 36:50.570
that, you know, if you
go back to Clausewitz

36:50.570 --> 36:53.000
and the fog and friction of war,

36:53.000 --> 36:56.450
where no good plan ever
survives first contact.

36:56.450 --> 36:58.040
And the reason this is so important,

36:58.040 --> 37:00.917
I think it's illustrative
of what Churchill said was,

37:00.917 --> 37:02.547
"Never, never, never believe

37:02.547 --> 37:05.497
"any war will be smooth and easy,

37:05.497 --> 37:09.017
"or that anyone who embarks
on this strange voyage

37:09.017 --> 37:13.303
"can measure the tides and
hurricanes you will encounter.

37:14.737 --> 37:17.537
"The statesman who yields
to war fever must realize

37:17.537 --> 37:19.467
"that once the signal is given,

37:19.467 --> 37:21.667
"he is no longer the master of policy,

37:21.667 --> 37:23.637
"but the slave of a unforeseeable

37:23.637 --> 37:26.280
"and uncontrollable events."

37:26.280 --> 37:28.223
That is the fog and friction of war.

37:30.100 --> 37:34.123
That is miscalculation, that
is unknowable red lines.

37:35.850 --> 37:37.800
So our goal is that unforeseeable

37:37.800 --> 37:40.350
and uncontrollable dynamics,

37:40.350 --> 37:43.723
that fog and friction will
never be completely eliminated.

37:45.010 --> 37:46.710
But we have a chance to reduce it,

37:48.443 --> 37:49.276
and we have a chance to reduce it

37:49.276 --> 37:50.350
by what we will discuss

37:50.350 --> 37:52.750
over the course of the next few days.

37:52.750 --> 37:54.560
And so I look for your engagement,

37:54.560 --> 37:56.660
I thank you for your support.

37:56.660 --> 37:59.600
We have significant issues
we gotta work through,

37:59.600 --> 38:01.753
because even as we speak right now,

38:03.050 --> 38:05.210
there are Soldiers,
Sailors, Airmen, Marines,

38:05.210 --> 38:09.780
Coast Guardsmen, and civilians
that are in harms way,

38:09.780 --> 38:12.990
and they are operating
in a sub-optimized way

38:12.990 --> 38:15.933
because there are problems
that we need to solve.

38:18.294 --> 38:20.470
And with that, I thank you

38:21.422 --> 38:23.961
and I look forward to your questions.

38:23.961 --> 38:27.128
(audience applauding)

38:30.036 --> 38:30.869
Was that all right?

38:30.869 --> 38:33.452
- Yeah, that was great, thanks.

38:35.210 --> 38:38.700
All right, so last year we
took a different approach

38:38.700 --> 38:40.300
to this conference opening session,

38:40.300 --> 38:42.047
and rather than me standing up

38:42.047 --> 38:44.120
and speaking for 30 minutes or so,

38:44.120 --> 38:45.150
and the general standing up here

38:45.150 --> 38:47.130
and speaking for 30 minutes or so,

38:47.130 --> 38:49.033
we did what we just did,

38:49.033 --> 38:51.710
and then went into a town hall.

38:51.710 --> 38:55.020
This was, I thought, it was well-received,

38:55.020 --> 38:56.790
based on the feedback we saw,

38:56.790 --> 38:59.140
and so we're gonna continue
it again this year.

39:02.780 --> 39:05.736
The point here is to, how
do we do from a town hall,

39:05.736 --> 39:08.390
address the pressing
questions that you have,

39:08.390 --> 39:10.580
rather than just telling
you what we think,

39:10.580 --> 39:12.570
and many cases on the town hall

39:12.570 --> 39:14.340
it's much better to hear from the audience

39:14.340 --> 39:15.820
what is it that's on your mind,

39:15.820 --> 39:17.320
and then let us to address it.

39:18.200 --> 39:20.220
So that's what we're gonna do.

39:20.220 --> 39:22.960
First thing I'm going to do is,

39:22.960 --> 39:26.060
I want to make an introduction
of this year's emcee,

39:26.060 --> 39:30.600
and who the individual that'll
be facilitating this session,

39:30.600 --> 39:31.433
there it is.

39:32.630 --> 39:34.003
This is Sumo Doug,

39:35.170 --> 39:39.330
but really this is my
deputy CIO, Doug Cossa,

39:39.330 --> 39:42.446
and Doug, thank you.

39:42.446 --> 39:45.613
(audience applauding)

39:50.682 --> 39:52.260
- Thank you, sir.
- Right, should be on.

39:52.260 --> 39:56.973
- Yes, Jack, thank you for
that flattering introduction,

39:58.160 --> 39:59.360
what you guys don't know about Jack,

39:59.360 --> 40:00.910
is that he tends to live in the moment,

40:00.910 --> 40:03.420
and has forgotten that I'm
about to start a Q&A session

40:03.420 --> 40:04.720
with him and the director.

40:06.530 --> 40:08.430
And to shed a little
light on the director,

40:08.430 --> 40:11.020
he, for those of you who have briefed him,

40:11.020 --> 40:13.780
asked some pretty touch questions.

40:13.780 --> 40:16.560
Questions, to where you really
need access to Wikipedia

40:16.560 --> 40:18.630
right in front of you to answer.

40:18.630 --> 40:21.390
So when I was asked to moderate

40:21.390 --> 40:24.260
this question and answer
panel with the two of them,

40:24.260 --> 40:27.850
I enthusiastically said, absolutely.

40:27.850 --> 40:31.463
So, we're gonna get started
with one simple question,

40:32.440 --> 40:35.550
two trains are leaving the
station at 45 miles an hour.

40:35.550 --> 40:37.360
No, just kidding, we're
not gonna start there.

40:37.360 --> 40:39.180
Actually, as Jack said,
we're gonna take questions

40:39.180 --> 40:40.970
from you guys, the audience.

40:40.970 --> 40:45.830
You can email your questions
to askdodiis@gmail.com,

40:45.830 --> 40:47.170
and I'll read them up here,

40:47.170 --> 40:49.250
hopefully that will go
smoothly, I know it will,

40:49.250 --> 40:53.610
and the director and Jack
will answer accordingly.

40:53.610 --> 40:54.443
But I'd like to start off

40:54.443 --> 40:56.070
with the first question that we have,

40:56.070 --> 40:57.860
this is for General Ashley.

40:57.860 --> 41:00.230
You have been leading DIA
for nearly two years now,

41:00.230 --> 41:02.510
can you talk about the
role that technology plays

41:02.510 --> 41:04.200
as part of the agencies mission?

41:04.200 --> 41:05.520
- All right, thanks Doug.

41:05.520 --> 41:07.570
You guys hear me, we're on?

41:07.570 --> 41:10.180
So that's really what I gave
you in the last 30 minutes

41:10.180 --> 41:12.530
in the role of technology and so the,

41:12.530 --> 41:14.670
and we did interview, I
think about a month ago,

41:14.670 --> 41:16.960
and one of the ways I qualified MARS,

41:16.960 --> 41:18.343
is that's our moon shot.

41:19.390 --> 41:21.830
And we've got to be able
to leverage information,

41:21.830 --> 41:23.360
it's not just really in the analytic side,

41:23.360 --> 41:24.400
it's everything we do.

41:24.400 --> 41:26.040
It's every commodity area we have,

41:26.040 --> 41:28.094
whether it's administrative back officers

41:28.094 --> 41:31.260
but really that flagship capability is

41:31.260 --> 41:34.660
how we take information at speed and scale

41:34.660 --> 41:38.840
and then allow analysts to think,

41:38.840 --> 41:40.280
to work their way through problems.

41:40.280 --> 41:42.600
So that they're not doing
these repetitive things,

41:42.600 --> 41:45.450
they're not engaged in laborious research,

41:45.450 --> 41:46.670
that the information comes to them,

41:46.670 --> 41:47.680
we're able to visualize it

41:47.680 --> 41:49.280
and present it in such a way

41:49.280 --> 41:50.740
that they can see those relationships,

41:50.740 --> 41:55.740
in many cases it would not
necessarily be evident to them,

41:56.320 --> 41:59.230
and then they can start
working at solving problems

41:59.230 --> 42:01.970
and engaging in dialog
with senior leaders,

42:01.970 --> 42:04.480
and having a much more robust conversation

42:04.480 --> 42:05.950
about the problem at hand,

42:05.950 --> 42:08.420
as opposed to figuring
out how the mechanics

42:08.420 --> 42:10.333
of just doing basic research.

42:11.740 --> 42:14.340
- [Doug] So Jack, we heard
about the director speak

42:14.340 --> 42:17.080
of the importance of technology
to support DIA's mission.

42:17.080 --> 42:18.990
Can you discuss some
of the emerging trends

42:18.990 --> 42:19.890
that we're seeing?

42:21.360 --> 42:24.830
- Okay, let me address
it from this vantage,

42:24.830 --> 42:28.350
and I want to talk from
General Ashley's speech

42:28.350 --> 42:29.800
that he talked about.

42:29.800 --> 42:31.110
And the reality is,

42:31.110 --> 42:34.600
we can have technological
advancements across the board,

42:34.600 --> 42:37.450
but the underpinning
of this is about data.

42:37.450 --> 42:42.450
So without data, you have a set of tools,

42:42.870 --> 42:45.600
that I'm not sure what the
real value proposition is.

42:45.600 --> 42:50.340
So data is the common denominator
that we must get straight.

42:50.340 --> 42:51.740
We're not there yet.

42:51.740 --> 42:55.020
Data is hard, it comes in at speed,

42:55.020 --> 42:56.883
at the volume, the veracity.

42:58.970 --> 43:00.350
We're working on it.

43:00.350 --> 43:01.610
We're all working on that,

43:01.610 --> 43:04.490
but we don't quite have
that fully harnessed yet.

43:04.490 --> 43:05.890
But then when you go up that layer,

43:05.890 --> 43:07.580
there's a number of technical advances,

43:07.580 --> 43:09.530
so AIML, we all hear about it,

43:09.530 --> 43:11.430
I personally think that's on,

43:11.430 --> 43:14.890
still on the hype curve
of we haven't quiet gotten

43:14.890 --> 43:17.893
to the valley of disillusionment yet.

43:19.440 --> 43:22.710
But I don't see AI, it's a few years out

43:22.710 --> 43:24.700
to what we actually think AI is,

43:24.700 --> 43:27.880
narrow AI is certainly available.

43:27.880 --> 43:30.540
It's things that are underpinning MARS,

43:30.540 --> 43:33.990
it's other technical
tools that we've done,

43:33.990 --> 43:36.480
including Redline and GOSU,

43:36.480 --> 43:40.570
that allow us to look at
large volumes of data,

43:40.570 --> 43:43.570
and discern those patterns in
there so that the analysts,

43:43.570 --> 43:45.520
instead of looking at the entire haystack,

43:45.520 --> 43:48.280
is looking at the small pitchfork of hay

43:48.280 --> 43:49.790
that's available to them,

43:49.790 --> 43:53.660
and make assessments,
automated assessments,

43:53.660 --> 43:55.210
that allows to move this mission forward.

43:55.210 --> 43:57.060
So there's things coming,

43:57.060 --> 44:01.240
but I don't want to dismiss
or minimize the point

44:01.240 --> 44:04.070
that the data is really key here.

44:04.070 --> 44:06.380
- Which gets back to Cloud infrastructure,

44:06.380 --> 44:10.640
and so let me put in a plug for Mr. Deasy,

44:10.640 --> 44:12.340
the CIO at the Defense Department.

44:14.148 --> 44:15.200
Thing like JEDI.

44:15.200 --> 44:17.560
You know, that data, that interoperability

44:17.560 --> 44:19.260
to be able to move information,

44:19.260 --> 44:21.240
and to be able to discover information,

44:21.240 --> 44:22.610
we've gotta have a Cloud architecture

44:22.610 --> 44:23.820
that allows us to do that.

44:23.820 --> 44:26.130
And again, not a technologist,

44:26.130 --> 44:27.770
but the way he kinda described it

44:27.770 --> 44:29.410
in a conversation I had with him,

44:29.410 --> 44:32.150
is, you know, 'cause I just
assumed he had this big

44:32.150 --> 44:33.517
uber Cloud, or is it multiple Clouds,

44:33.517 --> 44:36.110
and it is actually multiple Clouds.

44:36.110 --> 44:38.220
But the way he described
it is that you have Clouds

44:38.220 --> 44:41.960
that are application
aware, which is to say,

44:41.960 --> 44:44.490
if I have a question on a topic,

44:44.490 --> 44:47.870
I don't need to send it to
six different locations,

44:47.870 --> 44:49.400
I just need to send it once,

44:49.400 --> 44:51.410
because the Clouds are application aware,

44:51.410 --> 44:54.890
and it goes across the
Clouds to aggregate that data

44:54.890 --> 44:56.283
and bring my response back,

44:57.180 --> 44:59.293
and that is incredibly powerful.

45:02.180 --> 45:04.260
- [Doug] So we're having a few
questions come in right now,

45:04.260 --> 45:06.900
as a reminder, askdodiis@gmail.com.

45:06.900 --> 45:08.900
So one of those first
questions that we have,

45:08.900 --> 45:10.240
and this is for General Ashley.

45:10.240 --> 45:12.400
Will DIA place priority and focus

45:12.400 --> 45:13.860
on having other machine learning

45:13.860 --> 45:17.630
and artificial intelligence
initiatives in addition to MARS?

45:17.630 --> 45:20.193
- So MARS is an overarching environment.

45:22.190 --> 45:24.310
It will have, and again Jack said,

45:24.310 --> 45:26.500
as not-quite-there fully-machine learning,

45:26.500 --> 45:29.040
there will be multiple
machine learning applications

45:29.040 --> 45:31.300
that will be able to ride on the data

45:32.170 --> 45:33.860
that MARS will ingest.

45:33.860 --> 45:37.300
So think of an app store
that has a multitude

45:37.300 --> 45:39.590
of different kinds of machine
learning applications,

45:39.590 --> 45:41.990
they can be applied
against the data we have.

45:41.990 --> 45:43.680
So it's not any one ML,

45:43.680 --> 45:45.240
it's not any one computer vision,

45:45.240 --> 45:47.320
or any one AI tool,

45:47.320 --> 45:50.560
what we want to be able
to do is build a framework

45:50.560 --> 45:53.370
that has access to the information,

45:53.370 --> 45:55.830
and then we're looking for industry

45:55.830 --> 45:58.320
to be able to come in and innovate

45:58.320 --> 46:01.250
to how we are able to
understand that data.

46:01.250 --> 46:04.010
And it goes back to what
we talked about briefly,

46:04.010 --> 46:05.970
with the analytic data teams,

46:05.970 --> 46:06.830
and we have those looking

46:06.830 --> 46:08.140
at a couple different problem sets.

46:08.140 --> 46:09.930
We're having them look at
a problem set for China,

46:09.930 --> 46:13.210
We're having them look at a
problem set for Iran and Russia.

46:13.210 --> 46:16.300
But it's taking the data

46:16.300 --> 46:19.100
and applying multiple tools against it,

46:19.100 --> 46:21.700
multiple machine learning,
multiple computer vision.

46:24.630 --> 46:26.610
You have to look at the
problem you're trying to solve

46:26.610 --> 46:28.840
then you have a menu of options

46:28.840 --> 46:30.420
for how you can solve that.

46:30.420 --> 46:32.830
And the ADTs gives us the opportunity

46:32.830 --> 46:33.880
for the analysts to go,

46:33.880 --> 46:36.210
I really need to be able to do this,

46:36.210 --> 46:37.640
and then you have the tool developer,

46:37.640 --> 46:38.473
or the software developer,

46:38.473 --> 46:39.760
and the data scientist goes,

46:39.760 --> 46:41.020
okay, I think I can write a script

46:41.020 --> 46:42.850
to manipulate the information.

46:42.850 --> 46:46.100
So when you go out and
you buy a Microsoft Word,

46:46.100 --> 46:49.580
you get what's ever on
Microsoft Word until

46:49.580 --> 46:52.110
the good people at Apple
decide, or Microsoft decide

46:52.110 --> 46:54.070
they're gonna update that again.

46:54.070 --> 46:56.413
What we want to be able to do is,

46:57.550 --> 47:00.580
what if you could manipulate
the functionality in Word

47:00.580 --> 47:03.580
in realtime, to do different things?

47:03.580 --> 47:05.303
And that's what gotta be able to do.

47:06.630 --> 47:07.890
- [Doug] Thank you.

47:07.890 --> 47:08.980
So this one's for you, Jack.

47:08.980 --> 47:11.490
Another question from the audience here.

47:11.490 --> 47:14.430
When someone says DoDIIS
desktop of the future,

47:14.430 --> 47:15.480
what do you think of?

47:18.130 --> 47:19.430
- I'm gonna use a term

47:19.430 --> 47:24.083
from my fellow colleague, Ellison Howard,

47:25.040 --> 47:26.860
who's sitting up here in
the front shaking his head,

47:26.860 --> 47:31.160
but and what we talked about
is that single pane of glass.

47:31.160 --> 47:34.443
And I talked to you this
morning about that as well.

47:36.640 --> 47:38.420
And General Parker is coming

47:38.420 --> 47:40.290
from the National Guard Bureau,

47:40.290 --> 47:42.640
and he had come from STRATCOM,

47:42.640 --> 47:44.480
and had been on COE,

47:44.480 --> 47:46.789
our current desktop environment,

47:46.789 --> 47:48.197
I said, "Man, I love COE,

47:48.197 --> 47:50.467
"but being at National Guard Bureau,

47:50.467 --> 47:52.437
"it is very hard to communicate,

47:52.437 --> 47:53.947
"and or operate with others

47:53.947 --> 47:56.500
"because of the way the architecture is."

47:56.500 --> 47:59.300
So you shouldn't have
multiple panes to go from,

47:59.300 --> 48:01.470
hey, I gotta do something on this machine,

48:01.470 --> 48:03.940
and then go over to this
machine to do something else,

48:03.940 --> 48:05.930
or even have to go in and say,

48:05.930 --> 48:09.030
I gotta go point my
application at this data set,

48:09.030 --> 48:11.438
or this repository to get that,

48:11.438 --> 48:13.350
it should that single pane of glass,

48:13.350 --> 48:15.840
that I go in and I have
full interoperability

48:15.840 --> 48:17.840
across our partner community.

48:17.840 --> 48:19.140
And when I say partner community,

48:19.140 --> 48:21.940
I don't just mean the defense
intelligence enterprise,

48:21.940 --> 48:25.290
I mean everybody that
operates within those domains,

48:25.290 --> 48:27.110
whatever those domains happen to be,

48:27.110 --> 48:30.350
inclusive of our foreign partners.

48:30.350 --> 48:32.900
That's what I see as the desktop,

48:32.900 --> 48:35.457
I don't want to call it the
DoDIIS desktop of the future,

48:35.457 --> 48:37.860
but it needs to be that
interoperability set

48:37.860 --> 48:42.210
that we all can operate,
interoperability at speed.

48:42.210 --> 48:43.910
You shouldn't even think about it.

48:45.544 --> 48:46.560
- [Doug] Thank you.

48:46.560 --> 48:47.920
General Ashley, for you.

48:47.920 --> 48:50.170
What confidence do you need machines to,

48:50.170 --> 48:51.800
given their data analytics,

48:51.800 --> 48:54.890
so that humans, analysts,
can accept the results?

48:54.890 --> 48:56.497
- So I kind of alluded to that before,

48:56.497 --> 48:58.960
in one of the programs we have is,

48:58.960 --> 49:00.830
you have to have a high
degree of confidence,

49:00.830 --> 49:03.720
well, you need to establish
a confidence level.

49:03.720 --> 49:06.220
And so in this case, we've
been able to do some work

49:06.220 --> 49:08.210
where we have a high level of confidence

49:08.210 --> 49:10.550
that we can characterize
a particular theme

49:10.550 --> 49:13.260
that is happening because the
algorithm has been trained

49:13.260 --> 49:14.690
in such a way.

49:14.690 --> 49:17.010
And so there's nine
attributes of tradecraft,

49:17.010 --> 49:19.070
and whether you're working
in the digital world

49:19.070 --> 49:20.423
or the human world,

49:21.970 --> 49:25.170
we cannot walk away from those,

49:25.170 --> 49:28.870
the rigor of tradecraft as we
look at how we bring in data.

49:28.870 --> 49:30.463
And so part of training the algorithm

49:30.463 --> 49:33.450
is that you either have a
low/medium confidence level

49:33.450 --> 49:37.940
that what you've assessed
is, in fact, valid.

49:37.940 --> 49:39.390
And we've got to be able to provide

49:39.390 --> 49:42.120
that kind of assessment
still to decision makers.

49:42.120 --> 49:42.953
You can't just say,

49:42.953 --> 49:45.010
the box spit out the following response,

49:45.010 --> 49:46.540
you gotta tell them what's
the level of confidence,

49:46.540 --> 49:50.750
because built into that
algorithm is training,

49:50.750 --> 49:52.580
and background that underpins

49:52.580 --> 49:54.680
how it came up with that determination,

49:54.680 --> 49:56.870
and so we've got to be able
to tell our senior leaders

49:56.870 --> 50:00.270
how we came about with that assessment.

50:00.270 --> 50:02.120
I think it will get better over time,

50:03.440 --> 50:05.610
but it's also gonna get
more complicated over time,

50:05.610 --> 50:07.870
as we look at misinformation,

50:07.870 --> 50:09.590
deception and things like that.

50:09.590 --> 50:12.830
I had a conversation with General Kevin

50:12.830 --> 50:13.663
several years ago,

50:13.663 --> 50:14.570
and somebody made the comment,

50:14.570 --> 50:17.640
you know, it's gonna be
so easy to deceive people

50:17.640 --> 50:18.960
with deep fakes and everything else.

50:18.960 --> 50:21.307
And he goes, "Yeah but you look
at the other aspect of that

50:21.307 --> 50:23.457
"where people post things on social media,

50:23.457 --> 50:27.747
"you have so much truth that
is actually gonna come out

50:27.747 --> 50:29.887
"to contravert some of the deep fakes

50:29.887 --> 50:31.520
"and other information like that."

50:31.520 --> 50:36.520
But for us, the real advantage is the fact

50:37.000 --> 50:37.833
that we're gonna layer

50:37.833 --> 50:39.290
not only public available information,

50:39.290 --> 50:41.230
but we're gonna take
that pristine collection,

50:41.230 --> 50:43.500
so it really is about,
not a single source,

50:43.500 --> 50:45.380
it is about multiple sources,

50:45.380 --> 50:47.450
and tradecraft that we apply in analytics

50:47.450 --> 50:49.620
that is underpinning what
we've done for decades,

50:49.620 --> 50:50.900
and that's how we'll go forward.

50:50.900 --> 50:54.800
It's just we will start enabling
a digital aspect of that

50:54.800 --> 50:56.213
to work its scale and speed.

50:57.970 --> 50:59.420
- [Doug] So this next
question we've received

50:59.420 --> 51:01.740
from the audience deals with workforce

51:01.740 --> 51:02.750
and the challenges we have,

51:02.750 --> 51:05.000
and are both strategic
challenges and priorities

51:05.000 --> 51:09.710
that we have in our agency
strategic plan, as well as CIOs.

51:09.710 --> 51:10.810
So the question is,

51:10.810 --> 51:13.050
what do you consider are
the biggest challenges

51:13.050 --> 51:15.850
and opportunities to acquiring
and retaining our talent?

51:17.820 --> 51:20.900
- So we're re-looking training right now.

51:20.900 --> 51:24.560
Janice Glover-Jones, who is
Jack's predecessor at RCIO,

51:25.650 --> 51:28.202
spent a year with--
- Dell.

51:28.202 --> 51:31.113
- Dell, and what she did is,

51:31.113 --> 51:33.870
project she was looking
at bias in the workspace,

51:33.870 --> 51:35.180
she was looking at all
kinds of different projects,

51:35.180 --> 51:36.960
she came back in about a month

51:36.960 --> 51:39.157
before she finished her
year sabbatical and said,

51:39.157 --> 51:42.297
"Hey, I want you to read
this article about AT&T,

51:42.297 --> 51:44.617
"and it really is about how
do you re-skill the workforce

51:44.617 --> 51:47.280
"to be able to operate
in today's environment?"

51:47.280 --> 51:52.280
And for us, it is taking
those digital attributes,

51:52.990 --> 51:54.950
those capabilities and training,

51:54.950 --> 51:57.240
and injecting that into the
workforce they have right now.

51:57.240 --> 52:02.240
So we're in the midst of
Janice helping us scale that

52:02.260 --> 52:04.060
and the task where I've given to everybody

52:04.060 --> 52:06.160
that owns their career field,

52:06.160 --> 52:09.880
is to look at skills and
attributes in the digital world,

52:09.880 --> 52:11.490
what you need to sustain,

52:11.490 --> 52:13.980
and where there are gaps
that we need to build toward.

52:13.980 --> 52:15.330
Because everything that
we're talking about,

52:15.330 --> 52:20.030
I can't say tell me about
the analysts of 2025 or 2030,

52:20.030 --> 52:23.430
because really that
skill-set is needed now.

52:23.430 --> 52:25.770
And so we're going through
all the career fields

52:25.770 --> 52:29.590
and looking at what Big
Data, data analytics,

52:29.590 --> 52:32.530
all of that means to every
one of those career fields,

52:32.530 --> 52:34.710
so Janice is helping work that with,

52:34.710 --> 52:37.590
and we're actually looking at recruiting

52:37.590 --> 52:39.750
across the combat support agencies.

52:39.750 --> 52:42.730
Bob Sharp is the National
Geospatial Agency director,

52:42.730 --> 52:44.040
had a great idea a couple months ago,

52:44.040 --> 52:45.117
he goes, "We ought to really get

52:45.117 --> 52:46.997
"all of the organizations together

52:46.997 --> 52:49.627
"and talk about training, recruiting,

52:49.627 --> 52:53.350
"promotions, every
aspect of human capital."

52:53.350 --> 52:58.130
And so our Chiefs of Staff,
over the course of the last,

52:58.130 --> 53:02.020
probably 60, 70 days, had been meeting

53:02.020 --> 53:03.940
to look at those exact issues.

53:03.940 --> 53:06.650
And, you know, part of it
is retention of talent,

53:06.650 --> 53:09.420
you're not gonna get rich
working for the government,

53:09.420 --> 53:12.463
but where we can, how do we incentivize,

53:13.700 --> 53:15.360
whether it's financial
or other opportunities

53:15.360 --> 53:16.960
for credentialing to be able

53:16.960 --> 53:19.370
to keep some of that talent on board,

53:19.370 --> 53:21.530
the one thing is to present
them with the unique challenges

53:21.530 --> 53:24.887
that they will not necessarily
find in other places,

53:24.887 --> 53:27.160
to be able to solve some hard problems,

53:27.160 --> 53:29.423
for the government and
for national security.

53:31.440 --> 53:33.450
- And even, sir, even if my,

53:33.450 --> 53:36.900
Jack's view as your Career
Field Manager for IT,

53:36.900 --> 53:39.740
even if we lose those people
after a period of time,

53:39.740 --> 53:40.900
I don't see it as a bad thing,

53:40.900 --> 53:43.510
as because of that rotation into industry,

53:43.510 --> 53:45.150
into another agency,

53:45.150 --> 53:47.190
and they're still supporting
the overall mission.

53:47.190 --> 53:50.070
And so a lot of people
still had this mindset,

53:50.070 --> 53:52.290
and I have it in the workforce,

53:52.290 --> 53:54.330
that of like oh, I
gotta bring somebody in,

53:54.330 --> 53:56.205
and it's gonna be for a 30 year career.

53:56.205 --> 54:00.450
With the new entrees into the workforce,

54:00.450 --> 54:02.830
that is not, their mindset is differently,

54:02.830 --> 54:04.870
and it's okay, I'm okay with that.

54:04.870 --> 54:07.220
Because they're contributing,
they're moving on,

54:07.220 --> 54:08.810
and they're still contributing

54:08.810 --> 54:10.210
as they go through their career,

54:10.210 --> 54:11.420
and I think it's,

54:11.420 --> 54:12.670
I think we're doing a pretty good job

54:12.670 --> 54:14.410
of starting to address some of that.

54:14.410 --> 54:15.650
- Yeah, and I agree with Jack,

54:15.650 --> 54:18.430
it's, you know, there's
not a massive exodus,

54:18.430 --> 54:19.610
and for those that do leave,

54:19.610 --> 54:22.090
they take an understanding of our needs,

54:22.090 --> 54:23.160
and they take those to industry

54:23.160 --> 54:24.380
to help us solve those problems.

54:24.380 --> 54:26.550
So the other thing is,
thinking about the models,

54:26.550 --> 54:28.550
and Cyber's a good example of this,

54:28.550 --> 54:31.240
where Cyber's been able to bring people in

54:31.240 --> 54:33.090
at a higher grade-level,

54:33.090 --> 54:35.050
come in laterally to organizations,

54:35.050 --> 54:37.260
or to take a sabbatical
and bring 'em back,

54:37.260 --> 54:38.980
or you work in industry
for a couple of years,

54:38.980 --> 54:39.813
and you come back in.

54:39.813 --> 54:42.470
So the traditional model, and I agree,

54:42.470 --> 54:46.120
of the okay, you're locked
in for the next 30 years,

54:46.120 --> 54:48.870
is really not what this
generation's looking for.

54:48.870 --> 54:50.840
And so we've got to adapt,

54:50.840 --> 54:53.190
those of us that are not digital natives,

54:53.190 --> 54:57.160
to be able to think creatively
about career opportunities,

54:57.160 --> 55:01.180
and not be risk-averse to bringing people

55:01.180 --> 55:04.323
in and out of the IC.

55:06.290 --> 55:08.670
- [Doug] So this question
was pointed to the director,

55:08.670 --> 55:10.710
but Jack, I think this applies to a number

55:10.710 --> 55:12.440
of our efforts in CIO as well.

55:12.440 --> 55:15.440
So during our conversations
with allies abroad,

55:15.440 --> 55:17.030
how much importance would you place

55:17.030 --> 55:19.770
on advancing our
technological capabilities?

55:19.770 --> 55:20.710
- Great question.

55:20.710 --> 55:22.260
- Yeah, so let me jump on that one first,

55:22.260 --> 55:25.060
'cause one of the things we're
doing right now is with MARS.

55:25.060 --> 55:26.720
And so we have John Howard,

55:26.720 --> 55:29.480
who's our Deputy Director
for Commonwealth Integration

55:29.480 --> 55:30.430
from New Zealand.

55:30.430 --> 55:32.090
And John is an absolute zealot,

55:32.090 --> 55:34.250
there's nothing better than having someone

55:34.250 --> 55:36.870
with a different uniform go into an office

55:36.870 --> 55:38.620
with a bunch of U.S. people and go,

55:38.620 --> 55:40.530
and shame them for not sharing.

55:40.530 --> 55:42.810
Which goes back to my comments of

55:42.810 --> 55:45.670
why are we waiting for the
first shot to be fired?

55:45.670 --> 55:47.190
This is about building muscle-memory,

55:47.190 --> 55:49.420
and having situational understanding

55:49.420 --> 55:51.420
and deterrents before we go to conflict.

55:52.910 --> 55:54.360
So when I was just in Afghanistan,

55:54.360 --> 55:57.060
there was a particular capability

55:57.060 --> 55:58.500
that the task force was working on,

55:58.500 --> 56:01.470
and it's great, but there's some hiccups

56:01.470 --> 56:02.303
that they're working on,

56:02.303 --> 56:03.530
and oh, by the way, it's a NOFORN.

56:04.640 --> 56:08.120
So there is already an
impediment to that start.

56:08.120 --> 56:09.480
So as we think about MARS,

56:09.480 --> 56:11.650
what we've done with some
of our closest partners,

56:11.650 --> 56:13.600
and John's a big part of this,

56:13.600 --> 56:17.110
is I said, well I can't send
you the PowerPoint slides,

56:17.110 --> 56:18.470
or talk to you about it,

56:18.470 --> 56:21.700
I need to bring you in
at the engineering level.

56:21.700 --> 56:24.390
And so as we look at the basic tenets

56:24.390 --> 56:25.700
and the foundation of MARS,

56:25.700 --> 56:28.090
to some of our, you
know, closest partners,

56:28.090 --> 56:29.150
what we've done is we've said

56:29.150 --> 56:30.630
this is how this is gonna operate,

56:30.630 --> 56:33.570
what do you have in
your infrastructure now,

56:33.570 --> 56:35.130
I need to share some basic information

56:35.130 --> 56:35.963
some data with you,

56:35.963 --> 56:37.890
so that you can start working
at the engineering level,

56:37.890 --> 56:39.010
and oh, by the way,

56:39.010 --> 56:41.480
all those machine learning
apps and other things,

56:41.480 --> 56:43.540
you may have a better mouse-trap

56:43.540 --> 56:45.357
than the one that I'm working on.

56:45.357 --> 56:46.610
And so what we gotta really do

56:46.610 --> 56:47.830
with our partners and allies is

56:47.830 --> 56:51.830
not deliver a system to
them, that we can share,

56:51.830 --> 56:54.723
but to bring them in at
the engineering level.

56:54.723 --> 56:57.483
- So for those that know me,

56:59.050 --> 57:01.360
I'm pretty passionate
about the work that we do

57:01.360 --> 57:03.060
with the Five Eyes community.

57:03.060 --> 57:06.900
I've been doing that for,
(sighs) I don't know,

57:06.900 --> 57:09.600
to a large degree for about
five years pretty heavily,

57:10.630 --> 57:11.463
to the point where I,

57:11.463 --> 57:14.040
because I see the value proposition,

57:14.040 --> 57:16.030
'cause we don't fight
as an individual nation,

57:16.030 --> 57:18.990
we fight as a coalition of warriors

57:18.990 --> 57:20.453
wherever that happens to be.

57:21.360 --> 57:24.220
We work together as that coalition.

57:24.220 --> 57:28.290
I can't even separate that from my being.

57:28.290 --> 57:30.004
So one of the things I had to do

57:30.004 --> 57:33.720
when General Ashley put
me in this job last year,

57:33.720 --> 57:36.100
was sign as the original
classification authority

57:36.100 --> 57:37.762
for the JWICS classification,

57:37.762 --> 57:40.150
security classification guide.

57:40.150 --> 57:42.320
And I went through that
thing, and it was very long,

57:42.320 --> 57:45.560
and it was 1990-ish discussion,

57:45.560 --> 57:47.340
I said I'm not signing that.

57:47.340 --> 57:49.260
I went through the whole
thing, I red-lined it,

57:49.260 --> 57:52.300
I mean it was, Chris Ravirez
in the audience somewheres

57:52.300 --> 57:53.433
who did that for me,

57:54.620 --> 57:57.460
and he can attest to the amount
of changes that I had at,

57:57.460 --> 58:00.640
to the end result of
that is a major re-write

58:00.640 --> 58:03.150
of the JWICS Security
Classification Guide,

58:03.150 --> 58:08.150
and to wit, I took out
NOFORN almost exclusively

58:09.350 --> 58:10.680
in that document.

58:10.680 --> 58:12.300
It is now a releasable document,

58:12.300 --> 58:16.160
it talks about being
releasable to our partners,

58:16.160 --> 58:17.637
because that's how it is.

58:17.637 --> 58:20.393
And my litmus test on
that was pretty simple,

58:21.960 --> 58:23.000
if our partners,

58:23.000 --> 58:24.630
and I'm gonna use Major
General John Howard,

58:24.630 --> 58:26.810
he's sitting here in the
front row, as an example,

58:26.810 --> 58:29.060
so if our Kiwi partners get,

58:29.060 --> 58:30.930
find out that we have a problem

58:30.930 --> 58:33.830
on a JWICS node somewheres,

58:33.830 --> 58:36.420
have we compromised national security?

58:36.420 --> 58:37.630
Guess what, we didn't.

58:37.630 --> 58:39.450
They're our partners,

58:39.450 --> 58:41.520
well that instantly makes that route.

58:41.520 --> 58:45.938
It's just a mindset change
that we all have to adopt that,

58:45.938 --> 58:48.170
you know, we're not in this
little bubble ourselves,

58:48.170 --> 58:51.566
we have to work in this partner coalitions

58:51.566 --> 58:53.823
and it just plain-out makes sense.

58:56.310 --> 58:58.200
- [Doug] So another question we have

58:58.200 --> 59:00.420
deals with Cloud computing
becoming the new norm

59:00.420 --> 59:02.170
in the private and commercial sector.

59:02.170 --> 59:03.003
So the question is,

59:03.003 --> 59:05.890
how are we aligning
ourselves to better integrate

59:05.890 --> 59:08.670
with them from a government standpoint?

59:08.670 --> 59:09.670
- I'll let you take that one.

59:09.670 --> 59:14.370
- All right, so, I think
everybody's pretty aware,

59:14.370 --> 59:17.150
when Stephanie O'Sullivan was the

59:17.150 --> 59:20.280
Principal Deputy Director
of National Intelligence,

59:20.280 --> 59:23.047
a few years back, and General Clapper was

59:23.047 --> 59:25.470
the Director of National Intelligence,

59:25.470 --> 59:27.050
we stood up a thing called ICITE,

59:27.050 --> 59:28.270
and I'm not gonna talk a lot about it,

59:28.270 --> 59:32.010
because John Sherman's
going to speak to ICITE

59:32.010 --> 59:34.900
and EPIC 2 and where
we're going with that.

59:34.900 --> 59:37.210
But back then, the intent was,

59:37.210 --> 59:39.910
Cloud was generally a new concept

59:39.910 --> 59:42.270
for the government, at least.

59:42.270 --> 59:44.320
Maybe not so much in the private sector,

59:44.320 --> 59:46.290
and it was, hey you have to be all in,

59:46.290 --> 59:48.113
everything must go into the Cloud.

59:49.690 --> 59:53.530
We have grown in our knowledge since then.

59:53.530 --> 59:56.420
We've learned a lot about what that means,

59:56.420 --> 59:57.470
what it doesn't mean,

59:57.470 --> 59:58.640
where the value proposition,

59:58.640 --> 01:00:01.160
and how well it's gonna work
in some places than others.

01:00:01.160 --> 01:00:03.083
You can't be all-in right now.

01:00:04.210 --> 01:00:07.703
Simply because physics
sometimes get in the way.

01:00:09.070 --> 01:00:13.640
That said, what we've done
in the past is we said,

01:00:13.640 --> 01:00:18.340
is it technically feasible to
put something in the Cloud?

01:00:18.340 --> 01:00:20.220
Check, yeah, 'cause we can pretty much

01:00:20.220 --> 01:00:21.820
put anything a Cloud, right?

01:00:21.820 --> 01:00:23.650
Where that stands now.

01:00:23.650 --> 01:00:25.040
What I've implemented at CIO,

01:00:25.040 --> 01:00:26.800
is said there's two more criteria

01:00:26.800 --> 01:00:28.450
that you have to check off.

01:00:28.450 --> 01:00:32.900
One is, does it make a
functional mission impact?

01:00:32.900 --> 01:00:36.450
Where we do tracking from
that, check or minus?

01:00:36.450 --> 01:00:38.460
And the last one is cost.

01:00:38.460 --> 01:00:40.360
Because when you put
something in the Cloud,

01:00:40.360 --> 01:00:43.070
I end up with a fixed cost I must pay.

01:00:43.070 --> 01:00:46.510
And so you have to do a
business cost analysis to say,

01:00:46.510 --> 01:00:49.450
does it make financial sense to go there,

01:00:49.450 --> 01:00:51.910
or can you do it a different way?

01:00:51.910 --> 01:00:54.210
And so that's kinda where
we're at looking at that.

01:00:54.210 --> 01:00:56.400
There's multiple
technologies coming at you,

01:00:56.400 --> 01:00:58.320
as everybody is aware.

01:00:58.320 --> 01:00:59.153
Not saying anything new,

01:00:59.153 --> 01:01:02.890
C2S, the commercial Cloud
services run by Amazon,

01:01:02.890 --> 01:01:05.333
is on our TS environment.

01:01:06.440 --> 01:01:08.680
Microsoft is standing up Azure

01:01:09.608 --> 01:01:12.340
on the TS environment coming up.

01:01:12.340 --> 01:01:15.770
We're using various Clouds
in different levels,

01:01:15.770 --> 01:01:19.310
Dana Deasy as the DOD/CIO
is bringing in JEDI,

01:01:19.310 --> 01:01:23.470
bringing in Cloud computing
to the DOD at large,

01:01:23.470 --> 01:01:25.290
on all the different domains.

01:01:25.290 --> 01:01:28.670
What we're doing is, to
me it's an ecosystem,

01:01:28.670 --> 01:01:30.120
I don't care if it's a Microsoft,

01:01:30.120 --> 01:01:33.150
IBM, Google, what have you,

01:01:33.150 --> 01:01:34.750
and as General Ashley talked about,

01:01:34.750 --> 01:01:36.170
the interoperability amongst them,

01:01:36.170 --> 01:01:37.680
or as we saw this morning,

01:01:37.680 --> 01:01:40.590
with the iPhone and the Samsung,

01:01:40.590 --> 01:01:42.000
that the application or whatever,

01:01:42.000 --> 01:01:43.800
we gotta get past that

01:01:43.800 --> 01:01:46.780
so I can use the entire ecosystem.

01:01:46.780 --> 01:01:49.523
Give you an example and then I'll shut up.

01:01:50.600 --> 01:01:53.280
So in the intel community,

01:01:53.280 --> 01:01:55.500
we have essentially two
Clouds in the high side.

01:01:55.500 --> 01:01:59.910
We have C2S, which is a
commercial Cloud service provider,

01:01:59.910 --> 01:02:03.153
and then we have NSA provides
government the GovCloud.

01:02:05.610 --> 01:02:06.527
What I want to do,

01:02:06.527 --> 01:02:08.450
and what I've said for years I want to do,

01:02:08.450 --> 01:02:11.050
even though I got some
pushback over time from that,

01:02:12.370 --> 01:02:14.140
there's some people in
here that have heard

01:02:14.140 --> 01:02:15.220
some of that pushback,

01:02:15.220 --> 01:02:16.590
was I want to use the ecosystem,

01:02:16.590 --> 01:02:19.410
I want to develop
capabilities on on-class.

01:02:19.410 --> 01:02:24.120
I want to get data from
the PAI data and move that.

01:02:24.120 --> 01:02:27.850
I want to run analytics in
the Cloud that NSA provides,

01:02:27.850 --> 01:02:29.970
'cause it's a data analytics Cloud.

01:02:29.970 --> 01:02:32.800
And wanna do the compute
and the visualization

01:02:32.800 --> 01:02:34.210
in the commercial Cloud,

01:02:34.210 --> 01:02:36.510
so then you end up with this ecosystem

01:02:36.510 --> 01:02:38.690
that is using best-of-breed
of those things,

01:02:38.690 --> 01:02:40.800
that is fully interoperable,

01:02:40.800 --> 01:02:43.260
so that we provide the best capability,

01:02:43.260 --> 01:02:46.180
the best answer to our policy makers

01:02:46.180 --> 01:02:50.034
and our warfighters, so
we're doing things at speed.

01:02:50.034 --> 01:02:50.867
- And I just wanted to point out

01:02:50.867 --> 01:02:51.950
they just changed the screen here,

01:02:51.950 --> 01:02:54.313
'cause initially we had 95 hours left,

01:02:54.313 --> 01:02:56.200
- Five minutes.
- And now it's

01:02:56.200 --> 01:02:57.421
only five minutes, thank God.

01:02:57.421 --> 01:03:01.270
(audience laughing)

01:03:01.270 --> 01:03:02.103
Whew, I'm going to need more water.

01:03:02.103 --> 01:03:03.480
- Somebody's got a 5-Hour
Energy drink for me?

01:03:03.480 --> 01:03:04.313
- There you go.

01:03:06.180 --> 01:03:07.960
- [Doug] All right, well we're
gonna take one more question

01:03:07.960 --> 01:03:09.740
with that five minutes remaining.

01:03:09.740 --> 01:03:11.350
So the last question deals with

01:03:11.350 --> 01:03:12.930
our strategy and prioritization,

01:03:12.930 --> 01:03:14.600
we've been discussing
that a lot on this stage

01:03:14.600 --> 01:03:16.240
during our opening remarks.

01:03:16.240 --> 01:03:17.730
How are we partnering with Congress

01:03:17.730 --> 01:03:20.240
to keep them engaged with
the IA's developments?

01:03:20.240 --> 01:03:21.430
- So I'll start that one.

01:03:21.430 --> 01:03:24.333
It is, so we're pushing on an open door,

01:03:25.170 --> 01:03:26.420
and they are very helpful,

01:03:26.420 --> 01:03:28.690
but there's an education
process behind that,

01:03:28.690 --> 01:03:30.890
so we take every opportunity we can to go

01:03:30.890 --> 01:03:33.843
and talk to them about every
initiative that we have.

01:03:35.011 --> 01:03:36.070
And the successes which,

01:03:36.070 --> 01:03:38.010
a lot of them in the classified realm,

01:03:38.010 --> 01:03:40.420
of how we've leveraged machine learning,

01:03:40.420 --> 01:03:43.160
artificial, well, machine
learning computer vision.

01:03:43.160 --> 01:03:46.100
But we've gone up there
countless times with staffers,

01:03:46.100 --> 01:03:47.570
and members to talk to them

01:03:47.570 --> 01:03:52.310
about MARS and JWICS specifically,

01:03:52.310 --> 01:03:54.449
to make sure we're able
to get their support,

01:03:54.449 --> 01:03:56.060
understand where the program's going,

01:03:56.060 --> 01:03:57.970
that they don't have any questions.

01:03:57.970 --> 01:04:00.490
And for JWICS the big
thing I've asked Jack

01:04:00.490 --> 01:04:01.360
and the guys to push on,

01:04:01.360 --> 01:04:04.390
is to bring the staffers and
members to DIA headquarters

01:04:04.390 --> 01:04:07.373
to go down to the basement
and take a look at,

01:04:08.610 --> 01:04:10.190
I don't want to say
the state of disrepair,

01:04:10.190 --> 01:04:13.430
but we are challenged to
be able to upgrade that,

01:04:13.430 --> 01:04:17.130
so we cannot afford to take
marks against the program

01:04:17.130 --> 01:04:19.820
given we're kinda keeping
it alive right now,

01:04:19.820 --> 01:04:20.653
we want to make sure

01:04:20.653 --> 01:04:22.500
that we get it really, really healthy.

01:04:22.500 --> 01:04:24.000
So there's constant dialog,

01:04:24.000 --> 01:04:27.610
on any given week, we are on the Hill,

01:04:27.610 --> 01:04:32.433
either with threat topics,
modernization issues across DIA,

01:04:34.140 --> 01:04:35.710
probably, what, five, six times.

01:04:35.710 --> 01:04:39.150
So everyday, there's at
least one or two teams

01:04:39.150 --> 01:04:41.990
that are on the Hill,
having a conversation,

01:04:41.990 --> 01:04:43.880
and we have to make that investment

01:04:43.880 --> 01:04:45.800
because they're the ones
that are gonna ensure

01:04:45.800 --> 01:04:47.330
that these efforts are funded.

01:04:47.330 --> 01:04:48.710
They ask us lots of hard questions,

01:04:48.710 --> 01:04:49.543
they want to make sure

01:04:49.543 --> 01:04:51.820
we're not headed down proprietary lanes,

01:04:51.820 --> 01:04:52.653
and they want to know

01:04:52.653 --> 01:04:54.570
how this is solving the
nation's hardest problems.

01:04:54.570 --> 01:04:58.880
But they are close
partners in that way ahead,

01:04:58.880 --> 01:05:00.700
and we're working with them

01:05:00.700 --> 01:05:02.380
to make sure that they're
good, strong advocates.

01:05:02.380 --> 01:05:05.110
And those staffers can
explain to members, as well,

01:05:05.110 --> 01:05:08.370
why it is they need to spend that money

01:05:08.370 --> 01:05:09.930
to help the Department of Defense

01:05:09.930 --> 01:05:12.423
in the larger construct which is,

01:05:13.270 --> 01:05:15.380
the eroding technological
advantage we have

01:05:15.380 --> 01:05:16.440
which is the central problem

01:05:16.440 --> 01:05:18.180
in the National Defense Strategy,

01:05:18.180 --> 01:05:19.670
which the Defense Intelligence Agency

01:05:19.670 --> 01:05:21.363
plays a key role in that.

01:05:22.630 --> 01:05:24.660
- So in the, historically in the past,

01:05:24.660 --> 01:05:26.100
I will tell you that we have not done

01:05:26.100 --> 01:05:27.650
as well a job as we could have.

01:05:29.040 --> 01:05:32.623
At least, in the IT industry
talking to the Hill.

01:05:34.220 --> 01:05:37.770
I say it was an example where
we would do certain things,

01:05:37.770 --> 01:05:39.720
and we would wait,

01:05:39.720 --> 01:05:42.347
and then lobbyists would
go in and get in before us,

01:05:42.347 --> 01:05:46.293
and it ended up not being
the greatest situation.

01:05:47.410 --> 01:05:50.650
That has changed, we have
much better engagement,

01:05:50.650 --> 01:05:54.430
I have asked staffers
to come to this event,

01:05:54.430 --> 01:05:56.120
so that they can get an appreciation,

01:05:56.120 --> 01:05:57.320
an understanding of what,

01:05:57.320 --> 01:06:00.870
of the complexity of
this thing called DoDIIS,

01:06:00.870 --> 01:06:03.670
and the DIE and what DIA's doing,

01:06:03.670 --> 01:06:06.260
and how we're partnering
with our IC partners,

01:06:06.260 --> 01:06:08.970
and our DOD partners,
and our foreign partners,

01:06:08.970 --> 01:06:13.010
and our commercial partners,
'cause it's very complex.

01:06:13.010 --> 01:06:14.900
We have a staffer here today,

01:06:14.900 --> 01:06:18.380
I was very happy that he was
able to make it from the HiPC,

01:06:19.250 --> 01:06:22.410
to have an understanding
and feed that back in.

01:06:22.410 --> 01:06:24.670
And as General Ashley said,

01:06:24.670 --> 01:06:27.870
I have taken them down
to see our tech control

01:06:27.870 --> 01:06:29.960
and our data center,
and our comms closets,

01:06:29.960 --> 01:06:33.020
and to show what I call
Frankenstein equipment,

01:06:33.020 --> 01:06:38.020
where I did not have the
procurement authority

01:06:38.610 --> 01:06:41.260
to actually go buy a piece of equipment,

01:06:41.260 --> 01:06:44.750
mission was impacted,
we had to get it fixed,

01:06:44.750 --> 01:06:47.840
we took equipment or
parts of the equipment,

01:06:47.840 --> 01:06:51.890
out of equipment that
was going to the DRMO,

01:06:51.890 --> 01:06:54.000
it was destined for destruction.

01:06:54.000 --> 01:06:55.670
To pull that out, put it back in there,

01:06:55.670 --> 01:06:57.970
to say mission reigns supreme,

01:06:57.970 --> 01:06:59.720
we're going to do what we gotta do.

01:07:00.799 --> 01:07:03.210
And if you get a chance,

01:07:03.210 --> 01:07:05.590
Scott Miller's out here in the audience,

01:07:05.590 --> 01:07:06.750
and you get a chance to talk to him,

01:07:06.750 --> 01:07:08.770
you can ask what his views on that is,

01:07:08.770 --> 01:07:11.140
but I think it's a
resonating message with them

01:07:11.140 --> 01:07:12.800
to actually not hear it,

01:07:12.800 --> 01:07:14.660
but just, and to see it as well.

01:07:14.660 --> 01:07:16.460
- And the other piece of that is

01:07:16.460 --> 01:07:17.460
we're not just building this

01:07:17.460 --> 01:07:19.120
for the Defense Intelligence Agency,

01:07:19.120 --> 01:07:22.920
we're building this for the
Defense Intelligence enterprise.

01:07:22.920 --> 01:07:24.360
This will be provisioned and available

01:07:24.360 --> 01:07:25.470
to the all the combat commands,

01:07:25.470 --> 01:07:27.340
this is for the warfighter.

01:07:27.340 --> 01:07:28.880
This will be a Warfighter system,

01:07:28.880 --> 01:07:30.070
much like JWICS.

01:07:30.070 --> 01:07:33.970
JWICS is migrating to be more
about command and control.

01:07:33.970 --> 01:07:36.960
Network and General Hyten
said that last year,

01:07:36.960 --> 01:07:37.950
that was at this conference,

01:07:37.950 --> 01:07:40.520
he goes I see C2 off of JWICS,

01:07:40.520 --> 01:07:42.130
and so we're in discussion now of,

01:07:42.130 --> 01:07:45.350
okay, what does JWICS
need to be in the future?

01:07:45.350 --> 01:07:49.270
Because it was born as a
video teleconference system,

01:07:49.270 --> 01:07:52.960
and now, you know, we're
funded to provision to a point,

01:07:52.960 --> 01:07:57.910
but we can't provision
it as a C2 comm system.

01:07:57.910 --> 01:07:58.970
So there's a lot of work we gotta do

01:07:58.970 --> 01:07:59.910
within the Department of Defense

01:07:59.910 --> 01:08:02.070
and talk about what the
way ahead is for that.

01:08:02.070 --> 01:08:02.980
But everything we're talking about,

01:08:02.980 --> 01:08:04.100
all these tools, everything else,

01:08:04.100 --> 01:08:05.360
this is for the Warfighter.

01:08:05.360 --> 01:08:08.290
This is for senior leaders,
it is for the Hill,

01:08:08.290 --> 01:08:10.320
it is for decision advantage,

01:08:10.320 --> 01:08:14.043
and it has to scale to
the entire enterprise.

01:08:15.240 --> 01:08:17.410
- [Doug] So we've received
several thousand questions,

01:08:17.410 --> 01:08:19.860
it appears, as I'm watching
all of the emails come in.

01:08:19.860 --> 01:08:21.164
I will make sure--

01:08:21.164 --> 01:08:21.997
- So it was 95 hours that I've--

01:08:21.997 --> 01:08:22.830
- Yeah,
(all laughing)

01:08:22.830 --> 01:08:23.663
- [Doug] Well, you're gonna spend that,

01:08:23.663 --> 01:08:25.000
'cause I'm gonna make
sure every single one

01:08:25.000 --> 01:08:26.527
of those emails is
forwarded to both of you

01:08:26.527 --> 01:08:28.393
before we depart so you can respond.

01:08:28.393 --> 01:08:29.626
(audience laughing)
- I have a rule set up.

01:08:29.626 --> 01:08:31.560
- [Doug] (laughing) But I
wanted to thank you both

01:08:31.560 --> 01:08:33.338
for the question and answer session.

01:08:33.338 --> 01:08:34.171
- Thanks, Doug.

01:08:34.171 --> 01:08:35.900
- [Doug] Thank you to the
audience for participating,

01:08:35.900 --> 01:08:37.686
I appreciate your time.

01:08:37.686 --> 01:08:42.686
(audience applauding)
- All right, thanks boss.

01:08:44.653 --> 01:08:45.920
I think that's it, right?

01:08:45.920 --> 01:08:47.752
- That's it, yep.
- Thanks.

01:08:47.752 --> 01:08:49.152
- Thank you, thank you, sir.

01:08:52.150 --> 01:08:54.000
- We're gonna go off there somewhere.

01:08:58.670 --> 01:08:59.550
- Well welcome everyone.

01:08:59.550 --> 01:09:01.410
Again, my name is Doug Cossa,

01:09:01.410 --> 01:09:03.330
I'm the Deputy Chief Information Officer

01:09:03.330 --> 01:09:05.333
here at the Defense Intelligence Agency.

01:09:06.270 --> 01:09:09.150
Last year, I had just
started in this position.

01:09:09.150 --> 01:09:13.480
I'm actually on joint-detail
from ODNI to DIA,

01:09:13.480 --> 01:09:16.520
and I was here only a few
weeks before coming to DoDIIS.

01:09:16.520 --> 01:09:17.840
And I remember sitting in the front row,

01:09:17.840 --> 01:09:19.230
thinking to myself,

01:09:19.230 --> 01:09:21.250
man, what if they ask
me to speak next year?

01:09:21.250 --> 01:09:23.150
What on earth am I gonna say?

01:09:23.150 --> 01:09:25.000
So, here I am.

01:09:25.000 --> 01:09:26.610
Trying to think about what I'm gonna say.

01:09:26.610 --> 01:09:27.750
No, just kidding.

01:09:27.750 --> 01:09:28.960
So as Jack mentioned,

01:09:28.960 --> 01:09:32.020
DoDIIS is the largest
technology conference in the IC,

01:09:32.020 --> 01:09:34.290
and this is our 16th year of holding it.

01:09:34.290 --> 01:09:36.140
For me, and last year I experienced this

01:09:36.140 --> 01:09:37.560
it's a source for understanding

01:09:37.560 --> 01:09:40.050
how we might apply some of
the most innovative ideas

01:09:40.050 --> 01:09:41.365
and capabilities to solve

01:09:41.365 --> 01:09:43.750
some of our most pressing challenges.

01:09:43.750 --> 01:09:45.540
In the simplest terms,

01:09:45.540 --> 01:09:47.600
in terms of the definition
of what innovation is,

01:09:47.600 --> 01:09:50.810
it's really the intersection
of new capabilities,

01:09:50.810 --> 01:09:53.430
new disciplines, and new ways of thinking.

01:09:53.430 --> 01:09:56.040
And we heard a lot of that
from the director earlier.

01:09:56.040 --> 01:09:56.873
In a few minutes,

01:09:56.873 --> 01:09:59.510
we're gonna break for our networking

01:09:59.510 --> 01:10:01.280
and vendor booth visits,

01:10:01.280 --> 01:10:02.630
and we're gonna experience

01:10:02.630 --> 01:10:04.810
that very definition of innovation.

01:10:04.810 --> 01:10:06.520
Before we do I'd like to leave you

01:10:06.520 --> 01:10:08.870
with a few thoughts to bring along.

01:10:08.870 --> 01:10:11.850
We hear a lot about emphasizing innovation

01:10:11.850 --> 01:10:14.240
across the IC and across
the federal government,

01:10:14.240 --> 01:10:15.699
and often times we struggle

01:10:15.699 --> 01:10:17.970
with understanding what that really means.

01:10:17.970 --> 01:10:19.760
And the truth lies

01:10:19.760 --> 01:10:23.460
in the last part that I
gave you of innovation,

01:10:23.460 --> 01:10:25.270
which is new ways of thinking.

01:10:25.270 --> 01:10:27.300
It's more than just thinking about

01:10:27.300 --> 01:10:30.410
what's the next big capability
that we need to build?

01:10:30.410 --> 01:10:31.520
And if you look throughout time,

01:10:31.520 --> 01:10:32.820
look throughout history,

01:10:32.820 --> 01:10:34.900
the most impactful innovations

01:10:34.900 --> 01:10:37.250
have actually started
with paradigm shifts.

01:10:37.250 --> 01:10:40.710
So concepts like the world is flat,

01:10:40.710 --> 01:10:43.700
the earth is flat, continental shift,

01:10:43.700 --> 01:10:47.960
washing our hands to prevent
the spread of disease,

01:10:47.960 --> 01:10:49.150
those are basic thinking.

01:10:49.150 --> 01:10:51.820
Those are basic concepts
today that we all know,

01:10:51.820 --> 01:10:52.653
and take for granted.

01:10:52.653 --> 01:10:53.486
Although the last one,

01:10:53.486 --> 01:10:54.710
I've been in this bathroom a few times,

01:10:54.710 --> 01:10:57.052
I'm not sure that some of you
have bought on to that yet.

01:10:57.052 --> 01:10:58.470
(audience laughing)

01:10:58.470 --> 01:11:01.740
But we've experienced over
the past several years,

01:11:01.740 --> 01:11:03.890
our own paradigm shifts, right?

01:11:03.890 --> 01:11:05.840
So think back to before the internet.

01:11:05.840 --> 01:11:08.290
We were confident that the reason

01:11:08.290 --> 01:11:10.530
for collective ignorance and idiocy,

01:11:10.530 --> 01:11:12.190
was because of the lack of information,

01:11:12.190 --> 01:11:14.210
lack of access to that information.

01:11:14.210 --> 01:11:15.327
And then with the rise of the internet,

01:11:15.327 --> 01:11:17.850
and the advent of social media,

01:11:17.850 --> 01:11:19.755
we were actually completely
wrong on that one.

01:11:19.755 --> 01:11:21.170
(audience laughing)

01:11:21.170 --> 01:11:23.960
But, in the 1990s with the internet,

01:11:23.960 --> 01:11:26.570
we were told basic concepts, right?

01:11:26.570 --> 01:11:29.450
Never talk to strangers over the internet.

01:11:29.450 --> 01:11:31.220
And we always knew from
our childhood days,

01:11:31.220 --> 01:11:33.530
of never get into a stranger's car.

01:11:33.530 --> 01:11:35.500
Today, we use the internet

01:11:35.500 --> 01:11:38.670
to literally summon strangers
and get in their cars.

01:11:38.670 --> 01:11:40.700
And I bet that many of you did that

01:11:40.700 --> 01:11:43.273
on some portion of your travel leg today.

01:11:43.273 --> 01:11:44.190
(audience laughing)

01:11:44.190 --> 01:11:47.410
But in the IC, if you look at our history,

01:11:47.410 --> 01:11:49.320
we've experienced our own paradigm shifts,

01:11:49.320 --> 01:11:51.720
especially over the past decade.

01:11:51.720 --> 01:11:54.230
So when I started in this community,

01:11:54.230 --> 01:11:57.520
the idea of open-source,
as a collection discipline,

01:11:57.520 --> 01:11:59.510
was actually debated.

01:11:59.510 --> 01:12:00.963
If you said the word OCEN,

01:12:01.800 --> 01:12:04.570
people would think that you
weren't a collection specialist,

01:12:04.570 --> 01:12:07.330
you didn't understand
how intelligence works.

01:12:07.330 --> 01:12:10.070
Today, open-source is
woven into the fabric

01:12:10.070 --> 01:12:12.700
of nearly everything we produce.

01:12:12.700 --> 01:12:14.340
Within the past decade, we never thought

01:12:14.340 --> 01:12:17.210
that anyone would be able
to assess or produce,

01:12:17.210 --> 01:12:19.430
imagery intelligence from space,

01:12:19.430 --> 01:12:20.955
let alone own the capabilities

01:12:20.955 --> 01:12:23.030
for the government to leverage.

01:12:23.030 --> 01:12:26.400
Today, NGA even hosts a
conference, much like this one,

01:12:26.400 --> 01:12:28.290
to celebrate our
partnership with industry.

01:12:28.290 --> 01:12:29.330
It's not as good as this one,

01:12:29.330 --> 01:12:31.808
I think we'd all agree, but they try.

01:12:31.808 --> 01:12:32.920
(audience laughing)

01:12:32.920 --> 01:12:35.010
Just kidding, just kidding. (laughs)

01:12:35.010 --> 01:12:37.030
And just a mere seven years ago,

01:12:37.030 --> 01:12:39.020
we thought that each of
our intelligence agencies

01:12:39.020 --> 01:12:42.430
and services had to own, operate,

01:12:42.430 --> 01:12:44.630
and maintain its own IT infrastructure.

01:12:44.630 --> 01:12:48.060
And tomorrow, we'll hear
from ICCIO John Sherman,

01:12:48.060 --> 01:12:50.240
about how we're entering
the third epic of ICITE,

01:12:50.240 --> 01:12:52.430
to where we're not only
sharing our infrastructure,

01:12:52.430 --> 01:12:54.708
but we're also sharing our data.

01:12:54.708 --> 01:12:56.120
And so the topic of data brings me

01:12:56.120 --> 01:12:59.570
to another aspect of innovation, booms.

01:12:59.570 --> 01:13:02.030
And what I mean by that,
is as technology evolves,

01:13:02.030 --> 01:13:04.870
our use of that technology
evolves as well.

01:13:04.870 --> 01:13:06.050
And some of the most prominent

01:13:06.050 --> 01:13:08.410
and enduring companies throughout history

01:13:08.410 --> 01:13:11.120
actually arose during industry booms.

01:13:11.120 --> 01:13:13.300
Take for example the Gold Rush.

01:13:13.300 --> 01:13:15.130
That boom created whole industries

01:13:15.130 --> 01:13:19.110
for clothing, lodging and
tools, that didn't exist before.

01:13:19.110 --> 01:13:20.660
Levi's jeans, for example,

01:13:20.660 --> 01:13:22.490
which I'm sure every
one of us in this room

01:13:22.490 --> 01:13:24.570
has worn at one point in our lives,

01:13:24.570 --> 01:13:26.580
actually started by creating clothing

01:13:26.580 --> 01:13:28.833
for miners digging for gold.

01:13:30.070 --> 01:13:34.020
In the early 1980s we actually
saw another industry boom,

01:13:34.020 --> 01:13:36.440
and that was the rise of the PC.

01:13:36.440 --> 01:13:39.170
And that brought forth
transformational change,

01:13:39.170 --> 01:13:41.760
and what we saw was thousands of companies

01:13:41.760 --> 01:13:44.250
entering the market to build computers.

01:13:44.250 --> 01:13:47.120
And with that, we had
different models of computers

01:13:47.120 --> 01:13:48.450
which had different ports.

01:13:48.450 --> 01:13:50.300
And printers had different ports.

01:13:50.300 --> 01:13:51.470
And it was actually a nightmare

01:13:51.470 --> 01:13:52.450
to connect those devices,

01:13:52.450 --> 01:13:54.307
for those of you that remember.

01:13:54.307 --> 01:13:58.640
And so a guy named Chet
Pitkin actually saw

01:13:58.640 --> 01:13:59.610
that as an opportunity.

01:13:59.610 --> 01:14:02.760
And he didn't focus on making computers,

01:14:02.760 --> 01:14:05.490
he actually focused on the
interfaces to connect them.

01:14:05.490 --> 01:14:08.080
He made the cables and other devices

01:14:08.080 --> 01:14:10.470
to actually make what you bought work.

01:14:10.470 --> 01:14:13.630
So keyboards, mice, and so-forth.

01:14:13.630 --> 01:14:16.320
And he formed what today is
known as the Belkin Corporation.

01:14:16.320 --> 01:14:18.467
And he took advantage
of that industry boom.

01:14:18.467 --> 01:14:20.730
And with the smartphone
boom in more recent years,

01:14:20.730 --> 01:14:24.130
in the past decade, Belkin
took advantage of that as well.

01:14:24.130 --> 01:14:27.060
They created the cables
to connect your phones.

01:14:27.060 --> 01:14:29.020
The chargers, the cases, and so-forth.

01:14:29.020 --> 01:14:31.320
And today, Belkin is arguably

01:14:31.320 --> 01:14:35.030
one of the most successful
tech companies of our era.

01:14:35.030 --> 01:14:38.610
Sometimes you're lucky enough
to actually walk into a boom,

01:14:38.610 --> 01:14:43.220
and for me it happened 23
years ago, almost to this day,

01:14:43.220 --> 01:14:46.060
when I was starting my
freshman year of college.

01:14:46.060 --> 01:14:49.440
And I was lucky enough to save
up enough money that summer,

01:14:49.440 --> 01:14:51.650
and I bought my own computer.

01:14:51.650 --> 01:14:56.330
And when I got to school, most
of the students at that time,

01:14:56.330 --> 01:14:57.740
used computer labs, right?

01:14:57.740 --> 01:15:00.600
With long lines to wait
to get on a computer,

01:15:00.600 --> 01:15:02.210
and you had to share a printer,

01:15:02.210 --> 01:15:04.160
and it took much longer than it needed to.

01:15:04.160 --> 01:15:05.160
I had my own computer,

01:15:05.160 --> 01:15:08.200
and I was excited to hook it
up to the school's network,

01:15:08.200 --> 01:15:10.890
because it also meant that
you had unlimited access

01:15:10.890 --> 01:15:13.010
to free music, software, movies,

01:15:13.010 --> 01:15:13.960
whatever you could think of.

01:15:13.960 --> 01:15:15.930
I, of course, didn't
partake in any of that,

01:15:15.930 --> 01:15:17.219
but I know people that did.

01:15:17.219 --> 01:15:18.890
(audience laughing)

01:15:18.890 --> 01:15:21.800
But when I bought my computer,
it was missing one thing,

01:15:21.800 --> 01:15:23.780
and all computers really did at this time,

01:15:23.780 --> 01:15:25.670
and it was the network interface card,

01:15:25.670 --> 01:15:28.660
to actually sync-up to that network.

01:15:28.660 --> 01:15:32.390
And there was one store in
town that sold these NIC cards,

01:15:32.390 --> 01:15:34.510
and they charged $100.

01:15:34.510 --> 01:15:38.550
So I went down to buy
one, and I paid my $100.

01:15:38.550 --> 01:15:40.650
But you couldn't install it yourself.

01:15:40.650 --> 01:15:42.937
He said, "I'll schedule an appointment

01:15:42.937 --> 01:15:44.560
"to come over and install it for you."

01:15:44.560 --> 01:15:45.410
So I said, "Great."

01:15:45.410 --> 01:15:48.060
And I didn't know a ton
about computers at the time.

01:15:48.060 --> 01:15:50.560
So he came to my dorm
room a couple days later,

01:15:50.560 --> 01:15:52.680
he opened the box with the internet,

01:15:52.680 --> 01:15:54.570
the network card in it,

01:15:54.570 --> 01:15:57.400
and he popped it in the PC on
the slot to the motherboard.

01:15:57.400 --> 01:15:58.930
All in about 10 seconds.

01:15:58.930 --> 01:16:01.380
And he said, "That'll be $250."

01:16:01.380 --> 01:16:02.740
(audience laughing)

01:16:02.740 --> 01:16:06.083
And I thought to myself,
this will never happen again.

01:16:07.120 --> 01:16:08.790
So I didn't know about
computers at the time,

01:16:08.790 --> 01:16:11.590
so I started to work at the
computer help desk at school.

01:16:11.590 --> 01:16:14.750
And I worked at night with
another friend of mine named Rob,

01:16:14.750 --> 01:16:18.030
and we took trouble calls over the phone.

01:16:18.030 --> 01:16:19.330
But the thing was at the help desk,

01:16:19.330 --> 01:16:21.210
if you couldn't solve it over the phone,

01:16:21.210 --> 01:16:23.430
you had to defer it to an outside vendor.

01:16:23.430 --> 01:16:25.510
Well, guess who that vendor was?

01:16:25.510 --> 01:16:26.780
That same guy that installed

01:16:26.780 --> 01:16:28.760
that network card in my computer.

01:16:28.760 --> 01:16:30.407
And that wasn't happening.

01:16:30.407 --> 01:16:31.240
(audience laughing)

01:16:31.240 --> 01:16:33.660
So Rob and I started
to take our own calls,

01:16:33.660 --> 01:16:36.180
so the next morning we'd schedule calls,

01:16:36.180 --> 01:16:37.910
we'd go out to dorm rooms,

01:16:37.910 --> 01:16:39.080
and we'd go fix computers.

01:16:39.080 --> 01:16:41.230
And I learned a lot during that time,

01:16:41.230 --> 01:16:43.300
I also learned that was
illegal, you couldn't do that

01:16:43.300 --> 01:16:46.900
because this guy had a
contract with the school

01:16:46.900 --> 01:16:48.781
to be able to fix computers.

01:16:48.781 --> 01:16:49.690
(audience laughing)

01:16:49.690 --> 01:16:53.460
So we'd started our own company, actually.

01:16:53.460 --> 01:16:56.030
We actually worked with a
bunch of retired attorneys

01:16:56.030 --> 01:16:58.440
in Florida, they helped
us get incorporated.

01:16:58.440 --> 01:17:00.860
And we joined the business environment

01:17:00.860 --> 01:17:02.510
over in the town that we were in.

01:17:03.940 --> 01:17:06.140
And we became a somewhat
legitimate company.

01:17:07.000 --> 01:17:10.170
The next summer, as
freshmens started to enter

01:17:10.170 --> 01:17:13.230
into their freshmen year
and move into their dorms,

01:17:13.230 --> 01:17:14.600
we set up a tent.

01:17:14.600 --> 01:17:16.090
And like any good college student,

01:17:16.090 --> 01:17:18.883
Rob and I took out credit
cards with 20% interest rates,

01:17:18.883 --> 01:17:23.580
and we bought hundreds of ethernet cards.

01:17:23.580 --> 01:17:26.210
And actually that day,
we sold them all out.

01:17:26.210 --> 01:17:29.530
And we recruited many
friends, 20 at the time,

01:17:29.530 --> 01:17:30.363
to go install all of these things

01:17:30.363 --> 01:17:31.920
throughout the course of that week,

01:17:31.920 --> 01:17:34.820
to get all the other students
connected to the network.

01:17:34.820 --> 01:17:37.750
And that became a fairly sizeable company.

01:17:37.750 --> 01:17:39.940
And we got into new areas, new industries.

01:17:39.940 --> 01:17:41.460
We started doing network support,

01:17:41.460 --> 01:17:44.190
we spread out to other local companies,

01:17:44.190 --> 01:17:46.840
car dealerships and so-forth,

01:17:46.840 --> 01:17:48.150
to be able to build their networks

01:17:48.150 --> 01:17:51.440
and supply their computers,
and fix their computers.

01:17:51.440 --> 01:17:52.930
So it was a great experience of my life,

01:17:52.930 --> 01:17:55.640
and I was lucky enough to
actually walk into that boom.

01:17:55.640 --> 01:17:57.940
So the question is what's our boom now?

01:17:57.940 --> 01:18:00.200
And you've already heard
from Jack and the director,

01:18:00.200 --> 01:18:02.140
and you'll hear from many on
the stage throughout the week

01:18:02.140 --> 01:18:05.670
that our boom is data, and
the proliferation of it,

01:18:05.670 --> 01:18:07.880
and our newfound access to it.

01:18:07.880 --> 01:18:09.930
And along with that
comes the infrastructure,

01:18:09.930 --> 01:18:12.530
tools, techniques produced
by many of you in this room,

01:18:12.530 --> 01:18:14.270
to service that boom.

01:18:14.270 --> 01:18:16.100
Data's what intelligence depends on,

01:18:16.100 --> 01:18:19.120
and it's the interface to the
national security decisions

01:18:19.120 --> 01:18:21.100
that senior policy makers, warfighters,

01:18:21.100 --> 01:18:23.000
and intelligence leaders need to make.

01:18:23.890 --> 01:18:25.787
The theme of this years DoDIIS conference,

01:18:25.787 --> 01:18:28.820
as we saw, is resiliency,
redundancy, and security;

01:18:28.820 --> 01:18:31.150
adapting to asymmetric threats.

01:18:31.150 --> 01:18:34.700
And that's more than just a
random compulsive smattering

01:18:34.700 --> 01:18:37.760
of Jack and I's thoughts,
it's actually mostly Jack's.

01:18:37.760 --> 01:18:39.320
But it represents the need to shift

01:18:39.320 --> 01:18:41.260
our thinking as our environment changes.

01:18:41.260 --> 01:18:43.677
It represents the
challenges we're faced with,

01:18:43.677 --> 01:18:45.820
and it represents the dependency we have

01:18:45.820 --> 01:18:48.140
on the infrastructure, the capabilities,

01:18:48.140 --> 01:18:51.010
the tools and the advanced
techniques to connect us.

01:18:51.010 --> 01:18:52.380
Those are the very topics presented

01:18:52.380 --> 01:18:54.410
at the DoDIIS conference this week,

01:18:54.410 --> 01:18:55.940
and in a few minutes we're gonna depart

01:18:55.940 --> 01:18:58.090
to the vendor floor and
we're actually gonna see

01:18:58.090 --> 01:19:00.490
those capabilities first hand.

01:19:00.490 --> 01:19:01.750
Technology is more integrated

01:19:01.750 --> 01:19:03.780
than how we do business
today than ever before,

01:19:03.780 --> 01:19:05.400
hence this years theme.

01:19:05.400 --> 01:19:08.070
So as we depart to the vendor floor,

01:19:08.070 --> 01:19:10.833
and break for our network
socials, ask yourself;

01:19:13.810 --> 01:19:16.060
how are we shifting our thinking,

01:19:16.060 --> 01:19:18.910
and what are the opportunities
to best service this boom?

01:19:19.970 --> 01:19:23.030
When we depart and come back
at 10:55 to take our seats,

01:19:23.030 --> 01:19:25.980
we're gonna also hear from
Major General John Howard,

01:19:25.980 --> 01:19:28.510
who is our Deputy Director
for Commonwealth Integration.

01:19:28.510 --> 01:19:30.090
You heard both Jack and the director talk

01:19:30.090 --> 01:19:32.870
about the importance of interfacing

01:19:32.870 --> 01:19:35.370
with our Five Eye international partners,

01:19:35.370 --> 01:19:37.740
that's another boom that's on our horizon,

01:19:37.740 --> 01:19:39.290
of creating those capabilities

01:19:39.290 --> 01:19:41.790
to more closely interact and collaborate.

01:19:41.790 --> 01:19:45.080
So please come back,
take your seats at 10:55,

01:19:45.080 --> 01:19:47.080
and we'll introduce Major
General John Howard.

01:19:47.080 --> 01:19:50.463
Thank you.
(audience applauding)

