Price: $1,899.00

Length: 2 Days
Print Friendly, PDF & Email

ISO 26262 Training: Automotive Safety

ISO 26262 mandates a functional safety development process that automotive OEMs and suppliers must follow and document to have their devices qualified to run inside commercial (passenger) vehicles.

ISO 26262 is a risk-based standard that’s derived from IEC 61508 and outlines a risk classification system (Automotive Safety Integrity Levels, or ASILs) and aims to reduce possible hazards caused by the malfunctioning behavior of electrical and electronic (E/E) systems.

A functional safety standard like ISO 26262 ensures that automotive components do what they’re supposed to do, precisely when they’re supposed to do it.

Adherence to ISO 26262 requires extensive documentation and testing, which can be extremely time-consuming. It requires that engineers first assess their design software for Tool Confidence Levels.

ISO 26262 is a derivative of IEC 61508, the generic functional safety standard for electrical and electronic (E/E) systems, and continues a trend of safety practices becoming more regulated as industries adopt a standardized set of practices for designing and testing products.

New safety standards are the result of increasing complexity throughout the automotive industry is resulting in increased efforts to provide safety-compliant systems.

For example, modern automobiles use by-wire systems such as throttle-by-wire. This is when the driver pushes on the accelerator and a sensor in the pedal sends a signal to an electronic control unit. This control unit analyzes several factors such as engine speed, vehicle speed and pedal position. It then relays a command to the throttle body. It is a challenge of the automotive industry to test and validate systems like throttle-by-wire. The goal of ISO 26262 is to provide a unifying safety standard for all automotive E/E systems.

The Draft International Standard (DIS) of ISO 26262 was published in June 2009. Since the publication of the draft, ISO 26262 has gained traction in the automotive industry. Because a public draft standard is available, lawyers treat ISO 26262 as the technical state of the art.

ISO 26262 was a much needed standard that provides multiple benefits to automotive original equipment manufacturers (OEMs) and suppliers, such as:

  • Demonstrate due diligence and ensure overall safety of the respective vehicle and/or the corresponding systems in compliance with ISO 26262
  • Maintain your competitive advantage in interpreting and implementing the ISO 26262 requirements correctly
  • Minimize the risk of harm to people and non-acceptance of your products by the market
  • Avoid costly product recalls and reputational damage due to safety hazards because insufficient safety assurance
  • Simplified access to global markets by ensuring compliance with relevant international regulations

ISO 26262 Training: Automotive Safety Course by Tonex

ISO 26262 Training: Automotive Safety helps you provide the requirements for ISO 26262 and be prepared for the release of ISO 26262. We will teach you how to develop your internal ISO 26262 , implement it, and audit your company’s performance internally.

ISO 26262 is a Functional Safety guideline, which is presently ongoing, known as “Road vehicles — Functional Safety”. It was issued to consider the difficulty of safety-relevant electrical and electronic (E/E) systems. However, it has challenging and difficult specifications hard to understand and implement.

ISO 26262 Training: Automotive Safety

ISO 26262 is an alteration of the Functional Safety standard IEC 61508 for the particulars of Automotive Electric/Electronic Systems. It is applied in the associated Safety Related Systems that contain one or more E/E systems that are installed in manufacturing passenger cars showing the mass weight up to 3,500 kg.

ISO 26262 is a guideline, modified from the Functional Safety Standard IEC 61508 for Automotive Electric / Electronic Systems, established because of significant increase of software incorporation into automotive systems and the likelihood of disastrous flaws. Electronic Systems and software incorporation are a mainly target of ISO 26262. The standard tries to consider failures, which are exclusive, cascading or usual origin in nature. To achieve this, ISO 26262 executes a process to make sure safety in the design of Electronic Systems incorporated into automotive uses.

Learn About:

  • H&R / HARA: Hazard analysis and risk assessment
  • FMEA: Failure mode and effects analysis
  • FTA: Fault tree analysis
  • ISO 26262 hardware architectural metrics
  • ISO 26262 software design, implementation, and safety
  • ISO 26262 functional safety management
  • Analysis of safety goal violations because of random hardware failures
  • DFA: Dependent failure analysis
  • DRBFM: Design review by failure modes

Tonex ISO 26262 Training: Automotive Safety focuses on the parts of ISO 26262 associated with safety (Part 2, Part 4, and Part 6). However, a comprehensive training, including all parts of the ISO 26262 is provided in the Automotive Functional Safety ISO 26262 Training Bootcamp.

Tonex ISO 26262 Training: Automotive Safety is a combination of interactive lectures and practical activities, including labs, group activities, and hands-on workshops. You are encouraged to bring your organizational project to work on, or you can simply use the real-world case studies provided by our instructors.

Audience

ISO 26262 Training: Automotive Safety is a 2-day course designed for:

  • System engineers
  • Software engineers
  • Hardware engineers
  • Managers
  • All individuals involved in creating and executing the systems, software and hardware in a motor vehicle.

Training Objectives

Upon the completion of ISO 26262 Training: Automotive Safety, the attendees are able to:

  • Understand the automotive safety
  • Adjust the required actions through the lifecycle stages
  • Understand all the functional safety perspectives of the whole development process
  • Implement all the aspects of the functional safety development process
  • Understand and execute automotive-specific risk assessments (Automotive Safety Integrity Levels, ASILs)
  • Apply ASILs to identify the item’s required safety criteria to reach a satisfactory residual risk
  • Deliver specifications for verifying and validating techniques to guarantee an adequate level of safety is being reached
  • Understand ISO 26262 requirements
  • Discuss the functional safety issues in automotive development
  • Comprehend the official safety management procedures and the suggested processes to support such
  • Execute risk analysis
  • Understand the functional safety notion
  • Understand technical safety notions and associated system design
  • Develop safety-based hardware and software
  • Develop and execute a practical method to safety analysis

Course Outline

Overview of ISO 26262

  • Origin of ISO 26262
  • ISO 26262 terminology
  • ISO 26262 requirements
  • ISO 26262 applications
  • ISO 26262 life cycle

ISO 26262 Life Cycle

  • Management
  • Development
  • Production
  • Operation
  • Service
  • Decommissioning

 ISO 26262 Parts

  • Vocabulary
  • Functional safety management
  • Concept stage
  • Product development: System level
  • Product development: Hardware level
  • Product development: Software level
  • Production and operation
  • Supporting processes
  • ASIL-based and Safety-based assessment
  • Guidelines on ISO 26262

IEC 61508 Comparison 

  • Part 1: General requirements
  • Part 2: Requirements for electrical/electronic/programmable electronic safety-associated systems
  • Part 3: Software specifications
  • Part 4: Definition and abbreviations
  • Part 5: Techniques for the identification of safety integrity levels
  • Part 6: Guidelines on the parts 2 and 3 applications
  • Part 7: Overview of methods and measures

Automotive Safety Integrity Levels (ASIL)

  • ASILs mitigating risk methods
  • ASIL levels A-D, with D being the most demanding
  • Hazard risk assessment
    • Exposure
    • Severity
    • Controllability

Part 2: Management of Functional Safety

  • Planning, coordinating, and documenting actions
  • Functional safety management lifecycle implementation
  • Safety management after Start of Production (SOP)
  • Safety management during development

Functional Safety Management Verification

  • Confirmation review
  • Functional safety audit
  • Functional safety analysis
  • Confirmation measures requirements

Part 4: Product Development – System Level

  • Technical Safety Requirements
  • System Design
  • Item incorporation and testing
  • Safety validation
  • Functional safety evaluation
  • Release for manufacturing

Validation Process Components

  • The construction and structure of the item
  • The description of test cases
  • The acceptance requirements
  • The necessary environmental conditions

Release for Production Documentation

  • Name and signature of the individual accountable for release
  • Version(s) of the released piece
  • Configuration of the released part
  • References to relevant documents
  • The date of release

Part 6: Product Development – Software Level

  • Product development at software level
  • Modeling and coding procedures
  • Software safety requirements specification
  • Software safety requirements verification
  • Software design
  • Structural design verification
  • Design and execution of software unit
  • Software unit evaluation
  • Test case requirements
  • Test case configuration measures
  • Software integration
  • Software safety requirements verification

How to Integrate Software Tools In ISO 26262

  • V model
  • Coding standard enforcement
  • Cyclomatic complexity
  • Software structural design
  • Data and control flow
  • Software unit examination
  • Unit test case execution
  • Coverage assessment
  • Traceability matrices
  • Software lifecycle traceability

 

ISO 26262 Training: Automotive Safety

Request More Information

  • Please complete the following form and a Tonex Training Specialist will contact you as soon as is possible.

    * Indicates required fields

  • This field is for validation purposes and should be left unchanged.