30 likes | 172 Vues
This document outlines essential aspects of flight trajectory management (TMF) and its integration within the overall operational framework. It addresses the coordination of various traffic management services, including Ground ATC, ATFCM IOP, and FOS services. Key focus areas include the synchronization of RBTs (Recommended Business Trajectories) through FOS, interaction protocols on flight trajectories, and the necessary data sharing among stakeholders. This comprehensive approach aims to enhance seamless coordination, conflict management, and operational efficiency across air-ground interfaces.
E N D
Step1InteropInitial situation 3 OFAs: - OFA IOP: 03.01.08 - OFA TMF: 03.01.01 (2 main OIs : AUO 0203 & 0204) Not Swim but via ADS-C - OFA BMT: 03 01 04 TMF Services(Enabler) CFMU - FOSGround ATC - ATFCM IOP Swim Svces Network Mngt FO (SBT) RTA ETA min-max? PENS Traffic Synch i4D + CTA, AMAN, XMAN? FO (RBT) Seamless coord & transfer Separation conflict tasks Mngt IOP FOS (Enabler) ICOG ED133Ground ATC-ATC IOP New i4DAir-Ground IOP How to share and synchronise RBTs through FOS? When do we have to synchronise FO? Why do we need to interact on Flight Trajectory?(Which data do we need to share)?
http://im.eurocontrol.int/wiki/index.php/Trajectory_Management_Definitionshttp://im.eurocontrol.int/wiki/index.php/Trajectory_Management_Definitions