WEBVTT

00:17.469 --> 00:19.802
I rode a lot of submarines in my career .

00:19.802 --> 00:21.802
When I bring a system on board that

00:21.802 --> 00:23.913
submarine , I wanna make sure that it

00:23.913 --> 00:25.969
works . And in order to make sure it

00:25.969 --> 00:28.136
works , we have to test it and we have

00:28.136 --> 00:30.358
to test it thoroughly . You're counting

00:30.358 --> 00:29.959
on the systems that you have on board

00:29.969 --> 00:32.080
the submarine to work . When you need

00:32.080 --> 00:34.025
them to work , there's not time to

00:34.025 --> 00:36.191
troubleshoot , there's not time to fix

00:36.191 --> 00:36.110
systems , there's not time to solve

00:36.119 --> 00:37.952
problems . It either works or it

00:37.952 --> 00:40.008
doesn't work . The war fighter needs

00:40.008 --> 00:42.008
those things to work the first time

00:42.008 --> 00:41.939
every time and they need to work ,

00:41.950 --> 00:44.172
right ? Because there's no redo when we

00:44.172 --> 00:46.228
launch a weapon , we wanna make sure

00:46.228 --> 00:48.450
that weapon goes out and it's gonna hit

00:48.450 --> 00:50.450
and kill the target . So , I mean ,

00:50.450 --> 00:52.561
success rates matter . It has to work

00:52.561 --> 00:54.506
the first time . The only way that

00:54.506 --> 00:56.617
we'll ever know that the systems that

00:56.617 --> 00:58.783
we design and develop work are to test

00:58.783 --> 01:01.119
them whether that system is a sensor or

01:01.130 --> 01:03.186
a platform . Ultimately , what we're

01:03.186 --> 01:05.352
trying to do is improve it and make it

01:05.352 --> 01:07.574
so that it will be extremely robust and

01:07.574 --> 01:09.741
reliable when we do hand it off to the

01:09.741 --> 01:11.686
war fader , you know , T and E can

01:11.686 --> 01:13.741
cover from , you know , little , you

01:13.741 --> 01:15.797
know , co component level testing to

01:15.797 --> 01:17.908
full up units to an entire ship being

01:17.908 --> 01:20.593
tested . TNE tests can be done um in a

01:20.602 --> 01:22.752
laboratory on a bench , they can be

01:22.763 --> 01:24.707
conducted in one of our labs , for

01:24.707 --> 01:26.819
instance , in the combat system , lab

01:26.819 --> 01:29.542
on a range and also in an open sea

01:29.553 --> 01:31.664
environment . It is very important to

01:31.664 --> 01:33.886
test in different environments . That's

01:33.886 --> 01:35.942
why we don't do navy testing here in

01:35.942 --> 01:38.109
Arisa Bay is to make sure that we have

01:38.109 --> 01:39.886
places that we can test in that

01:39.886 --> 01:42.053
represent the threat environment . But

01:42.053 --> 01:44.109
the ocean is incredibly dynamic . We

01:44.109 --> 01:46.331
really do need to understand that ocean

01:46.331 --> 01:48.331
environment for the specific places

01:48.331 --> 01:50.664
that we are operating busy environments ,

01:50.664 --> 01:50.526
shallow environments , hot water , cold

01:50.536 --> 01:52.758
water critical that no matter where the

01:52.758 --> 01:54.980
submarine has to go or our fleet has to

01:54.980 --> 01:57.092
go or the work has to go to fight the

01:57.092 --> 01:59.203
fight their equipment will operate in

01:59.203 --> 02:01.258
any of those environments . Our test

02:01.258 --> 02:03.369
ranges are all over the world so that

02:03.369 --> 02:06.120
we can get a variety of data in a way

02:06.129 --> 02:09.020
that we can understand how the systems

02:09.029 --> 02:11.196
that we develop here and test here are

02:11.196 --> 02:13.418
gonna perform in a threat environment .

02:13.418 --> 02:15.473
But Newick Division , Newport does a

02:15.473 --> 02:17.751
lot more than the final testing at sea .

02:17.751 --> 02:19.973
You know , they're involved in the very

02:19.973 --> 02:22.140
beginning of development , acquisition

02:22.140 --> 02:21.479
of capabilities that are gonna

02:21.490 --> 02:23.789
eventually deliver to the fleet . Um So

02:23.800 --> 02:25.911
we see things from the very beginning

02:25.911 --> 02:27.856
to the very end , even when you're

02:27.856 --> 02:30.078
doing some small little things as a new

02:30.078 --> 02:31.856
engineer . If you start writing

02:31.856 --> 02:34.022
requirements , document , you're doing

02:34.022 --> 02:36.244
tee , you're starring the first line of

02:36.244 --> 02:38.356
TE , you're writing a specification .

02:38.356 --> 02:40.467
What really builds credibility in our

02:40.467 --> 02:42.522
TND community is when our scientists

02:42.522 --> 02:44.689
and engineers ride submarines with the

02:44.689 --> 02:46.800
systems that are being tested and you

02:46.800 --> 02:49.022
get on board that submarine and you see

02:49.022 --> 02:51.189
how they use the system and what works

02:51.189 --> 02:53.356
good and what doesn't ? That's TNE the

02:53.356 --> 02:55.578
TNE community . We at Newark Division ,

02:55.578 --> 02:57.689
Newport Ranges like Atlantic Noc Test

02:57.689 --> 02:59.689
and Evaluation Center are always in

02:59.689 --> 03:01.911
concert with our customers to know what

03:01.911 --> 03:03.689
they're thinking , what they're

03:03.689 --> 03:05.800
bringing . What's their event horizon

03:05.800 --> 03:05.289
look like ? What are they thinking

03:05.300 --> 03:07.300
about in one year ? Five years ? 10

03:07.300 --> 03:09.467
years and how do we need to prepare to

03:09.467 --> 03:11.578
make sure that we're ready to receive

03:11.578 --> 03:13.744
test and deliver the capabilities that

03:13.744 --> 03:15.689
our program offices are developing

03:15.689 --> 03:17.633
today in the future ? I do believe

03:17.633 --> 03:19.800
we'll be doing a lot more modeling and

03:19.800 --> 03:21.856
simulation . I see us having digital

03:21.856 --> 03:23.856
test ranges combined with live test

03:23.856 --> 03:25.689
ranges . Physical testing in the

03:25.689 --> 03:27.911
operational environment is always gonna

03:27.911 --> 03:29.744
be the gold standard . However ,

03:29.744 --> 03:31.880
integrating simulation along with

03:31.889 --> 03:34.460
physical testing is going to allow us

03:34.470 --> 03:36.669
to be able to provide necessary

03:36.679 --> 03:39.759
capability to the fleet quicker . In my

03:39.770 --> 03:42.440
opinion , I believe test and evaluation

03:42.449 --> 03:45.600
is really the check on technical

03:45.610 --> 03:47.499
excellence and how well technical

03:47.500 --> 03:49.729
excellence was executed . I sleep well

03:49.740 --> 03:52.000
at night because I know I have the

03:52.009 --> 03:54.479
confidence that we're doing the best we

03:54.490 --> 03:57.440
can to make sure that ships deploy .

03:57.570 --> 03:59.737
When they leave our sites , they leave

03:59.737 --> 04:01.626
our ranges that they're ready for

04:01.626 --> 04:01.759
combat .

