490 likes | 590 Views
Presentation to Trajectory Specs ISSUE Group FOS Structures & Interactions Brussels 27 Sept 2012. Peter Hendrickx Maastricht UAC – Operations peter.hendrickx@eurocontrol.int +31 34 466 1507. Flight Keys. Flight Characteristics. Cleared T. Agreed T. IOP Flight Script.
E N D
Presentation to Trajectory Specs ISSUE Group FOS Structures & Interactions Brussels 27 Sept 2012 Peter Hendrickx Maastricht UAC – Operations peter.hendrickx@eurocontrol.int +31 34 466 1507
Flight Keys Flight Characteristics Cleared T Agreed T IOP Flight Script IOP 4D Trajectory (IOP Consistency Check) Other Planning Data Last Downlinked EPP ADS-C Contract Info, ETA min/Max etc Air-Ground Consistency Check Results ARR-Gate to DEP-Gate Data (ATV Hook) Flight Object Main Structures Flight Object • Proposal • Any other solutions welcome • Why so complicated? • Why so much duplication? Other Shared Data
Flight Keys Flight Characteristics IOP Flight Script IOP 4D Trajectory (IOP Consistency Check) Last Downlinked EPP ADS-C Contract Info, ETA min/Max etc Air-Ground Consistency Check Results ARR-Gate to DEP-Gate Data (ATV Hooks) Single Reference – Basic Needs Flight Object • T = Trajectory in broad terms • More than 4D line • Can be MT or BT • Gate to Gate • Flag indicates S_T or R_T • 4D: • 2D Flight-path • Levels • Timing Info • Tolerances • Constraints Cleared “T” Agreed “T” Other Planning Data Other Shared Data
Flight Keys Flight Characteristics Cleared T Agreed T IOP Flight Script IOP 4D Trajectory (IOP Consistency Check) Other Planning Data Last Downlinked EPP ADS-C Contract Info, ETA min/Max etc Air-Ground Consistency Check Results ARR-Gate to DEP-Gate Data (ATV Hooks) Flight Object Main Structures Flight Object GUFI Callsign ADEP ADES EOBT/EOBD Previous/Next GUFI Type/Number Aircraft WTC Flight Type Alternative Aerodromes Special Status (STS) Mil Formation Info Other Shared Data
Flight Keys Flight Characteristics Cleared T Agreed T IOP Flight Script IOP 4D Trajectory (IOP Consistency Check) Other Planning Data Last Downlinked EPP ADS-C Contract Info, ETA min/Max etc Air-Ground Consistency Check Results ARR-Gate to DEP-Gate Data (ATV Hooks) Flight Object Main Structures Key & X-check elements Flight Object GUFI Callsign ADEP ADES EOBT/EOBD Previous/Next GUFI Type/Number Aircraft WTC Flight Type Alternative Aerodromes Special Status (STS) … Quasi static Other Shared Data
Flight Keys Flight Characteristics Cleared T Agreed T IOP Flight Script IOP 4D Trajectory (IOP Consistency Check) Other Planning Data Last Downlinked EPP ADS-C Contract Info, ETA min/Max etc Air-Ground Consistency Check Results ARR-Gate to DEP-Gate Data (ATV Hooks) Flight Object Main Structures Flight Object Inside FMS Flown in case of PLOC Departure Clearance + Updates (DSC, verbal re-route) Agreed 3D Hard constraints= CTA, CTOs(TSA Entry/Exit Times) Planning Constraints= TTA, TTOs All with Tolerances Other Shared Data
Flight Keys Flight Characteristics Cleared T Agreed T IOP Flight Script IOP 4D Trajectory (IOP Consistency Check) Last Downlinked EPP ADS-C Contract Info, ETA min/Max etc Air-Ground Consistency Check Results ARR-Gate to DEP-Gate Data (ATV Hooks) Flight Object Main Structures Flight Object • Used in optimisation of Revisions to get to most optimal solution AO Flight Constraints AO Preferences AO Planning Goals Military Specific Planning Info (TSA, Exercise-type, Time) Other Planning Data Other Shared Data
Flight Keys Flight Characteristics Cleared T Agreed T IOP Flight Script IOP 4D Trajectory (IOP Consistency Check) Last Downlinked EPP ADS-C Contract Info, ETA min/Max etc Air-Ground Consistency Check Results ARR-Gate to DEP-Gate Data (ATV Hooks) Flight Object Main Structures Flight Object Optimisation for AU (Civ/Mil) • Used in optimisation of Revisions to get to most optimal solution AO Flight Constraints AO Preferences AO Planning Goals Military Specific Planning Info (TSA, Exercise-type, Time) Other Planning Data Other Shared Data
Flight Keys Flight Characteristics Cleared T Agreed T IOP Flight Script IOP 4D Trajectory (IOP Consistency Check) Other Planning Data Last Downlinked EPP ADS-C Contract Info, ETA min/Max etc Air-Ground Consistency Check Results ARR-Gate to DEP-Gate Data (ATV Hooks) Flight Object Main Structures Flight Object • Shared additional info • Not subject to CDM • Reduces data transfer Complex Constraint Info Original EFPL Free Text NDC Formation Callsigns TSA Reservation ID (ASM System for details) Other Shared Data
Flight Keys Flight Characteristics Cleared T Agreed T IOP Flight Script IOP 4D Trajectory (IOP Consistency Check) Other Planning Data Last Downlinked EPP ADS-C Contract Info, ETA min/Max etc Air-Ground Consistency Check Results ARR-Gate to DEP-Gate Data (ATV Hooks) Flight Object Main Structures Flight Object Just additional info • Shared additional info • Not subject to CDM • Reduces data transfer Complex Constraint Info Original EFPL Free Text NDC Formation Callsigns TSA Reservation ID (ASM System for details) Other Shared Data
Flight Keys Flight Characteristics Cleared T Agreed T IOP Flight Script IOP 4D Trajectory (IOP Consistency Check) Other Planning Data Last Downlinked EPP ADS-C Contract Info, ETA min/Max etc Air-Ground Consistency Check Results ARR-Gate to DEP-Gate Data (ATV Hooks) Data LocalATCC – Airport – FOC -NM Flight Object Other Shared Data
Flight Data Record Flight Keys Flight Characteristics AoR Cleared T AoR Agreed T Other Planning Data AOR Last Downlinked EPP ADS-C Contract Info, ETA min/Max etc Local / Upstream Air-Ground Consistency Check Results AOI Flight Script AOI LOCAL TRAJECTORY ARR-Gate to DEP-Gate Data (ATV Hooks) Other Shared Data ATC Flight Data Record • Large Subset of FO • Local AOI/AOR limited • Other Planning Data = not vital data (initially)= Network/AO relevant • No IOP 4D Trajectory • Local 4D Trajectory, • updated every 4.8 seconds • ARR-Gate to DEP-Gate Data relevant for Airport Ground System / NM / AO • Only local/Upstream Consistency Check results relevant • Tolerances/Constraints known!!! • Used by Local Tools • Viewed by Local Actors • ATCOs, FMPs, MeSP
FOC-NM Flight Data Record Flight Data Record Flight Keys • Subset of FO • Less relevant: • EPP & related data • IOP 4D Trajectory • Cleared T • Other Shared Data • But available if wanted: • IOP Flight Script • To improve accuracy • IOP 4D Trajectory • Avoid TP computation • Better Monitoring – if wanted Flight Characteristics Cleared T Agreed T Other Planning Data Last Downlinked EPP ADS-C Contract Info, ETA min/Max etc Air-Ground Consistency Check Results IOP Flight Script IOP 4D Trajectory (IOP Consistency Check) ARR-Gate to DEP-Gate Data (ATV Hooks) Other Shared Data
Cleared “T” Agreed “T” IOP Flight Script IOP 4D Trajectory (IOP Consistency Check) Last Downlinked EPP ADS-C Contract Info, ETA min/Max etc Air-Ground Consistency Check Results ARR-Gate to DEP-Gate Data (ATV Hook) Structures most relevant to TM Flight Object
Cleared “T” Agreed “T” IOP Flight Script IOP 4D Trajectory (IOP Consistency Check) ARR-Gate to DEP-Gate Data (ATV Hooks) Non ADS-C Aircraft Flight Object
Cleared “T” Agreed “T” IOP Flight Script IOP 4D Trajectory (IOP Consistency Check) Last Downlinked EPP ADS-C Contract Info, ETA min/Max etc Air-Ground Consistency Check Results ARR-Gate to DEP-Gate Data (ATV Hooks) EPP Fully consistent Flight Object Downlinked EPP: • 2D Consistent • Levels consistent • TOD/TOC (COL) implemented in Flight Script/Agreed T • Timing used to update Flight Script/Agreed T Present in the background • EPP • ADS-C contract info • consistency check results Not subscribed to by some actors. Same applies locally in Flight Data Record – ATCO CWP Although… contrary initially!!!!
Cleared “T” Agreed “T” IOP Flight Script IOP 4D Trajectory (IOP Consistency Check) Further simplification 1 Flight Object • Ground-segment not yet includedOR • Ground segment embedded in IOP Flight Script • IOP 4D Trajectory: • Sole purpose is IOP ATC-ATC • Not used by anybody else • Just data to support “a” synchronisation mechanism ARR-Gate to DEP-Gate Data (ATV Hooks)
Cleared “T” Agreed “T” Further simplification 1 Flight Object • Ground segment (ATV Hooks) embedded in IOP Flight Script • IOP 4D Trajectory: • Sole purpose is IOP ATC-ATC • Not used by anybody else • Just data to support “a” synchronisation mechanism IOP Flight Script
Cleared “T” Agreed “T” Further simplification 1 Flight Object • Info is there in the background IOP Flight Script IOP 4D Trajectory ARR-Gate to DEP-Gate Data
Further simplification 1 Flight Object • Background info not subscribed to by some actors = does not exist for them Cleared “T” Agreed “T” IOP Flight Script
Cleared “T” Agreed “T” Further simplification 2 Flight Object • Cleared “T” is by magic always equal to Agreed “T” • Cleared “T” is by magic synchronised with ATC instructions • By MAGIC = • Initial conditions remain • Advanced AGDL Services (auto CPDLC, auto DSC) • Aircraft flying in “managed” mode • ATCO monitors, does not control IOP Flight Script
Further simplification 2 Flight Object • Cleared “T” is by magic always equal to Agreed “T” • Cleared “T” is by magic synchronised with ATC instructions • By MAGIC = • Initial conditions remain • Advanced AGDL Services (auto CPDLC, auto DSC) • Aircraft flying in “managed” mode • ATCO monitors, does not control Agreed “T” IOP Flight Script
Last simplification Flight Object • Some (non-ATC) actors do not care how ATC does “the job” • Some (ATC) actors: • use OLDI rather then FO mechanism • Use 3 minutes accuracies in Entry Time • Communicate verbally non-standard transfer conditions IOP Flight Script not used Agreed “T” IOP Flight Script
Last simplification Flight Object • Some (non-ATC) actors do not care how ATC does “the job” • Some (ATC) actors: • use OLDI rather then FO mechanism • Use 3 minutes accuracies in Entry Time • Communicate verbally non-standard transfer conditions IOP Flight Script not used Agreed “T” • Background info not subscribed to by these actors IOP Flight Script
Last simplification Flight Object • Some (non-ATC) actors do not care how ATC does “the job” • Some (ATC) actors: • use OLDI rather then FO mechanism • Use 3 minutes accuracies in Entry Time • Communicate verbally non-standard transfer conditions IOP Flight Script not used Agreed “T” • Background info not subscribed to by these actors • = does not exist for them
Single Reference Flight Object • Ideal case • Call this the R_T: RBT/RMT Agreed “T”
Flight Keys Flight Characteristics Single Reference+ Flight Object • Still ideal… Agreed “T”
Flight Keys Flight Characteristics Single Reference++ Flight Object • Still quite ideal !!! Agreed “T” Other Planning Data
Flight Keys Flight Characteristics Single Reference+++ Flight Object • Still quite ideal !!! Agreed “T” Other Planning Data Other Shared Data
Flight Keys Flight Characteristics Single Reference+++* Flight Object • Reality check 1 • Cleared versus Agreed T • Easily manageable !!! Cleared “T” Agreed “T” Other Planning Data Other Shared Data
Flight Keys Flight Characteristics Single Reference+++** Flight Object • Adding ATC-ATC IOP needs • Reality check 1 • To be proven through RTS • Looking good. Cleared “T” Agreed “T” Other Planning Data IOP Flight Script IOP 4D Trajectory ARR-Gate to DEP-Gate Data Other Shared Data
Flight Keys Flight Characteristics Last Downlinked EPP ADS-C Contract Info, ETA min/Max etc Air-Ground Consistency Check Results Single Reference+++*** Flight Object • Reality check 2 • Air-Ground consistency • Adding ATC-ATC IOP needs • Reality check 1 • Reality check 2 • Air-Ground consistency • ATC-ATC IOP • Adding the wish of every ATCO!!! Cleared “T” Agreed “T” Other Planning Data IOP Flight Script IOP 4D Trajectory ARR-Gate to DEP-Gate Data Other Shared Data
Flight Keys Flight Characteristics Cleared T Agreed T IOP Flight Script IOP 4D Trajectory (IOP Consistency Check) Other Planning Data Last Downlinked EPP ADS-C Contract Info, ETA min/Max etc Air-Ground Consistency Check Results ARR-Gate to DEP-Gate Data (ATV Hooks) Our Plan Flight Object • Proposal • Any other solutions welcome • Why so complicated? • Why so much duplication? Other Shared Data
Flight Keys Flight Characteristics Cleared T Agreed T IOP Flight Script IOP 4D Trajectory (IOP Consistency Check) Other Planning Data Last Downlinked EPP ADS-C Contract Info, ETA min/Max etc Air-Ground Consistency Check Results ARR-Gate to DEP-Gate Data (ATV Hooks) Flight Object Main Structures Flight Object • Proposal • Any other solutions welcome • Why so complicated? • Because it is a complicated situation • Solution is not so complicated • Why so much “duplication”? • Temporal differences • Different needs (granularity, presicion) and limitations (update rates) • Non-synchronised processes (not yet) • Step-wise Implementation • Seeking • Support by this “ISSUE” group • CP 3.1. and 3.2. defending the model Other Shared Data
Scenarios • EPP Downlink and Consistency check • Early ending Military Activity • Cracked Windshield • Turbulence – Level Change request • Temporary clearance for separation • Heavy wind – Time deviation • Change of STAR • Hotspot resolution by NM
Principles • FDMP/FDCs/FDUs roles • EPP data used by ATC/Airport to: • Check consistency • Improve ground-held view • Order of accuracy – update rate (H to L) • Trajectory in C-ATSU (tracks) • IOP Flight Script • Agreed T
NM IOP FDMP C-ATSU APT EFB Aircraft SWIM IOP Appl IOP Appl IOP Appl D-ATSU FOC
EPP Consistency Check NM FDMP C-ATSU APT EFB Aircraft SWIM FDC EPP EPP FDC FDU FDC D-ATSU FOC
EPP Consistency Check NM C-ATSU APT EFB Aircraft SWIM FDMP FDC EPP FDC FDU FDC D-ATSU FOC
EPP Consistency Check NM C-ATSU APT EFB Aircraft SWIM FDMP FDC EPP FDC FDU FDC D-ATSU FOC
EPP Consistency Check NM C-ATSU APT EFB Aircraft SWIM FDMP If consistent & If time buffer exceeded: -update IOP Flight Script (with IOP 4D Trajectory for checking FDC FDC FDU FDC If all upstream consistent & Quality increased (MTCD, Flow) D-ATSU FOC
EPP Consistency Check NM C-ATSU APT EFB Aircraft SWIM FDMP If consistent & If time buffer2 exceeded: -update TTO-s in Agreed T FDC FDC FDU FDC D-ATSU FOC
EPP Consistency Check NM C-ATSU APT EFB Aircraft SWIM FDMP FDC FDC FDU FDC D-ATSU Consume updated data FOC
Early availibility Mil Area in D-ATSU NM FDMP C-ATSU APT EFB Aircraft SWIM Graphical Work in Progress - Check next slide FDC EPP FDC FDU FDC D-ATSU FOC
Early availibility Mil Area in D-ATSU Events • Re-routeing proposal prepared by FDC • FDC notices his proposal is outside RBT tolerances • Through FDMP, FDC starts CDM revision on agreed RBT • FOC and NM are triggered • All partners agree • FDMP puts revised RBT in the Flight Object • EPP Consistency set to FALSE • FDMP updates the Flight Script (and Shared 4D Traj) • FDC detects mismatch Agreed-Cleared RBT and flags to ATCO • ATCO uses DSC • C-ATCO uses Route-Clearance • ATCO waits till flight on frequency (Cleared RBT = kept for PLOC) • EPP is downloaded • Cleared RBT updated by FDMP • EPP Consistency Check like in previous scenario (leading to properly better timing)
To be tackled • Where is the Executed Trajectory? • How embed the ARR-Gate to Dep-Gate data? (ATV Hooks) • Develop other scenarios supporting the 4 different processes. • Which EFPL Data fits well / where in FO Structures?
Processes • Air Ground Update Process • Air Ground Revision Process • Ground Ground Update Process • Ground Ground Revision Process
For Info: Correction Loops • Loop1: • Warning to Pilot: stay within tolerances please • Alert to Pilot: respect constraints!!! • Loop2: • Warning to ATCO: try to respect tolerances please • Alert to ATCO: respect constraints!!! • Loop3: • Warning to NM: OK to breach tolerances? • Alert to NM: Find solution for non-respected constraints
Peter Hendrickx Maastricht UAC – Operations peter.hendrickx@eurocontrol.int +31 34 466 1507 End... For now