Summary of the First Meeting Special Committee 227 ... - RTCA

More documents

Recommendations

Info

During the course of the meeting discussions, a number of issues related to aeronautical information and databases were raised e.g. changes in RF, FRT, displays, etc. Dave pointed out that in the committee planning he had raised such issues and documents DO-200A and DO-201A. However, it was felt that the scope was too large for the committee schedule. With the committee discussions, it was apparent that all the pieces for addressing lessons learned and new additions need to be worked in order to achieve success in implementation. It was pointed out that RTCA was considering expanding the scope of SC-217, Terrain and Airport Databases to add navigation. A number of the committee including the chair expressed concern that splitting off the effort might make sense from a functional standpoint but by being tackled by a group with a totally different perspective and goals, could also lead to divergent solutions and increased complexity for SC-227 standards. Dave pointed out that this adds the need for close coordination with this committee as well as SC-214 and SC-186 in moving forward. Dave will make these points known to RTCA. Schedule Discussion regarding MOPS Update Do we need the MOPS done at the same time as the MASPS It may be a long process after the completion of the MOPS for it to go into the TSO, so it should be okay if the MOPS are delayed until after the MASPS are complete. We can start MOPS activity before the MASPS are complete, but we may not be able to focus the full group attention on the MOPS until the MASPS are complete. JohnH: we can start fixing the text of the MOPS right away. We need the fixes made, and this can be done before the MASPS are done. The new stuff will need to wait, but not the fixes. Walk Through of DO-283A MOPS Dave pointed out that he was leading this discussion only because a lead had not been found by the time of the meeting. He stated that as an aircraft and systems person, it would be more appropriate to have an equipment manufacturer with experience in MOPS, TSO’s and related regulatory approvals in front of this effort. Until then, and for this session only Dave quickly skimmed over the content of the MOPS and discussed how it adds specificity to the MASPS and leaves out background rationale information that is not needed to describe the requirements. Dave mentioned a number of areas that may require changes including: RNP Scalability: the current MOPS provides specific criteria for set RNP values but also provides guidance with regard to the applicability to other RNP values and especially for the lateral deviations. However, more may be required with regard to factors such as acceptability of current discrete alerting levels or what mitigations will work VOR/DME is included as with the MASPS. However the MASPS goes, so will the MOPS. Currently the MOPS is only 2D. What becomes the minimum set of requirements e.g. VNAV and TOAC needs to be discussed and determined. The test sections may need updating for DO-160, as well as additional test scenarios for functions and performance for sequential RF turns, datacom, data outputs , etc. Hardware/Software compliance Relevant electronic display features/performance for the installed system All MASPS changes that correspond to a MOPS requirement. Dave also mentioned that more may be appropriate but will require the knowledge and perspective of those who actually need and use the MOPS as a basis for equipment development and approvals. Regarding holding – we may need to address lessons learned regarding disconnects between expectations and content. 20
Prioritization and Scope of Updates to be Made Dave presented a list of areas that we expect to need to make updates to the MASPS and MOPS and solicited input. In order to quickly order the discussion, the group ‘multi-voted’ for their priorities to get to an ordered, prioritized list. The group looked at the higher priority items in the list and discussed what needs to happen in those areas. Dave’s notes are contained in “DO236B_Update Issues Matrix.docx” that is posted to the Workspace. Action Required for All. Dave requested participants to develop issue white papers for items in the list, presenting their position for what needs to be changed and how to change it. The assignments are contained in the posted document. It is expected that the papers will be available via the workspace three weeks prior to the next meeting. It is recognized that this is a challenge with the 2 month interval and everyone was urged to make their best efforts to make this work. -S- Mike Jackson Secretary CERTIFIED as a true and accurate summary of the meeting. -S- Dave Nakamura Chairman 21
Page 1 and 2: Summary of the First Meeting Specia
Page 3 and 4: NEXTGEN IMPLEMENTATION PLAN (NGIP)
Page 5 and 6: NextGen Implementation Plan (NGIP)
Page 7 and 8: • flight deck display of speed cu
Page 9 and 10: Powerpoint: “3a Standards of Navi
Page 11 and 12: Sharing of common flight plan betwe
Page 13 and 14: Q: what is the impact on economy of
Page 15 and 16: Section 1.1 para 3 is significant.
Page 17 and 18: David DS: network and flow manageme
Page 19: concern that we don’t have moment

Summary of the First Meeting Special Committee 227 ... - RTCA

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?