WEBVTT

00:00.570 --> 00:02.980
Okay , so it's uh it's it's my pleasure

00:02.980 --> 00:06.400
to introduce our next speaker . Uh Mr

00:06.400 --> 00:08.990
tom vulture law ahead ? A quick a quick

00:08.990 --> 00:10.768
vulture analogy that I think is

00:10.768 --> 00:12.823
actually maybe pretty good here . So

00:12.823 --> 00:14.990
when I was growing up , my dad used to

00:14.990 --> 00:17.212
have this cartoon picture in his office

00:17.212 --> 00:19.212
and it was , you know , it's one of

00:19.212 --> 00:21.379
these lone trees in the desert kind of

00:21.379 --> 00:23.601
thing . You know , one , you know , one

00:23.601 --> 00:27.170
uh one branch and on the branch there

00:27.170 --> 00:29.360
were two vultures uh sitting on the

00:29.360 --> 00:31.527
branch and one vultures talking to the

00:31.527 --> 00:33.804
other and it says I'm tired of waiting ,

00:33.804 --> 00:36.027
Let's go kill something . And so when I

00:36.027 --> 00:38.027
think of Air Force futures and what

00:38.027 --> 00:40.082
Secretary Kendall is asking us to do

00:40.082 --> 00:41.971
with operational imperatives , it

00:41.971 --> 00:41.580
always reminds me of that , right ?

00:41.590 --> 00:43.701
Because in the end , I think that's a

00:43.701 --> 00:45.701
little bit what Secretary Kendall's

00:45.701 --> 00:47.757
right uh message to us is right , we

00:47.757 --> 00:49.923
got to stop waiting , Right ? Let's go

00:49.923 --> 00:52.090
figure out how we kill something . And

00:52.090 --> 00:54.910
so uh vulture as our leader of Air

00:54.910 --> 00:57.132
force vulture futures , has really been

00:57.132 --> 00:59.021
charged with the analytics behind

00:59.021 --> 01:01.243
figuring out what is the right thing to

01:01.243 --> 01:03.188
do , really has a huge part in the

01:03.188 --> 01:05.188
operational imperatives , I think a

01:05.188 --> 01:07.354
great speaker to lead us through . And

01:07.354 --> 01:09.410
also how we think current forward to

01:09.410 --> 01:09.160
your point about capability ,

01:09.160 --> 01:11.160
development planning . So , vulture

01:11.160 --> 01:12.438
over to you . Thanks .

01:19.030 --> 01:21.030
Alright , good afternoon . Thanks .

01:21.030 --> 01:23.086
General Morris , super excited to be

01:23.086 --> 01:26.140
here . Have this conversation uh

01:26.800 --> 01:29.300
interesting to be the cleanup hitter

01:29.300 --> 01:31.522
here , if you will , you know , an hour

01:31.522 --> 01:33.689
from now ? We can have a discussion on

01:33.689 --> 01:35.633
whether I was actually the cleanup

01:35.633 --> 01:37.578
hitter and successful or was I the

01:37.578 --> 01:39.578
cleanup sweeper ? Behind the circus

01:39.578 --> 01:41.578
parade and the elephants . So we'll

01:41.578 --> 01:45.330
we'll see where this goes . Uh

01:46.180 --> 01:49.330
What I'd like to do is kind of offer uh

01:49.340 --> 01:51.673
the operational side of the imperatives ,

01:51.673 --> 01:53.790
how we got there , why we got there .

01:53.800 --> 01:56.000
And then a few lessons learned along

01:56.000 --> 01:58.890
the way . I will note before I forget

01:58.900 --> 02:02.630
that I brought swag for you . It's not

02:02.630 --> 02:04.686
stress balls . It's not toads , it's

02:04.686 --> 02:07.340
not key chains but up on the front desk

02:07.340 --> 02:09.630
here is one page , front and back

02:09.880 --> 02:13.220
unclassified placemat for the

02:13.230 --> 02:15.286
operational imperatives kind of lays

02:15.286 --> 02:17.530
out the situation . The challenge in

02:17.530 --> 02:19.560
the approach for each of the seven

02:19.560 --> 02:21.727
operational imperatives so might be of

02:21.727 --> 02:25.030
interest . So

02:25.040 --> 02:28.970
why why do we care ? Why are we

02:28.980 --> 02:31.202
going to this effort on the operational

02:31.202 --> 02:33.370
imperatives ? And as as you've heard

02:33.370 --> 02:35.910
over the last several days , both in W .

02:35.910 --> 02:38.870
D . I . And El CID uh it's because of

02:38.870 --> 02:41.037
the threat that's out there . The peer

02:41.037 --> 02:43.680
adversary that we're facing continues

02:43.680 --> 02:46.730
to increase range of their weapons ,

02:46.740 --> 02:49.530
lethality of their weapons , capacity

02:49.530 --> 02:52.460
of their weapons and most importantly

02:52.470 --> 02:56.420
in group uh the ability to achieve

02:56.420 --> 02:59.700
their wartime objectives regardless of

02:59.700 --> 03:03.060
what we do . That's the overall

03:03.060 --> 03:04.840
imperative if you will for the

03:04.840 --> 03:07.430
operational imperatives ? Uh So what is

03:07.430 --> 03:10.170
changing the risk is changing as we

03:10.170 --> 03:12.226
look at our peer adversaries , china

03:12.226 --> 03:14.710
and Russia . Uh they are we are

03:14.710 --> 03:17.110
increasing risk across the spectrum

03:17.110 --> 03:19.300
with them , we're increasing the risk

03:19.310 --> 03:22.720
uh of maintaining our space

03:22.720 --> 03:25.440
superiority , we're increasing the risk

03:25.440 --> 03:28.490
of being able to gather and mobilize

03:28.500 --> 03:31.150
and deploy forces where and when we

03:31.150 --> 03:34.260
need to , we're increasing risk

03:34.270 --> 03:37.680
uh to the ability to generate the

03:37.680 --> 03:39.791
number of combat sorties that we have

03:39.791 --> 03:42.520
to generate to deny their objectives .

03:44.480 --> 03:47.730
And we're increasing risk to getting to

03:47.740 --> 03:50.050
and fighting in that highly contested

03:50.050 --> 03:53.330
environment . Uh these risks are

03:53.340 --> 03:56.650
unacceptable because without facing and

03:56.660 --> 04:00.360
and surmounting those risk , we lose to

04:00.370 --> 04:03.330
dale whites point . Uh the reason we do

04:03.330 --> 04:06.880
this is to win , but what does winning

04:06.890 --> 04:08.890
look like ? We'll talk a little bit

04:08.890 --> 04:12.430
about that in detail . Uh but even

04:12.440 --> 04:15.930
winning is not a good thing . If you

04:15.930 --> 04:18.680
can imagine a cross Taiwan strait war

04:20.010 --> 04:23.110
uh when we win and prevent china's

04:23.110 --> 04:26.820
objectives of seizing Taiwan , we

04:26.820 --> 04:30.440
still lose carriers and other surface

04:30.440 --> 04:33.070
combatants and all the people on them .

04:34.110 --> 04:37.840
We still lose whole air bases and a

04:37.840 --> 04:40.950
good portion of the airmen on them .

04:41.620 --> 04:44.060
We lose army and marine corps fighting

04:44.060 --> 04:47.650
positions and the marines and soldiers

04:47.660 --> 04:50.320
on them . And that's a that's a that's

04:50.320 --> 04:53.740
a win . Okay , so and

04:53.750 --> 04:57.240
potentially decades of economic impact

04:57.240 --> 05:00.670
to the globe . That's a win . So more

05:00.670 --> 05:02.820
importantly , the force that wins in

05:02.820 --> 05:05.930
that environment is also the force that

05:05.940 --> 05:08.940
deters prior to any conflict .

05:09.840 --> 05:12.400
So if we wanna win , we also want to

05:12.400 --> 05:15.060
deter the force that wins is the force

05:15.060 --> 05:17.227
that deters and we would like to never

05:17.227 --> 05:19.449
have that fight . So every morning when

05:19.449 --> 05:21.560
President she gets up , we'd like him

05:21.560 --> 05:23.838
to open his curtains , look out and go ,

05:24.430 --> 05:27.730
not today and we want to continue that .

05:27.740 --> 05:29.796
And that's the sense of urgency that

05:29.796 --> 05:31.629
the sec gap has given us for the

05:31.629 --> 05:33.573
operational imperatives . It's the

05:33.573 --> 05:35.407
sense of urgency that we have to

05:35.407 --> 05:37.629
continue this capability development to

05:37.629 --> 05:39.740
get us to the force of the future and

05:39.740 --> 05:41.962
the Joint Force of the future . That is

05:41.962 --> 05:45.190
able to deter our peer adversaries and

05:45.190 --> 05:48.410
that and survive against that that uh

05:49.170 --> 05:50.281
increasing threat .

05:52.630 --> 05:55.190
So what are we doing about it ? You may

05:55.190 --> 05:57.190
have heard of the joint warfighting

05:57.190 --> 05:59.301
concept . Start out at one point . Oh

05:59.301 --> 06:01.468
now surprisingly enough we went to two

06:01.468 --> 06:03.634
point oh and we're actually working on

06:03.634 --> 06:06.040
the J . W . C . Three point oh that is

06:06.050 --> 06:08.960
directly uh

06:08.970 --> 06:12.090
focused on winning this pier fight

06:12.090 --> 06:14.290
specifically . And across the Taiwan

06:14.290 --> 06:17.980
strait fight , it's aligned with the

06:17.980 --> 06:20.070
national Defense strategy . It's

06:20.070 --> 06:22.348
aligned with defense planning guidance .

06:22.348 --> 06:25.650
All the joint services are aligned with

06:25.650 --> 06:28.190
that warfighting concept and that's key .

06:28.200 --> 06:30.590
Uh you can think back to air land

06:30.590 --> 06:32.980
battle and not everybody was maybe on

06:32.980 --> 06:36.140
board with a L . B . All the services

06:36.140 --> 06:38.362
are on board with the joint warfighting

06:38.362 --> 06:40.584
concept . It is where we are going . It

06:40.584 --> 06:42.807
is the future force we need and from an

06:42.807 --> 06:44.973
internal look to the air force side it

06:44.973 --> 06:48.060
is where our future force design is

06:48.060 --> 06:50.460
focused at getting to , it is where our

06:50.460 --> 06:53.340
Air Force future operating concept is

06:53.340 --> 06:56.060
focused on operating and how we get

06:56.070 --> 06:59.710
there underneath the

06:59.720 --> 07:02.320
joint warfighting concept is these four

07:02.320 --> 07:04.376
supporting concepts , we can go into

07:04.376 --> 07:06.520
them afterwards if you want more

07:06.520 --> 07:09.530
specifics uh with specific concept ,

07:09.530 --> 07:11.697
required capabilities . And as we look

07:11.697 --> 07:13.252
at those concept , required

07:13.252 --> 07:15.900
capabilities that are spelled out , we

07:15.900 --> 07:19.310
see where the gaps are . Those

07:19.310 --> 07:21.980
gaps from an Air Force perspective are

07:21.980 --> 07:24.980
exactly what the set gap looked at and

07:24.980 --> 07:27.140
said . These are the critical

07:27.150 --> 07:29.317
imperative gaps that we have to fill .

07:29.317 --> 07:31.690
Hence the operational imperatives . So

07:31.690 --> 07:34.350
that's where we got this first tranche

07:34.350 --> 07:36.730
of seven operational imperatives .

07:36.740 --> 07:39.430
Those are the critical gaps in the

07:39.430 --> 07:41.300
concept required capabilities to

07:41.300 --> 07:43.640
fulfill the Joint warfighting concept .

07:44.890 --> 07:48.720
So we've tested the hypothesis . We've

07:48.720 --> 07:52.090
tested the Future Force design to see

07:52.090 --> 07:55.770
if it actually wins in the J . W . C .

07:56.440 --> 07:59.580
Uh Future Games , 22 Future Games 23

07:59.580 --> 08:02.250
that'll be next january . Actually

08:02.250 --> 08:05.400
takes the Air Force Future Force Design

08:06.370 --> 08:10.010
war Games . It in a joint warfighting

08:10.010 --> 08:12.240
concept scenario against representative

08:12.250 --> 08:15.160
threats and sees how it does and what

08:15.160 --> 08:17.360
we need to tweak most recently this

08:17.360 --> 08:20.040
spring in May . General high note uh

08:20.050 --> 08:23.730
Air Force Futures Director uh lead

08:23.740 --> 08:25.684
the globally integrated war game ,

08:25.684 --> 08:29.430
which is a joint staff uh five ay . So

08:29.430 --> 08:32.560
with Allies and Partners war game , in

08:32.560 --> 08:34.990
that same warfighting scenario

08:36.400 --> 08:40.170
and we found that that Future Force and

08:40.170 --> 08:43.300
the Joint warfighting concept , when we

08:43.300 --> 08:47.060
are able to fight in all domain ,

08:48.300 --> 08:51.100
fight with our allies and partners

08:52.150 --> 08:54.560
winds in that scenario and prevents our

08:54.570 --> 08:56.630
adversaries uh , meeting their

08:56.630 --> 09:00.450
objectives . Key point

09:00.450 --> 09:02.630
there is that with our allies and

09:02.630 --> 09:04.852
partners . So we talked in the previous

09:04.852 --> 09:06.630
panel about the comparative the

09:06.630 --> 09:09.390
comparative advantage we have in

09:09.390 --> 09:11.920
propulsion . I would offer that one of

09:11.920 --> 09:14.031
the great comparative advantages that

09:14.031 --> 09:17.200
we have that our peer adversaries do

09:17.200 --> 09:20.070
not have is our allies and partners . I

09:20.070 --> 09:22.660
include in allies and partners . Our

09:22.670 --> 09:25.180
industry partners granted uh , they

09:25.180 --> 09:28.530
have a very uh tight coupling between

09:28.530 --> 09:30.700
their government and their industry .

09:30.710 --> 09:33.760
But I would say that the brain trust

09:33.760 --> 09:36.000
that we have an industry , the brain

09:36.000 --> 09:38.111
trust and the capability that we have

09:38.111 --> 09:40.830
within our allies and partners is and

09:40.830 --> 09:42.552
will be critical to the future

09:42.552 --> 09:43.719
warfighting effort .

09:48.640 --> 09:51.130
So given that

09:52.030 --> 09:54.380
capability gap analysis of the joint

09:54.380 --> 09:56.269
warfighting concept in the second

09:56.269 --> 09:59.820
direction , uh , the Oh , I started

09:59.820 --> 10:03.700
out as a sprint Important to

10:03.700 --> 10:06.250
note this was a sprint to figure out

10:06.260 --> 10:08.850
what we could get after in the end ,

10:08.860 --> 10:11.040
insert into the FY 24 pond .

10:12.340 --> 10:15.170
I could not agree more with all that's

10:15.170 --> 10:18.430
been said about this coupling between

10:18.430 --> 10:21.870
the acquisition professionals , the

10:21.870 --> 10:24.750
requirements professionals and the re

10:24.750 --> 10:27.070
sourcing professionals as well as

10:27.070 --> 10:28.820
industry to get after this .

10:30.230 --> 10:33.310
That's really what we do in capability

10:33.310 --> 10:35.480
development and what we need to

10:35.480 --> 10:37.770
continue to do is that that trinity

10:37.770 --> 10:40.570
between require ear's

10:40.580 --> 10:44.540
acquirers and resources has to continue

10:45.840 --> 10:47.840
Sprinkle over the top of that , the

10:47.840 --> 10:50.860
analytic rigor that uh staff studies

10:50.860 --> 10:52.749
and analysis brings and the other

10:52.749 --> 10:55.390
analytic branches in all the services

10:55.400 --> 10:58.440
and that helps us get after that force

10:58.440 --> 11:01.950
that we need uh

11:02.600 --> 11:05.770
the sprint nature of the o eyes

11:06.620 --> 11:10.530
While focused initially on the FY 24

11:10.530 --> 11:13.960
palm , we'll continue on . You'll see

11:13.970 --> 11:17.500
uh as palms get revealed , we've made a

11:17.500 --> 11:19.480
down payment on the operational

11:19.480 --> 11:21.360
imperatives but the operational

11:21.360 --> 11:23.850
imperative work itself will continue .

11:23.860 --> 11:27.690
It'll be folded in uh to multiple other

11:27.700 --> 11:29.810
capability , development planning

11:29.810 --> 11:32.032
efforts and we'll continue to do that .

11:33.130 --> 11:35.186
So let's talk a little bit about the

11:35.186 --> 11:37.408
operational imperatives themselves from

11:37.408 --> 11:40.210
an operational perspective . Next slide

11:40.210 --> 11:44.090
please . So on the

11:44.090 --> 11:46.610
chart kind of the one liners on what

11:46.610 --> 11:50.090
exactly is the title and the one liner

11:50.090 --> 11:51.757
for each of those operational

11:51.757 --> 11:53.868
imperatives . But let's talk a little

11:53.868 --> 11:55.812
bit about what that means . On the

11:55.812 --> 11:59.750
space side , we cannot afford

11:59.750 --> 12:02.470
in the future fight to lose control of

12:02.470 --> 12:06.100
space , we need to be able to bring

12:06.110 --> 12:10.020
effects to space from space and in

12:10.020 --> 12:13.920
space . We need position having timing

12:13.930 --> 12:16.740
capability , we need communications

12:16.740 --> 12:18.850
capability , we need data transport

12:18.860 --> 12:21.760
capability and we must have that as a

12:21.760 --> 12:24.150
joint enabler for the future war fight

12:24.160 --> 12:27.940
period on the A B . M . S .

12:27.940 --> 12:30.420
Advanced battle management system side ,

12:31.570 --> 12:35.380
this is a critical

12:35.380 --> 12:38.680
effort really . 234 even five if you

12:38.680 --> 12:40.902
will all kind of get lumped together in

12:40.902 --> 12:43.270
my mind is one big mosh pit of

12:43.280 --> 12:46.290
capability but

12:47.180 --> 12:49.180
A B . M . S itself is that critical

12:49.180 --> 12:52.600
ability to sense

12:54.180 --> 12:57.420
to make sense and to bring effects to

12:57.420 --> 12:59.642
the battle space at a time and place of

12:59.642 --> 13:00.642
our choosing .

13:03.590 --> 13:07.430
If you think back from uh post desert

13:07.430 --> 13:10.530
storm into and certainly post 9 11

13:10.540 --> 13:12.820
we've had the luxury in the counter ve .

13:12.820 --> 13:16.690
O fight to put exquisite I .

13:16.690 --> 13:19.680
S . Are up over potential targets

13:21.430 --> 13:24.470
orbit for hours , sometimes days pick

13:24.470 --> 13:27.400
up kind of life

13:27.410 --> 13:31.000
trends , specified targets .

13:31.010 --> 13:33.250
Talk about what would be the best

13:33.250 --> 13:35.250
shooter and the best weapon against

13:35.250 --> 13:38.180
that target and ultimately make a

13:38.180 --> 13:40.291
command and control decision . Yeah ,

13:40.291 --> 13:42.402
go ahead and smack that that target .

13:43.030 --> 13:45.030
We have to have a battle management

13:45.030 --> 13:47.990
system that can scale to thousands of

13:48.000 --> 13:51.110
targets in hundreds of

13:51.110 --> 13:54.940
hours , making near real time decisions

13:55.080 --> 13:58.290
and think if you will a battle

13:58.290 --> 14:00.150
management system that can take

14:00.160 --> 14:02.520
information from a space sensor ,

14:04.460 --> 14:07.100
get it down to an army long range fires

14:07.100 --> 14:11.070
shooter who fires a

14:11.070 --> 14:14.190
surface to surface missile that's now

14:14.190 --> 14:17.630
moving at hypersonic speeds . That gets

14:17.630 --> 14:19.880
an in flight target update from a

14:19.880 --> 14:22.420
marine corps fighter

14:24.690 --> 14:27.960
that then hits a target and we get real

14:27.960 --> 14:31.100
time battle damage assessment from some

14:31.100 --> 14:33.960
other weapon , Some other sensor in the

14:33.960 --> 14:36.700
battle space and that comes back to

14:36.700 --> 14:38.922
command and control authorities as well

14:38.922 --> 14:41.033
as the rest of the fleet so that they

14:41.033 --> 14:42.910
understand from a battle space

14:42.910 --> 14:45.270
situational awareness standpoint ,

14:45.280 --> 14:48.750
whether that threat is up , it's

14:48.750 --> 14:51.910
down , it's at least been rendered

14:51.920 --> 14:54.830
unfunny channel and then we can

14:54.830 --> 14:57.700
continue operations . So that is not a

14:57.700 --> 14:58.660
simple

15:01.020 --> 15:03.780
solution either from an architecture

15:03.780 --> 15:06.550
standpoint as general Janet tempo real

15:06.550 --> 15:10.340
knows very well knows uh or

15:10.350 --> 15:12.517
from a doctrinal standpoint . So think

15:12.517 --> 15:16.240
about for a minute , Who's doing the C2

15:16.450 --> 15:19.770
of that specific battle management ,

15:20.350 --> 15:24.090
who owns that space sensor ,

15:24.110 --> 15:27.310
that army shooter , that marine in

15:27.310 --> 15:30.130
flight target update er and the battle

15:30.130 --> 15:32.130
damage assessment capability on the

15:32.130 --> 15:34.560
back end of it . Uh this is not trivial

15:34.560 --> 15:38.350
and I think next to uh oh I five

15:38.360 --> 15:40.582
and based resiliency , this is probably

15:40.582 --> 15:42.870
our toughest nut to crack going forward

15:42.870 --> 15:45.680
will probably take us the longest to

15:45.680 --> 15:47.370
kind of morph up to that full

15:47.370 --> 15:51.290
capability . Next you've

15:51.290 --> 15:53.380
heard uh dale white talk about the

15:53.650 --> 15:55.706
family of systems and one of the key

15:55.706 --> 15:58.950
takes out of that is that we believe

15:58.950 --> 16:02.130
that uh collaborative combat platforms ,

16:02.140 --> 16:05.280
combat aircraft will be part of that

16:05.290 --> 16:07.512
family of systems to increase volume of

16:07.512 --> 16:11.230
fires to increase lethality and to

16:11.240 --> 16:13.930
increase effectiveness on the , on the

16:13.930 --> 16:17.550
battlefield . And we are working to

16:17.550 --> 16:20.460
develop and field those c C A S and we

16:20.460 --> 16:23.410
will continue uh to

16:23.410 --> 16:26.030
specify what that means

16:28.280 --> 16:30.590
and how it will be employed and again

16:30.590 --> 16:32.940
back to the kind of dot mil pf side of

16:32.940 --> 16:35.720
this , you know , while we have

16:35.810 --> 16:39.640
unscrewed platforms today we are going

16:39.640 --> 16:41.480
to be using them in a completely

16:41.480 --> 16:44.000
different fashion , which will require

16:44.000 --> 16:47.030
us to potentially organize differently ,

16:47.040 --> 16:49.530
certainly train differently , uh

16:49.540 --> 16:51.860
potentially deploy differently and

16:51.860 --> 16:55.620
certainly employ differently alongside

16:55.620 --> 16:57.787
us . We talked about battle management

16:57.787 --> 17:01.770
and uh the family systems

17:02.000 --> 17:05.830
inherit in those and in the uh

17:07.590 --> 17:09.960
and in the long range kill chain piece

17:09.960 --> 17:13.620
of the O . I . S . Is the weapons

17:13.620 --> 17:16.230
themselves . So by and large the

17:16.240 --> 17:19.120
weapons we are developing currently

17:19.140 --> 17:21.860
have the right capability we need

17:23.080 --> 17:25.920
there are some changes will make around

17:25.920 --> 17:27.642
the margins and some potential

17:27.642 --> 17:29.790
additions in terms of weapons but

17:29.800 --> 17:32.580
capacity will be critical to the future

17:32.580 --> 17:35.880
fight . And frankly uh we are not

17:35.890 --> 17:38.760
producing at capacity not near enough

17:38.760 --> 17:41.130
capacity for the future fight . And we

17:41.130 --> 17:44.810
must we must do that . We've

17:44.820 --> 17:47.740
flip flopped the oh I order from from

17:47.740 --> 17:49.880
this chart to where they sit number

17:49.880 --> 17:52.550
wise now but moving target engagement

17:52.560 --> 17:55.720
at scale uh is a critical piece and

17:55.720 --> 17:59.120
we've pasted out in the oh I

17:59.120 --> 18:01.620
work the mission engagement thread for

18:01.620 --> 18:04.590
the long range kill chain or kill web

18:04.600 --> 18:06.780
if you will . And where the critical

18:06.780 --> 18:10.060
gaps are in that long range chain . And

18:10.060 --> 18:13.860
are we are getting after that com

18:13.890 --> 18:16.740
data transport , sense and sense making

18:16.750 --> 18:19.100
are critical to those efforts as well .

18:21.950 --> 18:25.080
We'll also look at how we get moving

18:25.080 --> 18:28.010
target indications and how we actually

18:28.020 --> 18:31.330
uh maintain target custody over

18:31.330 --> 18:35.180
time uh in that battle

18:35.180 --> 18:38.050
space so that we can in fact track

18:38.050 --> 18:41.640
targets from the air or the

18:41.640 --> 18:45.600
surface potentially from space . Both

18:45.610 --> 18:48.960
moving uh surface targets as well as

18:48.960 --> 18:51.320
airborne targets uh and

18:52.380 --> 18:56.290
maintain combat I . D maintain

18:56.290 --> 19:00.030
custody of those targets to seeker with

19:01.110 --> 19:03.110
of whichever weapon we need to pair

19:03.110 --> 19:05.630
against those targets ? Uh That again

19:05.630 --> 19:08.200
is another tough nut to crack , but

19:08.200 --> 19:12.070
we're going after it , I'd

19:12.070 --> 19:14.460
say , I think Mr Hunter mentioned a

19:14.460 --> 19:17.590
little bit about any sensor , any

19:17.590 --> 19:19.757
shooter . And I would just refine that

19:19.757 --> 19:22.020
a smidge uh in the long range kill

19:22.020 --> 19:24.270
chain , It should be the right sensor

19:25.690 --> 19:28.450
to the right shooter , with the right

19:28.450 --> 19:31.240
weapon for that particular target .

19:32.610 --> 19:34.554
And that's what we're trying for .

19:34.554 --> 19:36.730
Think foremost in Secretary Kendall's

19:36.730 --> 19:39.080
mind . Uh , and probably his biggest

19:39.080 --> 19:41.040
concern is a resilient , basing

19:41.050 --> 19:43.050
sustainment and communications in a

19:43.050 --> 19:45.740
contestant environment . Uh That is one ,

19:45.740 --> 19:48.050
oh , I that is keeping him up at night .

19:48.060 --> 19:50.960
Uh , I think anybody who's ever

19:50.960 --> 19:53.620
deployed to a main operating base uh

19:53.630 --> 19:57.020
lived out of it went to their aircraft

19:57.020 --> 20:00.430
at the same spot every day , uh with

20:00.430 --> 20:03.120
the same weapons load barn with the

20:03.120 --> 20:06.430
same weapons and ammo dump with the

20:06.430 --> 20:10.050
same fuel supply areas ,

20:10.060 --> 20:12.930
uh , knows that that is a ripe target .

20:12.940 --> 20:16.260
Not you can get that target from google

20:16.260 --> 20:19.060
maps . Uh , so this is not a difficult

20:19.070 --> 20:21.790
targeting uh situation for our

20:21.790 --> 20:23.790
adversaries and one that we have to

20:23.810 --> 20:25.977
really have to think hard about . Part

20:25.977 --> 20:27.921
of this will be agile agile combat

20:27.921 --> 20:29.643
employment . So let's make the

20:29.643 --> 20:31.421
targeting of our adversary more

20:31.421 --> 20:33.366
difficult part of this will be pre

20:33.366 --> 20:35.700
positioning as we move out from hubs to

20:35.700 --> 20:38.020
spokes . Uh part of this will be pre

20:38.020 --> 20:40.090
positioning of assets . But what are

20:40.090 --> 20:41.979
the right things we need at those

20:41.979 --> 20:43.868
places ? How do we get it there ?

20:43.868 --> 20:46.580
Either before conflict or during

20:46.580 --> 20:48.820
conflict ? And what might not be highly

20:48.820 --> 20:50.598
contested but certainly will be

20:50.598 --> 20:54.390
contested airspace ? How do we resupply ?

20:54.580 --> 20:58.420
How do we infill an ex fil and and how

20:58.420 --> 21:01.190
do we continue ops and generate sorties ?

21:01.430 --> 21:03.870
That logistics under attack piece it

21:03.870 --> 21:07.830
must must occur right at

21:07.840 --> 21:09.840
those particular bases or any where

21:09.840 --> 21:11.562
we're located . In addition to

21:11.562 --> 21:14.110
preposition in addition to dispersion

21:14.120 --> 21:16.120
outside the base , we need to think

21:16.120 --> 21:18.231
about dispersion on base . We need to

21:18.231 --> 21:20.398
think about camouflage . Some of these

21:20.398 --> 21:22.620
old concepts that were second nature in

21:22.620 --> 21:25.500
the Cold War are now coming back camo

21:25.510 --> 21:28.440
deception and concealment . Those are

21:28.440 --> 21:30.607
gonna be part and parcel of the way we

21:30.607 --> 21:32.273
fight the war of the future .

21:34.640 --> 21:37.370
I'll talk now about the B21 , the

21:37.370 --> 21:39.480
family of systems . So initially we

21:39.480 --> 21:41.690
were kind of thinking that this would

21:41.700 --> 21:45.230
parallel uh and God and the family of

21:45.230 --> 21:48.520
systems . I think We've thought a

21:48.520 --> 21:50.742
little bit differently about this . And

21:50.742 --> 21:52.798
we're taking I'll say an operational

21:52.798 --> 21:54.964
pause on the family of systems . Piece

21:54.964 --> 21:58.110
of the B-21 were concentrated mostly on

21:58.120 --> 22:01.840
what is the right weapons Load for the

22:01.840 --> 22:03.951
B- 21 . What are the right effects we

22:03.951 --> 22:07.770
need and when actually will uh we need

22:07.770 --> 22:11.670
and how best to use the B- 21 . So that

22:11.680 --> 22:13.710
would be critical to us but we will

22:13.710 --> 22:16.420
need that ability to penetrate in the

22:16.420 --> 22:19.160
highly contested environment . We will

22:19.160 --> 22:21.700
need it to be survivable and we will

22:21.700 --> 22:23.867
need to bring volume of fires to those

22:23.867 --> 22:25.922
engagements . So we will continue it

22:26.830 --> 22:30.780
finally , Oi seven the readiness

22:30.780 --> 22:32.724
of the Department of the Air Force

22:32.724 --> 22:35.050
transition to a war wartime footing .

22:35.060 --> 22:38.700
Uh really with General Hawk as the

22:38.710 --> 22:42.520
lead uh worked a lot on the cyber

22:42.520 --> 22:44.742
side of that transition . And how do we

22:44.742 --> 22:48.010
protect our networks that mobilize and

22:48.010 --> 22:51.430
deploy uh and generate forces ? How do

22:51.430 --> 22:53.890
we get them in theater ? Uh , what we

22:53.890 --> 22:56.320
are now thinking about is whether we

22:56.330 --> 22:59.420
add on to oh I seven for the mobility

22:59.420 --> 23:02.510
piece and the air to air refueling side

23:02.510 --> 23:04.566
of this . So do we have the mobility

23:04.566 --> 23:06.566
forces we need , do we have the air

23:06.566 --> 23:09.110
refueling forces ? We need to be able

23:09.110 --> 23:11.277
to get into theater to be able to move

23:11.277 --> 23:13.310
around within theater to be able to

23:13.310 --> 23:16.780
sustain and supply the forces . And

23:16.780 --> 23:19.380
that's the joint forces , not just the

23:19.390 --> 23:22.730
air forces within theater . So that's

23:22.740 --> 23:25.500
uh , that's what we're looking at on Oi

23:25.510 --> 23:28.820
seven . You can see as as we've had

23:28.820 --> 23:30.930
this discussion

23:32.420 --> 23:36.370
that the common thread and you've seen

23:36.370 --> 23:38.640
it over the last several days . The

23:38.640 --> 23:40.251
common threads through these

23:40.251 --> 23:41.807
operational imperatives are

23:41.807 --> 23:45.260
communications , networking and

23:45.260 --> 23:48.850
logistics . So either during

23:49.090 --> 23:52.440
competition and certainly during

23:52.440 --> 23:56.090
conflict , we will need to be able to

23:56.090 --> 23:59.560
command and control from Conus

24:00.270 --> 24:02.300
as we start to generate forces . We

24:02.300 --> 24:04.244
will need to be able to see to the

24:04.244 --> 24:06.356
forces as they move into theater . We

24:06.356 --> 24:08.356
will need to be able to command and

24:08.356 --> 24:10.578
control the forces as a disperse within

24:10.578 --> 24:12.744
theater . Uh We will certainly need to

24:12.744 --> 24:15.150
be able to see two as we move into the

24:15.150 --> 24:18.660
area of operations and uh deny enemy

24:18.660 --> 24:21.540
objectives uh saying a cross strait

24:21.540 --> 24:25.020
invasion . And we will

24:25.020 --> 24:28.660
need the networks uh that allow us to

24:28.660 --> 24:31.720
do that . The data links that allow us

24:31.720 --> 24:35.650
to move information not just too crude

24:35.650 --> 24:39.580
and unscrewed platforms to command and

24:39.580 --> 24:42.470
control platforms back to the main

24:42.470 --> 24:44.526
operating bases to forward operating

24:44.526 --> 24:47.920
bases , to army fires positions

24:47.930 --> 24:51.870
to uh marine uh expeditionary

24:51.880 --> 24:55.690
operations positions uh to invite

24:55.690 --> 24:58.450
targeting weapons in flight and then

24:58.460 --> 25:01.080
drawing what information we can as

25:01.090 --> 25:03.620
battle damage assessment Uh from

25:03.620 --> 25:07.230
whatever uh sensor in theater we

25:07.230 --> 25:09.260
can and bring it back to the C2 .

25:11.130 --> 25:13.220
All of those communications and

25:13.220 --> 25:17.060
networks need to be built .

25:18.050 --> 25:21.960
Uh It is not gonna come at uh we're

25:21.960 --> 25:24.016
not gonna wake up one morning and go

25:24.016 --> 25:26.071
hey everything we have is in place .

25:26.071 --> 25:28.238
We're good to go . We will be building

25:28.238 --> 25:30.850
on that throughout The sense of urgency

25:30.850 --> 25:33.320
that general white talked about uh to

25:33.320 --> 25:37.190
me means this isn't uh hey we

25:37.190 --> 25:39.301
just need to have something out there

25:39.301 --> 25:42.550
by 2030 . Uh this is we need to be

25:42.550 --> 25:46.030
ready tomorrow . So if I'm a fighter

25:46.030 --> 25:48.880
wing commander today , my forces need

25:48.880 --> 25:51.600
to be ready to deploy tomorrow .

25:52.580 --> 25:55.830
We as requirements

25:55.840 --> 25:58.590
professionals , you as industry and

25:58.590 --> 26:00.300
acquisition professionals ,

26:00.310 --> 26:03.100
logisticians . You need to be ready to

26:03.100 --> 26:05.810
go tomorrow . We need to be able to

26:05.810 --> 26:08.040
build to the best capability that we

26:08.040 --> 26:11.840
can uh in this next few years

26:11.850 --> 26:15.290
and then continue to work through

26:15.290 --> 26:18.530
those capability development plans ,

26:18.530 --> 26:21.760
those roadmaps via acquisition

26:21.760 --> 26:23.482
strategies and the appropriate

26:23.482 --> 26:25.570
requirements , documentation and

26:25.570 --> 26:28.560
certainly the correct re sourcing

26:29.610 --> 26:31.721
to get us to the future force that we

26:31.721 --> 26:33.832
need that actually fights and wins in

26:33.832 --> 26:34.943
that battle space .

26:37.560 --> 26:40.980
So , uh , lastly I'll comment

26:40.990 --> 26:43.390
on what are the O . I . S and maybe

26:43.390 --> 26:46.230
what maybe more importantly what the oh

26:46.230 --> 26:49.960
eyes are not right . The end , I'll

26:49.960 --> 26:52.240
reiterate the OS for a short sprint

26:52.330 --> 26:56.250
initially to get to fy 20 for

26:56.250 --> 26:58.250
palm solution , particularly in the

26:58.250 --> 27:01.010
near years . What they morphed into and

27:01.010 --> 27:03.960
what they will continue to be is a long

27:03.960 --> 27:06.580
term capability development planning

27:06.590 --> 27:10.440
iteration on where are we today and

27:10.440 --> 27:12.440
where do we need to get to in the

27:12.440 --> 27:16.130
future ? And what can we do right now .

27:16.140 --> 27:19.650
So that again , every morning when

27:19.650 --> 27:21.706
President she wakes up and opens his

27:21.706 --> 27:25.550
curtains . Not today . Today's

27:25.550 --> 27:26.240
not the day

27:30.240 --> 27:32.850
there is obviously along those lines ,

27:32.860 --> 27:35.670
a lot of work to do what you'll see in

27:35.670 --> 27:38.130
24 is a down payment on some of these

27:38.130 --> 27:40.450
will continue to work at . Obviously we

27:40.450 --> 27:42.617
don't even have the fy 23 budget yet .

27:42.617 --> 27:45.540
So that will affect the near term that

27:45.540 --> 27:47.762
will then affect what actually is going

27:47.762 --> 27:50.230
to happen in 24 to 27 . So we will

27:50.230 --> 27:52.920
continue to iterate on these capability

27:52.920 --> 27:55.130
development plans to get to the force

27:55.130 --> 27:57.570
that we need and so we will all have to

27:57.570 --> 27:59.737
breathe through our noses for a couple

27:59.737 --> 28:02.950
more months , maybe several more months

28:02.960 --> 28:06.570
uh maybe until early spring before we

28:06.570 --> 28:09.050
even know what FY 23 budget actually

28:09.050 --> 28:10.883
looks like . So that will ripple

28:10.883 --> 28:13.550
through all of this . The enemy gets a

28:13.550 --> 28:16.500
vote , the threat will change , we will

28:16.500 --> 28:18.722
continue to iterate on these capability

28:18.722 --> 28:20.889
development plans . But one thing I do

28:20.889 --> 28:24.810
know is as quickly as we can , we need

28:24.810 --> 28:27.032
to get capability into the hands of the

28:27.032 --> 28:29.120
Joint Warfighter and then be able to

28:29.130 --> 28:32.800
iterate and modernize

28:33.030 --> 28:35.820
and improve that capability to get out

28:36.380 --> 28:38.790
to the full capability that they need

28:38.800 --> 28:41.840
to fight that fight . So

28:41.850 --> 28:45.140
what the oh eyes are not , they're not

28:45.140 --> 28:48.010
the whole picture . Okay . You can't

28:48.010 --> 28:50.810
say , hey , we funded all seven

28:50.810 --> 28:53.200
operationalize their fully funded life

28:53.200 --> 28:55.367
is good . We don't need to do anything

28:55.367 --> 28:58.790
else . There are a ton of other concept

28:58.790 --> 29:01.330
required capabilities and foundational

29:01.330 --> 29:04.180
capabilities that both the Air Force

29:04.190 --> 29:07.180
Space Force and the Joint Force need

29:07.200 --> 29:09.280
that are not nested inside the

29:09.280 --> 29:11.447
operational imperatives . So there's a

29:11.447 --> 29:13.613
whole other part of the Air Force that

29:13.613 --> 29:15.447
still needs to be funded . Think

29:15.447 --> 29:17.669
weapons systems sustainment , think the

29:17.669 --> 29:19.558
flying our program think test and

29:19.558 --> 29:22.960
evaluation . All of that still has to

29:22.960 --> 29:26.880
get both funded and planned so that it

29:26.880 --> 29:29.580
marches in pace with the specific

29:29.580 --> 29:31.802
efforts of the operational imperative .

29:32.910 --> 29:36.230
It's also I think as we've talked about

29:36.240 --> 29:38.200
uh not a one and done so the

29:38.200 --> 29:40.311
operational imperatives are not a one

29:40.311 --> 29:42.660
and done again once I get them funded ,

29:42.670 --> 29:44.448
life is good . These are living

29:44.448 --> 29:46.670
documents that will continue to develop

29:46.670 --> 29:48.726
those capability development plans .

29:49.800 --> 29:52.022
Lastly , I'd like to finish up and then

29:52.022 --> 29:54.022
get into questions with a couple of

29:54.022 --> 29:56.640
thoughts on lessons learned from the

29:56.650 --> 29:59.900
operational imperative uh sprint so far

29:59.900 --> 30:03.750
and the ongoing work I

30:03.760 --> 30:07.640
talked earlier uh about the criticality

30:07.650 --> 30:09.910
of our allies and partners and actually

30:09.910 --> 30:12.920
that discussion during the oh eyes has

30:12.920 --> 30:16.450
spawned a lot of conversation on wow .

30:16.460 --> 30:19.660
Wouldn't it be good if we could bring

30:19.660 --> 30:22.440
the allies and partners into this

30:22.450 --> 30:24.810
classified discussion , see what they

30:24.810 --> 30:27.060
can offer in that space , See what

30:27.060 --> 30:30.470
they're bringing to the war fight and

30:30.480 --> 30:33.960
increase the overall joint force and

30:33.960 --> 30:36.710
coalition force capability . The good

30:36.710 --> 30:39.830
news is from a security standpoint . Uh

30:39.840 --> 30:43.810
We have uh broken down some doors , not

30:43.820 --> 30:45.876
all the doors , there are still some

30:45.876 --> 30:47.876
doors in the castle that need to be

30:47.876 --> 30:49.876
broken down . But we've broken down

30:49.876 --> 30:49.640
some of those security doors and

30:49.640 --> 30:52.530
started getting uh the ability to have

30:52.530 --> 30:55.540
higher level conversations both within

30:55.540 --> 30:58.040
the services and Department of Defense ,

30:58.050 --> 31:00.870
external the Department of Defense as

31:00.870 --> 31:03.340
well as with our industry partners . Uh

31:03.350 --> 31:05.560
to have more fulsome conversations

31:05.570 --> 31:08.870
about what we need when we need it and

31:08.880 --> 31:10.102
how do we get there ,

31:13.170 --> 31:15.270
one of the big lessons learned that

31:15.270 --> 31:17.103
we've got out of the operational

31:17.103 --> 31:19.214
imperatives and we've talked about it

31:19.214 --> 31:21.610
and multiple panels already is that

31:21.620 --> 31:24.080
collaboration is critical ,

31:24.090 --> 31:26.201
collaboration within the department ,

31:26.201 --> 31:27.868
collaboration with industry ,

31:27.868 --> 31:30.990
collaboration with the require urz the

31:31.000 --> 31:33.310
acquirers and the resources is is

31:33.310 --> 31:36.120
critical and even collaboration between

31:36.120 --> 31:38.231
the operational imperatives . So what

31:38.231 --> 31:41.680
we saw as the seven Oi teams scattered

31:41.680 --> 31:44.040
out and did their collaboration when we

31:44.040 --> 31:46.290
first brought the seven Oi teams back

31:46.290 --> 31:50.140
in for briefing , uh some of them were

31:50.140 --> 31:53.000
working on exactly the same things , so

31:53.000 --> 31:55.222
there's goodness there , so everybody's

31:55.222 --> 31:57.333
at least thinking alike , but there's

31:57.333 --> 31:59.500
some redundancy of effort that we need

31:59.500 --> 32:02.230
to prevent and and so that there was

32:02.230 --> 32:05.720
goodness to see that okay , we still

32:05.720 --> 32:07.942
have a gap and a seam over here between

32:07.942 --> 32:09.776
these oh eyes , but you guys are

32:09.776 --> 32:11.887
already working on closing that gap .

32:11.887 --> 32:14.053
That's good . But they're also working

32:14.053 --> 32:16.276
on closing that gap . Stop doing this ,

32:16.276 --> 32:18.053
let them work on that . So that

32:18.053 --> 32:19.800
collaboration is key . It is a

32:19.800 --> 32:21.856
beautiful thing . If you think about

32:21.856 --> 32:25.710
that Venn diagram of the acquirers ,

32:25.720 --> 32:29.160
the require ear's and the resources ,

32:29.270 --> 32:31.830
you know , the more and more that we

32:31.830 --> 32:33.970
can bring that Venn diagram into a

32:33.970 --> 32:36.940
single cylinder of excellence , uh the

32:36.940 --> 32:39.390
better off , we'll be again Sprinkle

32:39.390 --> 32:41.390
over the top of that , the analytic

32:41.390 --> 32:43.501
capability that we need Sprinkle into

32:43.501 --> 32:45.612
that the solutions that industry will

32:45.612 --> 32:48.470
provide and and we are onto something

32:48.470 --> 32:51.640
that will bring us success So that to

32:51.640 --> 32:53.340
me is very exciting .

32:55.640 --> 32:58.630
And then lastly I'll just touch base on

32:58.640 --> 33:00.980
so you know what's next ? I don't I

33:00.980 --> 33:03.260
don't know . I imagine we'll use the

33:03.260 --> 33:05.780
term operational imperative for quite a

33:05.780 --> 33:09.000
while to come . I think as I mentioned

33:09.000 --> 33:12.350
we'll bring mobility in to the O eyes

33:12.370 --> 33:15.030
either as a separate Oi or in addition

33:15.030 --> 33:18.930
to an add on to oh I seven . Uh we've

33:18.940 --> 33:21.100
already had as mentioned before the

33:21.110 --> 33:23.550
missionary reviews with the secretary .

33:23.560 --> 33:26.370
Maybe E . W . Becomes its own Oi or it

33:26.370 --> 33:30.370
stays as a missionary review . Uh two

33:30.370 --> 33:34.340
simple me doesn't really matter what

33:34.340 --> 33:36.118
matters is that we continue the

33:36.118 --> 33:38.173
collaboration and the discussion and

33:38.173 --> 33:41.060
the conversation and the hard work to

33:41.060 --> 33:43.060
build those capability development

33:43.060 --> 33:46.700
plans to build those road maps that

33:46.700 --> 33:48.970
take us from today

33:50.910 --> 33:53.670
With getting capability in the hands of

33:53.670 --> 33:55.614
the joint warfighter as quickly as

33:55.614 --> 33:57.920
possible and then spiraling out of that

33:57.930 --> 34:00.340
into the full capability that we need

34:00.350 --> 34:03.860
later in this decade and into the 2030s .

34:03.870 --> 34:07.810
And that will be success . That is

34:07.810 --> 34:11.350
what winning is about with that .

34:12.200 --> 34:14.256
I would love to answer any questions

34:14.256 --> 34:15.256
that you have

34:20.480 --> 34:21.310
none . Okay ,

34:37.080 --> 34:40.550
thank sir , thank you for your comments .

34:41.550 --> 34:44.890
Ed Jesperson Lockheed martin recently

34:45.100 --> 34:49.090
Secretary hicks conveyed in a memo ,

34:49.090 --> 34:52.200
the uh executive responsibility for air

34:52.200 --> 34:54.256
base defense slight modification . I

34:54.256 --> 34:56.367
was wondering if you could comment on

34:56.367 --> 34:59.120
that as it relates to Oi five an air

34:59.120 --> 35:01.342
base defense . So are you talking about

35:01.342 --> 35:04.210
the secretary's acquisition authority

35:04.210 --> 35:08.010
bestowed on the Air Force for uh cruise

35:08.010 --> 35:10.232
missile defense of the homeland ? Yes .

35:10.232 --> 35:12.454
Okay thanks . Uh No I'm sorry . I can't

35:12.454 --> 35:16.320
comment . I know I can . No no nothing

35:16.320 --> 35:19.410
about it . So uh that is , I'll say

35:19.410 --> 35:22.560
philosophically uh that is probably

35:22.560 --> 35:25.580
step one uh is the acquisition

35:25.580 --> 35:27.802
authority for cruise missile defense of

35:27.802 --> 35:29.969
the homeland . Uh We are now obviously

35:29.969 --> 35:32.420
just starting to go , okay . How does

35:32.430 --> 35:36.420
uh how does A q

35:36.430 --> 35:38.640
get their arms around all the service

35:38.650 --> 35:40.761
efforts ? And and when you're talking

35:40.761 --> 35:42.761
about cruise missile defense of the

35:42.761 --> 35:44.817
homeland ? It's not just D . O . D .

35:44.817 --> 35:46.928
It's really whole of government . How

35:46.928 --> 35:48.983
do they get their arms around all of

35:48.983 --> 35:50.983
that acquisition effort ? So that's

35:50.983 --> 35:53.170
that work is ongoing . I would say the

35:53.180 --> 35:56.380
next logical step would be

35:57.760 --> 36:01.720
Acquisition Authority is one thing . Uh

36:01.730 --> 36:05.490
Do we want uh an executive agent

36:06.550 --> 36:10.280
for the operational izing of cruise

36:10.280 --> 36:12.860
missile defense of the homeland . Uh

36:12.870 --> 36:15.092
And I think that will be a conversation

36:15.092 --> 36:17.790
that will be brought up uh at the joint

36:17.790 --> 36:20.012
requirements oversight council with the

36:20.012 --> 36:22.130
Vice Chiefs and the vice chairman uh

36:22.140 --> 36:24.690
and probably soon to accompany that

36:24.690 --> 36:27.100
acquisition authority . Clearly NORAD

36:27.100 --> 36:29.620
North com has kind of the c two of the

36:29.620 --> 36:32.500
actual execution but there's gonna need

36:32.500 --> 36:36.080
to be in a dot mil pf organizing . How

36:36.080 --> 36:39.620
do we get from just the acquisition of

36:39.620 --> 36:43.480
capability to the dot

36:43.480 --> 36:46.420
mil pF side of how we're gonna organize

36:46.420 --> 36:49.700
train and equip to use that capability

36:49.740 --> 36:51.980
to hand it over the combatant commander

36:52.000 --> 36:54.111
to execute that capability . So those

36:54.111 --> 36:56.111
are the conversations I think we're

36:56.111 --> 37:00.070
gonna , we're gonna have now . I

37:00.270 --> 37:03.970
am very optimistic that as we

37:03.980 --> 37:05.980
define solutions for cruise missile

37:05.980 --> 37:08.360
defense of the homeland , that we will

37:08.360 --> 37:11.220
transport those solutions to base

37:11.220 --> 37:13.620
defense and you know , oh I five and

37:13.620 --> 37:15.830
how that morphs into the future force

37:16.350 --> 37:18.900
but it will be critical . Thank you for

37:18.900 --> 37:19.900
that question .

37:33.080 --> 37:36.590
That's quite question . Good afternoon ,

37:36.590 --> 37:38.730
sir . So , uh just to talk about your

37:38.730 --> 37:40.786
agile combat employment , my name is

37:40.786 --> 37:42.730
rick with Floor Corporation . Uh ,

37:42.730 --> 37:44.640
we're one of your contractors on

37:44.650 --> 37:46.730
several of the contract augmentation

37:46.730 --> 37:49.680
programs have catalog cab so

37:50.020 --> 37:53.090
also having been a civil engineer in

37:53.090 --> 37:56.290
the Air Force growing up during the the

37:56.290 --> 37:58.290
Cold War . And I remember the salty

37:58.290 --> 38:01.110
demo results for those of you are

38:01.120 --> 38:03.310
really old and can look that one up .

38:03.320 --> 38:06.700
Uh but where do you see industry

38:06.710 --> 38:09.450
playing into this and how we're going

38:09.450 --> 38:12.100
to move forward on getting these

38:12.100 --> 38:14.850
resilient bases . These outlying island

38:14.850 --> 38:16.850
hopping campaign as it as it were .

38:17.870 --> 38:19.870
Yeah . So thanks for the question .

38:19.870 --> 38:23.410
That's a that's a great one . which of

38:23.410 --> 38:26.300
course is speaker parlance for give me

38:26.300 --> 38:28.300
a second to think about my answer .

38:28.300 --> 38:32.200
Right , So I'll hit that in in

38:32.200 --> 38:34.256
several areas , you know , since you

38:34.256 --> 38:36.144
mentioned uh ce ce side of this ?

38:36.144 --> 38:38.500
Certainly there's a milk on element to

38:38.510 --> 38:41.300
base resiliency . Can I build extra

38:41.300 --> 38:43.710
runways ? Can I build runways that we

38:43.710 --> 38:45.821
can drop into that aren't necessarily

38:45.821 --> 38:48.260
fobs or mobs but we can drop in their

38:48.270 --> 38:51.200
gas up . How do I propose fuel weapons

38:51.200 --> 38:53.200
there etcetera ? So there's there's

38:53.200 --> 38:55.340
kind of that piece

38:56.680 --> 39:00.290
uh there is a base defense piece to

39:00.290 --> 39:03.090
this and certain systems that would

39:03.100 --> 39:06.230
either uh you know for a long time .

39:06.230 --> 39:08.452
We've talked about base defenses either

39:08.452 --> 39:10.508
inside the wire outside the wire and

39:10.508 --> 39:13.500
that distinction has blurred

39:14.130 --> 39:16.820
even as we're in Afghanistan and now is

39:16.830 --> 39:19.870
is not just blurred but kind of pushed

39:19.870 --> 39:21.981
off the map . So we will have to have

39:21.981 --> 39:24.640
that doctrinal discussion within the

39:24.640 --> 39:26.650
Department of Defense on who's

39:26.650 --> 39:28.650
responsible for what and how are we

39:28.650 --> 39:30.706
getting after ? It ? Certainly as we

39:30.706 --> 39:33.500
get into uh a cruise missile defense of

39:33.500 --> 39:35.500
the homeland , that might enlighten

39:35.500 --> 39:37.667
some of those conversations . But what

39:37.667 --> 39:39.778
does based defense of the future look

39:39.778 --> 39:42.510
like what our dispersal capabilities

39:42.520 --> 39:44.464
that are gonna be out there in the

39:44.464 --> 39:46.798
future ? Is there a place in the future .

39:46.798 --> 39:50.760
Force for uh platforms

39:50.770 --> 39:53.650
that are don't require 8000 ft of

39:53.650 --> 39:57.380
concrete . So things like high

39:57.380 --> 40:00.620
speed vertical takeoff and land uh E

40:00.620 --> 40:04.450
vitale both from a combat capability

40:04.450 --> 40:08.110
standpoint and or uh the

40:08.110 --> 40:11.850
ability to resupply infill ex fil

40:11.860 --> 40:15.430
uh and sustain the forces in the field

40:15.440 --> 40:17.720
again inside of the second island chain

40:17.720 --> 40:19.980
in a contested environment . So you may

40:19.980 --> 40:23.170
see things like that . And certainly uh

40:23.180 --> 40:25.570
we've been talking a lot about that

40:25.580 --> 40:29.150
capability . I think the answer is , is

40:29.160 --> 40:32.570
all of that . In addition to material

40:32.570 --> 40:35.660
and non material solutions for camo

40:35.660 --> 40:39.380
concealment , dispersion hardened , uh ,

40:39.390 --> 40:41.750
hardening of bases that we currently

40:41.750 --> 40:43.917
have . Hardening of bases that we need

40:43.917 --> 40:46.180
to have and concepts of employment .

40:46.190 --> 40:48.300
Good news is the major commands both

40:48.300 --> 40:51.690
you safety and and uh uh in

40:51.700 --> 40:54.830
particular as well as Air combat

40:54.830 --> 40:56.774
command who is kind of showing the

40:56.774 --> 40:59.230
effort and kind of collating all of the

40:59.230 --> 41:01.790
thoughts from the the theater

41:01.800 --> 41:05.050
commanders on the Agile Combat

41:05.050 --> 41:08.720
Employment Con Ops uh , we're starting

41:08.720 --> 41:11.640
to hover on solutions that have a

41:11.650 --> 41:14.010
common centerpiece if you will of this

41:14.010 --> 41:16.930
is uh , this is the the agile Combat

41:16.930 --> 41:19.520
Employment kind of centerpiece with

41:19.530 --> 41:23.370
regional specificity for both . Pack

41:23.370 --> 41:25.710
off because different problem for pac

41:25.710 --> 41:28.380
calf certainly than it is for us Air

41:28.380 --> 41:30.650
forces in europe . So they'll have

41:30.660 --> 41:34.600
their own uh spice if you will on

41:34.610 --> 41:37.450
on a space . Uh and that's kind of

41:37.450 --> 41:39.394
where we're at where we're going .

41:39.740 --> 41:41.907
Hopefully that answers your question ,

41:43.430 --> 41:47.350
which is speaker parlance for that

41:47.350 --> 41:51.110
wraps me up . I

41:51.110 --> 41:53.110
think I had a hand up in the back ,

41:53.110 --> 41:56.790
nope , she's waving off anything else

41:57.470 --> 42:01.430
I will be around . So if you've got any

42:01.430 --> 42:03.910
other questions , comments , happy to

42:03.920 --> 42:05.960
feel them down here after . I don't

42:05.960 --> 42:08.110
have to leave for a flight for uh

42:08.120 --> 42:10.810
sometime so happy to chat later . Thank

42:10.810 --> 42:12.588
you for your attention , really

42:12.588 --> 42:14.866
appreciate it . Again , General Morris ,

42:14.866 --> 42:14.940
thank you so much for the invitation .

