Collaborative Routing Meeting 8/31/99 Northwest Airlines

**to:** Colloborative Routing Meeting Participants

**from:** GAry Dockan

**subject:** CR Short term/long term tool development meeting minutes

**date:** 11/12/2023

+------------+------------+-----+-----+---------------------+---------+
| ##### In   | > Name     | >   |     | > Email             | > Phone |
| Attendance |            | Org |     |                     |         |
|            |            | ani |     |                     |         |
|            |            | zat |     |                     |         |
|            |            | ion |     |                     |         |
+------------+------------+-----+-----+---------------------+---------+
|            | > Loraine  | >   | > L |                     | > 713-3 |
|            | > Sandusky | COA | SAN |                     | 24-7276 |
|            |            |     | DU@ |                     |         |
|            |            |     | COA |                     |         |
|            |            |     | IR. |                     |         |
|            |            |     | COM |                     |         |
+------------+------------+-----+-----+---------------------+---------+
|            | > Kevin    | >   | >   |                     | > 724-  |
|            | > Kollmann | Met | <Ko |                     | 857-346 |
|            |            | ron | llm |                     |         |
|            |            |     | ann |                     |         |
|            |            |     | @me |                     |         |
|            |            |     | tsc |                     |         |
|            |            |     | i.c |                     |         |
|            |            |     | om> |                     |         |
+------------+------------+-----+-----+---------------------+---------+
|            | > Mike     | >   | >   |                     | > 703-7 |
|            | >          | Met |  <W |                     | 87-8700 |
|            |  Wamsganss | ron | amb |                     |         |
|            |            |     | sga |                     |         |
|            |            |     | nss |                     |         |
|            |            |     | @me |                     |         |
|            |            |     | tsc |                     |         |
|            |            |     | i.c |                     |         |
|            |            |     | om> |                     |         |
+------------+------------+-----+-----+---------------------+---------+
|            | > Ken      | >   | >   |                     | > 617-4 |
|            | > Howard   |  Vo |  <H |                     | 94-2697 |
|            |            | lpe | owa |                     |         |
|            |            |     | rdk |                     |         |
|            |            |     | @vo |                     |         |
|            |            |     | lpe |                     |         |
|            |            |     | .do |                     |         |
|            |            |     | t.c |                     |         |
|            |            |     | om> |                     |         |
+------------+------------+-----+-----+---------------------+---------+
|            | > Phil     | >   | >   |                     | > 614-2 |
|            | > Smith    | OSU | <Ph |                     | 92-4120 |
|            |            |     | ilt |                     |         |
|            |            |     | @OS |                     |         |
|            |            |     | U.e |                     |         |
|            |            |     | du> |                     |         |
+------------+------------+-----+-----+---------------------+---------+
|            | > Roger    | >   | > < |                     | > 817-9 |
|            | > Beaty    | AAL | R_B |                     | 31-0951 |
|            |            |     | eat |                     |         |
|            |            |     | ty@ |                     |         |
|            |            |     | com |                     |         |
|            |            |     | pus |                     |         |
|            |            |     | erv |                     |         |
|            |            |     | e.c |                     |         |
|            |            |     | om> |                     |         |
+------------+------------+-----+-----+---------------------+---------+
|            | > Rick     | >   | > < |                     | > 617-4 |
|            | > Oiesen   |  Vo | Oie |                     | 94-2309 |
|            |            | lpe | sen |                     |         |
|            |            |     | @vo |                     |         |
|            |            |     | lpe |                     |         |
|            |            |     | .do |                     |         |
|            |            |     | t.g |                     |         |
|            |            |     | ov> |                     |         |
+------------+------------+-----+-----+---------------------+---------+
|            | > Craig    | >   | >   |                     | > 817-9 |
|            | > Marquis  | AAL | <CR |                     | 67-7192 |
|            |            |     | AIG |                     |         |
|            |            |     | _MA |                     |         |
|            |            |     | RQU |                     |         |
|            |            |     | IS@ |                     |         |
|            |            |     | amr |                     |         |
|            |            |     | cor |                     |         |
|            |            |     | p.c |                     |         |
|            |            |     | om> |                     |         |
+------------+------------+-----+-----+---------------------+---------+
|            | > Russell  | >   | >   |                     | > 901-7 |
|            | > gold     |  FE |  <R |                     | 97-6024 |
|            |            | DEX | gol |                     |         |
|            |            |     | d@f |                     |         |
|            |            |     | ede |                     |         |
|            |            |     | x.c |                     |         |
|            |            |     | om> |                     |         |
+------------+------------+-----+-----+---------------------+---------+
|            | > Anthony  | >   | >   |                     | > 703-9 |
|            | > Milligan | FAA |  <A |                     | 04-4417 |
|            |            |     | nth |                     |         |
|            |            |     | ony |                     |         |
|            |            |     | .mi |                     |         |
|            |            |     | lli |                     |         |
|            |            |     | gan |                     |         |
|            |            |     | @fa |                     |         |
|            |            |     | a.g |                     |         |
|            |            |     | ov> |                     |         |
+------------+------------+-----+-----+---------------------+---------+
|            | > Chris    | >   | > < |                     | > 877-6 |
|            | > Pear     | UAL | Cdp |                     | 01-9224 |
|            |            |     | ear |                     |         |
|            |            |     | @ua |                     |         |
|            |            |     | l.c |                     |         |
|            |            |     | om> |                     |         |
+------------+------------+-----+-----+---------------------+---------+
|            | > Curt     | >   | >   |                     | > 651-4 |
|            | > Kaler    | ZMP |  <C |                     | 63-5580 |
|            |            |     | urt |                     |         |
|            |            |     | .Ka |                     |         |
|            |            |     | ler |                     |         |
|            |            |     | @fa |                     |         |
|            |            |     | a.g |                     |         |
|            |            |     | ov> |                     |         |
+------------+------------+-----+-----+---------------------+---------+
| #####      | > Mike     | >   | >   |                     | > 301-4 |
|            | > Ball     | Uof |  <M |                     | 05-2227 |
|            |            | >   | bal |                     |         |
|            |            |  MD | l@r |                     |         |
|            |            |     | hsm |                     |         |
|            |            |     | ith |                     |         |
|            |            |     | .um |                     |         |
|            |            |     | d.e |                     |         |
|            |            |     | du> |                     |         |
+------------+------------+-----+-----+---------------------+---------+
| #####      | > Mike     | >   | >   |                     | > 314-5 |
|            | > Nadon    | TWA |  <M |                     | 51-1672 |
|            |            |     | jna |                     |         |
|            |            |     | don |                     |         |
|            |            |     | @tw |                     |         |
|            |            |     | a.c |                     |         |
|            |            |     | om> |                     |         |
+------------+------------+-----+-----+---------------------+---------+
| #####      | > Steve    | >   | > < |                     | > 770-9 |
|            | > Caise    | ADF | Ste |                     | 82-6626 |
|            |            |     | ve@ |                     |         |
|            |            |     | val |                     |         |
|            |            |     | uwe |                     |         |
|            |            |     | b.c |                     |         |
|            |            |     | om> |                     |         |
+------------+------------+-----+-----+---------------------+---------+
| #####      | > Carla    | >   | > < |                     | > 817-2 |
|            | > Beck     | ADF | Car |                     | 47-1777 |
|            |            |     | la@ |                     |         |
|            |            |     | val |                     |         |
|            |            |     | uwe |                     |         |
|            |            |     | b.c |                     |         |
|            |            |     | om> |                     |         |
+------------+------------+-----+-----+---------------------+---------+
| #####      | > Ted      | >   | >   |                     | > 412-7 |
|            | > Christie | USA | <Sm |                     | 47-5062 |
|            |            |     | ers |                     |         |
|            |            |     | h@n |                     |         |
|            |            |     | aut |                     |         |
|            |            |     | ico |                     |         |
|            |            |     | m.n |                     |         |
|            |            |     | et> |                     |         |
+------------+------------+-----+-----+---------------------+---------+
| #####      | > Gary     | >   | > < |                     | > 412-7 |
|            | > Dockan   | USA | Doc |                     | 47-1680 |
|            |            |     | kan |                     |         |
|            |            |     | @us |                     |         |
|            |            |     | air |                     |         |
|            |            |     | way |                     |         |
|            |            |     | s.c |                     |         |
|            |            |     | om> |                     |         |
+------------+------------+-----+-----+---------------------+---------+
| #####      | > Ed       | >   | >   |                     | > 214-7 |
|            | > Laster   | SWA | <El |                     | 92-4823 |
|            |            |     | ast |                     |         |
|            |            |     | er@ |                     |         |
|            |            |     | wnc |                     |         |
|            |            |     | o.c |                     |         |
|            |            |     | om> |                     |         |
+------------+------------+-----+-----+---------------------+---------+

+------------+---------------------------------------------------------+
| ##         | > Bill -- Open discussion on Long Term and Short term.  |
| ### Agenda | > Later on we will boil down specifics. Provide a wish  |
|            | > list of functionality for next years SWAP. Tools to   |
|            | > be developed by May 1^st.^                            |
+------------+---------------------------------------------------------+

+------------+---------------------------------------------------------+
| ##### Ye   | > Mike N. -- Reviewed yesterdays meeting. Concluded     |
| sterday's  | > that ATMC deals with increasing capacity and CDM      |
| discussion | > deals in problems where demand exceeds capacity.      |
|            | > Ultimately the same goal.                             |
+------------+---------------------------------------------------------+

+------------+---------------------------------------------------------+
| ##### CR   | > Goal of CR is to develop Collaborative Routing tools  |
| Goal for M | > to reduce TFM intervention, minimizing ground stops,  |
| ay 1 Tools | > ground delays, and MIT.                               |
+------------+---------------------------------------------------------+

+------------+---------------------------------------------------------+
| ###        | > Carla offered Severe Weather Management booklet       |
| ## Nationa | > developed by ATCSCC as the template as the National   |
| l Playbook | > Playbook.                                             |
|            | >                                                       |
|            | > Bill referred to items discussed in 8/30/99 Airline   |
|            | > only meeting.                                         |
|            |                                                         |
|            | 1.  Demand Prediction                                   |
|            |                                                         |
|            | 2.  Constraint Prediction                               |
|            |                                                         |
|            | -   What-if capability for ATM                          |
|            |                                                         |
|            | -   Impact assessment                                   |
|            |                                                         |
|            | -   Rationing                                           |
|            |                                                         |
|            | 3.  Route Generation/Approval                           |
|            |                                                         |
|            | 4.  Real-time display of...                             |
|            |                                                         |
|            | -   Constraint Display                                  |
|            |                                                         |
|            | -   AOC/ATC interact Collaborative Tool                 |
|            |                                                         |
|            | -   Demand Display                                      |
|            |                                                         |
|            | > Kevin suggested to add Impact assessment under        |
|            | > Constraint predictability.                            |
+------------+---------------------------------------------------------+

+------------+---------------------------------------------------------+
| #####      |                                                         |
+------------+---------------------------------------------------------+
| ###        | > Bill -- are we about reinventing the wheel or         |
| ## Demand  | > building upon ETMS?                                   |
| Prediction | >                                                       |
|            | > Rick O. touched on ETMS transitioning to CDM with     |
|            | > Demand prediction at 15 minute intervals.             |
|            | >                                                       |
|            | > Needed items from ETMS.                               |
|            | >                                                       |
|            | > **[DEMAND REQUIREMENTS]{.underline}**                 |
|            |                                                         |
|            | -   Airports                                            |
|            |                                                         |
|            | -   Sectors                                             |
|            |                                                         |
|            | -   Fixes                                               |
|            |                                                         |
|            | > Issues --                                             |
|            | >                                                       |
|            | > LOA's (Letter of Agreement?) Missing                  |
|            | >                                                       |
|            | > \*User Access                                         |
|            |                                                         |
|            | -   Probability of DEMAND (uncertainty)                 |
|            |                                                         |
|            | -   Constraint Feedback                                 |
|            |                                                         |
|            | -   Confliction Probability                             |
|            |                                                         |
|            | -   Advanced Demand Information                         |
|            |                                                         |
|            | -   ETMS Modeling                                       |
|            |                                                         |
|            | -   EADL (Enroute Aggregate Demand List)                |
+------------+---------------------------------------------------------+

+------------+---------------------------------------------------------+
| ####       | > Brief discussion with Anthony Milligan and Rick O.    |
| # Demand P | > and Ken Howard on ETMS capabilities in reference to   |
| rediction  | > changing flight plan data and having it reflected in  |
| Discussion | > ETMS.                                                 |
|            | >                                                       |
|            | > Bill -- any showstoppers on access to ETMS data base. |
|            | > Roger -- will the users have the access to certain    |
|            | > elements of the ETMS data base. Chris will take the   |
|            | > ACTION ITEM to write a letter to Jack Kies requesting |
|            | > open access to ETMS, which items will not be          |
|            | > accessible. Anthony suggested we request individual   |
|            | > items as needed.                                      |
|            | >                                                       |
|            | > Mike/Roger -- we are defining routes. Route as a      |
|            | > control mechanism. We use the route to define the     |
|            | > constraint. Mike Ball -- we try to get an estimate of |
|            | > time in center airspace and add them up. You have to  |
|            | > take into account the uncertainty. Bill -- you need   |
|            | > probability predictability. Anthony -- can a tool be  |
|            | > developed to have ETMS predict demand on flow based   |
|            | > on MIT. Mike reintroduced the "Dithering" factor.     |
|            | > Just as the Dispatch and Cockpit view of weather is   |
|            | > different and how to get around it is different,      |
|            | > Airlines stratagy of routing around weather will be   |
|            | > different as well. Mike -- those that don't           |
|            | > participate in CDM may have to abide by ATC direction |
|            | > to route around weather.                              |
|            | >                                                       |
|            | > Ken -- Is what you are looking for earlier route      |
|            | > data, and knowing a flight has already been rerouted? |
|            | > Do you want to have earlier filing of flight plans?   |
|            | > ETMS (ADL) should be thought of as a planning data    |
|            | > base.                                                 |
|            | >                                                       |
|            | > Roger -- what gets flown and what gets filed.         |
|            | >                                                       |
|            | > Mike N.-- TWA flies 90% of the way flight plans are   |
|            | > filed.                                                |
|            | >                                                       |
|            | > Bill -- airlines have to show advanced intent on      |
|            | > filing flight plans.                                  |
|            | >                                                       |
|            | > NATCA is opposed to user access of ETMS data.         |
+------------+---------------------------------------------------------+

+------------+---------------------------------------------------------+
| #####      | > **[CONSTRAINT PREDICTION]{.underline}**               |
|  CAPACITY  | >                                                       |
| PREDICTION | > -Climb/Desc                                           |
|            | >                                                       |
|            | > -Transition                                           |
|            |                                                         |
|            | -   ETMS -- Base #'s                                    |
|            |                                                         |
|            | -   Lack of Complexity information                      |
|            |                                                         |
|            | -   Isolate Complexity source by flight                 |
|            |                                                         |
|            | -   Dynamic Adjustment of sector capacity               |
|            |                                                         |
|            | -   Capacity Thresholds for planning query.             |
+------------+---------------------------------------------------------+

+------------+---------------------------------------------------------+
| #####      | > Roger -- Can we develop a flight planning data base   |
|  Capacity  | > that will look at sector constraints.                 |
| Discussion | >                                                       |
|            | > Rick -- ETMS numbers don't actually capture capacity. |
|            | > Phil - ATC says let me move these few planes and we   |
|            | > will increase capacity. Curt K. -- there is an        |
|            | > equation that allows a general knowledge of activity  |
|            | > in a sector.                                          |
|            | >                                                       |
|            | > Mike W. -- do you want to know capacity or do you     |
|            | > want to know constraint in the sector.                |
|            | >                                                       |
|            | > Anthony -- are you looking for a monitor alert        |
|            | > trigger that will prompt the controller to notify the |
|            | > dispatcher of the consequences of filing route. Mike  |
|            | > N. Let me file my NRP route. Let me know if the       |
|            | > consequence of saving 2 minutes by filing NRP will    |
|            | > cause additional dlys because of saturation of        |
|            | > specific sector.                                      |
|            | >                                                       |
|            | > Ken -- Just like Monitor Alert, you are looking for   |
|            | > thresholds that alert when capacity is exceeded. Bill |
|            | > -- filing a flight plan is "buyer beware", plans can  |
|            | > change at anytime. -- Ted C. -- you cannot predict,   |
|            | > but you need a tool that can reflect what is taking   |
|            | > place in the airspace at a given time. Roger -- A     |
|            | > flight plan is a ticket to an amusement park          |
|            | >                                                       |
|            | > Roger -- Collaborative, cooperative, independent      |
|            | > action.                                               |
|            | >                                                       |
|            | > Collaborative -- both have to agree                   |
|            | >                                                       |
|            | > Cooperative -- you watch and make a decision, I watch |
|            | > and make a decision.                                  |
|            | >                                                       |
|            | > Independent -- you see it and make a decision.        |
|            | >                                                       |
|            | > Mike --what can airlines do to increase the accuracy  |
|            | > further out.                                          |
+------------+---------------------------------------------------------+

+------------+---------------------------------------------------------+
| ###        | -   DEMAND                                              |
| ## Realtim |                                                         |
| e Displays | -   CONSTRAINT                                          |
|            |                                                         |
|            | -   AOC-TFM                                             |
|            |                                                         |
|            | > 4D Traffic Display                                    |
|            | >                                                       |
|            | > 4D Constraint Display                                 |
|            |                                                         |
|            | -   Digital Access to real time demand /constraints     |
|            |     > database.                                         |
|            |                                                         |
|            | -   Tool able to draw Flight Constrained Area's (FCA)   |
|            |                                                         |
|            | -   List flights caught up in FCA                       |
|            |                                                         |
|            | -   Up to six hours.                                    |
|            |                                                         |
|            | -   CDR (Coded Departure Routes) overlay.               |
|            |                                                         |
|            | -   Flight specific query through constrained airspace. |
+------------+---------------------------------------------------------+

+------------+---------------------------------------------------------+
| ####       | > Roger -- Talk about displays, but in the real world   |
| # Realtime | > we need to automate the displays. Bill -- does ETMS   |
|  Displays  | > have the ability to display real time demand? Rick -- |
| Discussion | > Traffic Management could make good use of data in the |
|            | > ETMS "LISTS". Roger -- show me when I will be over    |
|            | > this fix. Let me rewind and replay. If I submit 5     |
|            | > flights, get one back that is not affected by         |
|            | > constraints. Rick O. -- Every 5 minutes ETMS produces |
|            | > the TMD file that looks ahead 2 ¼ hours. For every    |
|            | > alerted sector and fix, it displays capacity and      |
|            | > demand. This is what is used to generate Monitor      |
|            | > Alerts.                                               |
|            | >                                                       |
|            | > Bill -- Looks like the tool to be developed is an FAA |
|            | > developed tool. C.R. wants to give input into the     |
|            | > development of a near term tool.                      |
|            | >                                                       |
|            | > Bill -- Each carrier send in a wish list of what is   |
|            | > important to you in the development of a long term    |
|            | > tool by 9/15.                                         |
|            | >                                                       |
|            | > Kevin -- Diversion off the gate tool, (DOG) will be   |
|            | > done in 30 days.                                      |
+------------+---------------------------------------------------------+

+------------+---------------------------------------------------------+
| #          | 1.  CDR's (Coded Departure Routes) -- Subgroup review.  |
| #### Near  |                                                         |
| Term Goals | 2.  Publishing and access to constraints.               |
|  by 5/1/00 |                                                         |
|            | -   ETMS data entry                                     |
|            |                                                         |
|            | 3.  Identification of Impacts by flight delays.         |
|            |                                                         |
|            | 4.  Common Display                                      |
|            |                                                         |
|            | -   NAS maps                                            |
|            |                                                         |
|            | -   WX maps                                             |
|            |                                                         |
|            | -   FCA Alerts                                          |
|            |                                                         |
|            | -   Constraints                                         |
|            |                                                         |
|            | -   SUA status                                          |
|            |                                                         |
|            | -   NAS status items                                    |
|            |                                                         |
|            | -   4D capabilities                                     |
|            |                                                         |
|            | -   Limited Resource Allocation.                        |
|            |                                                         |
|            | 5.  Limited Resource Allocation.                        |
|            |                                                         |
|            | -   Sector based GDP's                                  |
|            |                                                         |
|            | 6.  Route generation                                    |
|            |                                                         |
|            | -   ARTCC Playbook is required (procedure)              |
|            |                                                         |
|            | -   Approval/Denial must be much faster                 |
|            |                                                         |
|            | -   ATCSCC ability to validate route integrity.         |
|            |                                                         |
|            | 7.  POET to provide supporting analysis for C.R.        |
|            |                                                         |
|            | 8.  Filtering and alerting capabilities.                |
|            |                                                         |
|            | 9.  LAADR -- DOG Function                               |
|            |                                                         |
|            | -   Communication of exceptions                         |
+------------+---------------------------------------------------------+

+------------+---------------------------------------------------------+
| #####      | > (DOG) Diversions Off the Gate-- A way to convey to    |
| Near Term  | > the command center what flights are diverting to what |
| Discussion | > airport, and what flights are off the gate. Delivery  |
|            | > date 10/1/99. Chris - DOG will go to A & D subgroup.  |
|            | > Elliot wants it to go to C.R.                         |
|            | >                                                       |
|            | > Anthony -- MIT has to be loaded into ETMS. Ken -- we  |
|            | > can do it but individual information will not be      |
|            | > good. Information pertaining to the group should be   |
|            | > good..                                                |
|            | >                                                       |
|            | > Bill -- wants a tool that displays....                |
|            | >                                                       |
|            | > -- Red and Yellow areas, closed airways, ground       |
|            | > stops, sectors closed, FCA , ESP.                     |
|            | >                                                       |
|            | > Rick-(WSD)Web based situation display. Shows TSD      |
|            | > screen shots. Can show flights, alerts, and weather.  |
|            | > It's more than a week away. Ken -- instead of         |
|            | > developing the tools, lets decide some of the items   |
|            | > we want by May 1, 1999.                               |
|            | >                                                       |
|            | > MAP -- Monitor Alert Parameters                       |
|            | >                                                       |
|            | > Kevin -- If you have a thunderstorm and flights all   |
|            | > around, you want to display flights on this tool as   |
|            | > well. Bill -- system has to be realtime so when       |
|            | > Loraine zigs Bill sees it and can zag.                |
|            | >                                                       |
|            | > Discussion on when to file flights. Airlines want to  |
|            | > hold off filing so they can file on most current      |
|            | > SWAP.                                                 |
|            | >                                                       |
|            | > Mike- we want the ability to know if the host         |
|            | > computer will accept or reject a filed routing.       |
|            | > Suggestion to have the host computer respond to the   |
|            | > carrier whether there is integrity of the route or    |
|            | > not.                                                  |
|            | >                                                       |
|            | > Bill -- Can POET be used to develop the tools needed  |
|            | > near term.                                            |
|            | >                                                       |
|            | > Pass on to ATCSCC which flights cannot LAADR (DOG     |
|            | > type of tool).                                        |
|            |                                                         |
|            | -   incentive possible or desireable?                   |
+------------+---------------------------------------------------------+

+------------+---------------------------------------------------------+
| ##### Mis  | -   Russ wants airlines (by invitation only) to         |
| cellaneous |     > participate in Arrival/ Departure sub group       |
|            |     > meeting next week.                                |
|            |                                                         |
|            | -   CR workgroup in YYZ on 9/22?                        |
+------------+---------------------------------------------------------+

+------------+---------------------------------------------------------+
| ##### Ch   | > National Playbook -- Curt Kaler                       |
| airman for | >                                                       |
|  subgroups | > Short-Term Tool Development -- Bill Leber             |
|            | >                                                       |
|            | > Long-Term Planning -- Roger Beaty                     |
+------------+---------------------------------------------------------+

+------------+---------------------------------------------------------+
| ###        | > Rick O. gave a presentation on "A Proposed Tool for   |
| ## Rick Oi | > Managing Sector Congestion". Complete with handouts.  |
| sen's Tool |                                                         |
|            | 1.  Traffic Manager at center uses the standard         |
|            |     > capabilities of the TSD to detect a               |
|            |     > problem..Alert icons, Time lines, Bar charts,     |
|            |     > Lists.                                            |
|            |                                                         |
|            | 2.  Call up the Smooth Demand Dialog Box. (smooth the   |
|            |     > demand so it meets capacity).                     |
|            |                                                         |
|            | 3.  Select Exempt flights (Flights that are already     |
|            |     > controlled)                                       |
|            |                                                         |
|            | 4.  Initial Assignment of Delays (exempted flts "delay  |
|            |     > 0".                                               |
|            |                                                         |
|            | 5.  Evaluation of Delays.                               |
|            |                                                         |
|            | 6.  Confer with Command Center                          |
|            |                                                         |
|            | 7.  Issue the Delays (as EDCT's)                        |
|            |                                                         |
|            | 8.  Monitor the Traffic (are delays having the desired  |
|            |     > effect).                                          |
|            |                                                         |
|            | 9.  Revise Delays                                       |
|            |                                                         |
|            | > Issues                                                |
|            |                                                         |
|            | -   How can an airline substitute?                      |
|            |                                                         |
|            | -   How can an airline be aware of the planning process |
|            |                                                         |
|            | -   Is there anything analogous to ration-by-schedule   |
|            |                                                         |
|            | > If a flight is in a sector program, and if an airline |
|            | > reroutes it around the busy sector, the EDCT needs to |
|            | > be cancelled. Is any other incentive possible or      |
|            | > desirable? Everyone agreed this was worth looking     |
|            | > into and was listed under intem number 5 Limited      |
|            | > Resource Allocation.                                  |
+------------+---------------------------------------------------------+

+------------+---------------------------------------------------------+
| ##### Ac   | 1.  Long-term requirement to Leber 9/15                 |
| tion Items |                                                         |
|            | 2.  C. Pear letter to Jim Whetherly. By 9/1(Short term  |
|            |     > requirements May 1)                               |
|            |                                                         |
|            | 3.  C. Pear letter to J. Kies on clarifying ETMS access |
|            |     > to users by 9/15                                  |
|            |                                                         |
|            | 4.  C.R. Exploder -- Kevin Kollmann by 9/1.             |
|            |                                                         |
|            | 5.  Anthony Milligan - Investigate sending a letter to  |
|            |     > carriers asking them to express intent by a       |
|            |     > certain time frame. (file flight plans how long   |
|            |     > before departure).                                |
|            |                                                         |
|            | 6.  Short term meeting address issues on                |
|            |                                                         |
|            | -   CDR's/SID's                                         |
|            |                                                         |
|            | -   Regulatory Issues on SWAP routes.                   |
|            |                                                         |
|            | -   TMA Collaboration                                   |
|            |                                                         |
|            | 7.  Jim Wetherly to explore host option development     |
|            |     > plan by 9/22 CR meeting.                          |
|            |                                                         |
|            | 8.  Investigative trip to Breiteny                      |
|            |                                                         |
|            | -   Chris and Anthony                                   |
|            |                                                         |
|            | -   Report by 10/1/99                                   |
+------------+---------------------------------------------------------+