1. BOEING is a trademark of Boeing Management Company. Copyright © 2011 Boeing. All rights reserved. OMWG and All Working Groups DCIT-39 report out 11 March 2015 EOT_RT_Template.ppt | 8/1/2011 1

2. Engineering, Operations & Technology | Boeing Research & Technology Copyright © 2011 Boeing. All rights reserved. OMWG, 10 March 2015  Trials status updated and latest statistics as previously briefed  Minimum version of avionics (FMC, CMU, ATSU, …)  Presented current recommendations for avionics versions as understood by DCIT  Will be updated with some additional lessons from the DCL Trials, and brought forward to Plenary for approval  Once approved –Will be available for airlines and their regulatory authorities to utilize –Will be updated with new issues as they occur, throughout the Program’s life cycle  IOC criteria briefed; repeat of previous material

3. Engineering, Operations & Technology | Boeing Research & Technology Copyright © 2011 Boeing. All rights reserved. CPDLC DCL E2E Current Version  Draft V1.1, dated 3/02/ 2015  Description  Aligned with Data Comm Program requirements as of mid-Dec 2014 (WSSD 5.0)  Includes resolved comments from All WG telecon 1/14/15 and ERWG 3/4/15  Plenary Request – approve the additions for  Arrival Transition –Current IOC: Ground system will prevent an uplink if no there is no published Arrival T- fix in the route portion, terminate any session and go to voice –Future (Waterfall): First base leg point will be valid point for entering the arrival procedure, will be uplinked as NO Transition case  Airway-Airway –Current IOC: TDLS will prevent DCL uplink for airway-airway, display to controller, terminate session, go to voice. –Future (TBD): Coordinated solution with en route. Draft approach is to insert waypoints and lat/lon.  Next Steps  Work Cleared as Filed  Update/Replace Appendix E with DCP Enhancement Request tracking numbers  Address Error message uplinks to downlink messages

4. Engineering, Operations & Technology | Boeing Research & Technology Copyright © 2011 Boeing. All rights reserved. High Priority Future Capabilities: #Function/TopicDescriptionIOC/Salt Lake CityWaterfallNotes 2Cleared as Field Criteria Criteria for CAF if SID or SID/transition is applied that does not change anything prior to first filed fix. If route starting with first fix after SID transition has not changed and controller adds SID or SID/Tfix, then eligible for CAF. Flight deck stakeholders think this is a hazard. Remove this. Rules relaxed to allow CAF in cases where ERAM adds or changes the SID and/or T-fix, as long as route starting with the first fix after the T-fix has not been changed.TBD Ensure no ambiguity about how a SID and transition rejoin the route. See details High Critical IOC to prevent uplink if ANY change to SID/Tfix regardless of source. 4 Error Processing and Session Management Recover from some error without terminating session. If error and go to voice, then session is also terminated. TBDNeed to clarify conditions for when avionics and ground system are recoverable. High 11 Push DCLSend approved clearance as soon as session established on controller/system approval. Provide initial clearance as response to DM25 only TBDAt P-30, after system or controller approval, send initial CPDLC departure clearance if flight has logged on. Else queue for logon and send then. High, prior to waterfall? 18 Contact Uplink - Call Request Controller request for voice contact by pilot NoneTBDNeeds operational concept clarification. Would be separate message. High for controller?.

5. Engineering, Operations & Technology | Boeing Research & Technology Copyright © 2011 Boeing. All rights reserved. All WG, 10-11 March 2015 (En-Route “Full” Services)  Use Case team goes ‘pencils down’ on 1 May 2015  Service descriptions discussed at a top-level within multiple ERWGs  Key areas of work DCIT will focus on in updating the Routes End-to-End  Downlink requests  Tailored Arrivals  Use of “Hold” messages  Weather deviations, including follow up directions  Detailed work will be picked up after development assessments, later this year  Tailored Arrivals development work will continue now  Plenary Approval items  No “heading” messages will be included, uplink or downlink due to lack of operational utility  Understanding that only a limited number of crossing constraints will be sent –Current thinking, to be confirmed, is two message elements –More than this number will be handled via a route clearance if CPDLC is used

6. Engineering, Operations & Technology | Boeing Research & Technology Copyright © 2011 Boeing. All rights reserved. All WG, 10-11 March 2015  Non-VDL-2 sub-networks  Kevin Swiatek, leading PARC-CWG Project on this topic, briefed All WG on approach  PARC-CWG Project is targetted for completion in  All WG agreed with the PARC-CWG approach  Regular agenda item will be added to All WG meetings to track progress and provide DCIT input to the PARC-CWG Project as required  Andrew Onken will act as the DCIT interface to the PARC-CWG  Route Loadability Rules  Documented rules being worked by the AOC team with FAA facilities briefly reviewed (previously briefed)  Plenary Approval item –Add Route Loadability Rules as an Appendix to the Production DCL End-to-End routes  En-route Risk Mitigation  En-Route Trials briefed by Andria Roney  Additional risks and potential risk mitigations will be discussed at next DCIT, in light of the definition for the trials