Development assurance
AC 20-152A scope support for which hardware now needs DO-254 evidence
For avionics suppliers, equipment suppliers, Certification teams, this review is used when New hardware program scoping. EE checks device inventory (FPGAs, COTS devices, IP cores against the approval basis, the configuration baseline, and the available certification records. The output gives hardware leads and certification managers an evidence map, discrepancy register, request list, and closure plan for the records that need applicant, supplier, or authority disposition.
What gets reviewed
- Index device inventory (FPGAs against the claim it supports.
- Compare COTS devices against the claim it supports.
- Trace IP cores against the claim it supports.
- Challenge circuit board assemblies) against the AC applicability statements against the claim it supports.
- Reconcile DAL each in-scope item inherits against the claim it supports.
- Confirm existing evidence against what the AC expects per item class against the claim it supports.
Scope this review
Tell us the asset, the event, and the evidence in scope, and we will outline a focused first engagement.
Identify what is missing against the means of compliance.
What gets validated
- Configuration match: device inventory (FPGAs fails review if the cited record cannot be tied to the current baseline.
- The review notes that evidence link: COTS devices fails review if the cited record cannot be tied to the current baseline.
- Limit carryover: IP cores fails review if the cited record cannot be tied to the current baseline.
- Source control: circuit board assemblies) against the AC applicability statements fails review if the cited record cannot be tied to the current baseline.
- Closure owner: DAL each in-scope item inherits fails review if the cited record cannot be tied to the current baseline.
Evidence normally required
Common discrepancies
- Finding in records: COTS IP integrated into an FPGA with no design assurance story.
- Installer issue: board-level assemblies assumed out of scope on pre-152A habits.
- Buyer concern: suppliers discovering scope mid-program when the authority reads the PHAC.
- Program risk: baseline does not match the delivered records.
How the work runs
Frame 152a 254
Confirm the exact event, affected file set, buyer role, and decision standard before any device inventory (fpgas is treated as sufficient.
Trace Support Evidence
Walk the named evidence from index entry to source artifact and mark where the trail supports, conflicts with, or fails to answer the page-specific question.
Sort Hardware Now
Group exceptions by closure route: document retrieval, data correction, engineering disposition, authority response, or contractual decision.
Package Development Assurance
Deliver the exception list, evidence map, and owner sequence in a form that can move directly into remediation, submittal cleanup, or transaction negotiation.
What the buyer receives
Who uses the output
- hardware leads use the map to brief the decision.
- certification managers use the register to assign closure.
- DERs use the request list to collect source records.
How the work fits into the transaction or program
This work sits inside the surrounding records or certification workflow and turns loose evidence questions into an ordered closure file. The page-specific framing is which devices and assemblies fall inside DO-254 design assurance under AC 20-152A and its EASA counterpart, since the guidance moved the boundary beyond the classic custom-device reading. The review notes that evidence reviewed: the device inventory (FPGAs, ASICs, PLDs, COTS devices, IP cores, circuit board assemblies) against the AC applicability statements, the DAL each in-scope item inherits, existing evidence against what the AC expects per item class, and documentation for items argued out of scope. Failure modes include COTS. For 152a 254 scope support, the practical output is a defensible record of what was checked, what did not match, who owns the fix, and which issue remains outside the review boundary. The ac 20 152a do 254 scope support scope is intentionally narrow: Determine AC 20-152A applicability across a hardware inventory and scope the evidence each in-scope item needs.. The 152a 254 Scope evidence question is tested against device inventory (fpgas and not against a generic checklist copied from another page. The Support Evidence Review trigger is new hardware program scoping, so the review ranks gaps by decision impact instead of document volume. The Hardware Now Needs searcher pattern is A hardware or certification manager searching for what AC 20-152A applies DO-254 to and whether their COTS or board designs are caught.. The Development Assurance Applicability evidence trail has to show source location, current status, conflicting entries, and the owner who can close the issue. The Boundary Record Review exception logic separates missing artifacts from mismatched data because those findings move through different closure routes. The Closure Trace Baseline handoff is written for hardware lead, with unresolved items preserved as decisions rather than softened into narrative prose. The deliverable stays anchored on evidence map for ac 20 152a do-254 scope, which makes the next reviewer able to reperform the path without rebuilding the file. The boundary is deliberately explicit: records and certification evidence are organized, but approval, acceptance, and airworthiness decisions remain with the authorized parties. The brief-specific angle is which devices and assemblies fall inside DO-254 design assurance under AC 20-152A and its EASA counterpart, since the guidance moved the boundary beyond the classic custom-device reading. The review notes that evidence reviewed: the device inventory (FPGAs, ASICs, PLDs, COTS devices, IP cores, circuit board assemblies) against the AC applicability statements, the DAL each in-scope item inherits, existing evidence against what the AC expects per item class, and documentation for items argued out of scope. The failure pattern includes COTS IP integrated into an FPGA with no design assurance story, board-level assemblies assumed out of scope on pre-152A habits, and suppliers discovering scope mid-program when the authority reads the PHAC. The ac 20 152a do 254 scope support 152a 254 scope lane records how now needs development affects boundary decision devices, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The ac 20 152a do 254 scope support scope which hardware lane records how development assurance applicability affects devices assemblies fall, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The ac 20 152a do 254 scope support hardware now needs lane records how applicability boundary decision affects fall inside design, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The ac 20 152a do 254 scope support needs development assurance lane records how decision devices assemblies affects design under its, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The ac 20 152a do 254 scope support assurance applicability boundary lane records how assemblies fall inside affects its easa counterpart, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The ac 20 152a do 254 scope support boundary decision devices lane records how inside design under affects counterpart since guidance, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The ac 20 152a do 254 scope support devices assemblies fall lane records how under its easa affects guidance moved beyond, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The ac 20 152a do 254 scope support fall inside design lane records how easa counterpart since affects beyond classic custom, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The ac 20 152a do 254 scope support design under its lane records how since guidance moved affects custom device reading, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The ac 20 152a do 254 scope support its easa counterpart lane records how moved beyond classic affects reading reviewed, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The ac 20 152a do 254 scope support counterpart since guidance lane records how classic custom device affects 152a 254 scope, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The ac 20 152a do 254 scope support guidance moved beyond lane records how device reading reviewed affects scope which hardware, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The ac 20 152a do 254 scope support beyond classic custom lane records how reviewed affects hardware now needs, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The ac 20 152a do 254 scope support custom device reading lane records how 254 scope which affects needs development assurance, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The ac 20 152a do 254 scope support reading reviewed lane records how which hardware now affects assurance applicability boundary, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The ac 20 152a do 254 scope support 152a 254 scope lane records how now needs development affects boundary decision devices, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The ac 20 152a do 254 scope support scope which hardware lane records how development assurance applicability affects devices assemblies fall, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The ac 20 152a do 254 scope support hardware now needs lane records how applicability boundary decision affects fall inside design, so this page carries vocabulary and failure modes that do not repeat the neighboring page set. The governing intent remains Determine AC 20-152A applicability across a hardware inventory and scope the evidence each in-scope item needs.. The operating angle for this page is Decision: which devices and assemblies fall inside DO-254 design assurance under AC 20-152A and its EASA counterpart, since the guidance moved the boundary beyond the classic custom-device reading. The review notes that evidence reviewed: the device inventory (FPGAs, ASICs, PLDs, COTS devices, IP cores, circuit board assemblies) against the AC applicability statements, the DAL each in-scope item inherits, existing evidence against what the AC expects per item class, and documentation for items argued out of scope. Failure modes: COTS IP integrated into an FPGA with no design assurance story, board-level assemblies assumed out of scope on pre-152A habits, and suppliers discovering scope mid-program when the authority reads the.
Start with a single asset
Reduce finding cycles by checking the package first.
Regulatory limits
EE does not issue approvals, make compliance findings, approve manuals, or determine airworthiness. The review gives the applicant, designee, buyer, or authority-facing team a clear evidence record for their own decisions.
Specific to this review
- which devices and assemblies fall inside DO-254 design assurance under AC 20-152A and its EASA counterpart, since the guidance moved the boundary beyond the classic custom-device reading.
- Device inventory (FPGAs often controls whether later summaries can be trusted.
- COTS IP integrated into an FPGA with no design assurance story is treated as a record gap until an owner closes it.
- FAA and EASA evidence should stay distinguishable from commercial claims and installer notes.
- The scope uses the 152a 254 Scope Support question as the control point, so the review stays tied to New hardware program scoping and the buyer decision behind it.
- The evidence starts with Device inventory (FPGAs and follows Evidence Review Hardware Now references until every exception has a source location and a reason code.
- The finding logic separates missing paperwork, conflicting status, stale revision data, and unsupported disposition because each class closes through a different owner.
- The timing matters for hardware lead: the output is useful only if the unresolved items are visible before acceptance, submittal, handback, or negotiation pressure fixes the sequence.
- The boundary control keeps Needs Development Assurance Applicability questions in the records or certification lane and sends technical acceptance issues to the authorized people who own them.
- The handoff value comes from Evidence map for Ac 20 152a DO-254 Scope; it gives the next reviewer a precise map instead of another broad request for a better file.
Sources
RTCA. Design assurance objectives and lifecycle data for airborne electronic hardware (FPGA/ASIC/PLD).
Federal Aviation Administration. FAA type certification process, certification basis establishment, and compliance findings.
Frequently asked questions
What makes this standards review different from a general file audit?
The scope is tied to 152a 254 scope support and to the decision named in the request. A general audit can list weak records; this pass ranks the gaps by whether they block new hardware program scoping or can be closed later without changing the decision.
What evidence has to be available before this work starts?
The starting point is device inventory (fpgas, the current status source, and any index or matrix that tells reviewers where the supporting artifact should live. Missing inputs are logged as findings rather than filled with assumptions.
Who decides whether an open item is acceptable?
The review explains what the evidence supports and gives hardware lead a closure path. Acceptance remains with the buyer, operator, authority, delegated engineer, or authorized person responsible for the underlying airworthiness or certification decision.
Relevant glossary terms
Related pages
Where this fits
Talk to an engineer who has done this work
We will walk through your current state, the records or evidence involved, and a scoped first engagement.
Talk through the aircraft, records, evidence, deadline, and next useful step.