ATS Function (Section 2 of SPR) Progress Report

1. ATS Function(Section 2 of SPR)Progress Report Presented to: RTCA SC-214 / EUROCAE WG-78 By: Thierry Lelievre (ALTRAN)Jérôme Condis (Airbus)Thomas Mustach (FAA) Date: April 11th – 15th, 2011

2. Overview • ATS Function (Section 2) and Environmental Characteristics (Section 3) significantly changed • ATS Functions previously defined was incomplete and too vague (i.e. notional) • Change to Section 2/3 of SPR recognized to be necessary to perform Oceanic/Continental integration and regulators to use the SPR as an acceptable means of compliance for aircraft type design approval, operational authorizations, and safety oversight • CSG agreed in Atlantic City, Jan 10-14, 2011 mtg to new approach • ATS Function defined by “Operational Capability” in lieu of the notional approach • Each ATS Function: • Identify supporting data link application(s) and if the application is required or may be used to achieve the ATS Function. • Specify Data Communications capabilities necessary to support the ATS Function (e.g. enabling criteria for certification). • Specify the assumptions (i.e. Non-Data Comm enablers) also necessary to support the ATS Function. Any assumption (i.e. Environmental Characteristic) that is used as the basis for assessing and establishing operational, safety, performance requirements.

3. Objective • Revise, as necessary, Safety/Performance assessments relative to the functional capability of achieving the ATS Function. Current assessment: • Generally done at the application level vs. ATS Function level • Worse case service safety assessment applied to entire application • Multiple RCP criteria to support individual services • Safety/Performance Requirements traceable to the supported ATS Function • SPR that will support certification • Application, Performance, and Interop designators are currently used to identify aircraft equipage and capability. Obviously the Interop designator doesn’t come into play within the scope of our SPR. • FAA intends to use the SPR and Interop as a means of compliance within AC 20-140 for different aircraft implementations. A need to establish designators that will identify applicable requirements for each of these implementations must be established. Note: Need to ensure Interop and Performance designators are sufficient to differentiate aircraft equipment, capabilities, and flight crew qualifications. For instance, • Service Requirements (enabler in 2nd column) • CPDLC/FMS integration (enabler in 2nd column) • Each aircraft implementation and its support of ATS Functions

4. Section 2 (new) outline 2.1 Overview 2.2 Operational requirements related to ATS Functions Establishes link with high-level Operational Requirements from ICAO material 2.3 Environmental Types and Characteristics Describes APT, TMA, ENR-1 and ENR-2 airspaces 2.4 Description of ATS Functions 2.4.1 Integration of data link applications with the aircraft’s Flight Management System Introduce FMS integration capability for CPDLC and ADS-C 2.4.2 ATS Function Table Provides list of ATS Functions with DataComm enablers and external assumptions for each of the ATS Functions 2.5 Provision and Use Reused from previous SPR version 2.6 Flight Plan Reused from previous SPR version

5. Overview - Nineteen ATS Functions considered within our SPR

6. Sample 1 – DataComm Optional

7. Sample 2 – DataComm Required

8. ATS Functions Overview

9. ATS Functions Overview

10. Outstanding work / Open points • Define RCP requirements • Based on ATS Function assessment • Consistent with RCP-type families • RCP template • Opportunity to merge some rows / ATS Functions according to the common DataComm enablers

11. Plenary requested to… • Receive at this meeting the ATS Function document for incorporation in SPR (i.e. replace existing Section 2&3). • Editorial question with regards to Section 3 deletion to be addressed by CSG • Later on, manage this section as part of the global SPR document management.