Meeting Minutes for the

**Collaborative Routing (CR) Workshop Meeting**

**February 6^th^ & 7^th^, 2002**

The CR Workshop meeting was held at the Mitre Westgate building in
McLean, Virginia. In addition to the planned agenda items, several
additional items were discussed and are included in the minutes. The
draft Reroute Advisory Team Implementation Procedure is attached as
Appendix 1. Meeting briefings and presentations are available at
http://www.metsci.com/cdm/.

#### Section I: Attendees

+---+---------+-------+----------------+-----------+-------------------+
| # | #####   | ***   | ***O           | **        | ***email***       |
| # | ## *Las | First | rganization*** | *Phone*** |                   |
| # | t Name* | Na    |                |           |                   |
| # |         | me*** |                |           |                   |
| # |         |       |                |           |                   |
| # |         |       |                |           |                   |
| # |         |       |                |           |                   |
|   |         |       |                |           |                   |
| * |         |       |                |           |                   |
| \ |         |       |                |           |                   |
| # |         |       |                |           |                   |
| * |         |       |                |           |                   |
+===+=========+=======+================+===========+===================+
| 1 | Abbott  | Mike  | FAA            | 505       | [mike.abbott@fa   |
| . |         |       |                | .856.4540 | a.gov](mailto:Mik |
|   |         |       |                |           | e.abbott@faa.gov) |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 2 | As      | Fred  | FAA / SUPCOM   | 631       | <fred.a           |
| . | hendorf |       |                | .468.1319 | shendorf@faa.com> |
|   |         |       |                |           |                   |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 3 | Bassett | Phil  | ZJX TMU        | 904       | <philip           |
| . |         |       |                | .549.1543 | .bassett@faa.gov> |
|   |         |       |                |           |                   |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 4 | Ber     | Joe   | AAL            | 817       | [joe.bert         |
| . | tapelle |       |                | .968.9343 | apelle@aa.com](ma |
|   |         |       |                |           | ilto:Paul.hubbell |
|   |         |       |                |           | @americawest.com) |
+---+---------+-------+----------------+-----------+-------------------+
| 5 | Beatty  | Roger | AAL            | 817       | [rbeatt           |
| . |         |       |                | .931.0951 | y@gte.net](mailto |
|   |         |       |                |           | :rbeatty@gte.com) |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 6 | Brennan | Jack  | Mitre / CAASD  | 703       | <jb               |
| . |         |       |                | .883.5860 | rennan@mitre.org> |
|   |         |       |                |           |                   |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 7 | Browne  | Kevin | ARS-100        | 202       | [kevin.browne@fa  |
| . |         |       |                | .385.7706 | a.gov](mailto:Kev |
|   |         |       |                |           | in.brown@faa.gov) |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 8 | Bruce   | Roger | FAA /ZDV       | 303       | [roger.bruce@fa   |
| . |         |       |                | .651.4202 | a.gov](mailto:Rog |
|   |         |       |                |           | er.bruce@faa.gov) |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 9 | Buc     | Doug  | FAA ZLA        | 661       | <doug.bu          |
| . | kingham |       |                | .265.8255 | ckingham@faa.gov> |
|   |         |       |                |           |                   |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 1 | Bueno   | D     | ZBW            | 603       |                   |
| 0 |         | aniel |                | .879.6666 |                   |
| . |         |       |                |           |                   |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 1 | C       | Keith | MITRE/CAASD    | 703       | <                 |
| 1 | ampbell |       |                | .883.6221 | keithc@mitre.org> |
| . |         |       |                |           |                   |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 1 | Ch      | Tony  | Mitre / CAASD  | 703       | [achambliss@mitre |
| 2 | ambliss |       |                | .883.6611 | .org](mailto:Acha |
| . |         |       |                |           | mbliss@mitre.org) |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 1 | Clayton | Mark  | ZME NATCA      | 901       | <pclay            |
| 3 |         |       |                | .368.8250 | ton@accuship.com> |
| . |         |       |                |           |                   |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 1 | C       | Kelly | Mitre / CAASD  | 703       | <kc               |
| 4 | onnolly |       |                | .883.6627 | onnoll@mitre.org> |
| . |         |       |                |           |                   |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 1 | Collins | Dave  | ZFW TMU        | 817       | <dave             |
| 5 |         |       |                | .858.7537 | .collins@faa.gov> |
| . |         |       |                |           |                   |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 1 | C       | Ed    | ATCSCC         | 703       | <ed.              |
| 6 | orcoran |       |                | .904.4524 | corcoran@faa.gov> |
| . |         |       |                |           |                   |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 1 | Cragg   | Ed    | AUATAC/AUA-700 | 703       | <ed.c             |
| 7 |         |       |                | .345.6963 | tr.cragg@faa.gov> |
| . |         |       |                |           |                   |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 1 | Cranor  | Bill  | USAirways      | 540       | [w                |
| 8 |         |       |                | .972.7372 | illiamcranor@msn. |
| . |         |       |                |           | com](mailto:willi |
|   |         |       |                |           | amcranor@msn.org) |
+---+---------+-------+----------------+-----------+-------------------+
| 1 | Damato  | J     | NBAA           | 703       | <9-awa-atcsc      |
| 9 |         | oanne |                | .326.3819 | c-gadesk@faa.gov> |
| . |         |       |                |           |                   |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 2 | Davis   | A     | FAA /          | 781       | [arc              |
| 0 |         | rcher | ANE-530.5      | .238.7535 | her.h.davis@faa.g |
| . |         |       |                |           | ov](mailto:Archer |
|   |         |       |                |           | .h.davis@faa.gov) |
+---+---------+-------+----------------+-----------+-------------------+
| 2 | Dockan  | Gary  | US Airways     | 412       | [dockan@usairways |
| 1 |         |       |                | .747.1680 | .com](mailto:Dock |
| . |         |       |                |           | an@usairways.com) |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 2 | D       | Mic   | Mitre / CAASD  | 703       | <du               |
| 2 | uquette | helle |                | .883.4550 | quette@mitre.org> |
| . |         | A.    |                |           |                   |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 2 | Eure    | Paul  | TRW/AUATAC     | 703       | <paul.            |
| 3 |         |       |                | .345.8279 | ctr.eure@faa.gov> |
| . |         |       |                |           |                   |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 2 | Evans   | Jim   | MIT LL / UCB   | 781       | [jime@ll.mit.e    |
| 4 |         |       | NEXTOR         | .981.7953 | du](mailto:James. |
| . |         |       |                |           | wetherly@faa.gov) |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 2 | Fahey   | Tom   | NWA            | 612       | <t                |
| 5 |         |       |                | .726.3256 | om.fahey@nwa.com> |
| . |         |       |                |           |                   |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 2 | Failor  | Bill  | FAA            | 703       | <willia           |
| 6 |         |       |                | .904.4400 | m.failor@faa.gov> |
| . |         |       |                |           |                   |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 2 | Futer   | Aron  | Volpe          | 617       | <fut              |
| 7 |         |       |                | .494.3637 | er@volpe.dot.gov> |
| . |         |       |                |           |                   |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 2 | Gallus  | D     | Metron         | 703       | <g                |
| 8 |         | ennis | Aviation       | .771.4911 | allus@metsci.com> |
| . |         |       |                |           |                   |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 2 | Garcia  | Joe   | FAA / ZMA      | 305       | <joseli           |
| 9 |         |       |                | .716.1500 | n.garcia@faa.gov> |
| . |         |       |                |           |                   |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 3 | Gold    | Ru    | ATA            | 901       | <rgold@a          |
| 0 |         | ssell |                | .224.9918 | ir-transport.org> |
| . |         |       |                |           |                   |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 3 | Hall    | Wi    | AUA-460        | 202       | <will             |
| 1 |         | lliam |                | .366.9924 | iam.hall@faa.gov> |
| . |         |       |                |           |                   |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 3 | Harkin  | Mike  | Mitre / CAASD  | 703       | <m                |
| 2 |         |       |                | .883.6941 | harkin@mitre.org> |
| . |         |       |                |           |                   |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 3 | Henry   | Tony  | NATCA          | 304       | [henry@mounta     |
| 3 |         |       |                | .261.2276 | in.nst](mailto:he |
| . |         |       |                |           | nry@maintain.nst) |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 3 | Hoobs   | Gary  | FAA SoCal      | 858       | [garyhobbs@!f     |
| 4 |         |       | TRACON         | .537.5895 | aa.gov](mailto:Ga |
| . |         |       |                |           | ryHobbs@!faa.gov) |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 3 | Hopkins | Jean  | FAA / ATT-234  |           | [jean.hopkins@faa |
| 5 |         |       |                |           | .gov](mailto:Jean |
| . |         |       |                |           | .hopkins@faa.gov) |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 3 | Houde   | James | CTA / AUA-TAC  | 703       | [jhou             |
| 6 |         |       | / AUA-700      | .345.8787 | de@cta.com](mailt |
| . |         |       |                |           | o:Jhoude@cta.com) |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 3 | Huber   | Jack  | ZMP            | 651       | <ja               |
| 7 |         |       |                | .463.5512 | ck.huber@faa.gov> |
| . |         |       |                |           |                   |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 3 | Hu      | Mark  | Mitre / CAASD  | 703       | <m                |
| 8 | berdeau |       |                | .833.5906 | whuber@mitre.org> |
| . |         |       |                |           |                   |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 3 | Jackson | C     | Mitre / CAASD  | 703       | <cj               |
| 9 |         | laude |                | .883.6271 | ackson@mitre.org> |
| . |         |       |                |           |                   |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 4 | J       | D     | FAA/ANE        | 781       | <deborah.         |
| 0 | ohannes | ebbie |                | .238.7553 | johannes@faa.gov> |
| . |         |       |                |           |                   |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 4 | Kirby   | Scott | FAA ATLATCT    | 678       | [scott.kirby@fa   |
| 1 |         |       |                | .364.6107 | a.gov](mailto:sco |
| . |         |       |                |           | tt.Kirby@faa.gov) |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 4 | Klein   | Rich  | MIT/LL AvMet   | 202       | <r                |
| 2 |         |       |                | .646.0060 | klein@ll.mit.edu> |
| . |         |       |                |           |                   |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 4 | Klopf   | Mark  | Metron         | 703       | [                 |
| 3 | enstein |       | Aviation, Inc. | .787.8700 | klopfens@metsci.c |
| . |         |       |                |           | om](mailto:Willia |
|   |         |       |                |           | m.failor@faa.gov) |
+---+---------+-------+----------------+-----------+-------------------+
| 4 | Kohn    | Eliz  | Metron         | 703       | <kohn@metsci.com> |
| 4 |         | abeth | Aviation       | .234.0780 |                   |
| . |         |       |                |           |                   |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 4 | K       | Kevin | Metron         | 724       | [kollmann@metro   |
| 5 | ollmann |       | Aviation, Inc. | .857.3469 | n.com](mailto:Kol |
| . |         |       |                |           | lmann@metron.com) |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 4 | Kupper  | Kapri | ZDC TMO        | 703       |                   |
| 6 |         |       |                | .779.3787 |                   |
| . |         |       |                |           |                   |
|   |         |       |                |           |                   |
| K |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 4 | Lash    | Bill  | ZDC TMU        | 703       |                   |
| 7 |         |       |                | .771.3504 |                   |
| . |         |       |                |           |                   |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 4 | Leber   | Bill  | NWA            | 612       | [w                |
| 8 |         |       |                | .727.0293 | illiam.leber@nwa. |
| . |         |       |                |           | com](mailto:Willi |
|   |         |       |                |           | am.leber@nwa.com) |
+---+---------+-------+----------------+-----------+-------------------+
| 4 | Libby   | Mark  | FAA/ATCSCC     | 703       | <ma               |
| 9 |         |       |                | .925.3149 | rk.libby@faa.gov> |
| . |         |       |                |           |                   |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 5 | M       | Mark  | FAA\`          | 703       | <mark.            |
| 0 | archese |       |                | .326.3839 | marchese@faa.gov> |
| . |         |       |                |           |                   |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 5 | Martin  | John  | ATA            | 703       | <jmar             |
| 1 |         |       |                | .904.4534 | tin@airlines.org> |
| . |         |       |                |           |                   |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 5 | Matu    | Tim   | UAL            | 847       | <timothy.ma       |
| 2 | szewski |       |                | .700.3016 | tuszewsk@ual.com> |
| . |         |       |                |           |                   |
|   |         |       |                |           |                   |
| M |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 5 | Mather  | Steve | USAF AMC TACC  | 618       | <stephen.mat      |
| 3 |         |       |                | .229.0301 | her@scott.af.mil> |
| . |         |       |                |           |                   |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 5 | Mc      | Mike  |                | 630       | [mcphemike@i      |
| 4 | Pherson |       |                | .906.8342 | nil.com](mailto:m |
| . |         |       |                |           | cphemike@faa.gov) |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 5 | Meyer   | Darin | MIT Lincoln    | 407       | <d                |
| 5 |         |       | Lab            | .855.3593 | arinm@ll.mit.edu> |
| . |         |       |                |           |                   |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 5 | Moffatt | John  | Boeing Aim     | 703       | <john.e.mo        |
| 6 |         |       |                | .584.2938 | ffatt@boeing.com> |
| . |         |       |                |           |                   |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 5 | Mullen  | Ken   | AUATAC /       | 703       | <ken.ct           |
| 7 |         |       | AUA-700        | .345.6683 | r.mullen@faa.gov> |
| . |         |       |                |           |                   |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 5 | Murphy  | Mic   | ATSCC TMS      | 703       |                   |
| 8 |         | helle |                | .904.4523 |                   |
| . |         |       |                |           |                   |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 5 | Naylor  | Jerry | NATCA          |           | [                 |
| 9 |         |       |                |           | mailto:nayalaska@ |
| . |         |       |                |           | alo.com](mailto:n |
|   |         |       |                |           | ayalaska@alo.com) |
+---+---------+-------+----------------+-----------+-------------------+
| 6 | Ogles   | Mi    | FAA            | 770       | <mi               |
| 0 |         | chael |                | .210.7974 | ke.ogles@faa.gov> |
| . |         |       |                |           |                   |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 6 | Oiesen  | Rick  | Volpe          | 617       | [oiesen@volpe.dot |
| 1 |         |       |                | .494.2309 | .gov](mailto:Oies |
| . |         |       |                |           | en@volpe.dot.gov) |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 6 | Phaneuf | Mark  | Avmet /        | 703       | <p                |
| 2 |         |       | ARS-100        | .351.5649 | haneuf@avmet.com> |
| . |         |       |                |           |                   |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 6 | Rh      | Sid   | NWA            | 612       | [s                |
| 3 | inehart |       |                | .726.0080 | id.rhinehart@nwa. |
| . |         |       |                |           | com](mailto:Sid.r |
|   |         |       |                |           | hinehart@nwa.com) |
+---+---------+-------+----------------+-----------+-------------------+
| 6 | Reid    | Time  | NWA            | 612       | <timo             |
| 4 |         |       |                | .727.0294 | thy.reid@nwa.com> |
| . |         |       |                |           |                   |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 6 | Ro      | David | ATT-260        | 703       | <david.r          |
| 5 | denhuis |       |                | .925.3120 | odenhuis@faa.gov> |
| . |         |       |                |           |                   |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 6 | Ro      | Marty | FAA / ZNY      | 631       | <marty.r          |
| 6 | senberg |       |                | .468.1080 | osenberg@faa.gov> |
| . |         |       |                |           |                   |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 6 | S       | Lo    | COA            | 713       | [lsandu@          |
| 7 | andusky | raine |                | .324.7276 | coair.com](mailto |
| . |         |       |                |           | :Mjnadon@twa.com) |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 6 | Schocke | Bill  | UPS Airlines   | 502       | <                 |
| 8 |         |       |                | .359.1666 | wschocke@ups.com> |
| . |         |       |                |           |                   |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 6 | Sherry  | Joe   | Mitre / CAASD  | 703       | <j                |
| 9 |         |       |                | .833.5293 | sherry@mitre.org> |
| . |         |       |                |           |                   |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 7 | Smith   | Phil  | OSU            | 614       | <philt+@osu.edu>  |
| 0 |         |       |                | .292.4120 |                   |
| . |         |       |                |           |                   |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 7 | Tefre   | Joni  | NWA            | 612       | <jo               |
| 1 |         |       |                | .726.0607 | ni.tefre@nwa.com> |
| . |         |       |                |           |                   |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 7 | W       | James | FAA            | 703       | [jam              |
| 2 | etherly |       |                | .326.3841 | es.wetherly@faa.g |
| . |         |       |                |           | ov](mailto:James. |
|   |         |       |                |           | wetherly@faa.gov) |
+---+---------+-------+----------------+-----------+-------------------+
| 7 | W       | Erwin | ARS-100/AvMet  | 703       | <wi               |
| 3 | illiams |       |                | .351.5659 | lliams@avmet.com> |
| . |         |       |                |           |                   |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 7 | W       | Gre   | Metron         | 703       | [wilmouth@met     |
| 4 | ilmouth | tchen | Aviation, Inc. | .787.8700 | sci.com](mailto:J |
| . |         |       |                |           | nehman@erols.com) |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 7 | Wyman   | Pete  | USAF           | 781       | <pe               |
| 5 |         |       |                | .238.7901 | te.wyman@faa.gov> |
| . |         |       |                |           |                   |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+
| 7 | Zi      | C     | ZID TMU        | 317       | <cheryl.z         |
| 6 | browski | heryl |                | .247.2484 | ibrawski@faa.gov> |
| . |         |       |                |           |                   |
|   |         |       |                |           |                   |
+---+---------+-------+----------------+-----------+-------------------+

#### **Section II: Agenda**

# Collaborative Routing Workshop Agenda

#### **February 6-7, 2002**

####### Mitre Westgate Building

# Day 1 Wednesday February 6, 2002

**0900-0915 Opening and Introductions: Deb Johannes/Bill Cranor/Tony
Henry**

Where have we been and where are we going

Changes in the organization

NATCA update

**0915-0930 House keeping items: Kelley Connelly**

**0930-1000 Military Workgroup update: Bill Leber and Lt. Col. Wyman**

**1000-1015 Break**

**1015-1045 FCA/FEA/CCSD Update: Ed Corcoran and Tony Henry**

**1045-1130 Update on Early Intent/Flight Plan Preprocessor: Mitre
Corp.**

**1130-1230 Lunch**

**1230-1315 Update Automated Congestive Management Tool: Mitre Corp.**

**1315-1445 Multi-Fix, Distance based GDP's, EDCT +/- 5 Minute Window
Test: Metron Aviation**

**1445-1500 Break**

**1500-1545 Preemptive TFM: Mark Huberdeau**

Transcon Routing Options

**1545-1630 Playbook Update: Jeff Richards, Steve McMahon and Bruce
Wood**

# Day 2 Thursday February 7, 2002

**0800-0830 CCFP Update: Bill Failor and Mark Phaneuf**

Training

Evaluation

Changes

**0830-0915 Weather Products**

NCWF: Dave Rodenhuis

NOWRAD on TSD/CCSD: Rick Oiesen

CIWS: Jim Evans

**0915-0930 RMT: Gretchen Wilmouth**

**0930-1030 RAT Update: Mike Murphy, Keith Campbell and Roger Beatty**

**1030-1045 Break**

**1045-1115 S2K Training Update: Charlotte Happle**

**1115-1130 Pathfinder Tool/Diversion Recovery Tool/TCA Guidelines: John
Martin**

**1130-1230 Working Lunch**

**1300 Wrap up**

**Section III: Topics and Discussions**

**Day 1**

**Wednesday, 06 February 2002**

######## Opening and Introduction

Bill Cranor opened the Workshop and welcomed all participants. MITRE
provided the logistics for the meeting including information on building
security. Bill reported that the airlines are implementing an airline
workgroup to keep up with the overall activities. This will allow the
best use of very limited funds and resources by the airlines. Bill
reported that the agenda is flexible, and everything on it will be
covered during the meeting. Bill introduced Bill Leber and Debbie
Johannes as new Co-chairs. He also introduced Tony Henry as the NATCA
Rep.

In future we would like to institute a workgroup management organization
with a following of the workgroups closer to justify funding.

Debby Johannes is the new FAA lead and Co-chair. Debbie provided her
perspective on the goals for the future. One of the main goals is to
find ways to be more productive and efficient. We have many
opportunities but we need some focus and structure. We need to be more
effective and efficient due to tight resources. We need to ensure
meetings are published to keep everyone informed. She noted that SUPCOM
has a representative here for the first time and this is important.

Bill Leber is now the CDM Industry Co-chair. Bill advised not to expect
huge, major changes; but to expect many small changes that will be very
important to assist the survival of the airlines during this rough time.
Bill thanked FAA for continuing with this Workshop. While there are
unlikely to be major changes, there are a lot of little increments that
need to be done and will be necessary for the airlines. He stated that
this might be the last CR Workshop in this format. Hopefully the change
will be for the better.

AUA involvement will continue with Jim Wetherly as the lead.

Tony Henry, ATCSCC NATCA Representative, introduced his replacement
Jerry Naylor, from the IAD Tower. Tony will transition his duties to
Jerry over the next few weeks with March 8, 2002 as the effective
replacement date.

Tony said he expects NATCA to continue to participate in future
workgroups under Article 48 of the Collective Bargaining Agreement.
There is a specific, immediate need to assign NATCA representatives to
this group. Tony wants volunteers, with the usual caveat of NATCA
reserving the right to utilize their internal selection process as
applicable.

## 1.1 Action Item -- The CR Group needs NACTA representative(s) to support the CR group and sub-groups. (Tony Henry/Jerry Naylor, NATCA)

Fred Ashendorf of ZNY was introduced as the first FAA Air Traffic
Supervisor's Committee (SUPCOM) representative to participate in the CR
Workshop.

Bill Cranor encouraged the individual workgroups to provide specific
feedback and communicate activities to the larger group. Group leaders
have the responsibility to ensure their actions are focused, and to
ensure meeting/activity schedules do not overlap. It is the
responsibility of the Leads to provide timely meeting reports, minutes,
etc.

Workgroup Leads will be responsible for:

-   Developing concept papers and documenting requirements that can be
    used by the tool builders.

-   Arranging for and coordinate meetings, agendas, and facilities.

-   Establishing and maintaining timelines

-   Forwarding minutes of meetings and telcons to co-chair.

-   Reporting out at workshops and other meetings

Bill Leber interjected that it is anticipated that many more activities
will be conducted over the web in the future so all participants should
become more familiar with the web sites. As for now, all information
that destined for the web site will go through the CR Leads. The web
will be a major focus for future work.

Metron will put CR workgroup/subgroup information on the CDM CR web site
as they receive it. Web site input needs to be coordinated with
Leads/Co-Leads and sent to DeAnna Hines of Metron Aviation at
"hines@metsci.com". All members should be familiar with the web site and
its contents to "self brief" current CR activities.

Debbie stated that the S2K team supports us but needs to know what we
are doing. She said the CR Group must provide S2K and Jack Kies regular
updates on the progress and plans of the overall Team.

Debbie has expectations that Workgroups should have resources and plans
to develop procedures and training from the beginning as the workgroups
develop or enhance products. We need to ensure that the groups are
comprised of members with broad-based backgrounds, AT, IT, Training,
Procedures, etc.

Bill Cranor and Debbie further discussed the process of team makeup and
when and how the correct resources might be allocated to workgroups,
especially Training. New groups need to have the correct composition of
people from conception. Old groups may need to have people added for the
correct composition. Ed Corcoran voiced some concern that the Training
Department should usually be involved; but, does not have sufficient
resources to participate in all activities. Mike Ogles made the point
that it is vital to all activities to have the SUPCOM involvement and
participation.

# Military Workgroup Update

Bill Leber introduced Mark Libby who will discuss VACAPES and military
issues. Mark reported that he and others had been working with the
military groups for over 3 years and the coordination process is slowly
improving. He did emphasize that the military still has the Number 1
priority. A trial was attempted last year using 4 "VS" routes. It was an
improvement, but the routes were only available about 30% of the time.
VS1 route from HTO to ORF is the base offshore route and is the only
route approved for /A aircraft. The other VS routes (VS1-VS8) are
parallel to and to the East of VS 1.

In the future when VS routes are needed to support SWAP the FAA will
request routes from the military. The military will release routes and
assign altitudes for FAA use (mission permitting).

One new route is being established that will always be available. Routes
will eventually be put in the Coded Departure Routes (CDR). Mark
reported that new resources will soon be in place at VACAPES and they
hope the current level of cooperation will continue.

Testing is scheduled for March 23^rd^ & 24^th^, and more details need to
be worked out like future military airspace needs (e.g. F22 testing,
...)

Bill Leber recognized Jim Wetherly, AUA-740 and identified him as one of
the constants in this overall process. He feels AUA will continue to
provide the support as new, good ideas are identified.

Bill Leber discussed the ramifications of the changes in military
procedures that might affect the airlines. A resource from the Military
Refueling Support area is now involved daily to help coordinate those
operations within CDM. Debbie advised that many of the Security and
Military issues couldn't be discussed in this workshop environment.
National Security is paramount and most understand this. Bill Cranor
asked if a special workgroup might be needed to work the many Security
and Military issues? The Military Rep, Lt. Col. Wyman, advised that
information flowing out of NORAD is slowly improving and there may be a
"military playbook" in the future so controllers will know what to
expect on specific operations.

The ZJX representative advised that they had an Air Force liaison until
recently; but they have been recently assigned to ZLC for the Olympics.

Debbie advised that there was a CAP SWAP Group to coordinate CAPs
horizontally and vertically known as the "Carmine Group". This group is
tightly restricted by Security clearance requirements. They need to
develop a "bridge" with the airlines when there are specific issues of
concern. It is understood that there are many things at different levels
that can't be discussed. A mechanism for communicating needs to be
established. The Airlines can send any concern back to this group via
Lt. Col. Wyman.

The ZNY representative advised that it was difficult to discern who and
what is classified and guidelines need to be determined and
disseminated.

> 2.1 Action Item - Setup a meeting to determine if a standing workgroup
> is needed to work the Military/Security CAP coordination issues with
> the airlines. (Bill Leber)

# FCA/FEA Update 

Tony Henry and Ed Corcoran provided a briefing on the Flow Evaluation
Area (FEA) and Flow Constrained Areas (FCA), the "Live" tests, the
status and role of the CRCT Core Team, and, to discuss training needs.
The overall role of the CRCT Core Team (CCT) is to provide input and
guidance throughout the design, planning, and deployment activities for
all functional product improvements and CHI upgrades to the CRCT
prototype and to determine sufficient maturity of well defined
functionality appropriate for migration to ETMS or other Traffic Flow
Management Infrastructure (TFM-I) systems. The Team will no longer be in
effect as of March 31, 2002 having met all of the stated objectives.
This is also the expiration date of the CRCT MOU. It is unknown at this
time if the role of the Team will be replaced in the future. The Live
Tests were designed to validate the procedures for FEA/FCA usage. This
was completed as of the fifth test on January 30, 2002. The airlines
(Bill Cranor) asked for copies of the Test Reports. Jim Houde will
provide John Martin, ATA, with copies for distribution. The ATCSCC
Strategic Planning Team and the airlines requested additional tests to
provide training for their members. One additional test has been
scheduled for February 20, 2002 for this purpose pending coordination
with NATCA.

> 3.1 Action Item - Provide FEA/FCA Test Reports to John Martin, ATA,
> with for distribution. (Jim Houde)

Overall, the test have had mixed results. Tony advised that ZID and ZKC
would be key sites since they have CRCT. The equipment has worked well
for the tests and the procedures are evolving. For the upcoming spring,
there should be enough functionality to help with the current filtering
available. The question was asked how training would be accomplished? On
March 4 & 5, 20 cadres will be trained and groups of 2 from that group
will travel to train field personnel. The airlines involvement in the
CRCT Core Team activities was brought up. The airlines were allowed to
participate in the last meeting.

Tony advised that his goal was to have a good baseline product in the
field by June. Many field resources felt the last LLT was too long. Tony
feels this will improve with time and as procedures are improved. Tony
advised that the "What if" capability would not be available with the
baseline FEA/FCA functionality. Tony suggested that the Core Team will
end their work on March 31 as originally planned and he is not inclined
to extend the Team. He feels that any future work should be done in a
different forum. This issue will be further discussed on Feb. 19 at a
Leadership meeting.

> 3.2 Action Item - At leadership meeting on 19^th^ successor to core
> team and other follow on activities need to be a topic of discussion.
> (CRCT Core Team)

Carol Wolfe, ATCSCC said that the FEA/FCA Training Package would be
available on Friday.

Lorraine Sandusky of COA is concerned that airlines need more specific
input to safeguard the economics of the airlines. Debbie wants to share
CDM draft Training and Procedures documents. ***Tony cautioned that I &
I is next week and the contents could change during that process.***

The Denver ARTCC rep. asked whether FCA functions would be strategic or
tactical and how will they relate to Monitor Alert? There will be no
Monitor Alert info available until the "What if" capabilities are
available.

# 

# Proposed FEA/FCA Training:

-   Training will be conducted at the 20 CONUS Centers (possibly
    Anchorage) and the ATCSCC.

-   Requesting 20 volunteers, management and bargaining-unit, from
    facilities with the Collaborative Routing and Coordination Tool
    (ZID, ZKC, ATCSCC).

-   All 20 individuals will receive two-days of training at the ATCSCC
    on

> March 4th and 5th.

-   The following week would be used train "own facility" personnel.

-   Target Audience:

    -   Operations Managers/National Operations Managers or their
        designees

    -   Traffic Management Officers

    -   Supervisory Traffic Management Coordinators/National Traffic
        Management Officers

    -   Traffic Management Coordinators/Traffic Management Specialists

-   Eighteen individuals will visit 18 facilities in teams of two, the
    weeks of

> March 18th and 25th. Two individuals are alternates for
> illnesses/emergencies.

-   Each team will comprise of one field representative and one ATCSCC
    representative. Additionally, the teams will have a maximum of one
    management representative.

-   The teams will try to cover 0700-1900, Tuesday through Thursday, to
    cover day and swing shifts; one 0700-1500 and one 1100-1900.

-   During the training on March 5 and 6, the instructors will be
    assigned their facilities.

-   The training package will be mailed to the facilities in advance.

-   BFOT will be available for the instructors.

-   A briefing package will be available for supervisors and
    controllers. If jointly desired by the facility and the team, a
    briefing may be given to the controllers.

-   Facilities will be requested to schedule training slots. It is
    estimated to take 3-hours with a maximum of two students at a time.

-   Terminal facilities may get training at the ARTCC.

This training is contingent on successful Impact and Implementation
(I&I) bargaining scheduled for the week of February 11, 2002.

# CCSD Update

Rick Oiesen provided the status update on the CCSD. The CCSD is the
Airline version of the TSD/WSD. Version 2.5 was delivered on 2/4/02 to
the ATCSCC for testing. When testing is complete (\~2 weeks) it will be
available to the airlines.

Version 2.5 includes to following new features:

-   An overlay box to pick individual colors

-   Dynamic FCA lists that update each minute

-   Added Hold and Refresh buttons

-   Can now filter by airline

-   Shorter URLs, Back button will no longer work

-   Bookmarks will no longer work

-   Now have a save screen function; but will have to input user name

-   WSD and CCSD now have the same methods

-   Allowed entries increased from 6 to 20

-   Can control weather settings

Rick requested that any suggestions be emailed to him at Volpe as he
continues to implement many of the suggestions he receives. He would
also like a prioritized list of desired items from the airlines.

Another drop is scheduled for April.

# Preemptive TFM

# Transcon Routing Options

Mark Huberdeau and Jack Brennan of MITRE briefed the attendees on
high-level concepts for Transcon Routings. Because weather constraints
may not materialize, debates are common during SPT's about applying a
play or wait and see what materializes. When strategic decisions need to
be made accurate demand information is not available because user intent
is unknown. Allowance must be made for inaccuracies in 6hr+ weather
forecasts. New ETMS functions may aid in the expansion of the "Midnight
Cargo Test". The goal is to reduce reroutes on transcontinental flights.

Mark also reviewed possible alternative approaches and discussed the
uncertainty of weather forecasts.

Possible benefits include:

Bridge the gap between strategic and tactical,

Includes active flights only in decision making verses historical
routings,

Allow some flights to file through incase WX does not materialize.

FCA setup and process for alternative "B" (see briefing) was reviewed in
detail. These are strictly concepts at this point, not thought out in
detail. The general approach is to use a transition FCA that is
approximately 1-hour flying time from the primary FCA.

# Multi-Fix GDP Status

Mark Klopfenstein of Metron Aviation provided the attendees with
briefings on Multi-Fix, Distance based GDPs, and EDCT +/- 5 Minute
Window Test.

Multi-Fix GDPs create arrival slots for fix(s) as well as airports. Mark
demonstrated creating Multi-Fix GDPs. Mark advised that they would use
the current concept of RBS, which has minimum risk. Airline agreements
may be needed during initial implementation not to sub until bugs have
been flushed out. They need some input from ATC to develop the best
rules for testing. There was a discussion on how and who might be on a
Multi-Fix GDP working group that would run human-in-the-loop scenarios.
Debbie assigned individuals to this group.

Multi-fix GDP working group was established. (CR/A&D crossover)

-   NATCA

-   ATCSCC (Procedures and Automation)

-   CR Rep

-   A&D Rep

-   NBAA

-   Metron

-   Volpe

-   TMU (terminal/center)

Need a small group for initial testing (present at test facility: one
Airline, one CC, & 2 or 3 others.) and to lay the groundwork for the
group. This small group needs to keep the group informed and provide web
site updates about their activities. Metron would like to run about 1
test per month.

Initial Group:

1.  Joe Bertapelle -- AAL (Airline Lead)

2.  Kapri Kupper -- ZDC/DCC (+1 ATCSCC East Splst)

3.  ZAU / ZTL

4.  Tim Matuszewski -- UAL

One issue is that GDP models are based on forecast weather not actual
weather. Research continues on Multi-Airport and Playbook GDPs.

Mark demonstrated a new concept in which more graphics are used to
display data. This is an evolving prototype and this type of interface
will be more feasible with Java.

# EDCT Change Updates (±5 minute window)

Mark Klopfenstein provided the update on the proposed change to the EDCT
window to +/- 5 minutes. The current EDCT window is +5 --15 minutes. The
overall issue of EDCT compliance was discussed and that improved
compliance was the reason for the proposed change. Joe Bertapelle of AAL
cautioned the group that there are huge issues for the airlines related
to making any changes to EDCT procedures.

Mark proposed the use of an ECR (EDCT Change Tool) tool. The proposed
tool is simply a way to fill an empty slot. The changing of the window
for EDCT to +/- 5 minutes is a separate issue.

Testing is tentatively scheduled for April. Mark said that issues
similar to Slot Credit Substitution's need to be resolved. The Airlines
see lots of slot issued and a group is meeting to work them out. Bill
Cranor stated that the Airlines have major issues and not all of them
will be resolved by April. Also, a tool is being developed to deal with
a flight that misses a slot.

Jean Hopkins, ATT reported that the procedures are completed for the
EDCT reduction. Planes will be dealt with manually and individually
during the April test when the EDCT reduction takes effect. AOCs and the
FAA will work the phones and resolve problems manually. More manpower
will be available during the testing to work individual flights.

# Distance Based GDPs

Mark Klopfenstein demonstrated Distance Based GDPs user interface. Mark
initiated a power run and reviewed the statistics table and how you use
and run the graphical display for Distance Based GDPs. He explained the
trade-off curve and how unrecoverable delays might be used to select the
best distance for Distance Based GDP initiatives. Mark said these new
features would be fielded in the future using the JAVA version of FSM.
Mark welcomed feedback now while development is still ongoing.

1.  Overview of 6 December Evaluation of Automation-Assisted Weather
    Problem Resolution

Joe Sherry of MITRE briefed the attendees on AWPR (Automated assisted WX
Problem Resolution). The AWPR was in Concept Exploration from 99-01. On
12/6/01 the AWPR went through concept validation. 11 FAA/Industry
personnel participated. Concept development is ongoing. AUA-700 is the
program sponsor and the CRWG is participating. A primary goal of the
AWPR is to help limit reroutes to flights impacted by weather and to
tailor rerouted/GDPs for each flight. See the detailed briefing slides
for additional information on the AWPR objectives, concepts, and list of
automated features.

After a complete review of AWPR concept elements and features, Joe
walked the group through the evaluation results. Overall ratings were
3-5 (moderately to very useful). Joe said that industry ratings tended
to be lower. The next evaluation will focus on collaboration. We also
reviewed the major recommendations from evaluator's comments.

# 2002 Playbook routes

Jeff Richards of the ATCSCC provided a briefing on the 2002 National
Playbook, Canadian Route Expansion. Most of the briefing concerned the
finalization of the Canadian routes.

CAN 1 thru 6 will be available on Feb. 21, 2002 but will not be mapped
until June. All of the routes are RNAV except CAN 6. CAN 5 West will
have a fix moved in April to ensure boundary clearance of a military
area.

Canada has agreed to have at least 2 routes available all the time. The
East bound route will always be the most southern route to avoid
flow/crossing issues.

**Section III: Topics and Discussions**

**Day 2,**

**Thursday, 07 February 2002**

# Recap

Bill Cranor welcomed the group to Day 2 of the workshop. Debbie Johannes
provided the group with a recap of Day 1. Debbie stated that Day 1
provided a lot of new concepts and feedback from the field facilities
was needed. On Day 1 we covered a lot of military issues and need
feedback on what type of information we need during military meetings.
The following list was developed for the meeting with the Military at
the end of the month:

-   Advance notice/pre-coordination on CAPs and Refueling altitudes.

-   Greater details on what is classified and not classified.

-   FAA resources sometime man the "Hotlines" and it appear they may
    need more training to provide expedited services.

-   Better utilization of on Coded Departure Routes / Low Altitude
    Departure Routes from N90 to manage military constraints.

-   When possible more advance info on Military operations.

-   Need to attempt to increase trust between the FAA and Military.

-   Explore options that might de-classify information to assist the
    airlines. Airlines need operational info\-\--they don't need to know
    the "Why".

-   Need to attempt to increase the flow of information at the SPTs,
    especially any info concerning the military and their operations.

-   Follow-up and feedback on system breakdowns so we can learn and do
    things to do things better.

-   Better utilization of review processes.

# CCFP usage Study

Mark Phaneuf of AVMet and Bill Failor, FAA briefed on the most recent
CCFP operational study being conducted by AvMet and Metron Aviation. The
goal of the study is to see if the CCFP is being used as intended. Mark
provided background and previous study results. He provided an overview
of the CCFPs issued (they are top heavy in "Low" area coverage) and
reviewed the methodology used in their study.

Methodology:

-   Define the area that defines the CCFP,

-   Compute flights through during the effected time,

-   Compare that to the flights through during no CCFP,

-   The computed % reduction (min/max/ave) will be compared to the %
    reduction table previously developed.

> Accomplishments:

-   A data collection tool has been devolped,

-   The area has been selected,

-   Baseline days have been selected.

The next step is to coordinate with STP logs, flight plans filed versus
flown, GS's, and GPD's. Additional details about the study are available
in the briefing slides provided by Mark.

The question was asked, could you sort out and/or eliminate the
GA/Corporate flights from the study? Mark advised that the study was in
the early stages and this had not been considered.

Mike Ogles of ZTL advised that no official training on CCFP or on an
Operational Concept had been done; therefore no baseline is available.
Jim Evans of Lincoln Labs discussed the difference of using large areas
within CCFP vs. using small, identified areas of weather in other
products. Debbie suggested that every effort should be made to "home in
on" the issue of characterizing tops as this is very important. She
emphasized the importance of training on CCFP, both what it is and how
it is to be used. Mark advised that the individual airlines had better
training schemes than the FAA. All wanted to make it clear that CCFP was
developed as a tool for strategic planning, specifically to streamline
the SPT.

# CCFP for 2002

Bill Failor, FAA briefed on the 2002 version of CCFP that will be
available on March 1, 2002. AWC is working on a concept to be able to
update and amend outputs during fast changing weather. AWC is developing
a text box to help explain the forecast. The FAA and NWS are also
developing a lesson plan on CCFP (it's currently out for comment). Tony
Henry is concerned that any CCFP training be consistent across industry
and the country. Past training was just a briefing, but the perception
is that the CCFP has been trained --is has not!

It was emphasized that this is not a terminal forecast product. It is a
TFM strategic planning tool and the main convective weather forecast
product for SPTs.

There was a long discussion on the methods used to develop the CCFP
product, focusing on the relationship between the airlines weather
specialists vs. facility CWSUs. The ARTCCs feel their input is being
overridden regularly; therefore limiting the trust of the product. All
participants were encouraged to communicate any contrasting views via
the chat room or via E-Mail. Overall communications needs to improve.
The feedback process is not being utilized.

The airline representatives said that most airlines come to the SPTs
with a plan. AAL advised that they would not participate in the CCFP
chat rooms and the formulation of that product during 2002 due to
staffing reductions. Other airlines may be forced to pull out of SPTs
because of staff reductions.

> 13.1 Action Item --CR members need to talk to CWSUs about providing
> feedback on CCFP issues via the chat room or via E-Mail. (CR Members)

Rick Oiesen provide a short briefing on the CCSD changes to be expected
in ETMS 7.4 that will include the integration of the CCFP. He compared
the TSD/WSD to the CCSD. In April, the CCSD will be exactly the same
except you will not be able to "drag & drop" the data block.

Past CCFP data is archived and available on the web or through POET.

Rick also stated that CCFP amendments if/when they are available would
not be a problem as long as the format remains the same. If any CCFP
format changes are proposed they must be coordinated with the regular
ETMS releases. The AWC amendment proposal will probably be available to
be briefed and coordinated with Volpe at the next CR meeting.

> 13.2 Action Item --Get CCFP amendment proposal from AWC for
> distribution and coordination with the CR Group. (Kevin Brown)

# National Convective Weather Forecast (NCWF)

Dave Rodenhuis, Senior Meteorologist at the ATCSCC briefed on the NCWF
(National Convective Weather Forecast). Dave provided his thoughts on
planning and training needed for 2003. He quickly described the intended
use of the convective weather products available today.

CCFP = Strategic TFM

ITWS = Tactical

NCWF = National Forecast

Convective Sigmets currently used for convective weather are simple
polygons of weather in 60-minute forecasts that are subjective and cover
a large area. NCWF forecast contain complex polygons of weather, issued
every 5 minutes for weather the next hour, are automatically generated
and cover a small area. They are the "best guess" of where convective
weather will be in the next hour. The NCWF includes speed, movement, and
tops (FLs). The product is currently available at the ADDS web site
"<http://adds.awc-kc.noaa.gov/>".

Dave briefed the group on the characteristics and performance of the
NCWF as well as its strengths and weaknesses compared with other
products. See his briefing for additional specific details. The area of
coverage using the NCWF is reduced by a factor of 10. The NCWF is
scheduled for incorporation with the TSD/WSD/CCSD in March 2003.

They are still working on convective weather growth and decay to be
incorporated into the product. Mitre is working on metrics to determine
how the product should be used.

2.  Corridor Integrated Weather System (CIWS)

Jim Evans of Lincoln Labs briefed on CIWS (Corridor Integrated Weather
System) currently in the concept exploration stage. This would be a more
tactical weather tool used to "meter flow through the yellow boxes". The
CIWS product provides more details to allow route selection through CCFP
areas. The CIWS forecasts are 0-2 hours. However, utility drops after 60
minutes. The CIWS can be displayed on ITWS displays.

There are currently no official plans to integrate this into ETMS or
other currently used systems. A work group was suggested and formed to
further study this option in the future.

CIWS Integrate Tactical Process User Group.

1.  ZNY/ZBW/ZAU/ZID/ZOB/ATT-200

2.  Airlines (NWA/DAL/COA/AAL)

Representatives are needed for the February 26-28 meeting. Jim Evans
will provide the details to Debbie for coordination.

> 15.1 Action Item -- Provide meeting details to Debbie for coordination
> with the CR Group. (Jim Evans)

3.  Route Management Tool (RMT)

Gretchen Wilmouth of Metron provided an update on future changes to the
Route Management Tool (RMT). See handout for specific details. The chart
cycle was discussed as it relates to new or changed routes in RMT
including new ANRs (Advanced Navigation Routes) scheduled for released
in April 2002. Mike Olgles of ZTL advised that the 7210 mandates that
any route changes should be validated by all affected facilities and his
understanding was that ANR routes should be handled the same way.
Gretchen pointed out the future capability to use aliases such as
"DCALL" to identify all airports in the DC area. Gretchen said requests
for specific aliases could be sent to her. Mike suggested that use of
aliases should be standardized across all products, ETMS, RMT, etc.

> 16.1 Action Item -- Prior to routes being placed in RMT databases,
> ensure that they are validated by all impacted centers per the 7210.
> The 7210 may need to be updated to include ANRs. (TBD)

# Status of NOWRAD on TSD and CCSD

Rick Oiesen briefed on NOWRAD. On TSD, he reported that users should use
the 2K setting whenever possible. In CCSD, NOWRAD is only available at
the 8K setting. The airlines voiced a desire to have 2K CONUS data on
the CCSD and thought is was a high priority to maintain common
situational awareness. Rick wants the airlines to document desired
improvement they want on the CCSD.

# RAT Team

Roger Beatty and Mike Murphy briefed on the progress on RAT (Reroute
Advisory Team). Roger stated that the RAT team focus was to enhance
information exchange between the FAA and users. Mike led the group
through a review of the draft RAT Implementation and Procedures document
(attached as Appendix 1).

A procedure evaluation is scheduled for April 1, 2002. Lots of prototype
testing will take place in the summer of 2002.

Much discussion about who should make up aliases and the need for them
to come from a common sheet. Any new aliases from the RAT team need to
be coordinated and added to the list that has already been developed.

> 18.1 Action Item -- Provide the current list of aliases to the RAT
> team. (Bill Cranor)

The RAT team will report progress to the CR group and provide status
updates in June and August. The RAT team would like to make
recommendations for ETMS 7.6 implementation (March 2003). ETMS 7.6
requirements are needed by September 2002.

Rick Oiesen presented screen examples of the Volpe prototype tool and
Keith Campbell of MITRE showed examples of their prototype tool. These
tools will allow the testing of proposed RAT functions.

Rick said a "Create Route" dialog box would be implemented in ETMS 7.4.
Rick said the Volpe prototype could be implemented in ETMS 7.5 if the
evaluations are successful.

Roger emphasized that airlines need to participate in the prototype
evaluations.

> 18.2 Action Item -- Provide the examples of machine-readable
> advisories to the CR Group by the next meeting. (Roger Beatty)

# System 2000 Training

A briefing was provided on the ATCSCC Training plans for 2002, called
Systems 2000 that will start in February. There was much discussion on
how items are selected for training and why other items such as CCFP
continually are not considered. Many wanted to know why CCFP was not on
the list of items to be trained. The airlines advised that their funds
this year were extremely limited and they would not be able to
participate in the "Roadshows". They suggested that facility reps. come
to the ATCSCC and be briefed by the airline reps. so the airline
perspective would be included in the training. Any airline that wants to
participate in the training needs to provide a POC to the ATCSCC
training department.

> 19.1 Action Item -- Provide a list of questions to be included in the
> minutes. (Bill Cranor)

# Pathfinder Page

John Martin of ATA provided the Pathfinder Page briefing. The Pathfinder
training guideline document is ready and under review by the bargaining
representatives at the ATCSCC. John will request Tim Grovac to post the
guidelines on the Command Center Web Page and/or provide a copy for the
minutes (they will be posted on the CDM CR web site). John said that
most airlines were involved in the development of the guidelines. A
flight can only be entered onto the Pathfinder Page by the Airline.

> 20.1 Action Item -- Request Tim Grovac post the Pathfinder guidelines
> on the Command Center Web Page and/or provide a copy for the minutes
> (they will be posted on the CDM CR web site). (John Martin)

Rick Oiesen provided a quick briefing on the Pathfinder Tool.

# Diversion Recovery Tool

Rick Oiesen briefed on past and proposed changes to the Diversion
Recovery Tool. Reviewed version 1.7 changes deployed 1/9/02.

Reviewed version 1.8 changes including:

Airport Diverted to,

PGTD was removed,

Change in meaning of ETD (note was added),

Aircraft type was removed,

Priorities now I/Blank, ETD not prioritized.

The 2 ways flights get on the Diversion Recovery page are if DVRS is in
field 11 or if manually entered. Automatic entry using auto detect was
removed in December.

The removal of PGTD was questioned. There were long discussions on
exactly how to label the individual columns to safeguard the order of
priorities by the airlines. How should priority be determined? It was
suggested that diversion recovery page ETD should equal PGTD + 10
minutes. Debbie suggested that the tool be fielded as is and specific
feedback be solicited for future changes. Rick said most problems can be
quickly fixed, procedures/deployment take the longest.

# Proposed Preemptive TFM work group

Bill Leber suggested forming a workgroup to work issues he described as
"Preemptive TFM" to acknowledge traffic before the flight plan is cut.
These might be tools or products that target predictions/forecast in the
4 to 6 hour away range. Most thought that the issues he was identifying
were airline issues and he would attempt to form a work group in the
future for this.

# Meeting was adjourned

Section IV: Action Item Quick View

+-----+------------------------------------+----------------+----------+
| R   | Action Item                        | Actionee       | Suspense |
| ef# |                                    |                |          |
+-----+------------------------------------+----------------+----------+
| 1.1 | The CR Group needs NACTA           | Tony           | ASAP     |
|     | representative(s) to support the   | Henry/Jerry    |          |
|     | CR group and sub-groups.           | Naylor, NATCA  |          |
+-----+------------------------------------+----------------+----------+
| 2.1 | Setup a meeting to determine if a  | Bill Leber,    | ASAP     |
|     | standing workgroup is needed to    | NWA            |          |
|     | work the Military/Security CAP     |                |          |
|     | coordination issues with the       |                |          |
|     | airlines.                          |                |          |
+-----+------------------------------------+----------------+----------+
| 3.1 | Provide FEA/FCA Test Reports to    | Jim Houde.     |          |
|     | John Martin, ATA, with for         | AUATAC         |          |
|     | distribution.                      |                |          |
+-----+------------------------------------+----------------+----------+
| 3.2 | At leadership meeting on 19^th^    | CRCT Core Team | 2/19/02  |
|     | successor to core team and other   |                |          |
|     | follow on activities need to be a  |                |          |
|     | topic of discussion. CRCT Core     |                |          |
|     | Team                               |                |          |
+-----+------------------------------------+----------------+----------+
| 1   | CR members need to talk to CWSUs   | CR Members     |          |
| 3.1 | about providing feedback on CCFP   |                |          |
|     | issues via the chat room or via    |                |          |
|     | E-Mail.                            |                |          |
+-----+------------------------------------+----------------+----------+
| 1   | Get CCFP amendment proposal from   | Kevin Brown,   |          |
| 3.2 | AWC for distribution and           | ARS            |          |
|     | coordination with the CR Group.    |                |          |
+-----+------------------------------------+----------------+----------+
| 1   | Provide meeting details to Debbie  | Jim Evans, MIT |          |
| 5.1 | for coordination with the CR       | LL             |          |
|     | Group.                             |                |          |
+-----+------------------------------------+----------------+----------+
| 1   | Prior to routes being placed in    | TBD            |          |
| 6.1 | RMT databases, ensure that they    |                |          |
|     | are validated by all impacted      |                |          |
|     | centers per the 7210. The 7210 may |                |          |
|     | need to be updated to include      |                |          |
|     | ANRs.                              |                |          |
+-----+------------------------------------+----------------+----------+
| 1   | Provide the current list of        | Bill Cranor,   |          |
| 8.1 | aliases to the RAT team.           |                |          |
|     |                                    | USAirways      |          |
+-----+------------------------------------+----------------+----------+
| 1   | Provide examples of                | Roger Beatty,  | By next  |
| 8.2 | machine-readable advisories to the | AAL            | CR       |
|     | CR Group by the next meeting.      |                | meeting  |
+-----+------------------------------------+----------------+----------+
| 1   | Provide a list of questions to be  | Bill Cranor,   |          |
| 9.1 | included in the minutes.           |                |          |
|     |                                    | USAirways      |          |
+-----+------------------------------------+----------------+----------+
| 2   | Request Tim Grovac post the        | John Martin,   |          |
| 0.1 | Pathfinder guidelines on the       | ATA            |          |
|     | Command Center Web Page and/or     |                |          |
|     | provide a copy for the minutes     |                |          |
|     | (they will be posted on the CDM CR |                |          |
|     | web site).                         |                |          |
+-----+------------------------------------+----------------+----------+

Appendix 1

CDM Memorandum

\*\*1.2 DRAFT\*\*

Subject: Reroute Advisory Team Implementation and Procedures

To: RAT Team

From: Michael Murphy ATCSCC

Date: February 4, 2002

Vision

-   To dramatically increase understanding, throughout the National
    Airspace System of all ATCSCC advisories and their application.
    Clear and concise communication shall be developed to allow all
    involved parties, unambiguous interpretation of flights affected by
    reroutes and useful comprehension of the reroute goals and
    processes.

-   To foster participation, faster response and complete compliance
    with all reroute issues.

-   To substantially decrease workload associated with reroute
    advisories.

-   To provide improved support for all people involved in the advisory
    process; FAA, Military, Airlines, General Aviation and Analysts for
    Quality Assurance.

-   To develop procedures and processes that are measurable and proven.

-   To automate these processes wherever possible, to enhance all other
    aspects of the reroute advisory system.

1.0 Scope

The CDM process for the Reroute Advisory Team has identified the need to
plan for implementation of the automated advisory process. The upcoming
releases of ETMS will allow for implementation of some of the workgroups
concepts. To accomplish this, it is necessary to set priorities and
identify timelines. We should also have a clear understanding of
component functionality and the expected return from the users of this
technology. Additionally, roles and responsibilities need to be
formulated for ETMS implementation and use of data.

2.0 Implementation Dates

The implementation of the automated advisory process will coincide with
ETMS releases scheduled as follows:

a.  ETMS Release 7.4.0 Spring 2002

b.  ETMS Release 7.5.0 Fall 2002

c.  ETMS Release 7.6.0 and later Spring 2003+

```{=html}
<!-- -->
```
3.  System Functionality

System functionality is currently addressed in another document
entitled: Draft System Requirements for Reroute Advisory Functionality.
This document is currently under development.

4.  ETMS Release 7.4.0 (Spring 2002)

    1.  Goals

> The objectives for the time period encompassing ETMS release 7.4.0 are
> testing and communication. The ETMS 7.4 production release will
> include no new RAT functionality. ETMS will provide a support and test
> string, in a background process, to allow for the generation of flight
> lists. A modified TSD will be defined in the Severe Weather unit to
> run these processes, autosend will be enhanced to incorporate the
> sending of lists, and at least one new process will be developed to
> coordinate the routing of flight lists. The test string will use
> active reroutes, active flight plan data and historical routes for
> evaluation.
>
> The TSD Create Reroute dialog box and the MITRE RAT prototype will run
> in parallel to evaluate functionality, accuracy, and procedures.
> Testing will begin April 1, 2002 with the MITRE RAT prototype and June
> 2002 with the ETMS prototype. The team will review the flight lists to
> measure accuracy of the data generated. Feedback will be utilized to
> identify future requirements and problems with the process. An initial
> report due June 15 and a definitive report due by September 15 will be
> produced by the workgroup to keep the CR workgroup informed and
> provide input to ETMS 7.5+ development.
>
> A concept that was identified by the team is the need to improve
> communication contained in the reroute advisories. The first step in
> this process is the standardization of the advisory format and the
> software that will be utilized to generate the advisory. Work will be
> directed by the team to begin the structure and development of
> procedures to clarify advisory format and communication. A workgroup
> will be formed to identify the problems and formulate solutions to
> these issues. We expect this to be an ongoing process within the
> reroute team through all phases of implementation.

2.  System Components

> The following components will be included in ETMS Release 7.4.0:

-   Command Center Advisory - This will contain the current format that
    the command center uses today.

```{=html}
<!-- -->
```
-   Create Reroute Dialog Box -- This is the software tool under
    development, which allows the Severe Weather Specialist to input and
    import data that will be contained in the advisory. It will also
    generate a depiction of the route in ETMS.

    1.  Prototype Responsibilities

        1.  ATCSCC

A.  The Severe Weather Specialists will use the "Create Reroute Dialog
    Box" to shadow real Severe Weather events.

B.  The Severe Weather unit will generate test lists and review them for
    accuracy.

> C. In cases where the advisory contains unusual elements, particularly
> special exclusions, that make the flight list either incomplete or to
> contain excess flights, the specialist will note this in the remarks
> using a standardized term.

1.  System Users that receive Flight Lists

```{=html}
<!-- -->
```
A.  Users are responsible to receive flight lists and review them for
    accuracy.

    1.  FAA Facilities

```{=html}
<!-- -->
```
A.  During the first release of the reroute advisory automation process,
    FAA field facilities shall comply with all current procedures
    regarding command center advisories.

B.  No responsibilities for handling receipt of the flight list are
    identified. This is to allow for a period of feedback and program
    error resolution.

> *Note*: *FAA Facilities may be requested for test periods to review
> the advisory format and flight lists. User and Facility feedback will
> be solicited to enhance the later releases of ETMS. Destination
> addresses in the AUTOSEND program can be changed to allow exclusion
> and inclusion of participants on short notice.*

3.  Training

```{=html}
<!-- -->
```
A.  Severe Weather Specialists in the ARTCC will be trained on the
    "Create

> Reroute Dialog Box and it's components.

B.  Identified Users participating in Prototype testing will train their
    workforce on application of current advisories and their meaning.
    Additionally, the Users will communicate the use of flight lists
    generated through testing and recommend changes to the team.

C.  The RAT team will develop a survey form to ensure feedback remains
    focused on key issues.

    3.  Communications

> The team will form a workgroup to identify wording and phrasing in
> advisories that cause breakdowns in communication. The group will
> formulate and recommend changes to the team to clarify these
> advisories.

4.  Automation

4.6.1 ATCSCC Automation

A.  The ATCSCC Automation department will develop and implement the

> "Create Reroute Dialog Box".

B.  The ATCSCC Automation department will provide a test string for
    prototype development of reroute components. This will include the
    capability for a TSD in Severe Weather to generate and send flight
    lists.

> **4.6.2. TSD/ETMS Evaluations:**
>
> [Goals]{.underline}
>
> Evaluate the accuracy of the most basic flight list capability within
> the ETMS architecture.
>
> Evaluate reliability and configuration of the list communication
> process.
>
> Wargame procedures, particularly on the user end.
>
> Provide users an opportunity to develop tools and procedures for
> exploiting the information contained in the lists.
>
> [Features and Limitations to be ready for evaluation by June
> 2002]{.underline}

-   Structured advisory identical to ETMS 7.4 production version.

-   Support for CDRs

-   Initial flight list only. No updates. However the list shall contain
    the ETMS list request(s) that produced it.

-   Limited list generation capability. Probably playbook reroutes only.

-   Use of 7.4 GUI. List issuance will be turned on in the background
    for wargaming purposes, and this test mode will be invisible to
    specialists issuing reroute advisories.

> **4.6.3. CDM RAT MITRE prototype evaluations.**
>
> [Goals]{.underline}
>
> Evaluate additional features recommended for ETMS 7.6+ that cannot be
> conducted using TSD/ETMS. The prototype will be adapted to look and
> feel as much like the ETMS 7.4 rerouting interface as possible, and
> designed to communicate with users using the same AOC\*Net channel as
> the ETMS prototype.
>
> [Features and Limitations to be ready for evaluation by April 1,
> 2002]{.underline}

-   Specialist can select whether or not to issue a list

-   Additional fields supporting aliases for terms like NYMETRO and
    precise time window definitions

-   Support for flight lists from ad hoc reroutes.

-   Specialist can save and recall ad hoc reroutes.

-   Automatic and manually issued flight list updates.

```{=html}
<!-- -->
```
-   The list shall contain the ETMS list request(s) that produced it.

```{=html}
<!-- -->
```
-   Generates human readable and XML lists.

-   No support for tagging flights by initial responsibility for the
    reroute.

-   Tagging of flights by responsibility for the reroute. (Initial,
    inadequate design)

-   No support for CDRs

-   No support for FCA integration.

[Additional Features to be added and evaluated as time
permits]{.underline}

-   Enhanced support for reroute advisory extensions, modifications, and
    cancellations.

-   Integration of FCA and RAT capabilities.

-   Reroute options

-   Altitudes

-   Initial Substitution

> **4.6.4. Initial List Capability**

The initial RAT functionality provides the following: When a severe
weather specialist at the Command Center creates a reroute, he can check
a box to indicate whether a list of flights affected by the reroute
should be sent to the airlines If this box is sent, then when the
advisory is sent, the TSD or some helper process will take the data used
to define the reroute, form a list request using this data, and send it
out to airlines that have requested these test lists. (The ETMS
prototype may not contain the checkbox. If not, ETMS will, during
designated test periods, automatically issue lists for all appropriate
reroutes issued by the specialist)

In cases where the advisory contains unusual elements, particularly
special exclusions, that make the flight list either incomplete or to
contain excess flights, the specialist will note this in the remarks
using a standardized term.

The list request will contain the data elements detailed below. ETMS
will be configured so that an airline gets these lists via the ARINC
teletype, via CDMnet, both, or neither; lists will only be sent to the
airlines that have requested to be included in the testing.

> **Data Elements in the Flight List**

1.  ETMS shall form the list of affected flights in the following way.

> If the user indicates that flows are restricted, then ETMS shall
> determine what flights are in the list of affected flights by doing
> one or more list request.

2.  In the list of affected flights, ETMS shall include the following
    data for each flight in the list. (Given in square brackets is the
    ETMS abbreviation for each item except for assigned route, for which
    there is currently no ETMS abbreviation.)

    a.  Departure ARTCC \[DCENTR\].

    b.  Arrival ARTCC \[ACENTR\].

    c.  Aircraft ID \[ACID\].

    d.  Origin airport \[ORIG\].

    e.  Destination airport \[DEST\].

    f.  Estimated time of departure \[ETD\]. (This is ETMS's estimate of
        the wheels-up time given all the data that ETMS has, including
        data that airlines have provided in CDM messages.)

    g.  Estimated time of arrival \[ETA\]. (This is ETMS's estimate of
        the wheels-down time given all the data that ETMS has, including
        data that airlines have provided in CDM messages.)

    h.  P-time \[PGTD\]. (This is the departure time in the flight plan.
        This is important since it indicates who has the responsibility
        to reroute a flight. The current rule is that if the P-time is
        more than 45 minutes in the future, then the airline has the
        responsibility; otherwise, the FAA has the responsibility.)

    i.  Initial gate time of departure \[IGTD\]. (The IGTD shows the
        original day and time of departure. This is included since,
        along with the aircraft ID, origin airport, and destination
        airport, this allows a flight to be uniquely identified, even if
        it is delayed into the next day.) The format shall indicate the
        day of month, hour of day, and minute of hour to support
        unambiguous flight matching.

    j.  Initial gate time of arrival \[IGTA\]. The IGTA corresponds to
        the IGTD on the arrival end.

    k.  **Assigned route(s**).

    l.  A copy of the text of the list request(s) that produce the
        flight list for this advisory and the advisory date and number.

    ```{=html}
    <!-- -->
    ```
    1.  
    2.  

-   
-   

```{=html}
<!-- -->
```
-   

```{=html}
<!-- -->
```
-   

```{=html}
<!-- -->
```
-   1.  

1.  
2.  
3.  
4.  
5.  
6.  
7.  
8.  
9.  
10. 
11. 
12. 
13. 
14. 
15. 
16. 
17. 
18. 
19. 
20. 
21. 
22. 
23. 
24. 
25. 
26. 
27. 
28. 
29. 
30. 
31. 
32. 
33. 
34. 
35. 
36. 
37. 
38. 
39. 
40. 
41. 
42. 
43. 
44. 
45. 
46. 
47. 
48. 
49. 
50. 
51. 
52. 
53. 
54. 
55. 
56. 
57. 
58. 
59. 
60. 
61. 
62. 
63. 
64. 
65. 
66. 
67.