12/01/2011 FEDERAL AVIATION ADMINISTRATION AIR TRAFFIC ORGANIZATION 1 Execution of Flow Strategies (XFS) (aka Go Button)

12/01/2011 FEDERAL AVIATION ADMINISTRATION AIR TRAFFIC ORGANIZATION 2 XFS Purpose Primary Purpose: –To reduce the Traffic Manager and controller workload associated with issuing TFM generated reroute amendments for both predeparture and airborne flights. The TMC at the TMU can issue routes directly from the TSD. TFMS will send new messages directly to ERAM to implement the new routes. This should reduce errors as well. Secondary Purpose: –Inhibit ERAM automation from applying automated adapted routes (e.g., PARs) that “mess up” the reroute. Define a protected segment, the portion of the route that is important to follow for traffic management reasons. –Indicate to the en route controller that a flight is part of a reroute. Display a TMI ID in the inter-facility remarks field. Display the protected segment to the controller

12/01/2011 FEDERAL AVIATION ADMINISTRATION AIR TRAFFIC ORGANIZATION 3 Predeparture Reroutes Currently, when the need arises, TMs will issue ‘Reroute Advisories’ –Reroute advisories require airspace users to file a particular route between certain city pairs RAP J158 >ABR CEESNA JUVAG VIXIS YYZ< GOPEV Protected Segment: Route segment that is not to be modified by en route controllers or ERAM adaptation. Route segment that will be evaluated for route conformance in Reroute Monitor.

12/01/2011 FEDERAL AVIATION ADMINISTRATION AIR TRAFFIC ORGANIZATION 4 Predeparture Reroutes (cont’d) However, some airspace users do not file the correct route or do not amend a previously filed route to become compliant with the reroute advisory. Predeparture XFS provides a new function in TFMS to allow a TMC to electronically send a reroute amendment to ERAM for those flights that are non-compliant with a reroute advisory. Select any number of eligible flights and use the right-click “Generate Amendment” option

12/01/2011 FEDERAL AVIATION ADMINISTRATION AIR TRAFFIC ORGANIZATION 5 Predeparture Reroutes (cont’d) TFMS software for this function was delivered in Requires full deployment of ERAM release 3 to be used operationally. DataComm DCL service will allow the reroute clearance to be delivered directly to the cockpit. Exploring possible extension to prototype TFM tools such as Integrated Departure Route Planner (IDRP).

12/01/2011 FEDERAL AVIATION ADMINISTRATION AIR TRAFFIC ORGANIZATION 6 Airborne Reroutes Airborne rerouting concept for 2014 –Step 1 – Congestion predicted requiring action (e.g., reroutes and/or ground delays). –Step 2 – TMCs collaborate on congestion resolution. –Step 3 – Candidate resolution options are evaluated and one is selected. –Step 4 – TMC coordinates with FLMs and distributes reroutes to ATC automation (i.e., ERAM). –Step 5 – Reroute notification are sent to the controller for delivery. –Step 6 – Controller issues clearance via voice and amends flight plan. –Step 7 – Rerouted flights are monitored for conformance to reroute TMI. –Step 8 – If necessary, reroutes are modified or cancelled.

12/01/2011 FEDERAL AVIATION ADMINISTRATION AIR TRAFFIC ORGANIZATION 7 Airborne Reroutes (cont’d) HELAM Play: VHP Brickyard Portion of Reroute = Protected Segment AAL1406 Original Route

12/01/2011 FEDERAL AVIATION ADMINISTRATION AIR TRAFFIC ORGANIZATION 8 Airborne Reroutes (cont’d) Current Status –Held storyboarding meeting and demo earlier this year at Mitre. –2 nd demo scheduled for 12/13. –LM to complete hi fidelity prototype and requirements in 2012 –TFMS and ERAM development to start in 2013 –ERAM changes are currently part of ERAM release 4