Length: 2 Days
DO-254 Training: Avionics Hardware
DO-254 Design Assurance for Airborne Electronic Hardware is the go-to guideline for manufacturing airborne electronic hardware.
Although it is often considered the ‘Little Sibling’ counterpart to the DO-178C, it is no less complex. DO-254 kicks off with a classification system that allows you to separate electronic hardware items into simple or complex categories, and then provides systematic design guidelines for both.
DO-254 is similar again to DO-178C in that it uses a Design Assurance Level (DAL) framework as well. DO-254 uses a range of 5 levels too, ranging from A-E, with the most severe being A and the least impactful being E.
Conceptually speaking, this standard applies to all electronics in anything that flies or could crash and pose a hazard to the public.
While D0-254 is a bit complicated, there is a logical base on which its configured. For example, based on their safety criticality, different parts of the aircraft are designated different Design Assurance Levels, or DALs for short. A system that is highly critical will receive a higher DAL, with DAL A reserved for the most critical systems.
This criticality is determined by a safety assessment of the aircraft and interacting systems to determine the required target failure rate. For DO-254, the difference between meeting DAL A and DAL B is minimal, so they are frequently referred to as “DAL A/B.”
Planning is a critical piece of the DO-254 certification.
It’s very important to document project flow up-front and approach your certification official to gain their approval early in the project. Typically the high-level plans are documented in the Plan for Hardware Aspects of Certification (PHAC—commonly pronounced as “pea-hack”). This plan should include all aspects of your project and how you will meet the DO-254 requirements.
Before DO-254, avionics software was governed by DO-178B, but equally complex, silicon-based logic or firmware, was unregulated.
In the early years, because many players considered DO-254 too oppressive, the standard was evaded or ignored. Finally, in 2005, the FAA mandated DO-254.
Of course, DO-254 does have its critics. In reality, DO-254 compliance can be a lengthy and expensive process, so it’s no wonder that some working in avionics development wonder what the point is.
However, experts in this area say that if you are prepared with the right information, processes and tools, DO-254 compliance can be extremely beneficial for your organization. First of all, this level of airborne systems compliance helps you create products that put passenger, crew and operator safety first.
It also strengthens the health of your organizational business practices, which can be helpful in many different areas. Additionally, DO-254 gives your organization a competitive edge as some projects require DO-178C/DO-254 compliance capabilities, and you will have an advantage compared to other manufacturers and developers who don’t offer it.
DO-254 Training: Avionics Hardware Course Description
DO-254 Training: Avionics Hardware discusses various angles of DO-254 guideline and will help you develop and implement this standard in your organization.
DO-254, aka Eurocae ED-80, is an official avionics guideline, which demonstrates strategies of design assurance associated with airborne electronic hardware. DO-254 covers the required information comprehensively from the conceptual design, through planning, designating, executing, verifying, to validation. It also contains DO-254 Tool Qualification considerations. Presently, it is mandatory for most avionics projects to comply with a DO-254 certification. DO-254 training will help you fully learn all of these steps to execute in your own organization.
DO-254 Tool Qualification
Developing hardware demands using several tools including the tools for design, implementation, synthesis, simulation, libraries, verification, and physical coverage. DO-254 tool qualification relates to developing and verifying such tools. Various qualification requirements pertain to each, while most tools do NOT need to be qualified. But if necessary or mandated, DO-254 tool qualification uses a subset of DO-254. DO-254 training will also cover this part of the DO-254 guideline to ensure you are able to apply DO-254 Tool Qualification procedure when required.
TONEX DO-254 Training Format
This training course is mostly practical. The most majority of the course is dedicated to labs, individual/group class activities, and hands-on workshops. Once the participants receive all the required theories and concepts through presentations, they immediately experience what they are taught with real-world projects and case studies.
DO-254 training: Avionic Hardware is a 2-day course designed for:
- Project managers
- Hardware engineers
- Systems engineers
- Process managers
- Design engineers
- Testing engineers
- Quality assurance engineers and managers
- All professionals involved with the projects that require DO-254 certification.
Upon the completion of DO-254 training: Avionic Hardware, the attendees are able to:
- Understand the DO-254 and how it works
- Understand and execute design assurance level
- Apply PLDs in avionics
- Discuss the regulatory conditions
- Understand the background DO-254
- Explain the Hardware Management strategies and standards
- Explain the plan for hardware features of certification
- Understand the requirements
- Provide the requirements
- Understand COTS & IP cores
- Conduct the classic design process
- Explain RTCA/DO-254 design process considerations
- Apply design assurance via design practice
- Execute verification and validation
- Apply RTCA/DO-254 to complex electronic circuits
- Produce recommendations
- Develop, arrange and optimize requirements for verification
- Facilitate the verification process so that it would be less difficult, less costly, less time consuming
- Elaborate the differences of requirements and design
- Conduct elemental analysis consistent with RTCA/DO-254
- Express relevant functions
Overview of DO-254 Avionic Hardware
- DO-254 description
- RTCA/DO-254 background
- DO-254 evolutional path
- Terminology and definitions
- Applicable documents
Lifecycle of Designing Hardware
- Personnel roles and responsibilities
- How processes and activities are related
- Process sequencing
- Internal correlation between processes
- Feedback tools
- Feedback procedure
- Iterative development model
- Problem reporting techniques
- Traceability of reviews and evaluation outcomes
- Planning process
- Configuration management
- Process assurance actions
- Certification liaison
- Flow diagrams development
- Requirements apprehension
- Conceptual design development
- Detail design development
- Testing process
- Assembly transition process
Configuration Management Planning (CMP)
- Preparing for CMP
- Identifying configuration
- Defining the baselines and traceability
- Configuration status
- Reporting problems, tracking them, and developing corrective actions plan to solve them
- Change management and change review
Hardware Design Environment
- Hardware design techniques
- Programming languages
- Development environment
- Development tools
- Management tools
- Testing tools
- Tools hardware stage(s)
- Hardware design data
- Trace data
- Lifecycle of producing and regulating the hardware data
- Lifecycle of submitting the hardware data
- Hardware regulatory categories
- Recycling and reusing the previously developed hardware
- Commercial-Off-The-Shelf (COTS) elements
- SH-1 Issue paper
- Safety concerns
- Design assurance concerns
- Contractors, sub-tier vendors and off-shore facilities
- Changes to plans
TONEX Hands-On Workshop Sample
Assume that you have a client that is a principal aerospace provider located in the USA. Their goal is to design a system that links aircraft with ground-based channels. They hire you to execute DO-254 advanced verification methodology in order to confirm their FPGA design in time for the product release.
- Develop Constrained Random Verification (CRV) method for verifying FPGA design
- Design and develop a reusable structure to facilitate changes in requirements
- Verify the requirements
- Consider EASA robustness specifications
- Discuss which tools you are going to use
- Apply all the DO-254 steps
DO-254 Training: Avionics Hardware