S2K 7

1
S2K7
Spring 2007ICR(Integrated Collaborative
Rerouting)andDynamic AFPs
2
S2K7 Training for Industry

• This presentation is primarily for Industry ATC
  Coordinators.
• The intent of this presentation is to inform and
  to bring an awareness of changes to procedures
  and technology that will effect you and the NAS
  starting this spring (2007).
• This presentation probably includes more
  information than you would normally need to teach
  a class so feel free to edit as necessary to meet
  the needs of your class. Consult with ATA (Jeff
  Miller) before changing any slides that pertain
  to policy, procedure or guidelines.
  jmiller_at_airlines.org. NBAA contact Ernie
  Stellings at estellings_at_nbaa.org.
• You will need to strip this presentation down
  before presenting to Dispatchers. If time
  permits I will develop a Dispatcher friendly
  presentation and have Paul Eure and Jeff Miller
  upload it to the training websites.
• I have included 3 additional ppts to introduce
  Adaptive Compression and explain changes to the
  TCA Website and Playbooks.

Check CDM WEB for updates http//cdm.fly.faa.gov/T
raining/S2k7.html
3
Industry Training
4
Industry Training
5
S2K7 Training for Industry

• Review of S2K6
• AFP vs. GDP in Support of SWAP
• Canned and Dynamic AFPs
• ICR (Integrated Collaborative Rerouting)
• ICR Guidelines
• ICR Best Practices
• ICR Automation Enhancements
• ROG (Route Options Generation)
• AFP / ICR Checklists

• Adaptive Compression
• OIS Page Enhancements
• Playbook Changes
• ATCSCC Position and Responsibility Changes
• Dates of Note

6
Review of last years S2K6The Introduction of
AFPs

• AFPs on average
• Implemented 3 hours in advance
• Duration 6 hours
• Canceled 2 hours early
• Less than 1 Revision per AFP.

7
OPSNET Delay Minute Comparison
8
FSM EDCT, Ground and Arrival Delay
9
Total AFP flights by Departure Center
10
2005 VS. 2006 (March 01 Aug 31)
Number of Advisories
RQD Playbook Advisories RQD Playbook Advisories RMD Playbook Advisories RMD Playbook Advisories FYI Playbook Advisories FYI Playbook Advisories
COUNT Ave Duration COUNT Ave Duration COUNT Ave Duration
2005 1088 (231) 256 79 (0) 600 6 (0) 343
2006 742 (38) 253 252 (120) 632 33 (0) 455
2006 CHOKEPOINTS 38 as RQD CHOKEPOINTS
Advisory 120 as RMD CHOKEPOINTS Advisory
2005 CHOKEPOINTS 15 as CHOKEPOINTS
Advisory 216 as FCA
11
New Acronyms

• AFP Airspace Flow Program
• ICR Integrated Collaborative ReRouting
• NESP - National Enroute Spacing Position
• NSST National System Strategy Team
• ROG Route Options Generation

12

• Goals for S2K7

• Reduce Departure Delays
• Improve Delay Management Techniques
• Increase electronic interaction with decision
  support tools
• Reducing the number of required reroutes
• Respond to changing constraints with more
  flexibility
• Give users options and incentives to reduce
  demand in constrained areas.

13
Solutions for S2K7

• Create AFP flexibility
• Additional Canned AFPs
• Dynamic AFPs
• Allow users to file their own routes around a
  projected constrained area based on best business
  decisions.
• ICR (Integrated Collaborative Rerouting)

14
Canned and Dynamic AFPs
15
Naming Process for AFPs

• Canned AFPs from 2006 will continue with the
  same names, i.e., FCAA01 thru FCAA06 FCAA08.
• The naming convention for Canned and Dynamic AFP
  will use a format of FCAxxx, the FCA portion is
  required, Characters 4 5 will normally be the
  last two of the primary center for the AFP.
• Example ZID would be ID. The last character
  will be a number. So a FCAID1 would indicate
  that the AFP is located primarily in ZID ARTCC.
  Some portions of the AFP may extend into
  adjacent centers.

16
Where to view AFPs

• RMT/ROG AFPs can be displayed on the RMT Map.
• Type the FCA name in Show/Hide Overlays or Show
  Overlay Elements
• Active AFPs can be selected in ROG
• FSM Use the FSM Map feature to view the location
• CCSD Select the FCA in the FEA/FCA pulldown menu
• OIS Using the OIS, click the hotlink on the
  Control Element name, a map is shown below the
  advisory showing the graphical location of the
  AFP. This is a regional view.

17
RMT Map
18
FSM Map
19
OIS Control Element
20
CCSD Map
21
The flight is filed through/around an AFP and
wants a reroute?

• When the flight is on the ground and routed out
  of an AFP the delay is removed in the ETMS, the
  flight will receive an updated EDCT that will
  reflect a control time equal to the flights
  Proposed time (P-time), or the current time if
  after their P-time.
• With AFPs, recommended routes are published to
  assist pilots/dispatchers in filing routes to
  avoid the AFP. These are primarily between major
  hubs these routes may not always have
  transitions to all satellite airports. (ROG can
  help with this)
• With a flight that is airborne, ATC will try to
  keep them on their filed route as much as
  operationally possible. It is understood that
  changes in routes will impact the AFP if a flight
  is filed around the AFP and the route change then
  takes the flight through the AFP.
• Pilots need to coordinate with Dispatch before
  deviating from filed flight plan

22
New Canned AFPs Mid-Continent Line Segments
23
Canned AFPs

• 11 New Canned AFPs have been added to last years
  Classic Canned AFPs
• 5 Mid-Continent Lines
• 3 ZID Polygons
• 3 ZME Lines encompassing ZME

24
Mid-Continent Line Segments

• Series of connected FCA lines from Canada to Gulf
  of Mexico
• Developed to be used with playbook routes
• North, South, East and West traffic can be
  included
• Multiple implemented AFP to provide choices to
  customers on route vs. delay
• Designed around sector/center boundaries and
  specific flows

25
Mid-Continent Line AFPs

• Series of connected FCA lines from Canada to Gulf
  of Mexico
• Filtered for all traffic except
• ZEU/ZPA/ZSA/ZMX Arrivals
• Adjacent ARTCC
• ARTCC filtering will be adjusted based on
  impacting event proximity to the AFP
• Altitude Filters 180-410
• Developed to be used with playbook routes

26
New Canned AFPs ZID
27
FCAID7

• Filtered for all traffic except
• ZEU/ZPA/ZSA/ZMX Arrivals
• ZID Departures
• ZID would control internal departures with
  weather impact
• Altitude Filters 180-410
• Impacted routes
• J6/J42 Traffic between NE and ZFW/ZHU/ZME
• J89/J85/J43 Traffic between ZTL/ZJX/ZMA and
  ZOB/ZAU
• Typical Playbook Routes for consideration for AFP
  Avoidance
• Partial OXI/OKK, MDW BVT
• No J6
• VUZ/MGM
• VHP
• CVG JAVIT

28
FCAID8

• Filtered for all traffic except
• ZEU/ZPA/ZSA/ZMX Arrivals
• ZID Departures
• ZID would control internal departures with
  weather impact
• Altitude Filters 180-410
• Impacted routes
• J80, J29
• J89/J134 ZTL/ZDC/ZJX/ZMA to ZAU/ZMP
• ZAU Departures thru ZID
• DTW Departures via FWA/ROD
• SW to DTW/CLE
• STL Option of Chokepoints
• West to DC Metros/DC Metros to West
• West to CVG/CVG to West
• Typical Playbook Routes for consideration for AFP
  Avoidance
• MIZAR
• CAN 1
• OXI/OKK, MDW BVT
• Partial EAU

29
FCAID9

• Filtered for all traffic except
• ZEU/ZPA/ZSA/ZMX Arrivals
• ZID Departures
• ZID would control internal departures with
  weather impact
• Altitude Filters 180-410
• Impacted Routes
• J80, J29
• J89/J134 ZTL/ZDC/ZJX/ZMA to ZAU/ZMP
• ZAU Departures thru ZID
• DTW Departures via FWA/ROD
• SW to DTW/CLE
• STL Option of Chokepoints
• Typical Playbook Routes for consideration for AFP
  Avoidance
• OXI/OKK, MDW BVT
• EAU
• MIZAR
• CAN 1
• CVG SHB

30
New Canned AFPs ZME
31
ZME FCA/AFPs

• Designed with segmented lines
• Along the ZME boundary
• Reference to Sector boundaries when possible
• Allow for change in size by removing line
  segments
• This will cause flights to show as route out
  flights if changes made after the area is made an
  FCA

32
FCAME8

• Filtered for all traffic except
• ZEU/ZPA/ZSA/ZMX Arrivals
• Altitude Filters 180-410
• Impacted routes
• DFW BYP Arrivals
• ATL ERLIN Arrivals via MEM
• ATL To ZDV/ZLC/ZOA/ZSE
• MEM Traffic To/From West
• Traffic Between ZAU/ZHU
• J6 To West Coast
• Typical Playbook Routes for consideration for AFP
  Avoidance
• DFW BYP
• Partial ATL ERLIN
• Partial ELP/EWM For ZTL To ZLA/ZAB

33
Can be broken into segments
34
FCAME7

• Filtered for all traffic except
• ZEU/ZPA/ZSA/ZMX Arrivals
• Altitude Filters 180-410
• Impacted routes
• J6/J42 Traffic between NE and ZFW/ZHU/ZME
• ZOB/ZID To ZME/ZFW/ZHU
• ATL ERLIN Arrivals
• ZAU J73 Departures
• SW to DTW
• CVG Arrivals From SW
• Typical Playbook Routes for consideration for AFP
  Avoidance
• VUZ/MGM
• Partial IIU or VHP
• Partial BYP
• Partial DAS
• ATL ERLIN

35
FCAME6

• Filtered for all traffic except
• ZEU/ZPA/ZSA/ZMX Arrivals
• Altitude Filters 180-410
• Impacted routes
• DFW CQY Arrivals
• DFW East Departures
• IAH/HOU Arrivals via DAS
• IAH/HOU J101 Departures
• ATL Arrivals via HONIE
• ATL West Departures
• Typical Playbook Routes for consideration for AFP
  Avoidance
• DFW CQY
• IAH/HOU DAS
• ATL HONIE

36
Dynamic AFPs
37
Dynamic AFPs
Like a snow flake,no two constraints are
alikeergo Dynamic AFPs
Quote by Curt Kaler Father of the Playbook
Routes
Because NAS Constraints are not consistent we
have to have flexibility in the placement of
FEA/FCAs.
38
AFP Guidelines (1)

• No more than three domestic AFPs will be active
  simultaneously without approval of the NOM.
• Dynamic AFPs will be created early enough to
  allow airlines to protect slots for
  cancellations.
• Discussions will be held the night before and
  FCAs created for potential AFP events expected
  during the early morning hours of the next day.
• Discussions will be held during the early morning
  and FCAs created for potential AFP events
  expected during the afternoon hours of the same
  day.
• A minimum of three hours notice must be provided
  prior to activating an AFP. The initial
  development of the FSM-eligible FCA will be
  considered the three hour notification.

39
Dynamic AFP Guidelines (2)

• The NESP and others will discuss and consider the
  judicious use of filters to provide flexibility
  and to maximize the overall NAS operations.
• Altitude limits will regularly be discussed as
  options.
• NESP will be cognizant of potential increases in
  EDCTs with Dynamic AFPs and the distribution of
  EDCTs to more and different airport towers as
  AFPs are planned and implemented.

40
AFP Best Practices

• Airspace constraints will be the main reason for
  considering an AFP
• Do not use for terminal issues use GDPs.
• Select seasonal volume issues may be solved with
  an AFP.
• All FCAs that may become AFPs should be drawn
  with either lines or polygons.
• Filters will be used rather than exemptions
  whenever possible.
• Major airports in the immediate AFP area will be
  filtered out most of the time and managed with
  other TMIs (ESP, MIT, etc.)
• Each AFP will have to be approved by one of the
  five National Operations Managers (NOMs) at the
  ATCSCC prior to implementation.
• This will mitigate the concern that to many FCAs
  may be considered for AFPs on any given day.

41
ICRIntegrated Collaborative Rerouting
42
Phased ICR Implementation

• This Spring we are implementing Phase 0
  Initial ICR. Initial ICR lays the foundation
  for Electronic Negotiation which will be used
  in the future. In the future, using Electronic
  Negotiation, the customer will be able to
  request routes in priority order and the system
  will respond identifying the best opportunity for
  the customer to get the best possible route
  requested.
• Proposed Phased ICR Implementation
  Strategy
• Phase 0 (Initial ICR - Spring 2007)
• ETMS Enhancements
• Customer preference via Early Intent
• Route Option Generation (ROG) in RMT
• Phase 1
• Additional ETMS Enhancements
• Future Traffic Display (FTD) with current traffic
  only
• Phase 2
• Basic Reroute Modeling
• Future Traffic Display (FTD) with reroutes
• Phase 3
• Customer preference via Constraint Resolution
  Intent (CRI)
• Full ICR including FCAs with modeled traffic

43
What is ICR?
Submitting Early Intent before the RQD advisory
is implemented could avoid longer RQD reroutes.

• Built on Planning Advisories, current FEA/FCA
  procedures, Early Intent (EI) and Reroute Monitor

44
New Elements of Initial ICR

• Planning (PLN) Route Advisory with reroute
  guidance for customers
• ROG capabilities in RMT which identify
  pre-coordinated reroute options that avoid
  constraint
• Customer reroute preferences submitted via Early
  Intent, filing, or refiling
• Use of Reroute Monitor to identify whether
  flights follow advisory guidance

45
ICR Benefits

• Users will get information earlier through PLN
  advisories
• Users that send in EI (Early Intent) will have a
  better chance of receiving the EI reroute.
• Early Intent will give more accurate data on
  traffic demand around the projected constrained
  area. (It is recognized that the effectiveness of
  Early Intent will be limited due to automation
  constraints)
• Even the basic use of ICR could greatly reduce
  the use of traditional Required Reroutes

46
Integrated Collaborative Rerouting (ICR)

• Provides enhancements to current rerouting
  process
• Improves communications and coordination
• Incorporates customer preferences where possible
• Builds on and extends Planning Advisories, Flow
  Constrained Areas (FCAs), Early Intent (EI),
  Reroute Monitor
• Developed by Future Concepts Team (FCT) of
  Collaborative Decision Making (CDM) group

47
Why ICR?

• Customers have more input into how their flights
  are routed
• Customers have more incentive to be proactive
• Customers have better understanding of
  alternatives acceptable to traffic management
• Customers make fewer exception requests
• Traffic Managers have fewer flights to reroute
• Traffic Managers do fewer tactical reroutes
• Traffic Managers get earlier feedback on impact
  of reroutes on customers and sectors
• Improved traffic predictability

48
Incentive for Early Intent

• Better opportunity to fly around constraint
  before less desirable required routes are
  implemented.
• Avoid being held on the ground waiting for
  reroute.
• Mitigate risk by being proactive and submitting
  EI around Planned (PLN) FEA.
• Less likelihood of having to ask for a routing
  exception through the TCA Desk.

49
Background

• FCT conducted three full ICR storyboard
  evaluations and three human-in-the-loop (HITL)
  exercises in FY05
• Published operational concept and requirements
  documents for full ICR (FCT web page)
• Defined phased implementation strategy for ICR
• Conducted two HITLs for Initial ICR (Dec 2005,
  Jan 2006)
• ETMS and Route Management Tool (RMT) requirements
  defined for ETMS 8.3 and RMT 1.40
• Published operational concept document for
  Initial ICR (FCT web page)
• Transitioned Initial ICR concept from FCT to
  joint FCT/FET Implementation Team

50
Initial ICR Concept Overview
51
Traffic Managers Define Constraint

• Create Flow Evaluation Area (FEA) to define
  geographical area of concern with appropriate
  altitude and time limits, plus any other relevant
  filters
• Share FEA for coordination with other traffic
  managers
• Review FEA list and examine traffic expected to
  be affected by this constraint
• Determine whether reroutes will be necessary
• If not, then ICR process is not appropriate

52
Traffic Managers Define Recommended Route Guidance
Constraint Sharing

• Provide customers with a better understanding of
  operationally acceptable routes given current
  constraints
• Identify candidate routes to recommend to
  customers
• May use Route Options Generation (ROG) and Create
  Reroute search capabilities to identify Coded
  Departure Routes (CDRs), Playbook plays, or play
  segments that avoid FEA

53
Traffic Managers May Use ROG Reroute Planner to
Identify Applicable Plays
54
PLN Advisory is issued with suggested Routes
_ICR/PLN indicates opportunities for Early Intent
FEAKC1
FEAKC1
Suggested routes that help NAS coordination
REMARKS ALL FACILITIES AND CUSTOMERS TAKE NOTE
THAT THE ICR PROCESS IS IN EFFECT FOR FEAKC1_ICR.
EARLY INTENT WINDOW EXPIRES AT 2030. FLIGHTS
LEFT ON THE FEA LIST WILL BE ROUTED BY THE FAA
VIA THE TRADITIONAL REROUTE PROCESS TO AVOID THE
FEA. CUSTOMERS ARE ENCOURAGED TO AVOID
FEAKC1_ICR VIA THE USE OF UPT OR ANY OF THE
FOLLOWING ROUTES JOT 2BNAVUZ
FEAKC1
FEAKC1
55
Customers Examine Affected Flights

• View Reroute Monitor for list of flights affected
  by advisory
• Reference recommended route guidance available
  for each flight

Scheduled route different than route options for
USA742
Scheduled flight, Unknown Reroute Status
Route guidance shows PLN prefix
56
Customers Choose Whether To Respond
Generating/Analyzing
Reroute Options

• Have option of submitting preferences for their
  affected flights
• Can plan ahead for reroute (analyze and determine
  best reroute option for each flight)
• fuel
• priority passenger connections
• aircraft performance capabilities/limitations
• Can reduce tactical workload/potential diversions
• Increases probability of being able to fly what
  is filed (increased predictability)
• May use ROG capabilities, as well as other
  automation and information, to find acceptable
  reroutes that avoid the constraint

57
Customers use Reroute tools to select a route
Preference

• ROG (Route Options Generation) is a new tool that
  can identify route options around the FCA.
• (Projected to be deployed mid-late April.)

58
ROGRoute Options Generation
59
This slide is a video of ROG. Click gray area.
It may not work on your computer
60
Customers Select Preferences
Generating/Analyzing
Reroute Options
61
Customers Select Preferences
62
Customers Select Preferences
ROG
63
Customers Select Preferences
ROG
Right Click in the Route String and copy from ROG
then paste in CCSD Early Intent Window
64
Customers Submit Preferences
Customers Submit Preferred Routes
via Early Intent

• For flights that do not yet have filed flight
  plan
• Submit Early Intent (EI) message
• File a flight plan
• Refile for flights that already have flight plans
• Flights without preference submitted will be
  assigned route by traffic management

65
Customers Submit Preferences via Early Intent
Message
Customers Submit Preferred Routes
via Early Intent
66
Customers Submit Preferences via Early Intent
Message
Customers Submit Preferred Routes
via Early Intent
Route can be copied from ROG and pasted into
Early Intent New Route text box.
67
Traffic Managers Examine Customer Preferences and
Their Impacts
Evaluating System Impacts

• Review customer preferences on Reroute Monitor
• Early Intent route replaces historical route (N
  prefix is displayed on departure time)
• Preferences labeled to indicate their conformance
  with route guidance
• Conforming (C) Routes that follow route guidance
• Non-conformant (NC) Routes that do not match
  the route guidance
• Define monitoring FEAs to analyze impact of
  rerouted flights on airspace around constraint as
  necessary

68
Reroute Monitor After Customer Preference
Submitted
Evaluating System Impacts
69
Traffic Managers Examine Sector Count and Alert
Data
Evaluating System Impacts
70
Traffic Managers Address Impacts
Evaluating System Impacts

• Coordinate any desired adjustments to final route
  advisory with Command Center
• May take tactical actions after final route
  advisory is issued to handle other individual
  flight-specific customer preferences that cause
  local flow problems

71
Traffic Managers May Use ROG Reroute Planner on
Remaining Flights
72
Traffic Managers Assign Routes for Remaining
Flights
Evaluating System Impacts

• Assign routes to flights that do not avoid FEA
• Identified by analysis of demand using ETMS and
  ROG capabilities
• Defined in Create Reroute
• May be different than route guidance in PLN Route
  Advisory
• May include route segments added for flights with
  no available pre-coordinated routes

73
National Traffic Manager Issues RQD Route
Advisory
Implementation and Monitoring

• Issue RQD Route Advisory indicating assigned
  routes for flights still affected by constraint
• Customer preferences that take flights out of FEA
  are not affected
• For RQD Route Advisory, FEA is converted to
  public FCA

Required, based on FCA
Assigned routes on Reroute Monitor
74
ATCSCC ADVZY 022  05/05/2004 FCA001_ICR/RQD
Route is now Required. Early Intent window is
closed.
MESSAGE 
NAME PUBLIC FCA001 CONSTRAINED AREA FCA THROUGH
ZKC and ZAU REASON TSTMS INCLUDE TRAFFIC
ARRIVING ZDC, ZNY, ZBW FACILITIES INCLUDED ALL
FLIGHT STATUS ALL VALID FEA ENTRY TIME - FROM
1900 TO 2059 FLIGHTS IMPACTED SEE ATTACHED
FLIGHT LIST ALL FACILITIES AND CUSTOMERS TAKE
NOTE THAT THE ICR PROCESS IS IN EFFECT AND THIS
ADVISORY LINKS TO PLN ADVISORY FCA001_ICR. SEE
REROUTE MONITOR FOR FLIGHT-SPECIFIC
ROUTES. MODIFICATIONS CUSTOMERS ARE ADVISED TO
REFERENCE REROUTE MONITOR FOR POTENTIAL
MODIFICATIONS TO SUBMITTED EI ROUTES. DEFAULT
ROUTES JOT 2 BNA VUZ ASSOCIATED
RESTRICTIONS MODIFICATIONS
These routes will now be Required.
051900 052059
EFFECTIVE TIME 
04/05/05 1700  
SIGNATURE 
75
Traffic Managers and CustomersImplement and
Monitor Reroutes

• Traffic Managers and Customers
• Observe assigned routes on Reroute Monitor
• Customers file assigned routes or request
  exceptions via current exception process
• Traffic Managers and Customers
• Monitor updates to sector and FEA demand as
  assigned routes are filed
• Local Traffic Managers
• Monitor effects of reroutes and resolve any
  negative impacts tactically

76
ICR Best Practices

• Use ICR whenever conditions impact the en route
  environment to the point where reroutes may be
  necessary to manage the situation to provide
  maximum customer flexibility and increased
  predictability.
• Provide flexible route guidance and multiple
  options to spread the impact of the reroutes and
  reduce the need for additional restrictions, such
  as MIT.
• Accept customer-submitted preferences whenever
  possible without adverse impact on workload.

77
ICR Guidelines (1)

• Public FEAs should be created early enough to
  enhance customer flexibility and awareness in
  conjunction with managing the impact.
• Discussions will be held when appropriate and
  public FEAs created for potential ICR events
  expected during the next several hours.
• Issuing the PLN advisory early, with the shared
  understanding that all flights on the FEA flight
  list will be rerouted, gives the customer both
  the opportunity and the incentive to submit route
  preferences for their affected flights
• A minimum of 1 hour notice/30 min Early Intent
  window must be provided prior to activating the
  ICR process. The initial development of the FEA
  and publication of the PLN advisory will start
  the notice period.

78
ICR Guidelines (2)

• Depending on the severity of the situation, the
  route guidance may be Plays, CDRs, routes or
  recommendation to avoid the area by routing
  around the FEA (UPT).
• The filters will be discussed and used to ensure
  the minimum number of flights necessary are
  affected by the reroute requirements.
• Altitude limits will regularly be discussed as
  options
• Airports close in to the impacted area will be
  the first considered for exemptions
• ICR events are expected to be smaller in size and
  shorter in duration than AFPs (typically 2-3
  hours).

79
New Elements of Initial ICR

• Planning (PLN) Route Advisory with reroute
  guidance for customers
• ROG capabilities in RMT which identify
  pre-coordinated reroute options that avoid
  constraint
• Customer reroute preferences via Early Intent,
  filing, or refiling
• Use of Reroute Monitor to identify whether
  flights follow advisory guidance

80
When will AFPs, ICR be triggered?

• Trigger Rational
• Due to existing ICR/AFP Automation/Implementation
  Concerns, the implementation team agreed that ICR
  and AFPs will NOT normally be used on the same
  day.
• Discussion will be held the evening before (on or
  before the 915 PM Planning Telcon) for en route
  constraints expected to impact morning traffic
  and/or early in the morning (on or before the 915
  AM PT) for constraints expected to impact
  afternoon and evening traffic.
• Weather, volume and other factors will be
  reviewed to determine if the event/impact will
  be
• Large scale in terms of geographical extent and
  duration, requiring ground delay/AFP or
• Smaller scale either geographically or time
  horizon and can be managed with a less
  restrictive ICR or a required reroute. ICR events
  are expected to be smaller in size and shorter in
  duration than AFPs (typically 2-3 hours).

81
AFP/ICR Decision Making Guidelines 07
ICR No ICR No ICR
FEA/ICR Canned AFP Dynamic AFP
Public FEAs Created As NeededPLN ADZY named _ICR with route guidance Planning Discussions/ FCAs Created Evening/Early AM Planning Discussions/ FEAs Created Evening/Early AM
Rerouting Events, Midwest, Texas, Southeast, ZMP, or other areas as appropriate Thunderstorms NE, SWAP Event, NAS-altering events in Midwest FCA Created by 915 AM (or Before) unless NOM approved
PLN ADZY Issued with no less than 1 hour lead time AFP Issued no less than 3 hours before start time AFP Issued no less than 3 hours before start time
Standardized ADZY text Standardized ADZY text Standardized ADZY text
Early Intent Recommended Early Intent Optional Early Intent Optional
82
AFP/ICR Decision Making Guidelines 07
ICR No ICR No ICR
FEA/ICR Canned AFP Dynamic AFP
Public FEAs Created As NeededPLN ADZY named _ICR with route guidance Planning Discussions/ FCAs Created Evening/Early AM Planning Discussions/ FEAs Created Evening/Early AM
Rerouting Events, Midwest, Texas, Southeast, ZMP, or other areas as appropriate Thunderstorms NE, SWAP Event, NAS-altering events in Midwest FCA Created by 915 AM (or Before) unless NOM approved
PLN ADZY Issued with no less than 1 hour lead time AFP Issued no less than 3 hours before start time AFP Issued no less than 3 hours before start time
Standardized ADZY text Standardized ADZY text Standardized ADZY text
Early Intent Recommended Early Intent Optional Early Intent Optional
83
AFP/ICR Decision Making Guidelines 07
ICR No ICR No ICR
FEA/ICR Canned AFP Dynamic AFP
Public FEAs Created As NeededPLN ADZY named _ICR with route guidance Planning Discussions/ FCAs Created Evening/Early AM Planning Discussions/ FEAs Created Evening/Early AM
Rerouting Events, Midwest, Texas, Southeast, ZMP, or other areas as appropriate Thunderstorms NE, SWAP Event, NAS-altering events in Midwest FCA Created by 915 AM (or Before) unless NOM approved
PLN ADZY Issued with no less than 1 hour lead time AFP Issued no less than 3 hours before start time AFP Issued no less than 3 hours before start time
Standardized ADZY text Standardized ADZY text Standardized ADZY text
Early Intent Recommended Early Intent Optional Early Intent Optional
84
AFP/ICR Decision Making Guidelines 07
ICR No ICR No ICR
FEA/ICR Canned AFP Dynamic AFP
Public FEAs Created As NeededPLN ADZY named _ICR with route guidance Planning Discussions/ FCAs Created Evening/Early AM Planning Discussions/ FEAs Created Evening/Early AM
Rerouting Events, Midwest, Texas, Southeast, ZMP, or other areas as appropriate Thunderstorms NE, SWAP Event, NAS-altering events in Midwest FCA Created by 915 AM (or Before) unless NOM approved
PLN ADZY Issued with no less than 1 hour lead time AFP Issued no less than 3 hours before start time AFP Issued no less than 3 hours before start time
Standardized ADZY text Standardized ADZY text Standardized ADZY text
Early Intent Recommended Early Intent Optional Early Intent Optional
85
ICR Automation Enhancements
86
Automation Enhancements

• ICR PLN and RQD Advisory Text
• CCSD Enhancements (ETMS 8.3)
• ETMS Trajectory Modeling
• Reroute Monitor Enhancements
• Early Intent Route Formatting
• RMT Enhancements (RMT 1.40)
• ROG (Route Options Generation) Tool

87
ICR PLN Advisory Remarks

• REMARKS All Facilities and Customers take note
  that the ICR process is in effect for FEAXXX_ICR.
  Early Intent window expires at XXXXZ. Flights
  left on the FEA list will be rerouted by the FAA
  via the traditional reroute process to avoid the
  FEA. Customers are encouraged to avoid FEA via
  the use of UPT or any of the following routes
• XXX (Plays, CDRs)

88
ICR RQD Advisory Remarks

• REMARKS All Facilities and Customers take note
  that the ICR process is in effect and this
  advisory links to PLN Advisory XXX. See Reroute
  Monitor for flight-specific reroutes.
• MODIFICATIONS Customers are advised to
  reference Reroute Monitor for potential
  modifications to submitted EI routes.
• DEFAULT ROUTES
• XXX

89
CCSD Enhancements for ICR

• ETMS Trajectory Modeling
• Replace Historical Route with Required Reroute
  (ETD will have an R prefix)
• Reroute Monitor Enhancements
• Reroute Prefix Indicates whether or not Reroute
  is RQD
• Retain FCA Dropouts when a reroute is re-issued
• Allow Spaces as Separators in Early Intent Route
• Draw Reroute Segment for Selected Flights

90
Replace Historical Routes with Reroute
Reroute status is still UNKN
R prefix for modeled flights.
Current route is constructed by ETMS.
If flight has multiple assigned routes, model on
the shortest.
91
Reroute Prefix Indicates if Reroute is Planned or
Required
Prefix indicates that this reroute is required
(RQD).
92
Retain FCA Dropouts when Reroute is Re-issued

• Description
• A dropout is when a flight routes out of the
  FEA/FCA.
• Retain FCA dropouts in the Reroute Monitor flight
  list when a reroute is re-issued. (Currently
  dropouts are removed from list when reroute is
  re-issued, even if they are non-conformant.)
• This way, when ICR Reroute is changed from PLN to
  RQD, the flights that dropped out during the
  planning stage can still be tracked.

93
Draw Reroute Segment for Selected Flights
Drawing Control Panel.
Select flights to draw.
94
Early Intent Route Formatting
Can use either spaces or periods (field 10
format) to separate elements in route string.
Routes can be cut and pasted from ROG
You may have to enter arrival station
95
RMT ROG Capabilities

• Route Options Generation (ROG) is a new component
  within the Route Management Tool (RMT)
• ROG allows FAA and Customers to quickly find
  pre-coordinated reroute options that avoid a
  constrained area, e.g., FEA/FCA
• FAA Traffic Managers could use ROG for
• Characterizing and understanding the
  constraint/flight list
• Coordinating and developing route guidance or
  reroute plans
• Finding reroutes for flights that do not remove
  themselves from the constrained area
• Customers could use ROG to find reroute options
  for their flights
• Preferences then submitted to the system
  initially through Early Intent
• RMT 1.40 New Features CBI and Users Guide will
  be available as part of the RMT 1.40 deployment

96
RMT ROG Flight-Centric View

• Allows FAA and Customers to identify reroute
  options for the specified flights that avoid an
  FEA or FCA
• Pre-coordinated route databases that are
  currently being searched include Preferred
  Routes, CDRs and Playbook Plays
• Various filtering and graphical selection
  capabilities are provided to narrow the list of
  potential options
• Route statistics, e.g. length, centers traversed,
  and CDR/Associated Play information, are provided
  as a reference to help select best reroute for
  the given situation
• Capability to define and save Ad Hoc reroutes
  for city pairs that do not have pre-coordinated
  routes is also provided.

97
ROG Tool (Initial version RMT 1.40)
98
ROG Find Options Dialog

• FAA and Customers can examine all reroute options
  that avoid the FEA/FCA or can filter the list
  using different search criteria
• The route databases are then queried to bring up
  the flight and route option details to help make
  the reroute assignments

99
ROG Constraint/Flight List Characterization
FAA and Customers can examine the flight list
using various grouping categories, e.g.
Departure/Arrival Airport, Departure/Arrival
Center, Departure/Arrival Time Bin, Flight
Status, Airline, Flight Stage Length
100
ROG Mapping Capabilities

• Departure Airports in red
• Arrival Airports in blue

• ROG mapping capabilities allow for improved
  common situational awareness and better
  understanding of the constraint/flight list
• The FEA/FCA definition, flights on the flight
  list, and departure and arrival airports with
  flight counts can be displayed on the map

101
ROG Flight-Centric View Preferences Selected for
Flights by City Pair (LAX PHL)

ROG provides flight and reroute option specific
information in both tabular and graphical format
102
Ad Hoc Reroutes Tool
Users can create and save frequently used Ad Hoc
Reroutes. This may be useful for city pairs
without pre-coordinated route options.
103
Scenario 1

• Using the CCFP, what actions plan would you
  propose?

104
Scenario 2

• Using the CCFP, what actions plan would you
  propose?

105
CHECKLISTS
106
AFP Checklist
107
AFP Checklist for AOC/GA

• Evaluate and analyze current and forecast
  convective weather
• Monitor CCFP (CCSD/www.fly.faa.gov)
• http//aviationweather.gov/products/ccfp/
• Review all other approved weather sources.
• Discuss with MET Department
• Participate in CCFP Chats (For carriers with met
  departments only).
• Evaluate demand
• Watch for FSM eligible FEA/FCA
• Current Ops Plan
• CCSD
• FSM Server Auto Monitor
• Monitor the throughput on FSM Eligible FEA/FCAs
• FSM

108
AFP Checklist for AOC/GA

• Develop and Evaluate TMI strategies
• Review Ops Plan
• Model (AOCs) at anticipated rates to determine
  possible impact and prepare for special telcon
  discussions.
• Review reroute options
• Use RMT ROG capabilities to view flight specific
  information including reroute options, route
  statistics, length, centers traversed and
  CDR/Associated Play information.
• ROG will list all shared and public FEA/FCAs
• Use RMT from ATCSCC OIS to view CDRs in PLN
  Advisory
• http//www.fly.faa.gov/Products/Coded_Departure_Ro
  utes/coded_departure_routes.html
• Use Playbook from ATCSCC OIS to view Plays in PLN
  Advisory
• http//www.fly.faa.gov/PLAYBOOK/pbindex.html
• Use in-house flight planning systems and/or
  navigation databases

109
AFP Checklist for AOC/GA

• Discuss with regional partners
• Identify strategic flights
• Discuss with ATA rep/GA desk
• Participate in AFP Telcon
• Participate in Ops Telcons
• Prepare Worksheet
• Submit Agenda Items (CDM participants)
• If AFP is the selected option
• Re-Model the program using the public FEA
• Set the start and end times
• Set the AAR for throughput and include the popup
  factor
• Note The default AAR must be set to the desired
  rate.

110
AFP Checklist for AOC/GA

• Set the scope
• Select Power Run
• Analyze the results of the Power Run information
• Plan mitigation including reroutes and subs/swaps
  to reduce delay.
• Participate in AFP Telcons
• Discuss current and forecast convective weather
• Discuss the demand throughput and options for
  managing it
• Develop preference regarding the final details of
  the AFP
• Discuss preference for routing out of the AFP, if
  alternate routes will be available

111
AFP Checklist for AOC/GA

• Watch for AFP to be issued
• Review advisory
• Review slot list
• Review Actual Parameters in FSM
• Coordinate internally on substitution and route
  out
• Disseminate EDCTs and reroute options
• Discuss with regional partners
• Identify strategic flights
• Manage AFP delay
• Cancel and substitute flights
• Route out flights
• Develop the AFP recovery strategy

112
ICR Checklist
113
ICR Checklist for Customers

• Evaluate and analyze current and forecast
  convective weather
• Monitor CCFP
• http//aviationweather.gov/products/ccfp/
• Review all other approved weather sources.
• Discuss with MET Department
• Participate in CCFP Chats (For carriers with met
  departments only).
• Monitor for potential reroute candidates
• Watch for public FEA/FCAs
• Current Ops Plan
• CCSD
• In-House Company ASD
• View FEA/FCA Dynamic List for flights included in
  the FEA/FCA

114
ICR Checklist for Customers

• Develop and implement TMI strategies
• Review Planning Route Advisory (PLN)
• View Current Reroutes from ATCSCC OIS web page
• http//www.fly.faa.gov/ratreader/jsp/index.jsp
• Examine Affected Flights
• View Reroute Monitor FEA/FCA Dynamic List for
  flights affected by advisory
• Reference recommended route guidance available
  for each flight

115
ICR Checklist for Customers

• Evaluate and select routes that fit business
  objectives
• Use RMT ROG capabilities to view flight specific
  information including reroute options, route
  statistics, length, centers traversed and
  CDR/Associated Play information.
• ROG will list all shared and public FEA/FCAs
• Use RMT from ATCSCC OIS to view CDRs in PLN
  Advisory
• http//www.fly.faa.gov/Products/Coded_Departure_Ro
  utes/coded_departure_routes.html
• Use Playbook from ATCSCC OIS to view Plays in PLN
  Advisory
• http//www.fly.faa.gov/PLAYBOOK/pbindex.html
• Discuss with regional partners
• Identify strategic flights
• Discuss with ATA rep/GA desk

116
ICR Checklist for Customers

• Participate in Ops Telcons
• Prepare Worksheet
• Submit Agenda Options as Agenda Items (CDM
  participants)
• Implement TMI Strategies
• Submit customer preferred routes
• Submit Early Intent thru CCSD or internal
  capability
• File a flight plan or refile for flights with
  filed flight plans

117
ICR Checklist for Customers

• Monitor for RQD Reroute Advisories and respond
• Observe assigned routes on Reroute Monitor
• Respond to reroutes in Reroute Monitor
• File assigned routes or request exceptions via
  current exception process
• CDM Use ATCSCC OIS Planning Web Page
• Monitor effects of reroutes
• View Reroute Monitor FEA/FCA Dynamic List for
  flights affected by reroute

118
Adaptive Compression
Implemented March 20, 2007
119
Adaptive Compression

• Adaptive compression is a new approach to
  compression to help ensure that all slots in a
  program are used.
• Adaptive Compression processing is performed at
  the ETMS hub
• Can be turned ON or OFF globally or by control
  Element

120
Adaptive Compression Intro

• The general idea is that a background process at
  the ETMS Hub will
• Monitor a Ground Delay Program (GDP) or Airspace
  Flow Program (AFP) for open slots.
• Identify those slots that are in danger of going
  unused.
• Move other flights earlier to take advantage of
  those open slots
• Move the open slots later.
• Update the databases with the changes.
• Send notification to the flight operators about
  the changes
• The benefits are
• Higher utilization of the airport/airspace
  capacity.
• Reduced delay for the flights operating to that
  airport/FCA.
• Reduced workload for the ATCSCC specialist/ATC
  Coordinator.

See ppt included in this training package fora
detailed look at Adaptive Compression
121
Departure Delay Emphasis

• Improving Departures
• SWAP Advisories
• Departure Oriented
• Capping and tunneling
• Arrival routes/fixes for departures
• GA will be qualified to accept abbreviated
  clearances per Advisory Circular guidance

Check CDM WEB for updates http//cdm.fly.faa.gov/T
raining/S2k7.html
122
OIS Page

• Enhancements
• FSM delay assignment table
• Average Delays for AFP/FCAs
• All Public FEAs
• More information for Current Reroutes
• Changes to TCA Webpage

See ppt included in this training package fora
detailed look at changes to TCA Webpage
123
FSM Delay Assignment Table
124
Playbook Changes

• New Playbooks
• ONL, SLN
• Changed Playbooks
• OXI-OKK changed to OXI-ROYKO
• A761
• No J61 and 2
• No J48 2
• ORD GIJ-GERBS RENAMED MACER1
• Moved the CAN7 north of the CAN 1, via MLS DIK
  FAR.
• ZOB, CVG and Playbook Routes to SFO/OAK/SJC
• ORD Modernization
• DTW Arrivals

125
ATCSCC Position and Responsibiltiy Changes
126
National System Strategy Team (NSST)The Nest

• Replaced SVWX
• Functions include
• Planning Teleconferences
• Coordinating and implementing Airspace Flow
  Programs (AFP)
• Managing reroutes, and
• Facilitating International Operations
• Comprised of
• Planner
• National En Route Spacing Position (NESP)
• Tactical Airspace Manager (TAM)
• International Operations Manager (IOM) and
• Regional Airspace Managers (RAM).

127
ATCSCC Positions Facilitate CDM Control Room
Layout
Front of Room
NESP
STMP/ARO
NSST
CFWU
RAMS
Planner
TAM
TCA
ZTL/ZJX/ZMA
ZOA/ZSE/ZLC
ZOB/ZBW
ZKC/ZME
ZAU/ZMP
ZNY
ZFW/ZHU
ZLA/ZDV/ZAB
NTMO
NTMO
MITRE
ZDC/ZID
OSS
NBAA
SEC
NOM
AVN
ATA
NOCC
NAIMES
OSS/MAI
DOTS/IAM
NOTAMS
128
National Enroute Spacing Position
NESP Position involves Leadership, Take Action
BE Proactive , No more Wait-N-See, Authority,
Educate process to others, Problem Solving,
Look for problems to solve, Reach out, Avoid
Passivity, Minimize distractions, Avoid
time-wasters
SVRW
PT
East
ARTCCs
West
TERMINALS
NBAA/GA
NESP
DISPATCHERS
ATA
MILITARY
NOM
NTMOs
NAVCAN
129
The NSST will be divided into distinct areas of
geographical responsibility

• Domestically, responsibility is assigned to
  specific Regional Airspace Managers
• Geographical areas coincide with the traffic
  management responsibilities assigned to the
  Directors of Tactical Operations (DTO)
• Northeast, Southeast, Midwest, Southwest, and
  West
• Internationally, responsibility is assigned to
  International Operations Manager (IOM)
• Geographical areas coincide with major traffic
  flows
• North Atlantic, Pacific and Polar, Central and
  South America, and Caribbean.

130
RAMS responsible for 5 DTO Regions
131
ATCSCC Layout References

• Layout http//192.90.22.131/ois/ Position
  numbers http//192.90.22.131/Information/Layout/P
  osition_Numbers/position_numbers.html
• Here's a couple of others NSST Handbook
  http//192.90.22.131/Operations/NSST/nsst2006.pdf
  Playbook Link http//192.90.22.131/Operations/pl
  aybook/current/current.pdf

132
Dates of Note

• March 20, 2007 Adaptive Compression
• March 20, 2007 ETMS 8.3 (Reduce CT msgs)
• To Be Determined RMT / ROG Deployment
• May 1, 2007 ICR and new AFP FCAs start
• June, 2007 ETMS 8.4 Target Deployment
• TSD/WSD/CCSD/FSM enhancements
• Fall, 2007 ETMS 8.5 Target Deployment
• More TSD/WSD/CCSD/FSM/RMT enhancements
• January, 2008 Implement XML version of ASDI
  feed.

133

• Enter this address in your Internet Explorer to
  work in CCSD 8.4 Prototype

134
S2K7
Spring 2007ICR(Integrated Collaborative
Rerouting)andDynamic AFPs
THE END