New Airline Participation Document Draft– July 26, 2013
Data Communications Implementation Team (DCIT)
Departure Clearance Service (DCL) Trials
New Airline Participation Document
Version DRAFT
July 26, 2013
Airline Onboarding Document Table of Contents Page 1 of 13 New Airline Participation Document Draft– July 26, 2013
DOCUMENT CHANGE HISTORY
Revision Author Change Date Change Summary 0 Sean StJohn 7/26/13 Draft
Airline Onboarding Document Table of Contents Page 2 of 13 New Airline Participation Document Draft– July 26, 2013
Table of Contents
1 Introduction______5 2 DCL Trials Overview______5 3 Trials Time Line______7 4 What is expected from the Participating Airline______8 4.1 Identification and Participation of selected aircraft______8 4.2 Update Airline Specific Procedures______8 4.3 Training______8 4.4 Feedback______8 4.5 Attendance at the Operations Management Working Group (OMWG)______8 4.6 Attendance at DCIT______9 4.7 Funding and Trials Cost______10 4.8 FAA Regulatory (Safety)______10 5 FAQs______11 6 Additional Trials Details and Specifications______12 6.1 Systems Integration and Description Document (SIDD)______12 6.2 DCL End-to-end Trials Procedures Document______12 6.3 Flight Deck Operations Procedures______12 6.4 Trails Management Plan______12 6.5 DCL Trials Survey______12 6.6 Moratorium of Understanding (MOU)______12 7 Appendix A______13 7.1 MOU Template______13
List of Tables
Airline Onboarding Document Table of Contents Page 3 of 13 New Airline Participation Document Draft– July 26, 2013
No table of figures entries found.
List of Figures
No table of figures entries found.
Airline Onboarding Document Table of Contents Page 4 of 13 New Airline Participation Document Draft– July 26, 2013
1 Introduction
This document describes the onboarding process for new airlines wishing to participate in the Data Comm Departure Clearance (DCL) Trials. This document will also provide an overview of the DCL Trials and explain what is expected from the airlines if they decide to participate.
2 DCL Trials Overview
The DCL Trials support pre-operational demonstrations of key aspects of the tower controller-pilot data link communication (CPDLC) services in field trials. The DCL trials will validate the concept of operation for the delivery of departure clearances and revised departure clearances through advanced automation and CPDLC. The trials will ensure procedures and training plans are appropriate, and will provide airspace users an opportunity to experience the benefits associated with Data Comm services. Operational trials will evaluate requirements in support of the fully-compliant automation system development and deployment. The DCL service is designed for use in surface operations and replaces the existing Pre-Departure Clearance (PDC) at trial sites for participating aircraft.
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.
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.
Airline Onboarding Document Introduction Page 5 of 13 New Airline Participation Document Draft– July 26, 2013
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 MEM Air Route Traffic Control Center Host ATM Data Distribution System (HADDS) interface to receive NAS flight data. The MEM 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.
Airline Onboarding Document Introduction Page 6 of 13 New Airline Participation Document Draft– July 26, 2013
3 Trials Time Line Trials are conducted in two stages for each airline as the join the DCL trials. First will be limited trials to help train staff and get the Air Traffic Control Tower (ATCT) and airlines comfortable with the DCL procedures. Full trials will start once the ATCT and the airlines are comfortable that all are ready and system is stable. The length of limited trials will vary and be dependent on each airline. See the Trials Management Document for more detailed information on scheduling participating flights in Limited vs. Full Trials.
Trials are currently being conducted at Memphis and Newark towers only. There are currently no plans to extend to other towers as part of the trials.
The current participating airlines at each ATCT are as follows:
Memphis ATCT: Federal Express
Newark ATCT: United Parcel Service, Federal Express, United Airways, British Airways, Lufthansa Airlines, and Scandinavian Airlines
Note: These are the participating Airlines as of the creation date of this document. Airlines may change as Trials progress.
Airline Onboarding Document Page 7 of 13 New Airline Participation Document Draft– July 26, 2013
4 What is expected from the Participating Airline The following are the expectations of participation in the DCL trials.
4.1 Identification and Participation of selected aircraft The airline is expected to identify which aircraft will be participating in the trials and supply that information to the DCIT. In the case of limited trials, aircraft are scheduled on a weekly basis. In the case of full trials, aircraft are identified as they choose to participate in the trials. Participating aircraft must have access to the trials service with a VHF FANS equipped radio. HF and Satellite are not support.
4.2 Update Airline Specific Procedures The participating airline will need to modify their existing flight and AOC procedures to support trials operations. Flight procedures need to be changed to support the flight deck interaction with the tower. This specifically includes how to process DCL messages and when to fall back to voice. AOC procedures need to be changed to support the filing of Flight Plans using FRDCL in the comments field and receiving DCL trials dispatch messages at the AOC. There may also be changes needed to the Airlines Safety procedures which should be addressed by each airline.
4.3 Training The airlines are responsible for ensuring all participating pilots and AOC personnel are trained on the DCL trials procedures. Training procedures are developed by the DCIT working groups and … I need help here…
4.4 Feedback Feedback is expected from the airlines to help evaluate the DCL System. Feedback can and should be given at any time the airline has input. Feedback is expected from the airlines on issues that are discussed at the DCIT meetings. Feedback from the AOC and Flight deck is invaluable to help ensure the end system meets user needs and is effective.
In addition to Ad-Hoc feedback, there is a standard feedback/survey forum that was developed by the DCIT and it is requested that each participating AOC and Flight Deck personal complete.
4.5 Attendance at the Operations Management Working Group (OMWG) The OMWG is a weekly meeting composed of all the stakeholders in the DCL trials including the FAA, participating airlines, service providers, Harris, and other industry partners. It is held every Tuesday during the life of the DCL trials and is managed by the DCL Trials Lead.
Airlines are expected to attend and discuss the flights for the previous week or any issues or questions that they have.
Airline Onboarding Document Page 8 of 13 New Airline Participation Document Draft– July 26, 2013
The primary function of the OMWG is to state the results of flights over the preceding period, identify operational issues, and task out resolution for the issues. This is done via the following basic format:
. Quick and up-to-date stats
– Basically, last week’s stat’s, thru Friday, available on a Tuesday
. Ops around the room
– Ops leads from ATC, aircrew, and Dispatch report/drive discussions; minimal non- ops input
– Gauge operational health of the system
– Advise problems for joint resolution (near-term and more permanent fixes)
. Review of implementation date(s) for previously agreed problem resolutions.
. Review flights planned for the upcoming period
. Current Baseline documents (end-end, SIDD, Flt Deck), and planned updates (content and update schedule)
. Meeting records should go out the day of the telecon
4.6 Attendance at DCIT 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, facility-training 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
Airline Onboarding Document Page 9 of 13 New Airline Participation Document Draft– July 26, 2013 identify and remedy potential issues that have the potential to disrupt the 2015 permanent FAA DCL rollout.
It is expected that each participating airline attend the DCIT meetings and provide input and feedback. Additional information about the DCIT can be found on the FAA’s website: http://www.faa.gov/about/office_org/headquarters_offices/ato/service_units/techops/atc_comms _services/dcit/
4.7 Funding and Trials Cost The DCL Trials are not funded by the government for the Airlines. The airlines shall bear the full cost it incurs to perform, manage, and administer its participation in the DCL Trials.
4.8 FAA Regulatory (Safety) Trent to provide me with section write-up.
Airline Onboarding Document Page 10 of 13 New Airline Participation Document Draft– July 26, 2013
5 FAQs
TBD – I need the group to provide these to me.
Airline Onboarding Document Page 11 of 13 New Airline Participation Document Draft– July 26, 2013
6 Additional Trials Details and Specifications The below referenced documents are used for the DCL trials and contain additional and/or more in depth information about the program and system. Most of the documents can be found on the FAA’s DCIT website located at: http://www.faa.gov/about/office_org/headquarters_offices/ato/service_units/techops/atc_comms _services/dcit/
6.1 Systems Integration and Description Document (SIDD) The SIDD is a technical document that describes the systems architecture and integration plan that enable the end-to-end system underlying the Data Communications Program (DCP) Departure Clearance (DCL) Trials activities.
6.2 DCL End-to-end Trials Procedures Document This document describes the details of how the DCL Trials Systems work from beginning to End. This document is also used as the requirement document for coding of the DCL trials systems.
6.3 Flight Deck Operations Procedures These procedures describe how the flight deck operates when participating in the DCL trials service.
6.4 Trails Management Plan This document describes the operational procedures for the Data Communications Program (DCP) Departure Clearance (DCL) Trials activities. This is not a public document and will be provided by the DCL Trials lead.
6.5 DCL Trials Survey This is the survey that is provided to participant in the trials and is used to collect input on trials operation.
6.6 Moratorium of Understanding (MOU) This document is a working agreement between the FAA and each airline specifies the expectations of each. Please see Appendix A for a template and example.
Airline Onboarding Document Page 12 of 13 New Airline Participation Document Draft– July 26, 2013
7 Appendix A
7.1 MOU Template TBD - Scrubbing FedEx MOU to make generic for template.
Airline Onboarding Document Page 13 of 13