EUROCAE WG-78 / RTCA SC-214 Configuration Sub-Group Bethesda (US) , 15th– 19th Nov. 2010

1. EUROCAE WG-78 / RTCA SC-214 Configuration Sub-Group Bethesda (US), 15th– 19th Nov. 2010 CSG Progress Report Jane HAMELINK , (THANE) RTCA CSG Co-Chair Thierry LELIEVRE, (ALTRAN) EUROCAE CSG Co-Chair

2. CSG AchievementOverview • Resolution of INTEROP PDRs • FANS Accommodation See Chris presentation • PDR Resolution • Use free text for Clearances not supported • Operational Validation of accommodation rulesisrequired (not yetaddressed by VSG) • LINK2000+ Backward Compatibility • PDR Resolution • Review of Version Number exchanges in Logon

3. CSG AchievementOverview • Resolution of INTEROP/SPR PDRs • Use of UM143 CONFIRM REQUEST • What to reply : • if no request ? • if requestconcatenatedwith a report? • ResponseAttributeischangedfrom « Y » to « N » • Issue : • Whatrequestisreferring to when multiple requests are open ? • To Confirm the operational use/need for this message • D-TAXI Graphic • Size of the bitstringislimited to 1024 bits

4. CSG AchievementOverview • Resolution of INTEROP/SPR PDRs • CPDLC / Use of UM340 LATENCY VALUE [latency value] • The check of the latency on board is required only if UM340 has been received. If not received, a default value (999) is used for the latency check • CPDLC Message received before receiving the UM340 will not be rejected. The Error related to the receipt of UM before the receipt of UM340 is removed • LACK shall be required for UM340 • Some ATSU System may prohibit from sending any CPDLC message until LACK is received • Some ATSU may terminate the CPLDC connection if no LACK is received in due time (tr)

5. CSG AchievementOverview • Resolution of INTEROP/SPR PDRs • ADS-C / Clarification on Initial/Required Response Time • Reference to Initial/Requires Resp. time is removed from the OSD • To rely on the OPA that defines the RCTP for the Airborne component • Additional Safety & Performance assessment is needed for additional ADS-C Capabilities • Use of Facility designation parameter (in the context of SDA Concept) • Facility designation remains mandatory • Facility designation is used to designate the current Controlling ATSU (that could be different from the CDA (e.g. KUSA (CPDLC Server) and KZMA (Miami)) • No change in the SPR

6. PDR Mangement issue • Each PDR must convey the information about « Impact on Interoperability » and « Part of the version H Validation Baseline » • Need to identify the PDRs that impact the interoperability • Not a local implementation choice to support the PDR or not • Need to define a minimum PDR Baseline for vH validation • Identify the minimum set of PDRs that have to be implemented, no matter what • Other PDRs will be validated later

7. Tomorrow CSG Session Work program • To clarify on the use of EPP Tolerance Event Types / EPP Tolerance Event Default Values • Need to challenge 3 possibilities with 4DTRAD Ops People and Avionic manufacturers : • 1) The 5 EPP Tolerance Event types are always monitored. The ground may specify specific value for each of the 5 tolerances. When not specified by the ground, then the default values apply. • 2) The 5 EPP Tolerance Event types are not always monitored. The ground shall select which ones have to be monitored by the aircraft system. The ground may specify specific tolerance value for the tolerance event type it has selected. When the EPP Tolerance Event Type is selected but no specific tolerance value is fixed by the ground, then the Default Value applies.  • 3) The 5 EPP Tolerance Event types are not always monitored. The ground shall select which ones have to be monitored by the aircraft system and shall specify specific tolerance value for the tolerance event type it has selected. (consequence => No need to specify Default value!). • To review of Seamless Transition Position Paper • To address the FANS/ATN Dual Stack issues 7

8. Next Steps • To support the next SPR/INTEROP release (End of 2011) : • Focus on ACM, ACL, AMC, DCL, D-TAXI, D-OTIS and FLIPINT (including Epp) : • => Integration of OCR - OSA/OPA Results • Lead : Wim/Kathy • CSG requires an Plenary Agreement on the approach (see Bellevue MoMs): • => Harmonisation of Environment Figures/ATS Figures Defintion • Lead : Tom • => To Consolidate D-OTIS/ACM/ACL/AMC/DCL/D-TAXI OSDs & COPDLC/ADS-C/FIS Applications and FANS Accommodation (thru • SPR Lead : Jane/Thierry • INTEROP Lead : Fred/Chris • => To develop FLIPINT OSD and Additional ADS-C OSA/OPA • OSD Lead : Jane/Thierry • OSA/OPA Lead : Wim/Kathy • => To remove ADS-C from ATN INTEROP • Lead : Fred 8

9. Next Steps • To support the next SPR/INTEROP release (End of 2011) • => To assess the CPDLC Message Set (including Alert/urgent attributes) • Lead : Jane /Thierry • Initial Step : To figure out the Criteria used to remove/to keep a CPDLC message as part of the CPDLC Message Set. • Needs Inputs : VOLPE ‘s representatives contribution, OPLINK, JPDO, LINK2000+, ..? • => To assess Operational requirements vs Service/Application requirements • Lead : Wim/Tom • Initial Step : To figure out the what is an Operational Requirement (ref. Annex10/Vol2Ch8) • => To revise the Perfomance-based Framework – RCP • Lead : Wim/Kathy • Initial Step : FAA-AVS to provide guidance on specification of technical performance criteria 9

10. CSG Meetings & Webex(untill P12) • FAA Tech Center, ATLANTIC City, 10th – 14th January 2011 • To review of FLIPINT OSD • To progress on ADS-C OSA/OPA • To progress on Environment / ATS Functions Harmonisation • To figure out the CPDLC Message Assessmentcriteria • To beapproved? CSG Meeting, Location, 14th-19th February2011 • To assessCPDLC Message Set • To reviewthe Environment Harmonisation / ATS FunctionsDefinition • To reviewthe ADS-C OSA/OPA • Plenary #12, Berlin (Germany), April 2011 • CSG Webew – EachWednesday – Resolution of Comments / PDRs • DedicatedWebex : • Assessment of CPDLC Message Set • Environment / ATS FunctionsHarmonisation • OperationalRequirementassessment • Refinement of Performance basedframework - RCP • ADS-C OSA/OPA

11. Thankyou for your contribution to CSG 11