WEBVTT

00:00.009 --> 00:02.789
I was saying it's nice to have a lively

00:02.799 --> 00:04.966
AM crowd . So hopefully everyone's had

00:04.966 --> 00:07.969
coffee and I'm so pleased to welcome

00:07.980 --> 00:10.279
you all here today to the first ever

00:10.289 --> 00:13.789
guide industry insights forum . Uh So

00:13.800 --> 00:16.469
the forum is to focus on our global

00:16.479 --> 00:18.790
information domination dominance

00:18.799 --> 00:21.139
experiment series . And let me just be

00:21.149 --> 00:23.260
clear at the top on our purpose . And

00:23.260 --> 00:25.371
then I'll , I'll kind of walk through

00:25.371 --> 00:27.593
some framing to help motivate the day .

00:27.593 --> 00:29.427
Our goal today is to lay out our

00:29.427 --> 00:31.482
warfighter capability needs and help

00:31.482 --> 00:33.649
you all our partners and industry find

00:33.649 --> 00:35.649
the right technology solutions . So

00:35.649 --> 00:37.871
that's where we want to get to . Um let

00:37.871 --> 00:39.871
me dive right into some context and

00:39.871 --> 00:41.927
motivation on how we want to connect

00:41.927 --> 00:43.760
our critical needs with the best

00:43.760 --> 00:45.871
technology . And then I'll close with

00:45.871 --> 00:45.750
kind of what I'm hoping we'll all

00:45.759 --> 00:48.240
accomplish today . Um So from the

00:48.250 --> 00:50.028
Department of Defense , Digital

00:50.028 --> 00:52.209
Technology has just incredible promise

00:52.220 --> 00:54.259
uh for frankly our full range of

00:54.270 --> 00:56.270
activities from inside the Pentagon

00:56.270 --> 00:58.492
headquarter elements to the battlefield

00:58.492 --> 01:00.603
itself . And just as a couple of kind

01:00.603 --> 01:02.381
of motivating examples , we see

01:02.381 --> 01:04.603
tremendous progress in technology areas

01:04.603 --> 01:06.603
like generative A I , but also just

01:06.610 --> 01:08.721
digital decision support , predictive

01:08.721 --> 01:10.680
tools and all of these are built

01:10.690 --> 01:13.029
through a relentless focus both inside

01:13.040 --> 01:14.707
and outside the government on

01:14.707 --> 01:16.429
experimentation and continuous

01:16.429 --> 01:18.540
development . In parallel , there's a

01:18.540 --> 01:20.707
growing focus inside the department on

01:20.707 --> 01:22.540
how to adopt more mature digital

01:22.540 --> 01:24.762
capabilities at speed and scale earlier

01:24.762 --> 01:27.910
this year . Um The team in CD A O laid

01:27.919 --> 01:29.975
out a strategy to ensure warfighting

01:29.975 --> 01:32.086
advantage in everything from enhanced

01:32.086 --> 01:34.086
battle space awareness and adaptive

01:34.086 --> 01:35.863
force planning , to precise and

01:35.863 --> 01:37.919
resilient kill chain execution , all

01:37.919 --> 01:39.530
supported by agile adaptable

01:39.530 --> 01:42.184
sustainment resources . And A I , for

01:42.194 --> 01:44.138
example , is playing an increasing

01:44.138 --> 01:46.138
important role in our alliances and

01:46.138 --> 01:48.194
partnerships around the world . Just

01:48.194 --> 01:50.194
yesterday , I signed a statement of

01:50.194 --> 01:50.065
intent with our partners in Singapore

01:50.074 --> 01:52.745
on A I digital and data partnership .

01:53.495 --> 01:55.606
These types of partnerships with like

01:55.606 --> 01:57.717
minded countries are critical because

01:57.717 --> 01:59.551
digital adoption is broader than

01:59.551 --> 02:01.606
technology alone , that the adoption

02:01.606 --> 02:03.773
requires the right policy and security

02:03.773 --> 02:05.717
enables enablers . They have to be

02:05.717 --> 02:07.439
compatible with our values and

02:07.439 --> 02:09.551
interoperable with our partners to be

02:09.551 --> 02:11.773
truly meaningful . Now , it's important

02:11.773 --> 02:13.939
to recognize that this type of digital

02:13.939 --> 02:16.051
adoption is not just happening in the

02:16.051 --> 02:18.273
department . It's also happening by our

02:18.273 --> 02:17.880
our competitors and potential

02:17.889 --> 02:19.960
adversaries countries like China and

02:19.970 --> 02:22.559
Russia , Iran and North Korea and these

02:22.570 --> 02:24.570
countries have demonstrated a clear

02:24.570 --> 02:26.737
intent to harness the power of A I for

02:26.737 --> 02:28.570
their own military and strategic

02:28.570 --> 02:30.626
purposes . China , for example , has

02:30.626 --> 02:32.681
set the ambitious goal of becoming a

02:32.681 --> 02:34.570
global leader in A I by 2030 with

02:34.570 --> 02:36.792
significant investments in research and

02:36.792 --> 02:38.626
development and its focus on A I

02:38.626 --> 02:40.626
enabling technologies include areas

02:40.626 --> 02:42.792
like unmanned systems and surveillance

02:42.792 --> 02:44.903
autonomous vehicles , all which could

02:44.903 --> 02:47.014
bolster its military capabilities and

02:47.014 --> 02:49.292
pose a challenge to regional stability .

02:49.292 --> 02:49.220
Similarly , Russia has adopted a

02:49.229 --> 02:51.396
concept for development and use of A I

02:51.396 --> 02:53.340
technologies in its armed forces .

02:53.340 --> 02:55.396
Signaling its intent to leverage A I

02:55.396 --> 02:57.229
for applications from autonomous

02:57.229 --> 02:59.229
warfare systems . Like we're seeing

02:59.229 --> 03:00.896
play out in Ukraine and cyber

03:00.896 --> 03:03.062
operations . Iran has also expressed a

03:03.062 --> 03:05.089
desire about becoming an A I nation

03:05.100 --> 03:07.044
leader with investments in digital

03:07.044 --> 03:09.100
business and integration of A I into

03:09.100 --> 03:11.044
its military operations . And even

03:11.044 --> 03:13.378
North Korea , despite limited resources ,

03:13.378 --> 03:15.433
has shown interest in developing A I

03:15.433 --> 03:17.600
and machine learning capabilities . So

03:17.600 --> 03:19.600
with adversaries and allies alike ,

03:19.600 --> 03:21.711
investing in digital and A I adoption

03:21.711 --> 03:23.822
are focused on scalability in the con

03:23.822 --> 03:25.600
in , in the context here of our

03:25.600 --> 03:27.433
experimentation series is really

03:27.433 --> 03:30.093
focused on making real the promise of

03:30.102 --> 03:32.386
these digital tools in the competitive

03:32.395 --> 03:34.339
environment . And to do that , the

03:34.339 --> 03:36.796
department must proactively keep pace

03:36.805 --> 03:39.027
with the innovation that's happening in

03:39.027 --> 03:41.027
the private sector . CD A O plays a

03:41.027 --> 03:42.861
critical role in shepherding and

03:42.861 --> 03:44.916
scaling these A I enabled uh digital

03:44.916 --> 03:47.027
enabled tools across the department .

03:47.027 --> 03:49.555
And let me kind of lay out um what CD A

03:49.565 --> 03:51.732
O does , what I think and what I think

03:51.732 --> 03:54.149
needs to be done . CD A O is a unique

03:54.160 --> 03:56.279
kind of dod organization for those

03:56.289 --> 03:58.511
who've worked with the department , you

03:58.511 --> 04:00.567
know , it's typical to do policy and

04:00.567 --> 04:02.900
governance , but we also bu buy , build ,

04:02.900 --> 04:05.011
deliver and sustain capabilities . So

04:05.011 --> 04:06.789
we have a real , a big piece of

04:06.789 --> 04:08.733
business to do on making real that

04:08.733 --> 04:10.678
promise of digital capabilities at

04:10.678 --> 04:12.733
scale . And we do this through three

04:12.735 --> 04:14.654
buckets of activities , enabling

04:14.664 --> 04:16.553
adoption through key policies and

04:16.553 --> 04:18.775
partnerships . Like I mentioned , um we

04:18.775 --> 04:20.497
have uh agreements , bilateral

04:20.497 --> 04:22.608
agreements as well as A I partnership

04:22.608 --> 04:24.442
for defense . But we also try to

04:24.442 --> 04:26.664
translate that into real tools like our

04:26.664 --> 04:28.553
responsible A I toolkit to enable

04:28.553 --> 04:30.497
responsible adoption and our trade

04:30.497 --> 04:32.497
winds acquisition ecosystem , which

04:32.497 --> 04:34.497
you'll learn more about today . The

04:34.497 --> 04:36.608
second bucket is scale and we do that

04:36.608 --> 04:38.442
with a focus on things like data

04:38.442 --> 04:40.608
infrastructure and mission analytics .

04:40.608 --> 04:42.831
And that includes dod S data stacks for

04:42.831 --> 04:44.831
everything from business systems to

04:44.831 --> 04:46.942
strategic and operational planning to

04:46.942 --> 04:48.997
tactical orchestration . This covers

04:48.997 --> 04:48.739
the full range of business and

04:48.750 --> 04:50.806
warfighting analytics to enable data

04:50.806 --> 04:52.750
driven decision making . The third

04:52.750 --> 04:55.309
bucket is speed um where we focus on

04:55.320 --> 04:57.431
adoption through targeted investments

04:57.431 --> 04:59.542
and engagements . Our work today with

04:59.542 --> 05:01.709
you all at focus on guide industry day

05:01.709 --> 05:03.542
is part of our broader effort to

05:03.542 --> 05:05.542
accelerate the delivery of advanced

05:05.542 --> 05:07.598
command and control tools to deliver

05:07.598 --> 05:09.764
digital capabilities in months instead

05:09.764 --> 05:11.931
of years . So ultimately , in CD A O ,

05:11.931 --> 05:13.820
we really see our role as helping

05:13.820 --> 05:15.987
translate these digital tools into act

05:15.987 --> 05:18.153
actual capabilities . And this is very

05:18.153 --> 05:20.376
much a team effort with our partners in

05:20.376 --> 05:22.598
the research and engineering group , as

05:22.598 --> 05:24.653
well as in um the Defense Innovation

05:24.653 --> 05:26.876
Unit . We're working to integrate these

05:26.876 --> 05:29.429
technologies into our warfighter to get

05:29.440 --> 05:32.162
them into our warfighters hands . Now A

05:32.173 --> 05:34.173
I , so what needs to be done A I

05:34.183 --> 05:36.592
adoption is fundamentally governed by a

05:36.602 --> 05:38.852
key set of enablers . And in CD A O ,

05:38.863 --> 05:40.653
we've laid out what we call the

05:40.662 --> 05:42.606
hierarchy of needs . Think of this

05:42.606 --> 05:44.942
hierarchy as a pyramid at the top of

05:44.953 --> 05:47.972
the pyramid is responsible A I adoption .

05:47.983 --> 05:50.205
And I want to be clear that there are a

05:50.205 --> 05:52.205
range of different kinds of A I and

05:52.205 --> 05:54.436
digital technologies here that can um

05:54.446 --> 05:56.613
that the department can adopt in a use

05:56.613 --> 05:58.557
case driven approach , identifying

05:58.557 --> 06:00.724
where these digital tools may have the

06:00.724 --> 06:02.557
highest return on investment and

06:02.557 --> 06:04.613
ensuring we have the right assurance

06:04.613 --> 06:06.779
processes in place . The middle of the

06:06.779 --> 06:08.946
period pyramid is insightful analytics

06:08.946 --> 06:11.168
and this is where data driven tools can

06:11.168 --> 06:12.946
provide meaningful and accurate

06:12.946 --> 06:15.002
insights that allow us to understand

06:15.002 --> 06:14.996
specific domains and execute kill

06:15.006 --> 06:17.339
chains effectively the foundation of

06:17.350 --> 06:19.517
the period pyramid . And what makes it

06:19.517 --> 06:21.739
all work is quality data . And while we

06:21.739 --> 06:23.683
can and should spend a lot of time

06:23.683 --> 06:25.517
about the algorithms and digital

06:25.517 --> 06:27.072
technologies that drive new

06:27.072 --> 06:29.128
capabilities . These are all useless

06:29.128 --> 06:30.961
without our quality data and the

06:30.961 --> 06:33.183
quality and scale of the data is . What

06:33.183 --> 06:35.239
what drives a utility of new tools ?

06:35.239 --> 06:37.183
I'll come back to how we meet this

06:37.183 --> 06:37.170
hierarchy of needs . But assuming we

06:37.179 --> 06:39.012
can do that , we have to clearly

06:39.012 --> 06:41.123
identify the kind of tools we want to

06:41.123 --> 06:43.290
adopt . Fundamentally , the department

06:43.290 --> 06:45.512
needs to deliver capabilities and those

06:45.512 --> 06:47.568
capabilities have specific use cases

06:47.568 --> 06:49.750
where we think digital enabled tools

06:49.760 --> 06:51.816
can drive improved effectiveness and

06:51.816 --> 06:53.927
efficiency . To that end , we focused

06:53.927 --> 06:56.038
on a human centered design approach .

06:56.038 --> 06:58.204
Now , for all the natural inclinations

06:58.204 --> 07:00.260
and sci-fi machinations about things

07:00.260 --> 07:03.619
like A I scary A I let's be very clear

07:03.630 --> 07:05.741
that any technology and these digital

07:05.741 --> 07:07.790
tools are dependent on the human

07:07.799 --> 07:09.910
interaction with the digital system .

07:09.910 --> 07:12.079
So successful adoption of a of these

07:12.089 --> 07:14.089
digital tools is contingent on this

07:14.089 --> 07:16.311
human computer interaction . And that's

07:16.311 --> 07:18.533
where our experimentation series are so

07:18.533 --> 07:20.533
important . Think of it like making

07:20.533 --> 07:22.422
dinner , which I'm sure we all do

07:22.422 --> 07:24.720
pretty often you need an oven and a pan

07:24.730 --> 07:26.674
and the right ingredients in those

07:26.674 --> 07:28.897
foundational pieces . But a good cook ,

07:28.897 --> 07:31.008
a gourmet chef is gonna mix and taste

07:31.008 --> 07:33.063
and adjust the recipe to get it just

07:33.063 --> 07:35.119
right . They're gonna experiment and

07:35.119 --> 07:37.230
iterate until they get the food to be

07:37.230 --> 07:39.452
just as delicious as they want it . And

07:39.452 --> 07:39.070
those , while those enablers and tools

07:39.079 --> 07:41.301
are a necessary part of it . What makes

07:41.301 --> 07:43.523
a really good meal is that chef knowing

07:43.523 --> 07:45.523
how to use and combine the tools to

07:45.523 --> 07:48.160
achieve superior results . Today in dod

07:48.170 --> 07:51.000
operational users don't always know the

07:51.010 --> 07:53.720
proverbial recipe and sometimes we make

07:53.730 --> 07:56.008
a meal without anyone tasting it first .

07:56.008 --> 07:58.119
So to speak , that results in digital

07:58.119 --> 08:00.174
solutions and tools that in the best

08:00.174 --> 08:02.397
case , don't quite meet our operational

08:02.397 --> 08:04.452
needs and in the worst case , impede

08:04.452 --> 08:06.508
the war fighter on the mission . And

08:06.508 --> 08:08.674
that's why why the agile approach that

08:08.674 --> 08:10.619
incorporates experimentation it or

08:10.619 --> 08:12.674
development and deployment cycle and

08:12.674 --> 08:14.730
the pairing of operational users and

08:14.730 --> 08:16.897
technology experts is so critical . We

08:16.897 --> 08:19.063
need to meet this hierarchy of needs ,

08:19.063 --> 08:21.230
the data , the analytics , the digital

08:21.230 --> 08:23.397
responsible digital tool adoption . Um

08:23.397 --> 08:25.563
but we also need to bake in see what I

08:25.563 --> 08:27.508
did there . Um The experimentation

08:27.508 --> 08:29.230
cycles to enable our tools are

08:29.230 --> 08:31.654
delivering real useful capability . Let

08:31.665 --> 08:33.665
me turn to how we're doing that and

08:33.665 --> 08:35.776
what we're gonna do here today at our

08:35.776 --> 08:37.998
insight day . So to start , we need the

08:37.998 --> 08:40.109
data stacks and associated mechanisms

08:40.109 --> 08:42.332
to access , develop and test the models

08:42.332 --> 08:44.332
for identified use cases . The good

08:44.332 --> 08:44.294
news here is we're starting from a

08:44.304 --> 08:46.590
strong foundation . So the bottom two

08:46.599 --> 08:48.766
layers of the hierarchy of needs , the

08:48.766 --> 08:51.229
data and analytics . Um in CD A O , we

08:51.239 --> 08:53.295
focused on ensuring we have reliable

08:53.295 --> 08:55.406
access to our data infrastructure and

08:55.406 --> 08:57.572
the analytics . We need to support our

08:57.572 --> 08:59.406
mission to make that an enduring

08:59.406 --> 09:01.517
process last month or I guess . Now ,

09:01.517 --> 09:03.572
almost two months ago , we announced

09:03.572 --> 09:05.683
our construct open dagger that stands

09:05.683 --> 09:07.739
for the open data and applications ,

09:07.739 --> 09:09.461
government owned interoperable

09:09.461 --> 09:11.572
repositories . I know it's a mouthful

09:11.572 --> 09:13.795
open dagger has three parts . The first

09:13.795 --> 09:16.017
is enterprise level infrastructure that

09:16.017 --> 09:18.239
ensures reliable and enduring access to

09:18.239 --> 09:21.239
our government owned data stacks . The

09:21.250 --> 09:23.859
second part is enterprise licenses that

09:23.869 --> 09:26.400
facilitates scaled access to mature

09:26.409 --> 09:29.169
applications . And the third is this

09:29.179 --> 09:31.123
agile requirements and acquisition

09:31.123 --> 09:33.250
process that allows us to accelerate

09:33.260 --> 09:35.482
the procurement of digital capabilities

09:35.482 --> 09:37.704
and prototypes and experiment with them

09:37.704 --> 09:39.927
with our operational users to make sure

09:39.927 --> 09:41.982
we're delivering real capabilities .

09:41.982 --> 09:44.204
This last piece is critically important

09:44.204 --> 09:46.371
because we absolutely need to create a

09:46.371 --> 09:48.427
pathway to connect digital solutions

09:48.427 --> 09:50.538
developed outside the government with

09:50.538 --> 09:50.409
the capability needs that were

09:50.419 --> 09:52.530
identified inside the government that

09:52.530 --> 09:54.141
not only lets us bring those

09:54.141 --> 09:55.975
capabilities in but also sends a

09:55.975 --> 09:58.197
critical demand signal that enables the

09:58.197 --> 10:00.739
flows of privately held capital and to

10:00.750 --> 10:02.750
match to the right uh companies and

10:02.750 --> 10:04.750
lets the economic system do what it

10:04.750 --> 10:06.972
does best scale successful innovation .

10:07.030 --> 10:09.197
So with all that context , let me talk

10:09.197 --> 10:11.419
about what we're doing here today . The

10:11.419 --> 10:13.474
short answer is we think that one of

10:13.474 --> 10:15.530
the flagship areas we can accelerate

10:15.530 --> 10:17.586
with this approach is solutions that

10:17.586 --> 10:17.419
deliver advanced command and control

10:17.429 --> 10:19.485
capabilities or as we call it in the

10:19.485 --> 10:21.539
department CJ AC two . Let me start

10:21.549 --> 10:23.660
with command and control , which is a

10:23.660 --> 10:25.827
long standing war fighting function to

10:25.827 --> 10:27.993
do it effectively . Today , commanders

10:27.993 --> 10:30.105
need to integrate vast amount of data

10:30.105 --> 10:32.160
and information from all domains and

10:32.160 --> 10:34.382
all sources to do that effectively . We

10:34.382 --> 10:36.605
need a usable interface that integrates

10:36.605 --> 10:38.660
the data , data and enable strategic

10:38.660 --> 10:40.549
and operational and even tactical

10:40.549 --> 10:42.605
decisions . Um Everything from force

10:42.605 --> 10:44.716
planning to kill chain execution . To

10:44.716 --> 10:46.938
deliver these tools . We wanna identify

10:46.938 --> 10:48.938
solutions , experiment refine those

10:48.938 --> 10:51.049
tech solutions and ensure they really

10:51.049 --> 10:53.469
meet . Operator operator needs to do

10:53.479 --> 10:55.510
that inside CD A O . And across the

10:55.520 --> 10:57.464
department , we have leveraged the

10:57.464 --> 10:59.353
guide series which has now had 11

10:59.353 --> 11:01.520
iterations of experiments with leaders

11:01.520 --> 11:03.576
from the joint staff , the combatant

11:03.576 --> 11:03.049
commands and all of the service

11:03.059 --> 11:04.948
branches as well as international

11:04.948 --> 11:07.115
allies and partners . The guide series

11:07.115 --> 11:09.337
has proven essential to delivering that

11:09.337 --> 11:11.859
decision advantage to CJ AC two by

11:11.869 --> 11:13.647
taking an experimentation based

11:13.647 --> 11:15.591
approach and putting operators and

11:15.591 --> 11:17.780
technologists side by side to identify

11:17.789 --> 11:20.067
those key gaps and necessary solutions .

11:20.080 --> 11:22.302
And that allows us to enable those type

11:22.302 --> 11:24.136
of advanced C two functions that

11:24.136 --> 11:27.359
combatant commanders really need . That

11:27.369 --> 11:29.299
is we built a process to take an

11:29.309 --> 11:31.659
initial digital solution , test it out ,

11:31.669 --> 11:33.789
get feedback and improve so we can

11:33.799 --> 11:35.743
offer meaningful and executable so

11:35.743 --> 11:37.679
solutions and we accomplished in

11:37.690 --> 11:39.579
December , delivering the minimum

11:39.579 --> 11:41.809
viable capability in months instead of

11:41.820 --> 11:43.789
years , but there are a host of

11:43.799 --> 11:45.855
additional capabilities and features

11:45.855 --> 11:47.577
that could just drive decision

11:47.577 --> 11:49.632
advantage and priority kill chains .

11:49.632 --> 11:51.521
And this year , the guide team is

11:51.521 --> 11:53.521
focused on building out that NBC to

11:53.521 --> 11:55.243
deliver the 1.0 version of the

11:55.243 --> 11:57.355
enterprise mission applications ready

11:57.355 --> 11:59.577
for real world use to support that CD A

11:59.577 --> 12:01.799
O in partnership with our colleagues in

12:01.799 --> 12:03.966
R and E . The research and engineering

12:03.966 --> 12:06.021
team in Diu , the Defense Innovation

12:06.021 --> 12:08.243
Unit are connecting specific warfighter

12:08.243 --> 12:10.410
capabilities means with the technology

12:10.410 --> 12:12.632
experts in industry to help us identify

12:12.632 --> 12:12.530
and where appropriate adopt potential

12:12.539 --> 12:15.419
solutions into our global information

12:15.429 --> 12:17.849
domination dominance experiments . And

12:17.859 --> 12:20.479
that's where we are today kicking off

12:20.489 --> 12:22.545
our industry day . And that's really

12:22.545 --> 12:24.767
the start of this ongoing process . And

12:24.767 --> 12:26.822
that's the key that we want to drive

12:26.822 --> 12:28.656
today , a predictable repeatable

12:28.656 --> 12:30.767
process that matches these technology

12:30.767 --> 12:32.600
solutions with the resources and

12:32.600 --> 12:34.656
acquisition pathways to support it .

12:34.656 --> 12:36.820
We're pleased to be joined by Diu and

12:36.830 --> 12:39.052
Rne in partner with industry to deliver

12:39.052 --> 12:41.219
these critical capabilities and let me

12:41.219 --> 12:43.108
just close today with um with the

12:43.108 --> 12:45.750
following thought , the United States

12:45.760 --> 12:48.669
decisive and enduring advantage lies in

12:48.679 --> 12:50.735
the innovation ethic inherent in the

12:50.735 --> 12:52.735
American economy . The department's

12:52.735 --> 12:54.780
ability to incorporate the vibrant

12:54.789 --> 12:56.733
private sector's new technology is

12:56.733 --> 12:58.956
critical to meeting our no fail mission

12:58.956 --> 13:01.011
to deter and if necessary defeat any

13:01.011 --> 13:03.233
adversary and that's where you all come

13:03.233 --> 13:05.289
in our essential industry partners .

13:05.289 --> 13:07.345
The objective today , the objectives

13:07.345 --> 13:09.456
for today are to introduce you to the

13:09.456 --> 13:11.678
learning , to our learnings . From last

13:11.678 --> 13:13.678
year's guide series , enable you to

13:13.678 --> 13:15.900
support the guide experimentation teams

13:15.900 --> 13:17.956
for the purpose of generating faster

13:17.956 --> 13:19.733
and more comprehensive outlines

13:19.733 --> 13:21.678
outcomes , outline the acquisition

13:21.678 --> 13:23.845
opportunities to join guide and the CJ

13:23.845 --> 13:25.822
C two ecosystem . Increase the

13:25.833 --> 13:27.722
knowledge of the data marketplace

13:27.722 --> 13:30.013
concept and our open dagger process

13:30.072 --> 13:32.853
present JFN 2.0 requirements and the

13:32.862 --> 13:34.862
way ahead for guide as a nomination

13:34.862 --> 13:37.773
venue for JFN capabilities . In

13:37.783 --> 13:39.950
addition to sharing these objectives ,

13:39.950 --> 13:42.116
you , we hope to hear from you on what

13:42.116 --> 13:44.116
would be most helpful in clarifying

13:44.116 --> 13:45.950
priorities , structuring further

13:45.950 --> 13:48.172
sessions and generally creating a clear

13:48.172 --> 13:50.227
and predictable pathway to work with

13:50.227 --> 13:52.394
the department in the critical area of

13:52.394 --> 13:54.283
advanced C two capability . We're

13:54.283 --> 13:56.394
really honored by your attendance and

13:56.394 --> 13:58.561
we hope it's a very productive day for

13:58.561 --> 13:58.546
you all . I know it certainly will be

13:58.556 --> 13:59.926
for us . Thank you guys

14:05.630 --> 14:05.840
and .

