ISO 26262 Product Development at the Hardware Level Certification

Course Duration: 5 Days - 8 Hours/day

This five-day seminar is intended to enable participants to understand how functional safety applies to new product development at the hardware level. The course combines presentations with hands-on work and is conducted in English. There is an optional ISO 26262 Certification exam at the end of the class for those wanting to demonstrate and document their knowledge.

This course combines presentations, along with in-class group exercises to put what you are learning into practice. Concepts are reinforced by a running case study of a LIDAR case study and developed around a Hardware Product.

Learning Objectives

  • Tailor the necessary activities to support automotive safety lifecycle management, development, production, operation, service and decommissioning with a focus on hardware development including semiconductors
  • Understand the integration of ISO 26262 with APQP and IATF 16949
  • Understand functional safety aspects of the entire development process (requirements specification, design, implementation, integration, verification, validation and configuration)
  • Understand the automotive-specific risk-based approach for determining risk classes Automotive Safety Integrity Levels (ASILs)
  • Use ASILs for specifying the necessary safety requirements for achieving an acceptable residual risk
  • Provide requirements for validation and confirmation measures to ensure a sufficient and acceptable level of safety is being achieved

Course Outline

Daily Agenda (approximate, based on class discussions)

Day One

  • Chapter 1: Introduction and Overview to ISO 26262
  • ISO 26262 Purpose, Scope and Framework
  • Chapter 2: Management of Functional Safety (Part 2)
  • Overall Management, Project Management and After Release Management
  • Impact Analysis
  • Confirmation Measures
  • Breakout Exercise 1: Safety Case
  • Chapter 3: Production and Operation (Part 7)
  • Chapter 4: Safety Element out of Context (Part 10)
  • Chapter 5: Concept Phase (Part 3)
  • Item Definition
  • Breakout Exercise 2: Item Definition
  • Hazard Analysis
  • Breakout Exercise 3: Hazard and Risk Analysis (ASIL Determination)
  • Safety Requirements
  • Breakout Exercise 4: Functional Safety Requirements and Concept

Day Two

  • Chapter 6: ASIL-Oriented and Safety-Oriented Analysis
  • ASIL Decomposition Case Study
  • Safety Analysis in ISO 26262
  • Chapter 7: System Level Development (Part 4)
  • Technical Safety Concept
  • Safety Tactics
  • Hardware-Software Interface
  • Breakout Exercise 5: Technical Safety Requirements - Hardware
  • Chapter 8: Hardware Level Development (Part 5)
  • Initiation of Product Development at the Hardware Level
  • Specification of Hardware Safety Requirements
  • Hardware Detailed Design
  • Diagnostic Coverage Analysis Methodology
  • Breakout Exercise 6: Conducting Safety Analysis and Hardware Metrics

Day Three

  • Chapter 9: Evaluation of Hardware Elements (Part 8)
  • Evaluation of Hardware Elements
  • Proven Use in Argumentation
  • Interfaces Within Distributed Developments
  • Chapter 10: Hardware Level Development (Part 5 continued)
  • Chapter 11: Guidelines on Application of ISO 26262 to Semiconductors (Part 11)
  • Specific Semiconductor Technologies and Use Cases
  • Digital Components and Memories
  • Analogue/Mixed Signal Components
  • Programmable Logic Devices
  • Multi-core Components
  • Sensors and Transducers
  • Analysis of HW Design
  • Qualitative and Quantitative Analysis of Digital Component
  • Notes About Safety Analysis
  • Implications for Multi-core Components
  • Safety Analysis for Sensors and Transducers

Day Four

  • Chapter 12: Software Level Development (Part 6)
  • Interface with Hardware in Part 11
  • Qualification of Software Components
  • Breakout Exercise 7: Technical Safety Requirements - Software
  • Chapter 13: System Level Development (Part 4 continued)
  • Integration and Testing
  • Hardware-Software Integration
  • Safety Validation
  • Breakout Exercise 8: Safety Case and Assessment

Day Five

  • Chapter 14: Supporting Processes (Part 8)
  • Distributed Development
  • Specification and Management of Safety Requirements
  • Configuration Management
  • Change Management
  • Verification
  • Documentation Management System
  • Qualification of Software Tools
  • Qualification of Software Components
  • Evaluation of Hardware Elements
  • Chapter 15: ISO 26262 Implementation Strategy

Optional ISO 26262 Certification Exam - Final 3 hours of Day Five

Three Levels of Certification

Level 1

Functional Safety Engineer Provisional (FSEP)

Knowledge Requirements:

  • One week of Functional Safety Training and pass the ISO 26262 Certification exam.


  • At least three years of relevant professional experience, an engineering degree or work experience equivalency with degree.

Level 2

Functional Safety Engineer (FSE)

Knowledge Requirements:

  • One week of Functional Safety Training and pass the ISO 26262 Certification exam.


  • Submit a case study demonstrating experience in Functional Safety that can be verified. The case study should demonstrate a broad understanding from Safety Plan to Safety Case (work products).
  • Interview with an Omnex Functional Safety Expert.
  • At least five years of relevant industry experience.

Level 3

Functional Safety Expert (FSX)

Knowledge Requirements:

  • One week of Functional Safety Training and pass the ISO 26262 Certification exam


  • Submit two case studies demonstrating the ability to conduct confirmation reviews, evidence of communication and a broad understanding from Safety Plan to Safety Case.
  • Interview with an Omnex Functional Safety Expert.
  • At least five years of relevant industry experience.

Who Should Attend

Those involved or planning to be involved with the design and development of products in the Semiconductor Industry. Common titles of attendees include E/E & H/W Project Managers, HW Developers, Hardware Design Engineers, Systems Engineers and Functional Safety Engineers, or similar titles.

Participants should be, or plan to be, actively managing, or involved in, or aware of electrical and/or electronic items, systems, or elements that are incorporated in motor vehicles. Participants should also have the abilities, education, and experience required for the above roles.

Course Materials

Each participant will receive a seminar manual including case studies.

Note: Omnex does not provide copies of standard(s) during training courses, but clients are encouraged to have their own copy.


Attendees should have a working knowledge of their organization’s New Product Development Process.

Upcoming Training