presented to: by: date: federal aviation administration complex electronic hardware policy &...

Presented to:

By:

Date:

Federal AviationAdministrationComplex Electronic

Hardware Policy & Guidance

Software & Complex Electronic Hardware Standardization Conference

John Lewis, AIR-120, Technical Programs Branch, Washington DC

Email: [email protected], (202) 493-4841

July 26, 2005

2Federal AviationAdministrationJuly 26, 2005

Software & Complex Electronic Hardware Conference

Presentation Overview

• AC 20-152, Design Assurance Guidance for Airborne Electronic Hardware, RTCA/DO-254

• Policy Memo for RTCA/DO-254• RTCA/DO-254 training course• Authorization of DERs for complex electronic

hardware (CEH)



AC 20-152, Design Assurance Guidance for Airborne Electronic Hardware, RTCA/DO-254

• What is the background with developing and recognizing RTCA/DO-254?– RTCA SC-180 lasted 7 years and held 25+

meetings.– RTCA/DO-254 published April 19, 2000.– FAA recognition of DO-254 for programmable logic

devices (PLDs) via issue papers.– FAA published AC 20-152 on June 30, 2005.– Process took 12 years!




• Why did it take so long to publish and recognize RTCA/DO-254?– Scope problems: What is complex hardware?

(LRUs, circuit board assemblies, custom micro-coded components, COTS, etc.)

– Hardware design assurance levels.– Unofficial disagreement by industry on release of

RTCA/DO-254.




• What types of complex electronic hardware are covered by the AC 20-152?– Complex custom micro-coded components:

• Programmable logic devices (PLDs)• Field programmable gate arrays (FPGAs)• Application specific integrated circuit (ASICs)• Other similar electronic devices




• What design assurance levels does AC 20-152 recognize for RTCA/DO-254?– Complex devices supporting Level A, B, & C

functions.– For Level D devices, applicants can use:

• If RTCA/DO-254 is used, then FAA review of lifecycle data is not necessary.

• Existing manufacturing design assurance practices (contingent on ACO agreement).




• What about microprocessors?– Recognize alternate methods to ensure COTS

microprocessors perform intended functions.– RTCA/DO-254 may be used for custom developed

microprocessors.– Lack of guidance for to address advance design

features (cache, pipelining, extra micro-coded instructions, etc.) in COTS microprocessors.

– Ongoing FAA/AVSI (Aviation Vehicle Systems Institute) research project for COTS microprocessors.



Policy Memo/Order for using RTCA/DO-254

• How is the FAA going to harmonize with EASA for guidance on DO-254/ED-80?– Draft CAST paper P#86, Clarifications on the use of

RTCA/DO-254, Design Assurance Guidance for Airborne Electronic Hardware.

– FAA & EASA intend to publish equivalent guidance material.



Policy Memo/Order for using RTCA/DO-254

• How is the FAA going to clarify the technical issues when using DO-254?– Draft policy memo addresses the following technical

issues:• Modifiable devices, verification & validation

processes, traceability, configuration management, etc.

– Schedule for release of policy memo by September, 2006.

– Plan to incorporate policy memo into FAA Order.



Training for RTCA/DO-254

• What about new training for complex electronic hardware and RTCA/DO-254?– Proposed FY06 business plan nomination to develop

FAA course for RTCA/DO-254 (similar to DO-178B course for software).

– Course development contingent on budget resources.



Authorization of DERs for CEH

• What about authorization of DERs in the complex electronic hardware (CEH) technical area?– Point of contact is Kevin Kendall, AIR-140.– Draft policy memo under coordination to address

• Qualifications • Limitations • TSO approval of CEH

– Policy Memo will be incorporated in future revisions to Order 8150.1B, Order 8110.37, and Order 8100.8.




• What about some specific qualifications under consideration for CEH?– Thorough working knowledge and understanding

of RTCA/DO-254.– Understanding of and experience with DO-254

hardware life cycle processes and data required for certification.

– Experience with different kinds of CEH design, such as Application Specific Integrated Circuits (ASIC), Programmable Logic Devices (PLD), and Field Programmable Gate Arrays (FPGA) design.




– Familiarity with Hardware Description Languages that are used for programming CEH, and an understanding of the types of verification required for use of such languages .

– Experience with complex electronic hardware verification process activities, including reviews, analyses, and testing.

– Familiarity with complex electronic hardware modification processes, including determination of change impact analyses, regression analyses and testing.




• What are some delegation limitations under consideration for CEH?– Approval of the Plan for Hardware Aspects of

Certification (PHAC), Top Level Drawing, and the Hardware Accomplishment Summary (HAS) will be reserved for approval by the ACO.

– For some systems and complex electronic hardware requiring design assurance Level A or B, the verification and validation data may also be reserved for approval by the ACO.



Special thanks to national FAA team members!

• FAA team for AC 20-152:– Transport Airplane Directorate: Gregg Bartley, Will

Struck, & Varun Khanna– Rotorcraft Directorate: Jorge Castillo– Engine Directorate: Gary Horan– Small Airplane Directorate: Robin Sova & Wes Ryan– Chicago ACO: Brenda Ocker– Los Angeles ACO: Tom Phan– Wichita ACO: Gerry Pilj & Ruth Hirt



Questions?

Comments to:[email protected]

zzzz

presented to: by: date: federal aviation administration complex electronic hardware policy &...

Documents