# Presentation: 437683

## S2K+8 Industry Training

- This presentation is primarily for Industry Dispatchers.
- The intent of this presentation is to bring an awareness of changes to procedures and technology that will effect you and the NAS starting this spring (2008).  Also to share CDM reference material that can be useful.
- 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 (George Ingram) before changing any slides that pertain to policy, procedure or guidelines. GIngram@airlines.org.  NBAA contact Ernie Stellings at estellings@nbaa.org.
- I have included hyperlinks to a “ROG Early Intent CBT”, a “CDM acronyms” pdf and a “Traffic Flow Management in the NAS” pdf.

**This presentation can be downloaded at:**
- _[http://cdm.fly.faa.gov/Training/S2k+8.html](http://cdm.fly.faa.gov/Training/S2k+8.html)__ &_
- _[http://tfmlearning.fly.faa.gov/customer/1.s2k+8.ppt](http://tfmlearning.fly.faa.gov/customer/1.s2k+8.ppt)_

## S2K+8

- Spring 2008

- Industry Training

## S2K+8

**ICR Review**
**AFP Override **
**ADVZY's**
**FSM  Enhancements**
**RMT/ROG Changes / Enhancements**
**Reroute Monitor**
**ICR Scenario**
**Miscellaneous S2K+8 Transitions/Changes **
**CDM Resources **

- Overview

## ICR Review

- Integrated Collaborative Rerouting

## ICR Background 7210 ICR NOTICE

- Integrated Collaborative Rerouting (ICR) is a process that builds on FEA/FCA’s.
- The ICR process requires that a constraint is identified early.
- Traffic management issues a planning (PLN) advisory describing the system constraint and providing route guidance.
- System stakeholders are allowed an opportunity to consider the area of concern, and provide early intent (EI) messages that communicate their decisions in response to the constraint.

## ICR Background 7210 ICR NOTICE

- EI messages update the Enhanced Traffic Management System (ETMS) flight trajectories, monitor alert values and routing intentions.
- At the expiration of the EI window, traffic management can then analyze the customer responses and decide if the actions taken have resolved the issue, or if recommended routes, required routes, airspace flow programs (AFP) and/or other traffic management initiatives (TMI’s) will be necessary to further reduce demand

## ICR Background 7210 ICR NOTICE

- ICR allows system stakeholders flexibility in managing their flights based on an identified NAS constraint, reducing the possibility of more restrictive initiatives.
- Traffic flow management (TFM) tools benefit from enhanced flight information and collaborative responses to system capacity actions.

## ICR Review

**Submitting Early Intent before the RQD advisory is implemented could avoid longer RQD reroutes.**

**RQD ICR FCA**

## AFP Override

## Background

- Current Classic AFP’s cover large areas impacting all northeast destinations
- Capacity may vary in different areas of the AFP as weather changes, or does not develop.
- AFP Override is used to respond to Increases and Decreases in capacity.
- Coordination takes place via ad-hoc telcons
- The AFP Override avoids large program revisions for focused capacity level changes
- This minimizes EDCT changes to towers/customers
- This also limits multiple view changes for the customer

## Concept

- AFP Override automates the manual process to ...
- Provide predictability to customers
- Adjust capacity tactically
- Reduce the number of EDCT changes
- Implementing a new AFP ...
- Subset of the original AFP (FCAB05)
- Overrides the original AFP EDCTs in Subset
- Changes control to the New AFP

## ATCSCC 
Override AFP’s are implemented out of the same process that a regular AFP is implemented.
Override AFP’s will be up-lettered.
FCAA05 Override will be FCAB05, FCAC05, FCAD05...
Customers need to be aware of the change that is taking place in the Override AFP.
The Override AFP can Increase or Decrease traffic thru a portion of an already established AFP
This will effect EDCTs for flights captured in the Override AFP
Flight and slot are controlled by the new Override AFP.
Flights remaining in the Original AFP are NOT affected unless a revision is necessary.
Initial implementation is expected in early May and will be applied to Classic Canned AFP’s

- Override AFP’s are implemented out of the same process that a regular AFP is implemented.
- Override AFP’s will be up-lettered.
- FCAA05 Override will be FCAB05, FCAC05, FCAD05...
- Customers need to be aware of the change that is taking place in the Override AFP.
- The Override AFP can Increase or Decrease traffic thru a portion of an already established AFP
- This will effect EDCTs for flights captured in the Override AFP
- Flight and slot are controlled by the new Override AFP.
- Flights remaining in the Original AFP are NOT affected unless a revision is necessary.
- Initial implementation is expected in early May and will be applied to Classic Canned AFP’s

- Concept

## Benefits

- Allows modeling before implementing.
- Provides automated notification to the users and the towers as to which flights are being revised.
- Reduces or eliminates need for manual coordination.
- Provides complete flexibility for which flights to release, as the traffic manager is not just picking and choosing departure airports and centers.
- Is fully equitable, as it captures all flights traversing the geographic area regardless of origin or destination.
- Allows users to swap slots independently; that is, the flights in the second AFP can be swapped with each other and the flights in the original AFP can be swapped with each other, but slots cannot be swapped between the two.

## Benefits

- Explicitly manages the slots that are freed up by the flights that are moved earlier to make sure all capacity is used properly.
- Requires no software changes to FSM.
- Pop-ups get delays equitable with other flights in the same AFP (major caveat to this in the *Cons* section).
- Allows finer control of the flow; that is, the traffic manager can choose how much delay to reduce.
- Could be used to decrease the flow through part of an AFP as well as increase the flow.
- If the procedure to eliminate the overlap is adopted, this provides a complete, consistent, equitable pop-up solution.

**FCAA05 FSM**
**600 120**
**1100-0500**

**FCAA08 FSM**
**600 120**
**1100-0500**

**FCA****B****05 FSM**
**600 120**
**1800-2200**

- FCAB05 added to increase or decrease capacity across that section of airspace

## Advisories  (ADVZY)

-  ICR (PLN)
-  ICR (RQD)
-  AFP Override
-  AFP Suspended EDCT/RQD Routes

## ICR ADVZY – 

**ATCSCC ADVZY 010 DCC ROUTE**** ****PLN**
**NAME: ****ZKC_WX_EAST_ICR**
**CONSTRAINED AREA: ZOB ZID**
**REASON: ****WEATHER IN ZOB/ZID AIRSPACE**
**INCLUDE TRAFFIC: ZAB/ZDV/ZLA/ZLC/ZOA/ZSE**
**FACILITIES INCLUDED: ZAB/ZDV/ZLA/ZLC/ZOA/ZSE **
**FLIGHT STATUS: ALL_FLIGHTS**
**VALID: ETD 241700 TO 242000**
**PROBABILITY OF EXTENSION: MODERATE**
**REMARKS:**** ****CUSTOMERS ARE ENCOURAGED TO FILE EARLY INTENT OVER LNK AND ****NORTH OR IRW AND SOUTH.  THE EARLY INTENT WINDOW IS OPEN UNTIL 1700Z.  IF ****CUSTOMERS DO NOT FILE OUT VIA EARLY INTENT, THEY CAN EXPECT ROUTES AS ****FAR NORTH AS FSD OR AS FAR SOUTH AS ABI.  SEE DYNAMIC LIST FOR UPDATES.**
** **
**ASSOCIATED RESTRICTIONS: NONE**
**MODIFICATIONS: NONE**
**ROUTES:**
**ORIG                                   DEST                                                   ROUTE**
**----                                        ----                                                        ----**
**ZSE ZLC ZOA ZDV          ZBW ZNY ZDC                       ****UPT RTE:  UPT OVER LNK OR****ZLA ZAB                                                                          ****NORTH OR UPT OVER IRW AND****	****	****	****	****	****         ****SOUTH**

- “PLN”

## ICR ADVZY – 

**NAME: ****ZKC_WX_EAST_ICR**
**CONSTRAINED AREA: ZOB ZID**
**REASON: ****WEATHER IN ZOB/ZID AIRSPACE**
**INCLUDE TRAFFIC: ZAB/ZDV/ZLA/ZLC/ZOA/ZSE**
**FACILITIES INCLUDED: ZAB/ZDV/ZLA/ZLC/ZOA/ZSE **
**FLIGHT STATUS: ALL_FLIGHTS**
**VALID: ETD 241700 TO 242000**
**PROBABILITY OF EXTENSION: MODERATE**
**REMARKS:**** ****THESE ROUTES ARE REQUIRED FOR AIRCRAFT WHICH ARE STILL ****FILED THRU FCA010.  SEE DYNAMIC LIST FOR UPDATES.**
** **
**ASSOCIATED RESTRICTIONS: NONE**
**MODIFICATIONS: NONE**
**ROUTES:**
**ORIG                                   DEST                                                   ROUTE**
**----                                        ----                                                        ----**
**ZSE ZLC ZOA ZDV          ZBW ZNY ZDC                      ****ABI J4 FUZ UIM ELD SQS VUZ**
**ZLA ZAB                                                                        ****J14 ATL...PREF RTE TO DEST**
**ZSE ZLC ZOA ZDV          ZBW ZNY ZDC                     ****FSD J16 BAE...PREF RTE TO DEST**
**ZLA ZAB**

- ICR ADVZY –

- “RQD”

## Reroute for airborne flights back through the AFP’s

- ADVZY XXX DCC XX/XX/XXXX FCAXXX ASSOCIATED REROUTES
- UNTIL XXXXZ REROUTES MAY BE OFFERED TO AIRBORNE FLIGHTS WITHIN ZXX/ZXX/ZXX THAT PREVIOUSLY ROUTED AROUND FCAXXX TO BE PUT BACK ON NORMAL ROUTES THROUGH FCAXXX.

## Override AFP

**CTL ELEMENT: ****FCAB05**
**ELEMENT TYPE: FCA**
**ADL TIME: 1423Z**
**DELAY ASSIGNMENT MODE: DAS (or GAAP)**
**OVERRIDE AFP: YES **
**ENTRY ESTIMATED FOR: 27/1600Z – 27/2159Z **
**ANTICIPATED CUMULATIVE PROGRAM PERIOD: 27/1600Z – 27/2159Z**
**ANTICIPATED PROGRAM RATE: 92/90/90/80/80/80**
**ANTICIPATED POPUP FACTOR: 2/2/2/3/3/3**
**FLT INCL: ALL FLIGHTS IN FCAB05 DYNAMIC FLIGHT LIST**
**DEP SCOPE: ALL**
**ADDITIONAL DEP FACILITIES INCLUDED: ALL**
**EXEMPT DEP FACILITIES:**
**EXEMPT ARR FACILITIES:**
**CANADIAN DEP ARPTS INCLUDED: US Only**
**DELAY LIMIT: 500**
**ANTICIPATED MAXIMUM DELAY: 365 **
**ANTICIPATED AVERAGE DELAY: 91 **
**REASON: Weather**
**REMARKS: AFPB05 OVERRIDES AFPA05 AND RELEASES ALL FLIGHTS FROM ZSE ZOA ZDV ZDV ZMP ZAU TO ZBW FROM EDCTS**
**USER UPDATES MUST BE RECEIVED BY: 23/1500Z**
**271424-271559**

**ATCSCC Specialist could release all or selected ARTCC’s depending on the change in capacity/demand/situation**

**New to the ADVZY**

## Suspending EDCT/RQD Routes

- ADVZY XXX DCC XX/XX/XXXX EDCT SUSPENDED FOR FCAXXX
- CUSTOMERS ARE ADVISED THAT EDCT AND RECOMMENDED ROUTES ARE SUSPENDED UNTIL XXXXZ FOR XXX FACILITIES.  FLIGHTS THAT HAVE REROUTED OUT OF THE FCAXXX CAN BE ALLOWED TO ROUTE BACK THROUGH FCAXXX AND SUSPEND EDCT.

- At times additional capacity may be available only in a specific geographic area rather than the entire controlled airspace. For example, there may be unused capacity along routes only in the northern part of a center.  The additional capacity may only exist for a short time relative to the overall AFP time range.  There may not be a lot of lead time in knowing when this capacity is available.  A revision changes the control times for all flights in the AFP, which is very disruptive to the customers.
- There could be times that the ATCSCC sends out an advisory  that suspends EDCT’s or Reroutes.  There is no standardized format for suspending EDCT’s or Reroutes.  This notice is just to make you aware that ATC can suspend EDCTs or RQD routes when additional capacity exists.

## FSMChanges/Enhancements

- AFP Route Out CreditIPM Integrated Program Modeling FSM 8.6 Release Date

## AFP Route-Out Credit

- AFP Executed

- Time Line

- Route out of AFP area in this time frame

- FCA has no record of the flight***No credit***

- Route out of AFP area in this time frame

- Route out of AFP area in this time frame

- Adaptive compression moves flight to end of program
***Compression***** *****credit***

- Initial AFP treats flight as cnx  and moves to end of program
***No credit***

- Last year if you filed out before the AFP was executed you lost your slot.

- Now if you file after FSM-Eligible FCA is created you will receive slot credit.

- FSM-Eligible FCA Created

- Initial AFP treats flight as cnx  and moves to end of program
***Compression credit***

## IPMIntegrated Program Modeling

- FSM based modeling enhancement

## IPM Phase 1 

- Objectives
- Allow for modeling the impact of purging a program on elements other then purge element,
- i.e., model the purging of an AFP to see impact on GDP’s.
- Allow for modeling the impact of issuing a program on elements other then element for which the program was modeled,
- i.e., modeling the issuance of a GDP to see the impact on an AFP.
- Impact on Customers
- Customers will not be able to view FSM IPM displays (because of the requirements to mask data) but will benefit from the Command Center being able to see the impact an AFP will have on GDP’s and vice-versa.
- ATCSCC will be able to see the impact of an AFP on a non-GDP airports.
- ATCSCC will be able to see impact of AFP purges. (additional traffic at airports once AFP is cancelled)
- ATCSCC will be able to Model effect of an AFP on GDP to understand impact

## IPM Phase 1

- Program models can be applied to multiple data sets in “Ground Delay Modeling Mode”

- In this example, the FEAA05 AFP model is applied to PHL and BOS

## Multi-Program Bar Charts

- Now you can see how the AFP affects PHL and BOS.

- Changes in the demand can be viewed in the bar charts, before implementation.

## IPM Deployment

- 	IPM is projected to be deployed in FSM 8.6 Monday, April 14, 2008.  The software transitions to Keysite testing on April 7.  A final determination of the deployment date will be made at the end of Keysite testing; and promptly communicated to the CDM community. Barry DavisManager, TFM OperationsFAA System Operations Service UnitPrograms Directorate, ATO-R

## RMTRoute Management Tool

**Changes /**** ****Enhancements**

## RMT

**RMT**

## RMT

**RMT**

- Changes to RMT - “CoordReq”ROG OverviewSending Early Intent with ROG

## Changes to RMT

- UserFile Column header renamed “Coordination Required” (**CoordReq)**
**CoordReq**=Y
- Requires coordination with ATCSCC TCA before filing.
- All CDR’s with UserFile = Y will be reset to CoordReq=N in conjunction with the release of RMT 1.50.
- The **Coordination Required “CoordReq”** flag has been moved to the left in the default configuration of the CDR Query Results table (between the Route String and Departure Fix fields)

## “User File” has changed to “CoordReq”

- “Y” = Coordination is required to file this route

- “N” = Coordination is not required to file this route

## ROGRoute Options Generation

- ROGRoute Options Generation

-  ROG allows you to ...	- view FEA/FCA’s	- view Routes around FCA’s	- Select Routes and submit Early Intent

## Route Options Generation (ROG)

- RMT will allow users to view the associated Flow Evaluation Area (FEA) / Flow Constrained Area (FCA) advisories for the FEA/FCA definition and flight list loaded into the ROG Tool (if one has been issued for the FEA/FCA).
- RMT imports the FEA/FCA Advisories from the OIS Advisories database based on the FEA/FCA name.  If multiple advisories are available for an FEA/FCA, the last entered is displayed by the ROG Tool.  If there are no advisories available for the FEA/FCA or if the OIS database is unavailable, a warning message will appear.

## Route Options Generation (ROG)
RMT 1.50 allows Customers to submit Early Intent (EI) messages for their flights to the Enhanced Traffic Management System (ETMS) for flights that do not have a filed flight plan from the ROG Flight Summary window.  
ROG provides 
error checking, 
ETMS submission status, 
and warning messages 
RMT formats the EI messages in standard CDM message format.

- RMT 1.50 allows Customers to submit Early Intent (EI) messages for their flights to the Enhanced Traffic Management System (ETMS) for flights that do not have a filed flight plan from the ROG Flight Summary window.
- ROG provides
- error checking,
- ETMS submission status,
- and warning messages
- RMT formats the EI messages in standard CDM message format.

- Route Options Generation (ROG)

## Sending Early Intent

- 4. Send Early Intent

- 1. Load FEA/FCA flights

- 2. Load Route options around selected FEA/FCA

- 3. Assign Routes around selected FEA/FCA

- See the ICR Scenario at the end of this presentation for full demonstration

- Route Options Generation (ROG)

## RMT CBT

- If you can’t wait to see the ICR scenario click on the button below to view Metrons Early Intent CBT.

## Reroute Monitor

- Monitor for reroutes affecting your flightsMainline Sub-carriers (Express) viewable Sending Early Intent with Reroute Monitor

- Reroute Monitor is found in CCSD.

- Click the “Reroute” drop down menu and select “Monitor All Reroutes”

- Reroute Monitor is found in CCSD.

- Click the “Reroute” drop down menu and select “Monitor All Reroutes”

- Monitor for reroutes affecting your flights

- Does your _filed_ flight plan conflict with the  ADVZY route (NC)?

- Does your _unfiled_ flight have an ADVZY that pertains to your flight (UNKN)?

- Sub-Carriers are now viewable in Reroute Monitor.

- Early Intent Can be sent through Reroute Monitor

## Paste Route or copy from “Assigned Routes” into Early Intent “New Route:” and “OK”

## FEA/FCA’sReview

- UsageNaming Convention

## Flow Evaluation Area (FEA)

-  Used to evaluate traffic demand
-  Used to share information between FAA facilities and customers
-  Used with planned (PLN) advisories to specify system constraints
-  May be used to provide recommended (RMD) reroutes
-  The first step in the ICR process is to provide an FEA for information sharing and route planning

## Used to provide required (RMD) and (RQD) reroutes
Ex. Chokepoints, routes around weather
Used to develop AFPs / Dynamic AFP’s
Used to provide mandatory routes in the ICR process

- Ex. Chokepoints, routes around weather
- Used to develop AFPs / Dynamic AFP’s
- Used to provide mandatory routes in the ICR process

- Flow Constrained Area (FCA)

## Naming Convention

- FCA001 – 1st of the last 3 letters start with “0”  are automatically generated thru ETMS
- - FCA based Reroutes
- FCA010 ZKC_WX_EAST_ICR
- - ICR (ICR will include the ICR NAME and FCA# when it becomes RQD...

- FCAKC1 – 1st two of the last 3 letters start with ARTCC identifiers are
- - Dynamic AFP’s or
- - Canned (Mid-Continent, ZID, ZME)

- FCAA01/A08 – 1st of the last 3 letters start with “A” are
- - Classic Canned FCA’s

- FCAB01 – 1st of the last 3 letters start with “B” are
- - Override FCA’s

- FCAB01

## ICR Scenario

## ICR Scenario

## 1115Z - TSTMS build between LNK and IRW1135z - Conference held with ZMP/ZKC/ZFW to 	discuss the the wx in their airspace.

## CCFP Is Reviewed

- 15Z CCFP

## CCFP Is Reviewed

- 17Z CCFP

## NOTE the forecast improvement at 1900Z

- CCFP Is Reviewed
- 19Z CCFP

## 1115Z Planning Telcon

- 	- ICR proposed due to the wx in ZKC/ZMP and ZFW.  Proposal was sent for aircraft to file north via LNK or south via IRW using “Early Intent”.
- 	- If aircraft do not file early intent they would be moved further north via FSD or further south via ABI or a EWM playbook.

## 	1200Z Two public FEAs were created from a point just south of LNK to just north of IRW.  One of the FEAs (ZKC_WX_EAST_ICR) was filtered for eastbound traffic. Note the “_ICR” in the name.  A “PLN” advisory was sent out identifying the FEA along with the following remarks....

- 	**1200Z** Two public FEAs were created from a point just south of LNK to just north of IRW.  One of the FEAs (ZKC_WX_EAST_ICR) was filtered for eastbound traffic. Note the “_ICR” in the name.  A “PLN” advisory was sent out identifying the FEA along with the following remarks....

## ZKC_WX_EAST_ICR

## ZKC_WX_WEST_ICR

## “PLN” (PLANNING) ADVISORIES SENT WITH THE FOLLOWING REMARKS:

## 1315Z – PLANNING TELCONCAN1 AND CHOKEPOINTS RMDICR ROUTE OPTIONS BRIEFED

**1315Z – PLANNING TELCON****CAN1 AND CHOKEPOINTS RMD****ICR ROUTE OPTIONS BRIEFED**

- Additional TMI’s are implemented to support NAS capacity and flow issues

## Example:  USA1574 PHX/PIT

- Using **Reroute Monitor** to Send **Early Intent**

- Using **Reroute Monitor** to Send **Early Intent**

- Use CCSD (Common Constraint Situation Display ) to display flights affected by Reroute Advisories

- Click on the “Reroute” dropdown menu and select “Monitor All Reroutes”

- Using **Reroute Monitor** to Send **Early Intent**

- Use CCSD (Common Constraint Situation Display ) to display flights affected by Reroute Advisories

- Click on the “Reroute” dropdown menu and select “Monitor All Reroutes”

- Using **Reroute Monitor** to Send **Early Intent**

- Is FEA an ICR?

- Is there an Early Intent Check Box?

- Is the Assigned route “PLN”?

- Using **Reroute Monitor** to Send **Early Intent**

- Check the “Early Intent Box and Click on the “Submit Early Intent” button

## Early Intent window

- Using **Reroute Monitor** to Send **Early Intent**

- You can copy and paste a route from your routes data base or copy from “Assigned Routes” in the Early Intent window

- Select Best Route around FCA

- Using **Reroute Monitor** to Send **Early Intent**

- Using **Reroute Monitor** to Send **Early Intent**

- Select Best Route around FCA

## Select Best Route around FCA

- Using **Reroute Monitor** to Send **Early Intent**

## Paste Route into Early Intent “New Route:” (or “Copy” from “Assigned Routes”) and “OK”

- Using **Reroute Monitor** to Send **Early Intent**

- Paste Route into Early Intent “New Route:” (or “Copy” from “Assigned Routes”) and “OK”

- Using **Reroute Monitor** to Send **Early Intent**

## ICR Window of opportunity

- PHX/PIT with ICR _UN_available

- PHX/PIT with ICR available

- If you send Early Intent after the ADVZY goes from PLN to RQD you will lose the opportunity to choose your route around the FCA.

## Example: USA1500 SAN/PHL

- Using **ROG **to Send **Early Intent**

- RMT/ROGRoute Options Generation

- Using **ROG **to Send **Early Intent**

- Using **ROG **to Send **Early Intent**

- After you “Load FEA/FCA”1. Find Options (around FEA/FCA)2. Open “Assign Reroutes” window3. Open “Flight Summary” window

- Using **ROG **to Send **Early Intent**

- After you “Load FEA/FCA”1. Find Options (around FEA/FCA)2. Open “Assign Reroutes” window3. Open “Flight Summary” window

## After you “Load FEA/FCA”1. Find Options (around FEA/FCA)2. Open “Assign Reroutes” window3. Open “Flight Summary” window

- Using **ROG **to Send **Early Intent**

- After you “Load FEA/FCA”1. Find Options (around FEA/FCA)2. Open “Assign Reroutes” window3. Open “Flight Summary” window

- Using **ROG **to Send **Early Intent**

- After you “Load FEA/FCA”1. Find Options (around FEA/FCA)2. Open “Assign Reroutes” window3. Open “Flight Summary” window

- Using **ROG **to Send **Early Intent**

- After you “Load FEA/FCA”1. Find Options (around FEA/FCA)2. Open “Assign Reroutes” window3. Open “Flight Summary” window

- ROG works best with “Map”, “Assign Reroutes” and “Flight Summary” windows displayed simultaneously.

- Sort by ETD to see which flights are potential candidates for ICR.

- Sort by ETD to see which flights are potential candidates for ICR.

- Flights with a flight status of “S” are candidates for ICR “Early Intent”A - Active FlightP - Proposed Flight Plan (Flight plan has been filed)S - Scheduled (These are candidates for ICR)

- Double Click on the Flight Candidate for ICR

## All windows update with information related to the selected flight

- Select preferred route around ZCC_WX_EAST_ICR

- Selected route is both a CDR and a Playbook route.Hold the Ctrl key and click on the Playbook route to deselect

- Select preferred route around ZCC_WX_EAST_ICR

- Selected route is both a CDR and a Playbook route.Hold the Ctrl key and click on the Playbook route to deselect

- CDR is still selected.

- Assign the selected route to USA1500

- Route Status indicator changes to green indicating a route has been assigned.

- To submit Early Intent click on the “Send EI” button in the “Flight Summary” Window.

- Click the “Send” button

- A successful Early Intent submission should see:“ETMS Messages” indicating “PROCESSED”EI Status should be colored **green**

## 1400Z – FEAS CONVERTED TO FCAS PRIOR TO IMPLEMENTING REQUIRED REROUTES

- Meanwhile back at the scenario...the FEA’s are turned into RQD FCA’s and all who file after will be RQD to fly longer routes.

## 1400Z – FEAS CONVERTED TO FCAS PRIOR TO IMPLEMENTING REQUIRED REROUTES

## 1500Z – REQUIRED ROUTES FOR WESTBOUND TRAFFICSTILL FILED THRU THE FCA

## ICR Scenario

## MiscellaneousThe winds of change are upon us

**TFM Modernization ****ERAM****WATRS**

## MiscellaneousTransitions/Changes

**TFMM****ERAM****WATRS**

## TFMMTraffic Flow Management Modernization

## TFM Modernization (TFM-M)

- FAA is replacing the ETMS software system with a modernized Traffic Flow Management System (TFMS)
- Functional enhancements to the core traffic management system software are on hold until the transition from ETMS to TFMS is complete
- This means there will be little or no change to existing traffic flow management core software functions, such as FCAs and Reroutes, until the transition is complete

## Why TFM Modernization?
FAA is currently backlogged with solutions to TFM problems
Based on 20-year-old system originally deployed as prototype
New software applications and functional improvements are limited or simply not feasible with current architecture
TFM-M Releases
Release 1 –  Facility Site Prep at WJHTC (Complete 3/07)
Release 2 – TPC (TFM Processing Center) Operational (June 2008) 
New interface software for CDM and weather interfaces
New software / hardware architecture 
ASDI data feed converted to XML (Completed)
Consolidation of Help Desk 
Release 3 – Complete TPC Modernization (August 2009)
Remaining legacy hub site components are modernized
Support for CDM Test and Research Community via Mini TPCs

- FAA is currently backlogged with solutions to TFM problems
- Based on 20-year-old system originally deployed as prototype
- New software applications and functional improvements are limited or simply not feasible with current architecture
- TFM-M Releases
- Release 1 –  Facility Site Prep at WJHTC (Complete 3/07)
- Release 2 – TPC (TFM Processing Center) Operational (June 2008)
- New interface software for CDM and weather interfaces
- New software / hardware architecture
- ASDI data feed converted to XML (Completed)
- Consolidation of Help Desk
- Release 3 – Complete TPC Modernization (August 2009)
- Remaining legacy hub site components are modernized
- Support for CDM Test and Research Community via Mini TPCs

- TFM Modernization (TFM-M)

## TFM-M CDM Update Briefings

- Next Meetings: April 3rd 2008
-  		      	   May 1st  2008
- 				13:00 ET
- Phone: (641) 715-3300
- Code: 708037#
- Goto Meeting address:
**	**_**https://www1.gotomeeting.com/join/947288299**_
- Send questions or advance telcon topics:

**9-ATOR-ATCSCC-TFMM-Transition@faa.gov**

**Information will be emailed out CDM exploder list prior to each meeting**

**Notes:**
MARK WILL TAKE OVER HERE AGAIN AND TALK TO THE CDM PARTICIPANTS ABOUT THE UPCOMING FAA TELECONS
PHONE NUMBER AND EMAIL ACCOUNT TO BE DETERMINED.  CHRIS WILL GET THEM HOPEFULLY THIS WEEK,

## ERAMEn Route Automation Modernization

## En Route Automation Modernization (ERAM) is the largest National Airspace System (NAS) equipment replacement program in FAA history 
ERAM replaces 20 Air Route Traffic Control Center (ARTCC) legacy Host computer processing systems 
1st operational use of ERAM is at Salt Lake ARTCC (ZLC) in October 2008 
Last to transition to ERAM is Miami ARTCC (ZMA) in November 2009 

- ERAM replaces 20 Air Route Traffic Control Center (ARTCC) legacy Host computer processing systems
- 1st operational use of ERAM is at Salt Lake ARTCC (ZLC) in October 2008
- Last to transition to ERAM is Miami ARTCC (ZMA) in November 2009

**What is ERAM?**

## This FAA project will improve many HOST computer processes to improve center automation, especially regarding use of RNAV departures.
It also adopts the ICAO, international format flight plan strip for domestic use and will make the U.S. ATC system ICAO-compliant.
If the new format is not used, you cannot fly RNAV SIDS or STARS.

- It also adopts the ICAO, international format flight plan strip for domestic use and will make the U.S. ATC system ICAO-compliant.
- If the new format is not used, you cannot fly RNAV SIDS or STARS.

**What is ERAM?**

## ERAM Waterfall  as of March 19

**ERAM Waterfall  as of March 19**

## WATRS

## WATRS Plus Route Structure  Redesign & Separation Reduction

- WATRS Plus Route Structure  Redesign & Separation Reduction

## WATRS PLUS

- The Western Atlantic Route System includes parts of Miami, San Juan, and New York Centers
- Lateral separation between routes is currently at least 90 miles
- WATRS Plus will reduce the lateral separation to 50 miles for aircraft with adequate navigation accuracy
- 50 miles has been used in the Pacific since 1998

## WATRS PLUS

- To qualify for the 50 mile spacing routes the aircraft must be approved for RNP10, as a minimum.
- RNP4 approval is preferred
- Maintenance is currently verifying that all our aircraft which would operate in WATRS are approved for RNP10.

## WATRS PLUS

- Should have RNP10 authorization by May 5
- Will apply to
- Oceanic routes in WATRS Plus center areas
- Between FL290-410
- RNP10 requires
- Two operational long-range nav systems that meet RNP accuracy standards
- Time limit of 6.2 hrs between position updates if INS is only source of nav info

## WATRS PLUS

- Routes in WATRS Plus airspace NOT affected by RNP10:
- Routes defined by VOR, VOR/DME, NDB
- Special Area Nav routes between Florida and Puerto Rico (now called T-routes).
- These will soon be re-named to Y-routes
- Routes located within radar and VHF coverage
- A761 HANRI-ETOCA; R511 AZEU-ELTEE

## WATRS PLUS

- Non-RNP10 aircraft operating in WATRS Plus airspace after June 5:
- Field 18 of the flight plan must show
- 			“STS/NONRNP10
- Non RNP10 aircraft can still file and fly any route or altitude in WATRS Plus airspace, but will be cleared as traffic permits
- Expect long delays.
- Refiling to a WATRS Plus route that does not require RNP would be preferable

## WATRS PLUS

- To operate in WATRS Plus with 50 mile lateral separation, we must
- Show the letters “R” and “Z” in field 10 of the flight plan
- Show “NAV/RNP10” (or RNP4) in field 18
- This filing change should begin by May 5, and will be required effective June 5, 2008
- System changes to permit this are the same as the ERAM filing changes

## NEW 

- NEW
- WATRS
- PLUS
- ROUTE
- SYSTEM

## Key WATRS Plus Implementation Dates

- - 10 April 2008
- 	Navigation database and charting data published in National Flight Data Digest
- - 5 May 2008
- 	By 5 May 2008, operators capable of meeting the RNP 10 minimum requirement or operator-option RNP 4 should have:
- 		Obtained authorization from the appropriate State (country) 	authority and...
- 			Started annotating their ICAO flight plans in 			accordance with paragraph 7 of this notice.
-  - 5 May 2008, operators not capable of obtaining RNP 10 or RNP 4 	authorization by 5 June 2008 should start following the 	practices detailed in paragraph 4 (i.e., ICAO flight plan 	annotation and pilot report to ATC the lack of RNP 10 	authorization).
-  - 5 June 2008,  Planned effective date/time for implementation of WATRS Plus route structure 0901 UTC.
- - For additional updated information:

- http://www.faa.gov/about/office_org/headquarters_offices/ato/service_units/enroute/oceanic/WATRS_Plus/

## CDM Resources

**TFM Handbook****Acronyms **

## The TFM Handbook Traffic Flow Management in the NAS

## The material in the attached pdf explains terms, techniques, and programs associated with Traffic Flow Management in the National Airspace System. 
The attached document can be found at:
	http://www.fly.faa.gov/Products/Training/Traffic_Management_for_Pilots/TFM_NASv2.pdf

	“This is a wonderful foundational resource in helping to understand Traffic Flow Management.”
					Gary Dockan 				CDM Industry Training 

- The attached document can be found at:
- 	_[http://www.fly.faa.gov/Products/Training/Traffic_Management_for_Pilots/TFM_NASv2.pdf](http://www.fly.faa.gov/Products/Training/Traffic_Management_for_Pilots/TFM_NASv2.pdf)_
- 	*“**This is a wonderful foundational resource in helping to understand Traffic Flow Management.”*
- 					*Gary Dockan **	**	**	**	**CDM Industry Training *

**Traffic Flow Management****in the NAS**

**The TFM Handbook**** ****Traffic Flow Management in the NAS**

## CDM Acronyms

## Primary CDM Acronyms

- PDAR – Preferential Arrival and Departure Route.
- PDARS – Performance Data Analysis and Reporting System
- PDC – Pre Departure Clearance
- PLN – Planned
- POET – Post Operations Evaluation Tool
- RAA – Regional Airline Association
- RAPT – Route Availability Planning Tool
- RCTL – Re-controlled
- RMD – Recommended
- RMT - Route Management Tool
- ROG – Route Options Generation
- RQD – Required
- SBRG – SCS Bridging
- SCS – Slot Credit Substitution
- SEVEN – System Enhancements for Versatile Electronic Negotiation  (as in “Concept SEVEN”)
- SPT - Strategic Planning Team
- STMC – Supervisory Traffic Management Coordinator
- SWAP – Severe Weather Avoidance Procedures
- TCA - Tactical Customer Advocate
- TFM – Traffic Flow Management
- TFM-M – Traffic Flow Management Modernization
- TFMS – Traffic Flow Management System
- TMA – Traffic Management Advisor
- TMC – Traffic Management Coordinator
- TMI – Traffic Management Initiative
- TMU – Traffic Management Unit
- TSD – Traffic Situation Display
- UPD – Updated EDCT
- UPT – User Preferred Trajectory
- URET – User Request and Evaluation Tool
- WATRS - Western Atlantic Route System
- WET – Weather Evaluation Team  (CDM workgroup)

- FACET – Future ATM Concepts Evaluation Tool
- FCA – Flow Constrained Area
- FCT – Future Concepts of TFM  (CDM workgroup)
- FEA – Flow Evaluation Area
- FET – Flow Evaluation Team  (CDM workgroup)
- FSA – Flight Schedule Analyzer
- FSM – Flight Schedule Monitor
- FSS – Flight Service Station
- GA – General Aviation
- GAAP - General Aviation Arrival Program
- GDP – Ground Delay Program
- GDPE – Ground Delay Program Enhancements  (CDM subgrouop)
- GS – Ground Stop
- HAR – High Altitude Redesign
- HITL – Human in the Loop  (testing)
- ICR – Integrated Collaborative Rerouting
- IPM – Integrated Program Modeling
- ITWS – Integrated Terminal Weather System
- LAADR – Low Altitude Arrival/Departure Route
- MIT – Miles-in-Trail
- NAR – National Airspace Redesign
- NAS – National Airspace System
- NBAA – National Business Aircraft Association
- NESP – National Enroute Spacing Position
- NOC – National Operations Control Center  (Nav Canada)
- NOM - National Operations Manager
- NRP – North American Route Program
- NSST – National System Strategic Team
- NTML – National Traffic Management Log
- NTMO – National Traffic Management Officer
- OIS – Operational Information System
- OMS – Operations Management System

- AADC - Airport Arrival Demand Chart
- AAR – Airport Acceptance Rate
- ABRG – Adaptive Compression Bridging
- AC – Adaptive Compression
- ADC – Airport Demand Chart
- ADL – Aggregated Demand List
- AFP – Airspace Flow Program
- AOC – Airline Operations Center
- ARTCC – Air Route Traffic Control Center
- ATCSCC – Air Traffic Control System Command Center
- CCFP – Collaborative Convective Forecast Product
- CCSD – Common Constraint Situation Display
- CDM – Collaborative Decision Making
- CDR – Coded Departure Route
- CIWS – Corridor Integrated Weather System
- CRCT – Collaborative Routing Coordination Tool
- CTA – Controlled Time of Arrival
- CTAS – Center TRACON Automation System
- CTD – Controlled Time of Departure
- CWSU – Center Weather Service Unit
- DAS – Delay Assignment
- DSP – Departure Spacing Program
- EDCT – Expected Departure Clearance Time
- EI - Early Intent
- ERAM – Enroute Automation Modernization
- ESM – Enhanced Substitution Module
- ESP – Enroute Sequencing Program
- ETMS – Enhanced Traffic Management System

## Exhaustive list of CDM Acronyms and Definitions

**CDM Acronyms**

## S2K+8 Industry Training

- Special thanks to CDM Training Team Members

- Nathan DobleGary DockanJoe DottererChris Ermatinger
- Glenn GodfreyMike GolibersuchMark HopkinsGeorge IngramCurt KalerTim Matuszewski

- Charlie Mead
- Mike Murphy Alvin NepomucenoMark NovakEd OlsenTom St. ClairPhil Smith Ernie StellingsPat SomersallDon Wolford

## S2K+8 Industry Training

- Thanks to all who contributed to this years S2K Industry Training

## S2K+8

- Industry Training