Systems Integration Description Document Version 1.0– August 27, 2012 Data Communications Implementation Team (DCIT) Departure Clearance Service (DCL) Trials Systems Integration Description Document Version 1.0 August 27, 2012 DCP INTEGRATION PLAN Table of Contents • Page 1 of 37 Systems Integration Description Document Version 1.0– August 27, 2012 DOCUMENT CHANGE HISTORY Revision Author Change Date 0.1 DCIT Systems Integration Team DCIT Systems Integration Team 02/08/2012 Initial draft 04/24/2012 DCIT Systems Integration Team DCIT Systems Integration Team DCIT Systems Integration Team DCIT Systems Integration Team 05/07/2012 0.7 DCIT Systems Integration Team 07/11/2012 0.8 DCIT Systems Integration Team 08/22/2012 Revised draft to include end-to-end system architecture, and system description information Revised draft to include Courtesy Copy material Revised draft to include updated system level threads Revised draft to include protocol stack , TDLS and ERAM description Revised draft to include updated diagrams and text to describe the threads; update to assumptions Revised draft to include updated diagrams and text based on reviews and feedbacks Revised draft to include updated diagrams and text based on reviews and feedbacks 1.0 DCIT Systems Integration Team 08/28/2012 0.2 0.3 0.4 0.5 0.6 DCP INTEGRATION PLAN 05/14/2012 05/30/2012 06/14/2012 Change Summary Table of Contents • Page 2 of 37 Systems Integration Description Document Version 1.0– August 27, 2012 Table of Contents 1 INTRODUCTION ____________________________________________________ 6 1.1. Scope ______________________________________________________________ 6 1.2. Applicable Documents _______________________________________________ 7 2 SYSTEMS INTEGRATION APPROACH _________________________________ 9 2.1 3 Assumptions ___________________________________________________________ 9 SYSTEM DESCRIPTION______________________________________________ 10 3.1 Overview _____________________________________________________________ 10 3.2 Systems Descriptions and Interfaces _____________________________________ 11 3.2.1 3.2.2 3.2.3 3.2.4 3.2.5 3.2.6 3.2.7 3.2.8 3.2.9 3.2.10 4 INTEGRATION AND SEQUENCE DATA FLOW ________________________ 16 4.1 4.1.1 4.1.2 5 6 Overview ____________________________________________________________________ 11 Data Comm Trials Automation Platform (DTAP) _________________________________ 12 HOST _______________________________________________________________________ 13 Host ATM Data Distribution System (HADDS) ___________________________________ 13 Tower Data Link Services (TDLS) _______________________________________________ 13 NAS Security Gateway ________________________________________________________ 13 CSP networks ________________________________________________________________ 14 Aircraft ______________________________________________________________________ 14 Airline automation ____________________________________________________________ 14 Airline Operations Center (AOC) _____________________________________________ 15 Integration Approach___________________________________________________ 16 Ground-Ground Integration ____________________________________________________ 16 Air-Ground Integration ________________________________________________________ 17 End-to-End – SEQUENCE DATA FLOW ________________________________ 19 5.1 FLIGHT PLAN PRIOR TO DEPARTURE TIME ___________________________ 19 5.2 Timeline: Pre-Conditions _______________________________________________ 20 5.3 Logon and Session Establishment________________________________________ 21 5.4 Departure Clearance (DCL) _____________________________________________ 21 5.5 Revised Departure Clearance (Revised DCL) ______________________________ 23 5.6 Session Termination ___________________________________________________ 23 DISPATCH MESSAGE FORMATS _____________________________________ 25 DCP INTEGRATION PLAN Table of Contents • Page 3 of 37 Systems Integration Description Document 7 Version 1.0– August 27, 2012 TEST PROGRAM DESCRIPTION _____________________________________ 32 7.1 Approach and Concept _________________________________________________ 32 7.1.1 7.1.2 7.1.3 7.2 Evaluation Approach __________________________________________________________ 32 Performance Thresholds _______________________________________________________ 32 Activities Leading To Test _____________________________________________________ 32 Test Environment ______________________________________________________ 33 7.2.1 Test Location _________________________________________________________________ 33 7.3 Test and Analysis Tools ________________________________________________ 33 7.4 Test and Evaluation Descriptions ________________________________________ 34 7.4.1 7.5 DCL Trials End-to-End System Testing __________________________________________ 34 Test Approach _________________________________________________________ 35 APPENDIX D - Glossary _________________________________________________ 36 List of Tables Table 6-1 Table 6-2 Table 6-3 Table 6-4 Table 6-5 Table 6-6 Table 6-7 Table 6-8 Table 6-9 Initial Dispatch Message (CC) Message Format ................................................... 25 Revised Dispatch Message (RC) message format ................................................ 26 Notes ..................................................................................................................... 27 Clearance Fields ................................................................................................. 27 Revised Fields ...................................................................................................... 28 Dispatch Message Example................................................................................... 29 Revised Dispatch Message Example .................................................................... 29 Dispatch Message Acknowledgement Message ................................................... 30 Dispatch Message Acknowledgement Field Descriptions ................................... 30 List of Figures Figure 3-1 DCL Trials Architecture ................................................................................... 10 Figure 3-2 Protocol Stack View .............................................................................................. 12 Figure 4-1 DCL Trials End-to-End System Test Architecture ....................................... 16 Figure 4-2 Ground-Ground Integration .................................................................................. 17 Figure 4-3 Air-Ground Integration ......................................................................................... 18 Figure 5-1 Parameters for FP-to-Logon Correlation ....................................................... 19 Figure 5-2 Time Line: Pre-Conditions .................................................................................... 20 Figure 5-3 AFN Logon & Session Establishment .................................................................. 21 Figure 5-4 Departure Clearance- WILCO .............................................................................. 22 Figure 5-5 Departure Clearance- STANDBY......................................................................... 22 DCP INTEGRATION PLAN Table of Contents • Page 4 of 37 Systems Integration Description Document Version 1.0– August 27, 2012 Figure 5-6 Revised Departure Clearance ................................................................................ 23 Figure 5-7 Session Termination .............................................................................................. 24 Figure 7-1 DCL Trials End-to-End Test Process .................................................................... 35 DCP INTEGRATION PLAN Table of Contents • Page 5 of 37 Systems Integration Description Document 1 Version 1.0– August 27, 2012 INTRODUCTION This document describes the systems integration plan as part of the end-to-end system towards the Data Communications Program (DCP) Departure Clearance (DCL) Trials activities. 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 provides automated assistance for requesting and delivering initial and revised departure clearances. DCL provides CPDLC messages for the following: Flight plan route, initial and requested altitude and departure frequency. When DCL is provided through the use of CPDLC, this information is exchanged using CPDLC messaging. For the trials, the messages will be selected from those already used in Future Air Navigation Services (FANS) equipped aircraft. The CPDLC message elements are defined in RTCA DO-258A that current FANS avionics already support. The DCL service is designed for use in surface operations and replaces the existing Pre-Departure Clearance (PDC) at trial sites for participating aircraft. 1.1. Scope This document describes the system integration characteristics and the overall end-to-end architecture of the Federal Aviation Administration’s (FAA) DCL trials. This document is strictly limited to the initial trial at Memphis. Additional features that may be available for operational or trials beyond the first will be covered in future releases of this or other similar documents. These trials will take place in the 2012-2014 timeframe at various airports including Memphis, Atlanta and Newark. The primary purpose of the trials is to validate the concept of use associated with delivery of Data Comm services to the tower environment. This document also provides an overall technical approach for integrating the DCL Trials end-to-end system components supportive of the ATS Facilities Notifications (AFN) Logon and DCL service implementation by way of FANS as an air / ground digital communication solution. The DCL Trials will validate the concept of operation for the delivery of departure clearances and revised departure clearances through advanced automation and CPDLC. Systems Integration Description Document INTRODUCTION • Page 6 of 37 Systems Integration Description Document Version 1.0– August 27, 2012 1.2. Applicable Documents The following documents are considered applicable to the integration activities. Some of these documents provide the requirements baseline for the components being integrated while others are provided so their contents can be used as guidelines. Doc ID/Number Document Title Revision Date (Supersede s DO-258) 04/07/05 ARINC SPECIFICATION 622-4 Interoperability Requirements for ATS Applications Using ARINC 622 Data Communications (FANS 1/A Interop Standard) ATS Data Link Applications over ACARS Air-Ground Network Rev -4 10/12/01 AEEC/ARINC ARINC SPECIFICATION 620-6 DATALINK GRIOUND SYSTEM AND INTERFACE SPECIFICATION 6 11/15/07 AEEC NAS-IC-40010001 Interfaces Between the Enroute Data Distribution System (EDDS), EAS Air Traffic Management (ATM) Data Distribution System (HADDS)/Store And Forward Application (SAFA) & Their Client Applications (Host Version?) Mapping of Airline Reservation, Ticketing, and Messaging Traffic over IP Manual on VHF Digital Link (VDL) Mode 2 AIR/GROUND CHARACTER-ORIENTED PROTOCOL SPECIFICATION VHF DIGITAL Link (VDL) MODE 2 IMPLEMENTATION PROVISIONS ATS DATA LINK APPLICATIONS OVER Internet Protocol Specification May 1998 IETF ICAO 6 November 2001 06/16/06 4 8/31/05 AEEC 4 10/12/01 AEEC September 1981 IETF RTCA DO-258A RFC 2351 ICAO Doc 9776 ARINC Specification 618-6 ARINC Specification 631-4 ARINC Specification 622-4 RFC 791 Systems Integration Description Document Originating Organization RTCA AEEC Applicable Documents • Page 7 of 37 Systems Integration Description Document Doc ID/Number IATA Systems and Communication s Reference, Volume 3, Migration Strategies, Part III NAS-IC-4010001 Version 1.0– August 27, 2012 Document Title Revision Date Type B Application to Application Protocol (BATAP), 3.1 January 1998 System Segment Specification for DTAP FAA Data Communications Trials Automation Platform (DTAP) Concept Document HADDS –Client ICD A June 6, 2012 April 20,2012 End-end DCL Trails Procedure for DTAP Build 1 1.5 Systems Integration Description Document 1.0 C Originating Organization IATA Thales ATM Inc. FAA November FAA 25, 2009 DCIT August 23, 2012 Applicable Documents • Page 8 of 37 Systems Integration Description Document 2 Version 1.0– August 27, 2012 SYSTEMS INTEGRATION APPROACH The DCL Trials system is comprised of a number of major sub-systems, which by way of well-defined standard interfaces, integrate and communicate to form an end-to-end environment providing an infrastructure for the DCL Trials. The system components are described in detail in Section 3. The fully integrated system for the Logon and DCL service will include ground automation platform, the Host ATM (Air Traffic Management) Data Distribution System (HADDS), and the FAA’s Telecommunications Infrastructure (FTI) Operational IP (OPS-IP). The HADDS, a flight data system, uses the OPS-IP for network connectivity between facilities and for ground connectivity with the DCL Trials Communications Service Providers (CSPs). The CSPs provide a ground communication routing mechanism and an air / ground network to reach participating DCL trials aircraft. 2.1 Assumptions The assumptions that provide context for the integration approach are included in this section. These assumptions are subject to change, as certain aspects of the system architecture are still being detailed. Any changes that impact the integration approach will be addressed in future revisions of this document. Following are the current assumptions: 1. The trial system will either interface with the Host Computer or En Route Automation Modernization (ERAM) through HADDS o Depends on the trial site and the system operating in the En Route Center that has jurisdiction over the airport 2. PDC capability will be part of the operational environment during the trials for aircraft that are not participating in the trials 3. DTAP platform o A first DTAP platform will be delivered and validated at the FAA’s WJHTC o A second platform will be delivered to the first trial key site (Memphis Airport) DCP INTEGRATION PLAN SYSTEMS INTEGRATION APPROACH • Page 9 of 37 Systems Integration Description Document 3 Version 1.0– August 27, 2012 SYSTEM DESCRIPTION This section provides an overview of the DCL Trials end-to-end system. Figure 3-1 below presents an end-to-end architecture for the DCL Trials system. Figure 3-1 DCL Trials Architecture 3.1 Overview 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 Data Communications Trials Automation Platform (DTAP) will provide the FAA with the controller user interface, processing and National Airspace System (NAS) connectivity necessary to generate, deliver and track departure clearances utilizing Radio Technical Commission for Aeronautics (RTCA) Special Committee 214 (SC-214) standards to Future Air Navigation Services version 1/A+ (FANS-1/A+) equipped aircraft. The RTCA DO258(A) provides the description of operations of FANS equipped aircraft and ground system. The DTAP will be used in operational towers alongside the current Tower Data Link Services (TDLS) platform, to augment rather than replace the current PDC process. DCP INTEGRATION PLAN SYSTEM DESCRIPTION • Page 10 of 37 Systems Integration Description Document Version 1.0– August 27, 2012 The DTAP will provide the FAA with the controller user interface, processing and NAS connectivity necessary to generate, and deliver departure clearances to FANS equipped aircraft. The aircraft operator provides Flight Plan information to the Air Route Traffic Control Center (ARTCC) associated with the departure airport via the ground-to-ground communications system. The ARTCC automation processes the flight plan providing modifications to conform to established routes. The ARTCC transmits the processed flight plan to the Air Traffic Control Tower (ATCT) via ground-to-ground communications. DTAP automation creates a DCL by presenting to the controller for review, a proposed DCL that was created using flight data from the ARTCC flight data processing system. The controller may modify the DCL with local data and approves the DCL. After controller approval, DTAP makes the DCL available for a flight crew request. Upon approval of the DCL by the controller, the automation system forwards a copy of the DCL to the Airline Operations Center (AOC). The Flight Crew prepares the aircraft for the flight and activates the data link system, by sending an AFN logon via the CSP Network to the ground system. Ground acceptance of the logon and correlation of the logon information with a flight plan initiates a network connection between the aircraft and ground system. After network connection, the Flight Crew requests a departure clearance from the DCL Service automation. The service responds by transmitting a DCL to the aircraft via the CSP network. When changes in tower or en route conditions occur for weather or other reasons, the tower or the ARTCC will amend the clearance information. After amended data is processed, the controller will take action to transmit a revised DCL to the flight crew. 3.2 Systems Descriptions and Interfaces 3.2.1 Overview Interface testing will be performed for the DTAP to ensure connectivity and addressing characteristics are met. DTAP system interfaces will be tested to ensure that it can effectively connect and extract information from the NAS. This includes routing and forwarding testing with failover conditional testing. Interface testing will evaluate the DTAP requirements for the Flight Deck Interface through the CSP and the HADDS. Multiple systems will be utilized in the end-to-end environment during the testing at the WJHTC, including the DTAP, the FTI National Test Bed (FNTB), CSP, HADDS, and FANS1/A Aircraft Avionics. Communication capabilities will be tested to ensure satisfactory performance across relevant systems as shown in Figure 3-1. DCP INTEGRATION PLAN SYSTEM DESCRIPTION • Page 11 of 37 Systems Integration Description Document Version 1.0– August 27, 2012 3.2.2 Data Comm Trials Automation Platform (DTAP) The DTAP provides Departure Clearance messaging from within the selected tower(s) to participating aircraft. The DTAP interfaces with many other parts of the DCL Trials Architecture. At the physical and network layers the DTAP interfaces with FTI to obtain IP network service. The DTAP interfaces with HADDS and the CSP network(s) using FTI. The DTAP interfaces with HADDS to obtain flight plan information. DTAP uses the flight plan information to aid in its creation and revision of departure clearances. The DTAP interfaces with the CSP network(s) through the FTI National Enterprise Security Gateway (NESG). The DTAP uses the CSP interface to exchange messages with aircraft and airline automation systems. These messages are 620 formatted messages using Type B Application to Application Protocol (BATAP) over Mapping Airline Traffic over IP (MATIP). These 620 messages are received by the CSP network, processed and “forwarded” to the appropriate next destination. Figure 3-2 below presents the end-to-end protocol stack view of DTAP, CSP and the avionics system. Figure 3-2 Protocol Stack View DCP INTEGRATION PLAN SYSTEM DESCRIPTION • Page 12 of 37 Systems Integration Description Document Version 1.0– August 27, 2012 3.2.3 HOST The Host Computer System is FAA's key information processing system for its 20 en route centers, which control aircraft in transit over continental United States and during approaches to some airports. It processes radar surveillance data and flight plans, links filed flight plans with actual aircraft flight tracks, provides alerts of projected aircraft separation violations, and processes weather data. The Host provides flight plan information for the DTAP (via HADDS) as part of the FAA’s DCL Trials. 3.2.4 Host ATM Data Distribution System (HADDS) The HADDS provides the interface to DTAP for flight plan information as part of the FAA’s DCL Trials system. ERAM provides the flight plan data to the DTAP system through the HADDS interface. 3.2.5 Tower Data Link Services (TDLS) TDLS is included in the trial to provide services to the Controller independent of any additional automation being added for the Trials program. There is no interface between TDLS and new automation system(s). The TDLS system supports tower-to-AOC message exchanges via data link communications. The clearance received from TDLS by AOC is provided to the aircraft. The TDLS system is comprised of three applications; PDC, the Flight Data Input/Output (FDIO) Emulation and Digital Automatic Terminal Information Service (D-ATIS). The PDC application displays clearances received from the ARTCC. The TDLS operator can append information about departing aircraft at the airport and transmit the clearance using a data link to a participating airline/user computer. Users deliver the final clearance directly to equipped aircraft or to a departure gate printer for distribution to the aircraft not equipped with display capability. FDIO Emulation is an application that displays flight plan data, weather information, and general information messages from the ARTCCs. TDLS operators use the application to obtain flight plan information and input, request, and revise flight plan data via the TDLS processor. 3.2.6 NAS Security Gateway FAA’s FTI provides ground to ground network connectivity using an IP backbone between FAA networked systems. The NESG provides a secure interface between the private FAA DCP INTEGRATION PLAN SYSTEM DESCRIPTION • Page 13 of 37 Systems Integration Description Document Version 1.0– August 27, 2012 network and external systems. For the DCL Trials the external system(s) being connected is/are the CSP networks of ARINC and SITA. 3.2.7 CSP networks The CSP network subsystem(s) provide air/ground connectivity between the FAA’s network and aircraft. This connectivity is in the form of ACARS messaging to transport FANS messages. Ground-to-ground messages between the DTAP and the CSP network(s) are defined in DO-258A, ARINC 622 and ARINC 620. Air-to-ground messages between the CSP network(s) and aircraft are defined in DO-258A, ARINC 622, ARINC 631, and ARINC 618. The CSP network interfaces with aircraft at the physical and network levels. The CSP network interfaces with FTI/Security Gateway at the physical and network layers. The CSP network(s) interface with DTAP to exchange inputs destined for both aircraft and airline automation systems and send outputs received from aircraft and/or airline automation systems. The trials program intends to use multiple means to interface to aircraft at the physical level depending upon aircraft configuration and current capability. • • VHF Digital Link (VDL) Mode 0 – ACARS VHF VDL Mode 2 – VDL Mode 2 or ACARS over AVLC (AOA) At the network layer the air/ground communications protocol is ACARS (ARINC specification 618). More specifically using messages defined in ARINC 622 and RTCA’s DO-258A. 3.2.8 Aircraft Participating aircraft will have messaging capability to support the DCL trials program’s needs. These needs include a Flight Management system (FMS) with FANS communications capability and VHF Digital Link (VDL) (Mode 0 or Mode 2) capable radios and Communications Management Units (CMUs). 3.2.9 Airline automation The Airline automation system will receive a separate “dispatch message” for each departure clearance from the DTAP using an ARINC 620 formatted message. This “dispatch message” will be a separately created and sent message based upon the contents of the DO258(A) formatted message sent to the aircraft and other flight plan information available to DCP INTEGRATION PLAN SYSTEM DESCRIPTION • Page 14 of 37 Systems Integration Description Document Version 1.0– August 27, 2012 the DTAP. The airline automation system must acknowledge the “dispatch message” with an acknowledgement message. The acknowledgement has a field for gate information for the associated flight that may optionally be filled out by the airline automation. 3.2.10 Airline Operations Center (AOC) AOCs are responsible for airline operations and related interactions with the FAA. The AOCs communicate with the FAA to ensure that initiation, continuation, diversion or termination of flights for safety and efficiency reasons are also compliant with other regulations with which the airlines need to comply. DCP INTEGRATION PLAN SYSTEM DESCRIPTION • Page 15 of 37 Systems Integration Description Document Version 1.0– August 27, 2012 4 INTEGRATION AND SEQUENCE DATA FLOW 4.1 Integration Approach Technical integration for the DCL Trials system is addressed in two parts: 1) GroundGround System Integration, and 2) Air-Ground System Integration. Such integration approaches are further divided into “system threads” based on major ground-ground and air-ground system components in Section 4.2. The architecture that will be utilized to conduct end-to-end system testing of the DTAP system at the WJHTC in Atlantic City, NJ is depicted below in Figure 4-1. Figure 4-1 DCL Trials End-to-End System Test Architecture 4.1.1 Ground-Ground Integration To enable exchange of flight, logon and session information between end system components, the flight data hosted on HADDS, the AFN capability hosted on DTAP, and the CDPLC DCL capability hosted on DTAP will utilize the following integrated elements as a means of ground communications across the interfaces: • • • DTAP AFN Application DTAP CPDLC Application HADDS DCP INTEGRATION PLAN INTEGRATION AND SEQUENCE DATA FLOW • Page 16 of 37 Systems Integration Description Document • Version 1.0– August 27, 2012 NESG Figure 4-2 shows the approach for integrating the ground-ground system elements from a system’s threads point of view. The focus of this integration step will be on ensuring DTAP is able to receive and process flight data from HADDS, and ensuring that the DTAP can communicate with Front End Processor proxy located in the external DMZ of the NESG. Figure 4-2 Ground-Ground Integration 4.1.2 Air-Ground Integration To enable exchange of end-to-end AFN logon and CPDLC communication between end system components, the following integrated elements (across the ground-ground and airground interfaces) allow for the end-to-end service for the DCL Trials system: • • • • • • • • DTAP AFN Application DTAP CPDLC Application HADDS NESG CSP Aircraft AFN Application Aircraft CPDLC Application AOC Figure 4-3 shows the approach for integrating the air-ground system elements from a system’s threads point of view. The focus of this integration step will be to ensure that the DTAP Data Comm applications; AFN and CPDLC; can communicate with the Aircraft Data Comm applications; AFN and CPDLC respectively; through the CSP’s air/ground network. DCP INTEGRATION PLAN INTEGRATION AND SEQUENCE DATA FLOW • Page 17 of 37 Systems Integration Description Document Version 1.0– August 27, 2012 Figure 4-3 Air-Ground Integration DCP INTEGRATION PLAN INTEGRATION AND SEQUENCE DATA FLOW • Page 18 of 37 Systems Integration Description Document 5 Version 1.0– August 27, 2012 End-to-End – SEQUENCE DATA FLOW This section identifies the logical sequence of data flows within the end-to-end environment. Such sequences account for the ground-ground and air-ground message flow for end-to-end communications between ATC controller and Pilot. Prior to actual sequence data flows, below you will find relevant information about “Flight Plan Prior to Departure Time”, “ Parameters for FP-to-Logon Correlation”, and a “Timeline: Pre-conditions”. The sequence flow diagrams are shown on Figures 5-3, 5-4 and 5-5 respectively. 5.1 FLIGHT PLAN PRIOR TO DEPARTURE TIME • Flight Plans (FPs) are filed by FOC/AOC approximately 45 minutes prior to proposed departure time (P-Time) o Flight plan must have the Flight Identification (FLID), the departure airport, and registration number/Tail number o For flights that will participate in the DCL trials, airlines shall include “FRC DCL” in the first 22 characters of the Remarks field of the FP o FPs are validated, and if found valid they are assigned Computer Identification (CID) o Once stored, FPs are distributed to HADDS/DTAP; however FPs are distributed to TDLS when tower strip is printed o FOC/AOC will receive a response for filed FPs (Accepted / Rejected ) based on key fields such as Aircraft ID o FPs can be updated or deleted o Flight Plans are either Proposed (Pending) or Active (when aircraft takes off and is detected by the radars) o Multiple proposed FPs per flight can exist; and are resolved by a controller Figure 5-1 below shows the parameters that are used for FP-to-logon correlation. The FP is filed by the AOC/FOC and the logon information is obtained from the aircraft. Figure 5-1 Parameters for FP-to-Logon Correlation DCP INTEGRATION PLAN End-to-End – SEQUENCE DATA FLOW • Page 19 of 37 Systems Integration Description Document Version 1.0– August 27, 2012 5.2 Timeline: Pre-Conditions The timeline below shows the sequence of events and the major events that are involved for successful deliverance of departure clearance. In Figure 5-2, the purple bubbles on the right show the major events, the lavender bars are occurrences corresponding to the bubbles, the purple triangles indicate time barriers and the arrows emanating from one occurrence to another show flow of events. • • • Time progression is assumed to be from left to right The location of the purple bubbles is irrelevant to the flow Dependences are indicated by the curved arrows o For example the first curved arrow starts from the bar that corresponds to the “FP is Filed” and ends at the bar corresponding to “FP is Forwarded to DTAP”; this means the first event is a predecessor for the later event and the second event cannot happen unless the first event occurs Figure 5-2 Time Line: Pre-Conditions DCP INTEGRATION PLAN End-to-End – SEQUENCE DATA FLOW • Page 20 of 37 Systems Integration Description Document Version 1.0– August 27, 2012 5.3 Logon and Session Establishment At the appropriate time, and while still at the gate, the aircrew logs-on to DTAP using the local DTAP Tower address. This can be done any time; however a logon will be rejected unless the aircraft logs on after the airline has filed the FP with the FAA. DTAP will accept valid logons, provided that logon can be correlated with an FP containing the same registration number/Tail number and Flight Identification (FLID). In addition to the two items the FP must contain “FRC DCL” in the Remarks field to receive DCL. Assuming DCL has been created by DTAP and the controller has edited and approved the DCL, once DTAP accepts the logon, it will attempt to establish a CPDLC connection with aircraft. Note: The inclusion of the FRC DCL as part of correlation is an outstanding issue in the End-to-End. Figure 5-3 AFN Logon & Session Establishment 5.4 Departure Clearance (DCL) At the appropriate time, and after establishment of CPDLC connection, the aircrew requests DCL. DTAP then delivers the DCL to the aircraft using FANS-1/A message elements. The pilot responds with a WILCO (this flows assume normal condition). In addition, DTAP sends “dispatch messages” to the AOC/FOC. DCP INTEGRATION PLAN End-to-End – SEQUENCE DATA FLOW • Page 21 of 37 Systems Integration Description Document Version 1.0– August 27, 2012 Figure 5-4 Departure Clearance- WILCO After establishment of CPDLC connection, the aircrew requests DCL. Figure 5-5 shows a scenario where DCL request came before the approval of DCL. In this case DTAP responds with STANDBY and then delivers the DCL when ready. This scenario is considered to be a normal condition. Figure 5-5 Departure Clearance- STANDBY DCP INTEGRATION PLAN End-to-End – SEQUENCE DATA FLOW • Page 22 of 37 Systems Integration Description Document Version 1.0– August 27, 2012 5.5 Revised Departure Clearance (Revised DCL) One or more Revised DCLs may be sent by ATC prior to aircraft takeoff. These clearances will contain some or all of the same information as the initial Departure clearance. Figure 5-6 Revised Departure Clearance 5.6 Session Termination There are multiple automatic or manual triggers for session termination such as when flight departs, the flight plan times out, a controller manually terminates the session, or the system automatically terminates the session as a result of error processing. This section addresses session termination due to flight departure. After a parameter/ adapted amount of time after flight departure, DTAP receives flight departure indication. DTAP then sends CPDLC_END Request to the avionics. When DTAP receives CPDLC_END Response, it terminates the session and indicates to the controller that session has terminated. DCP INTEGRATION PLAN End-to-End – SEQUENCE DATA FLOW • Page 23 of 37 Systems Integration Description Document Version 1.0– August 27, 2012 Figure 5-7 Session Termination DCP INTEGRATION PLAN End-to-End – SEQUENCE DATA FLOW • Page 24 of 37 Systems Integration Description Document 6 Version 1.0– August 27, 2012 DISPATCH MESSAGE FORMATS This Section describes the initial and revised dispatch messages to be provided by the tower automation system to the airline host (or proxy). The format of the dispatch messages, as shown in Table 6-1, 6-2 and 6-8 are intended to be similar to the existing PDC messages the airline systems receive from TDLS today. The formatting is intended to be as close as possible to the formatting used by TDLS today to minimize the costs associated with updating airline automation systems to receive process and respond to the dispatch message set. This formatting extends to the concept of including such elements as the CID, equipment and departure time information that are in today’s PDC sent by TDLS but not included in a FANS DCL. Table 6-2 and Table 6-3 include “Notes” and “Outstanding Issues” as related to the CC formats; while Table 6-4 illustrates Clearance Fields and Table 6-5 shows the Revised Fields. Table 6-6 provides an example of the CC message. The last two tables, Table 6-8 and Table 6-9, provide the CC Acknowledgment Message and the Field Descriptions. Table 6-1 Initial Dispatch Message (CC) Message Format {field values in brackets. Field identifiers marked with “#” from table below, notes marked with *} ^AQU {IATA address TO } . {IATA address FROM} {DDHHMM} ^BCCI { Sequence Number} DCL DISPATCH MESSAGE – NOT AN ATC CLEARANCE {Flight ID *A} {field #1} {Equipment *B} P{Departure time *C} {Computer Identifier *D} {field #19} {Route Information *E} {Route Information *E} {Route Information *E} {Free Text *F} {Free Text *F} {Free Text *F} {Free Text *F} {Free Text *F} {Free Text *F} {Free Text Additional *G} {Free Text Additional *G} DCP INTEGRATION PLAN DISPATCH MESSAGE FORMATS • Page 25 of 37 Systems Integration Description Document Version 1.0– August 27, 2012 {field values in brackets. Field identifiers marked with “#” from table below, notes marked with *} {Free Text Additional *G} ^C Table 6-2 contains the format for the Revised Dispatch Message. The first 7 lines (from Start of Message through Computer Identifier) are required in each Revised Dispatch Message. The field (Revised *H *H} contains the list of fields that are included in the rest of the message. The changed portion of the associated FANS DCL message will be included in the remainder of the Revised Dispatch Message in the same order as in an Initial Dispatch Message. This is indicated below as Route Information, Free Text or Free Text Additional. Table 6-2 Revised Dispatch Message (RC) message format {field values in brackets. Field identifiers marked with “#” from table below} ^AQU {IATA address TO } . {IATA address FROM} {DDHHMM} ^BCCR { Sequence Number} DCL DISPATCH MESSAGE – NOT AN ATC CLEARANCE {Flight ID *A} {Field 1} {REVISED *H *H} {Equipment *B} P{Departure time *C} {Computer Identifier *D} {field #19} {Route Information *E} {Route Information *E} {Route Information *E} {Free Text *F} {Free Text *F} {Free Text *F} {Free Text *F} {Free Text *F} {Free Text *F} {Free Text Additional *G} {Free Text Additional *G} {Free Text Additional *G} ^C DCP INTEGRATION PLAN DISPATCH MESSAGE FORMATS • Page 26 of 37 Systems Integration Description Document Version 1.0– August 27, 2012 Table 6-3 Notes Notes A: Flight ID is not in the FANS uplink message, it will be derived from other DTAP information. B: Equipment type is not in the FANS message; it will be derived from other DTAP information. C: Departure time is not in the FANS message; it will be derived from other DTAP or airline information. D: Computer Identifier is not in the FANS message; it will be derived from other DTAP information. E: Route information consists of fields #2, #3, #4, #5, #6, #7, #8, #11, #12 as described in table 6-4. F: Free text consists of fields #10, #13, #14, 15, #16 and #17 as described in Table 6-4. G: Free text added consists of fields #18, #20. This field includes all fields that are not in the PDC message today including any additional free text not already specified. H: For each revised element include a REVISED XXX indication. See Table 6-5 for the possible revision reasons. Table 6-4 Clearance Fields Field number 1 2 3 4 5 6 7 8 9 Field description Example values AirportDeparture AirportDestination RunwayDeparture ProcedureDeparture RunwayArrival ProcedureApproach ProcedureArrival AirwayIntercept RouteInformationSequence KMEM KORD CRSON1.HUMMS MZZ.ROYKO3 0 PublishedIdentifier DHART /N01W05 1 LatitudeLongitude N45000W120456 2 PlacebearingPlacebearing N45000W120456/359T 3 PlacebearingDistance N45000W120456/359T/11NM J180 N45000W120456 DCP INTEGRATION PLAN DISPATCH MESSAGE FORMATS • Page 27 of 37 Systems Integration Description Document Field number Version 1.0– August 27, 2012 Field description Example values 4 AirwayIdentifier 10 5 TrackDetail RouteInformationAdditional ATWalongtrackwaypointssequence J180 +2NM ReportingPoints ??? InterceptCourseFromSequence PETTY/359T HoldAtWaypointsSequence ??? WaypointSpeedAndAlitutudeSequence PETTY/400K 11 12 13 14 15 16 17 18 19 RTArequiredTimeArrivalSequence Then As Filed Route As Filed Expect Level [level] Departure Speed [speed] Departure Heading [heading] EDCT [text] Special Instruction [freetext] Departure Frequency [frequency] UM19 Maintain Altitude [altitude] THEN AS FILED CLEARED AS FILED EXPECT LEVEL FL390 DEPARTURE SPEED 250K DEPARTURE HEADING 010 EDCT 1525 {freetext} FREQ 124.650 MAINT 5000FT Table 6-5 Revised Fields Tag Meaning Example RTE Route Information, minus any departure procedure HUMMS PXV BIGXX MZZ DP Departure procedure CRSON1.HUMMS EDCT Estimated departure clearance time EDCT 1525 EXPALT Expected altitude, this field can have more information based on local procedures FL390 ALT Initial Altitude 5000FT DEPFREQ Departure frequency FREQ 124.150 DCP INTEGRATION PLAN DISPATCH MESSAGE FORMATS • Page 28 of 37 Systems Integration Description Document Version 1.0– August 27, 2012 Table 6-6 Dispatch Message Example Line 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 Text ^AQU ANPOCFX .FMCBOCR 081251 ^BCCI 001 DCL DISPATCH MESSAGE – NOT AN ATC CLEARANCE FDX123 KMEM H/MD11/E P1330 A46 320 KMEM --- CHLDR1.ANSWA --- --TXMEX1 KORD ANSWA DHART J180 SWB EXPECT LEVEL FL390 WI 10MIN AFT DEP EDCT 1525 FREQ 124.650 MAINT 5000FT ^C Notes Destination Automation System address SMI Sequence number and notification Flight ID and departure airport Equipment and departure time Computer code and altitude Departure airport, placeholder for departure runway, departure procedure, placeholder for arrival runway, placeholder for approach procedure, arrival procedure For this field three ‘-‘ characters are used for placeholders. AirportDestination Route Information Free text Free text Free Text additional Free Text additional ETX Table 6-7 Revised Dispatch Message Example Line Text Notes 1 ^AQU ANPOCFX Destination 2 . FMCBOCR 081251 Automation System address 3 ^BCCR SMI 4 001 DCL DISPATCH MESSAGE – NOT AN ATC CLEARANCE Sequence number and notification 5 FDX123 KMEM REVISED RTE DP DEPFREQ Flight ID, departure airport and revision marking 6 A47 Computer code 7 KMEM --- CRSON1.HUMMS --- --MZZ.ROYKO3 Departure airport, placeholder for departure runway, departure DCP INTEGRATION PLAN DISPATCH MESSAGE FORMATS • Page 29 of 37 Systems Integration Description Document Line Text Version 1.0– August 27, 2012 Notes procedure, placeholder for arrival runway, placeholder for approach procedure, arrival procedure For this field three ‘-‘ characters are used for placeholders. 8 9 KORD HUMMS PXV BIGXX MZZ AirportDestination Route Information 10 EDCT 1525 Free text 11 12 13 FREQ 124.150 MAINT 5000FT ^C Free Text additional Free Text additional ETX Table 6-8 Dispatch Message Acknowledgement Message {field values in brackets. Field identifiers marked with “#” from table below} ^AQU {IATA address TO } . {IATA address FROM} {DDHHMM} ^BCCA {Flight ID *A} { Sequence Number} {Tail Number} {Departure time} {Gate Assignment} ^C Table 6-9 Dispatch Message Acknowledgement Field Descriptions Field name {IATA address TO } . {IATA address FROM} {DDHHMM} Flight ID Sequence Number {Tail Number} {Departure time } Gate Assignment DCP INTEGRATION PLAN Field Explanation Address of DTAP at destination tower Address of airline host sending the ACK Time message was sent to DTAP 2 or 3-char customer ID plus numerals This should match the sequence number of the CCI or CCR that this acknowledges If known, default if unknown is single period “.” Format is 2 characters of hours followed by 2 characters of minutes (HHMM) Format is GXXX, default if gate information is not available is “G” DISPATCH MESSAGE FORMATS • Page 30 of 37 Systems Integration Description Document DCP INTEGRATION PLAN Version 1.0– August 27, 2012 DISPATCH MESSAGE FORMATS • Page 31 of 37 Systems Integration Description Document 7 Version 1.0– August 27, 2012 TEST PROGRAM DESCRIPTION This section provides a summary of the Test Program, focusing on the test and evaluation approach, summary of test requirements, activities leading to test, test environment, test location, test tools, and an overview of the types of testing to be conducted in order to evaluate the DTAP requirements laid out in the Program Requirements for DTAP. 7.1 Approach and Concept The objective of the test activities is to evaluate the operational effectiveness and suitability of the DTAP system using a systematic approach, under simulated operational end-to-end conditions in the lab environment, including “aircraft in the loop” conditions that are representative of those found between Air Traffic Control sites and aircraft avionics in the field. Hardware and software will be evaluated. All findings will be submitted in a test report that will provide recommendations of acceptance or non-acceptance of the DTAP system. A preliminary test report will be delivered following the test conduct at the WJHTC, with a final report being delivered after SAT at each DCL Trials location. 7.1.1 Evaluation Approach The evaluation will be based on the degree to which the DTAP system satisfies the program requirements for DTAP under operationally realistic conditions. The evaluation and assessment of the DTAP will include a period of test procedure checkout and dry run testing before the formal test. This allows test personnel the opportunity to refine test procedures and to develop familiarization with the end-to-end system. 7.1.2 Performance Thresholds Relevant thresholds for the testing are included in the individual test procedures as required. 7.1.3 Activities Leading To Test The following activities must be accomplished prior to start of the formal DTAP test at the WJHTC: • • • • Completion of DTAP contractor Developmental Testing (DT) Development of the Test Plan Development of the Test Procedures Conduct of Test dry runs DCP INTEGRATION PLAN TEST PROGRAM DESCRIPTION • Page 32 of 37 Systems Integration Description Document Version 1.0– August 27, 2012 7.2 Test Environment To test the DTAP requirements, the WJHTC will allocate the necessary environment to perform the test procedures. The initial test environment will be a self-contained environment in the Data Comm Prototype and Integration Lab, and will consist of the DTAP and a HADDS stand-alone system. This will provide system functionality to test application and interface DTAP requirements in the lab bench environment. The final test environment will be an end-to-end system that will closely mimic the operational field environment, and will provide an end-to-end system to run the test procedures that will closely mimic the real field DCL Trials architecture. This end-to-end system test environment will consist of the DTAP in the Data Comm Prototype and Integration Lab, FTI National Test Bed (FNTB), HADDS, DCP CSPs, and FANS equipped aircraft avionics. Refer to Figure 4-1 for the test environment architecture. SAT will be performed at each DCL Trials location prior to the start of the Trials at that site, and will utilize the trials architecture environment shown in Figure 3-1. 7.2.1 Test Location End-to-end system testing will be conducted at the FAA WJHTC at the Atlantic City International Airport in Atlantic City, NJ. SAT will take place at each DCL Trials location prior to the start of that Trial period. FedEx, United Airlines, and Delta Airlines have offered FANS equipped aircraft at field locations to support testing. 7.3 Test and Analysis Tools Test tools are meant to be utilized in a lab environment in an effort to emulate specific system components in the absence of real software and hardware end-to-end system elements. For the laboratory environment test phase, such test tools are categorized as shown: • • • • • FANS Avionics Tool Set HADDS in a box TESTOPIA BUGZILLA FNTB DCP INTEGRATION PLAN TEST PROGRAM DESCRIPTION • Page 33 of 37 Systems Integration Description Document Version 1.0– August 27, 2012 Verification that the test tools perform properly with no anomalies and/or discrepancies will be performed as part of the environment. 7.4 Test and Evaluation Descriptions The test program for end-to-end system testing at the WJHTC encompasses four main areas of formal test as listed below: 1. 2. 3. 4. DTAP Functionality Data analysis on all of the DTAP functionality to verify their pass/fail status Document any Program Trouble Reports (PTRs) Flight Deck Avionics 7.4.1 DCL Trials End-to-End System Testing The William J. Hughes Tech Center (WJHTC) will jointly develop individual test procedures with the DCL Trials team to be executed at the WJHTC Data Comm Lab, in accordance with the test descriptions for the DTAP functionality requirements and must successfully verify that the DTAP meets or exceeds all requirements, as documented in the approved VRTM. This testing at the WJHTC will include application interface testing, CSP interface testing, and end-to-end system testing. Application interface level testing will be performed, which includes the DTAP application communicating and interfacing with ground-ground components as part of the end-to-end chain. CSP interface testing will be performed with the DTAP system ground infrastructure to ensure connectivity and addressing characteristics are met. This also includes routing and forwarding testing with failover conditional testing. End-to-end lab testing will be performed and will include testing with FANS-1/A avionics with “aircraft in the loop” scenarios. This end-to-end aircraft acceptance testing will be performed to validate and verify the proper function and operation of the DTAP. SAT will be conducted at each DCL Trials location prior to the beginning of the Trials. SAT has two parts: Functional, which is a subset of OT functional, and Operational, which is a mix of a subset of OT Ops testing and site specific testing. Test procedures will be utilized. 7.4.1.1 Test Objectives The objective of the Test will be to evaluate whether the DTAP requirements were implemented as designed and operationally suitable as outlined in the FAA Data Communications Trials Automation Platform (DTAP) Concept Document and documented in the VRTM. DCP INTEGRATION PLAN TEST PROGRAM DESCRIPTION • Page 34 of 37 Systems Integration Description Document Version 1.0– August 27, 2012 Once the formal test has been completed, data analysis will be conducted for those requirements assigned as Verify by Test. 7.4.1.2 Test Criteria The evaluation/success criteria for the DTAP functionality are found in the individual test procedures. 7.5 Test Approach The test approach used for each DTAP Functionality is listed in the individual test case/procedures. They include descriptions of specific tasks, activities, test conditions, scenarios and operational situations. The Test Process is depicted in Figure 7-1 below. Figure 7-1 DCL Trials End-to-End Test Process DCP INTEGRATION PLAN TEST PROGRAM DESCRIPTION • Page 35 of 37 Systems Integration Description Document Version 1.0– August 27, 2012 APPENDIX D - Glossary Acronym ACARS AOC AFN ARTCC AS ATC ATCT ATM ATN CC CPDLC CSP D-ATIS Data Comm DCIT DCL DCP DT DTAP ERAM FAA FANS FANS-1/A+ FDIO FDP FLID FMS FNTB FO FOC FP FTI HADDS ICAO ICD IP IRD MOE MOP MOS NAS NESG DCP INTEGRATION PLAN Description Aircraft Communications Addressing and Reporting System Airline Operations Center/Aeronautical Operational Control ATS Facilities Notifications Air Route Traffic Control Center Applications Systems Air Traffic Control Air Traffic Control Tower Air Traffic Management Aeronautical Telecommunication Network Dispatch Message Controller Pilot Data Link Communications Communications Service Provider Digital Automatic Terminal Information Service Data Communications Data Comm Integration Team Departure Clearance Data Comm Program Developmental Testing Data Comm Trials Automation Platform En Route Automation Modernization Federal Aviation Administration’s Future Air Navigation Services FANS Version 1+/A Flight Data Input/Output Flight Data Processing Flight Identification Flight Management System FTI National Test Bed Flight Object Flight Operations Center Flight Plan FAA Telecommunications Infrastructure Host ATM Data Distribution System International Civil Aviation Organization Interface Control Document Internet Protocol Interface Requirements Document Measures of Effectiveness Measures of Performance Measures of Suitability National Airspace System National Enterprise Security Gateway APPENDIX D - Glossary • Page 36 of 37 Systems Integration Description Document Acronym OPS PDC PTR RTCA SC-214 TDLS VDL VRTM VHF WJHTC DCP INTEGRATION PLAN Version 1.0– August 27, 2012 Description Operations Pre-Departure Clearance Program Trouble Report RTCA, Inc. (formerly Radio Technical Commission for Aeronautics) Special Committee 214 Tower Data Link Services VHF Digital Link Verification Requirements Traceability Matrix Very High Frequency William J. Hughes Technical Center APPENDIX D - Glossary • Page 37 of 37