WEBVTT

00:04.320 --> 00:06.739
Now like to introduce Mr Sean Lyman

00:06.750 --> 00:08.472
moderator for the digital data

00:08.472 --> 00:10.528
transformation , reverse engineering

00:10.528 --> 00:13.250
and data rights panel . Mister Lyman is

00:13.260 --> 00:15.427
in transition to his new assignment as

00:15.427 --> 00:17.819
the Deputy CEO for Air Force Security

00:17.829 --> 00:20.899
Assistance and Cooperation . AAC has

00:20.909 --> 00:23.131
nine divisions whose overall mission is

00:23.131 --> 00:25.187
directly linked to the Department of

00:25.187 --> 00:27.469
Defense and Air Force priorities to

00:27.479 --> 00:30.159
strengthen relationships with us allies

00:30.170 --> 00:32.950
and international partners . In his new

00:32.959 --> 00:34.681
role , he delivers direction ,

00:34.681 --> 00:36.737
leadership and management of the Air

00:36.737 --> 00:39.830
Force's 230 plus billion dollars of

00:39.840 --> 00:42.630
security assistance , deporting foreign

00:42.639 --> 00:45.360
military sales to 115 plus

00:45.369 --> 00:47.700
international partners countries in

00:47.709 --> 00:49.487
support of our national defense

00:49.487 --> 00:52.650
strategy . Mr Lyman's last assignment

00:52.659 --> 00:54.492
was the lead for digital product

00:54.492 --> 00:56.492
support in the office of the Deputy

00:56.492 --> 00:58.548
Assistant Secretary of the Air Force

00:58.548 --> 01:00.770
for logistics and product support where

01:00.770 --> 01:02.826
he was responsible for oversight and

01:02.826 --> 01:04.659
the integration of the Air Force

01:04.659 --> 01:06.881
digital Transformation efforts . Please

01:06.881 --> 01:08.010
welcome Mr Lyman .

01:13.519 --> 01:15.686
Hey , thank you , Chris . I appreciate

01:15.686 --> 01:17.797
it . Uh I'm really excited to be here

01:17.797 --> 01:19.908
and be a part of this panel . Uh What

01:19.908 --> 01:22.199
an honor to director Chief Brown and as

01:22.209 --> 01:24.220
a logistician chief Brown really ,

01:24.230 --> 01:26.459
really made my day today because he was

01:26.470 --> 01:28.470
talking in multiple times about the

01:28.470 --> 01:30.637
importance of logistics and how we are

01:30.637 --> 01:32.748
changing , how we need to think about

01:32.748 --> 01:34.859
logistics and CC A , how we are going

01:34.859 --> 01:36.581
to support our war fighter and

01:36.581 --> 01:38.800
maintenance . You talk about change ,

01:38.809 --> 01:40.769
that is change . I'm a career

01:40.779 --> 01:42.989
logistician , having discussions and

01:43.000 --> 01:45.000
having senior leadership at the Air

01:45.000 --> 01:46.889
Force make that part of a keynote

01:46.889 --> 01:49.056
address to an audience such as this is

01:49.056 --> 01:51.339
just outstanding . It's great to see .

01:52.040 --> 01:54.500
This panel is I I like to call it the

01:54.510 --> 01:56.621
kitchen sink panel . We're covering a

01:56.621 --> 01:58.788
lot of things up here . You can see we

01:58.788 --> 02:01.690
have uh the data transformation ,

02:01.699 --> 02:04.199
reverse engineering and data rights and

02:04.209 --> 02:06.376
all that ties . So importantly to what

02:06.376 --> 02:08.718
we are talking about with Keith Brown

02:08.729 --> 02:10.951
was talking about how we're changing as

02:10.951 --> 02:12.896
an Air Force . We're going to talk

02:12.896 --> 02:15.118
about where A F MC is going , where the

02:15.118 --> 02:17.340
Air Force is going to implement digital

02:17.340 --> 02:19.669
tool sets change , how we accelerate

02:19.679 --> 02:21.901
our products . And we're very fortunate

02:21.901 --> 02:24.335
to have the panel we have here , which

02:24.345 --> 02:26.764
is really a very diverse panel . It's

02:26.774 --> 02:29.095
not focused one specific area , one

02:29.104 --> 02:31.414
specific competency . And we did that

02:31.425 --> 02:33.203
on purpose because for us to be

02:33.203 --> 02:35.314
successful , we have to work together

02:35.314 --> 02:37.324
as an integrated team . And so we

02:37.335 --> 02:39.964
structured this to get the perspective

02:39.975 --> 02:41.975
from different stakeholders . And I

02:41.975 --> 02:43.642
think that will really make a

02:43.642 --> 02:45.419
difference for us as a group to

02:45.419 --> 02:47.419
understand what needs to change and

02:47.419 --> 02:49.586
what we have to go after to be able to

02:49.586 --> 02:51.753
make that difference . It can continue

02:51.753 --> 02:54.086
to build the world's greatest air force .

02:54.086 --> 02:56.031
So I'm gonna let our panel members

02:56.031 --> 02:58.031
introduce themselves to make this a

02:58.031 --> 03:00.197
little easier . And I'll start uh with

03:00.197 --> 02:59.820
Doctor Tim Mesner right here from Air

02:59.830 --> 03:02.052
Force Sustainment Center . Doctor Mex .

03:02.052 --> 03:04.240
Hey , everyone . Uh Tim Mesner , proud

03:04.250 --> 03:06.528
member of Air Force Sustainment Center .

03:06.528 --> 03:09.130
I serve as the division chief for the

03:09.139 --> 03:11.779
center , it , office there at uh

03:11.789 --> 03:15.690
headquarters uh A FSC sir .

03:16.669 --> 03:18.836
Yeah , my name is Paul Ray . I'm the B

03:18.839 --> 03:21.580
52 chief engineer from the B 52 program

03:21.589 --> 03:24.500
office . And uh I've been the uh chief

03:24.509 --> 03:26.949
engineer for about 1/6 of the age

03:26.960 --> 03:29.300
model's life . I'll let you do the math .

03:31.460 --> 03:33.516
All right afternoon , everybody . My

03:33.516 --> 03:35.682
name is Kyle Hearst . I'm the chief of

03:35.682 --> 03:37.904
the Digital Transformation Office uh on

03:37.904 --> 03:39.904
General Richardson's staff , uh the

03:39.904 --> 03:42.071
Material Command and I'm Ryan Tinner .

03:42.071 --> 03:44.199
I'm the head of the Digital

03:44.210 --> 03:46.543
Transformation office for North of Drum .

03:46.543 --> 03:48.488
And it's an office that we started

03:48.488 --> 03:50.599
about two years ago . Uh reporting up

03:50.599 --> 03:52.821
to the CEO and I partnered closely with

03:52.821 --> 03:54.932
the Chief information officer as well

03:54.932 --> 03:56.932
as operations here to drive digital

03:56.932 --> 03:59.154
transformation forward . Hi there , I'm

03:59.154 --> 04:01.154
Adriana Lid . I'm associate general

04:01.154 --> 04:03.850
counsel at Lockheed Martin . Um I am an

04:03.860 --> 04:06.210
engineer and patent lawyer by training ,

04:06.220 --> 04:09.240
uh joined Lockheed Martin uh in 2010

04:09.770 --> 04:12.600
and work with a lot of data rights and

04:12.610 --> 04:14.721
technology related questions of which

04:14.721 --> 04:16.610
there are many , both legally and

04:16.610 --> 04:19.420
technologically speaking . Good

04:19.429 --> 04:21.429
afternoon , everyone . I'm Gretchen

04:21.429 --> 04:23.096
Stewart . Uh I work for Intel

04:23.096 --> 04:24.929
Corporation . I'm the chief data

04:24.929 --> 04:27.151
scientist for our public sector . I was

04:27.151 --> 04:29.040
told that I need to probably be a

04:29.040 --> 04:28.950
little more specific that I'm not in

04:28.959 --> 04:31.209
the Intel community . I work for Intel

04:31.220 --> 04:33.350
Corporation , a semiconductor um

04:33.359 --> 04:35.640
company that is building a fabrication

04:35.750 --> 04:37.940
plants and also packaging plant about

04:37.950 --> 04:40.250
an hour and 15 minute drive from here .

04:40.359 --> 04:43.209
Um And I've been with Intel since 2015

04:43.470 --> 04:45.529
and I really spend my day trying to

04:45.540 --> 04:47.651
work with you all trying to solve the

04:47.651 --> 04:49.873
really hard problems and figure out how

04:49.873 --> 04:51.651
we do that in a collaborative ,

04:51.651 --> 04:53.707
cooperative sort of manner . Great .

04:53.707 --> 04:55.762
Thank you . As you see , it's a very

04:55.762 --> 04:57.929
diverse panel . Very fortunate to have

04:57.929 --> 05:00.151
this expertise with us . We're going to

05:00.151 --> 05:02.262
start the discussion with Mr Mr Hurst

05:02.262 --> 05:04.484
Kyle . You are the chief of the Digital

05:04.484 --> 05:06.373
Transformation Office and you are

05:06.373 --> 05:06.329
charged with leading the effort for

05:06.339 --> 05:08.506
General Richardson on digital material

05:08.506 --> 05:10.672
management . Can you take a little bit

05:10.672 --> 05:12.561
of time and tell us about what is

05:12.561 --> 05:14.728
digital material management as well as

05:14.728 --> 05:16.950
how you measure success ? What are your

05:16.950 --> 05:19.679
challenges ? Uh So first I want to

05:19.690 --> 05:21.912
start off with that term . So hopefully

05:21.912 --> 05:24.134
that's not a new term to anybody in the

05:24.134 --> 05:23.890
audience , digital material management ,

05:23.899 --> 05:25.955
but in case it is , I want to take a

05:25.955 --> 05:27.677
step back . So Os D originally

05:27.677 --> 05:29.455
published a digital engineering

05:29.455 --> 05:31.510
strategy shortly thereafter . As the

05:31.510 --> 05:33.621
Air Force was kind of posturing , how

05:33.621 --> 05:35.843
do we react to that ? What are our next

05:35.843 --> 05:38.010
steps going to be ? We started talking

05:38.010 --> 05:37.380
more about digital transformation than

05:37.390 --> 05:39.334
we did about digital engineering .

05:39.334 --> 05:41.501
Trying to acknowledge this is not just

05:41.501 --> 05:43.390
an engineering change , just some

05:43.390 --> 05:45.557
engineering revolution . This is a new

05:45.557 --> 05:47.779
way to do uh business holistically , so

05:47.779 --> 05:50.001
not not just the engineering functional

05:50.001 --> 05:49.899
but other uh acquisition , fun

05:49.929 --> 05:52.119
functional as well . And when General

05:52.130 --> 05:54.297
Richardson got in the seat , he coined

05:54.297 --> 05:56.408
this term digital material management

05:56.408 --> 05:58.352
to really hone in on the Air Force

05:58.352 --> 06:00.408
Material Command mission . What is ,

06:00.408 --> 06:02.630
what is it that A F MC does is material

06:02.630 --> 06:02.630
management . So he wanted to really

06:02.640 --> 06:04.799
hone in on that uh terminology and

06:04.809 --> 06:06.920
again , kind of hammer home that it's

06:06.920 --> 06:08.976
not an engineering strict thing . Uh

06:08.976 --> 06:11.440
With that being said , uh the the

06:11.450 --> 06:13.617
definition that general richen kind of

06:13.617 --> 06:15.799
put his name to was ensuring critical

06:15.809 --> 06:17.753
processes employed digital methods

06:17.753 --> 06:19.649
across the entire life cycle from

06:19.660 --> 06:21.716
invention to retirement for both war

06:21.716 --> 06:23.549
fighting capabilities as well as

06:23.549 --> 06:25.216
installation emission support

06:25.216 --> 06:27.104
capabilities . So by definition ,

06:27.104 --> 06:29.327
that's what we in a F MC term , digital

06:29.327 --> 06:31.493
material management . So within that ,

06:31.493 --> 06:33.660
there's six initiatives that I'm going

06:33.660 --> 06:35.827
to talk a little bit about . So one is

06:35.827 --> 06:37.993
structure and secure our data . So per

06:37.993 --> 06:39.827
the title of this panel , that's

06:39.827 --> 06:39.720
probably what I'll focus a little more

06:39.730 --> 06:42.119
on . Another one is providing access to

06:42.130 --> 06:44.279
critical DMM tools . Another one is

06:44.290 --> 06:47.029
train our workforce instill a digital

06:47.040 --> 06:48.950
first culture , develop digital

06:48.959 --> 06:51.089
strategies and then modernize it

06:51.100 --> 06:53.880
infrastructure . So starting with that

06:53.890 --> 06:56.001
first one instruction , secure data ,

06:56.001 --> 06:58.112
it's really taking an acknowledgement

06:58.112 --> 07:00.223
of the way we've done business in the

07:00.223 --> 06:59.779
past is not necessarily how we're going

06:59.790 --> 07:01.901
to do business in the future . So the

07:01.901 --> 07:04.068
data we've been asking for in the past

07:04.068 --> 07:03.980
is not necessarily the data we need to

07:03.989 --> 07:06.156
ask for in the future . So what is the

07:06.156 --> 07:08.156
right data that we need ? How do we

07:08.156 --> 07:10.156
change what we're gonna do uh as we

07:10.156 --> 07:12.510
acquire new data . Uh So a lot of the

07:12.519 --> 07:14.519
times we revert back to some of the

07:14.519 --> 07:16.741
data item descriptions or contract data

07:16.741 --> 07:18.575
requirements lists that previous

07:18.575 --> 07:20.797
programs have used were very copy paste

07:20.797 --> 07:23.019
culture in some sense . So we do have a

07:23.019 --> 07:22.649
way to systematically look through what

07:22.899 --> 07:25.066
uh what data item descriptions have we

07:25.066 --> 07:27.177
put on contract over the last however

07:27.177 --> 07:29.288
many contracts . And we can see , you

07:29.288 --> 07:28.950
know , some of them thousands and

07:28.959 --> 07:31.015
thousands of times we reuse the same

07:31.015 --> 07:33.359
did data descriptions . Uh Many of

07:33.369 --> 07:35.480
those did actually say something like

07:35.480 --> 07:37.536
contractor format acceptable when we

07:37.536 --> 07:39.591
talk about what data are we actually

07:39.591 --> 07:39.589
gonna acquire . That's probably not

07:39.799 --> 07:41.855
well enough thought out , right ? In

07:41.855 --> 07:43.799
many cases , as we shift to a more

07:43.799 --> 07:45.855
digital future . Uh So that , that's

07:45.855 --> 07:47.966
one of the big things . That's uh one

07:47.966 --> 07:50.077
of one of the challenges that we have

07:50.077 --> 07:49.730
is how do we actually articulate

07:49.739 --> 07:52.260
cleanly uh and consistently what data

07:52.269 --> 07:54.380
we mean ? What kind of data formats ,

07:54.380 --> 07:56.436
what styling guides , what uh IP and

07:56.436 --> 07:58.436
data rights uh considerations do we

07:58.436 --> 08:00.380
wanna make sure is included in our

08:00.380 --> 08:02.269
contracts ? Another one is access

08:02.269 --> 08:03.991
versus ownership of the data .

08:03.991 --> 08:06.102
Sometimes we don't actually need full

08:06.102 --> 08:08.269
ownership of a certain piece of data .

08:08.269 --> 08:08.195
Sometimes we might actually need just

08:08.204 --> 08:11.024
access to it to verify some requirement

08:11.045 --> 08:12.904
versus ownership of the data to

08:12.915 --> 08:15.082
potentially rec compete some subsystem

08:15.082 --> 08:16.859
in an open architecture kind of

08:16.859 --> 08:18.915
consideration . So those are some of

08:18.915 --> 08:18.695
the data considerations that we're

08:18.714 --> 08:20.825
gonna , that I think are important as

08:20.825 --> 08:22.839
we move forward . When it comes to

08:22.850 --> 08:24.961
critical DMM tools , you talked about

08:24.961 --> 08:27.017
metrics . So some of the things that

08:27.017 --> 08:29.239
are very easy to articulate and kind of

08:29.239 --> 08:31.294
track . How many licenses do we have

08:31.294 --> 08:31.190
deployed ? How many users have access

08:31.200 --> 08:33.400
to these licenses ? How frequently are

08:33.409 --> 08:35.631
they being used ? But that's not really

08:35.631 --> 08:37.687
getting after the . So what , what's

08:37.687 --> 08:39.742
the , what's the impact of that ? So

08:39.742 --> 08:41.965
trying to get a kind of a program level

08:41.965 --> 08:43.909
return on investment by leveraging

08:43.909 --> 08:46.076
these tools is really the most desired

08:46.076 --> 08:45.729
thing . But sometimes one of the harder

08:45.739 --> 08:47.628
things to measure , it's a little

08:47.628 --> 08:49.295
easier to measure it , the uh

08:49.295 --> 08:51.183
controlled and classified or even

08:51.183 --> 08:53.350
secret level . But once you get into a

08:53.350 --> 08:53.299
a program , it becomes much more

08:53.309 --> 08:55.109
difficult to measure and then

08:55.119 --> 08:57.286
communicate what the return investment

08:57.286 --> 08:59.397
was and spread that best practice and

08:59.397 --> 09:01.508
lessons learned . So tying it back to

09:01.508 --> 09:03.619
the the challenges questions . That's

09:03.619 --> 09:03.090
one of the challenges we have as many

09:03.099 --> 09:05.340
of our most advanced programs in this

09:05.349 --> 09:07.989
space are special access , highly

09:08.000 --> 09:10.333
classified , becomes difficult to scale .

09:10.333 --> 09:12.056
The goodness scale the kind of

09:12.056 --> 09:14.222
enterprise solutions or solutions that

09:14.222 --> 09:16.278
they're using . Uh I did wanna touch

09:16.278 --> 09:18.444
also on the uh uh instilling a digital

09:18.444 --> 09:20.444
first culture . So I actually loved

09:20.444 --> 09:22.667
that the chief of staff talked about uh

09:22.667 --> 09:24.722
kind of the World War Two industrial

09:24.722 --> 09:26.944
build up , right ? So anyone who hasn't

09:26.944 --> 09:29.167
read freedom's forge strongly recommend

09:29.167 --> 09:31.500
it . Uh sometimes in a smaller audience ,

09:31.500 --> 09:30.950
I'll ask the audience to shout out a a

09:30.960 --> 09:32.738
guess , guess an answer to this

09:32.738 --> 09:34.849
question , I'm gonna . But what's the

09:34.849 --> 09:36.960
fielding timeline from contract award

09:36.960 --> 09:38.960
or not fielding timeline , contract

09:38.960 --> 09:41.071
award to first production jet rolling

09:41.071 --> 09:43.238
off the line for the P 51 Mustang . So

09:43.238 --> 09:45.404
everyone think about it for a second .

09:45.404 --> 09:47.238
It's 100 and two days . That's a

09:47.238 --> 09:49.349
shockingly fast timeline . So when we

09:49.349 --> 09:51.349
talk about a , you know , he talked

09:51.349 --> 09:53.682
about risk aversion and risk acceptance .

09:53.682 --> 09:53.500
That was a very different risk posture .

09:53.510 --> 09:55.510
He talked about creating a sense of

09:55.510 --> 09:57.399
crisis before there is a crisis .

09:57.399 --> 09:59.566
Obviously , there was a crisis at that

09:59.566 --> 09:59.109
point in time , but that kind of

09:59.119 --> 10:01.063
acquisition timeline is unheard of

10:01.063 --> 10:02.730
today . So how can we kind of

10:02.730 --> 10:04.730
incentivize or create that sense of

10:04.730 --> 10:06.841
crisis to go faster ? Right ? Most of

10:06.841 --> 10:08.508
our acquisition timelines are

10:08.508 --> 10:10.508
significantly longer than that . So

10:10.508 --> 10:12.619
that's , that's a really good kind of

10:12.619 --> 10:12.429
way to frame some of the thinking

10:12.440 --> 10:14.607
around digital first culture . How can

10:14.607 --> 10:16.773
we accept a little more risk ? How can

10:16.773 --> 10:18.940
we be a little more forward leaning in

10:18.940 --> 10:21.051
our timelines around acquisition ? Uh

10:21.051 --> 10:23.273
When we talk about digital strategies ,

10:23.273 --> 10:23.020
it's really at the program level . Uh

10:23.030 --> 10:25.141
that , that , that's the way we frame

10:25.141 --> 10:27.308
it . Uh So I saw a couple of people in

10:27.308 --> 10:29.141
the audience who are part of the

10:29.141 --> 10:28.820
digital enterprise launch team for

10:28.830 --> 10:30.941
acquisition uh a group that's kind of

10:30.941 --> 10:33.570
out there charted to help uh programs

10:33.580 --> 10:35.580
kind of craft digital language into

10:35.580 --> 10:37.530
their uh RFPS into their initial

10:37.739 --> 10:39.549
acquisition processes . We also

10:39.559 --> 10:41.726
recently set up a center of excellence

10:41.726 --> 10:43.892
at a , it's officially live helped its

10:43.892 --> 10:46.115
first program just a couple weeks ago .

10:46.115 --> 10:48.226
Uh But it's intended to be a tactical

10:48.226 --> 10:50.337
user help uh that a , a program who's

10:50.337 --> 10:52.337
gonna dig into , you know , maybe I

10:52.337 --> 10:54.559
want to create a GR A that I can go put

10:54.559 --> 10:54.049
on contract and get industry to

10:54.059 --> 10:56.059
interact in some model based system

10:56.059 --> 10:58.059
engineering model format . How do I

10:58.059 --> 11:00.281
actually do that ? How do I create that

11:00.281 --> 11:02.281
model , interact with industry with

11:02.281 --> 11:01.919
that model ? That's that tactical help

11:01.929 --> 11:04.369
and reach back support . Um And then

11:04.380 --> 11:06.690
last one with modernized it

11:06.700 --> 11:08.644
infrastructure . Uh It's , it's an

11:08.644 --> 11:10.867
interesting one that General Richardson

11:10.867 --> 11:12.978
chose to highlight that as one of the

11:12.978 --> 11:14.978
initiatives within digital material

11:14.978 --> 11:14.549
management because it's not one we

11:14.559 --> 11:17.429
explicitly own right . There is uh as ,

11:17.440 --> 11:19.607
as I see General General Temple on the

11:19.607 --> 11:21.440
front row here . There's lots of

11:21.440 --> 11:23.551
families in the it business that have

11:23.551 --> 11:25.773
different ownership of different pieces

11:25.773 --> 11:27.996
and parts of the of the puzzle . So how

11:27.996 --> 11:30.218
we actually modernize it infrastructure

11:30.218 --> 11:32.162
holistically is a very challenging

11:32.162 --> 11:35.239
thing to do uh for real , right ? So we

11:35.250 --> 11:37.306
can , we can talk about , you know ,

11:37.306 --> 11:39.528
fix my computer with end user devices ,

11:39.528 --> 11:41.639
we can talk about it infrastructure ,

11:41.639 --> 11:43.861
we can talk about cloud hosted software

11:43.861 --> 11:46.083
tools , but they're all just pieces and

11:46.083 --> 11:48.250
parts of the broader it infrastructure

11:48.250 --> 11:49.972
as we talk about digital share

11:49.972 --> 11:51.972
management . So really honing in on

11:51.972 --> 11:54.083
that and figuring out how we wrap our

11:54.083 --> 11:53.059
arms around , that's one of the big

11:53.070 --> 11:55.237
challenges . So overall , I think kind

11:55.237 --> 11:57.459
of what data do we need , how do we get

11:57.459 --> 11:59.681
it ? How do we uh get that data in such

11:59.681 --> 12:01.626
a way that we're not either vendor

12:01.626 --> 12:03.792
locked in some software software model

12:03.792 --> 12:05.959
or a specific industry ? Prime partner

12:05.959 --> 12:07.737
is one focus area , one kind of

12:07.737 --> 12:09.959
challenge area . Uh workforce upscaling

12:09.959 --> 12:12.299
and culture change is a challenge area .

12:12.309 --> 12:14.590
Um One other interesting point I'll

12:14.599 --> 12:16.710
point out is that we talk a lot about

12:16.710 --> 12:19.043
the operational imperative this morning ,

12:19.043 --> 12:18.390
right ? Again , several of those are

12:18.400 --> 12:20.549
highly classified uh which makes

12:20.559 --> 12:22.503
spreading the goodness difficult ,

12:22.503 --> 12:24.559
right ? It also makes spreading that

12:24.559 --> 12:26.726
talent difficult , right ? People will

12:26.726 --> 12:26.669
get pulled into those most important

12:26.679 --> 12:28.457
programs and how we spread that

12:28.457 --> 12:30.568
knowledge uh becomes something that's

12:30.568 --> 12:32.735
difficult to do . Uh And then last one

12:32.735 --> 12:34.623
is that enterprise enabling verse

12:34.623 --> 12:36.735
prioritized support that gets back at

12:36.735 --> 12:36.229
that os those are the big challenges .

12:36.869 --> 12:39.091
Great . That's a great rundown . Uh For

12:39.091 --> 12:41.147
folks not familiar with it , greatly

12:41.147 --> 12:43.258
appreciate it . It helps shape things

12:43.258 --> 12:45.258
and ties very nicely . What we just

12:45.258 --> 12:47.510
heard . Uh Mr Tinner , you're doing the

12:47.520 --> 12:49.631
same thing in the commercial sector .

12:49.631 --> 12:51.576
You , you're dealing with the same

12:51.576 --> 12:53.687
challenges , multiple locations . How

12:53.687 --> 12:55.631
do we standardize ? How do we come

12:55.631 --> 12:57.631
together ? You started this journey

12:57.631 --> 12:57.489
ahead of us . What have you learned ?

12:57.500 --> 12:59.500
How do you measure and what can you

12:59.500 --> 13:01.611
tell us that we can learn from and we

13:01.611 --> 13:03.778
can share and better be prepared for ?

13:03.778 --> 13:05.500
Yeah , absolutely . You know ,

13:05.500 --> 13:07.444
listening to the discussion just a

13:07.444 --> 13:09.556
second ago , there are the thing I've

13:09.556 --> 13:11.556
learned the most is that in a large

13:11.556 --> 13:13.833
organization , whether it's commercial ,

13:13.833 --> 13:15.778
whether it's the Air Force , other

13:15.778 --> 13:15.429
parts of the government , we all have

13:15.440 --> 13:17.607
similar challenges and I think we have

13:17.607 --> 13:19.773
similar approaches for going to tackle

13:19.773 --> 13:21.940
it . You know , when you think of that

13:21.940 --> 13:24.162
example a second ago about P 51 and the

13:24.162 --> 13:26.496
timeline which is astounding . You know ,

13:26.496 --> 13:28.773
when we look at digital transformation ,

13:28.773 --> 13:30.829
a lot of it is working backward from

13:30.829 --> 13:32.884
that . The mission effect that we're

13:32.884 --> 13:32.809
going for is delivering product faster

13:32.820 --> 13:35.119
to the end user . But what are all the

13:35.130 --> 13:37.130
things that we need to go do within

13:37.130 --> 13:39.130
this process to make it faster , to

13:39.130 --> 13:41.080
make it more capable ? And so at

13:41.090 --> 13:43.201
Northrop very similar to what we just

13:43.201 --> 13:45.312
talked about . We've broken this down

13:45.312 --> 13:47.515
into four major areas that we want to

13:47.525 --> 13:49.414
go tackle and not just have every

13:49.414 --> 13:51.636
program do it independently but make it

13:51.636 --> 13:53.875
so everyone can contribute to a common

13:53.885 --> 13:55.955
digital ecosystem . And it really

13:55.965 --> 13:57.798
covers the areas of what we call

13:57.798 --> 13:59.743
digital transformation . And so to

13:59.743 --> 14:01.909
start off with , everyone obviously is

14:01.909 --> 14:04.021
familiar with digital engineering and

14:04.021 --> 14:06.076
manufacturing . And we have a pillar

14:06.076 --> 14:08.298
for that product facing area which then

14:08.298 --> 14:10.409
needs to extend well into sustainment

14:10.409 --> 14:12.409
because we know that so much of the

14:12.409 --> 14:14.576
cost of a program and where we need to

14:14.576 --> 14:16.798
get to is in sustainment , we then have

14:16.798 --> 14:18.798
a pillar that we're driving for the

14:18.798 --> 14:20.965
business facing side because we can be

14:20.965 --> 14:23.187
really successful in the digital models

14:23.187 --> 14:25.298
and the digital representations . But

14:25.298 --> 14:27.465
if we can't link to our supply chain ,

14:27.465 --> 14:27.010
we can't actually go out there and

14:27.020 --> 14:29.020
physically create these things . We

14:29.020 --> 14:31.187
haven't completed the mission . And so

14:31.187 --> 14:33.298
a large focus on that business facing

14:33.298 --> 14:35.131
back office element and making a

14:35.131 --> 14:37.187
comment across the company . Both of

14:37.187 --> 14:39.298
those together . When you think about

14:39.298 --> 14:41.520
how we get there are all rooted in data

14:41.520 --> 14:43.853
and our ability to have well structured ,

14:43.853 --> 14:45.853
secure data and be able to interact

14:45.853 --> 14:47.964
with the ecosystem , whether it's the

14:47.964 --> 14:50.131
government or whether it's the vendors

14:50.131 --> 14:52.298
and all that conversation earlier on A

14:52.298 --> 14:54.409
I , we can't get to reasonable use of

14:54.409 --> 14:55.909
AI without well structured

14:55.909 --> 14:58.131
understanding of our data . And so huge

14:58.131 --> 15:00.020
focus there . And in the last but

15:00.020 --> 15:02.715
likely most important piece of it is

15:02.724 --> 15:04.780
and like the chief chief was talking

15:04.780 --> 15:07.002
about this new business model , the new

15:07.002 --> 15:09.113
norms , it changes the culture of who

15:09.113 --> 15:11.113
we are when we're operating in this

15:11.113 --> 15:13.280
digital ecosystem . So we have a large

15:13.280 --> 15:15.502
focus on getting us to where we need to

15:15.502 --> 15:17.780
be when you think about a data culture .

15:17.780 --> 15:20.002
One of the challenges that we've gotten

15:20.002 --> 15:22.057
to is realizing when we're in this ,

15:22.057 --> 15:24.057
this digital web , it's no longer a

15:24.057 --> 15:26.057
digital thread . How do we actually

15:26.057 --> 15:28.057
operate together ? And it really is

15:28.057 --> 15:28.039
about operating in a shared data

15:28.049 --> 15:30.260
ecosystem and everybody in defense

15:30.270 --> 15:32.679
right now . So naturally protects their

15:32.690 --> 15:34.880
data . It's my data until there's a

15:34.890 --> 15:37.224
real strong reason to release it . If

15:37.234 --> 15:39.345
we want to go do what we need to do ,

15:39.345 --> 15:41.567
we need to find a way to share our data

15:41.567 --> 15:43.401
first and then hold it back when

15:43.401 --> 15:45.401
absolutely necessary . And that's a

15:45.401 --> 15:47.456
challenge , right ? But getting that

15:47.456 --> 15:49.790
data ecosystem in underpins all of this ,

15:49.790 --> 15:51.512
whether you're talking digital

15:51.512 --> 15:53.623
engineering where we have associative

15:53.623 --> 15:55.790
designs or you're talking supply chain

15:55.790 --> 15:57.845
where we want to directly streamline

15:57.845 --> 15:57.755
these products , these drawings right

15:57.765 --> 16:01.049
out to our suppliers . So those are the

16:01.059 --> 16:03.260
major areas that we're focused on and

16:03.270 --> 16:05.103
done a lot of work so that every

16:05.103 --> 16:07.270
program doesn't do it on its own . And

16:07.270 --> 16:09.381
when we look at measures of success ,

16:09.381 --> 16:11.381
there are of course , measures like

16:11.381 --> 16:13.103
cost , schedule quality and we

16:13.103 --> 16:15.048
certainly are measuring those very

16:15.048 --> 16:17.270
closely because they impact everybody .

16:17.270 --> 16:19.381
But the bigger thing to meet today is

16:19.381 --> 16:21.381
that a year ago , we probably would

16:21.381 --> 16:23.270
have been talking about a few big

16:23.270 --> 16:25.214
programs successes we're having in

16:25.214 --> 16:24.763
building digital ecosystems in that

16:24.773 --> 16:27.203
program . Success is not when a few

16:27.213 --> 16:29.435
programs have amazing ecosystems . It's

16:29.435 --> 16:31.491
when all programs are launching into

16:31.491 --> 16:33.491
these common ecosystems and sharing

16:33.491 --> 16:35.546
from day one . And we've gone from a

16:35.546 --> 16:37.657
company really focused in success and

16:37.657 --> 16:39.546
partnered with the Air Force in a

16:39.546 --> 16:41.435
number of these areas to over 100

16:41.435 --> 16:43.435
programs now launched into a common

16:43.435 --> 16:45.769
digital ecosystem and growing every day .

16:45.769 --> 16:47.935
And it's getting to the point now when

16:47.935 --> 16:49.824
a program comes in , whether it's

16:49.824 --> 16:51.713
company investment , whether it's

16:51.713 --> 16:53.880
government programs , the acceleration

16:53.880 --> 16:55.991
that we do in the digital environment

16:55.991 --> 16:58.324
is contributing now to the broader base .

16:58.324 --> 17:00.546
And to me that's really what success is

17:00.546 --> 17:02.435
about . It's getting that mission

17:02.435 --> 17:04.546
delivered and having all the programs

17:04.546 --> 17:06.602
which really leads us then to what's

17:06.602 --> 17:08.602
next . And again , thinking back to

17:08.602 --> 17:10.713
what the chief talked about . Success

17:10.713 --> 17:12.920
is not when we have a lower cost or we

17:12.930 --> 17:14.859
deliver a part of the mission

17:14.869 --> 17:16.869
successfully . It's when the entire

17:16.869 --> 17:19.130
mission is delivered successfully . And

17:19.140 --> 17:21.362
there's a couple of things that we need

17:21.362 --> 17:23.307
to do and partner even more across

17:23.307 --> 17:25.362
industry and with the government and

17:25.362 --> 17:27.584
one of them is looking at where are the

17:27.584 --> 17:29.862
places that we should not be competing ,

17:29.862 --> 17:31.973
right ? Where are the places where we

17:31.973 --> 17:31.598
simply need to get the whole ecosystem

17:31.609 --> 17:33.498
moving forward . And a place that

17:33.498 --> 17:35.609
sticks out is the way that we connect

17:35.609 --> 17:37.387
with all of our suppliers , our

17:37.387 --> 17:39.498
suppliers and vendors can't afford to

17:39.498 --> 17:41.553
have 10 different digital ecosystems

17:41.553 --> 17:43.609
that they need to connect into . And

17:43.609 --> 17:45.776
that's a place where I know along with

17:45.776 --> 17:47.887
my , you know , the industry partners

17:47.887 --> 17:49.942
and beyond , we are partnering on is

17:49.942 --> 17:52.165
somewhere need to go even further . And

17:52.165 --> 17:54.387
the second half of this is about data ,

17:54.387 --> 17:53.719
if we're going to share data and we're

17:53.729 --> 17:55.959
going to try and protect IP we need to

17:55.969 --> 17:58.025
make sure we're really talking about

17:58.025 --> 18:00.191
that first and figuring out how we use

18:00.191 --> 18:02.358
the technology and this data ecosystem

18:02.358 --> 18:04.469
to not let IP be something that holds

18:04.469 --> 18:06.247
us back , but something that we

18:06.247 --> 18:08.302
understand and helps us move forward

18:08.302 --> 18:10.136
together . So I'm really looking

18:10.136 --> 18:09.780
forward to that partnership with

18:09.790 --> 18:12.300
everyone . It's a lot of good

18:12.310 --> 18:15.270
information in there and you spoke

18:15.280 --> 18:18.069
heavily about data , data rights . The

18:18.079 --> 18:20.599
key thing for us , Dr Mesner works for

18:20.609 --> 18:22.720
a FSC . They're dealing with the fact

18:22.720 --> 18:24.887
that the Air Force , the Department of

18:24.887 --> 18:27.053
Defense , we don't own data rights for

18:27.053 --> 18:29.331
a lot of our weapons systems . However ,

18:29.331 --> 18:31.331
we still have to maintain them . We

18:31.331 --> 18:33.498
also have very antiquated systems . In

18:33.498 --> 18:33.479
many cases , we still have to maintain

18:33.489 --> 18:37.369
them . What is the impact of the

18:37.380 --> 18:39.491
sustainment center in terms of trying

18:39.491 --> 18:41.658
to do reverse engineering ? What would

18:41.658 --> 18:43.713
you like to do different in terms of

18:43.713 --> 18:43.640
what data . Do you need to support our

18:43.650 --> 18:45.650
platforms and what can we do in the

18:45.650 --> 18:47.650
digital environment going forward ?

18:47.650 --> 18:49.872
Great , thanks , uh Mr Lyman for that .

18:49.872 --> 18:52.206
But being from Oklahoma , um , you know ,

18:52.206 --> 18:54.428
kind of where our headquarters is , you

18:54.428 --> 18:56.599
can't start a conversation without ,

18:56.839 --> 18:59.061
you know , quoting Toby Keith . Right .

18:59.061 --> 19:01.172
So I think we need a little less talk

19:01.172 --> 19:03.283
and a lot more action in this space ,

19:03.283 --> 19:06.150
right ? So , you know , uh the Chief

19:06.160 --> 19:09.079
Brown said that uh leaders win through

19:09.089 --> 19:11.270
logistics , right ? And , and I think

19:11.280 --> 19:14.640
that really comes down to logistics is

19:14.650 --> 19:18.290
more and more um basically

19:18.300 --> 19:20.719
data at the edge . So how are we

19:20.729 --> 19:24.640
producing data rights ? And how can we

19:24.650 --> 19:27.250
act on those data rights ? Well , when

19:27.260 --> 19:29.427
you break down data rights , it really

19:29.427 --> 19:31.800
comes in a multifaceted eight flavors

19:31.810 --> 19:34.520
of data , right ? There's the unlimited

19:34.819 --> 19:36.880
and everything from unlimited to

19:36.890 --> 19:39.890
restricted . So when you start to look

19:39.900 --> 19:42.930
at the DMM , it's really about how do

19:42.939 --> 19:46.180
we start to look at data rights and

19:46.189 --> 19:49.339
look through and amass change so that

19:49.349 --> 19:52.550
we can impart knowledge and

19:52.560 --> 19:55.219
information to the skilled artisan to

19:55.229 --> 19:57.689
be able to turn , you know , their

19:57.699 --> 20:01.239
skills into readiness . So when you get

20:01.250 --> 20:03.810
into assessing , you know , the data

20:03.819 --> 20:05.819
rights , it's really the essence is

20:05.819 --> 20:07.986
about data . It's expressing that data

20:07.986 --> 20:09.652
from ones and zeros into that

20:09.652 --> 20:11.319
information and knowledge and

20:11.319 --> 20:13.449
effectively using the data throughout

20:13.459 --> 20:15.570
the life cycle of the weapon system .

20:15.570 --> 20:17.737
So your question really , um how do we

20:17.737 --> 20:19.880
improve the acquisition to support ,

20:19.890 --> 20:22.430
you know , uh the sustainment process

20:22.439 --> 20:25.319
it really focuses on , on as Kyle was

20:25.329 --> 20:29.180
talking about um the DMM . So I think

20:29.189 --> 20:32.199
first is to develop a holistic data

20:32.209 --> 20:34.750
centric acquisition process , we got to

20:34.760 --> 20:37.939
prioritize the data needs up front . Um

20:37.949 --> 20:41.000
As uh you know , the chief was saying

20:41.140 --> 20:44.589
we're moving actually from a , you know ,

20:44.599 --> 20:48.040
kind of uh data centric where we can

20:48.050 --> 20:52.000
start to turn a IML into knowledge to

20:52.010 --> 20:54.232
really support those weapon systems and

20:54.232 --> 20:56.510
move them forward . Um One of the key

20:56.520 --> 20:59.089
things that A FSC is doing is investing

20:59.099 --> 21:01.689
in the organic industrial base . Um We

21:01.699 --> 21:05.270
are aligned to the DMM . Um We have a

21:05.280 --> 21:07.430
key focus areas on the organic

21:07.439 --> 21:09.439
industrial base and we're trying to

21:09.439 --> 21:12.939
reduce those risk of the D MS MS world

21:12.949 --> 21:15.930
through data so that we can actually

21:15.939 --> 21:18.260
get in front of the obsolescence uh

21:18.270 --> 21:21.280
issues . So when we start to look

21:21.290 --> 21:23.880
through increasing and innovating

21:23.890 --> 21:26.359
through this untapped potential of the

21:26.369 --> 21:29.459
weapon system , I think that the OOIB

21:29.469 --> 21:31.880
is kind of key to emphasizing and

21:31.890 --> 21:34.001
extending the benefits of that weapon

21:34.001 --> 21:35.719
system , obviously partnering

21:35.729 --> 21:39.160
throughout the DMM and getting data

21:39.170 --> 21:41.609
right , and data up front . So those

21:41.619 --> 21:43.286
data rights are linked to the

21:43.286 --> 21:45.341
performance objectives of the weapon

21:45.341 --> 21:47.563
system of the acquisition community and

21:47.563 --> 21:49.790
through and to the sustainment center

21:49.959 --> 21:52.015
so that we can actually secure those

21:52.015 --> 21:53.969
data rights early so that we can

21:53.979 --> 21:55.760
iterate with industry on those

21:55.770 --> 21:57.492
improvements . You know , it's

21:57.492 --> 22:00.109
interesting in being in the sustainment

22:00.119 --> 22:02.459
center . A lot of times we kind of act

22:02.469 --> 22:05.750
as three sort of air logistics

22:05.760 --> 22:07.959
complexes and two supply chain wings .

22:07.969 --> 22:09.802
And it's very interesting in our

22:09.802 --> 22:13.130
partnerships in our interactions . You

22:13.140 --> 22:15.770
know , we get demand signals into the

22:15.780 --> 22:17.849
depot from our private , private

22:17.859 --> 22:20.344
partner tips from our supply chain wing .

22:20.545 --> 22:24.175
We get um obviously my caps and

22:24.185 --> 22:26.574
critical needs through the sustainment

22:26.584 --> 22:29.344
center through the 6 35th and then

22:29.354 --> 22:31.576
through the um supply chain wing at the

22:31.576 --> 22:33.798
wholesale level , we are working on the

22:33.798 --> 22:36.021
cognisant engineering of a lot of those

22:36.021 --> 22:38.243
components and trying to turn that into

22:38.395 --> 22:41.354
um purchases and um actually

22:41.364 --> 22:45.069
repairs . So holistically , our

22:45.079 --> 22:47.989
leadership is kind of driving through

22:48.000 --> 22:50.000
the digital material management and

22:50.000 --> 22:52.111
improvement in the organic industrial

22:52.111 --> 22:54.520
base so that we can be better partners

22:54.530 --> 22:56.419
both on the supplier side and the

22:56.419 --> 22:58.770
producer side . And one of those key

22:58.780 --> 23:01.002
components as we start to get into that

23:01.002 --> 23:03.169
is the reverse engineering component .

23:03.169 --> 23:06.150
So part of our Digital Depot ecosystem

23:06.160 --> 23:09.150
is really driving a lot of improvements

23:09.160 --> 23:12.380
into the reverse engineering we

23:12.390 --> 23:15.319
have at Oklahoma City , the reverse

23:15.329 --> 23:17.162
engineering and critical tooling

23:17.162 --> 23:19.520
component . Um They are actually

23:19.530 --> 23:22.839
working through a lot of uh inadequate

23:22.849 --> 23:25.270
data . Uh working through obsolescence

23:25.280 --> 23:28.729
of the tech data to actually improve um

23:28.739 --> 23:30.739
you know , the critical tooling and

23:30.739 --> 23:32.572
parts manufacturing through that

23:32.572 --> 23:35.040
process . Um as we start to go through

23:35.050 --> 23:37.609
that process , it's really kind of

23:37.619 --> 23:39.699
critical to understand the whole

23:39.709 --> 23:42.160
process and and really manage that with

23:42.170 --> 23:44.226
those digital engineering tools that

23:44.226 --> 23:46.226
Kyle was talking about , you know ,

23:46.226 --> 23:48.479
when we start to look at turning this

23:48.500 --> 23:51.689
obsolete data and a hard asset

23:51.699 --> 23:54.800
into a product , it requires a lot of

23:54.810 --> 23:57.489
disassembling , it requires breaking

23:57.500 --> 23:59.278
down the components , obviously

23:59.278 --> 24:01.611
scanning those analyzing the structures ,

24:01.611 --> 24:03.780
recreate , recreating the components ,

24:03.790 --> 24:06.380
testing those . And you know , we're

24:06.390 --> 24:08.719
partnering in a lot of those spaces to

24:08.729 --> 24:11.680
overcome the inadequacy of the data

24:11.689 --> 24:13.800
with our public private partnership .

24:13.800 --> 24:16.540
So um we've obviously got the um uh

24:16.619 --> 24:18.989
pacer edge , the phase three of that ,

24:19.000 --> 24:20.778
that we're working with General

24:20.778 --> 24:22.599
Electric in uh critical engine

24:22.609 --> 24:25.459
components to get over uh some of the

24:25.560 --> 24:29.449
um um obsolescence and um

24:29.459 --> 24:33.010
you know , the obsolescence and the

24:33.119 --> 24:35.619
end of those parts . Uh what's been

24:35.630 --> 24:37.780
interesting to me is , you know ,

24:38.209 --> 24:41.959
taking the industry 4.0 components of

24:41.969 --> 24:44.839
where we are from an A FSC perspective

24:44.849 --> 24:47.119
and integrating them into the digital

24:47.130 --> 24:49.880
material management aspect . I think ,

24:50.040 --> 24:52.589
you know , one key example of how we're

24:52.599 --> 24:55.180
doing that is obviously our search for

24:55.189 --> 24:58.640
compliance with the um section 1 42 of

24:58.650 --> 25:01.420
the FY 22 NDA A . I'm working with uh

25:01.430 --> 25:04.400
Lockheed Martin on , you know , those

25:04.410 --> 25:07.579
components as we break down um our

25:07.589 --> 25:09.719
supply chain and our supply chain

25:09.729 --> 25:11.840
management because it's a continuum ,

25:11.840 --> 25:14.007
even in that space , right , you could

25:14.007 --> 25:16.895
manage the PB L to the point of um you

25:16.905 --> 25:18.961
know , just managing the contract in

25:18.961 --> 25:21.183
partnership with the JP as that kind of

25:21.183 --> 25:23.238
moves down . Um we can always extend

25:23.238 --> 25:25.675
that actually into the um you know ,

25:25.685 --> 25:28.185
repair and assembly of those . And so

25:28.194 --> 25:30.361
we're doing some piloting , you know ,

25:30.361 --> 25:32.494
on that aspect with obviously the JO

25:32.505 --> 25:36.194
across the A FSC to include the 4 48

25:36.204 --> 25:38.824
and the uh Ogden Air Logistics Complex .

25:38.944 --> 25:41.265
And with Lockheed Martin to look at how

25:41.275 --> 25:43.053
can we take the wheel and brake

25:43.053 --> 25:45.930
assembly , break that down and put it

25:45.939 --> 25:48.180
into our catalog and provisioning . How

25:48.189 --> 25:50.709
can we remove it as a barrier as Kyle

25:50.719 --> 25:53.150
was talking about , you know , getting

25:53.160 --> 25:56.579
the organic um industrial base aligned

25:56.589 --> 26:00.020
to an ot and an it infrastructure um so

26:00.030 --> 26:01.974
that we can share data across that

26:01.979 --> 26:04.060
perspective is going to be key but

26:04.069 --> 26:06.125
continuing to work with our partners

26:06.150 --> 26:09.189
and growing that information from data

26:09.199 --> 26:11.489
to information to knowledge so that we

26:11.500 --> 26:13.222
can , you know , get after our

26:13.222 --> 26:15.969
collective adversaries in that space is

26:15.979 --> 26:18.201
really where we're headed . But I think

26:18.201 --> 26:20.319
it all does start with switching our

26:20.329 --> 26:22.739
acquisition processes to more of a data

26:22.750 --> 26:26.599
centric aspect and putting data first

26:26.609 --> 26:28.829
and then maybe even doing modeling and

26:28.839 --> 26:31.359
simulation long term about what does

26:31.369 --> 26:33.480
the life cycle of this weapons system

26:33.480 --> 26:35.702
look like ? How can you take advantages

26:35.702 --> 26:38.589
of these kind of key aspects of your

26:38.599 --> 26:40.821
organic industrial base that are really

26:40.821 --> 26:43.369
national treasures for uh rapid and

26:43.380 --> 26:46.609
innovative and agile manufacturing and

26:46.619 --> 26:48.786
uh remanufacturing of the capability ?

26:48.969 --> 26:52.510
Great . Thanks Tim . Um Adriana , a lot

26:52.520 --> 26:54.520
of talk about intellectual property

26:54.520 --> 26:56.631
data rights . What can the government

26:56.631 --> 26:59.069
get ? That's a real challenge for us

26:59.079 --> 27:02.369
because industry , that's your bread

27:02.380 --> 27:04.602
and butter . That's where you make your

27:04.602 --> 27:06.436
money , what you create and it's

27:06.436 --> 27:08.436
something you don't readily want to

27:08.436 --> 27:08.199
give over because you don't want to see

27:08.209 --> 27:10.265
it go to your competition . Although

27:10.265 --> 27:12.320
you're sitting together on a panel ,

27:12.320 --> 27:11.979
you don't want to share your secret

27:11.989 --> 27:14.322
information with Ryan right next to you .

27:14.430 --> 27:16.579
So what , what's the industry

27:16.589 --> 27:18.700
perspective on this and what are some

27:18.700 --> 27:20.645
win win solutions ? What can we do

27:20.645 --> 27:20.530
different ? How do you see

27:20.540 --> 27:22.750
opportunities for us to change , to

27:22.760 --> 27:26.380
help us meet the Chiefs intent , what

27:26.390 --> 27:28.390
we need to do as a nation and still

27:28.390 --> 27:32.109
protect our industry partners ? Uh So

27:32.119 --> 27:35.430
um it's complicated . Um So um

27:35.439 --> 27:37.800
first of all , so I , I come at this

27:37.810 --> 27:39.977
probably from a little bit a different

27:39.977 --> 27:42.130
perspective as the IP lawyer , uh and

27:42.140 --> 27:44.362
the IP lawyer , what we're trying to do

27:44.362 --> 27:46.584
is we're trying to figure out the terms

27:46.584 --> 27:48.862
under which we can get to the customer ,

27:48.862 --> 27:50.918
the technology and the data that you

27:50.918 --> 27:53.084
need and the terms under which you can

27:53.084 --> 27:55.170
do that . And one of the primary

27:55.180 --> 27:58.030
challenges um that has been growing

27:58.040 --> 28:00.644
over the years and as things speed up ,

28:00.654 --> 28:02.765
become more digital , the model based

28:02.765 --> 28:05.004
engineering A I all of those

28:05.014 --> 28:07.125
technologies , one of the things that

28:07.125 --> 28:10.673
has really fundamentally changed has to

28:10.683 --> 28:14.004
do with the increasing risk to IP

28:14.014 --> 28:16.923
protection . Um One of the things that

28:16.933 --> 28:20.644
is important to understand . Um as

28:20.654 --> 28:22.404
we're talking about providing

28:22.413 --> 28:24.624
technology , particularly whether it's

28:24.634 --> 28:26.904
commercial or non-commercial privately

28:26.913 --> 28:30.578
expensed developed technology . Um is

28:30.588 --> 28:34.348
that uh there is a much

28:34.358 --> 28:37.218
greater risk of even providing access

28:37.228 --> 28:39.637
to the technology . Um It used to be ,

28:39.647 --> 28:41.591
you know , you were in a lab , you

28:41.591 --> 28:43.703
would develop something you could put

28:43.703 --> 28:45.758
sort of boundaries around things . I

28:45.758 --> 28:45.177
mean , heck , you know , back in the

28:45.187 --> 28:47.187
day you were delivering software on

28:47.187 --> 28:49.988
disks , right ? Um Now because of all

28:49.998 --> 28:53.787
of the , the um uh all of the , the um

28:53.797 --> 28:57.157
basically connectivity , um all you

28:57.167 --> 28:59.952
need at this point is to basically get

28:59.962 --> 29:01.962
access to somebody's solution , you

29:01.962 --> 29:04.184
look at it , you can immediately figure

29:04.184 --> 29:06.184
out what they're doing , you can go

29:06.184 --> 29:08.406
build it yourself , you can modify it ,

29:08.406 --> 29:10.184
reverse engineer it , copy it ,

29:10.184 --> 29:12.406
distribute it . All of those things are

29:12.406 --> 29:14.629
very , very easy to do . So when you're

29:14.629 --> 29:16.740
looking at the technology that you've

29:16.740 --> 29:18.795
developed , particularly the digital

29:18.795 --> 29:21.018
technology that you've developed you as

29:21.018 --> 29:23.182
the owner of that IP , who wants to

29:23.192 --> 29:26.141
make sure that you are getting a return

29:26.151 --> 29:29.086
on investment of IP you want , you

29:29.095 --> 29:31.095
think about OK , who's going to get

29:31.095 --> 29:33.151
access to this ? It's not only who's

29:33.151 --> 29:35.151
going to , you know , to whom is it

29:35.151 --> 29:37.317
going to be delivered , but also who's

29:37.317 --> 29:39.428
gonna , who's going to be able to see

29:39.428 --> 29:42.115
it . And so just to give a little bit

29:42.125 --> 29:44.676
of context the way that kind of the

29:44.686 --> 29:46.630
commercial industries have largely

29:46.630 --> 29:49.086
managed . This is that they stopped

29:49.095 --> 29:52.906
delivering their IP . In other words ,

29:52.916 --> 29:54.916
we used to , you know , you used to

29:54.916 --> 29:57.180
actually receive soft . Now you receive

29:57.189 --> 29:59.133
services , you don't actually ever

29:59.133 --> 30:01.467
receive the software , you log in , you ,

30:01.467 --> 30:03.633
you use the software on their server ,

30:03.633 --> 30:05.745
you pull out your data , you go about

30:05.745 --> 30:07.856
your day . It's the same thing with ,

30:07.856 --> 30:09.800
with , you know , a lot of the A I

30:09.800 --> 30:12.079
technologies and that is how the

30:12.089 --> 30:15.459
commercial industry has largely helped

30:15.469 --> 30:17.636
to mitigate their risk , which is they

30:17.636 --> 30:19.750
don't really ever distribute the IP .

30:20.050 --> 30:22.739
And that is , you know , thinking about

30:22.900 --> 30:26.634
ways to go , how do we handle that in

30:26.644 --> 30:28.866
the government contracting world in the

30:28.866 --> 30:31.244
world of non-commercial deliverables .

30:31.683 --> 30:33.774
There are some situations in which ,

30:33.784 --> 30:35.951
you know , that type of approach could

30:35.951 --> 30:38.173
probably be workable for some period of

30:38.173 --> 30:40.340
time . But one of the things about the

30:40.340 --> 30:42.340
services model of course is that it

30:42.340 --> 30:44.228
locks you into actually using the

30:44.228 --> 30:46.228
service provider , right ? It's not

30:46.228 --> 30:48.340
like you walk away with the IP at the

30:48.340 --> 30:50.451
end of the day . And so what has come

30:50.451 --> 30:52.874
about with this ever accelerating

30:52.884 --> 30:55.728
increasing digital technologies is that

30:55.738 --> 30:58.937
we really have to be more open , more

30:58.947 --> 31:01.003
flexible and more creative about the

31:01.003 --> 31:03.807
ways in which we are going to license

31:03.817 --> 31:06.738
this technology . And I know

31:06.748 --> 31:10.447
we're all very familiar with

31:10.488 --> 31:14.017
the current dear scheme , the unlimited

31:14.027 --> 31:16.305
rights , the government purpose rights ,

31:16.305 --> 31:18.488
restricted , limited rights . That's

31:18.498 --> 31:20.498
what we've got . We've had a lot of

31:20.498 --> 31:22.437
talk about specially negotiated

31:22.447 --> 31:24.671
licenses which are somewhere between

31:24.682 --> 31:26.682
restricted , limited and government

31:26.682 --> 31:28.722
purpose . And I will tell you that

31:28.732 --> 31:30.899
going forward , we're going to have to

31:30.899 --> 31:32.822
do more and more of specially

31:32.832 --> 31:36.472
negotiated licenses because in order to

31:36.482 --> 31:39.702
get the right balance to encourage

31:39.712 --> 31:41.552
companies to spend their private

31:41.562 --> 31:45.261
dollars to develop technology and so

31:45.271 --> 31:47.141
that we can meet all of these

31:47.151 --> 31:49.411
increasing demands and requirements and

31:49.421 --> 31:52.196
time frames , we need to ensure that

31:52.206 --> 31:54.566
there is an openness and understanding

31:54.576 --> 31:56.816
that even when we have a model and

31:56.826 --> 31:58.993
we've built it and we want to leverage

31:58.993 --> 32:00.882
it as part of a deliverable . For

32:00.882 --> 32:02.882
example , we want to make sure that

32:02.882 --> 32:04.770
when we're handing it over to the

32:04.770 --> 32:06.548
government customer , we're not

32:06.548 --> 32:08.548
necessarily immediately agreeing to

32:08.548 --> 32:10.855
access by , you know , competitors or

32:10.865 --> 32:13.105
maybe there's a period of time in which

32:13.115 --> 32:15.556
it's only made available inside the

32:15.566 --> 32:17.677
government . And then ultimately , it

32:17.677 --> 32:19.733
can be broader rights , kind of like

32:19.733 --> 32:21.844
unlimited rights , goes to government

32:21.844 --> 32:23.899
purpose rights or sorry , government

32:23.899 --> 32:26.010
purpose goes to unlimited rights . We

32:26.010 --> 32:28.010
could do something similar with the

32:28.010 --> 32:29.955
specially negotiated license for a

32:29.955 --> 32:31.899
certain period of time and then it

32:31.899 --> 32:34.010
evolves into broader rights . But you

32:34.010 --> 32:36.170
have to take this whole arsenal of

32:36.180 --> 32:40.079
various ways of licensing in order to

32:40.089 --> 32:42.449
really be able to meet these challenges .

32:42.459 --> 32:46.010
There's so much unknown about what

32:46.020 --> 32:48.242
you're going to need when you start out

32:48.242 --> 32:50.020
at the beginning of a project ,

32:50.020 --> 32:52.187
particularly something that's going to

32:52.187 --> 32:54.634
be years , decades in the making and

32:54.644 --> 32:56.866
you have to have that flexibility . And

32:56.866 --> 32:58.977
the other thing you really need to do

32:58.977 --> 33:01.284
is you really need to have better and

33:01.293 --> 33:04.854
more training for the people who are in

33:04.864 --> 33:07.264
the room , negotiating , writing the

33:07.274 --> 33:09.384
terms and conditions , writing the

33:09.394 --> 33:12.473
requirements to reference . You have to

33:12.484 --> 33:15.384
have a better , a more concrete

33:15.394 --> 33:17.616
understanding , understanding , there's

33:17.616 --> 33:19.727
always going to be ambiguity and just

33:19.727 --> 33:21.783
as things are accelerating , they're

33:21.783 --> 33:24.005
going to keep accelerating . So there's

33:24.005 --> 33:23.838
there are always going to be things

33:23.848 --> 33:26.015
you're gonna need to solve . There are

33:26.015 --> 33:28.237
always going to be disconnects . And so

33:28.237 --> 33:30.237
having people who really understand

33:30.237 --> 33:29.878
that and are willing to continue to

33:29.887 --> 33:32.637
work together over the course over the

33:32.647 --> 33:35.437
uh the lifetime of the , the um the

33:35.447 --> 33:38.258
program , the project , the the product ,

33:38.267 --> 33:40.297
those things continue to be really

33:40.307 --> 33:44.137
important . But the the key is really

33:44.147 --> 33:46.036
is flexibility , is training , is

33:46.036 --> 33:49.651
understanding is no fear of going

33:49.661 --> 33:52.182
outside of these standard boxes of data

33:52.192 --> 33:54.472
rights , but instead thinking outside

33:54.482 --> 33:57.442
the data rights boxes , but to how can

33:57.452 --> 33:59.619
we make this , how can we get you what

33:59.619 --> 34:02.671
you need without ensuring , you know ,

34:02.682 --> 34:06.572
giving away access to uh to undermine

34:06.582 --> 34:08.872
the return on investment . And that ,

34:08.882 --> 34:11.104
that's in my view , that's , that's the

34:11.104 --> 34:13.104
best way the most productive way to

34:13.104 --> 34:14.993
move forward to meet all of these

34:14.993 --> 34:17.326
incredible challenges that we're facing .

34:17.668 --> 34:19.890
That's great that these are really good

34:19.890 --> 34:21.835
talking points , things I think we

34:21.835 --> 34:23.946
definitely need to build on and it is

34:23.946 --> 34:25.890
how do we change that . That's the

34:25.890 --> 34:25.888
challenge we have laid out in front of

34:25.898 --> 34:29.319
us . Speaking of change and challenges ,

34:29.608 --> 34:33.279
Paul has the B 52 which is , I

34:33.309 --> 34:35.531
think we share the same birthday . It's

34:35.531 --> 34:37.799
a very seasoned aircraft . And so the

34:37.809 --> 34:39.999
challenge he faces is the B 52 is not

34:40.009 --> 34:42.438
going anywhere away any time soon . And

34:42.448 --> 34:45.178
we're now applying digital tools for

34:45.188 --> 34:47.898
new engines for new radar . So he's

34:47.908 --> 34:50.529
going to be maintaining a digital ,

34:51.379 --> 34:53.379
digitally modified aircraft and you

34:53.379 --> 34:55.323
probably still have mylar drawings

34:55.323 --> 34:57.323
hanging in the office somewhere for

34:57.323 --> 34:59.601
other parts of your weapon system . So ,

34:59.601 --> 35:01.601
what are the challenges first off ,

35:01.601 --> 35:01.000
what are you doing as far as digital

35:01.010 --> 35:03.399
transformation on those new programs

35:03.409 --> 35:05.465
with the engines and the radar ? And

35:05.465 --> 35:07.800
then how do you work when your aircraft

35:07.810 --> 35:09.643
is going to be maintained in two

35:09.643 --> 35:12.780
different worlds of technology ? Yeah .

35:12.790 --> 35:15.169
So I , I think , I think we're in a

35:15.179 --> 35:17.401
unique position , you know , with the ,

35:17.401 --> 35:19.457
the , the aircraft is very old and ,

35:19.457 --> 35:21.623
and , but right now we've got a lot of

35:21.623 --> 35:23.679
modifications going on to , on to it

35:23.679 --> 35:25.901
and , and , and we , we've actually got

35:25.901 --> 35:28.123
a really good government team and a lot

35:28.123 --> 35:30.290
of good government uh or a lot of good

35:30.290 --> 35:32.346
industry partners going on with us .

35:32.346 --> 35:34.401
But II , I think I probably ought to

35:34.401 --> 35:36.512
tell a little bit background what all

35:36.512 --> 35:38.735
is going on . I think everybody uh b 52

35:38.735 --> 35:40.846
has been around forever and everybody

35:40.846 --> 35:40.629
kind of has an opinion their own

35:40.639 --> 35:42.861
opinion on it . But I , I can just tell

35:42.861 --> 35:44.861
what a little bit background what's

35:44.861 --> 35:46.695
going on . So , in the early two

35:46.695 --> 35:48.695
thousands , you know , the B 52 was

35:48.695 --> 35:51.090
kind of probably in getting close to

35:51.100 --> 35:53.409
sunset . People were thinking and some ,

35:53.419 --> 35:56.290
some got parked today and then , uh ,

35:56.570 --> 35:59.050
program office was down to a crew .

35:59.060 --> 36:00.727
There just really weren't any

36:00.727 --> 36:03.060
modifications going on . But , you know ,

36:03.060 --> 36:05.449
long about that time , uh things

36:05.459 --> 36:07.626
changed , you know , things changed in

36:07.626 --> 36:09.737
the world , things changed in the air

36:09.737 --> 36:11.903
air force's view of what we needed for

36:11.903 --> 36:13.959
bombers . And , and the decision was

36:13.959 --> 36:13.909
made that the B 52 is gonna be around

36:13.919 --> 36:16.280
for another 30 years . And , and a lot

36:16.290 --> 36:18.290
of times people ask me , you know ,

36:18.290 --> 36:20.234
it's like , how does , how does an

36:20.234 --> 36:22.346
aircraft last that long ? How does it

36:22.346 --> 36:24.568
last for 60 years ? And the fact of the

36:24.568 --> 36:26.568
matter is it doesn't just last that

36:26.568 --> 36:28.734
long . It has to be , there's a lot of

36:28.734 --> 36:28.429
work all along the way , maintaining it ,

36:28.439 --> 36:30.780
sustaining it and modernizing it . And

36:30.790 --> 36:32.957
that's been happening all along on the

36:32.957 --> 36:35.500
B 52 . So when you think of how all

36:35.510 --> 36:38.129
that plays into , you know , digital

36:38.139 --> 36:40.195
data , digital modeling , modeling ,

36:40.195 --> 36:42.195
how the engineering was done , what

36:42.195 --> 36:44.083
we've got in effect is like seven

36:44.083 --> 36:46.199
decades worth of like a museum of

36:46.209 --> 36:48.153
different ways of state of the art

36:48.153 --> 36:50.209
engineering . Some of the really old

36:50.209 --> 36:52.265
stuff on engineering paper , some of

36:52.265 --> 36:54.209
the latest stuff models running on

36:54.209 --> 36:56.320
supercomputers , you know , we've got

36:56.320 --> 36:58.376
the full gamut of things . So um our

36:58.739 --> 37:00.739
modifications that we currently got

37:00.739 --> 37:03.679
going on uh are kind of in four areas

37:03.760 --> 37:06.479
uh integrating new weapons , LRSO

37:06.489 --> 37:08.433
hypersonic , a number of different

37:08.433 --> 37:12.070
weapons , number of

37:12.080 --> 37:14.610
modifications on com systems . So

37:17.270 --> 37:20.639
satellite links and tactical data links .

37:20.780 --> 37:22.836
And then the two , you mentioned the

37:22.836 --> 37:24.891
big ones , the radar modernization ,

37:24.891 --> 37:27.169
putting an ace or radar on and uh doing

37:27.179 --> 37:29.235
the Reen engine program , which also

37:29.235 --> 37:31.346
includes uh electrical power system ,

37:31.346 --> 37:34.120
hydraulic pumps , uh cockpit controls

37:34.129 --> 37:37.250
and displays . So very much a

37:37.260 --> 37:41.030
major modification time for the B 52 .

37:42.639 --> 37:44.806
Another piece of background I think is

37:44.806 --> 37:47.570
in 2019 , we were up at a Q with doctor

37:47.979 --> 37:50.540
and , and he , he suddenly told us

37:50.550 --> 37:52.772
during the meeting , I want you to be a

37:52.772 --> 37:54.828
pathfinder for digital engineering .

37:54.828 --> 37:56.828
That was when we still said digital

37:56.828 --> 37:58.994
engineering . And uh and so we weren't

37:58.994 --> 38:01.161
quite sure what that meant . So we had

38:01.161 --> 38:03.328
to go figure that out . And uh kind of

38:03.328 --> 38:05.439
what we figured out is that means you

38:05.439 --> 38:07.606
get to run through a lot of thorns and

38:07.606 --> 38:09.606
make a lot of wrong turns . You get

38:09.606 --> 38:11.828
kind of beat up . And uh you know , but

38:11.828 --> 38:13.717
one thing we haven't always known

38:13.717 --> 38:15.939
exactly which way to go . But one thing

38:15.939 --> 38:18.050
is is we've known where we want to go

38:18.050 --> 38:20.106
and why we're doing it and , and the

38:20.106 --> 38:22.328
reason we're doing it is to go faster .

38:22.328 --> 38:24.899
And so while we , there's no way you

38:24.909 --> 38:27.131
can do everything that people suggest .

38:27.131 --> 38:29.353
But so we , we've taken a definite kind

38:29.353 --> 38:31.576
of value approach . If it adds value to

38:31.576 --> 38:33.853
going faster and delivering capability ,

38:33.853 --> 38:36.090
we try to do it . If it's just doing it

38:36.100 --> 38:38.520
to be doing it , we don't do it . So ,

38:38.530 --> 38:41.770
so what have we done ? So we , one of

38:41.780 --> 38:43.724
the big things we had to deal with

38:43.724 --> 38:45.891
early on was trying to figure out what

38:45.891 --> 38:48.058
infrastructure we were going to put in

38:48.058 --> 38:50.113
place to hold models , hold data and

38:50.113 --> 38:52.336
whatnot . And it was clear a lot of our

38:52.336 --> 38:54.669
Air Force systems just weren't up to it .

38:54.669 --> 38:54.510
So we started working on different

38:54.520 --> 38:58.030
strategies on that and uh have made

38:58.040 --> 39:00.040
some headway and that's , that's an

39:00.040 --> 39:02.262
area where we've had to make some turns

39:02.262 --> 39:02.139
because quite frankly , since we've

39:02.149 --> 39:04.260
been doing that , the Air Force cloud

39:04.260 --> 39:06.260
infrastructure is caught up to with

39:06.260 --> 39:08.427
what we're doing . And so we're having

39:08.427 --> 39:11.040
to maneuver some there . Another area

39:11.050 --> 39:13.106
that we've spent a lot of time on is

39:13.106 --> 39:15.050
just collecting and digitizing and

39:15.050 --> 39:17.550
organizing the data we had in , in , in ,

39:17.689 --> 39:19.800
you know , in our , in our possession

39:19.800 --> 39:21.911
in our control so that it's much more

39:21.911 --> 39:23.911
available because if you want to go

39:23.911 --> 39:25.967
fast , you can't spend a lot of time

39:25.967 --> 39:25.929
looking for your data , looking for

39:25.939 --> 39:28.879
your models . The third thing is we

39:28.889 --> 39:32.469
spent a lot of time actively working on

39:32.479 --> 39:34.423
our culture and our mindset in our

39:34.423 --> 39:36.669
program office and with our contractors

39:36.790 --> 39:38.957
to get it , that we're going to switch

39:39.590 --> 39:41.812
and kind of the fourth thing . And it's

39:41.812 --> 39:43.812
been talked about a lot here this ,

39:43.812 --> 39:46.034
this afternoon is , is what we do about

39:46.034 --> 39:48.201
with , with contracting language and ,

39:48.201 --> 39:50.534
uh , dealing with the contractors . And ,

39:50.534 --> 39:52.423
and , uh , Adriana mentioned it's

39:52.423 --> 39:54.534
complicated and that , and our lesson

39:54.534 --> 39:56.146
learned is , it's definitely

39:56.146 --> 39:58.146
complicated and , but , but we have

39:58.146 --> 40:00.034
learned one thing and , and , and

40:00.034 --> 40:02.090
that's to deal with it early . Um If

40:02.090 --> 40:03.868
you just write something in the

40:03.868 --> 40:06.090
contract or if you're vague and think ,

40:06.090 --> 40:08.257
well , we'll work that out later . I I

40:08.257 --> 40:10.312
it just doesn't work out . The , the

40:10.312 --> 40:12.423
thing to do is to get , do your level

40:12.423 --> 40:14.423
best up front to get the government

40:14.423 --> 40:16.646
team and the , the industry team on the

40:16.646 --> 40:18.979
same sheet of where you're gonna be and ,

40:18.979 --> 40:21.034
and , and , and work from there . Um

40:22.030 --> 40:23.919
And we've seen some benefits , um

40:23.919 --> 40:25.863
definitely from these actions we ,

40:25.863 --> 40:28.030
we've had and , and , and one of the ,

40:28.030 --> 40:30.419
the key things is is we , we much , we

40:30.429 --> 40:32.762
have much more effective design reviews .

40:32.820 --> 40:35.098
So , and what I mean by that is in the ,

40:35.098 --> 40:37.320
in , in the past , you know , before we

40:37.320 --> 40:39.487
were doing this , we tended to go into

40:39.487 --> 40:41.431
a design review . We had literally

40:41.431 --> 40:43.979
thousands of slides uh at a , at a top

40:43.989 --> 40:46.156
level design review and , and it would

40:46.156 --> 40:49.729
just be mind numbing and we , we still

40:49.739 --> 40:51.850
have slide decks now to kind of guide

40:51.850 --> 40:54.128
the discussion , but almost all of our ,

40:54.128 --> 40:56.295
our , the technical part of our review

40:56.295 --> 40:58.295
is directly in the models , whether

40:58.295 --> 41:01.320
it's a 3D mechanical model or a or AM

41:01.330 --> 41:03.219
BS C , you know , system model on

41:03.219 --> 41:05.219
function . We do the design reviews

41:05.219 --> 41:07.386
directly in the models with them up on

41:07.386 --> 41:09.386
the screen . So the the experts can

41:09.386 --> 41:11.552
explain that everybody else can review

41:11.552 --> 41:13.719
it . We have a similar thing on our re

41:13.719 --> 41:15.941
engine program where we built a virtual

41:15.941 --> 41:17.886
model so that somebody can put the

41:17.886 --> 41:21.070
virtual reality goggles on and , and go

41:21.080 --> 41:23.136
in and see what the cockpit controls

41:23.136 --> 41:25.247
are gonna look like , what the uh how

41:25.247 --> 41:27.524
the engine is gonna be mounted and how ,

41:27.524 --> 41:29.747
what the access is to all the different

41:29.747 --> 41:31.913
parts of the engines . And we did that

41:31.913 --> 41:34.024
so that we could get early input from

41:34.024 --> 41:36.191
the operators and from the maintainers

41:36.191 --> 41:38.358
on , you know , with the their , their

41:38.358 --> 41:40.524
ability , they're , they're experts on

41:40.524 --> 41:42.747
maintaining planes , operating planes ,

41:42.747 --> 41:45.024
not at looking at engineering drawings ,

41:45.024 --> 41:44.879
this put it in a context where we could

41:44.889 --> 41:46.889
get direct input from them and it's

41:46.889 --> 41:48.850
been really effective . Um

41:51.770 --> 41:53.881
And I , and I tell you on the culture

41:53.881 --> 41:57.260
change , I uh there's a uh a benefit to

41:57.270 --> 41:59.381
it but , you know , it's easier , you

41:59.381 --> 42:01.492
know , it's hard to measure . But one

42:01.492 --> 42:03.548
thing I have noticed is is that in a

42:03.548 --> 42:05.492
number of our programs , we've got

42:05.492 --> 42:07.603
places where people aren't wanting to

42:07.603 --> 42:09.826
make documents . So what I mean by that

42:09.826 --> 42:11.326
is uh instead of writing a

42:11.326 --> 42:13.492
specification document , the teams are

42:13.492 --> 42:15.548
coming back and saying , hey , we've

42:15.548 --> 42:17.659
been talking to the contractor and we

42:17.659 --> 42:19.826
think what we wanna do is just , we're

42:19.826 --> 42:21.881
just gonna do this indoors , meaning

42:21.881 --> 42:23.770
the , the requirements database ,

42:23.770 --> 42:23.594
because the guys that have to keep

42:23.604 --> 42:25.826
track of 1000 requirements , as soon as

42:25.826 --> 42:27.660
they realize they can do it in a

42:27.660 --> 42:29.882
database , they're kind of done wanting

42:29.882 --> 42:31.993
to do it in a document . So , so II I

42:31.993 --> 42:33.771
think our culture is definitely

42:33.771 --> 42:36.419
shifting . So um you , you mentioned

42:36.429 --> 42:38.596
something about , you know , how do we

42:38.596 --> 42:40.818
operate in both worlds ? So we , it's ,

42:40.818 --> 42:42.985
there isn't really a both in my mind .

42:42.985 --> 42:45.979
There's a many worlds because uh b 52

42:45.989 --> 42:47.989
is so old . There's a , we've got a

42:47.989 --> 42:50.211
variety of the way things were designed

42:50.211 --> 42:52.659
and , and documented and , and the fact

42:52.669 --> 42:54.891
is we already are and we , we have been

42:54.899 --> 42:57.066
for a long time and , and we , we have

42:57.066 --> 42:59.232
to kind of keep doing what we're doing

42:59.232 --> 43:01.455
and that's , that's to focus on when we

43:01.455 --> 43:03.566
do something new , we really focus on

43:03.566 --> 43:05.732
what the interfaces to the old are and

43:05.732 --> 43:07.955
we get that down and , and we work from

43:07.955 --> 43:09.955
there and , and , and , and I don't

43:09.955 --> 43:11.843
ever a time when we're completely

43:11.843 --> 43:14.066
whatever digital and air quotes means ,

43:14.066 --> 43:16.288
I think we're gonna , we're gonna stick

43:16.288 --> 43:18.399
with this value approach and say , is

43:18.399 --> 43:20.754
this a piece that we're gonna , it's

43:20.764 --> 43:22.725
gonna add value to sustaining or

43:22.735 --> 43:25.034
modifying or getting capability and

43:25.044 --> 43:27.745
keeping capability in the field . And

43:27.975 --> 43:29.975
in the one area that I look at that

43:29.975 --> 43:32.031
isn't related to modifications is is

43:32.031 --> 43:34.086
our structural uh program . So we're

43:34.086 --> 43:36.308
we're looking at doing using all modern

43:36.308 --> 43:38.253
tools for our structural integrity

43:38.253 --> 43:40.364
program . Uh If we're gonna be around

43:40.364 --> 43:42.419
for another 30 years , we need to be

43:42.419 --> 43:44.475
using modern approaches on it rather

43:44.479 --> 43:46.257
than you know , calculations on

43:46.257 --> 43:49.959
engineering papers . So um bottom line

43:50.620 --> 43:52.929
we're doing , we're making this

43:52.939 --> 43:54.979
conversion to data and models where

43:54.989 --> 43:57.156
digital data and models where it makes

43:57.156 --> 43:59.045
sense , you know , it can help us

43:59.045 --> 44:01.820
accelerate . Great . Thanks , Gretchen .

44:02.189 --> 44:04.189
We usually don't think of the Intel

44:04.189 --> 44:06.356
corporation when we talk about our big

44:06.356 --> 44:08.522
dod O Ems . But we know you're heavily

44:08.522 --> 44:10.633
involved working with our , the other

44:10.633 --> 44:13.120
uh our partners . Uh The one thing that

44:13.129 --> 44:15.159
we have talked about is a shrinking

44:15.169 --> 44:17.336
supply base . We talk about the impact

44:17.336 --> 44:20.820
of COVID and things changing . Um not

44:20.830 --> 44:22.997
unique to the public sector . I'm sure

44:22.997 --> 44:25.052
you guys are dealing with that . Can

44:25.052 --> 44:27.219
you tell us about what you're doing to

44:27.219 --> 44:29.386
leverage current and future technology

44:29.386 --> 44:28.840
to attack these types of issues in the

44:28.850 --> 44:31.100
supply chain and what you're seeing .

44:32.860 --> 44:34.916
And , and again , thanks so much for

44:34.916 --> 44:36.971
letting me participate . It's really

44:36.971 --> 44:39.159
fun to be up here because we not only

44:39.169 --> 44:41.391
cooperate together , we collaborate . I

44:41.391 --> 44:43.725
think all of us here in different forms .

44:43.725 --> 44:46.209
And honestly , um this morning or

44:46.219 --> 44:48.163
earlier today , someone was really

44:48.163 --> 44:50.108
talking about the fact that what's

44:50.108 --> 44:52.052
going on right now is changing the

44:52.052 --> 44:54.108
business model and it absolutely has

44:54.108 --> 44:56.530
done that for our corporation . So not

44:56.540 --> 44:58.899
only have we been very focused on open

44:58.909 --> 45:01.120
programming and software , which for a

45:01.129 --> 45:03.439
hardware company sounds a little

45:03.800 --> 45:06.959
counterintuitive . Um But we also want

45:06.969 --> 45:09.790
to make sure that in , in the way that

45:09.800 --> 45:12.050
we're talking about a supply chain that

45:12.060 --> 45:14.669
you can not only know that it's secure

45:14.679 --> 45:17.570
from our perspective intel , but for

45:17.580 --> 45:19.802
the partners that we I'm working with .

45:19.802 --> 45:21.913
So when I mention a , a change in our

45:21.913 --> 45:24.136
business model , what I mean by that is

45:24.136 --> 45:26.864
we now have a , a factory and we have

45:26.875 --> 45:28.945
um at least one person on this table

45:28.955 --> 45:31.011
who we're already or one company . I

45:31.011 --> 45:33.122
should say that we're already working

45:33.122 --> 45:35.288
with where we're cooperatively working

45:35.288 --> 45:37.011
together to build a particular

45:37.011 --> 45:39.304
processor that's needed in terms of a

45:39.314 --> 45:41.425
fit for purpose for what you all do .

45:41.465 --> 45:43.445
So in some cases , our commercial

45:43.455 --> 45:46.050
products will work fine and the truth

45:46.060 --> 45:48.282
is it's from the , from the sand to the

45:48.282 --> 45:51.229
silicon and we match every single step

45:51.239 --> 45:53.370
along the way . And then we basically

45:53.379 --> 45:56.290
hand that audit trail and that full

45:56.300 --> 45:58.229
description of what has happened

45:58.239 --> 46:00.699
through the entire process to whomever

46:00.709 --> 46:02.820
we work with , whether it be an OEM ,

46:02.820 --> 46:04.653
whether it be one of the defense

46:04.653 --> 46:06.580
contractors and we are ultimately

46:06.590 --> 46:08.770
working together to in some cases ,

46:08.780 --> 46:11.449
even with our uh companies that were

46:12.060 --> 46:14.540
competing against , we are talking with

46:14.550 --> 46:16.729
them also about building in our

46:16.739 --> 46:19.449
fabrication plants . And it's important

46:19.459 --> 46:21.292
we're talking all about national

46:21.292 --> 46:23.348
security . That's part of the reason

46:23.348 --> 46:25.348
why we're building more fabrication

46:25.348 --> 46:27.515
plants in the United States . And that

46:27.515 --> 46:29.681
we really do want to make sure that we

46:29.681 --> 46:29.459
have that audit traceability that we

46:29.469 --> 46:32.084
can hand all of that again from the

46:32.094 --> 46:34.514
sand to all the different components to

46:34.524 --> 46:36.935
the end process , the end product , the

46:36.945 --> 46:40.854
processor , um a technology , memory

46:40.864 --> 46:43.014
chip , whatever it might be that we

46:43.024 --> 46:45.024
hand that to whomever we're working

46:45.024 --> 46:47.344
with and that we do that cooperatively .

46:47.645 --> 46:49.812
And then when I talked about and , and

46:49.812 --> 46:51.923
um Adriana mentioned this that really

46:51.923 --> 46:54.149
thinking about being open . So I

46:54.159 --> 46:56.270
mentioned an open programming model .

46:56.270 --> 46:58.326
So we really are focused on the fact

46:58.326 --> 47:00.548
that we want you all to have code reuse

47:00.548 --> 47:03.050
so that you don't have to have software

47:03.060 --> 47:05.171
to find for each and every one of the

47:05.171 --> 47:07.338
products . So how do you do that ? You

47:07.338 --> 47:09.580
divine , you design something and

47:09.590 --> 47:11.701
there's a , a organization called one

47:11.701 --> 47:14.840
api dot org that is a bunch of

47:14.850 --> 47:16.794
collaboration between software and

47:16.794 --> 47:19.040
hardware companies . And we now have a

47:19.050 --> 47:21.272
software product that will allow you to

47:21.272 --> 47:24.199
use whether it's a vector or graphic

47:24.209 --> 47:27.479
processing unit or a standard CPU or

47:27.489 --> 47:29.378
whatever the next fit for purpose

47:29.378 --> 47:31.600
product is that we'll all work together

47:31.600 --> 47:33.711
to design , that the software will be

47:33.719 --> 47:35.810
able to run on that . The idea of

47:35.820 --> 47:38.129
course is there's specific intrinsics

47:38.139 --> 47:40.250
in each one of those that you want to

47:40.250 --> 47:42.361
know what those are to guarantee that

47:42.361 --> 47:44.528
you've got the right encryption or the

47:44.528 --> 47:46.583
right levels of security or that you

47:46.583 --> 47:48.695
can create secure enclaves for all of

47:48.695 --> 47:50.917
that data that you want to make sure no

47:50.917 --> 47:53.028
one's able to break into . But if you

47:53.028 --> 47:55.250
design that in a way that allows people

47:55.250 --> 47:57.472
to then say , oh , that's going to work

47:57.472 --> 47:59.639
on the B 52 . But if we come up with a

47:59.639 --> 48:01.583
next generation pro product , that

48:01.583 --> 48:04.489
ultimately some of that software that

48:04.500 --> 48:07.800
makes sense can be used in that new fit

48:07.810 --> 48:09.979
for purpose hardware . And that , you

48:09.989 --> 48:12.280
know , again , we've handed that audit

48:12.290 --> 48:14.629
trail that traceability to whomever

48:14.639 --> 48:16.639
we're working with or whether it be

48:16.639 --> 48:18.750
people in the audience or a brand new

48:18.750 --> 48:20.972
company that doesn't even exist today ,

48:20.972 --> 48:23.195
that we want to make sure that you have

48:23.195 --> 48:25.361
that capability and that you can reuse

48:25.361 --> 48:27.472
and that you can be flexible and that

48:27.472 --> 48:29.695
you can move on the fly and then you're

48:29.695 --> 48:31.750
not having to figure out that , oh ,

48:31.750 --> 48:33.583
that's code that we did for some

48:33.583 --> 48:35.695
particular product that happens to be

48:35.695 --> 48:37.969
something that maybe was a PDP 11 back

48:37.979 --> 48:39.812
in the day when a company called

48:39.820 --> 48:41.876
digital Equipment doesn't even exist

48:41.876 --> 48:43.987
anymore . You know what I mean ? That

48:43.987 --> 48:45.987
you really think of about how do we

48:45.987 --> 48:48.209
create those things that then allow you

48:48.209 --> 48:50.264
to process that forward . And one of

48:50.264 --> 48:52.487
the things that you probably don't know

48:52.487 --> 48:52.095
about Intel Corporation is that we do

48:52.105 --> 48:55.516
have over 20,000 software engineers and

48:55.525 --> 48:57.747
a lot of those folks are working on the

48:57.747 --> 49:00.081
underpinnings of what software is today .

49:00.081 --> 49:02.192
And that is the compilers that is the

49:02.192 --> 49:04.358
libraries that are needed , whether it

49:04.358 --> 49:06.815
be in an A I context and you've got a ,

49:06.825 --> 49:08.501
an open doll or you've got an

49:08.511 --> 49:10.572
application language that you need ,

49:10.582 --> 49:13.422
that we supply all of those that work

49:13.431 --> 49:15.771
for . Yes , absolutely . Optimize best

49:15.781 --> 49:17.892
for Intel hardware . But the truth is

49:17.892 --> 49:20.170
they work on everybody else's hardware ,

49:20.170 --> 49:22.503
they work on a MD , they work on others .

49:22.503 --> 49:24.725
So you'll get the advantage and then if

49:24.725 --> 49:26.892
you can program at that level and then

49:26.892 --> 49:29.059
you've been handed the absolute supply

49:29.059 --> 49:31.862
chain details from the silicon back to

49:31.872 --> 49:33.872
the sand , then you really have the

49:33.872 --> 49:36.039
security that really matters to all of

49:36.039 --> 49:38.870
us here . That's great . We , we

49:38.879 --> 49:40.823
started to get some questions . So

49:40.823 --> 49:42.879
thank you for the questions . Uh I'm

49:42.879 --> 49:45.101
gonna kind of combine a couple together

49:45.101 --> 49:46.879
because I think there's uh some

49:46.879 --> 49:48.990
crossover . And the first one was one

49:48.990 --> 49:51.046
Ryan , you mentioned something about

49:51.046 --> 49:52.935
the uh tools interoperability and

49:52.935 --> 49:56.010
coming together as a joint community on

49:56.020 --> 49:57.964
what tools do we use and how do we

49:57.964 --> 50:00.570
share information . And so this is a

50:00.580 --> 50:02.580
question to everybody that wants to

50:02.580 --> 50:04.747
participate . But I'm gonna start with

50:04.747 --> 50:06.913
you , Ryan is , you know , what are we

50:06.913 --> 50:09.080
doing in that area ? What's going on ?

50:09.080 --> 50:11.136
And then I think about as we , if we

50:11.136 --> 50:13.247
standardize on tools , what does that

50:13.247 --> 50:17.179
do to IP to competition .

50:17.199 --> 50:19.790
And so what efforts are you undertaking

50:19.800 --> 50:21.967
right now ? And how are you doing that

50:21.967 --> 50:24.133
to ensure competition at the same time

50:24.133 --> 50:26.356
as ensuring openness ? Yes . So I think

50:26.356 --> 50:28.467
the question was about the balance of

50:28.467 --> 50:30.780
standardizing tools with the continuous

50:30.790 --> 50:32.846
competition , even the comments that

50:32.846 --> 50:34.901
the chief made , you know , for us a

50:34.901 --> 50:37.123
couple of things , I don't think you're

50:37.123 --> 50:39.179
ever going , you would never want to

50:39.179 --> 50:40.901
get to the point where you say

50:40.901 --> 50:42.846
everybody has to use this one tool

50:42.846 --> 50:44.957
across all suppliers or everyone that

50:44.957 --> 50:47.179
would kill the idea of competition , it

50:47.179 --> 50:49.346
would kill the idea of innovation . At

50:49.346 --> 50:51.419
the same time within single business

50:51.429 --> 50:53.540
areas . I think lots of organizations

50:53.540 --> 50:55.485
are seeing the same thing when you

50:55.485 --> 50:57.596
balance decentralized decision making

50:57.596 --> 50:59.762
on what tool you want to use with some

50:59.762 --> 51:02.272
centralized efficiency . And so within

51:02.282 --> 51:04.338
Northrop and I know many people have

51:04.338 --> 51:06.393
the same kind of look to say , let's

51:06.393 --> 51:08.171
wrangle it in a bit so that the

51:08.171 --> 51:10.171
investments we make go a little bit

51:10.171 --> 51:12.338
further . And so for us , we're trying

51:12.338 --> 51:14.115
to make sure that we make smart

51:14.115 --> 51:16.282
decisions on what that ecosystem looks

51:16.282 --> 51:18.393
like for us , right ? And that we can

51:18.393 --> 51:20.560
then go and invest heavily into making

51:20.560 --> 51:22.782
sure that we complete the thread across

51:22.782 --> 51:24.893
those tools , right ? Because to us ,

51:24.893 --> 51:27.004
the complete thread is so valuable to

51:27.004 --> 51:29.115
get there and then the investment can

51:29.115 --> 51:31.338
go into interoperability . Now , we can

51:31.338 --> 51:33.393
say within that ecosystem , that one

51:33.393 --> 51:35.560
group is using , can we make sure that

51:35.560 --> 51:37.282
those API S and interfaces are

51:37.282 --> 51:39.338
standardized , we make sure they can

51:39.338 --> 51:41.504
interoperate with these agreed to APIS

51:41.870 --> 51:44.092
because when we have partners and other

51:44.092 --> 51:46.092
ecosystems , we know we're going to

51:46.092 --> 51:48.314
have to be able to interface there . So

51:48.314 --> 51:50.370
what I've been really pushing for is

51:50.370 --> 51:52.426
make the right consolidation of tool

51:52.426 --> 51:54.314
choices , but make sure that that

51:54.314 --> 51:56.370
ecosystem is interoperable with more

51:56.370 --> 51:58.949
standards . And A I can , I can chime

51:58.959 --> 52:01.070
in with a little bit of the Air Force

52:01.070 --> 52:03.126
perspective too where I think uh the

52:03.126 --> 52:05.459
Air Force has chosen a tool in one case ,

52:05.459 --> 52:07.459
right . So for PLM , we have S team

52:07.459 --> 52:06.699
center , which is our , our

52:06.709 --> 52:08.820
acknowledged tool of choice . I think

52:08.820 --> 52:10.931
in many other tool cases , but that's

52:10.931 --> 52:13.098
not a path we probably gonna go down ,

52:13.098 --> 52:15.265
right ? We can talk about CAD tools or

52:15.265 --> 52:14.860
model based system engineering tools .

52:14.870 --> 52:16.981
We're probably not gonna go prescribe

52:16.981 --> 52:19.449
one moving forward . It creates an

52:19.459 --> 52:21.626
interesting , you know , as we have to

52:21.626 --> 52:23.903
interact with Lockheed Boeing North or ,

52:23.903 --> 52:25.848
and a bunch of others , it's not a

52:25.848 --> 52:27.903
really viable path often but getting

52:27.903 --> 52:30.181
down to what data types , data formats ,

52:30.181 --> 52:32.348
data standards do we want to integrate

52:32.348 --> 52:34.570
or be interoperable back to the chief ,

52:34.570 --> 52:36.737
collaborate around . That's one of the

52:36.737 --> 52:38.848
things that we want to focus on . And

52:38.848 --> 52:38.489
then when it comes to actually

52:38.500 --> 52:40.611
purchasing the tools that we're going

52:40.611 --> 52:42.611
to , you know , ingest and read and

52:42.611 --> 52:44.444
manipulate the data with , uh it

52:44.444 --> 52:46.500
becomes being smart about how you do

52:46.500 --> 52:48.722
that investment , right ? So one of the

52:48.722 --> 52:50.722
things that we started to do uh now

52:50.722 --> 52:49.909
that we've been able to pull a little

52:49.919 --> 52:51.697
bit of enterprise resourcing to

52:51.697 --> 52:53.770
establish a uh kind of common

52:53.780 --> 52:55.947
enterprise level tool environment . We

52:55.947 --> 52:58.113
can read how much uh each , you know ,

52:58.113 --> 53:00.058
kind of how frequently are reading

53:00.058 --> 53:02.280
close to that , that limit of the tools

53:02.280 --> 53:04.391
that we have available . And so , you

53:04.391 --> 53:03.879
know , when we start to approach that

53:03.889 --> 53:05.945
limit , all right , maybe that's the

53:05.945 --> 53:08.111
next , you know , tranche of the tools

53:08.111 --> 53:10.278
we need to go buy more of , right . So

53:10.278 --> 53:09.879
having the right , you know , tracking

53:09.889 --> 53:12.449
the right metrics around tool usage .

53:12.639 --> 53:14.695
Uh you , you can be a little smarter

53:14.695 --> 53:16.750
about which ones to buy more without

53:16.750 --> 53:19.028
prescribing one um for a specific type .

53:20.179 --> 53:22.290
Yeah . And if I can add to one of the

53:22.290 --> 53:24.401
things that we've also noticed too is

53:24.401 --> 53:26.568
that because some of the technology in

53:26.568 --> 53:28.790
some cases is a little bit dated and so

53:28.790 --> 53:30.901
there isn't always going to be an API

53:30.901 --> 53:33.123
that makes it easy . So how do you work

53:33.123 --> 53:35.123
together to also in some cases , do

53:35.123 --> 53:37.346
translation tools ? How do you have the

53:37.346 --> 53:39.568
ability where OK , what you really want

53:39.568 --> 53:41.679
to do is bring the best technology to

53:41.679 --> 53:43.679
the data , not the data to , to the

53:43.679 --> 53:45.790
technology . So if you have something

53:45.790 --> 53:47.735
that's running in a big HPC system

53:47.735 --> 53:49.790
that's using NVIDIA GP US , and it's

53:49.790 --> 53:51.919
like at some huge amount of wattage

53:51.929 --> 53:53.985
which is not at all what you want to

53:53.985 --> 53:55.985
use at the edge . And so how do you

53:55.985 --> 53:58.318
then take that code ? And in some cases ,

53:58.318 --> 54:00.373
how do you translate that ? Maybe so

54:00.373 --> 54:02.373
that it can be run in more of a , a

54:02.373 --> 54:04.596
standard environment . Um And so that's

54:04.596 --> 54:06.540
also some of the things that uh we

54:06.540 --> 54:08.318
intel are trying to do with the

54:08.318 --> 54:10.429
compilers and the tools to be able to

54:10.429 --> 54:12.318
help support that not everybody's

54:12.318 --> 54:14.429
created those API S to make it easy .

54:14.429 --> 54:16.262
Um And so what are those kind of

54:16.262 --> 54:18.151
typical translation tools that we

54:18.151 --> 54:20.751
should be able to be to supply honestly

54:20.761 --> 54:22.892
into the open community ? So most of

54:22.902 --> 54:24.791
the ones that we've done are just

54:24.791 --> 54:26.958
available and you can go to github and

54:26.958 --> 54:29.124
get them and be able to use them . And

54:29.124 --> 54:31.235
that's probably what's gonna continue

54:31.235 --> 54:33.069
to happen until we get that more

54:33.069 --> 54:35.013
standardized kind of environment .

54:35.013 --> 54:38.159
Anybody else ? If not uh next question ,

54:39.310 --> 54:42.040
will the use of open source software be

54:42.050 --> 54:44.959
encouraged as we keep moving forward in

54:44.969 --> 54:47.590
our technology dependent world thoughts

54:47.600 --> 54:51.479
on open source software ? OK . I'll

54:51.489 --> 54:55.350
bite . Um So , um first of

54:55.360 --> 54:57.449
all , um I don't think that it is

54:57.459 --> 55:00.500
possible at this point to keep up with

55:00.510 --> 55:02.232
the pace of technology without

55:02.232 --> 55:04.290
leveraging open source software . We

55:04.300 --> 55:07.179
have absolutely gone from a model where

55:07.189 --> 55:09.540
people are really developing their own

55:09.550 --> 55:11.830
code from scratch . But instead that

55:11.840 --> 55:14.080
reusing and whether that's reusing

55:14.090 --> 55:17.075
proprietary code or using or using

55:17.085 --> 55:19.252
leveraging open source software , it's

55:19.252 --> 55:21.418
out there . Um One of the great things

55:21.418 --> 55:23.775
about it is that there is a high level

55:23.785 --> 55:26.196
of transparency , you get the code ,

55:26.206 --> 55:28.595
you know exactly what's in it . You can

55:28.605 --> 55:30.716
do , you know with it what you want ,

55:30.716 --> 55:32.986
but you have that transparency which is

55:32.996 --> 55:36.256
fantastic . Um I will say though that

55:36.496 --> 55:40.035
um from a licensing legal

55:40.045 --> 55:43.662
perspective , um it is one of the most

55:43.672 --> 55:46.572
annoying things ever . Um and

55:46.582 --> 55:49.602
basically what you have to understand

55:49.612 --> 55:53.491
is you get this code package and it has

55:53.501 --> 55:55.723
what's called a top level license which

55:55.723 --> 55:57.779
says , OK , you use this package and

55:57.779 --> 56:00.001
it's under some wonderful license , you

56:00.001 --> 56:02.501
know , Apache I something where you can

56:02.511 --> 56:04.622
do anything , you don't need to worry

56:04.622 --> 56:06.455
about anything other than really

56:06.455 --> 56:08.689
attribution . Um And then in that

56:08.699 --> 56:10.699
you've got a bunch of different sub

56:10.719 --> 56:13.429
files and you've got somebody who

56:13.439 --> 56:15.495
decided that they wanted to put in a

56:15.500 --> 56:18.080
really restrictive license and that

56:18.090 --> 56:19.979
kind of got swept up in the whole

56:19.979 --> 56:22.034
package . And then suddenly when you

56:22.034 --> 56:24.201
use that whole package and you combine

56:24.201 --> 56:25.979
it with your proprietary code ,

56:25.979 --> 56:27.868
suddenly you have put all of your

56:27.868 --> 56:29.909
proprietary code at risk because

56:29.919 --> 56:33.370
somebody in that whole package used ,

56:33.379 --> 56:35.157
for example , you know , a very

56:35.157 --> 56:37.689
aggressive g former GPL license or

56:37.699 --> 56:39.679
something like that . So there are

56:39.689 --> 56:42.379
tricks to open source software . And

56:42.389 --> 56:45.639
one of the things that is from , from

56:45.649 --> 56:48.100
the perspective in particular of

56:48.110 --> 56:50.110
somebody who , you know , an entity

56:50.110 --> 56:52.110
that is trying to leverage all this

56:52.110 --> 56:54.332
open source software and package it and

56:54.332 --> 56:57.300
deliver it is that the way again , the

56:57.310 --> 56:59.199
way the commercial world works in

56:59.199 --> 57:01.600
commercial licensing , they say here

57:01.610 --> 57:03.777
we're delivering our software . And by

57:03.777 --> 57:05.721
the way to the extent that they're

57:05.721 --> 57:07.610
creating includes any third party

57:07.610 --> 57:09.443
software , including open source

57:09.443 --> 57:11.610
software . We're not licensing that to

57:11.610 --> 57:13.777
you that's licensed on its own terms .

57:13.777 --> 57:15.888
We're not responsible for it . Have a

57:15.888 --> 57:17.999
nice day . And so the problem is that

57:17.999 --> 57:20.179
for a government contractor who is

57:20.189 --> 57:22.790
delivering something to the customer ,

57:22.800 --> 57:25.159
we do not have the ability to say , you

57:25.169 --> 57:28.169
know , it's just you guys just go do it

57:28.179 --> 57:30.401
right . We have to stand behind what we

57:30.401 --> 57:32.568
deliver , we have to go through it and

57:32.568 --> 57:34.623
basically make sure all the licenses

57:34.623 --> 57:36.401
are in place to ensure that our

57:36.401 --> 57:38.800
customers can do what we , what they ,

57:38.810 --> 57:41.088
what we have promised them they can do .

57:41.088 --> 57:44.379
So it is a , it is a fundamental

57:44.389 --> 57:47.239
tool uh in using open source software ,

57:47.250 --> 57:49.361
you need to handle it correctly , you

57:49.361 --> 57:51.583
need to pay attention to the licenses .

57:51.583 --> 57:53.417
You need to pay attention to the

57:53.417 --> 57:55.639
upgrades , the security aspects of it .

57:55.639 --> 57:58.270
Um But at the same time , um you know ,

57:58.280 --> 58:01.389
it's , it's a headache for lawyers . Um ,

58:01.399 --> 58:03.320
and there , there are some risks

58:03.330 --> 58:05.719
associated with it that's been fairly

58:05.729 --> 58:08.179
low risk . Um But you notice that there

58:08.189 --> 58:11.959
are some companies that have purchased

58:11.969 --> 58:14.025
open source products and then slowly

58:14.025 --> 58:16.080
but surely they begin to modify them

58:16.080 --> 58:18.280
into proprietary code and slowly but

58:18.290 --> 58:20.560
surely change the terms . And those are

58:20.570 --> 58:22.514
the types of things as you upgrade

58:22.514 --> 58:24.737
because obviously you want your code to

58:24.737 --> 58:26.792
stay updated as you update . You may

58:26.792 --> 58:28.848
notice that the terms are changing a

58:28.848 --> 58:31.070
little bit . You just , you have to pay

58:31.070 --> 58:33.348
attention to that and that's something ,

58:33.348 --> 58:35.681
you know , you just have to be aware of .

58:35.681 --> 58:37.737
That's great , appreciate that . And

58:37.737 --> 58:39.903
that pretty much takes us about to the

58:39.903 --> 58:39.800
end of the panel . I would like to

58:39.810 --> 58:41.754
thank all of the panel members for

58:41.754 --> 58:44.032
joining us . It's been very insightful .

58:44.032 --> 58:46.199
I think it did exactly what we want is

58:46.199 --> 58:48.310
to tee up the discussion . We have to

58:48.310 --> 58:50.088
have areas that we have to work

58:50.088 --> 58:52.254
together on and greatly appreciate you

58:52.254 --> 58:54.421
taking the time to come in and be part

58:54.421 --> 58:54.239
of the , of this here .