170 likes | 253 Views
This comprehensive report covers the planning and basis for avionics development, FAA Data Communication Program RFP, and Validation Break-Out Group discussions for NextGen and SESAR initiatives. It outlines tracing strategies between standards, incorporation of DO-306/ED122, and planning for segment delivery, interval management, and validation frameworks. Key focus areas include traceability, VDL2 MOPS and MASPS, security standards tailoring, and integration of oceanic and continental data link definitions. Additionally, the document details tasks for 2010, including completion of SPR/INT 0.H, validation strategy definition, and revision of VDL2 MOPS/MASPs for segment 2/IP3 environments.
E N D
SC-214/WG-78 Plenary 9: 14–18 December 2009Albuquerque
SG Reports Status of showstoppers Planning for delivery upon completion of Plenary guidance
Basis for approval of mature Draft #2 • Intended Use: • Basis for FAA Data Communication Program RFP • Basis for Prototype Avionics Development • Basis for Verification & Validation Activity NextGen and SESAR
Report from Validation Break-Out Group • TOR Revision • Incorporation of DO-306 – How and Why • Traceability – What and Why • VDL 2 MOPS and MASPS • Tailoring of Security Standards • Segment 2/IP3/EnvB Use Only • No A/G Security Required for Segment 1/IP1 & IP2/EnvA • Target Delivery in Final Standard 2011 • Planning for Segment 3 e.g. Interval Management (M&S) • FLIPINT, HAZWx & D-FLUP • Validation Framework • 214/78 Approach e.g. responsibility of committee vs validation teams, workload, timing • Project Identification – Note who, what, & when • Document Configuration Management – Management of inputs from validation teams and development of proposed disposition • Review Criteria • Intended Use • Status & Planning of FAA Procurement
Tracing Discussions(1) • Tracing at Interoperability Level • For 214/78 gnd systems to provide service to FANS A/C • Included in the interop specs of 214/78 • For 214/78 gnd systems to provide service to L2K A/C • Included in the interop specs of 214/78 • For FANS1/A gnd systems to provide service to 214/78 A/C • TBD • For L2K gnd systems to provide service to 214/78 A/C • TBD • Tracing from INT to SPR (Ch2) • From 214/78 INT – to appls/services/SRs/PRs to Functions of 214/78 • Limitations of 214/78 services for FANS A/C • Eg.Table that subsets the 214/78 SPR reqs for FANS A/C • Limitations of 214/78 services for L2K A/C • Eg.Table that subsets the 214/78 SPR reqs for L2K A/C
Tracing Discussions (2) • Tracing between Standards • Tracing between 214/78 standards to DO306/ED122/ DO258A/ED100A • Tracing between 214/78 standards to 290/ED120 Change1 and 2 / DO280B/ED110B • Tracing between 214/78 standards to DO305/ED154
Incorporation of DO-306/ED122 – How and Why • Integrate DO-306/ED122 content with 214/78 SPR • Develop a convergence package for oceanic and continental data link • First step entails minimum changes to DO-306/ED122 content • No revisions to oceanic operational environment • No revisions to operational, safety, or performance requirements • No revisions to safety analysis • Familiarize the Committee with the oceanic data link • Merge oceanic and continental definitions for convergence so that they can be compared side by side. • Identify differences or gaps, and determine a resolution. • Call for interest for oceanic experts
VDL 2 MOPS and MASPS • Specialized Subgroup to Revise • ICAO VDL 2 Tech Manual • ED-92, • DO-224B and • DO-281A in accordance with AEEC 631-5 to support: • Multiple frequency operations (autotune) • Frequency support list
Planning for coordination with SC186 • SC-186 approved ITP ISRA today • SC-186 to Develop an ISRA, by Dec 2012, for SC-214 to Develop CPDLC for Interval Management e.g.: • Merging and Spacing • Crossing and Passing • In Trail Procedures • SC-186 is Responsible for Safety Assurance and will Deliver Safety and Performance Requirements to SC-214 • 214/78 to Allocate the Safety and Performance Requirements Across ATSU, CSP, and Aircraft.
FLIPINT, D-HZWX & D-FLUP • FLIPINT – In • D-HZWX – In • D-FLUP – Out
Tasks for 2010 • Complete SPR/INT 0.H • Define Validation Strategy • Maintain and evolve the SPR/INT drafts • Revise VDL2 MOPS/MASPs • Oceanic/Continental Integration • Tailoring of security standards for Segment2/IP3 ENVB
Planning 2010 for SGs • Editorial SG • Meeting Toulouse – week of January 11 • Release SPR/INT 0.H • SG completed its tasks • New SGs • Validation Strategy SG • Configuration Control SG • VDL2 MOPS/MASPs SG
Validation Strategy SG • Interface to Validation Projects • Identify validation projects • Establish Minimum Validation Objectives • Ensure that humans and data comm systems on the flight deck and on the ground can meet the requirements of the airspace system • Define a robust and practical controller/pilot environment for E2E human-in-the-loop testing. • Assess adequacy that end-to-end human-in-the-loop is used appropriately and to the extent needed • Develop Validation Cross-Reference Matrix
Change Control SG • Define Template for Validation Projects to Document Issues to be Addressed by the Committee • Prepare Mature Draft 3 • Develop Tracing Material • Incorporate OSA/OPA/INT D-HZWX material • Include Comments after Rev 0.H • Oceanic/Continental Integration
VDL 2 SG • New functions in VDL2 in accordance with AEEC 631-5 • Multiple frequency operations (autotune) • Frequency support list • Revise • ICAO VDL 2 Tech Manual • ED-92 and DO-281A (MOPS) • DO-224B (MASPS)
New SG Meetings in 2010 • First Subgroup Meeting • In Europe • Proposal week of 1-5 March • Host Proposals • DFS Langen • Eurocontrol Brussels • Second SG • In US • Proposal week of 27 September • Host Proposals welcomed