RAT Reader Prototype

1
RAT Reader Prototype

• Ken Howard
• Arcon
• 1/28/03

2
CCSD RAT Reader

• Review ideas for the first pass of integrating
  the RAT Reader into CCSD.
• General approach
• Utilize existing functions.
• Simplify.
• Get a limited prototype working, then modify it
  from user feedback.
• NOTE Some features of RAT Reader may be useful
  to FAA as future enhancements to TSD.

3
Select Reroutes Window

• Current
• Shows summary data for all current reroutes.
• Allows user to display reroutes on the map.
• Provides buttons for Info (advisory) and List
  (flights).
• Enhancements
• Add advisory number and impacted areas.
• Add total flight count.
• Add Details button.

4
(No Transcript)
5
Details Window

• New function, patterned somewhat off of Create
  FCA.
• For each city-pair that has flights, left panel
  will show
• origin airport
• destination airport
• origin center
• destination center
• number of flights
• assigned routes
• User can sort on any column.
• User can draw routes for any city-pairs on the
  map.
• User can request flight list for any city-pair.

6
(No Transcript)
7
Flight List

• Based on FCA Flight List available on test CCSD.
• Current
• Can sort on any column.
• Can select individual flights, then submit early
  intent.
• Auto-updates every minute.
• Highlights flights that have been submitted.
• Enhancements
• Add all flight data fields from RAT list (sort on
  any).
• Show assigned routes.
• Add Save, Print.
• Take out the auto-update.
• Add Respond button.

8
(No Transcript)
9
(No Transcript)
10
(No Transcript)
11
Respond

• Based on early intent function.
• Current
• Can manually enter route or copy and edit current
  route.
• Can submit to ETMS as early intent.
• Enhancements
• Make split window with map display.
• Show all flight data with assigned routes.
• Allow user to draw current route, assigned
  routes, and/or manually entered route.
• For responder, allow user to accept assigned
  route, submit alternate, request as filed, etc.

12
(No Transcript)
13
Issues

• What are the possible user feedback/requests
  e.g. leave-as-filed, accept assigned reroute,
  propose alternate, etc?
• Do any of the concepts of the FCA monitor apply
  to reroutes?
• Instead of watching for pop-ups and
  drop-outs, watch for who has responded and how.