WEBVTT

00:00.084 --> 00:02.636
- All right, so hopefully
you had an opportunity

00:02.636 --> 00:06.553
to talk to the exhibitors,
mingle a little bit.

00:07.751 --> 00:10.471
Imagine how all this comes together,

00:10.471 --> 00:12.793
and see the challenge that
we have before us, right?

00:12.793 --> 00:16.630
How do we unlock all
of those opportunities

00:16.630 --> 00:19.198
and being smart about it
and really rippin' apart

00:19.198 --> 00:22.053
our bureaucracy to the
greatest extent that we can?

00:22.053 --> 00:22.886
All right.

00:22.886 --> 00:25.719
So, this is a unique topic for us.

00:30.188 --> 00:31.688
We knew we had a premise

00:31.688 --> 00:35.536
that we could help facilitate this dynamic

00:35.536 --> 00:38.453
in the autonomous vehicle industry.

00:40.011 --> 00:43.844
As I recall going back
to, Eddie may remember,

00:44.939 --> 00:48.628
but it was almost a year and a half ago,

00:48.628 --> 00:52.696
and the day that Uber brought
six autonomous vehicles

00:52.696 --> 00:54.776
from Pittsburgh where there had been,

00:54.776 --> 00:57.348
had an agreement when
they'd been utilizing them

00:57.348 --> 01:00.324
and brought them to
San Francisco and said,

01:00.324 --> 01:02.862
"All right, we're starting
our autonomous vehicle program

01:02.862 --> 01:05.090
"and testing in San Francisco."

01:05.090 --> 01:07.611
Later that day, they
got a cease and desist

01:07.611 --> 01:09.325
from the state.

01:09.325 --> 01:13.028
And then the next day,
the governor of Arizona

01:13.028 --> 01:16.184
tweeted that, "Hey, we
love autonomous vehicles.

01:16.184 --> 01:17.351
"Come on out."

01:18.346 --> 01:20.279
And then that weekend those vehicles

01:20.279 --> 01:21.986
were on their way to Arizona.

01:21.986 --> 01:26.986
And so it really highlighted
this collaborative environment

01:27.191 --> 01:30.084
where the policy could either be a barrier

01:30.084 --> 01:31.722
or be an opportunity.

01:31.722 --> 01:34.268
And so it set us on this
path of really thinking

01:34.268 --> 01:37.385
about autonomous vehicle proving grounds.

01:37.385 --> 01:39.885
And so we crafted this vision.

01:40.840 --> 01:41.963
I keep going back to vision,

01:41.963 --> 01:44.047
but we crafted this
vision where we'd create

01:44.047 --> 01:45.657
an autonomous vehicle proving grounds

01:45.657 --> 01:48.892
here at Miramar that would
facilitate that dynamic,

01:48.892 --> 01:50.100
but not just for us when we

01:50.100 --> 01:51.933
and DOD were trying to develop something,

01:51.933 --> 01:53.419
but more importantly,

01:53.419 --> 01:54.252
from my perspective,

01:54.252 --> 01:56.691
that it would be an
opportunity to industry.

01:56.691 --> 02:00.005
And industry would be
able to collaboratively

02:00.005 --> 02:02.901
get beyond the policy
barriers in some ways

02:02.901 --> 02:05.277
within the State but on our bases,

02:05.277 --> 02:08.944
and we'd be able to ride
that for market forecasting.

02:08.944 --> 02:11.273
And so you're gonna
hear a little bit about

02:11.273 --> 02:13.334
how we crafted that,
how we're utilizing it,

02:13.334 --> 02:15.543
and then how it started the dynamic

02:15.543 --> 02:19.675
for where we've gone, what
you heard from Jay earlier,

02:19.675 --> 02:21.041
and what you'll hear more about,

02:21.041 --> 02:24.853
and where beyond installations it takes us

02:24.853 --> 02:27.486
into the battlefield and for operations.

02:27.486 --> 02:28.319
All right.

02:28.319 --> 02:33.152
So, we've got a great panel
to kind of cover these topics.

02:34.428 --> 02:35.683
On the autonomous vehicle proving ground,

02:35.683 --> 02:37.582
so at the time we were
working with the state,

02:37.582 --> 02:39.676
California Energy Commission,

02:39.676 --> 02:41.899
and we were gonna craft
autonomous shuttles

02:41.899 --> 02:44.810
that were gonna for four
years here on Miramar.

02:44.810 --> 02:47.687
And so I needed to get
leadership so Colonel Dockery

02:47.687 --> 02:48.648
who you heard from earlier,

02:48.648 --> 02:50.469
his predecessor Colonel Woodworth,

02:50.469 --> 02:52.510
I needed to show him
that I wasn't leading him

02:52.510 --> 02:54.051
into the unknown,

02:54.051 --> 02:55.265
into the abyss, right?

02:55.265 --> 02:57.095
Like hey we're gonna
have autonomous shuttles,

02:57.095 --> 02:59.412
and you're accepting all the risk.

02:59.412 --> 03:00.885
And so we worked with

03:00.885 --> 03:04.718
what was formerly the
Army TARDEC vehicle lab,

03:05.621 --> 03:08.500
now Ground Vehicle
Systems Center in Detroit,

03:08.500 --> 03:10.202
because they had done autonomous shuttle

03:10.202 --> 03:12.795
in Fort Bragg in North Carolina.

03:12.795 --> 03:17.622
Moving wounded warriors from
the barracks to the hospital,

03:17.622 --> 03:19.768
and it was taking some of their autonomy

03:19.768 --> 03:22.345
that they had worked on
previously for operations,

03:22.345 --> 03:25.987
putting in a more commercial application.

03:25.987 --> 03:27.815
And I said, "Okay, I need a link to that.

03:27.815 --> 03:29.211
"I need to take all the lessons learned

03:29.211 --> 03:31.436
"that they started there
and bring that over

03:31.436 --> 03:34.246
"and show our leadership
from the Colonel here

03:34.246 --> 03:37.141
"all they way to one
star general at MCI West

03:37.141 --> 03:40.705
"over to General Coglianese
and his predecessor

03:40.705 --> 03:43.024
"up at Marine Corp Installations Command

03:43.024 --> 03:46.031
"that look we can do this
and we can do it smartly."

03:46.031 --> 03:49.562
And so to do that we
brought in Robotic Research,

03:49.562 --> 03:51.792
who you'll hear from Eddie Mottern here

03:51.792 --> 03:53.576
to be our subject matter experts.

03:53.576 --> 03:56.913
And so again, building that ecosystem,

03:56.913 --> 04:00.081
and then fast forward
whenever press got out

04:00.081 --> 04:02.262
that we were working
on this shuttle concept

04:02.262 --> 04:06.000
with the state, Qualcomm
called out of the blue

04:06.000 --> 04:08.467
and said, "Hey, we're right next door.

04:08.467 --> 04:10.159
"We've been dreaming about being able

04:10.159 --> 04:13.947
"to do our testing at the
time going six hours away."

04:13.947 --> 04:17.213
And so I'm trying to tie
these things together.

04:17.213 --> 04:20.406
Part of the premise was
never about just autonomy

04:20.406 --> 04:21.966
on the installation,

04:21.966 --> 04:25.196
it was also about unmanned
logistics systems.

04:25.196 --> 04:29.128
Moving goods which in the last 15 years

04:29.128 --> 04:32.660
has been a highly risky endeavor
for us on the battlefield.

04:32.660 --> 04:36.033
Moving resupplies, how can we expedite

04:36.033 --> 04:37.758
this understanding and the requirements

04:37.758 --> 04:41.937
around moving goods on the
battlefield without drivers

04:41.937 --> 04:43.460
in an unmanned system?

04:43.460 --> 04:46.287
And so Kyle's gonna cover
some of that for us as well.

04:46.287 --> 04:49.954
All right, so with that
we're first gonna go

04:51.430 --> 04:53.263
to Paul from Qualcomm.

04:55.935 --> 04:57.185
How is Qualcomm

05:00.646 --> 05:03.145
structuring itself to shape the future?

05:03.145 --> 05:06.090
And why is this relationship with us

05:06.090 --> 05:08.787
and the collaborative
research development agreement

05:08.787 --> 05:11.879
that we've created with the Navy's help,

05:11.879 --> 05:13.724
helped facilitate that?

05:13.724 --> 05:15.110
- Well, thank you Brandon.

05:15.110 --> 05:17.309
So, Qualcomm has actually benefited a lot

05:17.309 --> 05:21.709
from very strong collaboration
with them at Miramar.

05:21.709 --> 05:24.162
Started with actually drones a while back,

05:24.162 --> 05:27.646
and we moved to the cars
and then to connectivity.

05:27.646 --> 05:30.779
So, Qualcomm's view of the market,

05:30.779 --> 05:32.956
the autonomous car market,

05:32.956 --> 05:36.623
is one of several
opportunities that we see.

05:37.458 --> 05:42.413
Obviously, we have a lot of
core expertise in system on chip

05:42.413 --> 05:47.413
so looking at cost-optimized
SoCs for autonomous vehicles

05:47.838 --> 05:49.131
is a focus for us,

05:49.131 --> 05:52.525
but we see all these new features

05:52.525 --> 05:55.552
that can be added for
starting with Level Three

05:55.552 --> 05:57.813
moving on to Level Four, Five

05:57.813 --> 06:00.568
that also includes the infrastructure.

06:00.568 --> 06:05.157
And connectivity is obviously
a core competency of Qualcomm

06:05.157 --> 06:07.153
and that's where we have also

06:07.153 --> 06:09.459
the connectivity program going on.

06:09.459 --> 06:12.073
So we've actually
benefited from two programs

06:12.073 --> 06:15.351
that are somewhat independent
today but will converge.

06:15.351 --> 06:18.079
One is the autonomous vehicle platform,

06:18.079 --> 06:20.851
and you've seen that
out in the parking lot,

06:20.851 --> 06:24.319
which is really looking
at a whole software stack

06:24.319 --> 06:28.274
for autonomous vehicles
with a lot of features,

06:28.274 --> 06:31.254
and starting at fairly simple features

06:31.254 --> 06:33.671
of precision lane positioning

06:35.479 --> 06:38.729
to traffic jam aided feature and so on.

06:40.151 --> 06:43.051
And then we have the second program,

06:43.051 --> 06:46.733
which is called Cellular Vehicle-To-X,

06:46.733 --> 06:48.588
and vehicle-to-x is vehicle-to-vehicle,

06:48.588 --> 06:53.051
vehicle-to-infrastructure,
and vehicle-to-pedestrian.

06:53.051 --> 06:56.561
And that's really a big focus on safety,

06:56.561 --> 06:59.276
safety of both the vehicle
but also pedestrian

06:59.276 --> 07:02.149
with all the high rate of fatalities.

07:02.149 --> 07:05.797
So those two programs,
technology development efforts

07:05.797 --> 07:08.501
will converge at some point,
but they're very separate

07:08.501 --> 07:11.063
and we've benefited from
these two project teams

07:11.063 --> 07:14.392
here at Miramar out on Rifle Road,

07:14.392 --> 07:18.175
running a lot of tests
and development efforts,

07:18.175 --> 07:20.877
and we've had the benefit

07:20.877 --> 07:23.878
to bring on different obstacles to test

07:23.878 --> 07:26.597
at some of the lower speeds.

07:26.597 --> 07:31.014
As you can imagine, things
like lane cut-in, cut-out,

07:32.055 --> 07:33.681
taking that on to the open road

07:33.681 --> 07:36.606
as a big consideration for safety.

07:36.606 --> 07:40.007
So being able to do some of
that testing here at Miramar,

07:40.007 --> 07:41.755
we've learned a lot.

07:41.755 --> 07:45.873
It's shaped the integration
of the Qualcomm solution,

07:45.873 --> 07:47.326
the validation,

07:47.326 --> 07:52.326
and so the Miramar phase of
testing is actually very key

07:52.344 --> 07:56.143
to the overall development
that goes on at Qualcomm,

07:56.143 --> 07:58.098
so we're very appreciative of all the work

07:58.098 --> 08:00.370
that Lieutenant Colonel Newell has done

08:00.370 --> 08:03.287
and then Miramar has offered to us.

08:05.304 --> 08:06.137
- Thanks, Paul.

08:06.137 --> 08:07.805
So, I mean, wanna highlight
a couple of things

08:07.805 --> 08:12.222
that Paul touched on which
is we aren't their market.

08:13.515 --> 08:15.253
The autonomous vehicle
market that they're after

08:15.253 --> 08:18.420
the OEMs of shaping the auto industry,

08:19.526 --> 08:21.455
that's not focused on defense.

08:21.455 --> 08:24.149
We essentially are
riding that relationship

08:24.149 --> 08:27.468
to better understand what
that market looks like

08:27.468 --> 08:30.155
and that's why the big takeaway for us

08:30.155 --> 08:31.850
and the big in-kind support through

08:31.850 --> 08:34.756
this collaborative research
agreement with them

08:34.756 --> 08:37.369
is that market forecasting
and the design thing.

08:37.369 --> 08:40.169
Typically, those are used
for intellectual property

08:40.169 --> 08:44.273
whenever the government's
partnering with industry,

08:44.273 --> 08:46.568
but we stripped the IP out of this

08:46.568 --> 08:48.514
out of this CRADA

08:48.514 --> 08:50.798
because it wasn't about
their intellectual property.

08:50.798 --> 08:54.471
It was about better understanding
where the market's going

08:54.471 --> 08:57.300
because we are no longer
the market we once were

08:57.300 --> 09:00.997
in that post-World War II environment

09:00.997 --> 09:03.488
where we stood up all of these DOD labs.

09:03.488 --> 09:05.186
And so we have to find new creative ways

09:05.186 --> 09:07.649
to better understand where
that market's heading.

09:07.649 --> 09:11.805
So, with that I wanted
to bring in Eddie Mottern

09:11.805 --> 09:14.476
who kind of bridges for
us both the expertise

09:14.476 --> 09:15.766
but also the commercial market

09:15.766 --> 09:18.543
and the defense market with autonomy.

09:18.543 --> 09:19.376
Eddie?

09:21.501 --> 09:22.334
- I think this is

09:22.334 --> 09:25.363
(speaks away from microphone)

09:25.363 --> 09:26.713
Shuts on and off.

09:26.713 --> 09:28.535
(microphone clicks off)

09:28.535 --> 09:30.173
(speaks inaudibly into microphone)

09:30.173 --> 09:31.560
(microphone clicks on)

09:31.560 --> 09:32.977
(taps on microphone)

09:32.977 --> 09:33.810
There we go.

09:33.810 --> 09:35.627
It looks like I've got this thing working.

09:35.627 --> 09:36.567
I can do autonomous robots,

09:36.567 --> 09:39.912
but apparently I can't
operate a microphone.

09:39.912 --> 09:44.079
So, my story's a little
bit different than Paul's.

09:45.097 --> 09:49.530
Back then, it was Major
Newell who contacted me

09:49.530 --> 09:53.016
about providing engineering support

09:53.016 --> 09:55.639
or an owner's engineering role at Miramar.

09:55.639 --> 09:57.691
And what he was looking for was somebody

09:57.691 --> 10:00.781
to be able to look at a lot
of the technology that exists

10:00.781 --> 10:02.304
and make some sense out of it.

10:02.304 --> 10:05.317
Kind of not necessarily dumb it down,

10:05.317 --> 10:08.336
but put it in terms that
people that aren't familiar

10:08.336 --> 10:11.298
with autonomy can digest and understand.

10:11.298 --> 10:15.108
To give you a little bit
about why he selected us,

10:15.108 --> 10:18.545
we've been doing autonomy
since the late '80s.

10:18.545 --> 10:21.227
No one has heard of us
until very recently,

10:21.227 --> 10:23.523
and that's because most
of the work was done

10:23.523 --> 10:25.771
while our founder was at NIST,

10:25.771 --> 10:28.266
and after that most of it was done

10:28.266 --> 10:31.081
when robotic research
was started back in 2002,

10:31.081 --> 10:33.520
by supporting large defense contractors,

10:33.520 --> 10:36.937
your Lockheeds and your GDs of the world.

10:38.157 --> 10:42.519
So to give you a perspective
of how a lot of this started,

10:42.519 --> 10:46.269
we were doing autonomous
mobility before GPS,

10:48.107 --> 10:49.378
before there was LIDAR.

10:49.378 --> 10:51.115
We actually worked on
the first LIDAR systems

10:51.115 --> 10:54.925
that were available back in
the late '80s, early '90s.

10:54.925 --> 10:58.065
From there we went
through multiple programs.

10:58.065 --> 11:01.065
We've deployed overseas many times.

11:01.065 --> 11:03.938
Again, a lot of this
in the military space.

11:03.938 --> 11:07.360
You name the vehicle
in the military space,

11:07.360 --> 11:10.028
we've put autonomy on it.

11:10.028 --> 11:11.182
There's always gonna be a need

11:11.182 --> 11:13.520
for these vehicles to
operate in installations

11:13.520 --> 11:16.639
whether you're CONUS, or
whether you're OCONUS.

11:16.639 --> 11:20.338
Operating around the FOB
and even further out.

11:20.338 --> 11:22.407
So, in order to do that,
we had to characterize

11:22.407 --> 11:25.203
how these vehicles operate around people

11:25.203 --> 11:26.936
because that's one thing
that we hadn't taken

11:26.936 --> 11:27.845
into consideration.

11:27.845 --> 11:30.512
A lot of our OCONUS deployments,

11:32.309 --> 11:34.712
people in the environment
weren't necessarily something

11:34.712 --> 11:38.314
that we needed to worry
about for obvious reasons.

11:38.314 --> 11:40.623
But, back at the FOB, you have to worry

11:40.623 --> 11:43.157
about all your buddies,
about all your friendlies.

11:43.157 --> 11:46.907
So, we took this Fort
Bragg challenge, ARIBO,

11:48.481 --> 11:50.623
and what we did was we took
a lot of the lessons learned

11:50.623 --> 11:52.209
over the years from technologies,

11:52.209 --> 11:54.902
especially autonomous
mobility, LIDAR processing,

11:54.902 --> 11:56.406
vehicle actuation,

11:56.406 --> 12:01.406
and came up with a pretty
quick, dirty, cheap program

12:01.541 --> 12:03.372
that was gonna transport wounded warriors

12:03.372 --> 12:06.305
from the Wounded Warrior
Transition Battalion

12:06.305 --> 12:09.170
to the Womack Medical Center.

12:09.170 --> 12:11.567
And what we noticed was
the ridership went up

12:11.567 --> 12:12.513
after we did this.

12:12.513 --> 12:15.342
There were a lot of people
that were mobility impaired.

12:15.342 --> 12:19.346
They didn't have access to
actually get to the hospital.

12:19.346 --> 12:23.512
One of the biggest
issues a lot them had TBI

12:23.512 --> 12:24.458
and other issues.

12:24.458 --> 12:26.265
They were forgetting that
they had appointments.

12:26.265 --> 12:28.287
So, we developed an app,

12:28.287 --> 12:30.428
kind of like an on-demand type app,

12:30.428 --> 12:32.366
that would do all the
scheduling with the vehicles,

12:32.366 --> 12:34.773
but also act as a
reminder to let them know

12:34.773 --> 12:35.771
when they had appointments,

12:35.771 --> 12:39.153
where they had to be to
get picked up and so forth.

12:39.153 --> 12:41.873
So that started our look
into the commercial world.

12:41.873 --> 12:45.001
We were like wow, if we can
do this on a military base,

12:45.001 --> 12:48.095
maybe we can do this in the outside world.

12:48.095 --> 12:50.564
And right as that was happening,

12:50.564 --> 12:53.606
is when I met Lieutenant Colonel Newell.

12:53.606 --> 12:55.819
And he's like, "Hey,
I want to do something

12:55.819 --> 12:57.358
"similar to what you did at Bragg,

12:57.358 --> 12:58.955
"but more encompassing.

12:58.955 --> 13:00.324
"I want to bring a bunch of people in.

13:00.324 --> 13:02.300
"I want to bring industry in.

13:02.300 --> 13:05.088
"I want to bring local government in

13:05.088 --> 13:07.091
"and see if we can't
develop a testing ground

13:07.091 --> 13:09.611
"that facilitates all the technology

13:09.611 --> 13:10.873
"that you've been working on,

13:10.873 --> 13:12.587
"but getting it out there to everyone.

13:12.587 --> 13:13.741
"I don't want to help just the Army.

13:13.741 --> 13:14.789
"I want to help the Marines.

13:14.789 --> 13:15.622
"I want to help the Navy.

13:15.622 --> 13:17.763
"I want all of this to grow,

13:17.763 --> 13:20.159
"so that everyone can benefit from it."

13:20.159 --> 13:22.117
In the long run, it's
also bringing costs down,

13:22.117 --> 13:24.174
because that's one of the big challenges

13:24.174 --> 13:26.412
when it comes to autonomous mobility

13:26.412 --> 13:29.575
because I'm not gonna
sit here in front of you

13:29.575 --> 13:31.003
and tell you it's cheap

13:31.003 --> 13:32.789
and if people tell you
they have a cheap solution

13:32.789 --> 13:37.189
that does it all at this point
in time they're lying to you.

13:37.189 --> 13:40.984
But, as far as where
we've gone since then,

13:40.984 --> 13:42.952
I think Brandon and I've
traveled a lot of places,

13:42.952 --> 13:44.518
looked at a lot of systems,

13:44.518 --> 13:48.081
and what he's done here is
nothing short of amazing.

13:48.081 --> 13:49.344
The amount of people and industry

13:49.344 --> 13:51.335
that he's been able to bring to Miramar

13:51.335 --> 13:54.846
and participate in this is
more than anything I've seen

13:54.846 --> 13:55.963
in any other place.

13:55.963 --> 13:58.807
All the test centers across the US

13:58.807 --> 14:03.306
that were stood up initially
with state and federal funding,

14:03.306 --> 14:06.530
they're not doing the level of testing

14:06.530 --> 14:08.179
that's happening here
and the level of testing

14:08.179 --> 14:09.999
that will happen here.

14:09.999 --> 14:13.127
Another thing that Brandon
mentioned was logistics.

14:13.127 --> 14:15.161
That's something as a company

14:15.161 --> 14:20.161
that we've been working on
heavily for the past five years.

14:20.456 --> 14:22.967
We're also looking at doing some things

14:22.967 --> 14:25.634
with Local Motors in that arena.

14:26.767 --> 14:30.166
We basically do the autonomy for the PLS,

14:30.166 --> 14:33.916
which is the Army's
large logistics platform.

14:36.245 --> 14:37.425
That's been moving very well,

14:37.425 --> 14:39.489
and we're looking forward with that

14:39.489 --> 14:40.960
but it looks like we
may get an opportunity

14:40.960 --> 14:44.476
to actually bring this to the
Marines here very shortly.

14:44.476 --> 14:46.332
I find that rather interesting.

14:46.332 --> 14:49.974
- Yeah, so one connector
there is that we work

14:49.974 --> 14:52.816
with Office of Secretary of
Defense for Operational Energy

14:52.816 --> 14:56.233
on this idea of autonomous
unmanned logistics systems

14:56.233 --> 14:57.566
on the battlefield.

14:57.566 --> 14:59.589
And so they actually gave us the funding

14:59.589 --> 15:02.512
to bring Robotic Research
on as owner engineer

15:02.512 --> 15:04.426
in this effort.

15:04.426 --> 15:06.549
One of the ways besides what we did here

15:06.549 --> 15:10.133
is that we actually supported
Major Holloway's office

15:10.133 --> 15:12.341
a year ago out in 29 Palms

15:12.341 --> 15:14.751
when they were looking at
unmanned logistics systems,

15:14.751 --> 15:17.145
and the Nikola Reckless
that you saw outside

15:17.145 --> 15:18.934
was getting tested there.

15:18.934 --> 15:20.885
And we brought in Robotic Research

15:20.885 --> 15:24.503
to come and evaluate the system
as an autonomous platform

15:24.503 --> 15:26.561
for an autonomy applique kit

15:26.561 --> 15:28.632
in this mindset of we know electric,

15:28.632 --> 15:31.753
we know drive-by-wire is
some of the critical enablers

15:31.753 --> 15:34.076
to autonomy and so we wanted,

15:34.076 --> 15:36.162
even though they weren't
lookin' at autonomy

15:36.162 --> 15:39.174
or remote control at the time,
we wanted to start looking

15:39.174 --> 15:40.646
at platforms that would be ready,

15:40.646 --> 15:42.436
right for that opportunity.

15:42.436 --> 15:44.661
And so here I want to turn
it over to Major Holloway

15:44.661 --> 15:46.471
to talk about unmanned logistics systems

15:46.471 --> 15:50.081
for the Marine Corps and what
that means on the battlefield.

15:50.081 --> 15:50.928
- Thank you, sir.

15:50.928 --> 15:53.616
As Lieutenant Colonel Newell alluded to,

15:53.616 --> 15:56.813
we both kind of work for
two halves of the INL team.

15:56.813 --> 15:58.444
He's on the installations side.

15:58.444 --> 15:59.964
I work for LP,

15:59.964 --> 16:00.797
Logistics Plans Policies
and Strategic Mobility,

16:00.797 --> 16:02.047
General Maxwell

16:03.453 --> 16:06.575
underneath Lieutenant
General Chiarotti's the DC.

16:06.575 --> 16:10.363
And our focus is inherently
on the operational side.

16:10.363 --> 16:12.866
Over the past couple of
years we've been able

16:12.866 --> 16:16.270
to kind of leverage each other's efforts

16:16.270 --> 16:20.576
to create synergy and reduce
redundancies in the INL efforts

16:20.576 --> 16:21.493
as a whole.

16:22.549 --> 16:24.132
As Eddie alluded to

16:25.628 --> 16:27.048
we've had a relationship

16:27.048 --> 16:30.266
with TARDEC in their Expedient
Leader Follower Program,

16:30.266 --> 16:32.764
which is what he talked
about with the autonomy

16:32.764 --> 16:34.681
on the Army PLS trucks.

16:35.750 --> 16:37.414
Kind of a history of that program

16:37.414 --> 16:42.073
is a JCTD, Joint Capabilities
Technology Demonstration,

16:42.073 --> 16:44.442
that the Marine Corps
and the Army went into

16:44.442 --> 16:49.129
in 2012 and the Army continued
after it expired in 2015

16:49.129 --> 16:52.245
to now be the semi-autonomous

16:52.245 --> 16:57.225
Expedient Leader Follower
capability on their PLS trucks.

16:57.225 --> 17:01.536
The Marine Corps has
monitored the program,

17:01.536 --> 17:04.926
and hopefully in the near
future we're gonna be able

17:04.926 --> 17:06.712
to get some LVS trucks,

17:06.712 --> 17:09.639
which are very similar to
the Army's PLS platforms,

17:09.639 --> 17:12.279
into the pipeline to get the applique kit

17:12.279 --> 17:14.896
of the Expedient Leader Follower,

17:14.896 --> 17:19.183
and start getting back into
the autonomous vehicle program

17:19.183 --> 17:23.635
in a way that we were kind
of in the previous decade.

17:23.635 --> 17:26.628
A couple of other things that
Lieutenant Colonel Newell

17:26.628 --> 17:31.542
and I have worked on is
lookin' at things that work

17:31.542 --> 17:35.500
both on the installations
as well as forward deployed.

17:35.500 --> 17:38.975
So, we already discussed and I think

17:38.975 --> 17:42.116
Jay will talk about the
crowd-sourcing collab effort

17:42.116 --> 17:44.284
that will have a flavor of autonomy

17:44.284 --> 17:47.813
when we move forward
but Brandon was integral

17:47.813 --> 17:51.195
in assisting with all of
the crowd-sourcing efforts

17:51.195 --> 17:52.468
as well as the digital thread,

17:52.468 --> 17:55.448
providing the autonomous
vehicle proving ground here

17:55.448 --> 17:58.615
as a venue for that continued success.

18:02.879 --> 18:05.103
There was one other thing
I wanted to discuss.

18:05.103 --> 18:08.296
Oh, so, to kind of talk
about Robotics Research

18:08.296 --> 18:11.338
a little bit more and the
work that they're able to do

18:11.338 --> 18:13.260
in both the commercial, consumer space

18:13.260 --> 18:15.927
as well as the military space is

18:17.580 --> 18:20.129
the Marine Corps War Fighting Labs effort,

18:20.129 --> 18:23.845
the EMAV, or the Expedient
Modular Autonomous Vehicle,

18:23.845 --> 18:25.807
which is an SNT platform

18:25.807 --> 18:27.948
that the Marine Corps is invested in.

18:27.948 --> 18:30.418
We currently have two, we're
going up to 10 vehicles

18:30.418 --> 18:32.970
to do experimentation
in all realms of support

18:32.970 --> 18:35.575
to the MAGTF to include logistics

18:35.575 --> 18:39.060
and the Robotics Research
team's gonna provide autonomy

18:39.060 --> 18:41.310
hopefully for those future platforms.

18:41.310 --> 18:45.810
So Robotics Research has
been part of the Marine Corps

18:47.236 --> 18:48.365
part of the Marine Corps autonomy story

18:48.365 --> 18:52.227
for as long as we've
been looking at autonomy,

18:52.227 --> 18:55.421
so I'm glad to see that he's on the panel,

18:55.421 --> 18:59.004
and hopefully we'll be
able to use the EMAV

19:00.260 --> 19:04.748
movin' forward on the
autonomous vehicle platform.

19:04.748 --> 19:08.001
- All right, so we're showin'
you both sides of this,

19:08.001 --> 19:09.872
both the commercial applications

19:09.872 --> 19:12.985
and the operational applications.

19:12.985 --> 19:15.946
So, I want to tie that
together a little bit more

19:15.946 --> 19:17.993
with what Jay talked about earlier

19:17.993 --> 19:22.073
with on Joint Base Myer-Henderson
Hall in northern Virginia.

19:22.073 --> 19:26.188
And, so, I mentioned earlier
that we brought in the Army

19:26.188 --> 19:28.720
to collaborate with us on that project.

19:28.720 --> 19:31.290
And what the Army lab
that's involved, ERDC,

19:31.290 --> 19:35.704
is actually doing, is
they're running shadowing.

19:35.704 --> 19:39.022
They're shadowing the
operation and the setup

19:39.022 --> 19:42.160
of the system as industry leads it.

19:42.160 --> 19:44.960
So, between Robotic Research's autonomy

19:44.960 --> 19:48.180
and Local Motors' platform and operation,

19:48.180 --> 19:53.180
and even the infotainment side
I call it of the platform,

19:53.323 --> 19:54.848
and then that has implications back

19:54.848 --> 19:55.910
to our other installations

19:55.910 --> 20:00.910
and how we craft these
requirements and resource to it.

20:01.020 --> 20:04.580
The Army has plans at Fort
Carson in Colorado Springs,

20:04.580 --> 20:07.676
and then we have plans here
and other places as well.

20:07.676 --> 20:10.115
And so it's integral
to how we move forward

20:10.115 --> 20:12.086
when it's an emerging technology

20:12.086 --> 20:13.829
that we don't fully understand

20:13.829 --> 20:15.806
and the operation that
we don't understand.

20:15.806 --> 20:18.377
So I'm gonna tee-up Jay to talk more

20:18.377 --> 20:21.931
about kind of this dialogue
that's continuing forward

20:21.931 --> 20:25.014
and how you see it all come together.

20:27.671 --> 20:32.172
- So, I think for us
looking at these devices,

20:32.172 --> 20:35.316
these are a lot of discussion has gone on

20:35.316 --> 20:38.152
in the last decade about
the Internet of things,

20:38.152 --> 20:41.752
and these are industrial
Internet of things devices.

20:41.752 --> 20:44.669
And they have all of the attributes

20:45.576 --> 20:47.051
that are currently being discussed,

20:47.051 --> 20:49.843
and they have the potential
of so many more attributes

20:49.843 --> 20:51.632
coming forward quickly.

20:51.632 --> 20:53.815
So, we have really been inspired

20:53.815 --> 20:55.986
by the crowd-sourcing
efforts that are out there

20:55.986 --> 20:57.791
the work that we've
done in collab together

20:57.791 --> 21:01.194
to be able to uncover use cases.

21:01.194 --> 21:04.072
It's surprising even to
me running a co-creative

21:04.072 --> 21:06.246
and digital manufacturing business

21:06.246 --> 21:08.633
how specific the use cases can be.

21:08.633 --> 21:11.138
And, so, we spend a lot
of time talking right now

21:11.138 --> 21:14.456
about autonomy, but there
is actually how productive

21:14.456 --> 21:17.689
you can make a user, a
Marine, a serviceman,

21:17.689 --> 21:20.261
in this vehicle and that has a lot more

21:20.261 --> 21:22.490
than just autonomy associated with it.

21:22.490 --> 21:24.729
The connectivity that's
out there in the use case

21:24.729 --> 21:26.493
of the vehicle when you think about it,

21:26.493 --> 21:28.707
I'll use an example of Joint Base Myer,

21:28.707 --> 21:31.074
if you're taking a
disabled veteran around,

21:31.074 --> 21:33.069
and you want them to be able to know

21:33.069 --> 21:36.003
where the headstone is of
somebody they served with,

21:36.003 --> 21:37.529
that has nothing to do with autonomy,

21:37.529 --> 21:38.578
that has everything to do

21:38.578 --> 21:40.364
with what you're
processing on the vehicle.

21:40.364 --> 21:43.532
And so to be able to record their stories

21:43.532 --> 21:45.907
as you're doing that would be a use case

21:45.907 --> 21:48.327
that could really make
these vehicles come alive.

21:48.327 --> 21:50.357
To be able to point out
all of the other headstones

21:50.357 --> 21:52.400
of the people that may have
served in that same unit,

21:52.400 --> 21:53.948
and where they might be in Arlington,

21:53.948 --> 21:57.976
is an example of how you
make that veteran's time

21:57.976 --> 22:00.820
more valuable and
productive in their vehicle.

22:00.820 --> 22:03.939
We spend a lot of time now
thinking about the fact

22:03.939 --> 22:07.277
that it is no longer taking
a driver out of a car

22:07.277 --> 22:10.560
and putting a car to go
someplace without the driver,

22:10.560 --> 22:13.237
but rather what else could
you do during that time

22:13.237 --> 22:14.869
if you're no longer driving.

22:14.869 --> 22:17.665
And shared mobility was
kicked into high gear

22:17.665 --> 22:19.310
with Uber and Lyft.

22:19.310 --> 22:22.201
These will be the most
valuable IPOs in the history

22:22.201 --> 22:24.255
of IPOs this year.

22:24.255 --> 22:25.640
But, what does that mean?

22:25.640 --> 22:27.348
Today, in an Uber and a Lyft, you sit

22:27.348 --> 22:28.503
in the back of a vehicle,

22:28.503 --> 22:30.337
and you drive from one place to the next.

22:30.337 --> 22:33.300
But if the vehicles were
different, what else could you do?

22:33.300 --> 22:37.070
So, we see that for bases and
stations and civilian uses

22:37.070 --> 22:40.947
so much and Eddie's pointed
out we got to do in business,

22:40.947 --> 22:43.439
the third autonomy provider
that we've worked with

22:43.439 --> 22:46.579
in the process of Olli
was Robotic Research.

22:46.579 --> 22:48.107
And one of the reasons
why we wanted to work

22:48.107 --> 22:50.421
with Robotic Research was not just

22:50.421 --> 22:53.102
because they provided a very
credible autonomous system,

22:53.102 --> 22:55.305
but they were willing to work beyond that

22:55.305 --> 22:56.594
in what else you need to do

22:56.594 --> 22:58.582
in the connected Internet of things device

22:58.582 --> 23:00.410
to be able to make it really useful.

23:00.410 --> 23:02.472
And we've only just begun to play in that.

23:02.472 --> 23:04.806
I would say that we're in
the first of nine innings,

23:04.806 --> 23:07.036
and by the time these vehicles really come

23:07.036 --> 23:09.824
into their capability people are gonna see

23:09.824 --> 23:11.869
that it is the whole connected ecosystem,

23:11.869 --> 23:15.516
and we've seen a bunch of
wireless providers here today.

23:15.516 --> 23:17.525
And that also is important to note.

23:17.525 --> 23:19.182
That handling of data

23:19.182 --> 23:21.458
and both the secure transmission of data,

23:21.458 --> 23:22.807
and then the usage of data,

23:22.807 --> 23:24.778
and then the secure
transmission back to the vehicle

23:24.778 --> 23:26.208
to make it more productive.

23:26.208 --> 23:29.098
The first time I saw a 4K TV installation

23:29.098 --> 23:31.661
in the vehicle, with live, real translate

23:31.661 --> 23:33.371
and the ability for it to operate

23:33.371 --> 23:36.312
in the full spectrum
of 5G, I was blown away

23:36.312 --> 23:38.842
by what that would mean for
productivity in the vehicle.

23:38.842 --> 23:41.079
And so for professional
military education,

23:41.079 --> 23:46.079
for TDPs, for the ability to
be able to give instructions

23:46.172 --> 23:51.172
for safety, for security, for
simply enjoyment of your time,

23:51.643 --> 23:53.241
and those sorts of things,

23:53.241 --> 23:55.333
it's gonna be an amazing
new world for mobility,

23:55.333 --> 23:58.311
and that's what we're excited to see.

23:58.311 --> 23:59.282
- That's great, Jay.

23:59.282 --> 24:02.299
So, one of the most important
things that we learned

24:02.299 --> 24:03.871
early on about autonomous vehicles

24:03.871 --> 24:05.790
is that there's autonomous vehicles,

24:05.790 --> 24:07.404
and then there's connected vehicles.

24:07.404 --> 24:09.463
You know autonomous
vehicles is the brains,

24:09.463 --> 24:12.657
the eyes, the sensing is all on-board,

24:12.657 --> 24:14.976
all the processing's on-board.

24:14.976 --> 24:18.248
It's like what you see with Tesla today.

24:18.248 --> 24:20.370
The real leap forward in capability

24:20.370 --> 24:23.528
that really goes beyond
my ability cognitively

24:23.528 --> 24:27.882
in my eyesight as I drive
is the connected vehicle.

24:27.882 --> 24:29.665
The connected vehicle communicates

24:29.665 --> 24:31.878
to other vehicles, to infrastructure,

24:31.878 --> 24:33.848
to the pedestrian, and their smartphone

24:33.848 --> 24:37.156
walking across the pedestrian walkway.

24:37.156 --> 24:38.910
That's where you have
this great leap forward.

24:38.910 --> 24:43.115
So there's the autonomy
side of that technology

24:43.115 --> 24:46.115
that's integral to the connectivity,

24:47.036 --> 24:49.775
or the connectivity's integral to that,

24:49.775 --> 24:51.834
but with that it comes back to some

24:51.834 --> 24:53.398
of the things that Jay talked about

24:53.398 --> 24:56.694
and what we're excited to
see at the joint base there

24:56.694 --> 25:00.533
in Virginia and the relationship
with Amazon Web Services.

25:00.533 --> 25:03.766
And so the cloud computing,
the cloud services,

25:03.766 --> 25:06.518
even potentially some
computing on the edge, right?

25:06.518 --> 25:08.586
And so when you have that connectivity

25:08.586 --> 25:11.863
that really enables
both sides of the house

25:11.863 --> 25:14.137
of these new emerging capabilities

25:14.137 --> 25:16.407
and so that's to tee-up
Kevin to talk to us

25:16.407 --> 25:18.099
about what's going on with Verizon,

25:18.099 --> 25:21.807
what we're working on
here even at Miramar.

25:21.807 --> 25:25.072
- Well, thanks again for the opportunity.

25:25.072 --> 25:27.405
You know we obviously,

25:27.405 --> 25:29.373
Verizon doesn't make any
kind of autonomous vehicle,

25:29.373 --> 25:31.999
but as I've been listening
to the general speak,

25:31.999 --> 25:34.132
the commander of the base speak,

25:34.132 --> 25:36.256
Brandon speak all day today,

25:36.256 --> 25:40.097
every pain point and
technology that I heard

25:40.097 --> 25:43.923
I could connect to something that will be

25:43.923 --> 25:46.272
a use case or application
that would be enabled

25:46.272 --> 25:49.536
by our next generation 5G network.

25:49.536 --> 25:53.158
So, for example, autonomous vehicles,

25:53.158 --> 25:56.264
if you think about how they work today,

25:56.264 --> 25:58.719
they essentially digitize the world

25:58.719 --> 26:03.559
by using computer vision,
LIDAR technology, 3D LIDAR,

26:03.559 --> 26:07.043
and they digitize the world
the way you and I process

26:07.043 --> 26:08.426
as we are driving.

26:08.426 --> 26:10.768
There's a pedestrian
crossing, yellow light,

26:10.768 --> 26:14.132
red light, stop, take a
right when nobody's crossing.

26:14.132 --> 26:16.300
They essentially have to digitize it

26:16.300 --> 26:19.657
and use business rules
to essentially emulate

26:19.657 --> 26:21.809
what we do as humans.

26:21.809 --> 26:25.642
Now, at the moment, all of
the processing associated

26:25.642 --> 26:29.142
with that digitization of the world occurs

26:30.060 --> 26:35.060
on the vehicle simply because
you cannot afford latency.

26:35.438 --> 26:38.744
In other words, if that
processing was to occur

26:38.744 --> 26:41.327
in a edge cloud on a 4G network

26:43.412 --> 26:46.517
because of the kind of latency
we have in a 4G network,

26:46.517 --> 26:47.847
there's about a 100 milliseconds,

26:47.847 --> 26:51.780
you could have a blind spot
for the autonomous vehicle

26:51.780 --> 26:54.168
and it could hit somebody.

26:54.168 --> 26:56.258
Not because it can't function well,

26:56.258 --> 26:58.069
but because the latency didn't allow it

26:58.069 --> 27:00.285
to understand somebody was crossing.

27:00.285 --> 27:02.983
And so as a result of that
all those technologies run

27:02.983 --> 27:05.380
on board autonomous vehicles.

27:05.380 --> 27:08.531
As you look on the horizon,
we are building data centers

27:08.531 --> 27:09.997
close to the edge of the network

27:09.997 --> 27:12.237
where these vehicles are gonna be located.

27:12.237 --> 27:17.237
They're called the multi-edge
compute node or a MEC, 5G MEC.

27:17.597 --> 27:21.358
And, at that point in time,
a lot of the algorithms

27:21.358 --> 27:24.357
that are running inside
the autonomous vehicle

27:24.357 --> 27:26.750
could actually run in the MEC

27:26.750 --> 27:29.422
and create not only a control mechanism

27:29.422 --> 27:31.239
for the autonomous vehicle

27:31.239 --> 27:34.245
but the ability to do
vehicle-to-infrastructure,

27:34.245 --> 27:37.341
vehicle-to-vehicle,
vehicle-to-traffic signal,

27:37.341 --> 27:40.207
vehicle to other things,
Internet of things.

27:40.207 --> 27:43.189
Connectivity all via one integrated cloud,

27:43.189 --> 27:46.180
which is located at the edge
of the network called a MEC.

27:46.180 --> 27:49.254
And, so, as we look on the horizon,

27:49.254 --> 27:52.340
we see ourselves really a integral part

27:52.340 --> 27:55.616
of everything that has to
do with next generation

27:55.616 --> 27:58.592
of technologies, autonomous
vehicles being one of them.

27:58.592 --> 28:00.035
We think the costs will come down

28:00.035 --> 28:02.157
when a lot of these algorithms can run

28:02.157 --> 28:04.841
in common operating environments like MEC

28:04.841 --> 28:07.046
as opposed to every single vehicle.

28:07.046 --> 28:09.905
The other thing that we
really think will be conducive

28:09.905 --> 28:12.322
in the 5G environment is that

28:13.562 --> 28:14.568
case in point,

28:14.568 --> 28:16.195
take this base,

28:16.195 --> 28:18.461
first of all I should say as I listen

28:18.461 --> 28:20.809
to various people talk on the stage

28:20.809 --> 28:22.366
I'm like I've heard that before,

28:22.366 --> 28:24.886
and most of the problems
that I heard about

28:24.886 --> 28:27.965
lost my mobility, logistical operations

28:27.965 --> 28:32.965
that are more autonomous,
the ability to use your GCSS,

28:33.101 --> 28:35.702
and maybe generate a ticket for some kind

28:35.702 --> 28:39.005
of automated logistics
operation, what have you,

28:39.005 --> 28:41.338
condition-based maintenance.

28:42.206 --> 28:44.786
I hear these kinds of problems
from cities and mayors

28:44.786 --> 28:47.265
all the time because
you guys are essentially

28:47.265 --> 28:49.639
like mini cities in these bases.

28:49.639 --> 28:52.199
You have all of the
similar kind of construct,

28:52.199 --> 28:55.230
parking management
issues, security issues,

28:55.230 --> 28:58.371
lighting issues, and mobility issues,

28:58.371 --> 29:02.141
and so we deal, we have Uber
talking to us all the time

29:02.141 --> 29:07.058
about employing 5G technology
in their autonomous vehicles,

29:08.508 --> 29:09.863
next generation autonomous vehicle.

29:09.863 --> 29:12.776
Ford is a customer of Verizon.

29:12.776 --> 29:16.729
Amazon is talking to us because
in the world of logistics,

29:16.729 --> 29:21.729
what they're contemplating is
having these regional depots

29:22.073 --> 29:26.323
where robots and UAVs can
actually pick up an item,

29:29.175 --> 29:32.305
you know mother has a sick
child, can't go to the store,

29:32.305 --> 29:34.770
needs some kind of a fever reducer,

29:34.770 --> 29:36.863
you don't want a one-day
delivery thing for that.

29:36.863 --> 29:38.786
You want a one-hour delivery.

29:38.786 --> 29:42.367
And the robot can pick that
from the local regional depot

29:42.367 --> 29:43.817
and deliver that to your door.

29:43.817 --> 29:45.826
So, talking about logistical operations

29:45.826 --> 29:48.630
similar to what you guys need
in the military construct.

29:48.630 --> 29:50.774
Now, we obviously with the 5G network,

29:50.774 --> 29:53.419
we can support what
Amazon is contemplating it

29:53.419 --> 29:56.338
within the depots in the
cities around the US.

29:56.338 --> 29:59.804
CONUS because we're gonna
build a robust 5G network

29:59.804 --> 30:01.745
we can't do it in the
forward operating base,

30:01.745 --> 30:04.637
but it makes your operations
here more efficient

30:04.637 --> 30:07.191
in terms of supporting the
forward operating base.

30:07.191 --> 30:10.155
So as we look on the horizon,

30:10.155 --> 30:13.139
no matter what element
you're talking about,

30:13.139 --> 30:15.882
augmented reality for
condition-based maintenance,

30:15.882 --> 30:20.781
autonomous vehicles for
mobility logistics operations,

30:20.781 --> 30:23.457
Verizon's 5G network is gonna
be able to support that,

30:23.457 --> 30:25.572
as a matter of fact that's
the only way you can do it.

30:25.572 --> 30:27.238
The example I was gonna cite is

30:27.238 --> 30:29.500
that if you looked at this base,

30:29.500 --> 30:33.931
we probably can handle about
400, 500, 600 simultaneous call

30:33.931 --> 30:36.288
with 4G LTE densification.

30:36.288 --> 30:38.720
Now as you look on the horizon,

30:38.720 --> 30:40.763
when you add all of these sensors

30:40.763 --> 30:44.310
from autonomous vehicles,
intelligent lighting,

30:44.310 --> 30:46.624
intelligent videos that wanna stream,

30:46.624 --> 30:49.213
computer vision algorithms
that are monitoring

30:49.213 --> 30:52.606
for intersection safety and
other kinds of applications,

30:52.606 --> 30:54.991
smart parking, the number of sensors

30:54.991 --> 30:58.275
and the number of people that
want to talk simultaneously

30:58.275 --> 31:02.144
is gonna be way beyond the
capacity of a 4G LTE network.

31:02.144 --> 31:04.477
And, if you look at the 5G network,

31:04.477 --> 31:09.061
our CEO Hans Vesper talks about
the currency of 5G network.

31:09.061 --> 31:10.980
Obviously one of them is speed,

31:10.980 --> 31:14.082
because 5G is the equivalent
of wireless fiber,

31:14.082 --> 31:17.843
so the speeds that we deliver
on a fiber optic cable,

31:17.843 --> 31:19.937
which is around 10 gigabits per second,

31:19.937 --> 31:21.874
we can deliver on the 5G network,

31:21.874 --> 31:25.481
about one to 10 gigabits
per second wirelessly,

31:25.481 --> 31:27.050
so it's wireless fiber.

31:27.050 --> 31:30.384
But, the more important
aspect of 5G is that

31:30.384 --> 31:33.200
if you looked at a square mile,

31:33.200 --> 31:36.992
we could probably connect
one million devices,

31:36.992 --> 31:39.655
whether it's a light or autonomous vehicle

31:39.655 --> 31:43.105
or people talking to
that same radio system

31:43.105 --> 31:44.254
whereas you cannot do that.

31:44.254 --> 31:47.515
So, as we look on the
horizon for these devices

31:47.515 --> 31:49.233
to be connected to the network

31:49.233 --> 31:51.114
and to talk to the infrastructure

31:51.114 --> 31:54.288
and then use the infrastructure
to talk to each other,

31:54.288 --> 31:56.036
you're gonna need the kind of density

31:56.036 --> 31:57.592
that only 5G can support.

31:57.592 --> 32:01.377
So, as we look on the horizon
there is literally no use case

32:01.377 --> 32:04.554
or application where we
think would be possible

32:04.554 --> 32:08.545
entirely without the
use of the 5G network.

32:08.545 --> 32:09.555
- All right, thank you, Kevin.

32:09.555 --> 32:14.555
So, I thought we were talkin'
about autonomous vehicles.

32:14.833 --> 32:16.543
That was complex enough, right?

32:16.543 --> 32:18.292
And, then now we just showed you

32:18.292 --> 32:21.235
how 5G is gonna be critical to it,

32:21.235 --> 32:23.351
and it's like all right, all right,

32:23.351 --> 32:24.304
I spent all morning talkin'

32:24.304 --> 32:27.413
about our bureaucracy doesn't
change quick enough, right?

32:27.413 --> 32:29.178
Well, so this is what we're doing

32:29.178 --> 32:31.867
with the collaborative market.

32:31.867 --> 32:33.671
We're finalizing right now with Verizon

32:33.671 --> 32:36.225
and Naval Information
Warfare Center, so NIWC,

32:36.225 --> 32:38.683
formerly SPAWAR Pacific,

32:38.683 --> 32:42.850
another CRADA on 5G that
would be here at Miramar.

32:43.728 --> 32:46.329
And that allows us to
collaboratively move forward

32:46.329 --> 32:49.232
and deploy it on the base

32:49.232 --> 32:52.058
and look for the applications,
look for the use cases.

32:52.058 --> 32:53.704
We mentioned the connected vehicle.

32:53.704 --> 32:56.997
I mentioned earlier digital fortress.

32:56.997 --> 32:59.414
Drones, you'll hear more about that later.

32:59.414 --> 33:02.581
Again, having that network is critical

33:03.709 --> 33:05.676
to understanding where this is going

33:05.676 --> 33:08.771
and what we need to
unlock the opportunity.

33:08.771 --> 33:11.877
And, then that ties back to
our crowd-sourcing challenge

33:11.877 --> 33:13.010
that we talked about earlier,

33:13.010 --> 33:15.294
and I had Chris Waaler and Dave Ross,

33:15.294 --> 33:16.373
who couldn't be here today,

33:16.373 --> 33:20.603
but that relationship and
looking at how we drive forward

33:20.603 --> 33:24.993
to telecom as a utility so
that we actually are moving

33:24.993 --> 33:29.757
at the pace of emerging
technology, that's critical.

33:29.757 --> 33:32.765
So, you bring all that together.

33:32.765 --> 33:34.458
I'm gonna come back to Kyle here

33:34.458 --> 33:37.734
because when we first started
looking at autonomous vehicle

33:37.734 --> 33:39.911
and making that leap to a connected,

33:39.911 --> 33:43.291
we heard that 5G and the
connectivity you have

33:43.291 --> 33:47.156
to other devices and
other sensors is critical

33:47.156 --> 33:48.957
to take that next leap.

33:48.957 --> 33:51.720
We've talked about how
we gonna replicate that

33:51.720 --> 33:53.526
on the battlefield?

33:53.526 --> 33:55.556
Are we gonna have to fly a drone an hour

33:55.556 --> 33:59.443
before the vehicle goes out
or is that too much latency

33:59.443 --> 34:01.195
between sensing the environment?

34:01.195 --> 34:02.753
Do I have to fly it realtime?

34:02.753 --> 34:04.626
Am I gonna covertly drop sensors

34:04.626 --> 34:07.227
on the battlefield that
are gonna communicate

34:07.227 --> 34:09.733
back to this vehicle, right?

34:09.733 --> 34:12.283
An area and a location that
we've never gone before.

34:12.283 --> 34:15.409
Or maybe it's retro-traversing
an area we've gone before.

34:15.409 --> 34:19.585
So, any thoughts Kyle on how
the environment we're creating

34:19.585 --> 34:21.954
helps us craft that future?

34:21.954 --> 34:23.613
- Yeah, absolutely, and I
think it's important to note

34:23.613 --> 34:26.304
that the ecosystem that
you're setting up here

34:26.304 --> 34:28.849
with the autonomous vehicle proving ground

34:28.849 --> 34:31.161
is enabling us to leverage
dual-use technology.

34:31.161 --> 34:34.184
So, the installation side
is clearly as it was stated

34:34.184 --> 34:37.059
like a small town or city or community,

34:37.059 --> 34:40.358
where a lot of the stuff
that you're investigating

34:40.358 --> 34:42.103
may not have direct application

34:42.103 --> 34:44.632
to an operational environment,

34:44.632 --> 34:47.302
but it's something that

34:47.302 --> 34:50.619
with a couple of tweaks
can be operationalized.

34:50.619 --> 34:53.476
So, I think that maybe Paul
and Eddie can weigh in as well

34:53.476 --> 34:55.318
about the network,

34:55.318 --> 34:56.901
and you as a communicator probably

34:56.901 --> 34:58.586
could speak to it better than I could,

34:58.586 --> 35:01.669
but the stuff that Qualcomm addressed

35:04.112 --> 35:07.855
in regards to being tied
in with the infrastructure

35:07.855 --> 35:10.124
is not gonna be possible when you're

35:10.124 --> 35:11.779
in a forward deployed environment.

35:11.779 --> 35:13.731
So, having a network on the move

35:13.731 --> 35:16.318
that's capable of processing
all that data real-time

35:16.318 --> 35:18.728
with localized sensors and isn't relying

35:18.728 --> 35:22.728
on a GPS signal or
pre-loaded maps like you have

35:24.617 --> 35:27.409
in the legacy Blueport Tracker
system is gonna be key.

35:27.409 --> 35:31.027
So, leveraging a 5G network
on the move is gonna be

35:31.027 --> 35:34.117
absolutely necessary for a connected

35:34.117 --> 35:36.206
and autonomous vehicle
when you start goin'

35:36.206 --> 35:38.142
outside the wire.

35:38.142 --> 35:40.104
- And, it's a great point.

35:40.104 --> 35:41.766
Let me just kind of clarify.

35:41.766 --> 35:44.436
In a non-permissible environment,

35:44.436 --> 35:46.615
in all likelihood all of

35:46.615 --> 35:48.747
in a forward operating situation,

35:48.747 --> 35:51.373
where the environment's non-permissible,

35:51.373 --> 35:53.947
it would probably be
different if I'm talking

35:53.947 --> 35:56.639
about the environment SOCOM operate in,

35:56.639 --> 35:58.483
in all likelihood the
satellite is gonna be

35:58.483 --> 36:00.246
the main mode of connectivity,

36:00.246 --> 36:03.403
but when you have a
actual base, for example,

36:03.403 --> 36:04.727
in Iraq or something like that,

36:04.727 --> 36:07.444
where there is infrastructure,
fiber optic capacity,

36:07.444 --> 36:10.640
we probably could deploy not
only 5G small cell radios,

36:10.640 --> 36:13.169
because again the form
factor is very friendly,

36:13.169 --> 36:15.273
but we have cell on wheel
which is essentially

36:15.273 --> 36:18.887
a mobile switching center base station

36:18.887 --> 36:21.980
that can also kind of
fulfill a similar function

36:21.980 --> 36:23.178
in the world of 5G.

36:23.178 --> 36:26.131
So when I said, you know, in
the forward operating base

36:26.131 --> 36:28.020
with autonomous vehicles
and some of that stuff

36:28.020 --> 36:29.910
for reconnaissance for example,

36:29.910 --> 36:31.106
it might be more difficult,

36:31.106 --> 36:32.780
I'm talkin' about
non-permissible environments

36:32.780 --> 36:34.953
where there is a formal
base infrastructure

36:34.953 --> 36:37.485
fiber optic capable there is no reason why

36:37.485 --> 36:40.815
we couldn't replicate
what we do here, there.

36:40.815 --> 36:43.091
- So, yeah, I'm gonna
have Paul mention this

36:43.091 --> 36:45.646
'cause we've turned to
Paul as well at Qualcomm

36:45.646 --> 36:48.628
because they've helped shape
that market as well, right,

36:48.628 --> 36:49.705
5G with their technology,

36:49.705 --> 36:51.702
and so how we turn to them

36:51.702 --> 36:54.528
and better understand what
that market looks like

36:54.528 --> 36:57.596
before we take the next steps.

36:57.596 --> 36:59.882
- Yeah, I was just gonna follow on.

36:59.882 --> 37:02.503
I think Verizon is already looking at this

37:02.503 --> 37:04.869
in the commercial world
as they look at venues

37:04.869 --> 37:09.180
and how they support venues
where there's high density needs

37:09.180 --> 37:13.761
and even these venues tend
to be somewhat temporal,

37:13.761 --> 37:15.106
so where they have events

37:15.106 --> 37:16.315
and they have to go out and support.

37:16.315 --> 37:18.780
So they're I think very well experienced

37:18.780 --> 37:20.947
in the deployable networks

37:22.578 --> 37:25.412
that can be leveraged going forward.

37:25.412 --> 37:27.175
I think it's interesting Qualcomm,

37:27.175 --> 37:30.946
you probably read in the
news Qualcomm likes 5G.

37:30.946 --> 37:35.149
I think back to 10 years ago
when we were talking about 5G,

37:35.149 --> 37:38.323
and we talked about this
component called mission critical,

37:38.323 --> 37:40.286
and at the time everyone says,

37:40.286 --> 37:43.063
"Well, we only care about cell phones

37:43.063 --> 37:45.480
"and people only care abut smartphones."

37:45.480 --> 37:47.754
They rarely talked about mission critical

37:47.754 --> 37:52.583
and that really grew very
fast in terms of okay,

37:52.583 --> 37:55.350
what does that really mean in the space

37:55.350 --> 37:59.677
of autonomous vehicles, Internet of thing,

37:59.677 --> 38:02.714
connected devices, the medical world

38:02.714 --> 38:04.797
of needing a lot of data,

38:06.138 --> 38:09.788
needing it fast, and
needing it almost real-time

38:09.788 --> 38:11.684
and that's where the latency comes in.

38:11.684 --> 38:16.094
Drones has come into that
space or robotics in general.

38:16.094 --> 38:19.261
So, I think 5G is clearly a technology

38:20.608 --> 38:23.127
that has evolved very fast.

38:23.127 --> 38:25.863
It's evolved much faster than 4G.

38:25.863 --> 38:28.836
And the rollouts that Verizon is doing

38:28.836 --> 38:30.300
is a testimony to that.

38:30.300 --> 38:34.300
So that now all of these
different applications,

38:35.810 --> 38:38.470
and a lot of them safety
critical and mission critical,

38:38.470 --> 38:42.303
will now happen much
faster as a result of 5G.

38:45.537 --> 38:47.255
- So one of the feedbacks we
got from the morning session

38:47.255 --> 38:49.522
is that we wanted some time
for question and answers

38:49.522 --> 38:51.538
so we're gonna do that now.

38:51.538 --> 38:52.959
Captain O'Reilly's gonna walk around.

38:52.959 --> 38:55.937
So, we've got about 10
minutes here for you

38:55.937 --> 38:57.725
to ask some questions of our panelists

38:57.725 --> 39:00.366
and see where it goes.

39:00.366 --> 39:02.366
- You can have this one.

39:07.944 --> 39:08.777
Questions?

39:12.591 --> 39:14.095
- [Male Audience Member] Yeah, thanks.

39:14.095 --> 39:15.398
This one it's related,

39:15.398 --> 39:16.765
and it's something that we
don't often talk about it

39:16.765 --> 39:18.178
'cause it's not sexy,

39:18.178 --> 39:21.328
and it might be mostly for Kyle and Jay,

39:21.328 --> 39:22.744
but when you talk about
autonomous vehicles

39:22.744 --> 39:24.593
or even the network a lot
of times what we don't talk

39:24.593 --> 39:26.218
about is sustainability.

39:26.218 --> 39:29.028
And, so, what does that model look like

39:29.028 --> 39:32.000
to sustain these vehicles
or to sustain that network?

39:32.000 --> 39:33.921
And, is it a traditional model

39:33.921 --> 39:36.515
where you have a weapons
system or a network

39:36.515 --> 39:37.755
that's out there for 30 years

39:37.755 --> 39:41.184
or is it more of a disposable
model that you might use?

39:41.184 --> 39:42.800
And, Jay, I remember you said something,

39:42.800 --> 39:44.103
maybe you coined it and maybe you didn't

39:44.103 --> 39:46.963
but it sticks with me that
you did, cradle to cradle.

39:46.963 --> 39:49.303
So, can you talk about that a little bit?

39:49.303 --> 39:52.840
- So, the word cradle
to cradle is actually

39:52.840 --> 39:57.231
a trademarked word started
I think by Bill McDonough,

39:57.231 --> 40:00.044
one of the originators of the
LEED Building Certification,

40:00.044 --> 40:03.975
and it's a moniker that he
uses and his foundation uses

40:03.975 --> 40:08.435
in order to be able to describe
a full circle ecosystem.

40:08.435 --> 40:11.190
If you really read into
it, it has a lot of genius

40:11.190 --> 40:15.116
that's behind it, and we
think about everything

40:15.116 --> 40:16.843
from the sustainment on our bases

40:16.843 --> 40:18.616
for what the ecological signature is

40:18.616 --> 40:20.243
of throwing rounds down range,

40:20.243 --> 40:22.684
we were talking about
that outside recently,

40:22.684 --> 40:24.934
but also when you think
about leaving theater

40:24.934 --> 40:27.452
and vehicles that you simply
don't want to put on a ship

40:27.452 --> 40:29.875
and bring back and so
what are you gonna do?

40:29.875 --> 40:32.132
You could transition them
to a friendly nation.

40:32.132 --> 40:34.164
If it's not friendly, then
are you just gonna leave them

40:34.164 --> 40:35.208
on the beach?

40:35.208 --> 40:37.677
So, these are things that
we need to think about

40:37.677 --> 40:38.930
and we do think about.

40:38.930 --> 40:43.331
The concept of building
a full tail isn't just

40:43.331 --> 40:45.698
about servicing vehicles on a base,

40:45.698 --> 40:47.804
it's also about what you do with vehicles

40:47.804 --> 40:49.352
in an operating environment.

40:49.352 --> 40:52.483
And, so, humanitarian
assistance and disaster relief,

40:52.483 --> 40:54.687
the last thing you want to do
is bring a ton of vehicles in,

40:54.687 --> 40:56.787
then pollute the ecosystem themselves,

40:56.787 --> 40:58.829
and that becomes even more an issue

40:58.829 --> 41:01.453
when we are looking at
battery electric vehicles.

41:01.453 --> 41:03.317
That doesn't mean the batteries are bad.

41:03.317 --> 41:05.062
They happen to be some of the backbone

41:05.062 --> 41:08.817
that makes connected and
autonomous vehicles work better,

41:08.817 --> 41:10.906
but it is still something
that we need to think about.

41:10.906 --> 41:14.458
So, full service mobility as a service

41:14.458 --> 41:16.381
goes all the way down to
the sustainment level.

41:16.381 --> 41:18.849
Just as a note, we
print vehicles right now

41:18.849 --> 41:20.277
as I've noted in 10 hours.

41:20.277 --> 41:22.876
There's also material that
we use that is compostable.

41:22.876 --> 41:25.081
And so it doesn't have the same structure

41:25.081 --> 41:27.618
as some of the crash
structures that we have,

41:27.618 --> 41:28.679
but there's a lot of the vehicle

41:28.679 --> 41:29.742
that isn't a crash structure

41:29.742 --> 41:31.407
so the printout of a bioplastic

41:31.407 --> 41:33.314
that's reinforced with a bamboo fiber,

41:33.314 --> 41:34.761
and then being able to see that

41:34.761 --> 41:36.770
just chopped up and put in the ground,

41:36.770 --> 41:38.776
that's a really next
generation way of looking

41:38.776 --> 41:41.033
at the way in which you build a vehicle

41:41.033 --> 41:43.457
and is part of the sustainment story.

41:43.457 --> 41:45.874
- [Brandon] Another question?

41:46.833 --> 41:48.460
- Just to add to that,

41:48.460 --> 41:50.356
I think you might have coined the term

41:50.356 --> 41:51.635
through asking questions,

41:51.635 --> 41:53.646
it's making obsolescence obsolete,

41:53.646 --> 41:55.960
so not just sustainment
of autonomous vehicles

41:55.960 --> 41:59.524
but all of our major end
items moving forward,

41:59.524 --> 42:01.552
leveraging advance manufacturing

42:01.552 --> 42:03.990
as far forward as possible

42:03.990 --> 42:05.731
and then leveraging a
digital thread to ensure

42:05.731 --> 42:07.815
that we're having iterative maintenance

42:07.815 --> 42:11.521
and upgrades of any
weapons system or vehicle

42:11.521 --> 42:16.104
that we have in the future
is key for the future fight.

42:20.611 --> 42:21.444
- [Eva] Good afternoon.

42:21.444 --> 42:23.197
Thank you for this wonderful session,

42:23.197 --> 42:24.735
actually for the wonderful conference.

42:24.735 --> 42:26.391
My name is Eva Lerner-Lam,

42:26.391 --> 42:28.873
transportation systems consultant

42:28.873 --> 42:32.661
and representing the American
Society of Civil Engineers

42:32.661 --> 42:33.578
here today.

42:35.163 --> 42:37.748
As the Marine Corps is
doing this incredible job

42:37.748 --> 42:41.392
of trying to advance it's operations,

42:41.392 --> 42:43.892
it's community building really

42:46.109 --> 42:49.554
with the civilian community
trying to catch up

42:49.554 --> 42:53.304
to where technology is
I guess my question is

42:54.278 --> 42:57.543
how do we at the same
time as we are customers

42:57.543 --> 43:00.514
of the new technologies, how can we hold

43:00.514 --> 43:03.643
the technology companies to task

43:03.643 --> 43:06.432
for the security of the data that's going

43:06.432 --> 43:08.798
to be transmitted back and forth

43:08.798 --> 43:11.139
and a lot of the tech companies,

43:11.139 --> 43:15.284
not any of the ones up on the board today,

43:15.284 --> 43:18.819
but a lot of the companies
that do own a lot

43:18.819 --> 43:22.006
of the tech that we're using,

43:22.006 --> 43:24.100
ChargePoint is one of them,

43:24.100 --> 43:25.539
there're a lot of tech companies

43:25.539 --> 43:28.680
that are actually owned
by foreign enterprises,

43:28.680 --> 43:33.148
in particular China, and
that data now belongs

43:33.148 --> 43:37.344
a lot to them as well
so Scooter Information--

43:37.344 --> 43:39.441
- So, Eva, that's a perfect question,

43:39.441 --> 43:41.241
and so I'm actually gonna turn

43:41.241 --> 43:42.688
to Verizon and Qualcomm with this.

43:42.688 --> 43:45.002
And, one thing I wanna
highlight before this is

43:45.002 --> 43:50.002
we think of ourselves and this
uniform as the authorities

43:50.209 --> 43:52.959
of living in a secure environment

43:54.368 --> 43:56.652
because everything about us you know

43:56.652 --> 43:59.490
that it requires that type of protection.

43:59.490 --> 44:02.623
And where in my hypothesis has always been

44:02.623 --> 44:04.444
that we've missed the mark in this

44:04.444 --> 44:08.288
is that industry has
actually a lot more riding

44:08.288 --> 44:11.371
on the cybersecurity and the
performance of their system

44:11.371 --> 44:14.472
where dollars and cents drive them,

44:14.472 --> 44:16.534
where the losses are immediate,

44:16.534 --> 44:19.851
the impact is immediate
to them being compromised.

44:19.851 --> 44:21.986
And, so, we don't often see

44:21.986 --> 44:25.592
that they are actually well advanced of us

44:25.592 --> 44:28.642
with our regulations on
cybersecurity in this regard.

44:28.642 --> 44:32.439
And, so, I want a chance to
have maybe all three of you

44:32.439 --> 44:35.042
kind of address this
from the industry side

44:35.042 --> 44:37.113
starting with you, Paul.

44:37.113 --> 44:38.839
- Yeah, I'll just add a quick comment.

44:38.839 --> 44:41.018
As I mentioned mission critical was one

44:41.018 --> 44:43.611
of the fundamental pillars of 5G,

44:43.611 --> 44:47.281
security was probably
a bigger one than that.

44:47.281 --> 44:51.034
So, when we looked at
okay, you need more data,

44:51.034 --> 44:52.953
you need more connected things,

44:52.953 --> 44:55.722
the underlying fabric of security

44:55.722 --> 44:58.222
was very much forefront on 5G,

44:59.242 --> 45:04.242
and I think Verizon might
want to say more to that.

45:04.243 --> 45:06.973
- I don't have too many
deep thoughts on this one

45:06.973 --> 45:10.275
just because we're a
consumer of the technology

45:10.275 --> 45:13.108
that Qualcomm and Verizon provide.

45:14.431 --> 45:17.182
But, being in the military space,

45:17.182 --> 45:20.781
I would like to address
quickly a previous comment.

45:20.781 --> 45:22.994
The way that systems are
designed for the military

45:22.994 --> 45:26.010
we're communication or network agnostic,

45:26.010 --> 45:30.607
meaning that we have to
build enough intelligence

45:30.607 --> 45:32.973
into our platforms that they
don't need to be connected.

45:32.973 --> 45:34.172
They're connected when they need to be,

45:34.172 --> 45:37.811
but that's not in reality
on the battle space.

45:37.811 --> 45:38.985
You can't rely on GPS.

45:38.985 --> 45:41.031
You can't rely on comms.

45:41.031 --> 45:43.977
Even SATCOM you can have issues with.

45:43.977 --> 45:46.087
So, we have to take the physical security

45:46.087 --> 45:48.312
of our systems more important

45:48.312 --> 45:52.229
than actually the network
side of being secure.

45:55.165 --> 45:57.274
- Well, first of all bear in mind

45:57.274 --> 45:58.592
that Verizon has been providing

45:58.592 --> 46:00.213
mission critical secure networks

46:00.213 --> 46:03.255
for the military intelligence
agencies for decades.

46:03.255 --> 46:05.806
So, we're really good at that.

46:05.806 --> 46:07.791
But, one of the things, you know, I think

46:07.791 --> 46:11.320
if you talk to our chief
technology officer now,

46:11.320 --> 46:14.846
and our CEO who is a former
chief technology officer,

46:14.846 --> 46:16.634
the thing that keeps us awake at night

46:16.634 --> 46:19.138
is not being able to
build this 5G network,

46:19.138 --> 46:21.696
we're absolutely confident
that we can build it.

46:21.696 --> 46:25.101
It will have low latencies
under 10 milliseconds,

46:25.101 --> 46:30.013
ability to support millions of
devices in every square mile,

46:30.013 --> 46:33.603
and throughput rate of one
gigabit to 10 gigabit per second

46:33.603 --> 46:35.555
at the minimum those
are three key currencies

46:35.555 --> 46:36.388
that you get out of it.

46:36.388 --> 46:39.006
But, the thing that we
really are concerned about is

46:39.006 --> 46:41.756
as the military cities rely on us

46:42.792 --> 46:46.389
to have all their lights, their
equipment, their vehicles,

46:46.389 --> 46:49.867
connected to our network and
supported by that 5G network,

46:49.867 --> 46:52.727
the importance of security
becomes even more paramount.

46:52.727 --> 46:54.656
Because now if there's a problem,

46:54.656 --> 46:56.428
our military's having a problem,

46:56.428 --> 46:58.232
our cities are having a problem,

46:58.232 --> 47:00.165
and these are operational,

47:00.165 --> 47:02.333
mission-critical operational problems

47:02.333 --> 47:05.187
that can adversely affect the country.

47:05.187 --> 47:06.909
So, one of the key things,

47:06.909 --> 47:09.653
and this is probably a
little less sexy of an issue

47:09.653 --> 47:11.013
and doesn't get as much attention

47:11.013 --> 47:14.719
that is being baked in to
the design of the 5G network,

47:14.719 --> 47:18.113
is that we could've rolled 5G
maybe four, five years ago,

47:18.113 --> 47:23.113
but we first started by
defining a software defined

47:23.161 --> 47:27.615
networking layer in all of
our core and edge networks,

47:27.615 --> 47:30.944
and now we have a secure defined perimeter

47:30.944 --> 47:33.671
that's enabled by that software design,

47:33.671 --> 47:36.098
software defined networking
that's gonna support

47:36.098 --> 47:38.765
every 5G connection to a device,

47:39.618 --> 47:42.358
and there'll be an X.509 certificate

47:42.358 --> 47:45.422
on every sensor that identifies itself.

47:45.422 --> 47:48.066
So, a Qualcomm system on a chip

47:48.066 --> 47:49.668
is gonna have a unique identity,

47:49.668 --> 47:53.527
our 5G network is gonna
do a identity verification

47:53.527 --> 47:56.618
before it allows it to write its data

47:56.618 --> 48:00.279
over that network to our
MEC, which is the data center

48:00.279 --> 48:02.658
where the data at rest is gonna reside

48:02.658 --> 48:05.148
for all those algorithms
to process that data.

48:05.148 --> 48:08.722
So, that's been inherently
built in and baked in

48:08.722 --> 48:11.271
through the use of
software defined networking

48:11.271 --> 48:13.494
and secure edge perimeter.

48:13.494 --> 48:15.897
And, we find that as one
of the most critical things

48:15.897 --> 48:19.064
because if you recall we had a problem

48:20.052 --> 48:23.365
with server form
proliferation in the military

48:23.365 --> 48:25.325
over the last couple of decades,

48:25.325 --> 48:28.296
and the way we got around all
the security issues associated

48:28.296 --> 48:29.664
with that is we went to the cloud

48:29.664 --> 48:32.291
and kind of consolidated the data centers.

48:32.291 --> 48:34.478
Now, with the advent of all these sensors,

48:34.478 --> 48:38.033
we are proliferating the
number of edge devices

48:38.033 --> 48:40.427
that could potentially be compromised.

48:40.427 --> 48:42.857
So for one thing we lobbied to make sure

48:42.857 --> 48:45.753
Huawei, the Chinese company,
does not get to park

48:45.753 --> 48:47.920
any kind hardware,
software in this country

48:47.920 --> 48:50.199
because it's proven that both

48:50.199 --> 48:52.704
in their hardware and
software they have back doors.

48:52.704 --> 48:55.793
And, secondly, we have
designed a system inherently

48:55.793 --> 48:58.510
at the core of the network
and the edge of the network,

48:58.510 --> 49:01.622
the 5G network, so that it's secure

49:01.622 --> 49:04.044
and it does automatic authentication,

49:04.044 --> 49:06.642
so it's gonna be one of
the most critical aspects

49:06.642 --> 49:10.430
of the industrial IoT
as well as consumer IoT

49:10.430 --> 49:11.893
as we look on the horizon.

49:11.893 --> 49:13.004
- [Male Audience Member] Hey,
Brandon, I got one question,

49:13.004 --> 49:15.355
I know you're runnin' outta time.

49:15.355 --> 49:17.468
So as we're looking for
5G going forward with 5G

49:17.468 --> 49:20.661
we have a problem of
lack of infrastructure

49:20.661 --> 49:24.682
for the transport within
the installation itself.

49:24.682 --> 49:26.249
So, they want Wi-Fi,

49:26.249 --> 49:27.832
and you have copper leaving the building.

49:27.832 --> 49:28.929
They want Wi-Fi,

49:28.929 --> 49:30.244
and you have routers there,

49:30.244 --> 49:33.527
70% or 60% of our routers are
probably not cyber compliant

49:33.527 --> 49:35.677
because they haven't been updated.

49:35.677 --> 49:39.177
And, then you have non-ethernet capability

49:40.240 --> 49:41.838
within the transport itself.

49:41.838 --> 49:44.127
So, when you talk about
what could we be doing,

49:44.127 --> 49:46.512
so we're not trying to
solve today's problems

49:46.512 --> 49:50.216
that we're looking at 5G, and
we make the right investment

49:50.216 --> 49:53.355
into our installations
to have that correlation

49:53.355 --> 49:57.973
between being able to
speak to the installation-

49:57.973 --> 50:00.081
- No, thank you for that question.

50:00.081 --> 50:01.134
It's actually music to my ears.

50:01.134 --> 50:02.736
So.

50:02.736 --> 50:03.655
- [Male Audience Member] I can sing too,

50:03.655 --> 50:05.795
but I mean
- (laughs)

50:05.795 --> 50:07.560
No, it was plenty fine.

50:07.560 --> 50:12.060
So, in order for us to deliver
a gigabit to 10 gigabit

50:13.926 --> 50:16.386
per second wirelessly on the RAN side

50:16.386 --> 50:19.676
of the network we need to
have fiber optic coming

50:19.676 --> 50:23.164
to that radio cell, the small cell.

50:23.164 --> 50:25.494
In other words, it's
the throughput capacity

50:25.494 --> 50:27.912
of the fiber optic that allows us

50:27.912 --> 50:29.955
to then use new radio technology

50:29.955 --> 50:33.321
to deliver gigabit, two
gigabit, 10 gigabit per second

50:33.321 --> 50:34.467
on the front end.

50:34.467 --> 50:37.675
So, one of the key things about 5G is

50:37.675 --> 50:41.238
that we need high fiber
density to the edge

50:41.238 --> 50:43.443
where that small cell is gonna be located

50:43.443 --> 50:46.769
that delivers the radio
signal for 5G applications.

50:46.769 --> 50:49.436
So, anything that would allow us

50:50.415 --> 50:54.007
to have access to conduits
or any fiber deployment

50:54.007 --> 50:55.032
that you could have,

50:55.032 --> 50:56.284
and, again, it should be in conjunction

50:56.284 --> 50:58.111
with a company like Verizon

50:58.111 --> 51:01.153
because you want to deploy
the fiber where we think

51:01.153 --> 51:02.906
the small cells ought to be located

51:02.906 --> 51:04.751
to provide the right kind of coverage

51:04.751 --> 51:07.784
for the autonomous mobility,
autonomous logistics systems

51:07.784 --> 51:10.692
that you are contemplating as
well as future applications

51:10.692 --> 51:12.715
that you haven't even
thought about, right,

51:12.715 --> 51:16.298
maybe using augmented
reality and AR and VR

51:17.366 --> 51:18.744
for condition-based maintenance

51:18.744 --> 51:21.425
so the technician can
just get instructions live

51:21.425 --> 51:23.350
on how to fix.

51:23.350 --> 51:25.603
So, those things are all gonna need 5G,

51:25.603 --> 51:26.593
and in order to do that,

51:26.593 --> 51:29.082
we can kind of design the
architecture with you,

51:29.082 --> 51:30.610
but then the key aspect

51:30.610 --> 51:34.939
is bringing fiber as deep
as possible into the base.

51:34.939 --> 51:37.153
- All right, so I'm gonna
ask the last question.

51:37.153 --> 51:39.114
One or two sentences from each of us.

51:39.114 --> 51:41.246
Today is about unlocking the creativity

51:41.246 --> 51:45.568
so each of you starting with
Jay, point out 10 years.

51:45.568 --> 51:47.888
What are autonomous
vehicles, unmanned systems

51:47.888 --> 51:49.130
doing for us.

51:49.130 --> 51:52.989
Give us a taste of what you see use cases.

51:52.989 --> 51:54.946
- 20 years from now we're
definitely going to be

51:54.946 --> 51:56.090
a lot more in the air,

51:56.090 --> 51:57.964
and it's something that we have orphaned

51:57.964 --> 51:59.778
a little bit today will be demonstrated,

51:59.778 --> 52:02.817
but the work that's going
on in electrical systems

52:02.817 --> 52:06.240
for aviation vastly
reduces maintenance cycles,

52:06.240 --> 52:09.302
and it increases the ability for controls,

52:09.302 --> 52:12.162
the introduction of ADSB
and other things like that,

52:12.162 --> 52:14.676
and so the necessity for us to be able

52:14.676 --> 52:16.971
to get those systems online in 20 years

52:16.971 --> 52:19.473
is gonna unlock a lot of freedoms for us.

52:19.473 --> 52:21.579
We think about drones as something

52:21.579 --> 52:23.819
that might provide simple things

52:23.819 --> 52:27.619
like intercity mobility, the
ability to go from the edge

52:27.619 --> 52:31.502
to the edge is such an important
thing for air mobility.

52:31.502 --> 52:35.575
So, I'm a huge believer that
all of this ends up in the air.

52:35.575 --> 52:37.097
The ground is very congested,

52:37.097 --> 52:39.904
and the ground is a lot of
humans on the ground driving.

52:39.904 --> 52:42.359
It's a more controlled space in the air,

52:42.359 --> 52:43.192
and I think it's something

52:43.192 --> 52:45.245
that we're gonna see
coming online if 20 years

52:45.245 --> 52:46.747
is the horizon we're thinking about.

52:46.747 --> 52:47.580
- All right, thanks, Jay.

52:47.580 --> 52:48.564
Kevin.

52:48.564 --> 52:51.145
- I think VTOL is gonna be very dominant

52:51.145 --> 52:53.666
because, again, we just don't
have the road capacities

52:53.666 --> 52:56.418
to deal with the congestions
that we have right now,

52:56.418 --> 52:59.370
and at some point in time
we're gonna find cities

52:59.370 --> 53:02.771
essentially blocking the
city except for the residents

53:02.771 --> 53:05.685
or people that wanna pay
maybe 50 to 100 bucks a day

53:05.685 --> 53:08.010
just to get into the city, not to park.

53:08.010 --> 53:10.785
And that way they can
reduce the amount of flow

53:10.785 --> 53:12.193
of traffic that comes into it.

53:12.193 --> 53:17.075
Washington DC, my hometown
gets 500,000 people a day

53:17.075 --> 53:18.952
come into work and go out.

53:18.952 --> 53:21.466
And when you talk to
the mayor they say Uber

53:21.466 --> 53:23.650
and just shared mobility is
not gonna solve that problem.

53:23.650 --> 53:25.298
It's just too fundamental.

53:25.298 --> 53:26.862
So, I think at some point in time

53:26.862 --> 53:30.577
you will see shared mobility
from perimeter of the cities

53:30.577 --> 53:33.154
bringing people in and out so that you can

53:33.154 --> 53:34.696
kind of reduce the congestion,

53:34.696 --> 53:38.648
but short of that and even
with that VTOL is gonna be

53:38.648 --> 53:42.841
the dominant mode of autonomous logistics

53:42.841 --> 53:46.591
and transportation as
we look on the horizon.

53:47.545 --> 53:49.848
- All right, so, I'll
skip the flying vehicles

53:49.848 --> 53:52.431
and go back to being connected.

53:54.175 --> 53:56.329
The main limitation
with vehicles operating

53:56.329 --> 53:59.723
throughout the United
States is the infrastructure

53:59.723 --> 54:01.065
that's in the environment,

54:01.065 --> 54:02.334
and that can be sensors,

54:02.334 --> 54:06.370
but it's also the 5G connection
and the low latencies.

54:06.370 --> 54:08.241
So, I see that on the horizon.

54:08.241 --> 54:09.285
I see that as happening.

54:09.285 --> 54:12.622
When I did my thesis, it
basically boiled down to that.

54:12.622 --> 54:15.540
If you want systems, autonomous systems,

54:15.540 --> 54:18.022
to work harmoniously, they
need to be able to communicate

54:18.022 --> 54:21.611
and communicate instantly, and
that's what I'd like to see.

54:21.611 --> 54:23.797
And I'd like to go to work
without having to drive

54:23.797 --> 54:26.200
so I could get a few hours of my day back.

54:26.200 --> 54:29.142
- (speaks off microphone and laughs)

54:29.142 --> 54:29.975
- Sorry.

54:29.975 --> 54:30.808
- That's fine.

54:30.808 --> 54:32.993
Yeah, so we mentioned, Eddie
mentioned, I mentioned,

54:32.993 --> 54:35.558
cost-optimized solutions and Eddie said,

54:35.558 --> 54:38.563
"If someone tells you it's
cheap today they're lying."

54:38.563 --> 54:42.306
So obviously when you think
about 15, 20 years from now,

54:42.306 --> 54:44.151
we've got to address the cost.

54:44.151 --> 54:47.156
We've got to get autonomous
vehicles mainstream.

54:47.156 --> 54:50.026
I think we'll see these
cooperative environments

54:50.026 --> 54:53.693
of dense urban cities
will emerge very fast.

54:56.416 --> 54:58.656
That's where the private vehicles

54:58.656 --> 55:00.978
or shared vehicles will emerge very fast

55:00.978 --> 55:04.853
with again these cost-optimized solutions.

55:04.853 --> 55:07.318
I do agree also drones
will start showing up,

55:07.318 --> 55:10.764
and so it's another population
we like to think about,

55:10.764 --> 55:13.125
and we did think about it in 5G

55:13.125 --> 55:15.575
where we have a population that's overhead

55:15.575 --> 55:17.554
as well as a population on the ground

55:17.554 --> 55:20.697
that we have to manage
in a very cooperative

55:20.697 --> 55:22.676
and collaborative environment.

55:22.676 --> 55:26.009
So, we'll see a lot of connected things.

55:26.930 --> 55:29.610
- By the way the only
network that has a capacity

55:29.610 --> 55:32.479
to handle all the things
that will be on ground

55:32.479 --> 55:37.422
and all the things that we
flying will be a 5G network.

55:37.422 --> 55:39.103
- So, I do agree that
we'll all be traveling

55:39.103 --> 55:41.547
like George Jetson 10
or 15 years from now,

55:41.547 --> 55:45.166
but from a military
perspective having autonomy

55:45.166 --> 55:47.092
in all three of the legacy domains,

55:47.092 --> 55:49.981
surface, maritime, ground, and air,

55:49.981 --> 55:51.910
is gonna change fundamentally the way

55:51.910 --> 55:53.286
that we look at sustainment.

55:53.286 --> 55:57.203
So, gone will be the day
of a 60 vehicle convoy

55:58.306 --> 56:00.243
that you might've seen
in Iraq or Afghanistan.

56:00.243 --> 56:02.907
You're gonna have a much
more distributed environment

56:02.907 --> 56:05.858
where you can have a one-off
vehicle travel autonomously

56:05.858 --> 56:10.218
to deliver a precise
payload at a precise time.

56:10.218 --> 56:11.075
- All right.

56:11.075 --> 56:12.857
Thank you to our panelists.

56:12.857 --> 56:16.940
(audience applauds)
Thanks, guys.

56:22.558 --> 56:23.391
Thanks, Paul.

56:23.391 --> 56:25.403
Thanks for coming out.

56:25.403 --> 56:29.403
(speaking away from microphone)

56:30.576 --> 56:31.442
- All right.

56:31.442 --> 56:34.604
Next up is urban air mobility.

56:34.604 --> 56:36.350
So, we kind of closed on a note

56:36.350 --> 56:39.833
about airspace as if
it was the next panel,

56:39.833 --> 56:42.267
so that was interesting to go there.

56:42.267 --> 56:43.854
Before you start that,
Nicole, we're gonna get

56:43.854 --> 56:46.354
our panelists up on the stage.

56:55.182 --> 56:56.682
Chad, thanks, man.

56:58.223 --> 56:59.056
Thanks.

57:18.471 --> 57:19.971
All right, thanks.

57:22.414 --> 57:23.746
All right.

57:23.746 --> 57:26.610
Okay, so we're gonna
tease this a little bit.

57:26.610 --> 57:28.399
What is urban air mobility?

57:28.399 --> 57:30.743
And, we're gonna use someone
that's not on the stage

57:30.743 --> 57:32.837
to help us see the future a little bit

57:32.837 --> 57:36.417
about what you heard
about at the conclusion

57:36.417 --> 57:38.509
of that last panel.

57:38.509 --> 57:41.259
So, if you could start the video.

57:45.157 --> 57:47.574
(whispering)

57:58.772 --> 58:01.022
(laughing)

58:17.580 --> 58:20.330
(blissful music)

58:25.087 --> 58:28.504
(shoes tapping on floor)

58:33.059 --> 58:35.750
(beep)

58:35.750 --> 58:39.467
(plane engines running)

58:39.467 --> 58:42.217
(blissful music)

59:11.408 --> 59:14.158
(plane soars by)

59:19.796 --> 59:22.358
(door opens)

59:22.358 --> 59:24.858
(door closes)

59:44.978 --> 59:46.345
(low buzzing noise)

59:46.345 --> 59:48.687
- All right, so what we saw there was

59:48.687 --> 59:51.035
the vision of Uber Elevate.

59:51.035 --> 59:55.723
Uber in 2016 created, first
it started with a white paper,

59:55.723 --> 59:58.663
where they framed out what the ecosystem

59:58.663 --> 01:00:00.863
of air mobility would look like.

01:00:00.863 --> 01:00:04.375
These are electric vertical
takeoff and landing platforms.

01:00:04.375 --> 01:00:05.830
And, what we've watched them do

01:00:05.830 --> 01:00:08.840
over the last three years now,

01:00:08.840 --> 01:00:12.314
is create an entire ecosystem
around this concept.

01:00:12.314 --> 01:00:16.743
In the back if you turn
off the video audio,

01:00:16.743 --> 01:00:18.677
we'll take out that buzz.

01:00:18.677 --> 01:00:23.042
So, we use that to help us
see just like what you heard

01:00:23.042 --> 01:00:25.156
at the conclusion of that last panel that

01:00:25.156 --> 01:00:26.679
where that future is going.

01:00:26.679 --> 01:00:29.084
And, it sounds like Jetsons a bit,

01:00:29.084 --> 01:00:31.960
if you're old enough to remember Jetsons,

01:00:31.960 --> 01:00:35.151
but Jetsons didn't have ride hailing apps.

01:00:35.151 --> 01:00:39.484
Jetsons didn't have IPOs
like what we're seeing now,

01:00:40.364 --> 01:00:43.307
businesses that are meeting
the need right there

01:00:43.307 --> 01:00:44.640
to the customer.

01:00:45.593 --> 01:00:47.815
That can actually help shape

01:00:47.815 --> 01:00:50.993
that entire ecosystem around this future.

01:00:50.993 --> 01:00:55.993
And, so, we have this in mind
where your air taxi concept,

01:00:56.465 --> 01:00:58.733
but we're gonna start more locally

01:00:58.733 --> 01:01:00.876
and talk about some of the opportunities

01:01:00.876 --> 01:01:04.015
that have been created here regionally.

01:01:04.015 --> 01:01:06.394
So, we're gonna start with Jesse Gipe

01:01:06.394 --> 01:01:09.674
from San Diego Regional
Economic Development Council

01:01:09.674 --> 01:01:12.450
and who was integral with the city

01:01:12.450 --> 01:01:16.867
on starting the FAA's drone
Integration Pilot Program

01:01:17.895 --> 01:01:19.395
here in San Diego.

01:01:22.070 --> 01:01:23.590
- Thanks, Colonel.

01:01:23.590 --> 01:01:26.657
So, I'll talk a little
bit about the IPP program

01:01:26.657 --> 01:01:29.205
and some of kind of
what we're excited about

01:01:29.205 --> 01:01:31.244
for urban air mobility as a city,

01:01:31.244 --> 01:01:33.719
but also what we're doing
in kind of the interim steps

01:01:33.719 --> 01:01:35.634
through the IPP program
that's kind of laying some

01:01:35.634 --> 01:01:37.006
of the foundational groundwork both

01:01:37.006 --> 01:01:38.730
from a connectivity standpoint

01:01:38.730 --> 01:01:42.565
and also from a UTM, Unmanned
Traffic Management standpoint

01:01:42.565 --> 01:01:45.445
in order to kind of bring
this vision to reality.

01:01:45.445 --> 01:01:49.917
And, so, IPP is a FAA run
program, Integrated Pilot Program.

01:01:49.917 --> 01:01:51.885
There were 10 locations
selected across the country

01:01:51.885 --> 01:01:53.675
to participate in this program.

01:01:53.675 --> 01:01:56.672
And, the city of San Diego
was one of three cities

01:01:56.672 --> 01:01:59.456
in the entire country
selected, the largest city

01:01:59.456 --> 01:02:02.362
with frankly the most
complex airspace by far

01:02:02.362 --> 01:02:06.818
when you look at the dynamics
of our military airspace,

01:02:06.818 --> 01:02:10.868
dense urban corridor,
international border,

01:02:10.868 --> 01:02:12.243
international airport located

01:02:12.243 --> 01:02:14.494
in a downtown urban environment.

01:02:14.494 --> 01:02:16.114
Our airspace is extremely complicated.

01:02:16.114 --> 01:02:20.686
There's 55 heliports and
airports in San Diego County.

01:02:20.686 --> 01:02:22.644
So, we have very complex airspace,

01:02:22.644 --> 01:02:24.356
and if we're able to make

01:02:24.356 --> 01:02:26.831
large-scale drone operations feasible

01:02:26.831 --> 01:02:29.224
in a safe environment that doesn't impact

01:02:29.224 --> 01:02:31.780
these mission critical military missions

01:02:31.780 --> 01:02:33.849
that are taking place
within our community,

01:02:33.849 --> 01:02:35.342
it starts to set the groundwork

01:02:35.342 --> 01:02:37.177
for a vision where you
can have larger aircraft

01:02:37.177 --> 01:02:38.068
flying as well.

01:02:38.068 --> 01:02:39.843
And, so, in IPP we're working

01:02:39.843 --> 01:02:41.102
with a variety of great partners.

01:02:41.102 --> 01:02:44.826
You heard from one of them
earlier today with Qualcomm,

01:02:44.826 --> 01:02:48.391
but we've got Qualcomm,
Uber Elevate, Matternet,

01:02:48.391 --> 01:02:53.286
ModalAI, AT&T, Intel, and
some other folks at AirMap,

01:02:53.286 --> 01:02:56.756
GE Aviations, Aeros working
with us on a variety

01:02:56.756 --> 01:02:57.711
of different missions.

01:02:57.711 --> 01:03:00.573
We're working on a food
delivery mission with Uber.

01:03:00.573 --> 01:03:02.796
We're working on a medical
delivery mission with Matternet

01:03:02.796 --> 01:03:04.679
and UCSD Health, where they're looking

01:03:04.679 --> 01:03:05.959
at doing blood samples directly

01:03:05.959 --> 01:03:07.912
from the hospital to the lab.

01:03:07.912 --> 01:03:09.576
The food delivery mission is a partnership

01:03:09.576 --> 01:03:11.807
between Uber Elevate and Uber Eats,

01:03:11.807 --> 01:03:14.560
and really the Uber Elevate team is using,

01:03:14.560 --> 01:03:17.342
and Chad can talk a lot
about that potentially,

01:03:17.342 --> 01:03:21.330
but there's a lot going
on in those projects

01:03:21.330 --> 01:03:22.979
they are really laying the groundwork

01:03:22.979 --> 01:03:24.426
for what the long-term vision is

01:03:24.426 --> 01:03:26.388
for how are we gonna manage airspace

01:03:26.388 --> 01:03:27.764
in a dense urban environment.

01:03:27.764 --> 01:03:30.078
And, so, for Uber Elevate figuring out

01:03:30.078 --> 01:03:32.127
how they can deliver food.

01:03:32.127 --> 01:03:33.858
You think about Uber Eats app.

01:03:33.858 --> 01:03:36.037
Uber Eats is actually the
largest food delivery company

01:03:36.037 --> 01:03:38.574
in the world by volume.

01:03:38.574 --> 01:03:40.078
They've got a lot of really good data

01:03:40.078 --> 01:03:42.731
about how long does it take to get food

01:03:42.731 --> 01:03:45.124
from a particular restaurant
to their customer,

01:03:45.124 --> 01:03:47.655
how long can the food remain good

01:03:47.655 --> 01:03:49.921
before that customer starts
to complain about that food,

01:03:49.921 --> 01:03:51.189
and what are the traffic impacts

01:03:51.189 --> 01:03:53.648
of the food in transit
between those two locations.

01:03:53.648 --> 01:03:56.382
And, so, within this project
we're working on with them

01:03:56.382 --> 01:03:59.552
here in San Diego we're
looking at using drones

01:03:59.552 --> 01:04:02.098
to deliver food directly from restaurants

01:04:02.098 --> 01:04:04.166
to the end customer and eliminate some

01:04:04.166 --> 01:04:05.635
of that traffic congestion.

01:04:05.635 --> 01:04:06.468
In the process of doing that,

01:04:06.468 --> 01:04:09.205
we're gonna have to manage our airspace,

01:04:09.205 --> 01:04:11.071
and we're gonna have to figure out ways

01:04:11.071 --> 01:04:13.307
to make sure that we're
not coming into conflict

01:04:13.307 --> 01:04:14.629
with the important
missions that are happening

01:04:14.629 --> 01:04:15.519
around the community.

01:04:15.519 --> 01:04:17.768
And, ultimately, not only not
come into conflict with them,

01:04:17.768 --> 01:04:20.843
but within reality do the bases also want

01:04:20.843 --> 01:04:22.845
to have their food delivered
by Uber at some point?

01:04:22.845 --> 01:04:25.085
You know, just recently the
bases have opened themselves up

01:04:25.085 --> 01:04:27.610
to allow Uber and Lyft and these
other ride sharing services

01:04:27.610 --> 01:04:31.459
to come on base so we want the
things that we're developing

01:04:31.459 --> 01:04:33.196
with these companies that
are gonna be services

01:04:33.196 --> 01:04:35.491
to the broader community
to become services

01:04:35.491 --> 01:04:37.318
to the service members who live on bases

01:04:37.318 --> 01:04:38.153
throughout the community.

01:04:38.153 --> 01:04:40.467
And, so, we've been
working with Colonel Newell

01:04:40.467 --> 01:04:42.792
and the Marine Corps
here to do some testing

01:04:42.792 --> 01:04:44.562
for our projects so there's
been some integration

01:04:44.562 --> 01:04:46.233
between what we're doing both just

01:04:46.233 --> 01:04:47.628
from an airspace management standpoint

01:04:47.628 --> 01:04:49.335
to ensure that we're not
impacting operations,

01:04:49.335 --> 01:04:52.460
but also looking at how
we bring that technology

01:04:52.460 --> 01:04:55.924
on base simultaneously or in some ways

01:04:55.924 --> 01:04:58.608
even do some of the testing
here on this installation

01:04:58.608 --> 01:05:00.650
and surrounding installations
while we're looking

01:05:00.650 --> 01:05:02.377
at scaling those things within the city.

01:05:02.377 --> 01:05:04.347
And, I can talk more about
some of the things we're doing

01:05:04.347 --> 01:05:05.806
around 5G and the communications stuff,

01:05:05.806 --> 01:05:08.412
but Chad and ModalAI as one
of our partners is certainly

01:05:08.412 --> 01:05:11.490
more competent on that, so.

01:05:11.490 --> 01:05:12.386
- Oh, thanks, Jesse.

01:05:12.386 --> 01:05:16.553
So, I recall I guess it
was a year and a half ago,

01:05:17.413 --> 01:05:18.843
we were making some noise about staring up

01:05:18.843 --> 01:05:20.535
the autonomous vehicle proving ground,

01:05:20.535 --> 01:05:23.366
and Jesse and Tiffany Vinson,
who couldn't join us today,

01:05:23.366 --> 01:05:25.687
from the city, came over.

01:05:25.687 --> 01:05:28.445
And, they were looking for
how can we collaborate.

01:05:28.445 --> 01:05:32.086
They were crafting the
proposal to the FAA.

01:05:32.086 --> 01:05:34.336
(audio and video skip)

01:05:34.336 --> 01:05:36.575
And, they only selected ten.

01:05:36.575 --> 01:05:38.305
What was unique about that opportunity was

01:05:38.305 --> 01:05:40.417
that unlike some of the other

01:05:40.417 --> 01:05:41.561
Department of Transportation

01:05:41.561 --> 01:05:43.081
autonomous vehicle proving ground efforts

01:05:43.081 --> 01:05:46.095
where they never had industry partners,

01:05:46.095 --> 01:05:48.616
this one was all about
having the industry partners

01:05:48.616 --> 01:05:52.346
and the use cases, so collaboratively FAA

01:05:52.346 --> 01:05:55.082
and the location in this case the city

01:05:55.082 --> 01:05:57.411
could drive regulation forward,

01:05:57.411 --> 01:06:00.777
craft regulation
appropriate with the input

01:06:00.777 --> 01:06:03.972
from the industry that's
trying to meet that need,

01:06:03.972 --> 01:06:05.447
trying to evolve into it.

01:06:05.447 --> 01:06:07.794
And it created an awesome model

01:06:07.794 --> 01:06:10.557
of a collaborative market again

01:06:10.557 --> 01:06:15.057
where a federal entity could
enable itself by finding,

01:06:17.082 --> 01:06:21.834
creating a space where that
collaboration takes place.

01:06:21.834 --> 01:06:25.366
And, so, what's interesting
is that even though we saw

01:06:25.366 --> 01:06:30.199
a vision of this ecosystem of
air taxis from Uber Elevate,

01:06:31.080 --> 01:06:33.277
and their first flights
are supposed to happen

01:06:33.277 --> 01:06:35.777
in 2023 in both Dallas and LA.

01:06:36.643 --> 01:06:39.677
Well, their focal point,
Uber's focal point,

01:06:39.677 --> 01:06:42.294
for that program early on turned to

01:06:42.294 --> 01:06:44.064
how are they gonna do traffic management?

01:06:44.064 --> 01:06:45.809
How are they gonna shape the regulation

01:06:45.809 --> 01:06:48.804
that happens of flights over
people and everything else?

01:06:48.804 --> 01:06:51.000
And, so, since they were
selected in this program

01:06:51.000 --> 01:06:54.546
with the city, their
focus came to San Diego

01:06:54.546 --> 01:06:56.852
and presented an opportunity to San Diego

01:06:56.852 --> 01:07:00.019
and to ourselves in that relationship.

01:07:01.608 --> 01:07:04.199
One of the first instances
of creating that type

01:07:04.199 --> 01:07:08.631
of collaborative market
involves Andrew Musto here.

01:07:08.631 --> 01:07:12.204
The first time that I saw
that type of thing take place.

01:07:12.204 --> 01:07:16.615
And, so, I remember going
out a year and a half ago

01:07:16.615 --> 01:07:21.448
and to a training area in the
middle of central California

01:07:24.021 --> 01:07:27.854
and watching a company
fly prototype air taxis

01:07:28.781 --> 01:07:30.995
that they had a contract with the IU on.

01:07:30.995 --> 01:07:35.370
And, I watched, I was there
the same day I watched them fly

01:07:35.370 --> 01:07:38.690
that the FAA came and gave
an experimental license

01:07:38.690 --> 01:07:40.722
for that company to go back out

01:07:40.722 --> 01:07:42.917
to where they were from and fly.

01:07:42.917 --> 01:07:45.302
Because the iteration
that they were achieving

01:07:45.302 --> 01:07:47.654
on the deck, in our airspace,

01:07:47.654 --> 01:07:49.759
our collective DOD airspace,

01:07:49.759 --> 01:07:51.952
where they had engineers living in tents

01:07:51.952 --> 01:07:53.932
and just flying in the
morning and iterating

01:07:53.932 --> 01:07:55.294
and then flying in the evening.

01:07:55.294 --> 01:07:58.733
And, so, I watched that type
of collaborative ecosystem

01:07:58.733 --> 01:08:01.117
take place and how they
pushed the boundaries

01:08:01.117 --> 01:08:05.622
of what they could do by
an asset that we have,

01:08:05.622 --> 01:08:07.815
both the installation and the airspace.

01:08:07.815 --> 01:08:09.587
And that was within Andrew's program.

01:08:09.587 --> 01:08:13.078
And, so, getting back to this vision

01:08:13.078 --> 01:08:16.273
of air mobility and tie
us to what's happening

01:08:16.273 --> 01:08:19.251
in the industry and then
how we see the applications

01:08:19.251 --> 01:08:23.642
for Marine Corps
installations or operations.

01:08:23.642 --> 01:08:25.434
- (taps on microphone)
Sure, thank you, sir.

01:08:25.434 --> 01:08:26.698
So, good afternoon, everybody.

01:08:26.698 --> 01:08:28.813
Andrew Musto, I'm a program manager

01:08:28.813 --> 01:08:30.765
in the Defense Innovation Unit.

01:08:30.765 --> 01:08:32.301
For those of you who are not familiar

01:08:32.301 --> 01:08:36.301
with our organization we
accelerate the adoption

01:08:38.341 --> 01:08:40.158
of commercial innovative technologies,

01:08:40.158 --> 01:08:41.653
specifically very advanced technologies

01:08:41.653 --> 01:08:43.029
into the Department of Defense

01:08:43.029 --> 01:08:46.772
for the purpose of transforming
the DOD's capabilities.

01:08:46.772 --> 01:08:49.742
And if you look broadly at
research and development spend

01:08:49.742 --> 01:08:51.514
across the entire nation,

01:08:51.514 --> 01:08:54.413
commercial entities are outpacing DOD

01:08:54.413 --> 01:08:56.931
in R & D spending by a
factor of about four to one.

01:08:56.931 --> 01:08:58.694
You can make the argument that those $4

01:08:58.694 --> 01:09:03.111
are spent more efficiently
than our $1 is in general.

01:09:04.138 --> 01:09:06.931
So, specifically I'm within
the autonomy portfolio,

01:09:06.931 --> 01:09:10.627
and my specific area of
focus is generally UAS.

01:09:10.627 --> 01:09:12.775
I work on everything from
large air taxi programs

01:09:12.775 --> 01:09:15.662
all the way down to small
group one and group two,

01:09:15.662 --> 01:09:17.121
generally in the logistics space

01:09:17.121 --> 01:09:19.301
with a focus on critical supply delivery

01:09:19.301 --> 01:09:21.413
and things of that nature.

01:09:21.413 --> 01:09:23.913
I am actually the guy that
helped Jay and his team get

01:09:23.913 --> 01:09:25.687
the DIU project off the ground,

01:09:25.687 --> 01:09:27.953
but that's generally
outside of what I usually do

01:09:27.953 --> 01:09:29.681
within the portfolio.

01:09:29.681 --> 01:09:32.571
As far as what we're seeing
with industry in general,

01:09:32.571 --> 01:09:34.501
I would say that that caption that you saw

01:09:34.501 --> 01:09:38.043
at the end of the Uber
Elevate video is very apt.

01:09:38.043 --> 01:09:42.765
It's very much closer than
you think at all levels.

01:09:42.765 --> 01:09:46.132
We're working to deploy a few
smaller systems this summer

01:09:46.132 --> 01:09:49.110
to a couple non-disclosed locations

01:09:49.110 --> 01:09:51.925
that will be delivering stuff to Marines

01:09:51.925 --> 01:09:53.842
at very long distances.

01:09:54.858 --> 01:09:59.740
And, the Uber prediction for
when vehicles will be flying is

01:09:59.740 --> 01:10:02.240
probably not far off the mark.

01:10:03.226 --> 01:10:04.059
- All right.

01:10:04.059 --> 01:10:04.892
Thanks, Andrew.

01:10:04.892 --> 01:10:06.888
So, I want to turn to Chad Sweet here.

01:10:06.888 --> 01:10:09.398
So, he's gonna talk about ModalAI

01:10:09.398 --> 01:10:10.774
and kind of it's origins,

01:10:10.774 --> 01:10:13.450
but ModalAI as Jesse mentioned is part

01:10:13.450 --> 01:10:15.529
of the IPP program here.

01:10:15.529 --> 01:10:17.792
And, it ties back to what we were talkin'

01:10:17.792 --> 01:10:22.092
with Qualcomm and Verizon
on the last panel as well

01:10:22.092 --> 01:10:23.292
with connectivity.

01:10:23.292 --> 01:10:27.879
And, so, how does this
future of connectivity start

01:10:27.879 --> 01:10:31.388
to impact drones that are
really radio signals to date,

01:10:31.388 --> 01:10:33.369
RF signals right now?

01:10:33.369 --> 01:10:35.375
So, where do you wanna take us, Chad?

01:10:35.375 --> 01:10:36.208
- Sure.

01:10:36.208 --> 01:10:37.208
Thank you very much.

01:10:37.208 --> 01:10:42.208
So, ModalAI spun out of
Qualcomm research specifically,

01:10:42.435 --> 01:10:44.934
about a year ago last summer.

01:10:44.934 --> 01:10:47.407
We quickly joined up with
Jesse and the city crew

01:10:47.407 --> 01:10:50.350
as a part of the San Diego IPP program.

01:10:50.350 --> 01:10:53.710
We've been involved in
both of the CONOPS there,

01:10:53.710 --> 01:10:56.524
one for border security,
the other for food delivery.

01:10:56.524 --> 01:11:00.869
And helping enable those
companies really advance

01:11:00.869 --> 01:11:03.560
their autonomous programs
by connecting them

01:11:03.560 --> 01:11:06.703
via cellular, connecting
their aerial vehicles

01:11:06.703 --> 01:11:08.260
via cellular back to the networks.

01:11:08.260 --> 01:11:10.975
We also quickly after that joined up

01:11:10.975 --> 01:11:14.808
with DIU and are working
on helping them build

01:11:18.849 --> 01:11:20.965
a more standardized set of components

01:11:20.965 --> 01:11:25.382
for the group one class
small UAS for ISR operations,

01:11:26.599 --> 01:11:28.604
or short range reconnaissance operations,

01:11:28.604 --> 01:11:31.682
and we're involved in
two components there.

01:11:31.682 --> 01:11:36.182
One is an autopilot, which
is a computer vision heavy,

01:11:37.696 --> 01:11:40.741
high-computation autopilot system,

01:11:40.741 --> 01:11:43.076
paired with an open ecosystem

01:11:43.076 --> 01:11:45.506
to help bring best in class commercial

01:11:45.506 --> 01:11:48.133
and off-the-shelf components into the DOD,

01:11:48.133 --> 01:11:53.133
and the second part of that
aspect is a very portable 4G

01:11:53.541 --> 01:11:56.433
with an evolution to 5G cellular network,

01:11:56.433 --> 01:12:00.368
and by portable, ideally
sub one kilogram handheld

01:12:00.368 --> 01:12:03.510
portable cellular network
that would enable someone

01:12:03.510 --> 01:12:08.386
in the field to control
multiple robotic vehicles

01:12:08.386 --> 01:12:09.862
and potentially more.

01:12:09.862 --> 01:12:13.113
And, that is where then we got connected

01:12:13.113 --> 01:12:15.650
with Lieutenant Colonel Newell,

01:12:15.650 --> 01:12:19.865
who is organizing this AV proving ground,

01:12:19.865 --> 01:12:23.794
and so this is providing
us an outstanding way,

01:12:23.794 --> 01:12:27.413
providing ModalAI and DIU in tandem,

01:12:27.413 --> 01:12:29.859
an outstanding way to prototype

01:12:29.859 --> 01:12:32.440
and characterize these radio systems,

01:12:32.440 --> 01:12:35.334
and so we're gonna be able to
go down Rifle Road out there,

01:12:35.334 --> 01:12:36.886
which is five kilometers,

01:12:36.886 --> 01:12:39.108
long, straight five kilometer road,

01:12:39.108 --> 01:12:41.304
which will help us go test the range

01:12:41.304 --> 01:12:44.798
of our system and really prove out

01:12:44.798 --> 01:12:46.039
that we can make it happen.

01:12:46.039 --> 01:12:49.125
So, to kind of highlight
some of the topics

01:12:49.125 --> 01:12:51.621
that you've touched on, Brandon,

01:12:51.621 --> 01:12:53.448
the base may not always work

01:12:53.448 --> 01:12:56.815
in the supply and demand
traditional economics,

01:12:56.815 --> 01:12:59.732
but for new technology deployments,

01:13:00.576 --> 01:13:02.328
it offers a tremendous opportunity,

01:13:02.328 --> 01:13:04.492
because the two things we struggle with

01:13:04.492 --> 01:13:07.437
as a commercial entity
outside are spectrum

01:13:07.437 --> 01:13:09.437
and controlled airspace.

01:13:10.476 --> 01:13:13.869
That's something that you
can directly influence,

01:13:13.869 --> 01:13:17.090
and so that provides a
great opportunity for us.

01:13:17.090 --> 01:13:17.923
- All right.

01:13:17.923 --> 01:13:18.756
Thanks, Chad.

01:13:18.756 --> 01:13:19.589
So, I want to come back to Jesse,

01:13:19.589 --> 01:13:22.986
and I want to touch more on this concept

01:13:22.986 --> 01:13:25.890
of collaborative market and
what you and I have worked on

01:13:25.890 --> 01:13:29.211
a lot over the last year and a
half in many different areas,

01:13:29.211 --> 01:13:33.629
but it ties back into what your
organization is really about

01:13:33.629 --> 01:13:36.012
and so I want you to spend
a little more time talking

01:13:36.012 --> 01:13:39.598
about that, and whether it
applies to UAS and the airspace

01:13:39.598 --> 01:13:41.388
or not, that's up to you.

01:13:41.388 --> 01:13:42.749
- Sure.

01:13:42.749 --> 01:13:43.582
Yeah.

01:13:43.582 --> 01:13:45.615
So the San Diego Regional
Economic Development Corporation's

01:13:45.615 --> 01:13:48.442
a non-profit, most major
cities have an entity like us

01:13:48.442 --> 01:13:52.320
and what our focus is on is
trying to help grow the economy

01:13:52.320 --> 01:13:53.778
looking at longer-term trends,

01:13:53.778 --> 01:13:55.803
and so we identify growth sectors

01:13:55.803 --> 01:13:57.409
within the regional economy,

01:13:57.409 --> 01:14:00.104
and then we think through
what other resources

01:14:00.104 --> 01:14:01.940
that are gonna be needed to support

01:14:01.940 --> 01:14:03.137
those particular industries.

01:14:03.137 --> 01:14:05.334
And as the aerospace and defense lead

01:14:05.334 --> 01:14:07.944
for that organization
for a period of time,

01:14:07.944 --> 01:14:10.218
that got me very involved in working

01:14:10.218 --> 01:14:11.658
with our local installations

01:14:11.658 --> 01:14:14.019
and thinking about them not just there's,

01:14:14.019 --> 01:14:16.688
communities are often dealing
with encroachment issues,

01:14:16.688 --> 01:14:18.853
and hopefully in most
communities it's not this way,

01:14:18.853 --> 01:14:21.438
but there tends to be a
kind of us and them battle

01:14:21.438 --> 01:14:23.742
with local communities where you're trying

01:14:23.742 --> 01:14:27.098
to mitigate issues between the community

01:14:27.098 --> 01:14:27.931
and not so much think about

01:14:27.931 --> 01:14:30.522
how you can be mutually
beneficial to each other.

01:14:30.522 --> 01:14:33.393
I think San Diego is unique
in that we're not like that

01:14:33.393 --> 01:14:34.502
with our military installations,

01:14:34.502 --> 01:14:36.678
that we generally as a
government, as government entities

01:14:36.678 --> 01:14:39.423
in these communities lean in
in working with the military,

01:14:39.423 --> 01:14:42.356
but frankly we saw that there
was a much bigger opportunity

01:14:42.356 --> 01:14:45.262
to use the installations
and use the technology

01:14:45.262 --> 01:14:47.258
that we're seeing from
companies within the region

01:14:47.258 --> 01:14:49.756
to try to create more of
a test bed environment

01:14:49.756 --> 01:14:52.308
between the installations
and the companies

01:14:52.308 --> 01:14:54.547
that we're working with that
are doing advanced robotics

01:14:54.547 --> 01:14:56.247
and doing advanced cellular,

01:14:56.247 --> 01:14:58.329
a variety of technologies
we know are having an impact

01:14:58.329 --> 01:15:00.535
on the military but we
needed a conduit in,

01:15:00.535 --> 01:15:04.576
and I think for us looking at how the city

01:15:04.576 --> 01:15:06.476
is approaching smart cities technology,

01:15:06.476 --> 01:15:10.231
where we're looking at
deploying GE Smart Lights

01:15:10.231 --> 01:15:14.116
that are gonna do things
around carbon emissions,

01:15:14.116 --> 01:15:15.703
doing things from traffic patterns,

01:15:15.703 --> 01:15:17.125
light management, all these things,

01:15:17.125 --> 01:15:19.525
but all that stops at the fence line,

01:15:19.525 --> 01:15:21.318
especially in San Diego
County with the number

01:15:21.318 --> 01:15:24.276
of military personnel we
have, it's not very effective.

01:15:24.276 --> 01:15:26.041
We have traffic patterns being created

01:15:26.041 --> 01:15:27.407
in and out of the bases,

01:15:27.407 --> 01:15:29.529
so that we are not two
separate communities.

01:15:29.529 --> 01:15:33.332
We are a very large region with
installations inside of us,

01:15:33.332 --> 01:15:35.530
and if cannot have
these technologies bleed

01:15:35.530 --> 01:15:37.794
over the fence line and
come back and forth,

01:15:37.794 --> 01:15:39.740
then we're not gonna be as
effective as we could be.

01:15:39.740 --> 01:15:43.275
And, so, through really
just reaching out to people

01:15:43.275 --> 01:15:45.212
at different installations
and trying to figure out

01:15:45.212 --> 01:15:48.728
who is open to engaging in
those types of conversations,

01:15:48.728 --> 01:15:50.318
I think that's how we got connected

01:15:50.318 --> 01:15:54.661
to Lieutenant Colonel Newell
at that point Major Newell

01:15:54.661 --> 01:15:57.363
and figuring out how can we find

01:15:57.363 --> 01:15:59.979
a way to bring companies like ModalAI,

01:15:59.979 --> 01:16:03.462
who have solutions that are
both gonna impact the community

01:16:03.462 --> 01:16:06.275
and have a real business growth
opportunity for our region,

01:16:06.275 --> 01:16:08.737
but also have insights for the military

01:16:08.737 --> 01:16:11.508
even if it's just watching
where the technology's moving

01:16:11.508 --> 01:16:12.967
for kind of a scouting purpose,

01:16:12.967 --> 01:16:16.347
but beyond that looking at how
do you shape the requirements

01:16:16.347 --> 01:16:17.954
for this technology that's being developed

01:16:17.954 --> 01:16:20.911
by companies who are
looking for first customers,

01:16:20.911 --> 01:16:23.017
who are trying to develop their MVP

01:16:23.017 --> 01:16:24.595
and who need those test environments.

01:16:24.595 --> 01:16:27.669
And, so, I think that's where
the partnership around IPP

01:16:27.669 --> 01:16:28.576
and what we've been doing

01:16:28.576 --> 01:16:30.168
with Lieutenant Colonel Newell here

01:16:30.168 --> 01:16:32.536
at Miramar has been particularly unique

01:16:32.536 --> 01:16:35.994
and a special added advantage
for us in this region

01:16:35.994 --> 01:16:38.983
is that we have great
companies who are one,

01:16:38.983 --> 01:16:41.258
often willing to work with the military

01:16:41.258 --> 01:16:42.311
in a variety of different ways,

01:16:42.311 --> 01:16:43.599
both directly and indirectly,

01:16:43.599 --> 01:16:44.805
but then are also,

01:16:44.805 --> 01:16:47.386
we found commanders at
the installation level

01:16:47.386 --> 01:16:48.894
and folks like Lieutenant
Colonel Newell who have been able

01:16:48.894 --> 01:16:51.179
to find individual commanders who want us

01:16:51.179 --> 01:16:53.097
to showcase the technology

01:16:53.097 --> 01:16:54.834
and work on the problem set with them,

01:16:54.834 --> 01:16:56.047
and I think that's something

01:16:56.047 --> 01:16:57.558
that we're gonna continue to cultivate

01:16:57.558 --> 01:16:59.540
whether it's in unmanned aerial vehicles

01:16:59.540 --> 01:17:04.540
or in other problem sets that
our organization works on.

01:17:04.570 --> 01:17:06.144
- And, so, I want to come back
to something we talked about

01:17:06.144 --> 01:17:10.136
in the last panel which is
earning our seat at the table

01:17:10.136 --> 01:17:12.568
for all this emerging technology.

01:17:12.568 --> 01:17:17.040
It's not enough to just
have collaborative dialogue.

01:17:17.040 --> 01:17:17.873
It's just like what we did

01:17:17.873 --> 01:17:19.243
with Qualcomm and autonomous vehicle,

01:17:19.243 --> 01:17:21.934
just like what we're doing
with Verizon for the 5G,

01:17:21.934 --> 01:17:23.870
earning our seat at the
table to better understand

01:17:23.870 --> 01:17:26.443
where that market is
going, where it's driving,

01:17:26.443 --> 01:17:28.269
and what are the applications.

01:17:28.269 --> 01:17:31.661
And that goes beyond just
some of these platforms.

01:17:31.661 --> 01:17:33.515
It's really not about the platforms.

01:17:33.515 --> 01:17:36.108
It's how are we gonna
manage our air traffic?

01:17:36.108 --> 01:17:38.528
How are we gonna have UAS
air traffic management?

01:17:38.528 --> 01:17:41.085
How does it blend in to the archaic system

01:17:41.085 --> 01:17:46.085
with which we optimize or
manage our airspace here today

01:17:46.482 --> 01:17:47.715
around this facility?

01:17:47.715 --> 01:17:50.658
And, certainly, how does it go forward

01:17:50.658 --> 01:17:53.020
into operations on the battlefield for us?

01:17:53.020 --> 01:17:57.030
We cannot solve that
in a vacuum inside DOD.

01:17:57.030 --> 01:17:58.190
We'll put a lot of money to it,

01:17:58.190 --> 01:18:00.584
and we'll solve it very ineffectively.

01:18:00.584 --> 01:18:02.405
But, through the
collaborative opportunities

01:18:02.405 --> 01:18:04.040
that we can leverage through these types

01:18:04.040 --> 01:18:07.022
of relationships is critical to it.

01:18:07.022 --> 01:18:10.439
And, so, we're actually with Andrew doing

01:18:12.119 --> 01:18:15.125
a counter UAS effort that was developed

01:18:15.125 --> 01:18:18.478
within his program and we
took the opposite turn,

01:18:18.478 --> 01:18:20.786
where we were focused on the battlefield

01:18:20.786 --> 01:18:23.489
with that capability, we
the collective Marine Corps,

01:18:23.489 --> 01:18:26.181
and then we looked at
facilities applications,

01:18:26.181 --> 01:18:27.848
so that we could better understand

01:18:27.848 --> 01:18:30.946
a more congested
environment how it applies.

01:18:30.946 --> 01:18:32.565
And, so, we don't have to
get into any specifics,

01:18:32.565 --> 01:18:34.626
but just talking about how we leverage

01:18:34.626 --> 01:18:37.299
all these insights,
all these opportunities

01:18:37.299 --> 01:18:39.270
to not only look at the use case,

01:18:39.270 --> 01:18:43.059
but also our mitigation of the threat

01:18:43.059 --> 01:18:44.589
that comes with the use cases.

01:18:44.589 --> 01:18:47.301
You have any thoughts on that, Andrew?

01:18:47.301 --> 01:18:48.134
- Absolutely.

01:18:48.134 --> 01:18:51.278
So, a lot to unpack there, right?

01:18:51.278 --> 01:18:53.835
Starting with how we get
our seat at the table.

01:18:53.835 --> 01:18:56.281
Industry in particular is
very transactionally driven.

01:18:56.281 --> 01:18:57.543
They are by their nature,

01:18:57.543 --> 01:19:00.834
that's how the entire
country is set up to operate.

01:19:00.834 --> 01:19:03.867
If you look at the history
of Defense Innovation Unit

01:19:03.867 --> 01:19:06.450
formerly DIUX, in experimental,

01:19:07.294 --> 01:19:09.177
they initially just
dropped a bunch of folks

01:19:09.177 --> 01:19:11.680
from the DOD out in
Silicon Valley and Boston

01:19:11.680 --> 01:19:13.710
and said go make friends effectively,

01:19:13.710 --> 01:19:15.801
like that was the mission.

01:19:15.801 --> 01:19:16.812
And they had meetings,

01:19:16.812 --> 01:19:17.668
and then they had more meetings,

01:19:17.668 --> 01:19:18.696
and then they had more meetings,

01:19:18.696 --> 01:19:22.278
and eventually people were
sick of talking to them.

01:19:22.278 --> 01:19:25.281
So, one of the things that we
as DOD need to understand is

01:19:25.281 --> 01:19:27.821
that you have to have
an end state in mind.

01:19:27.821 --> 01:19:30.284
You have to come to the
table willing to play

01:19:30.284 --> 01:19:33.587
and willing to actually
put money into these ideas,

01:19:33.587 --> 01:19:35.126
or people are just not gonna be interested

01:19:35.126 --> 01:19:36.054
in talking to you.

01:19:36.054 --> 01:19:37.345
Not that they don't want to,

01:19:37.345 --> 01:19:38.655
but they just have other things to do

01:19:38.655 --> 01:19:41.194
with their time, frankly.

01:19:41.194 --> 01:19:44.686
As far as pulling commercial
technology into the DOD

01:19:44.686 --> 01:19:48.699
and using it to solve
problems like counter UAS,

01:19:48.699 --> 01:19:51.011
which is actually not
separate and distinct

01:19:51.011 --> 01:19:53.640
from this problem set in general, right?

01:19:53.640 --> 01:19:55.397
It's a subset of airspace control

01:19:55.397 --> 01:19:58.659
that we don't have solved, frankly.

01:19:58.659 --> 01:20:00.560
There are things that
are starting to solve it,

01:20:00.560 --> 01:20:03.106
but it's a very, very nasty problem set

01:20:03.106 --> 01:20:05.606
when you start talking about
universal traffic management

01:20:05.606 --> 01:20:08.171
and non-cooperative actors
that may be operating

01:20:08.171 --> 01:20:10.761
within that very congested airspace

01:20:10.761 --> 01:20:15.287
that we expect to see
here in the near future.

01:20:15.287 --> 01:20:18.510
And the commercial actors
are working a lot harder

01:20:18.510 --> 01:20:21.191
on solving that problem
than we are, frankly.

01:20:21.191 --> 01:20:23.245
We've got a lot of really great OV-1s,

01:20:23.245 --> 01:20:24.303
but at the end of the day the folks

01:20:24.303 --> 01:20:25.644
that are gonna solve it are the ones

01:20:25.644 --> 01:20:28.555
that are gonna be making
thousands and thousands

01:20:28.555 --> 01:20:33.011
of deliveries a day in
a congested airspace.

01:20:33.011 --> 01:20:35.654
- And, so, I want to highlight that

01:20:35.654 --> 01:20:38.246
through the relationships
that are fostered here,

01:20:38.246 --> 01:20:39.559
we've actually taken the next step

01:20:39.559 --> 01:20:43.033
with Uber Elevate where we've
joined Army Research Lab

01:20:43.033 --> 01:20:45.094
in a CRADA, collaborative
research agreement,

01:20:45.094 --> 01:20:49.331
that they have with Uber
Elevate that kind of facilitates

01:20:49.331 --> 01:20:51.204
that dialogue to a greater extent.

01:20:51.204 --> 01:20:53.768
And similar to how we
focused on the relationship

01:20:53.768 --> 01:20:58.037
with Qualcomm, the
market maker if you will,

01:20:58.037 --> 01:21:01.246
not necessarily the vendor,
that's what we were watching,

01:21:01.246 --> 01:21:02.987
and Jesse and I were there last year

01:21:02.987 --> 01:21:05.640
at the Uber Elevate summit.

01:21:05.640 --> 01:21:08.213
We're watching this
whole ecosystem emerge,

01:21:08.213 --> 01:21:11.654
so in that video you saw
that you would have had

01:21:11.654 --> 01:21:13.850
to not only tie back to the customer

01:21:13.850 --> 01:21:15.640
and get them to the skyport,

01:21:15.640 --> 01:21:18.028
but what's the design of the skyport?

01:21:18.028 --> 01:21:20.194
You saw the traffic management having

01:21:20.194 --> 01:21:22.574
to take place with
multiple vertical take off

01:21:22.574 --> 01:21:25.755
and landing platforms coming in and out.

01:21:25.755 --> 01:21:27.896
How many people are supposed to be able

01:21:27.896 --> 01:21:29.896
to sit in that platform?

01:21:30.901 --> 01:21:34.568
You saw US Traffic
Management as I mentioned

01:21:35.625 --> 01:21:37.922
in the end the vendors themselves

01:21:37.922 --> 01:21:39.602
that are designing the platform.

01:21:39.602 --> 01:21:41.433
You know what's unique
in that relationship,

01:21:41.433 --> 01:21:42.915
and I can't think of another parallel is

01:21:42.915 --> 01:21:46.958
that Uber Elevate is not
designing the platforms.

01:21:46.958 --> 01:21:49.703
They're designing the specific standards

01:21:49.703 --> 01:21:53.867
by which those that are
designing the platforms can then

01:21:53.867 --> 01:21:56.327
basically be authorized
to fly in their network.

01:21:56.327 --> 01:22:00.734
And, so, the ability to
get that type of insight

01:22:00.734 --> 01:22:04.135
through these relationships
and better position ourselves

01:22:04.135 --> 01:22:05.468
into the future.

01:22:07.403 --> 01:22:08.236
I don't know that anyone else

01:22:08.236 --> 01:22:11.101
would have included urban air mobility

01:22:11.101 --> 01:22:13.727
in this type of event, frankly,

01:22:13.727 --> 01:22:15.349
because it looks too far out.

01:22:15.349 --> 01:22:17.107
It looks too much like it's Jetsons,

01:22:17.107 --> 01:22:19.089
and it's only through the
types of relationships

01:22:19.089 --> 01:22:21.592
that this body's been able to foster

01:22:21.592 --> 01:22:24.627
that helps us see what that
looks like in the future.

01:22:24.627 --> 01:22:25.708
So, as the group that's with us

01:22:25.708 --> 01:22:29.476
over the next two days looks at 2035,

01:22:29.476 --> 01:22:34.103
we actually can value what
that airspace looks like for us

01:22:34.103 --> 01:22:36.794
and what it's doing for the
movement of people and goods.

01:22:36.794 --> 01:22:40.711
And, so, Chad just thoughts
on the applications

01:22:42.274 --> 01:22:45.181
for what you're doing with
ModalAI in the commercial market,

01:22:45.181 --> 01:22:48.931
and where you're looking
to impact and shape.

01:22:50.057 --> 01:22:51.854
- Oh, yeah, well that's a great topic.

01:22:51.854 --> 01:22:56.107
It's broad though. (laughs)

01:22:56.107 --> 01:22:59.517
But, yeah, obviously what we see a lot of,

01:22:59.517 --> 01:23:01.235
well what's represented up here,

01:23:01.235 --> 01:23:04.177
but whether it's package delivery,

01:23:04.177 --> 01:23:08.651
there's certainly opportunities
to ease congestion

01:23:08.651 --> 01:23:10.998
and augment the existing infrastructure

01:23:10.998 --> 01:23:12.385
by replacing that with aerial

01:23:12.385 --> 01:23:15.468
'cause cities like San Diego are not,

01:23:16.775 --> 01:23:18.240
they're not laid out in a grid,

01:23:18.240 --> 01:23:20.704
and it's not that uniform and regular,

01:23:20.704 --> 01:23:23.178
and so there's lots of hills and mountains

01:23:23.178 --> 01:23:26.921
and things that can be traversed with air

01:23:26.921 --> 01:23:29.334
much more efficiently than on the ground.

01:23:29.334 --> 01:23:33.247
And then obviously there's
a lot of discussion

01:23:33.247 --> 01:23:36.344
in drone delivery for medical applications

01:23:36.344 --> 01:23:39.581
very, very recently it's Matternet right?

01:23:39.581 --> 01:23:41.227
But, on the other coast.

01:23:41.227 --> 01:23:42.060
Yeah.

01:23:42.060 --> 01:23:43.020
(laughs)

01:23:43.020 --> 01:23:44.176
- (speaks away from microphone)

01:23:44.176 --> 01:23:45.009
- What's that?
- They're here now.

01:23:45.009 --> 01:23:45.842
- Oh, okay good.

01:23:45.842 --> 01:23:48.842
And, so, with reasonably lightweight

01:23:50.648 --> 01:23:55.063
but high value cargo that's
pretty critical to aerial

01:23:55.063 --> 01:23:58.151
and unmanned is pursuing
the smaller use case,

01:23:58.151 --> 01:24:01.050
and then trying to bring
as much to that technology

01:24:01.050 --> 01:24:04.634
as we can and leverage
as much of that effort

01:24:04.634 --> 01:24:07.664
as we possibly can back
with the relationship

01:24:07.664 --> 01:24:12.247
through DIU to bring
best in class components

01:24:12.247 --> 01:24:14.397
bring best in class
components into the DOD

01:24:14.397 --> 01:24:17.226
and the group one applications
they're going after.

01:24:17.226 --> 01:24:18.875
- [Brandon] All right.

01:24:18.875 --> 01:24:21.654
- I can speak to that a little more.

01:24:21.654 --> 01:24:24.106
So, about a year and a half ago

01:24:24.106 --> 01:24:26.121
at Defense Innovation Unit
we started taking a look

01:24:26.121 --> 01:24:27.883
at the smart UAS market.

01:24:27.883 --> 01:24:29.693
A number of DOD stakeholders came to us

01:24:29.693 --> 01:24:32.662
saying effectively there are
no good solutions out there.

01:24:32.662 --> 01:24:35.231
It's very difficult to
acquire a good, small UAS

01:24:35.231 --> 01:24:38.593
that doesn't come direct from China.

01:24:38.593 --> 01:24:40.979
And, those that do, they have
their own security issues

01:24:40.979 --> 01:24:42.574
that we're not okay with
et cetera, et cetera,

01:24:42.574 --> 01:24:43.949
and so on and so forth.

01:24:43.949 --> 01:24:47.209
And we looked at the
market, and it was true.

01:24:47.209 --> 01:24:49.486
Not only could you not
buy good, small UAS,

01:24:49.486 --> 01:24:51.025
you also couldn't buy the components

01:24:51.025 --> 01:24:52.752
to assemble a good small UAS.

01:24:52.752 --> 01:24:54.390
There were tons of folks that were doing

01:24:54.390 --> 01:24:56.649
effectively hacked together,

01:24:56.649 --> 01:24:59.636
minimally viable products
in the S & T shops

01:24:59.636 --> 01:25:02.561
where they were building
quadcopters that were working,

01:25:02.561 --> 01:25:04.215
and they were proving that this thing

01:25:04.215 --> 01:25:05.968
could do the thing effectively,

01:25:05.968 --> 01:25:09.968
but it wasn't a truly
well-polished end product.

01:25:12.448 --> 01:25:14.923
And, the folks that were in the space

01:25:14.923 --> 01:25:17.415
of building small
quadcopters and small robots

01:25:17.415 --> 01:25:19.510
and things like that were
not the folks that were

01:25:19.510 --> 01:25:22.744
in the space of building very well-defined

01:25:22.744 --> 01:25:26.008
and well-documented and
well-performing integrated circuits

01:25:26.008 --> 01:25:30.292
that could do edge compute
and things of that nature.

01:25:30.292 --> 01:25:33.038
So, when we were looking
at okay, how do you develop

01:25:33.038 --> 01:25:36.432
a small UAS and even a small
robotics reference architecture

01:25:36.432 --> 01:25:39.204
for the future so that folks
in industry can take a look

01:25:39.204 --> 01:25:42.419
at all right, what do I
buy for my compute board

01:25:42.419 --> 01:25:44.776
and my communications stack?

01:25:44.776 --> 01:25:46.844
And, what software I put on it?

01:25:46.844 --> 01:25:48.223
ModalAI was very exciting to us

01:25:48.223 --> 01:25:50.973
because it's a very good solution

01:25:51.902 --> 01:25:53.171
for a fairly low price

01:25:53.171 --> 01:25:56.397
that you couldn't
necessarily get otherwise.

01:25:56.397 --> 01:25:58.331
You see one of these
vehicles that are coming out

01:25:58.331 --> 01:26:01.613
of China right now, one
manufacturer in particular,

01:26:01.613 --> 01:26:04.454
they're effectively flying cellphones

01:26:04.454 --> 01:26:07.331
and that's a very, very
hard thing to build,

01:26:07.331 --> 01:26:10.811
and in the majority of the US market,

01:26:10.811 --> 01:26:13.018
we've kind of lost the
ability to build that

01:26:13.018 --> 01:26:15.689
to an extent at the lower levels,

01:26:15.689 --> 01:26:17.419
and we're trying to get that back,

01:26:17.419 --> 01:26:20.586
and we're hoping to see more
and more things like that come

01:26:20.586 --> 01:26:23.727
into the hands of folks that
are building things for DOD.

01:26:23.727 --> 01:26:24.560
- All right, great.

01:26:24.560 --> 01:26:26.118
So we've got about 10
minutes for questions.

01:26:26.118 --> 01:26:29.724
So, Jess, if you want to
take one of these mics.

01:26:29.724 --> 01:26:31.807
Do we have any questions?

01:26:42.489 --> 01:26:44.449
- [Male Audience Member]
So, very exciting.

01:26:44.449 --> 01:26:48.569
Just your experience with
the FAA, how are they doin'?

01:26:48.569 --> 01:26:53.247
Because it's a lot of opportunity
until you regulate it.

01:26:53.247 --> 01:26:56.872
So, the ground domain, air domain.

01:26:56.872 --> 01:26:59.087
The video shows people
coming out all over the place

01:26:59.087 --> 01:27:00.718
until it gets regulated.

01:27:00.718 --> 01:27:02.146
So, and that comes out of fear.

01:27:02.146 --> 01:27:05.854
So, the regulatory
commission that controls

01:27:05.854 --> 01:27:08.742
and can provide safe access
is either gonna handle it,

01:27:08.742 --> 01:27:10.253
or they're gonna lock it down.

01:27:10.253 --> 01:27:12.409
So, can you share some
thoughts on that please?

01:27:12.409 --> 01:27:14.492
- Sure, to your question,

01:27:15.697 --> 01:27:18.714
one of the things right now
it is locked down, right?

01:27:18.714 --> 01:27:21.131
So, from the UAS marketplace,

01:27:24.369 --> 01:27:27.575
we started it from a position
of you can't do anything,

01:27:27.575 --> 01:27:28.728
and now we're working our way

01:27:28.728 --> 01:27:30.653
towards you can do certain things

01:27:30.653 --> 01:27:31.937
in certain airspaces

01:27:31.937 --> 01:27:33.494
with limited exposure.

01:27:33.494 --> 01:27:35.267
You have to get waivers every single time,

01:27:35.267 --> 01:27:37.390
every single airspace,
every single mission,

01:27:37.390 --> 01:27:40.802
and so we're continually
kind of building with the FAA

01:27:40.802 --> 01:27:43.041
what are the risk mitigations
that need to be built in

01:27:43.041 --> 01:27:44.426
from an operational standpoint,

01:27:44.426 --> 01:27:45.713
from a communications standpoint,

01:27:45.713 --> 01:27:48.331
from a command, cyber, all of those things

01:27:48.331 --> 01:27:49.322
in order to start saying,

01:27:49.322 --> 01:27:51.976
"Okay Uber, you have
permission to deliver food

01:27:51.976 --> 01:27:54.349
"in San Diego, LA, San
Francisco, Boston, Chicago,

01:27:54.349 --> 01:27:56.557
"wherever you want to do it, go."

01:27:56.557 --> 01:27:58.058
And, we don't need to come check in on you

01:27:58.058 --> 01:28:00.226
every time you want to go fly.

01:28:00.226 --> 01:28:02.637
Right now, we're not there.

01:28:02.637 --> 01:28:05.321
Part of what IPP was
doing that was different

01:28:05.321 --> 01:28:08.573
than some of these other
UAS test environment cases,

01:28:08.573 --> 01:28:13.073
those were set up in Alaska,
in the deserts in Nevada,

01:28:14.354 --> 01:28:17.237
those were more about airspace worthiness,

01:28:17.237 --> 01:28:19.756
testing the core
technology of the aircraft,

01:28:19.756 --> 01:28:23.338
but not how do you actually
do this where the customer is?

01:28:23.338 --> 01:28:25.326
Amazon, Uber all these guys,

01:28:25.326 --> 01:28:27.332
they don't wanna go fly
in the desert in Nevada.

01:28:27.332 --> 01:28:31.409
No one's getting Prime delivered
in Fargo at a regular rate.

01:28:31.409 --> 01:28:33.414
They want to do that here.

01:28:33.414 --> 01:28:34.672
They want to do that in major cities.

01:28:34.672 --> 01:28:36.358
And, so, that's the
difference what IPP is trying

01:28:36.358 --> 01:28:37.712
to push the envelope on.

01:28:37.712 --> 01:28:41.759
So, to answer your question,
the FAA's making progress.

01:28:41.759 --> 01:28:44.098
And, I think the industry
is certainly very eager

01:28:44.098 --> 01:28:47.433
to demonstrate that the
technology has come a long way.

01:28:47.433 --> 01:28:50.422
We've had many meetings with
our telecommunications partners

01:28:50.422 --> 01:28:52.840
in IPP sitting down with some

01:28:52.840 --> 01:28:54.650
of the chief technology officers

01:28:54.650 --> 01:28:57.711
within the FAA's Unmanned
Systems Integration group,

01:28:57.711 --> 01:28:59.368
showing them data that they've collected

01:28:59.368 --> 01:29:02.938
from real-time flight
operations on 4G networks,

01:29:02.938 --> 01:29:05.800
showing the reliability of the C2 link

01:29:05.800 --> 01:29:07.205
on current cellular networks,

01:29:07.205 --> 01:29:10.307
let alone what's capable
for future 5G networks.

01:29:10.307 --> 01:29:11.864
And, they don't know that.

01:29:11.864 --> 01:29:13.241
They didn't have that information.

01:29:13.241 --> 01:29:15.142
So, there's an education component

01:29:15.142 --> 01:29:17.512
of demonstrating the level
of safety and reliability,

01:29:17.512 --> 01:29:21.172
of the technology, that IPP is
trying to enable for the FAA.

01:29:21.172 --> 01:29:26.172
They are safety first, that is
their mindset understandably.

01:29:26.963 --> 01:29:30.268
And, so, it's a whole
evolution for that organization

01:29:30.268 --> 01:29:33.578
to think about does 10 to the minus nine

01:29:33.578 --> 01:29:35.865
as a safety standard make sense

01:29:35.865 --> 01:29:38.068
for every type of UAS operation

01:29:38.068 --> 01:29:39.265
in every single environment,

01:29:39.265 --> 01:29:42.629
or should we change how much
risk we're willing to accept?

01:29:42.629 --> 01:29:46.253
How much do we evaluate
what the mission is?

01:29:46.253 --> 01:29:47.862
If we can guarantee that
we're gonna go save a life

01:29:47.862 --> 01:29:51.994
'cause I'm delivering
valuable blood to a hospital,

01:29:51.994 --> 01:29:54.308
and do we still care that
it's 10 to the minus seven

01:29:54.308 --> 01:29:56.011
instead of 10 to the minus nine that

01:29:56.011 --> 01:29:58.260
that drone might come down?

01:29:58.260 --> 01:29:59.674
So, those are the kind
of questions the FAA

01:29:59.674 --> 01:30:00.507
is grappling with.

01:30:00.507 --> 01:30:02.086
It's very challenging.

01:30:02.086 --> 01:30:02.919
But, I think they've
really been open to working

01:30:02.919 --> 01:30:07.468
with industry to help
solve this problem for them

01:30:07.468 --> 01:30:10.555
because it's not gonna be managed on

01:30:10.555 --> 01:30:13.788
The FAA's not gonna have ground
control, air traffic towers.

01:30:13.788 --> 01:30:16.281
In the same way it's gonna
have to be automated.

01:30:16.281 --> 01:30:17.386
It's gonna have to be network.

01:30:17.386 --> 01:30:18.771
It's gonna have to be a federated system,

01:30:18.771 --> 01:30:21.247
and there's gonna have to be a
lot more technology providers

01:30:21.247 --> 01:30:25.008
involved in that solution than
maybe what they're used to

01:30:25.008 --> 01:30:27.308
when there's a few controlled primes,

01:30:27.308 --> 01:30:28.784
and they can manage the
manufacturing process,

01:30:28.784 --> 01:30:30.638
and they can kinda work through.

01:30:30.638 --> 01:30:32.788
This is a different ecosystem.

01:30:32.788 --> 01:30:34.261
And, the last thing I'll say is,

01:30:34.261 --> 01:30:38.011
when you look at the
number of registered drones

01:30:38.011 --> 01:30:39.961
through DroneZone, it's like two

01:30:39.961 --> 01:30:41.681
and a half million registered drones.

01:30:41.681 --> 01:30:44.035
Those are hobbyists,
commercial, everybody.

01:30:44.035 --> 01:30:46.595
The FAA is right now
for certified aircraft

01:30:46.595 --> 01:30:49.066
has got about 350,000 certified aircraft.

01:30:49.066 --> 01:30:50.498
Not all those are flying.

01:30:50.498 --> 01:30:52.075
Those are your Cessnas that are parked

01:30:52.075 --> 01:30:54.215
that haven't been flown
in 30 years, everything.

01:30:54.215 --> 01:30:55.825
So, the scale of this industry,

01:30:55.825 --> 01:30:57.643
and it's not even really live yet,

01:30:57.643 --> 01:30:59.767
is completely different than
what the FAA is used to,

01:30:59.767 --> 01:31:02.590
but I think they're
working very aggressively

01:31:02.590 --> 01:31:04.507
to lean on industry to
help them figure out

01:31:04.507 --> 01:31:06.090
the right solution.

01:31:07.923 --> 01:31:09.390
- So, I'll just pile on to that,

01:31:09.390 --> 01:31:11.187
and first I would agree
that the FAA actually

01:31:11.187 --> 01:31:14.941
has been very forward
leaning from what I've seen,

01:31:14.941 --> 01:31:18.548
although technology is
outpacing policy in this case.

01:31:18.548 --> 01:31:21.805
And, I think as the curve
of technology acceleration

01:31:21.805 --> 01:31:23.217
just gets more and more vertical,

01:31:23.217 --> 01:31:25.983
we're gonna see that in
more and more sectors.

01:31:25.983 --> 01:31:28.938
And in many cases, in many instances,

01:31:28.938 --> 01:31:31.348
it's a case of want versus need.

01:31:31.348 --> 01:31:35.644
The FAA doesn't have to allow
you to get a burrito delivered

01:31:35.644 --> 01:31:39.335
to your doorstep via quadcopter right now.

01:31:39.335 --> 01:31:42.040
In fact, we as a nation
have basically mandated

01:31:42.040 --> 01:31:43.965
that they be very, very restrictive,

01:31:43.965 --> 01:31:45.073
which is a good thing,

01:31:45.073 --> 01:31:47.800
but we see them stepping forward,

01:31:47.800 --> 01:31:50.446
and we do see that changing.

01:31:50.446 --> 01:31:53.072
Interestingly enough, the largest
autonomous delivery system

01:31:53.072 --> 01:31:56.608
in the world, one of the
most advanced systems

01:31:56.608 --> 01:31:59.488
that you can find is in Rwanda,

01:31:59.488 --> 01:32:01.271
and it's a company called Zipline,

01:32:01.271 --> 01:32:04.564
who's doing almost all of the
delivery of blood and plasma

01:32:04.564 --> 01:32:06.181
in the entire country.

01:32:06.181 --> 01:32:07.515
It's happening by drone.

01:32:07.515 --> 01:32:09.280
It comes from the
capital, and it goes out,

01:32:09.280 --> 01:32:11.925
and 30 minutes later a couple
of units of blood show up

01:32:11.925 --> 01:32:13.787
at an outlying small hospital

01:32:13.787 --> 01:32:17.151
and go to a mother who's delivery a baby.

01:32:17.151 --> 01:32:18.999
Incredibly impressive system,

01:32:18.999 --> 01:32:22.706
more reliable than many
of our aviation assets

01:32:22.706 --> 01:32:23.705
in the United States.

01:32:23.705 --> 01:32:24.894
But, we just don't have the policy

01:32:24.894 --> 01:32:29.250
to enable the instantiation
of something like that here.

01:32:29.250 --> 01:32:31.668
I would argue that we as a service

01:32:31.668 --> 01:32:33.612
have a different mandate than the FAA,

01:32:33.612 --> 01:32:35.752
and we're probably a good organization

01:32:35.752 --> 01:32:38.127
for many of these folks to partner with

01:32:38.127 --> 01:32:40.370
because we are a little
bit more risk tolerant.

01:32:40.370 --> 01:32:41.636
I wouldn't say we're very risk tolerant.

01:32:41.636 --> 01:32:43.482
I would argue that we should try

01:32:43.482 --> 01:32:45.887
to be more risk tolerant in some cases.

01:32:45.887 --> 01:32:50.443
But, we're certainly more
risk tolerant than the FAA,

01:32:50.443 --> 01:32:53.492
especially when it comes
to pushing the boundary

01:32:53.492 --> 01:32:57.108
of feeling out what the
continuously evolving character

01:32:57.108 --> 01:32:57.941
of war is.

01:33:00.259 --> 01:33:01.283
- Sir.

01:33:01.283 --> 01:33:02.116
- [Male Audience Member] I got a question.

01:33:02.116 --> 01:33:04.553
It's more than just the FAA
dealing with this stuff.

01:33:04.553 --> 01:33:06.748
The FCC has got designated channels

01:33:06.748 --> 01:33:08.386
for ground-to-ground, air-to-ground,

01:33:08.386 --> 01:33:10.212
and air-to-air communications.

01:33:10.212 --> 01:33:12.352
Is there any discussion about building out

01:33:12.352 --> 01:33:15.435
a dedicated drone level of activities

01:33:16.826 --> 01:33:20.361
in the cellular frequencies versus

01:33:20.361 --> 01:33:25.194
the helicopter type stuff
that's already private channels?

01:33:26.527 --> 01:33:28.074
- Yeah, we can speak a little bit to that.

01:33:28.074 --> 01:33:31.124
We're under contract right now through DIU

01:33:31.124 --> 01:33:35.874
to build a prototype cellular-based
system for small UAS.

01:33:37.362 --> 01:33:39.890
And, it would be ideally within

01:33:39.890 --> 01:33:42.785
three to five kilometer
range communication.

01:33:42.785 --> 01:33:46.484
So single controller, single pilot,

01:33:46.484 --> 01:33:49.327
multiple vehicles would
be the big advantage.

01:33:49.327 --> 01:33:52.172
The other advantage would
be you could take any device

01:33:52.172 --> 01:33:53.959
right out of your pocket
and connect to the system

01:33:53.959 --> 01:33:57.815
and also be communicating with
any of the vehicles deployed.

01:33:57.815 --> 01:34:00.289
Actually, no, this would be
a portable cellular network

01:34:00.289 --> 01:34:05.155
in DOD spectrums, the 1800
MHz band specifically.

01:34:05.155 --> 01:34:05.988
- [Male Audience Member] Roger that.

01:34:05.988 --> 01:34:08.354
So, currently the cellular
companies can only go so high

01:34:08.354 --> 01:34:11.274
in their elevation of
transmitting and receiving signals

01:34:11.274 --> 01:34:14.197
in a designated allocation
for ground-to-ground,

01:34:14.197 --> 01:34:15.990
what you're saying is
using military spectrum

01:34:15.990 --> 01:34:18.500
with the authorization not so much

01:34:18.500 --> 01:34:21.037
as the 5G millimeter wave to be enabled

01:34:21.037 --> 01:34:23.754
to get through different
types of climate activities

01:34:23.754 --> 01:34:25.835
to ensure the reliability
of communications

01:34:25.835 --> 01:34:29.918
with the cellular function
is higher reliability?

01:34:31.546 --> 01:34:32.379
- Yes.

01:34:39.826 --> 01:34:42.159
- Question here in the back.

01:34:46.393 --> 01:34:47.446
- [Male Audience Member]
Great presentations.

01:34:47.446 --> 01:34:48.976
I really appreciate the information.

01:34:48.976 --> 01:34:51.345
My question is getting back to the point

01:34:51.345 --> 01:34:52.634
somebody made about China

01:34:52.634 --> 01:34:54.118
and some of the manufacturing advantages

01:34:54.118 --> 01:34:55.430
that they have.

01:34:55.430 --> 01:34:58.996
How much of a disadvantage
or what are your thoughts

01:34:58.996 --> 01:35:01.495
on the challenges that we
face in the United States

01:35:01.495 --> 01:35:04.884
with the regulation that we
have with respect to data

01:35:04.884 --> 01:35:07.788
and manufacturing
practices and other things

01:35:07.788 --> 01:35:12.371
in the competition with China
in developing technology?

01:35:13.231 --> 01:35:15.792
- Well, as the new director
of World Trade Center

01:35:15.792 --> 01:35:19.001
in San Diego I think this
is right up your alley.

01:35:19.001 --> 01:35:20.234
- Well, it's probably better for Chad

01:35:20.234 --> 01:35:23.858
'cause their business model
is addressing this problem,

01:35:23.858 --> 01:35:26.108
but I think that there are,

01:35:27.112 --> 01:35:27.972
when you look at the companies

01:35:27.972 --> 01:35:30.243
that are involved in our program,

01:35:30.243 --> 01:35:33.540
they're all either American or European.

01:35:33.540 --> 01:35:36.204
We have Matternet which
is a Swiss-based company,

01:35:36.204 --> 01:35:37.671
owned by Mercedes-Benz.

01:35:37.671 --> 01:35:39.617
But, our public safety CONOP,

01:35:39.617 --> 01:35:41.322
which involves Chula
Vista Police Department

01:35:41.322 --> 01:35:43.824
using drones to respond to 911 calls

01:35:43.824 --> 01:35:46.659
and provide live camera feed back

01:35:46.659 --> 01:35:47.837
to the responding officers

01:35:47.837 --> 01:35:49.532
to provide better operational
intelligence to them,

01:35:49.532 --> 01:35:51.471
they're flying DGI.

01:35:51.471 --> 01:35:53.194
And, it's because it's the cheapest,

01:35:53.194 --> 01:35:55.860
most reliable aircraft that they can find.

01:35:55.860 --> 01:35:58.215
So, there's a lot of law
enforcement right now,

01:35:58.215 --> 01:36:00.088
and a lot of other public safety entities

01:36:00.088 --> 01:36:04.721
that are flying equipment
that DOD has broadly banned.

01:36:04.721 --> 01:36:06.061
And, they know that.

01:36:06.061 --> 01:36:08.057
They're just still choosing that the risk

01:36:08.057 --> 01:36:11.327
and they've had, this is being used,

01:36:11.327 --> 01:36:13.335
they've had 14 arrests directly related

01:36:13.335 --> 01:36:15.144
to the drone operations
that have been live

01:36:15.144 --> 01:36:17.835
as part of IPP so far, and so
it's assisted in other cases.

01:36:17.835 --> 01:36:20.736
So, they have all kinds of very
strict evidentiary standards

01:36:20.736 --> 01:36:22.526
on what's happening with that data

01:36:22.526 --> 01:36:25.730
as it comes off, where it's
going in their cloud storage,

01:36:25.730 --> 01:36:29.068
and we've mentioned to
them this is a concern

01:36:29.068 --> 01:36:32.107
about potentially any
backdoor issues with the DGI

01:36:32.107 --> 01:36:33.962
that have been expressed by the DOD,

01:36:33.962 --> 01:36:35.275
and it's kind of like sort of,

01:36:35.275 --> 01:36:36.949
but it seems like it's too far away

01:36:36.949 --> 01:36:37.959
for them to deal with,

01:36:37.959 --> 01:36:42.203
and I think that a lot of those
agencies would pivot quickly

01:36:42.203 --> 01:36:43.739
to an American product,

01:36:43.739 --> 01:36:45.199
that was American made,

01:36:45.199 --> 01:36:46.517
or an allied nation product

01:36:46.517 --> 01:36:50.873
that they knew was at a
competitive price point.

01:36:50.873 --> 01:36:51.765
Because they were still in the process

01:36:51.765 --> 01:36:54.606
of demonstrating the added value.

01:36:54.606 --> 01:36:56.839
I'll tell you right now Chula Vista PD

01:36:56.839 --> 01:36:58.909
early on was trying to
scrap together resources

01:36:58.909 --> 01:37:01.390
from their foundation to
make this project happen.

01:37:01.390 --> 01:37:03.324
Now, they're at the point
where they're saying,

01:37:03.324 --> 01:37:05.657
"Do we really need to
buy two new SWAT cars?

01:37:05.657 --> 01:37:07.502
"We could buy 30 drones

01:37:07.502 --> 01:37:10.369
"because the add value
is exponentially better

01:37:10.369 --> 01:37:11.202
"for what we're getting."

01:37:11.202 --> 01:37:14.156
But, until you have these
live, real-world demonstrations

01:37:14.156 --> 01:37:16.298
taking place where you
can really see the impact,

01:37:16.298 --> 01:37:18.332
it's harder for agencies to figure out

01:37:18.332 --> 01:37:22.111
where they're gonna spend their funds.

01:37:22.111 --> 01:37:24.396
- So, we are working
on a number of programs

01:37:24.396 --> 01:37:26.845
that are not just advancing components,

01:37:26.845 --> 01:37:28.469
like the one that we're running with Chad,

01:37:28.469 --> 01:37:31.681
but also actually building
full up small drones

01:37:31.681 --> 01:37:34.045
to address this problem.

01:37:34.045 --> 01:37:37.030
And, yeah, when the police
went to buy their drones,

01:37:37.030 --> 01:37:39.012
they likely found that it was
not only the cheapest drone,

01:37:39.012 --> 01:37:41.081
but probably the best
drone that they could find.

01:37:41.081 --> 01:37:43.419
And, not by a small margin.

01:37:43.419 --> 01:37:45.212
Both anecdotally and empirically,

01:37:45.212 --> 01:37:47.514
they're just very, very good,

01:37:47.514 --> 01:37:50.368
which is not great news
for the US industrial base,

01:37:50.368 --> 01:37:52.451
but we are working on it.

01:37:53.660 --> 01:37:54.876
- I think one of the
questions was what are some

01:37:54.876 --> 01:37:57.989
of the manufacturing
challenges versus China.

01:37:57.989 --> 01:38:01.119
I'd say costs and that's understood.

01:38:01.119 --> 01:38:04.278
I think for the customers
that care about US built

01:38:04.278 --> 01:38:06.699
the cost isn't prohibitive.

01:38:06.699 --> 01:38:08.199
I think it's fine.

01:38:09.326 --> 01:38:11.336
On our side what we see
is just establishing

01:38:11.336 --> 01:38:14.718
that supply chain where certain components

01:38:14.718 --> 01:38:17.747
in Shenzhen literally
just fall out of the sky,

01:38:17.747 --> 01:38:19.210
or out of a window of a building

01:38:19.210 --> 01:38:20.917
as they go around with a net.

01:38:20.917 --> 01:38:23.130
It's unbelievable and for
us we have to struggle.

01:38:23.130 --> 01:38:24.503
We're up in the middle of the night,

01:38:24.503 --> 01:38:26.255
yelling at people on the phone.

01:38:26.255 --> 01:38:28.306
It's impossible to get certain components.

01:38:28.306 --> 01:38:32.806
So that would be where some
of the challenges come in,

01:38:33.676 --> 01:38:35.657
just that ecosystem
which hopefully you know,

01:38:35.657 --> 01:38:38.652
the World Trade Center
efforts help advance,

01:38:38.652 --> 01:38:40.569
but this ecosystem in the US

01:38:40.569 --> 01:38:43.402
whether it's degenerated over time

01:38:45.160 --> 01:38:46.509
or however you want to think about it,

01:38:46.509 --> 01:38:48.005
but in China there's things

01:38:48.005 --> 01:38:50.801
like supply of components
that's just much, much,

01:38:50.801 --> 01:38:52.301
much, much easier.

01:38:55.208 --> 01:38:56.875
- One more question.

01:39:03.477 --> 01:39:05.586
I just highlight that kind of tying

01:39:05.586 --> 01:39:09.419
in this last responses
to the question is that

01:39:11.916 --> 01:39:14.417
we have other roles to
play as the military

01:39:14.417 --> 01:39:15.516
and the Marine Corps,

01:39:15.516 --> 01:39:19.916
and sometimes the signal
that we set whenever we see

01:39:19.916 --> 01:39:22.263
the gaps in the industry
base and the vulnerabilities

01:39:22.263 --> 01:39:26.595
that it presents to us
we can play that role,

01:39:26.595 --> 01:39:28.659
and we've done it in the past.

01:39:28.659 --> 01:39:30.702
We the Marine Corps are too small

01:39:30.702 --> 01:39:32.486
and under-resourced to be the leader

01:39:32.486 --> 01:39:35.006
in playing that role,
creating that whole signal

01:39:35.006 --> 01:39:37.350
that's gonna unlock industry

01:39:37.350 --> 01:39:39.476
and the opportunity for industry.

01:39:39.476 --> 01:39:41.295
But, what we can do is events like this

01:39:41.295 --> 01:39:43.958
where it really highlights
why it's critical,

01:39:43.958 --> 01:39:46.135
why it's not just
critical to our use cases

01:39:46.135 --> 01:39:48.324
and our applications and the mobility,

01:39:48.324 --> 01:39:49.638
moving people and goods around bases

01:39:49.638 --> 01:39:51.921
but also the second
and third order effects

01:39:51.921 --> 01:39:53.419
to the nation.

01:39:53.419 --> 01:39:54.778
It's critical as well.

01:39:54.778 --> 01:39:56.928
And, so, we can't do that

01:39:56.928 --> 01:39:59.574
without these guys joining us here

01:39:59.574 --> 01:40:02.516
and without you being
here talkin' about this

01:40:02.516 --> 01:40:05.817
with us, and so we're gonna break here.

01:40:05.817 --> 01:40:08.920
We're gonna go back
out to the exhibit area

01:40:08.920 --> 01:40:11.604
for about an hour and then
we'll have panel four,

01:40:11.604 --> 01:40:14.698
electric vehicles, and then
we'll have some closing remarks.

01:40:14.698 --> 01:40:16.893
And, so, again, appreciate
you all being here,

01:40:16.893 --> 01:40:18.894
and thank our panelists please.

01:40:18.894 --> 01:40:21.144
(applause)