1 / 13

4D Trajectory Technical Interchange Meeting

4D Trajectory Technical Interchange Meeting. February 5-6, 2014 Bob Humbertson Dawn McConkey. Things to Know. In the event of a Fire Alarm, Proceed out the glass entry doors, take the stairway off to your left down to the first floor If you need assistance, let one of us know

kiana
Télécharger la présentation

4D Trajectory Technical Interchange Meeting

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 4D Trajectory Technical Interchange Meeting February 5-6, 2014 Bob HumbertsonDawn McConkey

  2. Things to Know • In the event of a Fire Alarm, Proceed out the glass entry doors, take the stairway off to your left down to the first floor • If you need assistance, let one of us know • Gathering place is in the courtyard at the front of the building • Restrooms are immediately past the elevators to the right. • Entry/Exit is through the front glass doors. • Guest internet is available • BAHWAP01-Guest ssid • PW: st@yP0sitive • use a 0 “zero” not an “O”

  3. Purpose • Continue work contributing to establishing the FIXM Standard and Data Elements for the dynamic exchange of flight information for the 4D Trajectory (4DT) • Status the work completed to date on the 4D Trajectory Core Data Elements for inclusion in FIXM Version 3.0 • Develop process, work plan, product(s) and resourcing needed for developing the minimum set of 4DT Extensions for Arrival/Departure for inclusion in FIXM v.4.0.

  4. FIXM 3.0 is scheduled to be released in late Summer 2014 FIXM team needed 4D trajectory data by November 2013 FIXM 3.0 is scheduled to include 4D Trajectory Core Elements put forth to date (pens down March 2014) FIXM and 4D Trajectory Data The Schedule we worked against

  5. Concept of Operation Concept of Use Scenarios Description of Messages Description of Data Elements Interface Control Document Documents

  6. Objective of this TIM • Status the Core 4DT FIXM Data Elements identified for FIXM v.3.0 • Establish the process to identify and define the minimum set of 4DT Extension Data Elements for FIXM v.4.0 • The trajectory management/harmonization process which will set the context for the trajectory definition TIM Success Criteria • Documented process, work plan, product(s) and resourcing needed for developing 4DT Extensions for FIXM v.4.0.

  7. Trajectory Team Members

  8. Day 1 - Agenda 8:00 – 8:15 Introductions 8:15 – 8:45 Welcome Bob Humbertson 8:45 – 9:15 Trajectory Level Setting Steve Bradford 9:15 – 10:15 European Level Setting Richard Pugh 10:15 – 10:30 Break 10:30 – 11:30 Australian Air Services Level Setting Greg McDonald 11:30 – 12:30 Lunch 12:30 - 1:30 FIXM Level Setting Rod Little 1:30 – 2:30 Discussion of 4DT Core Elements Stephane Mondoloni 2:30 – 3:00 Discussion and Wrap Up Bob Humbertson

  9. Day 2 - Agenda 8:00 – 8:15 Welcome 8:15 – 8:45 Recap Day 1 and FIXM v.4.0 Goals Bob Humbertson 8:45 – 9:15 Identify Process for 4DT Extensions NGATs SMEs 9:15 – 10:15 Discussion on Scenarios and FIXM v4.0 Stephane Mondoloni 10:15 – 11:15 Facilitated Discussions Group 11:15 – 12:15 Bounding of Work Plan and Resourcing Group 12:15 – 1:15 Working Lunch 1:15 – 2:15 Recap, Wrap-Up, Next Steps Bob Humbertson

  10. Recap from 2012 TIM TIM Held Oct. 9-11, 2012

  11. Summary and Assumptions • Need for Lexicon • Definition of trajectory terms (this is still and open item and an issue of discussion) • Concepts: • Regions have their own concepts and resulting information needs for TBO • Information exchange between Operators, ATSU and DSTs • FIXM Data Elements • FIXM 4DT Core and Extensions • Scenario analysis enables refinement to core • Items expected to be used where performance needs dictate • Exchange • Agreed to exchange cleared trajectory and alternative trajectory items to support operations • Agreed to exchange input data at a level mitigating interoperability concerns • Focus on airborne trajectory (describing path in the air, may be described pre-departure) • No need to distinguish between aircraft or FOC as source of data

  12. Action Items • Develop common trajectory definitions (suggest leverage AP-16?) • Individual Regions investigate their own TBO Concepts for trajectory information items supporting their concepts and needs (Extension Data Dictionary Elements) • Joint development of inventory of common items for initial global set (Core Data Dictionary Elements) • Obtain exchange characteristics of identified scenarios and determine sufficiency • Analyze scenarios against the data elements identified as common among the selected concept(s) • Refine core elements if required for inclusion in FIXM Version 4.0 • Identify and document rationale/justification for elements • Configuration Management of decisions and justifications

  13. Example Scenarios for ConsiderationExact Scenarios TBD • Arrival • Departure • Off-nominal • Nominal flight across multiple ANSPs • Trajectory computation through Area of Interest (including transition near a boundary, e.g., climb- out, descent) • Cross ANSP strategic flow including upstream constraints that propagate across the system • Alternative Planning such as reroutes during weather events • For Consideration During the Analysis: • Mixed capabilities (equipage, etc.) • Mixed Mode (ground-ground) • Mixed Equipage • UAS • Use of multiple trajectories and integration of operational data (including EPP) • Pre-departure trajectory creation and exchange • Multiple trajectory distinctions

More Related