1 / 15

EUROCAE WG-78 / RTCA SC-214 Configuration Sub-Group Meeting Long Beach, CA, US 22-26 October 2012

EUROCAE WG-78 / RTCA SC-214 Configuration Sub-Group Meeting Long Beach, CA, US 22-26 October 2012. CSG Progress Report Meeting Objectives Work Organisation. Jane HAMELINK , (THANE) RTCA CSG Co-Chair Thierry LELIEVRE , (ALTRAN) EUROCAE CSG Co-Chair.

kirk
Télécharger la présentation

EUROCAE WG-78 / RTCA SC-214 Configuration Sub-Group Meeting Long Beach, CA, US 22-26 October 2012

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. EUROCAE WG-78 / RTCA SC-214 Configuration Sub-Group Meeting Long Beach, CA, US 22-26 October 2012 CSG Progress Report Meeting Objectives Work Organisation Jane HAMELINK , (THANE) RTCA CSG Co-Chair Thierry LELIEVRE, (ALTRAN) EUROCAE CSG Co-Chair

  2. Main Achievementssince last SG Meeting (Iceland, September 2012) • SPR/INTEROP Status: • PU-10 SPR, PU-20 INTEROP and PU-30 FANS-ATN available on the FAA Website since end of June 2012 • Consolidation of ATS Function section, Annex M, rules for Route Loading and CPLDC OR6, OR5 and OR4 • Consolidation of CPLDC Message Set (in coordination with OPLINK, SESAR D-TAXI) • Consolidation of Baseline 1 BACKWARD COMPATIBILITY • Revision of section SPR 5.3 (Safety and Performance) – New table and approach for presenting SR/PR • Coordination with SC227/WG85 is initiated by Jarrett (on PBN Concept) • Update of D-RVR OSA • Change 1 to ED110B/DO280B: • Update of Position Paper Change 1 to ED110B/DO280B on 18 Sept 2012 • Change Request has been triggered to EUROCAE and RTCA • Coordination with OPLINK: • OPLINK#5 in September 2012 (See OPLINK Feedback by VSG co-chair) • Update of CPLDC Message Set with a list of open issues/areas: • Consolidation of D-TAXI and FIM Messages • Proposal to accommodate Dynamic Performance Based Navigation (PBN) Routing Operations • Alignment of Position Report content between CPDLC, ADS-C and PANS-ATM • 252 UM / 114DM (See CPDLC Message Set Satus)

  3. CPDLC Message Set Status • New CPDLC Message Set submitted to OPLINK and consistent withcurrent SPR/INTEROP Version J (October 2012) • High Level changes (since last version): • Changes vetted with Oceanic Centers, airframe manufacturers, OPLINKP and WG-78/RTCA SC-214. • To reduce the chances of pilots missing the condition  “AT [time]”, it was proposed to add the word “TIME” (e.g., “AT TIME [time]” will replace “AT [time]”). • To clarify the meaning of “BY” these messages were revised to define the condition as “BEFORE PASSING” (e.g., “CLIMB TO [altitude] BEFORE PASSING [position] will replace “CLIMB TO [altitude] BY [position]”). • Open issues : • New Messages to Support PBN Concept of Operations • Consolidation of D-TAXI and FIM Messages (Validation isongoing)

  4. Status of OPLINK Comment Resolution • SeeOPLINKP_CPDLC_Comments_5_October_2012.docfor details • 221 Comments have been received and assessed on OPLINK CPDLC Message Set • 216 Comments have been resolved and, when required, resolution is taken into account in the current SPR/INTEROP version J and associated PDRs have been created. • 5 comments remain open and are linked to open issues/areas that require CSG Assessment or OPLINK Feedback, notably: • Consolidation of D-TAXI Messages • Accommodation of Dynamic PBN Routing

  5. SPR/INTEROP Comments/PDRsStatusOverview(on version I) • 388 PDRs (5 new PDRs since Iceland) • 5 PDRs remains open (4 Working + 1 Proposed Fix):

  6. PDRsStatusOverview (on version I) • 1 PDR is “PROPOSED FIXED”: • 385 [SPR/INTEROP] Modifications of D-TAXI parameters Action EUROCONTROL: Povide operational use cases for Assigned Time Types:ELDT (Estimated LanDing Time) and CSTT (Calculated Spot Taxi Time). Use of ELDT & CSTT is confirmed by EUROCONTROL for CDM 5 PDRs are “WORKING”: • 312 [INTEROP] Ambiguous specification of the ATN default checksum algorithm • 345 [SPR/INTEROP][CPDLC] Addition of New/Reinstated CPLDC Messages • 347 [SPR/INTEROP][CPDLC] Deletion of CPLDC Messages • 396 [INTEROP] [CPDLC] LACK timer (tr) values Action AIRBUS: Determine solution for accommodating multiple values for tr (LACK Timer). • 397 [INTEROP] [CPDLC] Incorrect accommodation rule for UM46R with a level Block

  7. SPR/INTEROP Comments/PDRsStatusOverview(on version I) • 27Comments on SPR/INTEROP received from AIRBUS (October, 12) • xxxxx comments are still WORKING/OPEN and will require CSG assessment • 3 comments have an impact on CPLDC Message Set • 1 comment from MITRE about use of Conditions in ADS-C Tables: • Clarify use of Conditions for some of ADS-C Parameters: • C1: Mandatory when at least one EPP event is requested with the exception of the RTA missed event type • C1: M when in emergency/urgency, else X • C2: Mandatory when requested and when available, else X • C2: Mandatory when requested and when available, else X • C3: At least 1 must be provided

  8. Main Issues/Actions • Recommendations for CPDLC Message Alerting/Accessibility • In Iceland we agreed to a recommendation and requirement for Aircraft • Action FAA (Tracy and Kim) to propose groundrequirements/recommendations for downlink messages accessibility and alerting • a position paperwasalsodiscussedat OPLINKP. Review of the paperdeterminedthatfurther discussion wasneeded to refinethis guidance beforeincorporatingitinto the relevant (ICAO) document. • Impacts on the SPR to beassessed • Criteria and Rules for Autoloading (Annex M and SPR Section 2) • To consolidate the criteria for requiringautoloading in order to be consistent withAnnex M and CPDLC J OR-4 (seeTextproposalfrom Honeywell/FAA Cert) • To reviewtextproposal (including new requirments) from Boeing to make UM76R AT [time] PROCEED DIRECT TO [position] and UM78R AT [level] PROCEED DIRECT TO [positionR] loadable. • Use of Speed Schedule and RTA/CTO to meet a time constraint: • Action FAA (Jane Hamelink): To modify the SPR 4DTRAD OSD to removeany concurrent use of speed schedule and RTA/CTO. • Discussed during a CSG Webex and some members do not concur with this statement and do not want to constrain use of RTA/CTO and Speed Schedule. • Need to revisit this issue during the meeting to determine what constraints, if any, will be put in the 4DTRAD OSD.

  9. Main Issues/Actions • Dynamic setting of “tr” (LACK Timer) by the Aircraft System • AIRBUS confirmed the need for the LACK Timer for the AIRBUS aircraft • Action AIRBUS: Determine solution for accommodating multiple values for tr (LACK Timer). • To assess the best solution to provide the aircraft with the “tr” value: • To set up the tr value according to the Latency value (does it cover all the cases?) • To provide the tr value within UM340 LATENCY TIME VALUE • . • Rules for Baseline 1 Backward Compatibility • Action P15-5:  CSG to investigate the feasibility of moving existing ATN B1 backwards compatibility into a mixed interoperability document to include all requirements for aircraft and ground systems • the part 3 is written is such a way it is easy/feasible to move it completely into a separate document . Should it be a normative annex to INTEROP,  a new ED-xxx / DO-xxx document (60 pages) or be integrated of the Mixed INTEROP document (FANS acc.). • Some parts of part3 can be moved to part 1 • Action Plenary#16 to decide • To review rules for B1 Backward Compatibility (See Excel Sheet developed by Frederic) • Rules for accommodating REPORT REQUEST from the ground when the datalink REPORT is not supported by the B1 A/C: • The ground sends a REPORT REQUEST • The Pilot responds by WILCO and the dialogue is “technically” closed • When conditions are met, the flight crew will provide the REPORT using voice • Is acceptable to initiate a dialogue via Datalink and to provide the requested “Data” via Voice?

  10. Position Papers • Issues with Safety assessment (OSA) for CPDLC prepared by EASA • Notably for Human Factor Rate and Approach for the Safety Assessment. • Resolution and agreement of these issues is critical in order to consider the SPR as an acceptable means of compliance: - for the future approval of CPDLC beyond the actual use (cruise flight phase over upper airspace), and - the consideration of this standard within the European SESAR packages, without any further need of additional requirements to be developed by EASA. • ADS-C EPP White Paperprepared by AIRBUS/BOEING • Assessment of the level of complexity in the EPP and EPP change event reporting • Proposal for Simplification Comments received from GE Aviation and Thales(?) • Resolving interoperability issues for SATCOM Frequency Channelprepared by AIRBUS • Due to divergent implementations among aircraft types, the use of CPDLC to send satellite voice telephone numbers in MONITOR and CONTACT messages cannot be uniformly implemented and seamlessly used around the world • This may become a strong limitation with the ongoing deployment of Satcom voice for ATS communications • Paper proposes resolution by introducing a new definition for this parameter so that Global Technical and Operational Interoperability is ensured • Proposal to use in the WG78/SC214 Performance Specifications, the allocated timing values, corresponding to the 99% Probability target rather than the 99.9% Probability target prepared by EUROCONTROL • This POS Paper had been presented at the Plenary 15 meeting, (June, MUAC) for which it was proposed to discuss this within OPLINKP (Sep 12 meeting) => Not discussed • The purpose of this document is to propose the specification of the 99% TIME values for the allocations, except TRN, rather than the 99.9% TIME values within the performance specifications

  11. Main Tasks for this CSG Session • To address the open Issues/Actions (and review related Inputs/position papers if any) • To address Position Papers • To address open Actions fromIcelandic CSG Meeting: • Action CSG editors (cmt#12) Include a requirement to avoidhaving an EXPECT and a taxi clearance in the same message and to avoid 2 taxi route clearances in the same message. • Not consistent with the D-TAXI OSD! • (From VSG) Action CSG: Addresswhether the limit of 5 message elementsneed to beincluded in OR-2. => Is thisLimitstillrequired in B2 environments? • To address AIRBUS and MITRE Comments

  12. CSG SESSION organisation Need for Security Ad-Hoc meeting?

  13. Remark ? Comment ? 13

  14. 271 UM --------------------- PANS ATM Messages 40 « Replaced » 12 «  Not required » 18 Reserved • 252 UM • --------------------- • 88 New Messages • PANS ATM Messages • 89 « Required » • 78 « Replaced » • by 75 « Replacement » • « Not required » • 19 Reserved 227 UM --------------------- 245 UM Including 18 Reserved 114 DM --------------------- 40 New Messages PANS ATM Messages 41 « Required » 34 « Replaced » by 33 « Replacement » 38« Not required » 1 Reserved 135 DM --------------------- PANS ATM Messages 18 « Replaced » 7 «  Not required » 1 Reserved 117 DM --------------------- 118 DM Including 1 Reserved SPR Version J (October 2012) PANS ATM Doc 4444 Ed. 15 SPR Version H

  15. Interim Update from OPLINK • Note:OPLINKP/5 Summary of Minutes not yet distributed by Secretariat • CPLDC Message Set status and next steps • ICAO introduction to guide OPLINKP work on Message Set (from C. Dalton) • key question: when does a message go into the PANS ATM? • ICAO does not support inclusion of non mature items in PANS ATM. • Only elements that would support operations for the future 5 to 6 years should be included. • SC214/WG78 material would contain the whole message set. • OPLINKP agrees to submit the whole message set to wider consultation. The main intent is to make sure ICAO validation will be available in due time to align the supporting industrial standards (e.g. WG78/SC214). Any divergence shall be avoided at all costs. • The final target for formal inclusion of the whole CPDLC Message Set in PANS ATM should be aligned with Block 1 (e.g. 2018) • Continue to document all proposed changes in OPLINK comment matrix • Continue to follow-up with proposed alignment of DOC 4444 and ICAO Doc

More Related