WEBVTT

00:00.000 --> 00:03.080
- At the 36 CRS, our
mission primarily consists

00:03.080 --> 00:04.690
of conducting airfield evaluations

00:04.690 --> 00:07.751
at both established and austere locations.

00:07.751 --> 00:09.520
One aspect of the evaluation that's

00:09.520 --> 00:10.660
especially time consuming,

00:10.660 --> 00:13.670
and that's called the PCI,
Pavement Condition Index.

00:13.670 --> 00:15.500
It's a process that follows

00:15.500 --> 00:17.450
through a bunch of different calculations

00:17.450 --> 00:19.380
that can take anywhere
from one to four hours.

00:19.380 --> 00:22.221
In order to determine
airfield distress and damage

00:22.221 --> 00:23.780
and to continue to see
an environment where

00:23.780 --> 00:27.490
the airfield assessment team
is required to report back

00:27.490 --> 00:30.710
airfield suitability information
in less than four hours

00:30.710 --> 00:32.090
presents a serious problem.

00:32.090 --> 00:33.270
In order to combat these issues

00:33.270 --> 00:34.940
and meet our AFI-driven requirement,

00:34.940 --> 00:36.230
we have decided to go and move away

00:36.230 --> 00:38.140
from the manual calculations.

00:38.140 --> 00:39.820
What I've done is automated the process

00:39.820 --> 00:42.830
through the use of an
Excel-based prototype.

00:42.830 --> 00:44.670
And through that automation,
the process that once took

00:44.670 --> 00:48.110
one to fours hours, now
provides instantaneous results.

00:48.110 --> 00:49.970
Here's an example of the Excel calculator

00:49.970 --> 00:50.803
that I've developed.

00:50.803 --> 00:54.830
What you do is come in and
choose between rigid or flexible,

00:54.830 --> 00:56.260
and that's either concrete or asphalt.

00:56.260 --> 00:58.710
From there, these are all
of the different distresses.

00:58.710 --> 01:00.140
Basically what you can
do is rather than doing

01:00.140 --> 01:02.100
a paper base, choose
between low, medium, high

01:02.100 --> 01:05.520
for the damage severity, and
then put in the total damage.

01:05.520 --> 01:07.810
So in this case, I could say that I have

01:07.810 --> 01:11.240
medium longitudinal
transverse diagonal cracking,

01:11.240 --> 01:15.040
and I could go ahead
and say that it's a 15.

01:15.040 --> 01:17.003
It'll run through all its calculations,

01:17.970 --> 01:21.470
and here is an example
of one of the many many

01:21.470 --> 01:23.630
calculations, and here's another one

01:23.630 --> 01:27.640
that goes way past the bar
on the right hand side.

01:27.640 --> 01:29.570
Now what this allows the
user to do is come in

01:29.570 --> 01:32.430
and basically click on final PCI,

01:32.430 --> 01:34.250
skipping over every other chart

01:34.250 --> 01:35.530
that they would normally have to do.

01:35.530 --> 01:37.300
And voila.

01:37.300 --> 01:39.650
Now you have your final
result easily accessible,

01:39.650 --> 01:42.360
and you have a PCI of 47.

01:42.360 --> 01:44.920
My proposed solution is expanding on what

01:44.920 --> 01:47.570
the Air Force Research
Lab has already developed,

01:47.570 --> 01:49.610
and that's software called ATAK,

01:49.610 --> 01:51.960
Android Tactical Assault Kit.

01:51.960 --> 01:56.490
It's already in use by surveyors
and combat controllers.

01:56.490 --> 01:59.500
It provides a easy to use user interface,

01:59.500 --> 02:00.730
but more importantly it allows

02:00.730 --> 02:03.810
for third party plugins to be used.

02:03.810 --> 02:05.930
Using my Excel prototype
as the foundation,

02:05.930 --> 02:08.920
the plugin would dramatically
improve overall efficiency

02:08.920 --> 02:10.650
in collecting airfield damage data,

02:10.650 --> 02:13.670
which is directly reported
in both airfield assessments

02:13.670 --> 02:16.140
and surveys, and would
standardize the process

02:16.140 --> 02:19.130
in collecting airfield
data, as it greatly improves

02:19.130 --> 02:22.543
overall accuracy, and eliminates
nearly all human error.