WEBVTT

00:00.310 --> 00:01.890
- Hi my name is Cadet Ken Bamieh.

00:01.890 --> 00:02.723
I'm a student here at

00:02.723 --> 00:04.640
the Air Force Academy's Preparatory School

00:04.640 --> 00:07.500
and my idea for this years
Spark Tank competition

00:07.500 --> 00:10.090
is the expansion of computer
assisted weather products.

00:10.090 --> 00:12.680
Everyday forecasters in
hundreds of Air Force bases

00:12.680 --> 00:14.810
are making weather products
for their customers.

00:14.810 --> 00:15.643
Whether it be for

00:15.643 --> 00:17.790
the command staff, pilots or

00:17.790 --> 00:20.100
sometimes even intelligence agencies.

00:20.100 --> 00:21.960
One of the most common
weather products produced

00:21.960 --> 00:24.010
is the Mission Execution Forecast

00:24.010 --> 00:25.090
otherwise known as the MEF.

00:25.090 --> 00:27.180
The MEF is an
all-encompassing product that

00:27.180 --> 00:28.590
provides information on

00:28.590 --> 00:30.640
icing, turbulence, winds,

00:30.640 --> 00:33.020
visibility, cloud heights, and more.

00:33.020 --> 00:34.490
Pretty much if there is a weather element

00:34.490 --> 00:35.950
that can stop a mission

00:35.950 --> 00:38.590
pilots can use the MEF to
gain situational awareness

00:38.590 --> 00:40.140
on when and where

00:40.140 --> 00:42.370
forecasting severe conditions
are likely to occur.

00:42.370 --> 00:43.340
As you might imagine,

00:43.340 --> 00:45.130
producing a Mission Execution Forecast

00:45.130 --> 00:46.510
can be fairly time consuming.

00:46.510 --> 00:47.520
You need to compile

00:47.520 --> 00:49.700
hundreds of data points from multiple

00:49.700 --> 00:51.590
government websites.

00:51.590 --> 00:53.340
My idea, Lexi

00:53.340 --> 00:57.870
is a computer assisted
Mission Execution Forecast.

00:57.870 --> 01:00.420
Essentially, it will compile
these hundreds of data points

01:00.420 --> 01:02.740
from the same government sources that a

01:02.740 --> 01:04.260
forecaster would

01:04.260 --> 01:06.320
but it would do it in only
a fraction of the time.

01:06.320 --> 01:08.480
While Lexi will compile
the same exact data points

01:08.480 --> 01:11.140
from the same exact government sources,

01:11.140 --> 01:12.950
you'd be expected to maintain the

01:12.950 --> 01:15.310
same accuracy or even
slightly higher than that

01:15.310 --> 01:16.910
over human forecaster.

01:16.910 --> 01:18.630
This is because Lexi

01:18.630 --> 01:20.337
a computer software

01:20.337 --> 01:23.250
isn't prone to the same
human induced errors

01:23.250 --> 01:24.530
that a weather forecaster

01:24.530 --> 01:26.210
can sometimes be presented with.

01:26.210 --> 01:28.260
As the MEF has produced thousands of

01:28.260 --> 01:30.870
times every single month,

01:30.870 --> 01:35.160
Lexi would be able to save
approximately 48,000 man hours

01:35.160 --> 01:36.560
every single year.

01:36.560 --> 01:40.050
48,000 man hours given back
to our weather forecasters

01:40.050 --> 01:41.620
across the entire Air Force.

01:41.620 --> 01:44.030
When it comes to the feasibility of Lexi,

01:44.030 --> 01:47.150
I know it's possible because
it's already been done

01:47.150 --> 01:48.720
at my old weather unit.

01:48.720 --> 01:50.500
During my time as a weather forecaster

01:50.500 --> 01:53.858
I created and coded Lexi for
the 7th Weather Squadron.

01:53.858 --> 01:54.870
At this point

01:54.870 --> 01:56.510
Lexi has been run

01:56.510 --> 01:59.130
flawlessly over a thousand times

01:59.130 --> 02:01.570
and is currently the preferred
method for preparing MEFs.

02:01.570 --> 02:02.760
If my idea is selected

02:02.760 --> 02:04.620
and Lexi is able to be used across

02:04.620 --> 02:07.070
the entire Air Force weather community,

02:07.070 --> 02:08.400
we'd be able to save

02:08.400 --> 02:12.660
a total of 48,000 man
hours every single year.

02:12.660 --> 02:14.780
Thank you for your time and consideration

02:14.780 --> 02:15.613
in this idea.