WEBVTT

00:11.279 --> 00:14.140
Good afternoon everybody um . You know

00:14.140 --> 00:16.307
we're here to talk about the future of

00:16.307 --> 00:18.473
the Kim Bio Defense program and one of

00:18.473 --> 00:20.700
the things that we were really trying

00:20.700 --> 00:23.059
to do is to find some enduring

00:23.059 --> 00:25.700
objectives because one of the things

00:25.700 --> 00:29.020
going out into the community I kept

00:29.020 --> 00:30.964
hearing is that what we were going

00:30.964 --> 00:33.700
after was changing so frequently , you

00:33.700 --> 00:36.279
know , we're not being consistent . In

00:36.279 --> 00:39.880
going after things , we're ping ponging

00:39.880 --> 00:41.824
back year to year . It's making it

00:41.824 --> 00:43.991
difficult for folks to make objectives

00:43.991 --> 00:46.158
because they didn't know what problems

00:46.158 --> 00:48.439
we were trying to solve . So we worked

00:48.439 --> 00:51.319
together , really , really well as a

00:51.319 --> 00:53.950
community to develop some S&T

00:53.950 --> 00:56.439
objectives that define where we're

00:56.439 --> 00:58.550
going to go for the next 3 to 5 years

00:58.550 --> 01:01.049
at a minimum . And then we also have

01:01.049 --> 01:04.559
some . A longer term things trying to

01:04.559 --> 01:06.670
define what to call them , whether we

01:06.670 --> 01:08.781
call them moonshots or guiding lights

01:08.781 --> 01:11.839
or Uh , forward investment ,

01:12.699 --> 01:15.720
FIFA , you know , focus areas , um ,

01:16.129 --> 01:18.462
but really , you know , we're trying to ,

01:18.462 --> 01:21.930
to give you guys some understanding of

01:21.930 --> 01:24.041
where we're going and why we're going

01:24.041 --> 01:26.809
there , um , not for us to , you know ,

01:26.930 --> 01:29.980
define what you guys are doing and what

01:29.989 --> 01:32.322
what industry and academia brings to us .

01:32.449 --> 01:35.500
But So you guys can understand and

01:35.500 --> 01:37.667
innovate in these spaces and then come

01:37.667 --> 01:39.970
back to us with solutions , not with

01:39.970 --> 01:42.889
technologies , so . Where we're going ,

01:43.089 --> 01:45.879
um , I , I gave a very brief , uh ,

01:45.889 --> 01:48.650
overview of the general areas , but the ,

01:48.690 --> 01:51.050
the S&T objectives , the 6 of them ,

01:51.250 --> 01:53.417
and I'm gonna read them so I don't get

01:53.417 --> 01:55.610
them wrong , um , yeah , I should have

01:55.610 --> 01:57.666
them memorized , but you know how it

01:57.666 --> 01:59.943
goes . It's been a long week . So , um ,

02:00.489 --> 02:02.156
accelerating the chemical and

02:02.156 --> 02:04.129
biological threat characterization

02:04.129 --> 02:08.000
pipeline , so how fast we can

02:08.009 --> 02:10.360
can characterize the threat . So that

02:10.360 --> 02:12.193
way we can understand what we're

02:12.193 --> 02:14.249
getting after and come up with those

02:14.249 --> 02:16.559
solutions , enhancing early hazard

02:16.559 --> 02:20.250
awareness for the total force . Novel

02:20.250 --> 02:22.570
percutaneous protection materials for

02:22.570 --> 02:26.039
CB environments . Developing advanced

02:26.039 --> 02:28.399
respiratory and ocular protection .

02:31.309 --> 02:33.679
Sustainable contamination mitigation

02:33.679 --> 02:36.589
for in theater forces . And medical

02:36.589 --> 02:38.645
countermeasure development and rapid

02:38.645 --> 02:42.229
deployment . So that's , that's , that

02:42.229 --> 02:44.451
is where we are going for the next 3 to

02:44.451 --> 02:47.059
5 years . That is , those are the 6

02:47.059 --> 02:49.449
areas that we are looking for you all

02:49.449 --> 02:53.270
to help us solve , so we

02:53.270 --> 02:56.470
can enable our warfighters to win in

02:56.470 --> 02:59.699
any environment . So I mean

03:00.559 --> 03:02.559
as the Kim biodefense program and I

03:02.559 --> 03:04.670
kind of mentioned on the first day as

03:04.670 --> 03:06.781
we try to make sure that we're making

03:06.781 --> 03:09.003
top down strategic overall alignment to

03:09.003 --> 03:11.170
the national defense strategy and also

03:11.170 --> 03:13.337
the joint war fighting concept and how

03:13.337 --> 03:15.503
operational concepts are being updated

03:15.503 --> 03:17.670
with our warfighter , it was important

03:17.670 --> 03:19.448
working with JSTO leadership to

03:19.448 --> 03:21.781
establish these goals for a few reasons ,

03:21.781 --> 03:23.670
and they do a couple as we try to

03:23.670 --> 03:25.615
orient our program to deliver more

03:25.615 --> 03:27.948
rapidly the capability that is deserved .

03:28.240 --> 03:31.279
One and it sets it sets some some

03:31.279 --> 03:33.699
consistency over time with our industry

03:33.699 --> 03:35.810
and academic partners about where our

03:35.810 --> 03:38.032
focus is going to be and it's not going

03:38.032 --> 03:39.755
to waiver from year to year on

03:39.755 --> 03:41.755
prioritization or one to end list .

03:41.755 --> 03:43.588
These are the areas in which the

03:43.588 --> 03:45.588
leadership and governance and as we

03:45.588 --> 03:47.810
look at the biodefense posture review ,

03:47.810 --> 03:49.643
that's not and also let's not be

03:49.643 --> 03:52.199
exclusive of of uh of chemical across

03:52.199 --> 03:54.255
our entire portfolio is important to

03:54.255 --> 03:56.820
get these set . So that you know where

03:56.820 --> 03:58.653
we're going to be putting larger

03:58.653 --> 04:00.598
buckets of funding and where we're

04:00.598 --> 04:02.764
going to be putting our emphasis , and

04:02.764 --> 04:04.653
that means multiple shots on goal

04:04.653 --> 04:06.709
across these areas because these are

04:06.709 --> 04:08.876
the ones that need to accelerate , not

04:08.876 --> 04:10.820
just on the next iteration of what

04:10.820 --> 04:12.876
we're doing , but how we're actually

04:12.876 --> 04:15.042
reaching into the modernization that's

04:15.042 --> 04:17.264
required by our by our joint warfighter

04:17.264 --> 04:19.489
and all . 2 , it also helps us to align

04:19.489 --> 04:21.540
in the past for Kim Bo defense . We

04:21.540 --> 04:23.651
haven't done a tremendously great job

04:23.651 --> 04:26.119
of S&T . Actually informing

04:26.119 --> 04:28.286
requirements , development and stuff ,

04:28.410 --> 04:30.489
and the expertise and the technical

04:30.489 --> 04:32.600
acumen of our individuals and knowing

04:32.600 --> 04:34.839
the risk associated with developing

04:34.839 --> 04:37.450
technologies is super critical to that

04:37.450 --> 04:39.561
requirement , particularly as we move

04:39.561 --> 04:41.820
more towards those capability based

04:41.850 --> 04:43.739
based solution sets versus single

04:43.739 --> 04:46.489
widget widget identification of

04:46.489 --> 04:48.649
technology that's seen before . So

04:48.880 --> 04:51.102
there's nothing that JSTO and stuff and

04:51.102 --> 04:53.480
and the folks within it hadn't been

04:53.480 --> 04:55.647
doing . This is putting prioritization

04:55.647 --> 04:58.200
and stabilization and across there . It

04:58.200 --> 05:00.549
also allows for consideration . I

05:00.549 --> 05:02.216
always call out Erin and Dr .

05:02.216 --> 05:04.438
Reichhardt because she's my favorite on

05:04.438 --> 05:06.549
the across the medical countermeasure

05:06.549 --> 05:08.709
space . We have peanut butter spread

05:08.709 --> 05:10.950
over the years across a lot of projects

05:10.950 --> 05:12.950
and you'll see a lot of things with

05:12.950 --> 05:15.510
perhaps we count in the way we talk

05:15.510 --> 05:18.070
about externally as super important

05:18.070 --> 05:20.181
areas , but then you'll see only 3 or

05:20.181 --> 05:22.309
$4 million placed against those and

05:22.309 --> 05:24.709
that didn't jive with with what we're

05:24.709 --> 05:26.765
transmitting and so making sure that

05:26.950 --> 05:30.950
we're giving guidance to Our S&T

05:31.239 --> 05:34.200
cohort and our colleagues , but in a

05:34.200 --> 05:36.422
way that does not constrain them , that

05:36.422 --> 05:38.533
gives them all the all the ability to

05:38.533 --> 05:40.367
innovate within that with simple

05:40.367 --> 05:42.589
guidelines and objectives and so that's

05:42.589 --> 05:44.756
why they're fairly simple and they may

05:44.756 --> 05:46.700
seem overt and stuff . They're not

05:46.700 --> 05:48.756
things that you haven't heard Kim Bo

05:48.756 --> 05:50.867
work on before , but I can assure you

05:50.867 --> 05:50.480
that where the funding , where the

05:50.480 --> 05:52.647
emphasis , and where the priority will

05:52.647 --> 05:54.758
be placed will be in these areas that

05:54.758 --> 05:56.980
Bob just kind of went through today and

05:56.980 --> 05:59.829
stuff . Is that fair ? Perfect . What

05:59.829 --> 06:02.390
else do you got ? That's it for me . OK ,

06:02.820 --> 06:04.764
we literally , they told us it was

06:04.764 --> 06:06.876
going to be all questions and answers

06:06.876 --> 06:08.820
and stuff like that . So , if that

06:08.820 --> 06:11.299
serves as a answer not just around S&T

06:11.299 --> 06:13.521
but anything to do with the Bioodefense

06:13.521 --> 06:15.632
program or anything while you're here

06:15.632 --> 06:17.799
today . We'll go ahead and get started

06:17.799 --> 06:19.970
or if you have questions . We'll go

06:19.970 --> 06:22.137
ahead and get started then gentlemen ,

06:22.137 --> 06:24.329
you've just rolled out your new

06:24.329 --> 06:27.690
objectives . What do you foresee as the

06:27.690 --> 06:29.880
greatest challenge in all of those

06:29.880 --> 06:32.000
objectives or is that something that

06:32.369 --> 06:34.529
you all have looked at thus far as a

06:34.529 --> 06:38.369
wholesome approach ? So I mean I'll

06:38.369 --> 06:40.536
I'll take a crack at it , you know , I

06:40.536 --> 06:44.130
think . What we consistently hear is

06:44.130 --> 06:46.297
the number one thing that that our war

06:46.297 --> 06:48.463
fighters need is that integrated early

06:48.463 --> 06:50.660
warning capability . So getting ,

06:50.839 --> 06:53.160
getting information , usable

06:53.160 --> 06:55.799
information to the forces at the time

06:55.799 --> 06:58.649
that they need it is , is , you know ,

06:58.730 --> 07:00.609
our biggest challenge and it's

07:00.609 --> 07:02.720
something that we're that we're gonna

07:02.720 --> 07:05.190
be . You know , continuously . Um ,

07:06.730 --> 07:09.170
so I think that is , that is clearly a

07:09.170 --> 07:11.880
challenge , but I think all of these

07:11.880 --> 07:14.049
have their own challenges . All of

07:14.049 --> 07:16.049
these S&T objectives have their own

07:16.049 --> 07:18.327
challenges in their own way , you know ,

07:18.529 --> 07:20.640
medical countermeasures certainly not

07:20.640 --> 07:22.640
an easy space , you know , as we're

07:22.640 --> 07:24.970
trying to accelerate the , the , the

07:24.970 --> 07:26.970
development and delivery of medical

07:26.970 --> 07:30.730
countermeasures at the time and at the

07:30.730 --> 07:32.952
place where they're needed , you know ,

07:32.952 --> 07:35.063
when we're talking about our pivot to

07:35.063 --> 07:37.450
Indo Paycom . The ability to overcome

07:37.450 --> 07:39.619
contested logistics , right , to

07:40.049 --> 07:42.890
deliver diagnostics as you mentioned in

07:42.890 --> 07:45.619
theater to Maybe do

07:45.619 --> 07:49.140
expeditionary manufacturing of

07:49.140 --> 07:51.450
diagnostics or medical countermeasures .

07:51.779 --> 07:53.446
You know , those are all huge

07:53.446 --> 07:56.170
challenges delivering a new suit , you

07:56.170 --> 07:58.281
know , that that will protect our war

07:58.281 --> 08:00.739
fighters . All of these are huge

08:00.739 --> 08:02.628
challenges in their own way , and

08:02.628 --> 08:04.795
that's why they , they've all ended up

08:04.795 --> 08:06.906
in these these S&T objectives . And I

08:06.906 --> 08:08.920
think enterprise-wise , I think the

08:08.920 --> 08:11.142
greatest one of the challenges is going

08:11.142 --> 08:13.790
to be . And not having Mr . Mr . Colvin

08:13.790 --> 08:17.029
as our as our director for the JPEO up

08:17.029 --> 08:19.251
here as the advanced developer , he was

08:19.251 --> 08:21.473
unable to make it out here , but that's

08:21.473 --> 08:23.640
kind of the triad that that forms this

08:23.640 --> 08:25.696
up . What I'm most concerned , and I

08:25.696 --> 08:27.918
know that Major General Lodi started to

08:27.918 --> 08:27.149
call you out in the front row there ,

08:27.239 --> 08:28.795
ma'am , but then I had this

08:28.795 --> 08:31.128
conversation a little bit earlier today ,

08:31.128 --> 08:33.789
but In the past too is how we take

08:33.789 --> 08:36.219
deferred risk and stuff , meaning when

08:36.219 --> 08:38.330
we're having advanced development and

08:38.330 --> 08:40.441
we've already passed things on and we

08:40.441 --> 08:42.630
have a solution set that either the

08:42.630 --> 08:44.519
performance has to be bought back

08:44.519 --> 08:46.741
against the requirements due to lack of

08:46.741 --> 08:48.852
test methodologies or the requirement

08:48.852 --> 08:50.909
you can't read versus the objective

08:50.909 --> 08:53.500
versus the threshold . In the past ,

08:53.510 --> 08:57.179
that that that risk has evaporated .

08:57.349 --> 08:59.619
It's not deferred , not pulled back

08:59.619 --> 09:01.675
into the system . It isn't accounted

09:01.675 --> 09:03.580
for because we have singular

09:03.580 --> 09:05.247
requirements , not capability

09:05.247 --> 09:07.390
requirements , and as a result , we

09:07.390 --> 09:09.501
take risk and buy risk to that single

09:09.501 --> 09:11.612
widget , and then once that widget is

09:11.612 --> 09:13.612
fielded , that risk evaporates . So

09:13.612 --> 09:15.668
collectively as a checkbook , I look

09:15.668 --> 09:17.668
for risk across there and what that

09:17.668 --> 09:19.890
means to these objectives . is as we're

09:19.890 --> 09:21.779
rapidly passing and transitioning

09:21.779 --> 09:24.001
things over to our advanced development

09:24.001 --> 09:26.168
partners and they're choosing with the

09:26.168 --> 09:28.409
services where to take risk and if

09:28.409 --> 09:30.520
we're incrementally fielding or we're

09:30.520 --> 09:32.950
going to the good as and stuff and it's

09:32.950 --> 09:35.609
not technically feasible to get to the

09:35.609 --> 09:37.890
absolute threshold , I mean the overall

09:37.890 --> 09:40.099
objective . That I want to know that

09:40.109 --> 09:42.429
that risk is absorbed back into the S&T

09:42.429 --> 09:44.739
community . I want to know that the S&T

09:44.989 --> 09:47.100
has in place the highest priorities ,

09:47.100 --> 09:49.322
and they have the funding and they have

09:49.322 --> 09:51.378
the onus to receive back that risk .

09:51.390 --> 09:54.219
That risk again doesn't just doesn't ,

09:54.229 --> 09:56.340
doesn't just disappear and that we're

09:56.340 --> 09:58.562
taking accounting of that because if it

09:58.562 --> 10:00.618
is a capability , then that means we

10:00.618 --> 10:02.729
need to service the entire capability

10:02.729 --> 10:04.896
and that can be done through other.mil

10:04.896 --> 10:07.118
PF . Approaches , it doesn't have to be

10:07.118 --> 10:09.118
the material solution , but what it

10:09.118 --> 10:11.285
can't be is is that and I think . That

10:11.285 --> 10:13.285
will be a challenge with these that

10:13.285 --> 10:13.270
interplay between our advanced

10:13.270 --> 10:16.710
developers and our S&T partners to make

10:16.710 --> 10:19.469
sure that that risk is caught and

10:19.469 --> 10:22.150
managed and also at some point through

10:22.150 --> 10:24.261
either modernization because of where

10:24.261 --> 10:27.309
the TRL levels are in later stage S&T

10:27.309 --> 10:29.476
development or through other means and

10:29.476 --> 10:31.587
stuff like that is ameliorated . So I

10:31.587 --> 10:33.809
think that's going to be very important

10:33.809 --> 10:35.976
to work together closely . Yes , thank

10:35.976 --> 10:38.869
you gentlemen . So our first question

10:38.869 --> 10:41.469
is how will you push diagnostic and

10:41.469 --> 10:43.909
therapeutic capabilities to the front

10:43.909 --> 10:46.270
line in austere environments ? It's a

10:46.270 --> 10:49.200
pretty good question . That is a good

10:49.200 --> 10:50.367
question , Michael .

10:53.169 --> 10:55.336
Do you want to take your crack ? I can

10:55.336 --> 10:57.447
try , yeah , and stuff , and , and we

10:57.447 --> 10:59.502
have our folks in here that can also

10:59.502 --> 11:01.558
chime in and say when we're wrong so

11:01.558 --> 11:03.669
that you get . So that's it . We talk

11:03.669 --> 11:05.780
it's not exclusive . I know we talk a

11:05.780 --> 11:07.891
lot about Indo Paycom and the tyranny

11:07.891 --> 11:07.659
of distance and what we're going to

11:07.659 --> 11:09.437
have to deal with the contested

11:09.437 --> 11:11.603
logistics and the realities associated

11:11.603 --> 11:13.826
with that as the Kim Bo Defense program

11:13.826 --> 11:16.048
and not just us , our partners in Barda

11:16.048 --> 11:18.048
and others for drug developers have

11:18.048 --> 11:20.326
moved more towards that broad spectrum ,

11:20.326 --> 11:22.548
and I hate using that term as far as an

11:22.548 --> 11:24.603
overall approach , but as we look at

11:25.000 --> 11:27.239
How we're going to put put not only

11:27.239 --> 11:29.239
platforms but also products up to

11:29.239 --> 11:31.406
certain levels and how we're trying to

11:31.406 --> 11:33.461
make ourselves a not more nimble and

11:33.461 --> 11:35.572
speedy when we are dealt with with an

11:35.572 --> 11:37.295
emergent , I mean with with an

11:37.295 --> 11:39.628
engineered or an unknown related threat ,

11:39.628 --> 11:41.795
particularly in the Indopecom region ,

11:41.795 --> 11:43.906
our ability to rapidly translate into

11:43.906 --> 11:45.461
narrow spectrum and applied

11:45.461 --> 11:47.683
therapeutics affecting diagnostics . It

11:47.683 --> 11:49.795
is moot because we're not going to be

11:49.795 --> 11:51.906
able to get in theater . We're not we

11:51.906 --> 11:54.072
stockpile our way out of a situation .

11:54.072 --> 11:56.183
What's in kits is in kits and stuff .

11:56.183 --> 11:58.406
So if it's simple , pop your Cipro , if

11:58.406 --> 12:00.461
you think it's a bacterial infection

12:00.461 --> 11:59.940
and move on until we have

11:59.940 --> 12:02.218
characterization of what that might be .

12:02.218 --> 12:03.996
But in the case that we do have

12:03.996 --> 12:05.884
something that we have to rapidly

12:05.884 --> 12:08.051
develop or repurpose drug to get it in

12:08.051 --> 12:10.273
or diagnostics overall , we're going to

12:10.273 --> 12:12.619
have to very much be as active as the

12:12.619 --> 12:14.730
rest of the DOD is looking , and that

12:14.730 --> 12:16.619
means our services using additive

12:16.619 --> 12:18.841
manufacturing for spare parts and far .

12:18.841 --> 12:20.730
Expeditionary and far forward , I

12:20.730 --> 12:22.786
differentiate incorrectly , probably

12:22.786 --> 12:24.952
the two meaning expeditionary is small

12:24.952 --> 12:27.320
batch modular areas probably on

12:27.320 --> 12:29.487
platforms like aircraft carriers . Far

12:29.487 --> 12:31.709
forward being that with our partners in

12:31.709 --> 12:33.598
foreign places like Philippines ,

12:33.598 --> 12:35.542
Australia , and where you may have

12:35.542 --> 12:37.709
co-production . But the fact remains ,

12:37.709 --> 12:39.764
if we're into it , it doesn't matter

12:39.764 --> 12:41.820
how fast again . Erin and her cohort

12:41.820 --> 12:43.764
over in JPO is able to use a rapid

12:43.764 --> 12:45.820
medical countermeasure timeline . It

12:45.820 --> 12:47.931
doesn't matter if we can get to a 100

12:47.931 --> 12:49.542
day vaccine . In a situation

12:49.542 --> 12:51.764
operationally such as Indo Paycom , our

12:51.764 --> 12:53.820
ability to actually deliver that and

12:53.820 --> 12:57.159
make a difference is doesn't exist very

12:57.159 --> 12:59.326
much , and it will be difficult in UCO

12:59.326 --> 13:01.492
scenario as well . So that means , and

13:01.492 --> 13:03.603
we have a lot of services are leaning

13:03.603 --> 13:05.603
forward and thinking about this . I

13:05.603 --> 13:07.770
mean we do those things like on-demand

13:07.770 --> 13:09.992
pharmaceuticals , a small molecule . We

13:09.992 --> 13:09.770
know diagnostics in certain platforms

13:09.770 --> 13:12.109
can be done . Biologics harder , but

13:12.109 --> 13:14.276
we've seen how those can be done . And

13:14.276 --> 13:16.276
so really it's marrying up services

13:16.276 --> 13:18.387
like the navy . The navy is the first

13:18.387 --> 13:20.276
to roll out on their own to start

13:20.276 --> 13:22.442
looking at requirements and generating

13:22.442 --> 13:24.665
those and talking to industry . Because

13:24.665 --> 13:26.831
they are interested in putting some of

13:26.831 --> 13:29.053
this capability on not only the mercy ,

13:29.053 --> 13:31.165
the hope , but also maybe some of the

13:31.165 --> 13:33.276
larger cars . And so matching that up

13:33.276 --> 13:35.387
with early warning and surveillance ,

13:35.387 --> 13:37.387
it helps them to redefine and start

13:37.387 --> 13:39.387
thinking about it . But by no means

13:39.387 --> 13:41.331
does anyone have the answer on how

13:41.331 --> 13:43.553
we're going to look at both diagnostics

13:43.553 --> 13:45.387
and therapeutics in a forward or

13:45.387 --> 13:47.609
austere environments in a rapid way and

13:47.609 --> 13:49.776
it's exciting , but also it's going to

13:49.776 --> 13:51.998
be a daunting challenge , much of which

13:51.998 --> 13:54.109
Is going to be on the on the backs of

13:54.109 --> 13:56.220
our S&T partners here in the room and

13:56.220 --> 13:58.165
all but one operational need being

13:58.165 --> 14:00.165
generated obviously the operational

14:00.165 --> 14:02.525
concept calls for and now we have and

14:02.525 --> 14:04.804
we have some prior targets against that

14:04.804 --> 14:06.804
contested logistics what that might

14:06.804 --> 14:08.971
mean and as a result , I think the S&T

14:08.971 --> 14:10.693
community has a whole bunch of

14:10.693 --> 14:12.804
opportunity for work , but it's going

14:12.804 --> 14:14.915
to be difficult , yeah , and you know

14:14.915 --> 14:17.248
one of the key things to make this work .

14:17.650 --> 14:19.840
is the fact that we have to be able to

14:19.840 --> 14:21.840
develop these diagnostics and these

14:21.840 --> 14:25.000
therapeutics fast because we're not

14:25.000 --> 14:28.840
going to be able to rely on traditional

14:28.840 --> 14:31.007
paradigms as we solve , we're going to

14:31.007 --> 14:33.969
fall behind , right ? So In order to do

14:33.969 --> 14:36.080
that , it's going to require a lot of

14:36.080 --> 14:38.429
coordination across our enterprise to

14:38.429 --> 14:41.150
make sure that we are able to utilize

14:41.150 --> 14:43.309
our strengths . So we've been working

14:43.309 --> 14:46.229
with the JPO and with partners in the

14:46.229 --> 14:48.780
DASE's office to develop a medical

14:48.780 --> 14:51.030
architecture that will allow us to

14:51.030 --> 14:54.150
rapidly develop a diagnostic or a

14:54.150 --> 14:57.299
therapeutic or a vaccine , you know ,

14:57.390 --> 15:00.039
at the speed of need . So we've , we've

15:00.340 --> 15:02.451
been working very closely together to

15:02.451 --> 15:04.618
optimize our enterprise , which I know

15:04.618 --> 15:06.451
is one of your , you know , your

15:06.451 --> 15:08.507
strategic themes for the for the for

15:08.507 --> 15:10.618
the defense program because we're not

15:10.618 --> 15:13.309
going to be able to . We're not going

15:13.309 --> 15:15.789
to be able to function the way we

15:15.789 --> 15:18.669
always have . We have to reform how we

15:18.669 --> 15:21.830
operate for speed because the

15:21.830 --> 15:23.663
department really isn't going to

15:23.663 --> 15:25.552
tolerate it , right , and our war

15:25.552 --> 15:27.663
fighters deserve better . Speaking of

15:27.663 --> 15:29.886
that , I would imagine that you all are

15:29.886 --> 15:31.830
looking from the strategic and the

15:31.830 --> 15:33.774
operational level of your previous

15:33.774 --> 15:35.774
lessons learned . You you just said

15:35.774 --> 15:37.997
something in a moment , Dr . Kay , that

15:37.997 --> 15:39.997
you've got to do things differently

15:39.997 --> 15:42.052
going forward . Is there anything in

15:42.052 --> 15:44.163
the past that has worked that you all

15:44.163 --> 15:46.108
are seeing that we can incorporate

15:46.108 --> 15:48.163
moving forward ? Nothing in the past

15:48.163 --> 15:51.369
worked . Yeah , no , I mean , we have ,

15:51.630 --> 15:53.686
we have certainly , you know , our ,

15:53.686 --> 15:55.852
our enterprise has certainly delivered

15:55.852 --> 15:58.019
capability . What we have to do though

15:58.019 --> 16:00.409
is optimize it for speed . So

16:00.409 --> 16:02.465
realistically , you know , we have a

16:02.465 --> 16:04.576
number of examples , you know , we've

16:04.576 --> 16:06.798
developed an Ebola vaccine , you know ,

16:06.798 --> 16:08.742
that that is certainly impactful ,

16:08.742 --> 16:10.965
right ? But what we're trying to do . I

16:10.965 --> 16:12.798
clear the path , right , set the

16:12.798 --> 16:15.020
conditions so that way when a new thing

16:15.020 --> 16:18.099
pops up like COVID , that or or whether

16:18.099 --> 16:21.409
it's a natural or engineered threat ,

16:21.690 --> 16:23.859
we have everything in place to be able

16:23.859 --> 16:26.539
to respond quickly . where I draw the

16:26.539 --> 16:28.872
contrast and a little bit of difference ,

16:28.872 --> 16:31.039
I think we excel in that frankly , and

16:31.039 --> 16:33.039
I think I think our folks and their

16:33.039 --> 16:32.820
partners in this room and stuff like

16:32.820 --> 16:34.542
that are going to generate the

16:34.542 --> 16:36.764
capabilities . I think with a couple of

16:36.764 --> 16:38.820
the examples , I don't want to gloss

16:38.820 --> 16:40.709
over it . That I just happened to

16:40.709 --> 16:43.440
mention . So expeditionary

16:43.440 --> 16:45.496
manufacturing and then again back to

16:45.496 --> 16:48.679
the Kimbao Medical rapid Research

16:48.679 --> 16:50.846
response or the medical architecture .

16:51.580 --> 16:53.580
We're being asked to do things that

16:53.580 --> 16:55.691
aren't really chemical and biological

16:55.691 --> 16:58.289
defense program jobs , right ? And so

16:58.289 --> 17:00.233
what we just talked about was that

17:00.233 --> 17:02.599
speed and delivery , we don't get paid

17:03.130 --> 17:06.040
to develop expeditionary manufacturing .

17:06.130 --> 17:08.186
That's nobody's ever said that's our

17:08.186 --> 17:10.408
job . We deliver capability directly to

17:10.408 --> 17:12.630
the warfighter . The ability to rapidly

17:12.630 --> 17:14.852
manufacture isn't necessarily our job .

17:14.852 --> 17:17.160
Same with our medical architecture . We

17:17.160 --> 17:20.239
deliver and we develop drug products

17:20.239 --> 17:22.461
and things to protect our war fighter .

17:22.461 --> 17:25.199
No one pays us for speed to turn that

17:25.199 --> 17:27.255
on as a rapid response . We're not a

17:27.255 --> 17:29.477
rapid response organization . We're not

17:29.477 --> 17:31.588
Asper and we're not other elements in

17:31.588 --> 17:33.588
the board to do that . So meaning .

17:33.588 --> 17:35.532
Aaron , I always pick on you . You

17:35.532 --> 17:37.699
don't , Aaron doesn't have O&M funding

17:37.699 --> 17:39.755
when they say turn that on and moved

17:39.755 --> 17:41.866
against that narrow spectral threat ,

17:41.866 --> 17:44.088
right , and start producing . So when I

17:44.088 --> 17:46.143
say different , I think a lot of the

17:46.143 --> 17:48.255
good things as far as the products we

17:48.255 --> 17:47.650
have in the past and the lessons we've

17:47.650 --> 17:49.761
learned to optimize , but on the flip

17:49.761 --> 17:51.650
side . Now some of the what we're

17:51.650 --> 17:53.317
talking about not only in the

17:53.317 --> 17:55.428
operational context but also with the

17:55.428 --> 17:57.650
technologies we're talking about , it's

17:57.650 --> 17:59.761
drawing chem bio defense in and there

17:59.761 --> 17:59.560
has to be some hard questions with

17:59.560 --> 18:01.282
senior leaders and funding and

18:01.282 --> 18:03.959
authorizations around how far are we

18:03.959 --> 18:06.181
leaning to make sure the products we're

18:06.181 --> 18:07.903
developing actually get to the

18:07.903 --> 18:10.126
warfighter and whose job is that . With

18:10.126 --> 18:12.126
with with the services and with the

18:12.126 --> 18:14.292
components and so I think that's going

18:14.292 --> 18:16.403
to play a little bit of give and take

18:16.403 --> 18:16.084
as we decide that because it's not the

18:16.084 --> 18:18.665
only place that we're kind of being

18:18.665 --> 18:20.724
asked to spend our money but starts

18:20.724 --> 18:23.525
bleeding over into the a response or

18:23.525 --> 18:25.581
more operational setting and that we

18:25.581 --> 18:27.525
have to be cautious because we owe

18:27.525 --> 18:29.525
things directly to the warfighter .

18:29.525 --> 18:31.747
Thank you , sir . Thank you gentlemen .

18:31.747 --> 18:33.636
What future collaborations cooper

18:33.636 --> 18:35.636
operations would you like to see or

18:35.636 --> 18:37.747
planning with non-DOD agencies in the

18:37.747 --> 18:40.469
field of CBD like DHS or any what

18:40.469 --> 18:42.636
future partnerships I guess are on the

18:42.636 --> 18:45.750
horizon ? Oh , so you know , I think we

18:45.750 --> 18:49.069
have very active collaborations , you

18:49.069 --> 18:51.236
know , a lot of these folks are in the

18:51.236 --> 18:53.458
room , right , because of the work that

18:53.458 --> 18:55.890
we do together . Um , historically , I

18:55.890 --> 18:59.000
know that JSTO has leaned forward ,

18:59.209 --> 19:01.376
right , in , in making sure that we're

19:02.560 --> 19:05.069
That we are capturing the full breadth

19:05.069 --> 19:07.013
of everything that goes on so that

19:07.013 --> 19:09.013
we're not replicating and we're not

19:09.013 --> 19:11.013
trying to recreate something that's

19:11.013 --> 19:12.958
already been done . But we're also

19:12.958 --> 19:14.847
trying to make our information as

19:14.847 --> 19:16.736
available as we can . Now we're a

19:16.736 --> 19:19.060
defense organization and our job is to

19:19.060 --> 19:21.609
deliver capabilities to the war fighter ,

19:22.099 --> 19:23.821
but that doesn't mean that the

19:23.821 --> 19:26.260
information that we have is only useful

19:26.260 --> 19:28.859
to us , right ? And we are a government

19:28.859 --> 19:30.579
agency , so I think it's our

19:30.579 --> 19:33.689
responsibility to make sure that we are

19:34.219 --> 19:36.275
being good stewards of those dollars

19:36.275 --> 19:37.997
and make sure that we get that

19:37.997 --> 19:40.163
information out there . So that way we

19:40.163 --> 19:42.219
can accelerate and you know a lot of

19:42.219 --> 19:44.441
the capabilities we develop while we're

19:44.441 --> 19:46.608
not developing for the first responder

19:46.608 --> 19:48.552
community necessarily is certainly

19:48.552 --> 19:50.441
applicable , right , and could be

19:50.441 --> 19:53.199
utilized by other folks . So we try to

19:53.199 --> 19:55.829
be good partners , we try to be , um ,

19:56.000 --> 19:58.319
you know , we try to collaborate and

19:58.319 --> 20:01.390
cooperate across the community , um ,

20:01.640 --> 20:04.260
you know , and in addition , A lot of

20:04.260 --> 20:06.260
our mission is also in deterrence ,

20:06.380 --> 20:08.959
right ? And you know , when you look at

20:09.260 --> 20:11.939
deterring the use of the weapons that

20:11.939 --> 20:14.106
we're talking about here this week , a

20:14.106 --> 20:16.420
lot of that is going to be based on the

20:16.420 --> 20:18.380
information that we share . So

20:18.380 --> 20:20.491
partnering with Department of State ,

20:20.491 --> 20:22.658
I've had a history personally of doing

20:22.658 --> 20:25.109
that . You know , it's , it's critical

20:25.109 --> 20:27.276
that we can get that information out ,

20:27.479 --> 20:29.760
that people , you know , know what

20:29.760 --> 20:32.219
we're doing in the ways that we can ,

20:32.439 --> 20:34.661
you know , the ways that we can share ,

20:34.661 --> 20:36.606
um , and make sure that we're good

20:36.606 --> 20:39.560
partners . So I mean to the future

20:39.560 --> 20:41.893
aspect of what collaboration looks like ,

20:41.893 --> 20:45.459
I think . Not me saying it , but I

20:45.459 --> 20:47.500
think we have a there there is a

20:47.500 --> 20:50.060
particular benefit now that there

20:50.060 --> 20:52.116
hadn't been in the past a little bit

20:52.116 --> 20:54.227
and what I mean by that is that we've

20:54.227 --> 20:56.227
always had our very centric mission

20:56.227 --> 20:58.338
spaces , and that's made it difficult

20:58.338 --> 21:00.282
in some circumstances within their

21:00.282 --> 21:02.393
agency as we align to what we need to

21:02.393 --> 21:04.282
do . But as we've all seen coming

21:04.282 --> 21:06.282
forward , we're all in I think with

21:06.282 --> 21:08.504
this S&T conference , not only what Bob

21:08.504 --> 21:08.109
presented up on , particularly across

21:08.109 --> 21:10.449
the AI portion , we deal in a lot of

21:10.449 --> 21:12.449
platform technologies now and those

21:12.449 --> 21:15.199
platform technologies are more agnostic

21:15.199 --> 21:17.310
to what the back to the outcome might

21:17.310 --> 21:19.477
be and the benefits to one's mission .

21:19.630 --> 21:21.519
The point being is that we're all

21:21.519 --> 21:23.729
investing in large amounts . We've got

21:24.140 --> 21:26.196
Dr . Han here and we've got the Wake

21:26.196 --> 21:28.196
Forest here . There's no end to the

21:28.196 --> 21:30.939
amount thatAA , FDA , DOD need

21:30.939 --> 21:33.050
organoids and organoids and organs on

21:33.050 --> 21:35.217
the chip . And so meaning a lot of the

21:35.217 --> 21:37.390
S&T what you'll see are more towards .

21:37.449 --> 21:39.671
Platform based solution sets when we're

21:39.671 --> 21:41.671
all looking at viral backbones , if

21:41.671 --> 21:43.782
we're looking at things like with Los

21:43.782 --> 21:46.060
Alamos and Jay still working on Raptor ,

21:46.060 --> 21:48.171
it's the same stuff that NIA needs to

21:48.171 --> 21:50.338
be able to look at to be able to match

21:50.338 --> 21:52.505
up the right pathogen with the right ,

21:52.505 --> 21:54.671
I mean vaccine backbone so we can move

21:54.671 --> 21:56.671
faster . The point being is I think

21:56.671 --> 21:59.079
collaboration now is we all invest and

21:59.079 --> 22:01.190
we see biology , but not just biology

22:01.190 --> 22:04.079
and additional chemistry and the use of

22:04.079 --> 22:05.959
and purchase of high performance

22:05.959 --> 22:09.479
computing capability or over reliance

22:09.479 --> 22:12.400
on developing AI models , organoids .

22:12.479 --> 22:14.479
There's a lot of standardization in

22:14.479 --> 22:16.312
between interagency partners and

22:16.312 --> 22:18.535
there's a lot of benefits of economy of

22:18.535 --> 22:20.423
scale that can be realized around

22:20.423 --> 22:22.535
platforms , and I think that . Things

22:22.535 --> 22:24.590
that might have been difficult under

22:24.590 --> 22:26.646
the National Bio defense strategy to

22:26.646 --> 22:28.757
coordinate that gives us a little bit

22:28.757 --> 22:30.812
of the common vernacular by which we

22:30.812 --> 22:32.868
can better cooperate and collaborate

22:32.868 --> 22:35.035
that benefit all of our mission sets .

22:35.035 --> 22:37.146
And so I actually look at kind of the

22:37.146 --> 22:36.280
future and the way that we're going

22:36.280 --> 22:38.640
after our technological solutions as

22:38.640 --> 22:40.807
serving to bind us a little bit better

22:40.807 --> 22:42.973
with our with our interagency partners

22:42.973 --> 22:46.500
and for effect . So you mentioned uh

22:46.910 --> 22:49.459
clearly the importance of of working

22:49.459 --> 22:51.348
across different USGs , different

22:51.348 --> 22:53.790
government agencies and non-government

22:53.790 --> 22:56.849
partners can you share with the group a

22:56.849 --> 22:58.793
situation where that has been most

22:58.793 --> 23:00.670
beneficial , you know , from a

23:00.670 --> 23:03.709
collaborative effort . For example , do

23:03.709 --> 23:05.876
systems speak to each other ? Do you ,

23:05.876 --> 23:08.042
if there's something going on with DOD

23:08.042 --> 23:10.153
versus a state , do you , do you work

23:10.153 --> 23:12.189
across platforms for a particular

23:12.189 --> 23:14.356
problem that you could expand a little

23:14.356 --> 23:17.349
bit more on that , please , sir . Sir

23:18.339 --> 23:22.180
So I'm the surge . So I mean ,

23:22.339 --> 23:26.069
I think . I think you know

23:26.069 --> 23:29.829
I can speak of one example where , you

23:29.829 --> 23:33.479
know , after the The uh Novichok

23:33.479 --> 23:36.339
attack , right , in Salisbury . That

23:36.339 --> 23:39.219
was a perfect example where all of the

23:39.219 --> 23:41.441
government had to come together to help

23:41.441 --> 23:44.420
to respond , right ? It wasn't just a

23:44.420 --> 23:46.531
science problem . It certainly wasn't

23:46.531 --> 23:48.587
just a science problem . There was a

23:48.587 --> 23:50.809
science component to it , but it became

23:50.809 --> 23:53.459
policy and international and , you know .

23:54.119 --> 23:57.800
We had to work with the OPCW and help

23:57.800 --> 23:59.911
our international partners do their ,

23:59.920 --> 24:03.209
do their work , um , so watching all of

24:03.209 --> 24:05.520
that come together , you know , in a

24:05.520 --> 24:09.000
time of crisis . I , you know ,

24:09.329 --> 24:11.440
probably the best example , much like

24:11.440 --> 24:13.607
we did with COVID to help us respond .

24:14.459 --> 24:16.599
But what we're trying to do is is

24:16.599 --> 24:18.599
institutionalize that so it doesn't

24:18.599 --> 24:20.710
only happen during a crisis , right ?

24:20.810 --> 24:22.866
We don't want to , we do not want to

24:22.866 --> 24:25.089
rebuild that structure every single

24:25.089 --> 24:27.369
time and then tear it down and then

24:27.369 --> 24:29.489
start that over again . So what we're

24:29.489 --> 24:31.600
really trying to do is make sure that

24:31.600 --> 24:33.767
that's an institutional part of our of

24:33.767 --> 24:36.100
our culture that we're working together ,

24:36.100 --> 24:38.267
that we're collaborating and trying to

24:38.267 --> 24:40.378
be trying to be good partners all the

24:40.378 --> 24:42.711
time . Perfect answer . Thank you , sir .

24:42.859 --> 24:45.979
Regarding wearables , will the CBDP be

24:45.979 --> 24:48.489
investing in medical , physiological

24:48.489 --> 24:50.380
wearables , as well as physical

24:50.380 --> 24:52.099
environmental wearables ?

24:54.099 --> 24:56.880
No name . Either way , yeah .

24:57.969 --> 25:00.030
I'll go you go you already are

25:00.030 --> 25:02.141
investing in them . So this is , I'll

25:02.141 --> 25:04.250
be honest , this is probably in the

25:04.250 --> 25:07.689
area more of the JPO right now , but

25:07.689 --> 25:09.578
yes , you know , we are certainly

25:09.578 --> 25:11.578
looking at wearables as a potential

25:11.578 --> 25:13.856
technology to help us with diagnostics .

25:13.856 --> 25:16.022
I think I mentioned that in my , in my

25:16.022 --> 25:18.189
speech yesterday , you know , the fact

25:18.189 --> 25:20.022
that we're looking at developing

25:20.022 --> 25:21.911
wearables and partnering with the

25:21.911 --> 25:23.911
algorithms so we can get to quicker

25:23.911 --> 25:26.119
diagnostics and tell you . Uh , that

25:26.119 --> 25:28.175
you've got something going on before

25:28.175 --> 25:30.341
you're even feeling like you're sick ,

25:30.341 --> 25:32.452
right , to give you a couple of days'

25:32.452 --> 25:34.397
warning , um , you know , and as I

25:34.397 --> 25:36.341
mentioned earlier , our number one

25:36.341 --> 25:38.397
priority probably is that integrated

25:38.397 --> 25:40.619
early warning . So we're looking across

25:40.619 --> 25:42.939
the spectrum beyond wearables , you

25:42.939 --> 25:45.459
know , wearables are a component , but

25:45.800 --> 25:48.400
also looking at things like , uh , you

25:48.400 --> 25:50.344
know , wastewater surveillance and

25:50.344 --> 25:52.400
other things in the bio surveillance

25:52.400 --> 25:54.011
area . That will give us any

25:54.011 --> 25:56.011
information early that something is

25:56.011 --> 25:59.489
going on . So that is , yes . The short

25:59.489 --> 26:01.699
answer to that is yes . This is

26:01.699 --> 26:03.643
certainly something we're gonna be

26:03.643 --> 26:05.866
looking at in the future . Yeah , and ,

26:05.866 --> 26:08.032
and from our perspective , I mean , It

26:08.032 --> 26:10.255
was only a year and a half ago , so the

26:10.255 --> 26:12.088
DOD recognized the importance of

26:12.088 --> 26:14.199
wearables throughout , I mean for all

26:14.199 --> 26:16.366
types of uses , right ? And that's why

26:16.366 --> 26:18.588
we have the pilot study which we most ,

26:18.588 --> 26:18.349
I think the unclassified version is

26:18.349 --> 26:20.949
available to most folks and all , but

26:20.949 --> 26:22.729
in that because we had over 54

26:22.729 --> 26:24.896
different program of record across the

26:24.896 --> 26:26.673
entire DOD developing their own

26:26.673 --> 26:28.951
wearable systems , so non-standardized .

26:28.951 --> 26:31.118
So again , Putting an earring and ring

26:31.118 --> 26:33.229
and 12 watches on every single airman

26:33.229 --> 26:35.062
or sailor and so it's not a real

26:35.062 --> 26:37.118
effective way . So when we ran , and

26:37.118 --> 26:39.118
they had the Kim biodefense program

26:39.118 --> 26:41.173
meeting with JPO and others with our

26:41.173 --> 26:43.340
defense health agency run that overall

26:43.340 --> 26:45.007
assessment and that went over

26:45.007 --> 26:46.951
everything that wearables , how it

26:46.951 --> 26:49.062
actually reports into into electronic

26:49.062 --> 26:51.118
health records , what's privacy look

26:51.118 --> 26:53.340
like , what does cybersecurity on those

26:53.340 --> 26:55.507
look like systems are , I mean the the

26:55.507 --> 26:57.507
data systems architecture of them ,

26:57.507 --> 26:59.673
platform design . But even to how they

26:59.673 --> 27:01.562
emit and also give signals to our

27:01.562 --> 27:03.673
adversaries and across the board with

27:03.673 --> 27:05.673
that , the DOD has to kind of , and

27:05.673 --> 27:07.673
it's very much similar to counter I

27:07.673 --> 27:10.140
mean to counter UAVs or counter UAS's .

27:10.739 --> 27:12.961
The leadership is going to put in place

27:12.961 --> 27:16.410
an integrator to actually not own but

27:16.410 --> 27:18.466
to help standardize the requirements

27:18.466 --> 27:20.410
that are developing because to the

27:20.410 --> 27:23.010
question itself , how can how can well

27:23.010 --> 27:25.177
it was the past question on whether we

27:25.177 --> 27:26.954
invest . Yes , we invest in the

27:26.954 --> 27:29.177
research specifically on the biomarkers

27:29.177 --> 27:31.399
and the physiological indicators coming

27:31.399 --> 27:33.288
off for us , but as we use it for

27:33.288 --> 27:35.510
concussion protocol , blue for us IFF ,

27:35.510 --> 27:37.566
heat stroke , all the different ways

27:37.566 --> 27:39.829
again . We don't own the platform . The

27:39.829 --> 27:41.829
services have to own the platform ,

27:41.910 --> 27:44.132
which is the iPhone , and we're the app

27:44.132 --> 27:46.299
that goes on top of it . It's the same

27:46.299 --> 27:47.799
data that comes off of any

27:47.799 --> 27:49.910
physiological monitoring device , and

27:49.910 --> 27:51.910
the ability to extract that for our

27:51.910 --> 27:53.910
purposes means that we shouldn't be

27:53.910 --> 27:55.688
buying wearables . We should be

27:55.688 --> 27:57.799
developing the unique identifiers and

27:57.799 --> 27:59.854
how the algorithms and the increased

27:59.854 --> 28:01.632
data . And we gain benefit from

28:01.632 --> 28:03.688
physiological systems , no matter if

28:03.688 --> 28:05.854
they're heat stress or other things on

28:05.854 --> 28:08.021
wearables , that adds to the data pool

28:08.021 --> 28:10.077
from which we're understanding human

28:10.077 --> 28:12.299
physiology . So we do a lot not only in

28:12.299 --> 28:14.632
your S&T postion but not just , I think ,

28:14.632 --> 28:16.799
and I think you guys do also have some

28:16.799 --> 28:18.910
invasive related work on wearables as

28:18.910 --> 28:21.132
well and stuff for the bloodstream . So

28:21.132 --> 28:23.188
it's a critically important part for

28:23.188 --> 28:25.188
all of DOD and we've led in many of

28:25.188 --> 28:27.132
those areas , but to be clear , we

28:27.132 --> 28:29.299
don't , we , we're going to be held up

28:29.299 --> 28:31.299
a little bit as we wait for service

28:31.299 --> 28:33.077
platform designs so that we can

28:33.077 --> 28:35.780
contribute to those amongst the other

28:35.780 --> 28:37.836
platform things . We need to protect

28:37.836 --> 28:40.058
our war fighter and contribute to early

28:40.058 --> 28:41.891
warning before we go to the next

28:41.891 --> 28:44.113
question , follow up question to that ,

28:44.113 --> 28:46.454
sir , are we having issues or

28:46.454 --> 28:49.015
challenges ? How quickly are we getting

28:49.015 --> 28:51.175
this material in the hands of the war

28:51.175 --> 28:53.342
fighter because I know that that could

28:53.342 --> 28:56.109
be . Uh , uh , a sticky situation , you

28:56.109 --> 28:58.331
know , from the time it rolls out . How

28:58.331 --> 29:00.498
quickly are we getting these wearables

29:00.498 --> 29:02.665
and pieces of equipment into the hands

29:02.665 --> 29:04.831
of the war fighter ? Well , you know ,

29:04.831 --> 29:06.831
and I think , I think that really .

29:07.339 --> 29:09.729
Keys in on what Ian was just saying ,

29:10.380 --> 29:14.130
we can't . We can't develop a wearable

29:14.130 --> 29:17.209
just for a cambio . We just can't , you

29:17.209 --> 29:19.900
know , we'll never keep up . The

29:19.900 --> 29:22.011
technology will always be ahead . You

29:22.011 --> 29:24.178
see , you know , the Apple Watch comes

29:24.178 --> 29:26.178
out every year , right , with new ,

29:26.178 --> 29:25.790
better technology . We're never going

29:25.790 --> 29:27.890
to meet that pace . So what we are

29:27.890 --> 29:30.170
trying to do is position ourselves in a

29:30.170 --> 29:32.800
good place to use the newest technology

29:33.130 --> 29:36.699
and to be . To have a

29:36.699 --> 29:39.859
platform that we can key into whatever

29:39.859 --> 29:42.489
the services are currently using , so I

29:42.489 --> 29:44.979
think you know we're we're probably not

29:44.979 --> 29:47.599
going to get into the space of

29:47.599 --> 29:49.821
developing our own wearable , but we're

29:49.821 --> 29:51.821
going to be we're going to be there

29:51.900 --> 29:54.250
ready to use whatever platform is

29:54.250 --> 29:56.306
chosen . OK , thank you , sir . Good

29:56.306 --> 29:58.880
follow up . Our next question from

29:58.880 --> 30:02.040
Oliver Payne . How can governments more

30:02.040 --> 30:03.949
effectively incentivize the young

30:03.949 --> 30:06.171
generation of scientists to work in the

30:06.171 --> 30:07.949
defense , genomics , forensic ,

30:08.040 --> 30:10.569
bioinformatics to create a healthy ,

30:10.640 --> 30:12.390
enduring talent pipeline ?

30:13.900 --> 30:16.540
So we just , we literally just came out

30:16.540 --> 30:20.310
of a meeting with the travel award ,

30:20.790 --> 30:22.790
uh , folks for the conference , the

30:22.790 --> 30:25.140
young folks that are here . Trying to

30:25.140 --> 30:27.362
talk to them and talk , you know , talk

30:27.362 --> 30:29.640
about the future and where we're going .

30:29.640 --> 30:31.751
You know , I think this is critically

30:31.751 --> 30:33.918
important for everything that we do in

30:33.918 --> 30:36.160
biodefense . We have to continue to

30:36.160 --> 30:38.640
build the bench as we like to say . Um ,

30:38.680 --> 30:42.660
I worked in , you know , in A DOD lab

30:42.939 --> 30:44.900
starting as a postdoc uh prior to

30:44.900 --> 30:47.380
coming to to JSTO . You know , I worked

30:47.380 --> 30:50.359
at Decom CBC for 20 years , starting as

30:50.359 --> 30:53.339
a postdoc , working in the lab , and I

30:53.339 --> 30:56.380
saw firsthand the passion that folks

30:56.380 --> 30:59.189
have for service . You know that is the

30:59.189 --> 31:01.300
one thing that we have to continue to

31:01.300 --> 31:03.522
encourage is , you know , there's going

31:03.522 --> 31:05.790
to be folks that are , you know , the

31:05.790 --> 31:08.260
universities are spitting out fantastic

31:08.699 --> 31:10.709
individuals . What we have to do is

31:10.709 --> 31:14.150
really reach out , have the , the

31:14.150 --> 31:16.390
programs available , have the outreach

31:16.390 --> 31:18.501
available so that way those ones that

31:18.501 --> 31:20.790
are really driven by service know that

31:20.790 --> 31:23.012
we are a place to come and a good place

31:23.012 --> 31:25.270
to work . So I think that's what we're

31:25.270 --> 31:27.492
doing . We're trying to be . You know ,

31:27.630 --> 31:29.949
reach out , lean forward , make sure

31:29.949 --> 31:33.790
that they know that we exist . #1 . #2 ,

31:33.869 --> 31:35.980
that there are good programs that are

31:35.980 --> 31:38.147
functional and workable for them , you

31:38.147 --> 31:40.313
know , things like being active in the

31:40.313 --> 31:43.150
smart scholarship system where , you

31:43.150 --> 31:45.372
know , for those that are in the room ,

31:45.372 --> 31:47.594
I don't know how many we have , but the

31:47.594 --> 31:49.761
smart scholarship program is something

31:49.761 --> 31:52.310
that's fantastic . It's like ROTC

31:52.310 --> 31:54.949
essentially for for laboratory

31:54.949 --> 31:57.510
scientists so they can You know ,

31:57.670 --> 32:00.800
basically the DOD , they apply , they

32:00.800 --> 32:03.829
selects them , pays them a stipend and

32:03.829 --> 32:06.051
their tuition while they're in school ,

32:06.051 --> 32:08.949
and then they're guaranteed a job at

32:08.949 --> 32:12.069
Ditra or in one of the DOD labs upon

32:12.069 --> 32:14.920
their graduation , and it's , it's ,

32:15.030 --> 32:17.252
it's kind of a , you know , they , they

32:17.252 --> 32:19.619
have a service obligation . But you

32:19.619 --> 32:21.989
know , the vast majority I've seen it

32:21.989 --> 32:24.569
firsthand end up staying beyond that

32:24.569 --> 32:26.513
service obligation because they're

32:26.513 --> 32:29.270
driven by service , right ? And I think

32:29.270 --> 32:31.326
what we have to do is just make sure

32:31.326 --> 32:33.492
that that we're there ready to receive

32:33.492 --> 32:35.548
them , that we're being , you know ,

32:35.548 --> 32:37.492
forward and we're making sure that

32:37.492 --> 32:39.492
we're not getting stagnant with our

32:39.492 --> 32:41.659
with our protocols . So if you would .

32:42.819 --> 32:45.859
Now elaborate on how S&T performers

32:46.260 --> 32:48.149
better understand the operational

32:48.149 --> 32:51.560
contexts of the future fight . Oh do

32:51.560 --> 32:55.420
you ? So I mean I , I will tell you ,

32:55.449 --> 32:57.616
you know , that is , that is something

32:57.616 --> 33:00.939
that I think we have often struggled

33:00.939 --> 33:03.300
with , you know , is making sure that

33:03.660 --> 33:06.380
as an S&T community we understand what

33:06.380 --> 33:09.569
our operators are trying to do and what

33:09.569 --> 33:11.540
we have to deliver . So we have a

33:11.540 --> 33:13.707
number of programs , you know , I know

33:13.707 --> 33:15.873
you , Doctor Han , when you were , you

33:15.873 --> 33:18.207
know , started the scientists in Action ,

33:18.339 --> 33:20.810
you know , um , that that's a program

33:20.810 --> 33:23.099
that we make available where we try to

33:23.099 --> 33:25.719
get folks . Actually out with the war

33:25.719 --> 33:28.189
fighters so they can hear what's going

33:28.189 --> 33:30.522
on , what the challenges are , you know ,

33:30.829 --> 33:33.430
we run our Saboa events where we can

33:33.430 --> 33:35.910
bring in early technologies and put

33:35.910 --> 33:37.966
them in the hands of the warfighters

33:37.966 --> 33:40.132
and very importantly and probably most

33:40.132 --> 33:42.270
importantly at that event is that the

33:42.270 --> 33:44.437
folks that are making the technologies

33:44.437 --> 33:46.790
are hearing what the war fighters are

33:46.790 --> 33:49.150
saying . I know the first time I went

33:49.150 --> 33:51.469
it was eye opening to me because I was

33:51.469 --> 33:53.719
standing there watching . And there was

33:53.719 --> 33:56.750
a , a young , you know , private ,

33:56.880 --> 34:00.119
probably . And I , I'm not gonna say

34:00.119 --> 34:02.175
the bad word that she said , but she

34:02.175 --> 34:04.439
said , I got to hold this effing thing

34:04.439 --> 34:06.589
for 5 minutes like this , you know ,

34:06.640 --> 34:08.807
that's not gonna work , you know , and

34:08.807 --> 34:11.399
it , it just , it really opens your

34:11.399 --> 34:14.310
eyes to understand what it's like to

34:14.310 --> 34:16.679
operate , you know , so I think it is

34:16.679 --> 34:18.512
something that we that we really

34:18.512 --> 34:21.189
struggle with is making sure that we

34:21.189 --> 34:23.429
are communicating in the right way ,

34:23.760 --> 34:25.760
that when we host these events that

34:25.760 --> 34:27.760
we're communicating really what the

34:27.760 --> 34:29.760
challenges are . You know , so that

34:29.760 --> 34:31.649
we're matching our event with the

34:31.649 --> 34:33.879
current NDS so that we're not , you

34:33.879 --> 34:36.149
know , that we're not a step behind ,

34:36.790 --> 34:38.957
um , you know , I think , I think it's

34:38.957 --> 34:40.846
a challenge . I think it's a real

34:40.846 --> 34:42.901
challenge for the S&T community writ

34:42.901 --> 34:45.123
large , uh , and I think it's something

34:45.123 --> 34:47.290
that we , we collectively have to keep

34:47.290 --> 34:50.550
working at to try to get right . And so

34:50.679 --> 34:54.148
the only thing God It's incumbent on us

34:54.148 --> 34:56.315
and also our partners , and that means

34:56.315 --> 34:58.315
not just , not just in the advanced

34:58.315 --> 35:00.259
technology demonstration space but

35:00.259 --> 35:02.269
across experimentation , across

35:02.269 --> 35:04.436
training and exercising , frankly , as

35:04.436 --> 35:07.509
it starts catching up to again I'll say

35:07.509 --> 35:09.565
it again , Kimbio is not a mission ,

35:09.565 --> 35:11.509
it's a condition on a mission . It

35:11.509 --> 35:13.620
means that we're lagging in how those

35:13.620 --> 35:15.620
operational concepts are applied in

35:15.620 --> 35:17.620
some of the seams like we've talked

35:17.620 --> 35:19.565
about in the past . You have naval

35:19.565 --> 35:21.620
distributed operations in Baycom and

35:21.620 --> 35:23.676
Ace chain deployments and stuff like

35:23.676 --> 35:25.565
that . A lot of those in-betweens

35:25.565 --> 35:27.676
between the components , particularly

35:27.676 --> 35:29.676
on decontamination and other things

35:29.676 --> 35:31.509
haven't been worked out with the

35:31.509 --> 35:33.676
services . What is better though is to

35:33.676 --> 35:35.842
make sure that we're doing the best we

35:35.842 --> 35:37.787
can on the scenario derivement and

35:37.787 --> 35:39.842
stuff . So good one , and we agree ,

35:39.842 --> 35:42.176
and I've talked to Tom about this Saboa .

35:42.176 --> 35:44.850
I mean if we're prosecuting , if we're

35:44.850 --> 35:47.129
prosecuting a sarin lab that looks like

35:47.129 --> 35:49.929
it's in Syria on the lane , it will

35:49.929 --> 35:52.290
drive the technology that is relevant

35:52.290 --> 35:54.623
for that mission set . We don't need to ,

35:54.889 --> 35:57.056
we're not going to be swabbing . We're

35:57.056 --> 35:59.278
not going to be prosecuting , and so we

35:59.278 --> 36:01.278
saw like only one microelectron , I

36:01.278 --> 36:04.060
mean 11 microsensor that was a hand

36:04.060 --> 36:06.350
thrown . Those scenarios need to be

36:06.350 --> 36:08.294
updated to what the total force is

36:08.294 --> 36:10.572
actually going to come in contact with ,

36:10.572 --> 36:12.794
and the best way for us to make sure is

36:12.794 --> 36:12.610
that those are starting to matriculate

36:12.610 --> 36:14.830
into not only ATDs , the

36:14.830 --> 36:16.830
experimentation , but also the

36:16.830 --> 36:18.941
competition phase of the exercises as

36:18.941 --> 36:21.580
we work with the J7 on how to do those .

36:21.709 --> 36:23.376
That's going to help with our

36:23.376 --> 36:25.487
performers understanding because it's

36:25.487 --> 36:27.598
going to give them the mix of some of

36:27.598 --> 36:29.709
the challenges that are between those

36:29.709 --> 36:31.987
seams that are becoming very difficult ,

36:31.987 --> 36:34.098
right ? And so I think the technology

36:34.098 --> 36:36.265
has a uniqueness how it's deployed and

36:36.265 --> 36:38.431
how it's utilized that's going to make

36:38.431 --> 36:37.770
all the difference . And so I think

36:37.770 --> 36:39.992
it's incumbent on us to make sure we're

36:39.992 --> 36:42.979
constantly keeping . And not going back

36:42.979 --> 36:46.219
to coin and GWOT related situations and

36:46.219 --> 36:48.580
focusing on the CWMD , but really

36:48.580 --> 36:50.747
looking at the total force in the near

36:50.747 --> 36:52.747
peer competition and how we want to

36:52.747 --> 36:54.969
illustrate that within the scenarios we

36:54.969 --> 36:56.747
run that draw our technological

36:56.747 --> 36:58.969
application from our partners , I think

36:58.969 --> 37:01.080
it's going to be super important kind

37:01.080 --> 37:03.709
of going forward as well . Our next

37:03.709 --> 37:07.489
question . Says there was an emphasis

37:07.489 --> 37:09.433
on bio surveillance in the opening

37:09.433 --> 37:12.139
remarks , but conference talks seem to

37:12.139 --> 37:14.540
focus on data collection , for example ,

37:14.580 --> 37:17.409
sensors . Is there a desire to develop

37:17.409 --> 37:19.620
technology to process that data for

37:19.620 --> 37:22.060
early detection and identification .

37:23.489 --> 37:27.310
So yes , so I think , I think . You

37:27.310 --> 37:30.989
know , there is absolutely an emphasis

37:30.989 --> 37:33.870
on that , and I think you know one of

37:33.870 --> 37:36.229
the things that we're trying to do is

37:36.229 --> 37:38.173
make sure that we're linking those

37:38.173 --> 37:41.129
things up . So if you're you know

37:41.129 --> 37:44.540
looking at what we're doing in our

37:44.729 --> 37:48.050
um . In our emerging

37:49.189 --> 37:51.245
technology space , you know , with ,

37:51.245 --> 37:53.467
with our information technology and our

37:53.467 --> 37:55.689
decision support tools , I think that's

37:55.689 --> 37:57.939
really what we're looking at is , you

37:57.939 --> 38:00.060
know , using that as our hub for

38:00.060 --> 38:01.939
bringing that data together and

38:01.939 --> 38:04.850
processing it in a way that will make ,

38:05.100 --> 38:07.340
I think , as John Hannon , he's not

38:07.340 --> 38:09.451
here anymore , he used to say to make

38:09.451 --> 38:11.939
hard decisions easier , you know , how

38:11.939 --> 38:14.300
can we get that information . Off of

38:14.300 --> 38:16.929
those sensors and into a usable format

38:17.179 --> 38:19.123
that can make those hard decisions

38:19.123 --> 38:21.401
easier for the commanders in the field .

38:21.459 --> 38:24.770
So yes , look for , look for those uh

38:25.239 --> 38:27.939
platform uh parallel sessions to go

38:27.939 --> 38:30.050
find that information and and some of

38:30.050 --> 38:32.106
the investments we're making in that

38:32.106 --> 38:34.280
space and . We have several performers

38:34.280 --> 38:36.336
really partners in the room that are

38:36.336 --> 38:38.336
already working on this really hard

38:38.336 --> 38:40.558
question , right ? I mean , specific to

38:40.558 --> 38:42.780
bio surveillance as the department laid

38:42.780 --> 38:44.836
out in its biodefense strategy which

38:44.836 --> 38:46.947
was ordered by the biodefense posture

38:46.947 --> 38:49.169
Review recently in the bio surveillance

38:49.169 --> 38:51.280
implementation plan under development

38:51.280 --> 38:53.447
now . The capabilities , the funding ,

38:53.447 --> 38:55.669
and the people outlays have been put in

38:55.669 --> 38:57.836
place to start designing not only just

38:57.836 --> 38:57.810
that , the ingestion models and the

38:57.810 --> 39:00.129
overall analytics necessary to combine

39:00.129 --> 39:03.050
multimodal . Detection and that means

39:03.050 --> 39:05.106
across to all and that's why it's an

39:05.106 --> 39:07.272
Intel . That's why it's a chem bio and

39:07.272 --> 39:09.439
that's why it's a public health or for

39:09.439 --> 39:11.550
self protection role that all have to

39:11.550 --> 39:13.606
be integrated , whether that's early

39:13.606 --> 39:15.717
warning like we've talked extensively

39:15.717 --> 39:18.050
about wastewater surveillance wearables ,

39:18.050 --> 39:20.161
clinical syndromic type things to the

39:20.161 --> 39:21.883
sensors , hyperspectrals , the

39:21.883 --> 39:23.828
employment of those , but also the

39:23.828 --> 39:25.883
intelligence and the collection from

39:25.883 --> 39:27.661
social media as those all those

39:27.661 --> 39:29.550
indicators pull in as part of the

39:29.550 --> 39:31.772
common operating picture that for one .

39:31.772 --> 39:33.994
A combatant commander needs to consider

39:33.994 --> 39:36.161
and stuff like that and looking at the

39:36.161 --> 39:35.620
posture , particularly when we're

39:35.620 --> 39:37.731
sitting in competition or cooperation

39:37.731 --> 39:39.860
and not necessarily in crisis , are

39:39.860 --> 39:41.971
critically important . And so many of

39:41.971 --> 39:44.304
you in the audience are working on this ,

39:44.304 --> 39:46.304
and many are working within the bio

39:46.304 --> 39:48.304
surveillance , but bio surveillance

39:48.304 --> 39:48.020
isn't the only place again , it's not

39:48.020 --> 39:50.620
unique . It's one indicator . Nobody

39:50.620 --> 39:52.842
changes the military posture predicated

39:52.842 --> 39:55.100
off of a biological event . It comes in

39:55.100 --> 39:57.156
combination again with degradation .

39:57.156 --> 39:59.906
Space assets comes in with with cyber

39:59.906 --> 40:02.125
assets . It is one of , as Max talked

40:02.125 --> 40:04.525
about just earlier this morning . It is

40:04.525 --> 40:06.747
one of the asymmetric applications that

40:06.747 --> 40:08.969
will be used and it needs to be part of

40:08.969 --> 40:11.081
that common warning indicator for our

40:11.081 --> 40:13.247
leadership and at the tactical in that

40:13.247 --> 40:15.247
echelon . And so as we look at that

40:15.247 --> 40:17.136
data for and how we develop those

40:17.136 --> 40:19.426
technologies for ingestion , analytics ,

40:19.525 --> 40:22.145
and of it , it's critical because our

40:22.145 --> 40:24.256
early warning detections . Number one

40:24.256 --> 40:26.478
priority both from our service partners

40:26.478 --> 40:29.312
but across the DOD as well . OK , stove

40:29.312 --> 40:31.711
piped innovation is an issue in R&D

40:31.711 --> 40:34.872
efforts . How do we avoid this valley

40:34.872 --> 40:37.991
of death to ensure Ceri protection ,

40:38.072 --> 40:40.501
detection equipment and practices are

40:40.501 --> 40:42.872
effectively incorporated across the DOD ?

40:43.531 --> 40:47.152
Oh this is yeah this is one we've been

40:47.152 --> 40:50.350
focusing a lot on , so . One of the ,

40:50.429 --> 40:52.560
you know , one of the pillars of , of

40:52.560 --> 40:55.699
the CBDP um strategic plan is , is

40:55.699 --> 40:59.149
reforming the enterprise , and one of

40:59.149 --> 41:01.038
the ways that we're doing that is

41:01.038 --> 41:03.260
really looking to make sure that we are

41:03.260 --> 41:05.550
aligned across the enterprise because

41:05.550 --> 41:07.909
one of the things that would routinely

41:07.909 --> 41:10.020
kill us , you know , I've been around

41:10.020 --> 41:12.242
the Kim biodefense program for 20 years

41:12.242 --> 41:14.739
is . You know , like you said , in SNT

41:14.739 --> 41:16.939
we're going to develop solutions that

41:16.939 --> 41:19.729
will get after problems . But if

41:19.729 --> 41:21.951
there's no catcher mitt , ready to take

41:21.951 --> 41:24.173
it and advance that development and get

41:24.173 --> 41:27.139
it out to the warfighter because of an

41:27.139 --> 41:29.929
inefficient , you know , palm cycle

41:29.929 --> 41:31.873
where we didn't have money aligned

41:31.873 --> 41:34.489
there to take it into advanced

41:34.489 --> 41:37.449
development , you know , if there just

41:37.449 --> 41:41.290
wasn't a requirement there because we

41:41.290 --> 41:43.129
didn't do a good job in S&T of

41:43.129 --> 41:45.296
signaling that this new technology was

41:45.296 --> 41:47.407
coming that could change the way that

41:47.407 --> 41:49.740
the war fighters might fight . You know ,

41:49.740 --> 41:51.962
all of these things , if there wasn't a

41:51.962 --> 41:54.018
test , you know , if there wasn't an

41:54.018 --> 41:56.185
efficient way to test the technology ,

41:56.185 --> 41:58.351
you know , all of these things have to

41:58.351 --> 42:00.850
be in alignment to make this work , and

42:00.850 --> 42:03.017
all of those things contribute to that

42:03.017 --> 42:05.072
valley of death . So what we've been

42:05.072 --> 42:07.969
doing in the in the CBDP and one thing

42:07.969 --> 42:10.025
that that you know ourselves and the

42:10.025 --> 42:12.191
JPU have been working very , very hard

42:12.191 --> 42:15.570
at is to establish this tech transition

42:15.570 --> 42:17.792
pipeline to make sure that we're all in

42:17.792 --> 42:19.792
alignment . That , you know , we're

42:19.792 --> 42:21.626
communicating , that we're being

42:21.626 --> 42:23.737
transparent about where we're going .

42:23.737 --> 42:26.590
We signed a tech transition playbook um

42:26.590 --> 42:29.199
earlier this year . That really lays

42:29.199 --> 42:31.669
out those best practices and those

42:31.669 --> 42:33.725
understandings between ourselves and

42:33.725 --> 42:36.399
the JPO at the Advanced Developer to

42:36.399 --> 42:38.409
really make sure that everybody is

42:38.409 --> 42:41.030
operating on the same page and we're ,

42:41.719 --> 42:43.941
you know , we're going through a reform

42:43.941 --> 42:46.108
on how we're doing our palm , you know

42:46.108 --> 42:48.108
how we're laying out our investment

42:48.108 --> 42:50.219
strategy for the next 5 years to make

42:50.219 --> 42:53.090
sure that , you know . That when we

42:53.090 --> 42:55.719
have a technology that's going to be

42:56.050 --> 42:59.129
transitioning in 207 , that the JPO has

42:59.129 --> 43:01.489
money there in 207 to take that

43:01.489 --> 43:03.711
technology and advance it and make sure

43:03.711 --> 43:05.933
that it doesn't fall into the valley of

43:05.933 --> 43:08.156
death . So we have been focusing very ,

43:08.156 --> 43:10.378
very hard to make sure that we have all

43:10.378 --> 43:12.545
of that in alignment to make sure that

43:12.545 --> 43:14.767
we that we get that we get after this .

43:14.767 --> 43:16.989
And they , they've done a wonderful job

43:16.989 --> 43:19.045
working between those components and

43:19.045 --> 43:21.211
stuff to do that and a lot of kudos to

43:21.211 --> 43:23.267
Mr . Colvin and Dr . Christovich and

43:23.267 --> 43:25.267
their folks for kind of putting the

43:25.267 --> 43:27.433
place , most importantly , the folks ,

43:27.433 --> 43:29.489
say what I said , most importantly ,

43:29.489 --> 43:29.429
the folks , they are the ones that are

43:29.429 --> 43:31.596
doing that is for sure , but with that

43:31.596 --> 43:34.389
too , the The Valley death or what we

43:34.389 --> 43:36.611
call the valley death or basically just

43:36.611 --> 43:38.667
the transition at times depending on

43:38.667 --> 43:40.833
the program , isn't a singular problem

43:40.833 --> 43:42.889
and it's not just between JPO and so

43:42.889 --> 43:44.945
the transition playbook to make sure

43:44.945 --> 43:47.389
we're putting a finer point on . It is

43:47.389 --> 43:49.500
not just about the transition . It is

43:49.500 --> 43:51.800
also about forecasting for the test and

43:51.800 --> 43:54.820
evaluation community so that they have

43:54.820 --> 43:57.209
the methodologies , workforce , actual

43:57.209 --> 44:00.070
equipment , infrastructure , labs

44:00.070 --> 44:02.070
necessary for the technology that's

44:02.070 --> 44:04.292
coming down the line . It's making sure

44:04.292 --> 44:06.459
that when we're looking at transitions

44:06.459 --> 44:08.514
and planning those out , that S&T is

44:08.514 --> 44:10.292
considering . Early on what the

44:10.292 --> 44:12.403
manufacturability of what some of the

44:12.403 --> 44:14.626
risks are in derisking early on in some

44:14.626 --> 44:16.848
of those considerations . It's not just

44:16.848 --> 44:18.959
about the transition , it's about how

44:18.959 --> 44:18.780
effective that's going to be deployed

44:19.050 --> 44:21.106
to the force and you guys working in

44:21.106 --> 44:23.272
combination help the other communities

44:23.272 --> 44:25.439
that are that are part of that overall

44:25.439 --> 44:27.439
systems to make sure fast speed and

44:27.439 --> 44:30.050
performance is recognized in that and

44:30.050 --> 44:32.419
it should be lauded as we kind of bear

44:32.419 --> 44:34.308
that out to try to make sure that

44:34.308 --> 44:36.586
that's tighter knit , not just putting .

44:37.020 --> 44:38.853
Good S&T on the shelf and hoping

44:38.853 --> 44:41.020
somebody picks it up is not the is not

44:41.020 --> 44:42.409
the recipe for success .

44:44.810 --> 44:47.032
Mr . Watson mentioned that there should

44:47.032 --> 44:50.040
be improvement on S&T informing

44:50.040 --> 44:53.530
requirements . What would be the CBDP's

44:53.530 --> 44:55.840
first step towards this desired

44:55.840 --> 44:58.139
improvement ? Uh ,

44:59.919 --> 45:02.889
so . I'm gonna punt on this one and

45:02.889 --> 45:05.250
stuff only because the reason being is

45:05.250 --> 45:07.209
I have very , I have very specific

45:07.209 --> 45:09.265
things in mind and stuff , but those

45:09.265 --> 45:11.376
aren't necessarily correct and so the

45:11.376 --> 45:13.899
services do this far better and stuff

45:13.899 --> 45:15.843
as far as their S&T requirements .

45:16.090 --> 45:18.850
There are certain organizational and

45:18.850 --> 45:20.739
layouts of how the Kim Bioeffense

45:20.739 --> 45:23.017
program is organized with our partners ,

45:23.017 --> 45:25.017
and we're working through that very

45:25.017 --> 45:27.017
closely with our joint requirements

45:27.017 --> 45:28.961
office and also with our executive

45:28.961 --> 45:30.906
agent and stuff . And we have very

45:30.906 --> 45:33.128
large designs on on how that's going to

45:33.128 --> 45:35.183
change to start improving across the

45:35.183 --> 45:37.183
lanes , but I don't want to preempt

45:37.183 --> 45:39.350
Major General Collins in the work that

45:39.350 --> 45:41.517
he and his team are laying out , and I

45:41.517 --> 45:43.683
mean that earnestly is like in the end

45:43.683 --> 45:45.739
it is them along with the EA they're

45:45.739 --> 45:49.290
going to help to understand how because

45:49.290 --> 45:51.234
the S&T portion , some of that was

45:51.234 --> 45:53.401
backed into the risk portion of that ,

45:53.401 --> 45:55.457
but as we move towards the cap , the

45:55.457 --> 45:57.623
capability portfolio management that's

45:57.623 --> 45:59.734
been directed to us by the DOD . That

45:59.734 --> 46:01.957
means that things like our ICTs and the

46:01.957 --> 46:03.957
JSIDDS process are going to have to

46:03.957 --> 46:06.290
change in the way that they assess that .

46:06.290 --> 46:08.457
The main thing is that we maintain the

46:08.457 --> 46:10.457
services involvement , complete and

46:10.457 --> 46:12.568
absolute involvement in how how those

46:12.568 --> 46:15.479
capabilities are defined and how S&T

46:15.479 --> 46:18.229
needs to have a stronger voice in along

46:18.229 --> 46:20.285
with our operational and acquisition

46:20.285 --> 46:22.396
folks in this type of forum , but I'm

46:22.396 --> 46:24.229
going to reserve the . Right for

46:24.229 --> 46:26.451
General Collins to kind of come back on

46:26.451 --> 46:28.618
how because it's actually assigned . I

46:28.618 --> 46:30.840
had assigned it in the memo for the S&T

46:30.840 --> 46:33.070
as a responsibility for Dr . K working

46:33.070 --> 46:36.750
with with uh with uh General Collins to

46:36.750 --> 46:38.750
make sure that they figured out . I

46:38.750 --> 46:40.972
don't know the right way that is . What

46:40.972 --> 46:42.750
I do know is it's not happening

46:42.750 --> 46:44.861
adequately right now and that has , I

46:44.861 --> 46:46.806
can see the impact of that . So if

46:46.806 --> 46:50.570
that's fair . No , I , I , I , I agree ,

46:50.659 --> 46:52.770
you know , it's , it's a conversation

46:52.770 --> 46:54.937
that we're starting to figure out what

46:54.937 --> 46:57.159
that process is gonna look like , and I

46:57.159 --> 46:59.381
don't really don't want to get ahead of

46:59.381 --> 47:01.159
that either . So Doctor K , you

47:01.159 --> 47:02.826
mentioned uh relationship and

47:02.826 --> 47:04.770
partnerships with universities and

47:04.770 --> 47:07.020
different programs earlier , so this

47:07.020 --> 47:09.187
question says , what are your thoughts

47:09.187 --> 47:12.030
on partnering with academia ? Allowing

47:12.030 --> 47:14.070
us to realize the immense pool of

47:14.070 --> 47:16.270
talent and innovation while also

47:16.270 --> 47:18.389
keeping our research secure since

47:18.389 --> 47:20.709
universities have a large international

47:20.709 --> 47:23.929
student population . So . You know this

47:23.929 --> 47:27.479
is , this is a real problem . We

47:27.479 --> 47:31.409
have very effective processes in

47:31.409 --> 47:33.969
place to make sure that we're , you

47:33.969 --> 47:36.250
know , getting after the best

47:36.250 --> 47:38.306
information , getting after the best

47:38.306 --> 47:40.489
technologies , you know , partnering

47:40.489 --> 47:43.209
with the smartest people . But we also

47:43.209 --> 47:45.431
have a responsibility of making sure we

47:45.431 --> 47:47.600
protect that information , right ? So

47:48.010 --> 47:50.959
it is , you know , one thing that we do

47:51.350 --> 47:54.050
is we start a lot of our work in the

47:54.050 --> 47:56.370
basic research area . So a lot of the

47:56.370 --> 47:59.280
fundamental work that we do , um ,

48:00.050 --> 48:02.080
allows us to set the stage for the

48:02.080 --> 48:04.247
further development that we have to do

48:04.247 --> 48:06.358
later . So we have to build the right

48:06.358 --> 48:09.969
partnerships , um , and start early . I

48:09.969 --> 48:12.025
think that's that's one , you know ,

48:12.025 --> 48:14.302
one way that we can do that . You know ,

48:14.302 --> 48:16.525
the other is we just have to go through

48:16.525 --> 48:18.747
the process , right ? We need , we need

48:18.747 --> 48:21.600
the academia and our academic partners

48:22.090 --> 48:24.090
to be good partners with us in this

48:24.090 --> 48:26.146
space . So we're , you know , one of

48:26.146 --> 48:29.129
the things that that we often find that

48:29.129 --> 48:31.409
slows the process down is just .

48:33.389 --> 48:35.389
Getting the universities to kind of

48:35.389 --> 48:38.030
work with us and getting them to

48:38.030 --> 48:40.030
understand the requirements that we

48:40.030 --> 48:42.909
have and once they do , we have very

48:42.909 --> 48:45.020
effective partnerships , right ? Once

48:45.020 --> 48:47.076
we kind of get all get on the on the

48:47.076 --> 48:49.459
same page we've been very , very good

48:49.459 --> 48:51.570
and very , very effective at building

48:51.570 --> 48:53.626
those partnerships . It just takes a

48:53.626 --> 48:55.348
while to get there sometimes .

48:57.600 --> 49:01.189
I can't improve on him . Yeah .

49:03.300 --> 49:05.300
Our next question , how do you both

49:05.300 --> 49:08.370
define integrated early warning ? It is

49:08.370 --> 49:12.000
the concept something that intended for

49:12.000 --> 49:14.056
operational level or strategic level

49:14.056 --> 49:15.833
decision making ? That's a good

49:15.833 --> 49:17.889
question . Integra early warnings as

49:17.889 --> 49:19.833
close as it , I mean , to what the

49:19.833 --> 49:21.889
words actually say it is integrating

49:21.889 --> 49:24.056
different modalities and functions and

49:24.056 --> 49:25.944
trying to buy down risk and early

49:25.944 --> 49:28.056
across the thing . And like we said ,

49:28.056 --> 49:30.278
it's about fidelity of information from

49:30.278 --> 49:32.500
binary indicators and subtle indicators

49:32.500 --> 49:34.278
and even if we're talking bio ,

49:34.278 --> 49:36.444
environmental and other indicators and

49:36.444 --> 49:38.611
stuff all the way again , just like in

49:38.611 --> 49:40.556
integrated air missile defense and

49:40.556 --> 49:42.389
stuff , we're looking at overall

49:42.389 --> 49:44.500
surveillance and passing off the fire

49:44.500 --> 49:46.833
control radars and it's not that binary ,

49:46.833 --> 49:46.679
but the point being is that integrated

49:46.679 --> 49:49.199
early warning is not meant for only you

49:49.199 --> 49:51.255
make decisions throughout the system

49:51.255 --> 49:53.143
and that doesn't matter if it's a

49:53.143 --> 49:55.310
carrier . He captain making a decision

49:55.310 --> 49:57.532
on whether we had something going on in

49:57.532 --> 49:57.439
his boat versus at the combatant

49:57.439 --> 49:59.500
command versus the overall DOD and

49:59.500 --> 50:02.280
nation and stuff integrated warning

50:02.280 --> 50:04.391
simply means that that we cannot look

50:04.391 --> 50:06.558
at singular solutions , singular point

50:06.558 --> 50:08.879
detectors , singular applications . We

50:08.879 --> 50:10.919
need to look at the way in which

50:10.919 --> 50:13.141
they're employed because that matters a

50:13.141 --> 50:15.363
great deal . That doctrine matters in a

50:15.363 --> 50:17.586
great deal and stuff and how we do that

50:17.586 --> 50:19.697
because we'll spend ourselves again .

50:19.697 --> 50:21.808
Outside of coin and outside of GWAT ,

50:21.808 --> 50:23.975
we spend a lot of fun . We spend it on

50:23.975 --> 50:26.030
our particular services , but we did

50:26.030 --> 50:28.141
spend a lot on focus on our technical

50:28.141 --> 50:30.252
forces and special forces and some of

50:30.252 --> 50:32.363
our special operations forces . As we

50:32.363 --> 50:34.419
look at the total force , how do you

50:34.419 --> 50:36.419
actually do integrate early warning

50:36.419 --> 50:38.530
across the vastness of something like

50:38.530 --> 50:40.530
the Indo Paycom against a near peer

50:40.530 --> 50:42.530
competitor someone something a near

50:42.530 --> 50:45.229
peer competitor in that area ? That

50:45.229 --> 50:47.396
requires us to make sure we're looking

50:47.396 --> 50:49.396
at all the modalities , how they're

50:49.396 --> 50:51.507
outlay , or like I said , we'll spend

50:51.507 --> 50:53.507
ourselves into the into the earth ,

50:53.507 --> 50:55.618
right ? And so that's what it means .

50:55.618 --> 50:57.451
It's not for a single , a single

50:57.451 --> 50:59.507
consumer . It is for up and down the

50:59.507 --> 51:01.673
chain . It is about how the technology

51:01.673 --> 51:01.070
is brought to bear to give us the early

51:01.070 --> 51:03.070
warning and decision making that we

51:03.070 --> 51:05.237
need necessary to respond , and it has

51:05.237 --> 51:07.126
to be integrated not as something

51:07.126 --> 51:09.292
that's unique to Cambio again , put on

51:09.292 --> 51:12.389
top of JAD C and CAD C2 through CSC2

51:12.389 --> 51:14.500
into common operating . Pictures that

51:14.500 --> 51:16.445
is part of what the commanders are

51:16.445 --> 51:18.445
seeing holistically . It's not over

51:18.445 --> 51:20.556
here . It's just a chem bio problem .

51:20.620 --> 51:22.620
It is part of the overall situation

51:22.620 --> 51:24.509
awareness which they're doing and

51:24.509 --> 51:26.731
that's why just like any other things ,

51:26.731 --> 51:28.620
there are a lot of sensors on UAV

51:28.620 --> 51:30.842
satellites , national technical means .

51:30.842 --> 51:33.009
They're all integrated for situational

51:33.009 --> 51:32.419
awareness , and we have a

51:32.419 --> 51:35.939
responsibility to be part of that . So ,

51:36.020 --> 51:38.242
you want to add I have nothing to add .

51:38.242 --> 51:42.030
OK . OK , time . If

51:42.030 --> 51:45.070
you're you . There's , there's our

51:45.070 --> 51:49.070
budget money . If your budget were to

51:49.070 --> 51:51.830
double , where and how would you deploy

51:51.830 --> 51:54.229
the new money ? Oh wow . The first

51:54.229 --> 51:57.860
thing I would do . I get our basic

51:57.860 --> 52:00.082
research dollars back up . You know , I

52:00.082 --> 52:03.699
think , unfortunately we have taken a

52:03.699 --> 52:07.060
real hit over the years . We've watched

52:07.060 --> 52:09.580
our basic research dollars dwindle as a

52:09.580 --> 52:12.129
part of our portfolio . And a lot of

52:12.129 --> 52:15.399
that was , you know , because You know

52:15.399 --> 52:17.510
how it was being managed and the fact

52:17.510 --> 52:19.621
that it wasn't being spent as fast as

52:19.621 --> 52:21.979
it should , um , but I would start by

52:22.419 --> 52:24.530
really getting after our seed corn as

52:24.530 --> 52:26.586
we like to call it , and making sure

52:26.586 --> 52:28.808
that we're getting out there and really

52:28.808 --> 52:31.030
looking at those early new technologies

52:31.030 --> 52:33.239
that that will be the future of what

52:33.239 --> 52:35.295
we're doing in chem biodefense , you

52:35.295 --> 52:37.628
know , that that is where I would start .

52:37.919 --> 52:40.879
You know , next , I think , you know ,

52:41.409 --> 52:43.353
all parts of our portfolio could ,

52:43.360 --> 52:45.530
could use more , right , and I think ,

52:46.010 --> 52:49.889
you know , we have our S&P

52:49.889 --> 52:52.056
objectives , we have a lot of problems

52:52.056 --> 52:55.040
to solve right now , you know , and I

52:55.040 --> 52:58.239
think , you know , we , we . I don't

52:58.239 --> 53:00.239
know that I would ask to double our

53:00.239 --> 53:03.469
budget right now with where we are

53:03.840 --> 53:06.007
because I think we have some more work

53:06.007 --> 53:08.389
as we're trying to refine our our

53:08.919 --> 53:11.030
structures and making sure that we're

53:11.030 --> 53:13.141
spending the money that we do have in

53:13.141 --> 53:16.229
the most effective way possible , but

53:16.489 --> 53:18.433
You know , there are certainly big

53:18.433 --> 53:20.378
problems that we have to solve and

53:20.378 --> 53:22.433
there are lots of , as you mentioned

53:22.433 --> 53:24.545
earlier , deferred risk , right ? You

53:24.545 --> 53:26.711
know , we're we're , we're not gonna ,

53:26.711 --> 53:28.933
we are , we are taking risks in certain

53:28.933 --> 53:30.989
areas because we can get coverage in

53:30.989 --> 53:34.189
others , um , but I again , I , I would ,

53:34.270 --> 53:36.500
I would , my , my primary focus would

53:36.500 --> 53:39.570
be to return our basic research , uh ,

53:39.870 --> 53:43.300
dollars back to where , back to a more

53:44.020 --> 53:45.742
Reasonable level of our of our

53:45.742 --> 53:49.719
portfolio . Yeah . I think

53:49.719 --> 53:51.719
anybody that knows me and stuff , I

53:51.719 --> 53:53.775
mean , outside of being a glass half

53:53.775 --> 53:55.497
empty and poison kind of guy ,

53:55.497 --> 53:57.608
literally I'm critical of our program

53:57.608 --> 53:59.608
in the past and so , meaning not on

53:59.608 --> 54:01.889
what we produce , but the efficiency

54:01.889 --> 54:04.000
and effectiveness by which we've gone

54:04.000 --> 54:06.167
so our systems have been broken across

54:06.167 --> 54:07.778
the requirements of advanced

54:07.778 --> 54:09.945
development , S&T , and governance for

54:09.945 --> 54:12.056
quite some time , and those have made

54:12.056 --> 54:14.222
significant recovery . And what I mean

54:14.222 --> 54:16.222
by that is if had you asked me this

54:16.222 --> 54:16.080
question two years ago , I would have

54:16.080 --> 54:18.080
said there's no way you should give

54:18.080 --> 54:20.302
Kimbio Defense additional funding until

54:20.302 --> 54:22.358
we demonstrate back to Congress , we

54:22.358 --> 54:24.580
demonstrate back to the Comptroller and

54:24.580 --> 54:26.747
to our to our leadership on how that's

54:26.747 --> 54:28.802
applied against strategic priorities

54:28.802 --> 54:30.858
and stuff . A lot of that work which

54:30.858 --> 54:30.760
we've talked about over the course of

54:30.760 --> 54:32.982
these last couple of days has been well

54:32.982 --> 54:35.399
set largely in part to the leadership

54:35.399 --> 54:37.621
that's in there , but really the people

54:37.621 --> 54:39.788
that have leaned into . So I I know as

54:39.788 --> 54:41.788
far as S&T organizations across the

54:41.788 --> 54:43.955
entirety of the DOD , but particularly

54:43.955 --> 54:46.177
within defense wide funds , we now have

54:46.177 --> 54:48.288
one of the best execution rates , not

54:48.288 --> 54:50.510
obligation rates across the board , and

54:50.510 --> 54:52.732
that's due to hard work . But that with

54:52.732 --> 54:54.955
it comes a lot of credibility back with

54:54.955 --> 54:57.121
the Comptour and a lot when we go into

54:57.121 --> 54:59.288
the PBCB system and ask for additional

54:59.288 --> 55:01.343
funding . We've gained an additional

55:01.343 --> 55:03.343
$1.2 billion over the course of the

55:03.343 --> 55:04.955
last two years because we've

55:04.955 --> 55:07.177
demonstrated at times where we're going

55:07.177 --> 55:09.399
to apply that needed it . So if you ask

55:09.399 --> 55:11.455
me we're spitting spitting if we got

55:11.455 --> 55:13.621
double today , I would take it , but I

55:13.621 --> 55:13.439
would again come back to my partners on

55:13.439 --> 55:15.661
this . They have S&T objectives , and I

55:15.661 --> 55:17.959
think it talks about how much more risk

55:17.959 --> 55:20.389
we put against those , how far lean out ,

55:20.639 --> 55:22.750
how many more parallel efforts to get

55:22.750 --> 55:25.179
after those really . Those S&T

55:25.179 --> 55:27.068
objectives are there for a reason

55:27.068 --> 55:29.290
because we need to get them , they need

55:29.290 --> 55:31.512
to become compromised . They need to be

55:31.512 --> 55:33.735
addressed , and there are a lot of ways

55:33.735 --> 55:33.429
to go about that . There are no

55:33.429 --> 55:35.669
singular routes and if we and so I

55:35.669 --> 55:37.909
think that money goes a long way to how

55:37.909 --> 55:41.879
risky our S&T . Partners

55:41.879 --> 55:44.239
here and our colleagues can be and how

55:44.239 --> 55:46.406
many different paths we want to get to

55:46.406 --> 55:48.600
a solution to close it out faster and

55:48.600 --> 55:50.600
also more resolutely with broad

55:50.600 --> 55:52.767
spectrum applications . So I would , I

55:52.767 --> 55:54.933
would double down on the S&T side very

55:54.933 --> 55:56.878
heavily and stuff on those areas .

55:57.639 --> 56:01.520
Thank you . The next

56:01.520 --> 56:03.576
question is what are your strategies

56:03.576 --> 56:05.870
for articulating the value of S&T to

56:05.870 --> 56:08.030
the larger DOD and more importantly

56:08.030 --> 56:10.790
perhaps Congress ? The National Defense

56:10.790 --> 56:14.469
S&T strategy is like a 14-page document .

56:15.540 --> 56:17.979
But a page and a half out of a 14 page

56:17.979 --> 56:20.860
document is spent on strategic

56:20.860 --> 56:24.060
communications and the value of making

56:24.060 --> 56:26.227
sure that we do exactly this , that we

56:26.227 --> 56:28.500
tell that we're communicating the value

56:28.500 --> 56:31.449
of what we what we're doing so that way

56:31.449 --> 56:35.350
the the services , Congress , you know ,

56:35.379 --> 56:37.820
our stakeholders really know and

56:37.820 --> 56:39.820
continue to support the investments

56:39.820 --> 56:41.459
that we're making in S&T and

56:41.459 --> 56:45.280
modernization . So I

56:45.280 --> 56:47.560
think one thing that we do for

56:47.560 --> 56:49.727
articulating the value is number one ,

56:49.959 --> 56:51.903
so that we're good stewards of the

56:51.903 --> 56:54.330
dollars that we do get . So you know

56:55.080 --> 56:58.479
it's been a focus of ours to make sure

56:58.479 --> 57:01.320
that you know we are spending dollars

57:01.320 --> 57:04.080
the right way , that we're hitting goal ,

57:04.199 --> 57:06.421
that we're obligating our money when we

57:06.421 --> 57:08.588
get it , that we're getting it out the

57:08.588 --> 57:10.755
door , that our internal processes are

57:10.755 --> 57:13.969
optimized so that way . We're showing

57:13.969 --> 57:15.919
that we , when you give us money ,

57:16.129 --> 57:18.296
we're able to use it , right ? I think

57:18.296 --> 57:20.573
that's the number one thing that we do .

57:20.573 --> 57:23.149
The #2 thing that we do . It's events

57:23.149 --> 57:24.927
like this , right , where we're

57:24.927 --> 57:27.310
actually out there bringing folks

57:27.310 --> 57:30.310
together , we are showing the value ,

57:30.350 --> 57:32.628
the breadth of what we're investing in .

57:33.010 --> 57:35.229
The return on investment that we get ,

57:35.600 --> 57:37.439
you know , I think that's very

57:37.439 --> 57:40.030
important that we're capturing that

57:40.030 --> 57:42.250
return on investment , that when they

57:42.520 --> 57:45.790
give us that dollar , we can trace it

57:45.790 --> 57:48.719
to new capability that the warfighters

57:48.719 --> 57:51.639
have that that build them more combat

57:51.639 --> 57:54.600
power , right , that we're not , you

57:54.600 --> 57:56.840
know , spending money on science fair

57:56.840 --> 57:59.239
projects that we're actually taking

57:59.239 --> 58:01.350
that investment . And delivering

58:01.350 --> 58:03.560
something that brings additional

58:03.560 --> 58:05.750
capability and strength back to the

58:05.750 --> 58:09.189
force . And in Congress , you know ,

58:09.270 --> 58:12.290
this is something that we've been Um ,

58:12.469 --> 58:14.580
working on , I think I , I think it's

58:14.580 --> 58:16.750
fair to say , you know , very , very

58:16.750 --> 58:18.917
hard , you know , we've been up to the

58:18.917 --> 58:21.083
hill numerous times this year , really

58:21.083 --> 58:23.459
trying to let our , you know ,

58:23.629 --> 58:26.989
congressional staffers and and congress

58:26.989 --> 58:30.310
people understand . The real challenge

58:30.669 --> 58:34.469
that CBDP , you know , is facing right

58:34.469 --> 58:37.429
now , the threat is really real , as I

58:37.429 --> 58:39.318
said yesterday . This is not some

58:39.318 --> 58:42.870
obscure threat , and it's as Bad Watson

58:42.870 --> 58:45.429
says , you know , chembao is a

58:45.429 --> 58:47.750
condition on every mission . It's not a

58:47.750 --> 58:50.149
mission in itself , it's a condition on

58:50.149 --> 58:52.030
every single mission that our

58:52.030 --> 58:54.389
warfighters face , and I think that's

58:54.389 --> 58:57.510
really important for You know , our

58:57.510 --> 59:00.040
congress people and their staff to

59:00.040 --> 59:03.439
understand is how , number one ,

59:03.959 --> 59:05.959
that idea that it is a condition on

59:05.959 --> 59:08.126
every mission but also under to how it

59:08.126 --> 59:10.292
nests in our national defense strategy

59:10.479 --> 59:12.909
and how we're we're not just some

59:12.909 --> 59:15.520
obscure , you know , like you said , a

59:15.520 --> 59:18.979
coin operation or You know , and , uh ,

59:18.989 --> 59:21.830
you know , this is , this is a big part

59:22.229 --> 59:24.830
of great power competition as as Max

59:24.830 --> 59:27.030
pointed out really , really well this

59:27.030 --> 59:29.310
morning . So I think that is something

59:29.310 --> 59:31.532
that we have to do a really good job of

59:31.532 --> 59:33.199
making sure you know that our

59:33.199 --> 59:35.159
leadership understands just how

59:35.159 --> 59:37.520
important the space is . Let's say the

59:37.520 --> 59:39.742
other part that on the Bob since I love

59:39.742 --> 59:41.853
the question because I would just put

59:41.853 --> 59:43.853
that on , it'd be , it is the value

59:43.853 --> 59:46.949
articulation , you know , 12 sides one ,

59:47.120 --> 59:49.176
not the value , but the threat . The

59:49.176 --> 59:51.287
threat's very difficult to be able to

59:51.287 --> 59:53.509
convey . We , let's be frank , I mean ,

59:53.509 --> 59:55.398
we're highly compartmented in the

59:55.398 --> 59:57.564
Kimbao area , more so than space , for

59:57.564 --> 59:59.898
goodness' sake , and it's really . Hard ,

59:59.898 --> 01:00:02.064
particularly across the rest of DOD at

01:00:02.064 --> 01:00:04.120
times and also with Congress to make

01:00:04.120 --> 01:00:06.176
the right people understand what the

01:00:06.176 --> 01:00:06.125
threat is with our near peer

01:00:06.125 --> 01:00:09.645
competitors and how that applies to to

01:00:09.645 --> 01:00:11.645
contributing to foiling our overall

01:00:11.645 --> 01:00:13.939
operational plans . We've gone a long

01:00:13.939 --> 01:00:16.320
way up to even the I mean up to the

01:00:16.320 --> 01:00:18.620
sect on chem bio-related and up and

01:00:18.620 --> 01:00:20.842
down the leadership and with Congress .

01:00:20.842 --> 01:00:22.787
There's a lot of value that's made

01:00:22.787 --> 01:00:24.787
large differences , particularly in

01:00:24.787 --> 01:00:26.898
some of the AORs on how they now view

01:00:26.898 --> 01:00:29.009
the contributions and the defense and

01:00:29.009 --> 01:00:31.231
part of integrated deterrence that chem

01:00:31.231 --> 01:00:33.176
bio defense plays in their ARs . I

01:00:33.176 --> 01:00:35.398
think the second thing is that we do to

01:00:35.398 --> 01:00:37.530
Bob's point , we're producing value .

01:00:37.580 --> 01:00:39.580
We're demonstrating how we're going

01:00:39.580 --> 01:00:41.699
against those threat profiles in a

01:00:41.699 --> 01:00:43.399
really unique way . But our

01:00:43.399 --> 01:00:45.790
communication has been . Let's just be

01:00:45.790 --> 01:00:49.169
clear . We're super techie when we talk

01:00:49.169 --> 01:00:51.280
to our congressionals , and the stuff

01:00:51.280 --> 01:00:53.391
we do is not super easy to explain at

01:00:53.391 --> 01:00:55.613
times . So things that we've just tried

01:00:55.613 --> 01:00:57.669
to do a little bit better is cutting

01:00:57.669 --> 01:01:00.050
hundreds of pages out of our J books

01:01:00.050 --> 01:01:02.050
and stuff to Congress . How does it

01:01:02.050 --> 01:01:03.828
read simply when we're actually

01:01:03.828 --> 01:01:05.994
briefing our congressional members and

01:01:05.994 --> 01:01:08.217
we're trying to talk about the impact ?

01:01:08.217 --> 01:01:10.328
We're not talking about the technical

01:01:10.328 --> 01:01:12.272
impact , we're talking about the .

01:01:12.272 --> 01:01:14.272
Because they see us now more as the

01:01:14.272 --> 01:01:16.217
part of the con contributor to the

01:01:16.217 --> 01:01:18.439
overall DOD strategy , right ? And so I

01:01:18.439 --> 01:01:20.661
think we've become way better at that .

01:01:20.661 --> 01:01:22.606
We still have work to do and we're

01:01:22.606 --> 01:01:24.661
often asked to come back and explain

01:01:24.661 --> 01:01:26.661
out certain really complex things ,

01:01:26.661 --> 01:01:26.439
particularly things like guide and

01:01:26.439 --> 01:01:28.550
stuff like that where we're trying to

01:01:28.550 --> 01:01:30.606
talk about AI solutions for antibody

01:01:30.606 --> 01:01:32.661
development and silica . But I think

01:01:32.661 --> 01:01:34.828
we've come a long way , but it is that

01:01:34.828 --> 01:01:36.717
articulation of value , how we're

01:01:36.717 --> 01:01:38.939
telling that story that's not unique to

01:01:38.939 --> 01:01:40.995
us , how we're pulling into everyone

01:01:40.995 --> 01:01:43.106
else into the overall mission set and

01:01:43.106 --> 01:01:45.389
how we're expressing that in not as

01:01:45.389 --> 01:01:47.445
technical ways . You can't help it .

01:01:48.070 --> 01:01:50.530
Bob doesn't agree . I think that those

01:01:50.530 --> 01:01:52.770
are really important aspects . Do you

01:01:52.770 --> 01:01:55.530
fear that that the funding is in any

01:01:55.530 --> 01:01:58.169
type of jeopardy to an audience as

01:01:58.169 --> 01:02:01.090
important as Congress or Say that again

01:02:01.090 --> 01:02:04.010
sorry , do you think that the funding

01:02:04.010 --> 01:02:06.121
could potentially down the road be in

01:02:06.121 --> 01:02:08.570
jeopardy to Congress who holds the

01:02:08.570 --> 01:02:10.348
purse strings , or is that just

01:02:10.348 --> 01:02:12.292
something that's not on your radar

01:02:12.292 --> 01:02:15.879
right now of concern ? I think I don't

01:02:15.879 --> 01:02:17.546
know if you mean in regard to

01:02:17.546 --> 01:02:19.379
administration change , priority

01:02:19.379 --> 01:02:21.580
changes and stuff . So one , I hope it

01:02:21.580 --> 01:02:23.580
is , we should always be at risk of

01:02:23.580 --> 01:02:25.636
losing our funding to other national

01:02:25.636 --> 01:02:27.802
priorities , and that's why we need to

01:02:27.802 --> 01:02:30.024
take serious the how we're utilizing it

01:02:30.024 --> 01:02:31.802
and we again need to be able to

01:02:31.802 --> 01:02:33.636
communicate the value that we're

01:02:33.636 --> 01:02:35.858
producing for it . Do I see right now a

01:02:35.858 --> 01:02:38.080
large shift in those ? No , I don't see

01:02:38.080 --> 01:02:40.080
either , and I think our leadership

01:02:40.080 --> 01:02:42.247
agrees a large shift either down or up

01:02:42.247 --> 01:02:44.358
right now , but we're going to see or

01:02:44.358 --> 01:02:46.691
even Ben , I don't know if you think so ,

01:02:46.691 --> 01:02:48.858
and you're In your area for the larger

01:02:48.858 --> 01:02:51.024
ditch portfolio , but I , I don't seem

01:02:51.024 --> 01:02:51.010
to see . I don't expect too many

01:02:51.010 --> 01:02:53.177
perturbations over the , at least this

01:02:53.177 --> 01:02:55.288
next year , but priorities change and

01:02:55.288 --> 01:02:57.379
they should . So Cotour is always

01:02:57.379 --> 01:02:59.370
looking for dollars too for the on

01:02:59.370 --> 01:03:03.310
Congress . OK , this next question from

01:03:03.310 --> 01:03:05.229
Charity Dean says Top Gun was

01:03:05.229 --> 01:03:07.118
incredible marketing for the next

01:03:07.118 --> 01:03:10.909
generation of fight pilots . Where

01:03:10.909 --> 01:03:13.149
can we expect a blockbuster movie about

01:03:13.149 --> 01:03:15.909
Kim biodefense and who should star in

01:03:15.909 --> 01:03:18.510
it ? So one , I think you're asked the

01:03:18.510 --> 01:03:20.732
wrong person question . You should have

01:03:20.732 --> 01:03:22.954
asked Max that this morning , and two ,

01:03:22.954 --> 01:03:25.177
I think Ian should start is not gonna .

01:03:25.177 --> 01:03:27.288
There's no , you're not gonna get the

01:03:27.288 --> 01:03:29.399
next generation of anything following

01:03:29.399 --> 01:03:31.399
me into that . No , I think some of

01:03:31.399 --> 01:03:33.399
those things , but we do need to be

01:03:33.399 --> 01:03:35.288
better at our marketing . I think

01:03:35.288 --> 01:03:37.454
Maxson talked about this today , but I

01:03:37.454 --> 01:03:39.949
mean , even . Shoot me and my folks , I

01:03:39.949 --> 01:03:41.838
just bad at names and stuff . The

01:03:41.838 --> 01:03:43.782
Netflix series that came out , the

01:03:43.782 --> 01:03:45.616
documentary that came out on the

01:03:45.616 --> 01:03:47.616
nuclear side of the house . Anybody

01:03:47.616 --> 01:03:46.790
remember the name , just shut it out .

01:03:48.350 --> 01:03:50.389
Thank you . So that documentarian ,

01:03:50.429 --> 01:03:52.651
right , very interested in reaching out

01:03:52.651 --> 01:03:54.762
and stuff like that and talking about

01:03:54.762 --> 01:03:56.985
what that might look like from a Kimbio

01:03:56.985 --> 01:03:59.151
perspective and stuff , and we need to

01:03:59.151 --> 01:03:58.860
take the time to talk to those folks as

01:03:58.860 --> 01:04:01.310
they tell our story more readily . And

01:04:01.310 --> 01:04:03.254
I think we have , and I think it's

01:04:03.254 --> 01:04:05.366
great to have Max and I think the way

01:04:05.366 --> 01:04:07.532
we talk to , but Charity's right , and

01:04:07.532 --> 01:04:09.754
others , we do like Max say need to use

01:04:09.754 --> 01:04:11.699
others . Or better voices and tell

01:04:11.699 --> 01:04:13.977
because it's not a story on what we do .

01:04:13.977 --> 01:04:16.088
It's a story about overall biological

01:04:16.088 --> 01:04:18.254
and chemical use and that's that's one

01:04:18.254 --> 01:04:19.921
that has endured and has been

01:04:19.921 --> 01:04:22.143
throughout our history , and we kind of

01:04:22.143 --> 01:04:24.032
say the same things as far as the

01:04:24.032 --> 01:04:26.143
storytelling , and I think we do need

01:04:26.143 --> 01:04:26.123
some help . I didn't realize that

01:04:26.123 --> 01:04:27.833
really until Max said it as I

01:04:27.833 --> 01:04:30.111
inadequately tried to convey our story .

01:04:30.111 --> 01:04:32.111
Oftentimes myself , probably to the

01:04:32.111 --> 01:04:34.277
detriment of the program , but I don't

01:04:34.277 --> 01:04:36.456
know . So to charity , I don't know if

01:04:36.456 --> 01:04:38.678
you'll have any , it's certainly not us

01:04:38.678 --> 01:04:40.789
two up on here that's going to be the

01:04:40.789 --> 01:04:42.900
star in it , but I do believe that we

01:04:42.900 --> 01:04:45.012
need to have more engagement with our

01:04:45.012 --> 01:04:47.012
type of media that we're also going

01:04:47.012 --> 01:04:49.067
with in different ways to talk about

01:04:49.067 --> 01:04:51.178
what we're actually working against .

01:04:52.110 --> 01:04:53.832
Is Andy Weber going to put out

01:04:53.832 --> 01:04:55.943
Operation Fire anytime soon like that

01:04:55.943 --> 01:04:58.221
that was supposed to work , but anyway ,

01:04:58.221 --> 01:05:00.221
Stephen Bland says how important is

01:05:00.221 --> 01:05:02.054
allied biodefense engagement and

01:05:02.054 --> 01:05:04.277
integrated knowledge management in both

01:05:04.277 --> 01:05:06.510
setting requirements and capability

01:05:06.510 --> 01:05:08.629
development and the delivery of a

01:05:08.629 --> 01:05:11.310
global biodefense capability . We both

01:05:11.310 --> 01:05:13.477
said , you know , in both of our talks

01:05:13.477 --> 01:05:15.477
earlier how important it is that we

01:05:15.477 --> 01:05:17.588
engage with our partners , you know ,

01:05:17.588 --> 01:05:21.159
we , we multiply our our . Our

01:05:21.159 --> 01:05:23.520
investments when we work with our

01:05:23.520 --> 01:05:25.520
partners , you know , we're able to

01:05:25.520 --> 01:05:28.439
align and really , you know , enhance

01:05:28.439 --> 01:05:30.669
the value of every dollar we spend ,

01:05:31.000 --> 01:05:32.944
but I think the other thing that's

01:05:32.944 --> 01:05:35.167
important to understand and that we all

01:05:35.167 --> 01:05:37.280
saw is that , you know , biodefense

01:05:37.280 --> 01:05:39.502
doesn't know a border , you know , we ,

01:05:39.502 --> 01:05:42.159
we've got to be able to work across the

01:05:42.159 --> 01:05:44.381
world , you know , and , and especially

01:05:44.381 --> 01:05:46.603
when you look at Indo Paycom , which is

01:05:46.603 --> 01:05:49.280
what , 51% of the . You know , the

01:05:49.280 --> 01:05:52.959
surface of the earth , you know , bio

01:05:52.959 --> 01:05:55.181
defense is not going to know a border ,

01:05:55.181 --> 01:05:57.403
so we , we have to be able to work with

01:05:57.403 --> 01:05:59.626
our partners to really stay in front of

01:05:59.626 --> 01:06:01.850
this problem . And so the question

01:06:01.850 --> 01:06:04.072
focuses also , I mean , specifically on

01:06:04.072 --> 01:06:06.072
setting requirements and capability

01:06:06.072 --> 01:06:08.406
development and so I mean . To be clear ,

01:06:08.406 --> 01:06:10.572
I mean , for the most part , we said ,

01:06:10.572 --> 01:06:12.628
and that comes , that comes from our

01:06:12.628 --> 01:06:14.794
operational and priorities in national

01:06:14.794 --> 01:06:16.961
strategy . We set our requirements and

01:06:16.961 --> 01:06:19.128
capability development . Those help us

01:06:19.128 --> 01:06:21.294
in determining where the best place to

01:06:21.294 --> 01:06:23.239
match up with our partners overall

01:06:23.239 --> 01:06:22.959
requirements , capability and

01:06:22.959 --> 01:06:24.570
priorities as well , and the

01:06:24.570 --> 01:06:26.737
opportunities to actually leverage one

01:06:26.737 --> 01:06:28.848
another for best effect and do that .

01:06:29.129 --> 01:06:31.129
And as we try to move for things in

01:06:31.129 --> 01:06:33.129
KimbiO2 , and we do this in certain

01:06:33.129 --> 01:06:35.370
spaces as we not only look for not only

01:06:35.370 --> 01:06:37.481
how we augment one another , and that

01:06:37.481 --> 01:06:39.314
can be in testing and evaluation

01:06:39.314 --> 01:06:41.259
facilities all the way to actually

01:06:41.259 --> 01:06:43.314
capability development , we look for

01:06:43.314 --> 01:06:45.537
opportunities that are very similar . I

01:06:45.537 --> 01:06:47.481
mean we talk interoperability very

01:06:47.481 --> 01:06:47.239
often , but some of that

01:06:47.239 --> 01:06:49.517
interchangeability needs to happen too ,

01:06:49.517 --> 01:06:51.683
again , just like with our UK partners

01:06:51.683 --> 01:06:53.739
when the when the US boomer goes off

01:06:53.739 --> 01:06:55.860
station in North Atlantic . And a UK

01:06:55.860 --> 01:06:57.471
boomer comes on site that is

01:06:57.471 --> 01:06:59.416
interchangeable . There is no lost

01:06:59.416 --> 01:07:01.471
emission or the coverage between the

01:07:01.471 --> 01:07:03.193
two , and I think we need more

01:07:03.193 --> 01:07:04.749
opportunities as we look at

01:07:04.749 --> 01:07:06.749
requirements and capabilities where

01:07:06.749 --> 01:07:08.971
that interchangeability of mission sets

01:07:08.971 --> 01:07:11.082
with some of our allies in NATO needs

01:07:11.082 --> 01:07:10.659
to be realized versus just some of the

01:07:10.659 --> 01:07:12.881
interoperability on stanags and stuff .

01:07:12.881 --> 01:07:15.103
But when it comes to projects and other

01:07:15.103 --> 01:07:17.159
things we do , those get set against

01:07:17.159 --> 01:07:19.103
our requirements juxtaposed to the

01:07:19.103 --> 01:07:19.060
requirements and priorities of our

01:07:19.060 --> 01:07:21.004
allies . There's where some of the

01:07:21.004 --> 01:07:23.004
really richness comes in that we're

01:07:23.004 --> 01:07:24.838
augmenting one another , right .

01:07:27.909 --> 01:07:30.469
Joshua Smith's question is , with the

01:07:30.469 --> 01:07:33.070
long product fielding timeline , how do

01:07:33.070 --> 01:07:35.260
we keep up with the emerging tactics

01:07:35.590 --> 01:07:37.629
and expeditionary requirements ?

01:07:37.760 --> 01:07:40.540
Currently , most equipment is outdated

01:07:40.540 --> 01:07:42.750
by the time war fighters are fielded

01:07:42.750 --> 01:07:44.639
the equipment . You hit on this a

01:07:44.639 --> 01:07:46.917
little bit earlier and you both . Yeah ,

01:07:46.917 --> 01:07:50.100
I mean , the number one thing is

01:07:50.590 --> 01:07:53.629
reforming how , you know , what we have

01:07:53.629 --> 01:07:55.407
to do is take that long product

01:07:55.407 --> 01:07:57.296
fielding timeline and shrink it .

01:07:57.709 --> 01:07:59.987
Because if we're continuing , you know ,

01:08:00.550 --> 01:08:04.110
we operate in a fast evolving space by

01:08:04.110 --> 01:08:06.110
the nature of the threat that we're

01:08:06.110 --> 01:08:08.179
we're trying to counter . So what we

01:08:08.179 --> 01:08:10.100
have to do is do a better job of

01:08:10.100 --> 01:08:12.110
shrinking that product fielding

01:08:12.110 --> 01:08:14.070
timeline , making sure that we're

01:08:14.070 --> 01:08:16.390
communicating what's coming so the

01:08:16.390 --> 01:08:18.501
services are ready to receive it , to

01:08:18.501 --> 01:08:21.270
make sure that , you know , the JPO is

01:08:21.270 --> 01:08:23.437
ready to do its advanced development .

01:08:23.680 --> 01:08:25.979
Um , and also making sure that the

01:08:25.979 --> 01:08:28.146
requirements are there , you know , by

01:08:28.146 --> 01:08:30.312
being in that continuous feedback loop

01:08:30.312 --> 01:08:34.009
between S&T and , you know , and our ,

01:08:34.140 --> 01:08:36.660
you know , JRO partners , making sure

01:08:36.660 --> 01:08:39.020
that everybody that that S&T is

01:08:39.020 --> 01:08:41.839
informing what the art of the possible

01:08:41.839 --> 01:08:44.620
is . So I think that . You know , we'll

01:08:44.620 --> 01:08:47.020
go a long way of just basically

01:08:47.020 --> 01:08:50.000
reforming our practices and fixing this

01:08:50.000 --> 01:08:52.220
problem , and it's not just outdated

01:08:52.220 --> 01:08:54.490
equipment . I mean , let's be clear .

01:08:55.438 --> 01:08:57.738
As the JRO and as we do assessments on

01:08:57.738 --> 01:08:59.738
trip wires and things that actually

01:08:59.738 --> 01:09:02.579
divestiture by services of can buy

01:09:02.579 --> 01:09:04.858
overlay equipment , it's the timelines

01:09:04.858 --> 01:09:07.099
that not only that they're outdated .

01:09:07.869 --> 01:09:09.647
They're they're not , we're not

01:09:09.647 --> 01:09:11.591
delivering in time frames that are

01:09:11.591 --> 01:09:13.647
actually aligned with the concepts .

01:09:13.647 --> 01:09:15.813
And when we switch over concepts , and

01:09:15.813 --> 01:09:18.091
that's what happens with the Air Force ,

01:09:18.091 --> 01:09:20.313
not like they didn't want AVCAD , their

01:09:20.313 --> 01:09:22.425
operational concept changed under the

01:09:22.425 --> 01:09:21.659
National Defense strategy and how

01:09:21.659 --> 01:09:23.881
they're going to fight , so they divest

01:09:23.881 --> 01:09:25.937
from it a sensor which brings up the

01:09:25.937 --> 01:09:28.159
cost to all the other services that now

01:09:28.159 --> 01:09:30.215
have to they're going to continue to

01:09:30.215 --> 01:09:32.339
pursue pursue that capability . Our

01:09:32.339 --> 01:09:34.560
development timelines are too , too

01:09:34.560 --> 01:09:36.616
long . Everything in the strategy is

01:09:36.616 --> 01:09:38.830
designed from from streamlining

01:09:38.830 --> 01:09:41.052
business processes and making it faster

01:09:41.052 --> 01:09:43.274
to the way we're doing S&T and advanced

01:09:43.274 --> 01:09:45.163
development and incrementalism to

01:09:45.163 --> 01:09:47.386
reforming requirements . All of it's in

01:09:47.386 --> 01:09:49.441
the service of getting things faster

01:09:49.441 --> 01:09:51.497
and capabilities to the war fighters

01:09:51.497 --> 01:09:53.608
sooner . It doesn't need to be an all

01:09:53.608 --> 01:09:55.774
or nothing proposition . We don't need

01:09:55.774 --> 01:09:57.997
to go to watch everything . Out we have

01:09:57.997 --> 01:10:00.108
to be relevant within the operational

01:10:00.108 --> 01:10:02.274
concept they're doing , or we're going

01:10:02.274 --> 01:10:04.441
to continue to see divestitures and or

01:10:04.441 --> 01:10:06.497
equipment that is only delivered and

01:10:06.497 --> 01:10:08.552
the frequency is far too between and

01:10:08.552 --> 01:10:10.663
the old equipment we've said , I just

01:10:10.663 --> 01:10:12.830
went to the 71st out in Hawaii again .

01:10:12.830 --> 01:10:14.941
All of their is broken once again and

01:10:14.941 --> 01:10:17.163
stuff as we look at and that means that

01:10:17.163 --> 01:10:19.274
those things like I said , they don't

01:10:19.274 --> 01:10:21.441
operate independently . If we are good

01:10:21.441 --> 01:10:23.386
partners on our side as far as the

01:10:23.386 --> 01:10:25.839
rapidly developing and or . Or

01:10:25.839 --> 01:10:27.950
communicating when those capabilities

01:10:27.950 --> 01:10:30.061
are , the service's responsibility to

01:10:30.061 --> 01:10:31.950
sustain those will be there , and

01:10:31.950 --> 01:10:33.950
that's the commitment . Now when we

01:10:33.950 --> 01:10:36.061
don't , and they don't palm for their

01:10:36.061 --> 01:10:38.283
sustainment and we don't palm for those

01:10:38.283 --> 01:10:40.172
things and we're messing up their

01:10:40.172 --> 01:10:42.339
overall schedule and budgeting . Those

01:10:42.339 --> 01:10:44.561
have long term effects on the equipment

01:10:44.561 --> 01:10:44.040
that's in the field and otherwise . So

01:10:44.040 --> 01:10:46.649
across the entire system of of what

01:10:46.649 --> 01:10:48.919
Kimyo has to do , we have to get better

01:10:48.919 --> 01:10:51.141
at the capability and the services have

01:10:51.141 --> 01:10:53.363
to sustain it , or else we're not going

01:10:53.363 --> 01:10:55.475
to get past this . We're going to see

01:10:55.475 --> 01:10:54.919
further divestitures , and I don't

01:10:54.919 --> 01:10:56.086
blame the services .

01:10:58.830 --> 01:11:00.719
With the new focus on acquisition

01:11:00.719 --> 01:11:03.709
techniques across the USG such as

01:11:03.709 --> 01:11:07.439
Defense Innovation Unit and ARPAH ,

01:11:07.879 --> 01:11:10.660
is the CBDP community looking at

01:11:10.660 --> 01:11:13.069
innovative acquisition strategies for

01:11:13.069 --> 01:11:15.069
future work ? Chris , why are you

01:11:15.069 --> 01:11:17.291
asking that question when we don't have

01:11:17.291 --> 01:11:19.402
our advanced developer with us , Mr .

01:11:19.402 --> 01:11:21.990
Coleman , so , yes , I , I , I can

01:11:21.990 --> 01:11:24.229
speak for what we're doing at JSTO is

01:11:24.229 --> 01:11:27.390
that we are looking at every single .

01:11:28.430 --> 01:11:30.990
Vehicle at our disposal . Anything that

01:11:30.990 --> 01:11:33.669
we can do to make this faster , you

01:11:33.669 --> 01:11:35.891
know , we're looking at every aspect of

01:11:35.891 --> 01:11:38.270
our process . I have a team that is

01:11:38.270 --> 01:11:40.580
doing just that , going across ,

01:11:40.669 --> 01:11:43.549
scouring every , you know , authority

01:11:43.549 --> 01:11:46.109
that we have , every vehicle that's

01:11:46.109 --> 01:11:48.276
available to us , and making sure that

01:11:48.276 --> 01:11:50.790
we are positioned in prime to be as

01:11:50.790 --> 01:11:53.430
effective as possible , so . Again ,

01:11:53.509 --> 01:11:56.189
the short answer to that is yes . And

01:11:56.189 --> 01:11:58.356
you'll see and you'll be seeing more ,

01:11:58.356 --> 01:12:00.245
more from us in , in the , in the

01:12:00.245 --> 01:12:01.245
months ahead .

01:12:05.009 --> 01:12:08.850
How long the way up here , jeez . Do we

01:12:08.850 --> 01:12:12.669
have another question ? Are we close to

01:12:12.669 --> 01:12:15.350
our last question ? Alright .

01:12:16.569 --> 01:12:20.339
OK . OK . Which need is greater , broad

01:12:20.339 --> 01:12:23.779
spectrum prophylactics or broad

01:12:23.779 --> 01:12:26.250
spectrum therapeutics ? Camillo .

01:12:30.029 --> 01:12:32.640
Erin , do you have ? I mean , I ,

01:12:32.720 --> 01:12:34.942
they're , they're both very important .

01:12:34.942 --> 01:12:37.720
Um , I would say broad spec , my

01:12:37.720 --> 01:12:39.664
personal opinion is broad spectrum

01:12:39.664 --> 01:12:41.387
therapeutics are probably more

01:12:41.387 --> 01:12:44.839
important , um , but again , her face

01:12:44.839 --> 01:12:46.339
doesn't say you're right .

01:12:49.549 --> 01:12:51.470
Optimization for speed requires

01:12:51.470 --> 01:12:53.359
cooperation from other government

01:12:53.359 --> 01:12:55.310
agencies and acceleration of their

01:12:55.310 --> 01:12:57.950
processes . Do you have any insight

01:12:57.950 --> 01:13:00.910
into how that can be accomplished ? A

01:13:00.910 --> 01:13:03.077
key part of everything we do as senior

01:13:03.077 --> 01:13:05.390
leaders is making sure that that we are

01:13:05.390 --> 01:13:08.390
building the bridges to be able to to

01:13:08.390 --> 01:13:10.390
do just that , you know , so that's

01:13:10.390 --> 01:13:13.709
that's really on a leadership thing to

01:13:13.709 --> 01:13:16.370
make sure that . Across agencies that

01:13:16.370 --> 01:13:18.890
we're being good partners , so you know

01:13:18.890 --> 01:13:21.549
I've been focusing a lot on reaching

01:13:21.549 --> 01:13:24.810
out and making sure that you know we're

01:13:24.810 --> 01:13:26.977
being good partners so that way we can

01:13:26.977 --> 01:13:30.250
get that reciprocal , uh you know or or

01:13:30.250 --> 01:13:33.629
treatment back , um , you know , again ,

01:13:33.970 --> 01:13:37.410
I think right now . Everybody in the

01:13:37.410 --> 01:13:41.029
government should be feeling . That

01:13:41.029 --> 01:13:43.589
need to be efficient and to make sure

01:13:43.589 --> 01:13:45.922
that we're all optimizing our processes .

01:13:46.270 --> 01:13:48.470
I think we're all , it should be

01:13:48.470 --> 01:13:50.581
apparent to everybody that the status

01:13:50.581 --> 01:13:53.729
quo is not an option anymore , you know ,

01:13:54.149 --> 01:13:58.080
so I think You know , again ,

01:13:58.319 --> 01:14:00.520
the key is just to be a good partner

01:14:00.879 --> 01:14:03.359
and to really continue to drive and

01:14:03.359 --> 01:14:05.259
work together . Mhm .

01:14:07.259 --> 01:14:09.339
Just a couple of more questions . Is

01:14:09.339 --> 01:14:12.819
the CBDPP doing any work to support

01:14:12.819 --> 01:14:14.541
civilian response partners and

01:14:14.541 --> 01:14:16.263
preparedness for a chemical or

01:14:16.263 --> 01:14:18.263
biological attack on the homeland ?

01:14:20.629 --> 01:14:23.649
So you know our DHS countering weapons

01:14:23.649 --> 01:14:25.871
of mass destruction partners are here ,

01:14:26.000 --> 01:14:27.611
you know , we're in constant

01:14:27.611 --> 01:14:29.778
communication , you know , so you know

01:14:29.778 --> 01:14:31.778
a lot of the investments that we're

01:14:31.778 --> 01:14:33.889
doing , like I said , the information

01:14:33.889 --> 01:14:36.111
we're generating is certainly something

01:14:36.111 --> 01:14:38.850
that we are sharing constantly , you

01:14:38.850 --> 01:14:41.689
know , that is again outside of our .

01:14:42.640 --> 01:14:44.862
distinct mission set , but that doesn't

01:14:44.862 --> 01:14:46.973
mean the information that we generate

01:14:46.973 --> 01:14:49.084
isn't valuable to those partners . So

01:14:49.399 --> 01:14:52.000
while we're not You know , I know at

01:14:52.000 --> 01:14:54.959
JSO we are not making any very specific

01:14:54.959 --> 01:14:57.319
investments to support the civilian

01:14:57.319 --> 01:14:59.486
response . That doesn't mean we're not

01:14:59.486 --> 01:15:01.541
being good partners and sharing that

01:15:01.541 --> 01:15:03.763
information where where it's , uh , you

01:15:03.763 --> 01:15:05.986
know , where it's appropriate . I think

01:15:06.240 --> 01:15:08.240
I'll expand on that . So I mean , I

01:15:08.240 --> 01:15:10.296
think the opportunities that come in

01:15:10.296 --> 01:15:12.407
here and I always look back to former

01:15:12.407 --> 01:15:14.407
DCO Lieutenant General Roper out of

01:15:14.407 --> 01:15:16.573
NorthCO and stuff , particularly as we

01:15:16.573 --> 01:15:18.518
start looking at scenarios when it

01:15:18.518 --> 01:15:20.796
comes to bio-related activities as not ,

01:15:20.796 --> 01:15:23.799
you know . Not that you know Defense

01:15:23.799 --> 01:15:26.021
support to civil authorities , but even

01:15:26.021 --> 01:15:28.243
the inverse of what that looks like . I

01:15:28.243 --> 01:15:30.355
think what you're going to see and as

01:15:30.355 --> 01:15:30.160
we as we talk about this is when we

01:15:30.160 --> 01:15:32.759
look at the integration into public

01:15:32.759 --> 01:15:34.815
health surveillance , whether that's

01:15:34.815 --> 01:15:36.703
state , local , where our base is

01:15:36.703 --> 01:15:38.815
actually where we're talking Hawaii ,

01:15:38.815 --> 01:15:40.870
San Diego , other places that may be

01:15:40.870 --> 01:15:42.981
susceptible doesn't stop at the fence

01:15:42.981 --> 01:15:45.092
line . We work on those . I think the

01:15:45.092 --> 01:15:47.203
CRE transformation that is proved out

01:15:47.203 --> 01:15:49.426
by the SEF and how we're looking at our

01:15:49.426 --> 01:15:51.481
support through with NorthCO and the

01:15:51.481 --> 01:15:55.009
CRE . To civilian for this may change

01:15:55.009 --> 01:15:57.330
in its equipping and also how we

01:15:57.330 --> 01:15:59.441
support those elements and stuff like

01:15:59.441 --> 01:16:01.608
that as they move to a different compo

01:16:01.608 --> 01:16:03.497
and stuff . Do we provide support

01:16:03.497 --> 01:16:05.608
directly to them ? No , but I want to

01:16:05.608 --> 01:16:07.569
make really clear . We do that in

01:16:07.569 --> 01:16:09.847
combination . So it's not like , again ,

01:16:09.847 --> 01:16:11.850
our medical countermeasures , our

01:16:11.850 --> 01:16:14.240
entire group doesn't work hand in hand

01:16:14.450 --> 01:16:17.450
withAA every single day and that we

01:16:17.450 --> 01:16:19.450
don't share common programs and

01:16:19.450 --> 01:16:21.672
projects that we develop candidates for

01:16:21.672 --> 01:16:23.894
what our common needs are . And so when

01:16:23.894 --> 01:16:26.228
it comes to civilian response and stuff ,

01:16:26.228 --> 01:16:28.172
it depends on whether you meet the

01:16:28.172 --> 01:16:30.117
state and local or you meet at the

01:16:30.117 --> 01:16:31.894
national or the DHS , we're all

01:16:31.894 --> 01:16:31.845
benefiting and looking for

01:16:31.845 --> 01:16:33.734
opportunities for integration and

01:16:33.734 --> 01:16:36.205
leveraging one another's , but direct

01:16:36.205 --> 01:16:38.444
support to civil response ? No , it's

01:16:38.444 --> 01:16:42.080
OK . We're gonna take one more

01:16:42.080 --> 01:16:43.913
question before we take the last

01:16:43.913 --> 01:16:45.802
question . Is there anyone in the

01:16:45.802 --> 01:16:47.959
audience who has a question ? Wait ,

01:16:48.040 --> 01:16:50.151
were none of those questions from the

01:16:50.151 --> 01:16:49.790
audience ?

01:16:54.959 --> 01:16:56.959
It was all GPT derived . Anyone who

01:16:56.959 --> 01:16:59.126
would , who has not sent in a question

01:16:59.126 --> 01:17:00.126
in the app .

01:17:02.580 --> 01:17:04.810
OK , this is the last question for

01:17:04.810 --> 01:17:07.032
young leaders out there . What are some

01:17:07.032 --> 01:17:09.254
things you've learned that you wish you

01:17:09.254 --> 01:17:11.366
knew when you first started out ? You

01:17:11.366 --> 01:17:13.279
know , I , I think . I think when

01:17:13.279 --> 01:17:15.520
you're first starting out , you know ,

01:17:15.680 --> 01:17:18.959
you , you tend to think that you're You

01:17:18.959 --> 01:17:21.181
know , blazing your own path and you're

01:17:21.181 --> 01:17:23.560
kind of doing this on your own , right ,

01:17:23.640 --> 01:17:25.473
that you have to make a name for

01:17:25.473 --> 01:17:27.529
yourself so that you're , you're out

01:17:27.529 --> 01:17:29.307
there on this island and you're

01:17:29.307 --> 01:17:31.418
fighting this fight all by yourself .

01:17:31.418 --> 01:17:33.418
And I think what I wish that I knew

01:17:33.418 --> 01:17:35.589
when I first started out is the

01:17:35.589 --> 01:17:39.379
importance of Building that team

01:17:39.589 --> 01:17:42.189
and that network from day one . You

01:17:42.189 --> 01:17:44.300
know , I , I think Doctor Van when we

01:17:44.300 --> 01:17:46.578
were having our , our session with the ,

01:17:46.709 --> 01:17:48.820
you know , with the travel awardees .

01:17:49.470 --> 01:17:51.629
Really put it You know ,

01:17:53.490 --> 01:17:55.490
She , she , she said it very , very

01:17:55.490 --> 01:17:59.200
well . You know , reach out . You know ,

01:17:59.319 --> 01:18:01.600
ask the question . Don't be afraid to

01:18:01.600 --> 01:18:04.080
ask the question , you know , don't be

01:18:04.080 --> 01:18:06.520
afraid to go up to , you know , the

01:18:06.520 --> 01:18:09.549
senior leaders like ourselves and say ,

01:18:09.759 --> 01:18:11.703
you know , can I , can I pick your

01:18:11.703 --> 01:18:13.759
brain ? Can you , can I , you know ,

01:18:13.759 --> 01:18:15.981
can we , can you mentor me ? You know ,

01:18:15.981 --> 01:18:18.148
we're never gonna say no . Like , like

01:18:18.148 --> 01:18:19.981
she pointed out , all the senior

01:18:19.981 --> 01:18:21.926
leaders in there have some gray in

01:18:21.926 --> 01:18:25.160
their hair , their beard , um , there's

01:18:25.160 --> 01:18:27.493
a little bit there , sir . I can see it ,

01:18:27.493 --> 01:18:29.604
uh . You know , and we're all wanting

01:18:29.604 --> 01:18:31.882
to pass that information on , you know ,

01:18:31.950 --> 01:18:34.117
and nobody's going to look down on you

01:18:34.117 --> 01:18:36.117
for asking that question . Nobody's

01:18:36.117 --> 01:18:38.228
gonna think that it's a dumb question

01:18:38.228 --> 01:18:40.394
that you asked , you know , we are all

01:18:40.394 --> 01:18:42.561
eager and willing to help . So for the

01:18:42.561 --> 01:18:44.672
young leaders out there , reach out ,

01:18:44.672 --> 01:18:46.672
you know , we , we won , you know ,

01:18:46.672 --> 01:18:48.728
that's my favorite part of my job is

01:18:48.728 --> 01:18:50.728
working with the young folks in the

01:18:50.728 --> 01:18:52.839
organization . Really passing on that

01:18:52.839 --> 01:18:54.894
knowledge trying to give them a peek

01:18:54.894 --> 01:18:57.006
behind the curtain and learn and grow

01:18:57.006 --> 01:18:59.299
and develop into the into that next

01:18:59.299 --> 01:19:01.390
generation of leader . So you know I

01:19:01.390 --> 01:19:03.612
know some of the some of the folks that

01:19:03.612 --> 01:19:05.834
mentored me are right here in this room

01:19:05.834 --> 01:19:07.723
and I never would have been there

01:19:07.870 --> 01:19:09.926
without those contributions and that

01:19:09.926 --> 01:19:11.981
helped . So that that's what I would

01:19:11.981 --> 01:19:14.629
say . mine isn't dissimilar to Bob's .

01:19:14.669 --> 01:19:18.189
I think the . I , I think for

01:19:18.189 --> 01:19:20.990
me many people in the room , depending

01:19:20.990 --> 01:19:23.046
on where you are in your career , we

01:19:23.046 --> 01:19:25.268
all are successful in where we are as a

01:19:25.268 --> 01:19:27.601
result of your own acumen how you drive ,

01:19:27.601 --> 01:19:29.823
how you try we , we get noticed through

01:19:29.823 --> 01:19:31.768
achievement and stuff , but as you

01:19:31.768 --> 01:19:33.823
transition and stuff and recognizing

01:19:33.823 --> 01:19:35.768
that that achievement , it is that

01:19:35.768 --> 01:19:37.823
people first and that once you start

01:19:37.823 --> 01:19:39.934
switching over your value proposition

01:19:39.934 --> 01:19:42.390
to empowering those around you and

01:19:42.390 --> 01:19:44.557
that's where you're getting your value

01:19:44.557 --> 01:19:46.723
from , not your personal achievement .

01:19:46.723 --> 01:19:48.779
I wish I had gotten that earlier . I

01:19:48.779 --> 01:19:50.890
think that's superpower . The earlier

01:19:50.890 --> 01:19:53.339
and somebody is more mature to do that ,

01:19:53.399 --> 01:19:55.609
the transition , I think the better

01:19:55.609 --> 01:19:57.720
leader they become over the long term

01:19:57.720 --> 01:19:59.776
is realizing where your power can be

01:19:59.776 --> 01:20:02.109
doubled as a result of that , and it is ,

01:20:02.109 --> 01:20:04.165
and it's a value proposition because

01:20:04.165 --> 01:20:06.331
there's nothing wrong with achievement

01:20:06.331 --> 01:20:06.089
in science . There's nothing wrong with

01:20:06.089 --> 01:20:08.256
achievement in command . And stuff and

01:20:08.256 --> 01:20:10.256
that's your job to do . But at some

01:20:10.256 --> 01:20:12.478
point when you become a larger leader ,

01:20:12.478 --> 01:20:14.700
that's not your achievement of your not

01:20:14.700 --> 01:20:16.867
only team but really the entire system

01:20:16.867 --> 01:20:19.089
and those around you is what what China

01:20:19.089 --> 01:20:21.200
drives and I think the the best thing

01:20:21.200 --> 01:20:23.478
for young leaders is to lean into that .

01:20:23.478 --> 01:20:25.422
Even if it sounds uncomfortable at

01:20:25.422 --> 01:20:27.533
times , it's like taking on a new job

01:20:27.533 --> 01:20:26.669
that you just get there the first

01:20:26.669 --> 01:20:28.891
couple of weeks and don't know anything

01:20:28.891 --> 01:20:31.113
about and you're just kind of wandering

01:20:31.113 --> 01:20:30.470
around and wondering if you're adding

01:20:30.470 --> 01:20:32.303
value . That's OK . It gets more

01:20:32.303 --> 01:20:34.526
comfortable as you go on realizing that

01:20:34.526 --> 01:20:36.526
your team and really all the people

01:20:36.526 --> 01:20:38.581
around you are what's most important

01:20:38.581 --> 01:20:40.692
and stuff . So the earlier adoption ,

01:20:40.709 --> 01:20:44.529
better . Mr . Watson , Dr . Kay , thank

01:20:44.529 --> 01:20:46.640
you so much for sharing your insights

01:20:46.640 --> 01:20:48.862
today . Let's give them both a round of

01:20:48.862 --> 01:20:49.250
applause .