Operational Context and Use Case Focus Group September 27, 2018

Agenda Document Delivery Schedule Flight Domain Data Elements Flight SWIM Services by Phase of Flight Current NAS Operations Future NAS Operations

Delivery Schedule Use Case and Ops Context documents will continue to be worked on concurrently Deliver one domain Use Case Document every two months Continue delivering one SWIM service Operational Context Document per month Late Sept. 2018 SFDPS Airspace OCD Closeout ------- TAIS OCD Storyboard Flight UCD Storyboard Oct. 2018 TAIS OCD Flight UCD FNS OCD Storyboard Nov. 2019 TAIS OCD Closeout Flight UCD Closeout FNS OCD ITWS OCD Storyboard Flow UCD Storyboard Dec. 2018 FNS OCD Closeout ITWS OCD Flow UCD ADPS OCD Storyboard Jan. 2019 ITWS OCD Closeout Flow UCD Closeout ADPS OCD TFMS Status OCD Storyboard MET UCD Storyboard Feb. 2019 ADPS OCD Closeout TFMS Status OCD MET UCD SFDPS General OCD Storyboard March 2019 TFMS Status OCD Closeout MET UCD Closeout SFDPS General OCD ISMC OCD Storyboard Aero UCD Storyboard April 2019 SFDPS General OCD Closeout ISMC OCD Aero UCD May 2019 ISMC OCD Closeout Aero UCD Closeout *OCD – Ops Context Document, UCD – Use Case Document

Use Case Document Domains Flight STDDS – SMES STDDS – TAIS TFMS – Flight SFDPS – Flight SFDPS – General Flow TFMS – Flow TBFM Meteorological ITWS STDDS – ADPS Aeronautical SFDPS – Airspace FNS Storyboard – 9/27 Draft – 10/25 Closeout – 11/29

Sourcing Traffic Flow Flight Information Service Goal is to develop a common understanding of the data Data analysis will include traceability of data Includes discussion on how data is used in the NAS September 7, 2018

TFMS, STDDS, SFDPS Flight Information Decomposition of Flight Domain Data Elements TFMS, STDDS, SFDPS Flight Information Surface En Route International Terminal EDCT information Position updates ASDE-X data Airport surface surveillance data RVR Tower data link services Flight Plan Data Departure and Arrival time notifications Flight cancellations Boundary crossings Track position reports NCSM information Special activity airspace data Altimeter setting 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 STARS data Track and flight plan data September 7, 2018

Decomposition of TFMS, SMES, TAIS, and SFDPS Flight Data by Phase of Flight Flight Plan Data (TFMS) Departure Notification (STDDS) Cancellation of filed flight plan (TFMS) Notification of Departure Delay (STDDS) Off-block Time (SMES) Take-off Time (TFMS) Project wheels-up time (SMES) Target Time for Movement area entry (SMES) Surface movement data (SMES) Boundary Crossings (TFMS) Flight Track Position Reports (TFMS) Oceanic Track Position Reports (TFMS) Amendment to Flight Plan (SFDPS) Altimeter setting (SFDPS) Special Activity Airspace (SFDPS) Hold information (SFDPS) Terminal Flight Track Position Report (TAIS) Notification of Arrival of a Flight (SFDPS) STARS data (TAIS) RVR (TAIS) Arrival Time (TFMS) Notification that no additional reports will be received for a flight (SFDPS) Arrival Departure En route Push Back / Taxiing Out Take-off / Departure Landing / Taxiing In Pre-Flight Cruise / En route / Oceanic Approach

Current State: NAS Operations Flight information received by combination of airline schedule data & filed flight plans Information is supplemented by departure and arrival messages, position reports etc. Information usually not updated until after the fact, creates a lack of awareness throughout the system, resulting in trajectories which are not always current Airspace User is unsure of the actual departure and arrival time which negatively impact gate assignments, passenger connections, crew and aircraft rotations Airspace User, airport and ATC planning is negatively affected due to lack of accurate position reports and times ATC Is monitoring aircraft track Has latest arrival time Has updated TMI which may be causing delays Does not have immediate access to airline filed delays AOC May not have current track Is not provided with updated arrival times Must file delays manually with DLA message Is not alerted to holding, metering, fix balancing or in trail restrictions. Arrival The intent of this slide is to help drive engaged discussion to identify the range of considerations in the current state We want to be sure we capture the hottest issues to the community for the written use case, and reference for future exchanges Landing / Taxiing In September 7, 2018

Problem Statement Present State Aircraft departs on Time ATC is receiving live updates on aircraft while AOC experiences a delay in obtaining current information Updated arrival times are continually created based on factors affecting flight Aircraft arrives per time predicted by ATC Departure En route Arrival ATC Perspective Aircraft departs on Time AOC receives delayed information from ATC and may not be aware of updated arrival times Aircraft arrives later than planned AOC works to reallocate ground resources to handle late aircraft Backup on taxiway due to unplanned congestion in non movement area causes delay on ground Departure En route Goal is to have engaged discussion around the problem to determine root cause Want to engage the producer to help reflect a common understanding of the problem we’re seeking to solve Arrival AOC Perspective Pre-Flight Push Back / Taxiing Out Take-off / Departure Cruise / En route / Oceanic Approach Landing / Taxiing In September 7, 2018

New Reality Based on New Information Service Future State Aircraft pushes back AOC receives notification of aircraft pushback AOC receives updated surface movement, surveillance data and estimated departure time AOC receives departure time AOC receives continuously updated schedule route and aircraft position data Delay information, route, speed, altitude changes are communicated as they happen. Changes to SAA activity are communicated in real time. International flight data available AUs will have clear picture of flow programs (metering, fix balancing, MIT, etc.) impacting arrival time AOC is able to reallocate ground resources as needed based on accurate flight information Airport staff are able to better plan for identified delays Surface congestion is minimized Departure En route Arrival Slide intended to show what happens with getting access to data What does ATC/AOC operations look like, generally, with access to this new data Slide shows how the information service, with all the data elements, is now available and what the implications are It may be of value to coordinate this slide with a POC @ producer Pre-Flight Push Back / Taxiing Out Take-off / Departure Cruise / En route / Oceanic Approach Landing / Taxiing In September 7, 2018

Future State: Future NAS Operations Once flight pushes, information continually shared so all users have same updated data Airline schedules & flight plan information will be continuously updated via SWIM with current schedule, route and aircraft position data and sent to ATC / airports Collaboration with ATC will be improved because Airspace Users, Airport and ANSP all have the same accurate picture to manage resources As changes occur during flight (e.g., route changes, speed and altitude changes, SAA, etc.), updates continue to be shared with Airspace Users & airports Airspace Users planning for gate usage, fleet management, crew resources is improved with precise arrival data Airport planning will improve with current operations picture for traffic using airport Slide intended to show what happens with getting access to data, as it pertains to the specific operation we’re talking about This describes the operation in the future, now with access to data September 7, 2018

Benefits of Improved Flight Data Improved Flight Data and Sharing of information with stakeholders will allow Airspace Users and airports to know precisely when aircraft will depart and arrive. This enables: Improved decision making concerning aircraft fuel efficiency Improved diversion management Improved gate management Improved flight crew management Improved ground crew management Improved delay management Improved fleet management Improved customer experience Improved TFM system performance Improved airport effectiveness This slide is intended to identify the anticipated benefits associated with our understanding of the solution Goal is to identify some way to validate the magnitude of the improvement seen with the benefit Intent of this slide is to validate these and identify whether there are additional benefits not identified here September 7, 2018

Many Objectives, One Mission: Flight Information Data Driven Real-time Decisions & Post-Ops Analysis Air Traffic Control: Responsible for safe and efficient use of airspace, maximizing airspace use and runway efficiency Success is defined by maximum use of runways and airspace, effective strategic planning, and minimal use of tactical interventions that add delay to flights Airline Flight Ops: Responsible for ensuring regulatory compliance, ensuring on-time operations, managing gate and crew resources, maintaining flight schedules, fleet management, and applying the airline business model Success is defined by predictable on-time operations, adherence to schedules, effective gate, crew, and fleet management. End result is a positive customer experience. Airports: Provide a safe environment for flight and surface operations, provide ramp control, ensure airport resources are available (runways, taxiways, ramps) at times that meet Airspace Users and ATC requirements. This identifies the metrics and initiatives they identified for us during the first meeting, that could be addressed this solution I want them to see how we’re linking what’s important to them to what we’re providing them with the data sets September 7, 2018

References SWIFT Focus Group Website http://connect.lstechllc.com/index.cfm/main/opconfocusgroup Next meeting will be October 25th, 2018 Will review Flight Use Document Please have Flight SMEs available for comment Contacts Jay Zimmer (jay.zimmer@lstechllc.com) Felisa White (felisa.white@faa.gov)

Backup

Relevant Definitions Service Data Service Business Service A mechanism to enable access to one or more capabilities, where the access is provided using a prescribed interface Data Service A service which provides access to source data Business Service Business function or capability offered as a service Functionality delivered to business/operational decision-makers Information Service A service which provides tailored access to data or information defined by a set of user configurable rules

TFMS-Flight, STDDS-SMES/TAIS, SFDPS-Flight/General Flight Data Flight Data is comprised of data from a variety of systems but the main source of input data is En Route Automation Modernization (ERAM). TFMS, SMES, TAIS, TFDM and TBFM have a consolidated view of the entire system and adds value to that information. The resulting output is an accurate reflection of the state of the NAS in terms of traffic flow management. Flight Data is sent as it is updated, when there is a commanded change, or when there is a computed change. Message Name Description Track Information Track Information messages are used to provide a position update for the identified flight. In cases where the track position causes a route re-conformance (trajectory modeling) additional route data is provided. The messages are transmitted as received by TFMS on a cyclic basis. Flight Plan Amend Information The flight Plan Amendment message provides revised flight plan data as the result of a flight plan being successfully amended. Arrival Information Arrival Information Message is used to provide arrival date and time information for all eligible arriving flights. Departure Information The Departure information messages is transmitted for all eligible initially activated flight plans. Flight Plan Information The Flight Plan Information Message is used to provide flight plan data for all eligible flight plans. Flight Plan Cancellation Flight Plan Cancellation messages are used to provide cancellation data for all eligible flight plans when a cancel message is received from the Host/ERAM or IADE interface or an operator action associated with the schedule database that causes previously Schedule Activated flights inserted into the NCSM to be canceled. Boundary Crossing Update Boundary Crossing Update is used to provide TFMM with current flight plan information on active eligible flights that are inbound from one ARTCC to another ARTCC facility. Oceanic Report Oceanic Report Type provides flight information for transoceanic flights and is generated when an Oceanic Position Report is received via NADIN. Special Activities Airspace The SAA message provides schedules and status of SAA activity General Information A general information message is used to communicate a free-form text message and remarks. Hold Status Information The Hold Status Information message provides hold information (holding fix, and estimated fix departure time for definite-duration holds) on all active aircraft STARS data STARS status sent periodically (nominally every 60 seconds) and upon change of any published fields