<Airline Logo>
MEMORANDUM OF UNDERSTANDING
BETWEEN
THE FEDERAL AVIATION ADMINISTRATION
DATA COMMUNICATIONS PROGRAM OFFICE
AND
<Airline>
TO SUPPORT FAA DATA COMMUNICATIONS PROGRAM OFFICE
DEPARTURE CLEARANCE (DCL) OPERATIONAL TRIALS
The terms of this Memorandum of Understanding (MOU or Understanding) represent
the complete understanding between the parties concerning all known issues regarding
the FAA Data Communications Departure Clearance (DCL) Trials initiative. The two
sites of the Data Communications Departure Clearance (DCL) Trials (Trials) are
Memphis (MEM) Air Traffic Control Tower and Newark (EWR) Air Traffic Control
Tower.
1
Parties
The parties to this MOU are the Federal Aviation Administration (FAA) and <Airline>.
Points of Contact
The FAA and <Airline> agree to provide a designated point of contacts [POC] who are able
to address any issues pertaining to the Trials development and implementation for the
duration of Trials activities,
FAA (FAA POC)
Dennis L. Scanlon, Contracting Officer, AAQ-320 800 Independence Avenue, S.W.
Room 506
Washington, DC 20591
202-367-9422
dennis.scanlon@faa.gov
<Airline Contact>
2
Type of Agreement
This agreement is an Other Transaction - Memorandum of Understanding (MOU). As a
Memorandum of Understanding, this document represents an agreement to agree. This MOU
is not legally binding on either party. This MOU memorializes the plans of the parties for
cooperation and participation of the parties in the Data Comm Trials at the Memphis and
Newark Towers.
FAA DCL Trials Objectives
The FAA objectives of this MOU are as follows:

Support the Departure Clearance (DCL) CONOPS proof of concept

Support DCL Requirements Development for the 2015 TDLS Data Communications
upgrade;

Support DCL FAA facility training and procedures development; and,

Collect and calculate performance and benefit metrics for DCL resulting from the
operational Trials.
Data Communication DCL Service and Data Comm Trials Background
The DCL service provides automated assistance for requesting and delivering initial and
revised departure clearances to and from a FANS equipped flight deck. The intended use of
DCL service is during the surface departure phase of operation and will replace the existing
Pre-Departure Clearance service (PDC) at trial sites(s) for appropriately equipped and
participating aircraft. DCL provides Controller Pilot Data Link Communication (CPDLC)
messages for the following:

Flight plan route including SID/STAR,

Initial and requested altitude,

Beacon code assignment,

Control time, and

Departure frequency.
3
When CPDLC is used to provide DCL, the above information can be exchanged using
CPDLC message elements. During the Trials, appropriate message elements will be
selected from those defined in RTCA SC-214/D0-258A that already support FANS
avionics.
The DCL Trials will use a stand-alone DCL Trials Automation Platform System (DTAP).
That system will process participating initial and revised DCL aircraft clearances
independent of the current FAA TDLS system. The DTAP will interface with the Tower
Air Route Traffic Control Center Host ATM Data Distribution System (HADDS) interface
to receive NAS flight data. The Air Traffic Control Tower (ATCT) Clearance Delivery
position will host a dedicated DTAP DCL display and user interface for the duration of
the Trials. Participating Future Air Navigation (FANs:.1A /FANS1A+) equipped aircraft
will log into the DTAP via a communications service provider data link and establish a
Controller Pilot Data Link Connection (CPDLC). Once the link is established, the flight
deck will request and receive its initial departure clearance and any revisions to that
clearance. DCL Trials Justification - Data Communications Implementation Team
Background
In order to ensure success of the Data Comm program, it is necessary to engage
multiple stakeholders across all of the aviation industry in the development of the Data
Comm system. A key to that necessity, is the FAA Data Communications Implementation
Team (DCIT). The DCIT consists of the FAA, Airlines, the National Air Traffic Controllers
Association (NATCA), avionics manufacturers, data link communications providers, and
other interested industry members. After identifying a need for Trials, the DCIT and
associated Working Groups (ATC, AOC, Flight Deck, System Integration) have met
monthly during 2011-2012 to plan for these, and possibly subsequent, Trials. The Trials
will inform and support the Program's CONOPS and particularly the DCL CONOPS. The
Trials will also inform and support DCL requirements development for TDLS, facilitytraining development, and it will facilitate early collection of operations, performance, and
benefit metrics by the FAA and airlines. That data would not otherwise be available
before 2015-2016, because the permanent FAA Terminal Data Link System (TDLS) Data
Communications upgrade is not
scheduled to commence until 2015-2016. Early collection of this data is essential to the
success of the Data Comm Program because it facilitates understanding of needed
procedures early, and that allows adequate time to identify and remedy potential issues
that have the potential to disrupt the 2015 permanent FAA DCL rollout.
Funding and Trials Cost
The DCL Trials at Site #1 - MEM are not funded under this MOU and each party shall
bear the full cost it incurs to perform, manage, and administer its responsibilities under
this MOU.
Responsibilities of the Parties
(a) FAA
4
DTAP Requirements and Development
This work includes development and placement of a vendor COTS AL3 certified system
in the Trials facilities to support Trials execution. The FAA Trials team will develop
ground automation requirements and solicit vendor plans to meet those requirements.
To accomplish the installation, an interface with the National Airspace System (NAS), a
Communications Service Provider (CSP), and a Computer-Human Interface (CHI) will
be required. The FAA will perform test acceptance activities; deliver the system, and
support integration and maintenance.
Tower Procedures
The FAA will support the activities necessary to develop and receive approval for the
operational procedures used during execution of the Trials. The FAA estimates that
80% of the Trials procedural requirements can be determined irrespective of trial sites,
while the remaining 20% will be site-specific. The Trials team will coordinate with
several stakeholder groups including AJT SOS, AIR, AFS, NATCA, PASS, AJW, Facility
POCs, and Airline POCs.
Tower Training Requirements
The FAA will support the activities necessary to develop training requirements for Tower
trial participants.
SRMD Approval
The FAA Trials must meet relevant safety requirements, receive requisite approvals,
and the FAA must conduct the Trials in accordance with applicable safety guidance.
The FAA Trials team will follow the FAA's Safety Risk Management (SRM) process and
will develop and submit a Safety Risk Management Document (SRMD) for Agency
review and approval.
Test NAS Change Proposals (NCP)
The FAA will support the activities necessary to develop and ensure processing of
Technical, Space and Power Test NCPs for DTAP installation at MEM ATCT, ZME
6
ARTCC. In addition, The FAA will facilitate new NCP for FTI connection (physical or
logical) between the ZME ARTCC HADDS interface and MEM ATCT DTAP.
DCIT Coordination
The FAA will support the activities necessary via the Data Communications
Implementation Team (DCIT) meetings as a forum for discussions to ensure the
participation of airlines in support of Trials execution.
DTAP FAA Tech Center Testing
The FAA will support the activities necessary to complete end-to-end testing of the
ground automation system, such as: HNL HADDS configuration, application interface
acceptance testing, bench testing with avionics, AOC and CSP connectivity testing, and
"aircraft-in-the-loop" testing.
Trial Management
The FAA will support the activities necessary to conduct the Trials. The Trials team will
deliver training to participants as close as possible to the operations start date in order
to minimize refresher training prior to the start of each trial. Equipment delivery and
installation will be coordinated with the vendor and facility, followed by end-to-end
testing and resolution of any Problem Trouble Reports (PTR). Each trial/phase will start
with a familiarization period during which controllers, Ground Observers, and pilots will
be able to gain an understanding of the system and become comfortable with the
system and procedures. "Full scale" Trials will follow for a period, the length of which
the FAA will determine. Duration, possible extension, and conduct limitations will be
developed and finalized in cooperation with the selected facilities and the participating
aircraft operators. The FAA will conduct a trial closeout process that will include a
briefing to the facility.
Safety Summit
The FAA will conduct a safety summit about every one hundred-twenty (120) days.
During the safety summit, the FAA will analyze the data collected during the Trials to
7
investigate whether any anomalies warranting attention have occurred. The FAA will
make a determination at its sole discretion regarding whether to start, continue, or
extend any Trial.
Communication Service Provider (CSP) Connectivity
The FAA will support the activities necessary to provide communication between the
ground system and aircraft. The Trials team will define coverage and connectivity
requirements that will be integrated into the agreement with the operators. Since the
operator's must already have a working partnership with a capable communications
vendor, the responsibility of ensuring communication processes will be decided by the
DCIT working groups. The FAA will conduct testing of communication capabilities to
ensure satisfactory performance.
Ground-to-Ground Connectivity with AOC and CSP
The FAA will be responsible for coordinating with AOC's, participating CSP's, and FAA
Telecommunication Infrastructure (FTI) to ensure adequate connectivity between
relevant systems.
Site Installation and IOC
The FAA will be responsible for overseeing installation and integration of the DTAP at
the Tower facility, conducting Site Acceptance Testing (SAT), and completing related
activities necessary to declare IOC.
Trial Conduct Support and Maintenance
The FAA will provide personnel for its portion of the work to conduct the Trial and to
collect data.
Data Collection and Analysis
The FAA will develop methods of data collection for use during the Trial's execution.
Collection, analysis, and reporting of data will occur under program office guidance.
Expanding user participation
8
The FAA will conduct outreach to increase the numbers of airline participants and the
degree of participation in the Trial. To expand user participation and enhance the range
of data collected, the FAA will coordinate with airspace users beyond the initial
participants, identify opportunities and means to broaden participation and service
delivery, and, at its discretion, the FAA will implement such enhancements.
MEM Site Acceptance Testing (SAT)
The FAA will develop and conduct all SAT at the Trials location to ensure the system
operates correctly. This testing will include:
Verification of DTAP functionality and interfaces
OTAP connectivity with HAADS and FTI
Connectivity between the FAA and subject aircraft on ramps and taxiways
Trials Equipment Maintenance
The FAA will develop and execute a maintenance plan to ensure continuity of the
ground-to-ground and interface connectivity. This excludes maintenance of the DTAP
system itself, which the DTAP vendor will perform.
Facility ATC Training
The FAA will develop, approve, and deliver training to the Trials participants. Training
development will include coordinated and approved curriculum of operational and
technical training. The training will instruct participants in the use of the hardware,
software, procedures, and related system interfaces. Trials platform simulation
scenarios will be developed to enhance classroom instruction to provide Trials
participants with practical exercises before actual use.
(b) <Airline>
Participating Aircraft
9
<Airline> has committed FANS equipped aircraft and Operations Control Center (OCC)
support to ensure that an adequate number of aircraft are available at MEM and EWR
for participation in the Trials. <Airline> agrees to provide daily FANS equipped aircraft
capable of participating in CPDLC DCL Trials. <Airline> agrees to provide MEM and
ERW ATCT via email at DCIT@harris.com a current list of daily, weekly or monthly
participating DCL flights/air frames including the call sign and Registration N# as part of
this notification. FOX agrees that participating DCL aircraft will have crews trained for
such purposes.
<Airline>POC
The <Airline>POC will ensure that that the MEM ATCT receives all participating
DCL flight/air frames for entry into the Trials automation platform.
Airline Operations Center Support
<Airline>agrees to work with FAA DCIT/DCIS and Data Communications Trials
Automation Platform (DTAP) contractor representatives to help complete DTAP
requirements and development work.
PDC Suppression
The <Airline> AOC shall support any necessary AOC PDC suppression requirements for
participating DCL aircraft. This could include adding remarks (FRC DCL) to all
participating DCL flight plans and/or modifying OCC systems to limit PDCs back through
a CSP to the flight deck.
Trials Data Collection and Metrics
<Airline> agrees to allow FAA DCIT and contractor personnel access to the flight
deck for DCL processing observation and solicitation of pilot feedback. <Airline>
agrees to provide all Trials related flight data upon FAA request for Trials analysis and
benefits calculations.
Warranties
10
The parties hereto make no express or implied warranty of any type in this MOU.
Effective Date/Term/Termination
This MOU shall be effective on the date of the last signature of the parties for a period
not to exceed Three (3) years and shall remain in force until terminated by mutual
agreement or unilaterally by either party upon thirty (30) days' notice to the other party.
Legal Authority
This Agreement is entered into under the authority of 49 U.S.C. 106(1) and (m), which
authorizes agreements and other transactions on such terms and conditions as the
Administrator determines necessary.
Execution:
FAA Concur:
Date:
<Airline> Approved:
Date:
11
12