FTB_SU15_Mohanavel_MonissKissen_InternshipReport

FLORIDA NEXTGEN TEST BED INTERNSHIP REPORT
Moniss Kissen Mohanavel
Master of Science in Aeronautics (MSA)
MSA 696
Summer 2015
Florida NextGen Test Bed (FTB), FTB Ambassador
mohanavm@my.erau.edu
2377534

ii
Acknowledgements
I would initially like to thank Todd Waller for inducting me into the Florida
NextGen Test Bed (FTB) International Harmonization Program. I am also grateful to
Kirsten Kasper and all the employees at FTB for allowing me to work on the ongoing
projects involving the Next Generation Air Transportation System. I would also like to
thank MSA Program Advisor, Dr. John Lanicci, for allowing me to take this internship
and convert it into an elective course. I am also thankful to the Career Services
department at Embry-Riddle Aeronautical University for awarding me the Internship
Assistance Award, helping me build my resume, and for guiding me through my pursuit
to obtain an internship. Finally, I would like to thank BeeBee Leong, MSA Program
Advisor, for helping me and responding to my questions about the course.

iii
Abstract
Scholar: Moniss Kissen Mohanavel
Title: Florida NextGen Test Bed Internship Report
Institution: Embry-Riddle Aeronautical University
Degree: Master of Science in Aeronautics
Year: 2015
This report contains a detailed summary of the work that I accomplished through my
internship at the Florida Next Generation Air Transportation System Test Bed (FTB). To
summarize, the report consists of the process involved to develop a baseline of an airport
from scratch using the Total Airport and Airspace Modeler and the benefits of the
developed airport baseline for future research purposes. The other part of the report
contains project management information about the Trajectory Based Operations and
Unmanned Aircraft Systems Integration Demonstration, termed Task-U at the FTB.

iv
Table of Contents
Page
Acknowledgements............................................................................................................. ii
Abstract.............................................................................................................................. iii
List of Figures................................................................................................................... vii
Chapter
I Introduction..................................................................................................1
Airport Baseline Development Project Definition...........................1
Task U Definition ............................................................................1
Project Goals and Scope ..................................................................2
Definitions of Terms........................................................................2
List of Acronyms .............................................................................3
II Review of the Relevant Literature ...............................................................5
Airport Baseline Development Project ...........................................5
Airport Diagram...................................................................5
Terminal Map.......................................................................5
Airport overview..................................................................5
River Approach Maps..........................................................6
TAAM Reference Manual ...................................................6
Task-U Project ................................................................................6
Summary..........................................................................................6
III Project Planning...........................................................................................7
Project Statement of Work...............................................................7

v
Project Steps and Schedule..............................................................7
Project Resources.............................................................................8
Total Airspace and Airport Modeler....................................8
Performance Data Analysis and Reporting System.............9
Airport Surface Detection Equipment-Model X..................9
Aviation System Performance Metrics ................................9
Florida NextGen Test Bed Database....................................9
Task-U Resources ................................................................9
IV Project Outcomes.......................................................................................10
Airport Baseline Project.................................................................10
Digitizing ...........................................................................10
G-tool Modelling ...............................................................10
ASPM Data Analysis .........................................................10
PDARS...............................................................................14
SID/STAR Creator.............................................................14
Simulation and Debugging ................................................14
Task-U Project ...............................................................................15
Modelling and Simulation Exercise...................................15
Technical Interchange Meeting..........................................15
Human in the Loop ............................................................16
Documents Reviewed ........................................................16
V Project Conclusions ...................................................................................17
Lessons Learned.............................................................................17

vi
References..........................................................................................................................18
Appendices
A Tables.........................................................................................................17
B Figures........................................................................................................11

vii
List of Figures
Page
Figure
1 Comparison between Departure operations (IMC vs VMC) at DCA....................11
2 Comparison between Arrival operations (VMC vs IMC) at DCA ........................12
3 Seasonal Comparison of VMC Departures from DCA..........................................12
4 Seasonal Comparison of VMC Arrivals into DCA................................................13

1
Chapter I
Introduction
The internship report contains information about the research projects that I
worked on in the Florida NextGen Test Bed (FTB) and a comprehensive list of my task
and activities in those projects. The FTB is a joint initiative between the Federal Aviation
Administration (FAA) and Embry-Riddle Aeronautical University (ERAU) to provide
rapid prototyping and research of the NextGen programs. The FTB provides a platform to
test the operational feasibility of any new concepts and the NextGen programs.
I was involved in two research projects at the test bed, the Airport Baseline
Development Project using the Total Airport and Airspace Modeler (TAAM) software,
and Task-U, which is Trajectory Based Operations (TBO) and Unmanned Aircraft
Systems (UAS) Integration Demonstration.
Airport Baseline Development Project Definition
The primary reason for developing the baseline of Ronald Reagan Washington
National Airport (DCA) is to use it for future research purposes. The FTB’s airport
research database contains the baseline of a number of airports and this provides the
capability to conduct multiple research studies based on the need. The database did not
have the baseline of Washington-National (DCA) airport and Todd Waller (Project Lead,
FTB) wanted the baseline developed for a scenario analysis.
Task-U Project Definition
Task-U (TBO/UAS) is a research project of the FAA and the objective of
TBO/UAS project is to demonstrate Trajectory Based Operations using Unmanned
Aircraft Systems in Class A airspace and represent the future operations in the National

2
Airspace System (i.e. 2025). The FAA has contracted ERAU to provide project
management and manage the entire Task-U project. Therefore, ERAU was responsible
for accomplishing the project deliverables from start to finish.
Project Goals and Scope
The primary scope of the project is to develop the airport baseline of DCA with
the river approaches and departures, deduce a normal day to simulate, which can
accurately represent the average daily operations (arrivals/departures) compared to the
average of total number of operations in that year, and replicate that day’s schedule for
simulation.
The specific goals for me in the Task-U (TBO/UAS) project was to work as a
project manager assistant during my tenure at the FTB and demonstrate basic project
management skills to help the Project Manager accomplish the deliverables. From the
project management point of view, it consists of creating deliverable updates, creating
monthly reports, assisting in accomplishing milestones, and participating in other
research and demonstration exercises relating to Task-U.
Definitions of Terms
Kick-starter Kick-starter is an engineering exercise to confirm all
connectivity and protocols are correct and that information
flows and mediation all operate correctly (Embry Riddle
Aeronautical Univeristy, 2015a, p.40).
NextGen Next Generation Air Transportation System is the
transformation of the National Air Traffic Control System

3
from a ground-based system to a satellite-based system
(Federal Aviation Administration, 2015c).
Trajectory Based Operations An Air Traffic Management concept in which aircraft
separation assurance and conflict detection is based on the
identification of loss of separation between future positions
of aircraft on their precise four dimensional trajectories
(ERAU, 2015c, p.34).
Unmanned Aircraft System An unmanned aircraft system comprises an unmanned
aircraft, the ground control systems, and support systems
such as launch crews (ERAU, 2015c, p.36).
List of Acronyms
ASDE-X Aircraft Surface Detection Equipment – Model X
ASPM Aviation System Performance Metrics
DAL Dallas Love Field Airport
DCA Ronald Reagan Washington National Airport
ERAU Embry-Riddle Aeronautical University
FAA Federal Aviation Administration
FTB Florida NextGen Test Bed
HITL Human in the Loop
IMC Instrument Meteorological Conditions
M&S Modelling and Simulation
NAS National Airspace System
NextGen Next Generation Air Transportation System

4
PDARS Performance Data Analysis and Reporting System
sFMS simulated Flight Management System
SID Standard Instrument Departure
SOW Statement of Work
STAR Standard Terminal Arrival Route
TAAM Total Airport and Airspace Modeler
TBO Trajectory Based Operations
TIM Technical Interchange Meeting
UAS Unmanned Aircraft Systems
VMC Visual Meteorological Conditions

5
Chapter II
Review of the Relevant Literature
The literature provides information about the research conducted prior to the
baseline development of Ronald Reagan Washington National Airport (DCA) and
documents reviewed prior to working on Task U.
Airport Baseline Development Project
The literature review for this project consisted of reviewing the airport diagram,
terminal map, general airport information, visual river approach charts, and the TAAM
reference manual.
Airport Diagram. I reviewed the airport diagram to understand the structure of
the airport. The diagram gave an idea about the runways, their heading and length,
taxiways, terminal areas, and provided a structural overview to model the airport.
Terminal Map. I reviewed the terminal map of the airport to understand the gates
and the airlines parking in those gates. The airport has three terminals (A, B, and C) and
44 gates.
Airport Overview. The airport overview provided history and a basic overview
of the airport, such as the airlines operating at the airport and some important information
about the operations. One example is how aircraft follow the Potomac River for
approaches into DCA. The perimeter rule restricts aircraft to fly to destinations within a
1250-mile radius from DCA with exceptions to a few destinations, and the slot rule limits
the number of departures and arrivals to 62 per hour (Metropolitan Washington Airports
Authority, 2015).

6
River Approach Maps. The visual river approach maps indicate how the aircraft
follow the river and gave a basic idea of how to model the river approaches for the
project.
TAAM Reference Manual. The TAAM reference manual is a practical guide for
working with TAAM. It has a listing of all the options available in TAAM and provides
troubleshooting on how to perform unknown actions (Jeppesen, 2015).
Task-U Project
I read the TBO/UAS Operational Use Cases and Scenarios document to obtain an
overview about the project. I referred to certain documents to understand the concepts,
definitions, deliverables, and methodology about TBO/UAS project. Further, I exercised
the use of previous monthly reports and status update presentations to create the monthly
reports for the project. In addition, I used some templates available in the FTB to record
meeting minutes and notes.
Summary
The literature review for the airport baseline project indicated that Washington
Reagan National (DCA) airport has some interesting river approaches and departures.
The prospect of modeling these approaches and departures could be a research project by
itself in TAAM. The literature review also indicated that conducting airport research and
understanding the operations was necessary before starting the project. In the case of
Task U, reviewing the project documents helped in understanding the technical terms
discussed in the meetings and eased the process of creating the monthly reports.

7
Chapter III
Project Planning
Project Statement of Work
The Statement of Work (SOW) for the airport project is to develop the baseline of
DCA using TAAM software. One part of the development is to model the river
departures and approaches using the Standard Instrument Departures (SIDs) and Standard
Terminal Arrival Routes (STARs) creator in the TAAM software. The final work would
be to verify the simulation of the developed model in TAAM with the actual operations
data from DCA.
The SOW for the Task-U project is to attend weekly teleconference meetings,
monitor kick-starter activities, provide project management expertise, and contribute
towards accomplishing deliverables during the tenure of the internship.
Project Steps and Schedule
The first step in the airport baseline project is to digitize the airport diagram in
TAAM using the digitizer. The next step is to complete the airport outline developed
from the digitizer to a finished model using the G-Tool option in TAAM. Next, I used
Aviation System Performance Metrics (ASPM) data to get the average operations for a
year and find a single day whose operations number match with the calculated average
for the year. Then, I generated a schedule for the selected day from the Performance Data
Analysis and Reporting System (PDARS).
I created a route, schedule from the PDARS data, and uploaded this into TAAM.
Consecutively, I re-modeled the SIDs and STARs using the SID/STAR creator in
TAAM. After creating all the required files, running the simulation gives an overview of

8
the model created, and further debugging (creating rules) will fine-tune the model.
Finally, comparing the simulations from TAAM to the Aircraft Surface Detection
Equipment – Model X (ASDE-X) simulation will provide a verification of the created
model.
The responsibilities of my work for Task-U included, but were not limited to
recording meeting minutes and notes, creating monthly reports, reviewing documents,
assisting in creating weekly presentations, monitoring kick-starter activities and
participating in three major deliverable activities: (a) Modelling and Simulation (M&S)
exercise, (b) Technical Interchange Meeting (TIM), and (c) Human in the Loop (HITL)
exercise.
Project Resources
I used a number of specialized software programs for the Airport Baseline
Development project, and the three primary software programs used for the project
include TAAM, PDARS, and ASDE-X simulation tool.
TAAM. The capabilities of the TAAM software include airport and airspace
modelling combined with successively processing real and fast-time simulations of the
developed model. The software could generate solutions for multiple what-if scenarios
and the results could augment the real-time operations in the National Airspace System
(NAS). For instance, the operational effect on an airport in the case of a runway closure
could be modeled and simulated. The TAAM software is capable of generating multiple
solutions based on the customer need to solve the runway-closure problem, and the air
traffic controllers could use the results in a real time scenario. Based on the case studied,
TAAM could also conduct statistical analysis and provide Cost Benefit Analysis

9
solutions by generating taxi-time, arrival/departure delay data for the entire airport or a
specific aircraft.
PDARS. The PDARS software has a collection of air traffic data for the major
airports direct from the Air Route Traffic Control Centers, Terminal Radar Approach
Control facilities, and Air Traffic Control Towers (ATAC, 2015). PDARS also has the
ability to visualize the air traffic data on the screen for a selected airport and generate
aircraft track images to model the SIDs and STARs.
ASDE-X. ASDE-X is a surveillance system tool using radar, multilateration, and
satellite technology that allows air traffic controllers to track surface movement of
aircraft and vehicles. It is primarily used by air traffic controllers to reduce runway
incursions (FAA, 2015a).
ASPM. ASPM provides operations and performance data through an online
database system. The data on flights to and from the ASPM airports, and all flights by the
ASPM carriers, including flights by those carriers to international and domestic non-
ASPM airports, could be extracted (FAA, 2015b).
FTB Database. The FTB database had a plethora of documents available in
Dropbox, which is a data storage software program. The access to the FTB Dropbox
folder was available, through which I reviewed some of the past FTB projects and went
through previous interns’ completed projects.
Task-U Resources. The database had a list of research documents and they
provided information and knowledge regarding the TBO/UAS project. The complete list
of documents reviewed is available in Table A2 attached to Appendix A.

10
Chapter IV
Project Outcomes
Airport Baseline Project
The various methods to complete the baseline DCA included digitizing, G-tool
modelling, ASPM data analysis, extracting PDARS data, creating a schedule, creating a
route file, modelling SIDs/STARs, creating rules, debugging, and ASDE-X verification.
Digitizing. To digitize in TAAM, obtain the airport diagram and print it on a 2*2
feet cardboard sheet. To begin, input the co-ordinates (latitudes and longitudes) for the
airport in TAAM. The digitizer is a scanner type of equipment and it has a mouse pointer;
moving the mouse pointer over the corners in the printed airport diagram would create
the outline of the airport diagram in TAAM. Figure B1 in Appendix B shows the
digitized airport model in TAAM.
G-tool modelling. G-tool is a very useful option available in TAAM to model the
airport and allows the user to build on the created digitized airport outline. Using G-tool,
the user can model, edit, and re-create the runways, taxiways, apron centerlines, terminal
areas, gates, and almost any minute details relating to the airport. The user could use
Google Earth and the airport diagram for reference to model the baseline of the airport.
Figure B2 in Appendix B shows the completed G-tool model in TAAM.
ASPM data analysis. The ASPM data allows conducting a comprehensive
analysis of runway configurations, daily operations, and weather data for DCA airport.
The goal for this section is to generate a year’s worth of operations data (2014-2015) for
DCA and analyze the daily operations according to the weather conditions. The data had
the value of the total number of departures and arrivals for each month in terms of Visual

11
Meteorological Conditions (VMC) airport configuration and Instrument Meteorological
Conditions (IMC) airport configuration. I used the data to create a pie chart and
compared the operations (VMC vs. IMC); and the results indicated that VMC operations
were more predominant throughout the year than IMC operations. I created another pie
chart from the data to compare VMC operations by seasons to find out which season had
the most prevalent VMC operations. The results indicated that summer had more VMC
operations compared to any other season. The following figures (1-4) show the
comparison between IMC and VMC operations at DCA based on arrivals and departures,
and seasonal comparison of VMC departures and VMC arrivals at DCA.
Figure 1. Comparison between Departure operations (IMC vs VMC) at DCA.
19,871 (14%)
121,743
(86%)
Departure - IMC vs VMC
1 2VMCIMC

12
Figure 2. Comparison between Arrival operations (VMC vs IMC) at DCA.
Figure 3. Seasonal Comparison of VMC Departures from DCA.
19,342, 14%
122,167,
86%
Arrivals - IMC vs VMC
2IMC VMC
VMC - Spring
25%
VMC -
Summer
27%
VMC - Fall
25%
VMC - Winter
23%
Departures - VMC
Weather VMC - Spring VMC - Summer
VMC - Fall VMC - Winter

13
Figure 4. Seasonal Comparison of VMC Arrivals into DCA.
The ultimate goal of this ASPM data analysis is to isolate a single day, extract the
schedule for that day from Performance Data Analysis and Reporting System (PDARS),
and simulate it in TAAM. To be specific, the date selected from the ASPM analysis for
the year 2014-2015 would represent a normal day from the airport operations point of
view and simulating that schedule in TAAM will provide unbiased results.
The computed average number of daily arrivals (n = 335) and daily departures
(n = 334) matched closely with the actual operations data on 06/22/2014 for DCA airport.
Figure B3 in Appendix B shows the ASPM data metrics and the number of arrivals and
departures for 06/22/2014.
VMC - Spring
25%
VMC -
Summer
27%
VMC - Fall
25%
VMC - Winter
23%
Arrivals - VMC
Weather VMC - Spring VMC - Summer
VMC - Fall VMC - Winter

14
PDARS Reports. I used the PDARS software to extract the reports for the date
chosen (06/22/14) for DCA airport and “formatted” the data using Excel. Then, I created
the schedule and route file from the PDARS report and uploaded the files into TAAM.
Figure B4 and Figure B5 in Appendix B show the respective schedule and route files in
TAAM.
SID/STAR Creator. I used the SID/STAR creator in TAAM to re-create and re-
model the SIDs and STARs for DCA airport. The STAR creator in TAAM had an option
called vectoring, which is the act of altering the length and/or shape of the flight
segments to speed up or delay the arrival. Figure B6 in Appendix B shows the concept of
vectoring in TAAM. I generated actual aircraft tracks from PDARS software to edit and
re-draw the SIDs and STARs for the primary runway (01/19) and the secondary runway
(15/33). Figure B7 in Appendix B shows the generated tracks from PDARS for building
the SIDs and STARs in TAAM.
Simulation and Debugging. I created basic airport rules and loaded the airport
files required to start the simulation in TAAM. The rules form the backbone of the
simulation and the rules have to be modified, according to the requirements of the
research project that needs to be simulated. Therefore, I created some conventional
airport rules (runway, taxiway, and apron area rules) to remove the bottlenecks and
simulated the developed model in TAAM.
The simulation resulted in certain issues, and I debugged those issues by adding
other airport rules. Further, I used the ASDE-X data to compare and verify the simulation
results in TAAM. I simulated the data from ASDE-X in PDARS and compared it to the
simulation of the developed baseline model in TAAM. I fine-tuned the rules and

15
precisely matched the simulations of the developed model in TAAM with the ASDE-X
data simulated in PDARS.
Task-U project
I helped to accomplish some of the major deliverables of the Task-U (TBO/UAS)
project, and the list of meetings attended and minutes recorded are available in Table A1.
Figure B8 in Appendix B illustrates a sample of the minutes recorded during a
teleconference meeting. Table A3 in Appendix A shows the list of monthly reports
created and Figure B9 in Appendix B shows a sample of one of the monthly reports
created. In addition, I assisted and participated in three major research and demonstration
activities listed below.
Modelling & Simulation (M&S) Exercise. Boeing, one of the sub-contractors
for the Task-U project, conducted the M&S activity at their facility in Washington, DC.
They exercised the use of their own simulation software programs like TAAM and
ELASTic to create and simulate the trajectories for demonstrating TBO in class A
airspace with an UAS. The M&S was a demonstration of Boeing’s research and
development to the FAA and other stakeholders in the project (ERAU, 2015b).
Technical Interchange Meeting. The TIM was a deliverable update meeting
between all the stakeholders in the project and it took place in Washington, DC. The team
decided to schedule the Live Flight Demonstration to display TBO in November and
Boeing decided to change one of their 737 aircraft into a UAS for the live flight demo
(FAA, 2015d).

16
Human in the Loop Exercise. The HITL was a demonstration of TBO using the
modified GE simulated Flight Management System (sFMS). The HITL showed how the
ground controller used sFMS to control the UAS from the ground (ERAU, 2015b).
Documents Reviewed. The list of documents created, reviewed and proofread for
Task U is available in Table A2 in Appendix A. The documents created by ERAU and
Boeing were among the deliverables list to be submitted for the Task-U project.

17
Chapter V
Project Conclusions
The airport baseline of DCA was developed to conduct future research on the
SIDs and the STARs involving the airport. The baseline developed could satisfy the
researcher’s requirements, and the rules for the simulation would differ from one scenario
to another based on the study requirements. Completing the project created a prospect for
another interesting research study involving the 1250-mile perimeter rule of DCA.
Recently, the city of Dallas removed a similar amendment at Dallas Love Field (DAL)
airport and it created a major impact on the airport.
Lessons Learned
The airport baseline project provides ideas for further research projects like
removing the perimeter rule and calculating the operational impact. For the Task-U
project, successfully demonstrating TBO using UAS could increase the capacity of the
NAS and reduce the workload on air traffic controllers.
The latest version of TAAM software does not require the user to digitize the
airport, and that could further speed up the process. The user could just select from a list
of airports available in the TAAM database and begin the G-tool modelling. The latest
software also has a pre-loaded list of SIDs and STARs for the selected airport, and this
option saved a lot of time in modelling the SIDs/STARs based on the PDARS aircraft
tracks. I verified the TAAM model with ASDE-X simulation videos, but doing a
validation (regression analysis) with the ASDE-X data could provide a better explanation
about the accuracy of the developed airport baseline.

18
References
ATAC. (2015). Performance Data Analysis and Reporting System.
Retrieved from
http://www.atac.com/pdars.html
Embry Riddle Aeronautical University. (2015a). TBO-UAS FMS System Enhancements
& Integration. Daytona Beach, FL.
Embry Riddle Aeronautical University. (2015b). Modeling & Simulation (M&S), Human-
in-the-Loop (HITL) & Demonstration Plan. Daytona Beach, FL.
Embry Riddle Aeronautical University. (2015c). Operational Use Cases and Scenarios
for Task-U. Daytona Beach, FL.
Federal Aviation Administration (2015a). Airport Surface Detection Equipment, Model X
(ASDE-X). Retrieved from
https://www.faa.gov/air_traffic/technology/asde-x/
Federal Aviation Administration. (2015b). Aviation System Performance Metrics
(ASPM).
Retrieved from
http://aspmhelp.faa.gov/index.php/Aviation_Performance_Metrics_%28APM%29
Federal Aviation Administration. (2015c, May 1). NextGen Implementation Plan 2015.
Retrieved from
https://www.faa.gov/nextgen/media/NextGen_Implementation_Plan-2015.pdf
Federal Aviation Administration ANG-C5. (2015d, June). UAS/TBO Live Flight
Demonstration. Washington, DC.
Jeppesen. (2015, March 26). TAAM Reference Manual. Australia
Metropolitan Washington Airports Authority. (2015). About Ronald Reagan Washington
National Airport. Retrieved from
http://www.flyreagan.com/dca/airport-
overview?_ga=1.169169829.547885115.1442293065

19
Appendix A
Tables
Table A1
List of meetings attended and minutes recorded
Date Name of the meeting Minutes and Notes
05/20/15 Boeing TBO/UAS weekly teleconference meeting No
05/21/15 Task-U weekly status meeting Yes
05/27/15 Boeing TBO/UAS weekly teleconference meeting Yes
06/03/15 Modelling and Simulation Exercise Yes
06/26/15 Kick-Starter Meeting Yes
07/13/15 Kick-starter Meeting No
07/15/15 Technical Interchange Meeting Yes
07/23/15 Task-U weekly status meeting No
08/11/15 HITL Dry Runs Yes
08/12/15 HITL Dry Runs Yes
09/04/15 Human in the Loop Exercise Yes
Note. The meetings highlighted in Bold and italics are demonstration exercises and
special meetings.

20
Table A2
Documents reviewed for Task-U
Title Responsibility
1 TBO/UAS Operational Use Cases and Scenarios Reviewed
2 Modelling & Simulation (M&S), Human-in-the-Loop (HITL)
& Demonstration Plan
Reviewed
3 Safety Risk Management and Decision Memo Reviewed
4 Mini Global Demo Plan Created sections
5 TBO/UAS Live Flight Demonstration Proofread
6 TBO/UAS Flight Management Systems Enhancement
Integration
Reviewed
Table A3
List of reports created for Task-U
Monthly Report Reviewed/Created
1 Task U May monthly report Reviewed
2 Task U June monthly report Created
3 Task U July monthly report Created
4 HITL handout Created

21
Appendix B
Figures
Figure B1. Shows the digitized output of DCA.

22
Figure B2. Shows the completed G-tool layout of DCA.

23
Figure B3. Shows the ASPM performance metrics data for DCA in June 2014.

24
Figure B4. Shows the schedule file for DCA uploaded in TAAM.

25
Figure B5. Shows the route file for DCA uploaded in TAAM.

26
Figure B6. Describes the concept of vectoring in TAAM.
Figure B7. Shows the aircraft tracks generated from PDARS to build the STAR’s in TAAM.

27
Florida NextGen Test Bed
Task U Weekly Meeting Minutes
July 30, 2015
Present: Chris Kokai, Samet Ayhan, Charles Chen, Michael Masters, Thien Ngo, and Ian Wilson
Next meeting: August 6, 2015, 10am, FTB
Announcements
 Agenda for today’s meeting: Discuss about Dry Runs, Kickstarter activities, and the agenda for
the HITL
 Kickstarter #4 scheduled on Aug 7th
 HITL scheduled for Sep 3rd
 Samet: Need more than 30min after Indra’s test session for Sep 3rd
HITL
 Agenda for Dry Run (08/11)
o Morning : System preparation and Dry Run; Afternoon : Review Use case, Mini Global
agenda, and HITL agenda
o Same applicable for 08/12
 Mike agreed to accommodate Task U’s dry run on 08/11 and 08/12 in the FTB
 Charles: Two VNC machines and GE sFMS box available in the FTB for Kickstarters and HITL
 Samet wants to use the two big screens in the FTB to display Mini Global viewer and Trajectory
visualization and editing tool
 Thien: SRMDM just requires a last signature to fly the Boeing 737 for Task U TBO/UAS
demonstration
 Thien: John Stanley is available in the FTB to help for Task U HITL and other activities (He is
available for the entire week starting from Aug 31st
– Sep 4th
2015)
Discussions
 Task U’s HITL needs at least 1 hour after Indra’s test session (for setting up the systems and to
start the demo)
 The agenda for Sep 3rd
has TBO/UAS HITL activities scheduled between 08:30-12:30 EDT
has a lunch break between 12:30-13:30 EDT
 Thien has agreed to move his meeting to 14:00 on Sep 3rd
(His meeting was scheduled at 13:30
EDT) to accommodate Task U HITL
 Samet wants to end Task U’s HITL on Sep 3rd
at 12:30 EDT to allow people to go for lunch

28
 Indras’s testing session on Sep 3rd
is scheduled between 06:30-08:00 EDT (its tentative and has
been proposed to them)
 FTB Integrated Test (07/27) – Observed Issues discussed
 Thien discussed about the agenda for Sep 2nd
o Presentations in the morning
o Tool demos from the presenters in the afternoon
 Mary Ellen needs to send the final agenda for Sep 2nd
before it can be reviewed and discussed
Roundtable
 Samet, Chris and Thien discussed about the need to finish the HITL on Sep 3rd
at 12:30 EDT to
allow people to break for lunch
has Indra’s test session scheduled between 06:30-08:00 EDT and Task U
HITL between 08:30 and 12:30 EDT
 Samet requested for an hour gap in between the two activities scheduled
 Kickstarter scheduled on Aug 7th
and Dry Run’s scheduled on Aug 11th
and 12th
Figure B8. Illustrates an example of the minutes recorded at FTB during a teleconference
meeting.

29
Figure B9. Shows the Project Timeline and Accomplishment sections of the monthly report
created for Task U.

FTB_SU15_Mohanavel_MonissKissen_InternshipReport

Recommended

Recommended

More Related Content

Similar to FTB_SU15_Mohanavel_MonissKissen_InternshipReport

Similar to FTB_SU15_Mohanavel_MonissKissen_InternshipReport (20)

FTB_SU15_Mohanavel_MonissKissen_InternshipReport