Date: available upon request

Languages: English or German

ISO 26262 provides an internationally recognized reference for the development of safety-related automotive E/E systems. Developers of such systems need to understand and implement the standard’s requirements pertaining to system, hardware, and software development. This 2-day training workshop provides a systematic introduction to key concepts of ISO 26262 and their practical application, covering the concept phase including hazard analysis and risk assessment (HARA) as well as the subsequent system, hardware, and software development phases.

Agenda

Target audience

Automotive professionals (component and system engineers, engineering managers, quality and project managers) involved with the development of safety-related automotive E/E systems, future functional safety engineers and managers.

Conditions of Participation and Cost

This training workshop is available upon request in English or in German.
For company-specific adaptations to the agenda, quotations, or questions, please do not hesitate to contact Oliver Collmann (oliver.collmann@model-engineers.com).

Highlights

  • Safety 101 (harm, risk, risk reduction, fault, error, failure, hazard, failure classification)
  • Scope of ISO 26262 (safety, functional safety, safety of the intended function)
  • Item definition and hazard analysis and risk assessment (HARA), ASIL determination
  • Refinement of safety requirements (safety goals, functional safety concept, technical safety concept, hardware safety requirements, software safety requirements, ASIL decomposition)
  • Fundamentals of system, hardware, and software development in compliance with ISO 26262
  • OEM – supplier relationships (development interface agreement, workshare)
  • Functional safety management (safety plan, safety case, confirmation measures)

Speaker

Dr. Mirko Conrad

Mirko Conrad serves as Managing Director of samoconsult GmbH, an engineering and consulting firm recognized across industries for their comprehensive services in the area of functional safety. He lectures in functional safety at the Technical Universities in Munich and Dresden and actively participated in the standardization of ISO 26262, DO-178C and various MISRA guidelines. Mirko Conrad also has 10+ years of tool classification/qualification experience across industries and standards.

 

AGENDA - DAY 1

TIME TOPIC
10 a.m. Welcome and introduction round
10:30 a.m. Safety fundamentals
  • Intuitive notion of safety, harm, risk, and risk reduction
  • How systems fail (faults, errors, failures, hazards)
  • Systematic vs. random faults/failures
  • Failures in hardware/software
  • Dependent vs. independent failures
  • Safety, functional safety, safety of the intended functionality (SOTIF)
  • 11:30 a.m. ISO 26262 - Introduction
  • Technical standards and standardization process
  • Functional safety standards (IEC 61508 and derivative standards)
  • ISO 26262 overview
  • Scope of ISO 26262
  • ISO 26262 Safety Life Cycle
  • 12:30 p.m. Lunch break and open dialog
    1:30 p.m. ISO 26262 – Concept phase
  • Item definition
  • Hazard analysis and risk assessment (HARA), determination of Automotive Safety Integrity Levels (ASIL)
  • Safety goal determination
  • Functional safety requirements/functional safety concept (FSC)
  • ASIL decomposition
  • Management of safety requirements
  • 3 p.m. ISO 26262 – System development (I)
  • Technical safety requirements/technical safety concept (TSC)
  • Hardware Software Interface (HSI)
  • Confidence in the use of software tools (tool classification and qualification)
  • 5 p.m. End of day

    AGENDA - DAY 2

    TIME TOPIC
    9 a.m. ISO 26262 – Hardware development
  • Hardware safety requirements
  • Hardware design
  • Classification of hardware failures, hardware architectural metrics, diagnostic coverage
  • Hardware integration and testing
  • 11 a.m. ISO 26262 – Software development
  • Software safety life cycle
  • Software safety requirements
  • Software design
  • Software implementation
  • Software integration and testing
  • Verification of software safety requirements
  • 12 p.m. Lunch break and open dialog
    1 p.m. ISO 26262 – System development (II)
  • Hardware software integration and testing
  • Safety validation
  • Safety case, release for production
  • 3 p.m. ISO 26262 – Functional safety management
  • Development categories (new item development vs. modification)
  • Confirmation measures (confirmation reviews, safety audit, safety assessment)
  • 4 p.m. ISO 26262 – Special topics
  • Development Interface Agreement (DIA), workshare between OEMs and suppliers
  • Confidence in the use of software tools (tool classification and qualification)
  • 5 p.m. End of training workshop