Skip to main content
Concept guide · ISO 26262-1 / ISO 26262-5 · 16 chapters

Faults, Errors & Failures

Master ISO 26262-5 failure taxonomy, random hardware fault classification, latent fault analysis, multi-point fault concepts, common-cause failures, and the FMEDA methodology for hardware metrics calculation.

Chapters
16
Chapters
Core Method
FMEDA
Core Method
Analysis
MPF
Analysis
Calculation
PMHF
Calculation
Included inProExpert
The short version

Quick answers

What is the difference between a fault, an error, and a failure in ISO 26262?
ISO 26262-1 defines a precise causal chain. A fault is an abnormal condition that can cause an element to fail - a stuck-at transistor, a corrupted memory cell, a software defect. An error is a discrepancy between the computed or observed value and the correct one - the fault has become visible in the element's state. A failure is the termination of the element's intended behavior - the error has propagated to the element's output. Fault leads to error leads to failure, and safety mechanisms work by breaking this chain: detecting the fault or error before it becomes a safety goal violation.
What are single-point, residual, latent, and safe faults?
ISO 26262-5 classifies random hardware faults by their effect. A single-point fault is the worst kind: on its own, with no second fault needed, it can break a safety goal, and no safety mechanism stands in its way. A residual fault is the portion of a covered fault that escapes the safety mechanism because diagnostic coverage is below 100%. A multi-point fault only violates the safety goal in combination with another fault; when no safety mechanism reports it and the driver cannot notice it, it is called latent: it quietly removes a layer of protection while everything still appears to work. A safe fault cannot contribute to a safety goal violation at all. This classification is the backbone of the FMEDA and directly determines SPFM and LFM.
Why this course · ISO 26262, Part 1, Clause 3

Why it pays for itself

Get the vocabulary exactly right

Fault, error, and failure are not synonyms in ISO 26262. Learn the precise Part 1 definitions and the fault-error-failure chain that every FMEDA, metric, and safety mechanism argument is built on.

Classify faults like an analyst

Work through single-point, residual, latent, multi-point, and safe fault categories - the classification that decides which failure rates count against SPFM and LFM and which safety mechanisms earn coverage credit.

Connect taxonomy to metrics

See how random hardware fault classification, latent fault analysis, and common-cause failure concepts flow directly into the FMEDA methodology and the PMHF calculation your hardware evidence depends on.

After the course

What you’ll be able to do

Apply ISO 26262 Failure Taxonomy

Use precise ISO 26262 definitions for faults, errors, and failures, correctly classifying hardware failure modes in FMEDA analysis.

Classify All Hardware Fault Types

Correctly classify single-point, residual, latent, dual-point, and multi-point faults for every failure mode in a hardware element FMEDA.

Analyze Common-Cause Failures

Identify CCF vulnerability in redundant architectures and quantify CCF contributions using beta-factor analysis with appropriate prevention measure credits.

Build Complete FMEDAs

Construct rigorous FMEDA worksheets from element identification through failure rate sourcing, DC assessment, and safety classification.

Source Failure Rate Data

Select, apply, and justify failure rate data from IEC 62380, SN 29500, and supplier-specific sources with correct application factor calculation.

Map FMEDA to HW Metrics

Correctly map FMEDA fault classifications to SPFM, LFM, and PMHF hardware metric calculations per ISO 26262-5.

The curriculum · 16 chapters

Chapter by chapter

  1. 01

    Overview & Motivation

    Understand why precise failure taxonomy is foundational to ISO 26262 hardware safety. Learn how fault, error, and failure definitions underpin FMEDA, hardware metrics, and safety mechanism design.

    • Taxonomy importance
    • Connection to metrics
    • Module roadmap
  2. 02

    Definitions & Taxonomy

    Master ISO 26262 precise definitions of fault, error, failure, violation, and their subcategories. Understand the ISO 26262-1 vocabulary and how it differs from common engineering usage.

    • ISO 26262-1 definitions
    • Fault-error-failure chain
    • Vocabulary precision
  3. 03

    Random Hardware Faults

    Understand random hardware faults arising from physical degradation mechanisms in semiconductors and electronic components. Covers failure mechanisms, failure rate models, and the FIT rate concept.

    • Physical mechanisms
    • FIT rate concept
    • Failure rate models
  4. 04

    Systematic Faults

    Distinguish systematic faults from random faults. Understand how design errors, process errors, and usage errors become systematic faults, and how ISO 26262 processes address systematic fault avoidance and control.

    • Systematic vs. random
    • Design error sources
    • Process error control
  5. 05

    Latent Faults

    Master the concept of latent faults in ISO 26262 hardware analysis. Understand latent fault definition, the ASIL-dependent latent fault tolerance requirements, and how diagnostic coverage affects latent fault residuals.

    • Latent fault definition
    • ASIL tolerance table
    • DC impact on latency
  6. 06

    Multi-Point Faults

    Analyze dual-point and multi-point fault scenarios that bypass single-point fault coverage. Understand fault independence requirements, multi-point fault avoidance, and how MPF metrics relate to PMHF calculation.

    • Dual-point faults
    • Independence requirements
    • MPF contribution to PMHF
  7. 07

    Common-Cause Failures

    Identify and mitigate Common-Cause Failures (CCF) including dependent failures that can defeat redundant safety architectures. Covers CCF analysis methods, beta-factor models, and prevention measures.

    • CCF analysis methods
    • Beta-factor model
    • Prevention measures
  8. 08

    Transient vs. Permanent

    Distinguish transient faults (soft errors, EMC-induced) from permanent faults in hardware reliability analysis. Understand how this distinction affects failure rate data, diagnostic coverage, and safety mechanism design.

    • Transient fault sources
    • Soft error rates
    • Diagnostic implications
  9. 09

    FTTI Calculator

    Calculate Fault Tolerant Time Intervals for hardware fault scenarios using timing models derived from ISO 26262-4. Understand how FTTI constrains diagnostic timing budgets and safety mechanism latency requirements.

    • FTTI derivation
    • Timing budget allocation
    • Diagnostic timing constraints
  10. 10

    Beta-Factor Analysis

    Apply beta-factor analysis for quantifying common-cause failure contributions in redundant hardware architectures. Covers the IEC 61508 beta-factor checklist approach adapted for ISO 26262 automotive context.

    • Beta-factor checklist
    • Automotive adaptation
    • CCF quantification
  11. 11

    Failure Rate Data

    Source, evaluate, and apply failure rate data from industry databases (IEC 62380, SN 29500, MIL-HDBK-217) for FMEDA. Understand operating conditions, application factors, and how to justify failure rate assumptions.

    • IEC 62380 & SN 29500
    • Application factors
    • Data justification
  12. 12

    Bathtub Curve

    Understand the bathtub curve failure rate model and its phases: infant mortality, useful life (constant failure rate), and wear-out. Learn how automotive production screening and lifetime design address each phase.

    • Bathtub curve phases
    • Production screening
    • Lifetime design
  13. 13

    FMEDA Builder

    Build a complete Failure Mode Effects and Diagnostic Analysis (FMEDA) from scratch. Cover element identification, failure mode enumeration, failure rate allocation, diagnostic coverage assessment, and safety classification.

    • FMEDA worksheet structure
    • DC assessment method
    • Safety classification
  14. 14

    Handling Mechanisms

    Map hardware fault types to appropriate handling mechanisms: detection, indication, prevention, and tolerance. Understand mechanism selection criteria for each fault class and ASIL.

    • Mechanism taxonomy
    • Selection criteria
    • ASIL mapping
  15. 15

    HW Metrics Mapping

    Connect FMEDA fault classifications to SPFM, LFM, and PMHF hardware metrics calculations. Understand exactly how each fault category contributes to or exempts from metric denominators and numerators.

    • SPFM contribution
    • LFM contribution
    • PMHF summation
  16. 16

    Case Studies

    Apply the complete fault and failure analysis framework to real hardware examples including a microcontroller-based ABS controller, a redundant position sensor system, and an Ethernet switch for ADAS.

    • ABS FMEDA walkthrough
    • Redundant sensor analysis
    • ADAS Ethernet assessment
Interactive Tools

Not just text: the visual toolkit

Fault Taxonomy Tree

Interactive hierarchical diagram of the complete ISO 26262 fault and failure taxonomy with clickable nodes showing definitions, examples, and connections to hardware metrics.

FMEDA Builder Worksheet

Interactive FMEDA worksheet with guided entry for failure modes, failure rates, diagnostic coverage, and automatic classification of SPF, RF, LF, and MPF contributions.

Bathtub Curve Visualizer

Animated bathtub curve showing failure rate phases over component lifetime with configurable screening effectiveness, burn-in period, and wear-out onset parameters.

CCF Beta-Factor Calculator

Interactive IEC 61508 beta-factor checklist tool adapted for automotive systems, computing CCF contribution to PMHF with configurable prevention measure credits.

Multi-Point Fault Analyzer

Visual tool for identifying and analyzing dual-point and multi-point fault combinations in a hardware architecture, showing independence requirements and PMHF contributions.

Failure Rate Data Selector

Interactive database browser for IEC 62380 and SN 29500 failure rate data with application factor calculators, temperature derating curves, and automotive use-case defaults.

Real-World Application

FMEDA for Redundant Wheel Speed Sensor System

Complete FMEDA walkthrough for a dual-channel wheel speed sensor system used in an ABS application at ASIL-C, covering all fault classifications and SPFM/LFM calculations.

  • System architecture definition with sensor, signal conditioning, and MCU interface elements
  • Failure mode enumeration for 8 hardware elements with IEC 62380 failure rate sourcing
  • Diagnostic coverage assessment for each failure mode and safety mechanism
  • SPF, RF, LF, and MPF classification for all 47 identified failure modes
  • Beta-factor analysis for CCF between redundant sensor channels
  • SPFM and LFM calculation showing ASIL-C target compliance at 98.1% / 92.4%
Wheel Speed Sensor FMEDA
Failure mode enumeration - 47 failure modes across 8 hardware elements

Unlock 5 more analysis phases

Built for

Who this guide is for

  • Engineers new to functional safety who need the foundational vocabulary fast
  • Hardware analysts classifying faults in an FMEDA worksheet
  • Reviewers untangling misused terms in supplier safety documentation
  • Exam candidates who must distinguish fault classes under time pressure

Frequently Asked Questions

Common questions about Faults, Errors & Failures

A latent fault is a multi-point fault that remains undetected by any safety mechanism and unperceived by the driver. Alone it is harmless, which is precisely the danger: it can sit in a redundant channel or a monitoring path for months, and when the second fault arrives the protection you were counting on is already gone. That is why ISO 26262-5 defines the Latent Fault Metric with targets up to 90% for ASIL D, and why diagnostic test intervals and power-up self-tests exist - to find latent faults before the second fault finds them.
Random hardware faults arise from physical degradation mechanisms in semiconductors and electronics - they occur unpredictably in time but at statistically predictable rates, expressed in FIT. Systematic faults are baked in by a mistake in specification, design, or manufacturing, and reproduce deterministically under the same conditions; software bugs are always systematic. The distinction drives the whole standard: random faults are managed quantitatively with metrics and safety mechanisms, systematic faults are managed with process rigor - the ASIL-dependent methods, reviews, and verification the lifecycle prescribes.
The guide runs 16 chapters from definitions and taxonomy through random hardware faults, systematic faults, fault classification, latent fault analysis, multi-point fault concepts, and common-cause failures to the FMEDA methodology that turns the taxonomy into hardware metrics. It is the foundation module for the hardware metrics and FMEDA material elsewhere in the library. A free account starts you off, and the Pro and Expert plans unlock more of the library.

Start the course today

A free account unlocks one full concept guide, 3 work product templates, 1 guided process, the Markov simulator, and 5 practice exams per month. The Pro and Expert plans unlock more of the 78-guide library. No credit card required.