# Presentation: 891068

## FCA / Reroute Workgroup

**Changes to the Route Advisories**
**CRWG**
**September 9-11, 2003 **
**Mark Libby**
**     ****	**

## Introduction

**The Route Advisory format will change in conjunction with the redesign of the Create Reroute Dialog Box.**
**Effective ETMS 7.8 change**
**The following slides depict these changes.**

## Side by Side Comparison:Current 				New 

_**Title:**_
_**Impacted Area:**_
_**Reason:**_
_**Include Traffic:**_
_**Facilities Included**_:
_**Valid:**_
_**Probability of Extension:**_
_**Remarks:**_
_**Associated Restrictions:**_
_**Modifications:**_
_**Route (s):**_

_**Title:**_**  **
_**Name:**_
_**Constrained**__** Area:**_** **
_**Reason:**_
_**Include Traffic:**_** **
_**Facilities Included**_**: **
_**Flight Status:**_
_**Valid:**_** **
_**Probability of Extension:**_** **
_**Remarks:**_** **
_**Associated Restrictions:**_** **
_**Modifications:**_** **
_**Route (S):**_

## Route Advisory Format - New

**     **
_**Title:**_**  **
_**Name:**_
- Users have requested that the name of the reroute be included in the advisory. Line two of the advisory now specifies the name.
- If the specialist indicates that the reroute is tied to an FCA, then the name of the reroute is the name of the FCA – the specialist will have no way to change this.
- Example:
- NAME: FCA001
_**Constrained**__** Area:**_** **
_**Reason:**_
_**Include Traffic:**_** **
_**Facilities Included**_**: **
_**Flight Status:**_
_**Valid:**_** **
_**Probability of Extension:**_** **
_**Remarks:**_** **
_**Associated Restrictions:**_** **
_**Modifications:**_** **
_**Route (S):**_

## Route Advisory Format - New

_**Title:**_**  **
_**Name:**_
_**Constrained**__** Area:**_** **
**Facilities complained that the use of the heading ‘Impacted Area’ was ambiguous. Some argued that the impacted area was the area that flights were being rerouted into, and some argued that it was the area impacted by weather. **
**Since the intention of the advisory is to indicate the area of weather necessitating the reroutes, the heading has been changed to ‘Constrained Area’.**
_**Reason:**_
_**Include Traffic:**_** **
_**Facilities Included**_**: **
_**Flight Status:**_
_**Valid:**_** **
_**Probability of Extension:**_** **
_**Remarks:**_** **
_**Associated Restrictions:**_** **
_**Modifications:**_** **
_**Route (S):**_

## Route Advisory Format - New

_**Title:**_**  **
_**Name:**_
_**Constrained**__** Area:**_** **
_**Reason:**_
_**Include Traffic:**_** **
_**Facilities Included**_**: **
_**Flight Status:**_
**A new line has been added to indicate the flight status to be included in the reroute. The possibilities are:**
**ALL**
**AIRBORNE**
**NOT AIRBORNE**
_**Valid:**_** **
_**Probability of Extension:**_** **
_**Remarks:**_** **
_**Associated Restrictions:**_** **
_**Modifications:**_** **
_**Route (S):**_

## Route Advisory Format - New

_**Title:**_**  **
_**Name:**_
_**Constrained**__** Area:**_** **
_**Reason:**_
_**Include Traffic:**_** **
_**Facilities Included**_**: **
_**Flight Status:**_
_**Valid:**_** **
- Specialists can now create reroutes based on FCAs. This necessitated a change in the way that the valid time of the reroute is shown. The specialist can indicate that the valid time is based on ETD, ETA, or an FCA. The Valid Time field of the advisory will be set as in the following examples:
**If ETD - VALID: ETD 1545 TO 1800**
**If ETA - VALID: ETA 1545 TO 1800**
**If FCA - VALID: FCA ENTRY TIME FROM 1545 TO 1800**
**(Note: P- times are available on the dynamic list)**
_**Probability of Extension:**_** **
_**Remarks:**_** **
_**Associated Restrictions:**_** **
_**Modifications:**_** **
_**Route (S):**_

## Route Advisory Format - New

_**Title:**_**  **
_**Name:**_
_**Constrained**__** Area:**_** **
_**Reason:**_
_**Include Traffic:**_** **
_**Facilities Included**_**: **
_**Flight Status:**_
_**Valid:**_** **
_**Probability of Extension:**_** **
_**Remarks:**_** **
_**Associated Restrictions:**_** **
_**Modifications:**_** **
_**Route (S):**_
**Specialists can now include both full routes and split routes in the same reroute. To accommodate this, the Routes section of the advisory will, if necessary, contain two sections; a section for full routes and a section for split routes. Each section will only exist if there are routes of that type to be included in the advisory.**

## Route Advisory Format – NEW

**ROUTE(S):**
**FROM:**
**ORIG                 ****	****	****	****DEST                ****	**** ROUTE**
**-----              ****	****	****	****	****  ----                ****	**** -----**
**ZAB             ****	****	****	****	****BOS                  ****	****ABQ J6 LIT J66 MEM J118**
**	****	****	****	****	****                                          ****SPA RDU J207 FKN J79 JFK**
**	****	****	****	****	****                                          ****ORW5**
**ZFW                ****	****	****	****BOS/BWI/CLE/DCA/**
**	****	****	****	****                     ****EWR/IAD/JFK/LGA/****	**
**                    ****	****	****	****	****PHL/PIT/TEB          ****	**
**FROM:**
**ORIG                             ****	****	****	****	****	**** ROUTE – ORIGIN SEGMENTS                                                      **
**-------                          ****	****	****	****	****	**** ---------****	****	**
**ZLA                             ****	****	****	****	****	**** BCE J100 EKR MBW RAP RWFJ34 BAE  **
- ZLC (PRIMARY)                    				 BOY J32 CZI J82 RAP RWF J34 BAE
**ZLC (SOUTH OPTION)               ****	****	****	****	**** EKR MBW RAP RWF J34 BAE**
**ZMP                               ****	****	****	****	****	****ODI J34 BAE**
**ZOA                             ****	****	****	****	****	****SAC J32 CZI J82 RAP RWF J34 BAE**
**ZSE                               ****	****	****	****	****	****BIL J34 BAE**
**TO:**
**DEST                              ****	****	****	****	****	****ROUTE – DESTINATION SEGMENTS**
**-------                         ****	****	****	****	****	****  ---------**
**BOS                             ****	****	****	****	****	**** BAE J16 ALB GDM3 BOS****	**
**BWI                               ****	****	****	****	****	****BAE GIJ J146 WOOST J34 DJB J162**
**                                  ****	****	****	****	****	****MGW EMI3 BWI  **
**CLE                              ****	****	****	****	****	****BAE J36 FNT YQG GONNE2 CLE**

## Route Advisory Format - New

_**13. Route (S):**_
**To accommodate this, when the specialist wants to include a generic textual description, they will set a type for those individual route(s). This will indicate to the TSD that it should not try to parse and validate the route. The user will be able to choose from four types:**
**UPTRTE****	**
**CDRRTE**
**UNKNRTE**
**RERTE**
**These generic descriptions will be placed in the ROUTE field of the appropriate routes **

## Route Advisory Format - New

_**13. Route (S):**_
**Specialists will have the ability to provide generic textual descriptions of routes.**
** ****For example, the specialist may indicate that flights are to file south of a line from IRW to MEM – this would be indicated with ‘UPTRTE:’ followed by the generic description. **
**ROUTE(S):**
**FROM:**
**ORIG                 ****	****	****	****DEST                ****	**** ROUTE**
**-----              ****	****	****	****	****  ----                ****	**** -----**
**ZAB             ****	****	****	****	****BOS                  ****	****ABQ J6 LIT J66 MEM J118**
**	****	****	****	****	****                                          ****SPA RDU J207 FKN J79 JFK**
**	****	****	****	****	****                                          ****ORW5**
**ZFW                ****	****	****	****BOS/BWI/CLE/DCA/**
**	****	****	****	****                     ****EWR/IAD/JFK/LGA/****	**
**                    ****	****	****	****	****PHL/PIT/TEB          ****	****UPTRTE: SOME GENERIC ****	****	****	****	****	****	****	****DESCRIPTION**
** **

## Route Advisory Format – Example

**     **
_**Title:**_  ADVZY 068 DCC 12/20/02 RTE ADVZY PLAYBOOK_RQD/FL
_**Name:**__** **_**FCA001**
_**Constrained**__** Area:**_ ZOB/ZBW/ZNY/ZDC LANDING TRAFFIC
_**Reason:**_ TSTMS
_**Include Traffic:**_ ZDV/ZLA/ZLC/ZMP/ZOA/ZSE DEPARTURES TO BOS/BWI/CLE/DCA/EWR/IAD/JFK/LGA/PHL/PIT/TEB
_**Facilities Included**_: ZAB/ADV/ZLA/ZLC/ZMP/ZOA/ZSE/ZFW/ZME/ZTL/ZDC/ZNY/ZBW/ZAU/ZOB
_**Flight Status: **_**ALL **
_**Valid:**_ **FCA ENTRY TIME FROM 1545 TO 1800**
_**Probability of Extension:**_ LOW
_**Remarks:**_ NONE
_**Associated Restrictions:**_ NONE
_**Modifications:**_ NONE
_**Route (S):**_
- FROM:
- ORG				DEST			ROUTE
- -----				-----			---------------