1 / 13

EUROCAE WG-78 / RTCA SC-214 Plenary#6 Meeting Toulouse, 12th December 2008

EUROCAE WG-78 / RTCA SC-214 Plenary#6 Meeting Toulouse, 12th December 2008. Sub Group Progress Report. Overview of Sub-Group Progress. Consolidation of Integrated SPR SPR & Interop Consistency Ops Issues resolution : New ACM Scenario for UM120/DM89 ttr timer DCL & D-TAXI improvements

druce
Download Presentation

EUROCAE WG-78 / RTCA SC-214 Plenary#6 Meeting Toulouse, 12th December 2008

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 Plenary#6 Meeting Toulouse, 12th December 2008 Sub Group Progress Report

  2. Overview of Sub-Group Progress • Consolidation of Integrated SPR • SPR & Interop Consistency • Ops Issues resolution : • New ACM Scenario for UM120/DM89 • ttr timer • DCL & D-TAXI improvements • Progress on OPA • Progress on CPDLC(&CM) OSA

  3. Integrated SPR Session => Progress on pending comment resolution • 132 comments on « 24 November » version • Resolution of 36 Comments mainly related to Inetrop & SPR Consistency : • CM variables • CPDLC Message set • [Free Text] for Error

  4. Operational Issues (1/3) • UM120/DM89 ACM Scenario • No change of UM120 MONITOR (instead of STANDBY FOR [unit name] ON [frequency]) • If needed ICAO Voice phraseology may be updated to reflect the use of monitor • DM89 MONITORING is removed from the ACM scenario => not used • Frequency tuning confirmation could be performed via voice or datalink : UM120 MONITOR (instead of new msg CONFIRM ASSIGNED FREQUENCY [frequency]) • Airborne Automation ?

  5. Operational Issues (2/3) • ERROR to N Resp Message

  6. Operational Issues (3/3) • DCL : agreement reached in sub-group • - airborne system not limited to 1 DCL request (reboot possible) • - DM 138 DCL request not be used for operational request • - new attribute (else new message) to be developed for this purpose.(Todd/Matt/CB) • D-TAXI : agreement to replace 5.4.6 in ISPR • - Main concept supported, improvements in DUG and 214/78 • - Content to be reviewed and tailored (Matt & CB) • Coordination wiht WG 44/SC217 welcomed. • Final D-TAXI "graphic" ready for 2011 release.  (should be included in the 2009 draft) • 4DTRAD : 4 New « Speed » messages proposal • New variable : [speedschedule] => sequence of 1..2 [speed] • Need only two new « speed » messages : In CLIMB [speedschedule] & IN DESCEND [speedschedule] • Action on SG3 to assess the new variable structure & element

  7. Next step for Integrated SPR Consolidation • Objective : New « Redline » version of Full Integrated SPR will be distributed by End of January 2009 • Part 1 : Chapter 1: Introduction / Chapter 2 : ATS Function / Chapter 3 : Environment • Part 2 : Chapter 4 : CM Application • Part 3 : Chapter 5: CPDLC Application • Part 4 : Chapter 6 : FIS Application • Part 5 : Appendices and Annexes • OSA & OPA Contribution are expected no later than 15 January 2009 • Review and Provide comments on « 24 November 2008 » Integrated SPR no later than 10 january • Use Excel file to provide comments ! • When possible propose a resolution • Avoid comment about the scope (e.g. oceanic vs domestic) :

  8. EUROCAE WG-78 / RTCA SC-214 Plenary#6 Meeting Toulouse, 11th December 2008 CPDLC OSA Report 8

  9. ENV-C consideration • ENV-C will not be considered before March 2009 OR • A section will be added in the current CPDLC OSA: • A requirement will be formulated for the ground to be able to manage transition of PIAC in case of a loss of CPDLC. • Thanks to this requirement, OH classification will not change from ENV-B. • Therefore, Safety Requirements will be the same

  10. Timers: ttr and tts • Responder timer (ttr) removed on board. • This was already considered in CPDLC OSA (100% failure rate requirement). • Different Sender timer (tts) on ground depending on messages safety impact. • No need for a dedicated safety assessment: • There is always a tts on ground to detect interrupted transactions. • The current OSA considers the worst case (message with the worst safety impacts)

  11. CM OSA consideration (1/2) • Dedicated OSA for CM application was envisaged: • All safety requirements for CM application would have be gathered at the same place. • Application needing CM application derive requirements for CM hazards. CPDLC-OH CPDLC OSA AC BC CSP BC Gnd BC FC BC ATCO BC CM OH CPDLC SRs CM OH CM OSA AC BC CSP BC Gnd BC CM SRs

  12. CM OSA consideration (2/2) • But, after starting CM OSA: • CM does not lead to any direct OH. • This application may contribute to some other application OH. • Flight Plan correlation can be part of CM or ACM. CPDLC-OH CPDLC OSA AC BC CSP BC Gnd BC FC BC ATCO BC ? CPDLC SRs CM OH Correlation? All will be assessed in the same OSA CM OH ? CM OSA AC BC CSP BC Gnd BC CM SRs

  13. CPDLC OSA status and schedule • CPDLC OSA status • Agreed OHA. • Fault trees to be updated to include CM contribution to CPDLC hazards. • Safety requirements to be derived for CM contributors. • “Acceptability” from OPA perspective to be checked. • Likelihood estimates for basic causes to be included. • Conclusion about LWCE acceptability • CPDLC Functional Analysis: • Functional Flow Block Diagrams • N² diagrams • CPDLC OSA ready for integration:16th January 2009

More Related