Meeting Minutes for the

Collaborative Routing (CR) Workshop

**January 28-29, 2003**

The January 28-29, 2003 CR Workshop was held in Miami, FL. Several
planned breakout sessions were held during this workshop. The breakout
sessions included FCA/Reroute, ITFM, RAT, Playbook, NASCON, Training,
and Weather Applications. Minutes from the breakout sessions are
included as attachments or available on Workgroup web sites at
<http://www.metronaviation.com/cdm/workgroups.html>. Meeting briefings,
presentations, and supporting documentation are available at
<http://www.metronaviation.com/cdm>.

## Section I: Attendees

+---+----------+-------+-------------+------------+-------------------+
| # | ###      | ***   | ***Orga     | *          | ***email***       |
| # | #### *La | First | nization*** | **Phone*** |                   |
| # | st Name* | Na    |             |            |                   |
| # |          | me*** |             |            |                   |
| # |          |       |             |            |                   |
| # |          |       |             |            |                   |
| # |          |       |             |            |                   |
|   |          |       |             |            |                   |
| * |          |       |             |            |                   |
| \ |          |       |             |            |                   |
| # |          |       |             |            |                   |
| * |          |       |             |            |                   |
+===+==========+=======+=============+============+===================+
| 1 | ##       | Alex  | Mitre/CAASD | 70         | <al               |
| . | #######  |       |             | 3.883.7861 | shtein@mitre.org> |
|   | Alshtein |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 1 | Bair     | Dick  | Volpe       | 61         | b                 |
| . |          |       |             | 7.494.2393 | air@volpe.dot.gov |
|   |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 2 | Bassett  | Phil  | ZJX TMU     | 90         | <philip           |
| . |          |       |             | 4.549.1543 | .bassett@faa.gov> |
|   |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 3 | Beatty   | Roger | AAL         | 81         | [rbeatt           |
| . |          |       |             | 7.931.0951 | y@gte.net](mailto |
|   |          |       |             |            | :rbeatty@gte.com) |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 4 | Berggren | John  | FAA ZOA     | 51         | John              |
| . |          |       |             | 0.745.3332 | .berggren@faa.gov |
|   |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 5 | Be       | Joe   | AAL         | 81         | [joe.bert         |
| . | rtapelle |       |             | 7.967.8343 | apelle@aa.com](ma |
|   |          |       |             |            | ilto:Paul.hubbell |
|   |          |       |             |            | @americawest.com) |
+---+----------+-------+-------------+------------+-------------------+
| 6 | Birdsong | Mike  | HQ/AMC      | 61         | <Michael.birds    |
| . |          |       |             | 8-256-3700 | ong@scott.af.m.l> |
|   |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 7 | Brennan  | Mi    | Metron      | 70         | <Brennan@me       |
| . |          | chael | Aviation    | 3-787-8829 | tronaviation.com> |
|   |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 8 | Brown    | Ba    | NCAR/RAP    | 30         | <Bgb@ucar.edu>    |
| . |          | rbara |             | 3-497-8468 |                   |
|   |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 9 | Bruce    | Roger | FAA /ZDV    | 30         | [roger.bruce@fa   |
| . |          |       |             | 3.651.4202 | a.gov](mailto:Rog |
|   |          |       |             |            | er.bruce@faa.gov) |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 1 | Bu       | Doug  | FAA ZLA     | 66         | <doug.bu          |
| 0 | ckingham |       |             | 1.265.8255 | ckingham@faa.gov> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 1 | Cacioppo | Marty | FAA         | 20         | <Marty.           |
| 1 |          |       |             | 2-493-0093 | cacioppo@faa.gov> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 1 | Campbell | Keith | MITRE/CAASD | 70         | <                 |
| 2 |          |       |             | 3.883.6221 | keithc@mitre.org> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 1 | Catron   | Carol | ATCSCC      | 70         | <caro             |
| 3 |          |       | ATT-240     | 3.925-3135 | l.catron@faa.gov> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 1 | Christie | Ted   | US Airways  | 41         | <T                |
| 4 |          |       |             | 2-747-5062 | DC@usairways.com> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 1 | Connolly | Kelly | Mitre /     | 70         | <kc               |
| 5 |          |       | CAASD       | 3.883.6627 | onnoll@mitre.org> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 1 | Conroy   | Jay   | ZBW TMU     | 60         | [john j           |
| 6 |          |       |             | 3.879.6666 | conroy@faa.       |
| . |          |       |             |            | gov](mailto:john  |
|   |          |       |             |            | j conroy@faa.gov) |
+---+----------+-------+-------------+------------+-------------------+
| 1 | Cranor   | Bill  | USAirways   | 54         | [                 |
| 7 |          |       |             | 0.972.7372 | wcranor@adelphia. |
| . |          |       |             |            | net](mailto:willi |
|   |          |       |             |            | amcranor@msn.org) |
+---+----------+-------+-------------+------------+-------------------+
| 1 | Dalton   | Rick  | Southwest   | 21         | <                 |
| 8 |          |       | Airlines    | 4.792.2825 | rdalton@wnco.com> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 1 | Damato   | J     | NBAA        | 70         | jdamato@nbaa.org  |
| 9 |          | oanne |             | 3.326.3819 |                   |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 2 | Davis    | Barry | AUA-700     | 70         | [Barry.davis@f    |
| 0 |          |       |             | 3.326.3765 | aa.gov](../../../ |
| . |          |       |             |            | ../../../../../C: |
|   |          |       |             |            | /Documents%20and% |
|   |          |       |             |            | 20Settings/s08051 |
|   |          |       |             |            | 6/Local%20Setting |
|   |          |       |             |            | s/Temporary%20Int |
|   |          |       |             |            | ernet%20Files/../ |
|   |          |       |             |            | ../../c740252/Loc |
|   |          |       |             |            | al%20Settings/Tem |
|   |          |       |             |            | porary%20Internet |
|   |          |       |             |            | %20Files/OLKD/Bar |
|   |          |       |             |            | ry.davis@faa.gov) |
+---+----------+-------+-------------+------------+-------------------+
| 2 | DeBe     | Kevin | ZAB TMC     | 50         | k                 |
| 1 | nedittis |       | NATCA REP   | 5.856.4540 | evindeben@aol.com |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 2 | Ducot    | Beth  | MIT         | 78         | <                 |
| 2 |          |       |             | 1-981-7435 | Bethd@ll.mit.edu> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 2 | Durham   | Chip  | COEX        | 71         | <                 |
| 3 |          |       |             | 3.324.5505 | cdurha@coair.com> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 2 | Evans    | Jim   | MIT LL /    | 78         | [jime@ll.mit.e    |
| 4 |          |       | UCB NEXTOR  | 1.981.7433 | du](mailto:James. |
| . |          |       |             |            | wetherly@faa.gov) |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 2 | Fahey    | Tom   | NWA         | 61         | Tom.fahey@nwa.com |
| 5 |          |       |             | 2.726.3256 |                   |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 2 | Fa       | Jack  | Auatac      | 70         | <Jack.Fastn       |
| 6 | stnaught |       |             | 3-345-8893 | aught@auatac.com> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 2 | Fox      | Scott | FAA /       | 70         | [scott.fox@       |
| 7 |          |       | ATT-212 QA  | 3.904.4443 | faa.gov](mailto:S |
| . |          |       |             |            | cott.fox@faa.gov) |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 2 | Frame    | David | FAA ZHU     | 28         | <Dav              |
| 8 |          |       |             | 1.230.5530 | id.frame@faa.gov> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 2 | French   | Ba    | PHX STMC    | 60         | Barba             |
| 9 |          | rbara |             | 2.379.3684 | ra.French@faa.gov |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 3 | Futer    | Aron  | Volpe/ARCON | 61         | <fut              |
| 0 |          |       |             | 7.494.3637 | er@volpe.dot.gov> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 3 | Garza    | Ri    | FAA         | 120        | <Ricar            |
| 1 |          | cardo |             | 2-385-7654 | do.garza@faa.gov> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 3 | Gascoyne | Troy  | FAA         | 70         | <Troy.            |
| 2 |          |       |             | 3-904-4474 | gascoyne@faa.gov> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 3 | Gold     | Ru    | ATA         | 20         | <rg               |
| 3 |          | ssell |             | 2.626.4010 | old@airlines.org> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 3 | Grabbe   | Shon  | NASA        | 65         | <Shon.r.          |
| 4 |          |       |             | 0-604-1746 | grabbe@titan.com> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 3 | Grovac   | Tim   | ATCSCC /    | 70         | <ti               |
| 5 |          |       | ATT-200     | 3.904.4402 | m.grovac@faa.gov> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 3 | Happle   | Char  | ATT-240     | 70         |                   |
| 6 |          | lotte |             | 3-904-4449 |                   |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 3 | Hartman  | Mar   | FAA         | 70         | <Margaret         |
| 7 |          | garet |             | 3-904-4524 | .Hartman@faa.gov> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 3 | H        | Mike  | FAA         | 20         | <Michael.h        |
| 8 | awthorne |       |             | 2-866-6620 | awthorne@faa.gov> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 3 | Hill     | James | Volpe       | 61         | <Hi               |
| 9 |          |       |             | 7-494-2096 | ll@volpe.dot.gov> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 4 | Hobbs    | Gary  | FAA SoCal   | 85         | [garyhobbs@!f     |
| 0 |          |       | TRACON      | 8.537.5895 | aa.gov](mailto:Ga |
| . |          |       |             |            | ryHobbs@!faa.gov) |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 4 | Horton   | D     | FAA /       | 70         | [d                |
| 1 |          | aniel | AUA-730     | 3.326.3843 | aniel.horton@faa. |
| . |          |       |             |            | gov](mailto:Danie |
|   |          |       |             |            | l.Horton@faa.gov) |
+---+----------+-------+-------------+------------+-------------------+
| 4 | Houde    | James | CTA /       | 70         | <jim.             |
| 2 |          |       | AUA-TAC /   | 3.345.8787 | houde@auatac.com> |
| . |          |       | AUA-700     |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 4 | Howard   | Ken   | Volpe       | 61         | [ken.how          |
| 3 |          |       |             | 7.494.2697 | ard@volpe.dot.gov |
| . |          |       |             |            | ](mailto:Ken.Howa |
|   |          |       |             |            | rd@volpe.dot.gov) |
+---+----------+-------+-------------+------------+-------------------+
| 4 | H        | Mark  | Mitre /     | 70         | <m                |
| 4 | uberdeau |       | CAASD       | 3.833.5906 | whuber@mitre.org> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 4 | Jackson  | C     | Mitre /     | 70         | <cj               |
| 5 |          | laude | CAASD       | 3.883.6271 | ackson@mitre.org> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 4 | Jaeger   | Don   | ATCSCC      | 70         | [don.jaeger@f     |
| 6 |          |       |             | 3.326.3947 | aa.gov](mailto:Do |
| . |          |       |             |            | n.Jaeger@FAA.gov) |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 4 | Johannes | D     | FAA/ANE     | 78         | <deborah.         |
| 7 |          | ebbie |             | 1.238.7553 | johannes@faa.gov> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 4 | Johnston | James | ATCSCC      | 70         | <James.J.         |
| 8 |          |       | SVRWX       | 3.904.4520 | Johnston@faa.gov> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 4 | Kaler    | Curt  | ZMP TMU     | 65         | <Cu               |
| 9 |          |       |             | 1-463-5517 | rt.kaler@faa.gov> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 5 | Keirce   | Cliff | FAA         | 70         | <S                |
| 0 |          |       |             | 3-904-4522 | havcoo@yahoo.com> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 5 | Kirby    | Scott | FAA ATLATCT | 67         | [scott.kirby@fa   |
| 1 |          |       |             | 8.364.6107 | a.gov](mailto:sco |
| . |          |       |             |            | tt.Kirby@faa.gov) |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 5 | Klinker  | Mike  | ZDC TMO     | 70         | <Mike             |
| 2 |          |       |             | 3.779.3787 | .klinker@faa.gov> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 5 | Kraft    | Dick  | ARV-100     | 20         | <Dick..c          |
| 3 |          |       |             | 2-385-7657 | tr.Kraft@faa.gov> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 5 | L        | J     | NAV Canada  | 61         | <lanc             |
| 4 | ancaster | oanne |             | 3.563.5607 | ajo@navcanada.ca> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 5 | Leber    | Bill  | NWA         | 61         | [w                |
| 5 |          |       |             | 2.727.0293 | illiam.leber@nwa. |
| . |          |       |             |            | com](mailto:Willi |
|   |          |       |             |            | am.leber@nwa.com) |
+---+----------+-------+-------------+------------+-------------------+
| 5 | Libby    | Mark  | FAA/ATCSCC  | 70         | <ma               |
| 6 |          |       |             | 3.925.3149 | rk.libby@faa.gov> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 5 | Mahoney  | Jen   | AOPA/FSL    | 30         | <Maho             |
| 7 |          | nifer |             | 3-497-6514 | ney@fsl.noaa.gov> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 5 | Marchese | Mark  | FAA\`       | 70         | <mark.            |
| 8 |          |       |             | 3.326.3839 | marchese@faa.gov> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 5 | Marina   | Craig | FAA         | 20         | <Crai             |
| 9 |          |       |             | 2-366-5438 | g.marina@faa.gov> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 6 | M        | An    | Mitre/CAASD | 70         | <Tonym@mitre.org> |
| 0 | asalonis | thony |             | 3.883.5235 |                   |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 6 | Mat      | Tim   | UAL         | 84         | [Timothy.matu     |
| 1 | uszewski |       |             | 7.700.3016 | szewski@ual.com]( |
| . |          |       |             |            | ../../../../../.. |
|   |          |       |             |            | /../../C:/Documen |
|   |          |       |             |            | ts%20and%20Settin |
|   |          |       |             |            | gs/s080516/Local% |
|   |          |       |             |            | 20Settings/Tempor |
|   |          |       |             |            | ary%20Internet%20 |
|   |          |       |             |            | Files/../../../c7 |
|   |          |       |             |            | 40252/Local%20Set |
|   |          |       |             |            | tings/Temporary%2 |
|   |          |       |             |            | 0Internet%20Files |
|   |          |       |             |            | /OLKD/Timothy.mat |
|   |          |       |             |            | uszewski@ual.com) |
+---+----------+-------+-------------+------------+-------------------+
| 6 | May      | Jack  | NWS AWC     | 81         | Jack.may@noaa.gov |
| 2 |          |       |             | 6.584.7201 |                   |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 6 | McAfee   | Mike  | Fedex       | 90         | <mm               |
| 3 |          |       |             | 1-224-9818 | mcafee@fedex.com> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 6 | McGuirk  | Sid   | ATX-100     | 20         | <Sidney           |
| 4 |          |       |             | 2.267.7683 | .mcguirk@faa.gov> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 6 | McMahon  | Steve | FAA         | 70         |                   |
| 5 |          |       |             | 3-904-4400 |                   |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 6 | M        | Mike  | FAA ZAU TMC | 63         | <mike.m           |
| 6 | cPherson |       |             | 0.906.8342 | cpherson@faa.gov> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 6 | Merkle   | Jay   | FAA         | 20         | <Ja               |
| 7 |          |       |             | 2-366-4452 | y.merkle@faa.gov> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 6 | Meyer    | Darin | MIT Lincoln | 40         | <d                |
| 8 |          |       | Lab         | 7.855.3593 | arinm@ll.mit.edu> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 6 | Millspaw | Pa    | FAA         | 20         | <Patrick.         |
| 9 |          | trick |             | 2-267-9192 | millspaw@faa.gov> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 7 | Moffatt  | John  | Boeing ATM  | 70         | <john.e.mo        |
| 0 |          |       |             | 3.584.2938 | ffatt@boeing.com> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 7 | Moffitt  | Kelly | FAA         | 80         |                   |
| 1 |          |       |             | 1-320-2580 |                   |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 7 | Molin    | Doug  | ZID TMO     | 31         | Dougla            |
| 2 |          |       |             | 7.247.2267 | s.L.Molin@faa.gov |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 7 | Mullen   | Ken   | AUATAC /    | 70         | <ken.m            |
| 3 |          |       | AUA-700     | 3.345.6683 | ullen@auatac.com> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 7 | Munchak  | St    | CNAC        | 70         | <                 |
| 4 |          | ephen |             | 3-326-3806 | Munchaks@can.org> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 7 | Murphy   | Mi    | ATCSCC TMS  | 70         | <michael.         |
| 5 |          | chael |             | 3.904.4523 | d.murphy@faa.gov> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 7 | Nelson   | Gary  | AUATAC      | 70         | <Gary.n           |
| 6 |          |       |             | 3.345.8632 | elson@auatac.com> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 7 | O'Brien  | Mi    | ZAU TMO     | 63         | Michae            |
| 7 |          | chael |             | 0.906.8445 | l.O'Brien@faa.gov |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 7 | Oiesen   | Rick  | Volpe       | 61         | [oiesen@volpe.dot |
| 8 |          |       |             | 7.494.2309 | .gov](mailto:Oies |
| . |          |       |             |            | en@volpe.dot.gov) |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 7 | Olsen    | Ed    | NWA         | 65         | <edwa             |
| 9 |          |       |             | 1.405.1854 | rd.olsen@nwa.com> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 8 | Pederson | Paul  | TRW/AUATAC  | 70         | <Paul.Ped         |
| 0 |          |       |             | 3.345.8225 | erson@auatac.com> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 8 | Phaneuf  | Mark  | Avmet       | 70         | <P                |
| 1 |          |       |             | 3-351-5649 | haneuf@avmet.com> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 8 | Rhoda    | Dale  | DOT/Volpe   | 61         | <rho              |
| 2 |          |       |             | 7.494.2763 | da@volpe.dot.gov> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 8 | Richards | Je    | ATCSCC      | 70         | <Jeffrey.         |
| 3 |          | ffrey |             | 3.904.4523 | Richards@faa.gov> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 8 | R        | Dave  | ATT-260     | 70         | <david.r          |
| 4 | odenhuis |       |             | 3.925.3120 | odenhuis@faa.gov> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 8 | R        | Marty | FAA / ZNY   | 63         | <marty.r          |
| 5 | osenberg |       |             | 1.468.1080 | osenberg@faa.gov> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 8 | Serafini | Jerry | SCT TMU     | 85         | <Jerry.           |
| 6 |          |       |             | 8.537.5895 | Serafini@faa.gov> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 8 | Sh       | Riley | ASA         | 404.766    | [ri               |
| 7 | amburger |       |             | .1400x2294 | ley.shamburger@de |
| . |          |       |             |            | lta-air.com](mail |
|   |          |       |             |            | to:Riley.shamburg |
|   |          |       |             |            | er@delta-air.com) |
+---+----------+-------+-------------+------------+-------------------+
| 8 | Sherman  | Brad  | FAA         | 70         | <Brad             |
| 8 |          |       |             | 3-904-4520 | .Sherman@faa.gov> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 8 | Sketh    | Kapil | Raytheon    | 65         | <Ksketh@m         |
| 9 |          |       |             | 0-604-5728 | ail.arc.nasa.gov> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 9 | Smith    | Phil  | OSU         | 61         | <s                |
| 0 |          |       |             | 4.292.4120 | mith.131@osu.edu> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 9 | Snyder   | E     | ZFW         | 81         | <Erni             |
| 1 |          | rnest |             | 7.858.7537 | e.Snyder@faa.gov> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 9 | St.      | Tom   | FAA /       | 70         | [tho              |
| 2 | Clair    |       | ATCSCC/ TUT | 3.904.4525 | mas.stclair@faa.g |
| . |          |       |             |            | ov](mailto:Thomas |
|   |          |       |             |            | .stclair@faa.gov) |
+---+----------+-------+-------------+------------+-------------------+
| 9 | Stull    | Tim   | COA         | 71         | <t                |
| 3 |          |       |             | 3.324.6608 | .stull@coair.com> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 9 | Talmadge | John  | Delta       | 40         | <John.ta          |
| 4 |          |       |             | 5.715.1009 | lmadge@delta.com> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 9 | Tarakan  | R     | Mitre/CAASD | 70         | <rt               |
| 5 |          | obert |             | 3.883.7519 | arakan@mitre.org> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 9 | Tigert   | Gary  | ZME TMO     | 90         | [Gary.Tigert@fa   |
| 6 |          |       |             | 1.368.8548 | a.gov](mailto:Gar |
| . |          |       |             |            | y.tigert@faa.gov) |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 9 | Vivona   | Bob   | Titan Corp. | 97         | Robert            |
| 7 |          |       |             | 8-663-6600 | ,vivona@titan.com |
| . |          |       |             | X522       |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 9 | Vomacka  | Lor   | FAA/ATCSCC  | 70         | <Lorraine         |
| 8 |          | raine |             | 3.925.3112 | .vomacka@faa.GOV> |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 9 | Wa       | Mike  | Metron      | 70         | [wambsgans        |
| 9 | mbsganss |       | Aviation    | 3.787.8700 | s@metronaviation. |
| . |          |       |             |            | com](mailto:wambs |
|   |          |       |             |            | ganss@metsci.com) |
+---+----------+-------+-------------+------------+-------------------+
| 1 | Wertz    | Ti    | FAA         | 70         | <T                |
| 0 |          | mothy |             | 3-904-4530 | im.wertz@faa.gov> |
| 0 |          |       |             |            |                   |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 1 | White    | T     | NY TRACON   | 51         | <thomas           |
| 0 |          | homas |             | 6.683.2980 | .s.white@faa.gov> |
| 1 |          |       |             |            |                   |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 1 | Wilken   | Ed    | ZKC TMU     | 91         | [edwilken         |
| 0 |          |       |             | 3.254.8501 | @faa.gov](mailto: |
| 2 |          |       |             |            | EdWilken@faa.gov) |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 1 | Wilmoth  | Gre   | Metron      | 70         | <Wilmoth@me       |
| 0 |          | tchen | Aviation    | 3-234-0749 | tronaviation.com> |
| 3 |          |       |             |            |                   |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 1 | Wray     | Tom   | ZKC TMO     | 91         | <                 |
| 0 |          |       |             | 3.254.8460 | Tom.wray@faa.gov> |
| 4 |          |       |             |            |                   |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+
| 1 | Wyman    | Pete  | USAF        | 78         | <pe               |
| 0 |          |       |             | 1.238.7901 | te.wyman@faa.gov> |
| 5 |          |       |             |            |                   |
| . |          |       |             |            |                   |
|   |          |       |             |            |                   |
+---+----------+-------+-------------+------------+-------------------+

## Section II: Agenda

Collaborative Routing Work Group Meeting

**January 28 -- 29, 2003**

**Miami, Florida**

8:30: **Welcome To Miami,** Bill Cranor, and Debbie Johannes

8:35 -- 9:00: **Welcome from Miami Center and the Southern Region,**
Logistics information and housekeeping items. Peter Gullo, TMO Miami
ARTCC / Ron List, Manager Miami ARTCC

9:00 -- 9:30: **Changes in the NAS / Importance of collaboration,
technology and system planning, system initiatives vs local.** Jack
Kies, ATT-1

9:30 -- 9:35: **Review of Agenda,** Updated Action items from last
workshop: Debbie Johannes

9:45 -- 1015: **Plans for spring** -- ETMS 7.6 functionality, Rick
Oiesen, Volpe

1015 -- 1030: Break

1030 - 1130: **RMT / Playbook updates** Gretchen Wilmouth and Jeff
Richards Demo of the upcoming RMT changes and functionalities.

1130 -- 1230: Lunch

12:30 -- 1:15: **SWEPT / Route conformance briefing,**

Dr. Shon Grabbe, NASA Jim Hill Volpe Center, NASA

1:15 -- 2:15 **ICAO flight plan briefing and working session:** Pat
Millspaw, ATP and Lorraine Vomacka

2:15 -- 2:30 **Break**

2:30 -- 5:00 **Break out groups**

**Weather Applications team:** Leads Dave Rodenhuis, Bill Cranor, US
Airways

**ITFM:** Leads: Tom White and Bill Leber, Northwest Airlines

**RAT:** Leads: Mike Murphy and Roger Beatty, American Airlines --
(Focus is Field facility testing and RAT applications)

**Playbook**: Jeff Richards and Jeff Ralauk Spirit Airlines

##### Collaborative Routing Work Group Meeting

**January 28 -- 29, 2003**

**Miami, Florida**

Day 2: 0800 -- 4:00

8:00 -- 10:00: - **Plans for Spring-**

**RAT -- Phil Smith**

> **FCA process changes.**
>
> **Nav Canada Central Traffic Flow Management Facility** -- NAV Canada

# Canadian inclusion in the CCFP- Nav Canada

> **CCFP update-** Dave Rodenhuis
>
> **Pathfinder / Diversion Recovery --** John Martin / Jimmy Johnston

10:00 -- 10:15 Break

10:15 -- 10:45: **Metron Update / GNOME**

10:45 -- 3:00 (includes a working lunch) Break out sessions

**ITFM** -- Tom White

**NASCON:** Debbie Johannes / Bill Leber

**FCA/RAT:** Joint break out session

**Weather Applications:** Dave Rodenhuis

**Training:** Leads: Charlotte Happle and Tim Matasuski

3:00 -- 4:00: Break out session report outs, Identifying Action items /
meeting close out.

## 

## Section III: Meeting Notes

## CR Workshop Day 1

## January 28, 2003

### 1. Welcome to Miami and Agenda/Action Review

Peter Gullo, TMO Miami ARTCC and Ron List, Manager Miami ARTCC welcomed
the participants and provided meeting housekeeping and logistic
information. Debbie Johannes, FAA and Bill Cranor, USAirways also
welcomed the participants and thanked Peter and Ron for their efforts
setting up this workshop.

Debbie conducted a review of the open action items. A briefing from the
FCA/Reroute workgroup on plans for Spring 2003 was added to the agenda.

**Future Meeting info:**

The next CDM Meeting is on March 4-6 in the Washington area. Location
TBD. Patty Swenor, FAA has set up some great hotel rates, information
will be exploded. We will use the half-day, full-day, half-day format.

CRWG Meeting on May 13-15 in Detroit at the Westin Hotel. Information
will be exploded, we will use the half-day, full-day, half-day format.

CRWG Meeting on September 9-11, location TBD.

**2. Changes in the NAS / Importance of collaboration, technology and
system planning, system initiatives vs local.**

Jack Kies, ATT-1 addressed the members. Jack said in many ways this is
the "best of times and the worst of times", we have had lots of success,
but clearly, we face lots of challenges. "System thinking" and
collaboration has been the key to our successes. Training and procedure
development are key to successful integration of new tools and
functions. Jack mentioned the "State of the System" briefing and the
push within the FAA to focus on the near term to see what can be done
"now" to provide benefits to NAS users and help get them flying again.
Planning to have Debbie focus full time on CDM (details still being
worked out). Volpe was asked to focus on meeting commitments and on
functions that will help now. Several items in the pipeline should
provide some near-term benefits to the Airlines (RAT, FCA, RVSM, and
High Altitude Redesign were mentioned).

Some airline members responded that CDM has helped without spending
money on aircraft equipment, and that the OEP has some good and not so
good ideas, but that the CDM section provides the best return for
airline investment.

Jack replied that the OEP may need some adjustments and it's likely to
change in the next 6-8 months to focus more on the near-term. This may
provide an opportunity to make CDM more of a focus throughout the OEP.
Jack said that funding is being looked at for opportunities to redirect
some money to get near-term results. Jack also said with industry
downsizing, the FAA is likely to see staffing changes/redistribution as
well, but is working to increase staff where needed.

# 3. Plans For Spring

Rick Oiesen, Volpe provided this update. ETMS 7.5 was deployed on
December 9, 2002. ETMS 7.6 planned deployment is May 12, 2003. See the
Volpe briefing for detailed information. Highlights are included below.

ETMS 7.5 features:

-   FEA/FCA Enhancements

    -   Allow a circle to be an FEA/FCA.

    -   Lat/lon can be used to specify an FEA/FCA.

    -   Allow three levels of sorting for the dynamic FEA/FCA list.

    -   FEA/FCA timeline and bar chart optionally show counts of the
        number of flights entering an FEA/FCA.

    -   Add FCA as an ETMS remark.

    -   Info button in Select FEA/FCA box shows filters. Show reason for
        the FEA/FCA.

-   NAS and Center Monitors

-   Various GDPE enhancements (better handling of diversions, better
    specifying of airline relationships)

Rick requested the CDM members provide him feedback if they have any
issues with ETMS 7.5.

The group also discussed how some of the Centers currently use FCA's.
Many centers have developed local uses. The FCA group is working on
developing national solutions.

Some of the discussed local FCA uses are listed below:

-   To look at active military airspace

-   Draw FCAs around weather with movement

-   Draw FCAs around arrivals to capture flights in a certain time frame

-   Use in the TRACON where monitor alert is not available

-   Used to monitor aircraft and load in a sector

-   Filter by center/altitude

-   Pulling and monitoring lists

ETMS 7.6 features include:

-   ETMS will accept early route intent from NAS users.

-   Time-in-sector display.

-   National Convective Weather Forecast (NCWF) one-hour forecasts.

-   First phase of the RAT functionality

-   Slot Credit Substitution (SCS)

-   OOOI data from airlines used to activate flights in ETMS.

CCSD enhancements planned for May 12, 2003:

-   NCWF

-   Manual early intent.

-   NAS user create/share an FEA with other NAS users and FAA
    facilities.

-   Prototype FCA Monitor tool (will be available to FAA users on the
    WSD).

-   Prototype RAT Reader and RAT Responder.

Diversion Recovery Page:

At the last CDM meeting it was decided that Auto flights should be put
back on the Diversion Recovery Page. Auto flights had previously been on
the page but were removed a year ago.

A version of the page with Auto flights is in testing and will be
delivered to the ATCSCC soon.

Issue for group discussion: How can ETMS default routes be improved?

ETMS loads OAG data for a flight 15 hours before departure. If there is
no route in the OAG data, ETMS uses a "historical route," which is the
route most commonly flown in the near past.

These historical routes are often wrong, especially flights over 2
hours. How can the default routes be improved? The long-term solution is
for the NAS users to send early route intent.

Rick reviewed some possible solutions and is looking to the airlines for
ideas to improve "historical routes".

Some of the possible solutions discussed:

-   Add flight planning software to ETMS

-   Run Multiple routes used in the past, use the ETMS trajectory model
    to pick the least-time route, given the day's winds

-   Use flight plans filed early in the day to predict routes filed
    later in the day

-   Assume similar routes on similar days (similar needs to be defined)

-   Others, any airline ideas?

-   

Rick explained how ETMS models trajectories and how it syncs up with
Host flight data. Rick restated that this is a near-term problem, and
that early intent will eventually solve this problem. We discussed using
some type of probability of flying the route based on historical data.
Carriers said that when weather is rapidly changing, they do not know
their route very far in advance, so any solution needs to be able to
accept an "I don't know" from the airlines.

The system needs to deal with uncertainty, NASA just completed some work
in this area that needs to be looked into for ideas. Airline flight
plans could include cruise profiles for ETMS to use (new ICAO FPs use
cruise profiles). Currently, ETMS just gets cruise altitude, however,
long-term cruise profiles will be included. Rick requested that anyone
with ideas on this to send him an email with the suggestion.

**4. RMT / Playbook Updates**

Gretchen Wilmouth, Metron Aviation and Jeff Richards, ATCSCC discussed
and demonstrated upcoming RMT changes and functionalities. Playbook
routes are being integrated into the RMT, version 1.30. Version 1.3 user
guides, new feature training, and a CBI have been developed. The
prototype version will be delivered to the ATCSCC January 31, 2003. The
operational version will be deployed shortly after ETMS 7.6 deployment.
The new Playbook window has the look and feel of the current CDR window.
Users can choose between operational and staging databases. Jeff asked
the group to provide input when proposed updates are out for review (the
first 21 days of the 56 day cycle). The freeze date is 35 days prior to
implementation.

Action Item: Provide feedback to Jeff Richard and Gretchen Wilmouth on
the RMT/Playbook changes in the RMT Demo/prototype deployed at the
ATCSCC by the end of May. Jeff/Gretchen will distribute an instruction
package to the facilities and the training department.

**5. SWEPT / Route Conformance Briefing**

Dr. Shon Grabbe, NASA and Jim Hill, Volpe Center provided presentations
on FACET and SWEPT. Both briefings are available on the CDM web site.
Highlights of the presentations are included below.

FACET is NASA's Future ATM Concepts Evaluation Tool. It's a simulation
tool used to explore advanced ATM concepts. It is used for rapid
prototyping and can be integrated with other tools. FACET has trajectory
prediction and system impact assessment capabilities. FACET modeling
activities include:

-   Assessment of Alternative Traffic Flow Management Initiatives

-   Distributed Air-Ground Traffic Management (DAG-TM) Studies

-   Probabilistic Sector Demand Forecasting

-   Wind Optimal Rerouting

-   Benefits Study of Direct-To Tool

-   It's a simulation tool used to explore advanced ATM concepts

SWEPT is the System-Wide Evaluation and Planning Tool. SWEPT is a
decision support capability used for on/off line analysis and evaluation
of traffic flow scenarios. It can model the national traffic flow
management environment and is capable of refining traffic flow
initiatives and conformance monitoring. Earlier detection of
non-conformance permits earlier corrective action and less disruption to
the plan.

FACET was integrated into SWEPT. A Conformance Monitoring Capability was
developed and an ETMS and Playbook data interface developed. An initial
reroute conformance monitoring function was informally demonstrated to
the ATCSCC. A field test version was then developed and R&D
demonstration was completed in December 2002. Next steps are to
establish a user group for feedback and develop alternative algorithms
and concept of operations by December 2003. Tech transfer is planned to
be completed by December 2004. They would like to field test the Reroute
Conformance Monitoring Capability with the ATCSCC and several FAA field
locations to ensure a smooth transition.

6\. ICAO flight plan briefing and working session

Mike Hawthorne, FAA/AUA-200 led this discussion and presentation about
TFM data in the ICAO flight plan. The detailed briefing is available on
the CDM web site. Discussion highlights are included below. The FAA is
in the process of modifying Host software to be compatible with the ICAO
flight plan. AUA-200 is coordinating implementation with other product
teams. Testing of the new software in 2002 revealed that not all the
filed TFM data goes to ETMS. CDM support/input is needed to ensure
needed TFM data gets into the ICAO flight plan format. Mike said this is
an opportunity for CDM to provide input into the design and transition.

Background:

-   ICAO provides standards, recommended practices, and guidance for
    global aviation

-   Seamless ATM is needed between U.S. and surrounding flight
    information regions

-   Regional agreements capture implementation details (Mexico and
    Canada, ...)

-   Common data formats, procedures, phrases, communications interfaces

Implementation will significantly reduce controller cross-border manual
coordination, and increase safety via standard terminology and common
phraseology.

The group reviewed some of the differences between the NAS and ICAO
flight plan format and information.

-   NAS flight plans use a single letter suffix to describe aircraft
    navigation and surveillance capabilities. The ICAO flight plan uses
    up to 25 characters to describe equipage (each character represents
    a capability).

-   ICAO designates the type of flight (scheduled or non-scheduled air
    service, GA, Military, ...).

-   Wake turbulence in the NAS flight plan indicates if the aircraft is
    a "heavy", in the ICAO flight plan; heavy, med, or light can be
    used. The designation is dependant on aircraft weight, however, ICAO
    and NAS weight breakdowns use different weight ranges.

Recommendations:

-   Flight plan information for over-water equipage is needed (limiter
    over-water, over-water). Information about crew capability should
    also be included.

-   When new flight plans are entered into the system, the current
    flight plan should be closed (CNL) to prevent problems because of
    delays in processing and Host automation limitations.

Currently, ICAO flight plans have their data stripped and put into NAS
flight plans. When this is done, lots of data is dumped into the remarks
section and possibly lost if the remarks are edited. The new flight plan
processing will keep all the data.

The group discussed how best to get TFM data into the ICAO flight plans.
Currently, NAS flight plan remarks sections are scanned for TFM data.
The ICAO flight plan does not have a designated field for TFM data.
Candidate locations in the ICAO flight plan include the remarks, special
handling, or navigation equipment fields. Possibly, a new TFM data field
could be added.

The group had a long discussion about just putting the TFM information
in the ICAO remarks (RMK/ ) section. However, there are several issues
that will need to be resolved:

1.  Different countries tend to use the remarks section differently. We
    will all need to coordinate its use and get in the same page.

2.  Currently, when the remarks section is added to or edited by
    controllers it deletes previous entries. The field needs to be set
    up so you can add information, but not delete/overwrite information
    (unalterable).

3.  Cruise profiles and step climbs also need to be included in the
    flight plan information versus just cruise/assigned altitudes.

We discussed what data would be displayed to controllers. It was stated
that NATCA would not be interested in displaying all 25 equipment
designations. Mike responded that all flight plan data would be
available for use by the automation systems, but not all data would be
displayed.

Finally, we discussed flight plan acknowledgement. Currently, the Host
computer responds with an accept/reject response for NAS flight plans.
No response is provided for ICAO flight plans (an enhancement to the
Host computers is planned to acknowledge ICAO flight plans). Mike is
looking for feedback from the group about how this should be
accomplished, they are thinking about replying back to the sender with a
message number.

In closing, Mike emphasized the desire to keep the dialog open and
communication ongoing to ensure a successful implementation.

CR Members broke up into the breakout groups for the remainder of Day 1.

**CR Workshop Day 2**

**January 29, 2003**

Day 2 main group status reports:

**7. Weather Applications Group Out-Brief**

This update was provided by Bill Cranor, USAirways. This was the second
time the Weather Applications group has met. The group's near-term focus
is on the CCFP for 2003. At this meeting we reviewed the minutes and
actions from the first meeting, reviewed the mission statement, and
worked on updating the 2003 CCFP Statement of User Needs, requirements
document. CR members should provide any feedback/comments on the 2003
CCFP Statement of User Needs to Dave Rodenhuis, FAA or Bill ASAP if they
want them included for 2003. The group plans on completing the
requirements document review by the end of the meeting today. The group
will also be working on CCFP training. Canada will be included in the
CCFP this Spring.

8\. RAT Update

# Mike Murphy, ATCSCC led this discussion. Highlights are discussed below. The detailed briefing is available on the CDM web. The RAT functionality has several components: RAT Writer, RAT Reader, RAT Listener, and RAT Responder. 

RAT team goals are to improve the clarity, usefulness and understanding
of reroute advisories. They developed a process that attaches a flight
specific/route specific flight list to a reroute advisory, thus
providing users and facilities common situational awareness for reroute
planning.

NAS User Access methods:

1\. Receive all the less ambiguous advisories using current distribution
methods.

2\. Request that RAT advisories be sent with/without the associated
flight lists for their airline/organization via teletype.

3\. Machine-readable advisories and flight lists via CDM-Net for
internal processing (User developed RAT-Readers). They can request only
advisories for their airline/organization.

4\. Access the advisories via the CCSD, which will provide flight
specific information for their own flights, including map displays
showing the reroutes (CCSD version RAT-Reader).

FAA Facilities Access Methods:

1.  Graphic depiction of active system reroutes via the ATCSCC OIS
    intranet page (OIS RAT-Reader).

2.  ARTCCs can request "relevant" reroute advisories and get only the
    ones with their facility in the "facility field".

The focus has been on the RAT Writer and RAT Reader. The RAT Responder
has not been fully developed and many procedural issues need to be
resolved. The RAT Responder will not me ready for Spring 2003.

Mike briefly reviewed the features of all 4 RAT tools being developed
(RAT- Writer, Listener, Reader, and Responder).

[RAT Procedure Development]{.underline}

Proposed implementation:

-   FAA facilities are responsible to ensure flights are on their
    reroute prior to leaving their area.

```{=html}
<!-- -->
```
-   The Airline will be responsible for the reroute until 45 minutes
    before push-back.

-   If less than 45 minutes before push-back, the FAA would assume
    responsibility for the reroute.

Schedule:

-   Begin testing sample format messages with FAA field facilities in
    March 2003.

-   Testing will be 3 days a week, Monday, Wednesday, and Friday.
    0800-1600 EST.

Testing goals:

Provide feedback about; accuracy of data, format, content, usefulness,
collaboration, and limitations. The RAT team is looking for lots of
feedback.

Deploy initial version of RAT in ETMS 7.6 in Spring 2003 (planned for
May 12, 2003),

-   Initially for Transcon Playbook reroutes with1 hr of lead-time
    before reroute.

-   Expansion in the summer to include Playbook and tactical reroutes.

New RAT items being planned for ETMS 7.7 deployment in the Fall of 2003.

-   "Create Reroute Dialog Box" enhancements.

Mapping

GUI additions

-   Exclusion of individual flights in the flight list.

-   Capability to import FCA data to create a reroute with multiple
    options.

-   Export the "Create Reroute Dialog Box" to all ARTCC's

-   

-   Enhanced addressing

-   Rat-Reader enhancements

-   Improved ability to deal with airborne flights

-   Improved ability to deal with capped flights

-   Initial RAT Responder technology.

Some final points from the discussion:

Users will get all flights being rerouted, including airborne flights.
Airlines can tailor what they want to get. Airlines need to tell Volpe
what they want to receive. The default is they will get what they get
now the way they currently get it (option 1 above). GA flights will not
be on the initial list. The process for GA is being worked and they hope
to include GA in some yet to be determined fashion in the future.

Action Item: Mike Murphy, Put the instructions for the use of the RAT
Reader tool on the CDM web page.

9\. Diversion Recovery/Pathfinder Update

John Martin, ATA and Jim Johnson, ATCSCC led this discussion on the
status of the Pathfinder web page.

Pathfinder:

There has been limited participation in Pathfinder. More involvement is
needed to identifying aircraft available to participate. Pathfinder has
had some success in the New York area using DSP. Debbie Johannes and
Jack Kies want to brief facilities on Pathfinder. The page is still
being worked at the ATCSCC at ATA, NBAA, SVRWX workstations. Access will
be expanded to a few field facilities this summer.

10\. FCA/Reroute Status Report

Mark Libby, ATCSCC and Jo Damato, NBAA presented the concepts the
FCA/Reroute workgroup has explored for discussion and approval by the
CDM/CR group (see briefing for additional details). The group's primary
focus was to explore strategic use of FCAs. The group was established in
May 2002. Mark briefed the history of the FCA/Reroute workgroup and
described the ongoing testing. Mark noted that all airlines were invited
to participate in the testing and that more ARTCCs will participate in
future tests.

The group determined that a phased approach would be best because of the
complexity of the issues. They also committed to not rush a product that
was not ready to be deployed. The resulting plan was for a phased
approach with extensive testing. The group added the RAT team to the
group, simplified/standardized RAT advisories, and including early
intent.

Ed Olsen, NWA briefed terminology (UPT, Early Intent, etc.) and the
different types of options that might come out in the advisories
(unrestricted UPT, restricted UPT, multiple route options, and single
route option) in phase 1. Early intent was broken into two types (wind
intent and operational intent). Ed provided a 2-page handout of the FCA
Opscon summary (available on the CDM, FCA workgroup web site). The
entire Opscon is also available on the CDM, FCA workgroup web site as
well as past meeting minutes, briefings, and test plans/results. Phase 2
will include looking into exit strategies.

The Opscon allows the user to have option to stay on ground, go over the
top, or delay out of the FCA etc., verses a lateral reroute. Airlines
can also take an option that is not in the list of routes in the
advisory if the proposed routes are unacceptable.

It was suggested by a CMD participant that altitude should be included
in the advisory.

The FCA group briefed possible benefits (see slides). FCA/Reroute
implementation looks like a win-win for the FAA and users. The FAA can
more effectively manage the NAS while giving operators flexible route
options to the extent possible.

Ed Corcoran, ATCSCC discussed the limitations and concerns, many of
which are automation issues. Ed complimented Volpe and noted the need
for multiple playbooks and multiple flight filters (they have a
workaround for summer -- draw multiple FCAs), and other enhancements. Ed
provided a brief overview of future phases (post-2003), including users
being able to submit multiple-intent. He also acknowledged the "parking
lot" issues that will need to be revisited in the future and the need to
determine actual benefits. Continued coordination with RAT is also part
of the future plan. Ed sees RAT as the mechanism for disseminating info,
while FCA is the process for identifying flights subject to a
constraint.

Carol Catron, ATCSCC briefed the training plan. The goal of the group
was to provide a complete training package for FCA procedures and
recommend the best training strategy to the joint training team. Cadre
training (train-the-trainer) for FAA and Industry is planned for the
week of 4/7/03 (based on a 5/12/03 deployment). FAA field training can
start on 4/12/03. An Advisory Circular will be developed for
pilots/dispatchers. The training was collaboratively developed. FAA
materials are available for industry use, and foundational
pilot/operator materials are available and can be tailored by each user.
Training material will be put on the CDM web site 3/12/03.

Open Discussion:

-   The group is working to see what automation is needed to get FCA
    info out to GA users. Currently, FSS do not brief reroute advisories
    unless asked (just GDPs/GSs). The group is coordinating with FSS to
    include reroute advisories in FSS briefings.

-   NAV Canada will be involved in the SPO and reroute planning just
    like it is today. Canada will plan overtime based on demand for
    specific sectors.

-   What about the problems that are created because of rerouting for
    FCAs? Mark Libby stated that we will be watching this closely this
    year and collecting data. We must be cognizant of Monitor Alerts
    that are created from FCAs, after flights reroute around the FCA
    creating new congestion. Also, an FCA Monitor tool is being
    developed that will let you see who's filed out of FCA and where so
    you can get a quick look at what problems will be created.

-   What about the ATCSCC sending an advisory to suspend directs when
    multiple FCAs are issued (during SWAP)? Mark said the group has
    thought about it, its one of our "parking lot" issues that we need
    to get back to.

-   Some airline concerns:

    -   Dispatch workload

    -   Early intent, filing flight plans on UPT

    -   Use of field 11

    -   Create a second or third constraint that affects that flight

> Mark's said we are taking baby steps. If we get better data with early
> intent even on a couple airplanes that will help; when we get early
> and wind intent, even better. Workload is an issue for both sides,
> hopefully workload will be off-set by the benefits. Most benefits are
> expected in places dominated by airlines that are participating in
> early intent. FCA remarks in field 11 in phase 1 are not expected to
> carry much weight.

-   Debbie Johannes stated that FCA's are another tool that can really
    squeeze efficiency out of the system and commend the team for
    looking for win-win benefit for all NAS users.

-   Mark said if this process is going to be successful it's up to the
    TMUs to think about options before each SPT, otherwise it'll only be
    used tactically and not successfully implemented.

-   Airlines had lots of issues about early intent. Early intent needs
    to be specifically defined and applied. Hopefully, results from
    analysis using POET data will be useful. Many early intent issues
    will be addressed in future phases.

-   "FCA" will be used in the remarks field in phase 1 to support data
    collection/analysis. Use may be expanded later. Hopefully,
    controllers will be sensitive to rerouting flights with "FCA" in
    field 11. Concern was expressed that we are overloading field 11.

11\. Metron Update / NAS Genome

Mike Wambsganss of Metron Aviation provided a briefing on the CDM R&D
approach and initiatives (see briefing for specific details). Mike said
CDM successes can be attributed to the fact the researchers, developers,
and operations people work together. He provided an overview of the R&D
process and provided a quick review of some of the near-term R&D efforts
listed below:

-   SCS Procedures

-   Revised Popup Management

-   Multi-airport GDPs

-   Multi-fix GDPs

-   Airspace Congestion Management/RBS in the Sky

-   Use of OOOI data for GDPs

-   Playbook GDPs

-   GDP Algorithm Revisions

Jupiter simulation is used to support R&D and HITL. HITL utilized to
support recent and planned GDPE research (SCS, Pop-ups, Multi-fix,
Multi-airport).

NAS Genome was described as a longer-term effort to "map the DNA of the
NAS". The NAS Genome concept was originally introduced by Jim Wetherly
AUA-740 as a way to separate research from the constant pressure to
improve tools.

NAS Genome research is broken into three components:

-   Data Analysis & Interpretation

-   Data Management

-   Data Visualization

Mike describes some of the features of NAS Genome; library created, 3D
visualization techniques and NAS wide automated extraction & display. He
discussed non-linear systems behavior and dealing with uncertainty
(options decrease while knowledge increases).

Equity was also discussed at length. Mike presented lots of ideas about
what equity (fairness) is or could be. Many free market approaches are
being looked at. RBS has its root in the Babylonian Jog concept
developed by Talmud.

Issues:

-   Fairness needs to be defined; is it gate-to-gate service or specific
    events, a system of flights or one airport, over time or one event?

-   Do we provide Incentives for good behavior?

Inclosing, Mike briefly introduced the TFM Vision/Evolution concept
being developed by Ved Sud, AUA-740 and Gary Nelson, AUATAC.

Reconvened Breakout Groups until the end of Day 2.

## Section IV: Action Items

**CR Workshop**

## ![](media/image1.wmf){width="5.99375in" height="7.0375in"}January 28-29, 2003

**Attachment 1**

**Meeting Minutes for the**

**Weather Applications Workgroup**

# 

Meeting minutes in support of the Weather Applications Workgroup
breakout session held on January 28-29, 2003, in conjunction with the
Collaborative Routing (CR) Workshop in Miami, FL. This was the second
meeting of this group. The primary focus was to finalize the mission
statement, review and finalize the CCFP requirements for 2003, and
update the progress made toward Weather Applications Workgroup goals.
Documents supporting the work of this group are @
http://www.metronaviation.com/cdm/Workgroups/weather.html.

**Attendees:**

+-----------+-------+----------------+-----------+-------------------+
| #         | ***   | ***O           | **        | ***email***       |
| ###### *L | First | rganization*** | *Phone*** |                   |
| ast Name* | Na    |                |           |                   |
|           | me*** |                |           |                   |
+===========+=======+================+===========+===================+
| ######### | Alex  | Mitre/CAASD    | 703       | <al               |
|  Alshtein |       |                | .883.7861 | shtein@mitre.org> |
+-----------+-------+----------------+-----------+-------------------+
| Brown     | Ba    | NCAR/RAP       | 303       | <Bgb@ucar.edu>    |
|           | rbara |                | -497-8468 |                   |
+-----------+-------+----------------+-----------+-------------------+
| Catron    | Carol | ATCSCC ATT-240 | 703       | <caro             |
|           |       |                | .925-3135 | l.catron@faa.gov> |
+-----------+-------+----------------+-----------+-------------------+
| Cranor    | Bill  | USAirways      | 540       | [                 |
|           |       |                | .972.7372 | wcranor@adelphia. |
|           |       |                |           | net](mailto:willi |
|           |       |                |           | amcranor@msn.org) |
+-----------+-------+----------------+-----------+-------------------+
| Evans     | Jim   | MIT LL / UCB   | 781       | [jime@ll.mit.e    |
|           |       | NEXTOR         | .981.7433 | du](mailto:James. |
|           |       |                |           | wetherly@faa.gov) |
+-----------+-------+----------------+-----------+-------------------+
| Fahey     | Tom   | NWA            | 612       | Tom.fahey@nwa.com |
|           |       |                | .726.3256 |                   |
+-----------+-------+----------------+-----------+-------------------+
| Gold      | Ru    | ATA            | 202       | <rg               |
|           | ssell |                | .626.4010 | old@airlines.org> |
+-----------+-------+----------------+-----------+-------------------+
| Huberdeau | Mark  | Mitre / CAASD  | 703       | <m                |
|           |       |                | .833.5906 | whuber@mitre.org> |
+-----------+-------+----------------+-----------+-------------------+
| Lancaster | J     | NAV Canada     | 613       | <lanc             |
|           | oanne |                | .563.5607 | ajo@navcanada.ca> |
+-----------+-------+----------------+-----------+-------------------+
| Mahoney   | Jen   | AOPA/FSL       | 303       | <Maho             |
|           | nifer |                | -497-6514 | ney@fsl.noaa.gov> |
+-----------+-------+----------------+-----------+-------------------+
| May       | Jack  | NWS AWC        | 816       | Jack.may@noaa.gov |
|           |       |                | .584.7201 |                   |
+-----------+-------+----------------+-----------+-------------------+
| McPherson | Mike  | FAA ZAU TMC    | 630       | <mike.m           |
|           |       |                | .906.8342 | cpherson@faa.gov> |
+-----------+-------+----------------+-----------+-------------------+
| Meyer     | Darin | MIT Lincoln    | 407       | <d                |
|           |       | Lab            | .855.3593 | arinm@ll.mit.edu> |
+-----------+-------+----------------+-----------+-------------------+
| Mullen    | Ken   | AUATAC /       | 703       | <ken.m            |
|           |       | AUA-700        | .345.6683 | ullen@auatac.com> |
+-----------+-------+----------------+-----------+-------------------+
| Munchak   | St    | CNAC           | 703       | <                 |
|           | ephen |                | -326-3806 | Munchaks@can.org> |
+-----------+-------+----------------+-----------+-------------------+
| Phaneuf   | Mark  | Avmet          | 703       | <P                |
|           |       |                | -351-5649 | haneuf@avmet.com> |
+-----------+-------+----------------+-----------+-------------------+
| Rhoda     | Dale  | DOT/Volpe      | 617       | <rho              |
|           |       |                | .494.2763 | da@volpe.dot.gov> |
+-----------+-------+----------------+-----------+-------------------+
| Rodenhuis | Dave  | ATT-260        | 703       | <david.r          |
|           |       |                | .925.3120 | odenhuis@faa.gov> |
+-----------+-------+----------------+-----------+-------------------+
| Sherman   | Brad  | FAA            | 703       | <Brad             |
|           |       |                | -904-4520 | .Sherman@faa.gov> |
+-----------+-------+----------------+-----------+-------------------+

**Agenda:**

**[DAY 1 (Tuesday, 1/28 -- planned for 2:30-5:00 pm)]{.underline}**

1.  **Welcome / Introductions** Bill Cranor and Dave Rodenhuis, Cochairs

    a.  Report of the previous meeting minutes (Nashua, Dec 2002) Ken
        Mullen

        i.  Discuss and report status of open action items.

    b.  Review and consensus on current session agenda

2.  **Finalize draft Mission Statement for the Weather Applications WG**
    Bill Cranor

3.  **CCFP Requirements for 2003**

    a.  (Statement of User Needs) Dave Rodenhuis, ATCSCC

        i.  Agreement

        ii. Concerns

        iii. Out year projects

4.  **Status report and goals (2002+)**

    a.  Training package for 2003 Carol Catron, ATCSCC

    b.  Forecast Verification (Skill, Quality) Jennifer Mahoney, FSL and
        Barb Brown, NCAR

    c.  Forecast Evaluation (Operational Impact, Value) Jim Evans and
        Dave Rodenhuis

    d.  Producer Collaboration Mark Phameuf, Avmet

    e.  Canadian/U.S. Collaboration Joanne Lancaster, NAVCanada

    f.  Development of TFM strategies for CCFP (Application) Discussion

        i.  Discussion points:

        -   What are (list) the currently used strategies?

        -   When and how are they used?

        -   What new strategies could be employed in 2003?

        -   What work being considered by other Workgroups; for example,
            FCA, ITFM, NASCON ? Coordination ?

        -   How will NCWF affect CCFP strategies when it is deployed on
            ETMS ?

5.  **Summary (status report)** Bill Cranor, Cochair

**[DAY 2 (Wednedsday 1/29- planned for 10:30 -- 3:00 pm)]{.underline}**

6.  **Information Reports**

    a.  Report of the 3^rd^ Workshop on ATM and Weather (14,15 JAN,
        NCAR)

    b.  Report on Convective Forecasting Meeting (16-17 JAN, NCAR)

    c.  The New OEP Dave Rodenhuis

    d.  Report on NCWF training Dale Rhoda

    e.  Discussion and comments by the Workgroup

7.  **Strategies for CDM that use weather** (CCFP and others; focus on
    intense convection)

    a.  Discussion Points (continued from 1/28)

        i.  Review existing strategies.

        ii. How to use probabilistic forecasts? Jack May

        iii. Who is working on this problem?

8.  **Summary for the CDM plenary session** Co-chairs

    a.  Issues

    b.  ACTION items

    c.  Date/time/place for next meeting.

**Day 1 Notes:**

**Welcome / Introductions**

Bill Cranor welcomed the group and all participants introduced
themselves. The group reviewed the actions from the last (first)
meeting. The updated actions are attached at the end of Attachment 1 of
these minutes.

Action Item: Bill Cranor, Create a Weather Applications Team exploder

**Finalize draft Mission Statement for the Weather Applications WG**

The group reviewed the draft mission statement. One issue that was
discussed was the need to involve more traffic managers if we are to
work strategies. The group determined they could utilize Traffic
Managers or any other SMEs from the main CR group as needed to support
Weather Applications work. We also reviewed and discussed group size and
membership. After discussion, the group decided that the size and
composition could be changed in the future if needed. It was noted that
the group will "make recommendations" to others, and we can add members
as we go if needed.

Action Item: Russ Gold, Contact Mark Cato, ALPA to inform him that the
Weather Application group has been formed.

Words to include Canada were added to the Mission Statement. The updated
Mission Statement was adopted by the group.

**CCFP Requirements for 2003**

David Rodenhuis, ATCSCC led the review of the Statement of User needs.
Dave walked the group through all the proposed changes for the 2003
update. The bullets on page 14 of the users needs document are a
synopsis of the changes. Dave also reviewed all open issues that need to
be resolved by this group.

Sections Reviewed:

Page 13-14, 9.

Summary of changes CCFP/2003

Section 2, page 4

Definition of the forecast object: Intense Convection (2.1)

Issue: The group needs to agree on the minimum area for CCFP forecast
(2.1). ATC and TFM need to be part of determining the minimum size of
this object. The impact to Canada also needs to be included. The group
discussed the size of previous CCFPs. No de facto minimum size really
exist, however, it was probably around 3000 sq miles. Input is on
minimum size is also needed from producers and users. Most felt the
30,000 sq miles proposed was too big. It was recommended a team be
assembled to analyze this issue and determine the proper size.

Participants who volunteered to work this issue:

David Rodenhuis

Tom Fahey

Mark Phaneuf

Pete Gallo

Mike McPherson

Jack May

Presentation of colors/hatching/balloons? (2.x)

No Changes for 2003

Section 2, page 6

Textbox (2.6)

Brad Sherman, ATCSCC will review the Textbox work that has been started.
The group needs to determine requirements for future builds. This is not
doable in ETMS for 2003.

Action Item: Brad Sherman, Text Box, what should be included and how it
should be used needs to be defined. Some work was done on this topic by
another group that needs to be included in our work. Brad Sherman,
ATCSCC will get info and provide to the group. Brad & Dave R. will
consolidate previous work.

Section 3, page 6 Collaboration

Production collaboration will need more discussion in the future.

Avmet tracks chat room participation.

Section 4: Application

Section 5 Training

Carl Catron, ATCSCC presented the plan for training:

The plan for 2003 is similar to last year. The briefing has been
updated. No formal procedures for this year, but, hopefully in the
future. The briefing/training package will be available on 2/5/03 for
ATCSCC and FAA field. Carol did develop a lesson plan in the Fall of
2002, but reverted back to the briefing when it was decided to use that
approach again this year. A high and low graphic version of the briefing
is available. Statistical data is also available, but not included in
the training briefing.

Training Briefing comments and recommendations:

-   Add performance of the product to the training briefing to show the
    accuracy of the 2/4/6 hr forcasts.

-   TOPS info -Tops maybe different than indicated

-   Change "text box" to "Dialogue box"

-   Change "Probability of Detection" to "Probability of Occurrence"

-   Any additional input needs to be provided to Carol by Tuesday (Feb
    4^th)^\_

Action Item: All WxApps Members, Provide consolidated CCFP training
briefing changes to Carol Catron, ATT-240 by COB 2/4/03

Section 6: Forecast Verification and Assessment

Unresolved issues: Verification in Canadian airspace

Evaluation in areas of "no-convection"

Participants to work on the language in paragraph 6.3, page11.

Action Item: Review and update as required \"skill measure\" language in
CCFP User Needs, section 6. This action updated on day 2 to include the
establishment of a subgroup to work section 6 requirements; evaluations,
route impact assessments, and analysis of historical data requirements.
Co-Leads are Jennifer Mahoney and Mark Phaneuf. Support from Barbara
Brown, Jim Evans, others as required.

Section 7: Operational Evaluation and Feedback

Seasonal Evaluation, System Review (Nov 03)

Section 8: Expectation of User Needs in the Out Years

End Day 1.

**Day 2 Notes:**

The following items still need to be resolved:

> Textbox
>
> Min area
>
> Edit training brief
>
> Binary verification improvements
>
> (New Item) Omit 05z CCFP (with backups)

Note: Next year this group will commission the CCFP requirements
document -- this year we inherited the existing document.

Omit 05z CCFP:

Jack May presented a proposal to eliminate the 050Z CCFP (see briefing
for detailed specifics). Currently they have 3 shifts a day with 5
minutes minimum overlap. 5 CCFP forecasters produce 12 CCFPs a day.

-   1 ¼ hours to analyze and forecast

-   ½ hour to collaborate

-   ¼ hour production

Problems:

-   Minimum time to coordinate between shifts

-   8am shift plays catch up most of the shift

-   No time for review

Proposal:

-   Eliminate the 050Z CCFP because its not utilized

-   Re-align shifts and include overlap

-   Allow time for review, shift transition, feedback

-   Bring back 050Z CCFP as needed (staff would stay on if needed,
    case-by-case)

Jack said they are open to other proposals from the users (drop a
different CCFP). The Group said the proposal needs to be written up and
circulated to CDM leadership.

ETMS Impact:

Eliminating the forecast will have no impact on ETMS, it will just flag
the data as being old.

Jack said the Weather Service could implement this change after the
start of the severe weather season, but the sooner they have a decision
the better.

The Weather Applications group FAA and NavCanada members have no
objection to this change. Russ Gold will check with ATA, specifically
the "box haulers".

Action Item: Jack May, Write up the proposal to eliminate the 05Z CCFP
and distribute to the Weather Applications group for feedback.

Action Item: Russ Gold, ATA to coordinate a replay to the proposal to
eliminate the 05Z CCFP with the \"Box Haulers\".

Action Item: Bill Cranor, Set up a telcon to discuss feedback on the
proposal to eliminate the 05Z CCFP and status other Weather Applications
actions/activities.

User Guide Review (continued):

Continued review/resolution of Section 9, page 14 Summary of Changes for
CCFP/2003

Nav Canada: -- ok

Text Box: -- Follow-up work needed; but remains in requirements
document. Mark to get data from Brad Sherman and will work with Dave to
consolidate previous work. Specific text box requirements can then be
defined. Not doable for 2003.

Lessens Learned: -- Avmet is funded for this work. Dave is developing
concept of use with team members (Dave, Steve, Darin, Mike). Several
groups are working "best practices". We will review/pick-up their
results due latter this summer.

Training: -- Deadline for updates is next Tuesday. However, Carol can
update as needed. Mark Phanuef will email the CCFP training package to
the group for comment and set up a telcon to discuss and recommend
changes to provide to Carol before Tuesday's deadline.

Action Item: Mark Phaneuf, Set up a telcon to discuss/recommend changes
to the CCFP training briefing presented by Carol Catron, ATT-240

Verification/Assessment: - (Combined 3 bullets- evaluation, impact
assessment, and reanalysis for this discussion). Jennifer and Mark will
form a sub-group to work these requirements. We need to ensure feedback
gets to the users. Group will work with centers to provide feedback.

Action Item: Co-Leads-Jennifer Mahoney, Mark Phaneuf, Review and update
as required \"skill measure\" language in CCFP User Needs, section 6.
This action updated on day 2 to include the establishment of a subgroup
to work section 6 requirements; evaluations, route impact assessments,
and analysis of historical data requirements. Co-Leads are Jennifer
Mahoney and Mark Phaneuf. Support from Barbara Brown, Jim Evans, others
as required.

Timely Evaluation and Reports: Monthly reports to be provided from Mark.
Commenter's need to be made to realize that the better the feedback the
more useful the information will be. Russ and Bill will discuss how best
to use operational feedback.

Action Item: Review and provide feedback on CCFP User Needs, section 7
(Operational Evaluation and Feedback). Bill C., Jim E., Dave R., Mark H.
to work this initially.

Minimum Area: Probability was discussed as the forecasters confidence
that the Wx will be present. Page 2, item #2 will be restated as a
bullet and moved to the list on page 14. The group was asked to provide
feedback on the definition of "intense convection". Also discussed if
lightning needs to be part on the definition on convection (not all
convection has lightning).

Action Item: Review CCFP Requirements 2.1 (Intense Convection) and 2.5
(Confidence) and propose any needed changes to the group. Jack May will
lead this Action with support from Dave R., Dale R., Russ G., Jennifer
M., Barbara B., Pete G., Tom F., and Mark P.

Action Item: Tom Fahey, Review CCFP \"identification of expectations for
needs in the outyears\" and provide recommendations to the Weather
Applications group,

**Meeting wrap-up:**

-   Telcon to be set up for February 13^th^ @ 3:00EST to discuss status.

-   By February 11^th^ send you inputs to Dave for consolidation and
    distribution. Input will be posted on the web for review.

Tim Grovac, ATCSCC is looking for feedback/input on NCWF and other
weather products.

Action Item: Dale Rhoda, Send out to the Weather Applications group the
list of NCWF issues that need to be discussed and addressed by this
group.

Members recommended that this group meet again before the May CRWG.
Members felt this group needs to meet more often than the CRWG meetings.
Dave proposed a Washington meeting, location and date TBD. It was
recommended that all members check travel budgets to ensure they can
support the activities of this group.

End Day 2

> **[New consolidated action items from this meeting]{.underline}**

+-----+---+---------------------------------+--------+--------+--------+
| *   | * | **Action Item**                 | **Acti | **Susp | *      |
| *Or | * |                                 | onee** | ense** | *Origi |
| igi | O |                                 |        |        | nating |
| nat | r |                                 |        |        | G      |
| ion | i |                                 |        |        | roup** |
| Dat | g |                                 |        |        |        |
| e** | . |                                 |        |        |        |
|     | R |                                 |        |        |        |
|     | e |                                 |        |        |        |
|     | f |                                 |        |        |        |
|     | \ |                                 |        |        |        |
|     | # |                                 |        |        |        |
|     | * |                                 |        |        |        |
|     | * |                                 |        |        |        |
+-----+---+---------------------------------+--------+--------+--------+
| **  | * | **Weather Applications          | ** **  | ** **  | ** **  |
|  ** | * | Actions**                       |        |        |        |
|     |   |                                 |        |        |        |
|     | * |                                 |        |        |        |
|     | * |                                 |        |        |        |
+-----+---+---------------------------------+--------+--------+--------+
| 1/2 | 1 | Create a Weather Applications   | Bill   | ASAP   | WxApp  |
| 9/2 |   | Team exploder                   | Cran   |        |        |
| 003 |   |                                 | or/USA |        |        |
|     |   |                                 | irways |        |        |
+-----+---+---------------------------------+--------+--------+--------+
| 1/2 | 2 | Contact Mark Cato, ALPA to      | Russ   | ASAP   | WxApp  |
| 9/2 |   | inform him that the Weather     | Go     |        |        |
| 003 |   | Application group has been      | ld/ATA |        |        |
|     |   | formed.                         |        |        |        |
+-----+---+---------------------------------+--------+--------+--------+
| 1/2 | 3 | Write up the proposal to        | Jack   | ASAP   | WxApp  |
| 9/2 |   | eliminate the 05Z CCFP and      | M      |        |        |
| 003 |   | distribute to the Weather       | ay/NWS |        |        |
|     |   | Applications group for          | AWC    |        |        |
|     |   | feedback.                       |        |        |        |
+-----+---+---------------------------------+--------+--------+--------+
| 1/2 | 4 | ATA to coordinate a replay to   | Russ   | By     | WxApp  |
| 9/2 |   | the proposal to eliminate the   | Go     | T      |        |
| 003 |   | 05Z CCFP with the \"Box         | ld/ATA | elecon |        |
|     |   | Haulers\".                      |        |        |        |
+-----+---+---------------------------------+--------+--------+--------+
| 1/2 | 5 | Set up a telcon to discuss      | Bill   | 2/1    | WxApp  |
| 9/2 |   | feedback on the proposal to     | Cran   | 3/2003 |        |
| 003 |   | eliminate the 05Z CCFP and      | or/USA |        |        |
|     |   | status other Weather            | irways |        |        |
|     |   | Applications                    |        |        |        |
|     |   | actions/activities.             |        |        |        |
+-----+---+---------------------------------+--------+--------+--------+
| 1/2 | 6 | Set up a telcon to              | Mark   | 1/3    | WxApp  |
| 9/2 |   | discuss/recommend changes to    | Ph     | 1/2003 |        |
| 003 |   | the CCFP training briefing      | aneuf/ |        |        |
|     |   | presented by Carol Catron,      | AveMet |        |        |
|     |   | ATT-240                         |        |        |        |
+-----+---+---------------------------------+--------+--------+--------+
| 1/2 | 7 | Provide consolidated CCFP       | Mark   | 2/     | WxApp  |
| 9/2 |   | training briefing changes to    | Ph     | 4/2003 |        |
| 003 |   | Carol Catron, ATT-240 by COB    | aneuf/ |        |        |
|     |   | 2/4/03                          | AveMet |        |        |
+-----+---+---------------------------------+--------+--------+--------+
| 1/2 | 8 | Text Box, what should be        | Brad   | TBD    | WxApp  |
| 9/2 |   | included and how it should be   | Sh     |        |        |
| 003 |   | used needs to be defined. Some  | erman/ |        |        |
|     |   | work was done on this topic by  |        |        |        |
|     |   | another group that needs to be  | ATCSCC |        |        |
|     |   | included in the discussion.     |        |        |        |
|     |   | Brad Sherman, ATCSCC will get   |        |        |        |
|     |   | info and provide to the group.  |        |        |        |
|     |   | Brad & Dave R. will consolidate |        |        |        |
|     |   | previous work.                  |        |        |        |
+-----+---+---------------------------------+--------+--------+--------+
| 1/2 | 9 | Review and update as required   | Co-Le  | TBD    | WxApp  |
| 9/2 |   | \"skill measure\" language in   | ads-Je |        |        |
| 003 |   | CCFP User Needs, section 6.     | nnifer |        |        |
|     |   | This action updated on day 2 to | Ma     |        |        |
|     |   | include the establishment of a  | honey, |        |        |
|     |   | subgroup to work section 6      | Mark   |        |        |
|     |   | requirements; evaluations,      | P      |        |        |
|     |   | route impact assessments, and   | haneuf |        |        |
|     |   | analysis of historical data     |        |        |        |
|     |   | requirements. Co-Leads are      |        |        |        |
|     |   | Jennifer Mahoney and Mark       |        |        |        |
|     |   | Phaneuf. Support from Barbara   |        |        |        |
|     |   | Brown, Jim Evans, others as     |        |        |        |
|     |   | required.                       |        |        |        |
+-----+---+---------------------------------+--------+--------+--------+
| 1/2 | 1 | Review and provide feedback on  | Bill   | TBD    | WxApp  |
| 9/2 | 0 | CCFP User Needs, section 7      | Cr     |        |        |
| 003 |   | (Operational Evaluation and     | anor/U |        |        |
|     |   | Feedback). Bill C., Jim E.,     | SAways |        |        |
|     |   | Dave R., Mark H. to work this   |        |        |        |
|     |   | initially.                      |        |        |        |
+-----+---+---------------------------------+--------+--------+--------+
| 1/2 | 1 | Review CCFP Requirements 2.1    | Jack   | By     | WxApp  |
| 9/2 | 1 | (Intense Convection) and 2.5    | M      | T      |        |
| 003 |   | (Confidence) and propose any    | ay/NWS | elecon |        |
|     |   | needed changes to the group.    | AWC    |        |        |
|     |   | Jack May will lead this Action  |        |        |        |
|     |   | with support from Dave R., Dale |        |        |        |
|     |   | R., Russ G., Jennifer M.,       |        |        |        |
|     |   | Barbara B., Pete G., Tom F.,    |        |        |        |
|     |   | and Mark P.                     |        |        |        |
+-----+---+---------------------------------+--------+--------+--------+
| 1/2 | 1 | Review CCFP \"identification of | Tom    | By     | WxApp  |
| 9/2 | 2 | expectations for needs in the   | Fah    | T      |        |
| 003 |   | outyears\" and provide          | ey/NWA | elecon |        |
|     |   | recommendations to the Weather  |        |        |        |
|     |   | Applications group,             |        |        |        |
+-----+---+---------------------------------+--------+--------+--------+
| 1/2 | 1 | Send out to the Weather         | Dale   | TBD    | WxApp  |
| 9/2 | 3 | Applications group the list of  | Rhoda  |        |        |
| 003 |   | NCWF issues that need to be     | /Volpe |        |        |
|     |   | discussed and addressed by this |        |        |        |
|     |   | group.                          |        |        |        |
+-----+---+---------------------------------+--------+--------+--------+

> **[Action items update from last meeting (December
> 2002)]{.underline}**

+----+------------------------------------+-----------+-------+-------+
| ** | ## Action                          | **A       | # Sus | **Sta |
| \# |                                    | ctionee** | pense | tus** |
| ** |                                    |           |       |       |
+----+------------------------------------+-----------+-------+-------+
|    | ### Weather Applications Team      |           |       |       |
+----+------------------------------------+-----------+-------+-------+
| 1  | ### Write                          | Ken       | ASAP/ | C     |
|    | up and provide preliminary meeting | Mull      |       | losed |
|    |  minutes and distribute to the Wea | en/AUATAC | 2     |       |
|    | ther Applications team for review. |           | weeks |       |
+----+------------------------------------+-----------+-------+-------+
| 2  | Weather Applications team members  | Weather   |       | C     |
|    | send comments/response on the      | Ap        |       | losed |
|    | "Guidelines for a Workgroup on     | plication |       |       |
|    | Weather Applications" document to  | team      |       |       |
|    | Dave Rodenhuis, ATT-260 at         | members   |       |       |
|    | <david.rodenhuis@faa.gov>.         |           |       |       |
|    | Response should include ideas on a |           |       |       |
|    | problem/mission statement, vision, |           |       |       |
|    | outcome, and deliverables.         |           |       |       |
+----+------------------------------------+-----------+-------+-------+
| 3  | Distribute the draft OEP and a     | Mark      |       | C     |
|    | draft mission statement to the     | Huberd    |       | losed |
|    | Weather Applications team members. | eau/MITRE |       |       |
+----+------------------------------------+-----------+-------+-------+
| 4  | Write up information on the high   | Dale      |       | Open  |
|    | resolution VEL product and         | Rhoda/    |       |       |
|    | distribute to the Weather          | Volpe     |       |       |
|    | Applications team.                 |           |       |       |
+----+------------------------------------+-----------+-------+-------+
| 5  | Establish a Weather Applications   | Ken       |       | C     |
|    | team web location.                 | Mullen/   |       | losed |
|    |                                    | AUATAC    |       |       |
+----+------------------------------------+-----------+-------+-------+
| 6  | CR Co-Leads need to establish Core | CR        |       | C     |
|    | team members on the Weather        | Co-Leads  |       | losed |
|    | Applications Team.                 |           |       |       |
+----+------------------------------------+-----------+-------+-------+
| 7  | Respond to a proposal from AvMet   | WeaApls   |       | In-pr |
|    | for training: Phase 1 (2003);      | Co-Chairs |       | ocess |
|    | Phase 2 (2004)                     | and CR    |       |       |
|    |                                    | Co-Chairs |       |       |
+----+------------------------------------+-----------+-------+-------+
| 8  | Ensure CCFP lessons learned and    | CR Leads  |       | C     |
|    | guidelines are pulled together for | and       |       | losed |
|    | use in future CCFP training        | D.        |       |       |
|    | (03/04). (It was suggested that    | Rodenhuis |       |       |
|    | AvMet be tasked to do this)        |           |       |       |
+----+------------------------------------+-----------+-------+-------+

**Attachment 2**

Meeting Minutes for the

FCA/Reroute Workgroup Meeting

##### January 28 -- 30, 2003

The FCA/Reroute Workgroup (WG) meeting was held at the Sofitel Hotel in
Miami, FL. The WG met on the 28^th^ and 29^th^ during workgroup breakout
sessions that were scheduled as part of the CRWG meeting, and as a group
on January 30^th^ after the conclusion of the CRWG meeting. This was the
eleventh meeting of the FCA/Reroute WG in the continuing development of
FEA/FCA procedures utilizing the Human-in-the-Loop (HITL) process.
Meeting briefings and presentations are available at
www.metronaviation.com/cdm.

Section I: Participants & Attendees

  ------------------- ------------------ --------------------------------------------------------
  Name                Org.               E-Mail

                                         

  Carol Catron        ATT-240            <Carol.catron@faa.gov>

  Ed Corcoran         ATT-100            <Ed.corcoran@faa.gov>

  Jo Damato           NBAA               [jdamato@nbaa.org](mailto:9-awa-atcscc-gadesk@faa.gov)

  Barry Davis         AUA-700            <Barry.davis@faa.gov>

  Jack Fastnaught     AUATAC             <Jack.fastnaught@auatac.com>

  Scott Fox           ATCSCC QA          <Scott.fox@faa.gov>

  Dan Horton          AUA-700            <Daniel.horton@faa.gov>

  Jim Houde           AUATAC             <Jim.houde@auatac.com>

  Jim Johnston        ATCSCC             <jjohnston@natca.net>

  Scott Kirby         ATL TMU            <stkby@bellsouth.net>

  Mark Libby          ATT-100            <Mark.libby@faa.gov>

  Mark Marchese       AUA-700            <Mark.marchese@faa.gov>

  John Martin         ATA                <jmartin@airlines.org>

  Tony Masalonis      Mitre/CAASD        <tonym@mitre.org>

  John Moffatt        Boeing ATM         <John.e.moffatt@boeing.com>

  Rick Oiesen         VNTSC              <Oiesen@volpe.dot.gov>

  Ed Olsen            NWA                Edward.olsen@nwa.com

  Paul Pederson       AUATAC             Paul.pederson@auatac.com

  Ed Wilken           ZKC                <Ed.wilken@faa.gov>

                                         
  ------------------- ------------------ --------------------------------------------------------

**Section II: Minutes**

Overview

The FCA/Reroute Workgroup (WG) consists of all major stakeholders
(Airlines, ATA, NBAA, NATCA, ADF and FAA) in a collaborative effort to
develop FEA/FCA procedures. This meeting was the next planned phase in
the development process. The objectives of this meeting were:

-   Development of FEA/FCA procedures

-   Validation of the Operational Concept (OpsCon) Phase I

-   Identify outstanding issues

-   Identify possible SPT changes

-   Establish ETMS priorities

-   RAT Integration

-   Discussion of Phase II

-   FCA Update Briefing

The WG participated in the overall general session of the CRWG meeting
and briefed the CRWG on the history, status and future plans of the WG.
They reviewed and made changes to the OpsCon and the Route Advisory
Procedures and discussed RAT Integration, as well as, plan for future
testing and development. The WG will continue the aggressive schedule of
meetings and testing in order to continue their progress on Phase II and
beyond.

**[Background]{.underline}**

Rick Oiesen developed a draft FCA Operational Concept (OpsCon) on
9/8/02. The WG completed a "walk-through" of the OpsCon on September 24
& 25, 2002 and a Dry Run on October 2, 2002. Since the original draft,
Rick has provided a series of revisions based on WG feedback and input.
The latest version is based on the phased-in approach agreed to by the
WG. The WG is continuing to modify the OpsCon in a collaborative effort
to find the most effective process in reducing delays and providing safe
and efficient air traffic management through more accurate and timely
information exchange and data sharing.

**[General Discussion]{.underline}**

The WG met in the general session on January 28^th^ and 29^th^ and met
as a group on January 30^th^. Some members met with the RAT during a
breakout session on the 28^th^ with the rest of the WG meeting
separately to finalize the FCA briefing that was presented to the
General Body on the 29^th^. The briefing consisted of the history of the
group; described the ongoing testing; noted the limitations, many of
which are automation issues; talked about future phases, post-2003,
including users being able to submit multiple intent (Working with RAT
is also part of the future plan); and, the Training Plan. It was noted
that cadre training would start around March. A copy of the briefing is
available on the CDM website.

*Reviewed January 16^th^ meeting minutes:* There were no changes and the
minutes were accepted as written. They are posted on the website.

*Action Items from previous meeting:* The action items listed below were
determined at the previous meeting. A consolidated list of Action Items
is attached as Appendix B.

-   One page Phase 1 document plus the Harting diagram to CRWG meeting
    (75copies): *Completed*

-   E-mail users with the phone number & pin \# a week before Test and a
    day before test via CDM exploder: - *Ongoing:* *John Martin*

-   Setup test guidelines and scenarios: *Ongoing:* *Ed C and Bryan*

-   Add more facilities to testing -- *This will be done in a
    progressive manner by adding 2 or 3 facilities at each test:* *Mark*

-   Add more users to testing -- *Ongoing:* *Loraine*

-   Bring laptop to the meetings -- *Ongoing:* *John Martin*

-   Check Steve Harting's status regarding retention as a representative
    -- *Steve is on a short-term detail and will be back in a few weeks.
    Mark Libby will follow-up.*

-   Find out from Chuck Vomacka's details about playbook names and
    ability to modify name, and about adding an "info" field. *- Mike
    Murphy: Mike was not present. This will be a carry-over item.*

*Reviewed Jan 21 Test:* The Test Notes have been distributed. Some of
the issues that were noted and comments:

-   How do you consider winds in the process if electronic intent is not
    used?

-   How to identify flights (flows) not directly impacted by the FCA,
    but shifted due to a shift in flow directly affected by the FCA?

-   Need to get more conscientious about the recording the test results.

-   Instead of copying the FCA and changing the filters, you could have
    drawn one for each flow. Ed C will talk to Brian about maybe
    formatting them this way for the next test. Rick Oiesen noted that
    for overlapping FCAs, data blocks would be automatically offset.

-   More detail is needed in the minutes of the tests.

### Future Tests

The next two scheduled test dates are 2/11 and 2/18. Mark Libby will
invite ZAU, ZOB ZMP and ZME. Participants will receive training at 8:00
a.m. on the morning of the Test, and the test will begin at 2:00 p.m.
There is an open question on what the correct protocol is for
coordination of TMCs for participation. Ed Wilken suggested that the
scenario should be kept fairly simple if we have new people
participating. Another suggestion was that these participants should be
the cadre trainers. John Martin noted that Bill Cranor asked for better
coordination for the tests (2/11 conflicts with some other meetings on
airline side).

Consensus is that the scenario information should be sent out more in
advance, possibly e-mail, though this would have to be sent 24 hours in
advance to ensure timely delivery of large e-mails with graphics. Ed
Wilken noted that if he has them too far in advance it might bias his
responses.

*Test Ideas:*

1.  Test could be a minor problem around Denver in conjunction with a
    big line, and see if we can get users around the 1^st^ one since
    there'll almost never be just one isolated event. Several people
    noted that you couldn't use UPT all the way around both events
    because the East is too structured. You could have a UPT to a point
    (i.e., the option in the advzy could be UPT is allowed up to fix X,
    then this is the route(s).

2.  Test the "more restricted to less" progression. Start with UPT,
    moving to route options, eventually moving to single route if
    needed. The OpsCon also allows progression in the other direction.

3.  Test each of the four types (UPT, etc.) in each of three different
    areas of the country.

4.  Test "Huberdeau/Brennan" model (CARD).

5.  Test needs to have the users move their planes and see what problems
    that generates.

## FCA enhancements in 7.5

As part of the Volpe update to the CRWG, Rick Oiesen asked field people
to state what they use FEA/FCA for:

-   ZMP: Used during frequency outage that disallowed opening
    ultrahigh - used altitude filters to get the demand on the
    ultrahigh. Also used it to see when MOAs would conflict with
    playbooks during severe weather. Also noted that ZOB was saying how
    they draw a box on their ZNY boundary, pull lists and monitor that
    all day long.

-   ZDV: Use moving FCAs and use the FCA to see demand on evaluating
    sector combining and decombining.

-   ZAB: Makes FEA for PHX arrivals, and share them with tower and
    Tracon. Color scheme shows us exactly which planes we are talking
    about. Helpful with the PHX runway construction going on.

-   SCT: Uses them to represent sectors of the Tracon since don't have
    Monitor/Alert for the sectors.

-   ZJX: Uses it for the 6 heavy sectors that we keep up on ESIS -- also
    to catch oceanic traffic, e.g. the southbound traffic, or the PBI
    deps -- I like how as soon as they get off, they pop up, since some
    of these (e.g., some of the GA) aren't in ETMS. Supervisors and
    ATCSs can walk by and see how busy it is.

-   ZDC: Uses it a lot for ZDC Sector 50 when doing MIT with ZNY - helps
    with dynamic tactical offloads down J75 -- nice to be able to filter
    it by center and altitude -- makes it cleaner -- also for SUAs in
    NY-DC-Philly area.

Rick noted that these are all local uses, and the FCA group is also
looking at use of FCA for national problems. Rick also listed 7.6
enhancements and mentioned the rationale behind the FCA Monitor: FCA
group has found it's hard to keep track of an ongoing FCA, so what's
needed is a tool to keep track.

**[Route Advisory Team (RAT)]{.underline}**

*Phil Smith on RAT Responder*: Key definitions for this section: When
FAA offers route options, user sends back a list of routes with one of
the following: Accept: the one out of those choices they agree to fly.
Unable (or Reject): cannot fly that one. Request: a route not on the
FAA's list of suggestions that the user offers to fly. The purpose of
all this is that unambiguous msgs must be sent by both FAA and users.
Mentioned possibility of 3 different codes the user could send to go
with routes -- "min cost" (the one generated by the flight planning -
maybe dispatch hasn't approved yet), "risk mgt." (dispatch has looked at
it in depth and it's more likely this will be the real route), and "FP"
(flight plan).

Reject, Accept, and Request are what the group seemed to agree there
should be codes for. There is an issue of what to do with "unable"
responses. For Phase 1, RAT should look at users attaching those 3 codes
to the routes (unable, accept, request). The group also decided to wait
and see how FCA and RAT are going before we decide the next steps. Based
on today's discussion, RAT will begin the write up for the RAT Phase 2
concept.

*RAT Integration:* Tony Massalonis briefed the conceptual mockups (no
prototype) of the integrated FCA-Reroute definition and listing
capabilities, which were evaluated during the FY02 CRCT evaluations and
revised according to the eval results and the current direction of the
FCA OpsCon. This is relevant even if RR modeling is not implemented
right away, because it still provides a starting point for thinking
about the integration of RAT, FCA, and Create RR, and for multiple
filters and the FCA Monitor. Tony also mentioned that some of the
graphics in this presentation were used to evaluate Progressive
Planning, a concept relevant to many of the things this group's been
discussing recently. Tony will put the briefing on the CDM web page. Rat
Integration will be a discussion item for the Boston agenda.

## ETMS 7.7

Dan Horton stated that 7.7 priorities have changed. Due to the complex
nature and workload involved of Reroute (RR) Modeling and Future Traffic
Display, they will not be in ETMS 7.7. There is a need to provide
essential functionality, which has moved into a higher priority. ETMS
7.7 will include: RAT enhancements, dynamic airspace, FCA-RAT-Create-RR
integration, multiple filter FCA, increased "and/or" capabilities,
enhancements to Create RR to modify advzy header, FCA monitor, filtering
dynamic list for field 10 contents, FCA list in RR advzy, HAR (High
Altitude Redesign). Dan stated that if we make RR modeling available on
the test string, he did not want it to be a distraction to ops people or
Volpe. The WG believe that RR modeling is a valuable tool and did not
want to see it sit on the shelf. Rick provided what is ready in RR
modeling: choosing the flights to RR, defining RR segment (corridor),
and ETMS calculates the end to end RR, with the exception of Crossing
Segment. Modeling impact to sectors is not done. Barry Davis will send a
revised list to Jim Houde who will explode to the WG. Rick will provide
an update at the next meeting.

**[Phase I OpsCon]{.underline}**

Ed Olsen had revised the Phase I OpsCon that effectively eliminated
steps 3 & 5 which were the steps dealing with "User Response", and this
was included as part of the WG briefing. After further discussion, the
WG agreed to add that every time a new or revised advzy was issued,
users would respond. Rick Oiesen provided some examples of how an advzy
might read.

Rick Oiesen led a discussion and provided some examples of how to
construct the advzy so it makes sense:

Example 1:

unrestricted UPT

Example 2:

(specific route) or

unrestricted UPT

Example 3:

(specific route) or

(specific route) or

restricted UPT (e.g., UPT allowed north of a given fix)

\[or any other combination. \]

The WG also discussed the possible confusion of altitudes relating to an
FCA It was agreed that even though it should be obvious, airspace users
can file anything outside the altitude range and be outside the FCA,
it's a training issue and at least for now, it should be restated in the
remarks section of the advzy that one of the user options is to take the
other altitude: "or unrestricted UPT AOB 240"

Another issue is if the user intention is to file a step climb but the
altitude isn't cleared yet, they will still appear in the FCA list.

Default Route (route they get if they do nothing): If the advzy is
unrestricted UPT, the idea is that the default route would be in the
remarks section. If there is more than one specific route, the
specialist would pick one of these to be the default. The default route
would usually be a playbook. There was some discussion of where the
default route would be implemented. If the closest play to the FCA is
used, it might create congestion there. Also, some of the flights flying
their UPT might go there. If the default route is farther from FCA, this
could penalize users unable to do UPT with a long default route. There
was some agreement on having one default route north and one south.

Rick will revise the OpsCon outline and One Page document.

## Route Advisory Procedures

*Procedures Notice review:* Lorraine Vomacka discussed changes needed to
the document: Background section is usually past tense; decided to add
an "FYI" tag for advzys requiring no action. This adds a 4^th^ category
to the Required, Recommended and Planned categories. A "Reason" field
was added to the info in the advzy. There were several other minor
changes

*FCA in Remarks section:* There was some discussion concerning possible
"gaming", but the overall feeling was that it rarely happens and is not
a major issue. This is the only way at the present time to tell
controllers to leave flights on the route. Otherwise, controllers might
give them a route that puts them back into the FCA. The procedures state
that FCA flights are not rerouted unless necessary (the same as NRP),
and will not be changed. The training issue will be to ensure that
controllers understand the relative weight of NRP and FCA for
prioritizing flights. In ETMS 7.6, there will be a column for getting a
list of flights that have FCA in remarks.

## Phase II

The WG will look at what technology will be available (which will be
learned during Phase I). Rick Oiesen stated that we have to distinguish
core ETMS from CCSD. We've fixed things in core ETMS that were broken --
multiple filters, and attaching FCA list to RAT. CCSD stuff -- RAT
responder and FCA Monitor -- is new ground and might take us into Phase
II as we start to look at it. TSD is tied to the 6-month cycle, but CCSD
can be changed whenever we have new code to put in.

List (not completed) of potential Phase 2 components:

1.  Public FEA

2.  FL attached to advzy (see below)

3.  Data integrity \[which means early intent but also reader and
    responder, unable routes, etc., improved prediction tools (Rick --
    better default -- i.e. historical - routes)\]

4.  Tools for GA to participate (CDM members and nonmembers)

5.  Exit strategy

6.  Phase I cleanup

7.  Controller education for no directs

8.  Rat Integration

*Attaching FL to advzy:* This would create confusion if it were static,
but it might help to have a starting list. This will be a training issue
to start with (train that the flight list is not the definitive list).
There was some confusion as to whether FPPP would know about the reroute
advzy. For now, Rick will just call Elvan.

Rick also mentioned a problem with filtered lists and the fact that it's
done by 3-letter code: GA users can't just get their N numbers. Also, in
compression, can't tie majors to their subsidiaries.

## WG Business

There is an on-going rumor that the FCA WG will be disbanded, although
Debbie and Bill have stated that the WG is doing an outstanding job and
that the WG will continue. There was also the rumor that RAT was going
away and the FCA WG will continue their work. The WG sees FCA as a whole
complex of things including process, while RAT is just the technology
for disseminating.

## Action Items 

-   CCSD FCA list for multiple FCAs

-   ID NATCA field POCs

-   Coordinate future tests with ATA members -- *John Martin*

-   Steve Harting status: *ongoing -- Mark*

-   ETMS update in BOS -- *Rick*

-   Revise OpsCon to show changes and distribute by 2/20 -- *Rick*

-   Develop document for GA needs and will explode to WG when completed
    -- *Jo*

-   Check with Mitre on FPPP exchange of information (possible new
    briefing) -- *Rick*

-   Find out from Chuck Vomacka's details about playbook names and
    ability to modify name, and about adding an "info" field. Mike M's
    AI to come up with playbook names -- *Mike Murphy*

-   Add more facilities to testing -- *This will be done in a
    progressive manner by adding 2 or 3 facilities at each test:* *Mark*

**[Future Events and Timeline]{.underline}**

[2003]{.underline}

02/11 8:00 a.m. FCA Training @ ATCSCC: 1:00 p.m. FCA/RAT Unified Test

02/18 8:00 a.m. FCA Training @ ATCSCC: 1:00 p.m. FCA/RAT Unified Test

02/25 -- 27 FCA WG Meeting @ Volpe: Start 25^th^ @ 10:00 a.m. End 27^th^
@ 4:00p.m.

03/04 -- 06 CDM Meeting @ Northrop Grumman Office Building in Fairlakes:

Start 4^th^ 12:00 -- 5:00. End 6^th^ 2:00

03/05 Breakout FCA/RAT 1:00 -- 5:00

03/06 FCA/RAT Meeting 1:00 -- 5:00

03/11 FCA/RAT Unified Test 10:00 a.m.

03/18 FCA/RAT Unified Test 10:00 a.m.

03/25 FCA/RAT Unified Test 10:00 a.m.

04/01 -- 03 FCA/RAT Meeting @ Northrop Grumman Bldg in Reston: Conf.
Room 6B

Start 1^st^ 10:00 a.m. End 3^rd^ 4:00 p.m.

05/07 -- 09 CRWG Meeting @ DTW: Start 7^th^ @ 12:00 end 9^th^ @ 12:00

05/12 Implement 2003 Operational Testing

> **APPENDIX A:** Consolidated Parking Lot Items (1/30/03)

1.  Drop-down menu for Route Advzy Categories: *This issue is an open
    Item for 7.7*

2.  "AMD" in front of "Route Advisory" in ADVZY top line: *This issue is
    an open Item for 7.7*

3.  "Exit" ADVZY category: *Phase II issue to be discussed in MIA - High
    priority*

4.  Suspension of Direct Routes (prevention of routing into FCA by
    controllers upstream): *Phase II issue*

5.  FCA focal point for each facility (LS): *Discussion item for MIA*

6.  Determine TransCon Preplanning CARD-MITRE tie-in. (Huberdeau /
    Brennan presentation): *Future, Ongoing*

7.  Determine and correct the problem of FCA's dropping off the CCSD at
    the FCA's expiration, the "End Time". *Rick will update in MIA*

8.  Add CDR and Playbook routes to CCSD: *Ongoing Item for Volpe. Move
    to Phase 2 or beyond*

9.  Discuss the Host/FPPP presentations (Jay Merkle presentation):
    *Later discussion item*

10. Route Options: *Priority for 7.7 Multiple Playbooks*

11. Develop cancellation procedures when there are conflicting
    reroutes*. Will be evaluated during testing. Phase II discussion
    items*

12. Determine Exit Strategy. *Will be evaluated during testing. Phase II
    discussion items*

13. Equity: *Ongoing. Will be evaluated during testing. Phase II
    discussion items (Possible Equity Laundry List)*

    a.  Determine how to measure

    b.  Determine how equity in current OpsCon is captured. *(Statement
        for Phase 1 OpsCon?)*

14. Determine CCFP tie-in*. Resolved BY NO-auto tie-in*

15. Determine how to prioritize multiple FCA's . *Will be evaluated
    during testing. Phase II discussion items*

16. Conduct one of the FCA tests at VOLPE: *Scheduled for Apr 1-3* :
    **Cancelled for April**

17. Determine how airborne aircraft concerns are discussed on the SPT
    TELCON for Phase 1 (tactical) (for discussion: SH) (FCA Monitor?):
    *Phase II topic*. *Possible FCA Monitor Solution*

18. Suspension of Direct Routes that affect down-line sector
    predictability

19. Expand field to include more description of FCA (Why is FCA being
    issued...for Users): *For Phase II*

20. Change naming convention of FEA/FCA'S to:
    "FCA[\_\_\_(description)\_\_\_"]{.underline}, instead of "FCA001",
    etc: *For Phase II. 7.7 Issue*

21. Additional Early Intent code besides "N", for "Wind", "Operational",
    etc: *Priority for* *7.7 Phase II* *issue*

22. Dynamic List column "FCA\_\_\_\_" remark. In 7.6: *Completed*

23. Develop a TSD function to offer transition points: *Phase II disc.
    Item*

24. Filters for Dynamic list: *Completed in 7.6*

25. Automatic updating flights to the FCA flight list: *FCA Monitor
    should capture. Further testing to determine*

26. Identify FCA Icons w/symbol (?) What flights have been routed around
    FCA: Discu*ssion for 7.7 Part of FCA Monitor*

27. Sub-categories, ADVSRY Issue. Amended and Cancelled in top line: *To
    be discussed for 7.7 Phase II*

28. FCA sub-group (multi-filter capability) development in ETMS/TSD*:
    Defined for 7.7. Priority Item*

29. Determine and request a method of tracking the flights that take
    route options, on the TSD: *FCA Monitor. Will come out in phases*

> Prototype in March: *Testing and Candidate for 7.7*

a.  TSD icon: add a square or similar Bullets included with Monitor

b.  Flight list indicationTrack early intent in TSD

c.  Data block color, changing color, etcMore than one line of ADVZY in
    OIS: *Completed for Spring.*

**APPENDIX B:** Consolidated Action Items (1/30/03)

1.  Explode revised draft OpsCon to FCA/RR WG (FCA/Reroute Workgroup)
    for review/comment -- *This is an on-going issue: Rick*

2.  Review revised draft OpsCon and then forward to Debbie and Bill C
    for dissemination to CDM -- *Ongoing issue: Mark/Loraine*

3.  Include instructions for where to direct questions to the FCA/RR WG
    (to group leads, NBAA, or ATA) in the email accompanying the OpsCon
    draft exploded to CDM -- *Ongoing issue: Rick/Loraine/Mark*

4.  Write, then Explode (to FCA/RR WG), Review, Forward (to DJ/BC),
    Explode (to CDM): [Phase 1 Doc]{.underline} (steps same as for
    OpsCon) -- *Ongoing issue: Rick*

5.  Include instructions for where to direct questions to the FCA/RR WG
    (to group leads, NBAA, or ATA) in the email accompanying the OpsCon
    draft exploded to CDM -- *This is an on-going issue:
    Rick/Loraine/Mark*

6.  Form a Volpe team, re: Web page for Users -- *Rick*

7.  Submit SPO format change proposal to SPT -- *Joe Dotterer\**

8.  FCA Advzy template for v7.7 -- ***Joe Dotterer\****

9.  Second draft of Integrated Procedures for spring -- *LV, by 12/13 -
    Completed*

10. Memo re: sharing User-created (CCSD) FEA'S- *Ken*

11. Schedule OJT Lab for scheduled test dates: ***Carol\****

12. Add 1-2 airline alternates (including RAA, if possible): *LS*

13. E-mail users with the phone number & pin \# a week before Test and a
    day before test via CDM exploder: - *Ongoing:* *John Martin*

14. Setup test guidelines and scenarios: *Ongoing: Ed C and Bryan*

15. Add more facilities to testing -- This will be done in a progressive
    manner by adding 2 or 3 facilities at each test: *Mark*

16. Add more users to testing -- *Ongoing:* *Loraine*

17. Bring laptop to the meetings -- *Ongoing:* *John Martin*

18. GA access to enter intent on the web. - *Volpe*

. \* Joe & Carol's status with the WG has changed.

**Attachment 3**

Meeting Minutes for the

Playbook Workgroup Group

### Breakout Session, Wednesday 1/28

**Attendees:**

Jeff Richards (ATCSCC) Chair, Joe Bertepelle (AAL), Ted Christy (USA
Dispatch), Cliff Keirce (ATCSCC), Steve McMahon (ATCSCC), Gretchen
Wilmouth (Metron), Don Jaeger (ATCSCC), Scott Fox (ATCSCC), Jim Hill
(Volpe), Tom St. Clair (FAA/ATCSCC/TUT), Lt Col Pete Wyman (USAF), David
Frame (FAA-ZHU TMU), John Berggren (FAA-ZOA TMU), Jerry Serafini
(FAA-SCT TMU), Curt Kaler (FAA-ZMP), Roger Bruce (FAA-ZDV), Doug
Buckingham (FAA-ZLA), Ernest Snyder (FAA-ZFW), Gary Tigert (FAA-ZME),
Shon Grabbe, (NASA Ames), Kapil Sheth (NASA Ames/Raytheon), Bob Vivona
(Titan Corp), Bob White (NAVCANADA-CZY), Marty Rosenberg (FAA-ZNY), and
Paul Pederson (AUATAC/NGMS).

1\. Jeff Richards offered everyone the opportunity to see how the Route
Management Tool (RMT) works. Gretchen Wilmouth demonstrated RMT on a
laptop computer for those interested. Joe Bertepelle asked what names
would be used to identify routes. Jeff Richards said that the Playbook
name is used and there is only one unique CDR (coded departure route)
for each playbook play on a city pair. The Reroute Advisory Team (RAT)
list will give the full routing.

2\. Jeff Richards requested that each facility investigate the CDRs and
Playbook routes so that the RMT has every route and those associated
with it are properly linked in the RMT database.

3\. Jeff Richards stated that the Playbook group did not plan to do
Airspace Redesign grid system changes until that implementation is near
term. Currently, he stated there are ten Playbook routes that are in
conformance with the Airspace Redesign grid system.

4\. Marty Rosenberg asked if there was a way to identify whether
aircraft and flight crews were qualified to fly over oceanic areas in
ZNY airspace. This may allow some departures over the water beyond
domestic airspace when conditions preclude non-qualified flight
crews/equipment from such departures. Jeff Richards asked that airlines
contact Marty directly to discuss this.

5\. The group was provided with a demonstration of the Future Air
Traffic Management Concepts Evaluation Tool (FACET) and System-Wide
Evaluation and Planning Tool (SWEPT) by the NASA Ames people and Jim
Hill of the Volpe Center.

**Attachment 4**

Meeting Minutes for the

ITFM Workgroup Group

## Purpose

This note records activities of the Integrated Traffic Flow Management
(ITFM) committee of the Collaborative Decision Making (CDM) activity.
The committee met at breakout sessions of the CR meeting in Miami, FL on
January 28-29, 2003.

## Breakout Session, Tuesday 1/28

1.  Gary Nelson announced taking over as ITFM recorder for the AUA TAC.
    A signup sheet was circulated with the intent of giving access to
    the AUA-700 website and collaborative workspace.

2.  Several new participants attended. Co-Chair Tom White reiterated the
    mission of the committee and Co-Chair Bill Leber reiterated the
    products to be created: A roadmap of where to get data for making
    TFM/Dispatching decisions, a concept of operations (conops),
    business plan and requirements.

3.  Michael Wambsganns recommended reference to the RTCA conops
    \[National Airspace System Concept of Operations and Vision for the
    Future of Aviation, November 15, 2002. This is a RTCA copyright
    document.\]

4.  Extensive discussion followed on the approach to the mission.
    Various suggestions for:

    -   Bottom up rather than top-down approach of what is done to
        define best practices.

    -   Create the conops according to the available outline (from the
        Operational Concept Definition). Also need to go the next level
        from RTCA conops to support FAA requirements.

    -   Using the website for offline work.

    -   Commitment of more support resources.

    -   Get beyond current technical limitations for properly structured
        decision making.

    -   Respond to Jack Kies request for short-term solutions but also
        look at bigger picture for a system that is not stovepiped (is
        integrated).

5.  There was consensus that the approach required a scenario to augment
    existing process flow charts.

6.  Action: The AUATAC was assigned to ready the website for
    collaborative work in February. Committee members were assigned to
    supply inputs on "what you need to know about demand and capacity to
    make decisions".

## Breakout Session, Wednesday 1/29

1.  It was announced that Riley Shamburger would replace Bill Leber as
    co-chair.

2.  Tom White established that scenarios will be created as a way of
    testing products being developed for TFM. Decisions and data would
    be defined as part of the scenarios. A small core group would be
    maintained for continuity of the committee.

3.  There was extensive discussion about the scenarios, the need to
    define capacity more uniformly/objectively, knowledge about flight
    lists from tools and in TMC experience, and the need/availability of
    tools for predictive evaluation of TFM decisions.

4.  Mike Klinker took the floor to outline a scenario based on ZDC/ZNY
    coordination around fix White and Sector 50. This scenario is
    recorded in a separate document for the website.

5.  Action: Post the scenario on the website and notify committee list.
    The committee adjourned until further notice.

##  

**Attachment 5**

Meeting Minutes for the

RAT Workgroup Group

**Breakout Session, Wednesday 1/29**

Tim Grovac thought that a wall should be put in place to protect the OPS
from test data being sent to an operational system.

Data will be sent to ATCSCC to test the PC's that will be used.

A document will be sent to explain how the test will be conducted.

The test will be conducted on Mon, Wed., and Fri. in March and April.

Coordination with NATCA has been completed.

As of May "Spam" will be reduced.

Reroutes will be sent as if you were a participant on the flight list
and on the facilities list.

ARTCC's that have no departures still get the advisory if they are on
the facilities list.

Alternate restrictions are only able in Remarks.

Several question were asked;

1.  Should enroute restrictions be sent to the airlines.

2.  How to identify flights that get restrictions.

3.  Have these airplanes landed.