1
00:00:01,550 --> 00:00:02,670
- Even in the best scenario,

2
00:00:02,670 --> 00:00:04,290
such as setting up for a field exercise,

3
00:00:04,290 --> 00:00:06,510
there's always a lag between
the start of the setup

4
00:00:06,510 --> 00:00:09,010
and the establishment
of a secure data link.

5
00:00:09,010 --> 00:00:11,610
Our goal was to develop
capabilities to fill that gap.

6
00:00:11,610 --> 00:00:12,950
This was expanded upon

7
00:00:12,950 --> 00:00:15,452
and came down as a tasker to

8
00:00:15,452 --> 00:00:17,700
create essentially a program

9
00:00:18,920 --> 00:00:20,560
that would transmit weather data

10
00:00:20,560 --> 00:00:23,520
over the radio communication links.

11
00:00:23,520 --> 00:00:25,630
The eight member team
consisted of one meteorologist

12
00:00:25,630 --> 00:00:27,010
and five software developers

13
00:00:27,010 --> 00:00:28,420
from 16th Weather Squadron

14
00:00:28,420 --> 00:00:31,350
and 2nd Systems Operations Squadron.

15
00:00:31,350 --> 00:00:32,910
And two tactical radio technicians

16
00:00:32,910 --> 00:00:35,400
from 2nd Combat Weather Systems Squadron.

17
00:00:35,400 --> 00:00:36,520
A quarter of the team brought

18
00:00:36,520 --> 00:00:39,890
their previous experience
from working in Kessel Run.

19
00:00:39,890 --> 00:00:42,120
We brought this project
from idea to existence

20
00:00:42,120 --> 00:00:44,653
in approximately seven
weeks at a minimal cost.

21
00:00:45,490 --> 00:00:48,360
We used completely off-the-shelf materials

22
00:00:48,360 --> 00:00:50,663
including a very prolific military radio.

23
00:00:52,000 --> 00:00:54,860
And incurred no additional
costs to the squadron

24
00:00:54,860 --> 00:00:56,940
to develop this software.

25
00:00:56,940 --> 00:00:58,630
My involvement with the project ensured

26
00:00:58,630 --> 00:01:01,680
that the software was
tailored to the needs

27
00:01:01,680 --> 00:01:04,630
of a weatherman working
in austere conditions.

28
00:01:04,630 --> 00:01:07,200
The software we developed
consisted of two halves.

29
00:01:07,200 --> 00:01:09,040
A server side and a client side.

30
00:01:09,040 --> 00:01:10,893
The server side is nicknamed Alfred.

31
00:01:10,893 --> 00:01:13,450
And the client side is nicknamed Bruce.

32
00:01:13,450 --> 00:01:15,220
It's an obvious Batman analogy.

33
00:01:15,220 --> 00:01:18,370
The Alfred, or server half,
gathers and packages weather

34
00:01:18,370 --> 00:01:21,680
data for delivery to the
Bruce, or client side,

35
00:01:21,680 --> 00:01:23,350
through the radio.

36
00:01:23,350 --> 00:01:26,730
The Bruce side consists
of a UI to elegantly

37
00:01:26,730 --> 00:01:29,100
and efficiently display
the weather information

38
00:01:29,100 --> 00:01:29,950
for the end-user.

39
00:01:31,337 --> 00:01:32,380
The program that my team created

40
00:01:32,380 --> 00:01:34,820
will allow the airman in
the field to gather data

41
00:01:34,820 --> 00:01:36,620
during critical times before

42
00:01:36,620 --> 00:01:38,870
more robust communications are set up.

43
00:01:38,870 --> 00:01:42,480
Additionally, the properties
of the military radio

44
00:01:42,480 --> 00:01:46,120
allow it to be used in a contested
and degraded environment.

45
00:01:46,120 --> 00:01:48,430
Finally, it's important
to note that these radios

46
00:01:48,430 --> 00:01:50,000
won't just transmit weather data.

47
00:01:50,000 --> 00:01:51,230
They'll transmit any data.

48
00:01:51,230 --> 00:01:52,960
That means that this program

49
00:01:52,960 --> 00:01:54,960
is a stepping-stone
towards being able to use

50
00:01:54,960 --> 00:01:58,361
these radios throughout every
career field in the Air Force

51
00:01:58,361 --> 00:02:00,340
I greatly enjoyed my time
working on this project.

52
00:02:00,340 --> 00:02:03,360
It was interesting being a
member of such a diverse team.

53
00:02:03,360 --> 00:02:05,470
I hope that our efforts give future airmen

54
00:02:05,470 --> 00:02:08,270
the first-in weather and data
capabilities they deserve.