1 / 14

SC-214/WG-78

SC-214/WG-78. Plenary 8: 21 Sept – 25 Sept 2009 Toulouse. ENV-B Agreement. SC214/WG78 continue to agree to publish a common product at the end of 2011 Prior to 2011 publication:

crescent
Télécharger la présentation

SC-214/WG-78

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. SC-214/WG-78 Plenary 8: 21 Sept – 25 Sept 2009Toulouse

  2. ENV-B Agreement • SC214/WG78 continue to agree to publish a common product at the end of 2011 • Prior to 2011 publication: • SC214 have a requirement for ENV B to be included in the ISPR, particularly for the Dec 2009 milestone and beyond. • WG78 stakeholders are constrained from committing to the contents of an ENV B description until involvement/coordination can be performed with relevant work packages within the SESAR JU. Kick Off Meetings have only just begun and it will take time to initiate and action this task. • WG78 cannot yet commit to the characteristics of, or any analysis resulting from, ENV B up until the 2011 ratification deadline allowing coordination, feedback and involvement from the relevant SESAR JU work packages. • WG78 will however commit to supporting SC214 in advancing as much as practicable the ENV B description during the next two years through a review and comment process. SC214 are responsible for performing the actual analysis on the services and applications with regards to ENV B. • SC214 accept that any internal commitments they make based on details of, or analysis of, the ENV B characteristics represent a risk as environmental characteristics (and hence related requirements) may change prior to ratification of the ISPR.

  3. Oceanic material/discussions in SC214/WG78… • Common Understanding Oceanic/Continental Convergence is Required • Per current TORs • 2 CPDLC messages in INT to support ATSA/ITP • INT will ref DO312/ED159 for SPR material • Outside current TORs • Reference to Oceanic in ATS Functions • ED100A/DO258A update • 214/78 ATN INT–oceanic messages from ED122

  4. Status Oceanic/Continental Convergence • Discussion at P6 • Intention to include Oceanic Reqs in the final product (end 2011), during 2010-2011 in parallel with the validation activity. • Decision [P6-5]: The SC-214/WG-78 SPR should include both the Continental the Oceanic requirements in a converged SPR. • Action [P6-5]: Paul Mettus and Jose Roca to draft a paper analysing the impact of the change of scope of the group’s activities to include Oceanic requirements. • Existing Oceanic Material • SPR: DO306/ED122 INT:DO258A/ED100A • Basis for cert/approval of oceanic D/L ops today • Which Oceanic Environment do we include in the Converged SPR ? • The existing per 306/122 ? • The next generation environment ? • Other options ?

  5. The existing Environment per 306/122 • Integrated SPR doc • Merging 306/122 content with SPR 0.F 214/78 • Common Intro/ATS Functions/Messages (1) • Integrate OSA/OPA (2) • Traceability from (2) to (1) • Safety and Perf Reqs for Oceanic remain the same as in 306/122 • Convergence at SPR doc level • Keep existing safety approach cont/oceanic • No need to ..Align existing names for services and messages • INT for ATN accomodation by FANS ground centres • Benefits for Certification/Approval process and avionics development ?

  6. The next Oceanic Environment • Integrated SPR doc • Common Intro/ATS Functions/Messages (1) • New Oceanic ENV description • Conduct OSAs for Oceanic following 214/78 approach • Conduct OPAs for Oceanic following 214/78 approach • Convergence at SPR doc and System/Avionics level • INT for ATN accomodation by FANS ground centres • Benefits for Certification/Approval process and avionics development ? • (Assumption is that a new oceanic environment is required)

  7. Impact Assessment • Existing Oceanic environment • Extra Editing effort • … • New Oceanic environment • Call for interest for oceanic expertise required • Significant extra OSA/OPA effort • Validation and Verification for new Oceanic services and INT • …

  8. WP2 Draft WP1 Draft WP1 + WP2 FAA Call to Industry StandardsPublication 2008 2009 2010 2011 SC-214/WG-78 Scope and Plan

  9. SC-214/WG78 Meetings Plan

  10. Organisation • New SGs structure until December 2009 • SPR Integration: Jane/Thierry; Interop (Claudia/Fred) • SPR: 4DTRAD/FLIPINT SPR • Chairs: Dijana, John • INT: Interop for WP2 (4DTRAD, FLIPINT, ITP) • Chairs: Claudia, Frederic

  11. Do we need this? Interop with Old A623 Applications - 1 DO/ED-YYY ATN Advanced Continental and Oceanic Services ED85A/89A ACARS 623 DCL/DATIS services Air INTEROP Req. ED85A/ ED89A DO/ED-YYY A 623 INTEROP Ground INTEROP Req. ED85A/ ED89A ED85A/89A ACARS 623 DCL/DATIS services DO/ED-YYY ATN Advanced

  12. Interop with Old A623 Applications - 2 DO/ED-YYY ATN Advanced Continental and Oceanic Services ED85A/89A ACARS 623 DCL/DATIS services Air INTEROP Req. ED85A/ ED89A Ground INTEROP Req. ED85A/ ED89A Dual Stack on the ground ED85A/89A ACARS 623 DCL/DATIS services DO/ED-YYY ATN Advanced

  13. Planning for SPR Version F • End of Plenary 8 (21-25 Sept) • complete all OSD descriptions; good progress on OSA/OPA and Interop • End of Seattle SGs Meeting (26-30 Oct) • Complete OSA, OPA and interop for all services • Resolve remaining issues and complete ISPR integration 2 weeks after Seattle i.e. by 13 Nov. • 13 Nov - send out ISPR version F for comments by 4 Dec (3 weeks) • Week of 7 December • Consolidate all comments into one I-SPR vF Comment Matrix • Start integration of Comments (for the non critical one) • Prepare a report to P9 • Organise the work at P9 in order to address the critical ones • Approve ISPR F at P9 • Issue the document by end of 09

  14. SC214 / WG78 VALIDATION Activities WP x Validation contribution SPR Maintenance PDRs & SPDs Integration of Accepted PDRs PLENARY COORDINATION Accepted PDRs SESAR Support to the Validation Strategy Support to the Coordination Proposed Defect Report Analysis Definition of Scenario Protocol DocumentSpecification Support Coordination Standard Consistency WP y Validation contribution INT Maintenance Accepted PDRs Integration of Accepted PDRs PDRs & SPD NEXGEN Validation activities PDR : Proposed Defect Report Decribe the nature of the defect and propose modification to the standards SPD : Scenario Protocol Document Define and Identify the Ressources & Partners, the Validation Plateform, and the tests to be performed regarding a specific validation objective New SPR & INT Drafts by end of 2010 List of accepted PDRs

More Related