Operation Context and Use Case Focus Group

1. Operation Context and Use Case Focus Group May 31th, 2018

2. Agenda • Schedule • TFMS Flow Feedback • TFMS Flight • Operational Context • TBFM • Preview

3. Schedule

4. Closeout TFMS Flow

5. TFMS – Flow Operational Context • Introduction • Describes the purpose of the document and the scope it covers • Provides an overview of TFMS system and the information it produces • TFMS Flow Overview • Provides detailed descriptions of message categories produced by TFMS in the Flow data feed • TMIs • GDP • AFP • Reroute • CTOP • Other Constraints

6. TFMS – Flow Operational Context Cont. • TFMS Flow Message Types • Provides itemized breakdown of each data element in all message along with a description of the information provided • AfpAdvisory • afpCancel • afpCompression • generalAdvisory • gdpAdvisory • gdpCancel • gdpBlanket • gdpCompression • gsAdvisory • gsCancel • feaFca • reroute • ctopDefinition • ctopCancel • deicingMessage • restrictionMessage • airportConfigMessage • raptTimelineMessage

7. Feedback Received • Editorial: • Incorporated all editorial feedback received • Structural: • Adding table to Ops Context document to better organize Message Types information • Informational: • Received request to provide definitions of element level restrictions (max/min character length, case sensitivity, etc.) • This information will be added into the documentation. • A process for maintaining update to date information needs to be established. • Adding list of acronym definitions to list. • Questions: • What does “*” mean? • Wildcard • Within Flight Data description - Are these messages send on a flight by flight basis? IE: flight data changes for one flight so the AU will get a message about that specific flight? • Messages are published only containing information for the flight which was affect by the change • What is the difference between command change and computed change? • Command change: Change which occurred due to controller input • Computed change: Change which occurred due to automation input • Will a message contain all elements listed, or a subset? • Not all elements listed will be included. • Each message has a subset of elements which are “required” and the rest are “optional”. • Optional elements are only included when needed. • See XML schema for details.

8. Overview TFMS Flight

9. Decomposition of TFMS Flight Data Elements Traffic Flow Management Service – Flight Information • Flight • International • Terminal • Flight Plan Data • Departure and Arrival time notifications • Flight cancellations • Boundary crossings • Track position reports • NCSM information • Filed flight plan • Flight plan amendment • Flight arrival notification • Flight departure notification • Flight plan cancellation • Departure delay notification • Flight track position report • Oceanic track position report • Notification that no additional reports will be received for a flight • Target times for movement area entry • Off-block time • Take-off time • Projected wheels-up time

10. TFMS – Flight Operational Context • Introduction • Traffic Flow Management System Overview • TFMS Applications • TFM Flight Data Service Overview • Flight Data Messages: Overview • Message Overview and Usage • Schedule Data • CDM Messages • ATC Messages • Miscellaneous Sources • Flight Data Messages: Definitions • Flight Plan Information • Flight Plan Amendment Information • Departure Information • Arrival Information • Flight Plan Cancelation • Boundary Crossing Update • Track Information • Oceanic Report • Beacon Code Assignment • Flight Create (NCSM) • Flight Modify (NCSM) • Flight Control (NCSM) • Flight Schedule Activate (NCSM) • Flight Route (NCSM) • Flight Sectors (NCSM) • Flight Times (NCSM)

11. TFMS – Flight Operational Context • Flight Data Messages: Definitions • flightPlanInformation • flightPlanAmendmentInformation • departureInformation • arrivalInformation • flightPlanCancellation • boundaryCrossingUpdate • trackInformation • oceanicReport • beaconCodeInformation • ncsmFlightCreate • ncsmFlightModify • ncsmFlightControl • ncsmFlightScheduleActivate • ncsmFlightRoute • ncsmFlightSectors • ncsmFlightTimes • Background on how Legacy ASDI is processed by TFMS

12. Preview TBFM

13. Decomposition of TBFM Data Elements Time Based Flow Metering

14. Sourcing Time Based Metering Information

15. Current State: NAS Operations • Aircraft departs for constrained airport • Ninety minutes from destination TBFM creates an arrival plan for the aircraft • Arrival plan includes the ETA and STA at metering fix and runway • The STA at the runway is the time when the aircraft is scheduled to land • Controllers manage flights to meet these times • FOC unaware of STA: does not know when aircraft will arrive, negatively affecting gate assignments, passenger connections, crew and aircraft rotations decisions • FOC planning negatively affected due to lack of accurate arrival time data (STA) ATC • Creates Arrival Plan for Aircraft • Updated ETA/STA • Manages aircraft accordingly Arrival FOC • Unaware of metering plan • Using original ETA • Attempting to allocate resources based on inaccurate information Landing / Taxiing In

16. Problem Statement • En-route Traffic demand exceeds capacity at destination airport • Controllers enact a TMI to begin metering aircraft prior to arriving at destination airport • Aircraft is slowed down and the arrival time is pushed back • A new STA is issued for the aircraft and shared with down stream controllers • Aircraft arrives as planned per the updated STA • Backup on taxiway due to unplanned congestion in non-movement area causes delay on ground • Aircraft Departs on Time Departure Arrival ATC Perspective • Aircraft is slowed down and the arrival time is pushed back • ADC notices the slowdown but does not know what the new arrival time will be • Aircraft arrives later than planned • ADC works to reallocate ground resources to handle late aircraft • Backup on taxiway due to unplanned congestion in non-movement area causes delay on ground • Aircraft Departs on Time Departure Arrival AOC Perspective Take-off / Departure Push Back / Taxiing Out Cruise / Enroute / Oceanic Landing / Taxiing In Pre-Flight Approach

17. Time Based Metering Information Service Service Description • The TBFM Metering Information Service publishes metering information to allow the TBFM system, FAA systems (e.g. TFMS), and industry to collaborate, share TBFM data and be informed of TBFM STAs that are in effect during metering events. Service Interface • Publish/Subscribe via JMS Message Sets

18. References • SWIFT Focus Group Website • http://connect.lstechllc.com/index.cfm/main/opconfocusgroup • TFMS Flight – Operational Context Document • http://connect.lstechllc.com/files/TFM%20Flight%20Data%20Operational%20Context%20Document_Final.docx • TFMS Flight – Use Case Document • http://connect.lstechllc.com/files/TFMS%20Flight%20-%20Use%20Case%20Document%20Final%20v3.docx • Please review and provide feedback by June 15th, 2018 • Contacts • Stuart Wilson (stuart.wilson@lstechllc.com) • Felisa White (felisa.white@faa.gov)

19. Backup