This AC recognises DO-254/ED-80 and adds objectives for distinct hardware categories. Its stated applicability covers hardware contributing to DAL A, B and C functions; the relevant objective restrictions still apply.
The source, within reach.
Search within this AC, jump to a source page, or download the complete saved publication.
This extraction supports search. Read the original page for complete notation and layout.
10/7/22 AC 20-152A
5.11.2 Applicability to COTS IP
Section 5.11 is applicable to COTS IP used in a custom device that meets the definition
of “commercial-off-the-shelf intellectual property” in the Appendix A Glossary. This
scope encompasses digital, analog, and mixed-signal COTS IP.
Note: Analog COTS IP is within the above-mentioned scope, as it could be instantiated
within a custom mixed-signal device.
Section 5.11 is applicable to COTS IP contributing to hardware DAL A, B, or C
functions.
Section 5.11 is applicable to Soft IP, Firm IP, and Hard IP that are inserted within a
custom device by the applicant. However, Section 5.11 does not apply to Hard IP that is
embedded in the silicon of an FPGA or a PLD by the FPGA/PLD device manufacturer.
This type of IP is considered to be part of the COTS device, and is covered in Section
6, Use of Commercial Off-the-Shelf Devices.
5.11.3 Development Assurance for COTS IP
A COTS IP development assurance approach should be based on the category of the
COTS IP (soft, firm, hard) and on the identified risks of failure due to a design error in
the COTS IP itself or an error in the way it is used in the custom device.
This section provides objectives addressing development assurance when using COTS
IP. These objectives are intended to cover the particular aspects of development when
using COTS IP, and are expressed in connection with the custom device development
process that follows ED-80/DO-254 and the custom device objectives of this document.
The development aspects related to COTS IP start from the custom device process that
captures the allocated requirements for the function that will be performed by the
COTS IP. From this entry point, the following aspects provide a basis to define the
development assurance objectives for the use of COTS IP:
• Selection of the COTS IP,
• Assessment of the IP provider and the IP data,
• Planning activities, including the verification strategy,
• Definition of the requirements/derived requirements,
• Design integration, implementation, and verification of the COTS IP in the custom
device.
5.11.3.1 Selection of the COTS IP to implement the function
COTS IP can be available in different forms/source formats and various levels of
quality. Some COTS IP may not be acceptable for use in airborne systems. The
selection criteria below are intended to address the essential characteristics that are
considered a minimum for the use of IP in custom AEH devices.
14
Saved from the FAA on November 17, 2026. All original pages are retained. Engineering explanations are presented separately below.
Aerospace Consulting / Engineering perspective
Define the hardware assurance approach by function and device.
Use the PHAC to identify intended functions, assurance levels, custom and COTS boundaries, and the evidence needed for each applicable objective. Keep supplier information, integration verification and system-level assumptions connected.
A focused review, an agreed assessment package or ongoing support alongside your team. We can agree the relevant inputs and scope in the initial conversation.
This opens your email application.
Start a conversation
Tell us about your programme, the system you are developing and the support you need.
We can agree a focused use-case review, a defined evidence package or ongoing programme support.
This opens your email application.
Specialist aerospace expertise
Aerospace Consulting is led by Hussein Khimji, an FAA Designated Engineering Representative in systems and equipment, with a focus on system safety, flight controls and avionics.
We work with aircraft developers and systems suppliers to connect technical decisions, safety assessments and certification evidence.
This is the proposed introduction. The full About page will add your approved biography and associate expertise.
Systems engineering & development assurance
Tell us about the aircraft or system, its intended function, stage of development and the support you need.