Status of Collaborative Routing and NAS Status Work at Volpe

1
Status of Collaborative Routing and NAS Status
Work at Volpe

• Rick Oiesen
• 28 June 2000

2
Diversion Recovery Page

• This page shows the flights that are currently
  considered to be diversion recovery flights.
• This page is currently on the DataGate so it can
  be evaluated by the FAA and airlines.
• This page will when ready be moved to the ATCSCC
  web page so that everyone can see it.
• Features
• Diversion recovery flights currently identified
  in two ways.
• DVRSN in field 11.
• Automatic algorithm in ETMS.
• User can enter comments and a priority.
• User can sort on any of the seven fields and
  print.

3
(No Transcript)
4
(No Transcript)
5
(No Transcript)
6
(No Transcript)
7
(No Transcript)
8
Issues

• Why is it so frequently the case that a flight is
  flagged as a diversion recovery by the ETMS
  diversion detection algorithm but DVRSN is not in
  field 11?
• Should flights only be fed to this page if they
  have DVRSN in field 11? That is, should the
  diversion detection algorithm be turned off?

9
Partial List of Planned Enhancements

• A command that allows a user to add a flight.
• Passwording to be required of anyone who wants to
  add a flight or enter a comment.
• Time stamping of comments and TCA
  acknowledgements.
• Fields to be re-ordered to match the order in an
  ETMS list request (ACID, TYPE, ORIG, ETD, DEST,
  ETA, ACENTR) and the DCENTR field to be dropped.
• Should ETE be added?
• What should be added or changed?

10
Integrated Terminal Weather System

• The operational ITWS is to be deployed starting
  in 2001.
• Volpe will be providing a feed of the digital
  ITWS data to air carriers.
• Lincoln Labs will write software that will allow
  ITWS images to be displayed on a web site. Volpe
  will host this web site.
• The prototype ITWS and TCWF displays will remain
  on the CDM DataGate as long as they are
  available. They will be turned off when ITWS
  goes operational.
• TCWF is not currently planned to be in the
  operational ITWS that is deployed.
• It is time for carriers to discuss what they want
  on the web site.

11
Planned Work on Flow-Constrained Areas

• Phase 1(November 2000, ready for testing)
  Capabilities for the TSD User
• FAA user can define an FCA
• Area (shown by clicking)
• Upper and lower altitude
• Direction of movement
• Speed of movement
• Start and end time.
• FAA user can see what flights intersect an FCA.
• Phase 2 (November 2000) Airline user can see
  what flights intersect an FCA defined by the FAA

12
Feed of CTAS Data from DFW

• NASA is providing a feed of CTAS data from DFW.
  This feed will include
• Projected runway.
• Estimated touchdown time.
• Status
• System requirements document and interface
  control document are available to the airlines.
• Software by Volpe and NASA is written and is
  partially tested.
• The pacing item is that system testing cannot
  start until CTAS 5.5.3 is fielded this will
  happen at the earliest in August.
• After testing is completed, the feed will be
  turned on.
• An air carrier needs to sign a MOA with the FAA
  to get the data.
• Carriers need to make sure that they have the
  needed bandwidth.

13
Daily Download

• No recent activity.
• Work needs to get started again.

14
SMA/ARTS Data

• Current TRACONs from which twenty-second position
  updates are available.
• Philadelphia
• Detroit
• Dallas
• Chicago
• New York
• Minneapolis (new in May)
• St. Louis (new in May)
• Atlanta (new in May)
• 30 June 2000 SMA/ARTS data to be provided in the
  TZ format used in the ASDI feed for Dallas,
  Chicago, and New York.

15
Do You Have Enough Bandwidth?

• Changes in the pipeline that require bandwidth.
• One-minute TZs in the ASDI feed. (Late2000-early
  2001??)
• RVR (2001).
• CTAS from DFW (2000).
• ITWS (2001-2002).
• Common Constraint Situation Display (2000).
• Consult with your vendor to determine if you have
  enough bandwidth.

16
RVR

• 8 June 2000 Telcon held with twelve airlines on
  RVR.
• 14 June 2000 Revised versions of the RVR System
  Requirements Document and Interface Control
  document distributed to airlines.
• January 2001 RVR data available from BOS and
  MEM.
• Spring 2001 RVR data available from roughly 45
  airports.
• The RVR data will be available to the airlines in
  two forms.
• A digital stream of data.
• Tables and graphs on the DataGate.

17
Simplified RVR Data Flow
                                                 
               
 
To Controllers
ETMS Fileserver at TRACON   RVR TRACON Server  
RVR Sensor Data
DPU at Airport
ADUs
Volpe
Browsable Data
CDM DataGate
Web browser at FAA or Air Carrier
RVR Collector
Digital Data
RVR Hubsite Server
Client at FAA or Air Carrier
18
Revisions to the Digital Feed

• The feed will be available on three ports with
  three different update rates
• 60 seconds.
• 10(?) seconds.
• 2 seconds.
• On the port with an update rate of two seconds, a
  client will have the option of getting
• All data.
• Data only when there is a change.
• There should be an easy way for a client to
  indicate that it wants the RVR data from all
  airports.
• All of the revisions were made to the baseline
  documents.

19
User Interface Constraints for the Web Site

• Airlines should be able to display a table of
  current RVR data for an airport and/or graphs of
  RVR data for the last hour at selected runways.
• Airlines should be able to display any mix of
  tables and graphs without wasting screen space or
  bandwidth.
• Display must allow for different size monitors
  being used at a variety of resolutions. This
  means that the user should be able to control the
  amount of screen that is devoted to, e.g., the
  table of RVR data for an airport.
• The web environment has limitations.
• Use of bandwidth should be minimized.

20
Sequence of RVR Screens

• When a user clicks on the RVR link for the first
  time in a session, a series of screens appears.
• Disclaimer What you can use the data for. The
  data provided on this screen shall only be used
  for flight planning purposes. The RVR data
  obtained form ATC is the official RVR.
• Instructions How to interpret the data.
• RVR Options These control what the main RVR
  screen looks like and how it behaves.
• Main RVR Screen This displays the requested RVR
  data.

21
RVR Options
Table Update Rate
10 seconds
2 seconds
60 seconds
Screen Layout
OK
22
RVR Page
Instructions
Options
Mid-point
Rollout
Touchdown
Table
Table
Table
Graphs
Graphs
Graphs
Table
Graphs
Table
Table
Graphs
Graphs
Table
Table
Table
Graphs
Graphs
Graphs
23
Table Button
If the TABLE button in a cell is clicked, a box
something line the following pops up.
Show RVR Table
Click an airport in this list to cause it to be
displayed in the cell in which the TABLE button
was clicked.
None AAA BOS CCC DDD EEE FFF GGG HHH
III JJJ KKK LLL XXX YYY ZZZ
Cancel
24
RVR Page
Instructions
Options
Mid-point
Rollout
Touchdown
BOS
Table
Table
Table
Graphs
Graphs
Graphs
6/20/2000 1120Z
R/W TD MP RO E
C
04R 35 35 35 5
5
15R 30 20 5
5
22L 35 35 35 5
5
33L 20 30 5
5
Table
Graphs
Table
Table
Graphs
Graphs
Table
Table
Table
Graphs
Graphs
Graphs
25
Graph Button, Page 1
If the GRAPH button is clicked, it causes a box
to pop up that contains airport IDs much like
the box on the previous slide.
Show Graphs For
None AAA BOS CCC DDD EEE FFF GGG HHH
III JJJ KKK LLL XXX YYY ZZZ
If the user clicks an airport for which he or she
wants to see one or more graphs, the box on the
next page pops up.
Cancel
26
Graph Button, Page 2
BOS Show Graphs for
Check the runways for which graphs are to be
shown and then click OK. The selected graphs
will be shown in the cell in which the GRAPH
button was clicked.
04R
15R
22L
33L
Cancel
OK
27
RVR Page
Instructions
Options
Mid-point
Rollout
Touchdown
BOS
Table
Table
Table
Graphs
Graphs
Graphs
6/20/2000 1120Z
R/W TD MP RO E
C
04R 35 35 35 5
5
15R 30 20 5
5
22L 35 35 35 5
5
33L 20 30 5
5
BOS
Table
Graphs
Table
Table
Graphs
Graphs
Runway 04R 6/20/2000 1120Z
4000
3500
3000
1020 1040 1100 1120
Table
Table
Table
Graphs
Graphs
Graphs
28
Notes

• The user can distribute tables and graphs among
  the cells in any way. However, a particular cell
  holds
• One table showing RVR data for an airport or
• Any number of graphs for a particular airport.
• The cells will be vertically resizable but not
  horizontally resizable. To resize a cell, drag
  its boundary.
• If more data is requested than will fit in a
  cell, only part will be displayed, and a scroll
  bar will be shown. If the user wants to see all
  the data, then the size of the cell should be
  resized.
• Tables do not take much bandwidth, but graphs do.

29
Issues

• How often should a table update? Suggestion
  Once every five minutes.
• Should there be a Toggle Screen Layout button
  on the main RVR page to get rid of the items at
  the top of the page, i.e., the title, buttons,
  and color-coding? That is, should one be able to
  toggle between pages with and without the items
  at the top?
• Should the restriction be imposed that only one
  graph can go in each cell? Suggestion No.
• What colors should represent touchdown,
  mid-point, and rollout?
• How should a table update if no data is currently
  available? Suggestion Show a blank for the
  interval where no data is available, but continue
  to show the valid data from the last hour.