RTCA規格 DO-372, 2017: Addressing Human Factors/Pilot Interface Issues for Avionics
※セキュアPDF版（シングルユーザー版）をご希望のお客様は別途お問合せ下さいませ。
※当ウェブ・ショップに掲載のない規格につきましては、別途お問合せ下さいませ。
※掲載の規格は、当ウェブ・ショップに掲載時点で確認できた最新版でございます。 最新の発行状況につきましては受注時に改めて確認をさせて頂きますので予めご了承下さい。
Description
The objective of this document is to increase human factors awareness by the individuals who are responsible for the design and certification of systems and equipment and related interfaces designed for use by the flightcrew. This applies to systems and equipment that are certified at the box level or installation level.
The FAA documented this information previously in expired FAA Notice 8110.98, Addressing Human Factors/Pilot Interface Issues of Complex, Integrated Avionics as Part of the Technical Standard Order (TSO) Process. The original notice only addressed the TSO process, however human factors issues were being regularly identified late in the Type Certificate (TC), Supplemental Type Certificate (STC), and Amended Type Certificate (ATC) processes with installed avionics.
This document outlines a process for identifying the flightcrew interface aspects of a system as part of the engineering design and certification process, and provides previously approved design examples of how human factors issues have been addressed. The first section of this document is based on the original steps in expired FAA Notice 8110.98 but extends the process to include TC, STC, and ATC.
The second section provides the types of human factors issues previously identified in certification programs and approved design examples. Not every human factors issue encountered is covered. The focus remained on two core principles:
(1) identifying human factors aspects in a generic evaluation process that could be scaled as appropriate to the scope and size of the project, and used by avionics manufacturers, Original Equipment Manufacturers (OEMs), and certification authorities alike, and
(2) including only those human factors issues that were recurring in the certification process and had a clear human factors basis. Neither the process nor the examples are meant to be prescriptive. Good practices and lessons learned are provided as a means to inform the development and certification process in an effort to avoid common pitfalls that have been observed in past certification efforts. This document is not intended as a means of compliance for certification. Regulatory requirements and guidance take precedence over the content of this document.