DO-254 Complex Hardware Development & Certification - Project Planning Phase

Visit Certon on FacebookVisit Certon on TwitterVisit Certon on LinkedIn

What Phase is Your DO-254 Project In?

Planning  |  Validation & Verification  |  Requirements  |  Design & Architecture  |  Implementation & Integration  |  Delivery

Project Planning Phase

 

At the start of the DO-254 Electronic Hardware Lifecycle, and after the Safety Assessment processes and analyses have established the design assurance level of the AEH product, the Project's Planning Phase begins. The purpose of this phase is to define the means by which the requirements are converted into hardware item with an acceptable amount of evidence of assurance that the item will safely perform its intended functions. This Electronic Hardware Planning Process involves creating plans and standards to govern the development, verification, configuration management, quality assurance, and delivery of electronic hardware in compliance with DO-254 guidelines. In this phase, the following objectives must be addressed for compliance:

 

  • The Hardware Design Lifecycle processes are defined.
  • Standards are selected and defined.
  • The hardware development and verification environments are selected or defined.
  • The means of compliance of the hardware design assurance objectives, including stategies identified using guidance, are proposed to the certification

 

Execution of the phase will generate the Plan for Hardware Aspects of Certification (PHAC), Hardware Design Plan (HDP), Hardware Verification Plan (HVP), Hardware Configuration Management Plan (HCMP), Hardware Process Assurance Plan (HPAP), Hardware Requirements, Design, & Implementation Standards (HRDIS) documents are written and reviewed in preparation for the first Stage of Involvement (SOI) Audit with the Certification Authority. These documents are explained in further detail below.

 

CERTON has the experience and expertise to help you develop these plans that will be required and approved by your Certification Authority for your DO-254 project.

 

 

Plan Hardware Aspects of Certification (PHAC)

 

The purpose of this document is to provide planning for hardware development, configuration management, process assurance, verification, and standards. This document will be referenced throughout the entire development lifecycle of the hardware item. This document conveys all ideas of what the company seeking certification plans to do in the development process for the hardware item. This document applies only to the design and verification of the hardware item for which it is written. At a minimum the PHAC should include:

 

  • System Overview
  • Hardware Overview
  • Certification Considerations
  • Hardware Design Lifecycle
  • Hardware Design Lifecycle Data
  • Additional Considerations
  • Alternative Methods
  • Certification Schedule

 

Hardware Development Plan (HDP)

 

The purpose of the Hardware Design Plan (HDP) is to outline the process of design, implementation, and development of the hardware item. This HDP conveys all ideas of what your company plans to do in the development process of the hardware item. The scope of this document covers a recorded plan for the procedures, methods, and standards to be applied and the processes and activities to be conducted during the development process, ref. DO-254 Section 10.1.2, of the hardware item. This document can be included in the PHAC and should contain the following:

 

  • Hardware Design Lifecycle
  • Hardware Product Description
  • Hardware Design Methods
  • Hardware Design Environment
  • Hardware Item Data
  • Additional Considerations

 

Hardware Verification Plan (HVVP)

 

The purpose of this document is to describe the plans for ensuring that the product built matches the requirements or specifications. This document will contain details of the outputs and processes the team will follow to demonstrate that what was developed meets the requirements set forth in the project plans. This document will also demonstrate how to prove what was built is what was planned to be built and should include the following:

 

  • Validation & Verification Methods
  • Validation & Verification Data
  • Validation & Verification Independence
  • Validation & Verification Environment
  • Organizational Responsibilities

 

Hardware Configuration Management Plan (HCMP)

 

This document provides a Configuration Management plan for the hardware item to initiate and maintain hardware configuration identification, hardware configuration control, hardware configuration status, accounting records, and hardware configuration audits of hardware and software, including support hardware. This plan makes possible systematic and traceable control of changes throughout the product life cycle. The Hardware Configuration Management (HCM) process is outlined in this HCMP. HCM activities include configuration identification, change control, baseline establishment in the Hardware Library, and archiving of hardware lifecycle data. The plan also addresses the method of storage, handling, and delivery of project media, configuration status accounting, and configuration audits. Below are the items that should be included within this document.

 

  • Hardware Configuration Management Methods
  • Hardware Baselines
  • Problem Reporting and Resolution
  • Change Control
  • Storage and Retrieval
  • Environment Control
  • Configuration Management Tools

 

Hardware Process Assurance Plan (HPAP)

 

The purpose of this document is to address the methods and activities to be used for Quality and Process Assurance. The Hardware Development Process of the hardware item occurs correctly according to policies and procedures set forth by this plan, all project plans, and all quality policies and procedures. The items below should be included within this plan.

 

  • Process Control
  • Organizational Responsibilities
  • Conformance
  • Process Assurance Activities
  • Deviations

 

Hardware Requirements, Design & Implementation Standards (HRDIS)

 

The purpose the Hardware Requirements, Design, and Implementation Standards is to establish a set of methods, rules, and tools that will be used in the development of the hardware item to promote consistency among processes, outputs, and artifacts. These standards will provide the constraints necessary to enforce clarity and consistency between developers and streamline the activities associated with requirements, design, and code development, validation, and verification throughout the hardware lifecycle to prevent errors that could cause safety issues, schedule impact, and budget overruns.