Final Project Report Document information Project Title Project Number Project Manager Deliverable Name Deliverable ID Transversal Consistency of Business/Mission Trajectory Requirements (across WPs) P11.01.01 Airbus S.A.S Final Project Report D10 Edition 01.00.00 Template Version 03.00.04 Task contributors Airbus, Airbus Defence & Space, Lufthansa Systems, Sabre Airline Solutions, Honeywelll Abstract The purpose of the project P11.01.01 was to to be able to deliver the defined P11.01.02 ( FOC/WOC Operational Requirements Definition) The project P11.01.01 was in charge of the consistency of Business/Mission trajectory concept throughout the SESAR programme. In the frame of this activity, P11.01.01 defined the concept regarding FOC/WOC through : - the capture of the FOC part of operational requirements for other WPs (7, B, 6, 4, 5, 9, 8) - the description of operational processes from AU standpoint - the analysis of the gap against already developed requirements within the SESAR programme when required
P11.01.01 also contributed to support the standardisation work in external bodies, such as ICAO ATM-RPP. The main method used was "Expert group analysis" through the involvement of Airspace Users experts on both sides civil and military in workshops. 2 of 17
Authoring & Approval Prepared By - Authors of the document. Name & Company Position & Title Date Régis BATTEUX/AIRBUS P11.01.01 & 02 Project Manager 15/09/2016 Reviewed By - Reviewers internal to the project. Name & Company Position & Title Date Daniel CHIESA / Airbus WP 11.01 Leader 23/09/2016 Olaf BELZER / SABRE Airline Solutions P11.01.04 Project Manager 20/09/2016 Marcus HANTSCHKE / Lufthansa Systems WP 11.01 Member 22/09/2016 Joseph ABO-ROMMAN / Airbus P11.01.05 Project Manager 26/09/2016 Klaus Dieter HERMANN / Airbus DS Contribution Manager WP11.01 for ADS WOC domain 23/09/2016 Matej PAPP / Honeywell Contribution Manager WP11.01 for Honeywell 23/09/2016 Reviewed By - Other SESAR projects, Airspace Users, staff association, military, Industrial Support, other organisations. Name & Company Position & Title Date <Name / Company> <Position / Title> <DD/MM/YYYY> Approved for submission to the SJU By - Representatives of the company involved in the project. Name & Company Position & Title Date Régis BATTEUX/AIRBUS P11.01.01 & 02 Project Manager 27/09/2016 Daniel CHIESA / AIRBUS WP11.01 Leader 27/09/2016 Rejected By - Representatives of the company involved in the project. Name & Company Position & Title Date <Name / Company> <Position / Title> <DD/MM/YYYY> Rational for rejection None. Document History Edition Date Status Author Justification 00.00.01 09/09/2016 Draft Régis BATTEUX Initial version 00.00.01 16/09/2016 Draft Régis BATTEUX Internal Fly4D review 00.00.02 23/09/2016 Draft Régis BATTEUX Internal Fly4D review with comments integrated 01.00.00 27/09/2016 Final Régis BATTEUX SJU Release Intellectual Property Rights (foreground) This deliverable consists of SJU foreground. 3 of 17
Acronyms Acronym AFUA AIM ARES ASM ATC ATM ATMS AU BMT BT CARATS CDM CMAC CONOPS DOD DS EFPL E-OCVM FOC FPL ICAO INTEROP irmt ismt MEPS Definition Advanced Flexible Use of Airspace Aeronautical Information Management Airspace Reservation/Restriction Airspace Management Air Traffic Control Air Traffic Management Air Traffic Management System Airspace User Business/Mission Trajectory Business Trajectory Collaborative Actions for Renovation of Air Traffic Systems Collaborative Decision Making Civil-Military ATM Coordination Concept of Operations Detailed Operational Description Data Set Extended Flight Plan European Operational Concept Validation Methodology Flight Operations Centre Flight Plan International Civil Aviation Organization Interoperability Requirements Initial Reference Mission Trajectory Initial Shared Mission Trajectory Military Engagement Plan for SESAR 4 of 17
MET NM NextGen OAT OFA OI OSED PCG RBT RMT RPP SESAR SESAR Programme SJU SPR SWIM TMA TS TTO UDPP VPA WOC WP Meteorology Network Manager Next Generation Air Transportation System Operational Air Traffic Operational Focus Area Operational Improvement or Operating Index Operational Service and Environment Definition Programme Control Group Reference Business Trajectory Reference Mission Trajectory Requirements and Performance Panel Single European Sky ATM Research Programme The programme which defines the Research and Development activities and Projects for the SJU. SESAR Joint Undertaking (Agency of the European Commission) Safety and Performance Requirements System Wide Information Management Terminal Manoeuvring Area Technical Specification Target Time Over User Driven Prioritisation Process Variable Profile Area Wing Operations Centre Work Package 5 of 17
1 Project Overview The purpose of the project P11.01.01 was to to be able to deliver the defined P11.01.02 (FOC/WOC Operational Requirements Definition) The project P11.01.01 was in charge of the consistency of Business/Mission trajectory concept throughout the SESAR programme. In the frame of this activity, P11.01.01 defined the concept regarding FOC/WOC through: - The capture of the FOC part of operational requirements for other WPs (7, B, 6, 4, 5, 9, 8) - The description of operational processes form AU standpoint - The analysis of the gap against already developed requirements within the SESAR programme when required P11.01.01 also contributed to support the standardisation work in external bodies. Through proactive attendance of ICAO ATM-RPP panel, coordination with other external ATM research projects (i.e NextGen, CARATS) was granted. 1.1 Project progress and contribution to the Master Plan The main method used was "Expert group analysis" through the involvement of Airspace Users experts on both sides civil and military (State Airspace Users) in workshops. One civil Airspace User workshop per Quarter was organized by P11.01.01 & 02 to gather operational requirements and to consolidate operational use cases. In order to optimize the research activity related to the FOC, a unique Airspace User community was created for P11.01.01 and AU community includes both Civil and State Airspace Users: Civil Airspace Users are: Scheduled Mainline airlines Regional airlines Low Fare airlines Charter/Leisure airlines Cargo airlines Business Aviation General Aviation. State Airspace Users are: Operators of Large aircraft (military transport type aircraft) Operators of Fighter aircraft Operators of Light aircraft (light civil and military aircraft, helicopters, paramilitary aircraft) Different types of RPAS (Remotely Piloted Air Systems) During all activities performed by P11.01.01, the work has been performed with the involvement of several AUs, including AUs of other SESAR WPs communities. 6 of 17
Specifically for P11.01.01, as the FOC point of view was partially represented at the beginning of SESAR, it was really key to introduce the FOC role in the definition of basic concepts. In addition, the P11.01.01 contributed to transverse meetings to consolidate overall SESAR concepts (CONOPS and Transition CONOPS meetings organized by B04.02). P11.01.01 also contributed to support the standardisation work in external bodies. Through proactive attendance of ICAO ATM-RPP panel, coordination with other external ATM research projects (i.e NextGen, CARATS) was granted. In the frame of the projects P11.01.01, the methods and tools for the management of requirements are based on well-known international best practices in system engineering applied within SESAR programme (i.e E-OCVM) : Requirement matrix formalized through textual fields for links to other system engineering objects (requirement, process, service, Operational Focus Area ) A Revised process has been proposed and agreed between WP11.01, SJU and ECTRL in February 2014 for civil activities (FOC side). This 'validation oriented' process had a major impact on the project P11.01.01. The main impact for P11.01.01 was to postpone the DOD / OSED update to the end of SESAR Programme. Consequently, the full traceability to system level could not be provided anymore. Finally, decision to not update the FOC / WOC DODs was taken at Gate #5 (October 2015). The WOC part of P11.01.01 was performed as planned. The DOD was developed together with EUROCONTROL/CMAC and the MEPS. Even though the update of the DOD was cancelled, the DOD is valuable source of information for the description of the operational workflow. Major parts of the DOD are referenced in the OSED and are the baseline for the further work. Here below the table listing the OI Steps that the project P11.01.01 has contributed to. As far as possible, the reference Data Set is the DS16 (Integrated Roadmap Dataset 16) in order to be aligned with the most recent SESAR Dataset of OIs. There are only three OIs among 19 that were described using Dataset14. Each time there is an Operational Improvement linked to a SESAR solution, it has been mentioned in the table. The maturity level at project end for OI steps is retrieved from P11.01.05, leading V&V activities. Code Name Project contribution Maturity at project start Maturity at project end AOM-0202-A Automated Support for strategic, pre-tactical and tactical Civil- Military Coordination in Airspace Management (ASM). Linked to Solution #31 V3 reach the maturity for all AOM-0206-A Flexible and modular ARES in accordance Linked to Solution #31 V3 7 of 17
with the VPA design principle reach the maturity for all AOM-0303 Pan-European Transit Service OAT V3 reach the maturity for all AOM-0304-A Mission Trajectories in Step 1 ) reach the maturity for all AOM-0501 Free Routing for Flights both in cruise and vertically evolving within low to medium complexity environments Linked to Solution #33 - reach the maturity for all 8 of 17
AUO-0104 Selective Protection Flight reach the maturity for all AUO-0105 Fleet Assignment Delay reach the maturity for all AUO-0203 EFPL in NM processes Linked to Solution #37 V3 reach the maturity for all AUO-0205-B ATC-ATC, ATC/Aircraft and ATC/NM Update (partial) 9 of 17
and Revision of the Reference Business/Mission Trajectory (RBT/RMT) reach the maturity for all AUO-0210 Participation in CDM through ismt and Target Time (TTO) negotiation reach the maturity for all AUO-0211 WOC Management of irmt via improved OAT FPL The main contribution of the project P11.01.02 is the definition of the FOC/WOC operational requirements. As though, P11.01.02 contributed to reach the maturity for all AUO-0215 Sharing ismt through improved OAT flight plan reach the maturity for all 10 of 17
AUO-0223 Harmonised and improved integration of airspace and ATC constraints/procedures in trajectories calculated by FOCs and NM. reach the maturity for all AUO-0303-A (DS14) Ground-ground aspects related to irbt/irmt revision (executed at ground or flight crew initiative) reach the maturity for all AUO-0303-B (DS14) Ground-ground aspects related to RBT/RMT revision (executed at ground or flight crew initiative, when aircraft is airborne) reach the maturity for all (partial) MET-0101 Enhanced MET observations, nowcasts and forecasts provided by ATM-MET systems for Step 1 reach the maturity for all (partial) 11 of 17
IS-0205 Digital Integrated Briefing for pre-flight phase Linked to solution #34 V3 reach the maturity for all IS-0206 Digital Integrated Briefing during flight execution phase reach the maturity for all IS-0301 (DS14) Provision and use of FOC/WOC data to enhance ATM ground system performance. V3 reach the maturity for all IS-0901-A SWIM for Step1 V3 12 of 17
reach the maturity for all IS-0901-B SWIM for Step2 The main contribution of the project P11.01.02 is the definition of the FOC/WOC operational requirements. As though, P11.01.02 contributed to reach the maturity for all V0 1.2 Project achievements The main achievement of the project P11.01.01 is the federation of the FOC/WOC perspective, and contributing consequently to ensure the consensus of all stakeholders of the European air traffic management domain, (airspace users, air navigation service providers, professional staff associations, airports, and manufacturing industry). In addition, the P11.01.01 contributed to transverse meeting to consolidate overall SESAR concepts (CONOPS and Transition CONOPS meetings organized by B04.02). It has been recognized by SJU the significant interaction with the rest of the Programme, in particular with B4.2 on concept development; the PCG also recognised the federating role of the project 11.01.01. P11.01.01 proactively reacted to align the planning and the deliverables with the rest of the SESAR program. It resulted a significant bias between initial planning per contract and the current one at the end of the project. Before the beginning of WP11.01, the FOC role was mainly focused on flight planning phase. As a consequence to the development made, it has been recognized that it would not be possible to obtain full benefit of the ATM modernization programme if the FOC involvement during the execution phase is not reinforced, according to what is defined within ICAO document 9976 [9]. Due to organization of WP11.01, each project is a piece of a puzzle, and the overall picture is revealed at WP level only. The work package WP11.01 succeeded in establishing efficient coordination with other work packages, especially: P07.06.02 Optimized Airspace Users Operations (EFPL and UDPP) P07.05.04 Flexible Airspace Management P13.02.02 Aeronautical Information Management P04.03 Integrated and pre-operational validation & cross validation P11.02.02 MET Information Systems. Development, Validation and Verification 13 of 17
It permits in the end to execute several validations that were needed to achieve the overall concept of Business/Mission trajectory. Finally, through the work performed by WP11.01, the maturity of the following operational areas significantly increased: BMT (including Extended Flight plan and Improved OAT Flight plan) Free Route AFUA UDPP Digital Briefing 1.3 Project Deliverables The following table presents the relevant deliverables that have been produced by the project. Reference Title Description D01 Definition of the trajectory requirements for Step 1, including gap analysis, support to standardization report from AU perspective Civil DOD Step 1 - This document represents deliverable D11.01.01-1 and the input to project P11.01.02 focusing on the development of operational requirements for Step 1 from an FOC perspective. The two focus areas for FOC systems are therefore: - Initial time-based operations - Trajectory data exchange Refer to [5] D02 Definition of the trajectory requirements for Step 1 and Step 2 and Step 3 as available, including gap analysis, support to standardization report from Airspace User perspective D08 FOC Definition of the trajectory requirements for Step 2 and Step 3 as available, including gap analysis, support to standardization report from AU perspective D05 Contribution Note to Transition ConOps Military DOD Step 1, Step 2 & Step 3 as available - This document forms the input to project P11.01.02 focusing on the development of operational requirements for Step 1 and Step 2&3 capabilities from a WOC perspective. Refer to [6] Civil DOD Step 2 & Step 3 as available This document provides the description of a Flight Operations concept aiming to model and support the SESAR Step 2 and Step 3 objectives. As not enough material has been produced for Step 3, this DOD will be limited to concept related to Step 2. Refer to [7] This document describes the contribution of WP11.01 to the SESAR 2020 Transition Concept of Operations document with regard to the civil Airspace User s aspects. Refer to [8] 14 of 17
1.4 Contribution to Standardisation P11.01.01 contributed to support the standardisation work in external bodies, such as ICAO ATM- RPP (Refer to ICAO document 9976 [9]), NextGen, CARATS, by identifying and consolidating future standardisation requirements. As part of the different contributions made to the discussions and papers developed linked to WP11.01 role, a specific paper has been presented during the ATMRPP Twenty-sixth Working Group Meeting in Japan last 2014 titled: In-Flight monitoring activity performed by FOC (Flight Operations Centre) Although thru this paper it has been recognized that in the current ATM environment In-Flight monitoring of a flight is a task performed by several stakeholders for different purposes, the goal was to present In-Flight monitoring capabilities currently available in a typical Flight Operations Centre and describe the rationality behind each one of them. This paper has been previously agreed with the Airspace Users community of WP11.01. The participation in such meetings helped to raise the awareness of WP11.01 among the aeronautical community resulting most useful when both profiles (operational & technical) were present. 1.5 Project Conclusion and Recommendations The projects P11.01.01 & 02 supported the P11.01.03 to translate the operational and business requirements for the FOC/WOC into systems requirements and specifications for the The "Contribution Note to Transition ConOps" delivered by P11.01.01 will be a basis input for SESAR2020 projects like PJ06, PJ07, PJ08, PJ09 and PJ18. It describes the Civil AU Operations Centre and its role within other ATM stakeholders e.g specifically provision of airspace user operational scenarios, airspace user roles and responsibilities and top level & high level requirements related to SESAR 2020 PJ07 Optimised Airspace Users Operations (civil & military airspace user aspects). Thanks to WP11.01, it has been recognized that it would not be possible to obtain full benefit of the ATM modernization programme if the FOC involvement during the execution phase is not reinforced. The consolidation of the FOC role during execution phase has to be followed-up beyond SESAR and SESAR 2020. 15 of 17
2 References [1] SESAR Programme Management Plan, Edition 03.00.01 [2] European ATM Master Plan [3] Multilateral Framework Agreement ( MFA ) signed between the SJU, EUROCONTROL and its 15 selected members on August 11, 2009, amended on 14 June 2010, 19 October 2010 and 2 July 2012 [4] Transversal Consistency of Business / Mission Trajectory Requirements (across WPs) - Project Initiation Report - Edition 00.00.02-03/11/11 [5] Definition of the trajectory requirements for Step 1, including gap analysis, support to standardization report from AU perspective - Edition 00.00.04-11/07/12 [6] Definition of the trajectory requirements for Step 1 and Step 2 and Step 3 as available, including gap analysis, support to standardization report from Airspace User perspective - Edition 00.01.01-21/02/2013 [7] FOC Definition of the trajectory requirements for Step 2 and Step 3 as available, including gap analysis, support to standardization report from AU perspective - Edition 01.00.00-10/10/2013 [8] Contribution Note to Transition ConOps - Edition 00.01.00-11/08/2016 [9] ICAO document 9976 - Flight Planning and Fuel Management Manual - 2015 Edition 16 of 17
-END OF DOCUMENT- 17 of 17