Length: 2 Days
Print Friendly, PDF & Email

DO-254 Training by Tonex

DO-254 Training by Tonex

DO-254 is a two-day training class that provides a good overview and application of DO-254 as defined by current FAA and EUROCAE ED-12C / ED-109A guidance. Students will learn current FAA and EASA guidance on the application of DO-254 in airborne systems.

DO-254 Training covers principals, objectives, and guidance for design assurance of airborne electronic hardware based on RTCA DO-254/Eurocae ED-80 standards. Do-254 Training covers all aspects of airborne electronic hardware from conception through initial certification and subsequent post certification product improvements to ensure continued airworthiness. Get familiar with DO-254 defines objectives which must be met by avionics equipment manufacturers according to EASA and FAA guidelines.

DO-254 training also covers objectives of RTCA DO-254 five levels of criticality from level A (highest) to level E (lowest). These design assurance levels are required for all civil airborne electronic hardware. Learn also how military airborne applications such as A400M are now requiring DO-254 compliance.

DO-254 training is intended to help aircraft manufacturers and the suppliers of aircraft electronic systems techniques on how to assure that electronic airborne equipment safely performs its intended function. The DO-254 training clarifies design life cycle processes for hardware that includes line replaceable units, circuit board assemblies, application specific integrated circuits (ASICs), programmable logic devices, etc. It also characterizes the objective of the design life cycle processes and offers a means of complying with DO-254 certification requirements.

Learn more about:

  • DO-254 Requirements Capture
  • DO-254 Conceptual Design
  • DO-254 Detailed Design
  • DO-254 Implementation and Production Transition
  • DO-254 Verification and Validation

For DO-254, requirements must drive the design and verification activities, and requirements traceability helps to ensure this.

The DO-254 guidance outlines complex custom micro-coded devices such as PLDs, FPGAs and ASICs used in commercial airborne hardware subject to a stringent development process.

What this means is that the design and verification activities for these types of devices must follow the requirements-based development process described in DO-254.

The primary purpose of DO-254 is to provide assurance that the device under test meets its intended functions under all foreseeable operating conditions. Requirements express the functions of the device under test, therefore must drive the design and verification activities.

Simply stated, DO-254 is a requirements-driven process-oriented safety standard used on commercial electronics that go into aircraft. Conceptually speaking, this standard applies to all electronics in anything that flies or could crash and pose a hazard to the public.

The DO-254 specification itself is only part of the story. There are additional supplemental papers that clarify, restrict and limit how the DO-254 specification is applied. In addition, there are follow-on papers created by other bodies such as the international Commercial Aviation Safety Team (CAST) and the European Aviation Safety Association (EASA), as well as additional regulations set by air framers such as Airbus and Boeing.

There are also a variety of commonly accepted industry practices expected by certification officials. A minimal understanding of these documents and their organization is important, as these papers limit the scope, and clarify details necessary to successfully complete a DO-254 project.

DO-254 enforces a strict requirements-driven process for the development of commercial airborne electronic hardware.

Published by RTCA, DO-254 was formally recognized by the FAA in 2005 via AC 20-152 as a means of compliance for the design assurance of electronic hardware in airborne systems.

For DO-254, requirements must drive the design and verification activities, and requirements traceability helps to ensure this.

The DO-254 guidance outlines complex custom micro-coded devices such as PLDs, FPGAs and ASICs used in commercial airborne hardware subject to a stringent development process.

What this means is that the design and verification activities for these types of devices must follow the requirements-based development process described in DO-254.

The primary purpose of DO-254 is to provide assurance that the device under test meets its intended functions under all foreseeable operating conditions. Requirements express the functions of the device under test, therefore must drive the design and verification activities.

Simply stated, DO-254 is a requirements-driven process-oriented safety standard used on commercial electronics that go into aircraft. Conceptually speaking, this standard applies to all electronics in anything that flies or could crash and pose a hazard to the public.

DO-254 training is a good idea because, in truth, understanding the DO-254 specification and how to achieve DO-254 approval is, unfortunately, not as simple as downloading and thoroughly reading the document.

The DO-254 specification itself is only part of the story. There are additional supplemental papers that clarify, restrict and limit how the DO-254 specification is applied. In addition, there are follow-on papers created by other bodies such as the international Commercial Aviation Safety Team (CAST) and the European Aviation Safety Association (EASA), as well as additional regulations set by air framers such as Airbus and Boeing.

There are also a variety of commonly accepted industry practices expected by certification officials. A minimal understanding of these documents and their organization is important, as these papers limit the scope, and clarify details necessary to successfully complete a DO-254 project.

According to DO-254 experts, although it’s not explicitly detailed in the DO-254 specification, certification officials expect you to design your system to adequately handle a variety of nefarious conditions.

Learning Objectives

Upon Completion of the DO-254 Training, the attendees will learn:

  • How to write, organize and optimize requirements for verification.
  • How FAA Avionic certification works
  • Navigate and understand the RTCA/DO-254 document
  • Create Hardware Management Plans and Standards
  • Plan for Hardware Aspects of Certification
  • Understand DO-254 Hardware Requirements Apply the DO-254 lifecycle and supporting processes
  • Understand system safety assessments and the Design Assurance Level (DAL)
  • How DO-254 Compliance Works
  • How to work with DO-254 DAL
  • How to use PLDs in Avionics
  • Regulatory background and use of design assurance
  • CAST Papers
  • Understand Order 8110.105 & Job Aid
  • Set up a project correctly through proper planning
  • Follow the current guidance for DO-254 projects
  • Identify and avoid common pitfalls in DO-254 projects
  • Review and use the FAA AEH Job Aid
  • How to make verification less difficult, less expensive, less time consuming.
  • The difference between requirements and design.
  • How to perform Elemental Analysis according to RTCA/DO-254
  • The definition of a functional element.
  • How to express functions
  • Plan for Hardware Aspects of Certification (PHAC)
  • Appendix B for Levels A and B hardware

Who should attend ?

Program managers, Project managers, process managers, hardware engineers and designers, verification, and quality assurance engineers working on projects requiring DO-254 certification.

Course Agenda/Outline

Introduction to DO-254

  • DO-254 Hardware Design Lifecycle objectives and Data
  • Design Assurance of Airborne Electronic Hardware
  • System Safety and Design Assurance Level (DAL)
  • How to use the DO-254 Document
  • RTCA/DO-254 Design Process Considerations
  • Design Assurance Through Design Practice
  • Serial Line Data Receiver
  • Verification and Validation Considerations
  • Test Cases

Considerations for Application of RTCA/DO-254 to Complex Electronic Circuits

  • Elemental Analysis LRU Example
  • System Safety and DAL
  • Integral/supporting Processes
  • Validation and Verification
  • Configuration Management
  • Process Assurance
  • Certification Liaison
  • Additional Considerations
  • Tool Qualification
  • Previously Developed HW
  • COTs Cores and IPs
  • Single Event Upset and SRAM parts
  • Functional Failure Path (FFP)
  • Elemental analysis
  • Advanced Verification techniques
  • COTS & IP cores
  • Classic Design Process

Application of DO-254 by EASA and FAA

  • Additional documents defining application of DO-254
  • CRIs and Issue papers
  • Simple Vs. Complex Device
  • Additional documents defining application of DO-254
  • CRIs and Issue papers
  • Simple Vs. Complex Device
  • How to use the DO-254 Document
  • Planning Process
  • PHAC, HDP, HVP, HCMP, HQAP
  • Requirements, design and Code Standards
  • Hardware Design Process

System Aspects of Hardware Design Assurance 

  • System Development Process
  • Hardware Design Life Cycle Process
  • Information Flow from Hardware Design Life Cycle Process to System Development Process
  • Information Flow between Hardware Design Life Cycle Process and Software Life Cycle Process
  • System Safety Assessment Processes
  • Hardware Safety Assessment
  • Hardware Design Life Cycle Processes
  • Transition Criteria

FPGA Design Lifecycle and DO-254 

  • Principals
  • Traceability
  • Transition Criteria
  • Requirements
  • Conceptual Design
  • Detailed Design
  • Implementation
  • Production Transition
  • Integral/supporting Processes
  • Validation and Verification
  • Configuration Management and Process Assurance
  • Design Assurance Guidance for Airborne Electronic Hardware
  • what is DO-254 Compliance?
  • System Safety
  • Design Assurance Level (DAL)
  • Application of DO-254 by EASA and FAA
  • DO-254 Hardware Design Lifecycle objectives and Data
  • Tool Qualification
  • COTs Cores and IPs
  • Single Event Upset and SRAM parts
  • Functional Failure Path (FFP)
  • Elemental analysis
  • Advanced Verification techniques
  • Plan for Hardware Aspects of Certification (PHAC)
  • Requirements Capture
  • Conceptual Design
  • Detailed Design
  • Implementation and Production Transition
  • Verification and Validation

DO-254 Planning Processes

  • Planning Process Objectives
  • Planning Process Activities

 DO-254 Hardware Design Process

  • Requirements Capture Process
  • Conceptual Design Process
  • Detailed Design Process
  • Implementation Process
  • Production Transition Process
  • Acceptance Test
  • Series Production

DO-254 Hardware Design Lifecycle objectives and Data

  • Integral/supporting Processes
  • Validation and Verification
  • Configuration Management
  • Process Assurance
  • Certification Liaison

DO-254 V&V and CM Methods

  • Validation process
  • Verification Process
  • Validation and Verification Methods
  • Configuration Management
  • Configuration Management Activities
  • Data Control Categories
  • Process Assurance

DO-254 Hardware Design Life Cycle Data

  • Hardware Plans
  • Hardware Design Standards and Guidance
  • Validation and Verification Data
  • Hardware Acceptance Test Criteria
  • Problem Reports
  • Hardware Configuration Management Records
  • Hardware Process Assurance Records
  • Hardware Accomplishment Summary
  • Use of Previously Developed Hardware
  • Commercial-Off-The-Shelf (COTS) Components Usage
  • Product Service Experience
  • Tool Assessment and Qualification

Additional Considerations

  • Tool Qualification
  • Previously Developed HW
  • COTs Cores and IPs
  • Single Event Upset and SRAM parts
  • Functional Failure Path (FFP)
  • Elemental analysis
  • Advanced Verification techniques

DO-254 Data Items and Templates

  • Plan for Hardware Aspects of Certification (PHAC)
  • Hardware Design Plan
  • Hardware Validation Plan
  • Hardware Verification Plan (HVP)
  • Hardware Configuration Management Plan
  • Hardware Process Assurance Plan
  • Hardware Design Standards
  • Requirements Standards
  • Validation and Verification Standards
  • Hardware Archive Standards
  • Hardware Requirements
  • Conceptual Design Data
  • Detailed Design Data
  • Top-Level Drawing
  • Assembly Drawings
  • Installation Control Drawings
  • Hardware/Software Interface Data
  • Hardware Traceability Data
  • Hardware Review and Analysis Procedures
  • Hardware Review and Analysis Results
  • Hardware Test Procedures
  • Hardware Test Results
  • Hardware Acceptance Test Criteria
  • Problem Reports
  • Hardware Configuration Management Records
  • Hardware Process Assurance Records
  • Hardware Accomplishment Summary (HAS)

DO-254 Training

Request More Information

Please enter contact information followed by your questions, comments and/or request(s):
  • Please complete the following form and a Tonex Training Specialist will contact you as soon as is possible.

    * Indicates required fields

  • This field is for validation purposes and should be left unchanged.

Request More Information

  • Please complete the following form and a Tonex Training Specialist will contact you as soon as is possible.

    * Indicates required fields

  • This field is for validation purposes and should be left unchanged.