Transcript Data Link Presentation

Richmond Facility
ATN 2003
IEE London
Raytheon Integrated Data Link–RIDL
[email protected]
[email protected]
July 28, 2003
Page 1
Overview
Richmond Facility
• This paper presents the results of RIDL, an
internal Raytheon research and development
initiative
• Objectives of Data Link Integration in ATM
system:
- Integration with ATM system user interface
» CPDLC (Controller-Pilot Data Link Communication)
» ADS-A(C) (Automatic Dependant Surveillance)
- Integration with FDPS of ATM system
» Operationally significant use cases
• Conclusions
July 28, 2003
Page 2
Integration Objectives
Richmond Facility
• Maximize benefits for the controller using Data Link:
- Reduce controller workload through automation of frequent
repetitive tasks
- Provide controller with a common (integrated) view of ATM system
and Data Link (CPDLC and ADS)
- Increase safety
• Achieve these objectives by:
- Eliminating the need for a controller to enter the same information
twice (in two different forms) to two different systems:
» ATM system (e.g new cleared altitude)
» Uplink MAINTAIN <Flight Level> at CPDLC terminal
- Leveraging off FDPS functionality:
» Check for conformance and conflicts, before uplinking
clearances
July 28, 2003
Page 3
Challenges
Richmond Facility
• Achieve the objectives while minimizing controller
workload
- Can a controller accept pilot’s altitude request with a single click?
- Why more than a single click should be required?
• Make Data Link functionality available even when the
FDPS is not available
July 28, 2003
Page 4
Data Link in an ATM System
Richmond Facility
Data Link
Gateway
FDP
Data Link
Network
CWP
ACID etc
.. data ..
.. block ..
CWP
FDP — Flight Data Processor
CWP — Controller Working Position
July 28, 2003
Page 5
CPDLC on the Situation Display
Richmond Facility
• Data Link Field–  arrow symbolizes pilot and
controller initiated dialogues
• Color of the arrows and the background indicates
the state of CPLDC connection and ongoing
dialogues (e.g., green arrows on gray background
indicate CPDLC is connected)
July 28, 2003
Page 6
Data Link Message Log (1)
Richmond Facility
• Displays chronologically all the message the controller
has exchanged with the flights
• Banner color indicates the state of Data Link gateway
(e.g., green color indicates Data Link gateway is
operational)
July 28, 2003
Page 7
Data Link Message Log (2)
Richmond Facility
• Clicking on a message:
- Emphasizes the flight in the situation display & electronic lists
- Emphasizes the messages belonging to the same dialogue
- Displays the list of common Data Link commands applicable for
the selected dialogue
July 28, 2003
Page 8
Data Link Dialogue Window
Richmond Facility
• Clicking on the Data Link Field brings up the Data Link Dialogue
window:
- Displays chronological list of all message the flight has exchanged with
the center (most recent message at the top)
- Interactions are the same as for Data Link Message Log (emphasis of
the dialogue, display list of common Data Link commands);
July 28, 2003
Page 9
Data Link Uplink Menu (1)
Richmond Facility
• Right click on Data Link
Field brings up the Uplink
menu
• Allows controller to traverse
CPDLC message tree
July 28, 2003
Page 10
Data Link Uplink Menu (2)
Richmond Facility
• For a selected message
system displays Data Link
Message window
July 28, 2003
Page 11
ADS-A on Situation Display
Richmond Facility
• ADS – reported
position
• Extrapolated position
based on ADS intention
• Display of ADS
intention (predicted
line)
July 28, 2003
Page 12
Data Link & FDP Integration
Operational Use Cases
Richmond Facility
• Changing communication frequency
• Transfer of control
- Within the FIR and with adjacent FIR
• Altitude clearances
- Controller – initiated and pilot request
•
•
•
•
•
Speed and route clearance
Monitoring operational dialogues
Broadcast check stuck microphone
Pre-departure clearances
ADS contract management
- Manual & automated
July 28, 2003
Page 13
Frequency Change (1)
Richmond Facility
• Controller changes aircraft frequency, e.g.
- Clicking on the Frequency Field brings up the Frequency Pop–up
- Controller selects the new frequency
July 28, 2003
Page 14
Frequency Change (2)
Richmond Facility
• System accepts the update and automatically uplinks the
appropriate (MONITOR) CPDLC message
• System can also be tuned to require controller confirmation
before uplinking
July 28, 2003
Page 15
Transfer of Control within FIR
Richmond Facility
• Controller
initiates and
completes
transfer
• System
automatically
uplinks
CONTACT
CPDLC message
• CPDLC
messages
CONTACT/WILCO
displayed to
transferring and
receiving
controller
July 28, 2003
Page 16
Transfer to Downstream FIR
Richmond Facility
• Controller initiates and completes transfer
• System automatically uplinks CONTACT & END OF SERVICE
CPDLC messages
• System has previously automatically uplinked NEXT DATA
AUTHORITY, adapted time before boundary crossing
• Providing that downstream ACC is Data Link capable (adaptable)
July 28, 2003
Page 17
Altitude Clearance (1)
Richmond Facility
• Controller issues altitude clearance using e.g. Altitude
Slider or by selecting ACCEPT (single click)
• FDPS database is updated
• System automatically uplinks MAINTAIN <Altitude>
CPDLC message
July 28, 2003
Page 18
Altitude Clearance (2)
Richmond Facility
• Selecting a message emphasizes all messages
belonging to the same operational dialogue
• Support for multiple concurrent dialogues
July 28, 2003
Page 19
Automatic Conflict Probing
Richmond Facility
• Before accepting the altitude clearance, the system
automatically checks for conflicts
• If there is a conflict, the system displays a conflict warning
popup
• Controller can visualize the conflict on the situation display
July 28, 2003
Page 20
Speed and Route Clearance
Richmond Facility
• Controller issues speed or route clearance, e.g., Speed
Slider
- System updates the FDP database
- Automatically uplinks MAINTAIN <Speed> CPDLC message
July 28, 2003
Page 21
Monitoring Operational Dialogue
Richmond Facility
• If pilot (or controller) does not respond within predefined time,
the system times out the dialogue
July 28, 2003
Page 22
Check Stuck Mike
Richmond Facility
• Selecting a frequency from the Stuck Mike Slider, controller
uplinks the CHECK STUCK MIKE <on frequency> CPLDC
message to all flights on the selected frequency, under the
controller’s jurisdiction
July 28, 2003
Page 23
ADS-A Contract Management
Richmond Facility
• Manual management
- Demand Contract
- Periodic Contract
- Event Contract
July 28, 2003
Page 24
Advanced ADS-A Contracts
Richmond Facility
• System automatically establishes (and modifies)
default periodic contract with the flight, depending on
RNAV properties of the airspace
• System submits ADS position reports for
conformance monitoring
• System updates the FDPS database with emergency
indication upon receipt of an ADS emergency report
July 28, 2003
Page 25
Conclusions
Richmond Facility
• Internal research & development activity produced a
production quality prototype, RIDL which integrates
data link and FDPS functionality achieving the intended
objectives:
- Reduce controller workload
- Increase safety
• Selection of integrated operational scenarios based on
Oceanic experiences and en – route operational trails
(PETAL and BUILD 1/A)
• Future Integration Opportunities:
- Automatic Uplink of Altimeter Setting
- CPDLC – Assisted Radar Identification
- Processing of meteorological information from ADS reports
July 28, 2003
Page 26