CERTIFIED TRAINING

March 12, 2019
March 13, 2019

Munich

MOC Event Center Lilienthalallee 40 80939 Munich Germany

Optimizing DO-178C/DO-254 Avionics Software & Hardware Development Guidelines

Optimizing DO-178C/DO-254 Avionics Software & Hardware Development Guidelines

Tuesday 12th March

11am – 5.30pm

Register Today >>

In this fast-paced AEE course, experienced avionics engineers learn how to optimize DO-178C & DO-254 to real avionics. Not just theory, but practical examples to develop better compliance with DO-178C (ED-12C) and DO-254 (ED-80).

Software/Hardware development has rapidly evolved and interpretations of DO-178C/DO-254 have likewise changed. Attendees learn the latest rules including advanced software/hardware certification, EASA and CAST issue papers, trends in future avionics development, and much more as summarized below.

KEY FEATURES:
• Quick refresher on basic DO-178C & DO-254 and “how” they are applied to advanced avionics
• Advanced Safety, Derived Requirements, and Detailed Hardware/Software Requirements
• Understanding advanced DO-178C/254 mistakes and best practices to avoid them including model based development, OOT, and C++
• Multi-Core Processing usage and compliance
• Model-Based Development rules and best practices
• Applying new forthcoming A(M)C 20-152A
• Understanding new mandatory ARP4754A and forthcoming ARP4761A for Systems & Safety.
• Controlling engineering cost/risks with better DO-178C & DO-254 Requirements, Design, and Logic
• Understanding & applying the DO-178C & DO-254 Supplements for:
– DO-330/ED-215 Software Tool Qualification
– DO-331/ED-216 Model-Based Development and Verification
– DO-332/ED-217 Object-Oriented Technology
– DO-333/ED-218 Formal Methods Supplement

WHO SHOULD ATTEND:
Attendees may include engineers, managers, quality assurance or certification personnel with previous knowledge, training, or experience in DO-178 or DO-254; if no experience, we will send basic training materials in advance to peruse.

The Emerging & Required DO-326/ED-202 Set: Aviation-Cyber-Security Regulation for Safety – Guide for the Perplexed 

The Emerging & Required DO-326/ED-202 Set: Aviation-Cyber-Security Regulation for Safety – Guide for the Perplexed

Tuesday 12th March 2019
11am-5.30pm

Register Today >>

Aviation Security: understanding what is required for new avionics/aircraft development and operations via the new mandatory DO-326A/ED-202A documents. In this introductory “Guide for the Perplexed”, attendees will get a crash-course on the new “DO-326/ED-202 ecosystem” of emerging regulation.

The DO-326A/ED-202A set of documents is all about the mitigation of the aviation/aircraft safety effects of “Intentional Unauthorized Electronic Interaction (IUEI)”, a.k.a. “Cyber Threats”, and which were explicitly excluded from the classic DO-178/ED-12/ARP4754 set.

DO-326A/ED-202A & DO-356A/ED-203A focus upon type certification during the first three phases of an aircraft (including avionics) type: 1) Initiation, 2) Development or Acquisition, and 3) Implementation. Their companions DO-355/ED-204 focus upon security for continued airworthiness.
DO-326A/ED-202A currently has 3 (three) companion documents: ED-201, DO-355/ED-204 and DO-356A / ED-203A, and a few more planned. DO-326A / ED202A provide requirements and objectives in a similar fashion to DO-178C, DO-254, and ARP4754A; while the DO-326A guidance is just that, certification authorities increasingly assess DO-326A compliance as added requirements for aviation suppliers.

The DO-326A/ED-202A set currently applies to fixed-wing aircraft (Part 25), with clear FAA recommendations for the adaptation/tailoring of DO-326A/ED-202A for general aviation (Part 23),rotorcraft (Parts 27 and 29), engines (Part 33) and propellers (Part 35), and clear indications of it will increasingly being applied to these other aircraft including military beginning in 2022 or thereafter.

KEY FEATURES:
• Top-level acquaintance with Information/”Cyber” security in general
• Cybersecurity aspects of OT/ICAS
• Aviation as a unique Cybersecurity case
• Origins of Cybersecurity standards & regulation
• The road to ED-202/DO-326: “Security as a Safety Aspect”
• The development process of the entire “ED-202/DO-326 set”, rationale behind the documents & relations with the “DO-178/ED-12 set”
• Initial acquaintance with the documents:
– ED-201: Aeronautical Information System Security (AISS) Framework Guidance
– DO-326A/ED-202A: Airworthiness Security Process Specification
– DO-356A/ED-203A: Airworthiness Security Methods and Considerations
– DO-355/ED-204: Information Security Guidance for Continuing Airworthiness
– ED-205: Process Standard for Security Certification/Declaration of Air Traffic Management/Air Navigation Services (ATM/ANS) Ground Systems
– Planned new/revised documents

• Where does current regulation stand
• Where do we go from here – the expected regulatory landscape for the next years

WHO IS IT FOR:
Attendees may include all levels of aviation, aircraft, and avionics developers who must understand and comply with the new Security rules.

Applying the New Mandatory Aviation Systems/Safety Regulations: ARP4754A (with ARP4761/A)

Applying the New Mandatory Aviation Systems/Safety Regulations: ARP4754A (with ARP4761/A)

Wednesday 13th March

9.30am-4.30pm

Register Today >>

The now nearly-mandatory SAE-ARP4754A provides guidance for the development of aircraft and aircraft systems while taking into account the overall aircraft operating environment and functions. ARP4754 was long “suggested” for commercial avionics; the new ARP4754A is now required and increasingly mandatory for all avionics/avionics including worldwide militaries and UAV’s.. ARP-754A is commonly called “DO-178 for Aviation Systems”, but it’s really much different: ARP4754A requires detailed Safety processes (ARP4761/A) with FHA, PSSA, and SSA’s to determine then prove design, architecture, and safety features. ARP4754A also requires detailed data, systems-level planning, traceability, V&V and tight configuration management. While bearing some semblance to DO-178C/Do-254, ARP4754A really covers the Avionics Development Ecosystem and is a mandatory foundation – it must come BEFORE hardware and software but be continually addressed during development. This course is for those avionics engineers wanting to understand and apply better ARP4754A compliance.

KEY FEATURES:
• How ARP4754A fits into the Avionics Development Ecosystem including ARP4761A, DO-178C, and DO-254
• Avionics Safety Assessments: FHA, PSSA, and SSA
• Differences between ARP4754 and ARP4754A
• ARP4754A Planning – what is really required
• Aviation Safety: what is required for ARP4754A
• Handling Derived and Safety Requirements per ARP4754A
• System Requirements – What, Where, Why, and How
• Planning, Development, and Traceability Processes for Systems
• ARP4754A Documentation
• ARP4754A Verification & Validation
• ARP4754A Best Practices & Common Mistakes

WHO SHOULD ATTEND:
Attendees may include aviation engineers, managers, safety engineers, systems engineers, or hardware/software engineers. A basic understanding of engineering processes and aircraft/avionics systems is helpful but not required.

INTERESTED IN BOOTHS OR SPONSORSHIP?

INTERESTED IN BOOTHS OR SPONSORSHIP?