2. Page 1 July 28, 2003 Richmond Facility ATN 2003 IEE London Raytheon Integrated Data Link–RIDL Slobodan_Jovanovic@Raytheon.com Drasko_Sotirovski@Raytheon.com

3. Page 2 July 28, 2003 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 Overview

4. Page 3 July 28, 2003 Richmond Facility Integration Objectives 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 at CPDLC terminal -Leveraging off FDPS functionality: »Check for conformance and conflicts, before uplinking clearances

5. Page 4 July 28, 2003 Richmond Facility Challenges 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

6. Page 5 July 28, 2003 Richmond Facility Data Link in an ATM System

7. Page 6 July 28, 2003 Richmond Facility CPDLC on the Situation Display 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)

8. Page 7 July 28, 2003 Richmond Facility Data Link Message Log (1) 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)

9. Page 8 July 28, 2003 Richmond Facility Data Link Message Log (2) 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

10. Page 9 July 28, 2003 Richmond Facility Data Link Dialogue Window 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);

11. Page 10 July 28, 2003 Richmond Facility Data Link Uplink Menu (1) Right click on Data Link Field brings up the Uplink menu Allows controller to traverse CPDLC message tree

12. Page 11 July 28, 2003 Richmond Facility Data Link Uplink Menu (2) For a selected message system displays Data Link Message window

13. Page 12 July 28, 2003 Richmond Facility ADS-A on Situation Display ADS – reported position Extrapolated position based on ADS intention Display of ADS intention (predicted line)

14. Page 13 July 28, 2003 Richmond Facility Data Link & FDP Integration Operational Use Cases 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

15. Page 14 July 28, 2003 Richmond Facility Frequency Change (1) Controller changes aircraft frequency, e.g. -Clicking on the Frequency Field brings up the Frequency Pop–up -Controller selects the new frequency

16. Page 15 July 28, 2003 Richmond Facility Frequency Change (2) System accepts the update and automatically uplinks the appropriate (MONITOR) CPDLC message System can also be tuned to require controller confirmation before uplinking

17. Page 16 July 28, 2003 Richmond Facility Transfer of Control within FIR Controller initiates and completes transfer System automatically uplinks CONTACT CPDLC message CPDLC messages CONTACT/WILCO displayed to transferring and receiving controller

18. Page 17 July 28, 2003 Richmond Facility Transfer to Downstream FIR 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)

19. Page 18 July 28, 2003 Richmond Facility Altitude Clearance (1) Controller issues altitude clearance using e.g. Altitude Slider or by selecting ACCEPT (single click) FDPS database is updated System automatically uplinks MAINTAIN CPDLC message

20. Page 19 July 28, 2003 Richmond Facility Altitude Clearance (2) Selecting a message emphasizes all messages belonging to the same operational dialogue Support for multiple concurrent dialogues

21. Page 20 July 28, 2003 Richmond Facility Automatic Conflict Probing 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

22. Page 21 July 28, 2003 Richmond Facility Speed and Route Clearance Controller issues speed or route clearance, e.g., Speed Slider -System updates the FDP database -Automatically uplinks MAINTAIN CPDLC message

23. Page 22 July 28, 2003 Richmond Facility Monitoring Operational Dialogue If pilot (or controller) does not respond within predefined time, the system times out the dialogue

24. Page 23 July 28, 2003 Richmond Facility Check Stuck Mike Selecting a frequency from the Stuck Mike Slider, controller uplinks the CHECK STUCK MIKE CPLDC message to all flights on the selected frequency, under the controller’s jurisdiction

25. Page 24 July 28, 2003 Richmond Facility ADS-A Contract Management Manual management -Demand Contract -Periodic Contract -Event Contract

26. Page 25 July 28, 2003 Richmond Facility Advanced ADS-A Contracts 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

27. Page 26 July 28, 2003 Richmond Facility Conclusions 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