Professional Documents
Culture Documents
Avionic Systems Engineering Crash Course
Avionic Systems Engineering Crash Course
tonex.com/training-courses/avionic-systems-engineering-crash-course
Length: 4 Days
However, the sophistication and sheer number of these components have made system-
level avionics engineering an increasingly difficult challenge.
Avionic systems engineering is also all about understanding and meeting numerous
regulatory operating systems protocols, including ARINC 653, ARINC 429, CAN, and
ARINC 664.
1/11
Creating a well-integrated, robust systems architecture requires engineers to generate an
Interface Control Document (ICD), which is a large spreadsheet that gathers data and
inputs from multiple avionics system suppliers.
An ICD in avionic systems engineering also needs to accurately reflect all system
components interactions and interdependencies, including hardware and software
redundancies, messaging hierarchies, data inputs, and numerous communication
switches.
Since system integration is one of the final tasks that must be completed before a new
aircraft is launched, avionics engineers are typically under pressure to generate an ICD
quickly without sacrificing quality or reliability.
Analysts in this sector predict that future avionics systems will be making much greater
use of sensor data to increase their situational awareness and ability to make accurate
decisions quickly.
This will mean that developers will have to think more carefully about how they connect to
these sensors, the bandwidth of the interconnect schemes they specify, and the physical
ruggedness of their implementation. This could see a shift to the use of two-wire Ethernet
implementations, fibre-optic systems, and denser/lighter traditional interconnect
strategies.
Avionics developers will also need to think about how to provide the computing power
necessary to capture, fuse and interpret this data, which may lead to an exploration of
alternate computing architectures such as machine-learning coprocessors, to handle
pattern recognition tasks efficiently and at low energy cost.
Tonex Avionic Systems Engineering Crash Course is fun and dynamic. Lectures are
delivered in the format of interactive presentations. Once the theoretical part of the
training is finished, you will practice the taught concepts and theories with real-world
examples to ensure you have completely learned all the topics.
Audience
Design engineers
Manufacture engineers and managers
Support engineers
Application engineers
2/11
Systems engineers
Safety engineers
Software/hardware engineers
Quality assurance or certification personnel
All other professional engineers and managers involved in avionic systems onto air-
vehicles
Training Objectives
Upon the completion of Avionic Systems Engineering Crash Course, attendees are able
to:
Understand and explain how avionic systems and its components work
Describe and evaluate the basic performance requirements and essential
components of all the main avionic systems to be found in modern civil and military
air-vehicles
Understand the criteria for and derive the functionality of avionic system elements
within the fully integrated “systems of systems”
Formulate and incorporate avionic systems from requirements definition, through
concept development to final execution within their operating role
Understand and use the architectural rules and the design process to be used to
certificate safe and reliable avionic systems
Explain avionic certifications
Advanced systems
System design and development
Understand and implement DO-178C, DO-254 requirements
Understand various data bus systems
Course Outline
3/11
Emergency systems
Rotary wing systems
Military radar systems
Software Considerations in Airborne Systems and Equipment Certification
Software certification standard for airborne systems on commercial aircraft
Various software life cycle processes
Guidelines for Development of Civil Aircraft and Systems: ARP4754A
RTCA DO-178/C / EUROCAE ED-12B/C
DO-178C: Software Considerations in Airborne Systems and Equipment
Certification
4/11
Military Aircraft Implementation
Interrelationship of flight control, guidance and flight management
Engine/airframe interfaces
Engine technology and principles of operation
The control problem
Engine indications
Engine oil systems
Engine off takes
Reverse thrust
Engine control on modern civil aircraft
Fuel Systems
Hydraulic Systems
Electrical Systems
5/11
Electrical power evolution
Aircraft electrical system
Power generation
Primary power distribution
Power conversion and energy storage
Secondary power distribution
Typical aircraft dc system
Typical civil transport electrical system
Electrical loads
Emergency power generation
Recent systems developments
Electrical Load Management System (ELMS)
Variable Speed Constant Frequency (VSCF)
VDC Systems
More-Electric Aircraft (MEA) 227
Recent electrical system developments
Electrical systems displays
MIL-STD-1553
MIL-STD-1760
MIL-STD-1773
Pneumatic Systems
Emergency Systems
6/11
Warning systems
Fire detection and suppression
Emergency power sources
Explosion suppression
Emergency oxygen
Passenger evacuation
Crew escape
Computer-controlled seats
Ejection system timing
High speed escape
Crash recorder
Crash switch
Emergency landing
Emergency system testing
Advanced Systems
7/11
Systems analysis and design
Development processes
System design
Key agencies and documentation
Design guidelines and certification
Techniques
Key elements of the development process
Major safety processes
Functional Hazard Analysis (FHA)
Preliminary System Safety Analysis (PSSA)
System Safety Analysis (SSA)
Common Cause Analysis (CCA)
Requirements capture
Top-down approach
Bottom-up approach
Fault Tree Analysis (FTA)
Dependency diagram
Failure Modes and Effects Analysis (FMEA)
DFMEA and PFMEA applied
FMECA and FTA
Component reliability
Analytical methods
In-service data
Dispatch reliability
Markov analysis
Reliability and safety engineering
Development processes
The product life cycle
Concept phase
Definition phase
Design phase
Build phase
Test phase (qualification phase)
Operate phase
Disposal or refurbish
Development program
‘V’ diagram
Extended Operations (ETOPS)
Avionics Technology
8/11
The nature of microelectronic devices
Processors
Memory devices
Digital data buses
A 429 data bus
MIL-STD-1553B
ARINC 629 data bus
COTS data buses
Data bus integration of aircraft systems
COTS data buses – IEEE 1394 468
Fiber optic buses
Avionics packaging standards
Typical LRU architecture
Integrated modular avionics
Military Avionics
Military communications
Radar
Sonar
Electro-Optics
ESM/DAS
Aircraft networks
9/11
DO-178/DO-254 certification process
DO-178/DO-254 project planning and management
DO-178/DO-254 master plan
DO-178/DO-254 need analysis and requirements
Software life cycle processes
Software life cycle definition
Transition criteria between processes
Software development plan
Software life cycle environment planning
Software development standards
Review of the software planning process software considerations in System life
cycle processes
System considerations in software life cycle processes
Software plan development and certification
Software development, design, coding and testing techniques
DO-178C criticality levels
Software design, testing, verification and validation processes
Software planning process objectives
Software planning process activities
Software plans
Plan for Software Aspects of Certification (PSAC)
Software Quality Assurance Planning (SQAP)
Software Configuration Management Planning (SCMP)
Software Development Planning (SDP)
Requirements, design, code, and integration
Software Verification Planning (SVP)
Reviews, tests, and analysis
Programmable hardware plan development and certification
Software and programmable hardware verification and validation
Recommended templates and recommendations
Hardware design life cycle
Tool qualification
Cost estimation and metrics
Software aspects of certification
Compliance determination
DO-254 compliance
System safety and Design Assurance Level (DAL)
Application of DO-254 by EASA and FAA
DO-254 hardware design life cycle objectives and data
Integral/supporting processes
Validation and verification
Configuration management
10/11
Process assurance
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
--
11/11