Artefact · Safety & Security
Plan for Hardware Aspects of Certification
The plan an airborne electronic hardware project agrees with the certification authority, saying how the hardware will meet the objectives of DO-254 at its assurance level.
- Also known as
- PHAC
- Type
- Artefact
- Domain
- Safety & Security, Safety standards
Overview
The Plan for Hardware Aspects of Certification is the top hardware plan in an avionics programme. It describes the hardware items, their assurance levels, the lifecycle and processes to be followed, the data to be produced and any alternative methods, so that the authority can agree the approach before the work is done.
How it works
It names each hardware item, such as a programmable device, an ASIC or a board, with its level and its place in the system. It summarises the development, validation, verification, configuration management and process assurance plans beneath it, the tools and how they will be assessed, and how commercial parts are treated.
The authority reviews it at the first stage of involvement. Once agreed it is a commitment: later reviews check the evidence against it, and departures need a revision and fresh agreement.
Software has a matching plan, the Plan for Software Aspects of Certification, under DO-178C.
Examples
- A plan covering two programmable devices at different levels.
- A section on how commercial parts and their errata will be assessed.
- The assessment approach for synthesis and place and route tools.
- A revision after the authority asks for a different verification method.
Why it matters
Certification programme managers and hardware leads write it during certification planning. It shapes how the FPGA or ASIC team works for the rest of the programme, and the hardware accomplishment summary at the end reports against it.
It matters most to: Certification Program Manager, Configuration Management Engineer, FPGA Design Engineer
Common confusions
- Not the same as Hardware accomplishment summary
- The plan says what will be done; the accomplishment summary at the end says what was done and how it compares with the plan.
Related standards
- DO-254 (design assurance guidance for airborne electronic hardware)
Sources
- DO-254 Design Assurance Guidance for Airborne Electronic Hardware (opens in a new tab), RTCA, 2026-11-10
- EASA publishes new AMCs on development assurance for airborne electronic hardware and management of open problem reports (opens in a new tab), European Union Aviation Safety Agency, 2026-11-10
- DO-254 (opens in a new tab), Wikipedia, 2026-11-10
Related terms
Part of the Safety & Security glossary, with every term in the topic and the lifecycles, tools and standards that use them.
Where it appears on the Hub
Used on 2 pages of the Hub. In each group, the pages that mention it most come first.
Lifecycle stages and gates
Suggest an improvement
Suggest an improvement to this entry
A clearer definition, an example, a correction or a source an editor can check. Editors review every suggestion before the entry changes.
Last reviewed . Written by The Semiconductor Hub editorial team. The full glossary