WEBVTT

00:01.602 --> 00:05.157
- And thank you for joining
me through the corner of the--

00:05.157 --> 00:08.460
for a discussion about understanding

00:08.460 --> 00:12.370
the operational environment
and that from our perspective

00:12.370 --> 00:16.203
that requires employing
data-centric type approaches.

00:18.460 --> 00:22.250
I'll save the take-away
slide for the last one

00:22.250 --> 00:24.882
but there will be some
key bullets on what--

00:24.882 --> 00:26.670
that I understand, go to slide 2.

00:26.670 --> 00:30.070
I'm gonna start with a brief
description or an understanding

00:30.070 --> 00:33.920
of what it is that we
do in the TRADOC G-2.

00:33.920 --> 00:38.400
So the Training Doctrine
Command for intelligence G-2

00:38.400 --> 00:42.903
is responsible for understanding,
describing, visualizing

00:42.903 --> 00:46.810
delivering and assessing
the operational environment

00:46.810 --> 00:50.010
for leader development,
training and education--

00:50.010 --> 00:54.073
capabilities and concepts
development, experimentation.

00:55.770 --> 00:59.380
We do that with three lines
of effort, our first one being

00:59.380 --> 01:01.980
continuity of the narrative,
I'm gonna tie this back in

01:01.980 --> 01:03.560
because this is kind of a soft transition

01:03.560 --> 01:06.290
from the cross-functional team briefings

01:06.290 --> 01:09.940
that we had this morning but
this operational environment

01:09.940 --> 01:12.750
is defined by the TRADOC
G-2 in partnership

01:12.750 --> 01:17.750
with Futures Command,
Futures and Concepts Center,

01:18.690 --> 01:22.750
their OE futures cell
provides an underpinning

01:22.750 --> 01:26.560
for every one of the
cross-functional teams.

01:26.560 --> 01:29.110
All the capability developments
that we're talking about

01:29.110 --> 01:32.690
they're all underpinned by
the operational environment

01:32.690 --> 01:36.980
the pamphlets that are
defined by this team.

01:36.980 --> 01:39.800
So with that, we do
that, not in isolation,

01:39.800 --> 01:42.800
we do it vertically with our
intelligence community partners

01:43.919 --> 01:47.130
in that it's vetted widely
and horizontally across

01:47.130 --> 01:49.740
Training and Doctrine
Command, plus the Army,

01:49.740 --> 01:53.563
and our sister services with
our joint and allied partners.

01:55.050 --> 01:58.670
As we publish these documents
out, that lay down this

01:58.670 --> 02:01.390
determination of the future
operational environment

02:02.530 --> 02:05.370
and the current two future
operational environment

02:05.370 --> 02:09.950
it must be able to
withstand rigorous scrutiny

02:09.950 --> 02:11.600
from our partners, so we need

02:11.600 --> 02:13.350
a highly collaborative environment.

02:14.640 --> 02:16.400
Kinda leads into the second line of effort

02:16.400 --> 02:19.380
that we have, which is a
critical thinking exercise

02:19.380 --> 02:23.720
we have a team of folks that
take team-type techniques.

02:23.720 --> 02:27.380
Groupthink mitigation so
we're not only listening

02:27.380 --> 02:30.360
to ourselves but we're
also critiquing ourselves

02:30.360 --> 02:33.460
and think critically and apply
critical thinking techniques

02:33.460 --> 02:37.460
to the assumptions and the
outcomes of the expressions

02:37.460 --> 02:39.820
within the operational
environment for the future.

02:39.820 --> 02:43.550
We both train that and we
action that with ourselves.

02:43.550 --> 02:46.310
Again through Army University outreach

02:46.310 --> 02:51.310
and a robust e-intern program,
we bring in thought leaders

02:51.750 --> 02:56.500
from across industry, academic
and the military space

02:56.500 --> 02:59.100
to help us with that
critical thinking enterprise

02:59.100 --> 03:01.940
so we get the continuity
that we're looking for

03:01.940 --> 03:03.213
in the OE narrative.

03:04.390 --> 03:08.680
So that's generally an innate
capability to our primary line

03:08.680 --> 03:10.713
which is that delivery of the OE.

03:11.700 --> 03:14.990
The third line of effort
is, it's digitizing tools

03:14.990 --> 03:17.700
and content, that's really
where the data-centric approach

03:17.700 --> 03:21.410
piece comes into play, another
enabling line of effort

03:21.410 --> 03:23.570
to both the critical thinking enterprise

03:23.570 --> 03:26.870
and more importantly the
continuity of the OE narrative.

03:26.870 --> 03:31.690
It takes data for us to
understand from a broad area

03:31.690 --> 03:34.340
of collection, what variables need

03:34.340 --> 03:39.050
to be accounted for and addressed
and in what we publish out

03:39.050 --> 03:40.990
as the OE narrative, the narrative

03:42.964 --> 03:45.914
about the operational environment,
both current and future.

03:47.650 --> 03:51.240
We do that, with a number
of different tools,

03:51.240 --> 03:55.790
digitizing content and now
we're getting into the space

03:55.790 --> 03:58.830
where we're applying some machine learning

03:58.830 --> 04:03.458
to unstructured content to
be able to help our analysts

04:03.458 --> 04:08.003
do the analysis and synthesis
of the data and content

04:08.003 --> 04:11.283
to be able to provide the
results we're looking for.

04:12.488 --> 04:17.060
What I'm gonna do for you
today is demonstrate for you

04:17.060 --> 04:19.780
with the help of Dwayne in
the back, I appreciate that.

04:19.780 --> 04:22.100
One of the tools that we
have in place that allows us

04:22.100 --> 04:25.960
to do this, specifically
for the leader development

04:25.960 --> 04:29.950
training and education
and home station training

04:29.950 --> 04:32.540
and national training center type venues.

04:32.540 --> 04:34.850
One of the core products
you see at the top

04:34.850 --> 04:37.250
of our continuity narrative is DATE

04:37.250 --> 04:39.453
or the Decisive Action
Training Environment.

04:40.520 --> 04:43.510
TRADOC G-2 is the authoritative source

04:43.510 --> 04:45.740
for the Decisive Action
Training Environment.

04:45.740 --> 04:50.100
It sets the conditions now
and for regionalized areas

04:50.100 --> 04:53.980
of the world, that underpin
all of our scenarios

04:53.980 --> 04:56.290
that we develop for leader
development training

04:56.290 --> 04:59.250
and education, together
with concept development.

04:59.250 --> 05:02.030
So I'm gonna show you a
platform demonstration

05:02.030 --> 05:04.230
and show you kind of how
we've taken this data-centric

05:04.230 --> 05:08.420
approach and actually
implemented it for our analysts.

05:08.420 --> 05:11.393
So Dwayne, if you'll go to
the demonstration piece.

05:15.750 --> 05:19.160
As he starts to bring this
up, there is, as we understand

05:19.160 --> 05:22.980
in the information technology
world, there's no magic here.

05:22.980 --> 05:26.670
We take a number of proven
off the shelf capabilities

05:26.670 --> 05:29.870
mostly in the free and open
source realm, integrate them

05:29.870 --> 05:33.950
in kind of new ways to deliver
the operational environment

05:33.950 --> 05:34.943
in a different way.

05:36.840 --> 05:41.470
The whole intent here is
to deliver the right data

05:41.470 --> 05:43.710
to the right person at the right time

05:43.710 --> 05:46.680
and in the right format and
for some of those similar terms

05:46.680 --> 05:50.430
with other people talking up
here, is the same mantra for us

05:50.430 --> 05:52.575
So what you see here, is a web interface,

05:52.575 --> 05:54.710
and this is a publicly available site,

05:54.710 --> 05:57.220
you can go to on your phones it works well

05:57.220 --> 06:01.150
on a mobile device. Odin.TRADOC.army.mil

06:01.150 --> 06:02.720
I also have pamphlets and flyers

06:02.720 --> 06:05.463
in the back that you're
welcome to pick up at the end.

06:07.130 --> 06:08.990
Again, the intent of this platform

06:08.990 --> 06:11.440
is to share this
information then release it.

06:11.440 --> 06:14.750
It's been approved for
public release to be able

06:14.750 --> 06:16.810
to reach the widest audience
with the information

06:16.810 --> 06:19.023
to include our international partners.

06:21.760 --> 06:25.053
So what you see on the
site is the user interface,

06:26.300 --> 06:31.300
what's behind the user interface
is highly structured data

06:31.659 --> 06:36.640
provided through a highly
tuned user experience for users

06:36.640 --> 06:41.500
to be able to consume this,
that does a second job for us

06:41.500 --> 06:44.880
in that it provides the
data on the backend through

06:44.880 --> 06:47.660
application program interfaces
so that data can have

06:47.660 --> 06:50.773
a life-cycle beyond
delivery in this platform.

06:52.290 --> 06:54.590
We can get to the instructions
for the technical interface

06:54.590 --> 06:57.080
for those application program interfaces

06:57.080 --> 06:59.180
and it can move into any other machine

06:59.180 --> 07:00.960
or system that needs to consume it.

07:00.960 --> 07:02.910
So think, I'll give you
some examples of this

07:02.910 --> 07:05.760
but our models and simulation platforms.

07:05.760 --> 07:07.930
The data can move from this platform

07:07.930 --> 07:10.420
directly in to help build those scenarios

07:10.420 --> 07:13.116
for models and simulations
as well as formats

07:13.116 --> 07:17.090
that can be consumed through
our mission command systems.

07:17.090 --> 07:19.820
And I'll explain a little bit
later on how we're doing that

07:19.820 --> 07:22.310
in a real way with the
Army Models and Sims Office

07:22.310 --> 07:24.663
on something called the
Unified Data Initiative.

07:25.670 --> 07:28.840
So we'll start here, it's
the welcome to Odin platform.

07:28.840 --> 07:30.520
You'll be able to tell
what changes have been made

07:30.520 --> 07:33.410
to the platform with the modal
boxes on the right hand side.

07:33.410 --> 07:35.760
Those will be announcements
and whatever changes come

07:35.760 --> 07:38.540
gives you a description of
what the platform is used for.

07:38.540 --> 07:41.330
We'll click on the
Worldwide Equipment Guide.

07:41.330 --> 07:44.270
A lot of this platform takes the place

07:44.270 --> 07:48.160
of about 17 different volumes,
three to 400 page volumes

07:48.160 --> 07:51.020
of written product, we
no longer produce those

07:51.020 --> 07:54.070
in a written book format,
the only place you can find

07:54.070 --> 07:58.160
this authoritative data is
now in this web interface.

07:58.160 --> 08:00.230
So we produce something
in the TRADOC G-2 called

08:00.230 --> 08:01.960
The Worldwide Equipment Guide.

08:01.960 --> 08:05.740
These are selected equipment
from around the world

08:05.740 --> 08:10.160
that has specific military
application to the US

08:10.160 --> 08:14.580
in threat fight, again the
content that you see in this site

08:14.580 --> 08:17.280
is approved for public release,
but we've dumbed it down

08:17.280 --> 08:19.220
to the data-element level.

08:19.220 --> 08:21.850
So if you'll go ahead
and search in the block,

08:21.850 --> 08:23.990
it's fully searchable
from across the site,

08:23.990 --> 08:25.603
and search for T-64.

08:29.680 --> 08:32.030
So at the top level site,
you're gonna get both articles

08:32.030 --> 08:36.490
about T-64 and elements in
the Worldwide Equipment Guide.

08:36.490 --> 08:39.551
So let's select on the far left panel,

08:39.551 --> 08:42.243
the T-64 main battle tank.

08:44.030 --> 08:46.260
You'll see the data cards
come up, both the imagery

08:46.260 --> 08:47.680
and the description of the item,

08:47.680 --> 08:51.200
plus tabs across every field that you see,

08:51.200 --> 08:53.590
is the set of highly structured data.

08:53.590 --> 08:56.870
So it can be pulled out
in terms of attributes

08:56.870 --> 09:00.600
for those systems for
use in helpful arenas.

09:00.600 --> 09:03.530
You can click through the
tabs, I appreciate that.

09:03.530 --> 09:06.370
And it's standardized data sets across

09:06.370 --> 09:08.410
the WorldWide Equipment Guide piece.

09:08.410 --> 09:11.160
Again, this replaces about
three volumes of books

09:11.160 --> 09:15.263
that were updated on an annual basis.

09:16.260 --> 09:19.670
This is now a dynamic site,
it is updated on a daily basis

09:19.670 --> 09:23.256
or depending upon
feedback from governments

09:23.256 --> 09:26.723
that the field gives us, on
what needs to be represented.

09:28.250 --> 09:29.930
So we can back out and close out

09:29.930 --> 09:31.710
of the Worldwide Equipment Guide.

09:31.710 --> 09:33.790
You'll see another interaction,
this is interactive across

09:33.790 --> 09:36.480
the platform, the next
top level tab will go

09:36.480 --> 09:39.527
to the DATE knowledge base, left one.

09:39.527 --> 09:44.103
DATE knowledge base, I'm
sorry, DATE knowledge base?

09:47.170 --> 09:49.720
So here, we'll go through
the navigation on the top

09:50.717 --> 09:54.390
and go to Caucasus for me, so,

09:54.390 --> 09:59.370
at the top, you saw four
notional regions of the world.

09:59.370 --> 10:02.090
The Caucasus regions,
Pacific, Africa, and Europe.

10:02.090 --> 10:07.090
We just recently published the
Pacific, Africa, and Europe

10:07.752 --> 10:11.500
Decisive Action Training
Environments and again they were

10:11.500 --> 10:13.970
not produced in a Word
document and then PDF

10:13.970 --> 10:16.723
to put on a shelf, they were
authored in this platform.

10:17.750 --> 10:21.971
For the analysts, and
again what you don't see is

10:21.971 --> 10:26.971
this moves the creation of
the content in data form

10:27.050 --> 10:30.080
closer to the analyst, so
now they have a set of tools

10:30.080 --> 10:33.546
enabled by this platform
to author in data form.

10:33.546 --> 10:36.410
They're no longer having
to use Word type things.

10:36.410 --> 10:37.950
They go and do something called a

10:37.950 --> 10:41.100
What You See Is What You
Get-editor and put it into

10:41.100 --> 10:46.100
a wiki-type style database
for both representation

10:46.270 --> 10:49.622
visually here and also extractable through

10:49.622 --> 10:52.330
that application program
interface as well.

10:52.330 --> 10:54.350
So our analysts determine
what the best factors

10:54.350 --> 10:56.530
are to represent or
what the key factors are

10:56.530 --> 10:59.500
to represent the operational
environment for this area

11:00.900 --> 11:04.000
and then they come in here and edit it up.

11:07.090 --> 11:08.313
Let's go to Donovia.

11:10.330 --> 11:12.390
And I'll show you some
of the other features

11:12.390 --> 11:16.740
of the data sets that
are in here, the next...

11:18.932 --> 11:21.480
Atropia is fine, you can stay right there.

11:21.480 --> 11:25.230
So on the left-hand modal,
you see not only the index

11:25.230 --> 11:27.040
it's cutting off the
screen just a little bit

11:27.040 --> 11:29.730
of what's on the page and it goes through

11:29.730 --> 11:33.410
the PMESII-PT variables for
that operational environment.

11:33.410 --> 11:37.444
If you click the eye
icon, right next to it

11:37.444 --> 11:40.930
this gives you a modal for
the geospatial references

11:40.930 --> 11:42.750
for the region we're talking about

11:42.750 --> 11:45.463
plus the demographic
information as you scroll down

11:45.463 --> 11:47.600
in a side-panel modal...

11:50.370 --> 11:53.870
And if you click the next
kind of spider icon next to it

11:53.870 --> 11:56.000
we'll get into more detail on this as well

11:56.000 --> 11:58.130
but this gives you the force structure,

11:58.130 --> 11:59.890
the enemy force structure
that we've developed

11:59.890 --> 12:02.220
as an opposing force or a neutral force

12:02.220 --> 12:05.080
that's gonna play in that
operational environment.

12:05.080 --> 12:08.670
This can be tailored
off the platform to fit

12:08.670 --> 12:11.000
whatever scenario you're driving

12:11.000 --> 12:12.810
in leader development
training and education,

12:12.810 --> 12:15.590
again, capabilities and
concept development.

12:15.590 --> 12:17.550
So it gives it to you all in one space,

12:17.550 --> 12:19.633
cross-linked within the platform.

12:21.730 --> 12:24.730
So let's click on that force
structure tab on the top right.

12:27.670 --> 12:29.670
The other section and
this section has developed

12:29.670 --> 12:31.910
a lot of power for us in that,

12:31.910 --> 12:34.650
we no longer have spreadsheets of data

12:34.650 --> 12:36.490
about the force structure and designing it

12:36.490 --> 12:39.860
for a specific scenario
that we want to support.

12:39.860 --> 12:43.850
Users can now come to the
platform and select their regions.

12:43.850 --> 12:48.053
So let's go Donovia, Caucasus/Donovia.

12:52.520 --> 12:53.870
Go ahead and click on that.

12:56.407 --> 12:57.500
Is it working today?

12:57.500 --> 13:01.270
And it'll pull up the highest
level force structure design

13:01.270 --> 13:05.980
for what we have architected
for the threat representations

13:05.980 --> 13:08.113
or neutral representations for this.

13:09.646 --> 13:13.360
Takes just a minute to load,
but a couple of highlights

13:13.360 --> 13:15.410
on this again, takes it
out of spreadsheet form,

13:15.410 --> 13:18.380
puts it in data form and it can move.

13:18.380 --> 13:22.770
So if we click on the center
of the icon on ground forces

13:25.840 --> 13:28.410
you'll see another modal on
the right hand side come up.

13:28.410 --> 13:31.540
That's an MTO type listing
of all the equipment

13:31.540 --> 13:34.370
within the ground forces of
the National Command Authority

13:34.370 --> 13:37.093
for Donovia, and this works at any echelon

13:37.093 --> 13:39.460
and it can tier out as far as down

13:39.460 --> 13:44.057
to the individual platform
or life form with equipment

13:44.057 --> 13:46.203
within that force structure.

13:47.220 --> 13:52.220
So as that gets ready to
load, you'll see it pop up.

13:52.480 --> 13:55.470
It'll have the total force and
all of the equipment numbers

13:55.470 --> 13:58.900
just like you would normally
see in a force structure

13:58.900 --> 14:01.563
or an MTO type layout for an organization.

14:03.310 --> 14:05.530
If you'll just hover for me over

14:05.530 --> 14:10.530
this download button right
here, we have that capability

14:11.270 --> 14:15.040
within the platform and you
can go ahead and click on that

14:15.040 --> 14:18.286
to export at any echelon
of this force structure

14:18.286 --> 14:23.140
a CSV file of what you've
just selected in two formats.

14:23.140 --> 14:26.120
One is a simulation-ready
format, that goes into something

14:26.120 --> 14:29.490
called the Joint Training
Data Service format.

14:29.490 --> 14:32.055
That supports JCATS simulations

14:32.055 --> 14:34.620
and some other simulation
models and we've also created

14:34.620 --> 14:39.620
an agnostic data format called
Dragon, that's our term.

14:39.884 --> 14:43.840
That we're using to export
into other databases

14:44.800 --> 14:48.580
for holding, for sharing,
so not only can you access

14:48.580 --> 14:51.290
this part from an
application program interface

14:51.290 --> 14:53.270
but as you're navigating
and selecting through

14:53.270 --> 14:55.710
the force structure you're
looking for, you can select

14:55.710 --> 14:58.280
the icon to export just
that portion and get it

14:58.280 --> 15:02.240
in a comma separated values spreadsheet,

15:02.240 --> 15:06.061
that you can then import into your system.

15:06.061 --> 15:07.990
We're working a project right now

15:07.990 --> 15:11.010
with the Army Models and
Simulation Office that allows

15:11.010 --> 15:13.650
for this machine to
machine exchange of data

15:13.650 --> 15:16.463
into what's called the
Army Organizational Server.

15:17.350 --> 15:19.410
Traditionally, that has
served up all of the

15:19.410 --> 15:21.940
blue force structures for the Army,

15:21.940 --> 15:23.930
but there was no representation

15:23.930 --> 15:26.990
of opposing force data in there.

15:26.990 --> 15:31.150
There will be now, we've run a
couple of pilots with success

15:31.150 --> 15:33.480
and now we're doing the
machine to machine interface

15:33.480 --> 15:37.760
so as our authors, our
analysts who have the authority

15:37.760 --> 15:41.260
over this data to make
changes to the platform

15:41.260 --> 15:44.560
it will feed up into the
central repository that's used

15:44.560 --> 15:47.500
across the army for
modeling and simulation

15:47.500 --> 15:49.390
and for mission command systems,

15:49.390 --> 15:51.713
those representations
of the opposing force.

15:55.580 --> 15:57.633
Good, we can go back to the slides?

16:01.600 --> 16:04.290
So the data-centric
approach, to kind of walk you

16:04.290 --> 16:08.020
through this is, no longer
publishing in a book format.

16:08.020 --> 16:09.660
We're putting tools in
the hands of our analysts

16:09.660 --> 16:13.690
to publish in data, and
we're allowing that data

16:13.690 --> 16:16.000
to have a life-cycle, in
that once it's published

16:16.000 --> 16:19.150
in the platform it's
human-consumable through

16:19.150 --> 16:22.080
a web interface, additionally,
it can be consumed

16:22.080 --> 16:24.220
machine to machine and live on.

16:24.220 --> 16:26.870
We don't have perfect
knowledge on everything

16:26.870 --> 16:29.790
our data can be used for and that's okay.

16:29.790 --> 16:31.530
We just want to make sure that it's open

16:31.530 --> 16:34.130
and it's shareable for
people to leverage it

16:34.130 --> 16:36.003
in whatever use-case they may have.

16:37.300 --> 16:38.350
Go to the next slide?

16:40.756 --> 16:41.589
And the next?

16:42.800 --> 16:46.790
So the take-aways, we're
taking on this approach

16:46.790 --> 16:49.040
and we're advocating it across
the training doctrine command

16:49.040 --> 16:51.920
and the other commands, but
really consider your data

16:51.920 --> 16:55.120
as an asset, harvest it, curate it.

16:55.120 --> 16:58.450
From the demonstration I
showed you, that was putting

16:58.450 --> 17:00.860
the data tools in the
hands of the analysts.

17:00.860 --> 17:03.350
They are now the ones
who are curating the data

17:03.350 --> 17:07.153
for re-use and recognizing it as an asset.

17:07.153 --> 17:09.854
Focus on the data, not the applications.

17:09.854 --> 17:13.730
The goal of this project,
that I showed you on Odin

17:13.730 --> 17:17.640
was not to deliver a platform or a tool,

17:17.640 --> 17:21.230
it was to deliver data
and to enable the data

17:21.230 --> 17:24.000
to have a life-cycle,
that's focusing on the data

17:24.000 --> 17:26.040
because now we can connect a number

17:26.040 --> 17:29.050
of different applications
and uses up to that data

17:29.050 --> 17:30.453
with the open interfaces.

17:31.810 --> 17:34.190
Remove stovepiped data systems,

17:34.190 --> 17:36.460
move to a data-centric architecture.

17:36.460 --> 17:41.460
We are still delivering systems
out there that can only work

17:42.450 --> 17:45.290
with their specific database sets

17:45.290 --> 17:48.260
and the data is not shareable
out to other platforms

17:48.260 --> 17:50.320
that can consume and use that data.

17:50.320 --> 17:53.520
We have to change that trend and go

17:53.520 --> 17:56.860
to an open data type of
architecture and standards,

17:56.860 --> 17:58.700
and there's ways to do that.

17:58.700 --> 18:02.035
Utilize data science teams
to get at user requirements.

18:02.035 --> 18:05.740
We're taking some small
data science teams within

18:05.740 --> 18:08.470
the TRADOC G-2 interfacing them directly

18:08.470 --> 18:10.940
with functional
representatives, in this case

18:10.940 --> 18:14.420
for the creation of the OE
data integration platform

18:14.420 --> 18:17.390
that I showed you, the user's
voice was the biggest one

18:17.390 --> 18:20.460
at the table, those analysts
and the community that was

18:20.460 --> 18:23.602
gonna consume, in the various
types to help us drive

18:23.602 --> 18:27.080
to the solution for that
data-driven platform.

18:27.080 --> 18:30.279
The same type approach
we're trying to incorporate

18:30.279 --> 18:32.730
any of the other products
that we're responsible

18:32.730 --> 18:35.990
for delivering out, already talked to you

18:35.990 --> 18:37.810
about our data-centric vision

18:37.810 --> 18:40.820
and the overall intent of
what we're trying to do

18:40.820 --> 18:44.030
and this is transferable,
completely to a number

18:44.030 --> 18:46.340
of different projects
and efforts out there,

18:46.340 --> 18:48.240
and we're integrating again as I said,

18:48.240 --> 18:50.290
across the models and sims community

18:50.290 --> 18:53.383
and in the mission command
systems for data re-use.

18:55.350 --> 18:58.128
Any questions for me, and I
highly encourage questions

18:58.128 --> 19:00.083
from any folks.

19:04.630 --> 19:05.923
Bring him a microphone.

19:16.021 --> 19:20.674
- Does it just have the
databank, or does it have

19:20.674 --> 19:23.174
the capability to analyze data

19:24.482 --> 19:28.315
to read something to
reach a position or that?

19:29.480 --> 19:31.270
- Yeah so the question
if you didn't hear it is

19:31.270 --> 19:34.400
is it just a set of data
structures or are there

19:34.400 --> 19:37.130
analytic tools that are
also part of the platform?

19:37.130 --> 19:40.670
Today there are not any
integrated analytic tools

19:40.670 --> 19:43.140
to the platform, but we
have other analytic tools

19:43.140 --> 19:47.480
that we use to come up with
the results and the data

19:47.480 --> 19:50.190
that get published in here
that are worked in workflow

19:50.190 --> 19:52.980
prior to the analyst
publishing, plus you can see

19:52.980 --> 19:56.860
the opportunity to work this
downstream and we've exported

19:56.860 --> 19:59.460
a lot of the data that's in
here into some other platforms

19:59.460 --> 20:02.520
that we're using to get
at some big data solutions

20:02.520 --> 20:04.770
to then apply some other
analytics downstream.

20:04.770 --> 20:07.609
So there's not any native
to the Odin platform

20:07.609 --> 20:11.343
but the data is highly reusable
within other analytics.

20:19.772 --> 20:21.013
- I apologize, I came a little late,

20:21.013 --> 20:22.264
so you might've already answered this.

20:22.264 --> 20:25.110
So you know, in an ever-changing
world, everything changes.

20:25.110 --> 20:28.160
So how often is this data updated?

20:28.160 --> 20:32.270
- Yeah it's a really good
question so, we have heard talk

20:32.270 --> 20:34.480
about things like living doctrine,

20:34.480 --> 20:37.570
and things that can be
updated on a routine basis.

20:37.570 --> 20:39.790
This Decisive Action Training Environment

20:39.790 --> 20:42.100
lays the foundation for
which all these scenarios

20:42.100 --> 20:45.790
are built upon, so in and of
itself, it's not the scenario,

20:45.790 --> 20:48.080
but it's where they
draw the variables from,

20:48.080 --> 20:50.780
to be able to do that
so we want to make sure

20:50.780 --> 20:54.410
that the most current information
is available at the time.

20:54.410 --> 20:57.616
So how often is it updated,
really on a daily basis

20:57.616 --> 21:02.434
or as there's a desire or a
change requirement out there.

21:02.434 --> 21:06.529
So as we identify other
or changing variables

21:06.529 --> 21:10.060
that are going to impact a
specific operational environment,

21:10.060 --> 21:13.550
our analysts will dig in,
understand that fully.

21:13.550 --> 21:16.057
That's the assess part of
what we're trying to do

21:16.057 --> 21:18.500
and understand part,
then we go to deliver.

21:18.500 --> 21:20.270
They'll deliver it through this platform.

21:20.270 --> 21:23.810
So it's updated continuously,
it's a dynamic site.

21:23.810 --> 21:26.363
There's no versioning, if you will.

21:29.490 --> 21:32.210
Other questions, I think I'm
getting that's time for today.

21:32.210 --> 21:34.803
Thank you very much for your
attention, I appreciate it.

21:35.640 --> 21:37.890
(applause)