Visure Solutions


Support
Register
Login
Start Free Trial

DO-254 Audits & SOIs Preparations

DO-254 Audits & SOIs Preparations

Table of Contents

DO-254, the Design Assurance Guidance for Airborne Electronic Hardware, outlines the guidelines for the development of complex electronic hardware systems in airborne systems. The process involves extensive documentation and verification to ensure the safety and reliability of the hardware. This rigorous process requires the involvement of various stakeholders, including the developers, verification engineers, and auditors.

One crucial aspect of the DO-254 process is the audit, which involves a review of the hardware development process by an independent third party. The purpose of the audit is to ensure that the hardware has been developed in compliance with the DO-254 guidelines and that all requirements have been met. The audit process involves a review of the documentation and verification records, interviews with the developers and verification engineers, and an analysis of the development and verification process.

To prepare for an audit, it is essential to develop a comprehensive set of Standard Operating Procedures (SOPs) and a detailed audit plan. The SOPs should include all the necessary steps for the hardware development process, including requirements capture, design, verification, and validation. The audit plan should outline the scope of the audit, including the hardware to be audited, the audit team, and the audit schedule.

Another critical aspect of DO-254 compliance is the preparation of the SOI (Summary of Compliance). The SOI is a document that summarizes the compliance of the hardware with DO-254 guidelines. The SOI is prepared by the developers and submitted to the certification authorities, along with the hardware for certification. The SOI should include a detailed summary of the hardware development process, including the development and verification activities, as well as the compliance of the hardware with the DO-254 guidelines.

To prepare the SOI, the developers should ensure that all the required documentation is complete and up-to-date. The developers should also review the verification records to ensure that all requirements have been verified and that any non-compliances have been resolved. The SOI should also include a summary of the verification results, including any issues or concerns that were identified during the verification process.

It is essential to note that the audit and SOI preparation process should be integrated into the overall hardware development process. This integration ensures that the developers and verification engineers are aware of the audit requirements and are prepared to provide the necessary documentation and information during the audit process.

To ensure the success of the DO-254 compliance process, it is also essential to involve experienced DO-254 auditors and consultants. These experts can provide guidance and support throughout the development and verification process, as well as during the audit and SOI preparation process. Working with experienced auditors and consultants can help to ensure that the hardware development process is efficient and effective, and that the final hardware is compliant with the DO-254 guidelines.

In addition to the DO-254 guidelines, the aviation industry has also developed additional guidance for the audit and SOI preparation process. DO-331, the Model-Based Development and Verification Supplement to DO-178C and DO-278A, provides additional guidance for the development and verification of airborne software. DO-331 also provides guidance on the use of model-based development and verification tools and techniques.

The DO-331 guidance can be used in conjunction with the DO-254 guidelines to ensure the compliance of both hardware and software in airborne systems. The use of model-based development and verification tools and techniques can also improve the efficiency and effectiveness of the development and verification process, leading to reduced development time and costs.

Once the audit has been conducted, the next step is to prepare for the SOI (Summary of Compliance) submission. This document summarizes the DO-254 compliance efforts for the hardware design and demonstrates that the hardware has been developed in accordance with the DO-254 standard. The SOI submission is a critical step in the certification process and serves as a primary means for the certification authority to evaluate the DO-254 compliance efforts of the applicant.

To prepare for the SOI submission, it is important to ensure that all the necessary documentation is in order and up-to-date. This includes the hardware development plan, hardware requirements, hardware design, hardware verification, and configuration management plans, as well as the results of verification and validation activities. The applicant must also ensure that all processes have been followed as specified in the DO-254 standard, including the use of approved tools, and that all required documents have been properly reviewed and approved.

In addition to the documentation, the SOI submission should also include a summary of the safety assessment activities performed for the hardware design, as well as a summary of any issues that were identified during the verification and validation process and how they were resolved. The SOI should also include a statement of compliance that certifies that the hardware design is compliant with the DO-254 standard.

It is important to note that the SOI submission is not a one-time event. The certification authority may request additional information or clarification, which will require further documentation and testing. Therefore, it is critical to maintaining accurate and up-to-date records of all the DO-254 compliance efforts throughout the hardware development lifecycle.

Don’t forget to share this post!

Top

Automating End-to-End Traceability Coverage

June 13th, 2024

11 am EST | 5 pm CET | 8 am PST

Fernando Valera

Louis Arduin

CTO, Visure Solutions

Andreas Horn

Senior Manager, Vector Informatik

Gaining Full Requirements Traceability & Measuring Structural Coverage for Standard Certifications

Learn how traceability enhances transparency, mitigates risks, and ensures all project requirements are met.