Transcript Slide 1
REACT The REACT Initiative Miguel Vilaplana – Boeing Research & Technology Europe Seville, Spain • 24-25 June 2008 Motivation: Trajectory Synchronisation in the Future ATM System REACT Workshop Seville, Spain 24th-25th June 2008 • 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 REACT 2 A bit of terminology REACT Workshop Seville, Spain 24th-25th June 2008 • 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) REACT 3 Towards Trajectory Based Operations (TBO) REACT Workshop Seville, Spain 24th-25th June 2008 ANSP1 ANSP4 AOC2 ANSP2 BUSINESS TRAJECTORIES ANSP3 City B ANSP= Air Navigation Service Provider ANSP1 REACT AOC= Airline Operations Centre AOC1 4 Towards TBO: Interoperability and TP Synchronisation REACT Workshop Seville, Spain 24th-25th June 2008 ANSP1 ANSP4 AOC2 TRAJECTORY RELATED INFORMATION ANSP2 ANSP3 ANSP1 REACT AOC1 5 Towards TBO: Interoperability and TP Synchronisation REACT Workshop Seville, Spain 24th-25th June 2008 ASAS=Airborne Separation Assurance System TP2 TP4 ATFM=Air Traffic Flow Management FDPS=Flight Data Processing Tool CD&R=Conflict Detection and Resolution ATFM TPR FMS TP 3 TPI TPH FDPS TP1 FMS TPN TRAJECTORY RELATED INFORMATION TPK AMAN FMS TP6 ASAS TP5 AMAN= Arrival manager TPL CD&R REACT TPP DMAN= Departure manager FMS= Flight Management System FP=Flight Planning 6 More Terminology: Trajectory-Related Information REACT Workshop Seville, Spain 24th-25th June 2008 Trajectory Prediction (Air or Ground) Trajectory Predictor (TP) Intent Generation Infrastructure Flight Intent Aircraft Intent Trajectory Computation Infrastructure Predicted Trajectory Initial Conditions ? Airborne Automation System Flight Plan Tactical Amendments to Flight Plan Real World REACT Actual aircraft state (position, speed, weight…) Flight Commands & Guidance Modes Actual Trajectory Pilot Aircraft AT or ABOVE FL290 Environmental Conditions 7 Sharing Trajectory-Related Information REACT Workshop Seville, Spain 24th-25th June 2008 Trajectory Prediction (e.g., flight management system) Airborne TP Flight Intent Flight Intent Information Flight Intent Intent Generation Infrastructure (1) Data COM Infrastructure Intent Generation Infrastructure (2) Aircraft Intent Trajectory Computation Infrastructure (1) Predicted trajectory information Aircraft Intent information Aircraft Intent Airborne Predicted Trajectory Trajectory Computation Infrastructure (2) Ground Predicted Trajectory Ground TP TP PROCESS 2 (e.g., arrival manager) REACT 8 The Aircraft Intent Description Language (AIDL) REACT Workshop Seville, Spain 24th-25th June 2008 • 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 REACT 9 The REACT Project REACT Workshop Seville, Spain 24th-25th June 2008 Requirements Elicitation for an AIDL that supports Consistency across TPs 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 REACT Consortium: 10 The Scope of REACT REACT Workshop Seville, Spain 24th-25th June 2008 Air-Air Next generation FMS FMS Air-Ground AOC 2 AOC 1 Next Generation FDPS FDPS AMAN DST REACT Ground-Ground ATFM DST 11 Aircraft Intent Synchronisation in the future TBO without a standard AIDL… REACT Workshop Seville, Spain 24th-25th June 2008 TP2 Translator 2-K Translator I-2 TPR Translator I-R TPI Translator TRAJECTORY I-5 Translator R-P Translator RELATEDR-5INFORMATION: AIRCRAFT INTENT Translator H-5 Translator H-L REACT TPK Translator 5-K Translator K-P TP5 Translator L-5 TPL Translator R-K Translator 2-5 Translator I-H TPH Translator R-2 Translator 5-P Translator L-P TPP N· (N-1) ÷ 2 TRANSLATORS 12 AIDL as a Standard supporting TP Synchronisation in the future TBO REACT Workshop Seville, Spain 24th-25th June 2008 TP2 TPR Translator 2-AIDL TPI Translator R-AIDL Translator I-AIDL TPH Translator H-AIDL Translator K-AIDL AIDL TPK Translator 5-AIDL TP5 Translator L-AIDL Translator P-AIDL N TRANSLATORS TPL REACT TPP 13 REACT Approach REACT Workshop Seville, Spain 24th-25th June 2008 • 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 REACT 14 REACT Contributors REACT Workshop Seville, Spain 24th-25th June 2008 REACT 15 The Remainder of the Workshop REACT Workshop Seville, Spain 24th-25th June 2008 • 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! REACT 16 The Remainder of the Workshop REACT Workshop Seville, Spain 24th-25th June 2008 • BACKUP SLIDES REACT 17 Trajectory vs. Aircraft Intent REACT Workshop Seville, Spain 24th-25th June 2008 What aircraft trajectory IS: What aircraft trajectory is NOT: • 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) 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) • The output of the trajectory computation process What aircraft intent IS: 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 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 REACT 18 Formalization of the Concept of Aircraft Intent REACT Workshop Seville, Spain 24th-25th June 2008 • 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 REACT 19 AIDL Overview: Elements REACT Workshop Seville, Spain 24th-25th June 2008 AIDL Alphabet Grammar Lateral: Aircraft bearing Lateral Instructions Vertical Instructions Speed Instructions Law: Constant Syntactical Rules Value: 175º Speed: CAS Lexical Rules Law: Constant Value: 280 Knots Propulsive Instructions REACT Configuration Instructions Configuration: Flaps Law: Constant Value: 15º 20