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
The strategy may accomplish more than one aspect within a common
verification step.
This section identifies a general objective for the verification of COTS IP
used in a custom device, enabling various verification approaches.
Objective IP-4
The applicant should describe in the hardware verification plan, PHAC,
or any related planning document, a verification strategy that should
encompass all three of the following aspects:
1. The verification of the COTS IP itself, addressing the risk identified
from the IP-2, Item 3 objective,
2. The verification of the COTS IP after the design steps performed by
the applicant (e.g., synthesis/place and route),
3. The verification of the integrated COTS IP functions within the custom
device.
Note 1: Reliable and trustworthy test data, test cases or procedures from
the COTS IP provider may be used as part of the verification strategy to
satisfy this objective.
Note 2: If the COTS IP implements functions based on an industry
standard, proven standardized test vectors verifying compliance with the
standard may be used in the verification strategy of the COTS IP.
Note 3: The verification strategy covers at a minimum the used functions
of the COTS IP and ensures that the unused functions are correctly
disabled or deactivated and do not interfere with the used functions.
5.11.3.3.3 COTS IP and Planning Aspects
The applicant has to define the activities that are needed for the hardware
development assurance approach related to COTS IP.
Objective IP-5
The applicant should describe in the PHAC, or any related planning
document, a hardware development assurance approach for using the
COTS IP that at least includes:
1. Identification of the selected COTS IP (version) and its source
format(s) associated with the point(s) in the design flow where the
COTS IP is integrated into the custom device,
2. A summary of the COTS IP functions,
3. The development assurance process that the applicant defines to
satisfy the objectives of Section 5.11.3,
4. The process related to the design integration and to the usage of the
COTS IP in the development process of the custom device,
17
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.