1. Seville, Spain 24-25 June 2008 The REACT Initiative Miguel Vilaplana – Boeing Research & Technology Europe

2. REACT Workshop Seville, Spain 24 th -25 th June 2008 2 Motivation: Trajectory Synchronisation in the Future ATM System A New ATM Paradigm: Trajectory Based-Operations (TBO) - Key feature of the target concept of operations proposed by SESAR and NextGen: - Collaborative management of business trajectories supported by advanced trajectory-based automation tools - Trajectory-based automation tools rely on trajectory prediction - To support the interoperability between disparate trajectory-based automation tools, there is a need for mechanisms to synchronise Trajectory Predictors (TPs) - TP synchronisation is a key prerequisite for the SESAR/Next Gen concepts - The REACT project has focused on one of the types of information that can be shared between TPs to achieve synchronisation: the Aircraft Intent

3. REACT Workshop Seville, Spain 24 th -25 th June 2008 3 A bit of terminology Business Trajectory: – Represents the business/mission intention of an airspace user – Evolves through a collaborative planning process that involves users and ATM service providers and whose outcome should be a trajectory that results in minimum deviations from the user preferences Interoperability is a property referring to the ability of diverse systems to work together (inter-operate) A key necessary condition for the interoperability of trajectory-based automation tools is the synchronisation of the underlying TPs The synchronisation of two TPs results in a minimally acceptable difference between the trajectory outputs of those TPs (this minimally acceptable difference depends on the applications supported by the TPs)

4. REACT Workshop Seville, Spain 24 th -25 th June 2008 4 Towards Trajectory Based Operations (TBO) City B AOC1 AOC2 ANSP1 ANSP2 ANSP 3 ANSP 4 ANSP1 BUSINESS TRAJECTORIES ANSP= Air Navigation Service Provider AOC= Airline Operations Centre

5. REACT Workshop Seville, Spain 24 th -25 th June 2008 5 Towards TBO: Interoperability and TP Synchronisation TRAJECTORY RELATED INFORMATION AOC1 AOC2 ANSP1 ANSP2 ANSP 3 ANSP1 ANSP 4

6. REACT Workshop Seville, Spain 24 th -25 th June 2008 6 TRAJECTORY RELATED INFORMATION Towards TBO: Interoperability and TP Synchronisation TP 2 TP I TP 1 TP P TP 6 TP N TP 3 TP R TP 4 TP K TP 5 TP L TP H FP CD&R ASAS FMSAMAN FP FDPS FMS ATFM FMS DMAN AMAN= Arrival manager DMAN= Departure manager FMS= Flight Management System FP=Flight Planning ASAS=Airborne Separation Assurance System ATFM=Air Traffic Flow Management FDPS=Flight Data Processing Tool CD&R=Conflict Detection and Resolution FMS

7. REACT Workshop Seville, Spain 24 th -25 th June 2008 7 Actual aircraft state (position, speed, weight…) More Terminology: Trajectory-Related Information Environmental Conditions Pilot Real World Trajectory Prediction (Air or Ground) Flight Commands & Guidance Modes Flight Intent Flight Plan Tactical Amendments to Flight Plan Airborne Automation System Actual Trajectory ? Aircraft Predicted Trajectory Trajectory Computation Infrastructure Aircraft Intent Intent Generation Infrastructure Initial Conditions Trajectory Predictor (TP) AT or ABOVE FL290

8. REACT Workshop Seville, Spain 24 th -25 th June 2008 8 Sharing Trajectory-Related Information Data COM Infrastructure Predicted trajectory information Flight Intent Airborne Predicted Trajectory TP PROCESS 2 (e.g., arrival manager) Flight Intent Ground Predicted Trajectory Trajectory Computation Infrastructure (1) Aircraft Intent Intent Generation Infrastructure (1) Airborne TP Trajectory Computation Infrastructure (2) Aircraft Intent Intent Generation Infrastructure (2) Ground TP Aircraft Intent information Flight Intent Information Trajectory Prediction (e.g., flight management system)

9. REACT Workshop Seville, Spain 24 th -25 th June 2008 9 The Aircraft Intent Description Language (AIDL) Two levels in the language grammar: lexical and syntactical Lexical Level: Instructions – Instructions are atomic inputs to the Trajectory Engine that capture basic commands and guidance modes at the disposal of the pilot/FMS to direct the operation of the aircraft Syntactical level: Operations – Operations are sets of compatible instructions that, when simultaneously active, univocally determine the ensuing aircraft motion With a reduced set of instructions (AIDL alphabet), any possible aircraft operation can be formally specified in such a way that the ensuing aircraft motion is unambiguously determined

10. REACT Workshop Seville, Spain 24 th -25 th June 2008 10 The REACT Project R equirements E licitation for an A IDL that supports C onsistency across T Ps Aircraft Intent Description Language Eliciting requirements for a language that can serve as a standard means for sharing aircraft intent information between TPs – The language shall be independent of the –Operational context and application served by the TPs –Physical location of the TPs –Communication means Consortium:

11. REACT Workshop Seville, Spain 24 th -25 th June 2008 11 The Scope of REACT Next generation FMS AOC 2 ATFM DST FMS AOC 1 FDPS AMAN DST Next Generation FDPS Air-Air Air-Ground Ground-Ground

12. REACT Workshop Seville, Spain 24 th -25 th June 2008 12 TRAJECTORY RELATED INFORMATION: AIRCRAFT INTENT Aircraft Intent Synchronisation in the future TBO without a standard AIDL… TP 2 TP I TP P TP R TP K TP 5 TP L TP H Translator I-5 Translator R-5 Translator 2-K Translator R-2 Translator 2-5 Translator I-2 Translator H-5 Translator R-P N · (N-1) ÷ 2 TRANSLATORS Translator K-P Translator 5-K Translator I-R Translator 5-P Translator L-5 Translator I-H Translator H-L Translator R-K Translator L-P

13. REACT Workshop Seville, Spain 24 th -25 th June 2008 13 TP 2 TP I TP P TP R TP K TP 5 TP L TP H Translator L-AIDL AIDL Translator 5-AIDL Translator P-AIDL Translator K-AIDL Translator R-AIDL Translator 2-AIDL Translator H-AIDL Translator I-AIDL N TRANSLATORS AIDL as a Standard supporting TP Synchronisation in the future TBO

14. REACT Workshop Seville, Spain 24 th -25 th June 2008 14 REACT Approach Elicitation process based on uncovering the commonalities existing between the ways in which different TPs model aircraft intent information Superset of the aircraft intent information used by any two TPs that need to synchronise with each another Use of the theoretical language structured as a reference to describe the requirements The standard AIDL would include the aircraft intent description “dialects” used by the individual TPs, which could map their aircraft intent model to a subset of the AIDL Focus on information content and structure

15. REACT Workshop Seville, Spain 24 th -25 th June 2008 15 REACT Contributors

16. REACT Workshop Seville, Spain 24 th -25 th June 2008 16 The Remainder of the Workshop Stakeholders will present their views on the Business Trajectory and on trajectory synchronisation in different contexts Presentation of a set of preliminary AIDL requirements Gather your inputs on the way forward through open debate. Enjoy and engage!

17. REACT Workshop Seville, Spain 24 th -25 th June 2008 17 The Remainder of the Workshop BACKUP SLIDES

18. REACT Workshop Seville, Spain 24 th -25 th June 2008 18 What aircraft trajectory IS: The evolution of certain aspects of the aircraft motion ( geometry, kinematics and kinetics ) A time sequence of aircraft motion states (e.g. a sequence of 4D points) The output of the trajectory computation process Trajectory vs. Aircraft Intent What aircraft trajectory is NOT: A set of constrains that the aircraft motion must comply with (e.g. follow a specified CAS/Mach speed schedule) The specification of strategies to be implemented by the aircraft or objectives to be fulfilled by its motion (e.g. an RTA to be met) What aircraft intent is NOT: A flight plan A sequence of 4D waypoints with a set of constraints to comply with ATC instructions A predicted trajectory What aircraft intent IS: An unambiguous description of how the aircraft is to be operated within a timeframe An abstraction of the flight instructions issued by the Pilot/FMS to manage the aircraft behavior The input to the trajectory computation process

19. REACT Workshop Seville, Spain 24 th -25 th June 2008 19 Formalization of the Concept of Aircraft Intent Instructions: - They capture basic commands and guidance modes at the disposal of the pilot/FMS to direct the operation of the aircraft - They can be seen as minimal indivisible pieces of information describing distinct manners of closing one of the aircraft motion’s degrees of freedom - An instruction is characterized by a mathematical equation that is to be satisfied simultaneously with the equations of motion during a certain time interval, denoted as the execution interval Operations: - They represent an elemental aircraft behaviour that determines its motion unambiguously during a specific time interval denoted as the operation interval - An operation is the result of a set of compatible instructions simultaneously active during the corresponding operation interval

20. REACT Workshop Seville, Spain 24 th -25 th June 2008 20 AIDL Overview: Elements AIDL Alphabet Grammar Lateral Instructions Vertical Instructions Speed Instructions Propulsive Instructions Configuration Instructions Lexical Rules Syntactical Rules Lateral: Aircraft bearing Law: Constant Value: 175º Speed: CAS Law: Constant Value: 280 Knots Configuration: Flaps Law: Constant Value: 15º