WEBVTT

00:00.520 --> 00:02.510
- A couple of great panels this afternoon,

00:02.510 --> 00:06.677
and I'm the MC, Vice Admiral, retired, Carol Pottenger,

00:06.714 --> 00:10.797
and very happy to be here and help SNA

00:12.540 --> 00:14.770
introduce our wonderful speakers that we

00:14.770 --> 00:15.770
have this afternoon.

00:16.704 --> 00:20.871
So, our first panel, Naval Surface Warfare Domains,

00:21.360 --> 00:25.527
Enabling Technologies and Today's DMO EMW Technologies

00:26.730 --> 00:30.450
with Admiral Tom Druggan as the moderator.

00:30.450 --> 00:33.820
I'm just gonna introduce Tom and let him

00:34.140 --> 00:35.680
introduce his team.

00:36.470 --> 00:38.430
Something of note, this is the first time,

00:38.430 --> 00:42.590
I just asked Tom, that we've ever dedicated

00:42.590 --> 00:45.920
a panel to NSWC, so I think it's terrific.

00:46.240 --> 00:48.640
What they bring to the fight is so important,

00:49.020 --> 00:51.110
and I think we're gonna have a great time learning

00:51.110 --> 00:52.840
about that this afternoon, with hopefully

00:52.840 --> 00:54.310
lots of questions.

00:55.200 --> 00:57.670
So, it is my honor and privilege to introduce

00:57.670 --> 00:59.970
the commander of Naval Service Warfare Center,

01:00.090 --> 01:01.190
Admiral Tom Druggan.

01:01.190 --> 01:03.100
I've known Tom for many years.

01:03.100 --> 01:05.770
We were just confirming, we first met

01:05.770 --> 01:08.780
when he was a Lt. Commander and I was a Captain

01:08.780 --> 01:12.010
working for a Vice Chief called Admiral Mike Mullen.

01:12.360 --> 01:14.040
So those were good old days.

01:14.870 --> 01:18.170
Tom relieved Admiral Selby as the Commander NSWC

01:18.170 --> 01:20.390
in August of 2016.

01:20.930 --> 01:23.640
A highly respected Naval Service Warfare officer,

01:23.950 --> 01:26.680
native of Lexington, Kentucky, graduated

01:26.680 --> 01:28.820
from the naval academy in 1989.

01:30.032 --> 01:32.240
Holds a masters of Science and National Resource

01:32.240 --> 01:34.830
Management from what used to be called ICAF,

01:35.250 --> 01:37.170
and an MS in Operations Research

01:37.170 --> 01:39.120
from the Naval Postgraduate School.

01:39.730 --> 01:42.680
At sea, Tom served aboard a variety of service ships

01:42.680 --> 01:44.780
and commanded the USS O'Kane.

01:45.260 --> 01:48.350
Ashore, he served as the major program manager

01:48.350 --> 01:51.900
for AEGIS Combat Systems in PEO IWS,

01:52.300 --> 01:56.010
major program manager for In-Service AEGIS Fleet Readiness

01:56.250 --> 01:58.430
and as the principle assistant program manager

01:58.430 --> 02:02.597
for In-Service Aircraft Carrier Combat System Integration.

02:03.300 --> 02:05.800
His Pentagon tours included special assistant

02:05.800 --> 02:08.150
to the CNO and VCNO, and the founding

02:08.150 --> 02:09.810
member of Deep Blue.

02:10.481 --> 02:14.648
At NSWC, Tom leads more than 18,000 scientists,

02:15.484 --> 02:19.260
engineers, technicians, and support personnel,

02:19.260 --> 02:21.820
civilian and active duty, stationed

02:21.820 --> 02:24.750
at eight divisions located across the United States.

02:24.930 --> 02:28.050
So, just as a short primer for the audience,

02:28.230 --> 02:30.260
those eight divisions are Port Hueneme,

02:31.439 --> 02:34.190
and Corona on the West coast, Crane, Indiana,

02:34.190 --> 02:37.460
Panama City, and in the mid Atlantic area,

02:37.460 --> 02:39.690
Dahlgren, Carderock, Indian Head,

02:39.690 --> 02:43.190
and EOD Technology Division, and Philadelphia.

02:43.700 --> 02:45.650
Even though we call them divisions, they are

02:45.650 --> 02:48.169
each led by a commanding officer themselves,

02:48.169 --> 02:51.920
and today, we have the CO from Carderock with us,

02:51.920 --> 02:55.210
Captain Vandroff, the CO and the Technical Director

02:55.210 --> 02:58.030
from Dahlgren, Captain Weekes and Mr. Fiore

02:58.690 --> 03:01.520
and our final panel member is Dr. Fillinich,

03:02.040 --> 03:05.060
who is Admiral Druggan's chief technology officer.

03:05.910 --> 03:08.350
The NSWC's are service warfare centric,

03:08.350 --> 03:11.390
but they have significant submarine, aviation,

03:11.390 --> 03:14.070
and inter agency portfolios as well.

03:14.600 --> 03:18.767
Quoting Tom from a recent SNA surface sitrep interview,

03:19.350 --> 03:22.630
he describes his workforce as a Navy smart

03:22.910 --> 03:26.940
working brain trust, Navy smart because they truly

03:26.940 --> 03:29.190
understand the naval maritime environment,

03:29.840 --> 03:33.790
a brain trust because he has 600 PhDs,

03:33.790 --> 03:36.780
and several thousand people with masters degrees,

03:36.990 --> 03:39.700
including world class experts in energetics,

03:39.700 --> 03:42.080
radar propagation, missile control,

03:42.080 --> 03:44.610
electronic warfare, and ship design.

03:45.330 --> 03:48.320
Tom's also assigned additional duties as the DOD

03:48.480 --> 03:52.110
executive manager for EOD technology and training,

03:52.490 --> 03:54.580
and as the chief technology officer

03:54.580 --> 03:57.380
for the Navy Surface Warfare enterprise.

03:57.710 --> 04:00.250
So let's give a warm welcome to Admiral Tom Druggan

04:00.250 --> 04:01.870
and his panel members for what promises

04:01.870 --> 04:04.020
to be a very informative session.

04:04.847 --> 04:07.097
(applause)

04:11.070 --> 04:13.180
- A lot of great memories, a lot of great memories.

04:13.180 --> 04:14.840
Thank you so much, ma'am.

04:14.840 --> 04:16.280
It was an honor and privilege to work

04:16.280 --> 04:19.100
with you then and it's great to see you again today.

04:19.910 --> 04:22.160
Thank you to SNA, this is a fantastic forum

04:22.160 --> 04:22.993
as we all know.

04:23.520 --> 04:25.040
This is the one time during the year

04:25.040 --> 04:27.910
where we can all come together and look at the state

04:27.910 --> 04:30.750
of the surface warfare and our contribution

04:30.750 --> 04:33.590
to the Navy writ large and to our nation,

04:33.590 --> 04:35.920
and it's a great chance for us to catch up

04:35.920 --> 04:39.730
with classmates and former ship mates,

04:39.730 --> 04:41.840
a lot of former bosses out here too,

04:41.840 --> 04:44.950
so I'll try to keep, try to not embarrass

04:44.950 --> 04:46.100
the family there.

04:46.386 --> 04:48.480
But it is a fantastic way for us

04:48.480 --> 04:49.610
to all get together and keep up,

04:49.610 --> 04:53.777
because things are moving fast these days,

04:54.140 --> 04:55.630
there's no question about that,

04:55.630 --> 04:57.640
both on the technology side, but also

04:57.640 --> 04:59.829
organizationally, as a Navy, we're moving forward

04:59.829 --> 05:01.820
very quickly.

05:01.820 --> 05:03.620
And thanks to the industry, I really greatly

05:03.620 --> 05:05.460
appreciate SNA providing the forum

05:05.460 --> 05:09.377
and the venue so that industry and the military

05:09.546 --> 05:11.463
can come together here.

05:12.190 --> 05:15.438
And this is another important part of the military

05:15.438 --> 05:18.360
making sure that we keep pace with technology,

05:18.360 --> 05:20.510
which many of you are developing and demonstrating

05:20.510 --> 05:22.480
and showing here at SNA.

05:22.959 --> 05:26.260
It's a fantastic way for everybody in uniform

05:26.260 --> 05:27.890
to stay abreast of the developments,

05:27.890 --> 05:30.260
which, as you know, on the commercial side

05:30.260 --> 05:33.530
and industry side, is also moving incredibly fast,

05:33.550 --> 05:35.470
and we have to take advantage of that.

05:35.920 --> 05:38.610
The other pieces, the displays that I've walked around,

05:38.610 --> 05:40.340
have just been really tremendous and they're

05:40.340 --> 05:43.631
improving every year, and so I just want to congratulate

05:43.631 --> 05:46.520
the presenters at each of the booths,

05:46.520 --> 05:49.100
they really do an excellent job on your behalf.

05:49.860 --> 05:51.560
And in terms of the industry and

05:52.110 --> 05:54.400
the Naval Surface Warfare Center,

05:55.044 --> 05:58.880
almost about half of our money goes to industry.

05:58.880 --> 06:00.160
A lot of people don't know that.

06:00.160 --> 06:03.050
So this is a true team effort between

06:03.050 --> 06:04.350
the government and the industry at

06:04.350 --> 06:06.880
the Naval Surface Warfare Center and its divisions

06:07.160 --> 06:09.410
to work very closely with the industry,

06:09.460 --> 06:11.980
both on sustainment issues as well

06:11.980 --> 06:14.270
as reaching into far future technology.

06:15.352 --> 06:17.530
Thank you to SNA Writ Large for the opportunity

06:17.530 --> 06:19.170
to have this panel in particular

06:19.310 --> 06:21.160
so we can talk about the navy's efforts

06:21.160 --> 06:23.830
to maintain and expand our competitive

06:23.830 --> 06:26.480
warfighting edge, and we have to.

06:26.614 --> 06:30.290
NSWC has to deliver the sea power

06:30.290 --> 06:33.870
necessary to win and be victorious at sea.

06:34.800 --> 06:36.350
The CNO yesterday talked, and he's talked

06:36.350 --> 06:39.090
about this regularly, about, we are in a competitive

06:39.090 --> 06:42.030
environment, we are in a competitive environment

06:42.440 --> 06:44.700
for control of the sea, and without control,

06:44.700 --> 06:48.150
the provocations of that, it diminishes

06:48.150 --> 06:51.350
our national power, it threatens our way of life,

06:51.370 --> 06:54.461
and ultimately leads us into an area

06:54.461 --> 06:57.380
that we just don't want to go, it's high risk.

06:57.380 --> 07:00.100
So, we are in a competitive environment.

07:00.177 --> 07:03.760
Number two doesn't cut it in this business,

07:03.943 --> 07:06.390
we have to be number one, and so we have

07:06.390 --> 07:09.070
to be eyes wide open, we have to take advantage,

07:09.070 --> 07:12.010
we have to improve our readiness and maintain

07:12.010 --> 07:14.430
it at a high level and increase that,

07:14.430 --> 07:16.130
and then we have to take advantage

07:16.838 --> 07:18.250
of the technological solutions, but then we

07:18.250 --> 07:20.080
also have to do our due diligence

07:20.080 --> 07:22.740
and get it into the fleet in a usable manner

07:22.820 --> 07:24.860
right from the get go so that the warfighter

07:24.860 --> 07:27.600
can take advantage of it and change the calculus

07:27.600 --> 07:29.130
of the enemy and win.

07:29.620 --> 07:33.787
And that's the focus of delivering sea power for NSWC.

07:33.950 --> 07:37.490
And we have to be ready to win, it's important.

07:38.130 --> 07:41.300
Really, at the end of the day, this is a struggle

07:41.300 --> 07:43.840
between nations and states that control

07:43.840 --> 07:46.040
the individual and nations and states

07:46.040 --> 07:47.740
that are there for the individual.

07:48.210 --> 07:51.450
And we, obviously, have our individual liberties

07:51.450 --> 07:54.560
and civil liberties at risk if we don't pay attention.

07:54.672 --> 07:57.110
In the Navy, our job is to fight that everyday,

07:57.110 --> 07:58.990
we do it with forward sea presence,

07:59.410 --> 08:02.580
we do it with ready combat, combat ready forces

08:02.580 --> 08:06.747
that are there to immediately respond to crises

08:07.180 --> 08:08.190
across the world.

08:08.360 --> 08:10.120
And if it's not combat, we're doing good work

08:10.120 --> 08:11.590
everyday across the world.

08:11.590 --> 08:13.900
We're always first on station to provide

08:13.900 --> 08:16.690
aid, whether it's Haiti, whether it's Indonesia,

08:16.850 --> 08:19.530
whether it's hurricanes, whether it's earthquakes,

08:19.580 --> 08:22.440
the Navy is there quickest, first to provide relief

08:22.440 --> 08:26.607
to, really, the humanitarian relief that's necessary.

08:26.894 --> 08:30.477
So, I love the Navy and that's a part of it

08:30.840 --> 08:33.500
that I love, and then the fact that one day,

08:33.500 --> 08:36.360
we may have to go beyond presence

08:36.360 --> 08:39.860
and into combat operations we have to prepare for everyday.

08:40.968 --> 08:44.718
So, NSWC, real quick, we cover the life cycle

08:45.145 --> 08:47.630
of systems across the board, we do everything

08:47.630 --> 08:50.480
from rust to rail guns, logistics to lasers,

08:50.730 --> 08:54.802
we have world class talent in cyber security,

08:54.802 --> 08:57.635
and we have world class in lasers,

08:57.980 --> 09:01.270
we're leading in the rail gun evolution,

09:02.080 --> 09:04.130
so there we have some world class pieces.

09:04.220 --> 09:06.910
We have to rely, and we rely, in those programs

09:06.910 --> 09:09.680
and those efforts, on our industry partners

09:10.200 --> 09:11.580
to help us get there because you have

09:11.580 --> 09:13.120
knowledge that we don't, we have knowledge

09:13.120 --> 09:15.770
that you don't, and together we can deliver

09:15.770 --> 09:18.470
something, deliver sea power to the Navy.

09:19.170 --> 09:20.610
So, we do everything from future development

09:20.610 --> 09:22.740
to the in-service support across the board

09:23.130 --> 09:24.530
and we do it with your help.

09:25.430 --> 09:28.770
Today we're gonna cover this as a continuum of design

09:29.640 --> 09:31.310
for that sea power.

09:31.850 --> 09:34.040
So we're gonna start, we have an all star panel.

09:34.040 --> 09:36.340
We're gonna first start with Captain Mark Vandroff,

09:36.340 --> 09:39.187
with ship design, he's the CO of NSWC Carderock,

09:39.187 --> 09:40.270
class of '89.

09:40.433 --> 09:42.660
All right, a little plug there.

09:42.660 --> 09:45.272
He has a tremendous number of naval architects

09:45.272 --> 09:48.168
that are true experts, and he's developing

09:48.168 --> 09:50.889
new tools to really make us agile

09:51.110 --> 09:54.470
as we drive to a 355 ship Navy in the future,

09:54.590 --> 09:57.470
and previously, he's a ship builder,

09:57.550 --> 10:00.090
a true ship builder, being a major program manager

10:00.090 --> 10:02.470
in PMS 400D in PEO ships.

10:02.694 --> 10:05.690
Second, we're then gonna move into the combat system design.

10:05.690 --> 10:07.070
So we've got the platform, we've designed

10:07.070 --> 10:10.500
the ship in conjunction with, not as an after thought,

10:10.500 --> 10:12.130
but in conjunction with is designed

10:12.130 --> 10:14.090
with the combat system, absolutely

10:14.090 --> 10:16.730
critical that it be done in conjunction with, right?

10:16.730 --> 10:19.361
The combat system design and the ship integration efforts

10:19.361 --> 10:21.890
and requirements to go along with it.

10:21.890 --> 10:25.220
So, for that, we have Captain Gus Weekes with us today.

10:25.290 --> 10:27.525
He's the CO of NSWC Dahlgren.

10:27.525 --> 10:30.942
His expertise and his workforce expertise

10:31.090 --> 10:34.270
as combat systems to include the cyber expertise,

10:34.959 --> 10:37.660
and he was previously the A&L Department Officer

10:37.660 --> 10:39.340
out at NSWC Port Hueneme.

10:41.833 --> 10:44.430
Next, we'll have, now that we have a ship

10:44.430 --> 10:47.620
that's got, with its mission systems

10:47.620 --> 10:50.320
and now a warship, thing is, we'll have multiple

10:50.320 --> 10:52.630
warships anytime we do strike group operations

10:52.630 --> 10:55.950
or operate as a Navy at sea, so we'll have multiple ships,

10:55.950 --> 10:58.380
and Dr. Fillinich, my Chief Technology Officer

10:59.140 --> 11:01.810
with MIT, MBA, and a PhD

11:03.998 --> 11:05.110
in Information Theory

11:05.110 --> 11:07.250
will take us into the multi ship domain

11:07.360 --> 11:10.680
and how ships, the individual capability

11:10.680 --> 11:12.590
of the fighting integers can be increased

11:12.590 --> 11:15.850
even further with a multi ship approach.

11:17.300 --> 11:20.040
And then, and previously Dr. Fillinich

11:20.040 --> 11:24.207
was IWS7 Deputy and IWS10 Deputy Technical Director.

11:24.890 --> 11:27.780
IWS7 being the advanced warfighting

11:27.780 --> 11:31.947
and IWS10 being aircraft carrier combat systems.

11:32.350 --> 11:34.330
And finally, to close, now that we have

11:34.330 --> 11:36.630
a ship that's been transformed through

11:36.920 --> 11:39.510
missions systems and combat systems into a warship

11:39.670 --> 11:41.210
and we understand how it can operate

11:41.210 --> 11:44.010
in a strike group environment or a surface

11:44.010 --> 11:46.480
action group environment, how do we introduce

11:46.480 --> 11:48.460
that capability and get immediate value

11:48.460 --> 11:52.410
from it and not have issues during fleet introduction?

11:52.750 --> 11:54.970
And how do we train with that capability

11:55.200 --> 11:58.710
without having to show that advanced in some cases?

11:58.860 --> 12:00.050
Because there are times that we are gonna

12:00.050 --> 12:02.340
have capability and we just don't want

12:02.580 --> 12:06.190
out potential adversaries to understand what

12:06.190 --> 12:08.830
we actually can do and when we can do it

12:08.830 --> 12:09.880
and how we can do it.

12:09.980 --> 12:11.938
So, for that, Captain Steve Murray, former CO

12:11.938 --> 12:15.355
of NSWC Corona will be covering the fleet

12:15.557 --> 12:18.610
introduction and the sailor considerations,

12:18.610 --> 12:20.710
and the live virtual constructive training

12:20.780 --> 12:23.172
so that we can train with high end capability

12:23.172 --> 12:27.089
in a secure way, in a secure fashion.

12:28.387 --> 12:32.554
So, with that, let's kick it off with Captain Vandroff.

12:33.453 --> 12:36.000
Do you want to sit at the podium or the chair?

12:36.000 --> 12:36.833
- The chair.

12:36.833 --> 12:39.510
- Chair, okay, chair is good, I like chair.

12:41.360 --> 12:42.210
- Good afternoon.

12:45.457 --> 12:48.370
So, you see on my slide that at the top,

12:48.370 --> 12:51.070
it says, for Carderock, America's fleet starts here,

12:51.560 --> 12:54.150
and today it's, your brief starts here.

12:55.573 --> 12:59.740
So, the theme of our discussion is integrating to win.

13:00.609 --> 13:04.442
What are the technologies and the science that

13:04.749 --> 13:08.227
the Surface Warfare Centers need to provide

13:08.227 --> 13:10.974
to the fleet so that the fleet can win?

13:10.974 --> 13:13.870
And every part of that is important as we go.

13:13.870 --> 13:16.870
It's not, to win you have to be integrated,

13:17.010 --> 13:20.020
because things that are disjointed don't provide

13:20.020 --> 13:23.210
the effective solutions that it takes to win.

13:23.210 --> 13:26.150
So I'll be kicking it off and then passing

13:26.150 --> 13:29.200
it along here, but hold the theme that,

13:29.200 --> 13:31.980
there's nothing that I say that should stand

13:31.980 --> 13:34.190
in a vacuum, it is a continuum across

13:34.190 --> 13:38.357
all the different capabilities

13:38.460 --> 13:40.760
that the different divisions of the Warfare Center

13:40.760 --> 13:44.090
and our partner activities, both within NAVSEA

13:44.420 --> 13:46.680
and within the other system centers

13:46.910 --> 13:49.030
that make up the Naval Research and Development

13:49.030 --> 13:51.400
Enterprise that we provide together

13:51.450 --> 13:53.700
to provide those solutions to the warfighter.

13:54.580 --> 13:56.210
So, for those who may not be familiar

13:56.210 --> 13:59.630
with Carderock specifically, I include a slide

13:59.630 --> 14:03.797
there on things that Carderock is responsible for.

14:04.308 --> 14:07.641
Our technical capabilities and the areas

14:08.174 --> 14:09.757
that it falls into.

14:10.130 --> 14:11.850
Carderock is probably best known

14:11.850 --> 14:14.487
for naval architecture and best known for hydro dynamics

14:14.487 --> 14:17.750
because we have the naval tailor model basin

14:17.750 --> 14:19.640
and because we have maneuver and seakeeping basin

14:19.640 --> 14:21.590
and because those are big and, frankly,

14:22.736 --> 14:24.211
those are very attractive to look at,

14:24.211 --> 14:26.300
so people come and look at those things.

14:26.300 --> 14:28.130
But we have capabilities, techno capabilities

14:28.130 --> 14:31.280
across a wide range of engineering disciplines.

14:31.430 --> 14:34.410
Everything from vulnerability and survivability.

14:34.410 --> 14:36.450
Down at the bottom, you see environmental quality.

14:36.450 --> 14:38.650
If you don't think that environmental quality

14:38.650 --> 14:42.740
is a warfighting capability, then try having

14:42.740 --> 14:45.840
your ships maintain presence when people

14:45.840 --> 14:47.670
don't want to take the ballast water

14:47.670 --> 14:49.820
that you're discharging out of your ballast

14:50.074 --> 14:52.050
tanks into their ports, and you realize

14:52.050 --> 14:54.560
that environmental quality is actually a mission,

14:54.560 --> 14:56.595
it's a force multiplier to be able to do that

14:56.595 --> 14:58.428
in a compliant manner.

14:58.687 --> 15:00.760
All through the things of structures

15:00.760 --> 15:02.180
and help forms and things that you think

15:02.180 --> 15:03.700
of as Carderock and are more like,

15:03.700 --> 15:06.560
yeah, those guys do, and they design and test ships.

15:06.630 --> 15:10.430
So that's the spectrum of Carderock's capability

15:10.430 --> 15:13.760
and what we bring to our part of this task.

15:15.354 --> 15:19.271
So, my initial slide,

15:19.410 --> 15:20.400
and I hope to get into

15:20.400 --> 15:22.240
this in the Q&A, but just a few words

15:22.240 --> 15:23.310
to keep this quick.

15:24.040 --> 15:26.530
My initial slide talked about, what is it

15:26.530 --> 15:28.350
that we need to do to win?

15:28.350 --> 15:30.900
So, from the Carderock side, what do I have

15:30.900 --> 15:34.050
to provide for the rest of the capabilities

15:34.050 --> 15:35.660
that are gonna go on a platform as we're

15:35.660 --> 15:38.220
doing platform design, what are we

15:38.350 --> 15:39.450
gonna have to provide?

15:39.450 --> 15:42.950
And the word that I want you to focus on is flexibility.

15:42.950 --> 15:44.530
We need flexible platforms.

15:44.793 --> 15:47.191
What does it mean to be flexible?

15:47.191 --> 15:49.740
It means that the platform is adaptable to change.

15:49.740 --> 15:52.550
It means that not only does it do what it does,

15:52.660 --> 15:55.700
but it has the ability to grow or to be altered

15:55.990 --> 15:59.770
so that as the world changes and its requirements change,

15:59.770 --> 16:02.163
the platform remains relevant, the platform

16:02.163 --> 16:05.580
can continue to support all the different

16:05.780 --> 16:09.947
capabilities that might be substantiated on that platform.

16:10.200 --> 16:13.510
Flexibility is, if you will, a requirement,

16:13.510 --> 16:16.440
it is a capability, it is what we desire.

16:17.730 --> 16:20.340
Now, how do we get flexibility?

16:20.340 --> 16:21.510
There are a lot of different ways,

16:21.510 --> 16:23.830
but I'm gonna throw up a couple of different,

16:23.830 --> 16:25.130
and you see some up there.

16:25.785 --> 16:27.840
You have the acronym, and I hate to speak

16:27.840 --> 16:30.390
in acronyms, but we love talking about Swapsee,

16:30.390 --> 16:31.960
which is your margins, your margins

16:31.960 --> 16:34.090
for space and weight and cooling and power.

16:34.090 --> 16:35.900
I can provide that, I can provide all sorts

16:35.900 --> 16:38.900
of different things to make the ship flexible.

16:38.900 --> 16:41.100
I'm gonna talk about two things specifically

16:41.170 --> 16:43.660
that help make a ship flexible, that help us

16:43.660 --> 16:45.250
achieve this capability.

16:46.020 --> 16:47.790
The first one is modularity.

16:48.850 --> 16:53.017
So, modularity, and I want to lay

16:53.860 --> 16:55.010
another thought on you.

16:55.646 --> 16:57.400
When we look at modularity, people think,

16:57.400 --> 16:59.050
well, they think a lot of different things.

16:59.050 --> 17:01.270
You might think of an LCS mission module,

17:01.730 --> 17:03.220
and that's a good thing to think about.

17:03.220 --> 17:07.280
LCS mission modules are an example of modularity.

17:07.560 --> 17:10.310
But modularity exists on a continuum,

17:10.350 --> 17:12.500
so if you ask me, what was the very first

17:12.500 --> 17:15.810
example of a modular ship, I would say,

17:15.810 --> 17:18.277
well, that happened back in, and I'm gonna

17:18.277 --> 17:21.610
actually not give my full, I'm gonna not

17:22.270 --> 17:24.520
answer it right away, I'm gonna tell a story.

17:25.080 --> 17:27.460
If you come to Carderock, and please come to Carderock,

17:27.460 --> 17:30.940
I love giving tours, and you walk into our

17:31.330 --> 17:33.670
rotunda and you look to the left,

17:33.840 --> 17:36.420
you will see a beautiful ship model.

17:36.420 --> 17:39.630
One of Carderock's ancillary responsibilities is,

17:39.630 --> 17:42.190
we're the curator of all the Navy display models.

17:42.650 --> 17:44.910
So if you go the Pentagon or NAVSEA

17:44.910 --> 17:46.740
or Fleet Forces Command Core, if you see

17:46.740 --> 17:48.590
a model on display, somewhere on there,

17:48.590 --> 17:51.280
there's a little Carderock serial number

17:51.280 --> 17:52.680
and we know when to bring it back

17:52.680 --> 17:56.847
and give it the equivalent of a DSRA for a display model,

17:57.160 --> 17:58.260
so it stays representing.

17:58.260 --> 17:59.750
So, if you look and there's this one model,

17:59.750 --> 18:02.200
and I love it so much, coming right in

18:03.050 --> 18:04.330
from the rotunda of our front office,

18:04.330 --> 18:06.540
and it's of a ship that was never built,

18:07.010 --> 18:10.050
it's of the cruiser, the battle cruiser, Lexington,

18:10.670 --> 18:14.210
which was designed in the 1910s and started

18:14.210 --> 18:17.982
construction in the early 1920s, and then,

18:17.982 --> 18:21.565
after it was about halfway through keel up,

18:21.700 --> 18:23.460
the United States Navy signed the Washington

18:23.460 --> 18:27.620
Naval treaty of 1922, '23, one of the historians

18:27.890 --> 18:29.160
here will, somewhere in there.

18:29.160 --> 18:31.825
And suddenly, '22, all right, in 1922.

18:31.825 --> 18:34.200
And suddenly that ship became illegal.

18:34.200 --> 18:36.540
It was too heavy for a cruiser

18:36.830 --> 18:38.300
and we weren't gonna count it as one of our

18:38.300 --> 18:40.150
battleships because it was too small.

18:40.460 --> 18:42.080
But there was this new technology

18:42.080 --> 18:43.310
called the airplane.

18:43.360 --> 18:44.870
So the ship was finished without

18:44.870 --> 18:46.560
any of the superstructure that was in that

18:46.560 --> 18:49.450
original model, and it became the carrier, Lexington,

18:49.600 --> 18:52.210
one of our first, it was either CV-2, I believe,

18:52.210 --> 18:53.240
the second carrier.

18:53.607 --> 18:56.342
And all the first early carriers were converted cruisers,

18:56.342 --> 18:59.490
so it was a cruiser with a flight deck.

18:59.490 --> 19:01.240
That was our first modular ship.

19:02.570 --> 19:04.680
We didn't know it at the time, but it was

19:04.680 --> 19:05.830
our first modular ship.

19:05.830 --> 19:07.754
What could you swap on and off?

19:07.754 --> 19:08.837
The aircraft.

19:08.860 --> 19:11.090
You can put whatever aircraft you want,

19:11.090 --> 19:12.040
that became modular.

19:12.040 --> 19:13.889
So, for a long time, we had modularity there.

19:13.889 --> 19:16.740
The next big step in modularity was taken

19:16.740 --> 19:19.580
by the Surface Navy back in the 1980s.

19:19.800 --> 19:21.530
We had a modular launcher.

19:21.530 --> 19:23.530
Before the vertical launch system,

19:23.700 --> 19:26.460
your missile and your launcher had to match,

19:26.460 --> 19:28.700
if you wanted to launch a certain type

19:28.700 --> 19:30.160
of missile, you bought the launcher

19:30.160 --> 19:31.440
that went on with that.

19:31.600 --> 19:34.860
Since then, now we have modular weapons packages

19:34.860 --> 19:37.560
because we build missiles to go in a,

19:37.560 --> 19:40.340
whether it's a Mk.41 or now the Mk.57,

19:40.410 --> 19:43.310
but we put it in and then we change, and that's modular.

19:43.590 --> 19:46.421
So the mission package is the next step.

19:46.421 --> 19:49.215
What I'm here to tell you today is,

19:49.460 --> 19:51.250
if you think we're done with the mission

19:51.250 --> 19:53.200
package, that's not gonna cut it in the future.

19:53.200 --> 19:56.410
We need to continue to use the modularity we have,

19:56.870 --> 20:00.170
but what we're looking at at Carderock, in all of

20:00.170 --> 20:02.940
our efforts of looking at the future is greater

20:02.940 --> 20:03.773
modularity.

20:03.773 --> 20:06.320
How do we swap out different parts

20:06.320 --> 20:08.680
and greater parts of a ship and a ship system

20:08.680 --> 20:11.620
so that we can have that flexibility by keeping

20:11.620 --> 20:14.740
things modular and therefore more adaptable to change.

20:14.760 --> 20:17.470
So that's one of the paths to flexibility.

20:18.580 --> 20:20.350
The second thing is power.

20:20.568 --> 20:23.900
And here, we're the recipient of a lot of great work

20:23.900 --> 20:26.280
that's been done recently by the DDG 1000 program,

20:26.280 --> 20:29.060
the first U.S. Navy warship with an integrated

20:29.060 --> 20:29.945
power system.

20:29.945 --> 20:32.778
So, for years and years and years,

20:33.170 --> 20:36.140
since we went from sale to steam

20:36.140 --> 20:39.530
and then steam to diesel and gas turbines,

20:39.530 --> 20:43.697
we've always made power by spinning a generator

20:43.920 --> 20:45.880
with one prime mover, and we've done

20:45.880 --> 20:48.390
propulsion by spinning a gear hooked

20:48.390 --> 20:50.650
up to a shaft with another prime mover,

20:50.820 --> 20:53.843
and DDG 1000 decouples that.

20:53.843 --> 20:56.620
So they say, okay, let's decouple that,

20:56.620 --> 20:58.810
we'll just make power and then the power

20:58.810 --> 21:00.500
will do everything, including turning the shaft.

21:00.500 --> 21:03.640
And that provides you a lot of flexibility,

21:03.650 --> 21:07.817
because now I have power to do not one thing

21:08.140 --> 21:09.290
or the other, but I have the power

21:09.290 --> 21:11.690
to do what I need it to do when I need it to do.

21:11.910 --> 21:14.110
The next step in that, what we're looking at

21:14.662 --> 21:16.590
is now, not just integrated power, but iPads.

21:16.590 --> 21:19.910
So you add two integrated power energy sharing,

21:20.000 --> 21:22.900
you add the ability to store energy along

21:22.900 --> 21:26.070
with the generation of energy so that, again,

21:26.070 --> 21:28.960
you can achieve greater flexibility so that

21:28.970 --> 21:31.120
when you can handle high load, low load

21:31.120 --> 21:34.470
conditions that might arise in the capabilities

21:34.470 --> 21:37.504
that you want to put on that ship

21:37.504 --> 21:40.171
or potentially unmanned platform

21:40.650 --> 21:43.330
that's going to provide that warfighting capability.

21:43.360 --> 21:46.910
So power is the second of the examples

21:46.910 --> 21:50.980
that I gave, things that will enable flexibility.

21:52.230 --> 21:55.870
Now, how do we do it and how do we do it in a smart way?

21:56.160 --> 21:59.070
And here, I want to talk about, you see,

21:59.070 --> 22:01.610
I talk about this all the time or as much

22:01.610 --> 22:03.550
as people will let me talk to them

22:03.970 --> 22:06.633
until they get bored and turn and run and scream away.

22:06.633 --> 22:08.383
The set-based design.

22:08.557 --> 22:11.057
And you hear about that a lot,

22:11.434 --> 22:13.060
and I think a lot of people don't necessarily

22:13.060 --> 22:16.520
understand what we talk about when we have set-based design.

22:16.520 --> 22:19.140
The typical way we design things is,

22:19.140 --> 22:21.800
we come up with a technology set, and then we do

22:21.800 --> 22:25.320
a few, okay, how would this look, bang?

22:25.320 --> 22:27.360
And then we look at a few different things,

22:27.360 --> 22:28.960
and then we decide, well, which of those

22:28.960 --> 22:29.940
do we like better?

22:30.130 --> 22:32.190
That's point-based design, and in some ways

22:32.190 --> 22:33.330
it serves us well.

22:33.740 --> 22:37.210
In set-based design and the core to set-based design

22:37.750 --> 22:39.360
is the right tool set.

22:39.680 --> 22:41.940
When you have the right tool set,

22:42.240 --> 22:45.840
you can generate thousands

22:46.390 --> 22:50.380
of initial designs and create a design space.

22:50.880 --> 22:52.590
And when you have that design space,

22:52.590 --> 22:54.160
but in order to, I'll get that, but when

22:54.160 --> 22:56.300
you have that design space, you're not talking

22:56.300 --> 22:58.730
about, I like this or that, what you're

22:58.730 --> 23:01.570
talking about then is, we can see,

23:01.570 --> 23:04.490
what is it that we value in the design,

23:04.760 --> 23:07.100
and what's the cost of obtaining that thing with value.

23:07.100 --> 23:09.250
And I say cost, not merely in dollars,

23:09.600 --> 23:13.340
I say cost in, well, how much, in the case

23:13.340 --> 23:15.861
of an amphib, and whoever didn't hear

23:15.861 --> 23:18.795
the major general's talk yesterday, right,

23:18.795 --> 23:21.240
you missed out, because that was a great talk.

23:21.240 --> 23:23.480
But he talked about wanting to go beyond

23:23.480 --> 23:25.940
the five fingers of lift, so I'm not going

23:25.940 --> 23:27.950
to show him my slides that I have in here

23:27.950 --> 23:29.550
about the fiver fingers of lift,

23:30.150 --> 23:32.700
but it's really useful, and he was exactly right.

23:32.700 --> 23:34.350
But let's talk about the five fingers of lift.

23:34.350 --> 23:36.940
It's really useful for our senior leaders,

23:36.940 --> 23:39.310
when they're making decisions, to know,

23:39.310 --> 23:42.560
well, I need another two knots on that amphib.

23:43.060 --> 23:44.860
All right, that'll cost you four hundred feet

23:44.860 --> 23:46.770
of vehicle square when I redesign the engine room.

23:46.770 --> 23:49.030
And we got this, we tried it a bunch of

23:49.030 --> 23:51.040
different ways in the model so we could show

23:51.040 --> 23:53.880
all the different ways across thousands

23:53.880 --> 23:56.050
of possible designs, and you know that,

23:56.050 --> 23:58.030
roughly, that two knots is going

23:58.030 --> 24:00.820
to cost you four hundred feet of vehicle square.

24:00.830 --> 24:03.030
And then you can ask, is that worth it?

24:04.340 --> 24:06.090
That becomes a requirement decision.

24:06.090 --> 24:07.530
Well, what set-based design does

24:07.530 --> 24:09.430
is make an informed requirement decision.

24:09.430 --> 24:11.770
In order to do that effectively,

24:12.010 --> 24:14.859
you need a really high level tool set.

24:14.859 --> 24:16.500
RSDE, which you see up there,

24:16.500 --> 24:19.190
that stands for Rapid Ship Design Environment.

24:19.230 --> 24:20.910
And that's not only a tool set,

24:20.910 --> 24:22.610
but it's a collaborative tool set,

24:23.148 --> 24:24.450
it's gotta be your computer tools,

24:24.450 --> 24:26.220
not just us at Dahlgren looking

24:26.220 --> 24:29.020
at how hulls float through water,

24:29.020 --> 24:31.300
but that includes all of our partners,

24:31.300 --> 24:33.300
it includes the dahlgren tools

24:33.300 --> 24:37.020
for topside design, it includes the Corona tools

24:37.020 --> 24:39.350
for analysis, it includes not just our ship design,

24:39.350 --> 24:41.260
but our vulnerability tools to say,

24:41.260 --> 24:43.040
is this really going to be survivable,

24:43.040 --> 24:44.620
so that you can do the analysis,

24:44.620 --> 24:46.530
so that you can do the design across a lot

24:46.530 --> 24:48.630
of preliminary designs and then understand

24:48.630 --> 24:50.430
what your trade-offs when you do that.

24:50.430 --> 24:52.150
So to do that, you not only need

24:52.150 --> 24:54.120
the computer tools, but you also need the disciplines

24:54.120 --> 24:58.287
across the range that the Surface Warfare Center provides.

25:00.620 --> 25:03.010
And ultimately, and I can't stress this enough,

25:03.010 --> 25:04.010
you need the people.

25:04.900 --> 25:08.500
All the great models and all the great designs,

25:08.518 --> 25:12.070
if you don't have great people who are motivated,

25:12.070 --> 25:14.050
who are smart, who are properly educated

25:14.050 --> 25:16.240
and properly trained in order to make those

25:16.240 --> 25:18.647
models work and turn all that data

25:18.647 --> 25:21.814
into useful information so that we can

25:22.220 --> 25:24.540
make intelligent decisions about

25:24.830 --> 25:27.010
where we want to go with ship design

25:27.010 --> 25:30.711
and how we want to substantiate, instantiate

25:30.711 --> 25:32.858
that combat capability on those ships,

25:32.858 --> 25:34.960
you're never gonna get there.

25:34.960 --> 25:38.100
So, having the people, the people of the Warfare Center

25:38.100 --> 25:41.580
that we take time to identify, to recruit,

25:41.580 --> 25:45.740
to train, to retain, is what makes it all possible.

25:48.030 --> 25:52.197
So, with that, I just wanted to say those few words.

25:54.520 --> 25:57.240
Getting ready to turn it over to my colleagues.

25:57.900 --> 26:00.448
Carderock, when I first got to Carderock,

26:00.448 --> 26:04.350
Dahlgren had come out with the truly great tagline

26:04.350 --> 26:08.270
that they put the war in warship, which they do.

26:08.270 --> 26:10.470
And when I heard that, I said, that's right,

26:10.620 --> 26:12.570
and Carderock puts the ship in warship.

26:13.830 --> 26:15.500
So, for the building of future warships,

26:15.500 --> 26:17.670
you've now heard the ship side.

26:18.450 --> 26:20.550
Before I turn it over to the war side,

26:20.710 --> 26:23.000
I will say that this is the team business,

26:23.000 --> 26:25.960
and I talked about people, and we focused heavily

26:25.960 --> 26:29.280
on the team that Surface Warfare Center brings,

26:29.800 --> 26:32.530
and although that is a collaborative team,

26:32.680 --> 26:34.850
our collaboration does not end Just

26:34.850 --> 26:37.880
at the Warfare Center, but it is across

26:38.080 --> 26:41.720
the whole Naval Research and Development enterprise.

26:41.720 --> 26:43.300
Again, I hate speaking in acronyms.

26:43.300 --> 26:45.260
And with industry, and in our case,

26:45.260 --> 26:47.638
especially with academia, to bring all of that talent

26:47.638 --> 26:50.940
to bare, again, to provide the capabilities

26:50.940 --> 26:53.060
that the warfighters need to win.

26:53.060 --> 26:54.800
And that's the bottom line, it's the capability

26:54.800 --> 26:56.190
the warfighters need to win.

26:56.190 --> 26:58.700
And to talk about the war capabilities

26:58.700 --> 27:01.170
that they need to win, I turn it over to my friend

27:01.170 --> 27:02.870
and colleague, Captain Gus Weekes.

27:03.698 --> 27:04.698
- All right.

27:07.060 --> 27:08.110
Good afternoon, all.

27:08.969 --> 27:11.235
(chattering)

27:11.340 --> 27:12.173
All right.

27:12.796 --> 27:15.360
Captain Gus Weekes, CO of Dahlgren.

27:15.360 --> 27:17.802
Happy to be here, it's been an exciting

27:17.802 --> 27:18.921
couple of days.

27:18.921 --> 27:23.088
And even on Monday here, Admiral Kilby over at Pathfinders,

27:23.658 --> 27:27.325
but for SNA, the team, as my colleague said,

27:27.992 --> 27:30.075
is integrated in the win.

27:30.380 --> 27:33.910
So, let's talk for a moment about

27:33.999 --> 27:37.832
integration from a combat systems perspective.

27:38.190 --> 27:41.470
So, let's take something like a high energy laser.

27:41.720 --> 27:44.770
So, a high energy laser is not fully effective

27:44.770 --> 27:46.910
unless it is fully integrated across

27:46.920 --> 27:48.670
the ship and the combat system.

27:49.079 --> 27:51.912
But that is easier said than done.

27:53.680 --> 27:56.130
By definition, we all know, we can see

27:56.130 --> 27:58.190
in the picture, the environment in which we

27:58.190 --> 28:01.550
operate those combat systems is an unforgiving environment.

28:01.860 --> 28:04.770
We have Sea-Spray for those who operate

28:04.770 --> 28:07.510
up in the Gulf, we have the Immunity,

28:08.460 --> 28:12.627
and Wave Slap working up in the Northern waters.

28:12.875 --> 28:16.958
So, we have to build the systems to survive that.

28:19.821 --> 28:22.332
Many of the vibrations from the engines,

28:22.332 --> 28:25.350
again, just plowing through the seas,

28:25.350 --> 28:27.500
these are effects that the ATL,

28:28.261 --> 28:32.428
which is a precision system has to survive.

28:34.520 --> 28:36.480
And then you have, as we said,

28:36.530 --> 28:39.410
they are warships, so they carry weapons.

28:39.930 --> 28:44.097
And the employment of guns or missiles by definition

28:44.520 --> 28:47.680
produce a sonic shock.

28:48.909 --> 28:50.670
It has to survive that.

28:50.670 --> 28:53.480
The gases from a missile shot are corrosive.

28:54.010 --> 28:55.260
It has to survive that.

28:56.540 --> 29:00.663
It's operating on a Aegis platform or on an amphib,

29:00.663 --> 29:04.020
which has radars and other sensors.

29:04.020 --> 29:06.210
So the EMI environment in which it has

29:06.210 --> 29:09.400
to operate, more than likely, it will have

29:11.037 --> 29:14.704
to develop a different type of EMI shielding

29:14.810 --> 29:18.100
technologies and approaches for the high energy laser.

29:19.090 --> 29:20.200
Then there's power.

29:20.570 --> 29:23.400
And again, working with our sister centers

29:23.400 --> 29:27.100
like Carderock and Philly to develop,

29:27.100 --> 29:29.760
you know, high energy lasers, by definition,

29:29.760 --> 29:33.180
are only 25 to 35 percent efficient.

29:33.660 --> 29:36.250
And the weapon creates a pulse load

29:36.250 --> 29:38.300
through the power system during firing,

29:38.610 --> 29:41.180
and this can create a phase and voltage droops

29:41.180 --> 29:43.590
in the ship's prime power.

29:44.290 --> 29:47.100
Prime power management strategies and maybe

29:47.100 --> 29:48.954
even intermediate storage as we saw

29:48.954 --> 29:53.121
on Mark's slides showing

29:53.460 --> 29:55.750
about an energy battery.

29:56.133 --> 29:59.309
Those type of different ways of looking at

29:59.309 --> 30:02.726
how do we employ systems will be required

30:02.800 --> 30:06.467
as we move into things like directed energy.

30:08.010 --> 30:12.177
And then, finally, some of our sister services,

30:12.461 --> 30:16.020
they say, hey, the Navy has it easy when they

30:16.020 --> 30:19.320
want to integrate lasers onto a ship.

30:19.320 --> 30:23.487
They said, we have all of that space to bring

30:23.950 --> 30:26.630
that capability into, nothing like doing

30:26.630 --> 30:28.410
it on a tank or a jet.

30:29.140 --> 30:33.307
But let's not forget, on that DDG,

30:34.130 --> 30:38.060
there are 200 plus sailors that have to operate,

30:40.770 --> 30:43.730
get their laundry done, eat, work out,

30:43.960 --> 30:47.170
so you quickly find that you don't have as,

30:47.800 --> 30:51.967
369, 369 sailors aboard that have to

30:52.810 --> 30:53.940
operate that ship.

30:54.670 --> 30:58.330
And they're also filled with tons of explosives,

30:58.930 --> 31:00.980
hundreds of thousands of gallons of fuel,

31:02.086 --> 31:03.560
and, again, the sensors.

31:03.560 --> 31:07.727
So it is not a trivial matter to shoehorn

31:08.383 --> 31:11.216
capability, especially afterwards,

31:11.645 --> 31:13.395
onto these platforms.

31:13.410 --> 31:16.350
So, doing it with modularity and flexibility

31:16.350 --> 31:19.924
upfront will allow our nation to bring

31:19.924 --> 31:24.007
future capabilities to the forefront much easier.

31:25.231 --> 31:27.814
Okay, that's on the next slide.

31:29.150 --> 31:32.380
So, the only reason I put this slide on there

31:32.460 --> 31:35.280
is just because it is not getting simpler out there.

31:36.050 --> 31:38.690
The threat is growing, the threat is more complex,

31:39.150 --> 31:42.600
but as I tell the workforce where we are,

31:43.300 --> 31:44.980
if it was easy, someone else would be doing it,

31:44.980 --> 31:46.820
so we're getting after it.

31:49.660 --> 31:53.660
So, as we, and it's a balancing act.

31:53.770 --> 31:55.750
There are several drivers and variables

31:55.860 --> 31:59.380
that play into what we can and what we will produce.

31:59.610 --> 32:02.300
Never losing sight that our job remains

32:02.300 --> 32:04.580
engineering the detect, control, engage,

32:04.800 --> 32:06.500
and closing the fire control loop.

32:06.750 --> 32:10.150
So, what we end up doing, and what we

32:10.150 --> 32:13.640
are driving towards is a common warfighting design,

32:13.810 --> 32:17.977
which, by definition, will improve our affordability cost,

32:18.440 --> 32:21.240
and then exploit the network environment

32:21.260 --> 32:23.090
in which we operate.

32:23.980 --> 32:27.170
We have to do that in the time constraints

32:27.350 --> 32:29.450
that we are given between new construction

32:29.539 --> 32:31.870
or maintenance availabilities,

32:31.870 --> 32:35.000
but also not forgetting or nor discounting

32:35.330 --> 32:38.130
the capability or the ability to expand

32:38.130 --> 32:40.980
the advantage via taxes, the non-material

32:40.980 --> 32:44.130
solutions, not just materially

32:44.520 --> 32:46.550
what new widget or capability we try

32:46.550 --> 32:50.590
to bring, more, how do we employ those systems differently.

32:51.090 --> 32:54.510
But keeping to the theme of high energy laser,

32:55.010 --> 32:57.970
those are things that we'll have to do differently,

32:57.970 --> 32:59.808
and then find the time to bring it up

32:59.808 --> 33:02.391
and integrate it into the ship.

33:06.770 --> 33:08.070
I'll just say, the admirals have somebody

33:08.070 --> 33:10.403
clicking from yesterday, just saying.

33:10.403 --> 33:12.653
(laughing)

33:13.490 --> 33:17.530
So then we have, gotta put on the glasses for this one.

33:18.721 --> 33:22.888
So then we have CC, and how are

33:23.610 --> 33:25.390
high energy lasers in this regard

33:26.230 --> 33:29.700
brought into the CC or the combat systems?

33:30.010 --> 33:32.320
So CC provides a force level communication

33:32.320 --> 33:34.320
to enable coordination of engagement

33:34.370 --> 33:36.250
by enabling fire control quality

33:36.530 --> 33:38.480
data to be distributed across the force.

33:38.480 --> 33:40.520
So, as a weapon and as a sensor,

33:40.660 --> 33:43.630
a laser is envisioned to be both a contributor

33:43.830 --> 33:46.150
too, and a consumer of this information,

33:46.570 --> 33:49.190
providing high quality track data to the network

33:49.480 --> 33:51.740
and using data from other sensors to locate

33:51.840 --> 33:53.410
and engage targets itself.

33:53.870 --> 33:57.210
In regards to AEGIS, and integrated laser weapon system

33:57.210 --> 33:59.300
provides both a new sensor and an engagement

33:59.300 --> 34:02.050
capability to the AEGIS ship, broadening

34:02.050 --> 34:04.670
the range of tactical responses.

34:05.440 --> 34:08.210
So, giving you a graduates lethality

34:08.210 --> 34:10.790
I think somewhere, we heard earlier

34:11.992 --> 34:14.909
today that you can go from dazzling

34:15.050 --> 34:19.050
to interference to soft kill to hard kill.

34:19.440 --> 34:21.620
And the same thing is for SSDS

34:22.730 --> 34:26.360
that are found on the carriers and the amphibs.

34:26.420 --> 34:30.587
So it's a broadening of the scope

34:30.840 --> 34:34.110
of response that is available to the warfighter

34:34.260 --> 34:36.060
as we bring this capability forward.

34:40.780 --> 34:43.270
And again, back to the, but one of the things,

34:43.770 --> 34:45.520
and is always funny trying to think

34:45.670 --> 34:48.460
about this differently, the magazine,

34:48.460 --> 34:52.021
your new magazine is a capacitor or some type

34:52.021 --> 34:55.854
of energy storage device, and I will tell you,

34:56.180 --> 34:58.930
the electric engineers and scientists

34:58.930 --> 35:02.590
that we have at Dahlgren and Philadelphia

35:02.800 --> 35:05.050
are just tickled beyond reason to try to

35:05.050 --> 35:09.217
figure out what is the best strategy and design

35:09.296 --> 35:13.296
to bring to the ships to enable this capability.

35:19.210 --> 35:21.870
So, a little bit about how, a little bit

35:21.870 --> 35:24.220
how we're doing things a little differently now

35:25.840 --> 35:26.673
at Dahlgren.

35:26.930 --> 35:29.830
So, what we've embarked upon is to ensure

35:29.830 --> 35:32.030
that we have a repeatable process

35:32.410 --> 35:36.577
to go after the capability gaps

35:37.600 --> 35:39.320
that are identified by the fleet.

35:39.610 --> 35:42.780
So, as you see at the top, we've initiated,

35:42.780 --> 35:45.080
what we have are, the innovation lab,

35:45.570 --> 35:48.810
and we've had at least two workshops thus far,

35:49.170 --> 35:52.440
and what we do, we bring in, depending on the issue

35:52.440 --> 35:54.990
that we're, the thesis that we're trying to attack,

35:55.110 --> 35:59.277
we'll bring in Dahlgren workforce, bring in

36:00.040 --> 36:02.457
workforce from other centers.

36:03.200 --> 36:07.367
We'd love to get, we get fleet representatives

36:07.680 --> 36:10.990
to come in, academia if possible,

36:13.533 --> 36:17.283
and, at this point, a select few

36:17.760 --> 36:20.950
opportunities for other outside organizations

36:20.950 --> 36:25.117
to participate, and what they do, it's not

36:25.670 --> 36:28.680
just engineers, we've had in some of these workshops

36:28.730 --> 36:31.840
that are dealing with significant capability

36:32.350 --> 36:35.150
identification is have someone from, say,

36:35.150 --> 36:39.317
our logistics and a property management group

36:39.990 --> 36:44.157
come in and give a totally different perspective,

36:44.772 --> 36:47.410
not coming in with, I already know the answer

36:47.410 --> 36:49.460
because I've been doing this for 20 years,

36:49.460 --> 36:51.530
and they go through the workshop,

36:51.720 --> 36:55.887
and it's a process of discovery that can then

36:56.080 --> 36:58.820
be used, and we have, again, in a partnership

36:58.820 --> 37:00.710
across the warfare centers, we have

37:00.710 --> 37:03.640
the fleet engagement COP, we have three warfare,

37:03.640 --> 37:06.980
the main leaders, we are fortunate to have

37:06.980 --> 37:09.860
the surface warfare domain leader at Dahlgren,

37:10.111 --> 37:14.278
working out of Dahlgren even though he's a HQ employee.

37:17.300 --> 37:20.440
And we provide those inputs into the FECOP,

37:21.240 --> 37:25.407
which again, is our fleet engagement community,

37:26.690 --> 37:30.090
they take into the FET, which helps to inform

37:30.090 --> 37:33.340
how we choose what projects we pick

37:33.340 --> 37:37.210
during our 219 evaluations,

37:37.240 --> 37:41.407
which, for 219 is our iRAD, basically our research dollars

37:41.980 --> 37:45.760
to look at technologies that is needed

37:45.760 --> 37:49.380
by the fleet to address capability gaps.

37:51.700 --> 37:54.160
As my partner in crime, Mr. John Fiore

37:55.210 --> 37:57.000
says often, I'll (stuttering).

37:59.650 --> 38:03.610
Our soul purpose here is to identify with the

38:03.610 --> 38:05.850
where the warfighter gaps are and understand

38:05.850 --> 38:07.390
how we close those gaps.

38:07.390 --> 38:11.557
That is the purpose of this digital strategy

38:12.520 --> 38:16.340
and how we identify our future 219 dollars,

38:16.340 --> 38:18.270
and then we take that into demo, and that's

38:18.270 --> 38:21.070
where we are able to partner more

38:21.070 --> 38:24.310
with our industry partners to demonstrate

38:24.310 --> 38:28.477
a capability in closing the capability gap

38:29.670 --> 38:30.680
for the warfighter.

38:31.751 --> 38:32.584
And then the big thing about this,

38:32.584 --> 38:34.540
at least for me, is that it's repeatable

38:34.690 --> 38:35.780
and it's disciplined.

38:40.878 --> 38:43.090
And so we take things like strike group defender,

38:43.090 --> 38:45.610
which are just different tools and a different

38:46.417 --> 38:49.160
way of looking at it to have that discussion

38:49.160 --> 38:50.360
and have that discovery.

38:50.850 --> 38:53.510
So, that is one of the ways that we're looking

38:53.510 --> 38:56.450
at the integration of combat system and combat system

38:56.450 --> 38:59.090
capability at Dahlgren.

38:59.300 --> 39:01.750
So, with that, are you clicking?

39:02.225 --> 39:03.892
- Thank you.

39:07.740 --> 39:09.660
So, the guidance from Admiral Druggan

39:10.575 --> 39:12.430
was that less slides is better.

39:12.430 --> 39:13.612
So I'm gonna present a single slide,

39:13.612 --> 39:14.712
and but it's detailed.

39:16.832 --> 39:17.665
- With 15 clicks.

39:17.665 --> 39:19.915
(laughing)

39:20.000 --> 39:22.390
- A future electromagnetic maneuver warfare

39:22.390 --> 39:24.190
architecture to enable warfighting

39:24.190 --> 39:26.230
such that there is a proactive control

39:26.290 --> 39:29.350
of the electromagnetic spectrum begins

39:29.350 --> 39:30.690
with a focus on data.

39:31.400 --> 39:34.190
We need to develop, contribute, and maintain

39:34.190 --> 39:36.780
an EW data library that is integrated

39:36.780 --> 39:40.060
within an overarching and larger track library.

39:41.072 --> 39:43.320
We will capture ES detections and track information

39:43.320 --> 39:45.890
over time, throughout the fleet, and across

39:45.890 --> 39:49.180
multiple frequencies, with all sensors contributing.

39:50.220 --> 39:52.720
With the goal to gain decisive military advantage

39:52.720 --> 39:55.030
in the electromagnetic spectrum and enable

39:55.030 --> 39:57.342
the ability to conduct critical Navy mission areas,

39:57.342 --> 40:00.699
emerging data science approaches for unstructured data

40:00.699 --> 40:03.850
such as deep learning and spiking neural nets

40:03.850 --> 40:07.150
can enable the application of machine learning

40:07.150 --> 40:09.050
and artificial intelligence algorithms

40:10.263 --> 40:12.100
to this growing data set.

40:12.100 --> 40:14.810
Cognitive EW in advanced automation can provide

40:14.810 --> 40:16.800
the ability to maintain positive control

40:16.800 --> 40:19.100
of the spectrum within a tactical environment.

40:19.710 --> 40:22.010
This dynamic monitoring and captured data

40:22.010 --> 40:25.530
across multiple frequencies can enable the EMW C2

40:25.530 --> 40:28.950
necessary to respond to changes in the electromagnetic

40:28.950 --> 40:31.690
environment and warfighter requirements

40:31.690 --> 40:33.910
across C4I and combat systems.

40:34.330 --> 40:36.330
This dynamic frequency management

40:36.330 --> 40:38.890
can therefore enable optimization and resources

40:39.020 --> 40:40.970
to maximize warfighter performance

40:41.100 --> 40:44.010
and freedom of action across all mission areas.

40:44.690 --> 40:46.620
Coordination across multiple programs

40:46.620 --> 40:48.380
and virtual technologies can enable

40:48.380 --> 40:50.310
shared apertures and power management.

40:50.700 --> 40:53.720
Such bands are shared and optimized.

40:54.180 --> 40:57.730
We are ultimately creating an EMW digital twin

40:58.280 --> 41:01.650
of the dynamic spectrum at a technology,

41:01.820 --> 41:03.930
at a platform, and at a force level.

41:04.630 --> 41:07.240
The analysis of this EMW digital twin

41:07.330 --> 41:09.790
can enable rapid requirements identification

41:09.790 --> 41:12.775
based on emerging threats, new tactical approaches,

41:12.775 --> 41:14.940
and predicted capabilities.

41:15.190 --> 41:17.750
Through an agile software development approach,

41:17.750 --> 41:19.900
software updates can be developed rapidly

41:19.900 --> 41:21.292
to feed system updates.

41:21.292 --> 41:25.056
These may be pushed to legacy or future decoys

41:25.056 --> 41:28.040
with an expanding set of possibilities,

41:28.040 --> 41:30.580
including the miniaturization of recoverable

41:30.670 --> 41:33.310
software decoys, it gets you thinking,

41:33.310 --> 41:35.150
what is the future of decoys?

41:35.585 --> 41:39.040
Software updates can also be pushed to C-web,

41:39.040 --> 41:41.050
which is enabled with it's capacity to field

41:41.050 --> 41:42.870
block upgrades programmatically.

41:43.520 --> 41:45.516
The innovative software coordinator system

41:45.516 --> 41:48.766
provided through a modular architecture

41:48.840 --> 41:52.260
of the C-web software enables rapid and cost effective

41:52.260 --> 41:54.670
upgrade of improved capabilities in response

41:54.670 --> 41:56.770
to emerging requirements and threats.

41:57.469 --> 41:59.870
The decoupling of the hardware and software

41:59.870 --> 42:02.580
of C-web further enables the streamline

42:02.580 --> 42:03.600
upgrade approach.

42:04.170 --> 42:06.480
From a hardware perspective, what can we do

42:06.480 --> 42:08.443
to push beyond current hardware limits

42:08.443 --> 42:12.610
given the possibilities offered by material science?

42:12.800 --> 42:15.730
Wideband arrays allow for extended frequency coverage

42:15.730 --> 42:18.260
and advance FPGAs and they will increase

42:18.360 --> 42:19.340
processing power.

42:20.030 --> 42:22.200
Capacitor banks enable the ability to hold

42:22.200 --> 42:24.370
and condition power at a platform level.

42:25.180 --> 42:27.240
What is possible with meta materials?

42:27.400 --> 42:30.160
High efficiency, wide bandwidth power devices,

42:30.170 --> 42:32.740
and multi band high volume secure data links.

42:34.670 --> 42:37.280
Our EMW digital twin is critical.

42:37.590 --> 42:39.910
Not only for requirement setting perspective,

42:39.920 --> 42:42.940
but also from the perspective of rapid validation

42:42.950 --> 42:44.190
of those requirements.

42:44.620 --> 42:46.940
To pace a threat, we have to have an agile

42:46.940 --> 42:49.730
testing methodology, that allows for

42:49.730 --> 42:52.240
the complexities presented by new automation

42:52.490 --> 42:53.460
and technologies.

42:54.100 --> 42:57.680
How do we test in the future with artificial intelligence.

42:57.680 --> 42:58.610
Was that even on?

42:59.390 --> 43:00.240
- [Admiral] Nope.

43:00.590 --> 43:01.423
- Thank you.

43:01.750 --> 43:03.680
The streamline requirements development

43:03.680 --> 43:06.320
and testing approach align through a digital twin

43:06.320 --> 43:09.570
virtual representation, enables rapid fielding

43:09.570 --> 43:11.090
to serve as platforms.

43:11.960 --> 43:14.990
With the advent of digital solid state systems,

43:14.990 --> 43:16.810
multi statics, and advanced high power

43:16.810 --> 43:19.400
capabilities, we have to have the ability

43:19.400 --> 43:21.934
to create a force level integrated sensor network,

43:21.934 --> 43:24.934
with our EW radar and laser systems,

43:25.029 --> 43:27.300
all contributing to provide for

43:27.300 --> 43:29.840
integrated communications and increase

43:29.840 --> 43:32.820
battle space awareness to find, control,

43:32.820 --> 43:35.040
and predict adversary operations.

43:35.240 --> 43:37.330
We also have to be cognitive of our own

43:37.330 --> 43:39.700
emissions and incorporate this as a critical

43:40.627 --> 43:41.960
aspect of EMWC2.

43:42.162 --> 43:44.660
This integrated sensor network ultimately

43:44.660 --> 43:47.060
provides the ability to build maneuver space

43:47.060 --> 43:49.380
in contested and congested environments.

43:49.758 --> 43:52.330
With the resiliency enabled by the support

43:52.330 --> 43:55.060
of integrated communications, radar to radar

43:55.060 --> 43:57.160
line of sight communications and network links

43:57.160 --> 44:00.280
such as Tattle and CC, there's a vast expansion

44:00.280 --> 44:02.570
in the available CONOFF's that are possible

44:02.570 --> 44:03.870
in future warfighting.

44:04.350 --> 44:07.440
We have an approved accuracy at farther ranges.

44:07.550 --> 44:10.450
Cooperative, yes, obstacle detection and denial

44:10.450 --> 44:13.190
provided enhanced awareness and control

44:13.190 --> 44:14.960
over the tactical battles phase.

44:15.570 --> 44:18.050
Artificial intelligence technologies

44:18.180 --> 44:22.080
apply to our EMW digital twin, enables increased

44:22.080 --> 44:24.960
detection and predictive ID capabilities.

44:25.510 --> 44:27.890
We absolutely must be able to conduct

44:27.890 --> 44:30.750
simultaneous missions as well as hard kill

44:30.750 --> 44:32.330
and soft kill integration.

44:33.501 --> 44:36.100
And with unmanned platforms, it is offered

44:36.100 --> 44:37.900
an increased opportunity within

44:37.900 --> 44:39.810
the electromagnetic space.

44:40.610 --> 44:43.310
Dynamic control of magnetic spectrum

44:43.310 --> 44:46.173
is a critical part of architecting a force level design

44:46.173 --> 44:49.673
to enable distributed maritime operations.

44:49.820 --> 44:52.410
Emerging technologies enable an incredible

44:52.410 --> 44:55.680
expansion in the range of tactical possibilities.

44:56.090 --> 44:59.410
The development and maintenance of an EMW digital twin

44:59.440 --> 45:02.690
is a key component of an overhaul future architecture

45:02.870 --> 45:05.375
that can leverage emerging AI technologies

45:05.375 --> 45:08.538
and optimize frequency utilization within

45:08.538 --> 45:10.288
a dynamic EW context.

45:10.685 --> 45:14.268
We must evolve our requirements and testing

45:14.830 --> 45:17.890
methodologies to account for these new technologies

45:18.050 --> 45:20.570
and technological possibilities at the platform

45:20.570 --> 45:21.670
and the force level.

45:22.280 --> 45:24.550
It is absolutely essential that we evolve

45:24.550 --> 45:27.078
in these two areas, requirement setting

45:27.078 --> 45:30.090
and model-based testing, if we ware to control

45:30.090 --> 45:33.000
the spectrum, pace the threat, embrace artificial

45:33.000 --> 45:35.120
intelligence, and expand the range

45:35.120 --> 45:37.970
of tactical possibilities for the warfighter.

45:38.550 --> 45:40.800
Adoption of these new approaches by the fleet

45:40.965 --> 45:43.150
is critical.

45:43.150 --> 45:45.310
And so therefore I'll turn it over to

45:45.310 --> 45:47.270
Captain Steve Murray to talk about the fleet

45:47.270 --> 45:49.960
adoption aspects including training and LBC.

45:51.430 --> 45:52.800
- Hi, good afternoon, the goal was

45:52.800 --> 45:53.710
as few slides as possible.

45:53.710 --> 45:54.980
I win, I have no slides.

45:55.414 --> 45:58.738
But what I want to talk about is the greatest

45:58.950 --> 46:01.030
challenge that we, all the work that these folks

46:01.030 --> 46:03.550
do is of no benefit if the sailors

46:03.550 --> 46:06.190
on their ships do not understand how to use

46:06.190 --> 46:07.440
the capability they have.

46:07.720 --> 46:09.970
And that capability is integrated in a manner

46:10.563 --> 46:11.530
that allows us to fight and win

46:11.530 --> 46:13.340
when we're out there at the pointy end.

46:14.360 --> 46:16.670
So NSWC Corona, I left there back in October.

46:16.740 --> 46:18.620
The current CO, Rick Braunbeck is out in the audience.

46:18.620 --> 46:21.450
I encourage you, if you have questions about Corona

46:21.450 --> 46:22.740
to reach out to Rick.

46:23.046 --> 46:26.796
But Corona is partnered with Fleet Forces N7,

46:27.039 --> 46:30.116
Pac Fleet N7, and a large team from industry

46:30.116 --> 46:33.680
to deliver a capability to integrate training

46:33.680 --> 46:36.325
and provide the sailors with an environment

46:36.400 --> 46:38.130
they can use they can ensure they can

46:38.130 --> 46:38.963
fight and win.

46:39.702 --> 46:40.619
So why LBC?

46:40.874 --> 46:41.874
What is LBC?

46:42.470 --> 46:44.040
The live Virtual Constructive training environment

46:44.040 --> 46:47.220
is how do we ensure that, as we build

46:47.220 --> 46:50.420
new weapons systems, doctrine, and tactics,

46:50.570 --> 46:52.953
that exceed the capabilities of our live ranges,

46:52.953 --> 46:56.120
that we have sufficient training space

46:56.374 --> 46:59.624
in virtual constructive realms to ensue

46:59.980 --> 47:02.490
that we can stimulate our sailors to the adversaries

47:02.490 --> 47:04.080
we will face when we fight.

47:04.450 --> 47:06.940
And ensure they build reps and sets

47:07.360 --> 47:09.600
to handle those threats and win.

47:11.150 --> 47:12.650
We also have a world of challenges with resource

47:12.650 --> 47:14.550
constraints and those resource constraints

47:14.550 --> 47:15.850
apply to training as well.

47:15.970 --> 47:17.370
The amount of ordinance that we have

47:17.370 --> 47:18.203
is limited.

47:18.220 --> 47:20.270
The amount of targets we have is limited.

47:20.410 --> 47:22.440
The amount of ships we have they can play Op 4

47:22.440 --> 47:23.950
is limited, when ships are playing Op 4,

47:23.950 --> 47:25.746
they're not prepping themselves for the fight

47:25.746 --> 47:28.040
and we need all the ships wee can as we've heard

47:28.040 --> 47:29.440
throughout the week already.

47:30.400 --> 47:33.120
So if we can create a constructive or a virtual

47:33.120 --> 47:36.810
ship as an adversary that replicates the threat

47:36.810 --> 47:39.360
they'll face, we can make, for those sailors

47:39.360 --> 47:41.380
on the ships, simulate them to the environment

47:41.380 --> 47:43.230
they're going to see when they fight.

47:44.290 --> 47:45.720
And we're also challenged as the Admiral mentioned

47:45.720 --> 47:47.140
in his opening, with OPSEC.

47:47.720 --> 47:50.020
We are creating some great capabilities

47:50.220 --> 47:51.790
across warfare centers, across industries

47:51.790 --> 47:53.950
that our sailors are going to use to fight and win.

47:53.950 --> 47:56.530
But if we share those with our, in a public

47:56.530 --> 47:58.700
training forum, our adversaries are watching

47:58.700 --> 48:00.905
and they will learn and they will adapt

48:01.010 --> 48:02.214
and that advantage that we are building

48:02.214 --> 48:03.297
will go away.

48:03.731 --> 48:06.290
And we've got to maintain that advantage always.

48:06.290 --> 48:08.270
So we're building obviously for those reasons

48:08.270 --> 48:09.120
plus some others.

48:09.572 --> 48:12.100
Mark mentioned the environment as well.

48:12.100 --> 48:13.770
There's always environmental concerns.

48:14.434 --> 48:15.719
Every good ordinance we drop, there's always

48:15.719 --> 48:16.552
an environmentalist out there who is concerned

48:16.552 --> 48:18.164
at what that's going to do to

48:18.164 --> 48:20.914
whatever area we're operating in.

48:21.025 --> 48:23.610
So, the fewer amounts of live ordinance

48:23.610 --> 48:25.290
we drop, the better for the environment

48:25.290 --> 48:27.260
and fewer people are complaining about our training.

48:27.260 --> 48:28.640
So all of these pieces come together

48:28.640 --> 48:29.870
into the live virtual training,

48:29.870 --> 48:31.570
live virtual training environment.

48:31.858 --> 48:33.750
Commander Fleet Forces, Commander Executive

48:33.750 --> 48:36.328
agent for that task and Admiral Davidson

48:36.328 --> 48:38.156
through N7 is leading that effort

48:38.156 --> 48:39.982
to build that capability.

48:39.982 --> 48:43.510
Now he's articulated in a couple documents,

48:43.510 --> 48:46.500
2013 with the Fleet LBC training capability

48:46.500 --> 48:49.280
requirements document and then reiterate

48:49.280 --> 48:50.917
in 2016 with a concept of employment.

48:50.917 --> 48:54.196
Both of which lay out what we're looking

48:54.200 --> 48:56.210
to do with a live virtual training environment

48:56.210 --> 48:58.980
and more importantly, the ConAP, it's in this case

48:59.140 --> 49:00.990
about how we're going to employ that.

49:01.120 --> 49:02.790
So what is this environment?

49:03.700 --> 49:06.350
It starts with capabilities that many of you provide.

49:06.350 --> 49:08.360
The total ships, training capability

49:08.360 --> 49:10.990
that exists on our Aegis and SDS platforms today.

49:11.510 --> 49:13.020
We're building a capability for them to train

49:13.020 --> 49:15.980
internally, but also connect externally

49:15.980 --> 49:17.640
through BFIT alongside the peer,

49:17.690 --> 49:19.480
but we're also pushing the limits on that

49:19.480 --> 49:23.520
and connecting via BFAS

49:24.330 --> 49:27.590
or FIST at sea, to allow ships in a COMPTUEX environment

49:27.630 --> 49:30.190
under strike group 214 to connect and be

49:30.190 --> 49:33.430
stimulated virtually or constructively

49:33.600 --> 49:34.700
during their training,

49:34.780 --> 49:37.720
to provide that realism that we need to see.

49:39.460 --> 49:41.440
Also on the air side, the air simulators

49:41.440 --> 49:42.810
are a piece of this as well, and they're

49:42.810 --> 49:44.310
starting to get tied together.

49:44.630 --> 49:46.488
So those two pieces bring the air and the sea together.

49:46.488 --> 49:48.340
But what integrates them is the Navy

49:48.340 --> 49:49.940
continuous training environment.

49:50.520 --> 49:52.800
It's what began with Fleet synthetic training

49:52.900 --> 49:56.470
Navy continuous training environment is what

49:56.470 --> 49:59.050
connects TACTRAGRULANT and TACTRAGRULANTPAC together

49:59.050 --> 50:00.590
with simulated training?

50:01.130 --> 50:02.700
But it's growing around the world.

50:02.700 --> 50:05.980
And right now there's an effort started by

50:05.980 --> 50:08.210
Fleet Forces last year to integrate live tactical

50:08.210 --> 50:09.940
training ranges with the synthetic

50:10.040 --> 50:12.010
to provide that virtual training space,

50:12.010 --> 50:13.830
constructive training space or live training space

50:13.830 --> 50:15.640
as needed around the world.

50:16.050 --> 50:19.290
The concept, the use case, the Fleet forces sites

50:19.290 --> 50:22.760
is the goal is, how do we take a maritime operation

50:22.760 --> 50:25.770
center in a live training state with a strike group

50:25.770 --> 50:27.520
out at sea in a live training state

50:27.550 --> 50:31.717
with another strike group that's in a synthetic state

50:32.140 --> 50:35.380
so think said TACTRAGRULANT tied with other simulators

50:35.380 --> 50:37.610
that are flying and put all those pieces together

50:37.610 --> 50:39.440
into a scenario so all those people are getting

50:39.440 --> 50:41.000
training together.

50:41.220 --> 50:43.150
And from the Mach level all the way through

50:43.150 --> 50:44.870
all the units and ultimately down to all

50:44.870 --> 50:46.460
of the operators, we're able to train

50:46.460 --> 50:48.020
all of them at the same time to that

50:48.020 --> 50:50.100
high end fight and ensure that we can fight and win

50:50.100 --> 50:50.933
on the backend.

50:53.160 --> 50:54.710
Also look into the future that this is how

50:54.710 --> 50:57.160
we integrate this capability across the services.

50:57.670 --> 50:59.370
There's already a push with the Air Force

50:59.370 --> 51:01.771
to bring them together with our Naval aviators

51:01.771 --> 51:03.480
so that they can work together.

51:03.480 --> 51:05.084
JSF is a platform obviously requires integration.

51:05.084 --> 51:07.176
And of course with our Marine corps brethren

51:07.176 --> 51:10.204
and the AMPHIB fight, we've got to integrate

51:10.204 --> 51:14.371
through PM traces and bring that

51:14.969 --> 51:17.690
one training network across the beach.

51:17.690 --> 51:19.650
So if we start an amphibious operation

51:19.650 --> 51:22.830
at sea, say on the West coast, we go across

51:22.830 --> 51:25.750
into Pendleton, we're not operating on two

51:25.750 --> 51:26.960
separate training networks or two

51:26.960 --> 51:29.060
separate training capability, it's all one

51:29.506 --> 51:30.972
training capability tied together,

51:30.972 --> 51:32.560
integrated to ensure that that team,

51:32.560 --> 51:34.410
when called upon, will fight and win.

51:35.680 --> 51:36.940
So if there's no questions, I'll turn it

51:36.940 --> 51:38.640
back over to Admiral Druggan.

51:39.390 --> 51:40.840
- Great, thank you very much.

51:42.680 --> 51:43.513
Can you hear me?

51:43.513 --> 51:44.346
Is this good?

51:44.440 --> 51:46.010
So let's pause for a second there

51:46.010 --> 51:48.082
and just think about where we are

51:48.082 --> 51:50.931
in terms of technology as we mature in the Navy

51:51.200 --> 51:54.472
from a Mil-Spec analog kind of world

51:54.472 --> 51:57.222
into a digital solid state world.

51:57.840 --> 52:00.300
And the challenge is truly how to curate

52:00.430 --> 52:02.661
the opportunities, because it's just replete

52:02.661 --> 52:04.860
with incredible opportunities when you

52:04.860 --> 52:06.800
look into the future, and really,

52:06.800 --> 52:08.410
the future just being a few years,

52:08.410 --> 52:11.810
not decades, there's tremendous opportunity.

52:11.810 --> 52:14.010
And we in the Navy have to be really smart

52:14.010 --> 52:15.990
about the choices we make, and each

52:15.990 --> 52:17.480
of the tool sets and each of the kind

52:17.480 --> 52:21.624
of the mind sets that the panel demonstrated

52:21.624 --> 52:23.630
and talked about to you today

52:23.630 --> 52:25.671
become really important choices for the Navy

52:25.671 --> 52:28.588
and in delivering affordably a Navy

52:28.933 --> 52:32.766
that the nation needs to fight and win at sea.

52:33.290 --> 52:35.020
It's absolutely critical, because we will

52:35.020 --> 52:37.120
always be resource constrained, there's no

52:37.200 --> 52:39.040
question about that, but we've got to get

52:39.040 --> 52:40.940
maximum warfighting value.

52:41.170 --> 52:43.370
So, to do that, in fact, if you can pop to

52:43.550 --> 52:46.090
Captain Weekes, your first slide.

52:46.460 --> 52:48.270
Because I think this will be instructional

52:48.270 --> 52:49.410
because even though we have

52:49.410 --> 52:51.530
those opportunities when we make those choices,

52:51.530 --> 52:53.020
we have a technical due diligence

52:53.020 --> 52:54.370
that we have to go through.

52:55.380 --> 52:57.740
Can you go to Captain Weekes' first slide?

53:00.110 --> 53:01.150
Just one second.

53:09.230 --> 53:10.911
Anyway, so it was the ship integration slide,

53:10.911 --> 53:12.880
if you can remember that.

53:12.880 --> 53:14.330
So that's the technical due diligence

53:14.330 --> 53:16.700
that we have to go through on the government side

53:16.700 --> 53:19.786
and NSWC is a piece of that technical

53:19.786 --> 53:22.953
warrant pyramid to qualify and certify

53:23.178 --> 53:25.095
systems to go on ships.

53:25.280 --> 53:28.065
And these are things that I think are instructive

53:28.065 --> 53:30.565
for folks that have proposals

53:30.930 --> 53:34.410
and what they think they have is an opportunity

53:34.410 --> 53:36.510
for the Navy to increase its warfighting

53:36.510 --> 53:38.400
lethality and effectiveness,

53:38.550 --> 53:40.440
and then they bring their proposals

53:40.440 --> 53:43.270
to the Navy and then we ask a lot of questions,

53:43.510 --> 53:45.380
and we ask a lot of hard questions.

53:45.988 --> 53:48.312
But I have this great capability,

53:48.312 --> 53:50.760
the Navy needs to get this on the ship.

53:50.760 --> 53:53.240
But our technical due diligence is important.

53:53.470 --> 53:55.880
Can it survive shock and vibe,

53:55.940 --> 53:58.820
how will it work with other emitters topside,

53:58.820 --> 54:00.200
will it interfere with them,

54:00.200 --> 54:01.970
is it compatible with them?

54:02.430 --> 54:05.220
How will it work in just a normal maritime environment?

54:05.340 --> 54:07.250
And when I saw normal, I mean the abnormal

54:07.250 --> 54:08.510
maritime environment.

54:08.812 --> 54:12.446
Does it have radar cross section considerations,

54:12.610 --> 54:14.760
what is the demand on the ship in terms

54:14.760 --> 54:15.950
of the SWaP-C?

54:16.380 --> 54:18.810
And for those of you who have the systems

54:19.140 --> 54:22.465
with fantastic capability, please understand

54:22.710 --> 54:24.080
that these are important questions

54:24.080 --> 54:25.980
that must be answered on our side

54:26.270 --> 54:28.290
so that we can field this properly

54:28.500 --> 54:30.250
and then we can build the logistics

54:31.426 --> 54:32.259
and the ilities and get the right training

54:32.259 --> 54:34.610
in place to take advantage of that capability.

54:35.320 --> 54:38.660
It is not fair to the warfighter, absolutely

54:38.660 --> 54:41.550
not fair to deliver a system to a ship

54:41.550 --> 54:44.970
on board a ship, to deliver a system shipboard

54:45.320 --> 54:47.798
that cannot live day to day, that is not

54:47.800 --> 54:51.967
compatible with a shipboard environment, can't do it.

54:52.576 --> 54:54.990
So these are important prerequisites

54:54.990 --> 54:58.040
as we work through delivering capability

54:58.890 --> 55:01.020
to the warfighter so that we can deliver

55:01.020 --> 55:02.420
sea power to the nation.

55:02.610 --> 55:04.260
So, with that, I think we're ready to open

55:04.260 --> 55:05.310
up to a few questions.

55:05.310 --> 55:06.440
A round of applause real quick though

55:06.440 --> 55:07.360
for the panel members.

55:07.360 --> 55:09.610
(applause)

55:23.453 --> 55:26.130
- [Stew] Stew Magnuson, National Defense Magazine.

55:26.130 --> 55:28.730
As far as lasers on ships, what can we look

55:28.730 --> 55:29.563
forward to?

55:29.563 --> 55:31.603
Any milestones you're trying to hit,

55:31.603 --> 55:33.270
any tests coming up?

55:34.970 --> 55:36.330
What's in the near future as far as this goes?

55:36.330 --> 55:37.940
- So, I'll open with that and then

55:37.940 --> 55:39.133
I'll turn it over to Captain Weekes

55:39.133 --> 55:41.970
because there's a lot of activity in lasers.

55:41.970 --> 55:43.890
And the bottom line is, we've now reached the point

55:43.890 --> 55:46.510
in laser development, particularly solid state

55:46.510 --> 55:48.700
laser development, where we can get

55:48.700 --> 55:50.450
military utility out of them.

55:50.680 --> 55:52.210
And when I say military utility,

55:52.210 --> 55:54.865
I mean we can have an effect on the adversary

55:54.865 --> 55:57.698
or the adversary systems at range,

55:57.935 --> 56:00.850
at an operationally important range.

56:00.850 --> 56:03.870
And what may, what folks need to

56:03.870 --> 56:05.430
kind of appreciate is, there are

56:05.430 --> 56:07.950
different development paths that are

56:07.950 --> 56:10.690
currently being explored in the research and development

56:10.690 --> 56:13.500
efforts to deliver capability that are on different

56:13.500 --> 56:14.420
timelines.

56:14.490 --> 56:18.657
So there's near term capability at a lower power level,

56:19.150 --> 56:21.080
and then there's a higher power level,

56:21.080 --> 56:22.740
but it's a little bit further out,

56:22.740 --> 56:24.580
and then there's even further proposals

56:24.580 --> 56:27.710
for a third and highest power level.

56:27.720 --> 56:29.720
So the question depends, well, which laser

56:29.720 --> 56:30.960
do you want to talk about?

56:30.960 --> 56:32.710
So, Gus will talk about all three,

56:32.710 --> 56:34.438
but he did talk about the spectrum

56:34.438 --> 56:37.240
of effects that you can get, but it does

56:37.240 --> 56:38.850
depend on the power level.

56:39.410 --> 56:42.088
And also, the ship integration challenges

56:42.088 --> 56:44.792
that I talked about are even greater with lasers.

56:44.792 --> 56:46.980
Lasers are interesting because they're

56:46.980 --> 56:49.810
not a point effect, it's the whole,

56:50.050 --> 56:54.190
it's along the whole beam that you have an effects.

56:54.190 --> 56:56.730
So you have to understand not just where

56:56.730 --> 56:59.520
I'm sending my ordinance, your ordinance

56:59.520 --> 57:01.550
is a line of bearing, and so you have

57:01.550 --> 57:03.570
to understand what's before the target,

57:03.570 --> 57:07.400
what's after the target and am I inducing

57:07.400 --> 57:10.410
effects on objects in that range

57:10.410 --> 57:11.430
that I don't want to?

57:11.430 --> 57:14.440
So it brings extra considerations over and above

57:14.440 --> 57:17.280
the normal ship integration challenges,

57:17.280 --> 57:19.160
not to mention that it's optical.

57:19.260 --> 57:23.427
And optic in a sea environment and salt spray

57:23.460 --> 57:26.310
and things like that has its own special challenge

57:26.310 --> 57:28.220
just to be shipboard compatible.

57:28.220 --> 57:29.053
So, Gus.

57:32.970 --> 57:33.980
Now, if you can talk about at least

57:33.980 --> 57:36.510
the two programs that are program record right now.

57:39.610 --> 57:41.520
- Normally I don't need a mic, but...

57:42.575 --> 57:44.825
(laughing)

57:44.863 --> 57:47.863
So, as the Admiral stated, there are

57:48.220 --> 57:49.310
a couple of programs.

57:49.830 --> 57:51.940
We are fortunate at Dahlgren that we

57:51.940 --> 57:56.107
are pretty much in lead with (mumbles) and ONR

57:56.594 --> 57:59.560
on the Navy family of laser systems.

57:59.560 --> 58:03.041
So, we have systems that are gonna be

58:03.041 --> 58:07.208
out I would say, this came over the new year,

58:07.370 --> 58:10.350
so in the next year, year and a half

58:10.360 --> 58:12.893
that will be on the lower spectrum from power

58:12.893 --> 58:17.001
that will have a, let's call it a dazzling capability,

58:17.250 --> 58:20.880
out to in the 20, 20, 20, 20, 22 time frame

58:21.030 --> 58:24.580
that will have a larger affect and may be able

58:24.580 --> 58:25.580
to, (clears throat).

58:27.000 --> 58:27.833
Excuse me.

58:28.030 --> 58:32.048
That you'll be able to, in a 50 to 60 kilowatt

58:32.048 --> 58:36.215
power range, and then we'll go beyond,

58:38.230 --> 58:41.577
ONR right now is working on a 150 kilowatt

58:41.577 --> 58:44.244
scientific demonstration project

58:44.880 --> 58:48.170
that we're also leading from in Dahlgren,

58:48.170 --> 58:52.337
so there are graduated levels of capability

58:53.498 --> 58:57.050
that we're bringing forth, and the timelines

58:57.050 --> 58:59.360
for that is anywhere from, again

58:59.360 --> 59:00.970
the next year and a half out to

59:02.080 --> 59:03.610
the next typical five years.

59:04.230 --> 59:07.630
The exciting thing about the laser program

59:07.630 --> 59:09.560
within the Navy is that it has been designated

59:09.560 --> 59:13.727
as an RPED, Rapid Prototype Experimentation

59:15.010 --> 59:18.490
and Demonstration program so that we can

59:18.490 --> 59:20.710
get through some of the traditional acquisition

59:20.710 --> 59:23.070
wickets in an expedited manner so that

59:23.070 --> 59:25.500
we can take the capability to see,

59:26.330 --> 59:29.400
as Admiral Meyer would say, test early,

59:30.280 --> 59:31.290
test early--

59:31.850 --> 59:32.683
- Test a little.

59:32.683 --> 59:33.594
- Build a lot.

59:36.380 --> 59:38.040
So, that's the beauty of what we're getting

59:38.040 --> 59:39.930
ready to embark upon.

59:40.380 --> 59:41.213
- [Druggan] The other challenge I'd like

59:41.213 --> 59:44.140
to point out with lasers is the,

59:44.235 --> 59:48.068
lasers today, even the state of the art lasers

59:48.217 --> 59:51.800
are not as efficient as we need them to be.

59:52.100 --> 59:54.640
So, just the focus on the laser efficiency

59:54.640 --> 59:58.498
power in versus power out plus waste heat

59:58.498 --> 01:00:02.130
is an important consideration because it's driving

01:00:02.130 --> 01:00:04.430
ship integration internal to the ship

01:00:04.580 --> 01:00:06.460
requires a significant amount

01:00:06.460 --> 01:00:09.160
of cooling today to run even low power lasers.

01:00:09.814 --> 01:00:11.290
So there's technological challenges

01:00:11.290 --> 01:00:13.100
that absolutely still remain.

01:00:13.230 --> 01:00:15.620
What's really good about the laser programs

01:00:15.760 --> 01:00:19.700
is the organizations that are involved understand,

01:00:19.700 --> 01:00:21.979
and a lot of this is a tribute to Dahlgren's work,

01:00:21.979 --> 01:00:24.234
what the technical challenges are,

01:00:24.234 --> 01:00:26.817
and what you see is, you see ONR working

01:00:26.890 --> 01:00:29.970
on the future laser, the higher power laser

01:00:30.160 --> 01:00:32.870
while IWS is developing the programmer record

01:00:32.870 --> 01:00:34.670
and the RPED for the near term,

01:00:34.810 --> 01:00:36.350
and that's exactly right and proper,

01:00:36.350 --> 01:00:38.600
and what happened was, ONR was doing

01:00:38.600 --> 01:00:40.462
the lower power laser, it was mature,

01:00:40.462 --> 01:00:43.095
it was time for it to be fielded

01:00:43.150 --> 01:00:45.350
and hit the acquisition side of the house,

01:00:45.350 --> 01:00:48.100
and it was handed off to PEO IWS

01:00:48.100 --> 01:00:50.800
for them to run the programmer record for fielding.

01:00:51.610 --> 01:00:53.760
ONR then pivoted to the higher state,

01:00:53.760 --> 01:00:55.810
to the higher power levels, and we expect

01:00:56.714 --> 01:00:59.714
that to happen again as ONR matures,

01:01:00.500 --> 01:01:04.667
the 150 kilowatt-ish, laser,

01:01:05.000 --> 01:01:08.290
it'll mature at one point, it'll be shipboard compatible

01:01:08.430 --> 01:01:11.940
and it will move over to PEO IWS for execution

01:01:12.130 --> 01:01:13.680
of the acquisition and fielding

01:01:13.980 --> 01:01:16.970
while, meantime, ONR will pivot again

01:01:17.070 --> 01:01:21.237
and go to the highest power level for lasers.

01:01:22.400 --> 01:01:25.470
So, great question, important capability,

01:01:25.470 --> 01:01:27.920
particularly because it does span the spectrum

01:01:29.592 --> 01:01:33.759
from denial to interference, to kinetic effects.

01:01:35.090 --> 01:01:37.410
So, important capability force.

01:01:38.950 --> 01:01:39.783
Yes, please.

01:01:39.783 --> 01:01:41.270
- Hi, Tom, Jim Dick from Cobham Advanced

01:01:41.270 --> 01:01:42.420
Electronic Solutions.

01:01:43.110 --> 01:01:45.830
In the EMW area, I'm curious, we have a lot

01:01:45.830 --> 01:01:48.580
of challenges, you mention a lot of data.

01:01:48.780 --> 01:01:52.430
Is there a plan or a strategy to take advantage

01:01:52.430 --> 01:01:55.610
of the emergence of the unmanned vehicles

01:01:55.830 --> 01:01:57.723
to put sensors on there, to feed that

01:01:57.723 --> 01:02:00.940
data network, and if so, what kinds of sensors

01:02:00.940 --> 01:02:03.878
and how are we communicating that with industry

01:02:03.878 --> 01:02:06.320
to be starting development in the direction

01:02:06.320 --> 01:02:08.030
that the Navy needs us to go?

01:02:08.260 --> 01:02:09.950
- Well, certainly the major unmanned efforts

01:02:09.950 --> 01:02:11.840
have been in the aviation side of the house,

01:02:11.840 --> 01:02:13.840
there's a program office that's working.

01:02:16.159 --> 01:02:19.826
The aircraft carrier capable,

01:02:20.893 --> 01:02:24.909
UAV UBAR for refueling,

01:02:24.909 --> 01:02:27.460
and then potential payloads that go along

01:02:27.460 --> 01:02:30.670
with that, I think refueling is definitely

01:02:30.670 --> 01:02:33.690
the primary mission there, but we also

01:02:33.750 --> 01:02:36.920
had UAVs that we regularly use right now,

01:02:36.920 --> 01:02:39.140
the scan eagle piece and those kinds kinds of things.

01:02:39.140 --> 01:02:41.612
I think the aviation piece is maturing rapidly,

01:02:41.612 --> 01:02:45.779
the USV is a little bit more complicated and is simply

01:02:45.980 --> 01:02:49.250
due to rules of the road and safe navigation

01:02:50.310 --> 01:02:53.750
and the control of those in a maritime environment,

01:02:53.750 --> 01:02:55.880
very close to the ships.

01:02:55.880 --> 01:02:58.770
So the USV, there's lots of work going

01:02:58.770 --> 01:03:00.810
on right now, and what's the potential there.

01:03:00.810 --> 01:03:02.860
There's some key decisions that need to be made

01:03:02.860 --> 01:03:06.400
on what missions it would accomplish and capabilities,

01:03:06.400 --> 01:03:09.040
that's kind of part of the future service combatant

01:03:09.040 --> 01:03:11.830
effort that is ongoing to describe the requirements

01:03:11.830 --> 01:03:13.430
and the capabilities that are needed

01:03:13.430 --> 01:03:17.270
for that future force structure across the board.

01:03:17.370 --> 01:03:21.537
Now, in new UVs, less in the NSWC realm

01:03:21.630 --> 01:03:25.797
or in the NUC, Naval Underwater Center,

01:03:26.950 --> 01:03:29.360
there is activity, and that goes from

01:03:29.570 --> 01:03:32.720
large diameter UUVs all the way down

01:03:32.720 --> 01:03:36.190
to the current UUVs that we have and their missions.

01:03:36.270 --> 01:03:38.510
There's also even smaller ones, hand-held,

01:03:38.560 --> 01:03:42.270
well, not hand-held, but two man portable ones

01:03:42.270 --> 01:03:45.000
called the Mk. 18 that's used extensively

01:03:45.220 --> 01:03:48.542
by the EOD, the Explosive Ordinance Disposal community

01:03:48.542 --> 01:03:51.250
when they're clearing rivers and mines,

01:03:51.250 --> 01:03:52.760
that one happens to be, and I think

01:03:52.760 --> 01:03:56.430
this is true for the other UUVs, highly modular

01:03:56.430 --> 01:03:58.346
in its payloads, and it can take different kinds

01:03:58.346 --> 01:04:01.822
of front ends for different kinds of sonars,

01:04:01.822 --> 01:04:03.660
it has payloads on the side so you can do

01:04:03.660 --> 01:04:06.730
some side scanning, and you can change those out.

01:04:06.830 --> 01:04:10.000
So what happens is, each of these UXVs,

01:04:10.000 --> 01:04:14.167
if you will, become platforms for future payloads.

01:04:14.560 --> 01:04:17.040
So, when you get to the specific payloads,

01:04:17.040 --> 01:04:19.197
I'm less well versed in those on the aviation side

01:04:19.197 --> 01:04:22.140
and the UUV side, so does anyone have

01:04:22.140 --> 01:04:23.980
any particular special knowledge?

01:04:25.799 --> 01:04:28.216
- [Gus] I'll just say that...

01:04:30.290 --> 01:04:33.310
I'll just say that is a focus of one

01:04:33.310 --> 01:04:36.520
of the departments at Dahlgren, is not to

01:04:37.020 --> 01:04:40.310
develop the UUV or the UXV, but it's to,

01:04:40.310 --> 01:04:43.260
what are the payloads we can integrate into

01:04:43.968 --> 01:04:47.885
those platforms to provide a certain capability

01:04:47.971 --> 01:04:50.100
to the fleet, to the operator,

01:04:50.100 --> 01:04:54.267
whether it be sailor or marine or SOF forces.

01:04:54.572 --> 01:04:57.405
- And I'll just say, on the Carderock side again,

01:04:57.405 --> 01:05:00.738
I'm not as well educated on the payloads

01:05:00.984 --> 01:05:03.960
in the centers, it's not our line of business,

01:05:03.960 --> 01:05:06.920
but Carderock is very focused on the power,

01:05:07.060 --> 01:05:10.861
so advanced batteries, advances energy storage,

01:05:10.861 --> 01:05:13.611
and power transfer at sea are all

01:05:14.050 --> 01:05:17.467
areas of our research, and I think we've

01:05:17.480 --> 01:05:20.042
engaged with industry on that where appropriate already,

01:05:20.042 --> 01:05:22.420
and look forward to doing so again,

01:05:22.420 --> 01:05:25.560
but that's where Carderock is as far as our piece,

01:05:25.560 --> 01:05:29.727
especially in the UUV realm of the advanced

01:05:29.880 --> 01:05:31.780
power solutions that provide the power

01:05:31.940 --> 01:05:34.020
so that the payloads work.

01:05:34.886 --> 01:05:37.153
- I think, in terms of mission sets,

01:05:37.153 --> 01:05:38.100
it's pretty straightforward, we always want

01:05:38.100 --> 01:05:41.070
persistent ISR at the max range, right?

01:05:41.210 --> 01:05:43.085
That's every warfighter's dream is to know

01:05:43.085 --> 01:05:46.110
everything that's out there so they can

01:05:46.110 --> 01:05:48.310
make good decisions with less uncertainty.

01:05:48.400 --> 01:05:52.567
So, clearly EO, IR, ES, fit right in those domains,

01:05:52.713 --> 01:05:54.830
many of those systems are small enough

01:05:54.830 --> 01:05:56.260
to fit on the aviation ones.

01:05:56.290 --> 01:05:58.180
Persistent decoys and things like that

01:05:58.180 --> 01:06:01.890
kind of fit into the USV range as well (audio breaking up).

01:06:06.690 --> 01:06:09.470
You know, it remains a clear UUV as well as

01:06:09.470 --> 01:06:13.210
clearing of ordinance and whatnot and mines,

01:06:13.210 --> 01:06:16.900
both in the EOD realm, but also in the ASW

01:06:16.900 --> 01:06:20.040
mission module and the MCM world as well.

01:06:20.167 --> 01:06:23.917
And the other thing is, each of those sensors

01:06:23.919 --> 01:06:26.586
can be smaller, lighter, better,

01:06:28.510 --> 01:06:31.180
and more reliable, will always be a thrust.

01:06:31.200 --> 01:06:33.540
I think one of the things that we should talk

01:06:33.540 --> 01:06:36.590
about when it comes to UXV drones is the size.

01:06:36.600 --> 01:06:38.900
The size has to match the mission.

01:06:39.290 --> 01:06:42.410
And we often see these quadcopters,

01:06:42.740 --> 01:06:45.930
maybe around the neighborhood or on TV

01:06:45.930 --> 01:06:47.730
or delivering your Amazon package, right,

01:06:47.730 --> 01:06:49.680
some of those things.

01:06:49.917 --> 01:06:53.834
For a UXV to be effective with military utility

01:06:54.380 --> 01:06:56.680
at sea, that's insufficient.

01:06:56.680 --> 01:06:58.800
They've got no range and no payload

01:06:59.632 --> 01:07:02.299
that's of much military utility.

01:07:02.610 --> 01:07:04.260
So some people think, quadcopter,

01:07:04.360 --> 01:07:06.960
oh, that Navy really wants the quadcopter.

01:07:07.859 --> 01:07:10.250
Our systems have to have a purpose,

01:07:10.250 --> 01:07:11.690
they have to have a persistent purpose,

01:07:11.690 --> 01:07:13.180
they have to have capability,

01:07:13.290 --> 01:07:15.130
and that capability has to be important,

01:07:15.130 --> 01:07:17.260
because as soon as I start putting UXVs

01:07:18.310 --> 01:07:20.360
and populating and building ships that can

01:07:20.360 --> 01:07:23.060
accommodate those and do command and control of those,

01:07:23.060 --> 01:07:25.540
there's an opportunity cost because it may mean

01:07:25.540 --> 01:07:27.330
that I'm not taking other payloads.

01:07:27.490 --> 01:07:30.400
So, I think those are some of the considerations,

01:07:30.400 --> 01:07:32.790
people think UAVs, they think quadcopter,

01:07:34.470 --> 01:07:37.580
the reality is the sea bot that's being developed

01:07:37.580 --> 01:07:39.620
to go on the aircraft carrier to refuel

01:07:39.947 --> 01:07:44.030
strike wings is not small.

01:07:44.498 --> 01:07:47.310
It's got to carry a lot of gas to do refueling

01:07:47.310 --> 01:07:48.380
of a lot of fighters.

01:07:49.680 --> 01:07:50.513
Thanks.

01:07:52.996 --> 01:07:57.079
- Hi, Sidney Friedburg from Breaking the Offense.

01:07:58.470 --> 01:08:00.260
First of all, one, just to follow up

01:08:00.260 --> 01:08:04.427
on the HEL question, are there specific dates

01:08:04.500 --> 01:08:08.667
for kilowatt power levels of the platforms.

01:08:08.860 --> 01:08:12.437
I've heard some of the LPD might be going to sea.

01:08:12.437 --> 01:08:14.851
- Yeah, see, I'm going to refer you to IWS 20

01:08:15.050 --> 01:08:18.440
for all the fielding questions on dates

01:08:18.440 --> 01:08:21.440
and when it's coming and at what power level.

01:08:21.460 --> 01:08:22.293
- [Sidney] Okay.

01:08:22.605 --> 01:08:24.220
And the second questions, which is

01:08:24.220 --> 01:08:25.400
more directly to you all then,

01:08:25.759 --> 01:08:29.070
looking at set-based design, which I think I,

01:08:29.070 --> 01:08:32.840
as a (mumbles) major, understand almost 11% of,

01:08:33.530 --> 01:08:37.080
and looking at the EM digital twin,

01:08:37.080 --> 01:08:40.260
which I understand 0% of, these sound

01:08:40.260 --> 01:08:43.230
like very complex models that are federated

01:08:43.230 --> 01:08:45.420
by plugging in multiple models together.

01:08:46.020 --> 01:08:49.250
And we all know the old saying,

01:08:49.250 --> 01:08:50.520
garbage in, garbage out.

01:08:51.280 --> 01:08:53.010
How do you ensure, assuming you're sticking

01:08:53.010 --> 01:08:55.060
models on top of models on top of models,

01:08:55.110 --> 01:08:57.710
that you're not compounding initial errors

01:08:57.710 --> 01:09:01.180
until your final result has nothing to do with reality.

01:09:01.250 --> 01:09:02.659
- Yeah, so that's a great question,

01:09:02.659 --> 01:09:03.800
and actually, Sidney, I think that's a very

01:09:03.800 --> 01:09:05.307
important question.

01:09:05.330 --> 01:09:06.440
There is a good answer to it.

01:09:06.440 --> 01:09:09.040
Because if you're immature in your approach,

01:09:09.040 --> 01:09:11.730
you could end up exactly where you mentioned,

01:09:11.730 --> 01:09:13.080
which is a bad spot, right?

01:09:13.200 --> 01:09:15.560
So, one, there is model validation,

01:09:15.620 --> 01:09:18.290
and first thing is experience and the building

01:09:18.290 --> 01:09:20.520
of the models over time, and the system

01:09:20.520 --> 01:09:22.070
a system of models, right?

01:09:23.107 --> 01:09:27.274
So, and NSWC Carderock has been used

01:09:28.700 --> 01:09:31.990
in ship design and validated for a long time,

01:09:32.100 --> 01:09:34.180
and Mark will ask you to comment on that,

01:09:34.180 --> 01:09:36.040
and then that's wrapped up into RSDE.

01:09:36.040 --> 01:09:39.340
RSDE is really an automated way

01:09:39.340 --> 01:09:42.330
to run multiple runs of a validated model,

01:09:42.430 --> 01:09:44.810
so that's pretty simplistic, but that's

01:09:44.920 --> 01:09:48.740
what gives you that design space, is running

01:09:48.740 --> 01:09:51.720
a validates model multiple times

01:09:53.018 --> 01:09:54.090
and being able to characterize it

01:09:54.090 --> 01:09:55.999
by changing the attributes to go with it.

01:09:55.999 --> 01:09:58.960
- So, that was an excellent question, Sidney,

01:09:58.960 --> 01:10:01.640
and I'll add onto what the admiral said.

01:10:02.210 --> 01:10:04.590
But your premise is exactly right.

01:10:04.950 --> 01:10:08.450
If your model does not accurately reflect reality,

01:10:08.500 --> 01:10:09.940
then the product from that model

01:10:09.940 --> 01:10:11.880
will not be terribly useful,

01:10:12.260 --> 01:10:13.880
and so, the question then is,

01:10:14.580 --> 01:10:16.370
how confident are you that your model

01:10:16.370 --> 01:10:17.580
reflects reality?

01:10:17.800 --> 01:10:21.967
So, when I have my hydrodynamics models

01:10:23.305 --> 01:10:26.388
that are part of RSDE, if you give me

01:10:26.910 --> 01:10:29.680
a hull form that is very similar

01:10:29.680 --> 01:10:32.770
to previous hull forms I've used,

01:10:32.840 --> 01:10:34.710
then my models are excellent.

01:10:35.180 --> 01:10:38.240
If you give me something that's enough different,

01:10:38.470 --> 01:10:40.770
that's why I haven't put the mask

01:10:40.770 --> 01:10:42.910
in the toe tank up in layup yet,

01:10:42.910 --> 01:10:44.340
because we still do that.

01:10:45.110 --> 01:10:48.443
And so, how do you build on new science?

01:10:48.750 --> 01:10:52.900
You don't just immediately believe everything

01:10:53.130 --> 01:10:55.400
that a computer spits out at you.

01:10:55.640 --> 01:10:57.530
So sometimes you will take that

01:10:57.530 --> 01:11:01.697
and then you will bring it to life in 1/50th scale,

01:11:02.810 --> 01:11:05.220
and you'll experiment with that for a while,

01:11:05.220 --> 01:11:07.580
and then you'll bring it to life 1/20th scale,

01:11:07.860 --> 01:11:10.580
and maybe you'll bring it to life in 1/4 scale,

01:11:11.743 --> 01:11:12.710
and you'll continue to take data

01:11:12.710 --> 01:11:15.250
and see how that compares to your original model

01:11:15.380 --> 01:11:17.150
and refine and improve your model,

01:11:17.150 --> 01:11:18.950
and you'll do it in facilities,

01:11:18.950 --> 01:11:20.663
in the case of hydrodynamics, at a place like Carderock,

01:11:20.663 --> 01:11:23.960
that when you're done with that, now you say,

01:11:23.960 --> 01:11:26.930
okay, now my model within this space,

01:11:26.940 --> 01:11:30.400
within what I've validated, now has validity,

01:11:30.400 --> 01:11:32.580
and I can use that for the basis

01:11:32.580 --> 01:11:35.210
of future predictions over and over and over again.

01:11:35.210 --> 01:11:39.210
So, if you told me today, I want to have a model

01:11:40.400 --> 01:11:44.230
that is, and I'm not saying, don't take

01:11:44.230 --> 01:11:45.410
this as a prediction of the future,

01:11:45.410 --> 01:11:47.470
I'll ust use it as a historical example,

01:11:47.560 --> 01:11:49.260
if you wanted me to start modeling

01:11:50.654 --> 01:11:52.445
tumble home hulls, 20 years ago,

01:11:52.445 --> 01:11:53.749
I would have said, I don't understand that,

01:11:53.749 --> 01:11:54.830
I'm gonna have to do a lot of science.

01:11:54.830 --> 01:11:58.520
Now, at the end of the DDG 1000 and the science

01:11:58.520 --> 01:12:00.160
we've done and the investments we make,

01:12:00.160 --> 01:12:02.410
if we start putting tumble home hulls

01:12:02.960 --> 01:12:05.120
together for a future solution,

01:12:05.290 --> 01:12:06.760
I can tell you that my models are really

01:12:06.760 --> 01:12:09.380
good on that and that they will accurately

01:12:09.380 --> 01:12:11.210
predict what that behavior is.

01:12:11.470 --> 01:12:15.050
If we adjust that again to another type of hull that

01:12:15.470 --> 01:12:18.920
maybe is highly...

01:12:21.290 --> 01:12:22.920
Innovative, and I'm thinking now,

01:12:22.920 --> 01:12:24.590
I know I'm at the Surface Warfare,

01:12:24.590 --> 01:12:27.146
I'm at SNA, but in my mind, I have a submarine

01:12:27.146 --> 01:12:30.285
design that was kicking around at Carderock

01:12:30.540 --> 01:12:32.310
where we looked at that and said, wow,

01:12:32.310 --> 01:12:34.264
that's really great, but before we believe the models,

01:12:34.264 --> 01:12:37.540
I think I would want to build up of that

01:12:37.540 --> 01:12:39.480
in order to get the science right

01:12:39.690 --> 01:12:41.070
because it's something that doesn't look

01:12:41.070 --> 01:12:43.110
like any other submarine that's ever been built.

01:12:43.110 --> 01:12:47.277
So, that's where I would say that we use

01:12:47.532 --> 01:12:49.260
what we have to build the science

01:12:49.260 --> 01:12:50.760
so that our model's are right.

01:12:51.120 --> 01:12:53.140
- [Druggan] Okay, thanks, thanks very much.

01:12:53.140 --> 01:12:55.800
Listen, we only have time for one more question, I think,

01:12:55.800 --> 01:12:58.150
unless it's a quick one, so go ahead.

01:12:58.150 --> 01:12:59.650
- Thanks, Admiral.

01:12:59.850 --> 01:13:01.250
I'm Kurt Hamil, retired Navy.

01:13:01.250 --> 01:13:03.770
I work for a information systems company

01:13:03.770 --> 01:13:05.780
from California nowadays.

01:13:08.003 --> 01:13:10.640
Yesterday, General Kaufman and Admiral Boxall

01:13:10.640 --> 01:13:13.500
had an interesting presentation, and one of the

01:13:13.500 --> 01:13:15.150
challenges they presented was about

01:13:15.150 --> 01:13:17.700
information integration, and I asked a question

01:13:17.700 --> 01:13:19.840
about it and they said to ask you guys.

01:13:20.440 --> 01:13:22.760
- Sounds great, so over to us, right?

01:13:22.760 --> 01:13:23.720
- Well, they did--

01:13:23.720 --> 01:13:25.060
- So, I, go ahead.

01:13:25.060 --> 01:13:26.840
- I was gonna say, they did a good job of framing

01:13:26.840 --> 01:13:28.670
up the problem, that is, they showed

01:13:28.670 --> 01:13:32.120
that there's a number of systems that all are stovepiped

01:13:32.120 --> 01:13:34.570
and they all pump out a piece of information

01:13:34.570 --> 01:13:37.810
that the admirals, the generals, the staff officers

01:13:37.810 --> 01:13:40.390
have to stare and compare, have to integrate

01:13:40.400 --> 01:13:42.460
in their own brains, and the goal was that

01:13:42.460 --> 01:13:43.910
integrated combat system.

01:13:44.710 --> 01:13:46.530
So there's a reason why it's stovepipe now,

01:13:46.530 --> 01:13:48.270
it's because there are lots of acquisition

01:13:48.270 --> 01:13:50.190
processes that drive the program manager

01:13:50.190 --> 01:13:51.023
in that direction.

01:13:51.023 --> 01:13:53.610
So my question yesterday, and I just was hoping

01:13:53.610 --> 01:13:55.940
for your insight about it is, how are you

01:13:55.940 --> 01:13:57.810
gonna break that stovepipe paradigm,

01:13:57.810 --> 01:14:00.516
how are you gonna internally give guidance

01:14:00.516 --> 01:14:02.910
to these organizations so that they

01:14:02.910 --> 01:14:05.840
do in fact deliver something that they can integrate,

01:14:05.840 --> 01:14:08.250
something that can bring all of those different

01:14:08.420 --> 01:14:10.710
disparate sets of information, environment,

01:14:10.771 --> 01:14:13.271
EW, even radiological sensors,

01:14:13.455 --> 01:14:16.360
how can all those be brought together

01:14:16.360 --> 01:14:19.770
so that the commander can see it in his visualization

01:14:19.930 --> 01:14:21.530
and not have to brain integrate.

01:14:21.640 --> 01:14:22.540
- Okay, that sounds good.

01:14:22.540 --> 01:14:24.205
I will give it to Dr. Fillinich in a second

01:14:24.205 --> 01:14:25.690
while I have some initial comments,

01:14:25.690 --> 01:14:29.023
and the first one is, which data are you

01:14:29.025 --> 01:14:33.192
trying to access and bring together for what purpose?

01:14:33.220 --> 01:14:35.140
Because we can spend a lot of time,

01:14:35.590 --> 01:14:37.600
a lot of money, and a lot of resources

01:14:37.730 --> 01:14:39.460
trying to bring all data together

01:14:39.460 --> 01:14:41.625
to answer all problems, but we may not end up

01:14:41.625 --> 01:14:43.460
where we think we're going to.

01:14:43.460 --> 01:14:47.627
So, there's certainly the near, you know, probably,

01:14:51.550 --> 01:14:53.620
not real time requirement,

01:14:53.620 --> 01:14:56.750
and that would be fair to take our databases

01:14:56.750 --> 01:14:59.840
that are sure, that have to do with fleet maintenance

01:15:00.000 --> 01:15:02.330
and equipment reliability and availability

01:15:02.330 --> 01:15:05.960
work package, and bring that data together

01:15:06.400 --> 01:15:08.610
so that we can do better planning for future

01:15:08.610 --> 01:15:09.780
availabilities.

01:15:09.900 --> 01:15:13.230
That's completely different from the real time warfighting

01:15:13.230 --> 01:15:15.760
requirement of sharing EW and radar

01:15:15.760 --> 01:15:17.540
data across multiple ships.

01:15:18.900 --> 01:15:22.560
So, we always have to answer that question,

01:15:22.560 --> 01:15:24.920
buyer beware, what questions are we trying

01:15:24.920 --> 01:15:27.420
to answer with the data we want to bring together?

01:15:27.570 --> 01:15:30.150
And it's absolutely important to put some

01:15:30.150 --> 01:15:34.160
intellectual effort behind that so that we

01:15:34.160 --> 01:15:37.570
can get the right data together for,

01:15:37.570 --> 01:15:40.610
and then, the human system interface,

01:15:40.610 --> 01:15:42.880
so it's displayed in a meaningful way

01:15:43.240 --> 01:15:44.350
to the operator.

01:15:44.820 --> 01:15:46.370
So, those are a couple questions.

01:15:46.370 --> 01:15:50.537
Certainly, I think, right now one of our goals

01:15:50.880 --> 01:15:54.530
is to bring ship data together, you know,

01:15:54.530 --> 01:15:56.280
bring multi ship data together.

01:15:56.670 --> 01:15:58.610
So, today we do it kind of at a track level,

01:15:58.610 --> 01:16:01.140
it's a process track level, it's not a lot

01:16:01.140 --> 01:16:03.480
of raw data, there is some raw data

01:16:03.480 --> 01:16:06.953
that's passed on some of the data links.

01:16:06.953 --> 01:16:10.351
So the question is, is the process track data

01:16:10.351 --> 01:16:13.351
sufficient if we just had more of it

01:16:13.460 --> 01:16:16.120
or do we have to actually get into raw data

01:16:16.240 --> 01:16:18.000
and the sharing of raw data?

01:16:18.360 --> 01:16:21.200
And there is good reason to think through

01:16:21.200 --> 01:16:24.460
this problem, certainly as you look at, you know,

01:16:24.460 --> 01:16:27.010
potential adversaries that have more stealthy aircraft,

01:16:27.010 --> 01:16:30.640
UAVs, which are small in terms of radar

01:16:30.640 --> 01:16:31.590
cross section.

01:16:31.630 --> 01:16:35.000
How can we take radar data and EW data

01:16:35.362 --> 01:16:38.362
and other data and fuse it together?

01:16:38.621 --> 01:16:40.640
And maybe where I have a whisper and a whisper

01:16:40.640 --> 01:16:42.170
and a whisper, all of a sudden, I know

01:16:42.170 --> 01:16:44.750
I have a contact and I have a track, right?

01:16:45.690 --> 01:16:48.260
So I think that's important, and there's work

01:16:48.260 --> 01:16:51.040
going on, certainly on the fusing of

01:16:51.040 --> 01:16:55.050
real time tactical data, certainly combining

01:16:55.050 --> 01:16:57.157
the EW and the radar and EW to EW.

01:16:57.157 --> 01:17:00.657
So those are two areas that are happening.

01:17:02.540 --> 01:17:05.010
In the under sea domain, we are definitely

01:17:05.010 --> 01:17:06.800
doing multistatics and bystatics.

01:17:07.400 --> 01:17:11.567
So, that gets at this problem where you have

01:17:11.580 --> 01:17:14.980
multiunits multiships providing services

01:17:14.980 --> 01:17:16.270
and data together.

01:17:16.610 --> 01:17:18.560
we're doing this in the NIFC-CA domain.

01:17:19.410 --> 01:17:21.984
So, NIFC-CA is Navy Integrated Fire Control-Counter Air,

01:17:21.984 --> 01:17:25.363
and that's where a ship can shoot a smart missile,

01:17:25.363 --> 01:17:28.180
an AEGIS baseline 9 ship can shoot a smart missile,

01:17:28.180 --> 01:17:31.340
the SM-6 over the horizon, and conduct

01:17:31.340 --> 01:17:34.110
and air-to-air intercept using third party targeting.

01:17:35.214 --> 01:17:38.830
That's amazing that we can do that, and it's

01:17:38.830 --> 01:17:42.997
done under a quality of service structure,

01:17:43.692 --> 01:17:46.460
which is an open architecture approach

01:17:46.460 --> 01:17:48.930
so that other sensors, future sensors,

01:17:48.930 --> 01:17:51.110
and even additional sensors from today

01:17:51.640 --> 01:17:53.770
can be plugged into that, which is,

01:17:53.770 --> 01:17:55.900
IWS is definitely looking at that

01:17:55.900 --> 01:17:58.220
and doing work in this realm on,

01:17:59.293 --> 01:18:00.600
how do we get more data providers into

01:18:00.600 --> 01:18:02.590
the NIFC-CA network, right?

01:18:02.800 --> 01:18:04.830
The systems are ready to receive it because

01:18:04.830 --> 01:18:07.770
they didn't, they weren't engineered to accept

01:18:07.770 --> 01:18:09.850
only one kind of radar data from one kind

01:18:09.850 --> 01:18:12.580
of platform, they were engineered to take

01:18:12.580 --> 01:18:14.660
radar data from any platform, but then

01:18:14.660 --> 01:18:17.330
evaluate it through a quality of service construct,

01:18:17.490 --> 01:18:20.100
and if it's acceptable, then be able to act upon it.

01:18:20.580 --> 01:18:21.910
That's really smart engineering,

01:18:21.910 --> 01:18:25.300
that's exactly what we have to do going forward.

01:18:25.400 --> 01:18:26.620
But what I always want to start with,

01:18:26.620 --> 01:18:29.758
what problem are we solving, and now that

01:18:29.758 --> 01:18:31.873
we're trying to solve that problem,

01:18:31.873 --> 01:18:34.782
what (audio breaking up) available to solve it,

01:18:34.782 --> 01:18:37.900
and do we need all the data or do we just need

01:18:37.900 --> 01:18:42.030
to curate and take specific data out of what's available?

01:18:42.780 --> 01:18:44.700
For instance, a good one is, after you have

01:18:44.700 --> 01:18:46.820
an EW Sniff and another sensor Sniff

01:18:46.820 --> 01:18:47.930
and you have a radar Sniff,

01:18:47.930 --> 01:18:50.120
but you put them together, you know I have a track.

01:18:50.120 --> 01:18:52.290
If I know I have a track and then

01:18:52.290 --> 01:18:54.030
the radar can take the burden of tracking

01:18:54.030 --> 01:18:57.090
it over time, that's a different construct

01:18:57.090 --> 01:18:58.880
than always bringing all the data together

01:18:58.880 --> 01:19:00.870
and doing fusion data all the time,

01:19:01.890 --> 01:19:03.693
which takes more resources, more link resources

01:19:03.693 --> 01:19:04.693
and whatnot.

01:19:04.816 --> 01:19:07.860
So, once you go to multiship and you start

01:19:07.860 --> 01:19:11.151
getting network effects, tremendous opportunity,

01:19:11.151 --> 01:19:14.901
we have the reality of bandwidth limitations,

01:19:15.370 --> 01:19:17.290
if you will, across several data links.

01:19:17.290 --> 01:19:19.590
So, that's my opening, I'll turn it over

01:19:19.590 --> 01:19:21.044
to Dr. Fillinich here to fill in the holes

01:19:21.044 --> 01:19:24.114
or to correct me in the next 30 seconds.

01:19:24.114 --> 01:19:25.560
(laughing)

01:19:25.560 --> 01:19:27.210
- So, absolutely, it's about the purpose

01:19:27.210 --> 01:19:29.530
of the data, if the human had all the data,

01:19:29.530 --> 01:19:30.980
they would be overwhelmed.

01:19:31.206 --> 01:19:33.220
That being said, the human can

01:19:33.220 --> 01:19:35.880
actually receive a lot of information,

01:19:35.880 --> 01:19:38.660
in fact, our brains are wired to do that very well,

01:19:38.660 --> 01:19:41.040
and actually in some cases, it's very difficult

01:19:41.040 --> 01:19:43.056
for algorithms to perform as well.

01:19:43.056 --> 01:19:45.110
For example, we can very quickly

01:19:45.110 --> 01:19:46.930
distinguish between a cat and a dog,

01:19:46.980 --> 01:19:49.380
but that's actually really difficult artificial

01:19:49.380 --> 01:19:50.740
intelligence problem.

01:19:51.170 --> 01:19:52.987
So, we do need automation at some level,

01:19:52.987 --> 01:19:55.837
but in particular, to help us with predictions,

01:19:55.837 --> 01:19:58.097
what do we think is going to happen in the future.

01:19:58.097 --> 01:19:59.878
And I would say there's also an element of design,

01:19:59.878 --> 01:20:03.055
so how that information and data is being

01:20:03.055 --> 01:20:05.720
presented to the operator with a creative

01:20:05.720 --> 01:20:09.370
design of it is actually an incredibly challenging

01:20:09.370 --> 01:20:11.470
problem because it could have an impact as to

01:20:11.470 --> 01:20:14.400
if the operator notices that information or not.

01:20:14.700 --> 01:20:16.870
And looking forward into the future,

01:20:16.870 --> 01:20:19.190
in order to enable the automation and prediction

01:20:19.190 --> 01:20:21.723
that we want at a systems level, we are

01:20:21.723 --> 01:20:24.620
going to have to be able to make data

01:20:24.620 --> 01:20:26.740
available to the algorithm developers,

01:20:26.750 --> 01:20:27.950
and that's where I think there was

01:20:27.950 --> 01:20:30.080
the previous question about the data

01:20:30.974 --> 01:20:35.141
and the set-based and model-based engineering

01:20:35.696 --> 01:20:38.260
is that we really need to bring these communities

01:20:38.260 --> 01:20:41.470
together, the data, strategy community,

01:20:42.524 --> 01:20:44.240
and the strategists, the modeling and simulation

01:20:44.240 --> 01:20:46.540
community, the training community,

01:20:46.540 --> 01:20:48.380
and the artificial intelligence community

01:20:48.380 --> 01:20:50.980
and all work on that same data,

01:20:51.092 --> 01:20:54.750
and also do so in a way that the human can be able

01:20:54.750 --> 01:20:58.660
to best receive that and optimize the critical

01:20:58.660 --> 01:21:00.620
and limited time that is available

01:21:00.720 --> 01:21:03.080
for understanding the situational awareness,

01:21:03.080 --> 01:21:06.500
the battle space awareness, and decision making.

01:21:06.740 --> 01:21:08.869
- [Druggan] All right, so now to answer your question.

01:21:08.869 --> 01:21:10.199
(laughing)

01:21:10.199 --> 01:21:12.810
So, the near term opportunity for the Navy

01:21:12.810 --> 01:21:15.600
is certainly in the digital solid state systems

01:21:15.730 --> 01:21:17.506
that are open architecture that we are now

01:21:17.506 --> 01:21:21.173
fielding or about to field, so those systems

01:21:21.650 --> 01:21:24.670
include SEWIP block two, SEWIP block three,

01:21:25.040 --> 01:21:26.390
AEGIS Common Source Library,

01:21:26.390 --> 01:21:29.610
Baseline nine and 10, Spy six,

01:21:29.610 --> 01:21:31.930
those are the systems that were developed

01:21:31.930 --> 01:21:34.690
and architected to have some agility

01:21:34.690 --> 01:21:36.930
to take in future capability.

01:21:39.017 --> 01:21:41.680
So, with that, we're getting the hook.

01:21:41.680 --> 01:21:44.170
I greatly appreciate your participation.

01:21:44.170 --> 01:21:46.160
Great questions, really appreciate it.

01:21:46.240 --> 01:21:49.303
Again, thanks to SNA for enabling us to have

01:21:49.303 --> 01:21:52.590
this panel, and thank you, Admiral Pottenger.

01:21:52.590 --> 01:21:54.840
(applause)

01:21:57.600 --> 01:21:59.360
- Based on the size of the audience

01:21:59.360 --> 01:22:00.990
and the number of questions, I'm certain

01:22:00.990 --> 01:22:02.440
you'll all be invited back.

01:22:02.440 --> 01:22:04.580
So, thanks for a really informative session.

01:22:04.580 --> 01:22:07.220
Let's be back in 10 minutes, please.

01:22:07.220 --> 01:22:09.130
We have another first for SNA,

01:22:09.290 --> 01:22:11.200
another great panel coming up, thanks.